Database Users

Password on Bootup

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.

Cannot encrypt Nexus 6P with Marshmallow 6.0.1 after TWRP root and Xposed

I recently bought a Nexus 6P and I just rooted it a few days ago. I have been reading about how it is less safe now that the bootloader is unlocked, so I figured I could encrypt my phone for more securities! I don't want ro re-lock since unlocking will wipe my data all over again.
So I went into Settings->Encrypt phone and started the encryption process. It first showed a green outline of an Android, then it started the boot animation. It stayed there for about half an hour and it was clearly not encrypting (not getting hot or anything) so I just rebooted (I have a backup, that's why I'm so bold ) and it just normally rebooted to a working phone with nothing encrypted. Tried it again, same result.
I'm running Marshmallow 6.0.1 MMB29M with TWRP, SuperSU (I'm pretty sure it's systemless) and Xposed. I'm not sure what kernel I flashed when I rooted (that is the boot.img, right?).
Is this a bug? Is it a feature? I would like to be able to encrypt my phone; does anyone have any ideas on how to achieve this, now that TWRP can decrypt stuff?
Thanks!

I have the same issue with a HTC One M8 running Marshmallow 6.0 and systemless root. I've had this phone encrypted in the past but that was with standard root. Seems like systemless root and something to do with the modification of the boot image has something to do with encryption breaking.
Glad I made a nandroid before starting also, just incase.

I got it to work
So I just flashed the latest 6.0.1 (MMB29P) system, boot, etc. partitions because of the January security update. I folllowed Heisenberg's guide, point 10. I then had to reflash TWRP and then install SuperSU and Xposed again, because they were gone.
What this did was re-encrypt the phone, but with the default password. This basically offers no protection, with the added benefit of processor overhead. Yay I noticed this because it said the phone is encrypted, in Settings->Security even though it did not ask for a password at boot-time or in TWRP.
What you need to do is to remove any security you set up (just set the lockscreen unlock to "None") and then re-add it. When the phone asks if you want it to require the password at startup, say yes. It will then change the encryption password to your custom one and voila, your phone is now encrypted and uses your password/pin/pattern/whatev.

tudy77 said:
What this did was re-encrypt the phone, but with the default password. This basically offers no protection, with the added benefit of processor overhead. Yay I noticed this because it said the phone is encrypted, in Settings->Security even though it did not ask for a password at boot-time or in TWRP.
Click to expand...
Click to collapse
Question, is the default password: "default_password" lowercase and all? Im on the same boat you were, about to do this just to get encryption back but i want to be 100% sure of the steps lol

Well that's what I read here, but I never actually typed it anywhere because, from what I understand, it gets completed automatically by TWRP or Android of it is the default one.
Sent from my Nexus 6P using Tapatalk

tudy77 said:
Well that's what I read here, but I never actually typed it anywhere because, from what I understand, it gets completed automatically by TWRP or Android of it is the default one.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
so i dont type anything just hit enter?

I was not prompted to type anything
Sent from my Nexus 6P using Tapatalk

(XT1575) Moto X Style February Security Update Problem

Hi all
First I'd like to apologise if this thread already exists but so far I cannot find anything (please link me it if it does)(this is my first post as well)
I bought the phone a couple of weeks back. The phone had Android 6.0 marshmallow on it out of the box. The phone has been working perfectly up until today. This Morning i got a notification to say there was a new security update available. I downloaded the update (6mb) and installed it. I went off to work and when i took the phone out of my pocket it was rebooting. I waited for it to boot and after about 20 seconds of using the phone it became unresponsive, i.e. the screen froze, and a couple of seconds later the phone restarted. The phone rebooted constantly throughout the day when I tried to use it. When I got home I searched online for help but didn't find anything, although a factory reset can solve a lot of problems and so that's what I did. I setup the phone as a new phone but after about mins it froze and rebooted again. I have just turned the phone off and I am using a spare atm. I am considering a re flash of the software, however if any of you have had the same problem and have had an easy fix, please let me know. Any help is appreciated
Regards
TechGuy

