Zte skate 2 brick restoration. Installing official and unofficial firmware on ZTE Skate. Restoring your ZTE phone to working condition

After incorrect firmware, your phone may become inoperative, or as it is called on the Internet, it will become a "brick". Then the question arises of how to restore the Android brick yourself. Most sources will advise you to immediately contact the Service Center, but we recommend that you try everything first. available options"Resuscitation". In this article, we will describe all sorts of options in order to make a functioning smartphone out of a "ripped" Android again.

The last update of the article - 03/29/2018

We completely remove the consequences of an unsuccessful firmware

Let's start with the first few steps that will need to be done one by one. In order not to call Android “device” and other names, the word “phone” will be used in the future, so it is more convenient and understandable.

Reviving the phone / tablet via Recovery

If the phone is still on, turn it off. Then hold down the volume button and the power button at the same time. After this procedure, the smartphone will open dual menu Recovery... Two options will be presented:

• Restore the backup (this item is the main requirement for the firmware, if the smartphone was flashed, then the backup was also restored). Select the early position of your system, then the backup will start in Backup and restore.
• Chapter Install zip from sd card allows you to start the firmware installation process. At this point, you need to specify the exact path to the archive with the firmware. This option deals with system recovery. Especially if the phone was turned off while installing important files.
  You may also be interested in the article.

But sometimes, when the firmware is launched, it may not be possible to enter Recovery. Then the situation can be eliminated only with the involvement of third-party programs... Typically this application TWRP Manager, ROM Manager or Installer which are the most popular in the field.

These programs allow you to select all the necessary components for a specific version of the operating system, automatically detecting the gadget and launching Recovery.

If none of these programs helped launch Recovery, then you can try to find a program that can run it on a specific smartphone model.

Above, we discussed how to restore your Android if it still had chances of a painless "resurrection". Now let's consider what to do with it if the device was completely damaged and became a "brick" that does not function at all. If you think that this process is very difficult, then you should not immediately run to the workshop and pay the master, first try to do it yourself. Let's try to fix the situation on our own at home.

This instruction is based on the restoration of phones and tablets from Samsung. If you have a different brand of device, then you need to choose a different program or choose an option using FlashTool... Difficult to find the right one? Write to us in the comments - we will help you!

We perform a few simple step-by-step actions:

