Bringing a broken smartphone back to life. How to restore, turn on the ZTE touch, what to do if the smartphone does not turn on Restoring the ZTE phone to a working state

Initially, ZTE Skate was introduced with an operating Android system 2.3.5, which caused some criticism. To date, the network has a sufficient number of official and unofficial firmware to update Skate. Some of them are presented below.

Official firmware on ZTE Skate

Download firmware for ZTE Skate Android 2.3.5 (OUK_P743TV1.0.0B08 dated 05/21/2012) you can use this.

It is necessary to unpack the archive, copy the image.bin file on the SD card to the image folder and follow the installation instructions from the archive. The instruction is written in English in pdf format with screenshots.

Also, some official firmware for ZTE Skate are presented here. The official Android 4.0 firmware has not yet been presented, so you will have to use unofficial firmware.

Unofficial firmware on ZTE Skate

Installation of unofficial firmware is performed in the following sequence:

Remap your phone's memory.

Copy firmware.

Download ClockWorkmod Recovery(Home + Sound Up + ON).

Run in mounts and storage:

Format sd-ext (if available)

Run in advanced:

Wipe dalvik cache

Wipe battery stats

Flash ROM (install zip from SD card- choose zip from SD card- select firmware - confirm).

Reboot (reboot system now), wait a few minutes after the system is fully loaded, reboot into CWM.

Flash Gapps, reboot.

For ZTE Skate Android 4.0.3, cyanogenmod 9 is installed. A description of the installation and links to download the firmware can be found in this.

Another firmware presented on ZTE Skate and, as well as Android 4.2.1 and (check md5)

Update

In the case when it is necessary to install an update of the same firmware on the ZTE Skate, then the following order must be followed:

Copy ROM and Gapps.

Download CWM.

We execute in mounts and storage:

We execute in advanced

Wipe dalvik cache

Wipe battery stats

Flash ROM, reboot.

Download CWM, flash Gapps.

Reboot.

Do not forget that any flashing is performed at your own peril and risk. Before starting, the phone must be 100% charged.

An example of installing Cyanogenmod 10 on ZTE Skate can be viewed in the video.

Update ZTE Skate to Android 4.1 JellyBean.

Most of the articles in the X-Mobile column are devoted to hacks and tweaks that require obtaining root rights, modifying the firmware or replacing it with a custom one. However, not every reader is ready to expose their smartphone to such operations, fearing that they can turn the device into a brick or lead to instability in operation. Today I will debunk these myths and show that even in the most stalemate situation, bringing a smartphone back to life is not so difficult.

Destroying myths

Let's talk about what it is to “turn a smartphone into a brick” and what other pitfalls a user can expect on the way to changing the system and installing custom firmware. What glitches can be caught at the same time and is it possible to kill a smartphone by flashing it incorrectly? Will you lose the warranty forever or can the smartphone be returned to its previous state? Is not it custom firmware can let the smartphone owner down 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 that anyone who wants to flash a smartphone faces is that during the installation of the firmware, a failure can 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 while being used. To be able to install third-party firmware on your 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 in no way associated 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 installation of the firmware, the smartphone will not be able to boot it, however, the recovery console will remain in place, and all that needs to be done is to boot into recovery again and reinstall the firmware.

In addition, any custom recovery console contains a backup / restore function that allows you to make backup the 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 ask: what happens if there is a failure during the installation of the Recovery Console itself? Nothing, in this case the reverse situation will turn out, when the operating system itself will remain in place, and the console will be lost. To deal with it, just re-flash recovery directly from Android.

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

Conclusion: kill the smartphone by installing third-party firmware through a custom recovery console, it's not possible. Either recovery or the primary bootloader will always remain in place.

Myth 2. Custom firmware is unreliable

Firmware firmware is different. 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 instability in the smartphone and 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 an 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 a developer with the nickname Quarx. Their difference lies in the fact that the CyanogenMod team is responsible for the support and proper operation of the first, while the second is Quarx personally. Official firmware versions are usually fully functional, but the correct operation of the latter depends on a third-party developer.

Well, the third. There are stable and development versions of the firmware. Stable versions of CyanogenMod have the index M (CyanogenMod 11.0 M7, for example). This version of the firmware 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 the “normal” firmware on your smartphone, the risk of running into bugs is minimal. Everything else is for experimenters.

Myth 3. Software that requires root rights can corrupt a smartphone

