Getting superuser rights (root rights) on Xiaomi smartphones gives access to hidden Android features, allows you to remove system applications, optimize performance and install modified firmware. However, the process has become much more complicated after the tightening of the MIUI security policy in 2022-2026.
In this guide, we will discuss the current ways to obtain root rights to Xiaomi, Redmi and POCO, taking into account the latest updates MIUI 14/15 and Android 13/14. Particular attention will be paid to security: improper actions can lead to a βbrickβ (complete inoperability) of a device or loss of warranty. If you are a beginner, carefully study all warnings and prepare backups of data.
1.Preparation of the device: what to do before unlocking
Before you start unlocking the bootloader and obtaining root rights, you need to follow several critical steps, and skipping any of them can lead to failures or inability to complete the process.
First, check your device model and MIUI version. Some models (such as the Xiaomi 12T or Redmi Note 11 Pro+ 5G) have unique limitations. You can find out the exact model from the Settings menu β About Phone β Model. Also write down the firmware version (MIUI build number) - it will be necessary to select the correct unlock file.
- π± Backup all data (photos, contacts, messages) through Settings β Additionally. β Backup or using Google Account.Root can erase user data!
- π Charge the battery to at least 60%. Interrupting the process due to battery discharge often leads to a software blink.
- π Prepare the cable. USB (preferably original) and PC with drivers installed ADB/Fastboot. Windows will require Android SDK Platform-Tools.
- π Turn off all screen locks (PIN, pattern lock, print. Some versions MIUI This is required to unlock the loader.
Pay special attention to checking the status of the bootloader. On new Xiaomi devices, it is locked by default. You can find out the status by rebooting the phone in Fastboot mode (press Power + Volume Down) and checking the Device State bar. If it says locked, unlock is mandatory.
π‘
If your device is purchased in China (CN version), you may need a Chinese Mi Account with the +86 attached to unlock the bootloader, making it easier to use global firmware via MIUI ROM Flasher.
2. Unlock the bootloader on Xiaomi: the official way
Since 2021, Xiaomi has tightened the process of unlocking the bootloader, adding a mandatory binding to the Mi Account and a waiting period of 168 hours (7 days), which is done to combat device theft and unauthorized access.
Official unblocking instructions:
- Link your device to your Mi Account: Go to Settings β Xiaomi Account. Sign in or create a new account. Enable data sync and confirm email/phone.
- Activate debugging on USB and OEM-Unlock: Enable Developer Mode: Go to Settings β About the phone and 7 times click on the version MIUI. Back to Settings β Additionally. β For developers and include: Debugging by USB Unlocking OEM (It may be called a factory unlock)
- Download the Mi Unlock Tool (the official tool from Xiaomi).
- Launch the utility, log in under the same Mi Account as on your phone.
- Connect your phone in Fastboot mode and follow the program instructions.
Once the Mi Unlock Tool is successfully connected, it will show a countdown timer (168 hours) and then you can unlock the bootloader. It's important that you don't reset the device or log out during this period, otherwise the timer will be reset!
3. Alternative Unlocking Methods (without waiting 7 days)
The official wait-and-see approach is not for everyone, especially if the device needs to be flashed or repaired urgently, and there are informal methods of bypassing the 168-hour timer, but they come with risks:
- π¨ Using modified versions of the Mi Unlock Tool β some enthusiasts create patched versions of the utility that reset the timer.
The most reliable alternative is to buy an authorized EDL account (about $5-10 on specialized forums), but this violates Xiaomiβs user agreement and can lead to IMEI blocking.
What is it? EDL-The regime and why it is dangerous?
4.Installation of custom recavery (TWRP) after unlocking
After unlocking the bootloader, the next step is to install a custom Recovery, such as TWRP (TeamWin Recovery Project, which will replace the standard recovery MIUI and allow for the stitching of modified ZIP-files (e.g. Magisk for root rights).
Instructions for installing TWRP:
- Download the correct version of TWRP for your model: Official builds: twrp.me. Unofficial (for new devices): search the XDA Developers or 4PDA forums.
The file must have an.img extension (e.g., a file file file, twrp-3.7.0_12-vayu.img for POCO X3 Pro).
Fastboot
adb reboot bootloaderOr manually: Press Power + Volume down on the phone turned off.
fastboot
Fastboot flash recovery twrp version.img
fastboot boot twrp version.imgAfter the second command, the phone will automatically reboot to TWRP.
Important: On some devices (e.g. Xiaomi 11T or Redmi K50), standard MIUI firmware can overwrite TWRP on the first boot, to avoid this, immediately after installing the Recovery:
- π§ Go to Mount. β System and unmount the partition.
- π Delete the file. /system/recovery-from-boot.p (if there is).
- π Reboot back to the TWRP (off-the-shelf!).
βοΈ Preparation for Magisk firmware through TWRP
5. Getting root rights with Magisk
Magisk is the most popular root-rights tool on modern Android devices. Unlike the old SuperSU method, Magisk allows you to hide root from applications (such as banking or games) and updates through modules.
Step-by-step instructions for installing Magisk:
- Download the latest version of Magisk: Official repository: GitHub Magisk. Select the file Magisk-v26.4.zip (version may vary).
- Sweat ZIP via TWRP: Copy Magisk-v26.4.zip to your phone or flash drive. In TWRP, select Install β Select file β Swipe to Confirm Flash.
Check the root rights.
- Install the Root Checker app from Play Market.
- Run it and press Verify Root.
π‘
On Android 12+ and MIUI 13+ devices, Magisk may not work due to the new AVB 2.0 signature verification system, requiring manual patching of boot.img via PC.
6. bypassing the anti-rollback and other difficulties
One of the main problems with getting root rights to Xiaomi is the Anti-Rollback (ARB) mechanism, which is a protection that blocks rollbacks to older versions of the firmware. If you flash a device with a downgrade version of MIUI, it can turn into a brick.
How to check and bypass Anti-Rollback:
| Action. | Description | Risks. |
|---|---|---|
| Checking the current ARB | In Fastboot, type:fastboot getvar anti Shows the current level (e.g., anti: 4). | No. |
| Search for compatible firmware | Only download firmware with an ARB equal to or higher than the current one. For example, if you have anti:3, the firmware should be anti:3+. | Firmware with less ARB = Brik |
| Bypassing through EDL | Some service firmware (.mbn) ignore ARB but require an authorized account. | IMEI block, loss of warranty |
| Use of patches | On the forums, they post modified boot.img with ARB bypass for specific models. | System instability |
Another common problem is the encrypted /data partition. Android 10+ has encryption enabled by default, which prevents TWRP from accessing user data.
- π Disable encryption via Fastboot: fastboot format:ext4 userdata fastboot format:ext4 Cache Attention: This will erase all data on the device!
- π± Use OrangeFox Recovery β an alternative recovery with decryption support.
π‘
If banking applications (such as SberBank or Tinkoff) have stopped working after Magisk firmware, install the MagiskHide Props Config module and activate root hide mode. In the module settings, select Fingerprint devices without root (such as the Pixel 5).
7. Frequent errors and their solutions
Even if you follow the instructions accurately, you can get errors, and let's look at the most common ones and how to fix them.
β οΈ Note: If after Magisk firmware the device boots to bootloop (infinite reboot), do not try to reset the settings through the MIUI Recovery -- that's going to remove Magisk, but it's not going to restore the system:
- π Reboot to TWRP (clamp down on power. + Volume up when switched on).
- π Please. Magisk-uninstaller.zip (Download GitHub Magisk).
- π§ Install Disabler ZIP (unless you've done it before).
- π Re-flash the Magisk.
Other common mistakes:
| Mistake. | Reason. | Decision |
|---|---|---|
| Fastboot: FAILED (remote: 'Flashing is not allowed in Lock State') | The bootloader is not unlocked | Repeat the unlocking procedure with the Mi Unlock Tool |
| E: Footer is wrong in TWRP | Damaged. ZIP-file or incompatible version TWRP | Download the file again, check the checksum (MD5) |
| The device is not defined in fastboot | Lack of drivers or faulty cable | Install the Mi Flash Tool or ADB drivers manually |
| After root, mobile data stopped working | Damaged. modemst1 or modemst2 | Restore the modem partition backup via TWRP |
β οΈ Note: On devices with a Mediatek chipset (e.g., Redmi) 9A or POCO M3) slip-stick boot.img This can cause hard brick damage. Always check the compatibility of files with your model in the forums. XDA or 4PDA.
8 What to do after obtaining root rights
Now that you have root rights, you can optimize your device, but it's important to do it carefully.Uncontrolled changes to system files can lead to unstable operation or loss of functionality.
Useful actions after rooting:
- π§Ή Remove System Applications: Use Titanium Backup or System App Remover to remove Blaatware (e.g. Mi Browser, Mi Music, Mi Video).Do not delete applications with the names com.android. or com.xiaomi. - this can break the system.
- β‘ Performance Optimization: Install Kernel Adiutor to fine-tune the kernel (frequency) CPU/GPU, Task planners. Activate Force. GPU Rendering in the developer settings to speed up animation.
- π‘οΈ Security Enhancement: Install AFWall+ Use MagiskHide to hide root from banking applications.
- π System Update: Do not update after rooting OTA β This will remove Magisk and may lead to bootloop. Download full firmware (.tgz) with Xiaomi Firmware Updater and stitch them through TWRP.
On devices with MIUI 14+ and Android 13+, some Magisk modules (such as ViPER4Android or EdXposed) may not work due to the new SELinux security system in Enforcing mode. To fix this, install the Magisk SELinux Switcher module and switch to Permissive mode.