Nexus 6P not unlocking, even with right password - Nexus 6P Q&A, Help & Troubleshooting

As the title says, my phone just isn't unlocking, no matter what.
I know for a fact I'm using the right password, it's successfully decrypting my phone. Entering the same password or any password I've used doesn't unlock the right screen, though.
I tried flashing a backup from a couple days ago, but it's having the same problem too.
Any advice?

Did you remove all security from your devices before making a backup?
I've seen several posts that tell people to do so before backing up. So I think that's where the issue is.

Yreisolgakig said:
As the title says, my phone just isn't unlocking, no matter what.
I know for a fact I'm using the right password, it's successfully decrypting my phone. Entering the same password or any password I've used doesn't unlock the right screen, though.
I tried flashing a backup from a couple days ago, but it's having the same problem too.
Any advice?
Click to expand...
Click to collapse
That's the known issue with TWRP and has been fixed with v3.0.2-0. Try that one.

DJBhardwaj said:
That's the known issue with TWRP and has been fixed with v3.0.2-0. Try that one.
Click to expand...
Click to collapse
It's affecting the OS?

Yreisolgakig said:
As the title says, my phone just isn't unlocking, no matter what.
I know for a fact I'm using the right password, it's successfully decrypting my phone. Entering the same password or any password I've used doesn't unlock the right screen, though.
I tried flashing a backup from a couple days ago, but it's having the same problem too.
Any advice?
Click to expand...
Click to collapse
Did this start occurring after restoring a backup? And before making the backup did you forget to remove all security?
DJBhardwaj said:
That's the known issue with TWRP and has been fixed with v3.0.2-0. Try that one.
Click to expand...
Click to collapse
He's talking about the OS, not TWRP.

Heisenberg said:
Did this start occurring after restoring a backup? And before making the backup did you forget to remove all security?
He's talking about the OS, not TWRP.
Click to expand...
Click to collapse
Nandroid backup issue with security is solved, isn't it @Heisenberg ?
Please correct me if I am wrong.

DJBhardwaj said:
Nandroid backup issue with security is solved, isn't it @Heisenberg ?
Please correct me if I am wrong.
Click to expand...
Click to collapse
Not that I'm aware of, I could be wrong though.

Heisenberg said:
Not that I'm aware of, I could be wrong though.
Click to expand...
Click to collapse
I hope it is. In the meantime, I just backed up PN ROM with fingerprint and PIN, and restored it successfully. :victory:

DJBhardwaj said:
I hope it is. In the meantime, I just backed up PN ROM with fingerprint and PIN, and restored it successfully. :victory:
Click to expand...
Click to collapse
Interesting. I'll have to give it a try myself at some point when I get the time.

Heisenberg said:
Interesting. I'll have to give it a try myself at some point when I get the time.
Click to expand...
Click to collapse
Sure. If you confirm, we will know that the issue has been resolved with the latest update. :highfive:

2 days ago, I made a backup of the Pure Rom I had so I could try another asop rom. Today I decided I wanted to go back to pure and when I did the restore, all went well, except when I had to enter a pin right after it booted. It would not recognize my pin that I know 100% was correct.
Any advice on that?

joey3002 said:
2 days ago, I made a backup of the Pure Rom I had so I could try another asop rom. Today I decided I wanted to go back to pure and when I did the restore, all went well, except when I had to enter a pin right after it booted. It would not recognize my pin that I know 100% was correct.
Any advice on that?
Click to expand...
Click to collapse
Which TWRP recovery version did you use?

joey3002 said:
2 days ago, I made a backup of the Pure Rom I had so I could try another asop rom. Today I decided I wanted to go back to pure and when I did the restore, all went well, except when I had to enter a pin right after it booted. It would not recognize my pin that I know 100% was correct.
Any advice on that?
Click to expand...
Click to collapse
If the backup you restored had a security pin still active then it won't restore properly or you won't be able to deactivate the pin code when asked for a screen pincode. At least that's how it has been in the past. They may of fixed it by now but that's only in the latest version.

