Disabling PIN lock - Droid X General

Anyway to do this via adb? Found No Lock app in market...but I need to run the app first and enable no lock. Then it doesn't apply on boot.
I'm trying to unlock a friends phone without resetting data. Btw...this phone I'm trying to unlock is rooted. She's an idiot and forgot the pin she used and thinks she pressed the wrong pin....twice to confirm. Lol
I know its possible. I just need to find an app that runs/opens after I adb install it. And applies on boot. Or maybe a shell command to open it?
Edit:
***confirmed****
This works for pattern. I need PIN. Can anyone help?
> adb -d shell
# sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite> update secure set value=0 where name='lock_pattern_autolock';
sqlite> .exit
# exit
> adb reboot
Sent from my DROIDX using XDA App

andrewp3481 said:
Anyway to do this via adb? Found No Lock app in market...but I need to run the app first and enable no lock. Then it doesn't apply on boot.
I'm trying to unlock a friends phone without resetting data. Btw...this phone I'm trying to unlock is rooted. She's an idiot and forgot the pin she used and thinks she pressed the wrong pin....twice to confirm. Lol
I know its possible. I just need to find an app that runs/opens after I adb install it. And applies on boot. Or maybe a shell command to open it?
Edit:
***confirmed****
This works for pattern. I need PIN. Can anyone help?
> adb -d shell
# sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite> update secure set value=0 where name='lock_pattern_autolock';
sqlite> .exit
# exit
> adb reboot
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
did you try sqlite> update secure set value=0 where name='lock_pin_autolock';
edit:
if that doesnt work do this please:
> adb -d 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
that should remove all passwords on lock screen. i cant try here at work but i can once i get home if you like.

Related

[Question] Pattern lock - too many attempts

Good day,
I was curious about what would happen if i do to many fail attempts in the pattern lock screen of my magic.
I looked around on google to find the answere and noticed that there were many many pages that talked about andoid having a bug.
If i understood correctly, after x times incorrect pattern inputh you get a login screen for your google account you used for the phone.
The bug seems to make the login impossible.
You will be able to enter the credencials but login will always fail.
I was wondering if anybody is aware about this and can tell me if this bug has been solved now.
Many people talk about performing a hard reset when this happens.
Which is a solution,... but not one i was hoping for.
NOTE- i am not in this situation now, i can access my phone.
But i do have a lot of D**Head friend who love to figure out what happens when they try to many times.
If you try too many times you get a timeout. You have to wait 30 seconds for each attempt.
Don't know bout the loginscreen though, never happened to me.
Lucky for you, I've had the exact same problem recently and found a solution that doesn't require full reset =)
./adb shell
# sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite> update system set value=0 where name='lock_pattern_autolock';
sqlite> update system set value=0 where name='lockscreen.lockedoutpermanently';
sqlite> .exit
# exit
originally found on http://www.naschenweng.info/2009/09/17/android-too-many-pattern-attempts-phone-is-locked
good luck!
Hi there!
I have exactly the same problem but when i try the solution using the sqlite3 commande, i got an sqlite3: not found .
Is there any pre-requisite i forgot?
My steps were: fastboot with a modified image then adb shell: didn't work, then normal boot and adb shell: didn't work too.
Any help will we welcome!
Lg eve pattern locked need help!!!
my pattern lock was entered wrong too many times and i dont know how to access the phone even my google account wont work what do I do?
i have an Lg eve .
Here is what i got.
C:\AndroidSDK\tools>adb shell
# sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite> update system set value=0 where name='lock_pattern_autolock';
sqlite> update system set value=0 where name='lockscreen.lockedoutpermanently';
sqlite> .exit
# exit# sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite> update system set value=0 where name='lock_pattern_autolock';
sqlite> update system set value=0 where name='lockscreen.lockedoutpermanently';
sqlite> .exit
# # sqlite: not found
# sqlite: not found
# sqlite: not found
#
# exit
#
Click to expand...
Click to collapse
Have an idea?
afras said:
Have an idea?
Click to expand...
Click to collapse
Yeah. You did it wrong.
Pay attention:
Type this:
./adb shell
Click to expand...
Click to collapse
You'll get a shell prompt.
Type this:
sqlite3 data/data/com.android.providers.settings/databases/settings.db
Click to expand...
Click to collapse
You'll get the sqlite prompt.
Type these three lines:
update system set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
.exit
Click to expand...
Click to collapse
Many thanks to you my friend, it worked
You sir, are a life-saver
lost
ok i am having the exact problem with my lg eve android...but where do i type in these codes is my question?
im getting crazy
sqlite3 is there right?? see screenshot
C:\android-sdk-windows\tools>adb -d shell
$ su
su
# sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite3: not found
#
running sqlite3 manually (doubleclicking sqlite3) works perfectly, but it doesnt connect to my android phone
Hi,
I try to unlock my sister's phone (HTC Tattoo), but it doesn't work, I have a problem with sqlite3 : I write in the shell "sqlite3 data/data/com.android.providers.settings/databases/settings.db" and I have this : "sqlite3: permission denied"
I don't know what to do !? The device is recognized (adb devices detects it) and the Debug USB mode is activate.
I'm waiting for your help.
P.S. : excuse me for my bad english : I'm french !
Easier fix!
I just finish talking to rogers and all you have to do 9if your willing to reset your phone and lose all your apps etc) is hold one of your volume buttons the centre menu button and the photo button hold these 3 for about 15-25 seconds and it will ask you to factory reset your phone! problem solved!
I have a Q...
Approximate how many times you have to enter the wrong password/pattern to have it permanently locked?
I don't think it perma locks. If you mess it up, it should just ask for your Google credentials again.
Sent from my T-Mobile myTouch 3G using Tapatalk
yeah... I want to know how many attempts before it asks you for the google credentials.
thx
3-5, can't remember for sure though.
Sqlite3 not found
>20 wrong codes and your locked out.
>I found this out thanks to my darling wife...and of course I had just turned off wireless an hour before to stop kids downloading crap whislt playing >games.
>So now I'm stuck...
C:\android-sdk-windows\tools>adb shell
$ su
su
# sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite3: not found
#
>Any ideas how to "find" sqlite3? :fingers-crossed:

