Getting root rights to Xiaomi Redmi Note 9 (codename merlin) traditionally requires unlocking the bootloader through the official Mi Unlock Tool. However, this process involves waiting 7-15 days, binding to a Mi Account and the risk of losing warranty. Are there workarounds?
Yes, but with reservations. In this article, we'll look at alternative methods for getting root without unlocking the bootloader, their limitations and potential risks. It's important to understand that none of these methods will provide full root with modification of the system partition, we are talking about temporary or partial access. However, for most tasks (deleting the bloat, backup of applications, changing the DNS), this is enough.
Before you go ahead, check your deviceβs firmware version. The methods only work on MIUI 12β14 (Android 10β12) and require a rollback to the old firmware if you have a global version newer than V12.5.3.0.RJOMIXM installed. Use Settings β About Phone β MIUI version for clarification.
Why Official bootloader Unlocking Is Not Always Suitable
The process of unlocking the bootloader through the Mi Unlock Tool seems simple: link the device to your Mi Account, wait 168 hours (7 days) and unlock.
- π Resetting the waiting timer when you accidentally leave the account or change SIM-map.
- π« Block unlocking on devices purchased in some regions (e.g. India or China).
- π± Loss of warranty β even if unlocking is successful, Xiaomi service centers refuse repairs.
- π§ Difficulties with custom firmware - after unlocking not all custom ROM Works correctly with Redmi Note 9 due to problems with camera or module drivers NFC.
Alternative methods without unlocking the bootloader do not have these disadvantages, but have their limitations: for example, temporary root (through exploits) requires re-acquiring rights after each reboot, and Magisk in βsystemlessβ mode does not allow you to modify system files directly.
β οΈ Note: The methods described below may result in soft-brick (the device is switched on but not loaded beyond the logo). MI). Recovery is only possible through Fastboot with complete flashing and data loss!
Method 1: Temporary root through the DirtyCOW exploit (Android 10β11)
DirtyCOW (CVE-2016-5195) allows you to get temporary root rights without unlocking the bootloader. It runs on the Redmi Note 9 with firmware based on Android 10 and Android 11 (MIUI 12), but is not compatible with new versions of the kernel.
Implementation will require:
- π± Smartphone Redmi Note 9 with enabled debugging USB (Settings β The phone. β Version. MIUI β 7 times press to activate the developer mode, then Settings β Additionally. β For developers β Debugging by USB).
- π» Computer with Windows/Linux and installed drivers ADB/Fastboot.
- π Archive with utilities: DirtyCOW for Merlin (check the relevance of the link to the XDA Developers).
Step-by-step:
- Connect the phone to the PC and confirm the debugging permission.
- Open the command prompt (cmd) and check the connection: adb devices must display the serial number of the device.
- Download and unpack the archive with the exploit. Run the script: adb push dirtycow /data/local/tmp/ adb shell chmod 777 /data/local/tmp/dirtycow adb shell /data/local/tmp/dirtycow
- If the exploit worked, youβll see a message called Root success!. Now you can use an adb shell with superuser rights.
βοΈ Preparation for the use of DirtyCOW
Limitations of the method:
- β³ Rights are valid until the first reboot.
- π« It is not possible to modify system files (/system).
- π Requires the exploit to be re-run after each phone shutdown.
π‘
Use the adb shell su -c command "pm uninstall -k --user 0 com.miui.analytics" to remove Xiaomi analytics without unlocking the bootloader. Replace com.miui.analytics with another system application package if you want to uninstall another browser.
Method 2: Install Magisk via boot.img patch (without unlocking)
This is a way for users who need to root permanently, but without unlocking the boot.img, and the method is to extract the boot.img file from the firmware, modify it through Magisk, and download the patched image through Fastboot. Importantly, the bootloader remains locked, so the patched boot.img will have to be manually downloaded each time it is turned on.
Advantages:
- π§ Full Magisk with module support (e.g, ViPER4Android App Systemizer).
- π Ability to update firmware without losing root (subject to repeated patching) boot.img).
- π‘οΈ Data encryption is maintained (/data).
Instructions:
- Download the firmware for your model from the Xiaomi Firmware Updater website. Select the Fastboot version (not Recovery!).
- Remove boot.img from the firmware archive (located in the image folder).
- Install Magisk Manager on your phone and download it. boot.img So, the result is a file. magisk_patched.img.
- Reboot your phone to Fastboot (Switch Off β Hold Power + Vol Down)
- Download the patch image temporarily (without writing to the section): fastboot boot magisk_patched.img
| Action. | Team team. | Note |
|---|---|---|
| Connection check | fastboot devices | The serial number must be displayed. |
| Temporary loading of patched boot | fastboot boot magisk_patched.img | Root will be active until reboot |
| Permanent recording (not recommended!) | fastboot flash boot magisk_patched.img | Leads to bootloop on a blocked bootloader |
| Reboot. | fastboot reboot | After the reboot, the root will disappear. |
β οΈ Note: If you accidentally run fastboot flash boot instead of fastboot boot, the device will stop booting. Restore is only possible through full flashing in the Mi Flash Tool with loss of data. Always check commands before running!
Method 3: Using Shizuku for the ADB-root-access
If you donβt need a full root, but only need access to the Android API (for example, to backup apps or change settings through ADB), consider Shizuku.It allows you to run applications with adb rights without unlocking the bootloader and without risking damage to the system.
Shizuku works through USB debugging and does not require modification of system files.
- π± Data backup (Swift Backup, OAndBackupX).
- π§ Changes to system settings through ADB (For example, disabling MiuiOptimization).
- π Monitoring of application activity (AppOps).
How to set up:
- Install Shizuku from GitHub or F-Droid.
- Connect your phone to your PC and execute: adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
- In the Shizuku app, click Start and confirm access via ADB.
- You can now use compatible apps (e.g. AppOps or Swift Backup).
What apps work with Shizuku?
Limitations:
- π Requires a permanent connection to the PC or enabled debugging over Wi-Fi.
- π« No access to modification of system files (/system, /vendor).
- π Some features (such as Titanium Backup) donβt work.
Risks and how to minimize them
Any method of getting root without unlocking the bootloader comes with risks.
- π₯ Soft-brick β the device only loads to the logo MI. Reason: Incorrect modification boot.img Magisk module conflict.
- π‘οΈ Security breach β temporary root through exploits can be used by attackers to install malware.
- π΅ Loss of loss OTA-Updates - after modification boot.img Staff updates will no longer be installed.
- π Battery issues β some Magisk modules (such as Greenify) may conflict with energy-saving features MIUI.
How to reduce the risks:
- Data Backup: Use TWRP (if the bootloader is unlocked) or Swift Backup via Shizuku.
- Firmware check: Make sure that the MIUI version is compatible with the method you have chosen (see table below).
- Testing: Before using Magisk modules, check them for compatibility with Redmi Note 9 on the XDA or 4PDA forums.
- Recoil: Save the original boot.img for recovery in case of failure.
| MIUI version | Android | Compatible methods | Risks. |
|---|---|---|---|
| 12.0.1β12.5.3 | 10β11 | DirtyCOW, Magisk (patched boot) | Low (stable builds) |
| 12.5.4+ | 11 | Shizuku only. | Exploits don't work |
| 13.0β14.0 | 12 | Just a rollback to old firmware. | High (Brick Risk in Downgrade) |
π‘
On devices with MIUI 13+ and Android 12, temporary exploits (DirtyCOW) do not work. The only safe option is Shizuku or a pullback on MIUI 12.5.3.
What to do if something goes wrong
If after manipulations the phone stopped booting or there were errors, act on the algorithm:
- Soft-brick (hang on the logo) MI): π Try to download to Fastboot (Power) + Vol Down) and temporarily download the original boot.img: fastboot boot original_boot.img π₯ If it doesnβt work, run the full firmware through the Mi Flash Tool (select the clean all option).
- Bootloop (Cyclical Reboot): π§ Remove conflicting Magisk modules through ADB: adb shell magisk --remove-modules π Reboot to Fastboot and download the patched boot.img moduleless.
- Loss of network or camera: π‘ The problem is typical of unofficial firmware. MIUI via Mi Flash Tool. π· If the camera doesnβt work, check whether the ANXCamera or GCam module is compatible with your version. MIUI.
β οΈ Note: If after firmware through the Mi Flash Tool device requires authorization in Mi Account, but you do not remember the password, you can restore access only through the official Xiaomi service with confirmation of purchase.