Hello,
I thought you didnt need the migration zip, as the instructions in the 1st post donāt mention flashing it if coming from FPOS. I didnāt use it when I came from Open Android 5.1 and I can get OTA updates with Lineage.
Iād say that if you follow the instructions in the 1st post under āif coming from any other buildā then it should be a ok
Hello,
As I have a Mac, I had trouble getting fastboot to work, so instead I was able to use the TWRP App, which I downloaded from the play store to the phone, to flash the TWRP OTA Fix to recovery. This skipped the fastboot trouble. I can still successfully install Lineage OTA updates through the updater. What do you think about me adding a line or two with installation instructions in the beginning of this thread for those who canāt get fastboot going? It might help Lineage to reach a wider audience
Itās a wiki post, so you can edit it yourself. But try to keep the instructions as simple as possible
Thanks! But I am still tryingā¦
I updated open OS to the very last one 17.07.
(actually I had a look at lineage because it was impossible to get the file from here 2 days ago, but it worked todayā¦ )
Everything was still okay (apps, contacts, sms,ā¦ )
I flashed modem-17.07.6 (myabe it was not useful now I had the latest open OS?)
Then lineage-migration-signed (the latest one 08-03)
What should I choose now in the team wine recovery project page?
reboot?
Edit : Actually, I finally manage to get Lineage OTA updates through the updater so I made a step (or at least I hope soā¦). But after the reboot, I have this same screen and I donāt kow what to do
If coming from open OS, follow this part from the 1st post (no migration zip needed):
Be aware that youāll need to factory reset and youāll lose all data that you donāt backup.
Ok, thanks, I will start from scratch
Edit: sounds like it doesnāt workā¦ I am āstuckā in open OS 17.07 whatever I tryā¦
Maybe is it because I get an āerror 7ā message (while flashing lineage-14.1-20170803ā¦zip)?
I keep trying
Edit2: I did exactly what is written here
And I still get this get this error7 message :-/
Edit3: No, it worked finallyā¦ in 2 steps
- factory reset
- flashing lineage 14.1-20170614-UNOFFICIAL-FP2.zip
@sky I just installed the testbuild.zip of 05/08/2017 and I also confirm that the SIM2 for SMS setup doesānt survive a reboot
Pushed a update with the new security patches. Nothing else changed. Timestamp is 20170808.
Be aware of the following bugs:
As I still canāt OTA successfully (āDie ĆberprĆ¼fung ist fehlgeschlagen, beschƤdigter oder ā¦ā), I got me a logcat:
08-08 20:13:10.945 10081 18291 D DownloadManager: [269] Finished with status SUCCESS
08-08 20:13:14.691 7880 7890 I art : Background sticky concurrent mark sweep GC freed 139423(6MB) AllocSpace objects, 5(168KB) LOS objects, 28% free, 19MB/26MB, paused 1.564ms total 203.863ms
08-08 20:13:24.540 10081 10093 V DownloadManager: Deleting /data/data/com.android.providers.downloads/cache/lineage-14.1-20170808-UNOFFICIAL-FP2.zip via provider delete
08-08 20:13:30.775 18216 20682 E DownloadComplete: Verification failed
08-08 20:13:30.775 18216 20682 E DownloadComplete: java.security.SignatureException: signature digest verification failed
08-08 20:13:30.775 18216 20682 E DownloadComplete: at android.os.RecoverySystem.verifyPackage(RecoverySystem.java:315)
08-08 20:13:30.775 18216 20682 E DownloadComplete: at com.cyanogenmod.updater.service.DownloadCompleteIntentService.onHandleIntent(DownloadCompleteIntentService.java:99)
08-08 20:13:30.775 18216 20682 E DownloadComplete: at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:68)
08-08 20:13:30.775 18216 20682 E DownloadComplete: at android.os.Handler.dispatchMessage(Handler.java:102)
08-08 20:13:30.775 18216 20682 E DownloadComplete: at android.os.Looper.loop(Looper.java:154)
08-08 20:13:30.775 18216 20682 E DownloadComplete: at android.os.HandlerThread.run(HandlerThread.java:61)
(How do I format this best?)
Is it possible that the LineageOS/android_frameworks_opt_telephony tree isnāt used in our LAOS builds?
Itās included. If you search within the buildservers console log youāll see:
00:01:19.506 Fetching project LineageOS/android_frameworks_opt_telephony
But Iāve heard there have been some other changes yesterday that could fix it. Could you test this one after is finishes?
Iāve seen that, but no more hints to the content of that tree and also no hints to SubscriptionController.java in my logcat after booting the phone.
Iāll try the new build as soon as possible.
No, the new testbuild didnāt fix it.
Is it possible that this one is not build? @snevas @z3ntu @chrmhoffmann
*/enable this build only when platform library is available
ifeq ($(TARGET_BUILD_JAVA_SUPPORT_LEVEL),platform)
Pushed a new release over OTA (20170815). Changes:
- Support for the new hardware by @z3ntu
- A lot of CVE patches to the kernel by @chrmhoffmann
Iāve also put the new version of TWRP on the server with support for the new hardware (same filename as before).
Thanks for you great work. Have you thought about setting up a https://opencollective.com/ account/project?
Iāve been stuck on the 30 July release and it canāt seem to do the update check. Also it can delete the previous download. Should I manually install the latest release?
Iāve had some issues with LTE connectivity, restarting seems to be the only way to restore it. I used the migration file when doing the OTA fix but would installing the latest modem file help with this?
Yes manually do the lineage update and also update the modem files
Where can I file in bugs?