[Guide] Root for Redmi Note 9 - Mediatek (Helio G85)

Search This thread

VD171

Senior Member
Jun 21, 2012
2,961
2
2,207
127.0.0.1
LG K10
Samsung Galaxy J7
Hi, please beg my pardon for the delay in following up, I wish to report for completeness of the information.

HOW TO SOLVE THE "BOOTLOOP" SCENARIO:

Quite every time this scenario presents upon a wrong/failed/incomplete/incompatible fastboot flash operation. Most of the times I've seen it happening due to an improperly patched boot.img being flashed to the phone.

Aside from re-entering fastboot and perform a complete factory restore, using the appropriate MiFlash Tool and the corresponding MIUI Fastboot ROM (as mentioned by others early in the tread), there is a second approach which is worth trying.

Upon re-entering fastboot mode, you can re-flash the original vbmeta.img and boot.img (you'll have these files extracted as per previous instructions) and issue a reboot. The device should then return to the original state and boot correctly.

Please note: I have tested this on two devices - same model - flashing a wrong boot.img file.



HOW TO DEAL WITH FUTURE MIUI OTA UPGRADES:

Of course, the device will still receive every OTA upgrade and if you launch the upgrade procedure the root will be lost.

You just have to follow again the guide using the most recent Boot Image and VBMeta Image, derived of course from the latest MIUI ROM.



INSTALLING CUSTOM RECOVERY - TWRP:

As of today, I haven't found time to properly test the procedure - as seen on various posts including the last one from @awahok - which takes advantage of the virtually identical hardware of the Redmi 10X to install a Custom TWRP made for that device onto a Redmi 9 (Marlin).

I'll try to follow-up on this and update this guide accordingly.


CLARIFICATION ON PATCHING BOOT.IMG:

While using Magisk to patch the latest boot.img file, there is no need to worry about the default options for Preserve DM-Verity and Preserve Force Encryption.

You can patch the boot.img leaving these options active - as per default in Magisk - since the only real issue is with the vbmeta.img file.

Only when flashing the vbmeta.img is paramount that you disable these options with the appropriate flags in fastboot terminal.


Nice, my friend. Thank you very much.

For what exactly is Preserve DM-Verity, Preserve Force Encryption and vbmeta.img ??
 

pewe

Senior Member
Oct 20, 2005
313
7
England
I recently rooted my Redmi Note 9 using this method and it went extremely smoothly.
I used the boot.img from the rom current at the time, patched it and away we went.
2 Weeks later a rom update was released and it installed on my phone without my realising, and this returned the phone to a non-rooted state - so I had to go through the whole process again.

Is the re-rooting procedure going to have to be followed every time a rom update is released, or is there a way to updating without have to go through the process of updating, re-rooting and reloading apps.
 
  • Wow
Reactions: linolino

historys

Senior Member
Dec 2, 2020
82
19
I recently rooted my Redmi Note 9 using this method and it went extremely smoothly.
I used the boot.img from the rom current at the time, patched it and away we went.
2 Weeks later a rom update was released and it installed on my phone without my realising, and this returned the phone to a non-rooted state - so I had to go through the whole process again.

Is the re-rooting procedure going to have to be followed every time a rom update is released, or is there a way to updating without have to go through the process of updating, re-rooting and reloading apps.
you should disable auto update
i'm updating when a semi-major update is released that increases performance/looks/settings
i'm still on 12.0.4.0
 

pewe

Senior Member
Oct 20, 2005
313
7
England
you should disable auto update
i'm updating when a semi-major update is released that increases performance/looks/settings
i'm still on 12.0.4.0

I assume that you too have to reload everything afterwards then.
What method do you use to make the re-installation of apps, messages etc quick and easy?
 

n4xiii

Member
Mar 11, 2021
10
0

Redmi Note 9 - Mediatek (Helio G35) root guide please ? i am looking for it more than 20 days​

 

VD171

Senior Member
Jun 21, 2012
2,961
2
2,207
127.0.0.1
LG K10
Samsung Galaxy J7
  • Like
Reactions: RN9_G85

TheMagnificent_Y

Senior Member
Feb 3, 2021
54
0
Heya,

I'm using the Redmi Note 9 / merlinnfc / 10X 4G

Shouldn't simply booting the image work as well? And why modify vbmeta?

I'm new to this, I once ended up bricking my Redmi Note 9 while trying an un-official method using TWRP,

PS: Does this method work for the LATEST global ROM? I.e. 11.0.5
 

VD171

Senior Member
Jun 21, 2012
2,961
2
2,207
127.0.0.1
LG K10
Samsung Galaxy J7
  • Like
Reactions: RN9_G85

TheMagnificent_Y

Senior Member
Feb 3, 2021
54
0
Heya, thanks, but is there any possible way you could provide me with the Images i need? The original Mega link got suspended.

My MIUI Version: 11.0.5 (Global Stable)

And Vbmeta since well.. y'know.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    Preamble:

    After a bit of research, I've found a simple way to - at least - obtain root privileges on the basic version of Redmi Note 9 (Mediatek - Helio G85).

    The procedure has been tested on a Redmi Note 9 Global NFC 4/128 (Model: M2003J15SG) with MIUI Global 11.0.5.

    The attached files comprise:

    • Original Boot Image from MIUI Global 11.0.5 (provided as a courtesy, download your own copy from MIUI Website if you wish)
    • Patched Boot Image from Magisk on MIUI Global 11.0.5 (again, the file provided as a courtesy; you can generate your own file, on your device.)
    • VBMETA Patched Image: essential to the process, this file has not been created by me. Courtesy of user Neko-kun from MI.cn Forum. I can only confirm that the file works as expected; please, if you have the required expertise, inspect the file and report your findings.

    Warning:

    This procedure depends on having previously unlocked the bootloader. Doing so you have read, understood and accepted all the information regarding security and potential stability issues given by XIAOMI before completing the procedure.
    Also, this means you have understood and accepted potential warranty issues arising from such procedure, and you understand the risks associated with a rooted device.
    I'm not responsible for any damage, loss of personal data, brick or loss of usability arising from following this procedure and/or from any user error committed by doing so.
    As a result, your warranty may be void, according to laws in effect in your state.


    This procedure is only valid for Redmi Note 9 (not the Pro version, not the 9S version) with MEDIATEK chipset


    Note:
    Always make a back-up of your data! This procedure will re-initialize the device.


    Requirements:

    • A valid MI Account, associated with the phone, used to certification in the bootloader unlocking procedure. (via official MI UNLOCK)
    • Unlocked Bootloader (new devices usually have a 7-day waiting period)
    • A personal computer with FASTBOOT installed, basic knowledge of FASTBOOT commands, drivers correctly installed on your system of choice. (for windows users, a valid solution is "Minimal ABD and Fastboot".)

    Resources:

    1. Magisk Manager
    2. Boot Image / Magisk Patched Boot Image / VBMeta Image - link or see attached files

    Procedure:

    1. Download the attached files (or generate the first two on your own device, using Magisk Manager).
    2. Copy the prepared files inside the fastboot directory (so you don't have to worry about file path in the following steps)
    3. Reboot the phone into Fastboot Mode (hold Power+Volume Down until fastboot screen)
    4. Connect the phone to the computer, open fastboot terminal and issue the following commands. BE PATIENT AND DOUBLE CHECK EVERYTHING BEFORE CONFIRMING! Text between round brackets are comments, it must not be copied.
      Code:
      fastboot devices (check your phone is the only device shown)
      fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)
      fastboot erase userdata (this will clear user data!)
      fastboot erase cache
      fastboot flash boot magisk_patched.img
      fastboot reboot
    5. The following first reboot will take a while. After completing the initial configuration, install the latest Magisk Manager (at the time of writing, v. 7.5.1) and continue with the configuration following the in-app prompt.
    6. Phone will reboot at the end of the procedure. Launch once again Magisk Manager, select the "Beta Channel" for updates and enable Magisk Hide.
    7. Reload Magisk Manager, check for Safety Net: you should have the green light.
    Enjoy your root privileges. (aka, get rid of the bloatware ;) )



    Known BUGs / LIMITATIONS:

    • Can't modify /system partition
    • Need to temporary set SELinux to permissive in order to remove system apps. Please refer to this post.
    5
    Removing "Bloatware"

    Probably one the main reasons for obtaining root privileges is to get rid of some default apps which come bundled with the official MIUI.

    Given the current situation for this device, using classic methods (such as Titanium Backup / System App Remover / etc.) is not possible and - most probably - attempting in doing so will result in a soft-brick.

    Instead, there is a particularly useful Magisk Module that can be used for this scope: Debloater.

    You can read more about it here on XDA; the installation procedure will vary just a bit since there is currently no TWRP support for the Helio G85 Redmi Note 9.


    Installing Debloater

    1. Launch Magisk Manager and select "Download" from the menu
    2. Use the search function to locate the package "Busybox for Android NDK"
    3. Install the package, and chose to skip the reboot at the end of the procedure.
    4. Use the search function to locate the package "Debloater Terminal Emulator"
    5. Install the package and this time proceed with the reboot
    6. When the reboot is complete, install any terminal emulator app from PlayStore (like Termux)
    7. Open the terminal and issue:
      Code:
      su
      (confirm the request for superuser access) and then
      Code:
      debloat


    Now you can use Debloat to remove all the unwanted applications that come bundled with the ROM.

    Please refer to the video included in the post mentioned above to learn more about Debloat and how to use it.
    3
    Tested on RN9 Global non-NFC (M2003J15SS) with MIUI 12 Global

    Hi, just to inform. The following was tested in Redmi Note 9 Global non-NFC (M2003J15SS) with MIUI 12 Global.

    - Patched boot image from MIUI12 Global (Android 10) works fine if dm-verity and forced encryption are disable at the time of making the boot image with magisk.

    - vbmeta file provided by OP also works (I think any file would work if it's flashed with "--disable-verity --disable-verification" option. This option is essential to avoid bootloop after flashing any non-stock (or patched) image to any partition:
    Code:
    fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
    The vbmeta file I used was extracted (and possibly) edited from a previous version of MIUI (MIUI11), and applied over MIUI12 ROM, that's why I think any file could be used.
    2
    The download link in the first post does not work any longer ... Gives a 404. Please re-upload and don't use XDA's upload space. Thanks!

    Sorry for the inconvenience, there is still the MEGA link from the first post up and working.
    Here it is: https://mega.nz/file/ucFDXIaY#FrUllKuUASoStlSvrcMYABsbYv6ie-WHR4zOqJMdP4E
    2
    So my device is not rooted?
    You don't need to modify the system to root with magisk.
    Magisk is SYSTEMLESS.
    Attach the main screen of the Magisk app and let's see.