It is odd that even after a factory reset it did this. Maybe try another factory reset and put your Google account on the phone but not any of the apps from Google restore. This will tell you if an app that you have installed is clashing with the new security patch or if the phones software is the culprit.
Sent from my XT1575 using Tapatalk

TechGuy82 said:
Hi all
First I'd like to apologise if this thread already exists but so far I cannot find anything (please link me it if it does)(this is my first post as well)
I bought the phone a couple of weeks back. The phone had Android 6.0 marshmallow on it out of the box. The phone has been working perfectly up until today. This Morning i got a notification to say there was a new security update available. I downloaded the update (6mb) and installed it. I went off to work and when i took the phone out of my pocket it was rebooting. I waited for it to boot and after about 20 seconds of using the phone it became unresponsive, i.e. the screen froze, and a couple of seconds later the phone restarted. The phone rebooted constantly throughout the day when I tried to use it. When I got home I searched online for help but didn't find anything, although a factory reset can solve a lot of problems and so that's what I did. I setup the phone as a new phone but after about mins it froze and rebooted again. I have just turned the phone off and I am using a spare atm. I am considering a re flash of the software, however if any of you have had the same problem and have had an easy fix, please let me know. Any help is appreciated
Regards
TechGuy
Click to expand...
Click to collapse
@TechGuy82 ... Go to the "General" thread (if you haven't already) the whole matter of installing the update is being thrashed out there.

Yeah check out the thread in general... Also just wanted to confirm that I'm having the exact same problem you are and have tried factory reset with the same results. I'm currently attempting a complete software flash with the CLARK_RETUS_6.0_MPH24.49-18_cid9_subsidy-DEFAULT_CFC.xml.zip using the flash all bat

ahent said:
It is odd that even after a factory reset it did this. Maybe try another factory reset and put your Google account on the phone but not any of the apps from Google restore. This will tell you if an app that you have installed is clashing with the new security patch or if the phones software is the culprit.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
After the factory reset, the phone is rebooting before i can even set it up.

Same issue. I even rerooted and flashed a different rom and it will do it. going to try flashing back to stock before the update and see what happens.

I have the notice for this update - I am not rooted nor have I installed TWRP (I'd like to, eventually)
What I do need to know:
I don't use the phone like most do - services except for buying apps are not necessary. I have downloaded and paid for large data base nature and astronomy apps which a dumb phone won't run. I like speed on the phone so a program opens faster.
Given that - I have disabled 95% of the social type apps on the phone. I've disabled all the extras from Motorola. I don't use, want or need them. What will happen if I apply this update? I
1. Will it refuse to run if something is disabled?
2. Will it override disable and open whatever it thinks it needs?
3. Will it just install where it needs to?
4. Will it bugger the phone?
I just read through what's in Google services and I don't seem to need that. The only thing would be verification of a bought app from Play Store. I disabled Maps, Location, Hangouts, Photos -- There's better paid apps in Play Store and that's why I need to be sure that Play Services doesn't do the checks to see if you bought the app.
I like the feel of this phone, the performance and I love the camera. I just want to use it my way. If I could carry all my reference books with me, I'd use a feature phone. I like to take nature walks and birdwatch.

Guys can anyone help, after full restore on 6.0 I can't normally reboot or turn on my phone .the trouble is when am turn on my phone it loads bootloader instead boots up, and in bootloader when I click "start" it booting up. Reboot do the same thing .
Sent from my XT1575 using Tapatalk

towfurious said:
Guys can anyone help, after full restore on 6.0 I can't normally reboot or turn on my phone .the trouble is when am turn on my phone it loads bootloader instead boots up, and in bootloader when I click "start" it booting up. Reboot do the same thing .
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Clear data and cache in recovery?
(Warning, do you have a backup?)
Enviado desde mi XT1575 mediante Tapatalk

Altomugriento said:
Clear data and cache in recovery?
(Warning, do you have a backup?)
Enviado desde mi XT1575 mediante Tapatalk
Click to expand...
Click to collapse
It happens when I'm flash stock moto x ROM from moto gdrive on stock recovery , and on twrp too, and yes before flashing I had clear all cache and and data in recovery .
Sent from my XT1575 using Tapatalk

towfurious said:
It happens when I'm flash stock moto x ROM from moto gdrive on stock recovery , and on twrp too, and yes before flashing I had clear all cache and and data in recovery .
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I have got answer for my own question.
It happens when before flashing in terminal type "fastboot oem fb_mode_set" , thats kind like bootloader force mode , when you reboot it always boots to fastboot. So after flashing i forgot to type "fastboot oem fb_mode_clear" to exit force mode.
Sorry for too many "reboot" words)

The only way I was able to resolve it was to do a full restore using this factory image. Leave it in fastboot and reflash. I tested before had wiping my sd card, removing my sd, wiping the internal, cache. Figured at that point easier just use a full stock image and see what happens.
Here is the Image : https://docs.google.com/uc?id=0B5AiGacWcBRzMTBlWmppOC1DS3c&export=download

oracleminder said:
The only way I was able to resolve it was to do a full restore using this factory image. Leave it in fastboot and reflash. I tested before had wiping my sd card, removing my sd, wiping the internal, cache. Figured at that point easier just use a full stock image and see what happens.
Here is the Image : https://docs.google.com/uc?id=0B5AiGacWcBRzMTBlWmppOC1DS3c&export=download
Click to expand...
Click to collapse
I will try it, i hate lenovorola right now
Enviado desde mi SM-T320 mediante Tapatalk

towfurious said:
I have got answer for my own question.
It happens when before flashing in terminal type "fastboot oem fb_mode_set" , thats kind like bootloader force mode , when you reboot it always boots to fastboot. So after flashing i forgot to type "fastboot oem fb_mode_clear" to exit force mode.
Sorry for too many "reboot" words)
Click to expand...
Click to collapse
Thank you for this been struggling for hours

