Hi @ArianK16a , have you been able to identify, what the issue was? Any details/logs needed? Or will the next weekly be good for updating again?
No logs needed. The issue seems to be an unlucky build timing/infra issue. We’ve taken the build down and done new experimental builds, both locally and on infra, and they are working fine. The next weekly build should be alright again 
Hello all! I just got my new Fairphone 6+, applied the latest update (FP6.QREL.16.111.0) and then unlocked the bootloader and installed the latest version of LineageOS.
I want to re-lock my bootloader, but I see that FP6.QREL.16.111.0 included an Android Security Patch Level of September 5th, while my currently installed LineageOS has September 1st. I assume that’s an issue.
Does anyone have an idea of how soon LineageOS will release a version matching September 5th? It might be worth waiting a bit before actually using the phone, since I’ll have to wipe it again to relock the bootloader… If on the other hand it’s expected to take more than a month I might consider using the phone and making a back-up before re-locking.
Do not attempt locking your bootloader with LineageOS installed on your phone! If you even can, it will brick your phone.
LineageOS is not signed with the proper keys to work with a locked bootloader on the Fairphone. Only Fairphone OS and /e/os work with a locked bootloader, and only if they are unmodified (no rooting).
Really? That runs counter to what Fairphone themselves say here; they “highly recommend re-locking the bootloader” after installing a non-fairphone OS…
For me it reads, quote …
Also Iode and Calyx work with locked bootloader.
Yes, “it may prevent your Fairphone from booting” if you don’t heed the rollback protection - that’s how I read it. Reading the whole page and particularly the section on re-locking the bootloader, I really don’t get the impression that you should only re-lock with either Fairphone OS or /e/OS…
Quick searches do indicate that CalyxOS and Iode work with a locked bootloader on the Fairphone 6, but similar searches indicate that LineageOS does not. I may be wrong, but I still recommend double- and tripplechecking before doing it. I believe there are fastboot commands to check lockability state before performing the lock. At the very least try those first.
You’re right. LineageOS doesn’t support relocking the BL as per Frequently Asked Questions | LineageOS Wiki or this: FP6 Unofficial LineageOS 23 - #8 by ArianK16a
Proper keys for what? That only applies to relocking LineageOS if you build it yourself. The official Lineage builds just don’t allow relocking, whereas other ROMs like official Fairphone OS, Calyx… do, based on their keys, and out-of-the-box. The thing is you will (usually) always need to format data if you change the lock state (unlock/relock) of the bootloader. So… backup recommended.
Looks like I misunderstood the reason it couldn’t be done. I thought the key chain had to go back to some key in the hardware. But it seems like it just has to be supported by the OS, and cannot be combined with flashing GApps separately?
Regardless of reasons, it’s not supported.
What about the latest fix of September 2026? Fairphone seems that fixed the issue.
It’s included and works like a charm
Hi,
I tried to install the lastest nightly build (28 of September). I am currently on the 14/10 build. The lineageos updater app shows ‘failed to check for update’ and trying to update from the push_update script (lineages wiki) doesn’t work either. It just says ‘update failed’. The same goes for a local update with the file from the LOS website.
Thank you for your help
The latest build is the one from October 5. You can probably check once again if you get it offered after a few tries. Another option would be to download it from LineageOS Downloads and do a local update
Tap “install local update” and select the downloaded “lineage-23.2-20261005-nightly-FP6-signed.zip”
Thank You for you answer.
I already tried doing that and got the same error message.
So, only dirty flashing or, as a last resort, clean flashing from recovery are the options left, I guess. Backup recommended in both cases.