The situation where Xiaomi smartphone stops responding to touch or endlessly reboots, familiar to many users. In such cases, the standard settings menu becomes unavailable, and the only way out is to use the computer and debugging interface. ADB (Android Debug Bridge is a powerful tool that allows you to force clear partitions of a device’s memory, even if the operating system is unstable. IT-specialists and enthusiasts for deep cleaning of the gadget before resale or after unsuccessful experiments with root rights.
However, interfering with system partitions through the command line requires extreme care and understanding of the processes that are taking place. Incorrectly entered commands can lead to complete loss of data or, in the worst case, turn the phone into a “brick.” In this article, we will discuss in detail how to prepare the computer and smartphone, which commands to use for different boot modes, and how to avoid critical errors when performing the Hard Reset procedure over the debugging bridge.
Before you start taking action, you need to make sure you're aware of the risks, the data stored in your internal memory will be permanently destroyed, and if you have the option to turn on your device for even a few minutes, make sure to back up important contacts and photos in the Mi Cloud cloud or on your computer, and then we'll move on to the technical part of preparing your environment.
Preparation of the working environment and drivers
The first step is to install the necessary software on your personal computer. Without properly installed drivers, the system simply will not see the connected smartphone in debugging mode. You will need to download Platform Tools from the official Android developer site, since this package contains executable files adb.exe and fastboot.exe. Once you download the archive, it must be unpacked into the root folder on the disk, for example, C:\platform-tools to avoid problems with long paths.
Next, you need to ensure communication between the PC and the device. To do this, the smartphone should activate the “Debug USB” function. If the menu is available, go to Settings → About the phone and seven times click on the MIUI build number to unlock the developer menu. In the section that appears for developers, find the appropriate switch and activate it. When the cable is first connected, a request for debugging permission will appear on the phone screen - be sure to click “Allow” and check “Always Allow from this computer”.
An important nuance is the choice of quality USB-Cheap charging cables often lack data lines, leading to connection errors. Use the original wire or certified analogue, connecting it directly to the motherboard port, preferably at the back of the system unit, bypassing the system unit. USB-hub.
You can check the success of the driver installation through Windows Device Manager. When you connect your smartphone, the Android Composite ADB Interface device should appear in the list. If you display Unknown Device or Android instead, you will need to manually install drivers through the Manager, indicating the path to the folder with platform tools.
ADB Basic Commands for Entering Recovery Mode
Once you've successfully connected your device, you can go to sending commands. Open the command line (CMD) or PowerShell in the tool folder and type in the adb device command. If your device serial number appears on the list, the connection is correct. Now you need to move the phone to Recovery mode, where the direct reset occurs.
This is done using a reboot command to a special mode. Enter in the terminal:
adb reboot recovery
After this command, the smartphone should reboot and show the Mi logo, and then go to the Recovery menu. The interface may differ depending on the version of MIUI: in global versions, it is usually a graphic menu with touchscreen support, and in Chinese it is a text menu controlled by volume buttons. If the phone just rebooted in normal mode, then the command was not accepted, or access rights block the action.
What if the ADB can’t see the device?
If the adb device command returns an empty list or unauthorized status, check the cable and USB port. Also make sure that the phone screen does not have a debugging permission request. Sometimes it helps to reconnect the cable after unlocking the screen. If nothing helps, try installing Google USB Driver universal drivers. There is an alternative way to log into recovery mode if the standard command does not work. You can try the combination: adb shell reboot recovery This method is sometimes effective on devices with a heavily modified shell. Remember, the goal of this step is to get into an environment where you can perform a full Fboot access via the Wirecover or a full ADBype. If your smartphone is in Fastboot mode (a screen with a picture of a hare repairing an android), you can reset directly bypassing the Recovery menu. This is especially true for devices that have damaged the recovery partition. Connect the phone in this mode to the computer and check the connection with the command: fastboot When the serial number is successfully displayed, you can initiate a cleanup of user data. The reset command for erase userdata is as follows: fastboot will delete all user files, applications will be deleted, and the most secure option for the user, however, the full Recoverydata is also used after the first option. Once you log in (as described in the previous section), select Wipe Data, then Wipe All Data, and confirm the action. 💡If after a reset, the phone requires a Mi Account that you don't remember, it's protection. FRP (Factory Reset Protection: Without entering your Google or Mi Account account that your phone is synced to, you can't log in. It's important to understand the difference between erase commands in Fastboot and standard vape in Recovery. Fastboot commands are low-level and can be dangerous if misused, as they allow you to erase system partitions, which will cause the device to fail. Use them only for userdata and cache partitions. Problem diagnosis and error code tables While working with the userdata and cache partitions. ADB You may encounter different error messages. Understanding them will help to quickly correct the situation and continue the reset procedure, most often problems are related to drivers, access rights or the status of the bootloader. Below is a table with the most common errors and ways to solve them: Error / Message Probable cause Method of solution no devices/emulators Found Drivers not installed or cable damaged Reinstall drivers, replace USB-cable, check Device Manager unauthorized Not confirmed permission on the phone screen Unlock screen, click "Allow" in the debugging dialog box FAILED (remote: 'Command not allowed') Locked Bootloader Unlock bootloader via Mi Unlock Tool (requires account) Wait for device Phone is not in mode Fastboot/ADB Reboot the phone in the desired mode (Recovery or Fastboot) Particular attention should be paid to the error associated with the blocked bootloader. On modern Xiaomi smartphones, many Fastboot commands are blocked if the status of the bootloader is locked. In this case, you will not be able to execute fastboot erase userdata. The only way out is to use the Recovery menu, which is available even with a locked bootloader, or officially unlock through the Mi Unlock utility. It's also worth noting that some commands may claim superuser rights, and if you've previously obtained root rights, the commands may run differently, ADB It works with the rights of the ordinary user (shell), which limits access to critical system partitions, but allows you to manage user data. ADB You can't reset the device, and there are alternative methods that can help bring the smartphone back to life. EDL (Emergency Download Mode). This mode is designed for deep firmware recovery at the Qualcomm level and allows you to flash the phone even with a completely non-functioning bootloader. EDL You usually need to disassemble the phone and close special contacts on the board, or use a special combination of buttons when connecting the cable (depending on the model), this mode uses the Mi Flash Tool program and the firmware image in.tgz format. This is a more complex method, requiring an account with authorization (for new models) and accurate firmware selection. ⚠️ Attention: Entering mode EDL On new Xiaomi models (after 2020), it often requires an authorized service center account. EDL It might not work. Another option is to use a Recovery. TWRP, if it has been previously established. Custom Recovery allows you to reset partitions, backup and restore the system more flexibly than the standard menu. TWRP You can also send it through ADB, Using adb reboot recovery and then managing the menu. Frequently asked questions (FAQ) Is it safe to drop Xiaomi through the ADB? Yes, if you only use commands to clean user data (userdata, cache), but there is always a risk: the wrong command can damage system files. Be sure to back up before you start work. ADB? No, you don't need to log in to Recovery and perform a standard reset. To execute fastboot erase commands on some models and versions MIUI You may need to unlock the bootloader. What if the phone doesn't turn on after the reset? Try pressing the power button on the back of the phone. 15-20 seconds. If that doesn't work, log in to Recovery mode and try resetting again or flashing through the Mi Flash Tool. Will ADB remove the Google Account Reset (FRP)? No, standard data reset doesn't remove the Google account binding. Once turned on, the phone will require you to enter a login and password from an account that was synced earlier. This is anti-theft protection. Can you interrupt the reset process? It's strongly discouraged to interrupt the partition formatting process. This can damage the file system and require complex recovery via EDL.