Thanks. Don’t forget the signing keys bit when going to 16.
Thanks. Don’t forget the signing keys bit when going to 16.
I noticed that the adaptive brightness does not seem to work. Do I have to change some settings? Is anybody else experiencing this?
As far as I understand, I must have an Android Tree to generate the keys.
Do you mind publishing the script migration.sh? For me myself that would be much easier.
Rest seems to be rock-solid
As I never had to do this before … How exactly do I do it?
I had a look at https://wiki.lineageos.org/signing_builds.html, but everything there seems to base on building LineageOS myself?
Can’t I just take the migration ZIP from here and reverse the key changes it is doing in the update-binary script to get from official to unofficial keys?
Or are the key values different now?
For the record … didn’t help.
Encrypted the phone with 14.1 … wiped 14.1 and installed 15.1, which started up fine with encryption intact … flashed a “reversed” migration ZIP just to try something quickly … installed 16.0 without wiping 15.1 … didn’t help, decryption still unsuccessful.
Could there be some log somewhere which could help?
I’m also interested in Lineage-16.0, and also that the encryption works.
Encryption is a mandatory requirement that I can continue to use the phone as a company phone, therefore I have a great interest to support the test - especially concerning the encryption.
But just like @AnotherElk, I do not know what exactly to do with the zip file with regard to changing the key.
@chrmhoffmann, is there a more detailed description on how to do it?
Hi, hope this helps:
(except some apps AntennaPod import issue is already closed but not released, SilenceIM import but the development seens to be dead)
It look like IPv6 support becomes a little bit worse again (with clat in wifi) - but thats i am still testing, and does not matter for “usually” users.
To clarify: Encryption in LineageOS 16.0 works.
The problem: TWRP as of 3.2.3-0 can not decrypt encrypted data which was encrypted with Android 8 or (now) 9. TWRP would have to catch up here, but this seems to be extremely tricky for developers.
TWRP being able to decrypt is desirable, because TWRP has a really neat backup feature, which loses much of its charme when the data partition (the only thing that really gets encrypted) is missing in the backup.
Workaround for LineageOS 15.1: 15.1. could be installed and ran totally fine with encryption already in place from a former Android (e.g. LineageOS 14.1 = Android 7). So TWRP was happy with that, too.
Workaround for LineageOS 16.0: There’s the problem now. 16.0 seemingly doesn’t behave like 15.1. with the old encryption already in place and doesn’t even boot.
Thanks for the info that encryption work in principle.
But as you also mentioned it, I like TWRP’s backup/restore functionality, and I don’t want to miss it.
This is exaxtly the problem! I need a backup and if it does not even boot it is for me useless.
I understood that I can encrypt 16.1. but not backup data via TWRP because TWRP does not decrypt.
What can we do?
Keep using official 15.1 until currently unofficial 16.0 becomes official, and hope for some workaround until then?
It’s still testing stage … we’ve been there before .
Has anyone tried out Netguard? It doesn’t work with Lineage 15.1. (Thread: Netguard blocks all traffic. I’m not brave and clever enough to try out an unofficial version. But I really hope it works again with Lineage 16.0.
I installed the upgrade and it works, thank you chris!
Didn’t migrate the keys, though, but it works anyway (*).
What I had to do is to reinstall the openGapps pico for android 9, before doing that google play services was crashing continuously…
(*) EDIT: I desactivated “signature verification” in Parameters > Security and localisation > Trust
Tried it some time ago and it worked with Lineage 15.1 . Download was via F-Droid (now again available there). I tried the free version which is in my opinion fully sufficient. Upgrade is - as far as I remember - possible via a donation to the developer.
It was a test only for me because it is not really necessary with Lineage and I deleted it some time later. How to do installation and adjustments please read info from Mike Kuketz
Yes, you need to install via recovery a new version of gapps when upgrading to a new major release.
You should also migrate keys, as apparently you lose system app settings.
I would like to test this coming from FPOOS. Can I just wipe and flash in TWRP (as per usual)?
If you have a backup of everything you consider important, and if your phone is not encrypted, then yes.
If your phone is encrypted, you will have to remove encryption with Format Data in TWRP before installing 16.0 (currently), else it will not boot (currently). You can encrypt in 16.0 after it is installed, but TWRP can’t handle this 16.0-encrypted data partition then (currently, but TWRP will work with the other partitions, so e.g. updates should work).
many thanks to @chrmhoffmann and @z3ntu!!!
After I finally understood howto change the keys, I updated today.
It worked like charm! All system settings have been kept. Except the homescreen (widgets and nearly all icons lost; wallpaper stayed the same) and the preferred SIM card for calls .
A first Bug I’ve found: After setting the display size and tabbing the button “recent items” the screen just shows the wallpaper and I’ve to reboot the phone.
For all who want to change the keys. This is what I did:
adb root adb shell stop adb push ./migration.sh /data/local/tmp/migration.sh adb shell chmod +x /data/local/tmp/migration.sh adb shell sh /data/local/tmp/migration.sh unofficial adb reboot recovery # Now install the LineageOS install zip
The file migration.sh can be found here: migration.sh
Just tried to run the migration script as described above.
I get these error messages:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb push c:/temp/migration.sh /data/local/tmp/migration.sh
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell chmod +x /data/local/tmp/migration.sh
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell sh /data/local/tmp/migration.sh unofficial
: not found/tmp/migration.sh: line 2:
: not found/tmp/migration.sh: line 12:
: not found/tmp/migration.sh: line 22:
: not found/tmp/migration.sh: line 23:
: not found/tmp/migration.sh: line 26:
/data/local/tmp/migration.sh: line 27: syntax error: unexpected word (expecting “in”)
What I did wrong?