If the update you are installing is a full update, unlike the usual (at least for FPOS, CalyxOS) delta updates, the hashes of your current partition aren’t necessarily checked, because the update already contains the new partitions and doesn’t rely on the existing ones to be cleanly patchable.
I haven’t played around with Lineage on the FP4 yet, so not sure if that’s the case there. Do you have a OTA link handy?
On CalyxOS there sometimes are full OTAs (always available) and those install fine without restoring /boot as well.
Again my FP4 ran into a boot loop after disabling Magisk, updating OTA und trying to install Magisk in the inactive slot. It seems to me as if the a slot is somehow corrupted and cannot boot.
I sticked to the description here OTA Upgrade Guides | Magisk
Does anyone of you know how to fix a corrupted slot?
Strange that that keeps happening to some people. I just updated the FP4 of my family member to the latest release, no issues (as always) and Magisk works as expected.
Could you walk me through the steps you followed to update your system, did you get any error messages at some point? What version of Magisk are you using?
The most likely reason is that there’s something going wrong during the Magisk patching process, the OTA update should generally not produce unbootable slots (unless there’s an hardware issue somewhere)
Hi, I followed exactly the procedure in the link above and I got no error message. I use Magisk 25.2 (hidden).
After having the boot loop I started in fastboot and switched the the other slot (in my case b) and restarted successfully without root and without the OTA installed. So I ran the update again and rebooted after that unlike in the original instructions. The I boot via fastboot into some recovery (LOS or TWRP), run dd to get the boot.img and re-root from scratch (first patch the extracted image, boot it via fastboot and the install Magisk directly.
Is there a way to check the two slots for inconsistencies? A hardware issue should produce other problems, too IMHO. And after the second OTA run a is active (before it was b) and it booted successfully so I doubt that there is a hardware problem
Not really, you can check if the partitions match the expected hash, but in the case of /boot that’s not really helpful since you modified it by patching it with Magisk.
Hmm, maybe the issues has something to do with Magisk hide. Never used it and it’s not active on my family members phone either.
Which modules are you using? Anything that could modify the system partition? Maybe we aren’t looking at a Magisk issue here, maybe one of the modules doesn’t properly survive the update
For what it’s worth my Magisk is also hidden and I didn’t encounter a single issue while applying OTA.
As a matter of fact I don’t even need to uninstall magisk before installing OTA. Just installing Magisk on alternate slot before rebooting does the trick.
Feels like there are some modules messing up stuff here
I think I have the same problem as @Lars_Hennig since a couple of OTAs. When I go to Settings/System/Updates, I can see the animation running for a second or two and then it returns to the home screen. With Magisk hidden I uninstalled it (reinstalled the original images) successfully, but still can’t access the update.
After unhide Magisk the uninstallation does not work at all and I have the same behaviour acceding to OTA. The only way to do the OTA is to uninstall Magisk, reboot, do the OTA and reinstall Magisk from scratch.
My installed Magisk’s modules :
Well, in my case everything worked fine with my hidden Magisk until it finally came to the final reboot after patching the inactive boot image.
This time I was able to make it even worse myself: Just before the OTA procedure Magisk installed the beta update 26 (I had activated the beta upgrade path) and after that it was not able to find the stock image backup.
So I uninsttalled Magisk completely and started rooting from scratch this time
Had the same problem (on Calyx), which I kind of expected to happen. I ended up just downloading the factory images to the phone and dding the boot.img via Termux before starting the OTA update, worked fine
Thank you @hirnsushi . I saw your answer after I completed the upgrade and reinstalled Magisk from scratch. At the next OTA I will capture a logcat. But I couldn’t even get to the OTA startup screen, because after a second I was back on the home screen