Database Develop

Nexus one Lock pattern

The nexus one failed to unlock, and locked me out permanently. I used ADB shell to defeat it. Now although my phone is no longer locked. when I check my security setting. Every thing on it is still hightlighted as if it has a set pattern. Is there a way to reset it? I'm afraid to use the change pattern setting, since I don't remember the pattern anymore. Please Help. Thanks.

Try backing everything up and resetting all your settings. May I ask what adb shell command you used for this?
EDIT: If it was a pattern lock why didn't you just use your google account to reset it? This completely disables it.

I used this. The reason I didn't use google account reset is because of the bug that invalid all attempt to reset using google account.
How do I reset my setting?
> ./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

is there an update to this by chance? Note you CANNOT use your google login credentials to reset a lock pattern - the bug still exists.
I was able to get out of the lock screen via mobile defense but I want to go back in and get rid of it completely and reset it - any idea how?
thx

bpm2000 said:
is there an update to this by chance? Note you CANNOT use your google login credentials to reset a lock pattern - the bug still exists.
I was able to get out of the lock screen via mobile defense but I want to go back in and get rid of it completely and reset it - any idea how?
thx
Click to expand...
Click to collapse
That 5 tries bug is no longer there. I successfully unlocked the phone with my credentials a few weeks ago.

Its definitely still there - like I said I had this problem today and it wouldn't accept my credentials.
[email protected]
user
neither work.
also, "null" does not work.
ROM in sig.
thx

You're rooted, right?
I'm sorry if this is a stupid question... but can't you shut the phone off, boot into recovery, wipe, then flash the ROM again?

bpm2000 said:
Its definitely still there - like I said I had this problem today and it wouldn't accept my credentials.
[email protected]
user
neither work.
also, "null" does not work.
ROM in sig.
thx
Click to expand...
Click to collapse
Whoa, whoa, whoa. Don't be so quick to say that the "bug" is "definitely still there."
I literally just locked myself out, used my gmail username and password, and it had me immediately draw a new pattern. So there's no such bug on my device..

the bug was on 2.1 and fixed with 2.2.

Ryjabo said:
You're rooted, right?
I'm sorry if this is a stupid question... but can't you shut the phone off, boot into recovery, wipe, then flash the ROM again?
Click to expand...
Click to collapse
I could definitely do that - I just wanted to preserve all my stuff without having to wipe.
Whoa, whoa, whoa. Don't be so quick to say that the "bug" is "definitely still there."
I literally just locked myself out, used my gmail username and password, and it had me immediately draw a new pattern. So there's no such bug on my device..
Click to expand...
Click to collapse
That is great stuff - now did you list your ROM? I'm still on 2.1 like I said, and I *just* had this problem a day or two ago, so for some of us, the problem still exists. I didn't say anywhere it exists on 2.2 or that it exists for everyone now did I? Reading comprehension, its good stuff .
A quick look on the google bug reports would also note that this bug still exists for a great many number of users.

The bug was fixed in 2.2, and the assumption is that you should already be running 2.2 by now, since it has a ton of advantages and not one disadvantage over 2.1. Nobody's going to bother fixing the bug for the old version of OS, slowly being phased out.

Man when did xda get so uppity?
I am not going to run 2.2 yet - CM isn't out yet other than RC and I do not run stock. There are plenty of people who do this. If you're not one of them, don't worry about it and leave the question alone. If you are, and you figured out how to bypass, then please let us know. There are plenty of reasons to be running 2.1 CM/custom ROM over 2.2 stock.
Jack I hope you're on the latest Droid btw, I mean with your line of thinking you should have it right? Why are you in the N1 forum?

bpm2000 said:
Man when did xda get so uppity?
I am not going to run 2.2 yet - CM isn't out yet other than RC and I do not run stock. There are plenty of people who do this. If you're not one of them, don't worry about it and leave the question alone. If you are, and you figured out how to bypass, then please let us know. There are plenty of reasons to be running 2.1 CM/custom ROM over 2.2 stock.
Jack I hope you're on the latest Droid btw, I mean with your line of thinking you should have it right? Why are you in the N1 forum?
Click to expand...
Click to collapse
Whose being uppity? The bug is part of 2.1, the bug was fixed and implemented in 2.2.
Bug prevents you from unlocking phone, the solution is factory reset, or update to 2.2.
So....

Wow.
Lets state it one more time so people get it - bug is still present on 2.1 and fixed on 2.2

Google Account locked
wormbaby11 said:
I used this. The reason I didn't use google account reset is because of the bug that invalid all attempt to reset using google account.
How do I reset my setting?
> ./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
Click to expand...
Click to collapse
when i use this command >adb -d shell but it has message "device not found" . i set up the phone driver already. pls help me!!!

