no, I used the recovery from mmustermann (now I also understand why there is a recover) and I have dobe the steps till no. 5 as I posted. And yes, it looks like the one on your image. before each retry, I wiped again.
@mmustermann now you suggest to boot instead of flashing?
In general, I will not be able to update the next LOS version from mmustermann like this? Still I have a running instance. Maybe I can use it for some month and hopefully there will be an official release in the mean time…
So if you ignore the wrong signature and say yes to “install anyway?”, did you try to boot to the normal system afterwards? Does LOS work or does it hang in a bootloop?
If it ends in a bootloop, please check a few things:
Ensure that the files you downloaded have not been corrupted. Do so by checking if the sha256 hashes match.
Are you absolutely sure that you use the 20220511 recovery for sideloading? It didn’t complain about the wrong signature for me.
Doesn’t matter as long as it worked and you booted or flashed the 20220511 recovery.
You will be able to sideload the next update. You might just loose your root access after the update, because the update usually overwrites the boot partition. So any modifications you do to the boot partition might get lost and you probably have to patch the boot.img again to reinstall Magisk.
Usually not, because your data is stored on a seperate parition. Modifying the boot partition leaves the data partition untouched. But it is always a good idea to have a working backup!
Thanks, trying to patch you .zip tells me that something failed. Then I realized I need the boot.img. but where do I find yours? it’s neither the .zip and the recovery.img from you right?
You can use a tool like payload-dumper-go to extraxt the partitions (including boot) from the files in lineage-19.1-20220511-UNOFFICIAL-FP4.zip.
I’ve uploaded you a patched boot.img, just install the Magisk app and follow the usual instructions:
Sure You can download prebuilt binaries for your architecture from the github releases, no need to install Go. If you are on an Arch based distro, it’s also in the AUR (but then what isn’t ).
Extract lineage-19.1-20220511-UNOFFICIAL-FP4.zip first, you’ll find the payload.bin file in there we’re interested in.
If you’ve downloaded payload-dumper-go manually, just extract, it open your terminal where you extracted it to and run it with ./payload-dumper-go path/to/payload.bin and it will create an folder extracted_$date_$time in the current directory.
If you struggle with the payload-dumper I’d suggest you go with the first suggestion from @hirnsushi as it doesn’t require you to run any kind of tool:
Just to mention an alternative method I successfully used to have boot.img, is to (one-time-) boot to TWRP and backup the boot partition on the external SD card.
Internal memory is not currently available with TWRP-for-FP4 because of decryption incompatibilities, but boot partition is not encrypted so can be backed up
I updated my description with you points @hirnsushi
However, I delete the last point fastboot erase metadata. After that the LOS was corrupted I will not do it with the new attempt. So is it badly required?
Yes - AFWall+, XPrivacy, AdAway work like a charme. After 7 years a new phone with LineageOS <3 - another 7 and more on the road
I owe you folks, let me know how if applicable. My offer is still valid!