Hello xda community,
I've been having a problem with my OP3, I really like to flash a new rom quite regularly, like most people here, so Nandroid backups are awesome. However, for a while now I've been trying to switch between backups, but whenever they are done betting they ask me for my passcode, but it's always wrong no matter what I put in. Is there a way to fix this? I already tried wiping NY whole phone even /data so it was completely empty. I also turned off the option to retire the passcode before the boot finishes.
I would really appreciate any suggestions.
If it's the encryption pin, I'm not too sure what to tell you. However, if it's just the lock screen pin, after you restore, you go into the two file explorer and delete a few files from /data/system. Two of them are gatekeeper.password.key and gatekeeper.pattern.key and the other three are locksettings.db, locksettings.db-shm, and locksettings.db-wal. Then you can reboot after. Keep note that you'll need to go back into your security settings once the ROM boots and reactivate your preferred unlock method, the fingerprint data will not be touched however
Just DO NOT set a pin code or any security lock before doing Nandroid back up
Wow thanks for the quick answers. Now I've got both grounds covered thanks so much. I actually can't believe that I didn't think to disable the picture code before making a Nandroid. I guess it's because I never used a pin code on any of my previous phones before the OP3 as they had no fingerprintscanner.
Related
Hey All!
I've been browsing the XDA scene for a while after getting my new E4GT back in November, and until now haven't had any sort of problem flashing roms, themes, mods, and the like.
I had flashed the phone back to stock EL29 in order to have a chance to return the phone to my carrier for some USB issues I'm having...
But earlier today, I put a pin code on my phone in order to secure it when being put into a shared locker at my work, and I promptly forgot it. Now here's my problem:
I can't access the phone. I've tried every combination of every pin I think of that I would have used. Now, I wouldn't have thought this would be an issue, being able to hard reset the phone.
Well, it won't let me do any sort of factory reset to the phone without inputting the forgotten pin...
Read online that after 5 failed entries, Android asks for other security info to override pin codes. 50 failed attempts later, no prompts.
Ok no problem, I'll Odin EL29 using the rooted one-click method to put stock back onto the phone. (No Go... requires PIN to even boot system)
Ok I'll flash CWM5 (was able to get in and flash a rom that was on my SD card)
Success! I have a bootable OS now, and can change security.
Go to re-activate PIN security, type in new security code, it accepts it. Lock the Phone, put in the -new-code (that was just made), and it's incorrect.
Reboot CWM5, Wipe Data, Cache, etc. and reboot. Able to access phone again.
Go to try a password based security using a simple password. Lock the phone, put in the new password, and again it's incorrect.
Basically, no matter what I do, if I put a pin or password, it defaults to that forgotten pin code and locks me out of my phone.
Now my question to everyone is this:
Is there a way to wipe the boot-loader security, so it wont override the new settings, so that i can use my own passwords again?
(As a side note, pattern unlocks work)
I think if you had held the power button down, the phone should have rebooted no matter what. A battery pull of course would have too.
Did you do a format all then you reinstalled the rom? You should still do the one-click and reinstall the rom now that the phone is back up to see if the problem still persists.
try last 4 digits of your phone # or 0000.
SilverDFlame said:
Hey All!
I've been browsing the XDA scene for a while after getting my new E4GT back in November, and until now haven't had any sort of problem flashing roms, themes, mods, and the like.
I had flashed the phone back to stock EL29 in order to have a chance to return the phone to my carrier for some USB issues I'm having...
But earlier today, I put a pin code on my phone in order to secure it when being put into a shared locker at my work, and I promptly forgot it. Now here's my problem:
I can't access the phone. I've tried every combination of every pin I think of that I would have used. Now, I wouldn't have thought this would be an issue, being able to hard reset the phone.
Well, it won't let me do any sort of factory reset to the phone without inputting the forgotten pin...
Read online that after 5 failed entries, Android asks for other security info to override pin codes. 50 failed attempts later, no prompts.
Ok no problem, I'll Odin EL29 using the rooted one-click method to put stock back onto the phone. (No Go... requires PIN to even boot system)
Ok I'll flash CWM5 (was able to get in and flash a rom that was on my SD card)
Success! I have a bootable OS now, and can change security.
Go to re-activate PIN security, type in new security code, it accepts it. Lock the Phone, put in the -new-code (that was just made), and it's incorrect.
Reboot CWM5, Wipe Data, Cache, etc. and reboot. Able to access phone again.
Go to try a password based security using a simple password. Lock the phone, put in the new password, and again it's incorrect.
Basically, no matter what I do, if I put a pin or password, it defaults to that forgotten pin code and locks me out of my phone.
Now my question to everyone is this:
Is there a way to wipe the boot-loader security, so it wont override the new settings, so that i can use my own passwords again?
(As a side note, pattern unlocks work)
Click to expand...
Click to collapse
Excuse me if I missed something because I skimmed through your paragraph but I had the same problem with this phone and I followed sfhubs directions to the tee for restoring a phone with a pin code and it worked flawlessly.
http://forum.xda-developers.com/showthread.php?t=1433101
Note #1: Please DISABLE any PIN code you may have created to protect your phone. As a security measure, after the flash, Android will ask you for your PIN, if you have one enabled. It is simpler to have no PIN active. If you forgot your PIN then, after the factory restore, just enter the wrong PIN a few times and it will warn you. Enter the wrong PIN again and it will reset the filesystem.
Click to expand...
Click to collapse
^^^that gets done right after you odin it back to stock or restore it in his words
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.)
Hi guys, first, sry for my bad english.
I have a huge Problem. I did a Twrp Backup from my Viper rom. After Backing up, i installed cm13. After that, i would go back to my backup from Viper. The Problem is, i can restore the Backup but ive got a bootloop. How can i go back to my Backup ?
Next Problem is, everytime i start into twrp i got asked for the Decrypt password. How can i deactivate that ?
Which TWRP version are you currently on? Sounds asbif it is an older one. If so, try the latest 3.0.2-6 and report back.
Sent from my htc_pmeuhl using XDA Labs
hi, im on 3.0.2-6.
Now i restored my Viper backup. It Boots normaly.
Then i have type my Pin, that works. But after that, i have to unlock the Pattern lock. But it says my Code is Wrong.
I know it is the right code. I can try 1000000 different times, i cant unlock
pboden83 said:
hi, im on 3.0.2-6.
Now i restored my Viper backup. It Boots normaly.
Then i have type my Pin, that works. But after that, i have to unlock the Pattern lock. But it says my Code is Wrong.
I know it is the right code. I can try 1000000 different times, i cant unlock
Click to expand...
Click to collapse
directly from twrp FAQ:
"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."
pboden83 said:
hi, im on 3.0.2-6.
Now i restored my Viper backup. It Boots normaly.
Then i have type my Pin, that works. But after that, i have to unlock the Pattern lock. But it says my Code is Wrong.
I know it is the right code. I can try 1000000 different times, i cant unlock
Click to expand...
Click to collapse
adb into the phone via TWRP or live system and rm -rf /system/data/*.key and locksettings* this will reset the security. no one currently knows why twrp is doing this but it seems to only happen to me when flashing a different rom then going back. it does NOT does this if restoring a previous backup of my current rom.
really the only file you need to delete is the locksettings.db file. I've never had issues deleting just that one.
I also tried this way to delete the locksetting.db and can bypass the suck lockscreen!
BTW, highly recommend you that in addition to whole system backup in TWRP, also use Titanium Backup to backup all user apps. In case of restore failure, you still can preserve your user apps and restore in newly installed system.
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
Ok I'm on the VZW variant of the pixel XL. I have the guy Smiley or whatever his name is unlock my phone bootloader and I rooted it. As we all know when the bootloader is unlocked it wipes your phone completely clean so on first boot it's like starting the phone up right out of the box. I did not set up a pin or fingerprint or Smart Lock or anyting of the nature due to I figured I was going to be flashing or ROM or multiple ROMs soon. And everything I have read about TWRP says that you have to turn off your screen lock before you flash TWR P or a ROM so and so forth.
So my question is when I now have decided to stick with a stock ROM and just use substratum to theme it when I go in and try to setup my fingerprint for the lock screen it asked me to reenter my PIN. Keyword here being "re-enter". I'll have it no point in time created a lock screen pin or pain in TW RP or anywhere for me to have to re-enter it. I know what two or three pins would be that I normally use I have tried those and they do not work. I have tried one two three four I have tried one one one one I have tried 4 3 2 1 and I have tried 0-0-0-0. For the life of me I cannot figure out what the pan Maybe is there a default pin but furthermore why has it created a pin without my knowledge of it or authorization of it?
Any insight into my predicament would be greatly appreciated. As well as any ideas on how I can get rid of this would be greatly appreciated....
And I assumed that I could fastboot flash stock image and wipe the phone completely just like the bootloader being unlocked would. But I'm trying not to lose all my data and have to start fresh setting everything up again.
There is no default pin. Only pin is the pin that was created by the user. Ask that "Smiley or whatever his name" what he did to your phone.
mattwheat said:
Ok I'm on the VZW variant of the pixel XL. I have the guy Smiley or whatever his name is unlock my phone bootloader and I rooted it. As we all know when the bootloader is unlocked it wipes your phone completely clean so on first boot it's like starting the phone up right out of the box. I did not set up a pin or fingerprint or Smart Lock or anyting of the nature due to I figured I was going to be flashing or ROM or multiple ROMs soon. And everything I have read about TWRP says that you have to turn off your screen lock before you flash TWR P or a ROM so and so forth.
So my question is when I now have decided to stick with a stock ROM and just use substratum to theme it when I go in and try to setup my fingerprint for the lock screen it asked me to reenter my PIN. Keyword here being "re-enter". I'll have it no point in time created a lock screen pin or pain in TW RP or anywhere for me to have to re-enter it. I know what two or three pins would be that I normally use I have tried those and they do not work. I have tried one two three four I have tried one one one one I have tried 4 3 2 1 and I have tried 0-0-0-0. For the life of me I cannot figure out what the pan Maybe is there a default pin but furthermore why has it created a pin without my knowledge of it or authorization of it?
Any insight into my predicament would be greatly appreciated. As well as any ideas on how I can get rid of this would be greatly appreciated....
And I assumed that I could fastboot flash stock image and wipe the phone completely just like the bootloader being unlocked would. But I'm trying not to lose all my data and have to start fresh setting everything up again.
Click to expand...
Click to collapse
Just reset the phone, it's the most simple thing to do and you won't risk breaking something by trying to figure it out.
Yeah yeah you're right. It's just odd though. I can use my phone just fine. Just can't set up a lockscreen. Didn't know if it had to do with anything in regards to the TWRP /pin issues. And hoping it may be a known issue that I just happen to miss in their forums. You know to make life easier if there was an easier , no data loss, fix.
Maybe this will help you.