Database Info

No way to OTA when rooted, correct?

It's been a while since I've visited.
I plan to root with magisk and keep the stock recovery (boot to TWRP to install magisk). In such a scenario, it would still not be possible to update with a normal OTA, as the update process would see the device as compromised, even with a system-less root method. Is this accurate?

floepie said:
It's been a while since I've visited.
I plan to root with magisk and keep the stock recovery (boot to TWRP to install magisk). In such a scenario, it would still not be possible to update with a normal OTA, as the update process would see the device as compromised, even with a system-less root method. Is this accurate?
Click to expand...
Click to collapse
Yeah, as Magisk still changes something.
On my Nexus 5X it was possible to download the OTA and save it on a computer, then go to Magisk Manager, restore stock boot.img, reboot to (stock) recovery, sideload OTA via ADB, reboot to bootloader, boot TWRP via fastboot, flash Magisk and then boot your updated phone.
As I didn't test this on my Pixel 2 yet, I can not guarantee, that it works this way. Make sure, you have backups of everything!

That seems like a bunch of extra work to get the OTA. I would use the system image (downloaded from google) and apply it (removing the -w). Once applied then fastboot boot twrp.img to install magisk.

nolimit78 said:
That seems like a bunch of extra work to get the OTA. I would use the system image (downloaded from google) and apply it (removing the -w). Once applied then fastboot boot twrp.img to install magisk.
Click to expand...
Click to collapse
I suppose this is what most people do, but it still seems like a pain to keep root. Maybe I will see if I can go rootless for as long as I can stand to see the ads. I really don't know what else I would need for root access for these days. After a bit of hiatus with the iphone, I've grown a bit lazy lately.

My suggestion involves 2.5 steps. It's far less painful than trying to use the OTA. That's what I do and I'm systemless rooted with Magisk.

I used to do the whole system image thing, until I realized that even with the hassle of patching the boot image with Magisk, applying the OTA update is likely faster.
nolimit78 said:
That seems like a bunch of extra work to get the OTA. I would use the system image (downloaded from google) and apply it (removing the -w). Once applied then fastboot boot twrp.img to install magisk.
Click to expand...
Click to collapse

Anyone able to root the Dec update?

For the life of me I cannot root this latest patch. I have tried 6 times either with having the Magisk app repack the boot image or by booting TWRP to install the Magisk zip. Using either method forces my phone into the same state/condition. When the phone reboots, it goes into recovery which says the data on my phone may be corrupt and prompts me to either try again or factory restore (erase data).

i was able to. i booted into twrp, sideloaded the twrp installer, then the magisk zip and sultan kernel and everything is running smoothly for me

Ok, so I was able to recover and root from an answer given in a pixel 3 thread using:
Pixel 3/Pixel 3 XL
- fastboot flash boot --slot all boot.img (from December factory image)
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- magisk-18.0.zip
- reboot system
What happens though is when I use adaway to update the hosts file, it breaks everything and I can't boot into system until I do the above steps again. Strange...
Do you have adaway install by chance?

Hi! I have no problem with last update, magisk nor adaway. I just flashed last update with flash-all.bat script, than fastboot twrp, install magisk ver. 18... and everything is working on 100%.

To successfully root on the Dec update you must use Magisk v18.0
[2018.12.8] Magisk v18.0 - Root & Universal Systemless Interface [Android 5.0+]
If you've used an older version, you'll get a boot loop into Recovery.
Side load / install the uninstaller from @topjohnwu's page linked above.
Then side load / install again with v18.0
Use the uninstaller first.

Diesel_Jeremiah said:
To successfully root on the Dec update you must use Magisk v18.0
[2018.12.8] Magisk v18.0 - Root & Universal Systemless Interface [Android 5.0+]
If you've used an older version, you'll get a boot loop into Recovery.
Side load / install the uninstaller from @topjohnwu's page linked above.
Then side load / install again with v18.0
Use the uninstaller first.
Click to expand...
Click to collapse
I'm on the December patch and am rooted with Magisk 17.1.
I actually just noticed the new update and am fixing to update Magisk. But you don't have to use v18. 0 to root December update. I've been on December update since it came out and rooted like always right away and haven't had any bootloops.

I rooted okay today with Magisk 18.0. It sounds like some people have had problems if they did not first uninstall Magisk with the latest uninstaller. That's what I did as a precaution (rather than just restoring the stock boot.img with the Magisk app, before upgrading the factory image).

FilthyFord said:
I'm on the December patch and am rooted with Magisk 17.1.
I actually just noticed the new update and am fixing to update Magisk. But you don't have to use v18. 0 to root December update. I've been on December update since it came out and rooted like always right away and haven't had any bootloops.
Click to expand...
Click to collapse
I had issues on both of my Pixel 2 phones trying to use any Magisk less than v18.0
I also had issues with v18.0 until I used the uninstaller first.
I read that other people were having the same issue.
I guess you got lucky?

