Cannot Decrypt

[sureguy]

Tried the following on SGS3 running CM11-20140708-SNAPSHOT-M8 (4.4.4)+
TWRP v2.6.3.0 [d2can] - Unable to decrypt
TWRP v2.7.0.0 [d2can] - Unable to decrypt
TWRP v2.7.1.0 [d2can] - Unable to decrypt

Copied and pasted from #247 which is closed. I'm experiencing the same issue.

[wertarbyte]

I have the same issue here with i9300 - it's a real showstopper :-/

[jgus]

Ditto on d2spr. :-(

[alextoombs]

+1

[kasiub]

I have the same issue with cyanogen M8 on GT-I9300...

[BossLX]

+1

[jgus]

Still an issue with TWRP v2.8.0.1 on d2spr

[Alphakilo]

Still an issue on my i9300, using TWRP 2.8.0.1

The workaround posted in #247 by @boeleman no longer works, due to the vdc binaries missing.

[Muellersirch]

I am having this issue on my HTC m8 (Sprint). I was previously unable to find a decrypt option (several versions, up to the current official release). After working with Captain_Throwback, we got the option to decrypt to show up, but it does not accept the password. I am still using the original password that I set the encryption up with, and have no issues decrypting when booting into the system. I am currently running the CM11 nightly from 10/10.

[brbsix]

I had this same issue a while back on my d2lte/d2tmo after upgrading to 4.4.2 and it drove me nuts. Not one of the TWRP binaries available would properly decrypt /data in recovery. It would prompt for the password and fail.

I don't recall precisely what I did, but I ended up having to download all the CM and TWRP sources, tweak a few things, then compile the recovery myself. I'm not sure why all of the public binaries failed to handle decryption properly, but at least the source is fully functional.

[sureguy]

While that provides some hope, without steps to correct the problem we're left with hope, not a solution. Not your fault, at all - and thanks for taking the time to offer your input. I just wish TWRP devs would chime in with a "we know it's broken and are looking into it" or "we know it's broken and can't/don't care to fix it"

…

On Wed, Oct 15, 2014 at 12:02 AM, brbsix <notifications@github.com> wrote: I had this same issue a while back on my d2lte/d2tmo after upgrading to 4.4.2 and it drove me nuts. Not one of the TWRP binaries available would properly decrypt /data in recovery. It would prompt for the password and fail. I don't recall precisely what I did, but I ended up having to download all the CM and TWRP sources, tweak a few things, then compile the recovery myself. I'm not sure why all of the public binaries failed to handle decryption properly, but at least the source is fully functional. — Reply to this email directly or view it on GitHub <https://github.com/TeamWin/Team-Win-Recovery-Project/issues/293#issuecomment-59154999> .

-- Simon Bolduc

[Alphakilo]

So you could provide a patch? 2014-10-15 6:02 GMT+02:00 brbsix <notifications@github.com>:

…

I had this same issue a while back on my d2lte/d2tmo after upgrading to 4.4.2 and it drove me nuts. Not one of the TWRP binaries available would properly decrypt /data in recovery. It would prompt for the password and fail. I don't recall precisely what I did, but I ended up having to download all the CM and TWRP sources, tweak a few things, then compile the recovery myself. I'm not sure why all of the public binaries failed to handle decryption properly, but at least the source is fully functional. — Reply to this email directly or view it on GitHub <https://github.com/TeamWin/Team-Win-Recovery-Project/issues/293#issuecomment-59154999> .

-- PGP Public Key: 56AFB56B @ pgp.mit.edu http://pgp.mit.edu/pks/lookup?op=get&search=0x42F0C03156AFB56B