Getting root rights on Xiaomi smartphones gives you access to deep system settings, the ability to remove embedded applications, fine performance optimization and custom firmware installation. However, the process requires care: one error can turn a device into a brick. In this article, we will discuss three key steps β unlocking the bootloader, installing a custom TWRP recavator and Magisk firmware for root rights management β and explain which Xiaomi, Redmi and POCO models support this procedure in 2026.
It is important to understand: Xiaomi officially does not approve of unlocking the bootloader and obtaining root rights, so all actions you perform at your own risk. Once unlocked, the warranty flies from the device, and some functions (for example, Mi Pay or Widevine) L1 viewable HD-Netflix content may stop working, but for enthusiasts and power users, root has the undeniable benefit of removing ads from the Internet. MIUI Up to Google Camera with full functionality.
Before you get started, check if your model is suitable for unlocking. Since 2023, Xiaomi has tightened its policy: some new devices (such as the Xiaomi 14 Pro or Redmi Note 13 Pro+) require waiting up to 168 hours after you have attached your Mi Account before unlocking. Old models like the POCO F3 or Redmi Note 10 Pro unlock faster β in 72 hours.
1.Preparation of the device: what to do before unlocking
Before you start unlocking the bootloader, follow the mandatory preparatory steps, which can lead to locking the device or loss of data.
- π± Back up all data (photos, contacts, messages) via Mi Cloud or locally on your PC. Once unlocked, the device will be reset to factory settings.
- π Charge your smartphone to at least 60%. Interrupting the process due to battery discharge is fraught with "brickingΒ».
- π Link your Mi Account to your device: Go to Settings β Mi Account β Sync and make sure your account is active.
- π οΈ Install drivers for your Xiaomi model on your PC. Download them from the official website or through the Mi Flash Tool.
- π Disable all antiviruses and firewalls on your computer β they can block the Mi Unlock Tool.
Pay special attention to MIUI versions. At the time of writing (2026), only official global or Chinese firmware (stable or development) are suitable for unlocking. Castom firmware or modified versions of MIUI are not supported. You can check the version in Settings β About Phone β MIUI version.
β οΈ Note: If your device was purchased in China and is running on the MIUI China may need to be released before the release ROM. Using Chinese firmware outside China is fraught with problems with Google services and localization.
Also check if your deviceβs bootloader is locked at the hardware level.Some models (e.g. Xiaomi) 12T or Redmi K50i) have anti-Rollback protection, which does not allow you to roll back to the old version of the firmware after the update. XDA Developers or 4PDA for your model.
2 Unlock the bootloader through the Mi Unlock Tool
Unlocking the bootloader is the most important step. Xiaomi requires proof of ownership of the device through the attached Mi Account, and also withstands the mandatory waiting period (from 72 to 168 hours).
- Download Mi Unlock Tool. The official utility can be found at en.miui.com/unlock. Use only the latest version to avoid errors.
If the Mi Unlock Tool is a Cann't unlock error or Current account is different from the account info on the device, check:
- π Does the Mi Account match on the phone and in the utility.
- π Has enough time passed since the binding (sometimes the timer is reset when the update is made) MIUI).
- π± Is the phone connected in Fastboot mode (to do this, turn it off, then press Volume down) + Power before the appearance of the Fastboot logo).
β οΈ Warning: After unlocking the bootloader, the lock screen will display a warning This device is unlocked.This is normal and does not affect the operation of the device, but signals the loss of warranty.
Linked to the Mi Account to the device|Waiting. 72/168 clocked|On. OEM-unlocking USB|Installed drivers on PC|Data backup made.-->
3. Installation of custom TWRP Recovery
After unlocking the bootloader, the next step is to install a custom Recovery (TWRP). It will replace the standard recovery menu and allow you to stitch ZIP-files (e.g. Magisk for root rights: TWRP It is developed by enthusiasts for each model separately, so download the version exactly for your device.
Where to look for TWRP:
- π§ Official website: twrp.me (enter the model in search).
- π₯ Forum XDA Developers: Search for your device theme in the Xiaomi section.
- π¬ Telegram chat and 4PDA: Often publish current builds for new models.
Installation instructions:
- Download the TWRP image in.img format and save it to the folder with ADB/Fastboot on PC.
- Transfer the device to Fastboot mode (turn off, then press Volume down + Power).
- Connect your phone to your PC and open the command line in the folder with ADB.
- Check the connection command: fastboot devices If the device is determined (its serial number appears), continue.
- Please. TWRP Team: Fastboot Flash Recovery twrp-3.7.0_12-1-xiaomi_codename.img (substitute xiaomi_codename For example, you can encode your model with Vili for Xiaomi. 11T Pro).
Some Xiaomi models (like the Redmi Note 11 Pro+ 5G or POCO X4 Pro) have Anti-Rollback protection that blocks installation of older versions of TWRP. Always use the latest build that matches your version of MIUI.
| Model | Codename (codename) | Supported version of TWRP | Notes |
|---|---|---|---|
| Xiaomi 13 Pro | nuwa | 3.7.0_12-1 | MIUI 14.0.4+ required |
| Redmi Note 12 Pro+ | ruby | 3.7.0_12-0 | Not working with MIUI China |
| POCO F5 | marble | 3.6.2_11-0 | Support for A/B divisions |
| Xiaomi Pad 6 | pipi | 3.7.0_12-0 | Only for global firmware |
π‘
If the device loads into a standard recavator after TWRP firmware, repeat the command fastboot boot twrp.img and immediately run Magisk. This will prevent the TWRP from being replaced with stock.
4. Getting root rights through Magisk
Magisk is a universal root rights management tool that does not violate the integrity of the systemless root, which keeps many banking applications and services (such as Google Pay) running. The latest version of Magisk can be downloaded on GitHub.
Step-by-step installation:
- Download Magisk in.zip format (for example, Magisk-v26.4.zip) and save the file to internal memory or SD-map.
Check the root rights.
Magisk Manager
Play Market
If Magisk Manager does not appear in the app menu after the reboot, download it APK From the official repository and install manually. Also check for updates for Magisk modules in the Modules section.
β οΈ Note: Some Xiaomi models (e.g. Redmi) K60 Pro) may lose communication with base stations after installation (no network) in which case try flashing the Disable Force Encryption module or roll back to an older version of Magisk (e.g. 25.2).
What to do if Magisk is not installed?
5. Problems after obtaining root rights and their solutions
Even if you successfully install Magisk, you may encounter problems, and here are the most common ones and how to fix them:
| Problem. | Possible cause | Decision |
|---|---|---|
| The phone does not turn on after the firmware | Incompatible version of TWRP or Magisk | Download to Fastboot and stream the original boot.img through fastboot flash boot.img |
| No net (no catch) SIM-map) | Modem module or conflict with Magisk damaged | Sweep through the Disable Force Encryption module or disable the root for Android System in Magisk |
| Google Pay or Banking Apps Are Not Working | Root rights detection (SafetyNet) | Activate MagiskHide in Magisk Settings and add apps to the Hidden List |
| The device overheats or discharges quickly | Background processes with root rights | Check the active modules in Magisk and disable unnecessary ones. |
If Googleβs services (such as Play Market or YouTube) stopped working after obtaining the root rights, the settings of the Google Services Framework most likely went wrong.
- Delete your Google account in Settings β Accounts.
- Clear the Google Play Services and Google Services Framework application data.
- Restart the device and add the account again.
Important for POCO F4/F5 owners: These models may lose sound in the speakers after Magisk is installed, and the reason for this is a conflict with the ViPER4Android module, the solution is to flash an alternative sound modifier, for example, JamesDSP.
π‘
If the device is unstable after you get root permissions, the first thing you do is turn off all the modules in Magisk and check the system without them, and often the problem is that there's a conflict of modules.
6. How to hide root rights from applications (MagiskHide)
Many apps (banking, security games, Netflix, PokΓ©mon GO) block work on root-right devices. To circumvent this limitation, Magisk has a built-in MagiskHide module (in newer versions it is called Zygisk + DenyList).
How to set up a root rights concealment:
- Open Magisk Manager and go to Settings (βοΈ).
- Enable the options: Zygisk (Beta) Enforce DenyList
- Go back to the main menu and select DenyList (formerly MagiskHide).
- Click Add Apps and mark those for which you need to hide the root (e.g. SberBank Online, Tinkoff, PokΓ©mon GO).
- Reset the device.
To test MagiskHide, use the YASNAC (Yet Another SafetyNet Attestation Checker) app. If the SafetyNet test fails, try:
- π Update Magisk to the latest version.
- π± Install Universal SafetyNet Fix from Magisk repository.
- π§ Disable other modules that may conflict (e.g., Xposed or EdXposed).
On some devices (such as the Xiaomi 12S Ultra), MagiskHide may not work due to hardware integrity checks, in which case the only way out is to temporarily remove the root rights through Magisk Manager (Full Uninstall option), use the desired application, and then flash Magisk again.
7. Alternative ways to obtain root rights without TWRP
If your Xiaomi model does not have a stable version of TWRP (relevant for new devices like Xiaomi 14 or Redmi Note 13 Pro+), you can get root rights by alternative methods:
- π§ Patched firmware boot.img: Download the original boot.img For your firmware (can be extracted from the official ROM Patch it with Magisk Manager (Install option) β Select and Patch a File. Sweat the patch file through fastboot flash boot magisk_patched.img.
Fastboot
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.imgKitsune Mask
Magisk
for new devices:
Some models (like the POCO X5 Pro) require special Magisk forks, such as the Kitsune Mask, which support newer versions of Android 13/14.
The advantage of patched boot.img is that you don't have to install TWRP. But this approach requires care: if you flash the wrong boot.img version, the device won't boot. Always check the file's compatibility with your firmware!
How to remove boot.img from the official firmware?
8.How to remove root rights and return warranty
If you need to return your device to the service center or simply revoke the root rights, follow the following steps to completely remove Magisk and restore the original bootloader:
- Uninstall Magisk via the app: Open Magisk Manager. Select Uninstall β Complete Uninstall. Confirm the action and restart the device.
boot.img
fastboot flash boot boot.img(where boot.img is the original file from stock firmware).
Lock the loader:
fastboot oem lockβ οΈ Warning: This command will completely lock the bootloader and reset to factory settings. Once done, re-unlocking will require a new wait (72β168 hours).
Sweep through the original firmware:
Use the Mi Flash Tool to completely flash your device with the clean all and lock option.
After this, the device will return to the βout of the boxβ state, and the warning This device is unlocked will disappear from the lock screen. However, note: Xiaomi service centers can check the bootloader unlock log, so the warranty may not be fully restored.
If you plan to sell a device, it is also recommended to reset your Mi Account through Settings β Mi Account β Delete your account so that the new owner can link to your device.
π‘
Before locking the bootloader, make sure the device has official firmware installed. Using custom ROMs can lead to a "brick" when trying to block the bootloader.