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
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
Last updated May 2020
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Objectives :
Have root using Magisk
Be able to install OTA from the settings without bootloops
Avoid boot loop
Very important :
This will work with ANY Xiaomi phone, and should work with ANY ANDROID phone as well. The difference between phones would be in where you can get your boot image from.
Your phone has to have an unlocked bootloader
Your phone has to have stock recovery. TWRP WILL cause bootloop for root and/or OTA updates from system.
I like to have root with magisk and don't want to install TWRP because I want to be able to install OTA from system without boot loops. This guide will help you achieve this with ease.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
https://youtu.be/KsxHial1v1U
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
https://youtu.be/USHcCMYlexM
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
fastboot reboot
Click to expand...
Click to collapse
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Update May 2020
Hello again,
Sorry for being away for so long. Here are some of the things I have noticed people are confused with and need to make them clear:
This method works for ANY Android phone. As long as you have the Correct boot.img and can unlock the bootloader
MAKE SURE 100% you have the correct boot.img file for your CURRENT ROM
MAKE 100% SURE, the boot.img file you get from the FULL ROM zip file, not an OTA update zip file
Make sure you check the date and time of the "magisk_patched.img" file to make sure that is the one you made
Make sure you use the LATEST magisk manager
Make sure you open magisk after flashing the magisk_patched.img as boot image. Magisk manager will tell you if there is another step needed, just click yes and it will be done in seconds
Make sure to enable "Hide Magisk" to allow you to have your BANK apps working as well as security checks
If any app you use gives you an error "YOU ARE Rooted bla bla bla" Use magisk manager to hide the root for this specific app (in the settings)
That's all I can remember, good luck
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kiwironic said:
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Click to expand...
Click to collapse
After fastboot flash, reboot, open magisk manager, tap INSTALL beside "magisk is up to date". Then select direct install; reboot.
Works on MIUI 11.0.2; davinciin. ??
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
People report different amounts of wait time, depends on the mi account I think
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Can do with locked bootloader?
Micdu70 said:
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Click to expand...
Click to collapse
Thank you man :good:
Sent from my Xiaomi Mi 9T using XDA Labs
Cabeção-Flu said:
Can do with locked bootloader?
Click to expand...
Click to collapse
No, bootloader has to be unlocked.
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Lazer Bear said:
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Click to expand...
Click to collapse
I had root on MIUI10 and updated the ROM to MIUI11 then did my root again the way mentioned and did NOT have to wipe. You can get OTA anyway, it will try the update first, it will fail, then it download and install a full ROM zip automatically. You have to wait for it to do that twice, that's all. The first boot after the update takes some time.
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
kryzeK said:
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
Click to expand...
Click to collapse
If you flash the full rom, chances of bootloop is minimal. And should have stock experience except for being unlocked.
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
stone_henge said:
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
Click to expand...
Click to collapse
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
oblyvision said:
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
Click to expand...
Click to collapse
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Kiwironic said:
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Click to expand...
Click to collapse
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
On first installation MM asks to download what it needs e.g. to verify SafetyNet. Allow and there is no problem about. TWRP is generally not needed to install Magisk. Things are documented in Magisk guides
https://topjohnwu.github.io/Magisk/
https://www.didgeridoohan.com/magisk/HomePage
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Kiwironic said:
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Click to expand...
Click to collapse
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
oblyvision said:
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
Click to expand...
Click to collapse
You have to understand the requirements :
- stock recovery
- install magisk manager app
- patch the boot image for your stock ROM (same version on your phone)
- flash that Patched boot image.
- reboot
- done, that's magisk installed
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.
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)?
Hello everyone hope you are all keeping well.
Since I believe that many of you don't know about this, I've decided to share the steps I've done in order to root the OP 11R ( ACE 2 )
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!
1 - Unlock the bootloader (if you haven't done it already...beware that this will erase all of your user data). To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
adb devices
adb reboot bootloader
(so your phone will reboot into fastboot mode)
fastboot flashing unlock
(device should now unlock)
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped so set up the device from scratch again)
2 - Download OP 11R stock boot.img that you may find later on this post, that matches your current build.
Copy the boot.img to your devices internal memory
Leave a copy of it on your PC (on the same folder you have adb and fastboot...you never know if you will need to use it again in the future...to restore the stock boot.img, aka revert to stock...)
Indian Boot.img A_0.8 - download
3 - Download latest Magisk Manager from HERE and install it on your phone
4 - Open Magisk Manager App and press:
Install
Select and Patch a File
Browse to the path where you saved stock boot.img and select it
Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img
5 - Copy the patched boot image from your device to your PC (Store it on the same folder where you have adb and fastboot)
6 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
7 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!
8 - Enjoy!
All credits goes to topjohnwu and his incredible work with Magisk.
Why title says NORD 2T?
firoz3321 said:
Why title says NORD 2T?
Click to expand...
Click to collapse
MB ... typo
Thank you for detailed steps.
Is there any benefit with KernelSU over this method ?
I always used Magisk on OP8, but recently saw an article for OP11 with Kernel SU.
Also is there MSM tool support to recover softbriked device ?
firoz3321 said:
Thank you for detailed steps.
Is there any benefit with KernelSU over this method ?
I always used Magisk on OP8, but recently saw an article for OP11 with Kernel SU.
Also is there MSM tool support to recover softbriked device ?
Click to expand...
Click to collapse
Sorry but there is no msm tool available for new OnePlus devices. + You can use Fastboot enhance tool from github to recover softbrick , magisk is always recommended for rooting because of ease of steps and simple to use
Hello, thanks for the detailed instructions. Today I updated to A. 10, and unfortunately lost my root access. Without the root cannot extract the boot image. If you're already updated and have a backup of A. 10 boot, can you please share?
saifsohel said:
Hello, thanks for the detailed instructions. Today I updated to A. 10, and unfortunately lost my root access. Without the root cannot extract the boot image. If you're already updated and have a backup of A. 10 boot, can you please share?
Click to expand...
Click to collapse
i didn't got the update yet ... + oxygen updater also showing A.08. i will update this post soon as I got update
shiki_senpai said:
i didn't got the update yet ... + oxygen updater also showing A.08. i will update this post soon as I got update
Click to expand...
Click to collapse
Then remember to take a backup of the boot before rebooting. I messed up big time.
Thanks for the detailed information man. Can I know if bootloader unlock decreases widevine L1 to L3? As this was case with my OP6