True, my bad. I forgot that part.
Funnily enough I found out you can edit the default.prop in the recovery image to authorize it even with encryption on. Almost feels like you shouldnt be able to do that.
True, my bad. I forgot that part.
Just tried it, and it works to a degree, but doesn't hold settings and nor does it decrypt your storage. Stick with 3.2 on Oreo.
repo init -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-9.0 mkdir .repo/local_manifests cat > .repo/local_manifests/twrp.xml <<EOF <?xml version="1.0" encoding="UTF-8"?> <manifest> <!-- SONY --> <project name="cryptomilk/android_kernel_sony_msm8998" path="kernel/sony/msm8998" remote="github" revision="lineage-17.1" /> <project name="cryptomilk/android_device_sony_common-treble" path="device/sony/common-treble" remote="github" revision="twrp-9.0" /> <project name="cryptomilk/android_device_sony_yoshino" path="device/sony/yoshino" remote="github" revision="twrp-9.0" /> <project name="cryptomilk/android_device_sony_lilac" path="device/sony/lilac" remote="github" revision="twrp-9.0" /> <project name="cryptomilk/android_vendor_sony_lilac" path="vendor/sony/lilac" remote="github" revision="lineage-16.0" /> <!-- QCOM --> <project name="android_device_qcom_caf-sepolicy" path="device/qcom/sepolicy" remote="omnirom" revision="android-9.0" /> <project name="android_vendor_qcom_opensource_commonsys" path="vendor/qcom/opensource/commonsys" remote="omnirom" revision="android-9.0" /> <!-- TWRP --> <remove-project name="android_bootable_recovery" /> <project name="TeamWin/android_bootable_recovery" path="bootable/recovery" remote="github" revision="android-9.0" /> </manifest> EOF repo sync # this will take a long time cd device/sony/lilac ./extract-files.sh /path/to/vendor-files cd - export WITH_TWRP=true export ALLOW_MISSING_DEPENDENCIES=true # required by minimal-manifest-twrp . build/envsetup.sh lunch omni_lilac-eng mka -j5 recoveryimage # 5 is the number of parallel tasks to run. CPU cores + 1 is a good choice.
- 'Weird' restore procedure TWRP Android 10.0 (twrp-3.3.1-0-lilac-android10-1.img) -
I experienced difficulties when restoring a backup from my phone with 'lineage-17.1-20200714-UNOFFICIAL-v1.3-lilac' installed. In the first place I did not understand what to backup, since there is next to the system and vender partition also the system image and vender image in the TWRP backup menu. Anyhow...
I found out I had to back up the following partitions:
- System Image
- Vendor Image
After wiping all the data via 'Advaned Wipe' with 'Use rm -rf instead of formating' enabled in settings, reboot recovery.
When TWRP is rebooted and after again enabling 'Use rm -rf instead of formating' I try to restore the backup.
Problem: if I try to restore all the above mentioned partitions in one go, I get the createTarFork() process ended with ERROR=255 error when TWRP tries to restore the Data partition.
Solution: reboot system (TWRP mentions there is no OS installed), LineageOS is booted and the installation menu is showed, because the Data partition is not restored obviously. Reboot back into TWRP, restore the data partition, reboot system and the restore is finally complete.
Took me some time and fustration to figure out... I did not see this mentioned somewhere (correct me if I am wrong) ??
Are there others experiencing the same issue? Or is my backup method incorrect??
Either way I find this a little sketchy, and does not create a lot of confidence in the phone's backup, because I don't know what going on.
Not sure why this is happening, perhaps an insufficient or incompatible power supply issue, but the solution is to try different computers/USB ports. Also, in my case it only worked with Linux, EndeavourOS to be specific, but should work on Ubuntu or any other "complete" Linux OS/distro.
Don't wait on TWRP updates in this thread, get the latest version from the source and reflash it, it works for me on ROMs with Android 11 and 12: https://twrp.me/sony/sonyxperiaxz1compact.html
It's because of the encryption. Files on LineageOS 19 are encrypted if accessed via TWRP recovery, LineageOS 19 (maybe 18 also) has its own alternative recovery that can be installed during the first boot, perhaps the files are not encrypted if accessed from there. Either way, it's a security measure against unauthorized access to files. I'm pretty sure I've read somewhere that it's a default feature in Android 12.
The error 255 is caused due to insufficient space. One solution is to backup or restore one or several partitions at a time instead of all at once, alternative solution is to back up to external memory card.
gpg --keyring ./gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg --verify recovery.img.asc