Database Develop

Please Help

Ok i have an g1 thats unregistered and i kow how to activate it through wifi but i cant because i dont have an router i was wonder if someone could explain to me how to bypass this without activating my g1 it said or how i send these commands with adb
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 i am so confused thanks for the help

Do you have root? Most custom ROMs give you an option to skip.

i was in the process of rooting my g1 when i had downgraded it but i couldnt finish it because i had to activate it when i got it it was already activated

charles20212 said:
i was in the process of rooting my g1 when i had downgraded it but i couldnt finish it because i had to activate it when i got it it was already activated
Click to expand...
Click to collapse
It's been so long since I rooted that I can't remember if there are any other options. I think when first I got mine, there was no way to root with wifi. I couldn't even register while roaming, and had to drive 40 miles (nearest T-Mo tower) just to use my G1 for the first time. That sucked!

is there a way to bypass it without using wifi or can i install a new rom or something

If you are rooted, then try a new rom. Most of them will have the option to skip.

how i know if im rooted

Help is appreciated.

Ok so this all started 7 hours ago.
I did a factory reset and I couldn't get passed the gmail account login. I tried multiple times, and tried resetting. Didn't work.
So I looked online to see if I can use wifi, and I could.
http://modmygphone.com/forums/showth...1891#post51891
I updated my drivers, downloaded Android SDK.
I got up to the part where I type " adb shell "
It says no devices found. Please help. Thanks in advance :]
Currently I am in stock ROM RC29.
I am trying to do this on the site above:
"6. Now type this on your G1 keyboard..
<enter>setprop persist.service.adb.enable 1<enter>
7. Now.. Open the command prompt on your PC ( Start > Programs > Accessories > Command Prompt )
8. Type "adb shell" without the quotes.
(Just in case typing that doesn't do anything.. Navigate to the folder you've unzipped the ADB Files and type there instead)
9. Then when the '$' comes out .. type this:
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
9. Take a look at your G1 and now it'll be in the WiFi settings section. Configure it.. Connect to your network.. And done!"

I find this guide:http://forum.xda-developers.com/showthread.php?t=532719 much easier to follow
the code
cd C:\android-sdk-windows\tools needs to be typed in the cmd before typing in adb shell.

thanks for the guide, but I followed what you said/the guide said, still the same result =/

TmobileDash12 said:
thanks for the guide, but I followed what you said/the guide said, still the same result =/
Click to expand...
Click to collapse
Do you have the android-sdk-windows file on the root of your C drive?

Debugging
Did you make sure to add a path for adb in the environmental variables tab on the pc, and also make sure that usb debugging is checked off in the settings>applications>development tab.

It is in my C drive or root folder.
I can't access settings because my phone's stuck on the login screen.

ABSOLUTELY cannot root this G1!

The G1 is a loan from a friend, they want me to help fix it.
I get to the final part here in the list of rooting the G1:
10. The Final step is to type
"am start -a android.intent.action.MAIN -n com.android.settings/.Settings"
After I do that, in ADB all I get is this sign >. I get no settings menu popup in the phone at all. It stays at the no sim card / emergency calls only screen.
Fixing the phone for a friend - absolutely no way I can obtain a sim to get past this - no sim card at all. Its a fresh downgrade to RC29 to begin the root.
The reboot command works on the phone perfectly. ADB recognizes the device. Permission Denied in ADB when trying to SU.
I need to be able to bypass the activation AND the No Sim / Emergency calls only screen, thats my goal, to root, and install recovery and finally cyanogen.
Do have experience with ADB. Is definitely installed properly. Driveres are definitely in right.

havocxrush said:
The G1 is a loan from a friend, they want me to help fix it.
I get to the final part here in the list of rooting the G1:
10. The Final step is to type
"am start -a android.intent.action.MAIN -n com.android.settings/.Settings"
After I do that, in ADB all I get is this sign >. I get no settings menu popup in the phone at all. It stays at the no sim card / emergency calls only screen.
Fixing the phone for a friend - absolutely no way I can obtain a sim to get past this - no sim card at all. Its a fresh downgrade to RC29 to begin the root.
The reboot command works on the phone perfectly. ADB recognizes the device. Permission Denied in ADB when trying to SU.
I need to be able to bypass the activation AND the No Sim / Emergency calls only screen, thats my goal, to root, and install recovery and finally cyanogen.
Do have experience with ADB. Is definitely installed properly. Driveres are definitely in right.
Click to expand...
Click to collapse
I think there's a newer dreaimg.nbh file available that allows you to skip activation. Do that and install the 1-click-root app and be happy.

