Hey guys,
here is just a short guide on how to root EMUI9 with the newest Magisk 18.1 canary builds just release by John Wu.
This is not my work! All credits for this go to John Wu, the developer of Magisk.
You can try this of your own risk. I'm not responsible for any damage.
NOTE:
With the new Magisk, John Wu remapped the restart button in the standard power menu, so when you reboot with that button, you'll always reboot with root.
The power button works as normal.
You can revert to the stock recovery or an TWRP recovery at any time but without root.
- Download the TWRP app from Google PlayStore and install it.
- Go to the TWRP app and download the lastest twrp image for P20 Pro.
- Downlod one of the Magisk apk's from here and install it.
- Open the Magisk app, go to settings, put the update channel to manual and insert one of the links shown ontop of this page.
- Go back to the first page of Magisk, refresh it and make sure to install the lastet magisk apk. Open it again.
- You'll get asked to download and install the lastest Magist.zip. Do this and choose to patch only the boot.img. Choose the TWRP.img you've downloaded before.
- Plugin you device to a PC and download the patched img to your PC. Now reboot to fastboot mode and flash the patched img with "fastboot flash recovery_ramdisk patched_image.img"
- Now unplug your device and shut it down. Reboot it with holding vol-up button. Now it should boot fine with working root.
Have fun and thank you John Wu for your great work!
Not working
It's working for me. Finally have a root for EMUI 9
Do not use TWRP.img for patching,
use RECOVERY_RAMDISK instead
or simply download pre_patched one from here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
delete
works great
otonieru said:
Do not use TWRP.img for patching,
use RECOVERY_RAMDISK instead
or simply download pre_patched one from here : LINk2PATCH
Click to expand...
Click to collapse
I'm strongly thinking about getting the P20 Pro tomorrow
But I really want it to be able to run with Magisk and its wonderful modules.
So a quick question, or two:
1) That patched_boot.img - do I use fastboot and then Flash Ramdisk? Any other requirements out of the box? Do I have to unlock the bootloader (noob question).
2) Is it only for EMUI 9.0? Do I get this version by the official updater?
Best regards
ZHARQ said:
I'm strongly thinking about getting the P20 Pro tomorrow
But I really want it to be able to run with Magisk and its wonderful modules.
So a quick question, or two:
1) That patched_boot.img - do I use fastboot and then Flash Ramdisk? Any other requirements out of the box? Do I have to unlock the bootloader (noob question).
2) Is it only for EMUI 9.0? Do I get this version by the official updater?
Best regards
Click to expand...
Click to collapse
I think you'll need an unlocked bootloader and if your phone is new and locked you'll struggle obtaining root on any version of EMUI as it requires an unlocked bootloader. I believe there are paid services for that.
CaseyS said:
I think you'll need an unlocked bootloader and if your phone is new and locked you'll struggle obtaining root on any version of EMUI as it requires an unlocked bootloader. I believe there are paid services for that.
Click to expand...
Click to collapse
Just ordered it
Okay, so if I'm on 8.1 when I receive it - shall I try to unlock the Bootloader first or update to 9.0?
Thank you for your quick reply!
ZHARQ said:
Just ordered it
Okay, so if I'm on 8.1 when I receive it - shall I try to unlock the Bootloader first or update to 9.0?
Thank you for your quick reply!
Click to expand...
Click to collapse
I think you'll need to unlock bootloader before unless you receive the EMUI 9 update. But you may still need an unlocked bootloader. Better docrhst before you proceed. This is only coming from somone with an unlocked bootloader so I'm not sure if it's possible without.
ZHARQ said:
Just ordered it
Okay, so if I'm on 8.1 when I receive it - shall I try to unlock the Bootloader first or update to 9.0?
Thank you for your quick reply!
Click to expand...
Click to collapse
It almost certainly will come with 8.1
They've been boxed for sometime now
ZHARQ said:
I'm strongly thinking about getting the P20 Pro tomorrow
But I really want it to be able to run with Magisk and its wonderful modules.
So a quick question, or two:
1) That patched_boot.img - do I use fastboot and then Flash Ramdisk? Any other requirements out of the box? Do I have to unlock the bootloader (noob question).
2) Is it only for EMUI 9.0? Do I get this version by the official updater?
Best regards
Click to expand...
Click to collapse
That patched image file is only for EMUI 9,
and you need to flash it to recovery_ramdisk partition, not ramdisk. There's no longer ramdisk in EMUI 9. This is the exact reason for our trouble acquiring root, until topjohnwu, again, come as life saver, LoL
but if you decide to root on oreo and not upgrading, then you can simply use TWRP to flash Magisk.zip just like how you did with other phone.
for both, Unlocked Bootloader is a MUST. Unlock yours when you are still on 8.1. You gonna need to pay for the unlock code though. Keep your code safely in case you need it in the future.
otonieru said:
That patched image file is only for EMUI 9,
and you need to flash it to recovery_ramdisk partition, not ramdisk. There's no longer ramdisk in EMUI 9. This is the exact reason for our trouble acquiring root, until topjohnwu, again, come as life saver, LoL
but if you decide to root on oreo and not upgrading, then you can simply use TWRP to flash Magisk.zip just like how you did with other phone.
for both, Unlocked Bootloader is a MUST. Unlock yours when you are still on 8.1. You gonna need to pay for the unlock code though. Keep your code safely in case you need it in the future.
Click to expand...
Click to collapse
Thanks for clarifying that!
So I start with unlocking the bootloader (funkyhuawei .club/ buycodes - $55 )
Then see if there's an official upgrade to EMUI 9 available,
if not I will flash it myself(?),
then flash this premade patched_boot.img to recovery_ramdisk.
Another nooby question, what is it exactly that's changed on this .img?
Thanks!
ArtaxXP said:
NOTE: YOU HAVE NO MORE RECOVERY AFTER THIS AND YOU HAVE TO ALWAYS REBOOT WITH HOLDING VOL-UP BOTTON. (reboot to recovery)
Click to expand...
Click to collapse
Are you saying the power button (restart/power off) no longer works? That's weird!
What about apps that provide an advanced power menu/ reboot widgets etc?
How do we unroot/revert to stock (for future OTA purposes)? Should we be backing up our boot img? If so, how?
otonieru said:
Do not use TWRP.img for patching,
use RECOVERY_RAMDISK instead
or simply download pre_patched one from here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
Click to expand...
Click to collapse
So basically, just install Magisk apk and flash your patched boot img with "fastboot flash recovery_ramdisk patched_boot.img"?
colthekid said:
Are you saying the power button (restart/power off) no longer works? That's weird!
What about apps that provide an advanced power menu/ reboot widgets etc?
How do we unroot/revert to stock (for future OTA purposes)? Should we be backing up our boot img? If so, how?
So basically, just install Magisk apk and flash your patched boot img with "fastboot flash recovery_ramdisk patched_boot.img"?
Click to expand...
Click to collapse
I'm not certain that the patched_boot.img is the same as the one the way the topic author mentions (I can be wrong though).
Would be nice to know exactly what it's already patched with.. Magisk maybe?
colthekid said:
Are you saying the power button (restart/power off) no longer works? That's weird!
What about apps that provide an advanced power menu/ reboot widgets etc?
How do we unroot/revert to stock (for future OTA purposes)? Should we be backing up our boot img? If so, how?
So basically, just install Magisk apk and flash your patched boot img with "fastboot flash recovery_ramdisk patched_boot.img"?
Click to expand...
Click to collapse
Forget, what I told you in the first post. With the new Magisk, John Wu remapped the restart button in the standard power menue, so when you reboot with that button, you'll always reboot with root. The power button works as normal.
And for your second question:
Yeah, basically, that's it.
If you need to go back to stock, you need to extract the recovery ramdisk image from the original firmware, downloaded for example with Huawei Firmware Finder or maybe someone can provide the stock image.
ArtaxXP said:
Forget, what I told you in the first post. With the new Magisk, John Wu remapped the restart button in the standard power menue, so when you reboot with that button, you'll always reboot with root. The power button works as normal.
And for your second question:
Yeah, basically, that's it.
If you need to go back to stock, you need to extract the recovery ramdisk image from the original firmware, downloaded for example with Huawei Firmware Finder or maybe someone can provide the stock image.
Click to expand...
Click to collapse
Excellent, nice and simple that's what we like!!
Interesting way of doing it though, it's effectively booting from the recovery partition rather than the normal boot partition...hence no TWRP! I presume you could swap between rooted and stock that way...would help with those apps that even Magisk can't hide root from...would almost not want the remapping of the power button if it allowed you to swap between the two states (i.e. reboot from power button takes you to stock, reboot via up vol makes you rooted!)
colthekid said:
Excellent, nice and simple that's what we like!!
Interesting way of doing it though, it's effectively booting from the recovery partition rather than the normal boot partition...hence no TWRP! I presume you could swap between rooted and stock that way...would help with those apps that even Magisk can't hide root from...would almost not want the remapping of the power button if it allowed you to swap between the two states (i.e. reboot from power button takes you to stock, reboot via up vol makes you rooted!)
Click to expand...
Click to collapse
xactly what i thinking,
curently i swapping between root and non root simply by rebooting.
---------- Post added at 02:10 PM ---------- Previous post was at 02:08 PM ----------
ZHARQ said:
I'm not certain that the patched_boot.img is the same as the one the way the topic author mentions (I can be wrong though).
Would be nice to know exactly what it's already patched with.. Magisk maybe?
Click to expand...
Click to collapse
my file patched with magisk as well of course,
difference is, author of this thread using TWRP image as base, while am using a pure stock recovery ramdiak from .168 EMUI 9 firmware
TWRP image can work as well, but may cause issue in some devices with different firmware version,
after all, topjohnwu tell you to use recovery ramdisk image, not TWRP right
Thanks
It worked fine, but not with TWRP img, I used my own recovery img
Can´t get to rooted EMUI 9. Always ended in non-rooted even after multiple reboots to recovery
Related
Hi,
With the new version of Magisk v14.0, it seems that neither root neither custom recovery are necessary!
So if I just unlock the bootloader and install Magisk, my device should reveice the OTA right?
Anyone tried and succeeded?
I'm currently using PureNexus, but i'd prefer to go back on stock with OTA. (and edit /etc/host with magisk)
Thanks
You should install stock recovery if you want to get OTA . If you're rooted, you will lose root and need to flash Magisk again (with nexus root toolkit).
Locked or unlocked bootloader, it not affect the updating process. The custom recovery will not flash OTAs . Flash fire is the solution if you have custom recovery . Bootloader and radio can only flash with fastboot. But lately with the latest updates on flash fire, it reboot and screen stay black and need to perform force reboot.
What I wanted to do:
1 - Factory reset (I received my 5x yesterday, no data to backup)
2 - Revert to stock (stock rom + stock recovery)
3 - Install Magisk Manager
4 - Patch stock boot image in Magisk Manager
5 - Flash the patched boot image
After these few steps, I should have a stock rom with magisk.
When OTA is available, I have to restore stock boot image, then apply the OTA, and finally perform steps 3 to 5 right?
mika91 said:
What I wanted to do:
1 - Factory reset (I received my 5x yesterday, no data to backup)
2 - Revert to stock (stock rom + stock recovery)
3 - Install Magisk Manager
4 - Patch stock boot image in Magisk Manager
5 - Flash the patched boot image
After these few steps, I should have a stock rom with magisk.
When OTA is available, I have to restore stock boot image, then apply the OTA, and finally perform steps 3 to 5 right?
Click to expand...
Click to collapse
I find this easier/faster:
1. stock rom + stock recovery
2. "fastboot boot twrp.img" (boots TWRP without flashing it)
3. install magisk from TWRP
When OTA cames in, I just apply it and then repeat steps 2 and 3
_mysiak_ said:
I find this easier/faster:
1. stock rom + stock recovery
2. "fastboot boot twrp.img" (boots TWRP without flashing it)
3. install magisk from TWRP
When OTA cames in, I just apply it and then repeat steps 2 and 3
Click to expand...
Click to collapse
Ok, thanks for the tips.
It's easier sure, but it works only if you have a computer near to you
mika91 said:
Ok, thanks for the tips.
It's easier sure, but it works only if you have a computer near to you
Click to expand...
Click to collapse
Well, unless I missed something, in your steps you need computer to flash patched boot.img as well.. You have to have a stock recovery for OTA, you can't flash it via TWRP.
_mysiak_ said:
Well, unless I missed something, in your steps you need computer to flash patched boot.img as well..
Click to expand...
Click to collapse
oups, you're right!
so definitively you're method is the way I'll go
bug
---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------
_mysiak_ said:
I find this easier/faster:
1. stock rom + stock recovery
2. "fastboot boot twrp.img" (boots TWRP without flashing it)
3. install magisk from TWRP
When OTA cames in, I just apply it and then repeat steps 2 and 3
Click to expand...
Click to collapse
How did you suceed to boot twrp with locked bootloader? I'm trying to make as you wrote, but when I try it fails:
downloading 'boot . img'...
OKAY [ 0.429s]
booting...
FAILED (remote: unlock device to use this command)
I neither want to unlock my bootloader.
You can't use fastboot commands with locked bootloader, the only way is to unlock the bootloader. Unlocking bootloader on Nexus 5x is also a "safety" preparation for a future HW bootloop, you might be able to use one of the existing (temporary) fixes to boot the phone with problematic CPU cores disabled.
nigga99 said:
bug
---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------
How did you suceed to boot twrp with locked bootloader? I'm trying to make as you wrote, but when I try it fails:
downloading 'boot . img'...
OKAY [ 0.429s]
booting...
FAILED (remote: unlock device to use this command)
I neither want to unlock my bootloader.
Click to expand...
Click to collapse
_mysiak_ said:
You can't use fastboot commands with locked bootloader, the only way is to unlock the bootloader. Unlocking bootloader on Nexus 5x is also a "safety" preparation for a future HW bootloop, you might be able to use one of the existing (temporary) fixes to boot the phone with problematic CPU cores disabled.
Click to expand...
Click to collapse
Thank you much. So I'll unlock the bootloader then, I didn't know that it is possible to OTA with unlocked bootloader..
nigga99 said:
Thank you much. So I'll unlock the bootloader then, I didn't know that it is possible to OTA with unlocked bootloader..
Click to expand...
Click to collapse
As long as you keep stock recovery and unmodified system, you can apply OTA. It doesn't check bootloader status or systemless modifications (Magisk, Supersu,..). Just please keep in mind that bootloader unlocking will wipe all your data.
Here is a guide how to install the OTA without computer and keep magisk:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
mika91 said:
Hi,
With the new version of Magisk v14.0, it seems that neither root neither custom recovery are necessary!
So if I just unlock the bootloader and install Magisk, my device should reveice the OTA right?
Anyone tried and succeeded?
I'm currently using PureNexus, but i'd prefer to go back on stock with OTA. (and edit /etc/host with magisk)
Thanks
Click to expand...
Click to collapse
Dear Sir,
I have nexus 5x and it has bootloop issue. " https://www.youtube.com/watch?v=VyebEZMwVsQ " With the help of this video i repaired my phone. Thanks for one who created the Patched boot image.
I am not able to install any custom Kernel to my phone, if i install it wont boot up. Then i need to repatch the Patched boot image. Is there any soluction for this? I got any update to 8.1.0. Is it possible to update without any problem?
tomsonmathewv said:
Dear Sir,
I have nexus 5x and it has bootloop issue. " https://www.youtube.com/watch?v=VyebEZMwVsQ " With the help of this video i repaired my phone. Thanks for one who created the Patched boot image.
I am not able to install any custom Kernel to my phone, if i install it wont boot up. Then i need to repatch the Patched boot image. Is there any soluction for this? I got any update to 8.1.0. Is it possible to update without any problem?
Click to expand...
Click to collapse
You're asking in a dead and wrong thread. However, this post has everything you need. You can also check out https://forum.xda-developers.com/nexus-5x/general/nexus-5x-bootloop-death-blod-andorid-t3683926.
I got update from oero to pie via OTA today,
I tried many patched boot.img and root maunally by patching stock img but its stuck on boot screen.. Any idea??
Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.
Hakkinan said:
Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.
Click to expand...
Click to collapse
What's mean " in both slots " ?
I tried to patch boot.img maunally but my device stuck on boot animations, So I flashed back stock boot.img into fastboot without root agian..
This is an A/B device which means that it has two slots for every partition (A and B). You need to flash the stock boot in the same partirion that it currently being used, flashing It in both is just to be safe in future updates.
Oh hey try this one: https://drive.google.com/file/d/1dBX2dZV_wWgSip8d9lk0lrO_JHfxGdKU/view?usp=sharing
Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.
FRibeiro1400 said:
Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.
Click to expand...
Click to collapse
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?
FRibeiro1400 said:
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?
Click to expand...
Click to collapse
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"
Hakkinan said:
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"
Click to expand...
Click to collapse
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?
HaN5aR said:
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?
Click to expand...
Click to collapse
Wait, did you try to flash the whole OTA?
Hakkinan said:
Wait, did you try to flash the whole OTA?
Click to expand...
Click to collapse
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations
Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?
HaN5aR said:
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations
Click to expand...
Click to collapse
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
FRibeiro1400 said:
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?
Click to expand...
Click to collapse
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.
Hakkinan said:
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.
Click to expand...
Click to collapse
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.
FRibeiro1400 said:
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.
Click to expand...
Click to collapse
Doesn't matter if you had 10.0.1.0 previously or not. You can download it and install it without losing data.
https://mobile.twitter.com/topjohnwu/status/1077067871660855296?s=20
From the man himself.
Seems as though it's only a matter of time now.
https://github.com/topjohnwu/magisk_files/blob/master/canary_builds/notes.md
Or boot into twrp and adb sideload magisk-release.zip.
I'll try later.
It is possible to root without recovery for Ota updates?
Supzztar said:
It is possible to root without recovery for Ota updates?
Click to expand...
Click to collapse
OTA updates will fail if root is detected.
zgomot said:
OTA updates will fail if root is detected.
Click to expand...
Click to collapse
Is this due to emui 9? Because in 8.1 I've had OTA updates without a problem. Even when rooted with magisk.
curtricias said:
Is this due to emui 9? Because in 8.1 I've had OTA updates without a problem. Even when rooted with magisk.
Click to expand...
Click to collapse
That's strange, I could never take OTA updates while rooted, on any EMUI.
Hi,
I try this "How to" from P20 PRO forum : p20-pro/guide-how-to-finally-root-emui9-t3883295 using P20 twrp_p20_0.1.img by Pretoriano80 here : p20/recovery-twrp-3-2-1-0-t3778585
It works fine, my P20 whith Pie UMUI9 is rooted.
Be carefull :
To have root working, at each start, you have to Boot your phone with holding vol-up button.
Regards
zgomot said:
That's strange, I could never take OTA updates while rooted, on any EMUI.
Click to expand...
Click to collapse
Has to do with the custom recovery not the fact that it was rooted
Titioz said:
Hi,
I try this "How to" from P20 PRO forum : p20-pro/guide-how-to-finally-root-emui9-t3883295 using P20 twrp_p20_0.1.img by Pretoriano80 here : p20/recovery-twrp-3-2-1-0-t3778585
It works fine, my P20 whith Pie UMUI9 is rooted.
Be carefull :
To have root working, at each start, you have to Boot your phone with holding vol-up button.
Regards
Click to expand...
Click to collapse
It is possible to root without custom recovery?
Titioz said:
Hi,
I try this "How to" from P20 PRO forum : p20-pro/guide-how-to-finally-root-emui9-t3883295 using P20 twrp_p20_0.1.img by Pretoriano80 here : p20/recovery-twrp-3-2-1-0-t3778585
It works fine, my P20 whith Pie UMUI9 is rooted.
Be carefull :
To have root working, at each start, you have to Boot your phone with holding vol-up button.
Regards
Click to expand...
Click to collapse
Wow. It's so easy.
Can't seem to flash modules, though, but having root on EMUI 9 is just great!
Supzztar said:
It is possible to root without custom recovery?
Click to expand...
Click to collapse
I don't know.
With this method, you need to patch a recovery_ramdisk image to boot the system with root access
And then, you can't access to twrp anymore with patched image (but anyway, for me, this twrp version does not work anymore with EMUI9 ! => touch screen doesn't work).
Regards
Yes!
curtricias said:
Yes!
Click to expand...
Click to collapse
could you tell me how to do that? thanks
Ducati87 said:
could you tell me how to do that? thanks
Click to expand...
Click to collapse
Download latest magisk build.
Manually change update channel to canary build
https://www.google.com/amp/s/forum....sk-canary-channel-bleeding-edge-t3839337/amp/
Install magisk : patch your recovery_ramdisk
Then reboot bootloader.
Fastboot flash recovery_ramdisk patched_boot.img
When reboot, hold volume up button. As if you want to go to recovery.
But in stead recovery ,your system will boot. And magisk is installed ?
curtricias said:
Download latest magisk build.
Manually change update channel to canary build
https://www.google.com/amp/s/forum....sk-canary-channel-bleeding-edge-t3839337/amp/
Install magisk : patch your recovery_ramdisk
Then reboot bootloader.
Fastboot flash recovery_ramdisk patched_boot.img
When reboot, hold volume up button. As if you want to go to recovery.
But in stead recovery ,your system will boot. And magisk is installed ?
Click to expand...
Click to collapse
what you mean for patch your recovery_ramdisk? thank you.
edit: could be compatible with this: https://forum.xda-developers.com/huawei-p20/how-to/magisk-root-t3777612
Ducati87 said:
what you mean for patch your recovery_ramdisk? thank you.
edit: could be compatible with this: https://forum.xda-developers.com/huawei-p20/how-to/magisk-root-t3777612
Click to expand...
Click to collapse
Did you ever root your device with magisk?
ducati8701 said:
Unfortunately no
Click to expand...
Click to collapse
I suggest that you first read about magisk. And especially how to use it.
When you root your device many things can go wrong and your device can end up bricked.
Problem
So did this on my p20 and all worked well untill some module is causing the phone not to boot. I can boot without magisk but there is no way now to disable the faulty module. even reflashed the modified recovery boot image and the modules are still stuck. Any idea where i can delete all the modules?
Grumps said:
So did this on my p20 and all worked well untill some module is causing the phone not to boot. I can boot without magisk but there is no way now to disable the faulty module. even reflashed the modified recovery boot image and the modules are still stuck. Any idea where i can delete all the modules?
Click to expand...
Click to collapse
Remove magisk. Then reinstall magisk. Should work.
Villa Curtricias said:
Remove magisk. Then reinstall magisk. Should work.
Click to expand...
Click to collapse
Doesnt
But i got it right
adb shell
su
then deleted the magisk.img in data\adb i think it was
Hey guys. I accidentally (don't ask) installed the update for Android 10 from 9 stock and lost my twrp and root. Is there any way to at least get root back without having to reinstall everything?
More details will be needed to help. Bootloader unlocked? Guessing yes since you say you had twrp. Check the guide section for root instructions.
Yes I have it unlocked. I looked at the guide and it looks like I will have to reflash the stock rom which I'd like to avoid.
Kreuger said:
Hey guys. I accidentally (don't ask) installed the update for Android 10 from 9 stock and lost my twrp and root. Is there any way to at least get root back without having to reinstall everything?
Click to expand...
Click to collapse
Since, twrp is not available yet for Android 10 (Q), I suggest one of the three following options:
1. If you have to re-flash the Pixel 3 XL Android 10 (Q) Factory image, do #4 'keep data' in this Guide.
2. If your Pixel 3XL has the latest Android 10 (Q) Factory image installed, just do #9 A. in this Guide to root.
3. If you are on a Custom ROM follow the OP Instructions in the Custom ROM thread to root.
Apparently I have the Sept update (QP1A.19711.020.C3) but I currently have no available updates. Am I good to just use your step 2?
Kreuger said:
Apparently I have the Sept update (QP1A.19711.020.C3) but I currently have no available updates. Am I good to just use your step 2?
Click to expand...
Click to collapse
Yes!
Why not do #1 update your Pixel 3 XL to the February Factory image (QQ1A.200205.002). You will not lose your data (need to reinstall anything). Then do #2 to root.
I guess I can do it that way. Thanks.
Edit: Do I need to use a custom kernel? I don't really require one. Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.
Kreuger said:
Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.
Click to expand...
Click to collapse
Some people are reporting that issue. You can set the custom channel to canary/canary debug manually. Check the magisk thread.
Thank you. I tried to find it on the github site and found nothing.
Kreuger said:
Thank you. I tried to find it on the github site and found nothing.
Click to expand...
Click to collapse
It is under the magisk files repo.
Kreuger said:
I guess I can do it that way. Thanks.
Edit: Do I need to use a custom kernel? I don't really require one. Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.
Click to expand...
Click to collapse
Kernel/Kernel Managers are optional. #10 B ,in the guide, updated.
Hey so I patched the image and flashed the file, I'm stuck on the screen with the google logo and progress bar. Also, does it matter that I used adb reboot fastboot to get to the fastboot menu? I noticed it said fastbootd which ive never seen before. It seemed easier to do it that way.
Edit: Ive decided to try flashing another rom.
Kreuger said:
Hey so I patched the image and flashed the file, I'm stuck on the screen with the google logo and progress bar. Also, does it matter that I used adb reboot fastboot to get to the fastboot menu? I noticed it said fastbootd which ive never seen before. It seemed easier to do it that way.
Edit: Ive decided to try flashing another rom.
Click to expand...
Click to collapse
For flashing boot.img you should reboot bootloader. Fastboot is a separate thing now for system files to be flashed. Boot, bootloader, and radio are flashed in bootloader, others in fastbootd.
wangdaning said:
For flashing boot.img you should reboot bootloader. Fastboot is a separate thing now for system files to be flashed. Boot, bootloader, and radio are flashed in bootloader, others in fastbootd.
Click to expand...
Click to collapse
Ah I was unaware. Thanks
so i updated to OOS 10.0.9 Global on HD1900(China), but there is no patched boot or fastboot rom yet, so i patched it with his guide: guide by @gpz110
Boot.img patched with MAGISK 20.4 on OOS 10.0.9 HD65AA (GLOBAL)
Only for OOS 10.0.9 Global!!!!
Enjoy!
Instructions:
reboot to fastboot
Code:
adb reboot bootloader
Code:
fastboot boot magisk_patched_10_0_9.img
let it boot and check if u have root
if u got root then reboot to fastboot again
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched_10_0_9.img
patched boot.img download: https://drive.google.com/file/d/1mHbDV0t_TKrhV2XqT7YySoHsl8623Bc4/view?usp=sharing
stock boot.img download: https://drive.google.com/file/d/1RzUHNfp0Zns2FrfOHA9mwoDW9BKKeZVH/view?usp=sharing
My model is an HD 1905 but my current build number is 10.0.9 HD65AA... I bought it directly from OnePlus it's a 7T. Is this the boot image I need? I spent hours looking all over in different boot images patched with magisk. I haven't even unlocked my bootloader yet because I'm not sure what my options are... Lol also I noticed you have the patched boot image and a stock boot image I said just in case something goes wrong?
Sent from my OnePlus7T using XDA Labs
groovemetal81 said:
My model is an HD 1905 but my current build number is 10.0.9 HD65AA... I bought it directly from OnePlus it's a 7T. Is this the boot image I need? I spent hours looking all over in different boot images patched with magisk. I haven't even unlocked my bootloader yet because I'm not sure what my options are... Lol also I noticed you have the patched boot image and a stock boot image I said just in case something goes wrong?
Sent from my OnePlus7T using XDA Labs
Click to expand...
Click to collapse
it should work, but first u need an unlocked bootloader...
u can test it as described with the first and second step("fastboot boot" command only boot once, if u get bootloop, just restart and your device will boot as usual) , if it boot and u got root with no problems, then u can finish the process with the third and fourth step
boot image patched for EU version is possible 10.0.9.HD65BA ?
Yeah I just upgraded from a 6t and that was capable of a custom recovery but I'd run into trouble all the time because of the dual partition.. so that patched boot image with magisk all's I need is the APK file 7.51 correct I shouldn't need the magisk 24 .0zip
Sent from my OnePlus7T using XDA Labs
EmiRap said:
boot image patched for EU version is possible 10.0.9.HD65BA ?
Click to expand...
Click to collapse
check my tool here
Thx Thx Thx it worked properly
Thanks. Worked like a charm. The only thing is that I cannot find Advanced option and SafetyNet check is missing in Magisk Manager like I had previously in my OP6T. Also, with this root Google Pay and the likes work, as I also do not see Magisk Hide, but did enalbe in Settings. Thumbs up.
Update: Seems like WiFi is not working now! Any tips?
EazyVG said:
Thanks. Worked like a charm. The only thing is that I cannot find Advanced option and SafetyNet check is missing in Magisk Manager like I had previously in my OP6T. Also, with this root Google Pay and the likes work, as I also do not see Magisk Hide, but did enalbe in Settings. Thumbs up.
Update: Seems like WiFi is not working now! Any tips?
Click to expand...
Click to collapse
Are you sure, that you are on OOS 10.0.9 Global?
To revert back to stock boot image, grab the boot image from a fastboot rom here
be sure to grab the right one!
Definitely it is 10.0.9 HD65AA (GLOBAL) which I got over OTA. But I'll download the one from link again and update locally and then again re-run the steps for root.
Update: Reinstalled 10.0.0.9 and the steps ... all working, no above mentioned issues now. Thanks!
I did the whole steps but the phone application continues to stop and then the data network does not work What is the problem I have updated wirelessly to 1009
AboNaya said:
I did the whole steps but the phone application continues to stop and then the data network does not work What is the problem I have updated wirelessly to 1009
Click to expand...
Click to collapse
Did you already flashed or just booted the image?
HD1905BA Europe Patched boot
10.0.9 HD1905BA (Europe)
Stock boot : drive.google.com /file/d/1yyfzh6HbjrdZG3WDeyTv1d04fBgX3yzl/view?usp=sharing[/url]
Patched boot: drive.google.com /file/d/1ZCX7CWpRX-sZrb_ICOg64q2Abdumynmf/view?usp=sharing
guys!
Just a quick question: does this method pass the safetyNet check?
KyoshiDev said:
Did you already flashed or just booted the image?
Click to expand...
Click to collapse
I think I'll second his problem. I did first couple steps, confirmed root, everything seemed ok. Reboot and performed remaining steps. Now I have major stability problems. System UI eventually FCs then phone restarts. I'm able to get to settings and check version, still shows OOS 10.0.8 HD65AA. The signal bars showed no bars but LTE+ logo. Running another app called Signal Check Pro I confirmed that I had data. It seemed to get more stable the more it booted. The updater still wants to do a full update and wipe, it detects root and says that doing the full upgrade will lose root. I'm probably going to let mine do the full update and then reroot.
How did you patch the image? I get a non working patched boot.img when using the latest version of Magisk Manager.
AboNaya said:
I did the whole steps but the phone application continues to stop and then the data network does not work What is the problem I have updated wirelessly to 1009
Click to expand...
Click to collapse
im having a similar problem, after full ota update (2.6gb) from rooted 10.0.8 im losing mobile network (two SIM icon, greyed out, with a slash sign over it and no baseband infromation) after booting/flashing this boot, even creating mine. Mobile network restores after returning to stock. any clue? Im on 10.0.9.HD65AA
Sacob said:
guys!
Just a quick question: does this method pass the safetyNet check?
Click to expand...
Click to collapse
Yes
Nice Work with that .bat file
It works on Oneplus 7t 10.0.9Hd65BA. EU
Thanks for that super cool tool
To others that need to root a Oneplus 7t 10.0.9Hd65BA. EU i share my magisk boot file whit you all
#drive.google.com/open?id=1vGlNWrw2JAXmtb2ibst2BEQhKCM5ceMl #
Download the file an follow the guide in #1
Hi, I've just received my OP7t Global HD1900.
I installed OTA 10.0.9 and already unlocked the bootloader.
Please, does TWRP recovery work on this phone with 10.0.9? If not, which recovery should I use?
Do I have to flash a patched boot.img to get the phone rooted?
I used the boot image and it rooted my phone..great and many thanks!
Now...which recovery should I flash?
Thanks..