Database Develop

Stuck G1 - but Not your typical

Okay.
I dont think my problem is typical, and Ive searched google and xda for answers. Some situations seem similar, but none exact.
Here is the story:
G1 was running wifi tether and on charge. No bumps or bruises, just sitting by itself. The tether stopped working, so I went over to look at the G1 and the phone was frozen. Display was lit up and working, just frozen. Had to pop the battery out to shut it down.
After powering back up, the sits at the splash screen indefinitely.
I can go into fastboot but I can NOT get into recovery.
I have going into fastboot usb mode and:
1) flash a recovery image (works)
2) flash a nandroid backup (works)
3) flash rc29 (see below)
4) flash hboot (always fails)
What I mean by works is the flash indicates it was good, but there is no change in functionality of the phone. Hboot gives me device errors.
Dream PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
Radio-2.22.19.26I
Apr 20 2009,15:30:43
I have also flashed a different splash image - and even though it says it succeeded the image doesnt change.
When I attempt to flash the original RC29 using the SD card mode or fastboot mode it indicated I need HBOOT 1.33.2004. 2004 *will not install* --- it gives an error (I think something to the effect of wrong device.)
I know my way around fastboot and adb, but I dont know what "hboot mode" is used for. For grins, I tried flashing the recovery in hboot mode and it says "waiting on device" forever.
It seems almost like this is a hardware problem that is presenting itself as a software issue.
Also - *sometime* when I hold home/power to try to boot into recover the phone will connect to ADB (listed in adb devices) but no commands seem to work.
Im an a loss. 10+ hours trying to fix this thing...
Any ideas?
Thanks.
Blade

Blade10 said:
When I attempt to flash the original RC29 using the SD card mode or fastboot mode it indicated I need HBOOT 1.33.2004. 2004 *will not install* --- it gives an error (I think something to the effect of wrong device.)
Click to expand...
Click to collapse
Tried with a goldcard?

No. Maybe I didnt read enough, but I thought the goldcard required a WM Device? All my machines are win xp, obvously I can use a live cd to boot linux.
BTW, the SDcard method of installing dream.nbh (RC29) gives me a checksum error, while fastboot finishes but doesnt make a difference. Yes, tried different SD cards and ran checksum after coipying to the card - checksum is correct.
Any other ideas, or maybe some links that make a goldcard easy?
Thanks,
Blade

[Q] Help: Unrooted Nexus Fails To Boot

Hi Guys,
I have a rooted HTC Hero so am familiar with rooting Android etc.
I said I'd help a colleague out with a problem on her newly purchased Nexus One but I'm struggling. When you turn it on, it doesn't actually boot up - the static X (not the animated one) just sits there indefinitely. We've left it for ages and it doesn't do anything at all.
The only progress I have managed to make so far is to unlock the bootloader through "fastboot oem unlock". I've since tried copying some stock N1 ROMs onto the SD Card and tried getting them to install through the Bootloader/Hboot screen as passimg.zips. They're recognised and the blue progress bar runs but it always fails.
I also don't seem to be able to get adb access to the device. "adb devices" returns no results and "adb shell" obviously says "device not found".
I've also tried writing amon_ra's recovery to the device via fastboot and while it sends it fine, it fails to write (remote: image update error).
I'm assuming the last two points are because usb debugging isn't enabled (can't boot it to do so) and it isn't rooted.
Is there some way I can get a ROM flashed onto this that will boot to allow me to root it and then install the custom recovery and a ROM of my choice?
If it makes any difference, the model should be a UK Vodafone one. One of the passimg.zips I've tried has been PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_release_signed.zip, which I read is the one to downgrade Vodafone N1's to but it failed.
Any help at all will be gratefully received.
Thanks in advance.

Just a quick update about the passimg.zip failures...the error message is "main version is older"
Have also just tried a "fastboot boot recovery.img" (where recovery.img is a renamed amon_ra)...it downloaded fine and kicked off a reboot but it didn't actually boot into the recovery image at all...it remains at the static X screen (with unlocked padlock).

Have now tried a stock FRF91 as passimg.zip and this time it didn't error at the end. Instead it just returned to the menu after checking the passimg and didn't prompt me to apply etc...

Look here and download the PASSIMG.zip from the second post. put in root of sd .This will pass the "Older rom version" But it will downgrade you to EPE76.
If everything works out good. You would have EPE76 and a working N1. but you will need to download FRF85B. http://www.mediafire.com/?j5zejudgngm. rename that to update.zip. put into root of sd. boot into stock recovery. once you see triangle and android hold power and hit volume up. You will then see the recovery menu. Select apply update.zip. if its an success you will have FRF85B. Then just go to settings>system updates and search for FRF91 update.

Thanks for the reply. EPE76 is one of the ones I recently tried but even though it passes the check, it doesn't seem to apply. I don't get an option to apply and rebooting results in the static X again.
Earlier I managed to successfully apply amon_ra's recovery through fastboot. Apparently. The text in my command prompt said it was successful but attempting to boot into recovery from the bootloader menu presents me with the same static X.
I really don't understand what's going on with this thing.

I've now downloaded EPE76 in its original img component format from modaco and flashed boot, system, and userdata onto the three partitions separately using fastboot. System took three attempts but succeeded eventually.
Despite now having what should be EPE76 forced onto it, it still refuses to boot, giving me only the static X again.
I'm running out of ideas here. Does anyone have any suggestions at all?

Anybody? (bump)

I'm assuming she bought it used (because if it's new you would have took it back). From what I know, it sounds like a radio flash gone bad
I hope I'm wrong though.