Diesel_Jeremiah said:
I had issues on both of my Pixel 2 phones trying to use any Magisk less than v18.0
I also had issues with v18.0 until I used the uninstaller first.
I read that other people were having the same issue.
I guess you got lucky?
Click to expand...
Click to collapse
I guess so. I always open the .bat file and remove the -w so that it don't we my phone tough. Not sure if that makes a difference.

somin.n said:
Hi! I have no problem with last update, magisk nor adaway. I just flashed last update with flash-all.bat script, than fastboot twrp, install magisk ver. 18... and everything is working on 100%.
Click to expand...
Click to collapse
I enabled automatically granted root access and after a few mins after boot it granted access to adaway and after a reboot it seems to have worked again.

https://androidfilehost.com/?w=files&flid=249276&sort_by=date&sort_dir=DESC

update to 9.5.9 bootloop, only fix was twrp bootloop fix but removed root

As the title says I updated to 9.5.9 and I installed magisk to ota slot and then I got a bootloop.... I fixed it by using twrp option to fix bootloop but that removed root, everything I do now sends it into a bootloop, please tell me there is a way to reroot this without wiping my data

https://forum.xda-developers.com/on...-to-uninstall-magisk-module-t3940369#poststop
Just had the same issue an hour ago. Do this then re-root your phone again. Easy. Then re-install magisk modules.

spart0n said:
As the title says I updated to 9.5.9 and I installed magisk to ota slot and then I got a bootloop.... I fixed it by using twrp option to fix bootloop but that removed root, everything I do now sends it into a bootloop, please tell me there is a way to reroot this without wiping my data
Click to expand...
Click to collapse
Had the same issue.

Same here. I just reflashed TWRP (flash boot command), flashed the TWRP installer zip, rebooted recovery and then flashed Magisk. That solved it.
By the way, theres a new TWRP out for the 7 Pro.

I got the same problem but my internal storage is encrypted (it shows 0kb). TWRP is not asking for PIN to unencrypt the partition. What can I do now?

Do we have a custom boot image for 9.5.9? I'm looking to root and want to find the best method which will continue to allow future updates (even if I need to flash manually)

dude9946 said:
Do we have a custom boot image for 9.5.9? I'm looking to root and want to find the best method which will continue to allow future updates (even if I need to flash manually)
Click to expand...
Click to collapse
Your best bet is to use the oxygen updater app, download 9.5.9 and then copy it to a PC then use boot.img extract thingy and then use magisk to patch it and then use fastboot to to root it

Any way to root permanently?

After a while of being on my phone loses root and i have to restart to get it back. its annoying and stupid and i lose everything in memory. How can i just magisk once and be done?

odd, haven't seen a temp root method for the OnePlus 7 pro

OcazPrime said:
After a while of being on my phone loses root and i have to restart to get it back. its annoying and stupid and i lose everything in memory. How can i just Magisk once and be done?
Click to expand...
Click to collapse
I assume that after your rooted and happy with it you'll still want to update Android. If that's the case then you need to go through the various methods to apply an OTA (OOS update) and retain root.
I don't think your taking into account that the full OOS OTA contains components such as stock recovery that clobbers the system modifications that allow you to be rooted.
It is what it is and there simply isn't a way around it unless you stay with stock OSS (no root) or go to a ROM replacement of OOS which has a built in way to update that ROM and retain root.

Happens to me too sometimes, I just lose root and magisk says that additional setup is needed and installing magisk from the manager app fails and I have to reboot to recovery to install magisk again for it to work. I do not lose any modules.

it happens to me also. Sometimes magisk gets uninstalled, or root is not being detected. Sometimes I have to restart and some magisk or Xposed modules get deleted. So root is kinda buggy on this phone

jamesfitzes said:
it happens to me also. Sometimes magisk gets uninstalled, or root is not being detected. Sometimes I have to restart and some magisk or Xposed modules get deleted. So root is kinda buggy on this phone
Click to expand...
Click to collapse
Something possibly wrong with how you rooted.
I never lose root. I also flash both slots with the exact same version of the OxygenOS, TWRP and Magisk in both slots.
I never have an issue and the only time I lose root is when I do an OTA.

Root broken after forced update on t-mobile.

So back when I got my phone I had got it Sim unlocked and bootloader unlocked. Installed twrp and magisk to use some spoofing apps on my phone
Lately I've been promoted to update and just continually ignored it. It has since updated to 10.0.2.GM31CB.
My question is how can I return twrp and magisk to use my spoofs again? Once updated magisk wouldn't launch and got errors trying to use the spoof, so I'm pretty sure it deleted both magisk and twrp. I know things are different with the T-Mobile version so I'm scared to try an old version of a guide unless someone knows it still works
Just want directed to where to look to get those from the version I'm on, thanks!

