S8 Plus G955FD 7.0 encryption does not take . i input password to to encrypt, i get the lock icon saying ecrypting but no dialog stating encryption percentage left. about 5 mins the phone reboots and once i input password the phone reboots again. i go into settings to check and encrytion option is still there. also tried different nougat versions same results.
Related
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?
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?
I just updated the software from kitkat to marshmallow via samsung kies sofrware. There are many problems iam facing.
1) The keyaboard pops up automatically on the lock screen menu and it doesn't go away neither it lets me enter the pin code. In the end i have to restart my phone.
2) the ultra power saving mode doesn't work. It looks like it is disabled permanently.
3)Many apps like facebook,twitter and Instagram they stuck while working and then they automatically restart. I never faced these issues on kitkat.
4) Battery issue. Battery drops to 80% after a complete charge
Factory Reset it
Hi, I have a dual SIM S5 which I updated from Lollipop to Marshmallow using the normal phone update feature. I haven't done anything clever like rooting etc. Today I've been exploring 'Find-my-phone' on Samsung's website and am unable to set the Reactivation Lock on the phone. I check the box and get the warning message to remember the password and press OK and then the warning message disappears and I'm left with the Reactivation Lock box unchecked. If I check it I get the warning box again. I didn't try setting the Lock with Lollipop. Any ideas as to how to get it to work. Tried rebooting. Didn't do a factory reset after updating to MM, could this be the problem?
Solved
Found that reactivation lock was selectable immediately after doing a 'Wipe the cache partition' by holding vol up, power and home buttons on phone reboot and selecting this option from the menu.
My S5 did an operating system software update yesterday and same reactivation problem as before so I wiped the cache partition and problem remained so maybe wiping the cache partition does nothing and the solution lies elsewhere. If anybody else has any ideas please chime in.
Reactivation lock is useless anyway, easy to bypass
Finally got round to asking but I've noticed after updating to 7.0 that I no longer need to enter my encryption pass phrase to get the phone to startup.
It does require the pin to unlock the home screen but not to start up.
Is this a change in 7.0 doesn't seem like it would be as secure as requiring a pin to boot?