Database Develop

Root G1 with Latest update

Hey guys I have a stock G1 that was given to me and I can't access the wifi settings thus I cannot sign in. I believe I have the latest update. Anyone know a way around this?

http://forum.xda-developers.com/showthread.php?t=452316

B-man007 said:
http://forum.xda-developers.com/showthread.php?t=452316
Click to expand...
Click to collapse
Does not work with the very latest AOSP update : (

cars1106 said:
Does not work with the very latest AOSP update : (
Click to expand...
Click to collapse
You need to root your phone.....Read the stickys at the top of this section to learn how

It has been rooted before. then I unrooted it gave it to someone to use, it got updated and I don't have a sim with data and now I can't do anything with it. I guess I will have to downgrade via SD stick somehow through the recovery menu and try and run the exploit again.

if your one of those one-click rooters....your out of luck
you will have to root the old fashion way.....hint: RC29 DREAIMG.nbh

B-man007 said:
if your one of those one-click rooters....your out of luck
you will have to root the old fashion way.....hint: RC29 DREAIMG.nbh
Click to expand...
Click to collapse
Yup, I had the same issue, downgrade to RC29, then follow this:
**Originally Posted by dizzydevil111**
please make sure you have rc29 or lower by typer (enter)reboot(enter)
if the phone reboots then you have rc 29 or lower.
if not, follow this guide to downgrade to rc29
2. Mount your SD card in Windows and reformat it as FAT32. The HTC
bootloader won't be able to see the RC29 (or RC7) image otherwise. Make
sure you back up all your files first!
3. Download the appropriate image (RC29 for USA or RC7 for UK) from
http://koushikdutta.blurryfox.com/G1/DREAIMG-RC29.zip or
http://koushikdutta.blurryfox.com/G1/DREAIMG-RC7.zip . This is a DOWNGRADE
to the Android version that contains a root shell bug (this exploit just
seems too easy). I got these files from the forum thread
http://forum.xda-developers.com/showthread.php?t=442480 .
4. Extract the DREAIMG.nbh file from the downloaded zip archive and copy it
to your SD card (again, for me, this had to be formatted as FAT32, not just
regular FAT which is the default). Don't put it in a folder, just stick it
directly on there.
5. Disconnect the SD card the right way (eject, unmount, or otherwise tell
your OS you are unplugging it) to make sure the data gets written. If you
used an SD card reader, put the SD card back in your phone.
6. Make sure your phone has a full battery, then turn it off. Turn it back
on by holding down the CAMERA and POWER buttons. This should get you into
the HTC bootloader (the funky red, green, and blue screen).
7. If everything was done correctly, the bootloader will detect the image.
You'll be taken to a different screen that asks you to press the POWER
button to install the image. Do this, but beware, you will lose all your
saved data on your phone (with the exception of things that are synced with
Google's servers, like contacts, calendar, Gmail, etc.).
8. Wait for the update to complete. The progress bar will fill up, then
all the steps will say OK beside them, and finally, it will ask you to press
the "action key" (I think this means click the trackball). DO NOT do
anything until you see this message. The progress bar needs to DISAPPEAR,
not just fill up.
9. You now have the stock RC29 installed. Take out the battery, put it
back in, and turn on your phone. It should ask you to activate your Google
account again -
once you have this done type on the phone again (enter)setprop persist.service.adb.enable 1(enter)
your pc should now pick this up as an android adb device
point it to the correct drivers found in the file called androidusbwindows
once that installs, extract the adb file anywhere on your pc. (best place is root directory)
open up a dos command prompt and type (cd ..<enter>)
then type (cd ..<enter>)
then type adbshell
should look like this thereafter
$
referring to the dollar sign
then copy the following line into your dos command prompt and press enter
(am start -a android.intent.action.MAIN -n com.android.settings/.Settings)
please make sure that you copy the contents of adbwin.zip in your ROOT FOLDER or else you will be going through hell
voila you should be able to access wifi
pm me if it worked for you

My G1 is stuffed, but not bricked. Mount from Recovery? Wave invites for help.

Ok. So yesterday night I was trying to give my G1 a new ROM. I wasn't really concentrating. I was tired. I've done it successfully before. I was following the instructions on Cyanogen Wiki for phones already with custom SPL and OTA.
Something screwed up, I did the firstROM a while ago so it probably wasn't the right one. Maybe it needed deathspl.
Regardless, it is now stuck on the T-Mobile G1 screen (and its stuck, I've left it for an entire night: still stuck) . I can take out the battery and boot into recovery mode. So at this point I basically need to mount my SD through USB (i dont have adapter) so I can start from scratch with SPLs, Radios and Images. This is the problem.
I've read you can do it by pressing Alt+X, going into console/terminal and type some commands in. I press Alt+X but nothing happens. I'll tell you what happens when I do other things:
---------
Alt+S= E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (Invalid argument)
Can't mount sdcard
Alt+A= <<same thing except for last line:>> E:Can't mount SDCARD:
Move apps+dalvik-cache to SD: Error: run apps2sd via adb
Apply sdcard:update.zip: Can't mount sdcard
Apply sdcard:choose zip: E: CAn't mount SDCARD:
Wipe data/factory reset: Data wipe complete.
Nandroid v2.2 backup: Can't mount sdcard
Nandroid v2.2 restore: Can't mount sdcard, aborting.
Format SD : fat32+ext2+swap: Format complete!
Format SD : fat32: Format complete
Repair ext filesystem: Error : run e2fsck via adb!
Convert ext2 to ext3: Error : run upgrade_fs via adb!
Fix package uid mismatches: Error : run fix_permissions via adb!
-----------
Alrighty. So its royally stuffed up.
Please help! I'm telling myself its not bricked, because it has small but definite programs and calculations running.
It mentions adb, and I have used it in the past to skip through a tutorial (back when you couldn't skip through it) because it needed internet connection and at the time I didnt have data transfer on my SIM, but I did have Wireless. How exactly I did this escapes. Do I need to download anything?
I have no idea if this helps, but I was trying to think of a sort of prize for anybody to help and I have Google Wave invites. Whether thats a big deal or not, I have no idea.
Please help!

Well you can assure yourself that you are not bricked.
First check your SPL and Radio.
If they are:
SPL=1.33.2005
Radio=2.26.19.26I
then your good in that area.
you just need to wipe everything and retry the ROM.
If not then you might want to get the latest stuff and try again that way.

Thanks
Thanks.
But how do I check?
I can't get into the proper Android OS, the three states my phone can be in are:
Off
Stuck on T-Mobile Screen
Recovery Mode
Also, how can I get some new stuff on my SD card if I the only things I have are: the phone described above (i.e. the only workable state being recovery mode), an SD card and a USB cable.
Whats your email so I can send you an invite if you want it?

lachy95 said:
Thanks.
But how do I check?
I can't get into the proper Android OS, the three states my phone can be in are:
Off
Stuck on T-Mobile Screen
Recovery Mode
Also, how can I get some new stuff on my SD card if I the only things I have are: the phone described above (i.e. the only workable state being recovery mode), an SD card and a USB cable.
Whats your email so I can send you an invite if you want it?
Click to expand...
Click to collapse
To see you SPL and Radio do this:
Turn off phone
Hold Home and End Call buttons.
If you see:
Hboot-1.33.2005 or something like that then that means that you have the latest SPL
Radio-2.22.19.26I then you have the latest Radio too.
First we need to check to see what your SPL and radio is before you try to do anything that involves flashing ROMs
What recovery image do you have?

Can't see it
When I press Home + End Call I can see is:
Android System Recovery:
<the options I described before, with their errors>
The above is in green font, the background is black with an HTC logo, at the very bottom is white font that says this:
Build: RAv1.2.1G
Sorry for not replying as fast as could. I mega-ly appreciate this so I'll try to be more vigilant.
I'll look around for other key combos to get some more info.

lachy95 said:
When I press Home + End Call I can see is:
Android System Recovery:
<the options I described before, with their errors>
The above is in green font, the background is black with an HTC logo, at the very bottom is white font that says this:
Build: RAv1.2.1G
Sorry for not replying as fast as could. I mega-ly appreciate this so I'll try to be more vigilant.
I'll look around for other key combos to get some more info.
Click to expand...
Click to collapse
And I just did that! I pressed back + home and got a white background with three skateboarding androids with this text:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA*****)
CPLD-4
RADIO-2.22.19.26I
Apr 20 2009, 15:30:43
CLEARSTORAGE
Delete all user data?
<ACTION> Yes
<POWER> No
--------
Well thats atleast one step we've bypassed. Stay with me here.
Alrighty so I know the Radio and SPL, and apparently they are up to date.
What next?

From your above post, it seems your SDcard is not being read by your phone. Not sure what the issue is there.
But, if you can get it recognized by the phone, try the following:
It seems you have ADB set up, you may be in luck.
Connect the USB cable in recovery and type these commands on cmd prompt in Windows:
adb shell
ums_enable
This should mount your phone to your PC.
You can now move in necessary files to save your phone.
I suggest doing a FULL WIPE, then reflashing a ROM such as CM 4.2.14.1 (latest build).
If that doesn't work, you may have to start over by flashing DREAIMG.nbh (RC29), flashing latest radio, flashing SPL, DON'T REBOOT, then flashing rom RIGHT AFTER SPL.
Good luck, keep us updated.

Nearly There
Ok. So I got adb up and running.
I ran adb devices and it was blank so I followed part 2 of:
<do google search for "the unlockr hot to set up adb usb drivers for android devices>
After reinstalling drivers via USBDeview:
My Device Manager is now registering my phone as the Android Composite ADB Interface, but when I run adb devices it still has a blank list.
Keep in mind I am in recovery mode.
When I try and run adb shell, it errors with 'no device found' so I need to do this devices command successfully.
Does anybody know whats happening?

lachy95 said:
Ok. So I got adb up and running.
I ran adb devices and it was blank so I followed part 2 of:
<do google search for "the unlockr hot to set up adb usb drivers for android devices>
After reinstalling drivers via USBDeview:
My Device Manager is now registering my phone as the Android Composite ADB Interface, but when I run adb devices it still has a blank list.
Keep in mind I am in recovery mode.
When I try and run adb shell, it errors with 'no device found' so I need to do this devices command successfully.
Does anybody know whats happening?
Click to expand...
Click to collapse
Try running it while the Phone is on instead of recovery.

Say run terminal and post the output of:
cat /proc/cmdline
By the way you can still flash images using fastboot mode.

Its stuck
When you say 'on' do you mean on the T-Mobile Screen?

Thanks
Thanks again guys this is really good and I think we're getting close. OK. Here's an update as of right now:
My computer recognizes my phone in T-Mobile Logo, Fastboot (or thing with three skating Androids, Home and Back), and Recovery.
When I cd to my tools folder I can run adb commands but when I run 'adb devices' it shows:
List of devices attached
....
No serial number or anything. I've reinstalled the drivers.
When I do the command 'run terminal' it says 'run' is not recognized as an internal or external command blah blah
This is the same with 'cat /proc/cmdline'
I still can't run terminal with Alt+X in recovery mode (at least, nothing happens)
My phone cannot turn 'on'. It is stuck on the T-Mobile Screen.
What should I do?

lachy95 said:
When you say 'on' do you mean on the T-Mobile Screen?
Click to expand...
Click to collapse
Normal boot.

That doesn't work.
How can I see it in adb devices?
Argh!
Any ideas just throw them out there.

Have you tried another sdcard? That's the first thing I would try if the phone is complaining about not being able to read it.

Check ur drivers.
sounds like u need to update them.
Try the attachment

Technochris1 said:
Check ur drivers.
sounds like u need to update them.
Try the attachment
Click to expand...
Click to collapse
It works!
Sweet Technochris1, Sweet, sweet person. Thou hath skills and prowess!
I uninstalled the drivers then installed yours. Now adb devices is functioning and sees my device! Now to mount, transfer and fix! I'm indebted to you greatly, for you fixed my phone and everybody else on this thread! Thank you so much.

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.

How to FORCE stop phone from showing up as USB drives in Recovery, still no root :(

Okay I don't know if this will help anyone, but I figured out how to stop Windows from detecting the phone as two USB drives when the phone goes into Recovery mode, and to make it show up as Android Composite ADB device.
I do NOT have HTC installed, rather, I'm using the USB 3 drivers that come down through the SDK, so I'm not sure how to do this if you are using the HTC Sync drivers intead.
At any rate, start with the phone off and disconnected. Open the Device Manager. Boot with your prefered method into Recovery mode, then connect the phone. It should detect as USB Mass Storage Device under Universal Serial Bus Controllers. Right click on USB Mass Storage Device and click Uninstall and then OK. Once this is done, disconnect the phone (you can leave it running in Recovery).
Open My Computer and navigate to C:\Windows\inf. Copy the files usbstor.inf and usbstor.pnf to your desktop or wherever, it doesn't matter, just make sure you put them somewhere you can get them later. Then delete them from the C:\Windows\inf folder. These are the drivers that Windows automatically uses for USB storage devices.
Ok, now bring Device Manager back to the foreground and plug the phone back in in Recovery. It should show up as Android Phone with an exclamation mark. If Device Wizard pops up cancel out of it. Now right click on the Android Phone and click update driver. Click Browse my computer for driver software. Click Let me pick from a list... Click Android Phone and Next. Click Have Disk. Browse to your SDK folder into the USB Drivers folder and you should see android_winusb.inf, select that then click OK. You should now have a list of three items to select, this part I am not sure if there is a 'right' or a 'wrong' but I go with Android Composite ADB Interface.
Select that or whichever one you think and this is what it will install as. Bingo, now whenever you connect the phone into Recovery or boot into Recovery with it already connect it correctly detects as the Composite ADB Interface or whichever you selected, but does NOT show up as any USB drives.
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
At any rate, to get everything back to normal as far as your computer being able to use USB storage devices just copy those two files back to the inf folder before you connect them and you should be fine.

bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
.
Click to expand...
Click to collapse
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.

Or you could try what I've done 7 times and achieved ADB Shell 7 times...
1. Turn the phone off.
2. Start running Loop.bat
3. Unplug USB cable.
4. Turn device on in Fastboot by holding in the optical joystick and power.
5. Plug USB in.
6. Hit power button once to get to HBOOT.
7. Wait two seconds for it to do it's thing.
8. Pull off the back of the phone.
9. Hit Vol - to Recovery then hit power.
10. Immediately after doing this continuously push the sd card in and out (about every .5 - .75 seconds)
11. ?????
12. Profit

@DigitalDementia--
How is what you said relevant in this thread?

bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
Click to expand...
Click to collapse
drtrmiller said:
@DigitalDementia--
How is what you said relevant in this thread?
Click to expand...
Click to collapse
Pretty positive it had everything to do with that section of the first post, he said he still couldn't achieve root I attempted to help him. Why don't you explain to me exactly what it doesn't have to do with this thread?

rynosaur said:
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.
Click to expand...
Click to collapse
The real bummer here - and I should have known better, really - is that this wipes your phone.
I suppose it should be obvious, but take it from someone who's pretty new to Android phones and just wiped their entire phone after following your steps: Please add a warning to your original post.
It's late, I'm tired and irritated, but I'm sort of bummed to know I went from hero to zero in trying to enter shell (again) during recovery all in an effort to get proper perm. root. Sort of ****ty to know that I just lost everything.

still no root
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App

USB drives are ok in recovery
When I am in recovery with adb and working correctly it still shows the 2 USB drives so this is normal and ok, what you have done is fool yourself into thinking that your phone is in correct mode but it really is not, this is why it still does not work, sorry.

rynosaur said:
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Now that I've scorched the earth, I'm hitting this thing hard with every trick I can think of to get the shell in recovery again.
Thankfully, I at least have my app list on appbrain.

After researching around the different forums, I think this maybe my issue. I will have to make this attempt when I get home.
This is what I posted on a different forum. I am not sure if this is a similar experience you were having:
So, for a little a bit I was having issues with finding and modding the usb.inf file. I got that finally resolved... Now as I go to one of the first parts of the procedure, executing the adb shell command. Well at first it said the 2 lines, about the daemon and whatever the second line was. Anyways, the third line did not say "no device found" it went straight to a shell prompt "$" . The instructions made a point in the instructions for it to say " no device found" .
I went ahead with the rest of the instructions. No Luck. And I did both methods. A co-worker of mine told to run adb devices to see if my phone is recognized. I will also make that attempt tonight.
I wanted to know if any of you had some insight. I made sure I was in the right directory.
I will make another attempt on a different machine tonight.
Thanks. Oh yeah, I do have some UNIX experience if that makes a difference.

I had the same problem, used this method here
addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
Click to expand...
Click to collapse
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!

kentoe said:
I had the same problem, used this method here
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!
Click to expand...
Click to collapse
I rooted in Windows, rather than linux, simply because I like the look of MejDam's procedure better than the linux script posted here on XDA--and his windows procedure is accompanied by his YouTube video
Long story short: I had ADB Composite Device AND the two storage volumes mounted together, as I got shell, and did the other steps in recovery. NB: they were mounted as Generic Storage Volumes, not writeable partitions. The stock recovery on DI does not allow host to mount either partions, although I'd like to see if
Code:
mount /dev/block/mmcblk0p1
worked for the SDcard on the sdcard, cuz then it would be a cinch to mount sdcard/emnc partition into host OS--windows, linux, Atari 2600, etc Worth a try.
Anyhow, my conclusion: a bad driver setup could be a barrier to catching adb shell, but it is certain not the prevailing problem for most, IMHO.

Was wondering if bast525(the creator of the thread) was ever able to adb shell while in recovery, and if so what did you do thanks.

Heh, I wish.... I've tried just about every method posted on these forums, and five different SD cards from Sandisk, PNY, and Kingston. The only thing I haven't tried is rolling back to the pre OTA update, because I don't want to wipe the phone at this point.

[Q] Common Telnetd problem? - unable to root

Common Telnetd problem - unable to root
What's up xda!! This is my first post ever!
..please be kind.
I am experiencing a n00b issue w/ rooting my G1. So far I have been able to get up to where I am on RC29 and <enter>reboot<enter> successfully reboots my phone! This is great up until I'm told to hit the enter key twice, type "telnetd" and press enter. after the phone starts up.
FOOD FOR THOUGHT:
I believe I have ADB drivers installed properly installed
I am able to run Droid Explorer and it connects and recognizes my unit
I also have the following files on my SD CARD prepared
recovery-RA-dream-v1.5.2
update.zip
I have also read that ONE solution is to look for someone with an current T-Mobile Monthly Account and ask to borrow their sim card so I can install the Telnetd and enable WiFi past the Google Login(I have asked a fellow and I was told an aggressive NO, apparently people are afriad of anything related to hacking and their SIM CARDS)
I have the G1 Original SPL currently
Also when booting into recovery Alt+L gives me the Log that shows ""
I hope to have made an appropriate first post granted I've been searching for answers and help and am still experiencing issues. I look forward to participating in this forum in the future looks like you guys have been having fun for a while!
Any suggestions are definitely welcome.

Maybe try to update your phone to Android 1.6 with official OTA packages (last 3 ones are which you should flash) by stock recovery (it will accept this packages if you apply them in correct order - every package is named sth like "CRB43 to CRC1" - then you which should be applied) and then try one-click root app? When you have superuser priviliges you can download ROM Manager and flash custom recovery, then by recovery flash engeenering SPL. And with this SPL you can do what you want with your G1.
I rooted my G1 both ways with goldcard and with one-click root and I have to say, one click-root ROX.

RE: Maybe try to update your phone to Android 1.6
raven_raven said:
Maybe try to update your phone to Android 1.6 with official OTA packages (last 3 ones are which you should flash) by stock recovery (it will accept this packages if you apply them in correct order - every package is named sth like "CRB43 to CRC1" - then you which should be applied) and then try one-click root app? When you have superuser priviliges you can download ROM Manager and flash custom recovery, then by recovery flash engeenering SPL. And with this SPL you can do what you want with your G1.
I rooted my G1 both ways with goldcard and with one-click root and I have to say, one click-root ROX.
Click to expand...
Click to collapse
Hey raven, thanks for the reply!
By doing this update are you suggesting that I use the G1 Original SPL to flash the Offical Dream RC29 ROM (OTA_ROM RC) listed on that page, IF so what should follow that? Would I be allowed to flash the Official RC30 Patch - from RC29 to RC30 (Removed Root) (OTA_ROM RC) and the Official RC33 Update - from RC30 to RC33 (OTA_ROM RC) with the same update.zip that came from the G1 Original SPL also?!
I'm lost with your suggestion, b/c if it requires me to enable WiFi to get the OTA update I would still be unable get pass the Google login. Would I not be stuck back to where I am now? As of right now, I am at the Android Welcome Screen with the G1 Original SPL and RC29 that were not listed on that page AND so far unable to get root b/c of unavailability of TelnetD and WiFi. I will proudly follow those instructions?? Sounds like following the flash of Offical Dream RC29 ROM (OTA_ROM RC), that I would need to somehow use a method to flash the Official RC30 Patch - from RC29 to RC30 (Removed Root) (OTA_ROM RC)...I think?!

Excitement!!!!!
EXCITEMENT!!!!!
I used:::::
1- Plug your G1 & Install Drivers.
2- Without Sim Card in Your G1, <enter>setprop persist.service.adb.enable 1<enter> Even though u dont see what u typing, but u are actually executing a Command on your G1 to Enable USB Debugging in Settings.
3- Once u Execute that Command USB Drivers will be Installed again, but this time will be recognised as ADB Interface.
4- Click Start>Run>cmd> to Command Prompt
5- Type c:\adb devices (If your Device is Connected u will see it)
6- Restart your G1 but now With Sim, to see the Activation Screen then Plug USB Cable & Type c:\adb devices (to make sure u are connected)
7- Type c:\adb shell (U will see a $ sign) Just Copy & Paste this into Command Prompt (am start -a android.intent.action.MAIN -n com.android.settings/.Settings) The Settings Screen will Appear, now Switch on Wi-Fi & Connect to the Internet.
8- Now u can either Login with your Existing or Create New Account with Google.
Click to expand...
Click to collapse
here is where I was lost, I'm sure many are running into the same issue. The adb.exe that is located on my PC is what the command prompt should be finding, however there are other folder possibilities in where the application is ran to even use the adb functions. For instance, my adb.exe was installed in "c:\android-sdk-windows\tools" instead of strictly on the "c:\" I was not aware that I would be controlling the phone unit through my command prompt as well!! silly me, something so easy can become one of the biggest problems. ONE MONTH LATER!!!! THANKS XDA!