4.4 KitKat still has the same bug as previous releases as far as encrypting the phone goes. I had to attempt the process 4 times before the phone would actually encrypt. The first 3 times the Green Android popped up, but the phone didn't reboot to the "Encrypting Phone..." progress screen, it just went back to the lock screen. 4th time was a charm, so keep trying if it doesn't work for you.
Ronaldo Forenucci said:
4.4 KitKat still has the same bug as previous releases as far as encrypting the phone goes. I had to attempt the process 4 times before the phone would actually encrypt. The first 3 times the Green Android popped up, but the phone didn't reboot to the "Encrypting Phone..." progress screen, it just went back to the lock screen. 4th time was a charm, so keep trying if it doesn't work for you.
Click to expand...
Click to collapse
You using a custom recovery or stock?
Mine encrypted on the first try ...
Encrypting naturally makes the phone a tad bit slow though no? And to decrypt you have to do factory reset
Sent from my Nexus 5 using xda app-developers app
secondclaw said:
Mine encrypted on the first try ...
Click to expand...
Click to collapse
Stock recovery?
Sent from my Nexus 5 using Tapatalk
uh60james said:
Stock recovery?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, rooted only, but no other changes.
I've never had a problem encrypting with any recovery (CWM, TWRP, or stock), probably because it never boots to recovery while encrypting. It's probably a ROM issue.
Hey guys,
did you notice any significant performance impact after encrypting your N5?
How does an (stock) update work on encrypted N5? Do I have to wipe the phone prior to any update?
Just so you guys know there is a bug with kitkat encryption that will wipe your entire phone. Make backups of all the data you're keeping on your phone if you're going to encrypt. There's been a few users that have reported loosing everything due to encryption wiping out their phones. Just a friendly warning to whoever wants to encrypt.
Encryption does not slow down the performance. Only boots up slightly slower. Once you go through the password or pin, everything is decrypted until you lock your phone again.
I remember once you encrypt though...can't decrypt or need to reinstall stock.
Sent from my SM-T320 using xda app-developers app
my n5 was very picky about which cable and charger I was using before it would start the encryption process, with a N7 and a asus T100, it was hard to figure out which charger goes with which device.
Haven't noticed any particular slowdown since encrypting, except at boot.
The only thing I hated was not being able to use pattern unlock, using a PIN sucks. I worked around that by making a twrp backup right before the encryption process, change the security to PIN so encryption will work, then once it's done, boot into TWRP (which makes you enter the PIN to read inside the encrypted container), then restore the backup without wiping. So now I have a good length pin at bootup or entering twrp, pattern unlock for daily use. Maybe trading a little bit of security for convenience, but entering a 10+ character pin multiple times per day just isn't very usable.
I think it's the battery. The os shows another percentage than the recovery calculates. After some additional minutes of charging i hadn't that problem anymore. Thats just my opinion
I know that it is not possible to decrypt the data and that a factory reset is necessary to remove encryption.
I am just wondering if I can still update my system if I encrypt my phone?
What exactly is encrypted? Only /data?
Sent from my Nexus 5 using xda app-developers app
Encryption does not affect the OTA update or any kind of updates that push out offically. Phone itself decrypts once you go through personal lock screen. Since you can only update during unlocked stage, you won't have problem updating. It does encrypt everything except the media files such as videos, music's and etc. Correct me if I'm wrong though...
Sent from my SM-T320 using xda app-developers app
How long do you use the encryption now?
Do OTA updates still work?
Does adb work from TWRP recovery?
Sent from my Nexus 5 using XDA Free mobile app
FuMMoD said:
Just so you guys know there is a bug with kitkat encryption that will wipe your entire phone. Make backups of all the data you're keeping on your phone if you're going to encrypt. There's been a few users that have reported loosing everything due to encryption wiping out their phones. Just a friendly warning to whoever wants to encrypt.
Click to expand...
Click to collapse
Wish I had seen this!
[email protected] POS wiped EVERYTHING on my phone when I tried to encrypt.....EVERYTHING.
Was on latest TWRP, KangaKat and ElementalX
FAck U GOOGLE!
Globespy said:
Wish I had seen this!
[email protected] POS wiped EVERYTHING on my phone when I tried to encrypt.....EVERYTHING.
Was on latest TWRP, KangaKat and ElementalX
FAck U GOOGLE!
Click to expand...
Click to collapse
Ye when your phone running custom recovery, rom and kernel doesn't behave as intended, it's obviously Google's fault...
Seriously, if you change anything software related, you lose the right to blame the manufacturer.
I've heard of random passwords being generated so the user has to factory reset. Is this true????
# 47386
I am trying to update my Note 4 OTA and am running into an issue..
Both my phone and SD card are encrypted. My phone is stock. Previous updates I have done via Samsung Kies.
When I update it, it downloads the package and goes through the reboot sequence. When it starts the update process, it gets to about 2% and then says that the update failed and reboots and restores the previous settings. If I try to update via Kies, it goes through all of the screens and when I click the OK on the screen that says to not try to use the phone during the update, it just goes off into lala land and doesn't do anything at all..
Does anyone have any ideas as to what could be going on?
Thank you for your assistance.
Do you have reactivation lock enabled
BAD ASS NOTE 4
No. Reactivation lock is disabled. I verified it just in case, I have never used the feature.
ftanner said:
No. Reactivation lock is disabled. I verified it just in case, I have never used the feature.
Click to expand...
Click to collapse
I dunno man. By encrypted what do you mean. Knox or ????
BAD ASS NOTE 4
No. I mean I used the on-board encryption tool to encrypt the SD card and the internal phone storage. In the Security settings. I encrypted the device and the external SD card.
U might want ask a dev. U might get faster answer
BAD ASS NOTE 4
Have you tried to Odin the update?
ftanner said:
No. I mean I used the on-board encryption tool to encrypt the SD card and the internal phone storage. In the Security settings. I encrypted the device and the external SD card.
Click to expand...
Click to collapse
You will need to disable the encryption before going forward. The encryption is doing what it's supposed to do; preventing writing new code.
Sent from my SM-N910T using XDA Free mobile app
Will I be able to decrypt it without losing the data?
Disabling the encryption was the answer. I did not lose any data.
I would like to thank everyone for their assistance.
ftanner said:
I am trying to update my Note 4 OTA and am running into an issue..
Both my phone and SD card are encrypted. My phone is stock. Previous updates I have done via Samsung Kies.
When I update it, it downloads the package and goes through the reboot sequence. When it starts the update process, it gets to about 2% and then says that the update failed and reboots and restores the previous settings. If I try to update via Kies, it goes through all of the screens and when I click the OK on the screen that says to not try to use the phone during the update, it just goes off into lala land and doesn't do anything at all..
Does anyone have any ideas as to what could be going on?
Thank you for your assistance.
Click to expand...
Click to collapse
maybe try to desencryption i think the virtual machine dalvilk and art are not compatible in some functions
Hello everyone
I have now finally been able to root my beautiful Sony Xperia Z3 Compact. The bootloader is still locked. I did downgrade the Firmware in order to root the phone. Afterwards I made a backup of the DRM Keys via TA Backup. Additionally I updated the Firmware to 23.0.1.A.5.77. As the bootloader is still locked I did not install any kind of custom ROM and I am yet not planning to do so. The Sony ROM will probably do a good job. (My old phone is a Sony Xperia P which is now running with Root Sony's ROM since 3 years at least)
I am running on KitKat 4.4 and also not planning to change. I have a 64GB SD card in my phone as well.
Now my question:
Can I still use the encryption function or will this interfere or make problems because I have root (Bootloop)?
I am not planning to encrypt the SD card because I do not need encryption on the SD card but encryption for the Android System would be nice.
Thanks for your help guys :good:
Best wishes,
Dicey
No idea guys? Did no one ever try this before?
dicey said:
No idea guys? Did no one ever try this before?
Click to expand...
Click to collapse
I'd like to know this as well.
I tried this today. Left it encrypting and when I came back it said encryption had been interrupted and it then did a factory reset, after which I was unable to enter custom recovery.. As I had chosen to encrypt the SD I was left with an empty SD card too.
Somehow I kept root so I was able to install XZDualRecovery again and then restore from nandroid backup.
There's a thread on androidforums where Samsung owners have reported success with temporarily disabling SuperSU while running the encryption.
luuuis said:
There's a thread on androidforums where Samsung owners have reported success with temporarily disabling SuperSU while running the encryption.
Click to expand...
Click to collapse
Anyone tried this method or found another way to achieve root + encryption? It's the only thing keeping me from rooting again.
So this is almost the best phone in existence, except for one thing. It cannot be encrypted using the normal procedure. Choosing the encryption option simply restarts the phone. I have tried unrooting my phone then encrypting, I had the same issue. This same issue happened with MoFo'ed images before we had bootloader unlock. We got around it by loading an unrooted image, setting it up enough to encrypt the phone, then reloading the rooted image with MoFo root. Does anyone know if this could work again? Does anyone know if their is a way to "side encrypt" the phone by connecting it to a computer? I am currently running CM 12.1 with the newest update. Thanks for the help!
So, I've got a hard task that I cant seem to figure out.
My phone sometimes will say "Invalid Card" When I look at the lockscreen and wont let me use Data.
I've got the L90 Variant and have NOT done the 2nd Lolipop Update which would remove my root access.
My Question is, If I were to flash stock Lolipop and update, would I be able to root anymore?
And If i dont have to, How Do i fix this problem?
My Phone will sometimes even get a Toast Notification saying that android.phone has crashed and then it wont connect to T-Mobile and say Invalid Card too.
Any help?
I would factory reset first (backup your data preferably using custom recovery to get a full backup) to make sure it's not a hardware issue.
You can root with Kingroot, I've used it with 20b and 20c, then used a script to replace it with SuperSU. Or install a custom ROM layer.
Sent from my LG-D410hn using XDA Free mobile app