TWRP (Team Win Recovery Project) is a powerful tool for Xiaomi smartphone owners to install unofficial firmware, backup systems and recover data even when critical failures. However, logging into TWRP Recovery on Redmi, POCO or Mi devices often raises questions: some users experience a βhangβ on the logo, others with automatic reboot to the standard Mi Recovery reclaims. In this article, we will discuss all the current ways to log into TWRP in 2026, including bypassing typical Xiaomi errors and solving locks.
Itβs important to understand that the process differs depending on the bootloader status (unlocked/locked), the MIUI version and the device model. For example, new HyperOS smartphones may require additional steps, while older Redmi Note 4/5s may require very different commands. Weβll look at the universal methods that work on most devices, from POCO F5 to Xiaomi 13 Ultra, and also look at why sometimes TWRP doesnβt start and how to fix it.
1. Preparation of the smartphone before entering the TWRP
Before trying to log into TWRP Recovery, there are several critical steps to take, and skipping at least one of them can lead to a device blink or a booting impossibility.
First, check the status of the bootloader.
- Turn off your smartphone.
- Press Volume Down + Power before the Fastboot logo appears.
- Connect the device to the PC and type the command: fastboot oem device-info
- If the answer is Device unlocked: true, the bootloader is unlocked. If false is locked.
Second, make sure that the smartphone has the TWRP recovery installed. Many users mistakenly think that it is enough to download a.img file, but it needs to be flashed through fastboot or special utilities like OrangeFox. Without this, you can not log into TWRP.
Battery charge > 50%|The bootloader is unlocked|TWRP Imprinted in the Recovery section|Mi Account disabled (if required)|USB-debugging is on-->
Third, disable Mi Account protection (if activated). On some models (Redmi Note 10 Pro, POCO X3 NFC), a Xiaomi account with a link can block access to the Recovery.
- πΉ Go to Settings. β Xiaomi account β Security.
- πΉ Turn off the option Find the device.
- πΉ Delete your account (if you plan to reset completely).
Method 1: Enter through hardware buttons (for unlocked bootloader)
The easiest method is to use a combination of physical buttons, which works on 90% of Xiaomi devices with an unlocked bootloader and TWRP installed.
Instructions:
- Turn off your smartphone (hold power until vibration).
- Press the Volume up + Nutrition at the same time.
- Hold the buttons for 10-15 seconds until the TWRP logo appears (usually a blue or orange screen labeled TeamWin).
If instead of TWRP, you download the standard Mi Recovery (yellow screen with an android robot), this means that:
- πΈ The stainless stain is not in the right place).
- πΈ bootloader is locked (even if previously unlocked, Xiaomi can automatically block it after the update).
- πΈ Incompatible version is installed TWRP (For example, for Redmi Note 9 Pro downloaded firmware from Redmi Note 9S).
π‘
If the smartphone is vibrating but the screen is not turning on, try clamping Volume Up + Volume Down + Power. On some models (POCO F3, Xiaomi 11T) this is an alternative combination for entering the Recovery.
Method 2: ADB commands to log into TWRP (if the buttons don't work)
If the hardware buttons do not respond or the smartphone is βstuckβ on the screensaver, you can enter the TWRP through ADB (Android Debug Bridge. This method requires you to turn on USB-Debugging and working connection to the PC.
Step-by-step:
- Connect your smartphone to your computer through USB-cable (preferably original).
- Open the command prompt (cmd) in the folder with ADB.
- Enter the command to check the connection: adb devices If the device is displayed, go further. If not, install the Xiaomi USB Drivers drivers.
- Run the command to reboot in RecavΓ©rie: adb reboot recovery
If after this command the smartphone is rebooted to the standard Mi Recovery recovery, it means:
β οΈ Note: On new devices (Xiaomi) 13/14, Redmi Note 12) Xiaomi blocks transition to custom Recovery through ADB. In this case, only manual stitching will help. TWRP via fastboot (see Method) 4).
Alternative command to bypass the lock (does not work on all models):
adb shell su -c "echo 1 > /sys/class/android_usb/android0/enable"Method 3: Sign in via Fastboot (if TWRP is not installed)
If TWRP Recovery is not hardwired into the recovery section, but you have a twrp.img file, you can temporarily download it via fastboot. This method does not replace the standard recovery, but allows you to log in once to TWRP for firmware or backup.
Instructions:
- Turn off your smartphone and press Volume Down + Power to log into Fastboot.
- Connect the device to your PC and check the connection: fastboot devices
- Enter a command for temporary loading TWRP: fastboot boot twrp-3.7.0_12-0-joyeuse.img (Replace the file name with yours).
After completing the command, the smartphone should boot into TWRP. Note: this method does not flash the recaveri constantly - after the reboot it will disappear, and you will need to use the fastboot boot again to re-enter.
What if the fastboot canβt see the device?
5. Method 4: Firmware TWRP via Fastboot (permanent installation)
If you want TWRP Recovery to stay on your device after the reboot, you need to flash it into the recovery section.This method requires an unlocked bootloader and a compatible twrp.img file.
Step-by-step:
- Download the correct version of TWRP for your model from the official twrp.me website or trusted sources (e.g. XDA Developers).
- Rename the file to twrp.img and place it in the folder with fastboot.
- Download your smartphone to Fastboot (Loudness Down + Power).
- Run commands in order: fastboot flash recovery twrp.img fastboot boot twrp.img
After firmware, the smartphone will automatically boot into TWRP. To fix the changes and avoid overwriting with standard recaps, immediately after entering TWRP:
- πΉ Go to Advanced. β Flash Current TWRP (if the option is available).
- πΉ Or run the file. disable_forceencrypt.zip (encryption-based FBE).
Redmi Note 10/11/12|POCO F3/F4/F5|Xiaomi 11/12/13|Redmi 9/10/11|Another model-->
Method 5: Bypassing TWRP locking on new devices (HyperOS, MIUI 14+)
On smartphones with HyperOS or MIUI 14/15, Xiaomi has tightened protection against custom recaps. Now, even after TWRP firmware, the device can:
- πΈ Automatically reboot in Mi Recovery.
- πΈ Block access to data and system sections.
- πΈ Require the entry of a password even in TWRP (because FBE-encryption).
Solutions for new devices:
- Turn off automatic reboot: B TWRP Go to Mount. β Disable DM-Verity and file file dm-verity_forceencrypt_disabler.zip.
- Circumvention FBE-encryption: Download FBE_Patcher s XDA and run the patch through TWRP.
- Use alternative recavers: For some models (Xiaomi 13, POCO F5), OrangeFox Recovery is better suited than TWRP.
For example, for Redmi Note 12 Pro+ with HyperOS, the operating sequence:
fastboot flash recovery orangefox.img
fastboot reboot recovery7.Typical errors and their solutions
Even if you follow instructions correctly, users often face problems.
| Mistake. | Reason. | Decision |
|---|---|---|
| The screen goes out after the TWRP logo | Incompatible version of the recovery or blocked loader | Sweat the correct version of TWRP or unlock the bootloader |
| Requires a password in TWRP | Encryption FBE (File-Based Encryption) | Please. disable_forceencrypt.zip Or enter the old one. PIN-code |
| fastboot does not see the device | Lack of drivers or faulty cable | Install the Mi Flash Tool and try another one. USB-port |
| After the reboot, TWRP disappears. | MIUI Rewrites Recovery Section | Please. twrp.img slot-in (recovery_a and recovery_b) |
| Invalid zip file format error | A damaged firmware file or incorrect signature | Download the file again and check the MD5 checksum |
If none of the methods worked, check:
- πΉ Version compatibility TWRP with your model (for example, for POCO X3 Pro needs a special build with support for Dynamic Partitions).
- πΉ Antirollback (on some devices, Xiaomi blocks downgrade firmware).
- πΉ Status OEM Unlock in the Developer Settings (must be enabled).
π‘
On HyperOS devices, standard TWRP login methods may not work. Use alternative recaps (OrangeFox, PitchBlack) or patches to bypass AVB 2.0.