So...I had a pretty good record with Magisk and OTA's until December. Usually I just follow the steps, OTA, reboot, root intact, etc.
This time though, not so lucky. I went through the process to prepare Magisk for the update. But then the OTA failed to install. And after reboot, I now don't have an updated device, and I've lost root.
I posted to the Magisk support thread, they suggested I come back here...
Right now I have an OTA waiting on my device, I have a Magisk update waiting, and I have no root.
If the OTA failed then there is something that got modified that it does not like. Easiest move here is to just flash the full image. Use the flash all bat file, but edit it first and remove the -w near the end. That will save your data and you will be fine.
Related
first of all, i was a rooted user since a long time, but the recent january patch gave me a hard time, so i went through a lot of testing and here are those, if anyone can help me.
I was having MagiskSU.
1. by uninstalling MagiskSU and getting back to stock recovery, i was able to install the october patch OTA.
2. Installed Magisk again, then one day i saw another OTA (this was the january security update), so i followed my previous steps, again uninstalled magisk and went back to stock recovery, but it gave me a status 7 error.
3. I copied the update.zip, tried to flash it manually from recovery, it said error in /sideload/package.zip, status 7.
3. i reinstalled the stock ROM, repeated everything, again i was able to accept the october patch. this time i backed up the october boot.img and restored it before installing the january patch, but same error. i tried to modify the zip file by removing the system checks, but it didn't allow me. Can anyone tell me what is so special about January patch that it simply doesn't get installed?
P.S. I finally gave up and reinstalled stock and all the patches, without root.
Try installing stock recovery. Download the stock firmware for your device from XDA. Unzip. Flash the stock recovery.img using fast boot. Then download the update and let the device do all that is necessary.
P.S. you need to completely uninstall Magisk. Flash the uninstall Magisk.zip (available from Magisk thread at XDA) before installing stock recovery.
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
EDIT: Issue resolved! Thanks, Bill!
I am using my 8T with a stock ROM with an unlocked bootloader and Magisk. As I want to keep the systemless root, last time I did the OTA updates through Magisk so it can patch the boot image before rebooting into the newest update. I know this only works with the full ROM images and not the incremental ones thus I download the full update file through "Oxygen Updater" rather than the official system update. I went into Magisk, to the modules tab, selected "Install from storage", and selected the full OTA file. Once it finished I then installed Magisk again before rebooting. Everything worked great. This latest update, however, keeps failing to unzip in Magisk. All I get in the logs is:
Code:
- Copying zip to temp directory
! Unzip error
I haven't changed anything since the last time I had a successful update this way other than to update the ACC module. I don't really know how to proceed with this other than to wait for the next OTA update. Unfortunately, I didn't do the correct procedure the first time I updated and Magisk did not backup the stock boot image, so I can't really try that. Any thoughts?
Model: KB2005
Current version: 11.0.10.10.KB05AA
Update version: 11.0.11.11.KB05AA (file is ...15.O.29_OTA_0290_all_2110091944... [2.78GiB/2.84GB])
Magisk version: 23.0 (app is also v23.0)
Here are three ways for keeping Magisk for an incremental OTA:
1. https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
2. https://forum.xda-developers.com/t/...00-kb2001-kb2003-kb2005.4178675/post-85801253
3. https://forum.xda-developers.com/t/guide-rooting-oos-with-twrp.4327417/
And I would never try to install an OTA via Magisk. Simply put the OTA in the root of sdcard and then use the System Updates local upgrade option.
BillGoss said:
Here are three ways for keeping Magisk for an incremental OTA:
1. https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
2. https://forum.xda-developers.com/t/...00-kb2001-kb2003-kb2005.4178675/post-85801253
3. https://forum.xda-developers.com/t/guide-rooting-oos-with-twrp.4327417/
And I would never try to install an OTA via Magisk. Simply put the OTA in the root of sdcard and then use the System Updates local upgrade option.
Click to expand...
Click to collapse
Well, that was simple enough. I guess I got the process confused, somehow combining parts of the process with my old 5T using TWRP and the previous update I did on my 8T.
Thanks for taking the time to grab those links and make a reply! I appreciate it despite the fact that I had a case of the dumb and could have saved you the effort
The last System Update notification received was the Update from Android 11 to Android 12. It installed fine. Can keep up via sideload or a full manual flash, but why no notification of updates?
Are you bootloader unlocked and/or rooted?
I have never received an OTA notice or been able to do OTAs but I rooted as soon as I got my pixel 4a.
There was one update that was offered but it was strange, and was the first and only time a separate AU firmware was made.
My children have pixel 4as and get OTAs just fine.
a1291762 said:
Are you bootloader unlocked and/or rooted?
I have never received an OTA notice or been able to do OTAs but I rooted as soon as I got my pixel 4a
Click to expand...
Click to collapse
Bootloader unlocked and rooted from Day 1. I was notified of the update from A11 to A12 and was able to use the system OTA. Otherwise I have sideloaded or flashed the Factory Image.
Even with auto update off in Dev Options, all I read says one shiuld still receive notification of the OTA. Guess I'll contune to sideload
a1291762 said:
Are you bootloader unlocked and/or rooted?
I have never received an OTA notice or been able to do OTAs but I rooted as soon as I got my pixel 4a.
There was one update that was offered but it was strange, and was the first and only time a separate AU firmware was made.
My children have pixel 4as and get OTAs just fine.
Click to expand...
Click to collapse
How long after update release (usually 5th of the month or so) do they see their 4a updates?
I have a 4a, rooted and unlocked. When new updates come out (I check the https://developers.google.com/android/ota page), I just uninstall magisk from the phone, run the system update, then re-install magisk and re-root. I believe it was Monday night April 3 when I did it last. If you don;t mind the hassle of all the reboots, I find it an easy enough way to keep updated and rooted.
amphi66 said:
How long after update release (usually 5th of the month or so) do they see their 4a updates?
Click to expand...
Click to collapse
It can vary a little (I think sometimes google stages the roll out?), but it's normally pretty soon after. The April update was already offered and installed.
augggg said:
I just uninstall magisk from the phone, run the system update, then re-install magisk and re-root.
Click to expand...
Click to collapse
How do you get the new boot image for rooting after doing the OTA?
a1291762 said:
How do you get the new boot image for rooting after doing the OTA?
Click to expand...
Click to collapse
I do it by extracting/Magisk patching the boot.img from the Factory Image. Of course I had to sideload the OTA as it didn't show up in System updates.
a1291762 said:
How do you get the new boot image for rooting after doing the OTA?
Click to expand...
Click to collapse
For 4a, go to the latest factory image here, which is at the bottom of each phone's list of images: https://developers.google.com/android/images#sunfish
Download the factory image, then unzip the file. Go into the folder you get, then unzip the next zip file you see (starts with image-sunfish*), and look for the boot.img file. Should be 64mb
Thanks @augggg and @amphi66.
I use the factory image to upgrade each month. But since I have to download it, I see no value in doing an on-device OTA (ie. Uninstall Magisk, reboot, OTA, etc.)
@augggg mentioned uninstalling Magisk to OTA so I wondered if they had an alternative way of getting the boot image besides downloading the factory image or full OTA (which is a bit harder to unpack, but also includes the whole boot.img).
I suppose one could boot TWRP to extract the new boot.img from the phone and then use Magisk to patch that... But I feel like it'd end up being a lot more work than the few changed lines it takes to flash the factory image, and my download speeds aren't bad enough to make that faster
Since I have to download the full factory image inorder to patch the boot.img, I use the factory image to update as well.
But I would like to know the status of the technique to "uninstall-restore Images" in Magisk, not reboot, update via OTA, not reboot, "install to inactive slot" in Magisk, then finally reboot.
For me, an OTA system update is never found.
lbush said:
Since I have to download the full factory image inorder to patch the boot.img, I use the factory image to update as well.
But I would like to know the status of the technique to "uninstall-restore Images" in Magisk, not reboot, update via OTA, not reboot, "install to inactive slot" in Magisk, then finally reboot.
For me, an OTA system update is never found.
Click to expand...
Click to collapse
Exactly. Worked for me once, but have not seen an OTA nofication since
Just a May followup. 10 days w/ innumerable System Update checks and still have not seen the auto-rollout of the May OTA Update. Yes, I can certainly sideload OTA or flash the (already downloaded) Factory Image, but is this a typical delay? I was thinking 2 or 3 days after release. Thanks.
amphi66 said:
Just a May followup. 10 days w/ innumerable System Update checks and still have not seen the auto-rollout of the May OTA Update. Yes, I can certainly sideload OTA or flash the (already downloaded) Factory Image, but is this a typical delay? I was thinking 2 or 3 days after release. Thanks.
Click to expand...
Click to collapse
Gave up & sideloaded May OTA, followed by flashing the Magisk-patched boot.img to retain root. Still do not know why there was no OTA notification
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?