Honestly not sure how you got the update with twrp installed it always failed for me. Had to restore original boot.img to install.
But the update relocks the bootloader ... At least it did for me so hopefully you still have your unlock bin. Just unlock the bootloader and root as usual.
Unfortunately unlocking wipes.
If your bootloader didn't relock just root per the guide

nujackk said:
If your bootloader didn't relock just root per the guide
Click to expand...
Click to collapse
Agreed. Would like to add, depending on which guide the top poster used to root originally, to make sure they use a version TWRP that is compatible with Android 10 (unofficial TWRP version -75 is the current); and current Magisk (20.3) is advisable, as well.
---------- Post added at 09:08 AM ---------- Previous post was at 08:51 AM ----------
StrawHatZakk said:
Lately I've been promoted to update and just continually ignored it. It has since updated to 10.0.2.GM31CB.
Click to expand...
Click to collapse
Did it reboot automatically after the forced update? If not, next time this happens, you should be able to do the following to easily keep root and TWRP:
1) After the update, do not reboot.
2) Open Magisk Manager
3) Flash TWRP installer zip as it were a Magisk module
4) Install Magisk, picking option "Install to Inactive Slot (After OTA)"
5) Reboot, and you should be on the updated OOS version, with root and TWRP.
Try this, if this ever happens again (forced update). But as mentioned, in your present situation you'll need to root using the method you used originally.
StrawHatZakk said:
Once updated magisk wouldn't launch and got errors trying to use the spoof, so I'm pretty sure it deleted both magisk and twrp.
Click to expand...
Click to collapse
That is correct, that updating removes root and TWRP. Both Magisk and TWRP patch the boot.img partition in order to install root and TWRP (respectively). Updating the phone overwrites the patched kernel with a new stock boot.img, so it needs to be patched again for TWRP/root to work. The Magisk Manager is an app that resides on the user dat partition, so the app itself remains (as will your other user apps, as is typical for updates). But nothing will really work right, since the necessary boot.img modifications are not present.

StrawHatZakk said:
So back when I got my phone I had got it Sim unlocked and bootloader unlocked. Installed twrp and magisk to use some spoofing apps on my phone
Lately I've been promoted to update and just continually ignored it. It has since updated to 10.0.2.GM31CB.
My question is how can I return twrp and magisk to use my spoofs again? Once updated magisk wouldn't launch and got errors trying to use the spoof, so I'm pretty sure it deleted both magisk and twrp. I know things are different with the T-Mobile version so I'm scared to try an old version of a guide unless someone knows it still works
Just want directed to where to look to get those from the version I'm on, thanks!
Click to expand...
Click to collapse
Just reflash twrp/magisk with powershell
Go to settings developer mode turn off auto install updates.

redpoint73 said:
Agreed. Would like to add, depending on which guide the top poster used to root originally, to make sure they use a version TWRP that is compatible with Android 10 (unofficial TWRP version -75 is the current); and current Magisk (20.3) is advisable, as well.
---------- Post added at 09:08 AM ---------- Previous post was at 08:51 AM ----------
Did it reboot automatically after the forced update? If not, next time this happens, you should be able to do the following to easily keep root and TWRP:
1) After the update, do not reboot.
2) Open Magisk Manager
3) Flash TWRP installer zip as it were a Magisk module
4) Install Magisk, picking option "Install to Inactive Slot (After OTA)"
5) Reboot, and you should be on the updated OOS version, with root and TWRP.
Try this, if this ever happens again (forced update). But as mentioned, in your present situation you'll need to root using the method you used originally.
That is correct, that updating removes root and TWRP. Both Magisk and TWRP patch the boot.img partition in order to install root and TWRP (respectively). Updating the phone overwrites the patched kernel with a new stock boot.img, so it needs to be patched again for TWRP/root to work. The Magisk Manager is an app that resides on the user dat partition, so the app itself remains (as will your other user apps, as is typical for updates). But nothing will really work right, since the necessary boot.img modifications are not present.
Click to expand...
Click to collapse
I took my sweet time trying it but wanted to get root back as I just moved and won't have internet for a while. Everything seemingly went fine, got TWRP going then after installing Magisk it would just hang at the t-mobile screen indefinitely. Attempted to do a restore with TWRP and must have hit a leftover restore from the previous android version now the only thing it does is boot to the fast boot section. Might make a new topic but I'm searching everywhere for a fix, can't seem to get this MSM tool thing to recognize it... thinking I might just be boned. If you know of any fixes let me know lol.