[Q] Bricked my CEll upgrading the radio

Hello guys,
I know the first thing you may think is this is another moron who bricked his Cell. But please be patient with me and at least let me learn from my loss. Please let me know what I did wrong.
First I read 3 main thing before doing anything,(1) [Guide] One-Click Root for Rogers HTC Dream:, (2) the post by HYKO and and finally CyanogenMod Wiki. Since I cannot post URL I attached them at the end.
So first I tried to get a hboot 1.33.2005 SPL using the source (1) which went ok.
then I used CyanogenMod Wiki (3) to root my HTC DREAM. Every thing went ok till I tried to update the radio. After I flashed the radio my cell hangs on the rogers logo and does not go any further. I can go to the fastboot (camera butt and END). it is S-off and 1.33.2005 SPL. However, I can not reach the recovery menu (Home and END). I tried flashing back to the older radio 3.22.20.17 and 2.22.29.26I (using the haykuro zip file). none of them worked.
First I want ot know what did I do wrong. Second I noticed my SDcard is broken, and the HBOOT looks for deaimg and deardiag on sd. does anyone know if I can unbrick it using this.
Thanks
alrsar
(1)
1. Download Haykuro's root kit here.
2. Extract the recovery.img and update.zip files from the download and copy them to the root of your sdcard's fat32 partition (if you haven't partitioned your card yet for A2SD, then just the root of the card itself).
2. Last time I checked, the one-click root app, flashrec, has been pulled from the Market, so download it here.
3. Install the app and start it, it will look like this:
4. Tap 'Backup Recovery Image', in some cases the app will fail to backup the image. This shouldn't be a problem, but if it works, it's always nice to have a backup.
5. In the blank above the greyed-out button enter '/sdcard/recovery.img' without the quotes. If you were successful in making the backup, the top button should change to white and say 'Flash Custom Recovery Image'. If not, don't worry, there is a hidden button to the right of the backup button that will bypass the backup requirement. Like so:
6. Press 'Flash Custom Recovery Image'. If you get a flash failed message, try flashing with your phone unplugged from USB.
7. Power your phone down.
8. Power up your phone while holding the home button. You should get the older 1.2 Recovery Menu. If your phone hangs at the Rogers logo, remove your battery, re-install or try the 3-finger salute (Phone, menu, and power button together) and try again. If it still hangs on the Rogers logo, reboot without the home key, this will bring you back to normal boot. You won't be rooted but you won't be bricked.
9. Once you're at the recovery menu, choose the second option, apply sdcard:update.zip. In some cases you may get an error something like E: not found. If you choose the second option again, it should find the update.zip alright and then press home to continue.
10. Now click on reboot (Home & Back). Press and hold the camera button and you should boot into the new 1.33.2005 SPL.
11. If all has gone well and you see hboot 1.33.2005, you can safely follow the rest of the rooting instructions in this thread. There's also a great set of instructions for installing Cyanogen's 4.2.X roms in the same thread. The post is here.
Of course, these instructions may be rendered moot if Rogers chooses to fix the vulnerability that allows one-click root at which point we'll have to hope someone manages to find a way around the so-called 'perfect' SPLs.
If after a couple attempts you remain stuck at the Rogers logo, remove the battery, reinstall it and then power up normally. You should then boot back to the unrooted phone and it will restore the default recovery. You may not be rooted, but at least you're not bricked.
(3)
1. You will need fastboot on your computer to run the following commands. Set up ADB and fastboot on your computer.
2. Download exploid & Amon_Ra's Recovery:
* exploid (includes the source): Download
* Amon_Ra 1.7.0: Download
3. Rename Amon_Ra's Recovery Image to simply recovery.img.
4. Put both the exploid file & Amon_Ra's Recovery in the same directory as adb.
5. Turn on USB Debugging (Settings » Applications » Development).
6. Connect the Rogers Dream to the computer.
7. On the computer, open terminal & navigate to the adb folder
cd /path/to/adb/
8. Type in the following commands:
adb push recovery.img /data/local
adb push exploid /sqlite_stmt_journals
adb shell
cd /sqlite_stmt_journals
chmod 777 exploid
./exploid
9. You will see a message come up. The exploit has now been setup. Unplug & re-plug in the USB cable to the computer.
10. Now type in the following commands:
adb shell
rootshell
NOTE: This will prompt for a password, the password is "secretlol".
chmod 666 /dev/mtd/mtd1
flash_image recovery /data/local/recovery.img
NOTE: The first time this command runs, it may return "mtd: read error at 0x00000000 (Out of memory)". Simply run this command again & it should run without error.
11. The Rogers Dream has now been rooted & will have Amon_Ra's Recovery on it.
Flashing Radio
If the Rogers Dream already had the 911 patch, then the phone will already have the latest radio. Follow these instructions if the Rogers Dream did not have the 911 patch.
1. Download the latest version of the radio (3.22.26.17).
2. Rename the radio image to simply radio.img.
3. Power off the Rogers Dream.
4. Boot into bootloader mode. Hold the Camera button while powering on the Rogers Dream.
5. Connect the Rogers Dream to the computer.
6. On the computer, open the command prompt/terminal & navigate to the Android SDK Tools folder.
7. Type in the following command:
fastboot flash radio radio.img
8. Once finished, you can restart the Rogers Dream.

