Running Recovery Mode on Xiaomi smartphones (including Redmi and POCO sub-brands) is a skill for anyone who wants to reset, flash the device or fix software failures. This mode gives access to low-level system functions, but its activation often raises questions about which buttons to pinch, what to do if the phone does not respond, and how not to turn the gadget into a brick.
In this article, we will discuss all the current ways to log into Recovery (including hidden methods for new models from 2023-2026), explain the difference between stock recovery and custom recovery (for example, TWRP), and warn against typical errors.
What is Recovery Mode and Why You Need It
Recovery Mode is a separate micro OS built into a smartphone at the firmware level, which works independently of the main Android system and allows you to:
- π Reset the settings to factory (full wipe)
- π¦ Install official or custom firmware (fastboot or ADB sideload)
- π§ Fix download errors (such as bootloop)
- π Unlock the bootloader for advanced users
- π‘ Update the system manually if OTA-update is not working
Xiaomi smartphones use two types of Recovery:
- Stock Recovery is a standard mode from the manufacturer with limited features (reset and upgrade only via.zip).
- Custom Recovery (e.g. TWRP) is an extended version with support for backups, root rights and installation of unofficial firmware.
β οΈ Note: Login to custom recovery on a locked bootloader will result in a reset of all data! Xiaomi automatically formats the partition /data When uncertified software is found.
Method 1: Standard button input (for a working phone)
This is the most versatile method, which works on 90% of Xiaomi/Redmi/POCO models, including the new Xiaomi 14 series, Redmi Note 13 and POCO F6.
- Turn off your smartphone (press Power + select βSwitch offβ or hold the button for 10 seconds).
- Press the Power button + Volume Up button Hold them for 10-15 seconds until the Mi logo and Recovery menu appear.
- Release the buttons when you see the screen with the Android robot and the inscription No command (on some models, the menu will immediately open).
- If No command appears, press Power + Volume Up again for 1-2 seconds.
New devices (such as Xiaomi 13T or Redmi K70) may require additional confirmation via Mi Account, which is protection against unauthorized resets.
Turn off your phone (not reboot!)
Check the battery power (minimum 30%)
Prepare. USB-cable (if you plan to install the cable)
Make sure the buttons don't stick
-->
Method 2: Sign in via ADB (if the phone is turned on but the buttons are not working)
If the physical buttons are broken or unresponsive, you can run Recovery via ADB (Android Debug Bridge) which requires that you run Recovery through the Internet.
- π₯οΈ Computer with installed Xiaomi drivers and ADB Tools.
- π Included debugging by USB (Settings β The phone. β Version. MIUI (7 times press) β Additionally. β For developers β Debugging by USB).
- πΆ Working USB-cable (preferably original).
Instructions:
- Connect your smartphone to your PC and confirm the debugging permission on your phone screen.
- Open the command prompt (cmd) in the ADB folder and type: adb devices Make sure the device is identified (serial number should appear).
- Recovery: Adb Reboot Recovery: Adb Reboot Recovery
β οΈ Note: On some models (e.g, POCO X5 Pro) after this command, the phone can restart to Fastboot instead of Recovery.
π‘
If the adb reboot recovery command doesnβt work, try first restarting to fastboot (adb reboot bootloader), and then running Recovery from it with a combination of buttons.
Method 3: Sign in via Fastboot (if the phone doesn't turn on)
If Xiaomiβs smartphone doesnβt respond to the power button or is stuck on the logo, the only way to get into Recovery is through Fastboot mode, which is also suitable for devices with damaged firmware (bootloop).
Step-by-step:
- Turn off your phone (if it freezes, hold the Power + Volume Down for 20 seconds).
- Press the combination to enter the Fastboot: Power button + Volume Down button Hold until the image of the hare in the hat appears (Fastboot logo).
- Connect your phone to your PC and open the command line with ADB.
- Enter the command: fastboot reboot recovery If the device does not respond, try: fastboot oem reboot-recovery
On some models (e.g. Redmi Note 12), this command may be followed by a FAILED error (remote: unknown command).
- First, unlock the bootloader (fastboot oem unlock).
- Then repeat the reboot command in Recovery.
What if the Fastboot doesnβt recognize the device?
Features of the entry into Recovery on new Xiaomi models (2023-2026)
Starting with MIUI 14 and new devices (e.g. Xiaomi 14 Ultra, Redmi K70 Pro), Xiaomi has tightened protection against unauthorized access to Recovery.
- π Entering a password from Mi Account (if an account is linked).
- π± Confirmation through SMS Mi Cloud app.
- π§ Unlock bootloader to access advanced functions.
Also, on some devices, the Recovery menu can be in Chinese (even on global firmware) to change the language:
- In the Recovery menu, find an item with characters (language).
- Choose English or Russian (if available).
| Xiaomi model | Features of the entrance to Recovery | Is a Mi Account required? |
|---|---|---|
| Xiaomi 13/13 Pro | Standard button combination, but you may need to confirm via SMS | Yeah (on reset) |
| Redmi Note 12/13 | Menu in Chinese by default, language changes manually | No (unless the account is tied) |
| POCO F5/X5 | Entrance ADB It could be moved to Fastboot. | Yes (when unlocking bootloader) |
| Xiaomi Pad 6 | Power + Volume Up + Volume Down (hold 15 seconds) | Yes. |
Xiaomi (series 11/12/13/14)
Redmi (Note, K-series)
POCO (F, X, M-series)
Another brand
I don't know.-->
Frequent mistakes and their solutions
Even experienced users have problems logging in to Recovery, and here are the most common errors and ways to fix them:
- π« Phone doesn't respond to a combination of buttons Reason: button sticking, battery dead or hardware failure Solution: try charging the device for 30 minutes, then try again. If it doesn't, use the method through ADB or Fastboot.
- π After logging in to Recovery, the phone immediately restarts The reason: damaged firmware or conflict with custom Recovery Solution: Fastboot mode, run the official firmware through the Mi Flash Tool.
- π Requires a password from Mi Account, but it is not the reason: the phone was tied to the account of the previous owner.Solution: contact Xiaomi support with proof of purchase or use the official unlock tool (Mi Unlock Tool).
- π΅ Recovery menu does not have the option "Wipe Data" Reason: custom Recovery installed (for example, TWRP) Solution: Look for Wipe points. β Format Data or Advanced Wipe.
β οΈ Warning: If after resetting via Recovery, the phone requires an old password (such as a pattern lock) that you do not remember, the only way out is through Fastboot with full formatting (clean all and lock in the Mi Flash Tool!
π‘
On bootloader devices, logging into Recovery can automatically run TWRP instead of the standard menu. That's fine, but beware: unofficial firmware can take away warranty.
How to avoid turning your phone into a brick
Incorrect actions in Recovery Mode can lead to a complete loss of performance of the device (the so-called βbrickβ). To avoid this, follow the rules:
- π‘οΈ Don't interrupt the reset or firmware process. Even if the screen doesn't change for 5-10 minutes, wait.
- π The battery should be at least 50% charged, and when the charge is low, the phone can turn off at a critical moment.
- π₯ Use only official firmware from Xiaomi (e.g. new.c.mi.com).Castom firmware may contain viruses or incompatible modules.
- π Do not manually delete partitions (e.g. system, boot) unless you know what you are doing, which will make it impossible to download.
If you have a brick, try to restore it through EDL Mode (Emergency Download Mode).
- Turn the phone off the power.
- Close the test points on the motherboard (disassembly required) or use the Deep Flash Cable.
- Connect to your PC and run through the Mi Flash Tool in EDL mode.
Note that EDL requires authorization to Mi Account with developer rights, and without it, the firmware is blocked.