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.
Related
I rooted my galaxy S6 a couple of days ago and wow was it totally worth tripping Knox, any way I am writing this because I could not find a thread that had a guide usng these methods. I had to figure out how to get past several errors in TWRP and Magisk and I thought some people might be curious how I did it. I did not make any of these programs used, credit to the original authors. I did this so I could play Pokemon Go with root.
WARNING: THIS WILL TRIP KNOX AND MAY BRICK YOUR PHONE. DO THIS AT YOUR OWN RISK I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS. MAKE SURE YOU HAVE A FULL BACKUP OF YOUR DEVICE BEFORE CONTINUING. THIS WILL ALSO DISABLE OTAS.
Prerequisites:
Odin (make sure its version 3.10.6 others may not work): https://androidmtk.com/download-odin-downloader-versions
Galaxy s6 (have not tested on edge)
TWRP in .tar format for your model: https://dl.twrp.me/zerofltespr/
Stock ROM in case you mess up
Windows PC
Magisk v11.1: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Magisk manager: https://play.google.com/store/apps/details?id=com.topjohnwu.magisk&hl=en
Installing TWRP:
1.) Download all the necessary files and extract Odin to your desk top.
2.) Go into developer mode on your phone and enable OEM unlocking and USB debugging.
3.) Turn off your phone and enter download mode by holding power button, home button and volume down until the screen comes up that says something along the lines of installing a custom OS is dangerous, push volume up to continue.
4.) Plug your phone into your computer and start Odin.exe.
5.) Make sure Odin says "added" in the text window.
6.) Click on AP and browse for the TWRP .tar that you downloaded in the beginning.. Check the box next to AP once TWRP is loaded, then click "Start".
A.) If TWRP fails to install go to "options" and un-check "auto reboot". If this is un-checked make sure to reboot into recovering when Odin says "reset" by first exiting download mode by repeating the steps used to get into it and then holding home, power button and volume up until the TWRP logo appears.
7.) Congratulations you have now installed TWRP!
Rooting and installing Magisk:
1.) This will not work unless you have followed my previous steps.
2.) Make sure your phone is in recovery mode by holding power button, home, and volume up until the TWRP logo appears.
3.) Make sure your PC recognizes the phone and copy the Magisk 11.1 .Zip you downloaded earlier.
4.) Tap install on TWRP and and browse for the Magisk 11.1 .Zip, swipe to install.
5.) When it is done installing tap reboot.
6.) When your phone is done rebooting install Magisk manager from the play store.
7.) When you open Magisk it should say rooted with MAGISKSU in the center box.
A.) If it does not say that flash Magisk 11.1 in TWRP again.
B.) If the above does not work re-flash to stock and repeat all steps again.
8.) You are now rooted.
A.) If you would like to use Magisk hide tap the first box where it says install Magisk and follow the onscreen instructions.
1.) You can try rebooting your phone when it asks you too, but it would not install this way for me.
B.) After you have installed Magisk Framework, go into to settings and enable the hide Magisk option.
C.) Go back to the status section and tap on safety net check, it should be a green check-mark
1.) If it is not green restart and install Magisk again, then go into settings and disable and re-enable Magisk hide.
2.) If it is not green after doing the above re-flash the stock ROM and start over.
9.) You will have to reinstall Magisk Framework every-time you reboot, your root should stay installed after a reboot though.
That is the wrong version of TWRP for a Sprint phone. The correct version is here: https://dl.twrp.me/zerofltespr/
There is a thread with links to the latest stock TAR files, correct version of TWRP for this phone and SuperSU here: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
koop1955 said:
That is the wrong version of TWRP for a Sprint phone. The correct version is here: https://dl.twrp.me/zerofltespr/
There is a thread with links to the latest stock TAR files, correct version of TWRP for this phone and SuperSU here: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
Click to expand...
Click to collapse
Thanks for pointing that out.
hmm, may I ask what advantages we get from this root method?
thank you.
You can hide your root and play Pokemon Go XD. I just think its more convientant having all my control apps super su and busy box in one place.
Sent from my SM-G920P using Tapatalk
Thank you for this.!!!!!!!!! 10/10
joej191 said:
Thank you for this.!!!!!!!!! 10/10
Click to expand...
Click to collapse
Your welcome. Glad I could help.
Sent from my SM-G920P using Tapatalk
Is magisk supposed to be installed after every reboot, or is that one of the many G920p specific issues?
I believe it is a GP20 specific issue because I have install mine after every reboot.
flett044 said:
I believe it is a GP20 specific issue because I have install mine after every reboot.
Click to expand...
Click to collapse
I just read this on the OP magisk thread: "magisk doesn't play well with Samsung devices. Try a custom kernel"
So i flashed the skyhigh kernel and now magisk is surviving restarts... the trouble is, Skyhigh auto intalls supersu and busybox.
Supersu isn't compatible with magisk, and i THINK that kind of busybox fails safetynet.
... so i used the busybox app to Uninstall busybox and the supersu app to do a full unroot and mount the stock boot image. (All to see if I could get magisk fully working) Then wipe davlik/cache, flashed the magisk.zip... booted up and opened the magisk manager, magisk was still installed, and magisksu was "properly installed"... but i fail safetynet attest now so i don't know what thats about.
Wondering if any of the veterans can chime in about any of this, since magisk indeed is pretty glitchy on the stock kernel.
Tl;dr: magisk doesn't work well with stock kernel, not sure how to get it working with custom kernel
I would also like to learn how to install magisk in sky high kernal.
Hey @tdhite do you have any input on this? I assume it would break synapse support to use magisk and magiskSu instead of supersu and the normal busybox, but worth it.
Quick recap: trying to run a magisk set-up with a custom kernel. Presumably using magiskSu.
still work?
@flett044,
Does this hidden root option still work with latest version of Pokemongo?
thanks
Yes it still works.
Nye-uhls said:
Hey @tdhite do you have any input on this? I assume it would break synapse support to use magisk and magiskSu instead of supersu and the normal busybox, but worth it.
Quick recap: trying to run a magisk set-up with a custom kernel. Presumably using magiskSu.
Click to expand...
Click to collapse
The boot routines currently use a policy tool specifically provided by SuperSu which is not available in Magisk. Access to files needed by various processes executed periodically (cortexbrain, cron jobs and others) may fail, but that would not be a critical failure, just a 'bummer' in the worst case. The startup routine is smart enough to check the policy tools and will cleanly boot even if SuperSu's tools aren't around.
Long story short, the kernel should work fine, you'll just miss out on certain things that try to run now and then to 'tune' the system.
How would I go about replacing supersu with Magisk?
tdhite said:
The boot routines currently use a policy tool specifically provided by SuperSu which is not available in Magisk. Access to files needed by various processes executed periodically (cortexbrain, cron jobs and others) may fail, but that would not be a critical failure, just a 'bummer' in the worst case. The startup routine is smart enough to check the policy tools and will cleanly boot even if SuperSu's tools aren't around.
Long story short, the kernel should work fine, you'll just miss out on certain things that try to run now and then to 'tune' the system.
Click to expand...
Click to collapse
That sounds like a pretty solid explanation for what happened when i tried running stock with skyhigh kernel and magisk.
Huge hit to battery life, and i still failed safetynet. Probably because the system showed i was using a custom kernel? I haven't been able to figure out a good way to mask that...
Anyways, good luck with implementing magisk like you said you would! I'm sure it won't be easy! You better have paypal links littered in the release post, you'll deserve it
What is the difference between Magisk and SuperSU?
JoeFCaputo113 said:
What is the difference between Magisk and SuperSU?
Click to expand...
Click to collapse
So I'm not super technical so i hope someone corrects me if i misrepresent this...
Magisk itself is basically a framework (think like xposed) except it functions from OUTSIDE of the system partition. Its only compatible with MagiskSU (a modified version of phh's superuser), magisksu is also not installed on the system partition...
Through magisk manager you can enable root, which as i understand, puts MagiskSU in the system partition in a sort of ghosted way, so its not really there? (As you can see I'm fuzzy on this part) And a step further, even with root still enabled, magisk can hide magisk and magiskSu's presence entirely from chosen apps (it automatically hides from play services so you pass safetynet)
So plain and simple, it theoretically works the same as supersu with the added benefit of being able to fully and effectively hide root...
There's still a lot of work to be done to reach it's full potential, especially in regards to compatibility with vendors and apps, but the dev believes magisk can do a lot eventually... including genuine multi-rom support.
https://www.xda-developers.com/magi...es-samsung-bugs-adds-core-only-mode-and-more/
Good news! Magisk update specifically for samsung devices! I can't wait to try this out!
I'm having a rather difficult time rooting my device and I can't seem to figure out why.
I have unlocked my bootloader, installed the adb drivers and used "fastboot boot boot-to-root.img" to boot the image to my Google Pixel. The instructions indicate that my device should now be rooted.
But when I try and check it's still unrooted.
Does anyone know what I'm doing wrong/missing?
Boot to root is outdated. Fastboot boot twrp and use it to install supersu
WafflesNL said:
I'm having a rather difficult time rooting my device and I can't seem to figure out why.
I have unlocked my bootloader, installed the adb drivers and used "fastboot boot boot-to-root.img" to boot the image to my Google Pixel. The instructions indicate that my device should now be rooted.
But when I try and check it's still unrooted.
Does anyone know what I'm doing wrong/missing?
Click to expand...
Click to collapse
Not sure if you figured it out, but I went this route to root. All you need is the updated platform tools on your computer.
https://fwned.com/root-android-o-developer-preview/
Tried it didnt work as intended
noidea24 said:
Boot to root is outdated. Fastboot boot twrp and use it to install supersu
Click to expand...
Click to collapse
I used twrp flashed the elementalX kernel and the tried flashing supersu. It wont root and wont install supersu. What do you think happens?
Try this method. (im assuming you are on oreo?)
From a stock image.
Boot twrp, goto advanced, hit file manager, scroll down and find "fstab.marlin" or "fstab.sailfish" and tap on it, hit delete, return to the menu, flash supersu-v2.82 sr1 (i know its outdated but it allows busy box to be installed), reboot your phone and let it boot all the way up.
Now boot twrp again and go flash elementalx if you would like, then reboot the phone and you should be good to go
Thank you so much
noidea24 said:
Try this method. (im assuming you are on oreo?)
From a stock image.
Boot twrp, goto advanced, hit file manager, scroll down and find "fstab.marlin" or "fstab.sailfish" and tap on it, hit delete, return to the menu, flash supersu-v2.82 sr1 (i know its outdated but it allows busy box to be installed), reboot your phone and let it boot all the way up.
Now boot twrp again and go flash elementalx if you would like, then reboot the phone and you should be good to go
Click to expand...
Click to collapse
That did the trick perfectly
Permission Problems?
noidea24 said:
Try this method. (im assuming you are on oreo?)
From a stock image.
Boot twrp, goto advanced, hit file manager, scroll down and find "fstab.marlin" or "fstab.sailfish" and tap on it, hit delete, return to the menu, flash supersu-v2.82 sr1 (i know its outdated but it allows busy box to be installed), reboot your phone and let it boot all the way up.
Now boot twrp again and go flash elementalx if you would like, then reboot the phone and you should be good to go
Click to expand...
Click to collapse
The only issiue i have now is I cant get RW permissions in /system. Which is annoying since every app I'd like to use needs System write permissions.
I tried using console commands and Root explorer but neither work.
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
DarkPhoenix said:
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
Click to expand...
Click to collapse
From what I understand you can not do ADB in TWRP to install an update. What I did was download the factory images, remove -w from the flash all.bat. flashed the images and let the phone boot normally. Once I knew it was running I went to the bootloader and booted TWRP temporarily. Once that was up I flashed Magisk and then my kernel
I don't install TWRP anymore.
DarkPhoenix said:
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
Click to expand...
Click to collapse
Adding to what hatdrc said, you want the full image, not OTA, and install from your PC in fastboot mode. If you are concerned about saving your data, remove the -w switch from flash-all.bat first using a file editor like notepad. Have the twrp.zip, kernel.zip and magisk.zip files already staged. I personally don't boot to system first (but you can), I "catch" the reboot after flashing completes with the volume down button to reboot to fastboot mode. Then fastboot boot twrp.img, and then install twrp, kernel and magisk zips all in one go using the "add more zips" button in twrp. Every month when you update, you'll lose twrp, kernel and magisk, so those have to be reflashed each time. You'll soon get used to it and can do the whole thing in about 5 minutes consistently. Just make sure to pre-stage the 3 zip files on the phone before you start. Best of luck.
I tried that but couldn't get it to work. I downloaded the ADB tools again just in case there was an issue with that. I'm going to run the flash-all script again to see if I can get it to work.
DarkPhoenix said:
I tried that but couldn't get it to work. I downloaded the ADB tools again just in case there was an issue with that. I'm going to run the flash-all script again to see if I can get it to work.
Click to expand...
Click to collapse
if whats suggested above doesnt work, you can make the OTA work....download the ota to your PC, boot to Android Recovery (not TWRP), apply the ota via ADB from the menu. Whenever I have "odd" issues applying the Full image, this always works for me. Obviously you need to re-root after.
GL!
cmh714 said:
if whats suggested above doesnt work, you can make the OTA work....download the ota to your PC, boot to Android Recovery (not TWRP), apply the ota via ADB from the menu. Whenever I have "odd" issues applying the Full image, this always works for me. Obviously you need to re-root after.
GL!
Click to expand...
Click to collapse
Doesn't installing TWRP remove Android Recovery?
DarkPhoenix said:
Doesn't installing TWRP remove Android Recovery?
Click to expand...
Click to collapse
hmm, since I dont install TWRP anymore, you may be correct....still cant hurt to try
DarkPhoenix said:
Doesn't installing TWRP remove Android Recovery?
Click to expand...
Click to collapse
Yes it does. TWRP replaces the stock recovery.
Sent from my [device_name] using XDA-Developers Legacy app
v12xke said:
Adding to what hatdrc said, you want the full image, not OTA, and install from your PC in fastboot mode. If you are concerned about saving your data, remove the -w switch from flash-all.bat first using a file editor like notepad. Have the twrp.zip, kernel.zip and magisk.zip files already staged. I personally don't boot to system first (but you can), I "catch" the reboot after flashing completes with the volume down button to reboot to fastboot mode. Then fastboot boot twrp.img, and then install twrp, kernel and magisk zips all in one go using the "add more zips" button in twrp. Every month when you update, you'll lose twrp, kernel and magisk, so those have to be reflashed each time. You'll soon get used to it and can do the whole thing in about 5 minutes consistently. Just make sure to pre-stage the 3 zip files on the phone before you start. Best of luck.
Click to expand...
Click to collapse
Ok, I got the flash-all script to run. My brain shut down and I was running the wrong command.
DarkPhoenix said:
Ok, I got the flash-all script to run. My brain shut down and I was running the wrong command.
Click to expand...
Click to collapse
Well done. Now you can do it all over again in a week on Monday the 7th when the January build comes out.
v12xke said:
Well done. Now you can do it all over again in a week on Monday the 7th when the January build comes out.
Click to expand...
Click to collapse
I was updating so I could install Bootleggers rom so updating should be a lot easier lol.
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.
I'm currently on Magisk 20.4
Is it safe to update to 21.4?
I heard some updates didn't go well on our phone.
Thanks
kenbo111 said:
I'm currently on Magisk 20.4
Is it safe to update to 21.4?
I heard some updates didn't go well on our phone.
Thanks
Click to expand...
Click to collapse
Yup, did both updates this morning. Working fine on 21.4
Quick question - I was going to do this myself to provide another datapoint, but I'm wondering about the "Preserve AVB 2.0/dm-verity" option. It's unchecked, which I think is correct... but what does this mean, and how should we have this set (ie, if we think for ourselves, what's this about?)
For some reason, the "Direct Install" (or whatever it's called) option in Magisk Manager didn't work. It just said "download complete" and didn't actually install it. Maybe that's why you heard that the update didn't go well. I had to do the "Download zip only" option, instead, reboot into recovery and install it there. It seems to be working fine. It's just the update option in Magisk Manager that didn't.
Osprey00 said:
For some reason, the "Direct Install" (or whatever it's called) option in Magisk Manager didn't work. It just said "download complete" and didn't actually install it. Maybe that's why you heard that the update didn't go well. I had to do the "Download zip only" option, instead, reboot into recovery and install it there. It seems to be working fine. It's just the update option in Magisk Manager that didn't.
Click to expand...
Click to collapse
Weird, direct install has always worked for me. Other devices not so much, but always on the V30.
schwinn8 said:
Quick question - I was going to do this myself to provide another datapoint, but I'm wondering about the "Preserve AVB 2.0/dm-verity" option. It's unchecked, which I think is correct... but what does this mean, and how should we have this set (ie, if we think for ourselves, what's this about?)
Click to expand...
Click to collapse
Sorry to repost, but for you guys who did the Magisk install, can you please answer this question? Do we leave this preserve option unchecked (that's how it's coming up on my phone).
schwinn8 said:
Sorry to repost, but for you guys who did the Magisk install, can you please answer this question? Do we leave this preserve option unchecked (that's how it's coming up on my phone).
Click to expand...
Click to collapse
Anyone would know better than me, but I've done it checked and unchecked without issue. I lean toward checking it when updating, not really sure why.
ldeveraux said:
Weird, direct install has always worked for me. Other devices not so much, but always on the V30.
Click to expand...
Click to collapse
Yeah, it's always worked for me, as well. This was the first time that it didn't, which is why I mentioned that it could be an issue with this particular version.
schwinn8 said:
Sorry to repost, but for you guys who did the Magisk install, can you please answer this question? Do we leave this preserve option unchecked (that's how it's coming up on my phone).
Click to expand...
Click to collapse
I didn't get a "preserve" option (or any options). Maybe that's only if you're coming from certain versions, like 20.x versions, since I believe that I updated from 21.0.
Osprey00 said:
Yeah, it's always worked for me, as well. This was the first time that it didn't, which is why I mentioned that it could be an issue with this particular version.
I didn't get a "preserve" option (or any options). Maybe that's only if you're coming from certain versions, like 20.x versions, since I believe that I updated from 21.0.
Click to expand...
Click to collapse
Nope, it's there on mine when I upgraded from 21.X to 21.X. It's right there when you expand Option when you start the Install process.
ldeveraux said:
Nope, it's there on mine when I upgraded from 21.X to 21.X. It's right there when you expand Option when you start the Install process.
Click to expand...
Click to collapse
I get no such option when I install it from recovery. Maybe it's only if you install it through Magisk Manager.
Well, I went ahead and installed it with the option unchecked. It applied and booted with no issues. Looks like it worked.
I figured leaving it unchecked makes sense, since I believe we disable dm-verity during the WTF process anyway, so we shouldn't need to touch it. I wanted to be sure before I did it myself, but it seems I didn't have to worry. Unchecked worked for me.
Osprey00 said:
I get no such option when I install it from recovery. Maybe it's only if you install it through Magisk Manager.
Click to expand...
Click to collapse
Well yeah, I thought that would have been clear. I said I was able to flash direct install, not through twrp
ldeveraux said:
Well yeah, I thought that would have been clear. I said I was able to flash direct install, not through twrp
Click to expand...
Click to collapse
I know, and I did the opposite. I was just speaking it out loud for the sake of discussion.
Speaking of things that should've been clear earlier, it's occurred to me that that "Preserve AVB 2.0/dm-verity" probably does exactly what it says. Remember that, until about a year ago, it was recommended to flash a "dm-verity" zip in recovery when installing a ROM. I don't remember the order, but it could've been that we were supposed to flash Magisk first and then dm-verity because Magisk erased the latter. That "preserve" option, therefore, likely allows you to flash Magisk without erasing dm-verity and having to go into recovery after to re-flash it. Now, we haven't needed to flash dm-verity for a year, so the option may not matter if you're using a ROM version that's less than a year old, though there's probably no harm in being safe and checking it. Anyways, that's my guess.
My attempt of update Magisk from 21.4 to 22.0 brought me completely forgotten fastboot screen. Phone no longer boots. Just fastboot screen.
Magisk's direct install seemed to do nothing for unknown reason. Later I needed to reboot and was surprised to see fastboot screen.
Which partition should I flash using fastboot to fix this (especially preserving data, root, twrp etc.) ?
boot or boot + system? I do have a TWRP backups of these, but they are in WIN format. Can Ijust flash them with fastboot?
There's more to this -
fastboot devices
list no devices.
Reinstallation of the LG drivers didn't help.
you
przemhb said:
My attempt of update Magisk from 21.4 to 22.0 brought me completely forgotten fastboot screen. Phone no longer boots. Just fastboot screen.
Magisk's direct install seemed to do nothing for unknown reason. Later I needed to reboot and was surprised to see fastboot screen.
Which partition should I flash using fastboot to fix this (especially preserving data, root, twrp etc.) ?
boot or boot + system? I do have a TWRP backups of these, but they are in WIN format. Can Ijust flash them with fastboot?
Click to expand...
Click to collapse
You need to flash the original boot image from your stock or custom ROM via the flash boot using the command "flashboot flash boot <boot_file>
Then reflash TWRP and re-install magisk. Maybe the v21.4. The latest one broke my boot too. Good luck!
You need to flash the original boot image from your stock
Click to expand...
Click to collapse
I've got TWRP flashable TWRP-H93030b_00_OPEN_EU_0704.zip with two files: boot.img, and boot-original.img.
If I recall correctly boot.img is pre-patched? Which of these should I use?
I finally managed to connect over fastboot.
przemhb said:
I've got TWRP flashable TWRP-H93030b_00_OPEN_EU_0704.zip with two files: boot.img, and boot-original.img.
If I recall correctly boot.img is pre-patched? Which of these should I use?
I finally managed to connect over fastboot.
Click to expand...
Click to collapse
boot.img should be good. You can always flash the other boot image if it does not boot up.
Managed to flash "boot.img", TWRP and boot to TWRP, but... got "Mount Decrypt Data Enter Password".
I haven't encrypted purposely any partition.
Furthermore TWRP locked and doesn't unlock when I try to "swipe to unlock"...
Forced reboot. Android started. Phone works, but Magisk isn't installed. Rebooted once again into TWRP and installed Magisk ignoring data decrypt message. TWRP said it failed, but after reboot Magisk Manager sees Magisk installed and so TitaniumBackup
Seems it solved the prolem.