bpm2000 said:
Wow.
Lets state it one more time so people get it - bug is still present on 2.1 and fixed on 2.2
Click to expand...
Click to collapse
To be honest I wouldn’t even assume that it was definitely fixed in 2.2. It was inconsistent on 2.1. I actually pointed it out on the general board when I first got my Nexus One (not long after it was released) and I got the “uppity brigade” replying and telling me I was wrong and there was no bug because they couldn’t reproduce it.
Out of interest - has anyone got proof it was fixed in 2.2? Aside from the fact it doesn’t happen on your specific phone (which you know… congrats, but anecdotal evidence is useless). I assume its in a android changelog or similar?
bpm2000 – wish I had an answer but I ended up wiping my phone in the end. Didn’t even know about the ADB method back then. Sorry can’t be of more help. Its an incredibly annoying bug and one that was known about and should have been fixed long before the Nexus and 2.1 came out.

That is frustrating to hear BDH, I tried the adb stuff when it happened looking through the google support boards but I always got stuck on the:
sqlite>
portion and it would never register the commands for some reason. I was lucky that I had set up remote lock/unlock with mobile defense or else I would have had to wipe as well.
Thanks for the relevant reply.
sokhoeut said:
when i use this command >adb -d shell but it has message "device not found" . i set up the phone driver already. pls help me!!!
Click to expand...
Click to collapse
Did you try mounting first?

[Q] new D3 user

Hi,
i recently bought a new droid 3 from verizon i already sim unlocked it because i live in Europe.
but i'm totally new to the android system but i do know some things about it but is there a guide to help me started rooting and flashing?
or could someone tell me the basics in a nutshell?
my previous phone was a WinMo based phone and all you needed was sspl and you could flash custom roms.
how is it done for android? and what does it mean with fastboot, root? (i asume it is something like linux to be root user?) safeboot? bootstrap? and what is CM7 or CM9
P.S. i study electronics-informatics so you don't need to tell me what linux or windows is
thnx in advance

Can you tell me how you unlocked your phone???
To root
http://forum.xda-developers.com/showthread.php?t=1240130
To flash ROMs install Safestrap from here
http://hash-of-codes.blogspot.com/p/android-downloads.html
Go to the android development section to find ROMs.
Liberty, ICS/CM9, MavRom, and SteelDroid are the most popular. Im using mavrom with ICS currently.

I definitely recommend looking into CM9. I just did a bunch of Googling on it today for my D3.
Now I'm running Ice Cream Sandwich and loving it. It's early yet and it has it's quirks, but overall I think it was worth it.

Dri94 said:
Can you tell me how you unlocked your phone???
Click to expand...
Click to collapse
euhm i sim unlocked my phone using this website unlock4moto.com/order_code/Motorola/Droid_3/any_Motorola/
(put http in before the link) xda wont let me post hyperlinks yet
you only need to give the IMEI number you can find here:
At the Home screen, press Menu
Tap Settings
Scroll down and tap "About phone"
Tap Status
Scroll down the screen and the IMEI # will be listed there
it worked for me and i got the sim unlock code emailed to me within 30 mins (look in you spam folder too)
P.S. thnx for the info

Downtown Dan said:
I definitely recommend looking into CM9. I just did a bunch of Googling on it today for my D3.
Now I'm running Ice Cream Sandwich and loving it. It's early yet and it has it's quirks, but overall I think it was worth it.
Click to expand...
Click to collapse
ooh but is there a way to brick the phone? cause it would be darn stupid to brick my 3 day old phone and send it back to america for repairs.
so just root the phone and install safestrap? no worries of bricking the phone? and are there other methods besides safestrap?
if yes what are the differences?
it all looks SO easy to flash roms for android ( in WinMo it was always wait and see) but then again it was Microsoft...

There is always a chance of bricking your phone but fortunately perma-bricking your phone while trying to flash new roms or using safestrap is almost impossible since you can still enter fastboot (m+powerup) from where you can install the stock sbf/rom
You can also flash using the 'old' bootstrap which basically removes your stock rom and flahes the new one.
Safestrap backs-up your old rom so you can try out another rom in another system/partition. Almost dualboot like except you can't reflash the original rom (yet)
Sry no links i'm on my droid3

"Almost dualboot like except you can't reflash the original rom" hey double, what do you mean by this. If you toggle safe system you can use your original ROM again. although i think im understanding wrong lol