Warning: TWRP Restore on 7.0 may not work as intended..

EDIT 10/30/2016:
From some of the replies on this thread, I have reached the conclusion that this is not a widespread problem (duh.)
However, if you are locked out of your Nexus after a restore, I have found that the best solution was given by @toknitup420
Best Solution:
In TWRP (or ADB whatever you prefer) go into Advanced --> File Manager and navigate to /data/system/.
Locate locksettings.db and rename/delete it.
Reboot, unlock device, go to Settings --> Security and set a new screen lock passcode. The best part about this solution is that your previously registered fingerprints still work (mine did.)
Some suggested updating TWRP to the latest unofficial 3.0.2-3.
Flashing this version and restoring using it did not fix the issue for me personally, but if you would like to try then here is the link I found searching XDA.
**************************************************
OP:
Disclaimer: I am an XDA n00b, I've frequented these forums for a long while now, but I have never made an account and actually posted until now.
Also, I am using build NRD90U on my Nexus 6p
Not sure if anyone else has had these issues, but last night I had problems restoring from a nandroid backup on TWRP.
First issue:
TWRP would not restore System + Vendor + Data all in one operation. During the Data portion of the restore, it threw an error and cancelled the operation (for the life of me I wish I wrote it down, it was 3am and I just wanted to sleep.)
The Fix: I had to first restore System + Vendor, then reboot back into TWRP. Upon rebooting, TWRP prompts to allow modification of system. I accepted (by swiping) and proceeded to restore ONLY the Data from the nandroid backup.
Second issue:
Upon booting into my fully restored phone, I got locked out of the lockscreen. My pattern would not work, and no matter how many times I tried, I could not get to the "Forgot Pattern?" prompt so that I could change my password. Great.
The Fix: No option but to factory restore. I just booted into fastboot, followed Heisenberg's Flash Guide for the Nexus 6p Step 9 to flash everything except for my Internal Storage partition. Booted into a fresh version of android Nougat, and restored from a Titanium Backup.
I haven't seen any information or talk of turning off the passcode before backing up android in TWRP, but I suspect you should do this to avoid a fully restored system that you are locked out of . (Note: I am not talking about the passcode to boot feature, that was turned off for me in this case, and you should too because this is well known to cause issues when restoring. I am referring to the passcode at the actual lockscreen)
TLDR; Restore Data partition after restoring System + Vendor and reboot back into recovery, and turn off all passcode features before creating a nandroid backup.

