Solved it, posting in case it helps anyone relocking the FP6 with a custom AVB key on the official tree.
Root cause: the vbmeta verification flags. For relocking to work, the vbmeta must have Flags: 0 (verification enabled) — that is what the locked bootloader expects. If the vbmeta has Flags: 3 (verification and hashtree disabled), the device boots fine unlocked but drops back to the bootloader when locked (the yellow custom-key screen shows first, because the key itself is accepted, but then it won’t boot).
On the pre-official tree, the argument that sets Flags to 3 was placed in the else branch of the custom-key check. So when you passed your own AVB key, it took the if branch and that argument was skipped — the vbmeta ended up with Flags: 0, and relocking worked.
On the official tree the logic changed: that same argument is now applied whenever WITH_AVB is not set to true, regardless of whether you pass a custom key. So even signing with my own key, because I wasn’t exporting WITH_AVB=true, my build produced a vbmeta with Flags: 3 — and the device wouldn’t boot when locked.
The fix: export WITH_AVB=true before building. Then the official tree produces a vbmeta with Flags: 0, matching what worked before, and the device relocks and boots normally.
on the official FP6 tree, if you sign with a custom AVB key and want to relock, build with WITH_AVB=true. Verify with avbtool info_image on vbmeta.img — it must show Flags: 0, not Flags: 3.
@ArianK16a thanks — might be worth a note on the relock wiki page so others don’t hit the same thing.
First, great work! Been using this as a daily driver since December.
I updated to the latest build from June 29 and only just noticed that when I try checking for new updates it doesn’t say something like “your phone is up to date”, but it actually reports an error saying it failed to check for updates at all.
Wondering if this is happening to anyone else?
Thinking it could still be looking for updates from the old beta release repo instead of the now official repo maybe?
@AustinFoss i had the same problem with the updater but didn’t think it was widespread at the time, since there was only the first image on the server at the time. in my case, the updater crashed repeatedly and UI just bounced back to settings menu. i cleared storage for the updater app, and the problem went away.
I’m not sure how to do this. The updater function isn’t a standalone app with storage to clear and there is no setting to clear updater cache or similar.
Could you clarify? Clearing the storage of my Settings app wasn’t the fix
Yeah that’s not there… I just have system updates under the Settings app. I have no standalone updater app.
Again, I’ve just had a continuously updated FP6 on lineage os 23 since December. Maybe the move from unofficial to official builds failed to add that other app?
not even in Settings → Apps → See all apps → Show system? well i guess something got lost when you flash official on top of unofficial. my last experience of doing this was about more than 10 years ago, not so great.
Oh neat, I did find it there. But upone clearing storage for both it and “Dynamic system updater” I still get an error saying that update check failed and the last time it was updated was June 29 when I updated to the most recent official.
I wasn’t experiencing the bounce back you were, so mine must be a different issue.
I installed LOS 23.2 on my FP6. Thanks for the amazing work.
There is a really annoying issue, the microphone is very loud, When I record a video or an audio message with default recorder app, I can barely hear myself when I play it back with full volume. For example I was using whatsapp to make a video call with family. I had to get closer to my phone so they can hear me.
Microphone recording volume is way too low to be usable. It is as if the default microphone was set to the one when you are making a phone call.
I have installed the offical version and like the minimal application selection.
Before installation i did a call and send a SMS to make sure it works.
So far i have only 2 problems.
Bluetooth and audio seem to need a bit of work.
Reconnecting does not always work.
If you move around a lot it sometimes wont reconnect.
And for Audio the media keys seem broken.
Neither volume nor play/pause are working.
Even in the system UI.
For example im using Firefox and it has this button for play and pause in the notifications but that does nothing.
The headset buttons do not work either.
@ArianK16a Sorry to ping you directly but I noticed I’m still not able to successfully check for updates no my phone, last update check was when I installed the June 29 build. Now I see there’s a July 6 build.
In the system updater under settings I see a “local update” button. Is there a way for me to manually download the update? Downloading the build’s zip and inspecting the contents doesn’t see to be right method, so aside from flashing the build from scratch I seem a little stuck on the June 29 build
i assume you are on the unofficial june 29 build? Then you should use adb sideload to migrate to the official build, just like how you installed the first unofficial build. You do not need to wipe your data for this.
…