Perhaps try flashing a new recovey via fastboot?(aka screen with android skateboarding) with adb, looks at the rom bible in the dev section for more details. You also need the android sdk installed on your computer to do so, and a working mini usb cord.

ok first, you are not bricked, brick means cannot get into bootloader (camera+power) nor recovery (home+power), and it will be useless like a brick,thats why we call it "bricked" when you messed it up. Unless you use the jtag method, but thats for the super hardware geeks not for the people here in the forum.
Since you are not bricked, you can try to turn on the phone and wait for at least 5 minutes and see if the screen is still stuck on the same logo, because sometimes it takes quite long for the first boot after your new Flash. If it really stuck on the same logo for the damn 10 minutes, then you can try the following ways.
I dont know what version SPL and radio you use, but remember, always flash the radio first, then restart the phone then flash the SPL, because this really can brick your phone (i done it once)
- if your recovery support usb mount, then re-download the roms and double check with MD5, make sure the rom is 100% identical, then reflash it. because defected rom always caused your kinda problems.
-if it still doesnt work, do this also with your SPL and Radio zip files
-if still doesnt work, get the dreaimg.nbh file to sd, then camera+power to bootloader, and downgrade to 1.0. then start to root again carefully this time.

americanxo said:
I dont know what version SPL and radio you use, but remember, always flash the radio first, then restart the phone then flash the SPL, because this really can brick your phone (i done it once)
- if your recovery support usb mount, then re-download the roms and double check with MD5, make sure the rom is 100% identical, then reflash it. because defected rom always caused your kinda problems.
-if it still doesnt work, do this also with your SPL and Radio zip files
-if still doesnt work, get the dreaimg.nbh file to sd, then camera+power to bootloader, and downgrade to 1.0. then start to root again carefully this time.
Click to expand...
Click to collapse
Thanks for your reply, I have PVT 32B ENG S-OFF HBOOT -1.33.2005 drea21000
cpld-4
Radio 3.22.26.17
I can only go to the FASTBOOT mode (Camera and END) I dont have the recovery mode. So I think it rules out the first option. I can flash radio and done ut couple off time. No change to the situation. I dont know how to flash the SPL I should. Can you tell me what exactly the last option does?
thanks
Alireza