In theory, an application with root rights can do anything with the firmware of a smartphone, including erasing it completely. Therefore, with such software, you must be extremely careful. The software that we talk about on the pages of the magazine is completely safe and tested on 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 encounter a situation where root-supported 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 the smartphone vulnerable to viruses

It is not root rights that make a smartphone vulnerable to viruses, but the bugs used to obtain them. Rooting tools and viruses can use the same Android vulnerabilities to gain root permissions, so the very fact having root does not change anything on the device. A well-written virus will not ask for permissions in a standard way, giving away its presence, it will instead take advantage of 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 firmware allows you to disable root or create whitelists of applications that can use these rights.

Myth 5. A rooted smartphone can fail

Rooting software does four simple things: runs an exploit that allows you to gain root access on the system, mounts the /system partition in writable mode, copies the su binary required to gain root rights later on into the /system/xbin directory, and establishes supersu app or SuperUser, which will take control every time an application asks for root permissions with su.

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

Myth 6. Rooting 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 official app from the manufacturer.

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 delivers an elevated level android security, 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 a trigger that confirms the fact of modification. The trigger is implemented in hardware (eFuse chip), so resetting it to its initial position will not work. On the other hand, it is not entirely clear whether service center on this basis, repair the device. Secondly, the eFuse chip is also installed on some other devices (for example, smartphones from LG), and it also allows you to accurately determine whether the smartphone has been rooted or flashed.

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

On some smartphones, it is possible to lock the bootloader back, but you should learn about this separately, and 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 here 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 find fault with 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, you can disable it 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 corrupt a smartphone in a purely technical reasons. The only exception is an attempt to hack the bootloader in order to unlock 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 possibility of turning 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 a loss of 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 when getting root and flashing and how to deal with them.

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

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

Outwardly, all these problems usually manifest themselves either in endless resets of the smartphone to the initial logo of the manufacturer, or in the so-called boot-loop, when the loading animation spins on the screen for more than five to ten minutes. There are also problems with the screen (multi-colored ripples) and a non-working touch screen, which also prevent the use of a smartphone.

In all these cases, it is enough to make 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 a failed installation or update of the Recovery Console. The problem is that after rebooting the smartphone and turning it on with the volume down button held down, a black screen appears, after which the smartphone either resets or hangs.

Solving this problem is not easy, but very simple. You can install the recovery console on the vast majority of smartphones using applications TWRP Manager, ROM Manager or ROM Installer. They themselves determine the smartphone model, download and flash the required recovery without requiring a reboot. If with their help it is not possible to restore the console, it is enough to find instructions on the Web for recovery installation 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 shows, it is quite real. There are two ways to get out of this situation: use fastboot to upload recovery to your smartphone, or use a tool from the manufacturer to install stock firmware. We will take a closer look at the second method in the next section, and I will talk about fastboot here.

Fastboot is a tool that works directly with the primary bootloader of the device 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 block the ability to use it. So you will have to consult the Internet about its availability.

To access fastboot, you will need drivers and the Android SDK. 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 .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 scratching a smartphone and for removing traces of rooting and flashing. Unfortunately, I can't talk about all the possible models, so I'll focus on the four most popular flagships: Nexus 5 (I call this instance the control), Galaxy S5, LG G2 and Sony Xperia Z2.

Nexus 5 and other Google phones

