Related
Hello to all,
This is my first post on this forum. First of all I want to clarify to everyone that I'm spanish and I'll try to explain this in the better way I can. I've searched for similar cases but I don't know how really find a solution to this.
Today I've recivied a HTC Dream from a guy who sold it here in Spain. He said that the phone was crashed the installation of the firmware. What I've is a phone that only shows the boot image (in this case 'Telefonica Movistar', the carrier of the phone).
I can acces to the Recovery Mode by pressing 'Home + Power' and then ALT + L. In the microSD card I've a recovery.zip. It's not mine, I think that the user put on it. I don't really know because its the first Android system I touch.
When I access to the recovery mode, the first message I get is:
Code:
Android system recovery utility
E: Can't open /cache/recovery/command
I wan't to know if there is some way to go a stable version and later update to some modificated ROM with root support and extras.
Thank you in advance.
Sorry for school English.
Isern Palaus
Sorry!! This should go to 'Dream' thread.
Ask here. Read the rules before posting.
http://forum.xda-developers.com/forumdisplay.php?f=507
This post is going to get moved to the Q&A section by the mods shortly, I suspect.
What you need to do is follow the instructions found on this post. They will take you through flashing the old RC9 image (in English), using the SPL rather than recovery mode. You could then, from there, flash a new recovery and ROM. (Can't help you with the language part. Don't know it -- but I'm sure it's out there.)
IConrad01 said:
This post is going to get moved to the Q&A section by the mods shortly, I suspect.
What you need to do is follow the instructions found on this post. They will take you through flashing the old RC9 image (in English), using the SPL rather than recovery mode. You could then, from there, flash a new recovery and ROM. (Can't help you with the language part. Don't know it -- but I'm sure it's out there.)
Click to expand...
Click to collapse
Hello,
First thank to you. And yes, this sould go to Q&A, so if any moderator can move, I tried editting but there is no option.
I'll try it, but I supose that you are saying RC29.
Thank another time.
Isern Palaus
ipalaus said:
Hello,
First thank to you. And yes, this sould go to Q&A, so if any moderator can move, I tried editting but there is no option.
I'll try it, but I supose that you are saying RC29.
Thank another time.
Isern Palaus
Click to expand...
Click to collapse
I think he actually means RC8 for UK versions.
Hello,
I tried to flash it with the RC7 for UK versions and I got: Model ID incorrect! Update fail!
What I see on the top of the screen is:
Code:
DREAM PVT 32B SHIP S-ON
HBOOT-1.38.0000 (DREA20000)
CPLD-4
RADIO-2.22.16.19
Feb 28 2009, 18:40:30
I can try with the RC29... How to know if its US or UK (EU)?
EDIT: The same with RC29.
Thanks in advance,
Isern Palaus
Just noticed your HBoot version. Hopefully you have fastboot. (Press and hold the camera while booting up the phone, with it plugged into your computer via USB cable. Press "back" a few times; you should see "Fastboot USB" in red.)
From there, follow the instructions found here (starting w/ post # 53):
http://forum.xda-developers.com/showthread.php?t=493241&page=6
Has something to do with the fact that the European HTC Dream isn't the same as other Dreams.
From there you should pretty much be able to run any ROM you need. We hope.
As I am in the US and got my G1 during pre-order, I haven't had to go these routes.
Wrong thread
IConrad01 said:
Just noticed your HBoot version. Hopefully you have fastboot. (Press and hold the camera while booting up the phone, with it plugged into your computer via USB cable. Press "back" a few times; you should see "Fastboot USB" in red.)
From there, follow the instructions found here (starting w/ post # 53):
http://forum.xda-developers.com/showthread.php?t=493241&page=6
Has something to do with the fact that the European HTC Dream isn't the same as other Dreams.
From there you should pretty much be able to run any ROM you need. We hope.
As I am in the US and got my G1 during pre-order, I haven't had to go these routes.
Click to expand...
Click to collapse
Thank you! Now I'm in FASBOOT USB, of course.
I've found in this post a link to french site where they're explaining how to install a ROM (cupcake in this case i think): http://wiki.smartphonefrance.info/Default.aspx?Page=firmware-htcdream&AspxAutoDetectCookieSupport=1
In the post the only talk about changing the keys layout. Seems that this link could help, I'll try to understand it.
If you boot up the rooted kernel using fastboot, you //should// be able to run adb remount and then install the flash_image script from elsewhere. (Such as by pulling it out of the CyanogenMod ROM's .zip files)
Drop that script ("flash_image") into your phone's /system/bin folder, and then run (as root) "chmod 755 /system/bin/flash_image"
From there, you /should/ be able to run the "flash_image" script in order to flash a new recovery image (such as the RA-dream-v.1.2.2, or the Cyanogen Recovery 1.4) which would let you, from there, flash a new IPL ("radio") or SPL -- both of which are risky business -- or else you could just flash a new ROM by booting into recovery, as per usual.
The trick is to be able to successfully boot the rooted kernel image via fastboot.
Fact is, if you can do /that/, then you should /also/ be able to simply flash a new recovery image via fastboot (though you'd have to pull it out of the *.zip):
Code:
./fastboot flash recovery /path/to/recovery.img
Hopefully this is all making sense to you.
Now I've my phone full working.
The way to do it was enter with FLASHBOOT USB and use the SDK to boot.
Update with a update.zip (I used a Cupcake 1.5) and update the radios to the latests.
Thanks to all!
HELP!!
my rogers htc dream just bricked on me last night it only goes to the htc logo and the boot loader thing (power key+camera key)
can anyone help me with this
thanks
zerokenshin said:
my rogers htc dream just bricked on me last night it only goes to the htc logo and the boot loader thing (power key+camera key)
can anyone help me with this
thanks
Click to expand...
Click to collapse
What does the bootloader screen sat (power on holding camera )
If it was 1.33.2005 (ie was rooted) install a recovery via fastboot main version if the radio starts with 2, otherwise the -r if it starts with 3
If its 1.33.00?? Go to rogers website and download the january 911 ruu and install it.. if you want root follow the new rogers rooting directions
the bootloader screen says:
DREAM PVT 32B SHIP S-ONd
HBOOT-1.33.0009 (DREA21000)
CPLD-4
RADIO-3.22.20.17
May 12 2009,17:05:58
HBOOT
<SEND>FastBoot Mode
the phone was never rooted it just went out on me after i installed some new apps from the market place
well rooted or not with the perfected spl there is not much choice install the ruu or nbh of the official Rogers 911 rom and follow the new rerooting instructions.
If you follow all of it you will have an engineering split and can get out of this easily if it happens again.
the rogers site has the HTC Dream ROM Update Utility (RUU) January 2010 is that the right thing cause if so its not working for me
zerokenshin said:
the rogers site has the HTC Dream ROM Update Utility (RUU) January 2010 is that the right thing cause if so its not working for me
Click to expand...
Click to collapse
I can't say I've ever made the RUUs work short of extracting the NBH file from your users temp directory and flashing it manually... but I always assumed I just was lazy on making the phone connect to VMWare on a mac.
Try this:
0) install fastboot/adb if you don't already have them (again I'm on a mac search for it if you need help)
1) Download http://www.rogers.com/dream-zip
2) extract DREAIMG.nbh from the zip file and put it into a directory accessible from fastboot
3) enter fastboot mode on the phone
4) run 'fastboot oem rebootRUU' to put the phone into ruu usb mode
5) run 'fastboot flash nbh DREAIMG.nbh' (specifying the rogers nbh)
5b) wait for everything to flash .. this will take a few mins
6) if the phone dosn't reboot its self run 'fastboot oem powerdown' then boot normally
Once installed + running your re-rooting info is here: http://forum.xda-developers.com/showthread.php?t=733128
i dont understand step 2
2) extract DREAIMG.nbh from the zip file and put it into a directory accessible from fastboot
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.
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
Hi there.
This is not the first problem I have had with my G1 and Cyanogen cm5 or cm6. Yesterday my phone was working just fine, battery got low so I turned it off and out it on the charger. So I go to turn the phone on and I am stuck at the bootscreen.
I can get into fastboot use the cam/power button combo. But I can not get into recovery at all.
At the hboot/fastboot screen I have the following listed, BTW it's the screen with the 3 androids at the bottom on skateboards.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (Drea10000)
CPLD-4
RADIO-2.22.23.02
Apr 20 2009, 15:30:43
When I switch over to Fastboot then back to Hboot screen I get this.
SD checking.
Loading...[DREADIAG.zip]
No image!
Loading...[DREADIA2.nbh]
No image or wrong image!
Loading...[DREADIAG.nbh]
No image or wrong image!
SD Checking...
Loading...[DREADIAG.zip]
No image!
Loading...[DREADIA2.nbh]
No image or wrong image!
Click to expand...
Click to collapse
What can I do to get back in business? If I have to put it back to stock, that is fine. I plan on selling it and getting the new Samsung Vibrant.
I have to stock 1gb card in the G1 right now. I have the following files on it.
recovery.img
update.zip
DREAIMG.nbh
In fastboot I get this for device.
HT852GZ12970
UPDATE:
I have been able to flash recovery via fastboot, now just trying to get a good image on there to reflash.
Also curious about this.. friend's having the same problem with the same rom.
Well I am back up and running.
What I had to do was flash a new recovery image using fastboot. Once I did that I was able to boot into recovery; wipe everything and reflash a new ROM (went with SuperBad, since CM keeps messing me up).
If you need more details, let me know.
svtcontour said:
Well I am back up and running.
What I had to do was flash a new recovery image using fastboot. Once I did that I was able to boot into recovery; wipe everything and reflash a new ROM (went with SuperBad, since CM keeps messing me up).
If you need more details, let me know.
Click to expand...
Click to collapse
I was going to tell you to do just that until I read:
UPDATE:
I have been able to flash recovery via fastboot, now just trying to get a good image on there to reflash.
Click to expand...
Click to collapse
I thought you had figured it out already. I probably could have saved you some time. Sorry.
How did you flash recovery in fastboot? Right now I am going through the same thing that you did!
I have a G1/Cyanogen 5.0.8
mjybarr said:
How did you flash recovery in fastboot? Right now I am going through the same thing that you did!
I have a G1/Cyanogen 5.0.8
Click to expand...
Click to collapse
Code:
fastboot flash recovery recovery.img
The standard procedure is to power on the phone with camera/power button combo, be sure to get the phone into fasboot mode.
Open up the CMD window in windows, CD to the directory you have the recovery.img file in. Use the above command. Then you can wipe and reinstall the update.zip with another rom.
That should do it,l assuming you already installed all the USB and ADB drivers and software.
svtcontour said:
Code:
fastboot flash recovery recovery.img
The standard procedure is to power on the phone with camera/power button combo, be sure to get the phone into fasboot mode.
Open up the CMD window in windows, CD to the directory you have the recovery.img file in. Use the above command. Then you can wipe and reinstall the update.zip with another rom.
That should do it,l assuming you already installed all the USB and ADB drivers and software.
Click to expand...
Click to collapse
So what is CMD and what do you mean "CD to the directory you have the recovery.img file in." I did some research on xda-forums about adb, sdk, fasboot. Do I need to do that and install all those programs. As you can tell I am a new to this. So I need some thorough directions. Thank you so much for helping. I need to get back to Android, right now I am using an old blackberry......and it totally sucks!
CMD will bring up the DOS window in windows. Go to the START button and look for RUN, them type in CMD. A black window will pop up.
CD means change directory. Example: cd c:\temp\adb will bring you to that exact directory. Just make sure you remember where you put the recovery.img file and CD to that.
I would go to this post and follow the directions to install ADB and the USB drivers.
http://androidcommunity.com/forums/f10/adb-fastboot-for-rookies-18124/
I had the same problem in a rooted Hero, but i lost the recovery image as well as the ROM. I could not flash the new recovery image using fastboot because my SPL does not allow it.
Search in google for
Follow the instructions in
wiki.cyanogenmod.com/index.php?title=RE-recovery-img#Restoring_the_custom_recovery_image
to flash a recovery image (cyanogen or amon-ra, just check it to be the one for your model).
It solved my problem!
I have the same problem (with CM6)
adb works well, but fastboot is waiting for devices
G1 is on fastboot usb screen
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA20000)
CPLD-4
RADIO-2.22.19.261
Apr 20 2009,15:30:43
the command "fastboot devices" doesn't work : i don't even have a feedback like "list of devices attached"
does anyone know what I have failed ?
Update: miserable failure: I forgot to cd to C:\path\android-sdk-windows\tools\
sorry about it
Reinstalling recovery, then installing the latest nightlies did the trick for me. Did not need to wipe.
Hope this helps.
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.