Getting root rights on Xiaomi smartphones opens up access to hidden Android features, but requires care. Without proper preparation, the device can turn into a βbrickβ β an inoperable device that does not turn on even in Fastboot mode. In 2026, the process became more complicated: the company tightened its policy of unlocking the bootloader, and some models (for example, Xiaomi 13 Ultra or Redmi Note 12 Pro+) require additional steps to bypass the protection of the Mi Anti-Rollback.
This article will be suitable for owners of devices based on MIUI (including POCO And Black Shark, released after 2018, will be divided into two main methods: official (through unlocking the bootloader and Magisk) and alternative (for devices with locked bootloader). The procedure voids the warranty and may result in data loss on the internal drive β be sure to back up via Mi PC Suite or adb backup.
What is the root of Xiaomi and what are the risks?
Root rights allow:
- π§ Remove built-in apps like Mi Browser, Mi Music or GetApps.
- β‘ Increase productivity through nuclear tweaks (e.g., scheduler change) CPU performance).
- π± Install custom firmware (LineageOS, Pixel Experience) or modified cores.
- π Block ads at the system level through AdAway or Blokada.
But there is a downside:
- π¨ Loss of warranty β Xiaomi service centers refuse repairs when unlocked bootloader is detected.
- π‘οΈ Malware vulnerability β some banking applications (such as SberBank Online or Tinkoff) stop working due to SafetyNet trigger.
- π Risk of βbrickβ in case of firmware error β especially on models with A/B-sections (Xiaomi) 12T, Redmi K50).
β οΈ Attention: On devices with MIUI 14+ and Snapdragon processors 8 Gen 2/3 (for example, Xiaomi 14) Unlocking the bootloader can lead to hardware locking of the module 5G or NFC. Before you start, check the compatibility of your model in the forum. XDA Developers.
Preparation of the device: unlocking the loader
The first step is to unlock the bootloader. Xiaomi requires confirmation of the Mi Account account and waiting 7-15 days (up to 30 days on new models).
- Tie it up. SIM-Card to Mi Account (required!).
- Activate debugging by USB in Settings β About Phone β MIUI version (click 7 times).
- Enable OEM Unlock in Settings β Additional β For developers.
- Connect your phone to your PC, install Mi Flash Tool drivers, and run Mi Unlock.
If the utility gives you a "Couldn't unlock" error, check:
- π Cable - Use the original cable USB Type-C (cheap cables may not transmit data).
- π₯οΈ The Mi Unlock version - for MIUI 14 You need version 6.5.224.24 or later.
- π± Account Region β If the device is purchased in China, link it to your global account.
β οΈ Note: On the Redmi Note 11 Pro+ 5G and POCO F4 GT After unlocking the loader, the settings are automatically reset. IMEI. Save them in advance through the app MTK Engineering Mode (for MediaTek) or QCN Rebuilder (for Snapdragon).
Create a backup in Mi Cloud|Tie it down. SIM-card|Install drivers ADB/Fastboot|Download Mi Unlock latest version|Disable antivirus on PC-->
The choice of root method: Magisk vs. SuperSU
In 2026, Magisk (the author of topjohnwu) remains the only reliable solution for getting root on Xiaomi. The alternative - SuperSU - is outdated and does not support Android 13/14.
- π SafetyNet support (you can hide root from banking applications).
- π¦ Modular system (e.g. MagiskHide Props Config for changing device fingerprint).
- π οΈ Regular updates (current version at the time of writing β 26.4).
The installation will require:
- Castomic recovery (TWRP or OrangeFox)
- Magisk-v26.4.zip file (download only from official GitHub)
- Patch boot.img (if you install without TWRP).
| Method of installation | Pluses | Cons | Suitable for |
|---|---|---|---|
| Through TWRP | Simplicity, support for A/B-partitions | Risk of data corruption | Xiaomi 11T, Redmi K40, POCO X3 Pro |
| Patch boot.img | Safety, no need for custom recovery | Harder for beginners. | Xiaomi 12, 13 Lite, Redmi Note 10 Pro |
| Fastboot (for A/B) | It works on new devices. | Requires an unlocked bootloader | Xiaomi 13 Ultra, Redmi K60 Pro |
What is it? A/B-section?
Step-by-step: Install Magisk via TWRP
This method is suitable for most Xiaomi devices on Android 11-14. Before you start, make sure that:
- π Battery charge > 60%.
- π₯ Downloaded. TWRP for your model (for example, twrp-3.7.0_12-0-lmi.img for POCO F2 Pro).
- π File. Magisk-v26.4.zip lies in the inner memory.
Instructions:
- Turn your phone into Fastboot (Off β Power + Volβ).
- Connect to your PC and execute the command: fastboot flash recovery twrp.img fastboot reboot recovery
- In TWRP, select Install β Magisk-v26.4.zip and swipe for installation.
- Reboot to the system. If it hangs on the logo, repeat the steps by formatting Data in TWRP.
β οΈ Note: On devices with Dynamic Partition (Xiaomi) 12/13 standard series TWRP Use modified versions of the type TWRP A13 Or the fastboot utility enhances from XDA.
π‘
If after installing Magisk phone does not boot, try it in the TWRP execute the fastboot command --disable-verity --disable-verification flash vbmeta vbmeta.img. This will disable the integrity check.
Alternative method: boot.img patch without TWRP
If your model does not have a stable TWRP (such as Xiaomi Civi 3 or Redmi Note 12 Discovery), use boot.img patch:
- Download the stock firmware for your model from the Xiaomi Firmware Updater website.
- Remove boot.img from the archive (use 7-Zip or Payload Dumper).
- Move boot.img to your phone and in Magisk, select Install β Select and Patch a File.
- Copy the patch file (magisk_patched.img) On PC and run through Fastboot: fastboot flash boot magisk_patched.img fastboot reboot
For devices with A/B-partitions (e.g. Xiaomi) 13 Pro) both files must be patched β boot.img and init_boot.img, And then stitch them up:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot flash init_boot_a magisk_patched_init.img
fastboot flash init_boot_b magisk_patched_init.imgπ‘
On Android devices 13+ be sure to patch init_boot β Without it, Magisk will not work, even if it is not boot.img stitched.
Root check and SafetyNet bypass
After the reboot, install the Magisk App (download the APK from GitHub) and check the status:
- Open the app and make sure the top reads "Installed: 26.4."
- Click Check SafetyNet β If you are βFAILβ activate MagiskHide and restart.
- For banking applications, install Universal SafetyNet Fix via Magisk β Modules.
If Google Pay or Sberbank does not work:
- Turn on MagiskHide in the settings.
- Add the app to the hidden list (MagiskHide β select the app).
- Install the Props Config module and change the deviceβs print to a certified one (e.g. Pixel 6).
β οΈ Attention: MIUI 14 Android 13 MagiskHide may not work due to integrated MiuiOptimization protection. ADB: adb shell settings put global miui_optimization_disabled 1
Frequent mistakes and their solutions
Even with the exact following of the instructions, there can be problems.
| Mistake. | Reason. | Decision |
|---|---|---|
| "This package is for... but your device is..." | Mismatch of MIUI version | Download the firmware for your regional version (Global/China/EEA) |
| Hanging on the MI logo | Damaged by vbmeta or dm-verity | Switch stock vbmeta.img with the check turned off |
| "Invalid IMEI" after unlocking | Resetting NV-data on MediaTek | Restore your IMEI with Maui META or SN Writer |
| Magisk is not installed on Android 14 | Lack of support init_boot | Use Magisk Delta (fork with support for new devices) |
After installing root, the phone stopped seeing SIM-maps, check the cards:
- πΆ Correctness IMEI in *#06#.
- π‘ Network settings in Settings β SIM-maps and mobile networks.
- π§ File integrity modemst1 and modemst2 section /vendor.
1. Download QCN Rebuilder and stock firmware for your model.
2. Remove the nvdata.bin file from the firmware.
3.In QCN Rebuilder, specify your IMEI (printed on the box or under the battery).
4.Sweep the resulting nvdata.qcn via QPST or Maui META (for MediaTek).
β οΈ Wrong. IMEI This can lead to a network blocking!