I won’t update the modem.zip, as no relevant files have changed besides emmc_appsboot.mbn.
I have a feeling that we won’t see many updates for the modem firmware from Qualcomm in the future, because it hasn’t been updated for months now.
I’ll try to publish my build script on GitHub before the end of the year.
Changed some days ago to Lineage OS 14.1-20171212-nightly-FP2.
I used TWRP 3.2.0-0 and followed instructions of Lineage.
Everything went smooth and fine and I am really impressed about Lineage.
Yesterday my updater informed me that an update is available to Lineage 14.1 dated
19.12.2017.
To avoid any trouble in future- is there any WIKI how to handle updates?
As i installed via TWRP- is it necessary to install Update also via TWRP or can I use the updater?
I ask this question because i formerly used Fairphone software and already destroyed TWRP by using the updater.
Furthermore, i think prior to update Lineage i should update TWRP. Can TWRP update itself if i put latest version on my SD-Card and install it via TWRP, or do I have to use ADB/Fastboot?
Many thanks in advance and first thing now, prior to doing any updates, i will make a complete back-up!!
Fairphone OS uses the stock Android recovery and under certain circumstances is able to restore that over a TWRP installed by the user.
Fairphone Open OS uses TWRP as recovery itself, so it shouldn’t happen with Fairphone Open OS.
That’s not a bad idea, but not strictly required. If your phone is encrypted, you need a halfway current version of TWRP that supports encryption.
TWRP can update itself. If you want to select the TWRP image file in TWRP, there’s a button to switch the file view from displaying ZIP files to displaying IMG files.
Frankly speaking i had some heart palpitation because automatic update did not work. Therefore, your link to www.zdnet.de was very valuable. They also say that it is sometimes difficult and download of update via browser is a safer method.
I have also to mention that it seems that TWRP cannot check sha256 and always looks for md5 sums. Therefore, the first flashing did not work because of missing md5. Therefore i switched off in TWRP md5-check because i manually checked sha256 with my computer after download of update.
Herebelow the steps i did:
Download update from Lineage Homepage.
Check integrity of downloaded file (sha256). I did it under Linux in the Terminal with:
sha256sum lineage-14.1-20171219-nightly-FP2-signed.zip
Compare output of Terminal with sha256 listed on Homepage of Lineage for this file.
Put file on sd-card
Boot to TWRP-Recovery
Remove the md5sum check (see above sha256) and flash the file.
Reboot
[Edit @AnotherElk: Link corrected, the ZDF (Second German Television channel under public Law) doesn’t help much here.]
Acutally Fairphone Open does exactly this. If you don’t hold Volume Up on reboot after upgrading FPOOS your manually installed TWRP will be overwritten by the outdated TWRP 2.6 from the FPOOS image even when you install it from the ‘manual’ package and delete the recovery image from the extracted zip file and the shell script.
Baseband version is given in Settings - About phone, that’s why I mention it there, you don’t see something like “Modem files version 17.11.2” anywhere in LineageOS.
And the modem filename is a link to where you can get it .
Slightly updated my post above because I forgot to mention that bluetooth works. I tested my MusicMan BT-X2 and the car audio system of a Mercedes CLA last time I used car-sharing.
Found Baseband version and download link. But sorry, it is still not clear what i have to do. Shall i download and install latest Modem files version?
My phone works very good only with Lineage and Lineage found directly my provider and data connection worked out of the box. With Fairphone OS and F!airphone Open i had to manually insert all the APN-settings!
In any case, the modem files get installed independently from the OS, so if you run into a problem with a new modem version, you can just install an older version.
Or you can install the latest version again and again and again … doesn’t hurt the OS installation.
I encrypted my phone some versions ago and it works.
Root access for a secondary user doesn’t work. The ‘battery charge limit’ app doesn’t work for the secondary user, it also doesn’t for the primary one, if there is a secondary one.