TWRP Restore Problem with Fingerprint security - Nexus 6P Q&A, Help & Troubleshooting

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).

Related

Bad suprise with fingerprint scanner after TWRP restore

So yesterday I did my first TWRP restore. Restore worked fine, device booted without issues to the lockscreen.
Lockscreen was protected by fingerprint.
To my surprise, none of my fingers were detected. Strange I thought, but hey, thats what the backup password is for.
So I entered the backup password and ... the device unlocked.
So, no big deal I thought, somehow the fingerprint data got scrambled in the restore process but the password worked.
Next step: Disable Fingerprint lockscreen / Relearn fingerprints.
Of course here I have to authenticate myself again with fingerprint (not working of course) or the backup password.
To my surprise, the device does not accept the backup password when entered in the fingerprint settings...
Uh Oh, I now thought. Well, I CAN unlock my device but entering the backup password every time is kind of annoying.
As I found no solution on how to disable the fingerprint lockscreen I was forced to factory reset the device (strangely enough during factory reset I was again asked for the backup password and it was accepted in this dialog).
So, as a warning, disable your fingerprint lockscreen before making a TWRP/CWM backup.
If someone has a tip on how I could have avoided a factory reset, I would be grateful to learn more...
Gandhi70 said:
So yesterday I did my first TWRP restore. Restore worked fine, device booted without issues to the lockscreen.
Lockscreen was protected by fingerprint.
To my surprise, none of my fingers were detected. Strange I thought, but hey, thats what the backup password is for.
So I entered the backup password and ... the device unlocked.
So, no big deal I thought, somehow the fingerprint data got scrambled in the restore process but the password worked.
Next step: Disable Fingerprint lockscreen / Relearn fingerprints.
Of course here I have to authenticate myself again with fingerprint (not working of course) or the backup password.
To my surprise, the device does not accept the backup password when entered in the fingerprint settings...
Uh Oh, I now thought. Well, I CAN unlock my device but entering the backup password every time is kind of annoying.
As I found no solution on how to disable the fingerprint lockscreen I was forced to factory reset the device (strangely enough during factory reset I was again asked for the backup password and it was accepted in this dialog).
So, as a warning, disable your fingerprint lockscreen before making a TWRP/CWM backup.
If someone has a tip on how I could have avoided a factory reset, I would be grateful to learn more...
Click to expand...
Click to collapse
Hi there, I have same bad experience with it, even worse !
after reading your post I've trying to prepare myself so I turned off the screen lock fingerprint security and full of happiness flashed new rom, then I've noticed all my data moved before to PRIVATE disappeared so they are not stored in any more at internal sd card, but somewhere else! So i've restored my previous backup from twrp but none of my fingerprints works also my password is not recognised anymore in private mode
So it looks like I lost all my files saved in private mode, I am lucky it wasn't nothing special, just random photos I've put there for tests! but anyway we need some solution for future backups, maybe improved recovery or something
Gandhi70 said:
So yesterday I did my first TWRP restore. Restore worked fine, device booted without issues to the lockscreen.
Lockscreen was protected by fingerprint.
To my surprise, none of my fingers were detected. Strange I thought, but hey, thats what the backup password is for.
So I entered the backup password and ... the device unlocked.
So, no big deal I thought, somehow the fingerprint data got scrambled in the restore process but the password worked.
Next step: Disable Fingerprint lockscreen / Relearn fingerprints.
Of course here I have to authenticate myself again with fingerprint (not working of course) or the backup password.
To my surprise, the device does not accept the backup password when entered in the fingerprint settings...
Uh Oh, I now thought. Well, I CAN unlock my device but entering the backup password every time is kind of annoying.
As I found no solution on how to disable the fingerprint lockscreen I was forced to factory reset the device (strangely enough during factory reset I was again asked for the backup password and it was accepted in this dialog).
So, as a warning, disable your fingerprint lockscreen before making a TWRP/CWM backup.
If someone has a tip on how I could have avoided a factory reset, I would be grateful to learn more...
Click to expand...
Click to collapse
Same thing happened to me today, tried restoring Echoe rom (nandroid) then smack!! fingerprint no longer works
having to factory reset
That's weird, because i did a fully nandroid backup in TWRP on my Samsung Galaxy Note 4 (SM-N910F) like 4-5 days ago. I did that to try out another ROM, but i didn't like that so i restored the ROM i took a nandroid backup of.
After that, my fingerprint scanner works perfect or as good as it did before i did a nandroid backup.
Tom-Helge said:
That's weird, because i did a fully nandroid backup in TWRP on my Samsung Galaxy Note 4 (SM-N910F) like 4-5 days ago. I did that to try out another ROM, but i didn't like that so i restored the ROM i took a nandroid backup of.
After that, my fingerprint scanner works perfect or as good as it did before i did a nandroid backup.
Click to expand...
Click to collapse
well,I tried again (this time I disabled the fingerprint lockscreen before making the backup) and again, after restore, I cannot access the fingerprint settings.
Fingerprints are not recognized and the backup password does not work within the settings dialog.
Not that big of a problem as I did not use the fingerprint lockscreen.
But does anyone know a way to completely reset the fingerprint data/backup password other then making a factory reset?
krohme said:
Same thing happened to me today, tried restoring Echoe rom (nandroid) then smack!! fingerprint no longer works
having to factory reset
Click to expand...
Click to collapse
Backup password did not work either?
Gandhi70 said:
Backup password did not work either?
Click to expand...
Click to collapse
No it only worked to unlock the device - but strangely enough the same backup password would not be accepted by the system for gaining access to the finger print reset settings. Very weird.. I'll be holding off restoring from a nandroid until I know the reason for this bug.
I had the same issue from a cwm restore this evening. Fingerprints not recognised on lockscreen but password is. When I goto try and re-register my fingerprints I can't access the menu with either fingerprint or backup password. Did you guys wipe the cache and dalvik cache before restoring? Could this even have an effect on the fingerprint data? I can't face having to factory reset and then setting up again
my device got effed up... I was forced to delete the stored fingerprints cause I had no options, so when I did that, the fingerprint sensor came up the an error and it said to restart, I did so many times, it didn't work, got corrupted, so I odined the firmware, no luck, we had an update, so I odined the firmware, and still didn't work, this is my 2nd device and its working great.. on the tmobile thread, it stated to delete any stored fingerprints before doing a nandroid backup, or flashing a new rom,, my 2nd phone is working fine, I have flashed and tested my roms without any issues,
try to delete any stored fingerprints, then in twrp recovery, wipe system, data, cache and dalvik, I always do that 2x to make sure everything is clean,
do ODIN and use your firmware to see if it fixes your issues,
some have had success, others had to return there devices, don't know,
Any update to this issue? Returning the device not an option anymore
Well i switched from fingerprint to pattern lock screen. No problem with that one and Cwm restore works fine too
Gesendet von meinem SM-N910F mit Tapatalk
For All those suffer from a bad suprise with fingerprint scanner after TWRP restore: please visit this page and thank the great developer Dr. Ketan.
ucevik said:
For All those suffer from a bad suprise with fingerprint scanner after TWRP restore: please visit this page and thank the great developer Dr. Ketan.
Click to expand...
Click to collapse
Flashed with no luck. Still gives me error when opening fingerprint
Am I going to lose the fingerprint function forever? [emoji26]
So, what's the right thing to do if you want to install a new firmware and restore the data partition from nandroid backup?
I think:
1. Do nandroid backup
2. Unlock device, cancel all fingerprints
3. Full reset device
4. Restore nandroid of data only
5. Setup fingerprints again
Might this procedure work as expected?
Count me as another with the same problem. I even used Android Device Manager to change the backup password. It updates the screen lock password but does not update the fingerprint settings backup password. So still no solution.
There has to be a way to fix this w/ factory reset. The fact that factory reset wipes out the registered fingerprints indicates that the info is stored in /data. Where is it?
Edit: There is a "fingerprints" app. Clear data is not an option. When I select "Manage storage", I'm told that I do not have permission. If we know where the data is stored, we can wipe it and maybe start over.
Question for those who have this specific problem--do you have Xposed installed?
I started a thread here:
http://forum.xda-developers.com/general/general/25-via-paypal-to-1st-person-helps-reset-t2988027
Offering $25 to someone who comes up w/ a solution.....
Honestly I just stopped using the fingerprint scanner. I cannot access the fingerprint data but as i am using the pattern lockscreen i don't care.
Gesendet von meinem SM-N910F mit Tapatalk
Maybe one should look at the log while starting over with a pristine note 4 and setting up the fingerprint recognition.
Gandhi70 said:
Honestly I just stopped using the fingerprint scanner. I cannot access the fingerprint data but as i am using the pattern lockscreen i don't care.
Gesendet von meinem SM-N910F mit Tapatalk
Click to expand...
Click to collapse
Me also, and have converted all my other devices to pattern as well. The Samsung fingerprint implementation comes with too many baggage. I would still, though, like to know of a solution to clear up the registration.

