Fastboot mode on Xiaomi Redmi smartphones is a tool for low-level firmware, unlocking the bootloader or restoring the system. However, many users face a situation where the device βhangsβ in this mode after a failed update, resetting or experimenting with custom firmware. Unlike Recovery Mode, where you can still try to reset settings, Fastboot requires more careful action β one wrong move can turn your Redmi into a βbrickβ.
In this article, we will discuss all the working ways to exit Fastboot on Xiaomi Redmi in 2026, including methods for devices with locked and unlocked bootloader. Particular attention will be paid to the models of Redmi Note 12/13, Redmi 10/11 and POCO, as their firmware is often updated, and recovery algorithms are different from older devices. If your smartphone is stuck on the screen with a rabbit in a hat-duckle β do not panic: in 90% of cases, the problem can be solved without contacting the service center.
Why Redmi only downloads in Fastboot: the main reasons
Before you try to get out of mode, it's important to understand what caused the failure.
- π Interrupted update MIUI β if the firmware has downloaded, but the installation was interrupted (the battery has discharged, turned off) USB, press backΒ»).
- π Unsuccessful unlocking of the bootloader via Mi Unlock Tool β especially relevant for new models with a link to the Mi Account.
- π οΈ Installation of custom Recovery (TWRP) or firmware without checking compatibility with the anti-rollback version.
- β‘ Critical battery discharge while working with system files (less than a few) 30% charge blocks entry into the section /system).
- π€ Failure after reset to factory settings via Settings β Factory Reset if the system partitions have been modified before.
On Redmi models with Qualcomm processors (e.g. Redmi Note 11 Pro+), Fastboot can start due to damage to the boot or dtbo partition. Devices on MediaTek (e.g. Redmi 10A) are more likely to βhangβ due to problems with the preloader β in this case, standard exit methods may not work.
β οΈ Note: If before getting into Fastboot you tried to flash the device through SP Flash Tool (for MediaTek) or EDL Mode, don't try to get out in the standard way. It could lead to total loss. IMEI In such cases, specialized equipment (for example, UFi Box) is required).
Method 1: Simple restart (for accidental hitting the Fastboot)
If you find yourself in Fastboot mode after clicking a button combination (for example, you tried to log in to Recovery but missed), try the standard exit method:
- Hold the power button for 10-15 seconds until the screen goes out.
- Wait 30 seconds β the device should automatically boot into Android.
- If the screen lights up again with the Fastboot logo, repeat step 1, but hold the button for up to 20 seconds.
On some models (for example, Redmi Note 9 Pro) helps the combination:
Hold the power button + increase the volume 10-12 secondsAfter vibration release the buttons β the device should restart in normal mode.
π‘
If after the reboot there is a βNo commandβ error or an Android robot with a red exclamation point, then the Recovery partition is damaged. In this case, you will need to flash through Fastboot (see Method 4).
Method 2: Exit via Mi Flash Tool (for locked bootloader)
If a simple restart doesnβt work and the bootloader on your Redmi is locked (which is typical for new devices), youβll need an official tool from Xiaomi β the Mi Flash Tool. This method is suitable for devices that have not previously been unlocked or flashed by custom firmware.
You'll need:
- π» Windows computer 10/11 (on macOS/Linux Mi Flash Tool is not working).
- π Original. USB-cable (preferably from the set).
- π± Fastboot firmware ROM For your model (download only from the official Xiaomi website).
- π Mi Account linked to your device (if Find My Device protection is enabled).
Step-by-step:
- Install the Mi Flash Tool and Qualcomm drivers (if you have Snapdragon) or MediaTek (for Helio/Dimensity chips).
- Unpack the downloaded Fastboot firmware ROM in a folder without Cyrillic characters (for example, C:\ROM\redmi_note12).
- Connect the Redmi off to the PC, then press Volume Down + Power to log back into Fastboot.
- In Mi Flash Tool, click Select, specify the path to the firmware folder, then click Refresh β the device must be determined as COM-port.
- Select Clean all mode (saves data) or Clean all and lock (full reset + lock bootloader) and press Flash.
Install the latest Mi Flash Tool version|Download Fastboot firmware ROM forecast|Disable the antivirus (it can block drivers)|Charge your phone to at least 50%|Connect the original USB-cable
-->
It takes 5-10 minutes. Once it's done, it automatically reboots to Android. If you get an "Anti-rollback check error," you're trying to flash an older version of MIUI than you're currently running, in which case, download a newer firmware.
β οΈ Note: On Redmi models with MediaTek chip (e.g. Redmi) 10C) Mi Flash Tool may not work. Use this tool SP Flash Tool with scatter.txt file from firmware, but be careful β wrong actions will lead to loss of the file. IMEI.
Method 3: Fastboot commands (for unlocked bootloader)
If the bootloader on your Redmi is unlocked (checked by the fastboot oem device-info command - look for the Device unlocked: true string), you can exit mode using ADB/Fastboot commands. This method is suitable for power users, since it requires work with the console.
Tools required:
- π₯οΈ Platform Tools (adb and fastboot package from Google).
- π USB-cable with data transmission support (charging cables will not work!).
- π Know your device model (you can find out by sticker under the battery or through the command fastboot getvar product).
Instructions:
- Connect Redmi in Fastboot mode to your PC.
- Open the command line (Win + R β enter cmd) and go to the folder with the platform-tools:
cd C:\platform-tools- Check the connection of the device:
fastboot devicesIf the device is determined (its serial number will appear), execute commands in order:
fastboot reboot recovery #try to download Recovery
fastboot continue # Continue downloading Android (if Recovery is not available)
fastboot reboot bootloader #boot bootloader reboot (sometimes helps)
fastboot reboot # standard rebootIf the device returns to Fastboot after fastboot continue, the boot partition is damaged.
fastboot flash boot boot.img
fastboot rebootThe boot.img file can be extracted from the official Fastboot ROM firmware (it is in the image folder).
What to do if the fastboot team is not working?
Method 4: Recovery through EDL Mode (for bricks)
If none of the previous methods worked, and the device does not respond to commands or constantly returns to the Fastboot, the last option is Emergency Download Mode (EDL), which requires special hardware or knowledge of auth keys for your model, but it is the only one who can bring to life a fully βbrickedβ Redmi.
When you need an EDL:
- π¨ The device does not even turn on in Fastboot (black screen, no reaction to buttons).
- π§ Critical partitions (modem, abl, xbl) are damaged).
- π The bootloader is locked and the Mi Flash Tool gives an error "flash not allowed".
How to log into EDL:
- Turn off the device (if it is in Fastboot, hold the power button for 20+ seconds).
- Click the combination: For Qualcomm: Volume up + Volume down + Power (hold 10-15 seconds). For MediaTek: plug the phone off to a PC with the Volume up button pressed.
Qualcomm HS-USB QDLoader 9008
Snapdragon
MediaTek Preloader
For firmware in EDL, use:
- π₯οΈ Mi Flash Tool (Qualcomm only, requires an authorized account).
- π₯οΈ SP Flash Tool (for MediaTek, you need authentication file for new protection Xiaomi).
- π₯οΈ UFED/Chimera Tool (payment solutions for service centers).
β οΈ Attention: Firmware through EDL Without official permission from Xiaomi (for example, through unlicensed versions of Mi Flash) it can result in a lockdown. IMEI on the Redmi Note models 11/12/13 If you're not sure what you're doing, you can contact the service center.
Table: Compatibility of exit methods with Redmi models
| Xiaomi Redmi Model | Simple restart. | Mi Flash Tool | Fastboot teams | EDL Mode | Notes |
|---|---|---|---|---|---|
| Redmi Note 12 Pro+ | β | β (requires unlocking) | β | β (I need an auth file) | Snapdragon 7 Gen 1. When running through EDL, check the anti-rollback version. |
| Redmi 10A / 10C | β | β (only SP Flash Tool) | β (loader blocked) | β | MediaTek Helio G25/G35 chip. EDL requires authentication file. |
| Redmi Note 11 Pro 5G | β | β | β | β | Snapdragon 695 chip supports unlocking the bootloader via Mi Unlock. |
| POCO X5 Pro | β | β | β | β (You need a developer account) | Snapdragon 778G chip: Possible problems with anti-rollback in downgrade. |
| Redmi 9A / 9C | β | β | β | β | MediaTek Helio G25 Fastboot commands are not supported. |
Simple restart |Mi Flash Tool|Fastboot|EDL Mode |Teams didn't help, contacted the service |Another way
-->
What do you do if nothing helps?
If you've tried all the methods, but Redmi still only loads into Fastboot, maybe the problem is deeper than it seems.
- π§ Check hardware malfunctions: Connect a known working battery (a discharged or bloated battery can block boot). Check the contacts of the display plume (if the screen does not turn on, but the PC determines the device in the Fastboot). Test another USB-port and cable (power problems can interrupt firmware).
- π‘ Contact the service center: Xiaomi official services can restore a device even with a damaged eMMC (replacement of a memory chip).The cost of repairing a brick in 2026: from 1,500 β½ (software recovery up to 5,000 β½ (memory-replacement).
- π Consider buying a new device if: Smartphone is older 3β4 years (e.g. Redmi Note) 7/8). Repairs are more expensive 50% The problem is the hardware (for example, a burnt processor).
Before visiting the service, do the following:
- Take a picture of the Fastboot screen (if there are errors, such as "Invalid partition").
- Write down the serial number of the device (under the battery or in the box).
- Check with Xiaomi support if the warranty is valid (even if it is over, sometimes they make a discount for repairs).
π‘
If your Redmi doesnβt respond to any commands and isnβt detected by a PC, itβs likely that the first-level bootloader (PBL) is damaged. In this case, self-recovery is almost impossible β a programmer and soldering station experience are required.