Root rights to Xiaomi Redmi: a full guide from unlock to Magisk

Getting root rights on Xiaomi Redmi smartphones opens up access to hidden Android features, but requires care: one wrong step can turn the device into a brick. 9A up to the flagship Redmi K70 Pro, but it's important to take into account the nuances of each firmware, and we'll break down the official way through unlocking the bootloader and alternative methods using Magisk or Magisk. TWRP, And we also know why on the devices with MIUI 14+ It may be necessary to bypass the protection through EDL-regime.

The process is divided into 3 stages: unlocking the bootloader (without it root is impossible), installing a custom recavator and directly obtaining the rights of the superuser. In 2026, Xiaomi tightened the requirements: now you need to connect the Mi Account account to the device and wait for up to 720 hours (30 days) of confirmation.

Preparation of the device: what to do before unlocking

Before starting the procedure, make sure your Redmi meets the following key requirements:

  • ๐Ÿ”‹ Battery charge of at least 60% (when unlocked, the boot loader consumes a lot of energy).
  • ๐Ÿ“ฑ Version. MIUI at least 12.5 (old firmware may not have drivers for Fastboot).
  • ๐Ÿ–ฅ๏ธ Windows computer 10/11 (for Mac/Linux Additional libusb drivers will be required).
  • ๐Ÿ”‘ Mi Account with confirmed phone number and email (unblocking is impossible without this).

Download the official Mi Unlock Tool utility from Xiaomi (check out the version - in 2026 it is up to date 5.5.224.31). Install the ADB and Fastboot drivers via Android SDK Platform-Tools.

  1. Settings โ†’ About Phone โ†’ MIUI version (tap 7 times to turn on the developer mode).
  2. Settings โ†’ Additional โ†’ For developers โ†’ Unlock OEM (turn on the slider).
  3. Debugging by USB on the same menu.

โš ๏ธ Note: If the developer menu does not have the item "Unblock" OEMยป, Your device is locked by an operator (e.g., Redmi from MTS or Beeline), in which case unlocking is only possible through the use of a device. EDL (emergency mode) with the risk of loss of guarantee.

๐Ÿ“Š Which Redmi model will you unlock?
Redmi Note 12/13
Redmi 10/11
Redmi K50/K60
Another model

Unlock the bootloader: the official way from Xiaomi

The official method involves the use of Mi Unlock Tool, but with 2023 Xiaomi has introduced a mandatory wait 720 hours (30 days) after the account is linked to the device, this rule applies to all models except Redmi A1/A2 and some regional versions:

  1. Connect your phone to your PC in Fastboot mode (turn off the device, then press Volume Down + Power).
  2. Launch the Mi Unlock Tool and log in to the same Mi Account as your phone.
  3. The utility will show a waiting timer, and if you see the words "Couldn't unlock," it means 720 hours have not passed.
  4. After the expiration date, try again: press Unlock and confirm the action.

Successful unlocking is accompanied by a reset of the phone to factory settings. All data (photos, contacts, apps) will be deleted! Backup in advance via Settings โ†’ Google โ†’ Backup or Mi Cloud.

Model RedmiDoes it take 720 hours to wait?Does TWRP support it?
Redmi Note 12/13Yes.Partially (unofficial assemblies only)
Redmi 10/11Yes (except for the Indian versions)Yes.
Redmi K50/K60Yes.Yes (patch required for MIUI 14)
Redmi 9A/9CNo (waiting 168 hours)Yes.

โš ๏ธ Warning: If the phone is stuck on the logo after unlocking MI longer than 10 minutes, do not try to reboot it forcibly. Connect to your PC and run the official firmware through the Mi Flash Tool (select the clean all option).

Mi Account Linked to Device|Data backup made.|Drivers installed ADB/Fastboot|Battery charge >60%|Unlocking enabled OEM-->

Installation of custom TWRP Recovery

TWRP (Team Win Recovery Project) is an alternative recovery that allows you to install unofficial firmware and modules Magisk. For Xiaomi Redmi, there are both official and custom TWRP builds. It is important to choose a version that is compatible with your model and the version of MIUI.

