Mh, that sucks, patterns might be a special case then. What ROM you on? I read that there might be problems with patterns on CM13. Also, what exactly does not work? Are you not asked for a pattern or is your pattern just not accepted? And finally, there was a bug in twrp that any pattern larger than 3x3 didn't work. Can you temporarily change it to a 3x3 and see if it works then? At least this way I know if it's that bug that's supposed to be fixed.
TWRP 3.0.2 for amami update
- Thread starter sharonliu
- Start date
It's cm12.1 with a 4x4 pattern. It asks me for the pattern, but the console says unable to decrypt and unable to mount storage...
Could you try to get your build properties included into official TWRP support devices build server? This would be awesome to get our device officially supported. Maybe you can get into touch with the Devs in IRC and ask them what they need from you to set up an official build. Or maybe ask fefifofum who is supporting the LG Pad 8.3.
encryption of data didn't work for me too. just to clear for me.
pattern 3x3 mean a password with 9 letters?
and 4x4 means 16 letters?
pattern 3x3 mean a password with 9 letters?
and 4x4 means 16 letters?
Well, the way I understand it is that they are passwords that are made up out of a selection of a total of either 9 or 16 numbers. These numbers however then get converted into hex, and that is your password.
The problem here is (from the info I could gather) that there are different ways of how this conversion is done, depending on both Android versions and whether you run a custom ROM (since anything larger than 3x3 does not exist in pure AOSP, at least until LP).
I have made a new build a week ago, since there have been some commits that _might_ fix some issues - one of which is using a "password" of an odd length. I haven't uploaded it yet because I wanted to wait for TWRP to hit v. 3.0.3. But I can upload it tonight it you want to try it.
Edit: It could also be helpful if you post a recovery log after the failed decryption attempt.
The problem here is (from the info I could gather) that there are different ways of how this conversion is done, depending on both Android versions and whether you run a custom ROM (since anything larger than 3x3 does not exist in pure AOSP, at least until LP).
I have made a new build a week ago, since there have been some commits that _might_ fix some issues - one of which is using a "password" of an odd length. I haven't uploaded it yet because I wanted to wait for TWRP to hit v. 3.0.3. But I can upload it tonight it you want to try it.
Edit: It could also be helpful if you post a recovery log after the failed decryption attempt.
Last edited:
yes, please share the new build. i attach the recovery.log but seems not very helpfull to me.
OK, will upload it when I'm home tonight.
I'm not trying to ask a stupid question here, but are you sure you are using the TWRP from my post and not the one from OP? According to your logs, several partitions are tried to be mounted as ext4, whereas I changed that to auto (and my logs do say auto, too).
Also, your TA partition isn't being mounted, which is necessary for decryption to work. So I'm pretty sure you aren't running the right version.
Last edited:
you are completely right. i had used the twrp from first post. now i have flashed your one and its working like a charm.
Great to hear. So the log was useful after allyou are completely right. i had used the twrp from first post. now i have flashed your one and its working like a charm.
Maybe I will upload it tonight anyway. It might fix the issues with the 4x4 pattern (though maybe indirectly) that @frauhottelmann encountered.
I uploaded a new build. Some commits in TWRP might fix the larger than 3x3 pattern decryption. If somebody gives it a try, please report back.
Also added the tzdata to the recovery. I'm not sure if it really changes anything, of if it's just a cosmetic improvement by avoiding the error messages in the log. Also added a couple of TWRP flags.
https://www.androidfilehost.com/?fid=24533103863142425
Also added the tzdata to the recovery. I'm not sure if it really changes anything, of if it's just a cosmetic improvement by avoiding the error messages in the log. Also added a couple of TWRP flags.
https://www.androidfilehost.com/?fid=24533103863142425
Last edited:
Hi derf elot! After using TWRP 2.8.7. for a while now with working data partition decryption capability, I tried your latest version. But sadly it does not successfully decrypt data partition on start of TWRP, because it states my password would be wrong. I have PIN as security method, but changed this to a more complex passphrase within CM-security options (similar to the app cryptfs).
So I reverted back to 2.8.7.
So I reverted back to 2.8.7.
Hi,
I think this _might_ be because of the different ways encryption is handled in KK vs. LP, a lot has changed. I'm guessing you are on one of my CM11 builds, right? From what I gathered by looking at the TWRP code, the way decryption is handled depends on the sdk version set in the default.prop inside the recovery. Since I built from within CM12.1, this is 22 of course. I have unpacked the recovery, changed this value to 20 (KK) and repacked it. I am not entirely sure if this will work or if TWRP decryption is simply not compatible with KK anymore starting in version 3, but it's worth a try. I uploaded the repacked recovery for you:
https://www.androidfilehost.com/?fid=24533103863142853
If this doesn't work, I'd recommend to stick with what works for you. Version 3 is mainly for LP and MM anyway I think.
Cheers
Thank you! Yes I am on your latest CM11-Build. I am going to try repacked twrp later this day.
Edit: Sadly it did not work. But as TWRP 2.8.7 works for me (besides some issues with passwords and encrypted backups, when I have to enter those multiple times until it starts restoring) I'll stick with that
Edit: Sadly it did not work. But as TWRP 2.8.7 works for me (besides some issues with passwords and encrypted backups, when I have to enter those multiple times until it starts restoring) I'll stick with that
Last edited:
Mh, that's too bad. Guess it would have been too easy If you want, you can post a recovery.log after the failed decryption attempt and I can have a look when I get the chance.
If you want, you can post a recovery.log after the failed decryption attempt and I can have a look when I get the chance.
Thanks, but no worries, I just stay on the old TWRP-version for the time being. This weekend I plan to test your new CM13-build anyway, so hopefully new TWRP will work out of the box with MM.
I used this version with Dirty Unicorn 6.0.1. It worked well to install the ROM but now I can't get back into the recovery, even though it worked before. No idea if that is a problem with TWRP or Dirty Unicorn. Just thought, some people might want to know
From DU thread:I used this version with Dirty Unicorn 6.0.1. It worked well to install the ROM but now I can't get back into the recovery, even though it worked before. No idea if that is a problem with TWRP or Dirty Unicorn. Just thought, some people might want to know
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone