Screen lock was already change, try again with a new screenlock. HELP - General Questions and Answers

So after upgrading the android version of my phone and installing twrp after flashing new update android version of my rom.
I cannot use the Patter, PIN, Password screen lock type on my samsung a11 phone. After doing some research i noticed that my data/system does not have 2 gatekeeper.key files only the 3 lockscreen db. I also deleted the 3 lockscreen db files hoping it would work and i can get my screen lock types working againt but nothings change. Im only able to use swipe and none as a lock screen.
Is there anyway to get the 2 gatekeeper files in data/system back? because i dont have them before i deleted the 3 lockscreen db files.

Related

HELP!!! my nexus s I9023 is locked by the ROM XenonHD

I have installed the XenonHD few weeks ago so i am not using the most updated version.
http://forum.xda-developers.com/show....php?t=1667442
today when i am using the phone as normal, it suddenly rebooted.
when it is started, it didnt show any launcher screen or wallpaper but it required me a password to start up the phone.
It shows " Type password to decrypt storage".
As i remember there is a button for activating the encrypt storage function in the system setting/ rom setting.
I am 100% sure that i didnt press it. This function is activated somehow after the sudden reboot......
Is there a way to get the password or extract the data from the phone before i flashing a new rom.....
maybe you should try wiping dalvik cache, or just randomly try to unlock, eventually it should ask you what your google account is, and you should be able to unlock. or else you have to do this: make a nandroid backup, then, flash a new rom, use titanium backup to extract the apps and their data from the nandroid. hope this helps.

[Q] CM 10.1 Forgot to disable lock pattern!

I am at a total loss right now. I feel like I'm in Android Hell. I flashed the nightly CM 10.1 12/27 to my i535 through the CM Updater (from what I'm reading that was mistake #1), and I also had a 4x4 pattern in CM 10.0 Stable that was not disabled before flashing (mistake #2, the BIG mistake). I have an older CWM Touch that I can't restore a nandroid with, the only newer recoveries I can find are .img files so I can't flash them with Odin, and I can't seem to get a "Forgot Pattern?" button to come up on the lock screen. I'd really like to avoid a factory reset. Please help!
EDIT: Forgot to mention I've tried to disable the lock pattern with adb, but for some reason it is unable to open settings.db, so it doesn't work. SQLite3 is in the same folder as adb.
TweeterMan said:
I am at a total loss right now. I feel like I'm in Android Hell. I flashed the nightly CM 10.1 12/27 to my i535 through the CM Updater (from what I'm reading that was mistake #1), and I also had a 4x4 pattern in CM 10.0 Stable that was not disabled before flashing (mistake #2, the BIG mistake). I have an older CWM Touch that I can't restore a nandroid with, the only newer recoveries I can find are .img files so I can't flash them with Odin, and I can't seem to get a "Forgot Pattern?" button to come up on the lock screen. I'd really like to avoid a factory reset. Please help!
EDIT: Forgot to mention I've tried to disable the lock pattern with adb, but for some reason it is unable to open settings.db, so it doesn't work. SQLite3 is in the same folder as adb.
Click to expand...
Click to collapse
The lock pattern problem is a known issue when upgrading to CM 10.1, see this post: http://forum.xda-developers.com/showthread.php?t=2053799. It is also not recommended to use the CM Updated to go to 10.1 because you need to flash the JB 4.2 GApps.
Why can't you restore a nandroid? Are you just not seeing them because of the 10.1 file structure change? I believe that link also talks about this issue.
There was a post in the portal a while back about using ADB to disable the lock screen. I'd look for it if I wasn't on mobile right now, but five that a search to see if you can disable it.
Sent from my Nexus 4 using xda premium
Trying a few different things still. The nandroid I want is still there, it's just in the new "0" folder. Clockworkmod Touch can't find the "clockworkmod" folder if I put it in the root, so I'm in the middle of moving it to the SD card and I will try reinstalling from that.
No worries. Hang onto the CWM backup, do a factory restore, and using the Titanium Backup App (Pro Key needed I think), select extract from Nandroid backup. Titanium Backup will read the .img files and extract and install the apps of your choosing. Very helpful feature.

"Fingerprint hardware not available"