my FASTboot command works but ADB cannot connect. I assume you mean I should flash the recovery, right?

alrsar said:
Thanks for your reply, I have PVT 32B ENG S-OFF HBOOT -1.33.2005 drea21000
cpld-4
Radio 3.22.26.17
I can only go to the FASTBOOT mode (Camera and END) I dont have the recovery mode. So I think it rules out the first option. I can flash radio and done ut couple off time. No change to the situation. I dont know how to flash the SPL I should. Can you tell me what exactly the last option does?
thanks
Alireza
Click to expand...
Click to collapse
From where you are flashing fastboot or rom....
If you are able to go to fastboot mode, then flash the recovery from there....using fastboot from your PC....

alrsar said:
Thanks for your reply, I have PVT 32B ENG S-OFF HBOOT -1.33.2005 drea21000
cpld-4
Radio 3.22.26.17
I can only go to the FASTBOOT mode (Camera and END) I dont have the recovery mode. So I think it rules out the first option. I can flash radio and done ut couple off time. No change to the situation. I dont know how to flash the SPL I should. Can you tell me what exactly the last option does?
thanks
Alireza
Click to expand...
Click to collapse
the last option is to downgrade your phone to its stock version which i think it would be RC29, so you can root. I think you done it once before rooting your device right ?

americanxo said:
the last option is to downgrade your phone to its stock version which i think it would be RC29, so you can root. I think you done it once before rooting your device right ?
Click to expand...
Click to collapse
Please please please do not flash rc29 on a rogers dream.. if the flash fails but installs the spl you can be in an annoying position, best unroot to the rogers firmware and root that again..
However op just needs to flash the -r version of the dream recovery.

This thread is a case of the blind leading the blind. Ignore ALL of the nonsense and read the following:
You have fastboot. That's good.
Start by installing a proper radio image. 2.22.23.02. You do this with FASTBOOT.
Go into fastboot mode, type (on your computer) "fastboot flash radio radio.img", ensuring that you have a radio.img with 2.22.23.02 in the current directory, and the fastboot executable somewhere in your path variable.
Next, flash a proper recovery image to it. Again with fastboot. "fastboot flash recovery recovery.img". Use ANY standard EBI0 recovery image that you like.
Now it'll work.
DO NOT INSTALL ANY NBH FILES!!!!!

lbcoder said:
This thread is a case of the blind leading the blind. Ignore ALL of the nonsense and read the following:
You have fastboot. That's good.
Start by installing a proper radio image. 2.22.23.02. You do this with FASTBOOT.
Go into fastboot mode, type (on your computer) "fastboot flash radio radio.img", ensuring that you have a radio.img with 2.22.23.02 in the current directory, and the fastboot executable somewhere in your path variable.
Next, flash a proper recovery image to it. Again with fastboot. "fastboot flash recovery recovery.img". Use ANY standard EBI0 recovery image that you like.
Now it'll work.
DO NOT INSTALL ANY NBH FILES!!!!!
Click to expand...
Click to collapse
Since he's on Rodgers, doesn't he need the 3.22 radio and a special recovery?

