I'm running Carbon rom on my 6P, after getting around to flashing the flashabling zip for supersu, my pattern I use to boot into android(not the lockscreen pattern) no longer works.
It still asks for my pattern to start android, but when I put it in, it says it's not right. I've tried my pattern several times and a couple random ones to see if it just messed it up.
Is there something I can do in twrp to fix this? Or will I have to lose everything off my phone?
There's a sticky in the general section:
Https://forum.xda-developers.com/nexus-6p/general/psa-twrp-backups-lockscreen-security-t3245070
drnizeguy said:
There's a sticky in the general section:
Https://forum.xda-developers.com/nexus-6p/general/psa-twrp-backups-lockscreen-security-t3245070
Click to expand...
Click to collapse
I just had another person point me to that thread a few minutes ago. Deletion of the locksettings does nothing. I still have it asking for a pattern to start android.
xBr4v3x said:
...Is there something I can do in twrp to fix this? Or will I have to lose everything off my phone?
Click to expand...
Click to collapse
Nothing to do. Yes, you have already lost everything. Factory reset and start over. Most of the time this happens to people who have been running unencrypted, screw up, and then end up encrypted. NOT saying this is you because you seem to have at one time been encrypted and HAD a working boot PIN. One of the features of a true encrypted system is that once you lose the keys, nobody can help you. I usually keep a TiBu of all my non-market apps on the PC. Between Google's restore of market apps and Ti-Bu, anyone can be up and running the way they were within one hour. Sucks but there it is.
Related
I have a nexus 6P running rooted stock rom and I wanted to try out a new rom. Before flashing the new rom, I made a nandroid backup via TWRP. Now, the rom that I was backing up had fingerprint security setup with backup passcode for unlocking the phone.
So I tried new rom and it didn't work (read-too many issues and too many crashes). Decided to revert back to my original setup. Went back into TWRP and restored the backup.
After booting the phone up, I can't log in to my phone anymore. As you know after every reboot, fingerprint sensor doesn't work unless you enter the backup passcode. So I am entering my passcode and its not accepted. I have tried entering passcode many times but to no avail. I know my passcode so possibility of me forgetting it is not valid.
Has anybody else seen or ran into this issue yet?
The step folks are missing is Prior to installing a backup you Must Change security to None before you even start a backup This clears password, pin and saved finger prints. I believe once security is changed it is safe to backup and then install backup. You will need to reenter Pin and Fingerprints.
Born<ICs said:
The step folks ...
... is changed it is safe to install backup.
Click to expand...
Click to collapse
You mean clear the security before making a backup ... right?
if not, how would I change security on a backup file of rom that had security enabled.
I have never used lock screen security before so never ran into this issue.
No, dig through this forum for tech details. But my understanding is anytime you make/install a backup or reflash rom or go back to stock you must reset you Security options in settings to None. You have security now, probably Fingerprints, and the required Lockscreen Pin.
If you try to install backup or Rom or whatever without doing so you get what you experienced. There is a path out of it if you read further.
Pin or Pattern on boot after restoring Nandroid
Born<ICs said:
No, dig through this forum for tech details. But my understanding is anytime you make/install a backup or reflash rom or go back to stock you must reset you Security options in settings to None. You have security now, probably Fingerprints, and the required Lockscreen Pin.
If you try to install backup or Rom or whatever without doing so you get what you experienced. There is a path out of it if you read further.
Click to expand...
Click to collapse
The interesting thing is, I intentionally chose to enter pattern/pin on rebooting. The strange (actually may not be strange .....but strange to me) thing is that even when I move on to different Roms, that initial choice is remembered and embedded since even after choosing not to require pin/pattern when rebooting, I get prompted. Also the pin/pattern works during recovery, it also works on the initial startup after restoring a backup but then fails after successful fingerprint use (it will actually say "wrong pin" or "wrong pattern") at the end of the booting process. The thing is, I have only used one pin and at other times one password ever with this device. Eventually I had to do a factory reset to solve this issue (thank goodness I was able to back up my internal storage to my computer in TWRP recovery mode).
Recipe:
TWRP 2.8.7.2
TWO Nexus 6Ps on 6.0.1
One N6P systemless rooted
Official Android SDK (fastboot)
So I got a replacement N6P from Fi as I noticed some slight bending on my original, and I was working on moving my data over using TWRP so I could keep all my app data, etc. When I backed up my original 6P, I forgot to remove screen and boot security, so when I flashed on to my new 6P, I was locked out (as expected, known bug). I tried this fix to get in to my system, and it worked! I was able to log in. However, I noticed that my old fingerprints were still enrolled and I wanted to start those fresh, so I tried to remove them. When I selected "Delete" for each enrolled fingerprint, nothing happened. This was the first clue. I then tried to enroll new fingerprints and got the following message:
Code:
[B]Enrollment was not completed[/B]
Fingerprint enrollment didn't work. Try again or use a different finger.
The other odd thing is that on the lockscreen, I was getting a red text error message that read something like "Fingerprint hardware not available."
So I figured something got messed up security wise from the fix I tried after flashing a locked nandoird. I then went back and made a new nandroid backup (boot, system, data) on my old phone making sure that all security was turned off. Same thing!
Wondering if the hardware did actually get messed up somehow, I flashed back to official stock 6.0.1 from Google. Fingerprinting then started working!
So nothing I have done since then has made any difference when trying to restore my userdata from my old phone. I've tried wiping cache/dalvik, and removing the locksettings.db file, but these didn't change anything either.
Has anyone had this issue before? It seems really bizarre to me. I'm probably going to end up flashing stock and restoring userdata via TB, but that is a headache compared to nandroid so if possible I'd like to get this to work.
Tried wiping userdata then flashing userdata from my old 6P and that did not work either.
Have you tried wiping data, setting up the device again, and then checking if you can add a fingerprint?
I tried restoring data from a device I had to RMA too, and got that exact message every time - I gave up in the end as I tried wiping everything but the only thing that worked was clearing userdata & restoring my apps from the nandroid via TiBu.
All in all, I presume it's something to do with the fingerprint scanner having a different hardware key/serial to the new one and retaining that info somewhere in the data partition when you back it up.
DanielF50 said:
Have you tried wiping data, setting up the device again, and then checking if you can add a fingerprint?
I tried restoring data from a device I had to RMA too, and got that exact message every time - I gave up in the end as I tried wiping everything but the only thing that worked was clearing userdata & restoring my apps from the nandroid via TiBu.
All in all, I presume it's something to do with the fingerprint scanner having a different hardware key/serial to the new one and retaining that info somewhere in the data partition when you back it up.
Click to expand...
Click to collapse
Yup I did try that, didn't work either. I'm right where you were too, currently restoring apps for TB. Your hypothesis seems plausible to me, I hadn't thought of that. Kind of a bummer for swapping devices if that is the case. I wonder if we could find where the fingerprint key is stored in userdata and back it up prior to flashing the nandroid?
Thanks for the reply!
No problems & yes, it is, though I presume it's either been done for some sort of security, or as a complete oversight - I can't see Google deliberately doing so, especially on a Nexus device.
I think it's probably highly likely that someone will find the hardware/serial file soon and find a way to stop it from being overwritten when TWRP restores the data partition, though it is annoying that it hasn't been discovered yet... Thankfully restoring from a nandroid through TitaniumBackup isn't too bad nowadays!
Srry for necro but I think I might have found a workaround solution to this problem or at least the problem which is very similar to this one. Please check "symptoms" in the description of the solution to make sure we are talking about the same issue.
Here's the link to the solution: http://forum.xda-developers.com/showpost.php?p=68374321&postcount=1446
erikem said:
Srry for necro but I think I might have found a workaround solution to this problem or at least the problem which is very similar to this one. Please check "symptoms" in the description of the solution to make sure we are talking about the same issue.
Here's the link to the solution: http://forum.xda-developers.com/showpost.php?p=68374321&postcount=1446
Click to expand...
Click to collapse
Sorry for another necro, but this doesn't work for me on Android 7.1.1
Edit: Correct fix here: https://forum.xda-developers.com/showpost.php?p=68199207&postcount=9
Has anyone had issues setting up Imprint after importing a nandroid backup?
I had to RMA my 6P due to a faulty charging port and I can successfully set up Imprint in the factory state, however, after I import the backup, it won't allow me to set it up.
I've tried to do just a data import, a full nandroid import...pretty much every single option and constantly reflashing to stock to retry. I'm at a loss because it's definitely not a hardware problem as I can set it up during stock.
As soon as I click next to train my fingerprints, it flashes: "Enrollment was not completed. Fingerprint enrollment didn't work. Try again or use a different finger."
Has anyone ever run into this issue? Thanks for your help!
Never and I mean never restore a nandroid from one device to another. There are device specific files in that nandroid. Just hope you didn't kill your efs partition which kills your IMEI and in turn makes it not connect to any network.
RaysBucsBolts said:
Has anyone had issues setting up Imprint after importing a nandroid backup?
I had to RMA my 6P due to a faulty charging port and I can successfully set up Imprint in the factory state, however, after I import the backup, it won't allow me to set it up.
I've tried to do just a data import, a full nandroid import...pretty much every single option and constantly reflashing to stock to retry. I'm at a loss because it's definitely not a hardware problem as I can set it up during stock.
As soon as I click next to train my fingerprints, it flashes: "Enrollment was not completed. Fingerprint enrollment didn't work. Try again or use a different finger."
Has anyone ever run into this issue? Thanks for your help!
Click to expand...
Click to collapse
As already stated you should never restore a backup from a different device. If you had a pin and fingerprint setup when you made the backup then it will not restore properly on any device. A thread has been pinned in the general section about TWRP'S issues with lockscreen security and backups.
If you can get into adb try this after restoring:
rm /data/system/locksettings.db
rm /data/system/*.key
If this doesnt work, go to twrp file manager and manually delete the files.
As mentioned above, before backing up you should always remove security.
It was mentioned in the TWRP thread that you should NEVER make a Nandroid Backup before disabling the fingerprint and swipe gestures. If you did a Nandroid Backup without having removed the security options first, you won´t be able to use it.
I am having the same issue after getting my new phone and trying to do the same thing. Each device seems to have some kind of Sensor ID or something else that stops the scanner from working. check out the reddit thread and this other thread on xda...
https://www.reddit.com/r/Nexus6P/comments/3vjkq3/q_nandroid_from_6p_to_6p_which_partitions_to/cxqfcl1
http://forum.xda-developers.com/nexus-6p/help/fingerprint-hardware-unavailable-t3274436
seems everyone has the same issue. No fix as of yet but twrp will work to restore all of your data including your android id from a nandroid im pretty sure
jerflash said:
I am having the same issue after getting my new phone and trying to do the same thing. Each device seems to have some kind of Sensor ID or something else that stops the scanner from working. check out the reddit thread and this other thread on xda...
https://www.reddit.com/r/Nexus6P/co...oid_from_6p_to_6p_which_partitions_to/cxqfcl1
http://forum.xda-developers.com/nexus-6p/help/fingerprint-hardware-unavailable-t3274436
seems everyone has the same issue. No fix as of yet but twrp will work to restore all of your data including your android id from a nandroid im pretty sure
Click to expand...
Click to collapse
Of course each one has its own ID.
This is not what Nandroids are for. Restoring this way you risk ruining your imei which then requires you to get a new device which warranty will not cover. So come on guys stop being lazy and do things properly. If you mess up your device then you have no else to blame but yourself.
And we wonder why OEM/Google are locking devices down.
zelendel said:
Of course each one has its own ID.
This is not what Nandroids are for. Restoring this way you risk ruining your imei which then requires you to get a new device which warranty will not cover. So come on guys stop being lazy and do things properly. If you mess up your device then you have no else to blame but yourself.
And we wonder why OEM/Google are locking devices down.
Click to expand...
Click to collapse
I would never tell anyone to restore EFS between two different devices! That could really mess things up. What we are talking about here is restoring the "Userdata" backup between two devices which can be safe if you know what you are doing...(I have done it for years without issue.) problem comes form there must be something hidden inside the userdata that stops you from restoring and using the fingerprint reader. Its actually a good feature for most if not a high level user.
I'm sure there will be a work around soon enough
jerflash said:
I would never tell anyone to restore EFS between two different devices! That could really mess things up. What we are talking about here is restoring the "Userdata" backup between two devices which can be safe if you know what you are doing...(I have done it for years without issue.) problem comes form there must be something hidden inside the userdata that stops you from restoring and using the fingerprint reader. Its actually a good feature for most if not a high level user.
I'm sure there will be a work around soon enough
Click to expand...
Click to collapse
More and more apps are not storing their info into data partition.
Wouldn't count on a work around. With the new Qualcomm security settings many oem are really looking at doing it like the BB android device which can't even be rooted.
Did you find a solution guys? I have same problem.
Tell you the truth guys... just use helium, then factory reset. let google re-add everything and for what does not use helium. i did this and it works for most things. not very annoying at all
Hello all,
So in an absent minded spell I changed my screen pattern to a complicated one just to be more 'safe'. It hit me when i tried to unlock the phone seconds later that I had already forgotten the patter. . I know it is very stupid to **** around like that.
But silver lining is when the phone is paired with my Bluetooth headset the phone unlocks itself and I am able to go inside. This is due to Smart Lock feature which assumes my phone is safe when paired with Bluetooth headset.
But the main thing is I am not able to change the pattern itself as it asks for older pattern. I have read a lot of posts on how the pattern can be disabled by deleting gesture.key. It turns out getting super user permission to do that is very complicated. I have failed to change or disable the pattern so far.
Guys help!
kajang said:
Hello all,
So in an absent minded spell I changed my screen pattern to a complicated one just to be more 'safe'. It hit me when i tried to unlock the phone seconds later that I had already forgotten the patter. . I know it is very stupid to **** around like that.
But silver lining is when the phone is paired with my Bluetooth headset the phone unlocks itself and I am able to go inside. This is due to Smart Lock feature which assumes my phone is safe when paired with Bluetooth headset.
But the main thing is I am not able to change the pattern itself as it asks for older pattern. I have read a lot of posts on how the pattern can be disabled by deleting gesture.key. It turns out getting super user permission to do that is very complicated. I have failed to change or disable the pattern so far.
Guys help!
Click to expand...
Click to collapse
Its the only way to do it, the other way is to do a backup and then factory reset
PS: What made it difficult for you?
if you have a custom recovery, it is easy to pick up any zip file that is, for example, a mod, decompresses and only removes the metainfo file and create a zip that file and flashing, ready will restart without lock pattern without losing anything
Deleting gesture.key
ExCuTioN said:
Its the only way to do it, the other way is to do a backup and then factory reset
PS: What made it difficult for you?
Click to expand...
Click to collapse
Hi
I am able to go to adb shell and execute some commands. But not commands like delete which require Super user permissions. I am having hard time getting that. I am not well versed with command line.
Customer recovery
browcantor said:
if you have a custom recovery, it is easy to pick up any zip file that is, for example, a mod, decompresses and only removes the metainfo file and create a zip that file and flashing, ready will restart without lock pattern without losing anything
Click to expand...
Click to collapse
I have tried installing Twrp recovery, but it gives an error while installing. I am forgetting the exact error. I could not follow rest of what you are saying. I am relatively inexperienced. What is metainfo? Are talking about flashing new ROM?
I strongly suggest that you factory reset your device. It'll be simpler for you that don't have all the knowledge to do other way. Beside, doing so demands a rooted device. Also beside, with the Google account sync it's very easy to setup the device again.
https://drive.google.com/file/d/0B7C0PrsBvY69NU9JM0hJeEdQd2c/view?usp=drivesdk
Flashing
Hi everyone,
so in my immense stupidity, I actually managed to set my phone password wrongly, and now I can't get in. Spent a day trying passwords to find the typo but that was unsuccessful.
I have crDroid Android 11, bootloader unlocked, rooted with magisk, and TWRP 3.5.0.
How can get my phone back? I would love to save the internal storage since I have important stuff, but you know, if wiping it is the only way I have to go for it.
Thanks in advance.
Use this method. I have seen many people online suggesting it works.
Remove /Bypass Lockscreen With Recovery
Recently when i restored my data using TWRP i faced a problem at lock screen. I was not able to unlock my phone with the pin i set Earlier..So after so many attempts i was able to find a solution for that problem.(works with pattern,pin etc)...
forum.xda-developers.com
You are essentially removing lockscreen settings completely and should work as you still have TWRP access.
madman said:
Use this method. I have seen many people online suggesting it works.
Remove /Bypass Lockscreen With Recovery
Recently when i restored my data using TWRP i faced a problem at lock screen. I was not able to unlock my phone with the pin i set Earlier..So after so many attempts i was able to find a solution for that problem.(works with pattern,pin etc)...
forum.xda-developers.com
You are essentially removing lockscreen settings completely and should work as you still have TWRP access.
Click to expand...
Click to collapse
Thanks for the responce, but unfortunately that didn't work.
I deleted the files as explained in the thread you linked but now the lockscreen doesn't work at all, it's just a black screen. The power menu appears if I hold the power button, but nothing else. I tried swiping in some direction on the black screen but it doesn't unlock.
Also tried to sideload the rom again (dirty and clean flash), and magisk, still no luck.
Read the entire thread but nothing helpful.
DarkLudo77 said:
Thanks for the responce, but unfortunately that didn't work.
I deleted the files as explained in the thread you linked but now the lockscreen doesn't work at all, it's just a black screen. The power menu appears if I hold the power button, but nothing else. I tried swiping in some direction on the black screen but it doesn't unlock.
Also tried to sideload the rom again (dirty and clean flash), and magisk, still no luck.
Read the entire thread but nothing helpful.
Click to expand...
Click to collapse
Is TWRP able to decrypt the data? I'm guessing that's a no as the password is not accepted by the lockscreen. If TWRP was magically OK with the password, you could have adb pulled the files.
But apart from reseting the lockscreen using TWRP, I don't know a way to fetch the files.
madman said:
Is TWRP able to decrypt the data? I'm guessing that's a no as the password is not accepted by the lockscreen. If TWRP was magically OK with the password, you could have adb pulled the files.
But apart from reseting the lockscreen using TWRP, I don't know a way to fetch the files.
Click to expand...
Click to collapse
TWRP can decrypt if the correct passoword is provided. Tried pulling with adb the files anyway, even if they are encrypted, but the phone doesn't allow that either.
Thanks anyway