This is a known topic, nothing new lol.

tatico28 said:
This is a known topic, nothing new lol.
Click to expand...
Click to collapse
Thanks for acknowledging the disclaimer, just trying to help folks on Google. I didn't find out about it until it was too late.

aeg3d said:
Disclaimer: I am an XDA n00b, I've frequented these forums for a long while now, but I have never made an account and actually posted until now.
Also, I am using build NRD90U on my Nexus 6p
Not sure if anyone else has had these issues, but last night I had problems restoring from a nandroid backup on TWRP.
First issue:
TWRP would not restore System + Vendor + Data all in one operation. During the Data portion of the restore, it threw an error and cancelled the operation (for the life of me I wish I wrote it down, it was 3am and I just wanted to sleep.)
The Fix: I had to first restore System + Vendor, then reboot back into TWRP. Upon rebooting, TWRP prompts to allow modification of system. I accepted (by swiping) and proceeded to restore ONLY the Data from the nandroid backup.
Second issue:
Upon booting into my fully restored phone, I got locked out of the lockscreen. My pattern would not work, and no matter how many times I tried, I could not get to the "Forgot Pattern?" prompt so that I could change my password. Great.
The Fix: No option but to factory restore. I just booted into fastboot, followed Heisenberg's Flash Guide for the Nexus 6p Step 9 to flash everything except for my Internal Storage partition. Booted into a fresh version of android Nougat, and restored from a Titanium Backup.
I haven't seen any information or talk of turning off the passcode before backing up android in TWRP, but I suspect you should do this to avoid a fully restored system that you are locked out of . (Note: I am not talking about the passcode to boot feature, that was turned off for me in this case, and you should too because this is well known to cause issues when restoring. I am referring to the passcode at the actual lockscreen)
TLDR; Restore Data partition after restoring System + Vendor and reboot back into recovery, and turn off all passcode features before creating a nandroid backup.
Click to expand...
Click to collapse
"Warning: before you make a backup with TWRP you must remove all lockscreen security. If you do not do this you will not be able to unlock your device after restoring your backup (entering your pin will result in an "incorrect pin" message), you'll be forced to perform a factory reset to boot into Android. To remove lockscreen security go to Settings>Security>Screen Lock and set it to swipe/none."
I have two pins. One to unlock sim and one to unlock phone. I'm not sure which one you're referring to because I didn't turn off my pin to unlock sim card and I didn't get locked out after restore.
What did stump me was getting a half working phone since the restore included vendor.img which no one said to uncheck before restoring.

tropical cactus said:
I have two pins. One to unlock sim and one to unlock phone. I'm not sure which one you're referring to because I didn't turn off my pin to unlock sim card and I didn't get locked out after restore.
Click to expand...
Click to collapse
Ah, that is a feature that I do not use and didn't consider. What I was referring to was turning off the lock screen passcode (boot passcode should also be off, this is a known issue)
tropical cactus said:
What did stump me was getting a half working phone since the restore included vendor.img which no one said to uncheck before restoring.
Click to expand...
Click to collapse
Ah yes it is very unclear exactly what to have checked/unchecked for TWRP. I've always been under the impression a System + Vendor + Data backup is sufficient, maybe also check the EFS for extra security (you should back up EFS at least once and keep in a safe place, your phone depends on this to connect to cell towers. If it's corrupted and you have no backup, you're in trouble)