1. Install the latest USB driver for Samsung on PC;
2. Download and install the latest version of the program Odin(https://w3bsit3-dns.com/forum/index.php?showtopic=648344);
3. Next you need download the official(not author's) firmware for your model;
4. Turn off the device, then press "-" on the volume key and "Home".

After a while, a warning will appear.

1. Press "+" on the volume key, after which the smartphone will enter Odin mode;
2. After, we connect it to the computer;
3. Launch Odin, then press PDA, after which we designate the file in it tar.md5 in the directory where the firmware is located;
4. Next by clicking "Start", we run the recovery program, after which the smartphone will be ready for use.

In such a simple way, we returned the "brick" to its original state of a normal functioning device.

1. We charge the phone to the maximum so that it does not turn off during recovery (let it stand for a couple of hours on charging);
2. Let's take a smartphone that has turned into a real "brick";
3. Next, download the official firmware in FTF format;
4. Then you need to install the Flashtool program along with installation files firmware to your computer;
5. If your antivirus program often swears at other programs, then it is better to turn it off for a while, so that it does not interrupt the firmware process.

Directly the operation itself to restore Android through Flashtool:

• Turn off Android;
• Place the FTF file with the firmware at: C: \ Users \ UserName \ .flashTool \ firmwares;
• After starting, select the correct PC bit (32 or 64);
• Press the key with lightning logo;
• We turn on the mode “ Flashmode”;
• Next, a drop-down window will appear in which you select the available firmware in this program;
• At the moment when the firmware is ready, the program itself will inform you that it is time to connect to the PC;
• First, the program detects the device and then the Android recovery will start. After everything is successful, a sign “ Flashing finished”;
• After that, the smartphone must be disconnected from the computer and everything will work.

Video instruction

Answers to your top 4 questions about Android resuscitation The computer does not see the Odin program.

Check serviceability installed drivers, if necessary, reinstall them, disable the antivirus. And the most commonplace - check the USB cable and connectors.

The smartphone turned into a brick as a result of a fall, and not because of a failed firmware. Can you save it yourself?

Operating room Android system on each individual device has its own system, that is, software components. If it happens that your device has become a "brick", then it is best to find instructions for a specific smartphone.

Most of the articles in the X-Mobile section are devoted to hacks and tweaks that require getting root rights, modification of the firmware or its replacement with custom. However, not every reader is ready to subject his smartphone to such operations, fearing that they can turn the device into a brick or lead to instability in work. Today I will debunk these myths and show that even in the most stalemate situation, it is not so difficult to bring a smartphone back to life.

Destroying myths

Let's talk about what it is all the same "to turn a smartphone into a brick" and what other pitfalls may await the user on the way to change the system and install custom firmware. What glitches can you catch and can you kill a smartphone by flashing it incorrectly? Will you lose your warranty forever or can your smartphone be returned to its previous state? Can custom firmware fail the smartphone owner at the most inopportune moment and are they worth it?

Myth 1. Incorrect flashing can kill a smartphone

A fall from the fifth floor can kill a smartphone, but not a flashing. The main problem faced by anyone who wants to reflash a smartphone is that during the installation of the firmware, a failure may occur, which will lead to its inoperability, and the smartphone will actually turn into a brick.

All this is true, but only on paper. To understand why, it is enough to understand how the process of flashing a smartphone works and what system components are used in this case. To be able to install third-party firmware on a smartphone, you need to unlock the bootloader (not in all cases), get root and install a custom recovery console (ClockworkMod or TWRP) that can install firmware with any digital signature.

The Recovery Console is stored in a separate section of the internal NAND memory and is not connected in any way with the installed operating system. After installing a modified version of the console, it will be possible to flash custom firmware or even another OS (Firefox OS, for example). If a failure occurs during the firmware installation, the smartphone will not be able to load it, but the recovery console will remain in place, and all that needs to be done is to reboot into recovery and reinstall the firmware.

In addition, any custom recovery console contains a backup / restore function that allows you to do backup main firmware and restore it unchanged (with all applications, settings and data) in case something goes wrong. In fact, the smartphone can be returned to its original state.

You may be asking: what happens if a failure occurs during the installation of the Recovery Console itself? Nothing, in this case, the situation will be the opposite, when the operating system itself remains in place, and the console will be lost. To deal with it, you just need to re-flash recovery directly from Android.

Hypothetically, one can imagine a situation where both the firmware and the recovery console will be killed (although this is quite difficult to do), but even in this case, the primary bootloader will always remain in place, flashed into the permanent memory of the smartphone.

Conclusion: kill the smartphone by installing third party firmware via a custom recovery console is not possible. Either recovery or the primary bootloader will always remain in place.

Myth 2. Custom firmware is unreliable

Firmware firmware strife. In the open spaces world wide web you can find a huge number of Android assemblies for every taste and color, and most of them are really slag, which can lead to instabilities in the smartphone and the loss of some functionality. Therefore, the first thing to remember is that you should only deal with serious custom firmware developed by large teams of experienced developers. First of all, these are CyanogenMod, Paranoid Android, AOKP, OmniROM and MIUI.

Second. There are two types of firmware: officially supported and ported by third-party developers. The same CyanogenMod, for example, has official version for the Nexus 4 smartphone, but does not have one for the Motorola Defy. But for Defy there is an unofficial port of CyanogenMod 11 from the developer with the nickname Quarx. Their difference lies in the fact that the CyanogenMod team is responsible for the support and proper performance of the former, while the latter is personally responsible for Quarx. Official firmware versions are usually fully functional, but the correctness of the second depends on a third-party developer.

And the third thing. There are stable and development versions of the firmware. Stable versions of CyanogenMod have an M index (CyanogenMod 11.0 M7, for example). This firmware version usually does not contain bugs. Development versions (in the case of CyanogenMod, these are daily nightly builds) may contain bugs and are therefore not recommended for everyday use.

Conclusion: if you install a stable official version of "normal" firmware on your smartphone, the risk of encountering bugs is minimal. Everything else is for the experimenters.

Myth 3. Software that requires root privileges is capable of corrupting a smartphone

In theory, a rooted app can do whatever it wants with a smartphone's firmware, including erasing it completely. Therefore, you need to be extremely careful with such software. The software that we are talking about on the pages of the magazine is completely safe and tested in its own skin. In addition, for the entire time of using smartphones on Android (and this is starting from version 1.5) I never did not come across a situation where rooted software would kill a smartphone.

Software distributed through Google play, usually fully corresponds to the declared characteristics, and if it led to a brick or left a backdoor in the bowels of the smartphone, it would not last even a week in the store. In any case, here you need to follow the "trust but verify" rule and carefully read the instructions for using root applications.

Myth 4. Root rights make a smartphone vulnerable to viruses

It is not root permissions that make a smartphone vulnerable to viruses, but bugs used to obtain them. Rooting tools and viruses can use the same Android vulnerabilities to get root rights, so the mere fact of having root on the device does not change anything. A well-written virus will not ask for rights in a standard way betraying his presence, he will instead use the same vulnerability to get them stealthily.

Moreover, having root, you get the opportunity to install a fresh Android version(in the form of custom firmware), in which these bugs have already been fixed. Also, do not forget that most custom firmwares allow you to disable root or create whitelisting applications that can use these rights.

Myth 5. A rooted smartphone can fail.

Root software does four simple things: it launches an exploit that allows you to gain root privileges on the system, mounts the / system partition in write mode, copies the su binary to the / system / xbin directory, which is required to get root privileges in the future, and installs a SuperSU or SuperUser application that will take control every time an application asks for root privileges with su.

None of these steps can crash or kill the smartphone. The only thing that can happen is that the exploit will cause a segmentation error and the smartphone will reboot, after which it will continue to work normally.

Myth 6. Getting root and installing custom firmware will void my warranty

The warranty is lost not from the very fact of getting root, but because of its discovery by the service center. Most devices can be unrooted using the Universal Unroot app or by reinstalling the stock firmware using the manufacturer's official app.

There are, however, two exceptions to this rule. The first is the Knox system pre-installed on new smartphones and Samsung tablets such as Galaxy S4, S5, Note 3 and Note 10.1. Knox provides an increased level of security for Android, responding to any firmware modifications and installation of third-party kernels and firmware. In the event that the user performs these actions, the system sets up a trigger that confirms the fact of modification. The trigger is implemented in hardware (eFuse chip), so you won't be able to reset it to its initial position. On the other hand, it is not entirely clear whether service center on this basis, to repair the device. Second: the eFuse chip is installed on some other devices (for example, smartphones from LG), and it also allows you to accurately determine if the smartphone has been rooted or flashed.

If we talk about custom firmware, everything is more complicated here. Usually, a flashing operation requires unlocking the bootloader, and this can be done either using special exploits or using the web service of the smartphone manufacturer. In any case, the unlocked bootloader will definitely indicate that the smartphone did not belong to a blonde.

On some smartphones, it is possible to lock the bootloader back, but you should learn about this separately, and also keep in mind that a newly locked bootloader will most likely receive the Re-locked status, and not Locked, as it was originally (this happens on HTC smartphones, for example). The only exceptions are smartphones and tablets of the Nexus line, the bootloader of which can be locked and unlocked in three clicks without any dancing with a tambourine, and no one will pick on anything.

INFO

On Linux, ADB and Fastboot can be installed separately from the Android SDK. On Ubuntu: sudo apt-get install android-tools-fastboot. On Fedora: sudo yum install android-tools.

To prevent the Knox system from interfering with root applications, it can be disabled using the following command from the terminal: su pm disable com.sec.knox.seandroid.

conclusions

Getting root and flashing a smartphone are absolutely safe operations that cannot ruin a smartphone for purely technical reasons. The only exception is trying to hack the bootloader to unblock it. In this case, the eFuse chip (if there is one in the smartphone) may work and block the ability to turn on the smartphone.

Fortunately, today smartphone manufacturers either prefer not to block the ability to turn on a smartphone with a hacked bootloader (by setting a trigger indicating the fact of such an action, as Knox does), or they implement a special web service that allows you to painlessly unlock the bootloader with the loss of the smartphone warranty. which saves users from having to risk breaking the bootloader.

Problems that may arise when flashing

So, now let's talk about what problems can arise with getting root and flashing and how to deal with them.

Scenario one: after an unsuccessful flashing, the smartphone stopped loading

An unsuccessful flashing can be caused by several factors: the battery has run out and the firmware is only half full, the firmware turned out to be faulty or intended for a different smartphone model. In the end, there was simply not enough space on the smartphone, which can happen when trying to install a fresh version of Android on a smartphone three or four years ago.

Outwardly, all these problems usually manifest themselves either in endless smartphone resets to the manufacturer's initial logo, or in the so-called boot loop, when the boot animation spins on the screen for more than five to ten minutes. Problems with the screen (multicolored ripples) and a non-working touchscreen are also possible, which also impede the use of the smartphone.

In all these cases, it is enough to do one simple thing: turn off the smartphone by long pressing the power button, then turn it on with the volume down button held down (some smartphones use a different combination), and after you get into recovery, reinstall the firmware (Install zip from sdcard -> Chooze zip from sdcard) or restore the backup (Backup and restore -> Restore). Everything is easy and simple.

Scenario two: firmware works, but recovery is not available

This can happen after an unsuccessful installation or update of the Recovery Console. The problem is that after restarting the smartphone and turning it on with the volume down button held down, a black screen appears, after which the smartphone is either reset or freezes.

Solving this problem is not easy, but very simple. You can install the recovery console on the vast majority of smartphones using the TWRP Manager, ROM Manager or ROM Installer applications. They determine the smartphone model themselves, download and flash the required recovery without requiring a reboot. If you cannot restore the console with their help, it is enough to find instructions on install recovery to your device.

Scenario three: neither firmware nor recovery is available

To be honest, it is difficult for me to imagine such a scenario, but, as practice confirms, it is quite real. There are two ways to get out of this situation: use fastboot to upload recovery to a smartphone, or use a tool from the manufacturer to install the stock firmware. We'll take a closer look at the second method in the next section, and I'll talk about fastboot here.

Fastboot is a tool that works directly with the device's primary bootloader and allows you to upload firmware to your smartphone, recover and unlock the bootloader (in Nexus devices). Fastboot support is available in many smartphones and tablets, but some manufacturers are blocking its use. So you have to consult the Internet about its availability.

You need drivers and Android SDK to access fastboot. When they are installed, open command line, go to the SDK installation directory, then to the platform-tools directory, turn off the smartphone, turn it on with the volume buttons held down (both) and connect it with a USB cable to the PC. Next, you need to find the recovery image in the .img format for your device and run the command:

$ fastboot flash recovery image.img

Or even force the smartphone to download recovery without actually installing it:

$ fastboot boot image.img

In the same way, you can flash official firmware update:

$ fastboot update update-file.zip

You can find a recovery suitable for your device either on the TWRP website, or in the XDA-Developers and w3bsit3-dns.com forums.

We return the smartphone to its original state

In this section, I will talk about ways to return a smartphone to a clean drain, no matter what state it is in. These instructions can be used both for splitting up the smartphone and for removing traces of rooting and flashing. Unfortunately, I cannot tell you about all the possible models, so I will focus on the four most popular flagships: Nexus 5 (I call this one the control one), Galaxy S5, LG G2 and Sony Xperia Z2.

Nexus 5 and other Googlephones

Returning Nexus devices to their original state is easier than any other smartphone or tablet. In fact, it is so simple that there is nothing to even talk about. In fact, all you need to do is install the ADB / fastboot drivers (in Linux, even they are not needed), download the archive with the firmware and run the script. Step by step, the whole operation looks like this:

1. from here.
2. Download and install the Android SDK.
3. Download the archive with the firmware for the desired device from the Google website.
4. Turn off the device, turn it on with the volume buttons held down (both) and connect using a USB cable.
5. Unpack the archive with the firmware and run the script flash-all.bat (Windows) or flash-all.sh (Linux) and wait for the operation to end.
6. We launch the command line, go to the directory with the Android SDK, then platfrom-tools and execute the fastboot oem lock command to lock the bootloader.

For those wondering what the script does, here's a list of commands:

Fastboot flash bootloader bootloader-DEVICE-NAME-VERSION.img fastboot reboot-bootloader fastboot flash radio radio-DEVICE-NAME-VERSION.img fastboot reboot-bootloader fastboot flash system system.img fastboot reboot-bootloader fastboot flash userdata recovery recovery.img fastboot flash boot boot.img fastboot erase cache fastboot flash cache cache.img

Galaxy S5

With Galaxy smartphone The S5 is a little more complicated, but overall pretty simple. This time, you will need the Samsung Odin application, with the help of which the smartphone will be flashed. Sequencing:

1. Download and install the latest Samsung USB drivers from here.
2. Download and install the latest version of Odin from here.
3. Go to samfirmware.com, enter the model SM-G900F in the search, find the firmware marked Russia, download and unpack it.
4. Turn off the smartphone and turn it on with the volume down and Home buttons held down, wait five seconds until a warning message appears.
5. Press the volume up button to put the smartphone into Odin mode.
6. We connect the smartphone using a USB cable.
7. Launch Odin, press the PDA button and select the file with the tar.md5 extension inside the directory with the unpacked firmware.
8. Press the Start button in Odin and wait for the firmware process to end.

As I said, this operation will return the smartphone to its original state, but it will not reset the trigger, system-installed Knox (if it was in stock firmware). Therefore, the service center may refuse to repair.

LG G2

Restoring the LG G2 to its factory state shouldn't be too problematic either. The number of steps in this process is somewhat larger, but by themselves they do not require special training and knowledge. So, what to do to return the factory firmware to the G2:

1. Download and install ADB Driver Installer from here.
2. Download the official firmware (Europe Open 32G or Europe Open) from here.
3. Download and install the LG Mobile Support Tool and FlashTool (goo.gl/NE26IQ).
4. Turn off the smartphone, hold down the volume up button and insert the USB cable.
5. Expand the FlashTool archive and run the UpTestEX.exe file.
6. In the window that opens, select Select Type -> 3GQCT, Phone Mode -> DIAG, in the Select KDZ file option, select the firmware downloaded in the second step.
7. Press the CSE Flash button at the bottom of the screen.
8. In the window that opens, click Start.
9. In the next window, select the country and language and click Ok.
10. We are waiting for the end of the firmware, and then turn off and turn on the smartphone.

It's all. But keep in mind that, as is the case with Samsung, the smartphone will still have Rooted status, and this cannot be fixed.

Sony Xperia Z2

Now how to return to the factory state Sony smartphone Xperia Z2. As in the previous two cases, this will require a stock firmware and an official firmware utility. You launch the utility on your PC, connect your smartphone with a USB cable and start the update process. Step by step it all looks like this:

1. Download and install ADB Driver Installer from here.
2. We reset the smartphone to factory settings.
3. Download and install Flash Tool from the official Sony website and latest firmware from here.
4. Copy the firmware file to the C: / Flashtool / Firmwares directory.
5. Turn off the smartphone and turn it on with the volume down and Home keys held down.
6. We connect the smartphone to the PC using a USB cable and launch the Flash Tool.
7. Press the button with the lightning icon in the Flash Tool. In the window that opens, select Flashmode, double-click on the firmware in the list that opens.

WARNING

In many smartphones, a jailbroken bootloader will prevent over-the-air updates.

In 90% of cases, unlocking the bootloader will result in the deletion of all data from the smartphone, including the memory card.

conclusions

Flashing a smartphone, and even more so getting root access, is not at all such terrible and dangerous operations as they might seem at first glance. If you do everything correctly and do not resort to tools that unlock the smartphone's bootloader, bypassing the manufacturer's tools, it will not be possible to turn the smartphone over. Yes, in some cases you will have to tinker in order to put everything back in place, but which is better - to use a locked smartphone, which does not allow you to do even half of the things that it is capable of, or to gain full control over the device? Finally, reinstalling windows on the PC does not scare anyone.

Official Android firmware 4.2 [stock ROM file] -
Custom ZTE firmware -

If you haven't added a custom or official firmware on ZTE, then create a topic on the forum, in the section, our specialists will promptly and free of charge help, incl. with backup and manuals. Just do not forget to write a review about your smartphone - this is extremely important. This page will also display firmware for ZTE Skate 2. Please note that this ZTE model requires an individual ROM file, so you should not try firmware files from other devices.

What custom firmware are there?

1. CM - CyanogenMod
2. LineageOS
3. Paranoid Android
4. OmniROM
5. Temasek's

1. AICP (Android Ice Cold Project)
2. RR (Resurrection Remix)
3. MK (MoKee)
4. FlymeOS
5. Bliss
6. crDroid
7. Illusion ROMS
8. Pacman ROM

Problems and disadvantages of a smartphone from ZTE and how to fix them?

• If Skate 2 does not turn on, for example, see White screen, hangs on the screen saver, or the notification indicator only blinks (possibly after charging).
• If it freezes when updating / freezes when it is turned on (needs a flashing, 100%)
• Doesn't charge (usually iron problems)
• Doesn't see the SIM card (SIM card)
• The camera does not work (mostly hardware problems)
• Sensor does not work (depending on the situation)

For all these problems, contact (you just need to create a theme), specialists will help for free.

Hard Reset for ZTE Skate 2

Instructions on how to do Hard reset on ZTE Skate 2 (factory reset). We recommend that you read the visual guide, which is called on Android. ...

Reset codes (open the dialer and enter them).

1. *2767*3855#
2. *#*#7780#*#*
3. *#*#7378423#*#*

Hard Reset via Recovery

1. Turn off the device-> go to Recovery
2. "Wipe data / factory reset"
3. "Yes - delete all user data" -> "Reboot System"

How do I log into Recovery?

1. hold down Vol (-) [volume down], or Vol (+) [volume up] and the power button
2. a menu with the Android logo will appear. Everything, you are in Recovery!

Factory reset on ZTE Skate 2 can be done in a very simple way:

1. Settings-> Recovery and reset
2. Reset settings (at the very bottom)

How to reset your pattern

How to reset graphic key if you forgot it and now you cannot unlock your ZTE smartphone... On the Skate 2, the key or PIN can be removed in several ways. You can also remove the lock through a factory reset, the lock code will be deleted and disabled.

1. Reset graph. blocking -
2. Password reset -

Phone recovery phone / smartphone ZTE model 7 on operating system with a screen - dpi made of bricks. A modern mobile phone is such a complicated thing that it is better not to go into its insides unnecessarily.

It so happens that due to lack of knowledge or carelessness, after an unsuccessful flashing, changing the software, the phone does not turn on, it is blocked. In this state, the phone / smartphone ZTE model 7 on an operating system with a screen - dpi called "brick".

It's clear what to do with a brick, but what to do with such a phone? How to reanimate and run it? Of course, there is no universal tool, for each model ZTE a6, a610 plus, z11 s, z17 and other models, there are their own recovery methods phone.

Errors on the phone, how to turn on the phone ZTE m2, l5, af 3. Restoring from a brick state.

Information on how to recover ZTE l110, z10, black, ZTE 4g, 5, 8 phone after flashing or from a locked state, or when the phone does not turn on, you can read on specialized forums and sites.

Negligence or error when flashing a ZTE model v7 phone / smartphone device on an operating system with a screen - dpi.

If you did something unhealthy with your ZTE 8, 20, a910 phone, and after that it stopped loading at all and does not start up either in recovery, or in FTM, or in fastboot, then do not despair. There remains one more remedy:

Restoring dead ZTE phones that won't turn on at home.

- recovery of ZTE phones after unsuccessful firmware. The description posted on the site uses the so-called Jag method. The essence of the method is that it is necessary to make a special Jag plug by soldering the contacts (4 and 5) to each other through a 301 kOhm resistor. This Jag is inserted into the phone ZTE phone a6 - dpi with the battery removed. More details on how to restore your phone in this way are described here.

Restoring your ZTE phone to a working state.

- for phone owners. You can view a list of all supported devices, such as the ZTE a610 plus phone - dp and others, the Motorola Phone Recovery FAQ is posted on the link above. The site also provides a description of restoring the phone by closing the contacts with the battery removed.

Before restoring your phone, you need to download and install special program on the pc: Random "s Developments Flash & backup. Next, you need to: remove the battery, close contacts 4 and 5 on the phone connector (see photo), keeping the needles closed insert the battery, open the needles, insert the cord into the connector and connect to the computer, into Random "s Developments Flash & backup program should display a message that the ZTE z11 s - dpi phone is connected.

Restoring a ZTE phone from a "brick" state.

- this method of recovering ZTE a610c, 4, mf920 phones different models, different manufacturers. When restoring a ZTE v, mf823d, a210 phone, special software is used: a standard flasher from MTS, a programmer from ZTE and a HEX editor. A detailed description with screenshots of actions is posted on this page of the site (see link).

ZTE phone recovery via SEMCtool program.

- this instruction is for restoring some ZTE models. Breakdown symptoms: phone ZTE 610, mf90, t620 hangs on "Please wait", blinks with white display, no network signal, no connection via DCU-60, neither via "C" or via "2 + 5". The method of restoring the phones of the ZTE z17 - dpi phone posted on this site is the use of a service cable, together with the SEMCtool v8.7 software, which can be downloaded for free, on the same site.

Restoration of a water damaged ZTE cell phone - a drowned man.

- instructions with pictures on how to restore a ZTE g phone, zte nubia 32gb 32 gb, 6 after dropping it into the water. In order to prevent corrosion of the elements of the phone of the ZTE m2 - dpi phone, you must very quickly pull it out of the water and remove the battery. Then the case is removed and the phone is placed in a jar filled with rice for two days. The fact is that rice absorbs moisture very well and is an excellent absorbing agent. Ordinary homemade rice will draw out all the moisture from the smallest components of the ZTE t320, a330, mf823 phone, and also prevent corrosion. Cat litter can be used as an absorbent at home.

How to fix "Error performing operation" in Java on ZTE phones.

- instructions for users of ZTE a465, f660, a476 phones in case of problems installing applications or games on the phone. If, when entering the application / game folders, the message "An error occurred during the operation" pops up, it means that the Java machine on the ZTE l5 phone has crashed - dpi. This problem can be solved by simply removing and inserting the memory card into the phone. If this does not help, more complex actions will be required. To restore the Java machine to work, you will need to reflash the firmware FS file and do finalization. More details on how to do this are described in this article.

How to turn on your ZTE phone.

To turn on touch phone ZTE 510, blade, mf667, you need to do the following:

Press and hold the Power key until the phone vibrates.
- if the phone was turned on, but the screen is dark, press and release the power key to turn it on.
- an image of a lock will appear on the screen, to unlock the screen, drag the lock icon or click on it.
- when prompted to enter the code, enter the PIN from your SIM card. In most cases this is 0000 and click OK.
- wait for the phone to start.

Note: The PIN code from the SIM card is on a plastic card or in the package received when buying a SIM card in the salon cellular... But be careful, if the PIN code is incorrect three times, you can activate the SIM card only through the PUK code, which is also included in the package received when buying a SIM card. If the PUK code is lost, it will be possible to restore it only with the passport of a citizen of the Russian Federation for which the SIM card is issued. Therefore, do not enter the PIN code incorrectly more than three times. If you have lost your PIN-code and there is no way to recover it through your service provider, you can do the following.

Cancel the pin code request when you turn on your ZTE mf 180, l4, a5 phone. To do this, find another SIM card with a PIN code known to you (the PIN code can be assigned in the settings) and insert it into your phone. Turn on the phone according to the steps described above, when entering the password, enter the PIN code you know from another SIM card. Having successfully turned on the phone, go to the phone settings and cancel the PIN code request when you turn on the phone of the ZTE af 3 - dpi phone. Having done this, turn off your phone and change SIM cards. Now, when you turn on the phone, the system does not require you to enter the PIN code.

This is of course elementary advice, but there is a solution to problems and more serious.

Advice. Initially, the SIM PIN is provided by your network operator, but you can change it later in the Options menu. To correct a mistake in entering your SIM PIN, tap the Delete icon.

ZTE phone does not turn on! Phone self-test error

The very first thing to do is to try to reflash the ZTE af 3, a3, x9 phone. But the problem of not turning on the phone may be not only due to the "flown" software, but also due to the breakdown of the power button to turn off the phone, breakdown or failure of the battery - charger and etc.

ZTE phone won't turn on. What to do?.

- very detailed description fixes the problem phone ZTE z7, nubia z9 max, gf3 does not turn on, how to turn on the phone. The article is divided into points, with the solution to each problem point by point: checking the power source - the battery, the power button is faulty, the power button circuits, the power controller or its soldering failure, secondary power sources - the power supply of the processor, memory and rest. devices, setting software mobile phone ZTE af 3 - dpi.

Instructions for restoring a phone, a ZTE l110 phone on an OS platform on a screen with a resolution, a type of non-working state - brick More details on how to restore the device, turn on the touchscreen ZTE v8, 10, 7, v7, a6, a610 plus, z11 s, z17, m2, l5, af 3, l110, z10, black, zxhn h118n, 4g, 5, 8, 20, a910, a610c, 4, mf920, v, mf823d, a210, 610, mf90, t620, n1, g, zte nubia 32gb 32 GB, 6, t320, a330, mf823, a465, f660, a476, 510, blade, mf667, mf 180, l4, a5, s6, l3, v815w, l2 lte, af 3, a3, x9, z7, nubia z9 max , gf3, v5, x5, axon mini, af3, blade q lux, lite, af5, 1920x1080, hn, l370, v2 white, MTS 535, geek pro, leo black, z5s, star, z5 gray, s, v987, t220 , t221 red, x7 lte, x3 gold, m, v790, blade v807, v880g, v880e, v970, v970m, v889m, skate, grand era, r221, mimosa, v8110, a21plus, v71b, e7, v9c 1, light tab 2 , v9s 3g, light tab 3, light tab v9a, v9 light, v98, life and what to do if your cell phone won't turn on.

Popular ZTE Reviews

	How to watch, listen to outdated files in old formats, in particular, flash format on the phone?
	What do the displayed icons mean, icons on the screen cell phone? How to decipher the icon displayed at the top of the mobile phone display?
	Here you can find the most recent and up-to-date drivers for mobile phones and ZTE tablets. This link contains the correct, correct programs and latest versions drivers for mobile devices ZTE.
	If for some reason you have difficulty connecting your ZTE phone to a laptop or PC via wifi, bluetooth, usb, read the following instructions.