| 27 Jan 2025 |
 autra | yes | 20:52:25 |
 pentane ⭔ | If you try to sideload an OTA zip via the recovery which has a lower (i.e. earlier) SPL than your currently installed system, it will refuse to flash the OTA zip | 20:53:08 |
| pentane ⭔ | If that's the case you need to manually edit the SPL in these two files to match the SPL of your currently installed system | 20:53:40 |
| autra | ok got it! | 20:54:03 |
| autra | If I only go forward, the flash is enough right? | 20:54:33 |
 atemu12 | No | 20:54:45 |
| atemu12 | This is about signing keys | 20:54:48 |
| atemu12 | They're encoded in the system app metadata for some reason | 20:55:03 |
| atemu12 | So if you change ROMs, you must change the singing keys | 20:55:20 |
| atemu12 | cyclopentane ⭔ migrated her phone from and to offical LOS keys a few times, so it works fine but you do need to do it beforehand | 20:55:51 |
| atemu12 | https://wiki.lineageos.org/signing_builds#using-a-script | 20:56:23 |
| atemu12 | * cyclopentane ⭔ migrated her phone from and to offical LOS keys a few times, so it works fine but you do need to do it before flashing | 20:56:40 |
| pentane ⭔ | If you want to keep your data, you need to run a key migration script to change the keys on your userdata partition from the LineageOS release keys to the test-keys (the ones Robotnix uses per default), as described here: https://wiki.lineageos.org/signing_builds#test-keys-to-official-or-vice-versa | 20:56:46 |
| pentane ⭔ | You can find the script here: https://github.com/LineageOS/scripts/blob/main/key-migration/migration.sh | 20:57:10 |
| atemu12 | Oops, I had the wrong link | 20:57:10 |
| atemu12 | No wait, I didn't | 20:57:44 |
| atemu12 | ^^' | 20:57:51 |
| pentane ⭔ | It's the same but slightly different anchors | 20:57:55 |
| autra | Thanks! Is it compulsory even if I don't plan to relock the bootloader and I'm fine with the warning at boot? | 20:58:04 |
| pentane ⭔ | It's needed if you want to keep your data | 20:58:16 |
| pentane ⭔ | If you're okay with wiping your phone, then you don't need to migrate keys | 20:58:28 |
| atemu12 | Signing isn't cumpulsory though; I don't sign my builds for instance and just use test keys | 20:58:32 |
| autra | ok so if I understand correctly, either I keep my signed build but follow the migration instruction, or I rebuild with signing disabled. | 21:00:21 |
| atemu12 | No, you need to migrate either way | 21:00:34 |
| atemu12 | Signing cannot be disabled I think | 21:00:45 |
| pentane ⭔ | Wait a sec, there seems to be some confusion as to what "signing" means here: | 21:01:10 |
| atemu12 | It falls back to test keys which are effectively unsigned because the private key is public but technically still a signature | 21:01:12 |
| pentane ⭔ | When you build a LineageOS image, the system image is cryptographically signed. There are three options for the keys the image can be signed with:
- the official LineageOS keys (
release-keys). We don't have access to them, so the only images signed with these keys are the official LineageOS builds.
- the test keys (
test-keys). These keys are publicly available, and Robotnix uses them by default.
- your own release keys.
| 21:03:24 |
| pentane ⭔ | When you run LineageOS and install apps that save stuff to your phone, that data is somehow "coupled" to the keys your LineageOS install was signed with (don't ask me about the details though). If you try to boot a LineageOS install with an image that was signed with different build keys than the ones your user data was coupled to, it will complain and not boot. | 21:04:52 |
| pentane ⭔ | * When you run LineageOS and install apps that save stuff to your phone, that data is somehow "coupled" to the keys your LineageOS install was signed with (don't ask me about the details though). If you try to boot a LineageOS install with an image that was signed with different build keys than the ones your user data was coupled to, it will complain and not boot (I believe). | 21:05:58 |
