New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CM13 & TWRP 3.0.0.0 on jfltexx not accepting right 5x5 decryption Pattern #588

Open
EXTREMEGABEL opened this Issue Feb 24, 2016 · 29 comments

Comments

Projects
None yet
@EXTREMEGABEL
Copy link

EXTREMEGABEL commented Feb 24, 2016

No description provided.

@player-03

This comment has been minimized.

Copy link

player-03 commented Feb 25, 2016

Experiencing the same on shamu.

To reproduce:

  1. Create a new encryption pattern by going to settings -> lock screen -> screen lock -> pattern. When prompted, make sure "require pattern to start device" is checked, then create a 5x5 pattern.
  2. Reboot into recovery mode.
  3. On the "decrypt data" screen, tap the 5x5 button and enter the pattern you chose.

Result: TWRP will respond with "Pattern failed, please try again!"
Expected result: TWRP will successfully decrypt the partition.

Other notes:

  • CyanogenMod can decrypt the partition using the same 5x5 pattern (as expected).
  • Following those steps for a 3x3 pattern allows TWRP to decrypt the partition.
@Pietia10

This comment has been minimized.

Copy link

Pietia10 commented Feb 26, 2016

Cm 13 nightly oneplus one(bacon) and TWRP 3.0.0.1 same bug even with 3x3 pattern.

@EchoDev

This comment has been minimized.

Copy link

EchoDev commented Feb 28, 2016

Decryption also fails with PIN on CM13 nightly and TWRP 3.0.0.x

@radumas

This comment has been minimized.

Copy link

radumas commented Feb 29, 2016

Ditto hammerhead and 6x6 pattern

@Stokel

This comment has been minimized.

Copy link

Stokel commented Feb 29, 2016

Same with password and also after changing to 5x5 and 3x3

@nickalleyne

This comment has been minimized.

Copy link

nickalleyne commented Mar 8, 2016

This seems to be happening for me also when using a pin code, and on stable 12.1 CM with TWRP 3.0.0.x

@huegelc

This comment has been minimized.

Copy link

huegelc commented Mar 12, 2016

Failes also with Exodus 6. TWRP wont accept correct PIN. Had to format data to remove encryption

@zhimsel

This comment has been minimized.

Copy link

zhimsel commented Mar 14, 2016

Same issue happening with me on Bacon with CM13 nightlies and TWRP (2.6.8.0-3.0.0-1). I tried with password, pin, and pattern.

@briancross

This comment has been minimized.

Copy link

briancross commented Mar 22, 2016

Same issue with oneplus2 on CM13 and TWRP 3.0.0-2 (2.8.7.2 also). No option to enter my PIN as a "PIN", and entering it as text with the QWERTY keyboard fails as well.

Can flash /system just fine, but have to sideload, USB-OTG, or flash small zips from /cache as I cannot access /data to get to /data/media.

@ihor-sviziev

This comment has been minimized.

Copy link

ihor-sviziev commented Mar 24, 2016

I have same issue as @briancross on 3.0.0-2 for OnePlus 2 + Unofficial CM 13 by Grarak. Please fix this issue.

@briancross

This comment has been minimized.

Copy link

briancross commented Mar 24, 2016

It's a ROM issue, not recovery and should be fixed in his latest build or
any build using his sources. I haven't had a chance to treat myself though.
On Mar 24, 2016 5:25 PM, "Ihor Sviziev" notifications@github.com wrote:

I have same issue as @briancross https://github.com/briancross on
3.0.0-2 for OnePlus 2 + Unofficial CM 13 by Grarak. Please fix this issue.


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#588 (comment)

@Pietia10

This comment has been minimized.

Copy link

Pietia10 commented Mar 24, 2016

No , in rom encryption works fine in twrp not so its not rom issue.
24.03.2016 22:30 "briancross" notifications@github.com napisał(a):

It's a ROM issue, not recovery and should be fixed in his latest build or
any build using his sources. I haven't had a chance to treat myself though.
On Mar 24, 2016 5:25 PM, "Ihor Sviziev" notifications@github.com wrote:

I have same issue as @briancross https://github.com/briancross on
3.0.0-2 for OnePlus 2 + Unofficial CM 13 by Grarak. Please fix this
issue.


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
<
#588 (comment)


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#588 (comment)

@briancross

This comment has been minimized.

Copy link

briancross commented Mar 24, 2016