Nah I cant find it after tons of looking around. I just need to get that settings screen to pop up. But nothing........

havocxrush said:
The G1 is a loan from a friend, they want me to help fix it.
I get to the final part here in the list of rooting the G1:
10. The Final step is to type
"am start -a android.intent.action.MAIN -n com.android.settings/.Settings"
After I do that, in ADB all I get is this sign >. I get no settings menu popup in the phone at all. It stays at the no sim card / emergency calls only screen.
Fixing the phone for a friend - absolutely no way I can obtain a sim to get past this - no sim card at all. Its a fresh downgrade to RC29 to begin the root.
The reboot command works on the phone perfectly. ADB recognizes the device. Permission Denied in ADB when trying to SU.
I need to be able to bypass the activation AND the No Sim / Emergency calls only screen, thats my goal, to root, and install recovery and finally cyanogen.
Do have experience with ADB. Is definitely installed properly. Driveres are definitely in right.
Click to expand...
Click to collapse
go here it is the best place to root your g1 I use it for everything, it is da bomb
http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/

That requires adb to be enabled, which I believe it is NOT enabled on a tmobile firmware.
There was another sort of bug in the tmobile firmware... stuff you type might just be run in a console as root. I don't recall if it applies to where you're stuck, but it might... I think it is... try this:
Flip open the keyboard and type this: (don't worry that it doesn't show up on the screen)
<enter>sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO system (name, value) VALUES ('device_provisioned', 1);"<enter>reboot<enter>
Where "<enter>" is actually pressing the enter button.
It should reboot at this point and hopefully it will come up to the REGISTRATION screen instead of the NOSIM screen.
Then type:
<enter>am start -a android.intent.action.MAIN -n com.android.settings/.Settings<enter>
(again, won't see anything, so just type very carefully...)
If all works as planned, this should pop up the settings program, you can go into network and activate WiFi, press the <back> button a few times to return to the REGISTRATION screen, then you should be able to register (if you want). Or, when you activate the wifi, you could just type in <enter>telnetd<enter> and log in through telnet, root, and be happy.
Note: I believe that you can enable adb using this command:
<enter>setprop persist.service.adb.enable 1<enter>
** if you do this, then you can do the other two commands I showed you over adb rather than blind.

chris6551 said:
go here it is the best place to root your g1 I use it for everything, it is da bomb
http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
Click to expand...
Click to collapse
That isn't going to work for him since he doesn't have a simcard.

oh ok I didnt realize he did not have a sim card, my bad.

Without a SIM card, you're pretty SOL. It has to be in RC29 or RC7 firmware to be able to access the WiFi via that vulnerability, so you'd have to start there. I don't know how far you can get with SIM message, though.

Well, just search the development on this forum you can do anything even if you don't know how, and my last g1 i had to pass everything like you then root then unlock and done alll of that and now runing flawlesly. Don't be afraid of searching. And p.s. you don't need a sim card for anything after passing the login screen.

Ninjineer said:
Without a SIM card, you're pretty SOL. It has to be in RC29 or RC7 firmware to be able to access the WiFi via that vulnerability, so you'd have to start there. I don't know how far you can get with SIM message, though.
Click to expand...
Click to collapse
It is a really good idea to read through the entire thread before responding and making yourself look *really* foolish.

adb insufficient permissions

I've had a MT3G for awhile and just upgraded to a Nexus One. I still have my old phone and can use adb with the MT3G without any issues. When I try using adb with the Nexus one i receive an error insufficient permissions on the device. Here's some more info about my setup:
Nexus One:
Clockwork Mod Recovery
CM6.0.0RC1
USB debugging is enabled
Computer:
Ubuntu 10.04
I have the rules set up for adb
I have tried remounting and restarted adb with root permissions and have still receiving the same error. I've tried connecting to another Ubuntu box and a windows xp box with the same error.
Any help?

What response (if any) do you get to the "adb devices" command?
What exact command are you trying to execute when you get that error?

When i run adb devices i receive this:
List of devices attached
???????????? no permissions
adb shell gives this:
error: insufficient permissions for device
I receive the same output running the commands as user or superuser. I've also killed and started the server as user and root. Remember I'm running the udev rules so I can run these commands as user.
Today I went ahead and reflashed my phone. I downloaded cm6 from xda and frf91 from the same post. Checked the md5sum for the update and then wiped and flashed.
Even after the wipe I'm in the same spot.

Can you access the device via fastboot?

When I first got the device I used fastboot to unlock the bootloader.
now the command
Code:
fastboot reboot
hangs at
Code:
< waiting for device >
I can still reboot the device into recovery and fastboot.

another update.
I rebooted into recovery (holding trackball and power) and tried running fastboot devices. It found my phone. While fully loaded it normally displays nothing.
adb devices is still blank but I'm not sure if it's supposed to work while in recovery.

last thoughts, as it's been a while since I've used adb on Ubuntu...
Code:
./adb kill-server
./adb start-server
./adb devices
???
./PROFIT
It seems to be somehow an issue with your local adb set up, not anything phone-related. Could even perhaps be a driver issue.

raim1312 said:
another update.
I rebooted into recovery (holding trackball and power) and tried running fastboot devices. It found my phone. While fully loaded it normally displays nothing.
adb devices is still blank but I'm not sure if it's supposed to work while in recovery.
Click to expand...
Click to collapse
Yeah, should've pointed out that fastboot will only work while in fastboot mode
trackball + power == fastboot, btw.
volume_down + power == hboot, which will let you boot into recovery
trackball + volume_down + power == three-finger salute, the equivalent to CTRL+ALT+DEL

i get the same results after killing and starting adb either as user or root. i'll pull out the drivers and android sdk and reinstall. i'll let you know how it goes once its done

codesplice said:
Yeah, should've pointed out that fastboot will only work while in fastboot mode
trackball + power == fastboot, btw.
volume_down + power == hboot, which will let you boot into recovery
trackball + volume_down + power == three-finger salute, the equivalent to CTRL+ALT+DEL
Click to expand...
Click to collapse
Yeah sorry about that one. i'm still a newb but willing to learn

i just reinstalled the android sdk and removed the udev rules. gave my pc a reboot and killed then started the adb server.
same issue.
to verify adb was working i plugged my gf's mt3g in and adb found it.
i've never need to reinstall usb drivers in anything but windows so honestly I don't know how to do it in ubuntu. can you point me in the right place?

I'm afraid I'm out of ideas then. I've only had very limited experience using adb on my Ubuntu install

well thanks for all the help codesplice.
i'll keep looking and post anything i do here.

raim1312 said:
well thanks for all the help codesplice.
i'll keep looking and post anything i do here.
Click to expand...
Click to collapse
Please do. Everything that I was able to find on google relates to a screwy adb server... but being able to adb on another device complicates things. Very interested to see what you figure out on this.

I installed the rom froyou frf50 with radio from here:
http://android.modaco.com/content/g...ed-update-zip-no-radio-option-online-kitchen/
didn't work.
while looking into returning the phone to stock i received an ota update. so i ran it.
the update failed during a signature check.
i tried to follow the instructions here to return to stock: http://androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
only issue is fastboot will not find my device.
performed a nandroid restore to go back to cm6 frf91.
fastboot still will not find my device.
i'm at a loss here. the device is usable for everything but adb. and adb is the main thing i need. i dont' want to keep whacking at this and cause more issues.
any ideas are welcome. all my data is backed up and the bootloader is already unlocked.

its... working??? i finally got adb to recognize my device.
first i restored the phone back to stock using this: http://forum.xda-developers.com/showthread.php?t=717870
then i replaced the cable i was using for one from a Motorola droid. (since the mt3g has a different usb port i had to use a different cable).
then i ran the adb kill and start server commands as root. and voila. it works.
i remove the cable and go back to the one that came with the phone and it still works. not sure what happened but adt is working as well. so im back up and running. i wish i knew the cause of this frustration but i fear i will never know. anyway thanks for all your help!

Yikes.... take your boat back!!!
Perhaps you ran chmod u+s on adb?
Edit: Yep, that was the problem for me..
I don't know the commands to well, so i just right clicked adb and went to permissions and removed set uid.
seems adb needs started from root, but making the file always run as root doesn't work so well.. I thought it would fix my annoyances with eclipse starting adb with not enough permissions. Perhaps ill chmod u+s eclipse instead.
Oh and btw... nexus one can kiss my a$#. HTC Hero!!

Solution for permission problems:
http://wiki.cyanogenmod.com/index.php?title=Udev

stock firmware: stuck on android logo

I've not found any usefull manual to skip the android logo after booting (android 1.5), I'm stuck, can I install another bootloader without root (guess not) ? Maybe I'll better sell the phone, with cm I never had this kind of problems.

You could try flashing an upgrade/downgrade in fastboot(power + camera); you could root it afterwards.

Decimae said:
You could try flashing an upgrade/downgrade in fastboot(power + camera); you could root it afterwards.
Click to expand...
Click to collapse
ori bootloader: couldn't do that.
I got past the homescreen:
on adb: am start -a android.intent.action.MAIN -n com.android.settings/.Settings

robuser007 said:
ori bootloader: couldn't do that.
I got past the homescreen:
on adb: am start -a android.intent.action.MAIN -n com.android.settings/.Settings
Click to expand...
Click to collapse
Maybe you should spell out what, EXACTLY, you have on it and how it got there.

lbcoder said:
Maybe you should spell out what, EXACTLY, you have on it and how it got there.
Click to expand...
Click to collapse
really don’t you just have to:
1. go to rc29
2. on “click android” part setprop persist.service.adb.enable 1
3. on adb: am start -a android.intent.action.MAIN -n com.android.settings/.Settings
1. Just put in whatever SIM you are using, then on the activation screen, hit Menu then click on APN. Click add APN and put your company’s internet settings in (ask your provider for these settings). Then add the data plan to your account for the day and remove it after you have activated the phone OR get a friend with a data plan to activate it for you.
The following procedure can be used if none of the above are available to you…
I. Getting Back to RC29
1. This procedure requires you to be on an old version of Android (RC29 aka Android 1.0) so you must use our unroot procedure first and get to RC29, DO NOT DO THE STEP THAT TAKES YOU BACK TO CUPCAKE, skip it and come back to here once you are on RC29.
How To Get Back to RC29
2. You also need a WiFi connection to do this procedure.
II. Setting Up ADB
1. After you are back to RC29, follow our How To Setup ADB procedure EXACTLY as it is written. Once you are able to see your phone’s serial number after typing ADB devices in the command prompt, then come back to this procedure.
IIIa. Activating the Phone Over WiFi WITHOUT a SIM.
1. Borrow someone’s SIM card then procedure to Section IIIb.
IIIb. Activating the Phone Over WiFi WITH a SIM but No Data Plan.
1. Turn on the phone, you will get a Touch Here to Begin Screen.
2. Open the phone’s keyboard and hit enter once then type the following on the phone’s keyboard:
setprop persist.service.adb.enable 1
3. Then hit enter.
4. Hit enter AGAIN and type the following on the phone’s keyboard:
telnetd
5. Then hit enter.
6. With the phone still plugged in and the command prompt still up on your computer screen from the ADB process, type the following in the command prompt on your computer with hitting an enter at the end of each line:
cd\
cd c:\AndroidSDK\Tools\
adb devices
*this should bring up a serial number if your phone is connected, if not then redo the setup ADB process.
7. Now, in command prompt on your computer, type the following with hitting enter at the end of each line:
adb shell
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
8. On your phone should pop up the Android Settings screen, you can now choose a Wifi network to connect to then hit back and finish the activation process over Wifi. Enjoy!