Dri94 said:
"Almost dualboot like except you can't reflash the original rom" hey double, what do you mean by this. If you toggle safe system you can use your original ROM again. although i think im understanding wrong lol
Click to expand...
Click to collapse
You're right but you can't reflash your original rom (non-safe). E.g. i have mavrom as nonsafe/original and ics has safe..now if an update comes for mavrom i can't update it without uninstalling safestrap and going back to bootstrap

Oh I understand you now. And we got the same setup aha.
Sent from ICS Droid3 using xda premium

snakebomber said:
euhm i sim unlocked my phone using this website unlock4moto.com/order_code/Motorola/Droid_3/any_Motorola/
(put http in before the link) xda wont let me post hyperlinks yet
you only need to give the IMEI number you can find here:
At the Home screen, press Menu
Tap Settings
Scroll down and tap "About phone"
Tap Status
Scroll down the screen and the IMEI # will be listed there
it worked for me and i got the sim unlock code emailed to me within 30 mins (look in you spam folder too)
P.S. thnx for the info
Click to expand...
Click to collapse
Hello, Today I tried to unlock my droid 3 on the website that you share with us no luck for me.
I received an Email from them:
Hello
For IMEI number of the order, unfortunately, there is no code in database.
xxxxxxxxxxxxxxx
Please verifity given IMEI number.
If the IMEI is correct, we will propose an alternative solution.
Yours
unlock4moto
but when I dial *#06# it display MEID HEX
A00000xxxxxxxx i think this is the ESN
DEC
273045896523648364 is this the IMEI Number??
I tried to send the 18 numbers but on the website will not let me put more than 15.