No, it has to do with where the ROM stores the encryption key. Previously it was not storing it where TWRP was looking. If you've encrypted, you may need to wipe and reencrypt.

Read here: TeamWin/android_device_oneplus_oneplus2#1

@Pietia10

This comment has been minimized.

Copy link

Pietia10 commented Mar 25, 2016

Is this fix applied already into bacon (oneplus one) ? Cause I dont think
so .
24.03.2016 23:12 "briancross" notifications@github.com napisał(a):

No, it has to do with where the ROM stores the encryption key. Previously
it was not storing it where TWRP was looking. If you've encrypted, you may
need to wipe and reencrypt.

Read here: TeamWin/android_device_oneplus_oneplus2#1
TeamWin/android_device_oneplus_oneplus2#1


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#588 (comment)

@Pietia10

This comment has been minimized.

Copy link

Pietia10 commented Mar 26, 2016

I have found it ,
https://github.com/CyanogenMod/android_device_oneplus_bacon/blob/49317589d024e5da00a2f9be72bccfaad71fde79/bacon.mk

there is already
PRODUCT_PACKAGES +=
keystore.msm8974

and it still doesn't works.

@h-2

This comment has been minimized.

Copy link

h-2 commented Apr 16, 2016

Any news? Is this was always so complicated, I had had hoped it had gotten better 😢
Isn't it all platform independent now with Android M and TWRP3?

Anything I can do to help track this down? [OPO / CM13 / TWRP-3.0.2]

Thank you very much.

@radumas

This comment has been minimized.

Copy link

radumas commented May 3, 2016

Seems to be fixed in 3.0.2

@aredington

This comment has been minimized.

Copy link

aredington commented May 6, 2016

I'm still seeing this on a OnePlus One with COS 13.0-ZNH0EAS2JK, TWRP-3.0.2-0

@nickalleyne

This comment has been minimized.

Copy link

nickalleyne commented May 6, 2016

For everyone who has this issue, can you please check the following.

When you are using any apps that use "Accessibility options" in android, android sets the encryption key back to the default password. Examples of apps that can use this are LastPass or Tasker.

I have not yet confirmed, as I just wiped my phone and have kept all accessibility options off so far, but In this case, the password should be: default_password

See the following bug at google's side: https://code.google.com/p/android/issues/detail?id=79309

@Stokel

This comment has been minimized.

Copy link

Stokel commented May 7, 2016

Fresh CM13 nightly install and immediately encrypting without installing any apps still leads to this problem on Galaxy S4 (i9506). So I don't think that the accessibility options are the cause.

@zhimsel

This comment has been minimized.

Copy link

zhimsel commented May 10, 2016

For those on bacon: #596 (comment)

^ works for me.

@Frioo

This comment has been minimized.

Copy link

Frioo commented Feb 25, 2017

Can't decrypt data, 3x3 pattern lock.
Decryption fails even though I'm certain my PIN is correct.
No ROM installed (wiped, then updated TWRP from 3.0.2-1 to 3.0.3-1 because of another bug).
What should I do?

@Hello71

This comment has been minimized.

Copy link

Hello71 commented Mar 2, 2017

if you upgraded from old version of CM, try using old "hex grid" method from #323 via command line.

@lindhe

This comment has been minimized.

Copy link

lindhe commented Jun 4, 2017

I have no lock pattern, only pin. Decryption fails with correct pin. Do you think I am experience this same bug, even though I never set a lock pattern?

@player-03

This comment has been minimized.

Copy link

player-03 commented Jun 4, 2017

I don't think so. This bug is now fixed.

@DrDoctor13

This comment has been minimized.

Copy link

DrDoctor13 commented Mar 9, 2018

I'm experiencing this with a pattern on TWRP 3.2.1 with Sultan's Oneplus3 Nougat ROM.

@Snow344

This comment has been minimized.

Copy link

Snow344 commented Sep 5, 2018

Same in 3.2.3-0

@guoyunhe

This comment has been minimized.

Copy link

guoyunhe commented Sep 24, 2018

Nexus 5, unofficial LineageOS 15.1. Encrypted with PIN. Cannot decrypt.

@landry314

This comment has been minimized.

Copy link

landry314 commented Feb 10, 2019

The problem I have is my phone was stuck in boot loop and so i had to install a modified version of TWRP "TWRP3_1_1_5X.img" after a new boot partition but this version will not decrypt my drive because it wont take my password so I am still not able to get my files...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment