I've found a way to register the G1 in the initial registration screen that comes up the first time you boot the phone (or after you wipe the phone). It will allow you to register if you don't have a sim card at all, or if you have a sim card but no data plan.
First, You must have either RC29 or earlier, or modded RC30. It won't work with official RC30, sorry. If you don't know for sure what version you have, but you know you haven't installed a modified RC30 build, then the easiest way to check is to reboot the phone, and once it starts up and is showing the "click the android to begin" screen, or the "no sim card" screen, then type the following on the phone keyboard
<enter>reboot<enter>
If it reboots, then you have RC29 or ealier. Otherwise you have RC30.
Second, you must have adb installed on your computer, and have the USB drivers installed, or at least ready to install when it asks for the driver when you connect the G1. See this page for details on how to get adb working: http://code.google.com/android/intro/develop-and-debug.html#developingondevicehardware
Third, you must have a wifi network that you can connect to.
There are too many possibilities to write specific step-by-step instructions for every case. So I will give an overview of the process instead. If someone else wants to write some specific instructions, that would be welcome
-----------
When you start up the phone without a sim card, it goes into a locked screen that says "no sim card found", and you can't even get into the registration app. So the first step is to get around that screen. You have to connect to your phone with adb shell and get root access, and then type the following command:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO system (name, value) VALUES ('device_provisioned', 1);"
And then reboot the phone. When it starts up again it will go into the registration screen instead of the locked "no sim card" screen.
This assumes that you have the sqlite3 binary on your phone. This binary is provided in RC30 v1.2. Alternatively, you could manually copy the binary to your phone with adb push, or put it on the sdcard and copy it to your phone. I can post a copy of just the sqlite3 binary if needed.
-----------
The second step is to enable and configure wifi, so that the registration process can connect to the google servers. In an adb shell session, type the following command:
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
This doesn't have to have root access to work. It works fine with the "shell" user that adb on non-modded phones runs as.
That command will bring up the settings page on your phone. From there, you can enable wifi and connect to your wifi network, and then proceed with registration as per normal
------------
A few tips and tricks:
- If you have an official RC29 or lower phone, type the following command on the phone keyboard to enable adb:
<enter>setprop persist.service.adb.enable 1<enter>
- If you need to get root access on an official RC29 or lower phone, while it's at the registration screen, or the "no sim card" screen, enable adb (see first tip), and then type the following command on the phone keyboard:
<enter>telnetd<enter>
Now, copy a busybox binary to /data/local/busybox with adb push, and then connect to your phone with adb shell, and give the busybox binary execute permissions (i.e. chmod 755 /data/local/busybox)
busybox has a telnet applet, so you can do:
busybox telnet 127.0.0.1
to get a telnet session with root access.
- If you don't want to register the phone at all, you can set the app.setupwizard.disable property to 0 to prevent registration. Once you have an adb shell session open, type the following:
setprop app.setupwizard.disable 1
and then reboot. once it loads back up, it should bypass the registration screen all-together.
But beware, the phone seems a bit glitchy if you don't have it registered. For example, the home button doesn't seem to work. And you can't access the market or any of the google apps of course.
(Note: the following was the previous way to skip registration. I'll keep it here for informational purposes, but its easier to use the app.setupwizard.disable method instead of this)
- If you don't want to register the phone at all, you can edit /data/system/packages.xml and disable the registration screen. Add the following to the end of the <package> section for com.android.setupwizard, and then reboot:
<disabled-components>
<item name="com.android.setupwizard.SetupWizardActivity" />
</disabled-components>
so the full <package> would look something like below after the modification:
<package name="com.android.setupwizard" codePath="/system/app/SetupWizard.apk" system="true" ts="1217592000000" userId="10010">
<sigs count="1">
<cert index="0" />
</sigs>
<disabled-components>
<item name="com.android.setupwizard.SetupWizardActivity" />
</disabled-components>
</package>
He worked on this for a very long time with me and walked me through all the steps when testing this out. Great person.
Really nice...
I'll try to do it.
I have to study though...
I'll be in touch.
Thanks
thanks JF you are good in this thing.
My case i have sim card without data plan, when turn on phone show me screen for register email account with google.
c:\adb shell
show me # simbol
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
and in the phone show me the menu for connect to my wireless
conected, registered, go ahead.
thanks
satru, in what screen are you typing "c:\adb shell"?
1. Before you click "the android"
2. while reading the agreement
3. When you can select "create" or "sign in" to a google account
4. Or later ? (where?)
Thanks
EDIT:
Ok, I hate to do that but:
I am completely stupid. I've been reading around xda-dev for hours and still can't find how to check what software I'm running. (prior or post RC30...)
In boot loader it says:
"DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.28
Sep 2 2008
Serial0"
Do I have RC30?
I couldn't get it out of bootloader mode, so I pulled the battery out.
Ok, my device was recognised and "installed" but no driver was requested.
I have read I need to do some settings from within the g1, but I can't, since it's not activated! (http://forum.xda-developers.com/showthread.php?t=443797&highlight=info)
When I issue the "adb devices" command, I get no recognised devices...
To cmavr, try entering the restore mode and see if the computer will detect it then. Is it automatically mounting the SD card onto the computer? If it is then you probably have RC19 which is good. Try removing the SD card and plugging the phone into the computer.
cmavr8 said:
satru, in what screen are you typing "c:\adb shell"?
1. Before you click "the android"
2. while reading the agreement
3. When you can select "create" or "sign in" to a google account
4. Or later ? (where?)
Thanks
EDIT:
Ok, I hate to do that but:
I am completely stupid. I've been reading around xda-dev for hours and still can't find how to check what software I'm running. (prior or post RC30...)
In boot loader it says:
"DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.28
Sep 2 2008
Serial0"
Do I have RC30?
I couldn't get it out of bootloader mode, so I pulled the battery out.
Click to expand...
Click to collapse
A quick way to check if you have RC30 is to reboot the phone, and then once it starts up and it shows the "click the android to begin" screen, type
<enter>reboot<enter> on the phone keyboard.
If it reboots, you have RC29 or lower. Otherwise you have RC30.
If you do have RC29 or lower, then you can use the first tip I posted to enable adb. Once adb is enabled it should ask you to install the drivers when you plug it in.
satru said:
conected, registered, go ahead.
thanks
Click to expand...
Click to collapse
Great! Glad it worked for you
Hi again, thanks for your reply.
I rebooted without sim card, no "click here to begin" appeared, just the "no sim card" notice.
I entered reboot and it rebooted! So this is good.
Now, with the phone connected, I type in terminal:
"[email protected]:/media/Docs/Android/tools$ ./adb shell
error: device not found
[email protected]:/media/Docs/Android/tools$ ./adb devices
List of devices attached
[email protected]:/media/Docs/Android/tools$ "
This is not normal, is it?
What should I do now?
(I also have a t-mobile sim card, not activated. It just came with the phone. I can go through the activation proccess (gmail account etc) but it can't complete as it's disabled)
cmavr8 said:
Hi again, thanks for your reply.
I rebooted without sim card, no "click here to begin" appeared, just the "no sim card" notice.
I entered reboot and it rebooted! So this is good.
Now, with the phone connected, I type in terminal:
"[email protected]:/media/Docs/Android/tools$ ./adb shell
error: device not found
[email protected]:/media/Docs/Android/tools$ ./adb devices
List of devices attached
[email protected]:/media/Docs/Android/tools$ "
This is not normal, is it?
What should I do now?
(I also have a t-mobile sim card, not activated. It just came with the phone. I can go through the activation proccess (gmail account etc) but it can't complete as it's disabled)
Click to expand...
Click to collapse
Did you try my first tip to enable adb?
johnny13oi said:
To cmavr, try entering the restore mode and see if the computer will detect it then. Is it automatically mounting the SD card onto the computer? If it is then you probably have RC19 which is good. Try removing the SD card and plugging the phone into the computer.
Click to expand...
Click to collapse
Thanks for your reply.
SD mounting works fine.
In recovery mode nothing is better... (tried recovery without sd only)
Is there anything else I should try?
JesusFreke said:
Did you try my first tip to enable adb?
Click to expand...
Click to collapse
What do you mean enable?
I should enable it on the g1 but it's locked, no menus available.
I thought the first step was to enter the "adb shell" command in the PC, then pass this through the pc to the G1:
"sqlite3 /data/data/com.android.providers.settings/settings.db INSERT INTO system (name, value) VALUES ('device_provisioned', 1);"
Am I missing something?
cmavr8 said:
What do you mean enable?
I should enable it on the g1 but it's locked, no menus available.
I thought the first step was to enter the "adb shell" command in the PC, then pass this through the pc to the G1:
"sqlite3 /data/data/com.android.providers.settings/settings.db INSERT INTO system (name, value) VALUES ('device_provisioned', 1);"
Am I missing something?
Click to expand...
Click to collapse
A couple of things:
- Look further down the post, there's a "tips and tricks" section. The first tip is how to enable adb.
- second, I don't think you need to go through the first step (the sqlite3 command). The first step is to get past the "no sim card" screen. You said you have a sim card, just no data plan, right? So you don't need to get past the "no sim card" screen . You can skip to the second step (once you get adb working, of course)
DID IT!
Thanks so much!!
I now have to wait for the unlock code so that I can also use my sim card...
Thanks both of you!
EDIT:
T-mobile sent me the unlock code although I was not a customer for even one day!
That's great...
Great! Glad you got it working
cmavr8 said:
EDIT:
T-mobile sent me the unlock code although I was not a customer for even one day!
That's great...
Click to expand...
Click to collapse
how?
thanks
xaxis said:
how?
thanks
Click to expand...
Click to collapse
Probably by getting lucky and getting a nice CSR
JesusFreke said:
Probably by getting lucky and getting a nice CSR
Click to expand...
Click to collapse
man thank god you are here,
do i need the SDK installed to get the adb?
thank you
Yes, adb is included in the sdk
Hi.
First time making a post here, but have been using stuff here for quite a while. Thanks so much to the community for all the amazing stuff being developed, ect, here.
To the question:
My father's girlfriend recently came into 100's of phones. All various sources, mostly OBF's (Out of box failures) from the stores under their management.
I need a way to retrieve the models of each phone as quickly as possible. Other things aren't necessarily a necessity, but things like IMEI numbers, ect, would be a big bonus.
I then need to sort this data in a spreadsheet, but I can do that manually if exporting the data from the phones is possible.
These are obviously not rooted, as they were maybe turned on, or used once or twice if that much, and rooting them definitely would be longer than just doing the first time setup and then looking in settings.
Thanks to everyone for reading!
Greetings from South Africa.
You can retrieve a phone's brand / model and IMEI by means of ADB:
Get brand
Code:
adb shell "getprop 'ro.product.brand'"
Get model
Code:
adb shell "getprop 'ro.product.model'"
Get IMEI
Code:
adb shell "service call iphonesubinfo 4 | cut -c 52-66 | tr -d '.[:space:]'"
jwoegerbauer said:
You can retrieve a phone's brand / model and IMEI by means of ADB:
Get brand
Code:
adb shell "getprop 'ro.product.brand'"
Get model
Code:
adb shell "getprop 'ro.product.model'"
Get IMEI
Code:
adb shell "service call iphonesubinfo 4 | cut -c 52-66 | tr -d '.[:space:]'"
Click to expand...
Click to collapse
Is USB debugging not necessary for Adb? Or is fastboot all that you require? Do all android devices have a fastboot or similar? As I said, it's a lot of phones and they aren't all the same, all kinds of brands from Samsung to techno sparks.
Think I clearly spoke of ADB and not of Fastboot.
Yes, USB-debugging must be enabled on a phone to run ADB commands.
jwoegerbauer said:
Think I clearly spoke of ADB and not of Fastboot.
Yes, USB-debugging must be enabled on a phone to run ADB commands.
Click to expand...
Click to collapse
My apologies. I’m a computer technician. Don’t usually play with phones, except for the normal rooting devices from time to time (following guides ect.) So I’m not all that clued up yet.
Enabling usb debugging still means turning the device on, first time setup, enable usb debugging, use adb to get data.
Might as well just write down the model from “about” at that point and leaving the other less necessary data completely.
Any other ideas or is that the best we can do? In which case, thank you for the suggestion.
Is there perhaps a faster way to enable usb debugging?
AFAIK to access a phone's "About" screen it's not required that USB-debugging is got enabled on phone.
I am working with the wear OS sample watch faces. I can get them to run on the emulator but I can't seem to connect my watch 4 to run them on the watch. From my research I think it could be an issue with "abd" and doing something in the terminal but I've been unsuccessful. Another thing I noticed and I'm not sure if it's relevant, is that when I connect my phone with USB there is a caution symbol next to it that says warning missing watch. But I'm not sure if that's relevant. Can someone assist with connecting the watch 4? Any help is appreciated.
What happens when you try to connect with adb with the command line? Have you turned on adb debugging and wifi debugging in the developer options?
I have adb debugging on and debugging over wifi on with both phone and watch. But I don't know how to connect with abd in the command line. Can you explain the command?
Check the IP address of the watch, then type:
Code:
adb connect IP_ADDRESS
Then check your watch to accept the connection. Scroll down to allow permanent permission if you prefer.
You know this Video?
Maybe it helps...
Best Regards
Thank you both, I feel like I am doing something wrong with the abd command. Maybe the original file path is wrong, I am attaching a screen shot. How do I change that if that is the case? Sorry I am not a coder but I want to learn.
Mike2601 said:
Thank you both, I feel like I am doing something wrong with the abd command. Maybe the original file path is wrong, I am attaching a screen shot. How do I change that if that is the case? Sorry I am not a coder but I want to learn.
Click to expand...
Click to collapse
Make sure you have adb installed, then navigate to it's folder and run it from there. For myself the path is:
C:\Users\MY_USERNAME\AppData\Local\Android\android-sdk\platform-tools
Outch this makes pain in my eyes... I can not read...
A
ADB
B
Easier if short readable and knowable path to ADB...
Example...
I have my ADB files in
Code:
Android/ADB
For you maybe better to copy ADB files into C... ADB folder...
Code:
C:\adb
Best Regards
adfree said:
Outch this makes pain in my eyes... I can not read...
A
ADB
B
Easier if short readable and knowable path to ADB...
Example...
I have my ADB files in
Code:
Android/ADB
For you maybe better to copy ADB files into C... ADB folder...
Code:
C:\adb
Best Regards
Click to expand...
Click to collapse
Agreed. I was having issues with it installed in a location other than the default, so I just made a shortcut to the folder so it doesn't have to be typed out every time.
Ok I have it connected with the adb command, thank you for being so patient. But for some reason it times out and never loads onto the watch when I run the app. It says it loads and I press and hold the screen to look for a new face loaded but nothing new is there. I have attached a screen shot where it then shows it timed out.
I am also attaching a screen shot of getting it to load onto the emulator, I just did that now after it timed out trying the watch.
ADB command is under CMD(run as admin) in windows. Before connect comand line you have to navigate to folder wher is adb program. Both pc and watch have to be on same local network. On the watch go to con exion menu and chech always connect to your wireless network. From this menu you get local ip and adress and use it in adb connect comand line.
Hi ,
i made a batch file to connect the watch..
Put it in the adb program directory, just change the IP address with port number (192.......: port number). Run it as administrator. Look at the watch to accept. Then the watch is enable in Watchface studio.
So I tried to get back to my old Lenovo tab which I haven't used in like 2 years. But I forgot the pin code. I don't know its android version and don't know the model either. But when connected to my laptop, it shows Lenovo TB-8704V.
Speed Test https://vidmate.bid/
I tried various methods suggested on the internet but they haven't worked. I don't use any 3rd party lock screens so safe mode doesn't do anything, I have no emergency call buttons, android device manager doesn't list my tab to unlock it, factory reset wipes the photos in them which I need. I don't know anything about ADB software but I'm pretty sure my tab has USB debugging enable but I'm not sure about OEM something settings and whatever the case, typing in adb says adb isn' recognized in the command prompt. I went to a site to download ADB and extracted the downloaded file and ran adb.exe but it didn't do anything.
So, can you help me out here?
First thing unlocking bootloader without reset is same lime entering the room without opening the door
Second thing to run adb command you must use ./adb "command"