Develop Bugs

Locked out of phone after restoring system

I wanted to try an other rom so I backed up my current system. (using TWRP 3.0.0-0)
Now I want to go back, so I restored the backup.
Everything is fine, phone booting up, unlocking simcard, but then...
I cant get into my phone!
I use the fingerprint scanner, but when the phone reboots I have to put in the extra security pin.
But now it doenst accept my code anymore, so I'm locked out of my phone.
Is this a common bug/error?
I'm 200% sure the code is right.

this is a known issue, before making backups you should remove security. there is a way around it.. youll have to search for it. or, clean flash your rom again.

Thanks. After I restored the backup I removed /data/system/locksettings.db and was able to login again.

TWRP Restore

So I went to restore a previous ROM and the phone when I go to login is asking for my PIN (as usual). My previous PIN however isn't working. What do I need to do in the future before I make a backup so this doesn't happen again? Thanks.
EDIT: My guess is the data partition being encrypted is causing a problem...it's not a big deal if I don't recover this one but for the future so I know what went wrong?

You'd probably have to format storage in TWRP. Then flash a rom that supports having no encryption
I'm not sure if formatting the restoring a backup with encryption will work, though.

Nosferatu. said:
So I went to restore a previous ROM and the phone when I go to login is asking for my PIN (as usual). My previous PIN however isn't working. What do I need to do in the future before I make a backup so this doesn't happen again? Thanks.
EDIT: My guess is the data partition being encrypted is causing a problem...it's not a big deal if I don't recover this one but for the future so I know what went wrong?
Click to expand...
Click to collapse
boot back into twrp recovery- advanced - file manager-data-system-delete the files with the name locksettings.adb and 2 or 3more with locksettings file name

Appreciate it guys!

just data/system/lockscreen.db needs to be deleted. :good:

Replacement phone via Uh-Oh, Can I use NANDROID backup?

I managed to somehow break my 3 week old HTC 10's rear camera glass so I'm going to get it replaced via the "Uh-Oh Protection" since I bought from HTC directly.
I have the Unlocked US edition, but use it on Verizon. When I get my replacement phone, I'll go through the steps to Unlock via HTC dev, run Sunshine for S-OFF and change the CID/MID to Verizon. At that point, can I just flash a NANDROID backup from my old device onto the new one to get my ROM / Apps / etc. back? Will there be any issues since it'll be different hardware? The NANDROID will contain everything I need so I won't need to first apply the VZW RUU right? I think I've done it before on previous HTC hardware but I want to check if it'll work before I try it. Will encryption be an issue?

Sounds good as long as correct firmware is also flashed

drumz0rz said:
I managed to somehow break my 3 week old HTC 10's rear camera glass so I'm going to get it replaced via the "Uh-Oh Protection" since I bought from HTC directly.
I have the Unlocked US edition, but use it on Verizon. When I get my replacement phone, I'll go through the steps to Unlock via HTC dev, run Sunshine for S-OFF and change the CID/MID to Verizon. At that point, can I just flash a NANDROID backup from my old device onto the new one to get my ROM / Apps / etc. back? Will there be any issues since it'll be different hardware? The NANDROID will contain everything I need so I won't need to first apply the VZW RUU right? I think I've done it before on previous HTC hardware but I want to check if it'll work before I try it. Will encryption be an issue?
Click to expand...
Click to collapse
I don't see it being any issue.

So I just got my replacement phone. I followed the exact same steps as I did on my original HTC 10 to get s-off and convert to Verizon (used the same files as well). I made a fresh NANADROID backup on the old phone in TWRP, copied it over to the new phone, and restored it. When I reboot I get stuck on the white splash screen. I tried wiping the cache but I can't progress further.
I was really hoping I'd just be able to use the NANDROID so I don't have to go through the arduous process of backing up all of my apps and settings, and copying them over in TiBu, and having to recustomize everything in VenomHub/Xposed.
What am I doing wrong?

drumz0rz said:
So I just got my replacement phone. I followed the exact same steps as I did on my original HTC 10 to get s-off and convert to Verizon (used the same files as well). I made a fresh NANADROID backup on the old phone in TWRP, copied it over to the new phone, and restored it. When I reboot I get stuck on the white splash screen. I tried wiping the cache but I can't progress further.
I was really hoping I'd just be able to use the NANDROID so I don't have to go through the arduous process of backing up all of my apps and settings, and copying them over in TiBu, and having to recustomize everything in VenomHub/Xposed.
What am I doing wrong?
Click to expand...
Click to collapse
Try dirty flashing ROM

How would changing devices between TWRP backup/restore affect encryption?
EDIT: Since TWRP decrypts now, phone encryption would be a moot point in this context.

I received a replacement Uh-Oh phone from HTC. Unlocked bootloader, installed TWRP and S-Offed. Tried using my Nandroid to restore but TWRP would not see it (file names different, based on S/N). I created a small new backup to create the proper file structure and renamed the old Nandroid backup and placed it in the proper directory. Still would not work so I went to my TiBu backup and reset everything back up.
Here's a strange result though - my fingerprint works fine to unlock the phone but somewhere along the line (perhaps my attempt restoring Nandroid) the pattern lock changed. So now I cannot unlock phone using the pattern and cannot change it. I can use fingerprint so it works for now but I would like to reset the pattern lock - any ideas?

stebaile said:
I received a replacement Uh-Oh phone from HTC. Unlocked bootloader, installed TWRP and S-Offed. Tried using my Nandroid to restore but TWRP would not see it (file names different, based on S/N). I created a small new backup to create the proper file structure and renamed the old Nandroid backup and placed it in the proper directory. Still would not work so I went to my TiBu backup and reset everything back up.
Here's a strange result though - my fingerprint works fine to unlock the phone but somewhere along the line (perhaps my attempt restoring Nandroid) the pattern lock changed. So now I cannot unlock phone using the pattern and cannot change it. I can use fingerprint so it works for now but I would like to reset the pattern lock - any ideas?
Click to expand...
Click to collapse
So when you did a restore with TWRP, what was the result? What does "still would not work" mean exactly? What did the log say?

I'll have to dig into the log file but it is my habit to only backup /data. That's what I was trying to restore. I might need to factory reset to get the pin reset I suppose. Was hoping there was a file I could delete to reset the encryption.
Sent from my HTC 10 using XDA-Developers mobile app

Just in case anyone has this issue of losing their pattern lock from a Nandroid restore I found the answer in a different thread. Use a file manager with root access such as Root Explorer, or use TWRP's file manager capability to delete the locksettings.* files in /data/system. Reboot and your device will no longer have a pattern lock. You will need to create a new pattern lock along with new fingerprint unlocks.

stebaile said:
might need to factory reset to get the pin reset I suppose. Was hoping there was a file I could delete to reset the encryption.
Click to expand...
Click to collapse
Factory reset erases everything, leaving nothing to decrypt.
Your idea of "reset encryption" would make encryption useless if anyone could just remove the lock without the PIN/password.

stebaile said:
Just in case anyone has this issue of losing their pattern lock from a Nandroid restore I found the answer in a different thread. Use a file manager with root access such as Root Explorer, or use TWRP's file manager capability to delete the locksettings.* files in /data/system. Reboot and your device will no longer have a pattern lock. You will need to create a new pattern lock along with new fingerprint unlocks.
Click to expand...
Click to collapse
Rolo42 said:
Factory reset erases everything, leaving nothing to decrypt.
Your idea of "reset encryption" would make encryption useless if anyone could just remove the lock without the PIN/password.
Click to expand...
Click to collapse
Next time just read the TWRP FAQ
http://forum.xda-developers.com/htc-10/development/recovery-twrp-touch-recovery-t3358139/page74
10. After I restored my Data backup and boot back to Android, I'm entering the correct PIN/password, but it's telling me the password is wrong. What happened, and how do I fix it?
It appears that sometimes after restoring a backup of Data where security was enabled (such as a PIN or password lock), the device does not recognize the correct password. There are two ways to avoid this issue:
Disable security in Android?*before?*making a backup of data.
After restoring Data, while still in TWRP, use the TWRP File Manager to navigate to /data/system and delete all the locksettings.* files (such as locksettings.db, etc). When you reboot, the password will be gone.
Click to expand...
Click to collapse

Maik268 said:
Next time just read the TWRP FAQ
http://forum.xda-developers.com/htc-10/development/recovery-twrp-touch-recovery-t3358139/page74
Click to expand...
Click to collapse
Is that referring to unlocking the screen or decrypting the device?
The question was referring to encryption.
When TWRP restores a backup, is it encrypted? (There's a few "it depends" to that question I would think.)

Cannot get unlock pattern to work.... please read

Hi..
I updated to Android N, and everything went fine, but I found it a little buggy and (my mistake) didn't realize xposed was not working yet, and there are some privacy modules I really would like.... So, I decided to downgrade back to MM.
As I am s-off, I booted into a rom.zip RUU (1.96.617.20). During the subsequent initial setup, I picked a screen pattern (to be used on restarts only)..for whatever reason, I decided to pick something different besides the rather easy pattern I had used since the M8... I will call this pattern B. Also during setup I copied over my internal storage files which I had backed up my laptop.
I then flashed the correct TWRP and then installed the correct SuperSU.zip. When I rebooted from here, Pattern B worked fine as I expected it to. I then thought I it would save time by restoring a nandroid (also 1.96.617.20) which had a lot of tweaks and other things. That nandroid backup however I know used my old screen pattern, which I will call Pattern A. That restore finished without error.
After reboot I got the restart screen asking for the pattern... I wasn't sure which one would work, so I first tried Pattern A which would have been used in the nandroid restore I just finished.... no luck. So I thought ok, I will try the pattern I used when I set up MM, Pattern B. But that didn't work...
This makes no sense... I have never used a screen unlock pattern other than Pattern A, and then today, I tried Pattern B which I know I remembered correctly because I used it once before I restored the nandroid.
When I search on how to solve this problem, I see "do a reset"... but wouldn't a reset be the same as restoring a nandroid backup? And since I just restored a nandroid and the pattern doesn't work, I am stumped.
Anyone have any clue how I can fix this???
Thanks in advance!

syntropic said:
Anyone have any clue how I can fix this???
Thanks in advance!
Click to expand...
Click to collapse
I found in the Nexus Forum someone with this problem... I rebooted into TWRP, and using the file manager I deleted these files:
/data/system/locksettings.db
/data/system/*.key
And this allowed me into the OS.
Thank you for anyone who has read this anyway!!

syntropic said:
I found in the Nexus Forum someone with this problem... I rebooted into TWRP, and using the file manager I deleted these files:
/data/system/locksettings.db
/data/system/*.key
And this allowed me into the OS.
Thank you for anyone who has read this anyway!!
Click to expand...
Click to collapse
A hint: You are talking about twrp, sill you are searching a nexus forum. Next time try twrp htc 10 thread instead

mirok said:
A hint: You are talking about twrp, sill you are searching a nexus forum. Next time try twrp htc 10 thread instead
Click to expand...
Click to collapse
I just googled "site:sea-developers.com pattern security not working HTC 10"
This wasn't strictly a TWRP issue... You could use TWRP or ADB to access the system partition IF the files which stored this security code were stored there (of this I wasn't entirely sure).
I didn't know for certain if these files were located in the same place or even under the same name as the Nexus, so I used TWRP's file manager to look around (starting in the above location) aa maybe I'd find them.
Sent from my HTC 10 using XDA Labs

TWRP nandroid of stock changes security lock. (solved!)

Phone came to me as 6.0.1 .
I OTA'ed up to 7.1.1 Nov1 .
I unlocked bootloader and flashed Alberto's TWRP.
I backed it up and couldn't restore it and thus learned about verity patch.
I didn't realize that all I had to do was restore a backup, flash verity, and boot and it probably would have been fine.
So:
I RSD lite'ed it to the exact same place, flashed the verity patch and all was fine.
Restore's fine.
Okay so I added a bunch of apps and a pattern lock.
Went off to flash some other stuff, came back, wiped all 4, restored stock and pattern lock wouldn't work.
Time passes. This time I had set up 2 things: face lock and a pin.
Yup, you get the picture - neither will work.
Anybody else get this?
My only recourse is never to have any locks on a stock ROM when I back it up.
Much time wasted.
Any ideas?

KrisM22 said:
Phone came to me as 6.0.1 .
I OTA'ed up to 7.1.1 Nov1 .
I unlocked bootloader and flashed Alberto's TWRP.
I backed it up and couldn't restore it and thus learned about verity patch.
I didn't realize that all I had to do was restore a backup, flash verity, and boot and it probably would have been fine.
So:
I RSD lite'ed it to the exact same place, flashed the verity patch and all was fine.
Restore's fine.
Okay so I added a bunch of apps and a pattern lock.
Went off to flash some other stuff, came back, wiped all 4, restored stock and pattern lock wouldn't work.
Time passes. This time I had set up 2 things: face lock and a pin.
Yup, you get the picture - neither will work.
Anybody else get this?
My only recourse is never to have any locks on a stock ROM when I back it up.
Much time wasted.
Any ideas?
Click to expand...
Click to collapse
If you are wondering that when you restore your nandroid backup it then doesn't accept your pin/password? If this is the issue, here is the fix!
1. Boot into TWRP.
2. Go to Advanced Tab and select File Manager.
3. Now go to /data/system
4. Delete all these files (don't worry if any one of them don't exist just delete whichever you can find)
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
5. Reboot.
Now you won't be asked for any Pin/Pattern/Password. You can set a new lock ( like a new beginning) when your rom boots up. FYI completely safe, no data will be lost.

AmulyaX said:
If you are wondering that when you restore your nandroid backup it then doesn't accept your pin/password? If this is the issue, here is the fix!
1. Boot into TWRP.
2. Go to Advanced Tab and select File Manager.
3. Now go to /data/system
4. Delete all these files (don't worry if any one of them don't exist just delete whichever you can find)
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
5. Reboot.
Now you won't be asked for any Pin/Pattern/Password. You can set a new lock ( like a new beginning) when your rom boots up. FYI completely safe, no data will be lost.
Click to expand...
Click to collapse
Hey, THANKS!!! - tested by setting a pattern, boot to TWRP and removed the 3 locksettings and voila!!! THANKS!!!

KrisM22 said:
Hey, THANKS!!! - tested by setting a pattern, boot to TWRP and removed the 3 locksettings and voila!!! THANKS!!!
Click to expand...
Click to collapse
No problem.

I believe this is an anomaly of TWRP 3.2.1-0. Doesn't happen with 3.2.0-0