Ed27 said:
Hello, Today I tried to unlock my droid 3 on the website that you share with us no luck for me.
I received an Email from them:
Hello
For IMEI number of the order, unfortunately, there is no code in database.
xxxxxxxxxxxxxxx
Please verifity given IMEI number.
If the IMEI is correct, we will propose an alternative solution.
Yours
unlock4moto
but when I dial *#06# it display MEID HEX
A00000xxxxxxxx i think this is the ESN
DEC
273045896523648364 is this the IMEI Number??
I tried to send the 18 numbers but on the website will not let me put more than 15.
Click to expand...
Click to collapse
of what i read is that the MEID is a kind of IMEI number but because there are so many phones with an IMEI number that they needed something new but the unlock is (according what i found on google) always done with the IMEI number.
to what carrier is your phone locked to? and what is the exact type of your phone XT860 XT862? (you can find this in the "about" menu under settings.
maybe it is because my phone was brand new and never used.So it was never activated on the verizon network.
and i don't know if this has anything to do with it but on the box it says that the phone is "global ready".(I personally think it has nothing to do with that because if the phone is quadband it is ALWAYS global ready, if ofcourse the phone is not locked to verizon or some other carrier)
i have an alternative website but it is more expensive i thought it was 23 dollars or so. it first checks if they have an unlock code (never used the site but it looks promising)
sim-unlock.net/sim-lock/75/Unlock_for_any_New_Motorola_Defy_Flipout_Milestone/ (again put the http in front of it)
i hope this helps

[Q] The phone have problems with the network

Hey everyone, since yesterday I've been having some issues and I hope you can help me with it...
My Captivare wont let me send sms or calls, and on the screen says "mobile network not available"I was using the CM7 last build, so all I did was flash it again, hoping that would solve the problem, but that didn’t do anything, later I tried going back to Stock... so I used Odin to go back to 2.2, but now my phone says ” PHONE NOT ALLOWED MM#6” when it boots, and when I try to call someone says “data network not available”.
When I use the SIM in another phone works perfect, so the network is working.
What can I do to fix this ??
Sorry for my english

Sounds like your IMEI is incorrect. Some carriers outside the US do block the generic IMEI for Captivates. Try checking these posts and see if that helps you fix it. If not, Mobiletechvideos can rebuild your IMEI for a fee.
http://forum.xda-developers.com/showthread.php?t=1264021
http://forum.xda-developers.com/showthread.php?t=881162

@Red_81 Mobiletechvideos build IMEI for free where and from when did they started this for free, the charges are $30 in the link posted by u.

ridhi said:
@Red_81 Mobiletechvideos build IMEI for free where and from when did they started this for free, the charges are $30 in the link posted by u.
Click to expand...
Click to collapse
Huh? Can I get a translation? I'm guessing English isn't your first langauge and it is making it hard for me to understand the point you're trying to get across.
Where and from when did they started this for free? ??????
I don't think they do it for free. But I would love it if they did because I will be using their service sometime in the future.

Ridhi, I think the misunderstanding is that Red_81 said MobileTechVideos will do it for a fee, not that they would do it for free.

Reading and comprehension are two skills that are sadly lacking in the forums.

ridhi said:
@Red_81 Mobiletechvideos build IMEI for free where and from when did they started this for free, the charges are $30 in the link posted by u.
Click to expand...
Click to collapse
He said "for a fee," not "for free."

Apologies friends i think i need to get the eye test done.

Hi everyone again, after 3 days of struggle with my phone I've been able to fix it.
Red_81 thanks for you response the problem was the IMEI but none of the links you gave me works for me
After a lot of searching I found a guide that solves the problem of my phone these are the steps:
- Make sure you are on Froyo (whatever ROM, it worked for me on the stock UCJI6 )
- You need to be Root and have Busybox installed
- Now download the version of Galaxy_S Unlock that is at the end of this post into your phone
- Go to your download folder and click to unzip, then launch the .apk file
- If Android doesn't let you install go to Settings > Applications > tick Unknown sources and try again
0. Go to the tab > Signal fix problem
1. Save efs folder
2. Delete nv_data.bin files + reboot
3. Restore data + reboot
4. Create bak files
- Last step that is "restore efs folder" is only there for if the fix didn't work. It's very clear in the app.
That's it !
Now my phone is fully functional thank to this guide and Thanks all who tried to help me.
Source of this guide: darkyrom.com/community/index.php?threads/imei-issue-showing-004999010640000-instead-of-unique-original-number.1876 (the forum don't let me post a link...)

Did you get the original IMEI back for your phone or do you have the test one that starts with 0049?
Sent from my SAMSUNG-SGH-I897 using XDA App

It's the test one but works fine.
Do you know wich may be the consecuences if I keep this IMEI ?

There shouldn'tbe any issues with that one staying on your phone. Some other carriers block this IMEI but none of the American carriers seem to.
Sent from my SAMSUNG-SGH-I897 using XDA App

Felixcm88 said:
Hi everyone again, after 3 days of struggle with my phone I've been able to fix it.
Red_81 thanks for you response the problem was the IMEI but none of the links you gave me works for me
After a lot of searching I found a guide that solves the problem of my phone these are the steps:
- Make sure you are on Froyo (whatever ROM, it worked for me on the stock UCJI6 )
- You need to be Root and have Busybox installed
- Now download the version of Galaxy_S Unlock that is at the end of this post into your phone
- Go to your download folder and click to unzip, then launch the .apk file
- If Android doesn't let you install go to Settings > Applications > tick Unknown sources and try again
0. Go to the tab > Signal fix problem
1. Save efs folder
2. Delete nv_data.bin files + reboot
3. Restore data + reboot
4. Create bak files
- Last step that is "restore efs folder" is only there for if the fix didn't work. It's very clear in the app.
That's it !
Now my phone is fully functional thank to this guide and Thanks all who tried to help me.
Source of this guide: darkyrom.com/community/index.php?threads/imei-issue-showing-004999010640000-instead-of-unique-original-number.1876 (the forum don't let me post a link...)
Click to expand...
Click to collapse
Will try this, Thanks!!

Hope it works for you too

[Q] Does flashing a rom change the device ID?

My work uses the RSA token app to connect to the VPN. For security reasons, the program uses the phones device ID. I ran into an issue where I had to relock and flash the RUU. This changed the device ID and I had to have our IT guy resend the Token. If I flash a rom, will this change the device id again? I don't want to keep bugging our IT guy.

mbarthicus said:
My work uses the RSA token app to connect to the VPN. For security reasons, the program uses the phones device ID. I ran into an issue where I had to relock and flash the RUU. This changed the device ID and I had to have our IT guy resend the Token. If I flash a rom, will this change the device id again? I don't want to keep bugging our IT guy.
Click to expand...
Click to collapse
Depends on what is being used as a Device ID. If we are talking about the IMEI then no it will not change or the serial. Now I do not think this is what is being used and upon some research
It's known to be null sometimes, it's documented as "can change upon factory reset". Use at your own risk, and it can be easily changed on a rooted phone.
So yes when you flash a ROM or even factory reset that ID will be lost. However you can find out what it is and then change it on the new ROM :highfive:

nullkill said:
Depends on what is being used as a Device ID. If we are talking about the IMEI then no it will not change or the serial. Now I do not think this is what is being used and upon some research
It's known to be null sometimes, it's documented as "can change upon factory reset". Use at your own risk, and it can be easily changed on a rooted phone.
So yes when you flash a ROM or even factory reset that ID will be lost. However you can find out what it is and then change it on the new ROM :highfive:
Click to expand...
Click to collapse
Ok, thanks. I think I read the same thing somewhere, but I wasn't sure if the Android ID and the Device ID was the same thing. After a little more digging, I think it is. I found an app called Change Android ID *Root which will allow me to backup and restore the Device ID. It's only a Dollar, but maybe my work will let me expense it

mbarthicus said:
Ok, thanks. I think I read the same thing somewhere, but I wasn't sure if the Android ID and the Device ID was the same thing. After a little more digging, I think it is. I found an app called Change Android ID *Root which will allow me to backup and restore the Device ID. It's only a Dollar, but maybe my work will let me expense it
Click to expand...
Click to collapse
LoL there you go! Yeah Device ID and Android ID are the same thing from what I could determine for this

nullkill said:
LoL there you go! Yeah Device ID and Android ID are the same thing from what I could determine for this
Click to expand...
Click to collapse
Well, I just had one of those moments of "don't trust everything you read on the internet". It turns out they are not the same. I downloaded the app and the Android id is 16 digit hex. The device ID I sent to the IT guy is 24 digits. I guess it will be trial and error nandroid-->flash rom->restore RSA->recover if I have issues.

Digging up an old thread, but did you ever get a fix for this? I'm having a similar issue. Thanks

Permanently Changed MAC Address!!

Hey there. I recently flashed Resurrection Remix OS on my My Mi A2 and rooted with Magisk. After that, for a purpose , I wanted to change the MAC address of my phone(Mi A2) to my previous phone's MAC Address , for which I did install a application from Playstore called "Change Mac Address". I gave that Root access and tried to change it , it showed success but it indeed didn't change the mac. After that i Tried installing 2-3 different apps and they also failed to change it. Few mintues later I rebooted my phone and I see that my MAC has been changed to the MAC address I wanted to change and its now permanent. I tried rebooting several times and it has been the same. And Also I don't remember my original mac address so I don't know what to do . Now please tell me what should i do , and how can i get my original MAC address back to Original . And yes when i reboot my phone it first show mac address as (02:00:00:00:00).. something like this untill i turn on my wifi. I'm a bit worried about this issue . And please tell me what should I do and does changing mac affects my Phone's performance ?!

Try flashing stock modem.img from your rom / from PIE

Erecik, will it wipe all my data and how I can I find the file?

you have the original mac on the box of the phone
before the wifi is turned on the mac address is always 02:00:00...
dont mess around with flashing the modem img, you can break a lot of other things, the app has written the new mac on the efs of the phone, only way to revert is to write the original from the box

laviniu_c said:
you have the original mac on the box of the phone
before the wifi is turned on the mac address is always 02:00:00...
dont mess around with flashing the modem img, you can break a lot of other things, the app has written the new mac on the efs of the phone, only way to revert is to write the original from the box
Click to expand...
Click to collapse
Thank you so much for the help man. Can you tell me how it happened or is it caused because I used several apps(each app has its own way to change) ? And also Tell me which is the best Mac changer app that I can use without any problem. Please give me link to that app. It will be so kind of you.

just pick the one with the best user reviews on the play store, use just one, doesn't matter which one. whichever you use, you probably need to set, it, restart the phone and then the new mac will show.if you write the original mac from the box it will be like you never changed it.
even if you then uninstall the app i t should still keep the previously set mac.

laviniu_c said:
just pick the one with the best user reviews on the play store, use just one, doesn't matter which one. whichever you use, you probably need to set, it, restart the phone and then the new mac will show.if you write the original mac from the box it will be like you never changed it.
even if you then uninstall the app i t should still keep the previously set mac.
Click to expand...
Click to collapse
Okay I didn't knew that we have to restart after changing the Mac. And also the first app didn't change Mac even after restarting so that maybe not working I'll use another app. Thank you so much man . I'll reply here or dm if I get any other query. Thank you so so much

no problem, sorry i've never used many of them so i can't recommend any, i just know how they work (they basically write with root the efs file that holds the mac address of the wifi chip) so it's quite normal for the os to need a restart before the change is "seen"

laviniu_c said:
no problem, sorry i've never used many of them so i can't recommend any, i just know how they work (they basically write with root the efs file that holds the mac address of the wifi chip) so it's quite normal for the os to need a restart before the change is "seen"
Click to expand...
Click to collapse
Thanks. There is also a issue with my newly flashed rom and that issue is about speaker sound . I made a thread about it( https://forum.xda-developers.com/mi-a2/help/low-speaker-volume-sound-installing-rr-t3927310) and still no one has replied. So if you can help me please also do check out that thread. I'm new to XDA so I'm directly pasting the link here. ? Thanks

cant help you there undortunatly, i havent installed the rr on mine... ever.. maybe search the thread whre you found the rom, high chances someone ran into the same issue and might know how or if it can be fixed...