Hello, I have a SM-J200BT and I was wondering if I could brute force my way into the phone's password to gain access to the device without losing any data.
How should a Brute-Force-Attack help?
AFAIK the Google FRP pin / pattern / password is stored within a database located in Android's critical section. This db can only get accessed from outside if phone is rooted and ADB got enabled.
Ok so I guess reformatting the phone is the only option left, isn't it?
jwoegerbauer said:
How should a Brute-Force-Attack help?
AFAIK the Google FRP pin / pattern / password is stored within a database located in Android's critical section. This db can only get accessed from outside if phone is rooted and ADB got enabled.
Click to expand...
Click to collapse
s
Related
Problem:
I'm an app developer. I have one app that let's you lock the device using Device Administration. One of my users had some conflicts with my app and another. He then removed Device Administration and uninstalled my app, rebooted his phone, and now he cannot access his phone.
He of course cannot use my app to change the password now (since it's uninstalled).
His phone is stock 2.2 LG Optimus V, Virgin Mobile, Rooted.
Question:
I'm needing to find a way that my user can now change his lock code.
I need:
1.) to know an internal class (from com.android.internal) that I could use within an app to change the lock code (just like the system settings do).
OR
2.) to know a command I can use with adb shell to remove or change the phone lock code.
OR
3.) to know the location of the file that stores the lock code information.
Any help is greatly appreciated.
I did actually manage to rewrite a couple pieces of my app, install with adb install, then start it with adb shell am start, and re-enable device admin. So I was able to make it work.
This also worked when my user tried it. Problem Solved.
I've been searching extensively for an answer though I couldn't find one.
I'm currently testing an app, which is running on from android 4 to android 7. I wanted to find out whether it would be possible IN ANY WAYS to download a database from the root folder without knowing the PIN code, USB debugging set to off and without root.
Is that in any way possible (Android 4-7)?
After that, since I'm pretty sure I have no way of uploading the files back in to the system, I'll do a factory reset, the PIN code will be removed and I will enable USB debugging re-download the app and replace the databases with the ones I've downloaded.
How should the pushing phase work out? Rooting the phone isn't an option.
Thanks a lot
My unrooted Samsung S7 edge is pattern locked but I also set my fingerprint on it. Since I haven't used the pattern in a while, i forgot what it was but I can still open the phone with my fingerprint.
I read online of using adb to delete a gesture.key file however on mine it is a gatekeeper.pattern.key file and when I try to use adb to delete it, adb says permission denied.
my question: I don't want to root this phone or install a custom recovery. is there any way to remove or reset the pattern without factory resetting my phone? I do not get an option to reset using my gmail account.
Thanks.
If you can still access the phone threw finger print data why are you not able to go into lock screen and security and change pass key or it needs the puzzle and fingerprint to proceed
PoochyXXX
Without root you can pull files with adb, but editing or deleting them is out of the question. I've done what you are wanting to do before, but you have to have root or TWRP.
Sent from my LG-Q710AL using Tapatalk
Hello. I'm wondering if its possible to make a phone copy files from the sd card to a destination on the phone while its booting so it has root permissions with some sort of custom code pushed to the phone via adb update for this to happen. I know something of the sort is possible but i may have the wrong idea about it?
My goal is to access a phone with a pattern lock on it by removing the gesture.key file in order to access the data. The phone does belong to me but i don't know the pattern to it. Any help would be appreciated.
The phone is un-rooted but does have usb debugging enabled.
Assume that one has a device that:
Running a version of Android that is either Nougat, Oreo, or Pie.
The device uses not full disk encryption but rather file-based encryption.
Has a password, pattern, or PIN set.
Say that the user has booted into TWRP or something like and deletes each of these files if they exist:
gatekeeper.password.key
gatekeeper.pattern.key
locksettings.db
locksetting.db-shm
locksettings.db-wal
Here are my questions:
Upon booting into stock Android, will Android be able to load correctly? If not, what should it be expected to do?
I've seen on here and other websites users who did something similar to what I described and were unable to get to their applications/files BUT were able to access Settings. If this is what should be expected to happen, then what will happen if one sets another lock code through Settings? Will it erase the blob data connected to the old lock code that plays a role in deriving the decryption key? Will it crash instead?
Master Melab said:
Assume that one has a device that:
Running a version of Android that is either Nougat, Oreo, or Pie.
The device uses not full disk encryption but rather file-based encryption.
Has a password, pattern, or PIN set.
Say that the user has booted into TWRP or something like and deletes each of these files if they exist:
gatekeeper.password.key
gatekeeper.pattern.key
locksettings.db
locksetting.db-shm
locksettings.db-wal
Here are my questions:
Upon booting into stock Android, will Android be able to load correctly? If not, what should it be expected to do?
I've seen on here and other websites users who did something similar to what I described and were unable to get to their applications/files BUT were able to access Settings. If this is what should be expected to happen, then what will happen if one sets another lock code through Settings? Will it erase the blob data connected to the old lock code that plays a role in deriving the decryption key? Will it crash instead?
Click to expand...
Click to collapse
How about you set the conditions and try it out yourself
([emoji3590]09-09-18[emoji3590])
PoochyX said:
How about you set the conditions and try it out yourself
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
Because I don't have a functioning Android device that meets the requirements I outlined.
I am bumping this thread.
Bump.
**DONT**
did the same thing "accidently " a while ago, had to format /data (internal storage is gone!)
My device was struck on "Wait a second" forever.
It worked before file-based-encryption, but now I think the android system (Gatekeeper maybe?) checks for locksettings.db file during the bootup and doesn't start if not found or something
PS: Don't delete any of these files if your system uses file-based-encryption
locksettings.db
locksettings.db-shm
locksettings.db-wal.
file-based-encryption actually requires your PIN (used to encrypt) to decrypt the file-system, in addition it requires a lot of other ce/de key files, my advice would be not to delete stuff without making a proper backup!