That should match the boot_a I uploaded. What happens if you flash that?
If it doesn’t work, make sure it actually gets flashed to the right slot (the slot might be chosen based on suffix ) either rename it to your current slot or in fastboot do:
I used it on a OPO6T, but the script is manufacturer independent
In some cases slot b can be unpopulated or contain much older firmware than slot a, leading to various issues including a potential hard-brick. We can ensure none of that will happen by copying the contents of slot a to slot b. This step is NOT optional.
To do this, sideload the copy-partitions-20210323_1922.zip package by doing the following:
Download the copy-partitions-20210323_1922.zip file from here.
Sideload the copy-partitions-20210323_1922.zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload copy-partitions-20210323_1922.zip
Note: The copy-partitions script was created by LineageOS developer erfanoabdi and filipepferraz, but isn’t signed with LineageOS’s official key, and therefore when it is sideloaded, Lineage Recovery will present a screen that says Signature verification failed, this is expected, please click Continue.
Now reboot to recovery by tapping “Advanced”, then “Reboot to recovery”
I tried that, didn’t work. It is flashable from the OEM recovery and the script will execute just fine, but the other slot won’t be bootable.
Probably something to do with hashes still wrong for Verified Boot, but I really don’t know anything about how that works exactly.
Didn’t you get a update notification or did it fail during the update process and if so at what point?
Have you rerooted your phone before updating?
There has to be a way to get this working, what are we missing here
Huh, interesting… is that the same error you had before?
Maybe there’s still some modification to system files left somehow. I wouldn’t now how, but who knows
OK, here’s a crazy idea:
Install the Magisk app
Boot (not flash) your prerooted boot.img
Perform a Magisk uninstall in the Magisk app
That shouldn’t work, a factory reset should have purged all the remnants of Magisk off of /data, but hey, worth a shot.
Apart from that, could Titanium Backup have messed this up somehow, I don’t really know how it works these days, haven’t used it in almost a decade…
Third option, your other boot slot could be tainted, maybe because you flashed a wrong boot.img to it at some point. The updater usually flashes to the unused slot, maybe then, the failure gets triggered.
So try flashing that boot_a.img you used to get your phone working again to the other slot.
I tried to root my FP4 on /e/os using Magisk.
It worked using the default stock rom on FP4, so rooting the device works.
However, using /e/os Magisk just crashes when I try to modify the boot.img using the install button in Magisk.
This happens with v23 and the canary build. Does anyone have an idea how to fix it? Could it be any permission issue?
Yes. That works. However, a direct install using the app still doesnt work, after the flash.
Another user reported that he didnt have any issues with it.
I guess you also didnt have any issues with it.
I mentioned you in the ticket.
You shouldn’t have to install it again after you flashed the boot.img.
I patched the image on a phone running vanilla FPOS, so your problems with Magisk might well be connected to /e/.
If you want to figure this out, it would be really helpful if you could post your Magisk installation log, see here:
Installation log from the Magisk app (press “Save log” after installing Magisk or a module). If you experience errors when installing Magisk or modules in the Magisk app.
If that doesn’t tell us anything useful, a logcat would be the next logical step.