billquinn1 said:
Since he's on Rodgers, doesn't he need the 3.22 radio and a special recovery?
Click to expand...
Click to collapse
Shh people don't realize (ignoring carriers that may cause pain if they find a radio without an imei version of 3, only found on the latest 3.x radio) all dreams support 1.x, 2.x, and 3.x radios *if* installed properly.
The only thing to keep in mind is that like installing danger spl on a ebi0 stock dream, switching from ebi1 to ebi0 has a brick risk if done incorrectly.
To switch from 3.X->2.x or 2.X->3.x you need to flash the destination radio img file via fastboot (from hboot-1.33.2005) and *not* via recovery..
also after flashing you need to flash the recovery for the destination radio. (-r if 3.x otherwise the regular non -r)
As for if 2.x or 3.x is better.. they are nearly identical with some minor configuration changes that include some different memory offsets.. one or the other may or may not be better configured for any particular carrier.
Of corse there are many roms where we don't know what the kernel was pulled from for te ebi0 that since I don't know what kernel it has can't be used on ebi1.. I usually write these off however due to me not knowing where the source code is regardless of my target radio.
This only leaves the interesting aspect of lbcoder.. the amount he screams to ebi0 users not to use danger spl due to the dangers, but requests rogers/ebi1 users to switch to ebi0 radios despite the danger.. (note don't take this as you should or shouldn't do either recommendation, but that you need to understand what the approach means and what is your goal.. if you just want to access root to remove some bloat ware all you need is exploid or androot and you can keep the stock firmware.)
Ultimately however I expect people to take lbcoders advice with a grain of salt; and hopefully this will make the user actually read up on his suggestions, and what they where originally planning.. and figure out how to safely go from where they are to where they are going.

ezterry said:
Shh people don't realize (ignoring carriers that may cause pain if they find a radio without an imei version of 3, only found on the latest 3.x radio) all dreams support 1.x, 2.x, and 3.x radios *if* installed properly.
The only thing to keep in mind is that like installing danger spl on a ebi0 stock dream, switching from ebi1 to ebi0 has a brick risk if done incorrectly.
To switch from 3.X->2.x or 2.X->3.x you need to flash the destination radio img file via fastboot (from hboot-1.33.2005) and *not* via recovery..
also after flashing you need to flash the recovery for the destination radio. (-r if 3.x otherwise the regular non -r)
As for if 2.x or 3.x is better.. they are nearly identical with some minor configuration changes that include some different memory offsets.. one or the other may or may not be better configured for any particular carrier.
Of corse there are many roms where we don't know what the kernel was pulled from for te ebi0 that since I don't know what kernel it has can't be used on ebi1.. I usually write these off however due to me not knowing where the source code is regardless of my target radio.
This only leaves the interesting aspect of lbcoder.. the amount he screams to ebi0 users not to use danger spl due to the dangers, but requests rogers/ebi1 users to switch to ebi0 radios despite the danger.. (note don't take this as you should or shouldn't do either recommendation, but that you need to understand what the approach means and what is your goal.. if you just want to access root to remove some bloat ware all you need is exploid or androot and you can keep the stock firmware.)
Ultimately however I expect people to take lbcoders advice with a grain of salt; and hopefully this will make the user actually read up on his suggestions, and what they where originally planning.. and figure out how to safely go from where they are to where they are going.
Click to expand...
Click to collapse
Interesting stuff. I always thought there was a (carrier + hardware) reason for the different radio. Thanks for taking the time to explain.

ROM doesn't start, recovery fails, fastboot not recognized by PC

Today I tried to change ROM in my G1. With that I also wanted to change SPL and recovery. It was my first conact with flashing that phone. I flashed Samsung i7500 before, so I have some Android experience.
Recovery and SPL went OK. When I was flashing ROM, something has gone wrong, so I decided to restore nandroid backup I made before flashing new ROM. When I restored backup, system didn't load. It stops on "Android" text or on black screen. Recovery also got lost (I don't know how) - now I can see only picture with triangle and "!" sign.
First thought I have was to use fastboot to flash new recovery and have it working. But there is my problem - when I enter fastboot mode, PC doesn't see any new device. There is no difference in device manager when phone is connected or not. When I turn phone on normally (so system's stops loading on Android text), it's recognized by PC.
Have anybody had such problem? What should I do to restore recovery or flash working rom?

What ROM u trying to flash? Some ROMs need some base files. You can even install a new Recovry Image through Recovery Console. Thats what I did

