[ROM][UNOFFICIAL] LineageOS 17.1 for Xperia 10 II [OTA][SODP]

[bamdadkhan]

Well... The kernel of the current builds triggers a double free call on something inside the EXT4 filesystem - as my system only crashes on first login I assume something is really broken inside the decryption routines... Which is very, very bad... I'll try to use an other version of the kernel, but I guess all data is doomed at this point.

And regarding the Lineage Recovery: I could strip it, but won't be able to include any replacement (I have currently no time to integrate or even port the TWRP fork for SODP)... So, I'll let it be as it is.

i understand it would be hard to maintain. not to mention the available TWRP has some issues it seems (decryption, ADB sideload etc.)

"FIXED" IT! I was able to boot my device using an older kernel version - it seems like newer kernel versions have a bug inside the EXT4 filesystem driver, which causes the system to panic during decryption! I'll try to recompile my engineering build as userdebug and push it ASAP. Again, I'm very sorry for your data loss, but I hope this saves others from experiencing the same pain.

no worries, at least this reminded me that i need a proper backup solution and set up a nextcloud instance on a VPS. : )
too bad i didn't have any other option but to lose all my data and go with a different ROM for the time being. never would have suspected the ext4 module as it's so mainstream..

this makes me wonder though.. do you know of any full nandroid(-like) backup solution with LOS recovery? that way i could take a snapshot of my current working setup, flash oem from SODP and try your debug build(s) without much hassle..

 

[Simonmicro]

> no worries, at least this reminded me that i need a proper backup solution and set up a nextcloud instance on a VPS. : )

Hehe - this is also my solution

> this makes me wonder though.. do you know of any full nandroid(-like) backup solution with LOS recovery? that way i could take a snapshot of my current working setup, flash oem from SODP and try your debug build(s) without much hassle..

Well, recoveries are all not happy with the FBE of newer Androids... I personally use TitaniumBackup, as it may has an very old UI (it still works) BUT needs an running OS (either fresh or your current). As your files are all encrypted using a key only available inside the physical hardware "keystore" there is no real way of just copy-paste your data, either using the raw partition-images or using file-based solutions. Any new OS installation tends to wipe that keystore and install its own keys into it.
Maybe you could try to rsync all your files from /data/data and this way circumventing the encryption. Keep in mind there is a good chance, that the OS itself uses some sort of secret key to authenticate itself against the hardware keystore - if you restore this key you will basically wipe the keystore again and this way lock the encryption again

 

[bamdadkhan]

> no worries, at least this reminded me that i need a proper backup solution and set up a nextcloud instance on a VPS. : )

Hehe - this is also my solution

> this makes me wonder though.. do you know of any full nandroid(-like) backup solution with LOS recovery? that way i could take a snapshot of my current working setup, flash oem from SODP and try your debug build(s) without much hassle..

Well, recoveries are all not happy with the FBE of newer Androids... I personally use TitaniumBackup, as it may has an very old UI (it still works) BUT needs an running OS (either fresh or your current). As your files are all encrypted using a key only available inside the physical hardware "keystore" there is no real way of just copy-paste your data, either using the raw partition-images or using file-based solutions. Any new OS installation tends to wipe that keystore and install its own keys into it.
Maybe you could try to rsync all your files from /data/data and this way circumventing the encryption. Keep in mind there is a good chance, that the OS itself uses some sort of secret key to authenticate itself against the hardware keystore - if you restore this key you will basically wipe the keystore again and this way lock the encryption again

yeah i know all about those, but TiBackup is ooooold and doesn't really handle xapks properly. rsyncing is fine, but you need a running system *or* a non-limited recovery to have access to the decrypted partition. i'm also thinking of simply using fastboot to dump the partitions one by one with a script on my laptop.. might look into that.

this reminds me how easy it was to switch between systems before LOS crippled their recovery and before all this slot a/b nonsense.. : (((

 

[Simonmicro]

Hey,

as you guys may have already noted, I have stopped the active development phase for this LOS port a while ago. This was caused by me just not having enough time to do everything and additionally maintain a LOS port.

Today I'll upload the last maintenance build to the OTA server and mirrors. Of course I somehow included a little bug, which causes the system to complain about "an internal problem", which seem to be caused by some interaction with the OpenGApps package installer. Now, it is a feature. I'll may post one more update, if I figure this one out.

Nevertheless, I'll shut down the OTA service at 2022-06-01 (see https://status.simonmicro.de) and will then archive all project data. It was a great time to learn many (new/nasty) things about Android and how everything works. I have to say "thank you" to everyone, who supported me and was on board with this project.

See you next time,
simonmicro