[Completed] Encrypted Android device, but I'm not prompted for password on boot - XDA Assist

Issue:
Device is encrypted, but when I reboot my phone I am NOT prompted for a device password.
* It used to be that when I did a reboot or shutdown and restart, I would have to enter a password before the system fully started.
* But now the phone boots into the phone without putting in my password. I can reboot the phone and it will boot all the way to the Lock screen, and I can unlock the lock screen with my fingerprint or my backup password.
* I am concerned that somehow my device is either no longer encrypted or that there is some setting which has stored the boot password.
I have device encryption turned on:
Settings-->Personal and Security-->Other security settings: First item shows "Device encrypted"
Screen is locked with Fingerprints:
Settings-->Personal and Security-->
Screen lock type is Fingerprints
I'm on a Galaxy S6, AT&T branded phone, no root; this is a stock/vanilla phone.
Model - SAMSUNG-SM-G920A
Android Version - 5.0.2
Baseband G920AUCU2AOF4

subs said:
Issue:
Device is encrypted, but when I reboot my phone I am NOT prompted for a device password.
* It used to be that when I did a reboot or shutdown and restart, I would have to enter a password before the system fully started.
* But now the phone boots into the phone without putting in my password. I can reboot the phone and it will boot all the way to the Lock screen, and I can unlock the lock screen with my fingerprint or my backup password.
* I am concerned that somehow my device is either no longer encrypted or that there is some setting which has stored the boot password.
I have device encryption turned on:
Settings-->Personal and Security-->Other security settings: First item shows "Device encrypted"
Screen is locked with Fingerprints:
Settings-->Personal and Security-->
Screen lock type is Fingerprints
I'm on a Galaxy S6, AT&T branded phone, no root; this is a stock/vanilla phone.
Model - SAMSUNG-SM-G920A
Android Version - 5.0.2
Baseband G920AUCU2AOF4
Click to expand...
Click to collapse
Hi, thank you for using XDA assist.
There is a general forum for android here https://forum.xda-developers.com/android/help where you can get better help and support if you try to ask over there.
Good luck

Related

[Q] Encrypted phone - right password but fails to boot

Hi all,
I'm running CM11 on a Moto G. Due to work requirements I encrypted my phone via the security settings. It all went as expected, until I got to the screen where I have to enter my password to decrypt storage...
Once I enter the correct password, it loads a screen with an android on (I think it was similar to the one from the encryption screen) very briefly, then goes blank. I presume it turns off as it doesn't do anything else for quite a while. If I reboot and try enter an incorrect code, it prompts for the right code, so I'm definitely entering the correct pin.
My questions is - is there any way around this (without wiping the phone)? Any idea what's gone wrong?
I can still access recovery, but obviously it's rather limited as it's all encrypted. Is there any way I can connect via PC to get my files and decrypt them as I know the password?

[Q] Enabled Encryption - unable to boot

Unfortunately my OnePlus is no longer able to function and would like some assistance/suggestion from the community.
OnePlus has TWRP installed
- installed Paranoid Android rom = no issues
- enabled encryption
Now here is where the issue occurs.
When I start the phone I am able to see the PA bootup screen, it prompts me to enter the password. Once the password is entered "bugdroid" appears on the screen for a quick flash and then disappears. The screen continue to stay blank/black with no further progress, I have left the phone in this state for at least 20mins but it still doesn't proceed further. It should also be noted the the soft keys STAYS lit once the password has been entered for decryption.
I am still able to boot into recovery, enter my password to decrypt and use the standard TWRP functions. It should be noted that unfortunately I haven't done a backup on the phone at all {something that I totally regret right now), plus there is no rom left on the phone for me to attempt a install.
Any help is appreciated
note: the phone as able to complete its bootup process when I initially activated encryption but has failed ever since the first reboot
There are multiple threads discussing this in the very section you posted this thread in. Have a look, you'll find what you need.
Transmitted via Bacon

[Q] android device manager not sending password lock to phone