[Q] Samsung Fascinate screen 0 brightness

Hi all, I just downloaded one of the battery widgets from the market, and as soon as when I set up my brightness to 0 from the widget, screen went black. I still hear incoming calls and the notification sounds but nothing actually appears on the screen. I tried the hardreset (volume buttons + power), and odin3 system recovery, didn't fix the problem. I know this is not a screen damaged issue because the booting animation still plays... So does anyone know how to change my brightness settings using odin3? Or any solutions?
Thank you.
If you have usb debugging turned on, adb to it and rm the apk of the app you installed and reboot
Or if rooted, go in through adb via recovery
I don't have debugging mode on nor the phone is rooted. This is annoying..
I would try to use ODIN to install clockwork recovery. Then adb to the phone and do this:
$ ./adb -d shell
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db
sqlite> update system set value=255 where name='screen_brightness';
sqlite> .exit
# reboot
is my phone need to be rooted to perform those steps?
U r screwed. Not to be a **** bit likely if Odin won't fix it u will have to take it all the way back.
Sent from my SCH-I500 using XDA App
nitroxeno said:
I would try to use ODIN to install clockwork recovery. Then adb to the phone and do this:
$ ./adb -d shell
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db
sqlite> update system set value=255 where name='screen_brightness';
sqlite> .exit
# reboot
Click to expand...
Click to collapse
anyone notice that the adb command sqlite3 doesn't seem to exist on our fascinates? I swear I used it by default on my droid inc, but then again I was running custom roms... is that command just not on the fascinate?
Good calk forgot all about clockwork with Odin. Good save
Sent from my SCH-I500 using XDA App
What about a hard reset?
There should be a sticky about this.

SQlite3