After successfully restoring backup on the new phone the fingerprint doesn't work.
Details about restore process are here: https://forum.xda-developers.com/pixel-3a/development/twrp-3-3-1-pixel-3a-t3943413/page10
Before TWRP backup I did set two fingerprints. After restoring on new phone if I try unlock screen with fingerprint I'm getting message "Fingerprint hardware not available"
I can unlock screen using PIN but I can't add new fingerprint nor delete two existing.
When I delete one fingerprint, it greyed out (screenshot attached) but when I return back to Fingerprints it's still there.
Adding new fingerprint starts fingerprint setup but right before end I'm getting message (screenshot attached):
Enrolment was not completed.
Fingerprint enrolment didn't work. Try again or use different finger
Fear not, this is not hardware issue. I went back to stock image and I can setup and use fingerprint and delete fingerprints.
So, I went back to square one and flashed stock image, boot, reboot, TWRP, flashed StatiXOS, boot. At this point checked, fingerprint is still working in StatiXOS.
Rebooted to TWRP, wipe and restore my StatiXOS backup and still having the same issue with fingerprint.
Reading some threads my guess is that fingerprint should be disabled before backup. The fingerprint info is probably saved on fingerprint chip and factory reset should fix the issue.
Turther search lead to other threads about same issue and it seems deleting some files/folders in data partition reset fingerprint settings.
Unfortunately none of them doesn't match 3a. Have no time now but will investigate further other solutions. Pixel 3 threads might have the answer.
I had exactly the same prob on AOSiP on my Pixel 3 XL. Was not able to find it out or to solve it. Back to Stock and it worked fine w/o any probs. Since some days I am on DU and also no probs so far.
gogoffm said:
I had exactly the same prob on AOSiP on my Pixel 3 XL. Was not able to find it out or to solve it. Back to Stock and it worked fine w/o any probs. Since some days I am on DU and also no probs so far.
Click to expand...
Click to collapse
Same here, gave up and flash stock again. I was trying some stuff and noticed if I create another account and switch I can enable fingerprint but only for that account. So, something is screwed up in default account settings.
The best advice I can offer is from this Pixel XL thread: https://forum.xda-developers.com/pixel-xl/how-to/slota-b-how-to-flash-roms-magisk-kernel-t3754175
MAKE SURE YOUR LOCKSCREEN IS OFF... No fingerprint set up... Not a pin set up... No pattern set up. If your more secure than swiping up to open your screen your not getting in to TWRP 3.2.0-0 decrypted.
Click to expand...
Click to collapse
Unfortunately I don't have another Pixel 3a around to test, but it make sense.
So you already tried data/system/ & change locksettings.db to locksettings.db.bak ? It should create a new locksettings.db after you go into phone settings to set up a new pin/fingerprints then go & delete locksettings.db.bak or you can leave it...either way.
SketchyStunts said:
So you already tried data/system/ & change locksettings.db to locksettings.db.bak ? It should create a new locksettings.db after you go into phone settings to set up a new pin/fingerprints then go & delete locksettings.db.bak or you can leave it...either way.
Click to expand...
Click to collapse
I have some spare time today and will try. Need to test my backup first to make sure I can go back.
Even if it work on my phone it might not work on different phone. If I'm in charge of security on Pixel 3a project I will at least compare hardware fingerprints (i.e. serial numbers, MAC address, etc) of the phone with previous data save in encrypted file in some very protected area
However, it could be useful to all dummies like me who screwed their phones.
Pogo said:
I have some spare time today and will try. Need to test my backup first to make sure I can go back.
Not much luck today. I have created two backups on rooted StatiXOS:
- one with fingerprints and PIN unlock
- one without fingerprints and swipe unlock (no protection at all)
Before running backup checked all boxes in Backup option (Boot, System, System Image, Vendor Image, Data)
Note: only Boot, Data and System Image are actually required, but just in case
After that I've tried the following:
1.
- flash factory ROM to make sure there is no traces of my settings
- perform initial setup, enable ADB debug, setup PIN and one fingerprint
- back to TWRP, wipe Dalvik/Art, System and Data
- copy my backups to TWRP as well as all other folders originally on sdcard
- go to restore and select my backup with fingerprints
- only check Boot, Data and System Image boxes
- reboot, all good so far. PIN and fingerprint works, only needed to re-enable fingerprint in apps that use it like my banking app
2.
- back to fastboot, deleted file data/system/locksettings.db
- rebooted, there is no lock or PIN, just swipe
- "Pixel is starting..." message show up on display
- launcher and apps are not available, but Settings are available from status bar
- can add new fingerprint, delete fingerprint but the message on home screen won't disappear
- gave up after 10 min of waiting
3.
- flashed factory ROM again
- perform initial setup, enable ADB debug, setup PIN and one fingerprint
- back to fastboot, delete file data/system/locksettings.db
- reboot, there is no lock or PIN, just swipe
- same as before but the message is now "Phone is starting..."
- gave up after 10 min of waiting
Need to actually USE my phone, so I stopped here and restored my trusty backup.
So, you can restore your backup with fingerprint. Judging by my experience restore is fully functional only on the physically same phone (same s/n, same MAC, etc, no hardware modifications).
Deleting data/system/locksettings.db did remove lock but still didn't make phone fully functional. However it's promising.
Click to expand...
Click to collapse
Pogo said:
Pogo said:
I have some spare time today and will try. Need to test my backup first to make sure I can go back.
Not much luck today. I have created two backups on rooted StatiXOS:
- one with fingerprints and PIN unlock
- one without fingerprints and swipe unlock (no protection at all)
Before running backup checked all boxes in Backup option (Boot, System, System Image, Vendor Image, Data)
Note: only Boot, Data and System Image are actually required, but just in case
After that I've tried the following:
1.
- flash factory ROM to make sure there is no traces of my settings
- perform initial setup, enable ADB debug, setup PIN and one fingerprint
- back to TWRP, wipe Dalvik/Art, System and Data
- copy my backups to TWRP as well as all other folders originally on sdcard
- go to restore and select my backup with fingerprints
- only check Boot, Data and System Image boxes
- reboot, all good so far. PIN and fingerprint works, only needed to re-enable fingerprint in apps that use it like my banking app
2.
- back to fastboot, deleted file data/system/locksettings.db
- rebooted, there is no lock or PIN, just swipe
- "Pixel is starting..." message show up on display
- launcher and apps are not available, but Settings are available from status bar
- can add new fingerprint, delete fingerprint but the message on home screen won't disappear
- gave up after 10 min of waiting
3.
- flashed factory ROM again
- perform initial setup, enable ADB debug, setup PIN and one fingerprint
- back to fastboot, delete file data/system/locksettings.db
- reboot, there is no lock or PIN, just swipe
- same as before but the message is now "Phone is starting..."
- gave up after 10 min of waiting
Need to actually USE my phone, so I stopped here and restored my trusty backup.
So, you can restore your backup with fingerprint. Judging by my experience restore is fully functional only on the physically same phone (same s/n, same MAC, etc, no hardware modifications).
Deleting data/system/locksettings.db did remove lock but still didn't make phone fully functional. However it's promising.
Click to expand...
Click to collapse
In the future (I've done this on the last several phones running AOSP or similar) I always change locksettings.db to locksettings.db.bak before doing a nandroid because I've had issues restoring ROMs then my PIN won't work, etc. Once I've unlocked my phone on a restore I change it back to locksettings.db
Click to expand...
Click to collapse

Force decryption for user data?

Hi!
I think I managed to get two layers of encryption on my storage let me explain :
I had a pattern+fingerprint password. While changing my screen I also had to change the fingerprint sensor which lead to interface bootloop as I forgot to remove FP before changing sensor.
I tried a TWRP method to remove password from the device, consisting in removing some system files (which I didn't backup) without success, so I reopend th phone to plug the old sensor. This allowed me to remove my fingerprints and plug back the new sensor.
Now, I think my data is encrypted but the password is not prompted AND if i set the same password as before, I still can't access the data (even in TWRP as I think the encrypted data gets encrypted again)
Is there a way in TWRP (or other) to force a first decryption as I know both passwords?
Well, I removed my password and TWRP didn't prompt any pattern, and I can access my data.
However, My user remains encrypted with a password, and I can't figure it out.
I think the easy way is to copy my data and factory reset the phone.
Another way would be to clone full system partition to try recover the deleted files I think

Help! I can't access my phone, stuck at Phone is starting

It all started when I forgot my pattern, I've tried to delete lockscreen.db from data/system using X-Plore, my pattern gone but I can't go to home screen, it just showed me Phone is starting the whole night.. I've also tried to restore the lockscreen.db to it's default (I did backup before), but the problem remains the same.. I can only access status bar and settings now
I'm on stock android 10 now, rooted with magisk and twrp installed but my phone seems encrypted (weird folders and files name) .. Can I do dirtyflash OTA via TWRP?? I don't want to lose my data since they are very important to me

Categories

Resources