CM 12.1 With Encryption = Must Format, Can't Unlock/decrypt - Nexus 4 Q&A, Help & Troubleshooting

I was running CM 12.0 for a long time with encryption and no major issues, until recently I upgraded to 12.1, without formatting etc. Then I had this issue.. after the full boot, the phone reboots in a boot-loop at the pattern unlock screen. If I turned it off fully and restart, I would get to the SIM unlock screen, with the unlock dots showing below that, and after inputting the PIN it dissapears to a blank screen, where you can just pull the Dialer out, but with phone still not decrypted.
So I went into TWRP, pulled my data, fully formatted and started clean, installed 12.1 from scratch and used it for some days without any problems... until I turned encryption on, and after ~12 or so minutes (with the Android logo and some text saying it's encrypting etc).. I have exactly the same issue.
What's going on? Can I fix this without having to format all again?

Update: if I remove the SIM card it works, so maybe the issue is not directly related to the encryption.

Update2: the following steps seemed to resolve it, for now.. not sure what will happen on next reboot:
Remove SIM card
Access phone normally
Go to settings, Security, pattern unlock
Remove the lock. Then turn it on again (you'll need to draw the pattern once more)
Turn off.
Insert SIM back
~Working with some minor issues.

Related

[Q] Anyone else have Mango lock up on restart

I loaded Yuki's ROM and updated to Mango via Zune. Had it running for about a week before I discovered that when I turn off the phone and then turn back on, it gets stuck at the point where it should be loading the home screen. I get the time at the top and that's it; the phone is completely unresponsive. The only fix I found was to do a hard reset and start over. I thought maybe an application caused this so after the reset, I turned off the phone before loading any other applications. It got stuck again at the same place. I suppose this could be linked to the sd card and I'll try a different one. Just wanted to see if anyone else has experienced this problem.
--Edit--
I've linked my issue to the sd unlock cab. As long as I don't install, mango restarts with no problems.
I've had this a few times.
Usually get the lockup at the SIM password screen.
Just reboot again and it will come back. Sometimes a couple of boots are needed.
I have a supported Sandisk card BTW.
Thanks. I've given it 2 tries before the reset but not more. I'll try to be more patient with it this time...or just avoid turning it off
I had the same problem as well, reflashed it with the same problem. after doing about 3 hard resets it finally worked.
I'm getting this continually, every time i reset i end up having to hard reset...

Rooted with CF-Autoroot, now encryption not possible anymore

I just rooted a brand new Galaxy S4 on i9505xxuemke
Before I encrypted and decrypted several times. Always worked great. Now after root when it should encrypt display shows shortly the green android and then it goes black. Device does not react anymore. After about 1 minute it vibrates and reboots. However I don't have to enter my password to boot. Only to unlock. Now I can go to options and try encrpyting again. Hower same behaviour as before. Any suggestions?
There are no apps installed, no google account and so on. Its factory fresh. I even restored factory settings. Same behaviour.
Any ideas?

[Q] Unable to boot after encryption

Hi everyone,
I enabled the encryption on my unrooted unlocked G2. Once the encryption was done, it rebooted and asked for the pin to boot. In entered the pin but the phone keeps rebooting and asking for the pin again and again.
I have tried more than 20 times, sometimes it boots to android but it shows a warning sign in notification (backup account needed) and then reboots after a few seconds. I tried turning on/off but the same thing happens again.
Is there anyway I can get my data out of this mess before doing a factory reset? Maybe rooting it from download mode and mounting from recovery?
Thanks a lot!

T365 device encryption doesn work

Hi!
I have a problem. The device encryption (Settings - Security - Encrypt device) does not work for me.
I'm on stock T365XXU1AOA3 (SER) firmare (no root or other mods, pure stock).
After tapping 'encrypt device' and entering password and plugging in a charger, 'black screen with green android' appears for some time (~5 min or so) and then it reboots.
After rebooting it becomes obvious, that device is still not encrypted yet.
What is the problem?
andreya108 said:
Hi!
I have a problem. The device encryption (Settings - Security - Encrypt device) does not work for me.
I'm on stock T365XXU1AOA3 (SER) firmare (no root or other mods, pure stock).
After tapping 'encrypt device' and entering password and plugging in a charger, 'black screen with green android' appears for some time (~5 min or so) and then it reboots.
After rebooting it becomes obvious, that device is still not encrypted yet.
What is the problem?
Click to expand...
Click to collapse
i dont know, never tried that encryption, did you try on a fresh installation? else you can do a factory reset before.
pls tell me if it works so we can test twrp encryption.
I do not understand something, but after reflashing everything it become working.
So I was able to encrypt device and decrypt on stock kernel/rom.
But if I change kernel to custom, which I complied by myself, decryption stops working.
There are messages in logcat from SecureStorageDaemon that it stopped working because kernel is changed.
How can we test twrp encryption?

S4 Phone freezes/lags when unlocking

Hello,
I noticed within the last month that my S4 seems to lag when I go to unlock the phone.
I hit the power/home button and the screen doesn't turn on. If flashes on 10 seconds later then goes black again.
After a minute, the phone finally releases itself and then I can use it again, before...
It freezes when texting, instagraming, etc...
I have:
-Taken out the SD card
-Wiped Cache Partition
-Factory reset
The only time it doesn't freeze up is when it's in safe mode.
So I have 2 possible answers: Corrupted system file or corrupted app.
Anyone know how to go about isolating the problem? Or solutions similar to this in the past?
I would completely wipe the phone and reflash the software.

Categories

Resources