The Xiaomi smartphoneβs cyclical reboot is one of the most unpleasant malfunctions a user can encounter. The phone turns on, starts to boot, but suddenly restarts after a few seconds or minutes, getting into an endless cycle. The reasons for this behavior can be different, from software failures after an update to hardware problems with memory or battery. The main difficulty is that with traditional recovery methods (for example, reset via Recovery), all user data β photos, contacts, messages β can be irretrievably lost.
In this article, we will discuss ways to restore Xiaomiβs functionality without losing data, including methods for devices with unlocked and locked bootloader, and how to minimize the risks when working with system files. We will pay special attention to models based on MIUI and HyperOS, as the recovery algorithms for them may differ. If your Redmi, POCO or Mi turned into a βbrickβ with permanent rebates, the following instructions will help bring it back to life by saving personal information.
Why Xiaomi is constantly rebooting: the main reasons
Before you start to recover, it's important to understand what triggered the failure, because 80 percent of the time, the software is to blame, but sometimes the hardware is to blame.
- π Failed update MIUI/HyperOS β interrupted firmware or version conflict (e.g. transition from MIUI 14 HyperOS 1.0 cache-free).
- π± Damage to system files β due to viruses, incorrect rooting or deleting critical applications (e.g. com.miui.securitycenter).
- π Battery or power controller malfunction β if the phone reboots when charging is connected or when the charge level is below 20%.
- πΎ Problems with internal memory (eMMC/UF) β memory wear or file system error ext4/f2fs.
- π οΈ Hardware damage β falls, moisture, overheating of the processor (Snapdragon or Mediatek).
If the phone reboots strictly at the same stage (for example, on the MI logo or when download animations appear), this often indicates damage to the /system or /boot partition. If the reboots are chaotic, the problem may be kernel panic or unstable power supply.
After updating|After the fall/hit|When charging is connected|Accidentally, for no reason.|Other-->
Preparing for Recovery: What to Do Before Starting
Before you try to βresuscitateβ your device, follow a few critical steps to avoid total data loss if you fail to recover:
- Check the charge level. If the battery is under 30%, connect the phone to charge for 15-20 minutes. Use the original cable and power supply (for example, Xiaomi 33W for Redmi Note 12).
- Extract. SIM-card and memory card: these can interfere with diagnosis, especially if the problem is related to a conflict of the communication module (modem).
- Prepare your PC. Install the latest version of the Mi Flash Tool (for firmware) and ADB/Fastboot (for debugging). Download the firmware exactly for your model from Xiaomi's official website.
- Check the status. USB-If the cable is not fixed or the phone is not detected by the PC, the problem may be physical damage to the connector.
If you have a backup (e.g., Mi Cloud or Google Account), make sure it is up to date. Otherwise, try to retrieve the data in emergency mode (more on this in the next section).
π‘
If the phone reboots when connecting to a PC, try using it. USB-It's an externally powered hub or some other port on your computer, and sometimes the problem is that you don't have enough power to run it. USB 3.0.
Method 1: Emergency data retrieval (no reset)
If the phone turns on for a while, you can try to copy important files before it reboots again, which would require an ADB debugging bridge and a little bit of luck.
- Connect your phone to your PC via USB.
- Open the command prompt (cmd) and type: Adb devices If the device appears in the list (even for a second), move on to the next step.
- Copy data from internal memory: adb pull /sdcard/ C:\Xiaomi_Backup\ Here. /sdcard/ β the path to user data, and C:\Xiaomi_Backup\ β PC-folder.
If adb devices donβt show the device, try:
- π Reconnect the cable to another USB-port (preferably) USB 2.0).
- π Reset the service ADB: adb kill-server adb start-server
- β‘ Enable Developer Mode (if the phone has ever booted): Go to Settings β The phone. β Version. MIUI and tap 7 times.
What if the ADB canβt see the device?
Method 2: Recovery from Fastboot without data loss
If the phone doesnβt load beyond the logo but responds to a PC connection (defined as a Fastboot), you can try reflashing only damaged partitions.
- π The bootloader (bootloader) is unlocked.
- π You have stock firmware for your model (like fastboot-rom for Redmi Note 11).
- π The phone has no hardware damage.
Step-by-step:
- Unpack the archive with the firmware in a folder (for example, C:\Xiaomi_Flash\).
- Open the command prompt in this folder and type: fastboot devices Make sure the device is defined.
- Fastboot flash boot boot.img fastboot flash system.img fastboot flash vendor vendor.img fastboot flash vendor.img fastboot flash vendor.
- Reboot the phone: fastboot reboot
Important: Don't use fastboot flash all command, it will erase all data! If the phone still restarts after firmware, try flashing dtbo and vbmeta:
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.imgDownload firmware for your model |Install Mi Flash Tool|Unlock bootloader (if not unlocked) |Check charge level (>50%) |Unlock antivirus on PC-->
Method 3: Use of EDL mode (for locked bootloader)
If the bootloader is locked and the phone doesn't load even in the Fastboot, the last chance is Emergency Download Mode (EDL), which allows you to flash the device at a low level, but requires special cable or the ability to solder contacts.
For Xiaomi with Qualcomm processors (e.g., Snapdragon 732G in POCO X3), the following is the procedure:
- Download firmware in.mbn format (for example, for Mi Flash Tool).
- Install the Qualcomm HS-USB QDLoader 9008 driver (can be found on the 4PDA or XDA forums).
- Put the phone in mode. EDL: π For unlocked bootloader: fastboot oem edl. π For locked: close the test points on the board (disassembly required).
Mi Flash Tool
Clean All and Lock
Clean All
β οΈ Attention: Firmware through EDL If you use the wrong firmware version, you can always check the model and region (e.g. Redmi Note 10 Global vs China).
| Xiaomi model | Processor | Supported recovery method | Risk of data loss |
|---|---|---|---|
| Redmi Note 12 Pro+ | Mediatek Dimensity 1080 | Fastboot, SP Flash Tool | Low (with partial firmware) |
| POCO F5 | Snapdragon 7+ Gen 2 | Fastboot, EDL | Medium (EDL requires unlocking) |
| Mi 11 Ultra | Snapdragon 888 | Fastboot, EDL (with the risk of hard-brick) | High (with incorrect firmware) |
| Redmi A2 | Mediatek Helio G36 | SP Flash Tool, Fastboot | Low. |
Method 4: Recovery via TWRP (for rooted devices)
If your Xiaomi has a custom TWRP recavator installed, the chances of recovering without losing data are much higher, a method that is suitable for users who have previously unlocked the bootloader and installed Magisk or other root rights software.
Instructions:
- Load the phone to TWRP (clip Volume++ Power).
- Connect to your PC and copy backup or firmware to your memory card.
- In TWRP, select Mount β System Advanced β File Manager Delete corrupted files (e.g. /system/bin/debuggerd if it causes a reboot).
- Sweep through the corrected boot.img or restore the backup of the system partition.
For diagnosis:
- Try booting up with an external power source (e.g., via USB OTG charging) if the phone is working, it's the battery's fault.
- Check the temperature of the processor in Fastboot: fastboot oem temp Norm: 30-50 Β° C. If above 70 Β° C, you need to replace the thermal paste.
- Connect the phone to UART-console (soldier iron required) to read boot logs. EMMCDL: Timeout points to memory problems.
If you don't have soldering skills, you should go to a service center.
- π Battery replacement: 1,500β3,000 β½.
- πΎ Replacement of memory chips: 5,000β10,000 β½ (model-wise).
- π₯ Replacement of thermopaste/radiator: 1000β2,500 β½.
π‘
If the phone reboots when you connect to a charger, check the cable and the power supply first. In 30% of cases, the problem lies in a faulty USB-type-C connector, not in the battery.