I’ve uploaded a new build of LineageOS 23 based on Android 16 (but NOT QPR1 - this is not open source, more information here).
This build should be as stable, or better, than the last lineage-22.2 build and i strongly recommend to upgrade. There won’t be further lineage-22.2 builds.
Regarding the random vibrations/moments switch bug; i haven’t noticed it happening again, might or might not be fixed, please report back!
Asides from that, USB Tethering was fixed and the system security patch is updated to 2025-10-01. As usual, if you encounter any issues, please report them here or, if you’re also interested in following the progress on fixing it, open an issue on GitHub here.
The rollback index is set to 2025-07-05, matching FP6.QREL.15.122.0.20250718182448_VS1E-factory.zip. It should be safe to relock the bootloader on stock. However, don’t relock the bootloader on LineageOS for now, we might provide instructions for that later if it’s a thing you’d like to do.
I’ve been running 22.2 for a bit and appreciate the work you have put into this. Will 23 be available as an OTA update, or will this require a manual update?
No, as usual on LineageOS, OTA upgrades are not supported on major android version updates to avoid users running into issues with outdated addons, precisely gapps. You can do a manual upgrade without wiping data though by sideloading the new zip from recovery, like you did for the initial installation, and then re-installing updated versions of your addons, if you have any. If you installed MindTheGapps, that would mean that you have to install this addon: Release MindTheGapps-16.0.0-arm64-20250812_214353 · MindTheGapps/16.0.0-arm64 · GitHub
Hey, i’m sorry since i’m a newbie switching to lineage OS on fairphone with the will of supporting an european brand and open source world, but the bootloader can’t be re-locked on lineage, right? Thanks in advance and my respect for your great work of porting lineage os for this fantastic phone! ^^
Sorry if this is a stupid question but I’m currently in the market for a new phone and the FP6 is a strong candidate. Does it look like FP6 will gain official support on LineageOS at some point in the future? I would be OK running an unofficial build for now but in the long run it would be nice to see official support.
EDIT: A few more questions: Does this build support signature spoofing so MicroG can work? And is eSIM supported?
In any case, I applaud your effort on getting LOS working on this device. Looks really promising.
Currently you can not lock the bootloader on LineageOS, as stated in the first post. Once the builds are official, you won’t be able to lock the bootloader on these either.
In general, LineageOS is not designed to be used with a locked bootloader, you will not be able to install addons or use adb remount.
If you are aware of these things and still want to lock the bootloader, you should build it on your own and sign vbmeta with your own private keys. You can refer to this guide: [GUIDE] Re-locking the bootloader on the OnePlus 8t with a self-signed build of LOS 18.1 | XDA Forums which mostly matches what we have to do, but some of the steps are already done in our tree. I will provide more instructions about this when i get to do it myself.
Just another small question, is there something I can really do to “protect" more my device since an unlocked bootloder, from what I heard, is a serious security problem? Is it really like they say? And what are some other measures I can take if I wanna root my phone with lineage os?
It sounds like a locked bootloader is high on your priority list.
You might want to check whether you could make a different Custom ROM work for your use cases.
/e/OS for instance is based on LineageOS and supports relocking the bootloader on FP6. It comes with microG incorporated as a system App, though, which not everybody wants to have.
Where did you hear that an unlocked bootloader is a serious security problem?
Whether that’s true depends on the reasons they give.
As far as i can tell, an unlocked bootloader mostly only opens an attack surface for attackers with physical access to your device, such that they can install a modified operating system or patch something in the system. However, to benefit from the unlocked bootloader the attacker must use fastboot to flash the modified system image.
The other attack surface would be if the attacker finds an exploit in android to gain root privileges and flash a custom image from within the running system, in this case a locked bootloader would detect a change of the partitions and prevent booting the new image. However, to do so, the attacker must gain root privileges and if that happens, your unlocked bootloader, and thus the attackers ability to mess with your system partitions, ain’t your worst problem anymore anyway. (And thus google and OEMs are trying hard to avoid such exploits being open).
If you want to root your phone anyway it doesn’t make sense to bother with locking your bootloader.
My strong suggestion would be to self build your ROM with everything you need included (Google Apps, Ad block, etc.), sign it with your own keys and make sure to store them safely.
Thanks for the update. I just updated via sideload. I think you’ll need to add an option to install from storage to the recovery before the image can be made official. (I was surprised that this option is missing)
After install I get the message ‘system-UI is crashing’, and I get asked if I want to stop it. This message is displayed once at each reboot, then the UI seems to be killed off and starts correctly.
No other issues found until now. (it’s almost 2h on the phone ) SD card is usable (was an iddie I had) and I’ll check the Sony earbuds with the phone later. (older Samsung buds had no issues, the newer Sony buds sometimes didn’t have mic in calls)
Yea I perfectly know I cant lock the bootloader with root, it’s just I hear lots of graphene os users flexing they can relock the bootloader on graphene and so they are totally safe from attacks at their data and phone, and I read an unlocked bootloader can eventually be a problem for your data bc an hacker could manage to access them even if you have a strong passphrase, so my question was if there ar e some security tips to avoid this happening
I can’t think of any apart from using your phone as disposable (don’t store sensitive data on it).
It’s a phone, which you carry around, can be lost, stolen,… For me it’s just for texting (SMS, Signal), calling, navigation and pictures taken will be moved from the device within 24h-48h. (not in the cloud, but on local storage)
) SD card is usable (was an iddie I had) and I’ll check the Sony earbuds with the phone later. (older Samsung buds had no issues, the newer Sony buds sometimes didn’t have mic in calls)
. Everything is working like a charm 
.
