Hello guys, I have few questions and hopefully someone can answer them.
I am trying to root my mate 10 pro with version:
BLA-L29 8.0.0.127(C432)
I want to root it with magisk and since twrp is not available yet,
is it possible to root by patching the boot image?
If it is possible, how do I extract the boot image without root?
This is what i found online.
Method 2: Patching Stock Boot Image
This method doesn’t require you to have TWRP in order to install Magisk 15.0 update.
1. Download the latest Magisk Manager APK: MagiskManager-v5.5.1.apk
2. Use a file manager to install the downloaded app on your device.
3. Grab the stock boot image (kernel) and it should be corresponding to the firmware installed on your device.
For Nexus and Pixel devices, you can extract it from the factory image. For other OEM devices, you might need to check it with your manufacturer’s support.
4. Copy the downloaded “boot.img” to the internal storage of your Android device.
5.Open the Magisk Manager app and tap on the ‘Install’ button.
6. Again, choose ‘Install’ and then ‘Patch Boot Image File’.
7. Navigate to the storage and select the ‘boot.img’ file you just transferred.
8. The Magisk Manager app will patch the stock boot image and place the resultant ‘patched_boot.img’ in the ‘MagiskManager’ folder.
9. Transfer the file from your phone to C:\adb folder on your PC.
10. Hold the SHIFT key on your PC and right-click on an empty space inside the folder. Then select ‘Open PowerShell window here’ from the menu.
11. Boot your Android into Fastboot mode and connect it to the PC.
Enter the following command to root your Android phone using Magisk 15.0 update:
fastboot flash boot patched_boot.img
Finally, reboot your device.
fastboot reboot
I have tried this method and got a boot loop... Don't try this if you don't know what you do
with some ressources in others threads you can download the firmware, unpack it and try to patch this with magisk. But if you don't know how to do that, you shouldn't do that
Read these scripts to learn how flash works with mate 10 => https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Dagda-Esus said:
I have tried this method and got a boot loop... Don't try this if you don't know what you do
with some ressources in others threads you can download the firmware, unpack it and try to patch this with magisk. But if you don't know how to do that, you shouldn't do that
Read these scripts to learn how flash works with mate 10 => https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Click to expand...
Click to collapse
Did you get the boot.img file ? or did you do it in another way ?
I'm interested in this as well...
I have downloaded full OTAs, but there is no boot.img? I have tried the above method with the ramdisk.img since it's usually part of the boot.img, but I get bootloop.
trackloading said:
I'm interested in this as well...
I have downloaded full OTAs, but there is no boot.img? I have tried the above method with the ramdisk.img since it's usually part of the boot.img, but I get bootloop.
Click to expand...
Click to collapse
ramdisk.img is correct. boot.img is ramdisk and kernel combined, but as of Oreo it's now ramdisk.img and kernel.img.
So patching ramdisk.img is the way to go?
yfaykya said:
So patching ramdisk.img is the way to go?
Click to expand...
Click to collapse
Loop device support is not available yet, so Magisk can't be installed (System less only). The only option is Supersu.
Edit: Magisk can be installed, but it ends in a bootloop (Actually just a reboot before boot animation starts).
So it's not loop support that's wrong, because I've tested now and it does work.
My devices is Huawei Honor V10 with Emui 8.0 (OREO), I can't find the stock boot.img by extracting the official full OTA update.app.
I got the stock boot.img from a third party rom for V10 (Kangvip mod rom for v10 B122) , and patched it in Magisk manager.
I use ' fastboot flash ramdisk patched_boot.img ' to flash the pathed boot. And i got boot loop...
There's isn't a custom recovery for V10, so i can't flash supersu.
Anyone got a solution for this?
dawnc said:
My devices is Huawei Honor V10 with Emui 8.0 (OREO), I can't find the stock boot.img by extracting the official full OTA update.app.
I got the stock boot.img from a third party rom for V10 (Kangvip mod rom for v10 B122) , and patched it in Magisk manager.
I use ' fastboot flash ramdisk patched_boot.img ' to flash the pathed boot. And i got boot loop...
There's isn't a custom recovery for V10, so i can't flash supersu.
Anyone got a solution for this?
Click to expand...
Click to collapse
Do you know your model number?
Like
xxx-CxxxBxxx
ante0 said:
Loop device support is not available yet, so Magisk can't be installed (System less only). The only option is Supersu.
Edit: Magisk can be installed, but it ends in a bootloop (Actually just a reboot before boot animation starts).
So it's not loop support that's wrong, because I've tested now and it does work.
Click to expand...
Click to collapse
Did you get magisk working ?
lisa99 said:
Did you get magisk working ?
Click to expand...
Click to collapse
Nope. Magisk replaces original INIT in ramdisk, that makes it reboot after the "Your device is unlocked" screen.
I'm trying some other things.
I read that newer devices might actually read initramfs from recovery rather than ramdisk (boot) so I'm trying that out now...
ante0 said:
Loop device support is not available yet, so Magisk can't be installed (System less only). The only option is Supersu.
Edit: Magisk can be installed, but it ends in a bootloop (Actually just a reboot before boot animation starts).
So it's not loop support that's wrong, because I've tested now and it does work.
Click to expand...
Click to collapse
ante0 said:
Nope. Magisk replaces original INIT in ramdisk, that makes it reboot after the Your devices is unlocked screen.
I'm trying some other things.
I read that newer devices might actually read initramfs from recovery rather than ramdisk (boot) so I'm trying that out now...
Click to expand...
Click to collapse
let me know if you figure something out.
ante0 said:
do you know your model number?
Like
xxx-cxxxbxxx
Click to expand...
Click to collapse
bkl-al20c00
dawnc said:
bkl-al20c00
Click to expand...
Click to collapse
You seem to have fixed it already?
ante0 said:
You seem to have fixed it already?
Click to expand...
Click to collapse
I've made a boot.img with supersu inside.
But can't fix magisk root
dawnc said:
I've made a boot.img with supersu inside.
But can't fix magisk root
Click to expand...
Click to collapse
Nope. I've tested a lot.
First you need extract magisk zip then open common/util_functions.sh and edit
BOOTIMAGE=`find /dev/block -iname boot$SLOT | head -n 1` 2>/dev/null
to
BOOTIMAGE=`find /dev/block -iname ramdisk$SLOT | head -n 1` 2>/dev/null
save and repack.
But I'm pretty sure it's because of the INIT it places in RAMDISK...
You have to modify kernel too, because RAMDISK contains an empty kernel and it applies the hexpatch to RAMDISK instead of the real KERNEL.
But either way it ends in a boot loop. And before logcat can start so no logs either... :/
ante0 said:
Nope. I've tested a lot.
First you need extract magisk zip then open common/util_functions.sh and edit
BOOTIMAGE=`find /dev/block -iname boot$SLOT | head -n 1` 2>/dev/null
to
BOOTIMAGE=`find /dev/block -iname ramdisk$SLOT | head -n 1` 2>/dev/null
save and repack.
But I'm pretty sure it's because of the INIT it places in RAMDISK...
You have to modify kernel too, because RAMDISK contains an empty kernel and it applies the hexpatch to RAMDISK instead of the real KERNEL.
But either way it ends in a boot loop. And before logcat can start so no logs either... :/
Click to expand...
Click to collapse
Have u found a way to make magisk work?
dawnc said:
Have u found a way to make magisk work?
Click to expand...
Click to collapse
It might be because loop is not fully working.
But no, haven't found any way.
@ante0 Have you tested both flashing patched ramdisk.img and patched recovery_ramdisk.img ? Will this make magisk work?
dawnc said:
@ante0 Have you tested both flashing patched ramdisk.img and patched recovery_ramdisk.img ? Will this make magisk work?
Click to expand...
Click to collapse
Not both at once no.
Related
Thanks to serajr here - https://forum.xda-developers.com/showpost.php?p=75505302&postcount=2973 Go directly to that post and give thanks.
You need:
Stock O ftf (best to use Flashtool/Xperifirm)
Modded boot img for 34.4.A.2.19 - https://mega.nz/#!AgtQ2Sob!JjLRcUVjuy6FNanjGY49g-YYmkcda04witfHp4hwvmo
Modded boot img for 34.4.A.2.32 - https://mega.nz/#!Z1tzEJbZ!e9ET_RtUpKjXRwnJa_TDsMrVwvT-hPxmk06KtryHOuc
Modded boot img for 34.4.A.2.85 - https://mega.nz/#!p5UwAabR!_ofmr_WdId9RdH48Xb3cZtSIzsQ6qcTJTAFYcKHFWJE
Kernel elf file to use with rootkernel [34.4.A.2.85] - https://mega.nz/#!M102lYTZ!9bj2KE-vbNWlej3Dw0NuiXJcfpgiy16svSHud73bLfw
Modded boot img for 34.4.A.2.107 - https://mega.nz/#!Nls0EQBR!Cc4lVcA85f8YeNTo8nMqsuwLzveW5duSbyeZDlI5kDE
Kernel elf file to use with rootkernel [34.4.A.2.107] - https://mega.nz/#!Zp10CASK!iGLE94Tj1SSk1U2p4KLpVrcGmD68C3YvqKMXD6VPFjI
Modded boot img for 34.4.A.2.118 - https://mega.nz/#!14VkzCCB!GK-KEv0A-ZyhysXc1-IusyJjJEB-D5ZWOLm1DRt31tA
Kernel elf file to use with rootkernel [34.3.A.2.118] - https://mega.nz/#!Ylcm1SwA!GuX9dfd2HAqLXy1jom-C6mgP0s4jYXl9qSySkvb_mtA
TWRP - https://forum.xda-developers.com/x-compact/development/ub-twrp-v3-2-1-xperia-x-compact-t3793837
1. Flash stock ftf from Xperifirm via Flashtool
2. After flash, connect in fastboot (before booting phone) and type in command line 'fastboot flash boot boot.img' (this assumes that your modified boot img is in the current directory,and is named 'boot.img'; otherwise, you need to edit the command accordingl)
3. Then type 'fastboot flash recovery twrp-3.2.1.img' (same note as above)
Done
Now, you can flash Magisk, (or whatever), and have root access.
If you want Drm fix, flash serajr's zip here - https://forum.xda-developers.com/attachment.php?attachmentid=4404527&d=1517335127
If you want to restore your own ta with munjeni tool, you will need to patch boot img yourself with rootkernel tool here - https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
How to get stock kernel elf and patch your boot img with rootkernel:
1. Download and build stock ftf from Xperifirm via Flashtool
2. Go to Flashtool > tools > sin editor, and navigate to stock kernel sin file, in the downloaded firmware folder. Click on sin file and choose 'exrract data', and it will create a kernel elf.
3. Follow the guide by serajr. You need only to put the kernel elf into rootkernel folder, then open a command prompt there and run 'rootkernel kernel.elf boot.img'. Answer all questions 'yes', unless you want to skip drm fix and restore your own ta, (if that's the case, you need your target file in that folder renamed to TA.img). After script runs, you will have a new boot img that you can use to follow the guide.
Done...
Magisk, MicroG, and Xposed tested... (update - I haven't tried yet, but I've read that Xposed not working on ...85; update 2 - confirmed, bootloop; update 3 - Xposed fix now available here - https://forum.xda-developers.com/x-compact/themes/xposed-fix-118-t3870673)
I made a patched boot img with rootkernel tool and uploaded it. Link in op. Don't forget to thank serajr...
Can confirm the above method worked for me. I used the TA.img instead of drm fix, and i get root and security test still have widefine and fidokeys enabled.
Just slight reminder for linux user, you need to add execute permission on both `rootkernel` and `bootimg`, otherwise rootkernel tool will fail with permission issue.
levone1 said:
I made a patched boot img with rootkernel tool and uploaded it. Link in op. Don't forget to thank serajr...
Click to expand...
Click to collapse
With which options is your modified boot image prepared?
maluus said:
With which options is your modified boot image prepared?
Click to expand...
Click to collapse
Dm-verity disable - yes
Force encrypt disable - yes
Drm fix - yes
For Drm fix you still have to flash serajr zip. If you want to restore ta with munjeni tool, you will need to patch boot yourself.
Op updated for 3-click root...
SuperSU,Xposed
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Arsis said:
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Click to expand...
Click to collapse
...
Arsis said:
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Click to expand...
Click to collapse
Boot img just enables modification by disabling Sony security stuff, but you still need to flash whatever mod you want. So after flashing boot and recovery img, then flash supersu (or whatever), and you should have root.
I can't say about drm fix, since I've never used it before, but I don't think it will show fido provisioned, etc, because it simply recreates the drm functions through a different method, (not with ta).
I was able :laugh::good: Xposed release link
levone1 said:
Boot img just enables modification by disabling Sony security stuff, but you still need to flash whatever mod you want. So after flashing boot and recovery img, then flash supersu (or whatever), and you should have root.
I can't say about drm fix, since I've never used it before, but I don't think it will show fido provisioned, etc, because it simply recreates the drm functions through a different method, (not with ta).
Click to expand...
Click to collapse
Oh, well. Thank you! It's working now.
Hello,
i flashed on my sony with oreo this boot.img and twrp and im stuck on sony logo. Any ideas what could be wrong? I tried android 34.4.A.0.364 singapure and UK versions and neither of these works with this twrp.
I have the newest platform-tools and flashing went well.
Thanks
Stephenhs said:
Hello,
i flashed on my sony with oreo this boot.img and twrp and im stuck on sony logo. Any ideas what could be wrong? I tried android 34.4.A.0.364 singapure and UK versions and neither of these works with this twrp.
I have the newest platform-tools and flashing went well.
Thanks
Click to expand...
Click to collapse
Can you try running the tool and creating the boot.img yourself? I use the singapore ftf and doesn't have problem booting the system (with the boot img I created myself). I do not put twrp on boot img though. I boot twrp from fastboot when needed
I created boot.img and everything works Thanks a lot!
I dont understang the part that says :
Android Oreo ramdisk patching needs some additional files, and they must be copied from Oreo /system into the rootkernel's filesystem_files folder, prior to run the script, and they are:
Code:
/system/vendor/etc/fstab.qcom
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/init/hw/init.target.rc
(you can pull these files through adb, or even converting system.sin to system.ext4 and take them out from there - just copy them, and DO NOT touch its contents)
how to do that!? im noob...
Kianush said:
I dont understang the part that says :
Android Oreo ramdisk patching needs some additional files, and they must be copied from Oreo /system into the rootkernel's filesystem_files folder, prior to run the script, and they are:
Code:
/system/vendor/etc/fstab.qcom
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/init/hw/init.target.rc
(you can pull these files through adb, or even converting system.sin to system.ext4 and take them out from there - just copy them, and DO NOT touch its contents)
how to do that!? im noob...
Click to expand...
Click to collapse
Post linked in op has special instructions for us with Xc - skip that part.
https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
hello guys, i've created a boot.img whit the tool of rootkernel whit my ta.backup but it does not work. the boot it's ok but if i chek my drm keys they say not provisioned. my ta.backup load 2.097.152 byte like the post shows. can someone help me? thanks
update:
sorry guys, i've done again the kernel patch whit my ta backup and this time goes perfect. i don't know why the first time didn't work but now it's ok!
I tried the 3 click method, without doing any boot image myself, but impossible to decrypt with TWRP (or reboot to system).
Wxfdswxc said:
I tried the 3 click method, without doing any boot image myself, but impossible to decrypt with TWRP (or reboot to system).
Click to expand...
Click to collapse
Twrp - https://forum.xda-developers.com/x-compact/development/twrp-3-2-1-decryption-t3751998
As for rebooting to system, can't say for sure... Root method involves only changing boot img, so shouldn't affect system. Any errors in fastboot, etc?
Original flash should be clean flash official stock ftf from Xperifirm. First boot could be 10 minutes...
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
Hi,
I just updated to 10.0.9.HD01BA on my OP7T Pro and after that I tried to root it with Magisk by patching the OTA update.
This didn't work and it was stuck at the boot animation, so I extracted the boot.img and patched it with Magisk.
But with the patched version I'm also always stuck at the boot animation.
If I flash the original boot.img again, everything is fine, except that there is no root of course.
I already rooted many OP7 and OP7T and never got this result.
Is Magisk currently not supporting 10.0.9, or am I doing something wrong?
I really don't know what else I could do.
Is someone else experiencing this issue?
Catter38 said:
Hi,
I just updated to 10.0.9.HD01BA on my OP7T Pro and after that I tried to root it with Magisk by patching the OTA update.
This didn't work and it was stuck at the boot animation, so I extracted the boot.img and patched it with Magisk.
But with the patched version I'm also always stuck at the boot animation.
If I flash the original boot.img again, everything is fine, except that there is no root of course.
I already rooted many OP7 and OP7T and never got this result.
Is Magisk currently not supporting 10.0.9, or am I doing something wrong?
I really don't know what else I could do.
Is someone else experiencing this issue?
Click to expand...
Click to collapse
Did you disable and delete all Magisk modules before updating to OOS 10.0.9? If not, do the following:
- Boot your phone and enable ADB debugging in dev settings.
- Flash the patched Magisk boot.img.
- During boot connect your device to a PC and enter:
"adb wait-for-device shell magisk --remove-modules"
- Your device should reboot without any modules and you can install them again.
Macusercom said:
Did you disable and delete all Magisk modules before updating to OOS 10.0.9? If not, do the following:
- Boot your phone and enable ADB debugging in dev settings.
- Flash the patched Magisk boot.img.
- During boot connect your device to a PC and enter:
"adb wait-for-device shell magisk --remove-modules"
- Your device should reboot without any modules and you can install them again.
Click to expand...
Click to collapse
Unfortunately, I forgot to uninstall the modules.
I tried the adb command and the device reboots, but it's still in the same bootloop.
I also tried to uninstall the modules with TWRP, but since there isn't a fully working version for the OP7T Pro, this also didn't work.
What's weird is, that the magisk patched version of the boot.img always results in a way smaller file than the original.
The original file is ~100mb, while the patched version is ~40mb.
I don't know if this is normal, but it seems odd.
I also tried it with the canary version of magisk, which results in the same small boot.img.
Looks like I have to stay unrooted until this is fixed.
Ok, finally I got it to work.
Since my girlfriend also has a OP7T Pro and still is on 10.0.8 with root, I simply took her boot image and booted it with fastboot. This also resulted in the same bootloop, but now the adb command worked and I was able to boot a rooted 10.0.8 boot.img. Now I was able to use the direct install of magisk and patched the 10.0.9 installation with it.
I think my problem was, that I did't remove the modules in the first place, which screwed up the whole update.
I still can't explain why I wasn't able to patch the boot.img with magisk. It didn't work on my phone with the canary build of magisk, neither did it work on the phone of my girlfriend with magisk 20.4.
Anyway. Now I have a working 10.0.9 boot.img and can safely upgrade my girlfriends phone too.
Thanks for the help!
https://app.box.com/s/9r77wcvk2dnbos87rpr1lfcnmnd091le
Here is.... HD10.0.9BA Patched and the original boot.img..... ?
kovacsabesz said:
https://app.box.com/s/9r77wcvk2dnbos87rpr1lfcnmnd091le
Here is.... Last build... Patched and the original img..... ?
Click to expand...
Click to collapse
Interesting, your patched image also is way smaller than the original.
Did you verify, that it's working?
https://app.box.com/s/at1mhbvpkspg4wfzp16cqppgdvvidese
I'm using it now.... Without problem
Catter38 said:
Interesting, your patched image also is way smaller than the original.
Did you verify, that it's working?
Click to expand...
Click to collapse
It seems to be normal. I'm not sure why but it might be due to compression. Anyway, glad you figured it out.
Catter38 said:
Interesting, your patched image also is way smaller than the original.
Did you verify, that it's working?
Click to expand...
Click to collapse
kovacsabesz said:
https://app.box.com/s/9r77wcvk2dnbos87rpr1lfcnmnd091le
Here is.... HD10.0.9BA Patched and the original boot.img.....
Click to expand...
Click to collapse
Would you mind uploading the files again if you can? I'm struggling with my device being in bootloop and I can't remove the module causing it bc I can't access adb with the bootloop. With the stock boot img I'm hoping to boot the device again and remove the bad module via adb
Macusercom said:
Did you disable and delete all Magisk modules before updating to OOS 10.0.9? If not, do the following:
- Boot your phone and enable ADB debugging in dev settings.
- Flash the patched Magisk boot.img.
- During boot connect your device to a PC and enter:
"adb wait-for-device shell magisk --remove-modules"
- Your device should reboot without any modules and you can install them again.
Click to expand...
Click to collapse
Im im a similar situation now, is there a way before removing the modules all i can backup them or atleast access a file or something with the modules names ?
kovacsabesz: can you please reupload the file? Thanks
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.