• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help VZW: Can't encrypt phone after 4.2.2 update

cconover

Well-Known Member
I got the 4.2.2 update for my VZW Galaxy Nexus this morning, and decided after it was installed to reset to factory for good measure. After doing so, I tried to turn on phone encryption (which I'd had on before without issue), and every time I go through the steps to start the encryption process, the phone reboots as expected, but never actually does the encryption process - it just boots up normally.

Any suggestions on what I should do to?
 
Hi

I have a Nexus4 on 4.2.2 and just had the exact same issue, phone rebooted and then just loaded up without encryption.
I gave it a 2nd attempt and went through the start encryption process through Security in the settings, this time it rebooted, sat at the nexus logo for a lot longer (around 1-2 minutes) and then moved into the encryption screen.

Not sure why it failed the first time, but the second time I tried it looked to have worked. (busy encrypting right now)
 
I rebooted it and tried and still no luck, but I've rebooted a few times since then. I'll give it another shot.
 
I figured out the problem. I was using a charger other than the one that came with my phone. The phone must not have seen the right power output coming from the charger, so it rejected the encryption process. As soon as I plugged my phone into its OEM charger, the encryption ran without a hitch.
 
I've always been hesitant to try the encryption, any advice is appreciated. I'd love to have everything on my phone secure should I lose it or someone gets ahold of it and plugs it into a computer to browse it (the only way I think it's very vulnerable).

Any thoughts? Does it run and seem really normal upon bootup and stuff once its encrypted?
 
I've seen no noticeable performance decreases using encryption. I haven't run any benchmarks to get hard data, but my anecdotal evidence is that the impact is minimal. What slight performance hits there may be are outweighed by the peace of my mind having my phone secured even from offline attacks.
 
I just found this thread. I couldn't encrypt my Moto X (4.4.4). Having tapped the encrypt button, the phone would display a green android logo and then just restart, without encrypting anything. The fix for me was to disable Adaway. Coincidence? Maybe.
 
Back
Top Bottom