Download the current.img file TWRP for your device from twrp.me or forum XDA Developers. For example, for Redmi Note 12 Pro+ fit twrp-3.7.0_12-v7.4_A14-redwood.img. Installation is performed via Fastboot:

fastboot flash recovery twrp.img


fastboot boot twrp.img

After successful firmware, the phone will automatically reboot to TWRP.

  • ๐Ÿ“ Create a full backup of the current firmware (Backup section).
  • ๐Ÿ”ง Install Magisk to obtain root rights.
  • ๐Ÿ“ฑ Sweep custom firmware (for example, LineageOS or Pixel Experience).

On some models (Redmi) K60 Ultra, Redmi Note 13 Pro+) post-installation TWRP You may need to disable the DM-Verity check, or the system will not boot. TWRP Go to Advanced. โ†’ Terminal and execute:

echo "1" > /data/.magisk --disable-verity

๐Ÿ’ก

If TWRP doesn't start after firmware, try using the fastboot boot twrp.img command instead of fastboot flash recovery.This will temporarily load the recoveries without writing to the recovery section.

Getting root rights through Magisk

Magisk is a universal tool for obtaining root rights without violating the integrity of the systemless root, which allows you to hide root from applications (for example, banking or Pokรฉmon GO) and update MIUI without losing the rights of the superuser.

The latest version of Magisk (at the time of writing โ€” v26.4) download only from the official GitHub repository. TWRP:

  1. Download the Magisk-v26.4.zip file and transfer it to your phone.
  2. In TWRP, select Install โ†’ Select Magisk.zip โ†’ Swipe to Confirm Flash.
  3. Once installed, restart the device. When you first start, install the Magisk Manager app (downloads automatically).

To check the success of the procedure, open Magisk Manager and make sure that the top of the screen displays a green checkmark and the words "Installed: 26.4".

su