Fingerprint hardware unavailable? Enrollment didn't work?

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

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!

Screen lock pattern not recognized after restoring stock TWRP backups

After restoring in TWRP and booting to system the correct pattern wasn't recognized, meaning I couldn't authenticate thus rendering the backup useless. Tried all three backups I had of stock or stock-rooted with the same result, all using the same pattern since getting the phone. Interestingly, though, my latest non-stock ROM's backup, which I'd also set up with the same pattern, was recognized correctly after restoring, so it doesn't seem to be a problem with TWRP.
My only way to return to stock was by flashing the full firmware and setting up again from square one. I've made two fresh backups (before and after setting up my stuff) after temporarily setting the screen lock to none/slide. If others have been able to restore stock backups with their pattern security intact, please let us know. Otherwise I'd advise disabling lock screen security before backing up, and not trusting existing stock backups that weren't done that way.
Had the same problem on other phones. Fixed it by deleting all *.key files in ./data/system via TWRP Filemanager.
Had the same problem, I switched to PIN after a full restore. Good to know there is a fix!
http://cloud.tapatalk.com/s/59cd07bf923a3/LockscreenKey.zip
Flash this if you are locked out of your phone
Sent from my XT1687 using Tapatalk
thudenska said:
Had the same problem on other phones. Fixed it by deleting all *.key files in ./data/system via TWRP Filemanager.
Click to expand...
Click to collapse
Yes, this solves the problem. However, I recommend to disable the lock before doing the backup (and reenable after).
:laugh:
This problem also occurs when you use a multibooting environment. As soon as you switch back to the first rom, the the pattern isn't recognized. It's driving me crazy! Somehow the patterns don't survive a backup or a change such as installing a second rom...
robot_head said:
http://cloud.tapatalk.com/s/59cd07bf923a3/LockscreenKey.zip
Flash this if you are locked out of your phone
Sent from my XT1687 using Tapatalk
Click to expand...
Click to collapse
Awesome - thanks!
Got into this little pattern lock-out mess when I restored a good working ROM. Did TWRP full-wipe with System partition to do good housekeeping prior to Restore. Restore worked fine except my Pattern Security feature wasn't working. Flashed your Zip Install - worked great and got me in fine after reboot.
Cool to have your Zip Unlocker around in case this happens again.
Thanks - John

Locked Out Of Nandroid

Ok........ I removed pin and fingerprint Before doing the backup, rebooted TWICE to make sure there was no security, and did the backup. Put security back after all that. A day later I had reason to use the nandroid, removed security, wiped and restored, rebooted and to my surprise came to pattern screen. Mine would not work!
After much heartache, reboots and trying to get past it I ended up wiping and starting with fresh install. Anyone experienced this before? What's the work around? I'm pretty sure I did what was needed, please correct me if wrong, right now I'm weary of setting fingerprint or pattern again.
BTW yes I did delete locksettings.db (close enough at some point ... did not help

Categories

Resources