Restoring Nexus devices to their original state is easier than any other smartphone or tablet. In fact, it is so simple that there is not even anything to talk about. In fact, all you need to do is install the ADB / fastboot drivers (on Linux you don't even need them), download the firmware archive 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 pressed (both) and connect using a USB cable.
5. Unpack the archive with the firmware and run the flash-all.bat (Windows) or flash-all.sh (Linux) script and wait for the operation to complete.
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 who are wondering what the script does, here is a list of commands:

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

Galaxy S5

So Galaxy smartphone S5 is a little more complicated, but overall pretty simple. This time you will need the Samsung Odin application, with 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. We go to the site samfirmware.com, enter the SM-G900F model in the search, find the firmware marked Russia, download and unpack.
4. We 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. We 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 until the firmware process is completed.

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

LG G2

Restoring the LG G2 to its factory state will also not cause any problems. The number of steps in this process is somewhat larger, but in 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 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, just like with Samsung, the smartphone will still be rooted, and this cannot be fixed.

Sony Xperia Z2

Now about how to return to the factory state Sony smartphone Xperia Z2. As in the previous two cases, this will require stock firmware and the official firmware utility. You run the utility on your PC, connect your smartphone with a USB cable, and start the update process. Step by step it 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. We turn off the smartphone and turn it on while holding down the volume down and "Home" keys.
6. We connect the smartphone to the PC using a USB cable and run the Flash Tool.
7. Press the button with the lightning bolt 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, the unlocked bootloader will not allow you to update over the air.

In 90% of cases, unlocking the bootloader will delete 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 scary and dangerous operations as they might seem at first glance. If you do everything right and do not resort to tools that unlock the smartphone's bootloader bypassing the manufacturer's tools, you will not be able to corrupt the smartphone. Yes, in some cases you will have to tinker to get everything back in place, but is it better to use a locked smartphone that does not allow you to do half of the things that it is capable of, or to take full control of the device? In the end, reinstalling windows on the PC does not scare anyone.

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

It is clear what to do with a brick, but what to do with such a phone? How to revive and start it? Of course, there is no universal remedy, for each ZTE a6, a610 plus, z11 s, z17 and other models, there are recovery methods phone.

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

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

Carelessness or error when flashing a ZTE phone/smartphone device v7 model 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 let you into recovery, FTM or fastboot, then do not despair. There is one more remedy left:

Recovery of dead ZTE phones at home.

Restoring a ZTE phone to a working state.

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

Restoring a ZTE phone from a "brick" state.

ZTE phone recovery through SEMCtool.

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

How to resolve "Error while executing operation" in Java on ZTE phones.

How to turn on your ZTE phone.

To enable 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 went dark, press and release the power key to turn it on.
- a lock image will appear on the screen, to unlock the screen, drag the lock icon or click on it.
- when prompted to enter a code, enter the PIN code from your SIM card. In most cases it is 0000 and click OK.
- wait for the phone to start.

Note: The PIN code from the SIM card is located on a plastic card or in the package received when buying a SIM card in the cabin cellular communication. But be careful, if the PIN code is not correct 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 using the passport of the citizen of the Russian Federation for which the SIM card is issued. Therefore, do not enter your PIN incorrectly more than three times. If you have lost your PIN code and there is no way to restore it through your carrier, you can do the following.

Cancel the request to enter a pin code when you turn on your ZTE mf 180, l4, a5 phone. To do this, find another SIM card with a known pin code for you (you can assign a pin code in the settings) and insert it into your phone. Turn on the phone according to the points 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 request to enter a PIN code when turning on the phone of the ZTE af 3 phone - dpi. Having done this, turn off the phone and change the SIM cards. Now, when you turn on the phone, the system will not require you to enter a 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 Settings menu. To correct an error when entering the 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 your ZTE af 3, a3, x9 phone. But the problem of not turning on the phone can be not only because of the "flying" software, but also because of the breakdown of the power button off the phone, breakdown or failure of the battery - charger and etc.

ZTE phone does not turn on. What to do?.

Instructions for restoring a phone ZTE l110 phone on an OS platform on a screen with a resolution, type from a non-working state - a brick 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 grey, 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 the cell phone does not 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, icons on the screen mean? cell phone? How to decipher the icon displayed at the top of the mobile phone display?
	Here you can find the latest and most 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.

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

If custom or official firmware on ZTE has not yet been added here, 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. ZTE Skate 2 firmware will also appear on this page. Please note that this ZTE model requires an individual ROM file, so you should not try firmware files from other devices.

What are custom firmware (firmware)?

1. CM - CyanogenMod
2. lineageOS
3. paranoid android
4. OmniROM
5. Temasek's

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

• If the Skate 2 does not turn on, for example, you see a white screen, hangs on the splash screen, or the notification light only blinks at all (possibly after charging).
• If it freezes when updating / freezes when turned on (requires flashing, 100%)
• Not charging (usually, hardware problems)
• Can't see sim card
• The camera does not work (for the most part, hardware problems)
• Sensor not working (depending on the situation)

Hard Reset for ZTE Skate 2

Instructions how to do hard reset on ZTE Skate 2 (factory reset). We recommend that you familiarize yourself with 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 to enter Recovery?

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

Reset settings on ZTE Skate 2 can be done in a very simple way:

1. Settings->Backup & Reset
2. Reset settings (at the very bottom)

How to reset pattern

How to reset graphic key if you forgot it and now you can't unlock your smartphone. On the Skate 2, the key or PIN can be removed in several ways. You can also remove the lock by resetting the settings, the lock code will be deleted and disabled.

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