OK, What SPL you have right now...
Once you flash new SPL, old nandroid might not work properly as the partition layout has been changed....
Let us know the SPL you have now, sometimes if the phone is not getting recognized..then you have some old driver installed, try to see if that's the issue...
ms93 said:
Today I tried to change ROM in my G1. With that I also wanted to change SPL and recovery. It was my first conact with flashing that phone. I flashed Samsung i7500 before, so I have some Android experience.
Recovery and SPL went OK. When I was flashing ROM, something has gone wrong, so I decided to restore nandroid backup I made before flashing new ROM. When I restored backup, system didn't load. It stops on "Android" text or on black screen. Recovery also got lost (I don't know how) - now I can see only picture with triangle and "!" sign.
First thought I have was to use fastboot to flash new recovery and have it working. But there is my problem - when I enter fastboot mode, PC doesn't see any new device. There is no difference in device manager when phone is connected or not. When I turn phone on normally (so system's stops loading on Android text), it's recognized by PC.
Have anybody had such problem? What should I do to restore recovery or flash working rom?
Click to expand...
Click to collapse

I have installed haykuro SPL as I remember right.
I tried to update SDK and its USB drivers, but no result.
I remember also, that "USB debugging" wasn't on - maybe that's why phone in fastboot isn't recognized on PC?
To be clear: when I plug USB cable in fastboot mode, PC doesn't show that there is some new device. It acts like no device was connected to it.

There are other new and safe method to achieve the same or more then what you are trying to achieve with Haykuro SPL...see here..Custom MTD
But anyhow you are stuck with it...when you say Phone is not getting recognized..try restarting the phone in fastboot mode while connected to PC...when you are pressing back button are you getting fastboot..
I am not a good person to suggest something on this...If I would have been in your place I would have flashed DREAMIMG.nbh file and would have started from start....but wait till somebody better will tell you how to recover the device....
ms93 said:
I have installed haykuro SPL as I remember right.
I tried to update SDK and its USB drivers, but no result.
I remember also, that "USB debugging" wasn't on - maybe that's why phone in fastboot isn't recognized on PC?
To be clear: when I plug USB cable in fastboot mode, PC doesn't show that there is some new device. It acts like no device was connected to it.
Click to expand...
Click to collapse

G1sanju, I don't know what to say!
You saved my phone
Flashing DREAMIMG.nbh helped, phone has booted

OK, I have a new problem now.
Recovery is still not working - I have Android 1.0 in phone.
Fastboot is still not recognized by PC, so I can't flash it. I don't have root, so I can't flash recovery by terminal - is there any Android 1.0 root instruction?
Or maybe DREAIMG.nbh of 1.5 or 1.6 ROM?
EDIT:
Now everything works, I flashed recovery using telnet.

DREAMIMG.nbh is an default image for G1, so it remove root access and leave the phone with the stock image...now you have 1.x radio and stock SPL...flashing haykuro SPL right now can brick your phone....
unlocker.com has some good guide to get the root access if you are looking for it....
Do not flash the Haykuro SPL or DangerSPL......That's of no use now....also there are chances that it can brick your phone....
Use Safe SPL...1.33.2003 those are full engineering SPL with fastboot access....
use CustomMTD to get the increase size as mentioned in my post above...
ms93 said:
OK, I have a new problem now.
Recovery is still not working - I have Android 1.0 in phone.
Fastboot is still not recognized by PC, so I can't flash it. I don't have root, so I can't flash recovery by terminal - is there any Android 1.0 root instruction?
Or maybe DREAIMG.nbh of 1.5 or 1.6 ROM?
EDIT:
Now everything works, I flashed recovery using telnet.
Click to expand...
Click to collapse

I installed recovery via telnet, then changed radio, installed CustomMTD and ROM. All working fine.

Its great that you have used customMTD rather then Haykuro SPL...this is safe method....I just warned you because that's a very common way to brick the phone....flashing NBH and then installing SPL assuming you have the correct radio is a very common way of bricking the phone...
Also if you are playing with SPL and radio's then its advisable to erase the recovery first...then do the install from fastboot and then reinstall recovery...
ms93 said:
I installed recovery via telnet, then changed radio, installed CustomMTD and ROM. All working fine.
Click to expand...
Click to collapse

