Related
I read in another thread that I need to 'Just reflash the original boot.img on both a and b to unroot. Log in and then reroot'...how do I do this? I can flash boot.img via fastboot no problem...but how do I switch partitions? Also, this method doesn't result any data loss correct? Was going to do the 'full unroot' option in SuperSU but with the partitions stuff I'm not sure if that will work?
I'm running TWRP RC2 and SuperSU SR3 2.79. Phone is fully setup and functioning other than Snapchat. Went to bed at 5am after taking hours to log into all my apps, configure them again, etc....would HATE to do all that over again...so much that I would stop using Snapchat to avoid it.
Any help would be appreciated.
@blueyes, I saw you help another member out with something similar but not quite...any idea?
You can simply use the in app option it works just fine. Alternatively you can install Magisk without wiping to keep root and bypass Safteynet (will allow you to use Snapchat, Android Pay, etc..) I was running a nearly identical setup to you when I did it. Here's some instructions if you want to try that route https://forum.xda-developers.com/showpost.php?p=71629390&postcount=2394
tdct12 said:
You can simply use the in app option it works just fine. Alternatively you can install Magisk without wiping to keep root and bypass Safteynet (will allow you to use Snapchat, Android Pay, etc..) I was running a nearly identical setup to you when I did it. Here's some instructions if you want to try that route https://forum.xda-developers.com/showpost.php?p=71629390&postcount=2394
Click to expand...
Click to collapse
That certainly sounds better as it will give me the perk of being able to finally use Android Pay. I'll investigate, but worst case I'll do the in-app solution and do the old method of logging in to Snapchat and then re-rooting. Thank you!
tdct12 said:
Quoted from another thread. Anyway I tried it out. Already had Pure Nexus, superuser, twrp RC2, and elementalx installed. Magisk fully working. Here are the steps I followed (no wipe)
Open SuperSu
Uninstall supersu from in app option
Reboot system
Reboot recovery
Flash Magisk zip
Wipe cache/davlik cache
Reboot system (creates bootloop back to recovery)
From twrp switch bootloader slot to the inactive slot
reboot recovery
From twrp switch back to the orignal boot slot
reboot system (these steps end the bootloop for some reason)
You might need to force close your root check app and reopen for it to detect root at first.
edit: Saftey net passed, just checked =)
Click to expand...
Click to collapse
So...I had different results.
When I remove SuperSU from in-app option, my phone was still rooted. It didn't actually unroot. Is that because I told it to not flash the boot.img?
#7 didn't result in a boot loop...proceeding on...
@IlyaKol you do need to let it reflash the original boot.img. Supersu modifies it to achieve root. Magisk is it's own root you probably shouldn't have flashed it until you verified that supersu had been removed. You can still try removing supersu from in app option I have no idea if it will effect magiskSu. After you remove supersu go the Magisk app (the zip installed it) and see if it's still rooted. If not just try reflashing the zip. All you can do is hope it works out. Once it's installed properly you go the app and enable Magisk Hide, there is a Safteynet test in status page along with root status, I will post a screenshot for clarity
tdct12 said:
@IlyaKol you do need to let it reflash the original boot.img. Supersu modifies it to achieve root. Magisk is it's own root you probably shouldn't have flashed it until you verified that supersu had been removed. You can still try removing supersu from in app option I have no idea if it will effect magiskSu. After you remove supersu go the Magisk app (the zip installed it) and see if it's still rooted. If not just try reflashing the zip. All you can do is hope it works out. Once it's installed properly you go the app and enable Magisk Hide, there is a Safteynet test in status page along with root status, I will post a screenshot for clarity
Click to expand...
Click to collapse
Okay, I'm going back to recovery, will flash the Magisk Uninstaller followed by the SuperSU installer. Then I'll go into the app and this time tell it to restore the boot image but NOT the recovery. Right? lol.
That didn't work so I'm trying other methods to remove SuperSU...I'll report back later as I need to get going and will be doing this elsewhere lol.
@IlyaKol rather than reflashing supersu since the root is not removed you should instead just downloaded the supersu apo from the playstore then try removing the supersu root from there. If you get an "error no SuperSU binaries detected" then it is already removed.
tdct12 said:
@IlyaKol rather than reflashing supersu since the root is not removed you should instead just downloaded the supersu apo from the playstore then try removing the supersu root from there. If you get an "error no SuperSU binaries detected" then it is already removed.
Click to expand...
Click to collapse
It's still there even after running other tools found on XDA to try and unroot. I'll just flash the boot image manually when I get back home. Magisk sees it as such, not the Magisk root.
Thanks for the other steps...only remaining question I have is do I need to flash the boot image to both partitions? Or is whatever fastboot defaults to enough? If I do, what's the fastboot command for that?
If you use fastboot make sure it's on your current slot. I can't imagine why the unroot wouldn't work. Did you try clearing app data on your root checking app? Did the actual supersu app from play store detect supersu binaries? You might run into some data loss trying to remove root honestly if no methods are working. If all else fails do a wipe and then just install magisk when you've reinstalled the rom of your choice. I know it's not a pleasant solution but it's a solid last resort.
Eh, @tdct12, I finally caved and just ran flash-all.bat to get back to 100% stock. Third time redoing my entire phone (copying all the data back down such as pictures/videos, music, etc. and logging into each app and signing in, etc.). First time I forgot to unlock the bootloader first, so I had to wipe (DOH!), 2nd time was I didn't log into Snapchat before rooting (DOH^2) and now this is the 3rd time. #thirdtimesacharm
Yesterday (round 2) I finished at 4:45am. It's 1:13am now...so let's see how long the third time takes lol.
This time I added unlocked the BL, flashed TWRP RC2/Magisk 11.6 (from your quote)/ElementalX 1.09 right from the beginning lol. Taking no chances.
Sweet, I hope it works for you this time around!
tdct12 said:
Sweet, I hope it works for you this time around!
Click to expand...
Click to collapse
So far so good. Magisk detected proper root and passed safetynet, allowing Snapchat to login. So I'm golden. Thanks again for the rest of the steps, etc.! Have a good one!
IlyaKol said:
So far so good. Magisk detected proper root and passed safetynet, allowing Snapchat to login. So I'm golden. Thanks again for the rest of the steps, etc.! Have a good one!
Click to expand...
Click to collapse
Glad it worked for you. Would you mind posting your steps on how to get it working. I have been having issues with Magisk passing the safety check. I have flashed to 100% stock as well. I'm also using Pure Nexus if there is something different I have to do since I'm running that. Thanks!
Edit: I have followed the steps listed above after flashing Pure Nexus and it still will not pass safety check.
IlyaKol said:
@blueyes, I saw you help another member out with something similar but not quite...any idea?
Click to expand...
Click to collapse
Are you referring to "fastboot --set-active" a(or b) CMD. Run just fastboot and you'll see the available commands. After switching slots reboot bootloader to assure that you are in the opposite slot.
There's more commands available with fastboot oem... To see those (in Linux, i don't use Windows) pull your aboot.img and run "strings aboot.img | grep oem
GallardosEggrollShop said:
Glad it worked for you. Would you mind posting your steps on how to get it working. I have been having issues with Magisk passing the safety check. I have flashed to 100% stock as well. I'm also using Pure Nexus if there is something different I have to do since I'm running that. Thanks!
Edit: I have followed the steps listed above after flashing Pure Nexus and it still will not pass safety check.
Click to expand...
Click to collapse
Basically, the gist of what I did after I gave up and accepted the fact that I'd have to go back to 100% stock and rebuild my setup again:
1) Flash to 100% stock using Flash-All.bat from the Factory Image (using ADB/Fastboot tools)
2) Boot into the OS
3) Next I enabled developer options, allowed USB debugging and allowed for the bootloader to be unlocked
4) Plugged the phone into the PC, accepted the ADB fingerprint
5) Opened the platform-tools directory in my command window
6) Rebooted to the bootloader via 'adb reboot bootloader' command
7) Booted to TWRP using the 'fastboot boot *insert TWRP image name*' command (I used one of the alpha versions)
8) First thing I did in "Temp TWRP" was I flashed TWRP RC2 permanently and rebooted back to recovery
9) I then installed Magisk v11.6 (I did not have to do any of the additional steps to fix any bootloops with changing the boot slot, etc....might be a 7.1.2 thing vs 7.1.1, etc.)
10) *Optional* I flashed ElementalX 1.09 for Pixel
11) Wiped cache/dalvik (cache doesn't seem to wipe because it can't find /cache?)
12) Rebooted to system
13) In the Magisk Manager app, go to Settings and make sure "Enable BusyBox" and "Magisk Hide" are enabled.
14) Run the SafetNet check. It should pass.
DO NOT UPDATE TO v12.0 as I guess it's not ready for Pixel's yet.
blueyes said:
Are you referring to "fastboot --set-active" a(or b) CMD. Run just fastboot and you'll see the available commands. After switching slots reboot bootloader to assure that you are in the opposite slot.
There's more commands available with fastboot oem... To see those (in Linux, i don't use Windows) pull your aboot.img and run "strings aboot.img | grep oem
Click to expand...
Click to collapse
Thanks. I ended up finding the option on how to do that in TWRP and then later fastboot as well...all is well that ends well. Loving my new phone.
I am planning to root and use api2 for gcam. Will I receive updates after that? Also would those updates install successfully if rooted? If not any idea on how to just get api2. Can I UNROOT the device and will that install updates successfully?
No.
The thing you can do is that you install September ROM with MiFlash, then you get update. (You can install September ROM without loosing data.)
At the moment there is no way to keep root after update using current tools.
You will receive updates after root. I was on rooted September patch and I have successfully installed October OTA update. Just follow these steps and you'll be good to go.
Download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Enter fastboot mode on your device. I am assuming you know how to unlock your bootloader and you have all the ADB drivers installed.
I suggest you NOT to flash TWRP but boot to it instead. To do so type
Code:
fastboot boot recovery.img
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; While pressing vol down button connect the USB cable. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP and reboot to system.
Download the latest Magisk Manager and install. DO NOT update Magisk.
Use this module to get camera2 api.
Download and install normally when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Ex-Hunter said:
[*]Download the latest Magisk Manager and install. DO NOT update Magisk.
Click to expand...
Click to collapse
Hi, i have some mistake at this point, if i try to install newer magisk manager i cant because "i have another app with the same name", so what? using magisk 13.3 with the manager 5.1.1 provided by itself to active the cameras module? thanks
---------- Post added at 10:22 PM ---------- Previous post was at 10:21 PM ----------
[/COLOR]
Ex-Hunter said:
You will receive updates after root. I was on rooted September patch and I have successfully installed October OTA update. Just follow these steps and you'll be good to go.
Download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Enter fastboot mode on your device. I am assuming you know how to unlock your bootloader and you have all the ADB drivers installed.
I suggest you NOT to flash TWRP but boot to it instead. To do so type
Code:
fastboot boot recovery.img
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; While pressing vol down button connect the USB cable. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP and reboot to system.
Download the latest Magisk Manager and install. DO NOT update Magisk.
Use this module to get camera2 api.
Download and install normally when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
-----------------------------------------------------------------------------------------------------------------------
just a question: it's possible to edit build.prop via adb with twrp "live" without installing it?!
in this case, I could just edit it to enable camera2 api without rooting or installing twrp..
Click to expand...
Click to collapse
How to enable Camera2api after rooting with magisk? Please inform
n6i5k7h5 said:
I am planning to root and use api2 for gcam. Will I receive updates after that? Also would those updates install successfully if rooted? If not any idea on how to just get api2. Can I UNROOT the device and will that install updates successfully?
Click to expand...
Click to collapse
I just got a MiA1.I know how to root it with magisk but don't know how to enable camera2api.Will you please help me?
Flare_91 said:
Hi, i have some mistake at this point, if i try to install newer magisk manager i cant because "i have another app with the same name", so what? using magisk 13.3 with the manager 5.1.1 provided by itself to active the cameras module? thanks
Click to expand...
Click to collapse
You should use Magisk 13.4 for pixel not Magisk 13.3. Download it from here.
After flashing install this.
If you get any error, uninstall Magisk Manager--just the manager and install the downloaded apk. There shouldn't be any problems.
Chazy12 said:
just a question: it's possible to edit build.prop via adb with twrp "live" without installing it?!
in this case, I could just edit it to enable camera2 api without rooting or installing twrp..
Click to expand...
Click to collapse
It should be possible. But I am wary of editing system partition because it might interfere with OTA updates and SafetyNet check.
Take a backup of system partition using TWRP just to be safe and proceed with editing.
Kindly report here if it works. Goodluck!:fingers-crossed:
Kripacharya said:
I just got a MiA1.I know how to root it with magisk but don't know how to enable camera2api.Will you please help me?
Click to expand...
Click to collapse
Sure, just follow the steps I have written above. You'll definitely be able to enable camera2 api and more!
Ex-Hunter said:
You should use Magisk 13.4 for pixel not Magisk 13.3. Download it from here.
After flashing install this.
If you get any error, uninstall Magisk Manager--just the manager and install the downloaded apk. There shouldn't be any problems.
It should be possible. But I am wary of editing system partition because it might interfere with OTA updates and SafetyNet check.
Take a backup of system partition using TWRP just to be safe and proceed with editing.
Kindly report here if it works. Goodluck!:fingers-crossed:
Sure, just follow the steps I have written above. You'll definitely be able to enable camera2 api and more!
Click to expand...
Click to collapse
Thanks for the answer.
It's only a line of code.. I hope there'll be not a problem for just one line..
Inviato dal mio Mi A1 utilizzando Tapatalk
Ex-Hunter said:
Yure, just follow the steps I have written above. You'll definitely be able to enable camera2 api and more!
Click to expand...
Click to collapse
Ok, so I have Magisk 13.4 and manager app 5.4.0, and when I install camera module and restart it doesn't get that line written in build.prop so it doesn't work. In magisk it says that is installed. Is there something additional that has to be done or ?
Ex-Hunter said:
You should use Magisk 13.4 for pixel not Magisk 13.3. Download it from here.
After flashing install this.
If you get any error, uninstall Magisk Manager--just the manager and install the downloaded apk. There shouldn't be any problems.
Click to expand...
Click to collapse
Yes, my mistake i was already on 13.4 so i have unistalled magisk manager and then i have installed the latest version.
NITRO_100 said:
Ok, so I have Magisk 13.4 and manager app 5.4.0, and when I install camera module and restart it doesn't get that line written in build.prop so it doesn't work. In magisk it says that is installed. Is there something additional that has to be done or ?
Click to expand...
Click to collapse
Me too and i have add the lines manually then its ok for me.
Ex-Hunter said:
You will receive updates after root. I was on rooted September patch and I have successfully installed October OTA update. Just follow these steps and you'll be good to go.
Download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Enter fastboot mode on your device. I am assuming you know how to unlock your bootloader and you have all the ADB drivers installed.
I suggest you NOT to flash TWRP but boot to it instead. To do so type
Code:
fastboot boot recovery.img
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; While pressing vol down button connect the USB cable. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP and reboot to system.
Download the latest Magisk Manager and install. DO NOT update Magisk.
Use this module to get camera2 api.
Download and install normally when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Click to expand...
Click to collapse
So the only difference for now (hope the good guys here will solve this) is that we can use twrp but only in temporary way using " boot" command and not "flash" then use the known progress and install root etc etc etc... Can this guide work in a vanilla out of the box phone with the October patch on it ?
To reboot to bootloader then boot to twrp install root then reboot then all ok ? Or you have to set a partition first
Thanks again for the help
nikkpap said:
So the only difference for now (hope the good guys here will solve this) is that we can use twrp but only in temporary way using " boot" command and not "flash" then use the known progress and install root etc etc etc... Can this guide work in a vanilla out of the box phone with the October patch on it ?
To reboot to bootloader then boot to twrp install root then reboot then all ok ? Or you have to set a partition first
Thanks again for the help
Click to expand...
Click to collapse
Yes it will work. No need to set a partition.
enricogrim said:
Hi, I followed your guide but when I boot to TWRP I can see only empty folder in the internal memory and I can't select the sd card. What was my mistake?
thank you very much
Click to expand...
Click to collapse
Do you use any PIN/password? If so, you have to input it when the TWRP boots up.
Ex-Hunter said:
You will receive updates after root. I was on rooted September patch and I have successfully installed October OTA update. Just follow these steps and you'll be good to go.
Download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Enter fastboot mode on your device. I am assuming you know how to unlock your bootloader and you have all the ADB drivers installed.
I suggest you NOT to flash TWRP but boot to it instead. To do so type
Code:
fastboot boot recovery.img
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; While pressing vol down button connect the USB cable. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP and reboot to system.
Download the latest Magisk Manager and install. DO NOT update Magisk.
Use this module to get camera2 api.
Download and install normally when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Click to expand...
Click to collapse
Hi,
Have you tried using the newer Magisk V14.2 (1420) to root MI A1?
Thanks and best regards!
William
cmk7128 said:
Hi,
Have you tried using the newer Magisk V14.2 (1420) to root MI A1?
Thanks and best regards!
William
Click to expand...
Click to collapse
Yes, but unfortunately it doesn't work and the device will be stuck in a bootloop. @topjohnwu is working towards a fix. I'm sure we'll get the official Magisk on our device pretty soon.
Ex-Hunter said:
Yes, but unfortunately it doesn't work and the device will be stuck in a bootloop. @topjohnwu is working towards a fix. I'm sure we'll get the official Magisk on our device pretty soon.
Click to expand...
Click to collapse
Thanks for the feedback, much appreciated. BTW, do we have to fastboot flash the original/unpatched boot image before we proceed to download and install the new security update patch (eg. Oct to Nov 2017 update)?
Thanks!
William
cmk7128 said:
Thanks for the feedback, much appreciated. BTW, do we have to fastboot flash the original/unpatched boot image before we proceed to download and install the new security update patch (eg. Oct to Nov 2017 update)?
Thanks!
William
Click to expand...
Click to collapse
No, no need to flash the original boot img if you are already rooted with Magisk. Just download and install the update normally, but make sure to flash Magisk afterwards to get root back.
Ex-Hunter said:
No, no need to flash the original boot img if you are already rooted with Magisk. Just download and install the update normally, but make sure to flash Magisk afterwards to get root back.
Click to expand...
Click to collapse
Yes, I am rooted with Magisk v13.4 as per your steps. Thanks again.
Best regards!
William
Ex-Hunter said:
You will receive updates after root. I was on rooted September patch and I have successfully installed October OTA update. Just follow these steps and you'll be good to go.
Download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Enter fastboot mode on your device. I am assuming you know how to unlock your bootloader and you have all the ADB drivers installed.
I suggest you NOT to flash TWRP but boot to it instead. To do so type
Code:
fastboot boot recovery.img
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; While pressing vol down button connect the USB cable. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP and reboot to system.
Download the latest Magisk Manager and install. DO NOT update Magisk.
Use this module to get camera2 api.
Download and install normally when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Click to expand...
Click to collapse
Just asking after rooted, can I re-lock the bootloader again? In order to pass safetynet?
soralz said:
Just asking after rooted, can I re-lock the bootloader again? In order to pass safetynet?
Click to expand...
Click to collapse
If I'm not mistaken it will pass safetynet if you are rooted with magisk.
Sent from my Mi A1 using Tapatalk
Hey guys, I just recently did a systemless root of my pixel 2 XL and I haven't been able to get it to bypass safetynet, the only app I use right now that requires root is Adaway and I had tested to see if it was causing the trouble by uninstalling it which has proven fruitless, any ideas on how to get past safetynet would be great, even if it means rooting my phone again differently.
Are you running a custom kernel?
Custom kernels will hide the bootloader unlock from SafetyNet
Is there a particular app you need to hide root from? if so you can do this with Magisk Hide in Magisk Manager
Pyr0x64 said:
Are you running a custom kernel?
Custom kernels will hide the bootloader unlock from SafetyNet
Is there a particular app you need to hide root from? if so you can do this with Magisk Hide in Magisk Manager
Click to expand...
Click to collapse
I'm not running a custom kernel, and the apps I want to use won't work even if root is hidden, one's my banking app for my bank back in england.
If you flash a custom kernel to hide the bootloader unlock, you should pass safetynet.
For your banks app to work, you need to pass safetynet and hide root
I'm running magisk with Flash kernel. My phone passes safety net and under Magisk Hide, I've selected my Halifax banking app so it works.
Pyr0x64 said:
If you flash a custom kernel to hide the bootloader unlock, you should pass safetynet.
For your banks app to work, you need to pass safetynet and hide root
I'm running magisk with Flash kernel. My phone passes safety net and under Magisk Hide, I've selected my Halifax banking app so it works.
Click to expand...
Click to collapse
Same here with Flash Kernel and Magisk Hide. Safetynet passes.
Edit: I'm running beta Magisk but regular v16 works too
Pyr0x64 said:
If you flash a custom kernel to hide the bootloader unlock, you should pass safetynet.
For your banks app to work, you need to pass safetynet and hide root
I'm running magisk with Flash kernel. My phone passes safety net and under Magisk Hide, I've selected my Halifax banking app so it works.
Click to expand...
Click to collapse
henderjr said:
Same here with Flash Kernel and Magisk Hide. Safetynet passes.
Edit: I'm running beta Magisk but regular v16 works too
Click to expand...
Click to collapse
Okay, I'll try doing that, will update on the results
No luck, it all flashed fine but it's still not working.
EDIT: I don't know why my screenshot is so big.
Are you using Xposed?
No, I'm not using xposed
Brawler6216 said:
No luck, it all flashed fine but it's still not working.
EDIT: I don't know why my screenshot is so big.
Click to expand...
Click to collapse
Why are you flashing the dtbo.img???
Badger50 said:
Why are you flashing the dtbo.img???
Click to expand...
Click to collapse
Because is says so in the directions
Images (installation and upgrade):
Install the latest adb and fastboot:*https://developer.android.com/studio...orm-tools.html
Grab the boot and dtbo images from the download site above
(OPTIONAL) Patch the boot image with*Magisk*if so desired
Reboot into the bootloader using either restart and hold power button and volume down or adb:
Code:
adb reboot bootloader
Flash the boot image. Run the following command in the folder with the boot image and ensure fastboot is in your PATH:
Code:
fastboot flash boot <boot_image_name>.img
Do the same with the dtbo image:
Code:
fastboot flash dtbo <dtbo_image_name>.img
???
Reboot and profit!
Sent from my Pixel 2 XL using Tapatalk
gjkrisa said:
Because is says so in the directions
Images (installation and upgrade):
Install the latest adb and fastboot:*https://developer.android.com/studio...orm-tools.html
Grab the boot and dtbo images from the download site above
(OPTIONAL) Patch the boot image with*Magisk*if so desired
Reboot into the bootloader using either restart and hold power button and volume down or adb:
Code:
adb reboot bootloader
Flash the boot image. Run the following command in the folder with the boot image and ensure fastboot is in your PATH:
Code:
fastboot flash boot <boot_image_name>.img
Do the same with the dtbo image:
Code:
fastboot flash dtbo <dtbo_image_name>.img
???
Reboot and profit!
Click to expand...
Click to collapse
Did it work?
Flash your system back to stock with the flash all bat file. Remove the -w from the bat file to save data.
Copy the magisk zip to your downloads folder.
Remove your pin and fingerprint.
Boot to twrp and install the magisk zip.
Reboot.
Check if the magisk app is installed, if it isn't grab the APK from inside the zip and install it. If you had to install it, reboot once more.
That is exactly what I do each time and I have root and I pass saftey net. Just did it a couple of hours ago.
---------- Post added at 03:03 AM ---------- Previous post was at 02:53 AM ----------
And while you are at it, grab 16.2 from the Beta thread.
Badger50 said:
Why are you flashing the dtbo.img???
Click to expand...
Click to collapse
That's what the installation instructions were for installing flash kernel...?
I will point out I'm not anywhere near well versed in this.
Brawler6216 said:
That's what the installation instructions were for installing flash kernel...?
I will point out I'm not anywhere near well versed in this.
Click to expand...
Click to collapse
The post right before your by TonikJDK laid it out perfectly for you. It's exactly the same procedure I use. And SN passes just fine for me as well :good:
Badger50 said:
The post right before your by TonikJDK laid it out perfectly for you. It's exactly the same procedure I use. And SN passes just fine for me as well :good:
Click to expand...
Click to collapse
K, I'll try his instructions, but I've not done it with twrp, so that'll be new to me.
Brawler6216 said:
K, I'll try his instructions, but I've not done it with twrp, so that'll be new to me.
Click to expand...
Click to collapse
Gotta learn sometime my friend. It's not near as hard as you might think. Here's a little more detail for you if it helps :good:
TonikJDK said:
Flash your system back to stock with the flash all bat file. Remove the -w from the bat file to save data.
Copy the magisk zip to your downloads folder.
Remove your pin and fingerprint.
Boot to twrp and install the magisk zip.
Reboot.
Check if the magisk app is installed, if it isn't grab the APK from inside the zip and install it. If you had to install it, reboot once more.
That is exactly what I do each time and I have root and I pass saftey net. Just did it a couple of hours ago.
---------- Post added at 03:03 AM ---------- Previous post was at 02:53 AM ----------
And while you are at it, grab 16.2 from the Beta thread.
Click to expand...
Click to collapse
Badger50 said:
Gotta learn sometime my friend. It's not near as hard as you might think. Here's a little more detail for you if it helps :good:
Click to expand...
Click to collapse
It passed! Awesome thank you, guys so much!!
Brawler6216 said:
It passed! Awesome thank you, guys so much!!
Click to expand...
Click to collapse
Congrats my friend. Well done! ???
Now you just need to dark theme that sucker! ?
Badger50 said:
Congrats my friend. Well done!
Now you just need to dark theme that sucker!
Click to expand...
Click to collapse
When you're too excited that it passed safetynet
So today with some testers i managed to make root on OnePlus 7T, I want to specify that 95% of the work was done by @topjohnwu (Magisk creator). For now you should use only Magisk Canary files
I will explain 2 different guides:
First Root Guide:
This guide is for a specific rom version, so you will need to use a specific patched boot.img
- Download the patched_boot.img
- Reboot your device in bootloader-fastboot mode
- Flash the patched_boot.img in the boot partition:
Code:
fastboot flash boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
Second Root Guide:
This guide is more generic than the first one, you should use this one if you are unable to find a specific patched boot.img
- Download a patched_boot.img (you should try with the latest one)
- Reboot your device in bootloader-fastboot mode
- Boot the patched_boot.img:
Code:
fastboot boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
- Click on Install, then direct install and wait the end of the process
- Reboot the device
Third Root Guide:
Guide by @gpz1100
TIPS:
Actually you should use only Magisk canary files Magisk 20.3
You can get the stock boot images from the fastboot rom: https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
Actually i'm using magisk manager canary and magisk canary debug to patch the boot.img, I don't recommend updating magisk, if you don't want to see the updates install the normal magisk manager
Magisk 20.3 fully support OnePlus 7T and 7T Pro
HOW TO UPDATE a ROM and KEEP ROOT:
Before all Disable all magisk modules
Be sure to use Canary Magisk Manager and Canary Magisk (debug)
You can update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
Download:
Patched/Stock Boot Images: https://www.androidfilehost.com/?w=files&flid=300177
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Donations:
Credits:
@RohanAJoshi
Flashed and working flawless.
Really thanks for this.
Awesome work bro.
Can you please upload the patched boot.img please? I dont see it in the above folder at all.
nick_22 said:
Can you please upload the patched boot.img please? I dont see it in the above folder at all.
Click to expand...
Click to collapse
Done, i uploaded them using ftp and i forgot to move the files in the right folder
Working, thanks a lot @mauronofrio
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
See OP, its clearly mentioned there. You have to flash this via fastboot and not any custom recovery. Firstly setup adb on your PC and then check the commands. Its very easy. Do some googling and still if its difficult for you, come back and ask.
jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
Welcome to the android scene, reminds me of the old psx scene
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
Get your stock boot.img from 1st post.
Reboot to bootloader.
And do this command
fastboot flash boot boot.img
fastboot reboot
Device will boot unrooted.
---------- Post added at 05:58 AM ---------- Previous post was at 05:55 AM ----------
jesrani;80464121 [user=4712355 said:
@mauronofrio[/user], thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.
RohanAJoshi said:
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.
Click to expand...
Click to collapse
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
jesrani said:
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
In older devices like OP5T it happens like this, not in newer devices. OP7T has seamless updates, its installs while device is turned on in second partition.
nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
jesrani said:
@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
jesrani said:
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
Canary debug, don't update it
Help please. I have returned to Android after 5years with OnePlus 7t and trying to root it. I am trying this method but not being able to successfully root it. Steps I have tried
Went to fastboot mode by restarting the phone but I don't get an option to install the patched image file. And even boatloader is locked. Do I need to unlock the bootloader. And I unlock will I loose my data. Sorry for silly question I have completely forgot about Android.
Thanks, rooted successfully
?
To be honest need video tutorial asap?
mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Ok. Got it. So, I have already booted back to unrooted mode now. And I cant wipe my data again. Thanks for your response.
Hello i found a little way for have root & and working xposed with no bug on last firmware WW_17.1810.1910.73 & WW_17.1810.1911.110
Stock Recovery
You need adb drviers and unlocked ZenFone 6 on WW_17.1810.1910.73 or WW_17.1810.1911.110
First install last Magisk Manager
Open setting of Magisk and add custom update channel https://github.com/solohsu/magisk_files#custom-update-channel
Download ZenFone6RootXposed-10.73.img or ZenFone6RootXposed-11.110 (i have add stock boot11.110.img, we will need it for next update)
http://www.mediafire.com/folder/skzceszqu8d3j/AsusZenFone6
Now reboot device to bootloader
Code:
adb reboot bootloader
And boot with ZenFone6RootXposed-10.73.img or ZenFone6RootXposed-11.110 (not flash it, your device have a chance to bootloop)
Code:
fastboot boot ZenFone6RootXposed-10.73.img
Code:
fastboot boot ZenFone6RootXposed-11.110.img
The devices reboot automaticly
Go to Magisk and install Magisk, choose direct install
Reboot and Enjoy root
if you want Xposed flash it with magisk :
Riru Core
I use YAHFA
Android 10 ElderDrivers Xposed
And the manager
Xposed Installer​
Good morning
I have tried several times root for Android 10
The Magisk part works smoothly, but the Xposed part never works, producing a bootloop
I have extracted the boot and applied magisk, loaded the Riru Core module, but when loading ElderDrivers, the phone stays in bootloop
Do you know what the reason may be?
Works splendid, great guide!
Tried to use Sandhook first, but ended up with YAHFA instead due some xposed problems (xposed not detected).
Had an old version of Android 9, so i first upgraded it to "UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1" (only supported upgrade path - 9 to 10), then to "UL-ASUS_I01WD-ASUS-17.1810.1910.73-1.1.1-user" (your specified .73)
- Later patching with your img
Thanks
it is impossible
Starting with .73 stock
at the moment I install Riru Yahfa, following the manual, it does not start again, unless install the official boot
the device stays on the Zenfone boot screen without doing anything else
I have tried the version supplied by Magisk, I don't know if you have tried another version
Why will we need the stock boot for the next update? We can't make menully update after root? I just want to make root not install xposed.
Sent from my ASUS_I01WD using Tapatalk
thanks a lot, this a really easy way to get root, but i have a little issue, i had my phone with NO pin code or fingerprint before using this method, and now if i want to ad a pin, password or gesture it simply does not get saved, every time i do the procedure to set the pin it does like if i did nothing, anyone has this issue, or know how to fix it, is there a problem if i hard reset?
any help will be good
In the latest build .110 ctsprofile is false while basicintegrity is true. Is it due to the root or the rom has not been signed by google?
Rom1995 said:
In the latest build .110 ctsprofile is false while basicintegrity is true. Is it due to the root or the rom has not been signed by google?
Click to expand...
Click to collapse
https://zentalk.asus.com/en/discussion/comment/35355/#Comment_35355
baster72 said:
Why will we need the stock boot for the next update? We can't make menully update after root? I just want to make root not install xposed.
Sent from my ASUS_I01WD using Tapatalk
Click to expand...
Click to collapse
just flash ZenFone6RootXposed-10.73 or ZenFone6RootXposed-11.110 and you willl have it
hdsporty50 said:
Good morning
I have tried several times root for Android 10
The Magisk part works smoothly, but the Xposed part never works, producing a bootloop
I have extracted the boot and applied magisk, loaded the Riru Core module, but when loading ElderDrivers, the phone stays in bootloop
Do you know what the reason may be?
Click to expand...
Click to collapse
hdsporty50 said:
it is impossible
Starting with .73 stock
at the moment I install Riru Yahfa, following the manual, it does not start again, unless install the official boot
the device stays on the Zenfone boot screen without doing anything else
I have tried the version supplied by Magisk, I don't know if you have tried another version
Click to expand...
Click to collapse
Don't flash Xposed using Magisk Download, flash it manualy :
EdXposed v0.4.6.0_beta
You will always get bootloop with v0.4.5.1_beta
_______________________________________
UPDATE for 11.110
flash boot.10.73.img for update safe
And do the same with 11.110 files.
Don't forget to add custom update channel in Magisk
And use v0.4.6.0_beta for xposed
Why can't we have any YouTube guides for anything related to this phone?
vernj123 said:
Why can't we have any YouTube guides for anything related to this phone?
Click to expand...
Click to collapse
I want to do it but I don't have another device to record.
Someone try this method to install xposed? I afraid to get bootloop.
Sent from my ASUS_I01WD using Tapatalk
Hi everyone, I hope somebody can help me out to solve an issue I just got with my zenfone,
After using an advise from DaConcho for getting back screen lock after unlocking bootloader I got in another situation.
I followed the instructions from the post and everything was going fine, I boot thought adb with the provided patched boot for Q .110 and that far no issues , when I open magisk manager to download magisk from the alternative source magisk manager prompt to complete the installation downloading some necessary files, not the magisk version, just said some files, and I click yes, then it installed something and reboot, phone started fine, but when I wanted to start the process again I found out that I loose PC connectivity.
I have no connection at all, even if I manually boot in bootloader I can't connect to PC, so no adb commands,
Please can someone help
does someone has the patched boot image for new .119 firmaware, i updated and losee magisk
baster72 said:
Someone try this method to install xposed? I afraid to get bootloop.
Click to expand...
Click to collapse
Don't be afraid just flash stock boot if you get bootloop
joesa said:
does someone has the patched boot image for new .119 firmaware, i updated and losee magisk
Click to expand...
Click to collapse
I update my links you can get stock boot here Boot & RootedBoot ZenFone6
MystikMan97130 said:
Don't be afraid just flash stock boot if you get bootloop
I update my links you can get stock boot here Boot & RootedBoot ZenFone6
Click to expand...
Click to collapse
Thanks a lot !!! You really help a lot with this method
MystikMan97130 said:
Don't be afraid just flash stock boot if you get bootloop
I update my links you can get stock boot here Boot & RootedBoot ZenFone6
Click to expand...
Click to collapse
can you please check link, it is not working, i can see folder but can not download
Hello, direct link:
ZenFone6RootXposed
Nice, thanks a lot for this! Rooting on stock with unlocked bootloader worked for me perfectly (did not check xposed)!
est-ce que l'on perd ses données en faisant le root ?
merci!