The situation when a smartphone based on Android refuses to reset to factory settings is one of the most alarming for the user. The device may freeze at the logo, display a system error, or simply reboot again without completing the cleaning process. This is not just a software failure, but often a protective mechanism or a symptom of deep damage to the file system.
The reasons for this behavior can vary from a banal lack of space in the system partition to the triggering of protection FRP (Factory Reset Protection), which blocks the reset if there is a linked Google account. Understanding the nature of the failure is critically important, since incorrect actions can turn the phone into a “brick.”
In this article we will analyze in detail the technical aspects of why the procedure does not complete successfully, and we will offer step-by-step algorithms for solving the problem for various scenarios, including working through Recovery Mode and using a PC.
FRP protection and account blocking Google
One of the most common reasons why the reset does not go through or is blocked immediately after it starts is the security system FRP. If the device has been added Google account and the “Find my device” function is enabled, the system requires confirmation of the password before completely clearing the data.
This is done to protect against theft: an attacker will not be able to simply erase the data and resell the phone. If you try to reset through the settings menu, but the system asks for a password that you don't remember, the process will be stopped. In some cases, when you try to reset via Recovery, after rebooting the phone will require you to enter the details of the last synchronized account.
Ignoring this requirement results in the device remaining locked, even if the files have been deleted. The system considers a reset attempt without authorization as suspicious activity.
⚠️ Warning: Bypassing FRP protection using third-party utilities may violate the warranty and lead to system instability in the future. Use only legal methods of restoring access.
If you have forgotten your login information, the only legal way to unlock it is to restore access through the official Google website on any other device. Attempts to “break through” the protection through the engineering menu often lead to a complete blocking of the bootloader.
Damage to the system partition and firmware errors
The second common reason for a failed reset is damage to the operating system files. If the partition /data or /system has bad sectors or the file structure is broken, the reset script simply cannot be completed to the end.
This often happens after an unsuccessful update OTA (over the air) or when there is a sudden power outage while writing data. The system tries to delete user data, but encounters a read/write error and interrupts the process, returning the phone to its original state while saving the problematic files.
In such cases, the standard procedure through the menu Settings → Recovery and reset rarely helps. A deeper intervention is required, up to flashing the device through a computer using the manufacturer’s official utilities, such as Odin for Samsung or SP Flash Tool for MediaTek.
How to check the integrity of the file system?
To check, you can start the phone in Recovery mode and select "Wipe cache partition". If the process ends with an error, the problem is definitely in the file system.
It is also worth noting that on custom firmware or devices with unlocked Bootloaderreset scripts may not work correctly due to changes in the partition structure made by modification developers.
Lack of free memory for execution operations
Paradoxically, to perform a reset, the phone requires a certain amount of free RAM and internal memory. The wipe process creates temporary logs and requires CPU resources to correctly overwrite partition tables.
If the internal storage is full (less than 100 MB left), the system may not have space to create temporary files needed by the formatting procedure. As a result, you see an endless loading or an error message.
- 📉 Full cache: Accumulated application data interferes with the correct operation of system services.
- 💾 Fragmentation: Severe memory fragmentation on older devices slows down the recording process.
- 🔋 Low charge: The system blocks resource-intensive operations when the charge is less than 15%.
The solution in this case could be preliminary cleaning of garbage or an attempt to reset through recovery mode, where resource requirements are lower, since the main system is not is loading.
Before attempting a reset, make sure that the battery charge is at least 50%. A sudden power outage during formatting is the main reason for turning a smartphone into a “brick.”
Conflicts with superuser rights (Root) and modifications
Presence root access and installed system modifications (for example, Xposed Framework or Magisk) often becomes an obstacle to a regular reset. The factory reset script is designed to work with a standard file structure.
If you have superuser rights, some system files can be protected from deletion or moved to hidden partitions. When the standard reset utility tries to delete them, it is denied access or does not find the files in the expected paths.
In some cases, after a reset, “garbage” of access rights remains on the rooted device, which leads to a cyclic reboot (bootloop). The phone turns on, shows the logo, turns off, and so on in a circle.
adb reboot recoveryTo solve the problem, you often need to first remove root access through a manager application (for example, SuperSU or Magisk Manager), selecting the “Full removal” option, and only then perform a factory reset.
Hardware malfunctions of the drive
The most unpleasant scenario — physical degradation of the internal memory chip (eMMC or UFS). Over time, the memory cells wear out and go into read-only mode or completely refuse to write data.
In this state, the phone may become unstable, applications crash, and an attempt to reset the settings ends in failure, since the system is physically unable to write new configuration files. This often occurs on older smartphone models or devices that have been exposed to overheating.
| Symptom | Probable cause | Solution |
|---|---|---|
| Reset failed error | Logical failure Software | Reset via Recovery |
| Endless reboot | Damaged bootloader | Flashing via PC |
| Stuck on logo | Wear memory (eMMC) | Replacing the board or chip |
| Require a Google account | FRP protection | Entering account data |
It is difficult to diagnose a hardware problem at home, but an indirect sign may be the inability to write any file to the phone or constant errors when installing applications.
Forced reset methods via Recovery Mode
If the standard method through the settings menu does not works, you must use recovery mode (Recovery Mode). This is a separate mini-section in the phone's memory, which allows you to control the system bypassing the main interface.
To enter this mode, you usually need to turn off the phone and hold down a combination of buttons (most often Volume Up + Power or Volume Down + Power). The combination depends on the manufacturer: y Xiaomi this is often the volume up button, y Samsung is the home button (on older models) or volume up when connected to a PC.
☑️ Algorithm of actions in Recovery
In the recovery menu, navigation is carried out using the volume buttons, and selection is made using the power button. You need to find the item Wipe data/factory reset. After selection, the system will ask for confirmation, usually this is item Yes -- delete all user data.
⚠️ Attention: The Recovery interface may differ depending on the Android version and manufacturer. Some devices (for example, new Samsung) require a long press of the power button to confirm actions.
After completing the process, be sure to select the item Reboot system now. The first launch after such a reset may take up to 10-15 minutes, as the system optimizes applications.
Resetting via Recovery Mode ignores many software interface locks, but does not remove FRP protection if the phone was linked to an account.
Using ADB for remote formatting
For advanced users, there is a method reset via USB debugging using the tool ADB (Android Debug Bridge). This method is effective if the touch screen does not work or the system freezes at the boot stage.
To do this, you need to enable “USB Debugging” in the developer menu (if this has been done previously) and connect the phone to the computer. Then a reset command is sent via the command line.
adb shell recovery --wipe_dataOr an alternative command for some versions:
adb reboot recoveryAfter entering the command, the phone will automatically reboot into recovery mode and begin the cleaning process. This method allows you to bypass some graphical interface errors that prevent you from performing a manual reset.
What to do if the phone is not detected by the computer?
Make sure that the ADB drivers for your phone model are installed. Try using a different USB cable and a different USB port (preferably USB 2.0). Also check if USB debugging is enabled in the developer settings.
Is it possible to reset without losing photos and contacts?
A full factory reset (Hard Reset) by definition deletes ALL user data. You can save photos and contacts only by first synchronizing them with the Google cloud or copying them to your computer before the procedure.
Why does the phone ask for the password for the old lock screen after resetting?
This is normal behavior of the Android security system. After powering on for the first time after a reset, you must enter the last known password, PIN, or pattern that was used before the reset to confirm that the device is not stolen.
How long does the reset process take?
Usually the process takes from 5 to 15 minutes. If the phone hangs in the cleaning phase for more than 30 minutes, there is likely a problem. In this case, you should force a reboot of the device.
Will a reset help if the phone is infected with a virus?
In 99% of cases, a full reset removes viruses, since they are located in the user memory section. However, if a virus has penetrated the system partition (which is rare without root access), a complete flashing of the device may be required.