I use TWRP 3.0.2.3 and nandroids restored fine on 7.0 and 7.1 DP with lock screen pin enabled
Sent from my Nexus 6P using Tapatalk

scoot0073 said:
I use TWRP 3.0.2.3 and nandroids restored fine on 7.0 and 7.1 DP with lock screen pin enabled
Click to expand...
Click to collapse
Perhaps it's because I was using TWRP 3.0.2-2.. I'll have to try again later tonight to see if that's the case.
Good to know though, maybe what I experienced is an isolated issue.

3.0.2.2 I believe if I remember I had to disable security lock screen pin b4 I made a nandroid.
But the unofficial 3.0.2.3 not the case
Sent from my Nexus 6P using Tapatalk

aeg3d said:
Disclaimer: I am an XDA n00b, I've frequented these forums for a long while now, but I have never made an account and actually posted until now.
Also, I am using build NRD90U on my Nexus 6p
Not sure if anyone else has had these issues, but last night I had problems restoring from a nandroid backup on TWRP.
First issue:
TWRP would not restore System + Vendor + Data all in one operation. During the Data portion of the restore, it threw an error and cancelled the operation (for the life of me I wish I wrote it down, it was 3am and I just wanted to sleep.)
The Fix: I had to first restore System + Vendor, then reboot back into TWRP. Upon rebooting, TWRP prompts to allow modification of system. I accepted (by swiping) and proceeded to restore ONLY the Data from the nandroid backup.
Second issue:
Upon booting into my fully restored phone, I got locked out of the lockscreen. My pattern would not work, and no matter how many times I tried, I could not get to the "Forgot Pattern?" prompt so that I could change my password. Great.
The Fix: No option but to factory restore. I just booted into fastboot, followed Heisenberg's Flash Guide for the Nexus 6p Step 9 to flash everything except for my Internal Storage partition. Booted into a fresh version of android Nougat, and restored from a Titanium Backup.
I haven't seen any information or talk of turning off the passcode before backing up android in TWRP, but I suspect you should do this to avoid a fully restored system that you are locked out of . (Note: I am not talking about the passcode to boot feature, that was turned off for me in this case, and you should too because this is well known to cause issues when restoring. I am referring to the passcode at the actual lockscreen)
TLDR; Restore Data partition after restoring System + Vendor and reboot back into recovery, and turn off all passcode features before creating a nandroid backup.
Click to expand...
Click to collapse
All you needed to do was delete locksettings.db in twrp before rebooting. That deletes lock screen security pin. Then you can just reboot and add pin back in settings. Easy.

