Little help here please... So when i did a back up i couldn't enter my phone because the fingerprint and password didn't work!!!
I googled around and managed to get back in (thank god) by deleting these files in TWRP...
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
But now obviously the fingerprint thing doesn't work anymore... Is there any way to make this security work again?
Delete only locksettings.db
Use a new password
Now you can delete the fingerprints.
Use new fingerprints
Enjoy!
Thnx for the reply, but i already deleted all those files above, so i can't configure or delete the fingerprints i already have on the phone.. I can only use the pattern as security
I Just deleted password.key and then I could set a New PIN, using it I deleted the fingerprints
Oh wow.. Needed a new pin indeed and then it worked again.
Which comes with the next issue.. I deleted the previous prints because they didn't work anymore.. But i can't use the same fingers because it already exists. Now what?
How do you mean? I could just add them as new fingers after deleting the old one ?
Hi, I had same issue backup with TWRP, restored the backup and the pattern screen lock didn't work.
I ended up reflashed and rom and restore/install again apps from apk backup on the phone.
So now I clear all password before do TWRP system backup.
Ok, just to be sure.. Can i reflash it with Flashify? And do i need to wipe all 3, cache/dalvik/data? I have made a backup of my system and all my apps..
Just like that?
MaddyS said:
Ok, just to be sure.. Can i reflash it with Flashify? And do i need to wipe all 3, cache/dalvik/data? I have made a backup of my system and all my apps..
Just like that?
Click to expand...
Click to collapse
Disable all security on your phone...No password fingerprint etc. Just flash ROM over without wiping anything. You'll be good to go. Or you can restore your backup and delete the files someone else suggested.
Awesome.. That worked, much appreciated!
Related
so i accidentally deleted my stock phone and/or contacts app.
does anyone have an .apk or knows where i can dl it?
or any other solution for the problem.
thanks.
If you used Root Explorer, you have trouble. Probably the best solution is to re-flash stock ROM with SEUS. You might also try using .sin files decryption from flashtool files, but it's a little difficult.
i used the wrong expression, i didn't delete them, i just uninstalled them. according to what you thought, i guess the .apks still exist on my phone. but i don't know where. :/
or don't they?
Check in system/app using Root Explorer. If you won't find them, they're probably deleted and hard to restore.
What ROM do you use? If it's cooked ROM, you can get the .apk simply by unziping the ROM archive, you've downloaded in system/app.
I have found the .apks.
I have installed them but nothing. I tried deleting the data and reinstalling but nothing. I believe they would show up in menu if i deleted them completely and installed them again. But in the app manager i can only stop the process and wipe the data, i can't uninstall..
I have uninstalled them with another app, fast uninstaller for root.
Flash the ROM´s update.zip again.
or restore a backup of the same ROM with advanced restore, so that you only restore /system.
wow, that's clever. i flashed the whole ROM, never thought of only restoring the /system. :/
but it's solved.
I just replaced my phone after I cracked the screen I was stock rooted and had done a nandroid backup prior to running Odin to get the broken phone back to stock. I had a hard time getting safestrap installed and working on the new phone. Finally after several attempts, I got it up and running but there were no backupslisted under recovery. I checked in ES file explorer and they were still on the SD card where they were supposed to be in the TWRP directory. I figured that was possibly a folder issue so I tried creating a nandroid backup of the new phone and it made a new folder in the TWRP/Backups directory. So I copied my newest nandroid I created from the old phone into the new directory. It worked. It came up when I went to recovery in safestrap. I did the recovery of it and when the phone started up, it came to the lockscreen I have always used so I tried entering my pin. I got an "incorrect pin" message. I absolutely know that I used the right pin. I tried every pin I could think of that I though might work and nothing would unlock the phone. After doing some research, I found that if I get back into safestrap, I could use the file manager to get into /data/system and either delete or rename the gesture.key file along with all 3 of the the locksettings files. Once I restarted the phone, I only had to swipe to get it open. At least I was in. I then went back into settings and then into lockscreen, selected screen lock and clicked on PIN. A full keyboard came up which had never happened on the old phone. I again set the PIN that I have always used and restarted the phone. The lock screen came up after rebooting and again, my PIN did not work. I had to go back into safestrap's file manager and those 4 files had been recreated. I renamed them again and was able to get back into the phone.
I don't like not being able to lock the phone. Does anyone have any suggestions on how to fix this?
Somehow I was able to fix this. i don't quite remember all the steps but I got it done. I had originally just renamed gesture.key extensions to and all the locksettings files in /data/system to .bak or .old. When trying to add a PIN under sttings/lockscreen and checking the locksettings.db through sq lite editor that would be created , it would only have 5 entries under locksettings. I would then get the incorrect PIN message upon rebooting and have to go back to safestrap and rename those files. After rebooting this last time I went and deleted the gesture.key and all 3 locksettings files. I then went and selected the password option. I created a password and upon rebooting, IT WORKED!!!! I then checked the locksettings.db in sqlite and found that there were several more entries for it. I then went and changed the lockscreen from password to my regular PIN. I rebooted the phone and this time the PIN worked!!! I don't know why but I am happy agan.
mikeyk101 said:
Somehow I was able to fix this. i don't quite remember all the steps but I got it done. I had originally just renamed gesture.key extensions to and all the locksettings files in /data/system to .bak or .old. When trying to add a PIN under sttings/lockscreen and checking the locksettings.db through sq lite editor that would be created , it would only have 5 entries under locksettings. I would then get the incorrect PIN message upon rebooting and have to go back to safestrap and rename those files. After rebooting this last time I went and deleted the gesture.key and all 3 locksettings files. I then went and selected the password option. I created a password and upon rebooting, IT WORKED!!!! I then checked the locksettings.db in sqlite and found that there were several more entries for it. I then went and changed the lockscreen from password to my regular PIN. I rebooted the phone and this time the PIN worked!!! I don't know why but I am happy agan.
Click to expand...
Click to collapse
I know this is old, but thank you! You saved me from having to reinstall all my apps after getting my phone back from Samsung with a new motherboard (essentially new phone).
Hi there,
I am using the simple swipe unlock method, but often that also unlocks your phone in your pocket. When it did unlock it did something and now I cannot change my screen lock type, when I open settings>lock screen>screenlock it asks for 'Confirm PIN', while I never set a PIN. I tried all the ones I would possibly have set somewhere, but it doesn't work. I read somewhere that there are other people unable to change their lock type, and the solution would be to clear credentials, however, that option is greyed out.
I deactivated and activated device administrators, I cannot encrypt and decrypt my phone, as some people suggest, because it then also asks for a PIN.
Does someone know how to tackle this problem without a factory reset?
I have a SM-G900F with android 6.0.1
Thanks!
Do you have root?
shahram Ali said:
Do you have root?
Click to expand...
Click to collapse
No, I do not.
Jeebos said:
No, I do not.
Click to expand...
Click to collapse
Dude root it and it will be fixed easily by deleting some files but warranty will be void
shahram Ali said:
Dude root it and it will be fixed easily by deleting some files but warranty will be void
Click to expand...
Click to collapse
which files ?
Ven99 said:
which files ?
Click to expand...
Click to collapse
Use es file explorer as root go to data/system u see some files called
gatekeeper.password.key
gatekeeper.pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
personalpin.key
Delete them and go set new pin if it asked again for pin use 1234 or random number thats all
shahram Ali said:
Use es file explorer as root go to data/system u see some files called
gatekeeper.password.key
gatekeeper.pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
personalpin.key
Delete them and go set new pin if it asked again for pin use 1234 or random number thats all
Click to expand...
Click to collapse
Thank you for the info but it didn't work me.
Can you help me with another but similar issue please ?
I have TWRP Nandroid BACKUP zipped files downloaded from internet.
I open with 7zip and try to delete some files but can not as 7zip says : Read Only.
I have Debian as well on my computer. I transferred the zipped file there to change permissions. I did this successfully but somehow I can not open zipped file in Debian at all. There are 2 applications on Debian to open zipped file, both of them show and empty window, look like nothing inside.
How can I pass the Read-Only problem ?
So my every time I restore my TWRP backup of stock and restart it tells me my pin is wrong. Any idea what's happening here?
Reboot to TWRP, go to advanced and then file manager, navigate to data/system and delete these:
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
Priezti said:
Reboot to TWRP, go to advanced and then file manager, navigate to data/system and delete these:
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
Click to expand...
Click to collapse
Thank you. Also for whatever reason my backup when I managed to get into it by deleting data......the quick setting tiles are a weird shade of white and Black/grey and are makinh it hard to read like the battery settings and what not no idea why that is wasn't like that when i made the backup. Somehow somewhere substratum like stick to it and won't change on the stock ROM lol. This phone is weird.
Can't say 100% but possibly is substratum, have you disabled all themes?
Yes I have. I don't even have it installed right now on stock. It's somehow lingering from other roms even after clean wipes and only effecting the quick tiles lol. Weird.
I use LineageOS rom which I update monthly when release and tried to restore my TWRP data backup which completes with no errors. When I reboot it goes to the login screen where it ask for my pattern but rejects it. Tried 3 times but no joy.
Do I also need to backup my boot as well as data?
Thanks sammiev
sammiev said:
I use LineageOS rom which I update monthly when release and tried to restore my TWRP data backup which completes with no errors. When I reboot it goes to the login screen where it ask for my pattern but rejects it. Tried 3 times but no joy.
Do I also need to backup my boot as well as data?
Thanks sammiev
Click to expand...
Click to collapse
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find):
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
burningcreation said:
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find):
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Click to expand...
Click to collapse
Will give that a try.
Thanks for your help and time.
burningcreation said:
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find):
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Click to expand...
Click to collapse
Worked perfect!
Only had to remove: locksettings.db
Many Thanks again.
sammiev said:
Worked perfect!
Only had to remove: locksettings.db
Many Thanks again.
Click to expand...
Click to collapse
I'm glad I could help.
Just remember to set your pattern again.
burningcreation said:
I'm glad I could help.
Just remember to set your pattern again.
Click to expand...
Click to collapse
It was the first thing I did.