This happened to me the other day when updating to the new PureNexus. There's a file in MM you can delete through TWRP so the OS will boot without a passcode, and then you can set a new one. I'm not sure whether I'm allowed to post it here as it seems dodgy but I found it in another XDA forum.

joey3002 said:
2 days ago, I made a backup of the Pure Rom I had so I could try another asop rom. Today I decided I wanted to go back to pure and when I did the restore, all went well, except when I had to enter a pin right after it booted. It would not recognize my pin that I know 100% was correct.
Any advice on that?
Click to expand...
Click to collapse
Go into TWRP>Advanced>File Manager>data>system.......delete locksettings.db, locksettings.db-shm, and locksettings.db-wal. Reboot the phone and you'll be able go into the OS just fine after that. You'll have to do this every time unless you make a backup with security removed.

DJBhardwaj said:
Sure. If you confirm, we will know that the issue has been resolved with the latest update. :highfive:
Click to expand...
Click to collapse
I can confirm that the issue has been resolved. Performed a backup and restore of my PN setup today.
Everything on my phone was successfully backed up and restored, including pin and fingerprint.

bouchigo said:
Go into TWRP>Advanced>File Manager>data>system.......delete locksettings.db, locksettings.db-shm, and locksettings.db-wal. Reboot the phone and you'll be able go into the OS just fine after that. You'll have to do this every time unless you make a backup with security removed.
Click to expand...
Click to collapse
This is how I fixed mine a couple days ago. Easy and quick. I also recommend this method. Although all I deleted was the locksettings.db because I couldn't find the others lol either way it worked
Sent from my Nexus 6P using XDA-Developers mobile app

