thats not fully correct I think or I misunderstand something from your comment. The current installed security patch level is important for anti-rollback and in general when installing an older one you will brick your phone when locking the bootloader. Also for the FP6 there might be a bug as several e/OS user bricked theri phones when relocking, also the SPL was newer. So really be very careful.
The currently installed security patch is not directly relevant for anti rollback (when formatting data).
Usually, OEMs configure this rollback index to be the security patch of the ROM, but that’s not a hard requirement. For example the volcano (FP6s platform) reference tree does this: BoardConfig.mk · qcom-devices.lnx.14.0.r1-rel · CodeLinaro / la / platform / vendor / qcom / volcano · GitLab
However, that does not hold for LineageOS, we do set the rollback index to the value of the stock ROM whose firmware we include, such that you won’t have a rolback index ahead of the stock ROM: android_device_fairphone_FP6/BoardConfig.mk at 967ec1b1da6ca6ea3cdcde13505325c9f3a9cc26 · ArianK16a/android_device_fairphone_FP6 · GitHub
So far with the theory, in practice this should not matter at all as long as you don’t lock the bootlaoder (which you currently can’t on this lineage release, or at least shouldn’t). The rollback index should never be updated as long as the bootloader is unlocked: Android Verified Boot 2.0
you might be correct in theory, however we have seen so many bricked phones because of the fact that older SPLs were flashed and the bootloader locked that I would still disagree somehow… also kindly see the topic I linked for the FP6, unfortunately FP is saying anything to it, so its unclear whats going wrong, So overall I think the general warning and advise to check get_unlock ability is still correct
I would assume that e/OS does not set the index according to the stock spl, but to their own spl. I can’t verify this currently, but they do for FP5: FP5 - BoardConfig.mk
The FP6 tree is not open (yet?) and since i’m going on vacation i can’t disassemble their ROM and verify it, though if anyone wants to try: You need to download their zip, unpack it until you get their boot.img and run avbtool info_image --image boot.img on it, this should print the avb rollback index as timestamp (if you want to make really sure, do this for init_boot, recovery and vbmeta_system too).
Do people also really report that they can’t go back to stock and lock even if they didn’t lock the bootloader on e/OS?
I dont know actually, that would be a point to ask those who faced the issue….will do in the topic.
@all who bricked their phone after installing e/OS and going back to FPOS. Did you lock the bootloader after installing e/OS?
Can confirm. Sending SMS works, but receiving them unfortunately not.
Anyone testet SD Card and Video Playback?
Can you please also try my suggestion here? Cannot receive SMS · Issue #28 · ArianK16a/android_device_fairphone_FP6 · GitHub
Feel free to report back on either github or here, i read both regularly 
It seems like @ArianK16a found a solution to the sending SMS issue! Required adb root for now, but I’m sure it will be integrated in a future build soon. Thanks for your awesome work!
Good evening 
I have a new update to share: Release LineageOS 22.2 for Fairphone Fairphone 6 (FP6) · arian-ota/ota · GitHub
Thanks to @acolombier we should have eSIM mannagement working now 
SMS should be fixed for good now, thanks for the testing!
The fairphone moments switch is functional now and can be configured to control several audio modes in settings → system → buttons → additional buttons.
Always on Display is also available now.
I have added some more detailed build instructions to this issue on github: Current state · Issue #7 · ArianK16a/android_device_fairphone_FP6 · GitHub
Let’s goooo!
Quick questions:
- Are there plans for an official release?
- If so, is there a rough ETA?
- Will you work on updates in the upcoming years?
- If so, is there any way to send donations to you/the team?
Thanks! 
Hy
to install LineageOS one question to unlock Bootloader…
both commands necessery? fastboot flashing unlock and fastboot flashing unlock_critical?
on my Fairphone 5 i try only fastboot flashing unlock……..
Yes, i plan to get FP6 officially supported. As always, there is no ETA for this.
I will work on updates as long as i have enough time for it and the hardware is reasonably capable of running the latest android versions, which should be some years.
My FP6 was donated to the LineageOS project and then distributed to me such that i can work on it and provide official LineageOS support (though this comes with no support guarantees or promises).
I already maintain a variety of other devices.
You can donate the the LineageOS project via PayPal or Patreon and to me personally via PayPal.
I’d recommend to follow the whole instructions provided by fairphone here.
Apart from that, afaict, you don’t gain anything from not unlocking critical partitions, in practice i think that unlock would be sufficient, as you don’t have to flash critical partitions via fastboot to install LineageOS.
Nice to hear it will be official! I can’t wait!
Oh wow, interesting how things work with LOS and the devs. That’s kinda cool! Thank you for carrying all the people that rely on your ports 
As soon as LOS goes official, you can expect annual donations from me!
One question: when lineageOS will go official for the FP6, will it also provide vendor firmware updates along with Android security patch level (SPL) or will it only provide Android SPL?
Thanks for great Image ……..mobile data Vodafone Germany and 1TB SD Card works perfect 
Some components of the vendor partition are proprietary software which we re-use from the stock rom. There is no way for us to update these on our own. However all parts built from source will be updated regularly.
The shown vendor security patch level in settings is the minimum of the source built AND proprietary vendor components, so typically the value of the stock ROM where we extracted the proprietary components from.
Good evening!
I have uploaded another update, it adds charging control settings (to stop charging at a specific percentage) and should fix upcoming OTA updates (OTA to this build is still broken).