greetings, i need SQlite3 to change my android id, since everyone has the same id on the froyo leak. if anybody can provide me with it, its located in
/system/xbin
to be specific i need it to access storm8 games. they identify your account by iphones UDID or android_id. for those interested in changing it just follow the following commands using adb
Code:
su
cd /dbdata/databases/com.android.providers.settings
sqlite3 settings.db
sqlite> insert into secure (’name’, ‘value’ ) values (’android_id’,'what-ever-your-device-id-was-before’);
sqlite> .exit
Reboot
or simply download android id changer, which personally i don't like.
***mods if find find this inappropriate edit the post but keep the request for sqlite3

Fix Mobile Data drain.

After 2 days of testing i think i have a clean solution to fix the mobile data drain by setting the preferred network mode to 1 (GSM only). No need to delete or rename anything. Just update the db that is already there .
You need a rooted device for this.
Extract the sqlite3.zip and push to your device with the following commands:
Code:
adb shell mount -o rw,remount /dev/block/mmcblk0p3 /system
adb push sqlite3 /system/bin
adb shell chmod 6755 /system/bin/sqlite3
adb shell
su (to gain root permissions)
sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
reboot
I'll give this a try. Thanks
Edit: Is it possible I can do this on the device without adb? Adb doesn't want to detect my tablet with debugging enabled.
agentdax5 said:
I'll give this a try. Thanks
Edit: Is it possible I can do this on the device without adb? Adb doesn't want to detect my tablet with debugging enabled.
Click to expand...
Click to collapse
Sure, as long as you have some sort of terminal emulator installed.
agentdax5 said:
I'll give this a try. Thanks
Edit: Is it possible I can do this on the device without adb? Adb doesn't want to detect my tablet with debugging enabled.
Click to expand...
Click to collapse
with root explorer and a terminal app (eg connectbot) you can do it.
What exactly does this do? Is it the same result as renaming the phone and telephone apks?
Sent from my SPH-D700 using XDA App
Thanks! Mine is done. I'll report back later after I charge and give it a go.
mrkrabs said:
What exactly does this do? Is it the same result as renaming the phone and telephone apks?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
This updates the database configuration setting that causes the phone to not to look for 3G networks only 2G (GSM which includes GPRS and EDGE). I'll let the OP elaborate more, but this config change must reduce the battery usage by causing the phone and telephony services to chill out out a bit when in standy mode.
_motley said:
This updates the database configuration setting that causes the phone to not to look for 3G networks only 2G (GSM which includes GPRS and EDGE). I'll let the OP elaborate more, but this config change must reduce the battery usage by causing the phone and telephony services to chill out out a bit when in standy mode.
Click to expand...
Click to collapse
couldn't describe it better
2g = only poll cell if request is made that needs cell, 3g = poll all the time, which means that if you change to only 2g then it should not check for cell if you are in wifi range.
I am sure thats how the tech works if i remember my time at nokia right LOL
is there a post around here to explain how to get ADB working on this thing? i can ADB shell in but i get "operation not permitted" when i try to mount /system as r/w
(yes i'm rooted)
thanks guys
edit: i got permission to mount the /system as r/w but when i try to push the sqlite3 i get "Device not found"
i suppose i can give a little more info
i'm running windows 7 ultimate 64 bit with an administrator command prompt and the newest iconia a500 usb drivers from acer's support site and i have my SDK up to date
I did this and it doesn't seem to have a big effect. 2 hours on battery mostly in sleep, Display 33%, Cell 31%, Idle 18%, etc.
Richard:
Just out of curiosity (Yes, I fully acknowledge I should have done something like "select * from secure where name='preferred_network_mode'" beforehand! ) what is the default value of "preferred_network_mode" before this modification sets it to "1"?
-----
Doc Kinne
Somerville, MA
kinnerc said:
Richard:
Just out of curiosity (Yes, I fully acknowledge I should have done something like "select * from secure where name='preferred_network_mode'" beforehand! ) what is the default value of "preferred_network_mode" before this modification sets it to "1"?
-----
Doc Kinne
Somerville, MA
Click to expand...
Click to collapse
Default value is 0 (zero).
agentdax5 said:
I did this and it doesn't seem to have a big effect. 2 hours on battery mostly in sleep, Display 33%, Cell 31%, Idle 18%, etc.
Click to expand...
Click to collapse
It's not about what your stats say, but what your mA drain is. i loose only a couple of % in a night (sleep).
edgemaster191 said:
is there a post around here to explain how to get ADB working on this thing? i can ADB shell in but i get "operation not permitted" when i try to mount /system as r/w
(yes i'm rooted)
thanks guys
edit: i got permission to mount the /system as r/w but when i try to push the sqlite3 i get "Device not found"
i suppose i can give a little more info
i'm running windows 7 ultimate 64 bit with an administrator command prompt and the newest iconia a500 usb drivers from acer's support site and i have my SDK up to date
Click to expand...
Click to collapse
@edgemaster191
I am getting the same error; I also am rooted, running ADB from Windows 7 (and Mac OS X - tried both, same error). I also have latest drivers, and latest ADB.
I get "operation not permited error." Did you have any luck on getting further?
try this instead as a work around:
adb push sqlite3 /sdcard/sqlite3
adb shell
$ su
# mount -o remount,rw /system
# cp /sdcard/sqlite3 /system/bin/sqlite3
# chmod 6755 /system/bin/sqlite3
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
# reboot
I've never been able to use root level adb cmnds with this device from outside the adb shell env, I think you need to update the default.prop, but this gets overwritten on reboot, I'm sure there is a way to fix this, and has proabably been discussed in another thread I've been too lazy to go find lol.
nycbjr said:
try this instead as a work around:
adb push sqlite3 /sdcard/sqlite3
adb shell
$ su
# mount -o remount,rw /system
# cp /sdcard/sqlite3 /system/bin/sqlite3
# chmod 6755 /system/bin/sqlite3
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
# reboot
I've never been able to use root level adb cmnds with this device from outside the adb shell env, I think you need to update the default.prop, but this gets overwritten on reboot, I'm sure there is a way to fix this, and has proabably been discussed in another thread I've been too lazy to go find lol.
Click to expand...
Click to collapse
FTFY. 10char.
I am going to have to run some logs....just not seeing any drain that would justify doing this ....will definitely keep an eye out for it though
nycbjr said:
try this instead as a work around:
adb push sqlite3 /sdcard/sqlite3
adb shell
$ su
# mount -o remount,rw /system
# cp /sdcard/sqlite3 /system/sqlite3
# chmod 6755 /system/bin/sqlite3
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
# reboot
I've never been able to use root level adb cmnds with this device from outside the adb shell env, I think you need to update the default.prop, but this gets overwritten on reboot, I'm sure there is a way to fix this, and has proabably been discussed in another thread I've been too lazy to go find lol.
Click to expand...
Click to collapse
such things will be able with kernels that overwrite the default.prop
matguard said:
@edgemaster191
I am getting the same error; I also am rooted, running ADB from Windows 7 (and Mac OS X - tried both, same error). I also have latest drivers, and latest ADB.
I get "operation not permited error." Did you have any luck on getting further?
Click to expand...
Click to collapse
i was able to finally get it, i copied the splite3 to /system/bin using root explorer, ran chmod through terminal emulator then ran the final command from adb shell.
not ideal but it worked

[Q] problem using adb to unlock phone [want to find solution deadly!!!]

My phone was locked after too many attempts to unlock the pattern password(i didnt did it myself, anyway~)
I didnt turn on usb debugging before the phone was locked so i tried to start adb daemon from the CWM recovery(in advanced->start adbd)
i followed instructions there after google around: http://chethaka.wordpress.com/2013/02/28/unlock-an-android-device/
Type following commands in cmd
adb devices (verify device is identified by pc. If not reconnect device and try again. it should display “device” with a serial no)
adb shell
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update secure set value=0 where name='lock_pattern_autolock'; (for some devices update “system” is enough but I had to update “secure” too)
update system set value=0 where name='lockscreen.lockedoutpermanently';
update secure set value=0 where name='lockscreen.lockedoutpermanently';
.quit
exit
adb reboot
however i failed on the step "sqlite3 settings.db", saying that
"3 settings.db <
register_localized_collators() failed"
why is that?? what should i do???
(my last post related: http://forum.xda-developers.com/showthread.php?t=2531921)
screenshot
help
any answer??
Use aroma file manager to remove gesture.key
Sent from my MB526 using Tapatalk 4

Categories

Resources