[Updated/All Versions & Models!] Root OnePlus 7T Pro - OnePlus 7T Pro (Regular & McLaren) Guides, News...

How to root any version of the OnePlus 7T Pro!
1. Make sure your bootloader is unlocked!
2. Once you're unlocked enter the following ADB commands to extract your current boot image (Your phone needs to be on)
adb shell dd if=/dev/block/bootdevice/by-name/boot_a of=/boot_a.img
adb pull /boot_a.img pathinyourpc
Click to expand...
Click to collapse
3. Download & install Magisk Manager on your phone
4. Put the boot_a.img file on your phone
5. Open the magisk manager app and click the "Advanced Settings" button, then enable "Prserve AVB 2.0/dm-verity & Preserve force encryption", then select the top "Install" button and select "Patch to boot image" and select the boot_a.img
6. Now magisk will create a magisk patched boot image file, put that on your computer
7. Now enter the following ADB command
adb reboot fastboot
fastboot --set-active=a
fastboot boot pathtomagiskpatched.img
Click to expand...
Click to collapse
8. Now you'll boot into the system, reopen the magisk app and click the top install button again and select "Direct install", then reboot
Congratulations you've now successfully rooted your phone!

EDIT: This guide is wrong.
Check these references for the proper guide to root. OP refuses to acknowledge it's wrong even when I pointed it out to him with proof.
https://forum.xda-developers.com/showpost.php?p=81023631&postcount=144
^^^
Mainly this one.
https://forum.xda-developers.com/showpost.php?p=81105485&postcount=171
https://forum.xda-developers.com/showpost.php?p=81106827&postcount=173
-----
Now I have something so do for the weekend, thanks
Just a question, have you tried Viper4Android (if your use it)?: Use 2.7.1.6 stable version.

hi,
tryed it out.. When i boot your patched image.. there is no install button in magisk. It tolds me that i am already on the newest version.
Second.. WLAN isnt working any more. Cant enable wlan. When i reboot with stock img. everything is fine.

Dukynuky said:
hi,
tryed it out.. When i boot your patched image.. there is no install button in magisk. It tolds me that i am already on the newest version.
Second.. WLAN isnt working any more. Cant enable wlan. When i reboot with stock img. everything is fine.
Click to expand...
Click to collapse
Yes it says its installed thats correct but you need to install it again in the magisk app so it stays after restarting the phone. I don't know about WLAN tho

Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.

I can confirm I have successfully rooted using this method, and WIFI is working fine. Thank you very much, OP and everyone involved, no wits time to set up my device

Ah! Will do this immediately when I get home.

I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
edit: flashed the original boot img and boots fine, whever i try to boot magisk patched it bootlops because faulty drivers
to clear up, i tried installing viper4android driver directly from the app, so i guess theres residue left

Lossyx said:
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
Click to expand...
Click to collapse
did you install modules ? try booting the patched boot image from here and then, uninstall the modules again...

Works like a charm!
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
Thanks to everyone who made this possible so soon!

Dukynuky said:
did you install modules ? try booting the patched boot image from here and then, uninstall the modules again...
Click to expand...
Click to collapse
please see my edited reply, i installed directry through viper4android app, no the module

Dukynuky said:
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
Click to expand...
Click to collapse
got ist working.. layer 8 error.. didnt had the ota update installed.
Updated oxygen os.. then wifi is working. also used canary magisk files.. works perfekt.. thanks

Dukynuky said:
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
Click to expand...
Click to collapse
my wifi works perfectly fine, I have the EU version too.
I attached screenshots of what to do with the installed, please select the direct install option and then reboot!

droidvark said:
Works like a charm!
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
Thanks to everyone who made this possible so soon!
Click to expand...
Click to collapse
I have a warning above the instructions already, I think you might have missed it

Lossyx said:
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
edit: flashed the original boot img and boots fine, whever i try to boot magisk patched it bootlops because faulty drivers
to clear up, i tried installing viper4android driver directly from the app, so i guess theres residue left
Click to expand...
Click to collapse
I also bootlooped as well, I tried to install liveboot and i guess that didnt work lol
anyways, I fixed my bootloop by booting the unpatched boot img and then doing a factory reset in the settings, after that you can just boot to the magisk boot img again!

Lossyx said:
please see my edited reply, i installed directry through viper4android app, no the module
Click to expand...
Click to collapse
Use the module next time!

HolyChickenGuy said:
I have a warning above the instructions already, I think you might have missed it
Click to expand...
Click to collapse
I'm not sure where the misunderstanding is coming from, I know that you give that warning. What I mean is that strictly speaking following your steps does not wipe the phone, unlocking the bootloader wipes the phone. But you don't have that step in your instructions. See what I mean? .
When I read your steps, I was like "wipes my phone how?" Maybe booting your image would wipe my phone or something? I'm glad it didn't .
I just thought for clarity's sake it would be good to make that clear in the steps that's all!

droidvark said:
I'm not sure where the misunderstanding is coming from, I know that you give that warning. What I mean is that strictly speaking following your steps does not wipe the phone, unlocking the bootloader wipes the phone. But you don't have that step in your instructions. See what I mean? .
When I read your steps, I was like "wipes my phone how?" Maybe booting your image would wipe my phone or something? I'm glad it didn't .
I just thought for clarity's sake it would be good to make that clear in the steps that's all!
Click to expand...
Click to collapse
Oh sorry, yeah I rewrote it to make it clearer. Unlocking the bootloader will wipe your data
Sent from my HD1913 using Tapatalk

HolyChickenGuy said:
I also bootlooped as well, I tried to install liveboot and i guess that didnt work lol
anyways, I fixed my bootloop by booting the unpatched boot img and then doing a factory reset in the settings, after that you can just boot to the magisk boot img again!
Click to expand...
Click to collapse
Damn, you are my hero. Did a factory reset and followed the OP again, now everything is fine and I'm rooted. Thank you again.
edit: also, for safety precaution, disable automatic updates in Developer options
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

Great, I'll check back in on this tomorrow and see how everyone is getting on before I try. Had a skim through here this morning before mine arrived and didn't see anything so set up as is.

Related

Magisk on rooted LG LV3 or Aristo with TWRP

