You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i used the app on my onplusone after upgrading to cm 12 / android 5.0.2 with twrp (rooted) yesterday, so i am still in "experimental mode" and have up to date backups (no panic).
after sucessfully changing the encryption password and rebooting, i get the following error: "decryption unsucessful - the password you entered is correct, but unfortunately your data is corrupt. to resume using your phone, you need to perform a factory reset..." and the only thing i can do is click "reset phone".
i suppose i cannot get more information about what went wrong so i will do the reset now and start over... and try again when the app is stable for cm12.
cheers :-)
The text was updated successfully, but these errors were encountered:
This appears to have been a bug in CM, which should now be fixed (I haven't tested it personally). Not that CM on the OnePlus One uses hardware disk encryption, which manages the decryption key separately from the password. Thus even if you enter the correct password and manage to decrypt the crypto footer, decryption may still fail if the HW-backed key is not passed properly. This appears to be what happened in your case.
i used the app on my onplusone after upgrading to cm 12 / android 5.0.2 with twrp (rooted) yesterday, so i am still in "experimental mode" and have up to date backups (no panic).
after sucessfully changing the encryption password and rebooting, i get the following error: "decryption unsucessful - the password you entered is correct, but unfortunately your data is corrupt. to resume using your phone, you need to perform a factory reset..." and the only thing i can do is click "reset phone".
i suppose i cannot get more information about what went wrong so i will do the reset now and start over... and try again when the app is stable for cm12.
cheers :-)
The text was updated successfully, but these errors were encountered: