Before rooting, you'll need an unlocked bootloader. Check my previous guide here: https://forum.xda-developers.com/x3...ck-bootloader-realme-x3-t4136325/post83109505.
After unlocking, we can get started with rooting.
First, you'll want to install Magisk Manager. You can find the latest APK here: https://github.com/topjohnwu/magisk/releases.
Next, you'll need to download the latest OTA OZIP. There's a link at the end of the post for this.
While that's downloading, you'll also need to grab a copy of an OZIP extractor. Follow the link below, download the repository as a ZIP, and unzip it.
For this program to work, you'll need Python 3 installed. On Linux systems, it should already be installed. On Windows 10, you can install Python from the Store.
Open a terminal or CMD window and cd to where you extracted the OZIP extractor files.
Use pip to install the docopt module: "pip3 install docopt".
Once the OZIP has finished downloading, move it to the same folder as the extractor program.
Run the following command: "python3 ozipdecrypt.py NAME_OF_OZIP_FILE". This will take a while!
Once it's done extracting, there will be a ZIP file with the same name as the OZIP. We only need two files from here: boot.img and vbmeta.img.
Extract those two files to the same folder as the extractor program.
Copy the boot.img file to your device.
Open Magisk Manager and choose the "INSTALL" option next to the Magisk status. Tap "INSTALL" in the dialog that appears and then choose "Select and Patch a File."
Browse to where you copied your boot.img to and select it. Magisk will now patch it and create a file named magisk_patched.img in your Download folder. Copy magisk_patched.img back to your computer.
Reboot your phone into fastboot: "adb reboot bootloader". If you don't have ADB or fastboot installed (which you should, since you needed them for the previous guide), you can find the link in the bootloader unlocking guide.
Before you flash the patched boot image, you need to disable image verification, which is where the vbmeta.img comes in.
Run "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" (remember, you'll probably need to unplug and replug the device after hitting Enter). This will disable boot verification and allow the patched image to actually work.
Finally, run "fastboot flash boot magisk_patched.img". This will flash the rooted boot image to your device.
Run "fastboot reboot" and let the phone boot back into the system. Check Magisk Manager and you should now be rooted!
Troubleshooting:
If you get an error that the boot image was "destroyed," don't worry. You'll just need to flash the stock boot.img and try again. Unplug your phone from your computer and wait for it to turn off. Once the screen is black, hold down VOL-DWN and PWR to enter fastboot mode. You can then run "fastboot flash boot boot.img" (where boot.img is the stock image) to restore. Reboot, then try the vbmeta and patched image flashing again.
You can get the OTA OZIPs from Realme EU's site: https://www.realme.com/eu/support/software-update.
You can get an OZIP extractor from here: https://github.com/bkerler/oppo_ozip_decrypt. (NOTE: you'll need to install the "docopt" Python module.)
OZIPs contain a boot.img, which you can extract and patch with Magisk for root. If someone else has an idea for patching Magisk into the boot.img, this is where to start.
Here's my patched boot.img for A.32. I don't recommend using this on other versions: https://www.androidfilehost.com/?w=files&flid=315334
Could you share your patched boot.img for the latest OS version? And could you check if the aux magisk module from X2 pro works to activate all aux cameras in Gcam? Thanks
Patched boot image
Thanks Zacharee1....Could someone upload the patched boot image for the latest one? Also do we have a generic version of twrp that can be installed on x3 ?? If yes, then we could try installing havoc gsi...
I've added a link to a patched A.32 boot.img.
also needed pip install pycryptodome win10
Zacharee1 said:
I've added a link to a patched A.32 boot.img.
Click to expand...
Click to collapse
Thanks a ton Zacharee!!
But it seems like I have A.33 version (https://www.realme.com/in/support/software-update)
I wish we had a video guide or something. Does anyone have a patched A.33 boot.img?
cheth20 said:
Thanks a ton Zacharee!!
But it seems like I have A.33 version (https://www.realme.com/in/support/software-update)
I wish we had a video guide or something. Does anyone have a patched A.33 boot.img?
Click to expand...
Click to collapse
It's pretty simple to patch it yourself. Download the OZIP, use the Python tool to unencrypt it, take the boot.img file out of the created ZIP, copy it to your device, and then patch with with Magisk Manager.
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Firmware for RMX2085
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
sukhad86 said:
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Click to expand...
Click to collapse
cheth20 said:
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
Click to expand...
Click to collapse
The firmware is the same for them all.
Great thread @Zacharee1. I have been waiting for this!
I have one question - is it mandatory to download the OTA package and do the patching? Is it because of the absence of recovery software like TWRP yet, for the X3 Super Zoom?
phonedroid said:
Great thread @Zacharee1. I have been waiting for this!
I have one question - is it mandatory to download the OTA package and do the patching? Is it because of the absence of recovery software like TWRP yet, for the X3 Super Zoom?
Click to expand...
Click to collapse
Yes, and that's why. It might be possible to pull the boot image directly from your device, but I'm not sure.
Can someone tell me if I can use realme 6 pro vbmeta.img?
realme x3 super zoom twrp recovery bro give me
Hi Sukhad,
I updated the system to the latest OTA (39), but I do not have the latest magisk patched file. Could you kindly help me with latest version patched boot for x3 superzoom?
sukhad86 said:
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Click to expand...
Click to collapse
Thanks Zacharee1!
Finally did it (15/20 year old windows machines... Win7 was dificult and finally use a win8). Worth big as root gives me a new smartphone
Had all sorts of problems (installing python... But once installed was pretty quick) mainly adb conneting...
Anyway I will share vbmeta.img attached for a38 rom.
Also link to boot img, again a38.
For A38 rom
http://www.mediafire.com/file/i9jvl1al95k40vv/magisk_patched_a38.img/file
bro please could u tell me.. help
cheth20 said:
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
Click to expand...
Click to collapse
bro please could u tell me.. after unlocking the bootloader of realme X3 superzoom , does it breaks the fingerprint sensor?
ota update after root
Someone have experiencing ota update failed on rooted device with this procedure? I m on RMX2081EU_11.A.40 but ota update to RMX2081EU_11.A.42 fails. how to update now?
Good afternoon. I want to get a root for my X3 super zoom, but I literally do not understand all the manipulations so that your description is attached with an image (screenshots). I think it will be useful for everyone who can't.
Anyone have working patched boot.img for a46?? I'm trying and always boot destroyed. Magisk 21.4
It's really weird on official en site there is a42 soft from September but on pl site there is a46 from December.
Related
Requirements / Downloads
Honor 10 view BKL-09 with unlocked bootloader (I not tested in other version)
Minimal ADB & Fastboot
Patched Recovery_Ramdisk BKL
Rooting your device
1. Unzip Minimal ADB & Fastboot to any folder of your PC
2. Download the patched file for your device and copy it to Minimal ADB & Fastboot folder.
3. Start your smartphone in fastboot mode pressing [Vol-]+[Power] and connect it to your PC.
4. Open a Powershell window in your Minimal ADB & Fastboot folder by [Shift]+[Rightclick].
5. Flash the Recovery_Ramdisk:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
Adjusting Magisk Manager and patching files by yourself
1. Download Magisk Manager canary build to your phone and install.
2. Change in Magisk settings the update channel to "custom" inserting this URL. https://t2m.io/wuAFCrwO
Magisk Manager now will find the canary builds.
3. Check "force encryption" and "AVB 2.0" boxes.
To patch yourself recovery_ramdisk:
4.a) Patch your *.img, that you have copied in any folder to your smartphone by pressing "Install" --> "Install" --> "Patch boot image" in Magisk Manager.
ORIGINAL RECOVERY_RAMDISK BKL-09 PIE version 9.0.0.162 C432
5. Transfer the patched file (You will find it in your download folder of your smartphone. It will be called "patched_boot.img".) to your PC, start Smartphone in fastboot mode and flash:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
(You must adapt the file name to the real name of your file, e.g. patched_boot.img)
To actualize Magisk:
4.b) Choose in Magisk Manager: "Install" --> "Install" --> "Direct Install (Recommended)" --> Restart
Thanks
Thanks a lot for this great guide!
Hello, will this also be on my bkl-l09c432? I have rom
blazios said:
Hello, will this also be on my bkl-l09c432? I have rom
Click to expand...
Click to collapse
If your device is on pie ?, yes
What should I use twrp?
blazios said:
What should I use twrp?
Click to expand...
Click to collapse
OP never mentioned anything about twrp. That is not needed
I Have same version as you Android Pie and everythin firmware and region... But no matter how i try i get UNABLE TO UNPACK BOOT IMAGE... Instalation failed... why is that? i have TWRP installed... and everything as is your phone firmware and version 9.0.0.162 C432...
BlueMan_86 said:
I Have same version as you Android Pie and everythin firmware and region... But no matter how i try i get UNABLE TO UNPACK BOOT IMAGE... Instalation failed... why is that? i have TWRP installed... and everything as is your phone firmware and version 9.0.0.162 C432...
Click to expand...
Click to collapse
Flash in bootloader mode. Not in twrp.
Android pie not work with twrp for now.
I am on ROOTED EMUI 8.0 (BKL-L09 8.0.0.130). How do I update to pie and then root? First unroot than update than root? or just update and root with the instructions in post#1?
Sadly it does not work for me. Tried it with your patches bootimage and with my own. Flashing the ramdisk works fine but after restart I don't have root.
I dont need Magisk installed if I use the pre patches bootimage right? Nevertheless I tried with Magisk installed and without. In the Huawei Mate Forum I read that one might need to shutdown the phone after flashing and then to start it with Volume Up and Power Button pressed. But this also does not work. Or any Idea how exactly to start with this Key combination?
Any other suggestions?
Today I updated from OREO with root to PIE same version as you have in pictures 9.0.0.162(C432E4R1P9). Tried both steps (with your patched file and me patching file) to root my phone but even I always got OK in fastboot mode I still have no root
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
resdano said:
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
Click to expand...
Click to collapse
I get the same error
any advise ?
Worked like a breeze for me. Shoutout to @ante0 and @shashank1320 who kept their calm in guiding me through and suggesting me this method.
@ante0 made things easier for me and it worked excellently for me. The steps are-
Download and install Magisk canary builds from the mentioned link. Change in Magisk settings the update channel to "custom" inserting*this*URL.*https://t2m.io/wuAFCrwO
Magisk Manager now will find the canary builds.
Check "force encryption" and "AVB 2.0" boxes.
Transfer stock recovery ramdisk to phone, open Magisk Mnager and hit install - > patch boot image, select recovery_ramdisk.img. Take patched_boot.img from /sdcard/Download/ and transfer to computer, reboot to fastboot and flash patched_boot.img to recovery_ramdisk. Unplug USB, holv vol up + power to reboot to recovery, which will now boot phone with Magisk. If you reboot and don't hold vol up it will boot to system without root.
---------- Post added at 02:08 PM ---------- Previous post was at 02:01 PM ----------
Huge thanks @fabio84
Finally have root privileges on Pie.
resdano said:
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
Click to expand...
Click to collapse
davidsiv said:
I get the same error
any advise ?
Click to expand...
Click to collapse
Emui9 doesn't have a ramdisk partition. You flash to recovery_ramdisk, then when you reboot hold volume up to get to recovery (unplug USB as it will take you to erecovery if you have it plugged in).
This is the only way to get root on Emui9, currently.
It will not boot to recovery, it will boot to system with Magisk.
Not flash ramdisk. Need flash recovery_ramdisk!
worked, thanks
fabio84 said:
Not flash ramdisk. Need flash recovery_ramdisk!
Click to expand...
Click to collapse
@ante0 has been helping me get root access and we still are working on it.
@fabio84 did you by a chance experience issues in using root applications especially root explorer or root Uninstaller? For some reason they won't just work for me, just titanium and root checker works. On further scrutinising, I found the su binary files missing probably why the applications won't load for me. Any help?
ankan1993 said:
@ante0 has been helping me get root access and we still are working on it.
@fabio84 did you by a chance experience issues in using root applications especially root explorer or root Uninstaller? For some reason they won't just work for me, just titanium and root checker works. On further scrutinising, I found the su binary files missing probably why the applications won't load for me. Any help?
Click to expand...
Click to collapse
Update: @ante0 helped me yet again to figure it out. Apparently was because of pie's aggressive background restrictions. Root is now working full fledgedly. Thanks everyone. Big cheers to @ante0
Hello,
It finally worked for me. Thank you so much!
ante0 said:
Emui9 doesn't have a ramdisk partition. You flash to recovery_ramdisk, then when you reboot hold volume up to get to recovery (unplug USB as it will take you to erecovery if you have it plugged in).
This is the only way to get root on Emui9, currently.
It will not boot to recovery, it will boot to system with Magisk.
Click to expand...
Click to collapse
this guide help you to root k20/mi9t by using magisk patched boot img
this guide is for users who likes to be on stock with magisks modules customisation
advantage
[no data loss in whole process]
[safety passes okk]
[install modules like dolby,viper4android after root to improve sound quality]
REQUIREMENTS
.unlocked bootloader( its one time requirement)
.magisk patched boot img
patched boot img is created using stock boot img that is different for every miui version,so create your own patched boot img according to your miui version by this easy process https://forum.xda-developers.com/mi...dian-rom-v10-3-6-0-twrp-t3958566/post80163818
just to be on safe side remove all types of lock, u can use lock after all steps completed
NOW FOLLOW THE STEPS
install latest magisk manager apk
place the downloaded magisk patched boot img to adb folder or platform tool folder whatever u call in pc
1.boot your phone into fastboot by holding power menu &volume down button togethor
2.connect your phone to pc using original cable
3.Go to adb folder & open command window by clicking shift+control+right key on the blank space (command window appear in option)
4.now check your devices by if its properly connected by typing
code: fastboot devices
if it shows attached devices then proceed
5.now flash patched img by typing command
code: fastboot flash boot magisk_patched.img
finally boot your phone to system by typing command
code: fastboot reboot
6.now open magisk manager it show some recommendation just reject that option(important steps)
7.click on install in magisk manager then select direct install recommended option
let it install &reboot [step 7 is neccessary otherwise you cant install module in magisk)
this is 100% tested method
need any help or confused comment down below before attempting this
hit THANKS BUTTON IF U LIKE
Is bootloader unlock is required because you didn't mentioned that....
if u debloat xioami apps in miui roms & do some customization with magisk module .its become quite useful rom for a while now until stable custom rom available for use
RSM10 said:
Is bootloader unlock is required because you didn't mentioned that....
Click to expand...
Click to collapse
yes bootloder unlocked is required this is basic
u can do very little customisation like debloating with locked bootloader
Thanks I knew that bl unlock is required but since you didn't mentioned it here I thought you found a way out without unlocking bl. This patched boot.img is for 10.3.6.0 What if there is new update, then we will lost root.
i will try to provide patched boot img for future updates
rkview37 said:
this guide help you to root k20 by using magisk patched boot img
this guide is for users who likes to be on stock with magisks modules customisation
advantage
[no data loss in whole process]
[safety passes okk]
[install modules like dolby,viper4android after root to improve sound quality]
REQUIREMENTS
.unlocked bootloader
.magisk patched boot img (download from link below)
.must be on miui v10.3.6.0
just to be on safe side remove all types of lock, u can use lock after all steps completed
download magisk patched boot img provided by me
https://mega.nz/#!CpUz3KwB!76fE3z30gngG282mA9DzS05AZyjG6RuQFs5-STg2kXE
now follow steps carefully
install latest magisk manager apk
place the downloaded magisk patched boot img to adb folder or platform tool folder whatever u call in pc
1.boot your phone into fastboot by holding power menu &volume down button togethor
2.connect your phone to pc using original cable
3.Go to adb folder & open command window by clicking shift+control+right key on the black space (command window appear in option)
4.now check your devices by if its properly connected by typing
code: adb devices
if it shows attached devices then proceed
5.now flash patched img by typing command
code: fastboot flash boot magisk_patched.img
finally boot your phone to system by typing command
code: fastboot reboot
6.now open magisk manager it show some recommendation just reject that option(important steps)
7.click on install in magisk manager then select direct install recommended option
let it install &reboot [steps 7 is neccessary otherwise you cant install module in magisk)
this is 100% tested method
need any help or confused comment down below before attempting this
hit THANKS BUTTON IF U LIKE
Click to expand...
Click to collapse
Thank you keep updating as and when stock updates are received.
Sent from my [device_name] using XDA-Developers Legacy app
If we receive ota update. How should we install? Will magisk stay?
Sent from my [device_name] using XDA-Developers Legacy app
Can i do magisk update regularly?
manan001 said:
If we receive ota update. How should we install? Will magisk stay?
Sent from my [device_name] using XDA-Developers Legacy app
Can i do magisk update regularly?
Click to expand...
Click to collapse
1)as we all know k20 is single partition device.so we cannot perform ota whiile preserving magisk,i will update op with all info once i figured out a way to save effort of installing all modules all over again
2)magisk can be updated regularly,no issues at all
Finally installed magisk. Thanks for the detail steps. It works well.
Sent from my [device_name] using XDA-Developers Legacy app
10.3.8 OTA update available.
Patched boot.
https://drive.google.com/folderview?id=1-3QhAjIH5JmrlZaYgsCjr92XjcUv90nN
Sent from my [device_name] using XDA-Developers Legacy app
manan001 said:
10.3.8 OTA update available.
Patched boot.
https://drive.google.com/folderview?id=1-3QhAjIH5JmrlZaYgsCjr92XjcUv90nN
Click to expand...
Click to collapse
from where did you extracted stock boot img
afaik latest 10.3.8.0 stock rom not available on any site yet
manan001 said:
10.3.8 OTA update available.
Patched boot.
Do you have the stock recovery.img ?
How to update via OTA when i am on twrp ?
Can you confirm if root working after flashing your patched boot image ?
Click to expand...
Click to collapse
rkview37 said:
from where did you extracted stock boot img
afaik latest 10.3.8.0 stock rom not available on any site yet
Click to expand...
Click to collapse
In phone update we get option to download full rom ota. I downloaded and extracted boot.img, rest you know the process.
If you like my work do hit like button.
Dear Rkview31
If the flash install of the patched image fails, can we reinstall de rom with miflash? Or, is enough to reflash by fastboot command line the original fastboot rom image?
Can any one provide stock recovery (10.3.6) please.
neek619 said:
Can any one provide stock recovery (10.3.6) please.
Click to expand...
Click to collapse
go here
download from my mega account
https://mega.nz/#!Ok8yBYaB!N9CnTLSfpvoakHiQGDyyIxDvEL0MUmUsxAQqj3nhSu0
Guys
This procedure wokrs with eea device?
mauriciocardoso said:
Guys
This procedure wokrs with eea device?
Click to expand...
Click to collapse
guide is okk but stock boot img of every rom is different so patched boot img in this thread will not work for u
rkview37 said:
go here
download from my mega account
https://mega.nz/#!Ok8yBYaB!N9CnTLSfpvoakHiQGDyyIxDvEL0MUmUsxAQqj3nhSu0
Click to expand...
Click to collapse
Thanks for the file, was able to update to 10.3.8
Patched boot image by @manan001 in the link above do not work and reboots phone in recovery mode.
Patched my own boot image works fine with 10.3.8
https://drive.google.com/file/d/1-odNizuv4HlEw92O8tl_X13aQxdFwbGe/view?usp=drivesdk
VERY IMPORTANT:
Please make sure your boot.img version matches the ROM version . that's mean if you update your device then you have to use patch boot.img from new recovery rom.never use the old one. If they mismatch you might brick your phone and MediaTek phones are HELL to unbrick.
YOU HAVE BEEN WARNED.
Yes you can root your phone without data loss. You do not need to you type so much command line. You have to patch the stock boot image file with magisk manager. Then you have to download a a blank vbmeta.img file.(link in this post)
Then run this command
fastboot flash vbmeta vbmeta.img
fastboot flash boot patch-boot.img
%%replace patch-boot as your file name...
I guarantee you no data loss.
Remember one thing...
You must patch the correct boot image of your rom... If you to flash a wrong version of bhoot image then you have some problem.
Suppose you update miui global 11.0.5.0 from 11.0.4.0 and you use 11.0.4.0 version patch boot image file....
Then your device boot up but you can not play any music .....i do this dump thing.....but do not worry just flash currect patch boot image and your problem is gone...
Shas45558 said:
Yes you can root your phone without data loss. You do not need to you type so much command line. You have to patch the stock boot image file with magisk manager. Then you have to download a a blank vbmeta.img file.
https://forum.hovatek.com/thread-32719.html
Go to method 3....log in to download vbmeta.img file.
Then run this command
fastboot flash boot patch-boot.img
fastboot flash vbmeta vbmeta.img
%%replace patch-boot as your file name...
I guarantee you no data loss.
Remember one thing...
You must patch the correct boot image of your rom... If you to flash a wrong version of bhoot image then you have some problem.
Suppose you update miui global 11.0.5.0 from 11.0.4.0 and you use 11.0.4.0 version patch boot image file....
Then your device boot up but you can not play any music .....i do this dump thing.....but do not worry just flash currect patch boot image and your problem is gone...
Click to expand...
Click to collapse
Hey @Shas45558, I can't root MIUI V11.0.7.0.Q having tried these steps on a friend's phone yesterday. It worked on my phone on V11.0.50.Q but I also installed that update though my bootloader is still locked as you may know
nielsync said:
Hey @Shas45558, I can't root MIUI V11.0.7.0.Q having tried these steps on a friend's phone yesterday. It worked on my phone on V11.0.50.Q but I also installed that update though my bootloader is still locked as you may know
Click to expand...
Click to collapse
Do u flash vbmeta.img?? (Download from this post)
It workes for me every time...
When any update appires you should download full recovery rom reather then otq update.
Then extract and patch boot which is insiDe the recovery rom...
It will must work...
Shas45558 said:
Do u flash vbmeta.img?? (Download from this post)
It workes for me every time...
When any update appires you should download full recovery rom reather then otq update.
Then extract and patch boot which is insiDe the recovery rom...
It will must work...
Click to expand...
Click to collapse
That's exactly what I did. Downloaded the full recovery rom and extracted it. Patched the boot.img inside images folder with Magisk canary and after copied it to my PC and flashed it via fastboot. I then flashed the vbmeta after. Do you mind sharing with me your patched boot image for V.11.0.7Q? Maybe I'll have luck with that otherwise I did everything right. Its really strange.
nielsync said:
That's exactly what I did. Downloaded the full recovery rom and extracted it. Patched the boot.img inside images folder with Magisk canary and after copied it to my PC and flashed it via fastboot. I then flashed the vbmeta after. Do you mind sharing with me your patched boot image for V.11.0.7Q? Maybe I'll have luck with that otherwise I did everything right. Its really strange.
Click to expand...
Click to collapse
You should use your phone and magisk manager To patch boot image file...
Do not use computer to patch it
I give the boot file in this post which root your redmi 9 based on global v11.0.7.0....
Do not flash it on outher version...
Extract mboot7.tar you get mboot7.img....
Flash it and enjoy root on globalv11.0.7.0....
Do not forget to flash vbmeta.img....
Flash vbmeta file then patch boot file..
Good luck..
Shas45558 said:
You should use your phone and magisk manager To patch boot image file...
Do not use computer to patch it
I give the boot file in this post which root your redmi 9 based on global v11.0.7.0....
Do not flash it on outher version...
Extract mboot7.tar you get mboot7.img....
Flash it and enjoy root on globalv11.0.7.0....
Do not forget to flash vbmeta.img....
Flash vbmeta file then patch boot file..
Good luck..
Click to expand...
Click to collapse
Thanks a lot it worked!!! :good:
I've been patching using Magisk Manager canary version on the phone. What version of Magisk Manager did you use It's really strange
nielsync said:
Thanks a lot it worked!!! :good:
I've been patching using Magisk Manager canary version on the phone. What version of Magisk Manager did you use It's really strange
Click to expand...
Click to collapse
I use this version of magisk manager and it always work
Shas45558 said:
I use this version of magisk manager and it always work
Click to expand...
Click to collapse
Thanks. I've been using Magisk Manager beta/canary and it seems it does not patch the boot image properly. You are the best.
Thanks for the post. It helped me to root my redmi note 9.
nielsync said:
Thanks. I've been using Magisk Manager beta/canary and it seems it does not patch the boot image properly. You are the best.
Click to expand...
Click to collapse
Welcome. Redmi 9 and redmi note 9 are are based on same chipset mt6768....
And so the process help you. I think it is the same to root any device running on Android 10.
And vbmeta.img which I provide upper post, is a universal vbmeta.img. you can use it to flash any Android device which has vbmeta partition because this vbmeta.img is a dummy file or you can call it as a blank file...
Shas45558 said:
Welcome. Redmi 9 and redmi note 9 are are based on same chipset mt6768....
And so the process help you. I think it is the same to root any device running on Android 10.
And vbmeta.img which I provide upper post, is a universal vbmeta.img. you can use it to flash any Android device which has vbmeta partition because this vbmeta.img is a dummy file or you can call it as a blank file...
Click to expand...
Click to collapse
My issues was patching using the canary version of Magisk Manager which isn't stable enough and was probably not patching the boot image properly as opposed to Magisk Manager 7.5.1 which is the stable version. Nice explanation on the vbmeta.img file.
VERY IMPORTANT:
Please make sure your ROM version matches the ROM version of those patched boot image and files. If they mismatch you might brick your phone and MediaTek phones are HELL to unbrick.
YOU HAVE BEEN WARNED.
For the post author:
Thanks for your effort
I understand you are trying to help and that you put a note at the end of your post. But please make it clear at the BEGINING, that this method is valid for this specific ROM Version "xx.x.xx.x.x"
I guess this still doesn't unlock the bootloader, and what about system updates?
Kiwironic said:
VERY IMPORTANT:
Please make sure your ROM version matches the ROM version of those patched boot image and files. If they mismatch you might brick your phone and MediaTek phones are HELL to unbrick.
YOU HAVE BEEN WARNED.
For the post author:
Thanks for your effort
I understand you are trying to help and that you put a note at the end of your post. But please make it clear at the BEGINING, that this method is valid for this specific ROM Version "xx.x.xx.x.x"
Click to expand...
Click to collapse
Ok i do ir on top and bottom of the post and thanks for your advice:good::good:
I have an issue. I cannot install any custom recovery on Redmi 9, no matter how much I try (Twrp or PBRP). Every time the phone reboots directly. There is anyone that can help me?
rizelgeorgel said:
I have an issue. I cannot install any custom recovery on Redmi 9, no matter how much I try (Twrp or PBRP). Every time the phone reboots directly. There is anyone that can help me?
Click to expand...
Click to collapse
Download pbrp from official website.then extract it and you will get a .img file.flash it via fastboot mood and the cmd is
fastboot flash recovery pbrp.img
*Change pbrb.img according to your file name.
One big question..did you unlock your bootloader and root your device?
Thank you very much! I succeeded according to your advice!
shas hows pbrp?
regarding flashing?
mhark.moby said:
shas hows pbrp?
regarding flashing?
Click to expand...
Click to collapse
Pbrp is in beta testing....so it has some bug and there's no use to install..
Buenas tardes tengo problemas al cargar el parche de magisk en redmi 9. Cuando cargo el boot.img parchado de magisk el tlfn queda en bootloop estoy en la version 11.0.8 global.
Hi all and sorry for my bad english in first!!
i live in italy and i've buyed(but still not recieved) one oneplus 9r from china whit oxygenos rom on board..
When it comes i want to root & debloat it, but i've some queustion cause in last year i've used only device with custom rom!.
first of all i wan't to root the phone, but preserve the possibility to update the OS with ota. if i understand right it's possible with magisk, can please someone tell me the correct step to make?
after root i vant to uninstall not necessary app for my utilization (facebook/instagram/netflix, red cable and oneplus account, google app, gdrive, google photo and most of BigG apps cause i'm using only gmail/yt/maps/ an store!).
the question is.... if i uninstall this app it will be re installed in future ota?
Thanks in advice!
Step1 : unlock bootloader, this will wipe the storage, then setup the device once again then enable usb debugging in developer options.
You can use this
Tool to make (tool all in one) your life easier : https://sourceforge.net/projects/tool-all-in-one/files/TOOL_ALL_IN_ONE_1.0.6.1.zip/download
you should select 8t as 9r is not supported officially
at the moment.
Step2: update the phone to latest version , right now it's 11.2.5.5
Step 3: download the same version of the oxygen is ota wether from xda, OnePlus official site , oxygen updater ( make sure it is full version).
Step4: on pc now extract only the payload.bin file in the input of the payload extracter ,
Now use the payload extracter ,
Run .exe and get boot.img .
payload_dumper_tool_by_ius.zip
drive.google.com
(MAKE SURE THE PHONE OS VERSION AND BOOT IMG VERSION IS SAME)
Step 5: install magisk manager on phone, now patch the boot.img that you extracted earlier. Copy this patched boot.img in platforms tool folder(I hope that u have installed the platform tools and adb & fastboot ).
Step 6: open terminal there in platform tools , use the tool all in one to boot your phone in fast boot mode,then flash patched boot.img using.
Fastboot devices
Fastboot flash boot_a patched.img
Fastboot flash boot_b patched.img
Bingo got rooted.
Step 7( optional) : now properly restart the phone by opening magisk , then install universal safety net fix, debloat modules in magisk.
You can use lucky patcher to debloat unnecessary things (which don't exist as it is oxygen os)
Now in future if your phone gets ota make sure you disable all magisk modules then download the full version of ota from oxygen updater & update it locally & do not restart.
go to magisk ,
flash magisk to inactive slot.
restart now,
REnable the modules. (Tip don't enable the lucky patcher module this will put you in bootloop)
enjoy the ota .
@Rajveer chauhan
Do you have instructions to install TWRP?
I even tried to read the thread on the 8t forum, but I didn't understand it very well.
So, 1st of all make sure u are on oos , then simply boot in to bootloader then flash this ofox img file , using the command
fastboot flash recovery name.img then boot into recovery it will ask u your screen lock, then flash this ofox zip file .
this or any recovery are in beta phase , everything works but not 100/100 times.
unzip this and flash the img cuz the img could not be uploaded
this will only work on oos not on any custom rom, uwill not require to format data
& trust me i am not a hacker
Rajveer chauhan said:
So, 1st of all make sure u are on oos , then simply boot in to bootloader then flash this ofox img file , using the command
fastboot flash recovery name.img then boot into recovery it will ask u your screen lock, then flash this ofox zip file .
this or any recovery are in beta phase , everything works but not 100/100 times.
unzip this and flash the img cuz the img could not be uploaded
this will only work on oos not on any custom rom, uwill not require to format data
& trust me i am not a hacker
Click to expand...
Click to collapse
Is Orange Fox easy to use as TWRP?
Just flash via fastboot? Because I want to keep magisk/root.
lvints said:
@Rajveer chauhan
Do you have instructions to install TWRP?
I even tried to read the thread on the 8t forum, but I didn't understand it very well.
Click to expand...
Click to collapse
lvints said:
Is Orange Fox easy to use as TWRP?
Just flash via fastboot? Because I want to keep magisk/root.
Click to expand...
Click to collapse
Way better than twrp just follow the steps u won't lose anything
lvints said:
Is Orange Fox easy to use as TWRP?
Just flash via fastboot? Because I want to keep magisk/root.
Click to expand...
Click to collapse
So how did it go?
Rajveer chauhan said:
So how did it go?
Click to expand...
Click to collapse
I've already downloaded the files, but I haven't tested them yet.
I'll leave it for the weekend, if there's a problem I can solve it with peace of mind.
Sir have you tried changing the font of your 9R?
I've been looking on the magisk forums or some app but I haven't had success.
Yeah I actually use the Einstein font the font manager by androidacy seems to work for me.
Rajveer chauhan said:
Yeah I actually use the Einstein font the font manager by androidacy seems to work for me.
Click to expand...
Click to collapse
I tried this module too, only with Komika font, my favorite.
What version of the module do you use? I tried with the last one (5.5.6) and the font doesn't seem to have been applied.
I'm on OOS 11.2.7.7.
Same version
lvints said:
I tried this module too, only with Komika font, my favorite.
What version of the module do you use? I tried with the last one (5.5.6) and the font doesn't seem to have been applied.
I'm on OOS 11.2.7.7.
Click to expand...
Click to collapse
.
Rajveer chauhan said:
So, 1st of all make sure u are on oos , then simply boot in to bootloader then flash this ofox img file , using the command
fastboot flash recovery name.img then boot into recovery it will ask u your screen lock, then flash this ofox zip file .
this or any recovery are in beta phase , everything works but not 100/100 times.
unzip this and flash the img cuz the img could not be uploaded
this will only work on oos not on any custom rom, uwill not require to format data
& trust me i am not a hacker
Click to expand...
Click to collapse
I flashed the img file and it booted to OrangeFox but I cannot press anything as the screen does not react. What is the solution for it?
It's is compatible with oos 11
Not with oos 12, any custom roms
Rajveer chauhan said:
It's is compatible with oos 11
Not with oos 12, any custom roms
Click to expand...
Click to collapse
I was on OOS 11. The 11.2.8.8.LE28DA.
Flashed it, boot up but cannot press anything. How can I go back to the original boot?
U can unzip the payload.bin and extract the recovery file and flash it in the bootloader and everything goes normal
Rajveer chauhan said:
U can unzip the payload.bin and extract the recovery file and flash it in the bootloader and everything goes normal
Click to expand...
Click to collapse
Thanks I got back to the original boot, but now how can I root with Magisk?
@Rajveer chauhan
Hello sr
Have you updated your 9r for A12 ? If yes, how did you do it? Would it be possible to go from A11 (11.2.8.8) to A12 (C.33)?
Hi guys so Many users are facing issue while they are rooted and twrp installed on there phone.
They can't able to Flash update through stock settings OR via twrp if they tries to flash it via twrp manually facing no wifi and Bluetooth.
So here is the process to flash any incremental update via twrp just we need update zip, vbmeta image and boot image of old oos version respective to your new update means if. We are upgrading to V11 we need V10 boot img
U can use following commands to extract your current stock boot img after connecting to PC
adb shell
dd if=/dev/block/sdc49 of=/sdcard/boot.img
exit
Note: Remember this process will replace your twrp and removes root to gain root access. We need to repeat twrp installation shown in the following tutorial
TUTORIAL TWRP AND ROOT NORD 2 OXYGEN OS 11 ( Links updated!)
SO finally I successfully rooted with TWRP and root access.thanks to all developers @Eastw1ng @TheMalachite Following are all download links combined in one post Also there are two threads like unlocking boot loader and twrp but there are some...
forum.xda-developers.com
You can gain root acess only by flashing magisk.zip file after step no 7 given under instructions but I didn't tested it yet.
DOWNLOADS:
1)Download update v11 from Telegram :
®D$ in OnePlus Nord 2 Community
t.me
2) DOWNLOAD V13:
®D$ in OnePlus Nord 2 Community
t.me
3) Download V14 update zip:
️ in OnePlus Nord 2 Community
t.me
4) Download A15 update zip:
e9708c8610bae8fa64d76e0f9a55dda444ce981a.zip
drive.google.com
We can also download update in system update process. Just download OTA update and when we boot in twrp just click install and then go to following folder there you will find update.zip
/data/OTA-package/update.zip
5)A17 update zip:
https://t.me/OnePlusNord2GlobalOfficial/81364
Download vbmeta:
vbmeta.img | by TheMalachite for OnePlus Nord 2 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Download boot.img:
1) upgrade from v10 to v11(indian)
boot.img
drive.google.com
2) upgrade from v11 to v13(indian)
bootnew.img
drive.google.com
3)Upgrade from v13 to v14:
Rose in OnePlus Nord 2 Community
t.me
4)Upgrade from A14 to A15:
Rose in OnePlus Nord 2 Community
t.me
5)15 Boot img india (update from A15 to AA16)
https://t.me/OnePlusNord2GlobalOfficial/57795
5)A16 boot.img to upgrade to A17:
Rose in OnePlus Nord 2 Community
A16 stock boot image
t.me
6)17 BOOT IMG Upgrade to A18 (boot.img vbmeta zip extract file)
Rose in OnePlus Nord 2 Community
t.me
Boot img for nord 2 EU REGION :
File folder on MEGA
mega.nz
This another thread for all boot img of EU region
Stock Boot & Patched images Oneplus Nord 2 Oxygen 11.3 DN2103_11_A.07/09/10 EEA
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process! https://mega.nz/folder/fZx2nBaR#Q33lJstFRMQg6_0j7Z0TJw Special Thanks: @HofaTheRipper @phhusson
forum.xda-developers.com
Instructions :
1) Download all file from the link given under this thread place them at one place on your phone so it can be easily accessible when we boot in TWRP.
2)Now to boot in TWRP use following root acess app called as advance reboot. Open it and click reboot to recovery
Advanced Reboot Tools [ROOT] - Apps on Google Play
Provides lots of options for restarting your device; excellent for tweakers.
play.google.com
Or you can use adb command after connecting phone to pc in USB debugging mode.
adb reboot recovery
3) when phone boot in TWRP click install tab now go to folder where we placed All files.
4) click install image tab at bottom now you we see image files boot. img and vbmeta.img that we downloaded
5)now select boot.img and then select boot partation and slide bottom bar after successful installation
6)click reboot and select recovery phone will boots back to twrp( This step is optional)
7)Now again click Install and find our old folder now select update.zip file and slide bottom bar it will take 2min for complete falshing of zip.
8)now agian click install now click install image and select vbmeta.img
9)Now click reboot system phone will reboots and take 10min.
Now you are successfully updated and have new OOS 11.3 A11 version on your phone without any issues.
Follow the video:
New update v13 update process :
New update A14 update process:
New update A15:
New update A16:
New A18 update:
pankspoo said:
Hi guys so Many users are facing issue while they are rooted and twrp installed on there phone.
They can't able to Flash update via twrp if they tries to flash it via twrp manually facing no wifi and Bluetooth.
So here is the process to flash any incremental update via twrp just we need update zip, vbmeta image and boot image of old oos version respective to your new update means if. We are upgrading to V11 we need V10 boot img.
Follow the video:
Click to expand...
Click to collapse
good Instructions! Reboot after flashing boot.img isnt necessary. OTA Update zip can be downloaded within OTA App in Settings (do not press reboot). After downloading you can reboot to TWRP and the file location is: /data/OTA-package/update.zip.
HofaTheRipper said:
good Instructions! Reboot after flashing boot.img isnt necessary. OTA Update zip can be downloaded within OTA App in Settings (do not press reboot). After downloading you can reboot to TWRP and the file location is: /data/OTA-package/update.zip.
Click to expand...
Click to collapse
Yes but I don't want to go to automatic reboot and flashing process of OTA Update installation after download which may cause some issues for new users.
The old boot.img I image is the stock one not rooted right? How can you extract it from your firmware if you're not rooted? From the Nandroid backup maybe?
Edit, found out: https://forum.xda-developers.com/t/how-to-extract-your-boot-img-from-any-rom-adb.3760210/ Just had to google it
Don't wo
Raygen said:
The old boot.img I image is the stock one not rooted right? How can you extract it from your firmware if you're not rooted? From the Nandroid backup maybe?
Click to expand...
Click to collapse
Donts worry from here every new updates we will provide all stock boot. img
Thread updated for latest update v13 for India region
HI. This is my 1st OnePlus and OxygenOS. I am now on DN2103_11_A.11 and OTA is available. It is DN2103_11_A.12
Basically I can flash it from TWRP and I do not need to save and flash boot.img afterwards bec OS will be the same version. Is that so? Or am I wrong? And I have to follow threads instructions ?
Thank you
jis251 said:
HI. This is my 1st OnePlus and OxygenOS. I am now on DN2103_11_A.11 and OTA is available. It is DN2103_11_A.12
Basically I can flash it from TWRP and I do not need to save and flash boot.img afterwards bec OS will be the same version. Is that so? Or am I wrong? And I have to follow threads instructions ?
Thank you
Click to expand...
Click to collapse
NO u need A11 boot img of only DN 2103 firmware not indian I don't have that now first flash that then flash update zip of v12 then flash Vbmeta now that's done
pankspoo said:
NO u need A11 boot img of only DN 2103 firmware not indian I don't have that now first flash that then flash update zip of v12 then flash Vbmeta now that's done
Click to expand...
Click to collapse
HI. And thx for quick reply. I mange now, thank you.
DN2103 A.11 stock boot img :
HofaTheRipper said:
DN2103 A.11 stock boot img :
Click to expand...
Click to collapse
You got it do it now
HofaTheRipper said:
DN2103 A.11 stock boot img :
Click to expand...
Click to collapse
HI and thx. I have made TWRP backup, boot and vbmeta
So I can first restore boot then flash OTA and then restore vbmeta, yes? (Version 11)
I do not have to flash boot and vbmeta, restore does the same??
jis251 said:
HI and thx. I have made TWRP backup, boot and vbmeta
So I can first restore boot then flash OTA and then restore vbmeta, yes? (Version 11)
I do not have to flash boot and vbmeta, restore does the same??
Click to expand...
Click to collapse
Don't use backup boot image restore process.
Just download above boot image given
https://forum.xda-developers.com/attachments/boot_stock_a11-img.5461307/
and vbmeta image given in. My thread
vbmeta.img | by TheMalachite for OnePlus Nord 2 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
And u r update zip of device of your region not mine
First flash boot img then. Install update zip then. Flash Vbmeta done
pankspoo said:
Don't use backup boot image restore process.
Just download above boot image given
https://forum.xda-developers.com/attachments/boot_stock_a11-img.5461307/
and vbmeta image given in. My thread
vbmeta.img | by TheMalachite for OnePlus Nord 2 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
And u r update zip of device of your region not mine
First flash boot img then. Install update zip then. Flash Vbmeta done
Click to expand...
Click to collapse
Thx. OK I do that.
Magisk is installed (patched) to boot image so after OTA and Vbmeta I flash Magisk to keep root.
jis251 said:
Thx. OK I do that.
Magisk is installed (patched) to boot image so after OTA and Vbmeta I flash Magisk to keep root.
Click to expand...
Click to collapse
Yes
pankspoo said:
Download boot.img:
1) upgrade from v10 to v11(indian)
boot.img
drive.google.com
2) upgrade from v11 to v13(indian)
bootnew.img
drive.google.com
Click to expand...
Click to collapse
Do the boot.img files in the original post only work on the Indian variant? Where can I get the A11 boot.img for the European variant if I want to update to A12?
NetSoerfer said:
Do the boot.img files in the original post only work on the Indian variant? Where can I get the A11 boot.img for the European variant if I want to update to A12?
Click to expand...
Click to collapse
Ok I will upload in thread
NetSoerfer said:
Do the boot.img files in the original post only work on the Indian variant? Where can I get the A11 boot.img for the European variant if I want to update to A12?
Click to expand...
Click to collapse
File folder on MEGA
mega.nz
Use boot images from stock folder
pankspoo said:
U can use following commands to extract your current stock boot img after connecting to PC
adb shell
dd if=/dev/block/sdc49 of=/sdcard/boot.img
exit
Click to expand...
Click to collapse
Still trying to wrap my head around this (although updating worked fine from A11 to A12 on my EEA variant, thanks @pankspoo!).
Can I actually extract a stock boot.img from a Magisk-rooted phone? Is it stock (in which case why is root removed by the update.zip) or is it modified (in which case, why can I extract it as stock)?
NetSoerfer said:
Still trying to wrap my head around this (although updating worked fine from A11 to A12 on my EEA variant, thanks @pankspoo!).
Can I actually extract a stock boot.img from a Magisk-rooted phone? Is it stock (in which case why is root removed by the update.zip) or is it modified (in which case, why can I extract it as stock)?
Click to expand...
Click to collapse
You can use those adb commands while booted in TWRP, without being rooted. So you'll extract the stock boot image