My friend that has a Nexus 6 said that his TWRP has the option to decrypt his internal storage built in to it in order to make flashing files easier and less troublesome while using full disk encryption. The latest unofficial recovery for the E980 however does not. Is there any way we could get this feature added to the current unofficial build of TWRP 2.8.1.0 for the E980? I think many people would benefit from this. Of course I am probably going to be ignored as usual, but I thought it is worth a try to see if anyone can help. Does anyone have the source code for it?
Related
So I was forced by my employer to enabled Device Encryption on my Gnex. Not a huge problem, as we already had to enter a PIN/Password to access company email. Fine.
So then I decide to switch ROMs from CNS 1.5.1 to AOSP r7, and lo and behold, when I flash, everything on my sdcard has been devoured. I did not select any options to do a full wipe, and as I would come to find out later, I couldn't have if I wanted to, since even the latest version of TWRP doesn't know how to correctly decrypt using the supplied PIN.
So here I am with my thumb up my ass wondering how to prevent this from happening again. I'm also considering decrypting my device, leaving it decrypted, and just using the web interface for my work mail.
Is this expected?? I'm reading in other threads for other devices that TWRP and CWM both don't know how to decrypt Samsung phones.
Say it ain't so....
maxawesome said:
So I was forced by my employer to enabled Device Encryption on my Gnex. Not a huge problem, as we already had to enter a PIN/Password to access company email. Fine.
So then I decide to switch ROMs from CNS 1.5.1 to AOSP r7, and lo and behold, when I flash, everything on my sdcard has been devoured. I did not select any options to do a full wipe, and as I would come to find out later, I couldn't have if I wanted to, since even the latest version of TWRP doesn't know how to correctly decrypt using the supplied PIN.
So here I am with my thumb up my ass wondering how to prevent this from happening again. I'm also considering decrypting my device, leaving it decrypted, and just using the web interface for my work mail.
Is this expected?? I'm reading in other threads for other devices that TWRP and CWM both don't know how to decrypt Samsung phones.
Say it ain't so....
Click to expand...
Click to collapse
what version of twrp are you using? the newest version supposedly fixed decrypting.
simms22 said:
what version of twrp are you using? the newest version supposedly fixed decrypting.
Click to expand...
Click to collapse
The very latest version that can be downloaded via GooManager. I always update it before flashing any new ROMs. This was done last night, so the very latest version GooManager installs as of around 9PM PST yesterday. 2.3.2.1 I suppose?
I was reading that the new TWRP revision supports decrypting aosp and twiz encrypted partitions, so i made an attempt to try it with CM10.1 Build 2/19/2013 and TWRP can see that its encrypted but it cant decrypt it, it just keeps saying invalid password.
So i changed my cryptfs password thinking the pin password was messing with the twrp backend or something, but still no love with the new password.
Has anyone else tried this?
webstas said:
I was reading that the new TWRP revision supports decrypting aosp and twiz encrypted partitions, so i made an attempt to try it with CM10.1 Build 2/19/2013 and TWRP can see that its encrypted but it cant decrypt it, it just keeps saying invalid password.
So i changed my cryptfs password thinking the pin password was messing with the twrp backend or something, but still no love with the new password.
Has anyone else tried this?
Click to expand...
Click to collapse
I had the exact same experience on CM10.1 on the Sprint S3 with the newer TWRP 2.4.3 as well. I pinged the devs in the IRC channel about this and they offered little assistance. They basically said the Nexus devices would have the highest level of TWRP encryption support. I am a bit disappointed about this. This is a feature I definitely need.
same same
swiggs98 said:
I had the exact same experience on CM10.1 on the Sprint S3 with the newer TWRP 2.4.3 as well. I pinged the devs in the IRC channel about this and they offered little assistance. They basically said the Nexus devices would have the highest level of TWRP encryption support. I am a bit disappointed about this. This is a feature I definitely need.
Click to expand...
Click to collapse
Hi, tried it too today with the twrp 2.5.0 and have the same problem.
webstas said:
I was reading that the new TWRP revision supports decrypting aosp and twiz encrypted partitions, so i made an attempt to try it with CM10.1 Build 2/19/2013 and TWRP can see that its encrypted but it cant decrypt it, it just keeps saying invalid password.
So i changed my cryptfs password thinking the pin password was messing with the twrp backend or something, but still no love with the new password.
Has anyone else tried this?
Click to expand...
Click to collapse
I've had this trouble on a custom rom as well. Encrypted my phone for work and now I can't get decrypt my device for TWRP (v2.5). Now I can't even wipe my phone to permanently decrypt device lol. Guess the only choice is to ODIN back to stock and re-root?
EDIT: Just deleted the account that forced the encrypt and restarted. Now have the ability to decrypt device in Security settings. Would much rather have that freedom with my device than be stuck encrypted and have company access haha.
I use CM 10.1 and unfortunately I have the same exact issue. I wish I could find out what the problem is and help them fix it.
Same problem on SGS3 LTE with TWRP 2.5.0.0 and CM10.1. Can't update it anymore :/. Too bad since I'm used to update daily.
In case you are not aware, 2.6.0.0 has been out for a week or two. Give it a try. Probably won't do much better but you don't know unless you try it.
Sent from my SGH-T999 using xda premium
Tryied 2.6.0.0 just now, still the same -- "Password Failed, Please Try Again", all the time.
Ahh well, worth a try...sorry.
Sent from my SGH-T999 using xda premium
On CM site, I found a page (/blog/security-and-you) with the following remark:
"Warning for emmc only users – encrypted /data means recovery will be non-functional."
Click to expand...
Click to collapse
which apparently means we're stuck don't know whether we can do anything about it. First thing is to figure out why so....
Actually, TWRP claims that it can decrypt partition decrypted by both Samsung stock and AOSP firmwares. There're issues opened on their GitHub for several Samsung devices.
i googled it and there are people with other phones saying their twrp asks for encryption password and can still perform flashes and backups on an encrypted phone (i realize there are also alot of ppl who it doesn't work for) just wondering if anyone has gotten it working on G3.
Yes. I have the nexus 9 encrypted and when I go on twrp and ask me for my password (using a full keyboard) and it does take a longer time to perform the operation .
Sent from my LG-D852 using Tapatalk
Same problem here. Can't get /data to mount in TWRP. Had the same problem in some versions on Nexus 4, but it always got fixed quite fast. Would be nice to get it working on the G3... Tried to compile TWRP myself, but failed badly...
A while ago I posted a workaround to use custom recovery and full device encryption and it seems like it's STILL needed, meaning I can't use TWRP, unless someone has found a ROM that has working encryption with TWRP? I've tried a few ROMs so far, as well as the latest stock ROM (NJ2 - 4.4.2). TWRP just gives the error "cannot find crypto footer" and the devs have said in the past this is a "wontfix" problem. I'd really, really like to put Marshmallow on here but I need full device encryption and TWRP support. So frustrating.
I don't mind wiping this device and re-encrypting as many times as needed, I just need it working.
Hi everybody,
After the cm13 on my Zenfone 2 (ZE551ML / Z200A) crashed down with no recent backups, I decided to upgrade to Lineage OS 14 now that I had to reinstall the ROM anyways. And now I'm stuck:
My device is encrypted (as it always has been). Since the first boot of Lineage OS the encryption method seems to have changed to an Android Nougat - specific encryption method. That means:
My installed TWRP 3.0.2 is now unable to decrypt the phone (known issue, as I found out).
The TWRP version 3.1 that would be able to decrypt it, is however not available for my Zenfone 2.
Even without a screen password, PIN or pattern set, TWRP still promts for a decryption password.
Without the TWRP working, I believe I cannot make any changes to the system, e.g. downgrading back to cm13, without wiping the entire internal storage.
The only thing that does seem to work is ADB sideload, but even so, Google Play Services installed from a side-loaded GAPPS e.g. doesn't work.
Now, how can I restore a state on that phone model where I have a working TWRP recovery that can modify the system partition?
Is there maybe an unofficial TWRP 3.1 for the Zenfone 2 or an alternative recovery that does handle the Nougat encryption?
Or is it somehow possible to downgrade back to cm13 without decrypting yet without losing all data on the internal storage?
I'm scared of trying to compile TWRP 3.1 from the source code myself as I have no experience "building" whatsoever.
Thanks for your help!!
Have you tried 3.0.3 available in the LinOS thread?
Sent from my ASUS_Z00A using Tapatalk
Yes, as available on theflamingskull.com. Either version cannot decrypt the phone (even when re-installed).
This one works for my encrypted phone (encrypted with CM14.1):
https://www.androidfilehost.com/?fid=457095661767154983
Even with encrypted f2fs (changed to f2fs with this one).
Z200A is Z00A Essentially, right?
If yes: https://infinitus-rom.com/devices/asus/asus-z00a
You can download TWRP 3.1.0 there
I use this one too, it works flawlessly
Thank you!! Those worked! For some reason I always flashed version 3.0.3-M3 without noticing the M3 at the end. Starting with version 3.0.3-M4 as you linked, I was able to get back into recovery decrypting my phone! :good: