Good news: Thanks to @chrmhoffmann the LineageOS build is now official. Follow these instructions to migrate from this UNOFFICIAL OTA release to the official one:
Old instructions to get on the UNOFFICIAL Lineage build
In a effort to make updating to the latest version of LineageOS easier we’ve setup the following:
A Jenkins that builds new versions of LineageOS every time something is committed into the LineageOS repository.
This version is then available as testbuild.zip here. After it is tested this release is offered Over The Air via the Lineage Updater already present in the OS.
LineageOS reviews their code through Gerrit, but still: consider this a nightly beta OS. To see what’s currently working and what’s not: check the porting thread.
When coming from any other OS:
Flash the latest build of TWRP, boot into it and make a backup (backup /data/media separately because TWRP doesn’t do this)
Factory reset from the wipe menu (or format /data when device was encrypted)
Queue this modem zip when coming from any other build than FP (Open) OS Android 6.
Queue this migration zip BEFORE the lineage build but don’t apply it just yet (this is needed to introduce a signing key which is required for OTA updates)
The final goal is to have Lineage take over this build as a official one. When we’ve reached that point I’ll make 2 migration zips to go to the official release from chrmhoffmann’s build and this one.
I applied the @z3ntu’s OTA fix via TWRP, rebooted again to TWRP and then queued the lineage-migration-signed.zip and the lineage-14.1-20170609-UNOFFICIAL-FP2.zip -> flashed and rebooted. Reboot took quite a bit longer than previously but without any issues so far.
Update under Settings -> About Phone -> LineageOS updates now shows available updates
Yeah, it’s incredible !! Thanks a lot !! Just a question : I didn’t do it because I don’t know if it will break the phone (and the guide say @z3ntu is not the official build) , but is it possible to install the official TWRP app (and install it as a system app) ?
First of all, I’m the maintainer of the official TWRP version See Maintainer on https://twrp.me/devices/fairphone2.html .
Secondly, the only change between the latest build and the one linked above is this change: https://gerrit.twrp.me/c/2508/ (which basically makes TWRP look for updates on that partition). So yes, it’s safe to use
Hello !
Does that means all the (current and future?) changes of chrmhoffmann are automatically merged into the WeAreFairphone repository, or this somehow is a process done manually by an admin?
Chris released a new release yesterday (lineage_FP2-ota-2017-06-14.zip), could I get the new features with the OTA Lineage Updater process described here?
My questions about this might to be more suited on the dummy post but because I already have OpenGapps installed, does your comment mean I would be reinstalling it? Also, what does that mean for app data for apps downloaded from the play store?
When updating this release it’ll preserve OpenGapps, so no need to re-flash anything. Only the updater is necessary. Also all app data is preserved. (This is because OpenGapps adds a addon.d-script which LineageOS runs during updates)
When installing this release for the first time, you do need to queue Gapps when you want it.
I have installed LineageOS 14.1 today following the steps in the first post and so far I am quite impressed. Thanks to all who made this happen!
Since I used an encrypted data partition on FP Open I had to do an additional step: A factory reset and wiping the data partition wasn’t sufficient. Only after formatting the data partition I was able to boot into the new system. @snevas Maybe it makes sense to add this info to the first post?
@snevas I would format the data partition only in case the data partition was encrypted before (because the current LineageOS version is not able to decrypt the data partition). In all other cases a factory reset may be sufficient (and has the advantage that the data on that partition will not be deleted).
I have installed the latest build OTA. But the automatic (daily) check of the updater notifies me of a new version, that is already installed.
Do you have the same behaviour?
See 