toknitup420 said:
All you needed to do was delete locksettings.db in twrp before rebooting. That deletes lock screen security pin. Then you can just reboot and add pin back in settings. Easy.
Click to expand...
Click to collapse
I thought I read somewhere on XDA that this could potentially break the feature (a.k.a. wouldn't be able to reset a new passcode after getting access to homescreen.)

aeg3d said:
I thought I read somewhere on XDA that this could potentially break the feature (a.k.a. wouldn't be able to reset a new passcode after getting access to homescreen.)
Click to expand...
Click to collapse
I've been doing it like that for months now with no issues.

toknitup420 said:
I've been doing it like that for months now with no issues.
Click to expand...
Click to collapse
OK I'll have to try that as well, others seem to say it was an error that was patched in the latest TWRP (I was apparently using a slightly older version). Thanks for the tip!

scoot0073 said:
3.0.2.2 I believe if I remember I had to disable security lock screen pin b4 I made a nandroid.
But the unofficial 3.0.2.3 not the case
Click to expand...
Click to collapse
OK that seems to be the consensus, that I was using a slightly older version of TWRP with this bug. Going to flash tonight to confirm!

Factory reset - locked bootloader - safetynet fails

Some history with the phone. I've gone back and forth a few times with this phone. At one point the bootloader was unlocked, I was rooted, etc etc. This was quite a while ago. Since then I have flashed the factory rom, locked the bootloader and ran 100% pure stock until this morning and everything worked just fine. Android Pay worked, etc. Today I decided I'd do a factory reset and not bother restoring data. Prior to doing that, I decided to give Magisk a quick try just for the heck of it. I flashed the current Oreo factory image (With Sept security patches) left the bootloader unlocked, flashed TWRP, installed Magisk via TWRP. Didn't really give it much of a chance but either way, after a quick check safetynet failed. So I figured, whatever no big deal. I flashed the factory image again, then relocked the bootloader, and eventually rebooted and signed back into my account and didn't bother restoring any backup. Let all the stock apps install/update, checked Android Pay.....and it wouldn't allow me to add a card. I checked the Safetynet tests and it fails the CTS Profile match. I'm pretty much at a loss now as to what in the world the problem is. The phone is fresh off of a factory reset and the bootloader is locked. No magisk, no root, nothing.
Another REALLY strange thing is, during boot up, I have to unlock the phone, then it continues booting up and eventually finishes the boot up process, although I think I recall reading about this being some new security thing. Either way, don't think it relates to my issue.

Well I unlocked the bootloader again, flash the August 7.1.2, relocked the bootloader, and after updating apps and Google Play Services, all is well again. Guess I'll just grab the OTA and go from there.

Wow, so sideloading the OTA broke it again.

Ug...found out there's a build 019. Apparently there's a problem with build 017. Sideloaded 019 and now I have no issues with safetynet.

glad someone else is seeing this, sideloaded OTA build 017 and Android Pay stopped working with it failing Safetynet's CTS Profile check

ParadingLunatic said:
Ug...found out there's a build 019. Apparently there's a problem with build 017. Sideloaded 019 and now I have no issues with safetynet.
Click to expand...
Click to collapse
Where is this 019 OTA? I'm having this same problem. I thought I was the Andromeda I tried but I knew that was rootless.
Thanks for shedding light on this.
---------- Post added at 07:45 PM ---------- Previous post was at 07:35 PM ----------
Did some more digging. Found it. Gonna see if it works.
Sent from my Nexus 6P using XDA-Developers Legacy app

ParadingLunatic said:
... Another REALLY strange thing is, during boot up, I have to unlock the phone, then it continues booting up and eventually finishes the boot up process, although I think I recall reading about this being some new security thing. Either way, don't think it relates to my issue.
Click to expand...
Click to collapse
This is because when you set the screen lock you checked the box to ask for the lock code when the system boots up. It's a good security measure that insures that if the phone is lost or stolen, a reboot will not allow someone to bypass the screen lock.

stevemw said:
This is because when you set the screen lock you checked the box to ask for the lock code when the system boots up. It's a good security measure that insures that if the phone is lost or stolen, a reboot will not allow someone to bypass the screen lock.
Click to expand...
Click to collapse
Yup I figured that out. I knew it was an added security feature but I couldn't recall where it was set. It seems that in Oreo, when you enroll in the fingerprint setup during the initial phone config, when it forces you to create a PIN it automatically sets that option without asking unlike how before, it used to ask.

ParadingLunatic said:
Yup I figured that out. I knew it was an added security feature but I couldn't recall where it was set. It seems that in Oreo, when you enroll in the fingerprint setup during the initial phone config, when it forces you to create a PIN it automatically sets that option without asking unlike how before, it used to ask.
Click to expand...
Click to collapse
Didn't realize it was automatically set in Oreo. I went thru 7 and the preview, so this option was already set. I will be getting the Pixel 2 XL, so it's something for me to check on.