Here’s a new CUSTOM build made from the v1.8.1-s tag. (See here for information about build types)
The reason it is CUSTOM rather than UNOFFICIAL, is that in this build it is possible to use Trebuchet as the default Home / Launcher app. If you clean flash the build, you will be offered a choice between Trebuchet and Bliss at the end of first time setup. This was achieved by changing two lines of code, (shown in the patch in my previous post).
I don’t plan to make an UNOFFICIAL build without the Trebuchet change: if you don’t want to use Trebuchet, then choose Bliss, which should work as well as it always does
I have clean flashed the build and it seems to work: the test phone boots up fine, receives calls and SMS, internet access via WiFi and mobile network both work, fingerprint scanner works. It should dirty flash OK over previous unofficial and custom S builds, but - as always - use at your own risk.
I don’t really know, but I allowed the root debug and then wrote the same but with sudo first.
The first time I dit it, it didn’t work but then I re-did the same (I also wrote sudo adb devices while in TWRP) and then sudo adb sideload and this time it worked.
Honestly I’m not sure why the last time worked, I’m sorry
I haven’t used TWRP backup for a while - sorry. Were you trying to backup just the data partition or Boot, System and Data?
I remember seeing something like this in the past when trying to backup with no screen lock set. I think that Android does encryption using a key based on the screen lock (Pattern or PIN). If no screen lock is set, then a random key is generated and used. When TWRP starts, if screen lock is set, the PIN or pattern must be entered, and is therefore available for TWRP to use to decrypt the data. If there is no screen lock set, then TWRP does not have access to the generated random key, and is therefore unable to decrypt the data, so fails to backup, with the error message you quote.
So, if you don’t already have a screen lock set, you may be able to get round this problem by setting a PIN or pattern in /e/OS, then rebooting to TWRP, entering the PIN or pattern, and re-trying the backup.
If you do already have a screen lock set, then I don;t know what the problem is - sorry!
The reason I haven’t used TWRP backup in a while is that I use Android Backup and Restore Tools project to back up user apps and data. It backs up just about everything I need, except for
eCloud / Murena account details. I can live with the hassle of re-entering this when I need to restore or migrate apps
email accounts and setting: I export them using the app to my external SD card
I was trying to backup boot system and data.
I have a PIN and that’s the problem, it doesn’t ask me for my PIN code anymore (in TWRP).
That’s the first time since I went from 1.7-q to 1.7-s that I go to TWRP. Before the update it always asked me for my PIN but this time it didn’t.
I read a few things but I didn’t see any answers…
Maybe a re-install we’ll do it ?
But if I do that, will I have to re-install every apps ?
I think you will need to update your TWRP: earlier versions won’t cope wiht the changes to file encryption between Android Q and Android S.
I use version 3.6.2_12-0 from here https://sourceforge.net/projects/yoshino/files/lilac/twrp/
The only part that doesn’t work is the Exposure Notification framework, which is only needed a f you run a Covid contact tracing app. The EN framework doesn’t work in any /e/ devices, not just this device.