UPDATED AND EDITED
Hello everyone. I decided to edit my first post on this thread to make finding the instructions on how to Root & Install TWRP along with Magisk on the LG ARISTO or LV3 for T-Mobile/Metro PCS
WARNING:
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE, DAMAGE IT, GET IT STUCK ON BOOTLOOP, MAKE YOUR DEVICE CAUSE A NUCLEAR EXPLOSIVE, OR HAVE IT CAUSE A ZOMBIE APOCALYPSE. TRY AT YOUR OWN RISK.
But if you follow Messi's instructions down to a tee. You shouldn't have any problem
The stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications after flashing twrp!
SOLUTION:
Flash a root such as SuperSU or Magisk V13.3 You should also flash no-verity-opt-encrypt.zip. (although I was informed you might not need to with Magisk, again try at your own risk)
Prerequisites :
Enable OEM Unlocking and usb debugging in developer options!
Go to settings
About Phone
Software Info
And press on Build Number about 9 times
You will see a pop up notifying you that you have unlocked Developer Options
Go Back and you should see the new settings option
Enter Developer Options
Enable it, select ok
Enable OEM unlock
And finally disable Automatic System Updates
UNLOCKING BOOTLOADER
(You must be familiar with Command Prompt on Windows)
• YOUR BOOTLOADER MUST BE UNLOCKED
- reboot into fastboot [ adb reboot bootloader ]
- fastboot oem unlock [ this is going to wipe your data ]
If you have problems with the device drivers installed , you will need to install lg bridge app from lg that contains the device driver
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=PWZO7A26B9UW
How to flash the recovery:
• BOOT INTO FASTBOOT MODE:
With your phone off, connect your usb cable to your phone while holding VOLUME DOWN to boot into fastboot mode or just type [adb reboot bootloader] in the adb terminal
• ONCE YOU ARE IN FASTBOOT MODE:
Open a command prompt and type "fastboot flash recovery <path_to_recovery.img>” without the quotation marks.
Example: fastboot flash recovery C:/Users/John/Desktop/recovery.img
[don't forget to extract the downloaded recovery zip to get the recovery.img]
• WHEN THE FLASH COMPLETES: (Takes about 2 seconds)
On your phone, unplug the usb cable and power it off by taking out the battery and putting it back in.
• BOOT INTO RECOVERY MODE FOR THE FIRST TIME
HOLD VOLUME DOWN + POWER until you see the LG logo and then temporarily release the POWER button, immediately pressing and holding it back down until you see the white prompt [factory reset] screen. You will NEVER release the volume down button in this process!
Use the hard keys to select "YES" and then "YES" again to boot into TWRP!
How to Disable encryption & flash super su
1. In TWRP, go to Wipe > Format Data. Enter the keyword ‘yes‘, in the provided space and enter. This will wipe the automatically encrypted filesystem, and decrypt it.
2. Once the wiping is done, reboot back into recovery. Go to Reboot > Recovery.
3. When the recovery boots again, connect your phone to the PC and Enable MTP under the Mount section.
4. Transfer the downloaded ‘no-verity-opt-encrypt-5.1.zip’ and ‘UPDATE-SuperSU-v2.82-20170528234214.zip or if you wants MAGISK then the MagiskV13.zip to your internal storage or EXTSD
5. Disconnect the device now.
6. Tap on Install. Now, navigate your phone’s storage and select ‘no-verity-opt-encrypt-5.1.zip’. Finally swipe the ‘Swipe to confirm Flash’ button on the bottom of the screen.
7. The flashing process will merely take a few seconds. And when it’s done, follow the same method to flash the root package – UPDATE-SuperSU-v2.82-20170528234214.zip or you can flash the MAGISKV13.zip
Wait 1 or 2 minutes after the zip files are done flashing then reboot system and PROFIT! Your phone may take 3-5 minutes to boot the first time and it might boot-loop once or twice at the Metro PCS splash screen but don’t worry this is expected.
DOWNLOADS
All required files [supersu+dm-verify disable] can be found in this thread :
https://forum.xda-developers.com/lg-g5/development/recovery-team-win-recovery-project-lg-g5-t3363047
MAGISK V13.3 by topjohnwu
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
#2 build [stable]
http://www.mediafire.com/file/x1bo7scmrga40q5/lg_aristo_twrp_v3_stable_build_by_messi2050.zip
#2 build Changelog:
-fixed device gets wiped everytime you use the hardware buttons to boot into twrp.
-fixed flashing boot/recovery images through twrp
-built using latest twrp source.
[do not mirror the downloads]
Notice: After the TWRP splash screen you will see the option to type in the password to decrypt the filesystem. just ignore it and hit the cancel button.
--------------------------------------------------------------------------------------------------------
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from So Please Consider donating using the link below if you appreciate my work.
https://www.paypal.me/messi2050
THANKS AND CREDIT
I do not take any credit for this. All the thanks and credit go to: 
 @Messi:
https://androidforums.com/members/messi2050.1983077/
For taking time to build a TWRP Recovery for us without actually owning the device. Much credit and a million thanks.
@topjohnwu
https://forum.xda-developers.com/member.php?u=4470081
For their hard work on the Magisk systemless interface software and dedication to keep on developing the software especially for a lot of us Nougat phone owners. Thanks thanks thanks
Special Thanks
 @phhusson for his advice with sepolicy and his sepolicy injection tool, boot image tools, hide su tools, superuser
@Chainfire for many bits of shell script code, his supolicy in older versions, and the complete documentation How-To SU
 @nkk71 for his original resetprop
 @osm0sis for his shell script for image/zip size detection, unSU, addon.d, also providing numerous support for all kinds of boot image unpacking knowledge
@digitalhigh and @DVDandroid for massive contributions to Magisk Manager
@Captain_Throwback for being the No.1 supporter, testing and finding bugs all the time
Ortem1UP said:
Hello everyone. I'm no stranger to rooting and TWRP. Always looking for rooting methods for wtv device I own. I currently own an LG LV3 or Aristo running Nougat 7.0 and successfully rooted it via adb as well as installed a fully functional TWRP thanks to Messi's method.
Now when it comes to Xposed I'm no novice. But unfortunately there isn't a Nougat compatible one yet. So I'm going with the alternative Magisk. But I am a complete noob when it comes to Magisk.
Can I simply flash the Magisk zip and follow the steps mentioned on the Magisk forum? Also, will MagiskSU replace my current SU without any flaws?
Any help would be appreciated
Click to expand...
Click to collapse
Depends on what root solution you're currently using. If you're using systemless SuperSU Magisk won't replace it, but use that instead. In that case you'll have to first remove SuperSU. If you're using any other root Magisk will try to replace it with MagiskSU (no guarantees). Also, I believe LG devices need a "bump" script, or something like that... I also believe this has been added to the Magisk code, but is not yet in the official release. If v11.1 doesn't work, you could try the unofficial beta snapshot: https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
And just to clarify: Magisk is not an alternative to Xposed... You can do certain things with Magisk that can also be done with Xposed, but they work in completely different ways. Think of Magisk as a "file injector" where it can replace files and props on your device at boot, completely systemless. And along the same kind of thinking Xposed is a "code injector" that can alter the code of a running app. This can also be made systemless, by tools such as Magisk. @topjohnwu have hinted at ideas about making Magisk work as a "code injector", but this is purely on the idea stage at the moment and is probably quite far away in a possible future.
Take a look in the release thread and the Magisk All-In-One Wiki (both stickied at the top). They contain a lot of useful information. There's also a lot of information in the support thread, which is pretty big by now so the search function is a good tool there.
I've also collected a bunch of tips and tricks for Magisk installation and troubleshooting, and as well for Magisk Hide if you want to use that:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Didgeridoohan said:
Depends on what root solution you're currently using. If you're using systemless SuperSU Magisk won't replace it, but use that instead. In that case you'll have to first remove SuperSU. If you're using any other root Magisk will try to replace it with MagiskSU (no guarantees). Also, I believe LG devices need a "bump" script, or something like that... I also believe this has been added to the Magisk code, but is not yet in the official release. If v11.1 doesn't work, you could try the unofficial beta snapshot: https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
And just to clarify: Magisk is not an alternative to Xposed... You can do certain things with Magisk that can also be done with Xposed, but they work in completely different ways. Think of Magisk as a "file injector" where it can replace files and props on your device at boot, completely systemless. And along the same kind of thinking Xposed is a "code injector" that can alter the code of a running app. This can also be made systemless, by tools such as Magisk. @topjohnwu have hinted at ideas about making Magisk work as a "code injector", but this is purely on the idea stage at the moment and is probably quite far away in a possible future.
Take a look in the release thread and the Magisk All-In-One Wiki (both stickied at the top). They contain a lot of useful information. There's also a lot of information in the support thread, which is pretty big by now so the search function is a good tool there.
I've also collected a bunch of tips and tricks for Magisk installation and troubleshooting, and as well for Magisk Hide if you want to use that:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Click to expand...
Click to collapse
Thank you so much. I will definitely look over the links you shared and try some out. I couldn't thank you enough for taking the time to reply and with a ton of info. I'm bound to find something that works. Thanks again.
Sent from my lv3 using XDA Labs
Ortem1UP said:
Hello everyone. I'm no stranger to rooting and TWRP. Always looking for rooting methods for wtv device I own. I currently own an LG LV3 or Aristo running Nougat 7.0 and successfully rooted it via adb as well as installed a fully functional TWRP thanks to Messi's method.
Now when it comes to Xposed I'm no novice. But unfortunately there isn't a Nougat compatible one yet. So I'm going with the alternative Magisk. But I am a complete noob when it comes to Magisk.
Can I simply flash the Magisk zip and follow the steps mentioned on the Magisk forum? Also, will MagiskSU replace my current SU without any flaws?
Any help would be appreciated
Click to expand...
Click to collapse
so what method did you use to root? I can't find any documentation anywhere
brad2192 said:
so what method did you use to root? I can't find any documentation
Here is the link. Sorry for the late response been busy with work and school I'm not sure if this is against the XDA rules like sharing a link to another Forum but here you go
http://androidforums.com/threads/recovery-twrp-v3-for-lg-aristo-metropc-t-mobile.1117942/
Sent from my lv3 using XDA Labs
Click to expand...
Click to collapse
Ortem1UP said:
Thank you so much. I will definitely look over the links you shared and try some out. I couldn't thank you enough for taking the time to reply and with a ton of info. I'm bound to find something that works. Thanks again.
Sent from my lv3 using XDA Labs
Click to expand...
Click to collapse
Did you ever get this figured out? Kinda curious if I can do this without wiping.
BrothelWaffles said:
Did you ever get this figured out? Kinda curious if I can do this without wiping.
Click to expand...
Click to collapse
I almost did but I got stuck on bootloop. The only way I can think it might work would be to return to stock. Follow Messi's method for Twrp & Root. But at the point of root. U can stick with Chainfires SuperSU, or use the latest MagiskSU by Topjohnwu (would recommend)
Then just reboot the device and follow TopJohnwus method of installing Magisk.
But don't take my word for it. It's just and idea. I've yet to try it Cuz I haven't really had time. So it's up to you if u wanna give it a shot.
Or u can wait for me to try it. I was thinking of doing it 2nite. It's 930pm pst
I say around 11-12 I will be giving it another go. Wtv my results are. I will report back. Wish me luck
SUCCESS
I got Magisk to work on My LG Aristo as of today. It was just as I thought.
I went back to stock. Then I followed Messi's method to get TWRP installed. Since I already had my bootloader unlocked. I didnt need to worry about it. Just flashed TWRP via adb as Messi says to do. Unplugged my device and pulled out the battery to turn of my device. Put it back in and rebooted into recovery. Went to wipe and formatted data. Once it was done. Went back and went into Reboot. Rebootted back into recovery. Plugged my phone to my laptop, enabled mtp and transferred both the no-verity-opt-encrypt-2.1.zip file and magiskzip file. Didn't need SuperSu seeing as how Magisk alone roots the device. Flashed the no-verity-opt-encrypt-2.1.zip first and then Magiskzip. Latest version is V13.2 right now. It automatically installs Magisk Manager since it isn't available on the Play Store anymore. Rebooted system. Waited for my phone to start. Set it up and immediately tested it. And Magisk is 100% fully functional with all green checkmarks. Hope it helps. Maybe I should create a thread. Would be my first one. Don't really know how to tho. But I'll try.
Also, here are the snapshots of proof and my magisk settings to get them to pass.
Ortem1UP said:
SUCCESS
I got Magisk to work on My LG Aristo as of today. It was just as I thought.
I went back to stock. Then I followed Messi's method to get TWRP installed. Since I already had my bootloader unlocked. I didnt need to worry about it. Just flashed TWRP via adb as Messi says to do. Unplugged my device and pulled out the battery to turn of my device. Put it back in and rebooted into recovery. Went to wipe and formatted data. Once it was done. Went back and went into Reboot. Rebootted back into recovery. Plugged my phone to my laptop, enabled mtp and transferred both the dm-verity file and magiskzip file. Didn't need SuperSu seeing as how Magisk alone roots the device. Flashed Dm-verity first and then Magiskzip. Latest version is V12 right now. Rebooted system. Waited for my phone to start. Set it up and immediately updated Magisk Manager and viola. Magisk is 100% fully functional with all green checkmarks. Hope it helps. Maybe I should create a thread. Would be my first one tho. Don't really know how to tho. But I'll try.
Also, here are the snapshots of proof and my magisk settings to get them to pass.
Click to expand...
Click to collapse
Thank you so much your a life saver I finally have magisk installed right
Hey ortem, have you had an issue with magisk modules knocking out cell service upon reboot?
Anyone install this by unrooting\uninstalling supersu and flashing the zips...its crazy i have to go all the way back to square one just to install this...any help appreciated
jessebanks said:
Anyone install this by unrooting\uninstalling supersu and flashing the zips...its crazy i have to go all the way back to square one just to install this...any help appreciated
Click to expand...
Click to collapse
Use the full uninstall provided within the supersu app and restart your phone, then go into recovery and flash magisk.
Ortem1UP said:
SUCCESS
I got Magisk to work on My LG Aristo as of today. It was just as I thought.
I went back to stock. Then I followed Messi's method to get TWRP installed. Since I already had my bootloader unlocked. I didnt need to worry about it. Just flashed TWRP via adb as Messi says to do. Unplugged my device and pulled out the battery to turn of my device. Put it back in and rebooted into recovery. Went to wipe and formatted data. Once it was done. Went back and went into Reboot. Rebootted back into recovery. Plugged my phone to my laptop, enabled mtp and transferred both the dm-verity file and magiskzip file. Didn't need SuperSu seeing as how Magisk alone roots the device. Flashed Dm-verity first and then Magiskzip. Latest version is V12 right now. Rebooted system. Waited for my phone to start. Set it up and immediately updated Magisk Manager and viola. Magisk is 100% fully functional with all green checkmarks. Hope it helps. Maybe I should create a thread. Would be my first one tho. Don't really know how to tho. But I'll try.
Also, here are the snapshots of proof and my magisk settings to get them to pass.
Click to expand...
Click to collapse
Hi Ortem1UP, I get the jist of the method but not sure what the dm-verity parts are. Can you explain what this is for, and where are you getting it and what version? Is dm-verity the same as no-verity-opt-encrypt-2.1.zip that messi describes in his twrp tutorial for the Aristo?
azizLIGHT said:
Hi Ortem1UP, I get the jist of the method but not sure what the dm-verity parts are. Can you explain what this is for, and where are you getting it and what version? Is dm-verity the same as no-verity-opt-encrypt-2.1.zip that messi describes in his twrp tutorial for the Aristo?
Click to expand...
Click to collapse
Oh wow. So sorry. I hadn't noticed my mistake. Yes, the dm verity I accidentally mentioned is actually the no-verity-opt-encrypt zip that Messi mentions. I'll fix that mistake. Wouldn't want ppl to get confused. Thanks for that. BTW, the same method also works with the new Magisk V13.2. Just an FYI
Sent from my lv3 using XDA Labs
ninjasinabag said:
Hey ortem, have you had an issue with magisk modules knocking out cell service upon reboot?
Click to expand...
Click to collapse
I apologize for the very late reply.
Actually, no I haven't. Which modules did you install?
Sent from my lv3 using XDA Labs
Ortem1UP said:
Oh wow. So sorry. I hadn't noticed my mistake. Yes, the dm verity I accidentally mentioned is actually the no-verity-opt-encrypt zip that Messi mentions. I'll fix that mistake. Wouldn't want ppl to get confused. Thanks for that. BTW, the same method also works with the new Magisk V13.2. Just an FYI
Sent from my lv3 using XDA Labs
Click to expand...
Click to collapse
Ortem, while I was waiting for your reply, I went ahead and flashed the magisk zip (13.2) without flashing no-verity and I was able to get it to work. I have all green checks as well with SafetyNet. So the no-verity-opt-encrypt zip file may not be needed for magisk to work and to get root/safetynet pass
azizLIGHT said:
Ortem, while I was waiting for your reply, I went ahead and flashed the magisk zip (13.2) without flashing no-verity and I was able to get it to work. I have all green checks as well with SafetyNet. So the no-verity-opt-encrypt zip file may not be needed for magisk to work and to get root/safetynet pass
Click to expand...
Click to collapse
No way. Seriously? Does SafetyNet always pass? Because for me it does at times and other times it doesn't. I wonder if the no-verity-opt-encrypt.zip is to blame? I shall try it your way and see how that goes. Thanks for the heads up. Guess the zip is only needed for SuperSu. Not Magisk.
Sent from my lv3 using XDA Labs
Ortem1UP said:
No way. Seriously? Does SafetyNet always pass? Because for me it does at times and other times it doesn't. I wonder if the no-verity-opt-encrypt.zip is to blame? I shall try it your way and see how that goes. Thanks for the heads up. Guess the zip is only needed for SuperSu. Not Magisk.
Sent from my lv3 using XDA Labs
Click to expand...
Click to collapse
Yeah I'm actually passing SafetyNet sometimes as well and sometimes not. I can't figure out why that's the case. In any case, I don't think the no-verity-opt-encrypt.zip is to blame given since we're both experiencing the same symptoms!
azizLIGHT said:
Yeah I'm actually passing SafetyNet sometimes as well and sometimes not. I can't figure out why that's the case. In any case, I don't think the no-verity-opt-encrypt.zip is to blame given since we're both experiencing the same symptoms!
Click to expand...
Click to collapse
Oh OK. For a second I thought it was the zip file.
Anywho. IDK about you but ever since the latest update. I haven't had a single problem with Safety Net. It passes every time now. I hope your getting the same results?
Sent from my lv3 using XDA Labs
In the "first boot" after TWRP flash process. While holding power button+vol. Down . You must let go of the volume button to make the selection "yes" then "power" to select then hold "VOL DOWN" the next option comes up. Let go press "VOL DOWN" to select "YES" still holding down push "POWER" to make final selection along with DOWN and again proceed as you would when you first went into recovery. Now this in no way a insult to the work that's put into this but I believe in order to teach those that want to learn we must combine our knowledge and create an amazing Rom:victory:

Root OnePlus 7 Pro , Install Magisk And EdXposed

There Is No TWRP Until Now As Its Been Just 4 Days. But We Don't Need TWRP When We Have Magisk . What I Did :-
1:- Downloaded The Stock Boot Image From Github
2:- Downloaded Latest Magisk Manager And Installed.
3:- Patched Stock Boot Image With Magisk.
Download Here
4:- Flashed The Boot Image Using
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
5:- Rebooted. Dang Its Done:laugh:
Credits :- acervenky for stock image.
Xposed
1:- Download Riru-Core From Here
2:- Download EdXposed From Here
3:- Goto Magisk Click On Modules Click On + Button Than Choose Riru And Do Same From EdXoosed.
4:- Reboot And Install EdXposed Apk From Here
Enjoy
Works.
Installed GravityBox. Running smoothly.
Has anyone tried the european Variant gm1913?
jatinarora said:
Works.
Installed GravityBox. Running smoothly.
Click to expand...
Click to collapse
Which version of gravitybox did you install? I can't find a version for Android P.
sippi90 said:
Has anyone tried the european Variant gm1913?
Click to expand...
Click to collapse
Don't do it, I did and now my device is messed up until I can find a full stock zip. Didn't think to backup my stock boot image unfortunately, with the patched boot image I got here wifi won't work anymore and the settings app became very unstable.
Does anyone have a stock 9.5.4 boot image for GM1913? Or a flashable zip for GM1913? Any help would be much appreciated..
Does this work with a T-Mobile variant that's bootloader unlocked?
ScottOtis said:
Does this work with a T-Mobile variant that's bootloader unlocked?
Click to expand...
Click to collapse
I don't think so - or it will but you can't use the patched boot image posted by others here. If I understand correctly you'll need to patch your own rom's boot image. I think the T-mobile version is its own model (not the GM1917 that most people here have).
I used the patched boot image for GM1917 on a GM1913 and now my wifi and most settings are broken. And unfortunately I can't find a stock zip flash file to recover anywhere... I guess that's how it is buying the phone on launch day in Europe.
gururoop said:
Which version of gravitybox did you install? I can't find a version for Android P.
Click to expand...
Click to collapse
https://github.com/GravityBox/GravityBox/releases/tag/v9.0.0-beta-11_p
unixunderground said:
Don't do it, I did and now my device is messed up until I can find a full stock zip. Didn't think to backup my stock boot image unfortunately, with the patched boot image I got here wifi won't work anymore and the settings app became very unstable.
Does anyone have a stock 9.5.4 boot image for GM1913? Or a flashable zip for GM1913? Any help would be much appreciated..
Click to expand...
Click to collapse
Did you solve your issue ?
I got the same when I try, no wifi on the patched boot.
And unfortunately like you I suppose, I wiped and erased the system..... Spend 4h30 trying to solve it ahah
I did find and download the OTA 9.5.4 from XDA dev named
9.5.4-GM21BA-OnePlus7ProOxygen_21.E.08_OTA_008_all_1905150058_12457a8b-FASTBOOT
Click to expand...
Click to collapse
, if you copy and past this name on Google you will find a download link, and I used the All-In-One tools to flash it, you can here this software : here
Because when I tried to flash with the fastboot command, my device was stucked in the Fastboot Mode and could not do anything for 4h30 until I use the All-in-one tools
Hope it can help
How do we keep root if the when there's an OOS update?
After installing Edxposed it fails safetynet check
A.Priori said:
After installing Edxposed it fails safetynet check
Click to expand...
Click to collapse
I'm on gm1917 with patched 9.5.3 (from rom page here) and followed instructions. With gravitybox it has worked well and passes safetynet...
A.Priori said:
After installing Edxposed it fails safetynet check
Click to expand...
Click to collapse
I also faced this, for me not an issue, would be nice if it passed, but I never use no apps that require it. I'd rather the customization than SafetyNet personally, but fair warning.
ERIC
jatinarora said:
Works.
Installed GravityBox. Running smoothly.
Click to expand...
Click to collapse
Yep running fine on my phone with 9.5.4, Magisk 19.2.
Phone is a GM1917
I thought gm1917 is US version which only has 9.5.3 as latest ?
Are you sure you are gm1917?
---------- Post added at 01:49 PM ---------- Previous post was at 01:48 PM ----------
tech_head said:
Yep running fine on my phone with 9.5.4, Magisk 19.2.
Phone is a GM1917
Click to expand...
Click to collapse
thought gm1917 is US version which only has 9.5.3 as latest ?
Are you sure you are gm1917?
unixunderground said:
Don't do it, I did and now my device is messed up until I can find a full stock zip. Didn't think to backup my stock boot image unfortunately, with the patched boot image I got here wifi won't work anymore and the settings app became very unstable.
Does anyone have a stock 9.5.4 boot image for GM1913? Or a flashable zip for GM1913? Any help would be much appreciated..
Click to expand...
Click to collapse
From the other thread, that's a sign the wrong boot image was flashed
I am European with GM1913 with patched 9.5.4 and works flawless! Used the image in here:
forum.xda-developers.com/oneplus-7-pro/how-to/guide-root-oneplus-7-pro-patched-boot-t3931205
Noob question: Can someone point me in the right direction on how to update to the recently released 9.5.4 if I am rooted with this method?
Sent from my GM1911 using Tapatalk
Aren't we missing the command of "fastboot oem unlock"? Actually aren't we missing several steps from the instructions? Like these:
1) Become a "Developer" by clicking on "About Phone" from the settings menu.
2) Click on "Build Number" over and over until it says you are now a developer.
3) Go to the "Developer Options" from within the "System" section.
4) Turn ON "OEM Unlocking".
5) Boot into FastBoot menu through one of three methods. The easiest is turning ON "Advanced Reboot", holding the power button until the menu pops up and selecting "Bootloader".
6) Once rebooted, type "fastboot OEM Unlocking" to fully unlock the device. (The device will now wipe everything).
Mix some of the instructions from Kingmohdarif in here at the end or somewhere in there.
Munk0 said:
Aren't we missing the command of "fastboot oem unlock"? Actually aren't we missing several steps from the instructions? Like these:
1) Become a "Developer" by clicking on "About Phone" from the settings menu.
2) Click on "Build Number" over and over until it says you are now a developer.
3) Go to the "Developer Options" from within the "System" section.
4) Turn ON "OEM Unlocking".
5) Boot into FastBoot menu through one of three methods. The easiest is turning ON "Advanced Reboot", holding the power button until the menu pops up and selecting "Bootloader".
6) Once rebooted, type "fastboot OEM Unlocking" to fully unlock the device. (The device will now wipe everything).
Mix some of the instructions from Kingmohdarif in here at the end or somewhere in there.
Click to expand...
Click to collapse
Well yeah OP makes some assumptions.
I typed "fastboot flashing unlock" instead of what you said but maybe both works.
Anyways, as OP said, we don't have TWRP yet so we must do more ourselves. I've extracted the lastest STOCK boot image from version 9.5.5.GM21BA (at the time of writing the last on downloads.oneplus.com and also what my 7 Pro is running right now). I patched it with Magisk 19.2 and flashed it using "fastboot flash boot magisk_patched.img".
Result was successful, latest firmware, Magisk rooted :good:
The patched boot image was too large to include so I uploaded it to some random file hosting site: https://www.file-up.org/z8ka0weyftcv
To extract the stock boot image I used this nice tool: https://github.com/cyxx/extract_android_ota_payload