If you receive an input invitation (# instead of $), the root rights are active.

โš ๏ธ Attention: On devices with MIUI 14 Magisk can conflict with the HyperOS module. If after installing the root phone reboots to the bootloop, run the module. Magisk-Disable_Dm-Verity_ForceEncrypt.zip through TWRP.

What to do if Magisk is not installed?
If you install Magisk, you get a Failed to Mount error. /system", Your firmware is likely to use dynamic partitions: 1. Download the modified Magisk-Dynamic.zip forum XDA. 2. Sweat it instead of the standard Magisk. 3. After restart, run at the terminal: resetprop ro.boot.dynamic_partitions true

Alternative ways to get root

If official unlocking of the bootloader is not available (for example, due to operator binding), alternative methods may be used.

  • ๐Ÿ”ง EDL-Mode: Emergency boot mode, allowing you to flash the device without unlocking. Requires an authorized Xiaomi account (or bypass through firehose files). Suitable for Redmi with a blocked bootloader.
  • ๐Ÿ“ฑ Exploit Methods: Using Vulnerabilities in MIUI (For example, DirtyCow for older versions of Android, most exploits are shut down in 2026.
  • ๐Ÿ”„ Downgrade firmware: rollback to the old version MIUI, where it takes 72 to 168 hours to unlock instead of 720.

For EDL-will require:

  1. USB Type-C cable with data support (not all cables are suitable!)
  2. Mi Flash Tool and firmware in.tgz format.
  3. An authorized Xiaomi account (or a patched firehose for bypassing).

The firmware process through EDL:

  1. Turn off the phone, press Volume up + Volume down and connect to the PC (the screen will remain black).
  2. In the Mi Flash Tool, select the firmware and press Flash.
  3. After 5-10 minutes, the phone will automatically restart.

On devices with Qualcomm Snapdragon chipset 8 Gen 2/3 (Like Redmi. K70 Pro) EDL-The mode can be locked at the hardware level, in which case only official unlocking will help.

๐Ÿ’ก

EDL-The mode is a last resort, and its use voids the warranty and can cause hardware damage to the device if you do not do the right thing.

Risks and how to minimize them

Getting root rights to Xiaomi Redmi involves risks that fall into three categories:

  1. Software: Data loss, MIUI failures, inability to update OTAs.
  2. Hardware: In rare cases, damage to the EFS (IMEI) section.
  3. Security: Malware vulnerability (root gives applications unlimited access to the system).

To reduce the risks:

  • ๐Ÿ”„ Regularly create backups through TWRP (Boot, System, Data sections).
  • ๐Ÿ›ก๏ธ Install Magisk module to block malicious applications (MagiskHide) + XPrivacyLua).
  • ๐Ÿ“ต Do not use banking applications with active root (even with MagiskHide, blocking is possible).
  • ๐Ÿ”„ Update Magisk and TWRP last-minute.

If the root has stopped working after the root:

  • Google Pay / SberPay โ†’ Install the Universal SafetyNet Fix module.
  • Camera. โ†’ Switch the module. ANX Camera for GCam.
  • OTA-update โ†’ Download the firmware manually and stitch through TWRP.

On devices with MIUI 14+ and HyperOS, when you get root, you may lose the sound in the speaker or stop working NFC. This is due to the protection of AVB 2.0. The solution is to flash the patched boot.img with the signature verification disabled.

What to do after obtaining root rights

Now that you have root, you can optimize Xiaomi Redmi for your needs. Here are some useful steps:

  • ๐Ÿš€ Removing embedded debris: Mi Browser, Mi Video, GetApps and others can be removed via Titanium Backup or ADB: adb shell pm uninstall --user 0 com.miui.browser
  • ๐Ÿ”‹ Battery Optimization: Install Battery Charge Limit to limit charge (e.g. up to 80%).
  • ๐ŸŽฎ Game Tweaks: Game Optimizer Module allows you to overclock GPU Disable the lags in Genshin Impact or Call of Duty Mobile.
  • ๐Ÿ“ก Network Improvement: Replace modem.img on the best-supported version 5G (Relevant to the Redmi Note 12 5G).

To manage root rights, use:

  • Magisk Manager is the main tool for installing modules.
  • Root Explorer is a file manager with access to system folders.
  • Kernel Adiutor is a fine kernel setting (CPU/GPU frequencies, task scheduler).

If you plan to flash custom firmware (like LineageOS or ArrowOS), first check their compatibility with your Redmi model on the XDA Developers forum.Some firmware may not support HyperOS or new MediaTek Dimensity chipsets.

๐Ÿ’ก

After installing custom firmware, be sure to flash GApps (Google Apps), otherwise Google Play, YouTube and others will not work.

FAQ: Frequent questions about root on Xiaomi Redmi

โ“ Can I get root without unlocking the bootloader?
No, on all modern Xiaomi devices (starting with the Redmi Note 8), unlocking the bootloader is mandatory. The only exception is exploits for older versions of Android (for example, KingRoot for Android 8-9), but they do not work on MIUI 12+ and carry the risk of infection with viruses.
โ“ How long does it take to unlock the loader?
Since 2023, Xiaomi has set a mandatory wait of 720 hours (30 days) for most models. For older devices (such as the Redmi 9A) can be 168 hours (7 days).
โ“ Why the phone wonโ€™t boot after installing Magisk?
This is due to the DM-Verity test enabled. Solutions: Flow through TWRP file Magisk-Disable_Dm-Verity_ForceEncrypt.zip. Or manually edit the fstab in the section /vendor, I've replaced it with a checkout. MIUI 14+ may require a rollback MIUI 13 before rooting.
โ“ Can I return the guarantee after unlocking?
Technically, no, because unlocking the bootloader will void the warranty. However, some Xiaomi service centers turn a blind eye to root if the problem is not related to the software part (for example, a broken screen). To hide the traces of root: Remove Magisk through Uninstall in the settings. Select the official firmware through the Mi Flash Tool (select clean all and lock). Block the bootloader with fastboot oem lock. Attention: Once the bootloader is blocked, it will be harder to return the root!
โ“ Does Google Pay and Banking Apps Work with Root?
Most banking applications (including Sberbank Online, Tinkoff, Google Pay) block work on root devices. Bypass: Install MagiskHide Props Config and activate SafetyNet mode. Use alternative payment methods (such as Mir Pay or virtual cards). For Google Pay, additionally swipe the Universal SafetyNet Fix module. On MIUI 14+ and HyperOS, these methods may not work due to the new Hardware-backed Keystore verification mechanism.