Database Develop

Rogers HTC Dream died, plz Help!

I follow this instruction
http://forum.xda-developers.com/showthread.php?t=558301
I flashed the rom by another custmer firmware (same process as magic before)
after i update the rom, then i restart it, but I just get stuck with the ROGERS logo loading screen and nothing else after that.
I got this message when it is in fastboot(in red color) mode.
DREAM PVT 32B ENG S-OFF
HBOOT -1.33.2005 (DREA21000)
CPLD-4
RADIO 3.22.20.17
Apr 20 2009, 15:30:43
(camera step2)HBoot Mode
(back) Reset Device
(Action)Restart to HBoot
(Menu) Power Down
I wait 1 hour, it still shows Rogers Logo on the sreen, nothing happend. I tried all the combination keys. ( it either shows flashboot mode or get stuck with the Rogers logo. I have even no chance to flash another rom again.
So is anyway to fix it please? great appreciate for any kind helps.

You need to flash your radio. Go here, grab the radio "ota-radio-2_22_19_26I.zip."
Put the zip file onto the root of your SD card, and flash from recovery.
Edit: Wait I misunderstood all that. Can you get to recovery?

FaJu said:
You need to flash your radio. Go here, grab the radio "ota-radio-2_22_19_26I.zip."
Put the zip file onto the root of your SD card, and flash from recovery.
Edit: Wait I misunderstood all that. Can you get to recovery?
Click to expand...
Click to collapse
Thanks for your fast reply. Mr.Faju
so download it and rename to update.zip, then put it into the memory card?
but I cannot get into the recovery mode any more.

Ah okay. But you can get to fastboot so all you need to do is take the recovery.img you downloaded from this zip file and put in the "tools" folder of your sdk. Then:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
This should give you back your recovery partition. Reboot while holding the home button after doing this and see if you can get to recovery. If you can then yeah just use that radio update and flash anything.

FaJu said:
Ah okay. But you can get to fastboot so all you need to do is take the recovery.img you downloaded from this zip file and put in the "tools" folder of your sdk. Then:
This should give you back your recovery partition. Reboot while holding the home button after doing this and see if you can get to recovery. If you can then yeah just use that radio update and flash anything.
Click to expand...
Click to collapse
Hi Faju, thanks again for your reply. i just downloaded the android-sdk_r3-windows, and as you said, i put recovery.img into the tools folder. once i click the sDK Setup, the dos window automatic gone. I have no chance to enter the code.. by the way, i am using windows 7, no sure if is that matter?

Oh no don't do it that way. Open a dos window and navigate to the tools folder inside the sdk. So if your your sdk was in "C:\Android\sdk" you would do the command
cd C:\Android\sdk\tools
Click to expand...
Click to collapse
Once you've navigated to the tools folder, put your phone into fastboot mode, and on the dos screen on your conputer type that command I quoted in my last message. Once you enter the command you'll see a progress bar on the top right corner of the white bootloader screen on your phone. Once it finishes, reboot your phone while holding home.

FaJu said:
Oh no don't do it that way. Open a dos window and navigate to the tools folder inside the sdk. So if your your sdk was in "C:\Android\sdk" you would do the command
Once you've navigated to the tools folder, put your phone into fastboot mode, and on the dos screen on your conputer type that command I quoted in my last message. Once you enter the command you'll see a progress bar on the top right corner of the white bootloader screen on your phone. Once it finishes, reboot your phone while holding home.
Click to expand...
Click to collapse
great. you are the man Mr.Faju. now i can get into the recovery utility mode again. IT shows: CyanogenMod V1.2 + JF. is that okay to upgrade the radio on that? because I saw v1.4 would be better.
I just did update the ratio, but i cannot get into any fastboot or recover mode( it always shows Rogers logo). i tried all the combination keys... any idea plz? Thanks a lot

Uh you can't get to fastboot?
**** I remember you had to flash radio but it wasn't the one from HTC. It was Haykuro's. Could you try reflashing the Rogers RUU again? The one that gives you the 1.33.0010 spl. At least that will get you back to stock and get your phone restarted. Then redo everything with the flashrec application from your first post.
This time do the same thing to get back your recovery partition but flash the radio from this file. This is haykuro's Rogers root from his thread. This is what worked for me before. This zip also has the 1.4 recovery.

FaJu said:
Uh you can't get to fastboot?
**** I remember you had to flash radio but it wasn't the one from HTC. It was Haykuro's. Could you try reflashing the Rogers RUU again? The one that gives you the 1.33.0010 spl. At least that will get you back to stock and get your phone restarted. Then redo everything with the flashrec application from your first post.
This time do the same thing to get back your recovery partition but flash the radio from this file. This is haykuro's Rogers root from his thread. This is what workede for me before. This zip also has the 1.4 recovery.
Click to expand...
Click to collapse
e
no. I cannot get into any fastboot or recovery mode any more. i cannot use the RUU since it requiest it can get into the system at least. I did a search, and found it died, and cannot be fixed so far. I will try to talk with the Rogers tech support guy tomororrow morning to see if i can have the replacement even i get the phone from my friend. It is okay Mr.Faju, at least i know what is the problem and know how to use the sdk now. Thanks again for your time. you teached me a lot.

[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.

[Q] So my phone is bricked...

First some history with my G1:
I used the normal unrooted G1 for about a ear after i decided to root it. I rooted it succesfully to 5.something (old, because there wasnt ADW launcher yet). Soon after i wanted to go 2.2 or cyanogen 6.0.3. That too was a succes, but after short use it turned out quite slow. I did some research and found out that 5.0.8 is the way to go for a fast G1 phone ith use of apps. Short install but a few trial and errors (lots of factory resets etc.) i got it running smooth. I installed all my apps once again and thought to myself "i should do a Nandroid back-up before i have to wipe it all again...". So i remembered ROM Manager from 6.0.3 and installed it from market. I did a backup via there, but as i clicked i saw a message for a milisecond. It seemed like an error message, but after a split second my phone just rebooted.... Only this time it got stuck at the G1 boot logo....
After getting familiar with Cyanogen this was very new to me. I tried going into recovery obviousley, but that didnt boot. Only thing that did boot was Fast Boot. No idea what i can do there so i didnt touch it.
More research came i decided that i phone maybe bricked... I found out that you can try Terminal or something in fast boot to reflash something... This still isnt clear to me, and i was wondering if there is any guide that i couldnt find that gives me a noobie guide on how to use terminal on your computer to flash something on your phone?
Thanks very much in advanced!
Summary of things i use/did:
Computer: Macbook 1.0.6 OSX
Phone: G1 rooted to 5.0.8 Cyanogen (stable)
Possible cause: Using ROM Manager to make a Nandroid backup

Uh, did you remove the back cover and remove/replace the battery?

Glycerin50 said:
First some history with my G1:
I used the normal unrooted G1 for about a ear after i decided to root it. I rooted it succesfully to 5.something (old, because there wasnt ADW launcher yet). Soon after i wanted to go 2.2 or cyanogen 6.0.3. That too was a succes, but after short use it turned out quite slow. I did some research and found out that 5.0.8 is the way to go for a fast G1 phone ith use of apps. Short install but a few trial and errors (lots of factory resets etc.) i got it running smooth. I installed all my apps once again and thought to myself "i should do a Nandroid back-up before i have to wipe it all again...". So i remembered ROM Manager from 6.0.3 and installed it from market. I did a backup via there, but as i clicked i saw a message for a milisecond. It seemed like an error message, but after a split second my phone just rebooted.... Only this time it got stuck at the G1 boot logo....
After getting familiar with Cyanogen this was very new to me. I tried going into recovery obviousley, but that didnt boot. Only thing that did boot was Fast Boot. No idea what i can do there so i didnt touch it.
More research came i decided that i phone maybe bricked... I found out that you can try Terminal or something in fast boot to reflash something... This still isnt clear to me, and i was wondering if there is any guide that i couldnt find that gives me a noobie guide on how to use terminal on your computer to flash something on your phone?
Thanks very much in advanced!
Summary of things i use/did:
Computer: Macbook 1.0.6 OSX
Phone: G1 rooted to 5.0.8 Cyanogen (stable)
Possible cause: Using ROM Manager to make a Nandroid backup
Click to expand...
Click to collapse
Rom manager has a habit of breaking recoveries. If you can get into fastboot you can flash a new recovery from there. If you have an engineering spl that is. Need your info from fastboot. Do you have danger spl? Amonra has guides on how to flash from fastboot. Get his 1.7.0 and fastboot flash it. You dont sound bricked.
http://forum.xda-developers.com/showpost.php?p=4647751&postcount=1

Ok been a while ,sorry! I am still "bricked" (or at least i think i am). Yes i have taken out the battery and putting it back in.
@Johnson: Yes so i have read! A little to late, My info from fastboot:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA11000)
CPLD-4
RADIO-2.22.19.26I
Apr 20 2009, 15:30:43
I'll go to that tutorial ,see if i can figure it out. Thanks for the help!
EDIT: So, ive read it... But its not clear to me. Do i need to open a terminal like program on my mac and just type in:
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.7.0.img
Or do i need to connect with my phone somehow (besides USB)

Yes, boot in to the SPl (you might need to enable fastboot in there, just poke stuff), then fire up Terminal.app, cd to the /tools directory where the SDK is installed, then issue the commands.

I havent heard of SPL boot yet, how do i do this? Or is this Camer+power on/off?
Also the part about Terminal.app is total abracadabra to mee, haha. ill try and figure it out using the tutorial and maybe some common sense. If i did figure it out, i'll let you guys know!
Otherwise, if u read this and feel like helping... Much appreciated! I can use all the help you can offer!
Thanks!
Tobias

Boot to fastboot mode. Should tell u how on amonra's page. Put recovery in tools folder of your sdk. Then open command prompt on PC and type: fastboot devices hit enter. Should get a serial number. CD to tools folder and type fastboot flash image command in thread
Sent from my HTC Magic SparksMod using XDA App

Glycerin50 said:
I havent heard of SPL boot yet, how do i do this? Or is this Camer+power on/off?
Also the part about Terminal.app is total abracadabra to mee, haha. ill try and figure it out using the tutorial and maybe some common sense. If i did figure it out, i'll let you guys know!
Otherwise, if u read this and feel like helping... Much appreciated! I can use all the help you can offer!
Thanks!
Tobias
Click to expand...
Click to collapse
Yes, the SPL is the bootloader (camera+power). To open the terminal, got to Applications > Utilities > Terminal.

ok, this is getting more and more understandable to me
Just where is this tools SDK folder. Will this apear on my pc when i plug my phone while i bootloader? or do i need to download some more stuff for this all to work on my pc...

U will need to look up how to install sdk on your computer. Its another program u need to control your phone with the PC. Called adb. Android debugging bridge
Sent from my HTC Magic SparksMod using XDA App

I don't think that fastboot comes with the SDK. There is fastboot-mac zip file somewhere out there... I can't remember where I got mine from, but there is one here http://developer.htc.com/adp.html
Put the file somewhere on your mac and use the terminal program in your applications/utilites folder to access it. You should be a little familiar with Linux to use it If you want to get fancy, put it in /usr/sbin or somewhere in your $path.
The SDK kit is good too, especially adb.
EDIT:
Here are a few good threads to get you headed down the path to flash-a-rama. Most of the commands are the same, regardless of platform, but the installation procedure will vary, i.e., fastboot erase system -w does the same thing on any platform.
http://forum.xda-developers.com/showthread.php?t=517874
http://forum.xda-developers.com/showthread.php?t=532719
Lastly this thread should be required reading... http://forum.xda-developers.com/showthread.php?t=655097

SUCCES! YEAH!!! Thank you guys so much! While reading your posts and all the guides i decided to get into bootcamp (windows on mac) and do it all there.
It was way easy to install and ive setup adb and SDK easy and used fastboot to flash Amon Ra's recovery!
It installed within seconds and from recovery i did a fresh wipe and installed my 5.0.8 cyanogen.
Right now it booting up for the first time as i typ and i think its going to boot.... Yes, it takes a long time the first time.
Yes, it works!
Thank you guys again!
Tobias

[Q] WiFi not working

I recently started using the "Froyo Melt" ROM and while it has been better than others, I still have a problem. Whenever I try to turn Wifi on, it gives me an error. This could be due to an incompatible radio or spl but I'm not too knowledgeable on that because I bought the phone rooted and haven't done too much with it.
I'd be grateful for any help I can get, thank you.

well first off power into fastboot by holding the back arrow and power. write down everything on that screen here
then what method did you use to flash your rom --- give us simple step by step

Fastboot says:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005
CPLD-4
RADIO-2.22.23.02
Apr 20 2009, 15:30:43
To flash the rom I put the zip onto an sd card, booted into recovery, wiped data and cache, and then installed it from the zip.

You probably need a different spl/radio for the rom
But you can also try flashing a different kernel
The cm6 one would work with the spl/radio
But then you'd also need to copy all the wifi libs over
Hmmm...you can also try ezgb kernel...it should autodetect your spl/radio

I tried flashing the ezgb kernel but unfortunately it didn't do the trick. How would I go about changing my spl/radio and what should i change it to?

Google "2708+ kernel" or find it in G1 development
Follow the instructions for flashing the spl and radio from fastboot
Then you're gonna probably have to reflash the ROM

i would definitely recommend the 2708+ radio?spl combo, but i dont think it is 100% necessary for froyomelt (but it would make your rom much nicer) if you dont want to bother just do a superwipe and reflash the latest version of your rom, this should fix your wifi issue so long as it is a software not hardware problem.

It sounds like mismatched kernel/radio to me
I had the same problem with my AOSP rom
Had to flash 2708+ spl/radio and ezgb kernel to fix it
And the DreamTeam Froyo post says that it has been tested on the 2708+ spl/radio
So I think that they haven't done anything to enable other spl and radios
If wiping and flashing again does not work, then it probably is spl/radio.

Downloaded the radio and spl stuff but I'm not sure how to install it. I go into fastboot and then Hboot mode and it can't find the images. Is there a certain place I should be putting them and should I leave the radio and spl in a zip?

Download this and unzip it somewhere, like your desktop
http://www.sendspace.com/file/g8rnkq
Copy the img files from inside the dream2708kit zip into the folder
Copy recovery.img to the folder also
Now open command prompt from the shortcut in the folder
Now type the commands you are told to type in the 2708+ thread
Edit: also be careful in downloading
Sendspace has many ads
The file should be adb.zip or similar

After trying to flash the recovery on the command prompt, it gets stuck at "<waiting for device>" and the phone doesn't look like it's doing anything. Did I miss something?

make sure you are booted into fastboot
it will say fastboot usb
you can test by typing in the cmd <fastboot devices>
if you are connected properly you will see your device

Jay67 said:
After trying to flash the recovery on the command prompt, it gets stuck at "<waiting for device>" and the phone doesn't look like it's doing anything. Did I miss something?
Click to expand...
Click to collapse
Go into fastboot usb mode
Do the "fastboot devices" thing
If the phone doesn't show...
Right click on my computer > properties
Go to...I think hardware...then device manager
Find the phone...it most likely will be "android device" or something similar
Right click and do update drivers
Do "no", then "advanced"
Browse to the htc drivers folder and install the fastboot drivers

Thank you, both of you guys. It works perfectly now and runs better than ever! You both deserve trophies.

glad to hear! so you have the 2708+ now and your running froyomelt right?

Yes and it's the fastest version of Froyo i've used yet. Glad to see that my G1 isn't completely obsolete yet.

Jay67 said:
Yes and it's the fastest version of Froyo i've used yet. Glad to see that my G1 isn't completely obsolete yet.
Click to expand...
Click to collapse
Awesome
G1s are pretty awesome no matter what some say
I do so many things from my G1
Even practice some programming!

[Q] RUU - Stuck to "HTC" on screen

Coucou !
I need to put my HTC Desire C back as new, therefore I looked for RUU stuff.
I checked this post: http://forum.xda-developers.com/showthread.php?t=2035480, trying to follow it the more I can. HTC Sync as well as Android SDK (up to date) are present on my laptop using Windows 7 64.
1. I re-lock the phone: fastboot oem lock.
2. I downloaded the RUU from: http://www.androidruu.com/?developer=Golf, file: RUU_GOLF_U_ICS_40A_HTC_Europe_2.00.401.2_Radio_10.11.98.09H_1.06.98.13M2_release_295101_signed.exe
3. I ran with administrator rights the RUU til first screen, asking for agreement.
4. I extracted the recovery_signed.img and flashed it. Fine.
5. I followed the instructions on the screen.
6. It says (translation from french, sorry if it's not exactly what you'll have on an english screen): "checking", "rebooting to bootloader", "waiting for bootloader", "erase user's data" and finally "sending". On my phone screen, there is a white HTC on a black screen.
And it is stuck there. I waited for an hour, still there.
When I disconnect the phone, it says:
- On my computer: error 155: error to image update
- On my phone: a white RUU on an orange background, under classical "*** Relocked ***" (and sometimes "*** Security warning ***") and "GolfU PVT SHIP S-ON RL", then "HBOOT-1.31.000", then "RADIO-1.10.98.15", then "eMMC-boot", then "Jul 12 2012, 15:44:30".
I followed the instruction to "recover" (correct ? button at the bottom and righ of the window), nothing good. I restarted the phone, the laptop, nothing changes.
What can I do?
If you want, I can take screen captures to show you.

i think you also need to flash the stock boot.img

Coucou Bogdy,
First of all, I'd like to thank you for your answer. But, sadly, it didn't work.
I flashed the boot.img, extracted from the "temp" directory , like this:
Code:
fastboot flash boot boot.img
I ran the program and the same thing, stuck on HTC logo, then started the repair stuff, and again stuck on HTC logo.
Does somebody have an idea?

you could also try flashing a stock rom+boot+recovery from http://forum.xda-developers.com/showthread.php?t=2220396&page=2
from what i experienced with a stock based custom rom is that when activating data connection the phone restarts(radio versions differ) so this could happen with a stock rom(not sure)
as for the RUU,i've read that if the hboot version on the phone is higher than the RUU's it won't flash. also i think that the RUU you have only works on european CID but i could be wrong.
you should wait for a more "PRO" answer

Thanks again for your answer, Bogdy.
I'm downloading from the link from the post you suggest me. When it's finished, good or bad, I'll come back.

Coucou !
Well done. Now it's OK, I could flash the original ROM and the phone works perfectly.
Thank you for your help.

BBBenj said:
Coucou !
Well done. Now it's OK, I could flash the original ROM and the phone works perfectly.
Thank you for your help.
Click to expand...
Click to collapse
You could also do this: - lock bootloader
- power on device
- enable adb debugging on device
- make sure you have adb and fasboot working corectly
- connect device via usb to PC
- run RUU with administrator rights
- and from there on just follow the instructions given by software
you really need the 2-4 lines i mentioned up for this to work
no need to flash anything recovery or boot if it's an .exe
if it's a .zip you need to :
flash via custom recovery and flash boot and recovery via fastboot

Coucou Makerrr,
More or less, it is what I've done. I haven't check if adb were working, nevertheless. So it may be the cause of all my problems. But I won't know because I followed Bogdy's way and the job is done, the phone is completly configured, and already in my wife's hand.
Next time, I'll try your way. So thanks a lot.