Can I get root with pie of the Japanese version SM-N960J / D?

I own the Japanese version of Note9 SM-N960D (SC-01L) SM-N960J (SCV40).
Currently using 9.0 pie.
I want to get the route, but when I wipe with TWRP, I fall into the boot loop.:crying:
Even if you install Magisk and RMM-State_Bypass, it will not start.
I also installed no-verity-opt-encrypt-6.1.zip or no-verity-opt-encrypt-6.0.zip.
Does anyone know how to get root of this Note9 terminal and start it?
neoquor said:
I own the Japanese version of Note9 SM-N960D (SC-01L) SM-N960J (SCV40).
Currently using 9.0 pie.
I want to get the route, but when I wipe with TWRP, I fall into the boot loop.:crying:
Even if you install Magisk and RMM-State_Bypass, it will not start.
I also installed no-verity-opt-encrypt-6.1.zip or no-verity-opt-encrypt-6.0.zip.
Does anyone know how to get root of this Note9 terminal and start it?
Click to expand...
Click to collapse
you might need to flash a custom kernel( or at least a patched one after data format. or it will just bootloop)
also please read dr ketans guide in the general discussion section and use method 1.
bober10113 said:
you might need to flash a custom kernel( or at least a patched one after data format. or it will just bootloop)
also please read dr ketans guide in the general discussion section and use method 1.
Click to expand...
Click to collapse
Thank you for your reply.
Which kernel should be rewritten?
Which discussion page is [dr ketans guide in the use method 1]?
I would be happy if you could tell me.
neoquor said:
Thank you for your reply.
Which kernel should be rewritten?
Which discussion page is [dr ketans guide in the use method 1]?
I would be happy if you could tell me.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143/
bober10113 said:
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143/
Click to expand...
Click to collapse
Thank you for teaching me.
However, TWRP freezes during installation of "N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip" and cannot be installed.
what should I do?
neoquor said:
Thank you for teaching me.
However, TWRP freezes during installation of "N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip" and cannot be installed.
what should I do?
Click to expand...
Click to collapse
what do you mean? have you tried to flash again? also do you choose magisk option and kernel option during setup?
bober10113 said:
what do you mean? have you tried to flash again? also do you choose magisk option and kernel option during setup?
Click to expand...
Click to collapse
I tried the following:
1. Burn carrier genuine ROM with Odin
2. Launch download mode again and write [TWRP_3.2.3-0_N9600_beta3.tar.md5] with Odin
3.TWRP immediately after Method 2
4.Wipe → FORMAT DATA → yes with TWRP
5.Reboot to recovery mode and mount system etc.
6.Install → microSD card menu → “N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip” → Install
Freeze the installation screen.
The terminal I am using is snapdragon.
neoquor said:
I tried the following:
1. Burn carrier genuine ROM with Odin
2. Launch download mode again and write [TWRP_3.2.3-0_N9600_beta3.tar.md5] with Odin
3.TWRP immediately after Method 2
4.Wipe → FORMAT DATA → yes with TWRP
5.Reboot to recovery mode and mount system etc.
6.Install → microSD card menu → “N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip” → Install
Freeze the installation screen.
The terminal I am using is snapdragon.
Click to expand...
Click to collapse
oh snapdragon really? that's why. i thought the japanese model was Exynos. very sorry for that mistake.
then please go to:
https://forum.xda-developers.com/showpost.php?p=77721998&postcount=2
there is guidance in that post towards the end regarding twrp and root.
also i think if you flash twrp, boot to twrp, flash decryption fix then format, reboot back to twrp and then flash latest patched kernel:
https://mega.nz/#F!XlkXxYZK!-KlTcLtsQ14eQBTa-AUNhA!T4lmyYJC
(taken from mentalmuso's thread i linked)
to flash .img choose install image button in twrp then select kernel.img then select destination partition:
boot
bober10113 said:
oh snapdragon really? that's why. i thought the japanese model was Exynos. very sorry for that mistake.
then please go to:
https://forum.xda-developers.com/showpost.php?p=77721998&postcount=2
there is guidance in that post towards the end regarding twrp and root.
also i think if you flash twrp, boot to twrp, flash decryption fix then format, reboot back to twrp and then flash latest patched kernel:
https://mega.nz/#F!XlkXxYZK!-KlTcLtsQ14eQBTa-AUNhA!T4lmyYJC
(taken from mentalmuso's thread i linked)
to flash .img choose install image button in twrp then select kernel.img then select destination partition:
boot
Click to expand...
Click to collapse
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
neoquor said:
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
Click to expand...
Click to collapse
i really dont know. im on exynos device. people with n9600 will have to help you as i have no experience with snapdragon.
sorry
neoquor said:
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
Click to expand...
Click to collapse
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
bober10113 said:
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
Click to expand...
Click to collapse
Thanks, Bob! Just like @neoquor, I am using a Snapdragon Note 9 (SCV40/SM-N960J) from the carrier au. I was able to successfully boot with the firmware of another Japanese carrier variant SM-N960D/SC-01L (carrier DoCoMo) and @klabit87 's N9600 klabit kernel.
Following the Magisk installation instructions from @topjohnwu 's GitHub, my installation was a bit windy (trial-and-error), but I (1) launched Odin and flashed my Magisk-patched SC-01L AP binary along with BL, CP, and CSC; and (2) after falling into the bootloop, I flashed klabit's official N9600 TWRP build, and (3) flashed klabit's N9600 kernel.
After that, success--finally! Dekita!
bober10113 said:
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
Click to expand...
Click to collapse
Thanks, Bob!
With this, Snapdragon Note 9 (SCV40 / SM-N960J) did not reach the boot loop and succeeded in rooting!
However, when I start it, "It's a non-genuine kernel" is displayed and I can't start some apps I want to use.
What should i do?
neoquor said:
Thanks, Bob!
With this, Snapdragon Note 9 (SCV40 / SM-N960J) did not reach the boot loop and succeeded in rooting!
However, when I start it, "It's a non-genuine kernel" is displayed and I can't start some apps I want to use.
What should i do?
Click to expand...
Click to collapse
Dear NeoQuor, did you find any solution ?
I have the same problem I I flashed patched magisk with boot.img file it is flashed 100% but I'm not able to boot to android. it keeps restarting on the boot loop.
I just found one source this guy he is able to root SCV40
https://support.halabtech.com/index.php?a=downloads&b=folder&id=77034
i look forward to a solution for my phone to be rooted.
regards,
Sher
I also have SCV40, and the only reason I need to root my SCV40 because I need to edit and rewrite ro.confiq.tima=1 to 0 so that I'll be able to use S-Health, but in the end I can't root my SCV40, It is impossible, but I did rooting my friend's Note9 and it work well. I guess there's still no one can root SCV40 Until today.

How To Guide [TWRP] MI 11 (Pro/Ultra) (mars/star)

[TWRP] MI 11 (Pro/Ultra) (mars/star)​
WARNING : I do not know who made this TWRP and I am NOT taking credit for it. It was posted on eu site and I'm just sharing since there was no thread for twrp here on xda.
INSTRUCTIONS
1. Before starting the process, the bootloader must be unlocked.
2. Install Xiaomi USB drivers.
3. Enable Usb debugging from Settings - Additional settings - developer options.
4. Download TWRP for Mi 11 (Pro/Ultra) , and put it in your fastboot folder.
5. Put your phone into fastboot mode.
6. Rename downloaded file to "twrp.img".
7. Do the following command. It will automatically boot into TWRP.
Code:
fastboot boot twrp.img
8. If you get a screen asking for a pin, press 2nd option
and change language to English then enter phone pin.
9. Change language to English (press the 6th option).
10. Go to "Advanced" and select "Onekey inject TWRP".
11. Swipe to inject the TWRP. It might take a few minutes, so don't worry.
Note
1) Don't change the boot slot, currently (Slot A) for most or your device will not boot at all.
2) For user experiencing decrypt issue, you can try one of the methods below to enable decryption:
a. Remove all your security eg. fingerprint, face unlock, pattern and leave ONLY pin. Reboot to twrp and try again.
b. Reflash twrp.
c. LAST RESORT! Format data and factory reset your device then reflash twrp.
3. For user experiencing decrypt issue but just want to flash latest build:
a. Boot to twrp > mount > mount usb storage then transfer your rom.zip to data/media/0
b. Now go to install and look for rom.zip under data/media/0. Profit!
4. The decrypt issue was a bug on the Chinese twrp, no update since may so don't ask for an ETA.
CHANGELOGS
07/18/21
1) Additional instruction from scratch.
2) Additional note for people having decrypt issue.
CTTO: xiaomi.eu, hoangsang
Is the legit TWRP ?? Xiaomi.EU getting ready to push updates via TWRP? :'D
skylerfly16 said:
Is the legit TWRP ?? Xiaomi.EU getting ready to push updates via TWRP? :'D
Click to expand...
Click to collapse
Yes, They just did the new stable in TWRP Format.
The Chinese exe worked for me this morning but after I installed it the phone didn't want to boot and I got stuck in twrp for awhile
speedtripler said:
The Chinese exe worked for me this morning but after I installed it the phone didn't want to boot and I got stuck in twrp for awhile
Click to expand...
Click to collapse
Why did you install the Chinese exe?
skylerfly16 said:
Why did you install the Chinese exe?
Click to expand...
Click to collapse
The official one hadn't been released yet and I like a challenge sometimes
Hey, thx for bringing this to my attention, but i checked... root-access is gone... :/
deleted post
I keep getting a " no such partician " fail msg , what am I doing wrong here?
speedtripler said:
I keep getting a " no such partician " fail msg , what am I doing wrong here?
Click to expand...
Click to collapse
Your device is not connected, hence the empty list after adb devices.
Did you enable USB debugging in Developer options?
heinhuiz said:
Your device is not connected, hence the empty list after adb devices.
Did you enable USB debugging in Developer options?
Click to expand...
Click to collapse
Thx It's ok,I got it after a few attempts
The language on twrp still opens on Chinese and it needs changed to English each time but apart from that it seems to work fine!
SanHelios said:
Hey, thx for bringing this to my attention, but i checked... root-access is gone... :/
Click to expand...
Click to collapse
mine was revoked after i flash the latest stable, just download magisk23.apk then rename it to magisk23.zip and flash thru twrp, got my root back that way, cheers
innocence07 said:
mine was revoked after i flash the latest stable, just download magisk23.apk then rename it to magisk23.zip and flash thru twrp, got my root back that way, cheers
Click to expand...
Click to collapse
Is banking and payment apps still working?
Can you still pass safetynet check?
speedtripler said:
Is banking and payment apps still working?
Can you still pass safetynet check?
Click to expand...
Click to collapse
Yes and yes
Thanks, it works for me.
But each time i boot on TWRP, go back to chinesse language.
Can we do backup ? (and what can we backup) in case of something wrong in the future
sabrewulf said:
Thanks, it works for me.
But each time i boot on TWRP, go back to chinesse language.
Can we do backup ? (and what can we backup) in case of something wrong in the future
Click to expand...
Click to collapse
The recovery is fully functional as far as I can tell...
I did a complete backup successfully but I haven't tried to restore it yet
You click on everything ?
Hi,
after a long day of learning the hard way (got stuck in Fastboot Loop) I am now on stable EU 12.5.7 (MI11 Ultra, EU phone). So far so good, but I was wondering, how can I make TWRP stuck to the phone, meaning, when I push the power button to have an option like: Boot into TWRP. Is that possible or is there a "click this button with this... trick"?
ATM, I can only get TWRP to work, when I enable it via PC, which is not good.
I am asking, because I have an old Oneplus 6, which has this option. TWRP is installed and I can boot directly to it, if I want to.
Can you please help me out? Is there a trick or am I doing something wrong?
Greetings from Germany
Placebo
I believe you are on custom EU rom right? Just reboot into recovery, custom eu rom injects twrp as standard recovery
Hi, yes I am and I did that also. But still can't boot into TWRP from within the phone. Is there a trick after the injection?