hi, i'm running the 5.0.0 version (i think) and i recently made a new pattern lock as a security measure. however i forgot the pattern. GG
after i got locked out, i installed android device manager from my pc to my phone. it says the install was successful, and i'm on the android device manager webpage to get a password lock sent to my phone, however the screen that displays the actual INPUTTING of the password doesn't appear ;(
i get the recovery message screen to display on my phone, but nowhere does it allow me to put in a password.
is my only option to factory reset it?
tldr; phone doesn't receive password lock - what can i do now

Encryption problem

I have had my phone encrypted for a while now. The other day I decided to install the Google Screenwise app since I take part in the panel. During the setup process it said I had to enter my pin because it "affected" encryption. Well I entered it and went about my business.
Now for the weird part. I needed to restart my phone later on and as it booted up, where it would ask me for my pin before it would boot Android, it now flashes a grey screen really fast and continues booting to the lockscreen where I can enter my pin. When I check under settings it says that my phone is still encrypted, and yet never ask me for my pin during boot up.
Anyone know what's going on here? Am I going to have to do a factory reset to get encryption working correctly again?
I am on Cyanogen OS 12.1 build YOG4PAS3JL.
BluGuy said:
I have had my phone encrypted for a while now. The other day I decided to install the Google Screenwise app since I take part in the panel. During the setup process it said I had to enter my pin because it "affected" encryption. Well I entered it and went about my business.
Now for the weird part. I needed to restart my phone later on and as it booted up, where it would ask me for my pin before it would boot Android, it now flashes a grey screen really fast and continues booting to the lockscreen where I can enter my pin. When I check under settings it says that my phone is still encrypted, and yet never ask me for my pin during boot up.
Anyone know what's going on here? Am I going to have to do a factory reset to get encryption working correctly again?
I am on Cyanogen OS 12.1 build YOG4PAS3JL.
Click to expand...
Click to collapse
You need to re-enable the pin from lockscreen options
Sent from my A0001 using Tapatalk
cloudx720 said:
You need to re-enable the pin from lockscreen options
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I think you misunderstood. The lockscreen still ask for a pin. When the phone has encryption turned on, when you either restart or turn the phone on you will receive a prompt on a grey screen to enter you pin. At this point Android hasn't fully booted yet. It then checks the pin and then boots Android. My phone is no longer brining me to this grey screen, it flashes grey but seems to just skip that screen. It is just fully loading android all the way.
BluGuy said:
I have had my phone encrypted for a while now. The other day I decided to install the Google Screenwise app since I take part in the panel. During the setup process it said I had to enter my pin because it "affected" encryption. Well I entered it and went about my business.
Now for the weird part. I needed to restart my phone later on and as it booted up, where it would ask me for my pin before it would boot Android, it now flashes a grey screen really fast and continues booting to the lockscreen where I can enter my pin. When I check under settings it says that my phone is still encrypted, and yet never ask me for my pin during boot up.
Anyone know what's going on here? Am I going to have to do a factory reset to get encryption working correctly again?
I am on Cyanogen OS 12.1 build YOG4PAS3JL.
Click to expand...
Click to collapse
If you set up pin code again will ask if you want pin to boot.
You have two option
One is pin to boot
Other pin after boot
I do not use screenwise for related issues
But i am familiar with encryption
Encryption will exist unless do factory reset
geowolf1000 said:
If you set up pin code again will ask if you want pin to boot.
You have two option
One is pin to boot
Other pin after boot
I do not use screenwise for related issues
But i am familiar with encryption
Encryption will exist unless do factory reset
Click to expand...
Click to collapse
I didn't even know it had the other option in it to ask for the pin during boot up. I would have thought if there was an option for that it would be in the Security menu with encryption rather than the lockscreen menu. Thanks.

Decryption fails at boot but works fine in recovery

Can't find a solution for this anywhere. I have an encrypted rooted moto g with unlocked bootloader and latest harp recovery. I installed an app that needed accessibility services which turned off unlock screen at bootup. I downloaded am closed app that was supposed to allow me to use accessibility services without turning off encryption at bootup but it didn't appear to do anything. I then went into security settings and re-entered unlock gesture and when asked if I wanted to be prompted for unlock at boot I said yes. Looked at accessibility settings and the permissions for the app were still turned on. I revolted the phone and now after moto logo boot screen, without asking me for a password, it goes straight to a screen saying that my password is correct but that decryption failed and to please factory reset phone. However I can boot into harp recovery and enter my unlock gesture and it works fine. So how can I turn off accessibility services for that app or otherwise fix this problem through recovery or adb? Please help.

Categories

Resources