So, I just set a pin lock screen on my Sprint GS5, and I immediately locked it, and went to unlock it (to see what the lock screen looked like), and I entered the pin that I just set on the phone, and it said that it was incorrect. I know what I entered, and the lock screen is not taking it. I have tried multiple combinations involving numbers near the numbers I put in, and nothing has worked. I'd really like to remove the pin lock without erasing anything, as I have things I have not backed up that are not on my SD card. I did not have the device set up with Android Device Manager, nor my Samsung Account. The phone was rooted with Towel Root.
Is there anything I can do other than a factory reset? This is really aggravating me.
Now you know why you should always make a backup first.
You should be able to remove the PIN using Paulyhofman's method.
This requires ADB debugging on or in the alternative, installing a custom recovery.
If the Sprint bootloader is locked and hence you can't do a proper custom recovery, then do a forum search as there are several other PIN bypass methods in existing threads. Actually doing a search should always be the first step before posting any question.
adb shell
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db
sqlite> update secure set value=65536 where name='lockscreen.password_type';
sqlite> .exit
# exit
adb reboot
.
fffft said:
Now you know why you should always make a backup first.
You should be able to remove the PIN using Paulyhofman's method.
This requires ADB debugging on or in the alternative, installing a custom recovery.
If the Sprint bootloader is locked and hence you can't do a proper custom recovery, then do a forum search as there are several other PIN bypass methods in existing threads. Actually doing a search should always be the first step before posting any question.
adb shell
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db
sqlite> update secure set value=65536 where name='lockscreen.password_type';
sqlite> .exit
# exit
adb reboot
.
Click to expand...
Click to collapse
I must not have had usb debugging enabled on my phone because ADB says device not found. I was able to copy the settings.db file to my SD card using aroma, but I try to open it in SQLite reader, and it says it is encrypted. Do you know how to decrypt this file? Or anyone?
Okay, I found a solution. Instead of modifying settings.db, I deleted /data/system/locksettings.db, and the lock screen was removed.
I did this from within the aroma file manager. I finally have my phone back! I will be setting up remote controls, usb debugging, and backing some stuff up now.
Related
Just installed Elelinux-7.1.0-Hero-v2.1, poked around in Dev Tools, and apparently turned on some debugging feature I should not have. Now my phone goes into a reboot loop. It isn't a full reboot... only the Android boot animation is shown, not the initial HTC splash screen. It makes it up to the lockscreen and the phone is responsive for about 10 seconds before it freezes up and reboots.
This isn't enough time for me to unlock the screen, open the app drawer, run Dev Tools, and change back the setting before the phone reboots. Is there another way of manually clearing the Dev Tools settings without having to do a factory wipe?
Since I can't get into Dev Tools now, I cannot say which options were enabled. I turned on one that shows the touch coordinates, and I think another that shows the running processes (trying to track down battery drain issues). There may have been a couple of others, but due to the delay in the reboot, it's hard to tell exactly which one is the culprit.
So I'm hoping there is some way to bring up the phone in single-user mode, edit or delete a settings file, and then rebooting the phone. I'm using the AmonRA recovery console, if that helps.
I'd just reflash...
Yeah, there isn't much on the phone yet, so I could do a wipe and not lose anything, but I'd rather see if there is a way to recover in case something like this happens again in the future.
I did find an issue tracker page on Google that describes the problem, and a couple of proposed fixes. I'm not allowed to post links yet, so demangle this to bring up the page. I'm going to try editing the settings.db file and hopefully that will fix things:
ht tp://code.google.com/p/cyanogenmod/issues/detail?id=1026
Hooray, editing the settings.db file worked! I followed the suggest posted by cryptographrix in post #14 of the code.google.com thread:
Code:
$ [B]./adb shell[/B]
/ # [B]mount /data[/B]
/ # [B]mount /system[/B]
/ # [B]/system/xbin/sqlite3 ./data/data/com.android.providers.settings/databases/settings.db[/B]
SQLite version 3.7.2
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> [B].header ON[/B]
sqlite> [B]select * from system where name="show_processes";[/B]
_id|name|value
109|show_processes|1
sqlite> [B]update system set value=0 where name="show_processes";[/B]
sqlite> [B]select * from system where name="show_processes";[/B]
_id|name|value
109|show_processes|0
sqlite> [B].quit[/B]
/ # [B]reboot[/B]
I am running CM
So I disabled the slider unlock, but it stopped recognizing my gesture for some reason and I cannot figure out how to login to my phone. Running stable build of CM7.1, not sure if I can change that setting somehow from ADP or do something from a terminal... Any ideas?
When I say gesture, I am not referring to the password based on the motion with the dots, I am saying the screen where the unlock / silent toggle was has been disabled and I cannot get passed there.
Your help is appreciated
Did u try unlock with menu button?
I remember that from cm7
Sent from my MB525 running 4.5.1-134 DFP 231 DEFY+ ROM...
using XDA App
No menu button doesn't do anything....
Do you know WHERE this "Slider Disabled" setting is stored? I could go in thru ADB and change it but I don't know where to look.
Here are the things I have tried already
----
Attempt 1:
$ ./adb -d shell
# cd data/data
# sqlite3 ./com.android.providers.settings/databases/settings.db
sqlite> update system set value=1 where name='lockscreen_disabled';
sqlite> .exit
# reboot
Attempt 2:
adb shell
input keyevent 82
---
Neither of these worked. I think the solution should be in the updating the settings.db, but maybe its a different row/record that contains "ENABLE slider"?
Help would be appreciated!
could deleting the the offending theme restore to normal?? Just thinking out loud here ^^
don't know much about adb
Okay. No help here, but I found a fix and I thought i would share it since I have seen that apparently other people have had this problem with no help as well other than "Wipe and reinstall rom"
This app fixed it!
https://market.android.com/details?id=se.curity.android.screenlockbypass
Just make sure you follow the instructions, you have to install the app, than install any other random app and BAM- unlocked phone! Sweet
Hi there,
I had kinda trouble today skipping the "Verify your account" after a recovery Factory Reset.
Long story short, a collegue's daughter locked her phone, and he had to perform a factory reset from recovery.
Since she changed her phone number and lost her password, no google's account recovery were possible.
After a week of trial and error, he decided to let me take an eye.
As you know :
- If you perform a factory reset with recovery, a google's anti-theft feature, called Factory Reset Protection, occurs and force you to login once with a google account that was previously set on this phone.
- If you perfrom a factory reset with android built-in (Settings -> Backup and restore -> Factory reset), you won't encounter this issue.
- If for a reason or an other, you don't know the required credentials, don't have unlocked your bootloader and never checked "Allow oem unlock", you're kinda screwed.
Here is how I figured a way to bypass this feature (BTW, I won't post any link this I didn't wrote any of theses tools. I juste figured a way to use them) :
Disclaimer :
I have not made any of the tools or adb command.
I can't be held responsible for any damage done to your phone.
Don't use any of theses instructions if you don't know the consequences.
Use theses instructions/tools at your own risk.
I achieved this bypass by search and trial.
English is not my native language. Name has been translated and may not be accurate. However, I'm sure you'll find what I meant.
1) Install minimal ADB and fastboot (Google that)
2) Install Motorola's USB drivers (Motorola's website)
3) Power on your phone, set-up a wifi connection.
4) Return to the Wifi wizard, choose a connection you do not want to connect to. Check 'Show password" and enter a random password.
5) Double press the text, choose "Share".
6) Long press "Gmail", you'll be redirected to Gmail's settings.
7) Press "Notification" then "Application settings"
8) Press Option (3 dot menu) then "Manage account"
9) From there, you'll sucessfully enter phone settings. Unlocking the "Developper option" won't work anyway.
10) Press "Users" and create a new one. Don't set it up ; instead, log in the newly created user.
From there, it was Trial and Error and I, somehow, managed to allow Developper option.
11) Try various things such as : Enabling developper option from new user ; Switch to owner and try again ; Open an app and return to settings with the little square (suspended app) with owner and new user.
Search anywhere, be patient, try various things, it'll work somehow ...
From a certain point, you'll be able to unlock the Developper option.
12) In Developper Option, check "Enable USB debugging"
13) Open a cmd in Windows, navigate to the adb folder. Type in the following command :
Code:
adb devices
You should be able to see the phone. If not, ensure you have the correct drivers (From device manager).
If your phone is detected, type in the following command :
Code:
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
Thanks to : Matthew Read (android stackexchange)
14) Perform a factory reset from settings.
15) Optionnal : After phone reboot, enable Developper Option, check "Allow OEM unlock" to allow future bootloader unlock and flashing.
That should do it.
Step 11 is very vague but I spent few hours unlocking this phone and I did LOT of things. I spent 1 hour or so on this step and forgot what I precisely did to unlock this option.
If you manage to succeed, please post your instructions.
I WON'T relock the phone in order to discover exactly what worked.
This won't work for long, since this is a security fault and will be patched (as every previous bypass) sooner or later.
Be patient and be curious ! Have fun
Don't waste time here.....
Already Video available on YouTube...
PIN doesn't work, although Fingerprint is OK, so either I input it wrong or one of us forgot. Is there anyway to rest the PIN w/o a Factory Reset? Thanks
Hmmmmm, the plot thickens . .. . .. . I attempted to use Android Device Manager to have Google lock the phone and provide a new passcode (PIN). ADM located the phone OK and tbe phone reflected that it had locked the phone with a new passcode. However the new passcode PIN did not function, the old PIN still did not work, but fortunately Fingerprint is still OK.
It appears that PIN may not function & I need to enter PIN to attempt to change it!
amphi66 said:
Hmmmmm, the plot thickens . .. . .. . I attempted to use Android Device Manager to have Google lock the phone and provide a new passcode (PIN). ADM located the phone OK and tbe phone reflected that it had locked the phone with a new passcode. However the new passcode PIN did not function, the old PIN still did not work, but fortunately Fingerprint is still OK.
It appears that PIN may not function & I need to enter PIN to attempt to change it!
Click to expand...
Click to collapse
you have TWRP install?
DrakenFX said:
you have TWRP install?
Click to expand...
Click to collapse
Yes. TWRP, rooted & ROM is ZAD Mix7 rev .2 with some minor mods. I recall the PIN working yesterday (I think). I certainly needed (& used it ) it to set the Fingerprint
Using TWRP or Any file explorer with root access and do the following:
- Go to file explorer then go to :
- data > system > locksettings.db (Delete that file)
- reboot and setup your pin or whatever you want.
DrakenFX said:
Using TWRP or Any file explorer with root access and do the following:
- Go to file explorer then go to :
- data > system > locksettings.db (Delete that file)
- reboot and setup your pin or whatever you want.
Click to expand...
Click to collapse
Haha, I want to thank you for this. I've had this issue since upgrading from B20 to B29, but I just lived with it since I could unlock using my fingerprints.
I have kept my phone from locking for a day because I Forgot the lockscreeen passsword while changing it on LGK20+, I'm roooted is there any way to disable/delete the lockscreeen pin using twrp? I read an article online that says I can delete a few files ending in .key and i willl be able to set a new passsword can any1 confirm that or have an easier way to disable my lockscreeen pin ( i've prevented it from locking so far),,,...
Pitchblack Recovery, which you can download from a thread on our K20plus forum, has an option within advanced tools with several useful scripts one of which is removing Fingerprint/PIN passwords. It deletes some specific files but I'm not sure of the full extent of these scripts.