[Guide] Root for Redmi Note 9 - Mediatek (Helio G85)
- Thread starter N3OMOD
- Start date
-
- Tags
- magisk mediatek redmi note 9 root
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.
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.
Unofficial TWRP Method: DO NOT PROCEEDE
I did find some time to test the procedure mentioned by @awahok - which I believe originated from a blog called UnofficialTWRP - and I must say that it doesn't work on my Redmi Note 9 (M2003J15SG) with MIUI Global 12.0.2.0 (QJOEUXM).
To be precise, the procedure is half-successful since I was able to sideload TWRP correctly but then the touchscreen interface was not responsive.
TWRP Main Screen is unusable - of course - without touch support, and the device is stuck in a soft-bricked state where the only option is to reboot into TWRP.
(no matter what key combination, I wasn't able to escape the recovery loop; fastboot mode was not reachable)
Thankfully TWRP enables/supports ADB so with the device stuck into the TWRP Main Screen It's possible to reboot into fastboot mode via CLI.
Once again in Fastboot Mode, I had to re-flash and start again from stock.
So, as of now, I wouldn't suggest following this procedure if you own a "Merlin NFC" model.
I did find some time to test the procedure mentioned by @awahok - which I believe originated from a blog called UnofficialTWRP - and I must say that it doesn't work on my Redmi Note 9 (M2003J15SG) with MIUI Global 12.0.2.0 (QJOEUXM).
To be precise, the procedure is half-successful since I was able to sideload TWRP correctly but then the touchscreen interface was not responsive.
TWRP Main Screen is unusable - of course - without touch support, and the device is stuck in a soft-bricked state where the only option is to reboot into TWRP.
(no matter what key combination, I wasn't able to escape the recovery loop; fastboot mode was not reachable)
Thankfully TWRP enables/supports ADB so with the device stuck into the TWRP Main Screen It's possible to reboot into fastboot mode via CLI.
Once again in Fastboot Mode, I had to re-flash and start again from stock.
So, as of now, I wouldn't suggest following this procedure if you own a "Merlin NFC" model.
It's highly advisable. You might still succeed without erasing user data, but chances of something going wrong increase without doing so.
It's a precautionary step that I strongly suggest following.
I successfully rooted my redmi note 9. Download rom from xiaomi website, extract boot.img and vbmeta.img from the rom, patch boot.img in Magisk Manager. Original vbmeta.img from the rom works.
The question is now, how can I replace the hosts file in system partition? It is read-only.
The question is now, how can I replace the hosts file in system partition? It is read-only.
Last edited:
I don't know exactly why, but with this method and/or version of Magisk I can't edit system partition either.
Maybe you could try through TWRP, however be aware you would probably break Safetynet that way.
Cheers
---------- Post added at 08:24 PM ---------- Previous post was at 08:06 PM ----------
I had been there too. How ever there's a most quick solution: flashing stock recovery partition from the last fastboot rom image avaliable.
You can also manage to do some basic task in this faulty TWRP through ADB: (eg. "adb shell twrp install /sdcard/file.zip")
Although touch-screen is completly unresponsive TWRP can work through adb command-line.
Thank you for the description
just installed MagiskManager 8.0.2 + Magisk 20.4 on MIUNI-Ver.: 12.0.3.0 (QJOEUXM) [Updates 2020-09-01]
+AdAway (including my whitelist hosts form old phone)
Now I'm gonna play with "Debloater", is it save? Any list of apps available to "get rid of", is there Apps I should not disable?
cheers
lino
just installed MagiskManager 8.0.2 + Magisk 20.4 on MIUNI-Ver.: 12.0.3.0 (QJOEUXM) [Updates 2020-09-01]
+AdAway (including my whitelist hosts form old phone)
Now I'm gonna play with "Debloater", is it save? Any list of apps available to "get rid of", is there Apps I should not disable?
cheers
lino
As a general rule of thumb. If you don't know what something does, don't get rid of it.
Also, if you have the option, disable the apps instead of uninstalling them, so you can revert your changes easily.
i have a problem with the phone, when i installed your version, it just make me to the set up and then when i swipe it unlocks and gives me a blurry white screen and boots again
+1
one other thing, why this method requires flashing a "custom MIUI" rom and not simply flashing magisk via recovery?
feels to me the current method is much more inconvenient and risky
Dear All;
Since a long time I'm trying to root my Redmi Note 9 M2003J15SG without any success, at least the success what I've in my head. I mean, from my ignorance I would like to raise a question: what's the point to root a device in which you can not modify the /system partition? Obviously I could made all wrong and that's why I can not, but, for instance, the twrp is most of the time getting stacked and I can not swipe it, once I can swipe it, I can install Magisk but the phone is going in bootloop with twrp. So I mean, probably is better to let the people from the twrp team to release a adhoc recovery and only then maybe we can try again.
Beside this particular experience, as a linux user, I would like to remark my sadness about the difficulties to find tools and tutorials using this OS environment. Luckly I found some java apps and the entire fastboot list of command are also available on linux.
Thanks for your time.
Since a long time I'm trying to root my Redmi Note 9 M2003J15SG without any success, at least the success what I've in my head. I mean, from my ignorance I would like to raise a question: what's the point to root a device in which you can not modify the /system partition? Obviously I could made all wrong and that's why I can not, but, for instance, the twrp is most of the time getting stacked and I can not swipe it, once I can swipe it, I can install Magisk but the phone is going in bootloop with twrp. So I mean, probably is better to let the people from the twrp team to release a adhoc recovery and only then maybe we can try again.
Beside this particular experience, as a linux user, I would like to remark my sadness about the difficulties to find tools and tutorials using this OS environment. Luckly I found some java apps and the entire fastboot list of command are also available on linux.
Thanks for your time.
Last edited:
This guide worked for me. My both Redmi Note 9 are rooted with magisk v20.4
I've used the original vbmeta.img from Stock ROM.
But, I can't install Riru-Core and Riru-Edxposed using MagiskManager-v8.0.3.
It says to install any magisk version 19+. I've tried to bypass this verification, but it fails.
So, I've installed MagiskManager-v7.5.1 and I can install Riru-Core and Riru-Edxposed perfectly.
Magisk shows modules list perfectly.
Edxposed shows its installed and working perfectly.
I've tried to install XPrivacyLua and now it is working perfectly too.
Thank you very much ❤❤❤
SOLUTION:
At first run of magisk you need to have your phone CONNECTED to internet (wifi or mobile) ! Once it detects the Redmi Note 9 as version, it installs a custom patch for magisk manager can works perfectly. IT IS EXTREMELY IMPORTANT.
I've used the original vbmeta.img from Stock ROM.
But, I can't install Riru-Core and Riru-Edxposed using MagiskManager-v8.0.3.
It says to install any magisk version 19+. I've tried to bypass this verification, but it fails.
So, I've installed MagiskManager-v7.5.1 and I can install Riru-Core and Riru-Edxposed perfectly.
Magisk shows modules list perfectly.
Edxposed shows its installed and working perfectly.
I've tried to install XPrivacyLua and now it is working perfectly too.
Thank you very much ❤❤❤
SOLUTION:
At first run of magisk you need to have your phone CONNECTED to internet (wifi or mobile) ! Once it detects the Redmi Note 9 as version, it installs a custom patch for magisk manager can works perfectly. IT IS EXTREMELY IMPORTANT.
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
7Preamble:
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:
- Magisk Manager
- Boot Image / Magisk Patched Boot Image / VBMeta Image - link or see attached files
Procedure:
- Download the attached files (or generate the first two on your own device, using Magisk Manager).
- Copy the prepared files inside the fastboot directory (so you don't have to worry about file path in the following steps)
- Reboot the phone into Fastboot Mode (hold Power+Volume Down until fastboot screen)
- 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 - 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.
- Phone will reboot at the end of the procedure. Launch once again Magisk Manager, select the "Beta Channel" for updates and enable Magisk Hide.
- Reload Magisk Manager, check for Safety Net: you should have the green light.
)
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.
5Removing "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
- Launch Magisk Manager and select "Download" from the menu
- Use the search function to locate the package "Busybox for Android NDK"
- Install the package, and chose to skip the reboot at the end of the procedure.
- Use the search function to locate the package "Debloater Terminal Emulator"
- Install the package and this time proceed with the reboot
- When the reboot is complete, install any terminal emulator app from PlayStore (like Termux)
- Open the terminal and issue:
(confirm the request for superuser access) and thenCode:
suCode: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.3Tested 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:
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.Code:fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img2
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-WHR4zOqJMdP4E2
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.