Yreisolgakig said:
As the title says, my phone just isn't unlocking, no matter what.
I know for a fact I'm using the right password, it's successfully decrypting my phone. Entering the same password or any password I've used doesn't unlock the right screen, though.
I tried flashing a backup from a couple days ago, but it's having the same problem too.
Any advice?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B3AOKwsYI1C5WWVTeDZSSFhXZ0U/view?pref=2&pli=1
Try flashing this zip it will remove your current lock security. It is working on my phone though. (Don't have nexus 6p yet ) just be sire to make a backup before as i have never tested this for nexus 6P.

Related

scrambled PIN now locked out. Help please.

Hi guys.
i'm new here and greatly appreciate the knowledge here. I recently installed purenexus on my 6p. first time installing a custom rom. worked beautifully until i decided to try out the lockscreen scramble pin feature. Now when I try to unlock my phone it doesn't recognize my PIN. i've tried many times and something undoubtedly went wrong. is this a known issue with scrambling your pin?
So what should i do? A quick google search suggested I restore a backup. Is this the recommended method? I did a factory back up, i think. i did the back up after the factory reset but before flashing purenexus. i used the default twrp back up settings, which i believe did not include the vendor file.
i'm a complete novice when it comes to this sort of thing so if someone can give me a step-by-step explanation for me to unscrew myself here i'd greatly appreciate it.
thanks.
ent3rpryze said:
Hi guys.
i'm new here and greatly appreciate the knowledge here. I recently installed purenexus on my 6p. first time installing a custom rom. worked beautifully until i decided to try out the lockscreen scramble pin feature. Now when I try to unlock my phone it doesn't recognize my PIN. i've tried many times and something undoubtedly went wrong. is this a known issue with scrambling your pin?
So what should i do? A quick google search suggested I restore a backup. Is this the recommended method? I did a factory back up, i think. i did the back up after the factory reset but before flashing purenexus. i used the default twrp back up settings, which i believe did not include the vendor file.
i'm a complete novice when it comes to this sort of thing so if someone can give me a step-by-step explanation for me to unscrew myself here i'd greatly appreciate it.
thanks.
Click to expand...
Click to collapse
Are you sure you're hitting the right numbers? They'll be in a different position every time.
Heisenberg said:
Are you sure you're hitting the right numbers? They'll be in a different position every time.
Click to expand...
Click to collapse
I am. 100% certain.
it really seems as if my password was for some reason changed. before someone asks i am definitely using the correct pin. its the same PIN i've been using for years.
how do i regain control of my phone?
ent3rpryze said:
I am. 100% certain.
it really seems as if my password was for some reason changed. before someone asks i am definitely using the correct pin. its the same PIN i've been using for years.
how do i regain control of my phone?
Click to expand...
Click to collapse
i rebooted to recovery mode and i discovered that i moved my backup to my laptop. so now backup file is available.
can i just wipe my phone and reinstall the purenexus rom which is still on my phone
ent3rpryze said:
i rebooted to recovery mode and i discovered that i moved my backup to my laptop. so now backup file is available.
can i just wipe my phone and reinstall the purenexus rom which is still on my phone
Click to expand...
Click to collapse
Yes, if you clean flash the ROM you'll be able to get back into it. Had you restored a nandroid backup recently by any chance?
Heisenberg said:
Yes, if you clean flash the ROM you'll be able to get back into it. Had you restored a nandroid backup recently by any chance?
Click to expand...
Click to collapse
thanks a lot for clarifying that. i guess i have no other option.
has this been known to happen? scrambling PIN causing the pin to change.
I dont have a recent nandroid backup because my purenexus flash is only days old. is there a way to automate nandroid backups? is it wiser to keep the backups on the phone?
ent3rpryze said:
thanks a lot for clarifying that. i guess i have no other option.
has this been known to happen? scrambling PIN causing the pin to change.
I dont have a recent nandroid backup because my purenexus flash is only days old. is there a way to automate nandroid backups? is it wiser to keep the backups on the phone?
Click to expand...
Click to collapse
I've never seen this happen before. I'm pretty sure you can use Tasker to automate backups. I usually advise people to keep at least one backup or ROM zip on their phone, just in case.
IT HAPPENED AGAIN!
Per the ever hepful Heisenberg's recommendation, I wiped my phone and reflashed purenexus. This was yesterday. Everything went smoothly. Recreated my security PIN. Was able to unlock my phone with it without incident...until just now. Incorrect PIN error 3 times.
What is going on?!?!
It should be noted that both times this has happened has come after I turned my phone off. This time I happened to be charging my phone while it was off. I can't recall if it was the same case the first time it happened. Is this a purenexus issue?
found the solution.
"Delete this file /data/system/locksettings.db from TWRP."
I wish I had known this the first time it happened. Oh well. I sure hope this helps someone else in the future.
ent3rpryze said:
found the solution.
"Delete this file /data/system/locksettings.db from TWRP."
I wish I had known this the first time it happened. Oh well. I sure hope this helps someone else in the future.
Click to expand...
Click to collapse
This is usually over necessary after a user has created (and later restored) a nandroid backup without removing lockscreen security first. Are you saying you hadn't done this at all prior to the problem occurring?
Heisenberg said:
This is usually over necessary after a user has created (and later restored) a nandroid backup without removing lockscreen security first. Are you saying you hadn't done this at all prior to the problem occurring?
Click to expand...
Click to collapse
i dont know what qualifies as a nandroid backup. the only backup i created was with the TWRP backup function which i later moved to my laptop, as previously mentioned. and yes, i did that before the problem occured. it was before I had even installed pure nexus.
btw, it happened AGAIN (#3 for those keeping score). i'm going to assume there's a bug in the rom and forego the use of a security pin. also, for the first time, when i went back into twrp to once again delete the locksettings.db file i was prompted to enter a password before i could modify the system. Odd.
ent3rpryze said:
i dont know what qualifies as a nandroid backup. the only backup i created was with the TWRP backup function which i later moved to my laptop, as previously mentioned. and yes, i did that before the problem occured. it was before I had even installed pure nexus.
btw, it happened AGAIN (#3 for those keeping score). i'm going to assume there's a bug in the rom and forego the use of a security pin. also, for the first time, when i went back into twrp to once again delete the locksettings.db file i was prompted to enter a password before i could modify the system. Odd.
Click to expand...
Click to collapse
When making a nandroid (backup) in TWRP remove any pin, patter or fingerprints before backup or getting locked out will continue.
elevatorguy said:
When making a nandroid (backup) in TWRP remove any pin, patter or fingerprints before backup or getting locked out will continue.
Click to expand...
Click to collapse
thanks for that, but i believe i did that because i backuped a clean factory 6.0.1, sans any security setup. not sure if that was necessary but that's what i did.
ent3rpryze said:
i dont know what qualifies as a nandroid backup. the only backup i created was with the TWRP backup function which i later moved to my laptop, as previously mentioned. and yes, i did that before the problem occured. it was before I had even installed pure nexus.
btw, it happened AGAIN (#3 for those keeping score). i'm going to assume there's a bug in the rom and forego the use of a security pin. also, for the first time, when i went back into twrp to once again delete the locksettings.db file i was prompted to enter a password before i could modify the system. Odd.
Click to expand...
Click to collapse
The problem isn't with the ROM, I (along with what I'm guessing is pretty much every other user) use fingerprint and/or PIN/pattern security on Pure Nexus with no issues. A nandroid backup is one of those backups you create with TWRP, so yes it's what you described. But this problem shouldn't be occurring on a clean flash of Pure Nexus, can you please explain in detailed steps how you installed the ROM?
ent3rpryze said:
Hi guys.
i'm new here and greatly appreciate the knowledge here. I recently installed purenexus on my 6p. first time installing a custom rom. worked beautifully until i decided to try out the lockscreen scramble pin feature. Now when I try to unlock my phone it doesn't recognize my PIN. i've tried many times and something undoubtedly went wrong. is this a known issue with scrambling your pin?
So what should i do? A quick google search suggested I restore a backup. Is this the recommended method? I did a factory back up, i think. i did the back up after the factory reset but before flashing purenexus. i used the default twrp back up settings, which i believe did not include the vendor file.
i'm a complete novice when it comes to this sort of thing so if someone can give me a step-by-step explanation for me to unscrew myself here i'd greatly appreciate it.
thanks.
Click to expand...
Click to collapse
On Marshmallow, the scramble pin option is bugged if you use a long pin. Some rom devs choose to leave this out entirely. I haven't played with it to determine the cut off point but 4 digits is fine. I think I tried 8 digits once and it locked me out.
Sent from my Nexus 5X using Tapatalk
ent3rpryze said:
found the solution.
"Delete this file /data/system/locksettings.db from TWRP."
I wish I had known this the first time it happened. Oh well. I sure hope this helps someone else in the future.
Click to expand...
Click to collapse
Awesome.. Thanks a bunch for posting this... I am using Oneplus 3T , Resurrection Remix 5.7.4 ( Marshmallow) . Had turned on Scrambled PIN.. Ran into same issue as yours.. Last option left for me was to do factory reset from TWRP but I was scared to lose Google Authenticator Setup on my phone and many other things... Your solution saved me!! :good::good:
I also had a similar problem:
- freshly installed Carbon ROM with TWRP
- added lockscreen password in phone
- locked screen
- tried accessing using password
The password just fails. Using a shorter password works normally. The failing password is 13 characters long.

Restored a TWRP backup, now swipe pattern isn't working

So, I just restored a TWRP backup to my phone from earlier today, and upon boot, I can't unlock my phone. My fingerprint brings up the unlock pattern as normal, but my phone doesn't accept the pattern. And it's the same pattern I've always used, so it's not just me being stupid. Anyone know of a way around this? I'm going to try restoring the backup again, but I'm guessing it won't work any differently the 2nd time.
sfreemanoh said:
So, I just restored a TWRP backup to my phone from earlier today, and upon boot, I can't unlock my phone. My fingerprint brings up the unlock pattern as normal, but my phone doesn't accept the pattern. And it's the same pattern I've always used, so it's not just me being stupid. Anyone know of a way around this? I'm going to try restoring the backup again, but I'm guessing it won't work any differently the 2nd time.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/general/psa-twrp-backups-lockscreen-security-t3245070
matt4321 said:
http://forum.xda-developers.com/nexus-6p/general/psa-twrp-backups-lockscreen-security-t3245070
Click to expand...
Click to collapse
Awesome, thanks

Phone wont boot Into System

Hey there. I was wondering if anyone could help me out. I was running CM 13 on my Nexus 6P for a while but then I kept getting this message that said that there was something wrong internally and that I should contact the manufacturer. I just ignored it. I decided to download the latest nightly and try to freshly install it. I did a full wipe and installed the new CM13 nightly (7-1) and then gapps. When I tried booting the phone up it wouldnt go into the system. I went back into the recovery and tried installing a back up. I did that and tried booting up again into that restored backup and stilled didnt work. So I'm stuck right now with a non working phone. My bootloader is unlocked if that helps any.
XAL2 said:
Hey there. I was wondering if anyone could help me out. I was running CM 13 on my Nexus 6P for a while but then I kept getting this message that said that there was something wrong internally and that I should contact the manufacturer. I just ignored it. I decided to download the latest nightly and try to freshly install it. I did a full wipe and installed the new CM13 nightly (7-1) and then gapps. When I tried booting the phone up it wouldnt go into the system. I went back into the recovery and tried installing a back up. I did that and tried booting up again into that restored backup and stilled didnt work. So I'm stuck right now with a non working phone. My bootloader is unlocked if that helps any.
Click to expand...
Click to collapse
Have you tried flashing a factory IMG?
Sent from my Nexus 6P using XDA-Developers mobile app
XAL2 said:
Hey there. I was wondering if anyone could help me out. I was running CM 13 on my Nexus 6P for a while but then I kept getting this message that said that there was something wrong internally and that I should contact the manufacturer. I just ignored it. I decided to download the latest nightly and try to freshly install it. I did a full wipe and installed the new CM13 nightly (7-1) and then gapps. When I tried booting the phone up it wouldnt go into the system. I went back into the recovery and tried installing a back up. I did that and tried booting up again into that restored backup and stilled didnt work. So I'm stuck right now with a non working phone. My bootloader is unlocked if that helps any.
Click to expand...
Click to collapse
What options did you select when creating and restoring your backup? And, as above, have you tried flashing the factory images?
Heisenberg said:
What options did you select when creating and restoring your backup? And, as above, have you tried flashing the factory images?
Click to expand...
Click to collapse
I actually just did that. All is well. I was having trouble with fastboot commands because my phone wasnt being recognized but i just googled nexus 6p drivers installed them again and ran through the fastboot commands to get my phone back to stock.
XAL2 said:
I actually just did that. All is well. I was having trouble with fastboot commands because my phone wasnt being recognized but i just googled nexus 6p drivers installed them again and ran through the fastboot commands to get my phone back to stock.
Click to expand...
Click to collapse
Cool, glad you got it worked out. With your backup you may have selected the wrong options, have a look in my guide, there's a section dedicated to backups.
Heisenberg said:
Cool, glad you got it worked out. With your backup you may have selected the wrong options, have a look in my guide, there's a section dedicated to backups.
Click to expand...
Click to collapse
I actually have a question about that. When you say check vendor boxes are we supposed to check them both or just the vendor box and not the vendor image box to backup?
XAL2 said:
I actually have a question about that. When you say check vendor boxes are we supposed to check them both or just the vendor box and not the vendor image box to backup?
Click to expand...
Click to collapse
Only the ones that I mention, leave the system image and vendor image boxes alone.
Heisenberg said:
Cool, glad you got it worked out. With your backup you may have selected the wrong options, have a look in my guide, there's a section dedicated to backups.
Click to expand...
Click to collapse
Heisenberg said:
Only the ones that I mention, leave the system image and vendor image boxes alone.
Click to expand...
Click to collapse
Noted for sure. Thank you for your help. Oh hey can you answer one question for me though? When I was running CM13 how come I always got that alert that something internal was messed up and that I should contact my manufacturer? Also how come when I tried to do a clean install it wouldn't boot? Like that confuses me a lot because it was a clean install but I ran into problems.
XAL2 said:
Noted for sure. Thank you for your help. Oh hey can you answer one question for me though? When I was running CM13 how come I always got that alert that something internal was messed up and that I should contact my manufacturer? Also how come when I tried to do a clean install it wouldn't boot? Like that confuses me a lot because it was a clean install but I ran into problems.
Click to expand...
Click to collapse
Perhaps you had the wrong vendor image installed? Other than that I'm not sure. As for why the clean flash didn't boot I'm not sure either, there could be multiple causes for that so it's a bit hard to narrow down.
Heisenberg said:
Perhaps you had the wrong vendor image installed? Other than that I'm not sure. As for why the clean flash didn't boot I'm not sure either, there could be multiple causes for that so it's a bit hard to narrow down.
Click to expand...
Click to collapse
Oh man who knows. Thank you again though for the help and answering to quickly! Also thank you for that guide! Saved my phone's life. Lol
XAL2 said:
Oh man who knows. Thank you again though for the help and answering to quickly! Also thank you for that guide! Saved my phone's life. Lol
Click to expand...
Click to collapse
No probs, happy to help.

Can't unlock pattern and TWRP shows no files

Earlier I was on Megapixel Rom running february vendor img. I flashed my PN ROM backup thru flashify then it boots up with my security lock pattern. It shows that my pattern is not correct. I am rebooting to y TWRP but still it doesn't show me any files and I cant flash a zip rom. Someone help me (((
Try using different decryption method...
Your problem seems to be unsolvable right now. This is a known bug or vulnerability in the latest release of TWRP build. I am sorry.
Gameplay_Ethan said:
Your problem seems to be unsolvable right now. This is a known bug or vulnerability in the latest release of TWRP build. I am sorry.
Click to expand...
Click to collapse
wow I am in shock right now, idk what to do.. my computer doesn't recognize my phone even though Im on bootloader/twrp
lesterinidad said:
wow I am in shock right now, idk what to do.. my computer doesn't recognize my phone even though Im on bootloader/twrp
Click to expand...
Click to collapse
factory reset?
v12xke said:
factory reset?
Click to expand...
Click to collapse
idk what I did but the files suddenly shows but it wipes my media.. only problem now is whenever I reboot into TWRP it asks me the password to decrypt and after I booted up it also ask me my password to start my device like a pop up message
lesterinidad said:
idk what I did but the files suddenly shows but it wipes my media.. only problem now is whenever I reboot into TWRP it asks me the password to decrypt and after I booted up it also ask me my password to start my device like a pop up message
Click to expand...
Click to collapse
See the sticky thread in General: https://forum.xda-developers.com/nexus-6p/general/psa-twrp-backups-lockscreen-security-t3245070
You might be better off flashing the full factory image to start over and then reflash whatever you want in terms of recovery and custom rom. I did that when I was in the same situation as you. But I have never successfully restored a nandroid backup on the 6P and I never had that problem with any other phone I have ever owned. Different versions of TWRP only give me different issues when I try to restore a backup. I've had bootloops. I've had TWRP ask for a password even though I removed security before making the back up as people advise. I've had backups that seemed to restore until I started getting error messages that there was something wrong with my device and I should contact the phone manufacturer. I've given up on Nandroid backups on this phone.

Upgraded to Android 10 - Gapps asking for a pin?

So upgraded to Android 10 removed all fingerprints and locks before hand.
Tried multi different Android 10 ROMs asks me a for a pin on setup wizard which I cannot get past keeps saying invalid pin.
When I remove the Gapps I can get though to the normal start up and this happens on all Android 10 ROMs I've tried.
I've now reverted to Android 9 with no problems. Any ideas?
Hi,
Happened to me as well, please try this https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
it worked for me.
koolnauman said:
Hi,
Happened to me as well, please try this https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
it worked for me.
Click to expand...
Click to collapse
Thanks Kool. Not sure if I can be bothered to risk it. Restoring is such an effort
jameswalker457 said:
Thanks Kool. Not sure if I can be bothered to risk it. Restoring is such an effort
Click to expand...
Click to collapse
he didn't mean to restore a backup!..
he just suggested that u try that methode by deleting those files from TWRP

Categories

Resources