I’ve never tried that. It sounds easy.
Because of the warning concerning migration builds, I would use the script as described a section later: Signing Builds | LineageOS Wiki
Maybe @mmustermann knows something about this?
1 Like
Yes, it’s an issue with the signing keys. It’s possible but I’d just flash clean.
1 Like
The switch to official builds should not be a big deal. It is just a matter of swapping my keys with the official ones. Worked before for me when switching from the test keys to my own. The switch to official should be similar.
This script should do it:
Download
mmustermann_to_official_migration.zip | by mmustermann for Fairphone 4
sha256sum mmustermann_to_official_migration.zip
7f476e9b47016039d582a570ee0fc39ad904cc2ede2574430a278afdd5307dcd mmustermann_to_official_migration.zip
7 Likes
I have to admit that I never tried it. But the first entry in the FAQ is
-
Installing LineageOS zips in Recovery results in “Error 7”
-
- You are attempting to migrate from an unofficial build to official LineageOS. A full data wipe is needed if you are coming from something other than an official build of LineageOS.
But I don’t see anything different to @mmustermann’s switching to his own keys, just be warned if there are any errors.
Wow thanks for providing a ready to use script !
So, it would be as simple as opening Termux and running your script with sudo right ?
My script is just the official one with the test keys replaced by my own. Download it, extract it, rename it to migration.sh, backup your data and follow the instructions in the “Using a script” section: Signing Builds | LineageOS Wiki
4 Likes
Does the bootloader need to stay unlocked for the key switching script to work and for OTA updates to work once on official or is it fine to lock it again after either of those points?
I can recommend the following reddit post:
If something goewrong while you have your bootloader locked, the only thing that could help you right now would be the support center.
4 Likes
Can someone summarize whats the issue at hand here is in particular? I understand there is a merge conflict, which is why there is no official LOS support for FP4 and that there is a workaround using the solutions advised by mmustermann. However I am looking forward using microG which will only provide the build if it is officially supported by LOS.
I tried to figure out whats the hold up is and especially if this might take I while but I only found minor changes in the conflicting merge.
tl;dr Is there an eta on the conflict? Can anyone shortly explain whats wrong with the merge? Is there a dependency that is unresolved?
I’d guess no one here knows either. Most likely just a single developer looking at it and they haven’t had time or are on vacation or something?
3 Likes
Are there problems known Installing and using Lineage OS 19.1 for FP4?
When will a official version available?
I’ve been using it for a couple of months without major issues.
Battery life is great as long as your reception is decent, only intermittent issues I get are related to bluetooth pairing with specific devices. Nothing that can’t be managed.
This entire thread is partially about how we have no way of knowing the ETA for official release 
2 Likes
So I flashed mmustermanns build, but having trouble flashing MindTheGAPPS 12.01 arm64 version. It says something about this would be SDK32 and I am on SDK.
NikGAPPS core 12.1 arm64 seemed to work.
For those of U using GApps, what did u use?
I had the same problem. I had the following workaround:
I flashed the ROM.
Then setup, skipped what i could skip.
After that the system installed is Android 12 etc, so the GApps package should be compatible.
Again recovery, formatting and flashing the GApps.
It should work now.
Im newbie therefore sorry in case it does not work for you, but for me it worked.
Edit: i used the MindTheGApps
1 Like
I installed the build from mmustermann because I can’t wait for the official version. It works fine. But however, since then I’ve had problems with desktop mode. I can no longer move the windows
Hello,
I’m using the build of mmustermann and it’s working fine with the Gapps.
I have used the OpenGapps nano.
The only issue I seen for now with this rom is the usage of Greenify.
With or without root, it go to a black screen and I have to restart the smartphone.
I don’t have found a solution for now
Funny how every LOS user has different issues with installing gapps.
I personnally use NikGapps, and I flash it through TWRP as LOS recovery usually doesn’t let me do it.
It was my understanding that Greenify is very much outdated and is not relevant to use since Android 10. In fact, I’ve even got to realize that apps such as Greenify, Naptime, Servicely actually drain more battery than they save on latest version of Android.
Using the built-in battery limitations option is the way as far as I’m concerned.
1 Like
New build for September is up.
Download
sha256sum lineage-19.1-20220911-UNOFFICIAL-FP4.zip recovery-19.1-20220911-UNOFFICIAL-FP4.img
272ab7ae2701ec1b0ce873e852343a8f8aec495d78ab08c5c39b2ab7d49b7dec lineage-19.1-20220911-UNOFFICIAL-FP4.zip
bab283f20eadb3c33f295256cba6a43fd7fb84a74f630badd35be1ddd47dce0a recovery-19.1-20220911-UNOFFICIAL-FP4.img
8 Likes
I opted for iodeOS 3.1 (installation quite similar to LOS), worked like a charm, besides the bootloader lock. But I can live with that anyhow.