[Q] HTC Dream update to Android2 (wow this is hard)

I've been trying for a long time reading all the guides following all instructions and I think I finally see how all the pieces work together, but for some reason, I get completely stuck by fastboot.
Here's what it says when I hold back and power:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.23.02
Sep 2 2008
Serial 0
this guide: http://wiki.cyanogenmod.com/index.php?title=Dream:DangerSPL
Says to root the G1 (based on the radio version, I think that's been done).
Next I'm supposed to install Amon Ra recovery
From this guide: http://forum.xda-developers.com/showthread.php?t=566669
It says that if I have the engineering SPL (which I seem to based on the numbers), I should be able to follow these directions:
Copy recovery-RA-dream-v1.7.0.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.7.0.img
I've copied the img to somewhere on the phone (I forget where) and I've done the second and third steps, but fastboot never sees the device even though ADB can. What now?
Copy recovery-RA-dream-v1.7.0.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.7.0.img

Something must have happened at some point because now the phone won't boot unless I do it into safe mode. This is pretty frustrating. All these guides and none work for me.

What is the status at this point? Are you able to get into Recovery, fastboot, etc...?

When you boot normally and you plug your phone in fastbooted, do you hear a sound/any indication from Windows that it's detected in any way at all? Have you checked device manager?
You need not bother with the further commands unless 'fastboot devices' picks up the phone in command prompt. Fastboot didn't find mine straight away either. I had to change to HTC Bootloader driver when connected to USB in bootloader -which shouldn't effect ADB or anything else as the phone is booted differently and loads as a different device to have ADB operational, hence why I believe you generally can't mix fastboot/adb ccommands.

BeenAndroidized said:
What is the status at this point? Are you able to get into Recovery, fastboot, etc...?
Click to expand...
Click to collapse
Sorry for the late reply. I don't often get a chance to work on the phone. I can boot to the four color boot screen that shows the hboot and radio information as follows:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.23.02
Sep 2 2008
Serial 0
For a second it flashes to a different screen and then says "no image" or something then goes back to the multi-color screen. When I plug the device into the computer during the multi-color screen, nothing happens. The computer makes no noises to indicate it knows a USB device is there.
If I exit colored screen mode (whatever it's called), and leave the cable plugged in, Windows says there's something attached but it malfunctioned. Both the phone and Windows respond when I plug in USB at any time other than the multicolor mode.

I'm trying to solve the "g1 looks like usb mass storage" issue and it's not working. If I follow directions to boot to fasboot mode first, it only goes to the four color screen and the USB isn't recognized. If I do it while it's on normally, Windows sees it, but won't let me update the drivers.
I tried picking them manually, but that's not working. Wait... all of a sudden I see HTC Android listed under "Disk Drives" I don't know what happened, but it seems to have worked (I just updated the GOOGLE USB drivers using the SDK third party installer so maybe that was it). Let me try from scratch again.

Still nothing. By the way, I've never been able to boot to Fastboot mode. I've never seen skateboarders. Do you install that?

Ok, I've tried a series of other guides online. I've spent the last 4 or 5 hours on this trying to root and then install various other things. Using three different rooting techniques, I still can't get super user access when using terminal emulator.
What is this? Some kind of practical joke?

Making progress... I think
I followed the directions here:
http://wiki.cyanogenmod.com/index.php?title=HTC_Dream:_Rooting
Which didn't use to make sense, but now are helping. I downgraded the Firmware per instructions, but used the SuperOneClickv1.7-ShortFuse to root the phone instead (which worked splendidly). Now I FINALLY can get root using ADB though installing Amon Ra recovery isn't going too smoothly yet.
Edit, spoke too soon: I didn't see anything in the SDCARD folder until I disconnected the cable and reconnected it. I was able to use the flash_image recovery recovery.img file now (recovery.img is a renamed amon ra cyan image).

After installing Amon Ra, upgrading the SPL to Danger was easy to do in recovery mode as was installing Cyanogen. I also installed a different mod (biffmod), but didn't like it.
Now everything seems to work other than clockwordmod still won't install (but I don't really care since I can do everything fine with Amon Ra if I move downloads into the root folder).
I hope this thread helps others!