Will make it short.
I had a password set on my phone, keyboard did not pop up when needed to enter password. I booted into TWRP. Entered my password to decrypt the phone. In file manager I deleted this file "/data/system/locksettings.db". When booting to android, device was unlocked with an "android is starting" message (launcher did not start). It was still possible to go into settings, so I did and changed the password to none. Restarting into TWRP I still had to enter a password to decrypt the device, OLD password worked. I booted back to android, changed the password to a swipe pattern, booted back to TWRP once again. This time the pattern nor the OLD password worked. I can't decrypt my phone and was dumb to not backup data beforehand.
I've tried changing the password back and forth to my previous one in android settings, removing the new locksettings.db file, also tried pull&pushing files from another device with the same password to my phone, no success.
Is there anyone familiar with Android encryption that could help me out? What can I do, is there a any specific encryption file somewhere? I noticed a file called /data/unencrypted/key/encrypted_key, most likely unrelated.
Thanks for any help or suggestions!
Related
Good evening everyone,
I forgot my pin and searched the internet how to access without reset the device.
I try lot of times with wrong pass to see if show "forgot password" (not work).
So i found this: install TWRP, rename files gesture.key, password.key (not found), gatekeeper.password.key, gatekeeper.pattern.key, locksettings.db-shm, locksettings.db-wal and locksettings.db in data/system/, reboot. After reboot should skip pin screen...
But after reboot, the device keep rebooting. It shows the Samsung logo and reboot. I tried rename back those files, but continue rebooting.
Someone know how to resolve without factory reset?
Thanks and sorry for my bad english.
You're in a bootloop. Unless there is somebody who knows more about this that I do, you're gonna have to reset. Sorry
mav_kll said:
Good evening everyone,
I forgot my pin and searched the internet how to access without reset the device.
I try lot of times with wrong pass to see if show "forgot password" (not work).
So i found this: install TWRP, rename files gesture.key, password.key (not found), gatekeeper.password.key, gatekeeper.pattern.key, locksettings.db-shm, locksettings.db-wal and locksettings.db in data/system/, reboot. After reboot should skip pin screen...
But after reboot, the device keep rebooting. It shows the Samsung logo and reboot. I tried rename back those files, but continue rebooting.
Someone know how to resolve without factory reset?
Thanks and sorry for my bad english.
Click to expand...
Click to collapse
Is verity disabled?
Have a custom ROM installed (Havoc) with PIN as screen lock. Have never installed the encryption/verity disable mod. Here's the thing:
When I reboot into TWRP, I am prompted for a password. If I type in the correct PIN, it goes into TWRP. HERE'S THE THING: If I just hit cancel, I am still able to see all of the contents of the device, mount MTP, etc. as if there was no PIN protection at all
It may be still "encrypted" but even though I have set my own PIN, somehow I believe that it's just using the default password. I have tried disabling the PIN, changing the PIN, removing work mode, setting to password rather than PIN, repairing filesystem, etc.
I'm kinda at a loss. Is this expected behavior or am I missing something?
Did you format data from TWRP while switching to Havoc os from OOS
Disregard, I got it sorted by doing a data wipe in TWRP then set new passcode in havoc during setup
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
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
Last year I installed LineageOS on a S9+ (now discontinued) and I encrypted the device. Now I have completely forgotten the pin to decrypt it, so it returns a message which states it will wipe all my data after some failed attempts. How to solve this problem before it's too late? Can I reset the attempts count, change the pin or backup the encrypted data?
The good news is I can access TWRP (v3.4.0) recovery mode. I read some tutorials, but I shouldn't remove decryption by cleaning the partition. Unlike normal boot, can I try to decrypt it as many times as I want, until I retrieve the pin, without worrying about my data being automatically erased? What if normal boot won't recognize the correct pin after recovering/changing it from TWRP? Do you know any terminal commands to execute the above tasks?
casxa said:
Last year I installed LineageOS on a S9+ (now discontinued) and I encrypted the device. Now I have completely forgotten the pin to decrypt it, so it returns a message which states it will wipe all my data after some failed attempts. How to solve this problem before it's too late? Can I reset the attempts count, change the pin or backup the encrypted data?
The good news is I can access TWRP (v3.4.0) recovery mode. I read some tutorials, but I shouldn't remove decryption by cleaning the partition. Unlike normal boot, can I try to decrypt it as many times as I want, until I retrieve the pin, without worrying about my data being automatically erased? What if normal boot won't recognize the correct pin after recovering/changing it from TWRP? Do you know any terminal commands to execute the above tasks?
Click to expand...
Click to collapse
Go into TWRP.
Click the file manager.
Now go to data/system and find "locksettings.db" and delete it.
Reboot phone and see if pin is gone. If not.
Beck to TWRP. Back into data/system. And delete all of these and anything else that starts with "locksettings" that I forgot.
"gatekeeper.password.key
-gatekeeper.pattern.key
-locksettings.db
-locksettings.db-shm
-locksettings.db-wa
Reboot and pin should be gone.
Look into these as well.
[Solution] How to Delete Your Android Security PIN & PATTERN
This guide will walk you through deleting your security PIN via several methods. This guide is for those who have forgotten your security PIN and cannot do a Google reset for some reason. Have restored your phone from an old backup that had a...
forum.xda-developers.com
[Tool][Tested]Remove lockscreen password/pin
Hi Guys, I know it's a frustrating situation when your phone reject your lockscreen password. There are some solutions and I had made a flashable zip which will make the task easier for you instead of deleting the files yourself. This has been...
forum.xda-developers.com
andybones said:
Go into TWRP.
Click the file manager.
Now go to data/system and find "locksettings.db" and delete it.
Reboot phone and see if pin is gone. If not.
Beck to TWRP. Back into data/system. And delete all of these and anything else that starts with "locksettings" that I forgot.
"gatekeeper.password.key
-gatekeeper.pattern.key
-locksettings.db
-locksettings.db-shm
-locksettings.db-wa
Reboot and pin should be gone.
Look into these as well.
[Solution] How to Delete Your Android Security PIN & PATTERN
This guide will walk you through deleting your security PIN via several methods. This guide is for those who have forgotten your security PIN and cannot do a Google reset for some reason. Have restored your phone from an old backup that had a...
forum.xda-developers.com
[Tool][Tested]Remove lockscreen password/pin
Hi Guys, I know it's a frustrating situation when your phone reject your lockscreen password. There are some solutions and I had made a flashable zip which will make the task easier for you instead of deleting the files yourself. This has been...
forum.xda-developers.com
Click to expand...
Click to collapse
The /data folder doesn't list any files
casxa said:
The /data folder doesn't list any files
Click to expand...
Click to collapse
That's weird..
Are you rooted?
andybones said:
That's weird..
Are you rooted?
Click to expand...
Click to collapse
Should be. I don't remember any time I unrooted it after Lineage installation. Can I try to install magisk via twrp (even without installing the manager first, since I can't access the os) or will it override the data?
casxa said:
Should be. I don't remember any time I unrooted it after Lineage installation. Can I try to install magisk via twrp (even without installing the manager first, since I can't access the os) or will it override the data?
Click to expand...
Click to collapse
You can flash the Magisk.apk in TWRP and it won't remove any data.
Then do a reboot from TWRP bavk into TWRP and then you should be rooted and should be able to see data/ partition now.
I'd flash the newest 25.2, and you can flash the .apk in TWRP.
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
andybones said:
You can flash the Magisk.apk in TWRP and it won't remove any data.
Then do a reboot from TWRP bavk into TWRP and then you should be rooted and should be able to see data/ partition now.
I'd flash the newest 25.2, and you can flash the .apk in TWRP.
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
I tried to flash the Magisk apk
Code:
adb sideload Magisk-v25.2.apk
But it had no effect.
casxa said:
I tried to flash the Magisk apk
Code:
adb sideload Magisk-v25.2.apk
But it had no effect.
Click to expand...
Click to collapse
Curious why sideload instead of just hitting install button?
But can you Screenshot me what is shows in the TWRP file manager.
(after the successful flash of Magisk, you'd need at least 1 reboot from TWRP to TWRP before taking effect)
andybones said:
Curious why sideload instead of just hitting install button?
But can you Screenshot me what is shows in the TWRP file manager.
(after the successful flash of Magisk, you'd need at least 1 reboot from TWRP to TWRP before taking effect)
Click to expand...
Click to collapse
Even that method didn't work. I put the apk (renamed to zip) and clicked on "Install" and rebooted. Nothing.
The file manager still shows nothing inside data folder.
casxa said:
Even that method didn't work. I put the apk (renamed to zip) and clicked on "Install" and rebooted. Nothing.
The file manager still shows nothing inside data folder.
Click to expand...
Click to collapse
Very strange, it should flash as .apk.
But I can't think of any reason why nothing is showing in /data.
Sorry man.
Hopefully someone with more experience can help out.