Ever since I have unlocked my bootloader I have 2 things that bug me.
1. Whenever I restart my phone it asks for my password/pin/pattern everytime before it will start. It's not a huge deal except when I restart my phone and forget I have to do that part it sits a while waiting for the password.
2. The little "warning" screen that tells me my bootloader is unlocked. Just like the way the old Nexus's were with no warning, just the little white unlocked pad lock on the google screen.
It will ask for your password on restart even if your bootloader is locked.
That's standard behavior, It will prompt you for manual password entry on every restart. If you don't want it, then disable secure startup. The bootloader unlock warning is common as well.
When you set your pattern or password it asks you if you want it enabled before android boots.. If you don't want that then set it to none, then reset it to pattern and answer no when it asks the question if you want pattern/pin required before the system boots
Sent from my Nexus 6P using Tapatalk
You can disable it in Settings -> Security -> Screen Lock, and click Password, select "No thanks". Same with PIN or pattern lock.
The weird thing is that I selected 'No thanks' to pin on boot, and it is still there in the settings. But, should I reboot the device and use fingerprint to unlock it requires a pin.
graffixnyc said:
When you set your pattern or password it asks you if you want it enabled before android boots.. If you don't want that then set it to none, then reset it to pattern and answer no when it asks the question if you want pattern/pin required before the system boots
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
That must only work with an encrypted device?
I don't get the prompt or the setting.
tech_head said:
That must only work with an encrypted device?
I don't get the prompt or the setting.
Click to expand...
Click to collapse
Same here, rooted with mod boot image
I've tried all of the above and don't get the prompt or setting. I'm also modded, but this is driving me crazy. Is there no way to turn this setting off?
This setting is set when you're initially setting up the phone for sure - you have to manually choose "no thanks" on the page right before where you actually start tapping on the fingerprint sensor to set it up. I'm not certain about the encrypted vs. unencrypted piece, although I wouldn't think that would make a difference...
I did it once, and then reflashed my entire system and upgraded twice since then. I didn't have the option after that first time.
kboya said:
The weird thing is that I selected 'No thanks' to pin on boot, and it is still there in the settings. But, should I reboot the device and use fingerprint to unlock it requires a pin.
Click to expand...
Click to collapse
The exact same thing happened to me so it must be a bug
Pilz said:
The exact same thing happened to me so it must be a bug
Click to expand...
Click to collapse
Yep. Same here. I've tried everything and it still always asks me for my password on startup.
Really annoying since random reboots are an issue too.
Basically, if my phone reboots at during my sleep (which it has done a few times already) I don't have my alarm in the morning.
Same problem here. I selected 'No thanks' (don't ask for a password on reboot), but it still asks for a password after I use my fingerprint every time I reboot the phone. Changing from password to pattern and back and turning "ask for password" on/off didn't help.
Myrrhman said:
Yep. Same here. I've tried everything and it still always asks me for my password on startup.
Really annoying since random reboots are an issue too.
Basically, if my phone reboots at during my sleep (which it has done a few times already) I don't have my alarm in the morning.
Click to expand...
Click to collapse
gnadenlos said:
Same problem here. I selected 'No thanks' (don't ask for a password on reboot), but it still asks for a password after I use my fingerprint every time I reboot the phone. Changing from password to pattern and back and turning "ask for password" on/off didn't help.
Click to expand...
Click to collapse
It will always do this.
Unlock using your backup screen lock method
Sometimes you might need to use your backup PIN, pattern, or password:
*When your fingerprint isn't recognized after a few tries
*After restarting your device
*After switching to a different user on the device
*After more than 48 hours have passed since you last unlocked using your backup method
Click to expand...
Click to collapse
From "How to use your fingerprint" on Nexus Imprint Help page: https://support.google.com/nexus/answer/6285273?hl=en
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
It will always do this.
Click to expand...
Click to collapse
In that case, the option and dialogs to turn that behavior off are useless.
gnadenlos said:
In that case, the option and dialogs to turn that behavior off are useless.
Click to expand...
Click to collapse
I'm almost positive the "Password on boot" option y'all see blocks access to recovery as well. When enabled, I think it locks access to the phone on the recovery level with a password. With it off, you can fully access recovery. Could y'all try and see if that's what happens?
I don't see the "password on boot" setting in Chroma's security settings, idk if being decrypted affects this.
SlimSnoopOS said:
I'm almost positive the "Password on boot" option y'all see blocks access to recovery as well. When enabled, I think it locks access to the phone on the recovery level with a password. With it off, you can fully access recovery. Could y'all try and see if that's what happens?
I don't see the "password on boot" setting in Chroma's security settings, idk if being decrypted affects this.
Click to expand...
Click to collapse
Sorry, i'm not entirely sure what you mean.
I have TWRP installed and i do know when first booting into TWRP, you must enter the password. After that, you can normally boot into TWRP.
BTW: I've gotten rid of the random reboots it seems. I simply flashed the official firmware from the Google Developers site a few days ago. I've not had a random reboot since. Really happy about that.
Myrrhman said:
Sorry, i'm not entirely sure what you mean.
I have TWRP installed and i do know when first booting into TWRP, you must enter the password. After that, you can normally boot into TWRP.
BTW: I've gotten rid of the random reboots it seems. I simply flashed the official firmware from the Google Developers site a few days ago. I've not had a random reboot since. Really happy about that.
Click to expand...
Click to collapse
Does TWRP always prompt you for a password regardless of whether you have "Password on boot" on/off?
Editv Glad you resolved your random reboots! That's always a good feeling.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Does TWRP always prompt you for a password regardless of whether you have "Password on boot" on/off?
Editv Glad you resolved your random reboots! That's always a good feeling.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I tried (had to install the latest TWRP anyways) and no.
If you choose Password off at boot, TWRP won't prompt you.
Related
If you have the security feature Secure startup enabled, which requires you to enter your password/pin/pattern before your phone boots up, sRGB mode will reset every time. After turning secure start-up off, sRGB mode will stick and you won't need to re-enable it after every reboot. You can disable/enable this feature by going into security and resetting your password
Thanks for the tip, seems to work :good:
Any idea why I can't disable the secure startup feature? I've tried turning password on/off repeatedly, and it never gives me that option again.
amirfk12 said:
Any idea why I can't disable the secure startup feature? I've tried turning password on/off repeatedly, and it never gives me that option again.
Click to expand...
Click to collapse
You need to change it to another security type. For example if you have a PIN change it to pattern and back or vice versa
tried that. didn't work. any other ideas?
I never set secure startup and mine reset every reboot. Since I reboot every day.
Sent from my Nexus 6P using XDA Free mobile app
I can't turn off the secure reset feature as well. I tried changing from pattern to pin to password and still no dice. I even factory reset to see if that would help and it didn't. Maybe a bug that will get fixed in a future update.
Sent from my Nexus 6P using Tapatalk
Can not remove the secure startup
uknowme4me said:
I can't turn off the secure reset feature as well. I tried changing from pattern to pin to password and still no dice. I even factory reset to see if that would help and it didn't. Maybe a bug that will get fixed in a future update.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Did you factory reset through recovery mode or through backup and reset setting?
I did it through both. I just got my 64gb frost 6P yesterday and it does the same exact thing. I'm thinking a software bug.
Sent from my Nexus 6P using Tapatalk
uknowme4me said:
I did it through both. I just got my 64gb frost 6P yesterday and it does the same exact thing. I'm thinking a software bug.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
yeah, was chatting with Google CS....wiped cache, didn't work and so they suggested factory reset. if it didn't work for you, i don't think i'm going to do it
My 6P requires patern before boot up and sRGB does not reset by itself.
Sent from my Nexus 6P using Tapatalk
That did the trick! Thank you!
For those of you still having issues, here are the steps: Settings > Security > Screen Lock (top option on this page) > confirm your password/pattern/etc. > choose a new one (can be the same as before) > THEN you choose the "Secure Start-up" yes or no. CHOOSE " No Thanks" ...Problem solved. Well, for me at least.
Absolutely 100% stock
Non rooted
Build number MDB08K
enhancedcollagen said:
If you have the security feature Secure startup enabled, which requires you to enter your password/pin/pattern before your phone boots up, sRGB mode will reset every time. After turning secure start-up off, sRGB mode will stick and you won't need to re-enable it after every reboot. You can disable/enable this feature by going into security and resetting your password
Click to expand...
Click to collapse
if you disable Secure startup doesn't that make device encryption useless?
I'm having this issue too with my Nexus 6p running Nougat. I'm unable to turn off secure startup. I've tried a factory reset through recovery and that didn't help. I wonder if it's some kind of issue with the OTA. I wish they would hurry up and make the factory image available so I could try flashing it to see if that somehow fixes it. The odd thing is that while running marshmallow I had secure startup in place, but sRGB stuck during a restart. I'm also wondering if decrypting would resolve the issue since that would basically disable secure startup, but I'm reluctant to do that because I'm getting tired of setting up my phone again and again. The other reason I'm reluctant is because my phone was decrypted until I pushed the nougat OTA. If I'm going to go to the trouble of decrypting my phone just to have another OTA encrypt it in the future, I'd rather not bother. Does anyone know whether flashing factory image (not necessarily an OTA) always encrypts the device? (Sorry for my wordiness)
chaddesch said:
I'm having this issue too with my Nexus 6p running Nougat. I'm unable to turn off secure startup. I've tried a factory reset through recovery and that didn't help. I wonder if it's some kind of issue with the OTA. I wish they would hurry up and make the factory image available so I could try flashing it to see if that somehow fixes it. The odd thing is that while running marshmallow I had secure startup in place, but sRGB stuck during a restart. I'm also wondering if decrypting would resolve the issue since that would basically disable secure startup, but I'm reluctant to do that because I'm getting tired of setting up my phone again and again. The other reason I'm reluctant is because my phone was decrypted until I pushed the nougat OTA. If I'm going to go to the trouble of decrypting my phone just to have another OTA encrypt it in the future, I'd rather not bother. Does anyone know whether flashing factory image (not necessarily an OTA) always encrypts the device? (Sorry for my wordiness)
Click to expand...
Click to collapse
Yes. Every OTA will force encryption due to the "forceencrypt" flag in the boot.img. Flashing SuperSU, modified boot.img, or custom kernel will turn that off and keep you decrypted, if you are decrypted.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Yes. Every OTA will force encryption due to the "forceencrypt" flag in the boot.img. Flashing SuperSU, modified boot.img, or custom kernel will turn that off and keep you decrypted, if you are decrypted.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick reply, SlimSnoopOS. Can I infer that as long as I'm not flashing an OTA and just the system image from the factory image (not the boot image) then it won't screw with the decryption?
chaddesch said:
Thanks for the quick reply, SlimSnoopOS. Can I infer that as long as I'm not flashing an OTA and just the system image from the factory image (not the boot image) then it won't screw with the decryption?
Click to expand...
Click to collapse
It won't but there's nothing wrong with ADB Sideload the OTA zip or manually flashing boot, system and vendor. Just make sure to go directly into TWRP (do not boot into the rom) and flash superuser/custom kernel before booting up to stay decrypted. I've manually installed each OTA and kept decrypted doing those steps.
Sent from my Nexus 5X using Tapatalk
Like, I don't know if I'm the only one experiencing this issue. Whenever I do something with the system, boot back up, first prompt telling me to enter my password to continue the boot, works. However, when I hit the system, enter the lock screen, it sometimes ask me for another password just in case. This second time I enter the password, wrong. I had made sure that my password was right, nope, still locked out. I had to use "No Lock for Home 2" Xposed module to somehow get pass this freaking lock screen. Am I the only one experiencing this issue or did I do something wrong?
I have tried almost everything,
1) Try to set a new password via Android Device Manager (LOCKED STILL)
2) Going to Security -> Password -> Typing the password all over (LOCKED STILL)
3) Going to Security -> Switching lock type to none -> Setting password again (LOCKED STILL)
4) Going to Security -> Switching to PIN (FINALLY WORKED)
What's bizarre is that under the Security settings my password apparently works, just not on the lock screen.
I would honestly prefer password over PIN and this is driving me insane. Is there a way to wipe the security settings in TWRP safely? Last time I tried deleting gatekeeper.password.key under /data/system in TWRP File Manager, it worked but FC whenever I try to set a new password.
Try clearing credentials under security
galaxy s4 nutjob said:
Try clearing credentials under security
Click to expand...
Click to collapse
Nope, still the same.
Hi.
Ever since i had to flash the stock rom B574, i have been unable to use the swipe to unlock option. I have the other 3 (pattern, pin, password) but not the swipe.
"Disabled by administrator, encryption policy or credential storage."
Now, before you start screaming about clearing the credentials in the security settings, i have done so 5-6 times by now.
I do not have any VPN installed. No Ad blocker either. And i have not encrypted my SD card (the option to encrypt is grayed out so i am unable anyway.)
I have tried several things. Set up a pattern with a pin as backup, then enter the pattern incorrect 5 to cause the system to remove the pattern.. Or something. It didn't work. Checked everything related to administrator and disabled it.
I've used SD Maid to clear any temp or cached files/settings.
The only thing i haven't done is a full factory reset. But i really wish not to.
And as i am unable to remove the pin, i'm not able to flash TWRP or root .
Frustrating.
Edit: System info:
Model:ALE-L21
Buildnr: ALE-L21C432B574
I got the same issue and I posted this problem week ago. Still not solved.
Freddyak said:
I got the same issue and I posted this problem week ago. Still not solved.
Click to expand...
Click to collapse
OK. Good to know it's not just me.
I'll keep an eye out on your post as well.
Probably the only solution is factory reset
BaronRafau said:
Probably the only solution is factory reset
Click to expand...
Click to collapse
Funny thing is that i tried to perform a factory reset, but the phone only switched off and refused to start up again.
Only way to get it working was to connect the cable to computer and phone before starting it in fastboot. Then restart.
But the workaround is fine by me. (set a pattern, choose backup pin, enter the pattern incorrectly 5 times. Wait 30 seconds, enter pin and the lockscreen is gone.
I believe this must be a bug in 574 onward. Or a ridiculous security "patch"
I have B584 and had this problem. Method with incorrectly pattern doesn't work for me, but factory reset works.
This issue is present almost on all versions I guess. Funny thing is, even some Honor users have problem with it. But trick with a pattern password is working though.
Wys?ane z mojego ALE-L21 przy u?yciu Tapatalka
I'm very confused by the behavior of my Nexus6p right now. I would like my phone to be fully encrypted, IE, you pick up the phone and can access absolutely none of my data without typing in a password. So I've clean flashed it several times, usually whenever a new update comes out. And each time I do this, the phone behaves how I want, when it boots, I get a password screen that says "enter a password to continue boot". It goes on this way for a day or so usually, and then suddenly this password screen stops showing up and I get the "you must enter a password after restarting" screen that clearly has already decrypted my data because I can see notifications and even play music through bluetooth without entering the password.
After each clean flash, I have been installing various mods. This time around, I have the things I've flashed down to TWRP 3.1.0, Magisk 12, and ElementalX 4.08. In the security settings, the phone still reads as encrypted, so I'm very confused. Is this normal behavior for this device, or is it one of the above things I have flashed? Either way, how do I fix this so that my data actually stays encrypted when the phone boots?
I have had similar issues to fix I formated everything and then installed the rom installed newest vendor image and then kept on eye on what I allowed special access to my phone
Keeper was wanting special access so I stopped using them and switched to last pass I have not lost decryption on phone boot
Also decided to pay for esexplorer pro to get ride of any possible infected ads
Your phone data is still encrypted, but your security settings are not optimized for what you want to accomplish. Make sure your Lockscreen has a password/PIN/Gesture set. There is the password on BOOT when encrypted, a password on Lockscreen when the screen is off, and In Settings>>Notifications>>Gear Icon>>"On the lock screen"- there are three settings. Default is set to "Show ALL notification content". Set it to NOT show notifications for now until you set which ones you want to show or hide. TWRP and EX are not causing your issue. Magisk might be but I don't use it. Uninstall just to be sure and/or check in the dedicated Magisk thread. This is on the stock 7.1.2 ROM. If you are running a custom ROM, YMMV.
So if I understand the issue correctly, you clean flash and you have the prompt to enter your credentials before booting finishes. Eventually you get set up and upon a reboot you notice that the prompt is gone?
Check your apps. You're using an app that requires an accessibility service (see Settings / Accessibility / Services). Granting an app accessibility service will do away with the boot entry of your pin/pattern/password. Set up your apps again and either don't use the app in question or just don't grant it the accessibility service for whatever feature requires it.
Known issue, btw. I forget why it happens, Google may turn up the results you're looking for.
Edit: Despite it not asking for that prompt on boot, your phone is still encrypted, by the way. This also has absolutely nothing to do with TWRP, EX, Magisk or how you choose to have your notifications hidden on lock screen.
2nd: Sadly, just revoking the service won't usually restore the prompt while booting. You'll need to clean flash again and not grant it in the first place.
That makes sense, I was looking in the wrong place. That's a really irritating design decision, there's no sense in having the encryption at all if you're just going to store the material necessary to decrypt the data in the clear.
For now, changing my password seems to have returned the encryption prompt while leaving the accessibility services working to the best of my observation.
It will probably go away again shortly​, most likely after the app uses the accessibility service. If it does, revoke the service and change your password again or clean flash. I don't believe there is a way to keep both 100% of the time.
*Fixed by suggestoins below.*
Hey,
So all of a sudden, I can't login to my phone after it boots (where you usually use fingerprint). I enter my pin but it says it's wrong, but I know it's right because it works for TWRP and during Android boot.
Anyway to fix without having to factory reset/format data?
Thanks
strifej said:
Hey,
So all of a sudden, I can't login to my phone after it boots (where you usually use fingerprint). I enter my pin but it says it's wrong, but I know it's right because it works for TWRP and during Android boot.
Anyway to fix without having to factory reset/format data?
Thanks
Click to expand...
Click to collapse
Yeah, that's a normal problem. I think there's a guide, but you simply have to go to TWRP's file manager and delete a couple of files (I don't remember the exact files, search on XDA for that). One of them is lockscreen-settings.db I think, so you can use that as a keyword
strifej said:
Hey,
So all of a sudden, I can't login to my phone after it boots (where you usually use fingerprint). I enter my pin but it says it's wrong, but I know it's right because it works for TWRP and during Android boot.
Anyway to fix without having to factory reset/format data?
Thanks
Click to expand...
Click to collapse
Yep, CaUname got it:
- Boot toTWRP Recovery
- Use the File Manager & navigate to:
- data > system > locksettings.db -- Delete that file
- reboot then re-setup your pin
Good luck