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
Related
Unlocked, Magisk-rooted, TWRP 3.1.1 beta working. Updated from .010 to .018 to get rid of "System Update" notice that failed to install, but I had to "flash-all" factory image as I could NOT get .018 OTA image to sideload. Failed immediately.
Cannot sideload .011 (8.1) OTA image, tried with all versions of TWRP. Fails immediately.
And, TWRP 3.2 will both sideload and zip-install from 3.1.1 beta, but after reboot, I'm back to beta.
Please tell me what I'm missing: any help appreciated. TIA
You might try using flashfire to install the ota.zip image. It's worked for me on other rooted phones.
neuron617 said:
Unlocked, Magisk-rooted, TWRP 3.1.1 beta working. Updated from .010 to .018 to get rid of "System Update" notice that failed to install, but I had to "flash-all" factory image as I could NOT get .018 OTA image to sideload. Failed immediately.
Cannot sideload .011 (8.1) OTA image, tried with all versions of TWRP. Fails immediately.
And, TWRP 3.2 will both sideload and zip-install from 3.1.1 beta, but after reboot, I'm back to beta.
Please tell me what I'm missing: any help appreciated. TIA
Click to expand...
Click to collapse
- Uninstall Magisk to unroot
- Flash the system.img and boot.img from whatever version/factory image you're on to confirm you are stock (this should also uninstall twrp if you went with the install method over the temp boot)
- Then follow the instructions on Google's OTA page (download OTA, boot into Stock Android Recovery, hold power and press volume up, select Apply update from ADB to sideload OTA)
- Flash custom kernel if desired (via fastboot, I'm using Flash Kernel), temp boot twrp and sideload Magisk (14.3 worked for me with 8.1)
foosion said:
You might try using flashfire to install the ota.zip image. It's worked for me on other rooted phones.
Click to expand...
Click to collapse
Thanks; I'll check it out.
Ra6idr0y said:
- Uninstall Magisk to unroot
- Flash the system.img and boot.img from whatever version/factory image you're on to confirm you are stock (this should also uninstall twrp if you went with the install method over the temp boot)
- Then follow the instructions on Google's OTA page (download OTA, boot into Stock Android Recovery, hold power and press volume up, select Apply update from ADB to sideload OTA)
- Flash custom kernel if desired (via fastboot, I'm using Flash Kernel), temp boot twrp and sideload Magisk (14.3 worked for me with 8.1)
Click to expand...
Click to collapse
Thanks for confirming what I was coming to suspect: have to unroot and ditch TWRP to move ahead. I appreciate this.
What is point of "systemless" root, however, if you have to unroot to get OTA update?
neuron617 said:
Thanks for confirming what I was coming to suspect: have to unroot and ditch TWRP to move ahead. I appreciate this.
What is point of "systemless" root, however, if you have to unroot to get OTA update?
Click to expand...
Click to collapse
Systemless root shouldn't change anything on the system partition. All changes are made to the kernel. Note that when rooting with Magisk you provided a boot.img rather than the system.img. the suggestion to reflash the system image is to nuke any changes you may have made to it. An OTA will fall off you have done any tinkering.
Unrooting should be as simple as restoring the original boot image.
Sent from my Pixel 2 using Tapatalk
PiousInquisitor said:
Systemless root shouldn't change anything on the system partition. All changes are made to the kernel. Note that when rooting with Magisk you provided a boot.img rather than the system.img. the suggestion to reflash the system image is to nuke any changes you may have made to it. An OTA will fall off you have done any tinkering.
Unrooting should be as simple as restoring the original boot image.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Ahhh... I really appreciate that clarification.
Y'all are the best: @ foosion, @ Ra6idr0y, @PiousInquisitor
Many thanks and Happy Holidays!
My phone keeps bugging me to upgrade to Android 10. I have systemless root, magisk etc.
Is this safe to just do? Do I need to get the image from elsewhere and start over? I've had an update alert come through from Magisk announcing Android 10 compatibility, so I'm guessing that won't be an issue...
I really only wander in here whenever I get a new phone so I have no clue how this works.
you can update to android 10 just fine with magisk installed, however you will lose it once the upgrade is done. you will need to patch your boot image with magisk once you are on android 10.
Not sure what that means.
koberulz said:
Not sure what that means.
Click to expand...
Click to collapse
You. Will. Need. To. Patch. Your. Boot. Image. With. Magisk. After. You. Update. To. Android. 10.
I can read, dude.
What's a boot image? How do I patch it? What are the actual steps here?
koberulz said:
I can read, dude.
What's a boot image? How do I patch it? What are the actual steps here?
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-10-0-q-t3964112
So start the root process over, basically? Is there any point in doing the OTA update or do I just grab the latest image from the website?
Steps 7/8 say there's no TWRP for Android 10 yet, so how does that work?
koberulz said:
So start the root process over, basically? Is there any point in doing the OTA update or do I just grab the latest image from the website?
Steps 7/8 say there's no TWRP for Android 10 yet, so how does that work?
Click to expand...
Click to collapse
you can not install twrp on android 10, you can still boot twrp though. you will not need twrp for the boot image patch.
update your phone to android 10, get the boot.img from the factory image of the version you updated to, using magisk manager patch that boot.img, boot to bootloader, flash the patched boot.img with
Code:
fastboot flash boot_a patchedboot.img
and
Code:
fastboot flash boot_b patchedboot.img
(or only flash for the boot of the current slot you are on, doesnt really matter)
Personally, on every monthly update I always flash the full factory image (deleting -w if I want to keep my stuff) and then reinstall Magisk and custom kernel by temporarily booting TWRP. I find it much less of a hassle, it applies to major upgrades too (as is your case) and it's guaranteed to work every time.
Flipz77 said:
Personally, on every monthly update I always flash the full factory image (deleting -w if I want to keep my stuff) and then reinstall Magisk and custom kernel by temporarily booting TWRP. I find it much less of a hassle, it applies to major upgrades too (as is your case) and it's guaranteed to work every time.
Click to expand...
Click to collapse
i usually do this also
Flipz77 said:
Personally, on every monthly update I always flash the full factory image (deleting -w if I want to keep my stuff) and then reinstall Magisk and custom kernel by temporarily booting TWRP. I find it much less of a hassle, it applies to major upgrades too (as is your case) and it's guaranteed to work every time.
Click to expand...
Click to collapse
There are monthly updates?
I've not been aware of anything at all until now, because now it's sending me a notification.
koberulz said:
There are monthly updates?
I've not been aware of anything at all until now, because now it's sending me a notification.
Click to expand...
Click to collapse
December will be the last one, sadly
Hi,
After installing Magisk i no longer receive OTA Updates. The safety net checks are ok. How can i fix this?
Thanks.
+1
Sent from my Pixel 3 using Tapatalk
adrianppa said:
Hi,
After installing Magisk i no longer receive OTA Updates. The safety net checks are ok. How can i fix this?
Thanks.
Click to expand...
Click to collapse
AFAIK, your only choices are to sideload the OTA from https://developers.google.com/android/ota and re-root. You can also flash the factory image and re-root. Be sure to remove the -w from flash-all.bat/sh so you don't wipe your data. I prefer the factory image method. You can patch boot.img before flashing the image, which makes re-rooting a bit easier. I believe there have been some reports of OTA working again after flashing the factory image.
well you have root duh lol, off course otas will fail, at least they dont install unlike old times when install would be error
there are many ways to install but this is the easiest for me every month
each month download full system image
copy boot to phone and patch it with magisk apk, copy back to pc
apply full system image flash all.bat but remove the -w from the .bat (Edit the bat)
this will install the lastest ota but you wont lose any data or settings, everything well be okay
root is lost, now you have to root again
boot magisk boot image
apply direct install in magisk apk
restart
this has to be done every month
you can also uninstall magisk every month and let the ota download and install but that is even slower and annoying, this is how is done
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Thanks,
¿GJ?
¿GotJazz? said:
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Than
Click to expand...
Click to collapse
¿GotJazz? said:
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Thanks,
¿GJ?
Click to expand...
Click to collapse
I had the same issue, I had to downgrade to 11.04, grab a new 11.05 ota from oxygen updater app, extract boot from that and go from there
hammered58 said:
I had the same issue, I had to downgrade to 11.04, grab a new 11.05 ota from oxygen updater app, extract boot from that and go from there
Click to expand...
Click to collapse
Is this the Oxygen Updater App you are referring to, or is it the incremental OTA that I would get from a "OnePlus system update" on a now unrooted and unTWRP'd phone?
Also ... Will I lose any data if I downgrade to 11.04? I've never downgraded before, so do I just install the stock 11.04 image via TWRP like I did the 11.05 image?
Lastly ... I'm assuming this will just get me root, but not including TWRP?
¿GotJazz? said:
Is this the Oxygen Updater App you are referring to, or is it the incremental OTA that I would get from a "OnePlus system update" on a now unrooted and unTWRP'd phone?
Also ... Will I lose any data if I downgrade to 11.04? I've never downgraded before, so do I just install the stock 11.04 image via TWRP like I did the 11.05 image?
Lastly ... I'm assuming this will just get me root, but not including TWRP?
Click to expand...
Click to collapse
1. Yes that is the app Iam talking about.
2. Will you lose data? I always do a format (after the down grade) so I lost data but I never tried it with out formating, it might work, you could try it and see what happens .If it acts strange then it will need a format.
3. Yes you install 11.04 via twrp
4. Yes you will get root but if you want twrp you will have to reinstall
Once you down grade install the oxygen updater, let it download the update , don't let it install it, you can then grab the update from your root directory as it doesn't hide it, then your good to go, you can extract the boot.img by using payload dumper, then take the boot.img and patch that with the magisk app . ( Just install the magisk app on your downgraded 11.04 you don't need root to run the app ) ,,Then after your thru upgrading to 11.05 and after setup just reboot to bootloader and run the magisk patched boot.img, ( fastboot flash boot boot.img) reboot and wait a minute for the magisk app to appear ,it will want to install and do a reboot . Then you can install twrp if you want.
This is how I did it and it worked, you may find a simpler way once you start doing it ,, hth
I'm reluctant to go and do a total wipe (which I have been reading will be required to downgrade).
I'm wondering if the problem I'm facing is that my OP7P needed to be rooted for Magisk 24.1 to be able to successfully patch the latest OP7P build? My OP7P isn't rooted right now although I have v24.1 installed.
I accidentally had installed the latest 11.0.5 OTA before I had a chance to attempt re-rooting.
¿GotJazz? said:
I'm reluctant to go and do a total wipe (which I have been reading will be required to downgrade).
I'm wondering if the problem I'm facing is that my OP7P needed to be rooted for Magisk 24.1 to be able to successfully patch the latest OP7P build? My OP7P isn't rooted right now although I have v24.1 installed.
I accidentally had installed the latest 11.0.5 OTA before I had a chance to attempt re-rooting.
Click to expand...
Click to collapse
Right now I have 11.05 installed and Iam rooted, tomorrow I will unroot and downgrade to 11.04 without wiping and let you know what happens iam curious myself
I'm rooted now. I did have to wipe my OP7P to get root (due solely to my own heavy-handed approach to getting root again).
I posted in another thread, and I think that the thing that might have made a difference for me wasn't that I wiped, but possibly that I removed encryption before installing the Magisk-patched boot image.
¿GotJazz? said:
I'm rooted now. I did have to wipe my OP7P to get root (due solely to my own heavy-handed approach to getting root again).
I posted in another thread, and I think that the thing that might have made a difference for me wasn't that I wiped, but possibly that I removed encryption before installing the Magisk-patched boot image.
Click to expand...
Click to collapse
I guess that's possible , I never thought of that, the only way to know is to do a fresh install only this time setup encryption then try to install magisk . But for now your rooted,, until the bug hits you or me to try another rom then we can start the whole thing over again,,
I cant do normal OTA updates, nor can I install them with the built in installer in settings (that I gained with conversion). Im not exactly sure why and trying to figure this out. Were you able to update as normal to A13?
Its possible I broke something (cant think of what), so Im restoring my after-root twrp "base" backup to see if it can OTA.
Figured Id ask in the meantime...
TimmyP said:
I cant do normal OTA updates, nor can I install them with the built in installer in settings (that I gained with conversion). Im not exactly sure why and trying to figure this out. Were you able to update as normal to A13?
Its possible I broke something (cant think of what), so Im restoring my after-root twrp "base" backup to see if it can OTA.
Figured Id ask in the meantime...
Click to expand...
Click to collapse
You have to uninstall magisk/restore images. Then start ota. Then before you reboot go into magisk again and install to opposite slot and reboot . After ota has installed. Stock boot image is the only way it works. It's will fail upon checksum of partitions by google
I figured as I just went back to my base savior A11 rom fresh root, and still nothing. Thank you!
Uninstall magisk it automatically restores boot images right?
*Actually do I need stock boot? I have twrp. Where do I get stock boot image?
Im screwed. Its unable to restore my old image from usb, so Im bricked now. No idea what to do.
mattie_49 said:
You have to uninstall magisk/restore images. Then start ota. Then before you reboot go into magisk again and install to opposite slot and reboot . After ota has installed. Stock boot image is the only way it works. It's will fail upon checksum of partitions by google
Click to expand...
Click to collapse
Do you know how I can get back to stock boot?
NM found it. So to be sure, when i want to move from A11 I need to uninstall Magisk, boot to fastboot, then fastboot flash stock boot.img?
Here
^But I have twrp, so wont restoring just bring me to unlocked bootloader unrooted with twrp? (*still not stock?)
*Sorry for the questions. It just seems TWRP has problems restoring backup completely (or I missed something, I backed up everything in TWRP maybe I dont need to do that?).
Im trying to avoid what happened a couple nights ago, because I lost confidence in TWRP on this phone. Usually, its just something ****s up? Well restore your backup, because you just made one. That didn't work completely (it didn't restore /data), and I had to set up a ton I dont want to do again, unless Im on custom A13 rom. Got savegames!
Thanks for all help.
I was on android 12 with april 2022 security update, so it was a very very early android 12 build. I couldn't update via OTA cause I kept getting "update failed" I was rooted, had data I didn't wanna lose so I just ignored it.
I'm now on A13 with root. what I did was: MSM tool back to A11, update via OTA until I reach final official build, extract the boot file through msmtool, patched it with magisk, flashed it via fastboot, job done.
Couldnt Magisk patch boot image from app? Instead of extracting it? Thats how I did it on 11.
I also dont know how to use msm tool to get to 11, or even where to get files. *I think this is it? General - OnePlus 9 11.2.22.2 (T-Mobile) MSM Download Tool | XDA Forums
*Thats exactly whats happening to me too. update failed. So I guess this would be a sure fix.
pubmastervnt said:
I was on android 12 with april 2022 security update, so it was a very very early android 12 build. I couldn't update via OTA cause I kept getting "update failed" I was rooted, had data I didn't wanna lose so I just ignored it.
I'm now on A13 with root. what I did was: MSM tool back to A11, update via OTA until I reach final official build, extract the boot file through msmtool, patched it with magisk, flashed it via fastboot, job done.
Click to expand...
Click to collapse
Wait. How did you unlock bootloader (after MSM put your phone back to lock BL I assume)? Is the option later available on Tmobile roms? Did you need a token?
pubmastervnt said:
I was on android 12 with april 2022 security update, so it was a very very early android 12 build. I couldn't update via OTA cause I kept getting "update failed" I was rooted, had data I didn't wanna lose so I just ignored it.
I'm now on A13 with root. what I did was: MSM tool back to A11, update via OTA until I reach final official build, extract the boot file through msmtool, patched it with magisk, flashed it via fastboot, job done.
Click to expand...
Click to collapse
you get update failed bec. of the magisk image. you have to restore to stock image before you download the OTA. in magisk dashboard, go to uninstall magisk. choose RESTORE IMAGES. download the ota. do not reboot. go to magisk and install magisk. choose install Magisk after OTA (or something) then press Let's go. and reboot.
jmadiaga said:
you get update failed bec. of the magisk image. you have to restore to stock image before you download the OTA. in magisk dashboard, go to uninstall magisk. choose RESTORE IMAGES. download the ota. do not reboot. go to magisk and install magisk. choose install Magisk after OTA (or something) then press Let's go. and reboot.
Click to expand...
Click to collapse
Doesn't having twrp boot image installed mean that magisk restored twrp image to when before magisk patches it (so it's not actually stock)? Doesn't it just restore a non rooted image with twrp on it?
jmadiaga said:
you get update failed bec. of the magisk image. you have to restore to stock image before you download the OTA. in magisk dashboard, go to uninstall magisk. choose RESTORE IMAGES. download the ota. do not reboot. go to magisk and install magisk. choose install Magisk after OTA (or something) then press Let's go. and reboot.
Click to expand...
Click to collapse
This fails if you have TWRP.
pubmastervnt said:
I was on android 12 with april 2022 security update, so it was a very very early android 12 build. I couldn't update via OTA cause I kept getting "update failed" I was rooted, had data I didn't wanna lose so I just ignored it.
I'm now on A13 with root. what I did was: MSM tool back to A11, update via OTA until I reach final official build, extract the boot file through msmtool, patched it with magisk, flashed it via fastboot, job done.
Click to expand...
Click to collapse
Are you tmobile? How did you unlock BL on 13?