Getting root rights on Xiaomi devices opens up endless possibilities for customization of the system. It is not just a way to remove preinstalled software, but also the key to deep customization of MIUI or HyperOS. Many enthusiasts are looking for ways to circumvent the limitations imposed by the manufacturer to unlock the full potential of their gadget.
However, the process requires careful follow-up and careful follow-up, and a mistake at any stage can lead to a loss of warranty or turn the phone into a brick.Modern versions of Xiaomi firmware are equipped with powerful security mechanisms, such as Verified Boot, which block unauthorized changes to the system partition.
In this article, we will discuss current methods of obtaining superuser rights in 2026. We will look at the tools necessary to unlock the bootloader and how to install rights managers. Unlocking the bootloader on new Xiaomi models requires binding your Mi Account account at least 7 days before the procedure.
Preparation of the device and necessary tools
Before you start modifying the system, you need to make sure you have everything you need. Unlocking the bootloader is the first and mandatory step. Without the bootloader unlocked, none of the instructions below will work. This is the foundation on which all the work on superuser rights is built.
You will need quality. USB-cable, preferably original or certified MFi, and Windows computer. ADB Also make sure that the battery of the smartphone is at least 60% so that the device does not turn off at a critical moment.
Make a full backup. The process of unlocking the bootloader completely erases all data from the phone's internal memory. Photos, contacts, and apps will be deleted, so transfer important information to the cloud or to your computer in advance.
☑️ Preparation for obtaining Root
Check the MIUI and Android version on your device. Some versions of HyperOS may require specific versions of unlock tools. Download the official Mi Unlock Tool from the developer's website. Using third-party versions can lead to authorization errors.
Unlocking the bootloader (Bootloader Unlock)
The bootloader unlocking procedure is the gateway to getting root rights. In your smartphone settings, go to About Phone and press seven times the build number to activate Developer Mode. Then, in the Advanced Settings menu, find the Developer For option and turn on the option. OEM-unlocking and debugging USB.
You need to link your account. In the same developer menu, select Mi Unlock Status, log in to your Mi Account and click Add Account and Device. The system will alert you to the risks — confirm the action. After that, you will have to wait 7 to 168 hours (depending on region and account status) before the server allows you to unlock.
⚠️ Note: Once the bootloader is unlocked, Xiaomi’s security system marks the device as modified.Some banking apps and Google Pay (Wallet) may stop working normally, requiring additional manipulation to conceal rights.
When the waiting time expires, turn off the phone and press the Volume Down + Power buttons to enter Fastboot mode. Connect the device to your PC, launch the Mi Unlock Tool and log in to the same Mi akka. Press the Unlock button. The process will take a few seconds, after which the phone will restart and clear the data.
What if Mi Unlock can’t see the phone?
Choosing the method of obtaining rights: Magisk or KernelSU
There are two main ways to get superuser rights today: the classic Magisk and the more modern KernelSU. The choice depends on the Android version and your goals. Magisk works in userspace and patches the boot image, making it compatible with most devices, but more visible to security systems.
KernelSU works directly in the kernel space, which requires a Generic Kernel Image (GKI), which is relevant for Android 12 and higher devices. KernelSU provides better stealth and performance, as it runs at a lower level than Magisk.
For older Xiaomi models running Android 10 or 11, Magisk remains a no-choice option. It has a huge module base and has been time-tested. However, for new flagships on HyperOS, it is preferable to use KernelSU if the developers have already ported it to your model.
- 🔹 Magisk: Universal, has many modules, easier to install through image patching.
- 🔹 KernelSU: Operates at the core level, virtually invisible to detectors, requires GKI nucleus.
- 🔹 APatch: A new player in the market that combines the benefits of both methods, but is less stable.
Install TWRP Recovery and Patching Image
The most common way to install rights is to use custom recavers, such as TWRP (Team Win Recovery Project), find the actual TWRP build for your smartphone model on the official XDA Developers forum or in the Telegram community channels, and using a Recovery from another model is guaranteed to cause breakdown.
Download the official firmware (Fastboot) ROM), The version that matches the version installed on your phone, and you need to extract the file from the firmware archive. boot.img. If you plan to use KernelSU, you may also need a file. init_boot.img, which appeared in Android devices 13+.
Go to Fastboot mode on your phone and connect it to your PC. Open the command line in the ADB tool folder and type in the command to run the recovery firmware:
fastboot flash recovery twrp_image_name.imgImmediately after entering the command, press the Volume Up + Power button so that the phone boots directly into TWRP. If you release the buttons and let the phone boot into the system normally, the stock recavery will overwrite TWRP, and the procedure will have to be repeated.
Inside. TWRP Go to the Install (or Advanced) menu → Install Image and select the previously prepared file boot.img, But not for firmware, but for patching through the Magisk app. APK-magisk ZIP-KernelSU archive on the phone and install it via the Install menu TWRP.
| File for patch | Android version | Tool. | Firmware section |
|---|---|---|---|
| boot.img | Android 10 - 12 | Magisk | Boot |
| init_boot.img | Android 13+ | Magisk / KernelSU | Init Boot |
| boot.img | Android 13+ (without GKI) | Magisk | Boot |
| kernel.img | Specific cases | KernelSU | Kernel |
💡
It is critically important to flash the recovery image immediately after the fastboot command, not letting the phone boot into the OS, otherwise the stock recovery will remove the modifications.
Magisk setup and root rights hiding
After the successful installation and the first restart, the Magisk icon will appear in the system. Open the application. If you see the version but you don't have the rights, you may need additional customization. Go to the settings (cogs) and turn on the Zygisk option. This is a modern MagiskHide replacement, necessary for many modules to work and hide the root.
To bypass the banking application detectors, you need to set up an exception list. In Magisk settings, turn on Enforce DenyList. Then go to Configure DenyList and check for any apps that shouldn't see the rights: banks, Google Pay, anti-cheat games.
⚠️ Warning: Once you turn on Zygisk and set up DenyList, be sure to perform a full reboot of the device (Reboot), not just a quick turn off of the screen.Without reboot, the changes will not take effect and the apps will continue to block.
It is also recommended to rename the Magisk package through the application settings to hide its presence from simple checks. Some advanced anticheats can detect the fact that the rights manager is already there, even if it is hidden. In such cases, the use of the Shamiko module helps, which enhances stealth, but requires you to disable the “Respect the exception list” in the Magisk settings (when installed Shamiko, the list works automatically).
Check for permissions with the Root Checker app, and if you're successful, congratulations, you've got full control of the device, and you can now install modules to change fonts, control CPU frequency, or improve sound.
Possible problems and solutions
Xiaomi users often experience a cyclic bootloop in the process of rooting. If the phone is stuck on the Mi or Android logo, don't panic. Try booting up to TWRP (clamping Volume Up + Power) and making Wipe Dalvik/Cache. If that doesn't work, you'll have to reflash the stock image of boot.img from the original firmware.
Another common problem is the failure of the NFC and Google Pay module after unlocking, which is due to a violation of system integrity, and in addition to setting up DenyList, you may need to remove security keys or use modules that mask the model of the device as a certified smartphone.
💡
If your fingerprint stops working after you get root, try formatting the Data partition in TWRP, but remember that this will delete all the files. Often the problem is desynchronizing the encryption keys.
Some users complain about fast battery discharge after installing Magisk.This is often caused by module conflict or Zygisk malfunction. Disable installed modules one by one to find the culprit. Also make sure you don't install modules designed for other versions of Android.