Question Rooting Zenfone 8

I understand there is no TWRP recovery for Zenfone 8 yet, but according to other posts, their are other ways to root the phone, e.g. using Magisk boot image patch method.
I tried, but I'm not able to flash the boot image in fastboot. I'm able to boot to fastboot mode, but it's showing no device when I use "fastboot devices" with USB connection. If I enter recovery mode, "adb devices" is showing unauthorized.
I don't know how to proceed. Appreciate your help!
It's solved by plugging the USB cable to USB 2.0 port on the PC
Good to hear it worked out. I was going to suggest installing a driver when in fastboot mode.
How did you get the boot image btw? I've never tried for anything other than a Lineage OS device, for which all the files are easily accesible.
To get the boot image:
1. Get the full firmware form Asus official site: (must get the same version as your current phone)
https://www.asus.com/UK/supportonly/ZenFone 8 (ZS590KS)/HelpDesk_BIOS/
2. Extract payload.bin from the zip file
3. Use Payload Dumper to extract the img files, and you'll find boot.img
note. their are some versions requiring to install Python on your PC. I found this one with executable:
https://ava4.androidfilehost.com/dl...18474/2188818919693785372/Payload_Dumper.zip?
4. Use Magisk to patch boot.img.
Hope this helps.
Please note after flashing the patched boot.img, your phone will be rooted but it fails safetynet. Have to install the module "safetynet-fix-v1.1.0.zip", then everything is fine.
After opening the bootloader and rooting the phone, are there any disadvantages you discovered? Warning screen on boot, (banking) apps not working, etc.?
DerSteppo said:
After opening the bootloader and rooting the phone, are there any disadvantages you discovered? Warning screen on boot, (banking) apps not working, etc.?
Click to expand...
Click to collapse
Yes, there is a warning screen on boot. And yes, some banking apps I use can't be cheated by Magisk Hide, but I use Work profile (via Island) to work around it. So far so good.
dohanin said:
Yes, there is a warning screen on boot. And yes, some banking apps I use can't be cheated by Magisk Hide, but I use Work profile (via Island) to work around it. So far so good.
Click to expand...
Click to collapse
OK thanks for the information!
dohanin said:
To get the boot image:
1. Get the full firmware form Asus official site: (must get the same version as your current phone)
https://www.asus.com/UK/supportonly/ZenFone 8 (ZS590KS)/HelpDesk_BIOS/
2. Extract payload.bin from the zip file
3. Use Payload Dumper to extract the img files, and you'll find boot.img
note. their are some versions requiring to install Python on your PC. I found this one with executable:
https://ava4.androidfilehost.com/dl...18474/2188818919693785372/Payload_Dumper.zip?
4. Use Magisk to patch boot.img.
Hope this helps.
Please note after flashing the patched boot.img, your phone will be rooted but it fails safetynet. Have to install the module "safetynet-fix-v1.1.0.zip", then everything is fine.
Click to expand...
Click to collapse
After rooting, it seems that the official ota update cannot be detected, and it cannot be seamlessly achieved by using the Magisk to install to the unused slot. Is there any other way to achieve the update? For example, OnePlus can choose to install the full ota downloaded from the official website locally.
dohanin said:
To get the boot image:
1. Get the full firmware form Asus official site: (must get the same version as your current phone)
https://www.asus.com/UK/supportonly/ZenFone 8 (ZS590KS)/HelpDesk_BIOS/
2. Extract payload.bin from the zip file
3. Use Payload Dumper to extract the img files, and you'll find boot.img
note. their are some versions requiring to install Python on your PC. I found this one with executable:
https://ava4.androidfilehost.com/dl...18474/2188818919693785372/Payload_Dumper.zip?
4. Use Magisk to patch boot.img.
Hope this helps.
Please note after flashing the patched boot.img, your phone will be rooted but it fails safetynet. Have to install the module "safetynet-fix-v1.1.0.zip", then everything is fine.
Click to expand...
Click to collapse
Ah, thanks that did help. I didn't know the full firmware was available from the site.
yunyou said:
After rooting, it seems that the official ota update cannot be detected, and it cannot be seamlessly achieved by using the Magisk to install to the unused slot. Is there any other way to achieve the update? For example, OnePlus can choose to install the full ota downloaded from the official website locally.
Click to expand...
Click to collapse
Do you mean you already tried this with Zenfone 8 OTA update after rooting? I did it with firmware "WW-30.11.51.67" and it's still the current one, so I don't know whether it would work or not.
dohanin said:
Do you mean you already tried this with Zenfone 8 OTA update after rooting? I did it with firmware "WW-30.11.51.67" and it's still the current one, so I don't know whether it would work or not.
Click to expand...
Click to collapse
I found ota's solution. Download the "WW-30.11.51.67" firmware from the official website and move it to the main storage directory of the phone. Then the phone should detect the update file, but if the phone does not prompt, then try to restart the device. When the phone restarts and enters the system again, the system will detect the update, and there will be an update launcher notification in the notification bar!
When the system update interface is over, when prompted to restart, install to an unused slot through the Magisk option. Select the installation to keep ROOT to achieve seamless ota.
dohanin said:
Yes, there is a warning screen on boot. And yes, some banking apps I use can't be cheated by Magisk Hide, but I use Work profile (via Island) to work around it. So far so good.
Click to expand...
Click to collapse
If you use DRM Info app do you still have Widevine L1 security level? (needed for netflix hd playback) thanks.
grootzy said:
If you use DRM Info app do you still have Widevine L1 security level? (needed for netflix hd playback) thanks.
Click to expand...
Click to collapse
yes, it's showing L1 in Widevine CDM
dohanin said:
yes, it's showing L1 in Widevine CDM
Click to expand...
Click to collapse
Thanks, great news that ASUS are not being dicks with the bootloader unlocking.
For anyone else who isn't too clear on the steps (like me!) - After patching the boot image with magisk you then can use adb to pull that image to a PC and then use adb reboot bootloader and then fastboot boot patched-image.img to check the rooting works without flashing anything and then use adb reboot bootloader again and then fastboot flash boot patched-image.img to write it to the flash memory if everything went smoothly. This worked for me and everything seems great. Obviously you need adb and fastboot set up on your PC for this to work. I'm not sure if this was the intended method but it is what I did.
dohanin said:
Yes, there is a warning screen on boot. And yes, some banking apps I use can't be cheated by Magisk Hide, but I use Work profile (via Island) to work around it. So far so good.
Click to expand...
Click to collapse
did you try hiding magisk manager by changing the magisk manager package name? (it's an option in magisk manager).
some apps detect the magisk manager app to guess rooting.
If you hide magisk app + use magiskhide on the bank app it should be working.
please check let me know
fatjoez said:
did you try hiding magisk manager by changing the magisk manager package name? (it's an option in magisk manager).
some apps detect the magisk manager app to guess rooting.
If you hide magisk app + use magiskhide on the bank app it should be working.
please check let me know
Click to expand...
Click to collapse
hi, yes i tried but while most apps are working fine, some banking apps can still detect root. however, for those apps, if i disable the magisk app beforehand, then it can be passed. i could not figure why since the magisk app is already with a random package name. i posted my query in the magisk forum too.
anyway, with this method, i don't need to use work profile now.
Hi everbody.
I hope someone can help me out.
I unlocked my Zenfone 8 with the official unlock tool and i want to relock the bootloader back.
I was using commands like fastboot oem asus-lock, fastboot flashing lock, but nothing works.
Did Asus changed something in Android 11?
In Android 10 the first command was working without problems.
Thanks
You can't lock it back.
Only to change motherboard.
dron39 said:
You can't lock it back.
Only to change motherboard.
Click to expand...
Click to collapse
Oh that's bad news. Thank you very much for your fast answer.
yunyou said:
When the system update interface is over, when prompted to restart, install to an unused slot through the Magisk option. Select the installation to keep ROOT to achieve seamless ota.
Click to expand...
Click to collapse
Can you explain further on this? Are you saying to install the firmware to an unused slot? What exactly is an unused slot? I haven't seen anything like this in magisk.

Categories

Resources