Database Info

Trying To Register Without a Data Plan (apparently) But...

I need to know more about ADB I guess, like how to get it to stay open when I double click the app if thats even how I open it. Instead the window keeps closing as soon as it opens.
My friend (the one who owns this forum account) just downgraded my G1 from RC33 to 29 and now its asking me to sign in but I can't. Apparently my girlfriend can't either on her phone and we didn't do anything with hers but I just signed her in through wifi since it wasn't on the setup screen like mine was. I on the otherhand am stuck at the beginning and need a way to get around it, I don't know why we lost the data plan we had all of a sudden but I'm not going to bother with that and instead will keep moving forward with an alternative.
I'm completely noob to all things command promp so I don't know what an SDK is, just found out what the ADB is and dled that and the drivers but can't start anything up as of yet. I know my android is at RC29 because of the reboot test on the how to bypass the registration thread.
EDIT: Lmfao I guess I picked a bad time to modify my G1, at the time of this post there is a global outage of T-mobile's internet, everything west of the mississippi river is out so thats why I couldn't sign in before, if this thread gets locked or ignored then its ok, I can just wait it out, but just goes to show murphy's law is the real deal, the day I decide to finally start editing stuff this happens.

I'm not really an expert and I had to learn as I went, but here's how I went through the same problem.
Basically, you don't run ADB as a normal program, you open a command prompt (for vista and xp go to run and type cmd) and then you have to navigate to the folder that ADB is in, so if you have the SDK on your desktop youd type something like
"cd c:\users\yourusername\desktop\SDK\tools" (for vista)
yours will probably differ, but use "cd" to navigate to the folder ADB is in. Then assuming you have your phone and the drivers setup properly, when you're navigated to that folder you can type commands that start with adb or whatever and they should work.
If that doesn't work then your phone may not be setup properly, in which case you need to follow the steps in the registering without a data plan thread, although I had a sim so I skipped the disabling of the insert sim screen. The rest is fairly simple, assuming you've got past the insert sim screen somehow you need to type on your phone
<enter>setprop persist.service.adb.enable 1<enter>
I did this in the email box of the signup so you can actually see what you've typed because you won't know if it's worked until you actually try it. After that again type
<enter>telnetd<enter>
which will allow you to get root access to the phone temporarily, then we connect to your phone from your computer.
In a command prompt on your computer do what I said up top by navigating to the folder ADB is in (c:\users\yourname\desktop\sdk\tools or whatever depending on which version of windows you're on and where the SDK is) and type
adb shell
this will probably say the daemon is not currently running, start the daemon etc.... this is good. If it then gives you a hash (#) at the start of the line you are now accessing your phone from your computer. If not, type
adb devices
and see if it gives you anything under where it says "List of devices attached" in the command prompt. If not it's not recognising your phone so you need to get it to do that first.
Last step when you have this, on your computer type
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
which should bring up the page on your phone to enable and manage wifi connections... Connect to your wifi like normal, check it says connected on the settings page and press back and you can register over your wifi.
Hope this helps, I'm no pro but this is how I did it and it worked fine.

G1 Security

Hi all,
I notice on t-mobile (uk) you are accessible to all other t-mobile users on their internal 10.x.x.x network.
I have two sims and can shell from my home machine into my G1 wherever it is and vice versa (which is great, but...)
However this also means other people can too, and I notice the JF image I'm currently running (1.41 - rc8) is permanently listening on port 5037 (i.e. adb)
ADB is a debugging tool, my hunch is this wouldn't be too hard to crash, and leading on from there to run an exploit on it.
adb is of course running as root, so if exploited it's game over....
all in all, I'm rather concerned some 1337 HaXor is gonna take over my phone.
sure I can kill adb, but it would be nice to not have it running at all unless asked for.
Can I remove it from a startup script somewhere?
TOP TIP, make sure when rooting your phone you don't leave telnetd running else you are asking for trouble!!!!!!

I'm surprised no one has commented on this matter yet (I noticed it this morning.)
This is truly something that T-Mobile would have to fix on their end. I haven't had a chance to try it out today, but when my brother gets here I'll be sure to give it a shot (he has a G1 as well.)

I haven't tested this, so I can't vouch that this is an accurate description of how the system behaves.
However, adb should ONLY listen on the usb port. Listening for an adb connection on an internet-facing interface is just crazy.
I don't see adb running as non-root being a big help either. You can still compromise most of the personal data on the phone and run almost arbitrary commands on the phone as non-root. You just can't change the system image.

[Q] Converting old Android phone into simple image displayer

Is there a way to change the Android display programmatically from a PC via a USB cable? I have an old phone, Samsung Moment, that I would like to convert into a simple display device. Ideally I would be able to send it properly sized and formatted image files and have the phone simply display the image fullscreen. I am able to use ADB to send and receive files to the phone, but the phone is not yet rooted. If rooting is required, then I guess I'll do that first. Is there an app for this already or is it something that can be done simply by issuing ADB shell commands, sending files into the right places? Also, I would of course need to turn off the automatic screen lock. The phone should not need to respond to any input; it would just be a display device. Is all of that doable via some app or is this something requiring specialized ROM's? If so, what are my options?
Thanks!

fastboot driver for mac

for about two weeks, i've attempted to root the n5 using a mac. i have android sdk installed and fully updated. I've tried three different macs, one on mountain lion and two on mavericks. No matter what, adb can see the device when its fully booted. fastboot nor adb can see the device when it's in fastboot mode however.
i've mentioned this several times in the chainfire and chromium threads, but the only responses i get seem to be assumptions that every android device ever will work on mac without drivers, when clearly on 3 different macs i have fastboot not seeing the n5 in fastboot mode. when i ask if anyone has ever seen a mac see the device in fastboot mode there is nothing but silence. is it true this device has never been rooted on a mac? is it impossible (no assumptions please; if you haven't seen it work, don't spread the lie that it is possible)?
If the myth that this is possible stops getting spread, maybe i'll buy a windows pc solely to root. This is a cruel lie to spread that it's so simple when the poster has never seen it happen before though.

That's really strange. I rooted my old N4 on my mac mini at home, and my N5 on my iMac at the work.
What message do you see when you use ./fastboot devices?

@Blario i rooted it on a mac, no driver needed..you only need the sdk or fastboot and adb executable
post a screenshoot of the error, will make everything more easily to solve
also in fastboot mode, you can't use adb as you mentioned..in fastboot mode you can only use fastboot commands

Thanks so much for the replies! You're the first two people I've seen actually saw they've seen it work.
I went to get another failure result, so i could copy the screen exactly and paste it here, and omfg it worked.... After two weeks of fail, it finally worked. For hours I couldn't figure out why. Then when notifying another thread that it finally worked, it came to me. My Little Snitch was accidentally turned off this morning. I think that must have been it. I've noticed that adb uses network ports for communication... so much pain and finally success. Don't know whether to cry or jump for joy.

Can't access broken screen OPO, adb not working

Recently my OPO's screen cracked for the second time in half a year, and because of the ridiculous screen prices I've decided to not get it fixed this time.
But, I do want to get all my data and grab some other stuff from the phone before I discard it. I came across a tool by k.janku1 that does exactly what I need right now. I installed adb, sdk, intel android drivers and the tool itself but realised that USB debugging probably is not enabled on my phone. This post proposes a workaround for that, but that doesn't seem to work. Running adb shell comes up with an error and adb devices gives me an empty list. Is there a solution to this?