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.
So last night I installed the November 5, 2017 security patch on my Pixel XL running Google's 8.0.0 ROM. I did have Magisk installed at the time and this is what I did:
Uninstall Magisk from Magisk Manager
Start update and wait for step 2
Go back to Magisk Manager and install in the OTA slot with force encrypt disabled
Reboot
This caused a boot loop, figuring that the Magisk flash was just bad I downloaded "marlin-opr3.170623.013" from Google and flashed the boot image in there. This fixed the bootloop but prevented my phone from passing SafteyNet, and I found that there was an update notification saying that the update failed. I attempted it again and it would not install at all.
So I downloaded the OTA package from Google and flashed as there instructions say.
Still not passing.
I then removed the -w flag from flash-all.bat to keep my data and ran that to flash my device with the factory image.
Still not passing.
What should I do about this? I can not manage to get my phone to pass SaftetyNet and I want to keep all of my data. When I had my Nexus 6p I would just reflash the system stuff with TWRP, but since TWRP does not work that is not an option here. (I also used to use a custom ROM, but don't now because TWRP is broken)
gudenau said:
So last night I installed the November 5, 2017 security patch on my Pixel XL running Google's 8.0.0 ROM. I did have Magisk installed at the time and this is what I did:
Uninstall Magisk from Magisk Manager
Start update and wait for step 2
Go back to Magisk Manager and install in the OTA slot with force encrypt disabled
Reboot
This caused a boot loop, figuring that the Magisk flash was just bad I downloaded "marlin-opr3.170623.013" from Google and flashed the boot image in there. This fixed the bootloop but prevented my phone from passing SafteyNet, and I found that there was an update notification saying that the update failed. I attempted it again and it would not install at all.
So I downloaded the OTA package from Google and flashed as there instructions say.
Still not passing.
I then removed the -w flag from flash-all.bat to keep my data and ran that to flash my device with the factory image.
Still not passing.
What should I do about this? I can not manage to get my phone to pass SaftetyNet and I want to keep all of my data. When I had my Nexus 6p I would just reflash the system stuff with TWRP, but since TWRP does not work that is not an option here. (I also used to use a custom ROM, but don't now because TWRP is broken)
Click to expand...
Click to collapse
It sounds like it's not passing after you flashed the image because you are unlocked. If you want to pass safetynet with an unlocked bootloader, you need to modify the kernel (or use one that is already modified).
Like this one: https://forum.xda-developers.com/pi...rnel-stock-kernel-safetynet-patch-dm-t3684405
mwalt2 said:
It sounds like it's not passing after you flashed the image because you are unlocked. If you want to pass safetynet with an unlocked bootloader, you need to modify the kernel (or use one that is already modified).
Like this one: https://forum.xda-developers.com/pi...rnel-stock-kernel-safetynet-patch-dm-t3684405
Click to expand...
Click to collapse
Strange, I didn't have to use a custom kernel before this patch. I guess Google did something.
gudenau said:
Strange, I didn't have to use a custom kernel before this patch. I guess Google did something.
Click to expand...
Click to collapse
I believe Magisk was hiding it for you. If I understand where you are at now Magisk is gone right?
TonikJDK said:
I believe Magisk was hiding it for you. If I understand where you are at now Magisk is gone right?
Click to expand...
Click to collapse
It passed before without Magisk. The latest update did something.
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.
Hey guys like the title says this months update is ready. I'm wondering if I can do the restore stock boot img thru magisk even tho I'm using MVK kernel?? Will it send me into boot loop??
** No bootloop everything worked out just fine **
Just a note tho, if you've rooted by patching the boot img you won't have a backup in magisk. You'll have to take the stock boot img from your current build and compress it with this file name stock_boot_0.img in a .gz compression then copy that to the /data folder in root storage. Then go into /sbin folder and go into .magisk folder, tap on config and change the SHA value to 0 and save it.
After that's done you can restore your stock boot thru magisk, take the OTA update, don't reboot yet, install magisk to the inactive slot, once done you can reboot and your good to go and still rooted
Perfect
Grabbed the full factory image. Removed the -w in flash-all. Flashed, patched boot.img. Works great!
Anyone having trouble with root on Jan update getting lost after a rebooot?
Tried 3 times now and same result each time.
Load magisk patched boot image for January via fastboot
Root fully operational
Install a magisk module
Required reboot after installing above module
Phone is no longer rooted
Can anyone confirm or deny if they get the same.
adm1jtg said:
Anyone having trouble with root on Jan update getting lost after a rebooot?
Tried 3 times now and same result each time.
Load magisk patched boot image for January via fastboot
Root fully operational
Install a magisk module
Required reboot after installing above module
Phone is no longer rooted
Can anyone confirm or deny if they get the same.
Click to expand...
Click to collapse
No..root still working here after reboot.
adm1jtg said:
Anyone having trouble with root on Jan update getting lost after a rebooot?
Tried 3 times now and same result each time.
Load magisk patched boot image for January via fastboot
Root fully operational
Install a magisk module
Required reboot after installing above module
Phone is no longer rooted
Can anyone confirm or deny if they get the same.
Click to expand...
Click to collapse
Working just fine here
adm1jtg said:
Anyone having trouble with root on Jan update getting lost after a rebooot?
Tried 3 times now and same result each time.
Load magisk patched boot image for January via fastboot
Root fully operational
Install a magisk module
Required reboot after installing above module
Phone is no longer rooted
Can anyone confirm or deny if they get the same.
Click to expand...
Click to collapse
UPDATE: thanks to the feedback i got it working... Turns out was a bad magisk module, updated and all is well. Thanks
thatsupnow said:
Hey guys like the title says this months update is ready. I'm wondering if I can do the restore stock boot img thru magisk even tho I'm using MVK kernel?? Will it send me into boot loop??
** No bootloop everything worked out just fine **
Just a note tho, if you've rooted by patching the boot img you won't have a backup in magisk. You'll have to take the stock boot img from your current build and compress it with this file name stock_boot_0.img in a .gz compression then copy that to the /data folder in root storage. Then go into /sbin folder and go into .magisk folder, tap on config and change the SHA value to 0 and save it.
After that's done you can restore your stock boot thru magisk, take the OTA update, don't reboot yet, install magisk to the inactive slot, once done you can reboot and your good to go and still rooted
Click to expand...
Click to collapse
I've done all steps up until the OTA part. It keeps giving me "Couldn't update, Installation problem" after numerous tries. Both here and the Magisk guide say DO NOT reboot. Am I screwed if I reboot or just have to repeat the process?
Thanks
Basically I was on November update with magisk and a custom kernel installed I couldn't take otas so how I fixed it was @mbk17 I had to flash the matching boot IMG in fastboot from the update I was on to get installation problem error to go away so I could take an ota.
Download matching factory image from goggles website
Then unzip the file
Then also unzip the image bonito zip
The boot IMG is inside second zip
Flash boot IMG in fastboot issue fixed :victory:
thatsupnow said:
Just a note tho, if you've rooted by patching the boot img you won't have a backup in magisk. You'll have to take the stock boot img from your current build and compress it with this file name stock_boot_0.img in a .gz compression then copy that to the /data folder in root storage. Then go into /sbin folder and go into .magisk folder, tap on config and change the SHA value to 0 and save it.
After that's done you can restore your stock boot thru magisk, take the OTA update, don't reboot yet, install magisk to the inactive slot, once done you can reboot and your good to go and still rooted
Click to expand...
Click to collapse
Actually, there is an easier way. Get the stock boot.img for the current build, put it on your phone, and patch that boot.img through Magisk. It will backup that original boot.img before it patches it. Don't need to do anything with the patched boot.img, but when you restore images, it will take the backup you just created.
---------- Post added at 10:03 PM ---------- Previous post was at 09:59 PM ----------
mbk17 said:
I've done all steps up until the OTA part. It keeps giving me "Couldn't update, Installation problem" after numerous tries. Both here and the Magisk guide say DO NOT reboot. Am I screwed if I reboot or just have to repeat the process?
Thanks
Click to expand...
Click to collapse
I know it's too late but in the future if you get this, you're still rooted until you reboot, so just reinstall magisk through direct install. Now when you reboot, you're still rooted.
That said, if you can't update through the ota, you're going to have to update through ADB, and you'll lose root anyway.
Bramton1 said:
Actually, there is an easier way. Get the stock boot.img for the current build, put it on your phone, and patch that boot.img through Magisk. It will backup that original boot.img before it patches it. Don't need to do anything with the patched boot.img, but when you restore images, it will take the backup you just created.
Tried that and didn't work. Kept saying backup didn't exist, hence why I posted this steps
Click to expand...
Click to collapse
OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://file5.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img
Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?
My computer is down so:
THANKS A MILLION!!!!!!!!!!!!!
YOU'RE SO AWESOME!!!!!!!!!!!!
Orion9k0 said:
Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?
Click to expand...
Click to collapse
If you are not using TWRP, follow this guide: https://forum.xda-developers.com/t/guide-how-to-root-oneplus-7t-without-twrp.3979307/
didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on
posiblyLopsided said:
didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on
Click to expand...
Click to collapse
Did you switch back the default OTA active slot after flashing both?
nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
i did not flash i only booted. i have tried flashing in the past with android 11 and had the same result of eternal loading. but that was a while ago and it is possible i did smth wrong.
nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
Did you remove or at the very least disable all Magisk modules before OTA updating?
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"
kurskoo40 said:
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"
Click to expand...
Click to collapse
the issue is that when i do fastboot boot magisk.img it gets stuck on the boot animation. i have to hold the power button and volume up to force it to power off then i can boot it back to the normal version
posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.
thexile said:
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.
Click to expand...
Click to collapse
how would i do that? can i use my phone file manager or do i need to use adb?
posiblyLopsided said:
how would i do that? can i use my phone file manager or do i need to use adb?
Click to expand...
Click to collapse
Since you have no root access currently, you have to do so via adb in recovery mode with adb enabled.
thexile said:
Since you no root access currently, you have to do so via adb in recovery mode with adb enabled.
Click to expand...
Click to collapse
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.
posiblyLopsided said:
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.
Click to expand...
Click to collapse
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
yeah looks like i learned the hard way too. also i didnt realise they released twrp for oneplus 7t. id heard that it just didnt work with android 11 but maybe im wrong. ill try it out anyways. if the twrp works that would be amazing. also thanks for all the help.
thexile said:
OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://srv-store6.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img
Click to expand...
Click to collapse
Thanks. This worked fine. I just used local install from update, backed out without rebooting, installed magisk app and did the first reboot into bootloader, then wrote magisk modded boot image to boot a/b. It was a dirty update over the prior version.
thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
i have successfully rooted after useing twrp to remove those magisk modules.
Hi, I really need EU version of boot.img, could you please help me?
I've even looked for the full 11.0.2.1.HD65BA but with no luck.
So basically can't find anywhere both the boot.img and the full stock rom, any advice?
Thank you