1

My S10e is running LineageOS 19.1, rooted with Lygisk. After one specific reboot after changing the SIM card, it entered a boot loop where it showed the Lineage boot animation for a few minutes, then reboots. I never got to the unlock screen anymore.

After reinstalling bootloader etc. as well as dirty flashing LineageOS, the phone boots up again but I don't get access to data on the interal /sdcard. The partition is accessible but all files/folders are encrypted. Trying to access them in TWRP terminal (or trying anything else like Nandroid backup) I always get the error "Required key not available".

So, my questions are:

  • can I in some way bring the phone's software to exactly the same state as before and making it recognise data, so that I can decrypt it?
  • will enabling phone encryption again and using the same lock/encryption pattern be sufficient? (I fear not)
  • Or is my assumption that it should be possible to reconstruct the key when using the same lock pattern on the same hardware & software flawed in general?
  • EDIT:
  • Is there any kind of redundancy of storing keys in LineageOS, which would allow to restore the original one?
  • I do have a SeedVault backup - does it include the original encryption keys?
11
  • 1
    Only in some old Android versions the cryptographic key (for the user data partition) was directly derived from the lock pattern/pin/password. On recent versions this is not the case instead random generated keys are used, protected e.g. using GateKeeper, so I doubt that you will be able to "reconstruct" the key. Not sure how exactly the keys management works on LineageOS.
    – Robert
    Mar 10 at 13:41
  • 1
    /sdcard actually is /data/media so it's very unlikely you have decrypted /data
    – alecxs
    Mar 10 at 20:23
  • @alecxs I didn't mention /data but "data" on /sdcard, more specifically user data mounted from /dev/block/platform/13d60000.ufs/by-name/userdata
    – nopopem
    Mar 10 at 21:06
  • /dev/block/platform/13d60000.ufs/by-name/userdata is the only rw partition, all other partitions are mounted ro. all data is saved in /data. My best guess is the encrypted files in /data/media/<user> belong to another profile and therefore cannot decrypted with same credentials like the rest of files?
    – alecxs
    Mar 11 at 7:45
  • Ok, maybe I mixed things up, seeing different paths at different stages via adb shell vs TWRP terminal. Current situation is I see all those encrypted folders in /data/media/0 which belongs to my original profile (there never was any other profile on the phone). Shouldn't I see a fileencryption= parameter in fstab somewhere (there is none)?
    – nopopem
    Mar 11 at 10:52

0

You must log in to answer this question.

Browse other questions tagged .