Database Users

Noob trying to flash to 2.1d

I have successfully flashed my Sprint THC hero with no problems.
My issue though is flashing the phone to 2.1d. i can't for the life of me follow these directions and I am really stumped on the process of doing a nandroid and flashing the ROM.
I downloaded the nandroid from this site but not sure where I put the directory with the files at. Can anyone break this process down into "ejpyle terminology"?
My problems are:
- where to copy the nandroid directory
- where to put the 2.1d ROM
- do i need this busybox that everyone is talking about?

Successfully flashed what? And what method.
If you mean you successfully ROOTED your Phone then huzzah, that's step one complete.
Part of the rooting process should include putting a recovery image on the phone. If you did that correctly then do this, power off the phone.hold down the home button and power it back up. In a few seconds you should boot into a recovery menu with options to do a nandroid backup/restore turn on the usb connection to move files to the phone from your pc, and flashing a zip. If you don't have this recovery menu then you need to install it.

I don't think you have downloaded a Nandroid, I think you have downloaded an "update.zip" as we so affectionitly call them around here. This is a term used from the first set of recovery tools we had, where we had to rename update files update.zip to be loaded. Thankfully the recovery software has been updated to let us store and use multiple files.
So you probable have fresh-cdma-hero-2.0d.zip downloaded.
Plug your phone into USB and set it to Mount SD Card or what ever it says in 1.5
Copy this file to the root of the sdcard. don't put it in to any folders just F:\ or whatever the drive letter is.
THEN
Unmount the sdcard or turn off the disk drive mode (Cant remember what 1.5 calls it)
THEN
Power off the phone.
Power the phone back on whilst holding the home key. When you feel the vibration (let your girl hold it if she wants ROFL) let go and it will boot into recovery.
THEN
Go to Wipe...do Factory Reset
THEN
Wipe dalvik
THEN
Go back to Flash Update from SDcard
Select the update file above and hit the home key to flash it.
The phone SHOULD install and go back to the main screen of recovery.
THEN select
Reboot
THEN
Wait a hell of a long time 10+ minutes is NOT uncommon (it has to rebuild dalvik and other stuff)
THEN
When the phone boots hit Always Allow for the memory settings app.
THEN
Setup all your google info again.....
THEN
You should be good to go
AND DEN????????
HAHAHAHAHAHAHA
EDIT:
I am SURE that I left a step out above, just go with the flow and wipe everything under the wipe menu. It's laid out so a monkey can do this stuff...hence the reason I am able to.

gunnyman said:
Successfully flashed what? And what method.
If you mean you successfully ROOTED your Phone then huzzah, that's step one complete.
Part of the rooting process should include putting a recovery image on the phone. If you did that correctly then do this, power off the phone.hold down the home button and power it back up. In a few seconds you should boot into a recovery menu with options to do a nandroid backup/restore turn on the usb connection to move files to the phone from your pc, and flashing a zip. If you don't have this recovery menu then you need to install it.
Click to expand...
Click to collapse
thank you thank thank you... you have me going in the right directions.
Quesion..what is the best (most reliable without as many bugs) ROM to load that is 2.0-1?

ejpyle said:
thank you thank thank you... you have me going in the right directions.
Quesion..what is the best (most reliable without as many bugs) ROM to load that is 2.0-1?
Click to expand...
Click to collapse
Not to be rude, because you seem like a decent enough person, but please read http://forum.xda-developers.com/showthread.php?t=668905 before asking anything else. Most of your answers are there, and 'search' will find the rest.

Kcarpenter said:
I don't think you have downloaded a Nandroid, I think you have downloaded an "update.zip" as we so affectionitly call them around here. This is a term used from the first set of recovery tools we had, where we had to rename update files update.zip to be loaded. Thankfully the recovery software has been updated to let us store and use multiple files.
So you probable have fresh-cdma-hero-2.0d.zip downloaded.
Plug your phone into USB and set it to Mount SD Card or what ever it says in 1.5
Copy this file to the root of the sdcard. don't put it in to any folders just F:\ or whatever the drive letter is.
THEN
Unmount the sdcard or turn off the disk drive mode (Cant remember what 1.5 calls it)
THEN
Power off the phone.
Power the phone back on whilst holding the home key. When you feel the vibration (let your girl hold it if she wants ROFL) let go and it will boot into recovery.
THEN
Go to Wipe...do Factory Reset
THEN
Wipe dalvik
THEN
Go back to Flash Update from SDcard
Select the update file above and hit the home key to flash it.
The phone SHOULD install and go back to the main screen of recovery.
THEN select
Reboot
THEN
Wait a hell of a long time 10+ minutes is NOT uncommon (it has to rebuild dalvik and other stuff)
THEN
When the phone boots hit Always Allow for the memory settings app.
THEN
Setup all your google info again.....
THEN
You should be good to go
AND DEN????????
HAHAHAHAHAHAHA
EDIT:
I am SURE that I left a step out above, just go with the flow and wipe everything under the wipe menu. It's laid out so a monkey can do this stuff...hence the reason I am able to.
Click to expand...
Click to collapse
You rock....You just taught a death and blind monkey how to do it. Thanks man!!!!! I will be sure to have my wife hold the phone for the vibrate thing. LMFAO

ejpyle said:
thank you thank thank you... you have me going in the right directions.
Quesion..what is the best (most reliable without as many bugs) ROM to load that is 2.0-1?
Click to expand...
Click to collapse
There is no best one. The 2.1 ROMS are all very stable. Just avoid the ones that say {DEV} in the thread title because they are under development and likely have lots of stuff broken in them.
Decide what you want for yourself, beauty, speed, both? A good hint is to look for the ROM threads that have the most pages attached to them these are the ROMS that have the most discussion and help within them.

ejpyle said:
You rock....You just taught a death and blind monkey how to do it. Thanks man!!!!! I will be sure to have my wife hold the phone for the vibrate thing. LMFAO
Click to expand...
Click to collapse
DO NOT FLASH THE 2.1 Signed RUU Test ROM
OR I WILL FIND AND KILL YOU!

gunnyman said:
There is no best one. The 2.1 ROMS are all very stable. Just avoid the ones that say {DEV} in the thread title because they are under development and likely have lots of stuff broken in them.
Decide what you want for yourself, beauty, speed, both? A good hint is to look for the ROM threads that have the most pages attached to them these are the ROMS that have the most discussion and help within them.
Click to expand...
Click to collapse
thanks man, if I win the power ball lottery I will be sending you all a private message.
one more quickie though, If Sprint releases the 2.1 before I become eligible for AARP will I have to flash back to the 1.5 version before updating my device with it?

Kcarpenter said:
I don't think you have downloaded a Nandroid, I think you have downloaded an "update.zip" as we so affectionitly call them around here. This is a term used from the first set of recovery tools we had, where we had to rename update files update.zip to be loaded. Thankfully the recovery software has been updated to let us store and use multiple files.
So you probable have fresh-cdma-hero-2.0d.zip downloaded.
Plug your phone into USB and set it to Mount SD Card or what ever it says in 1.5
Copy this file to the root of the sdcard. don't put it in to any folders just F:\ or whatever the drive letter is.
THEN
Unmount the sdcard or turn off the disk drive mode (Cant remember what 1.5 calls it)
THEN
Power off the phone.
Power the phone back on whilst holding the home key. When you feel the vibration (let your girl hold it if she wants ROFL) let go and it will boot into recovery.
THEN
Go to Wipe...do Factory Reset
THEN
Wipe dalvik
THEN
Go back to Flash Update from SDcard
Select the update file above and hit the home key to flash it.
The phone SHOULD install and go back to the main screen of recovery.
THEN select
Reboot
THEN
Wait a hell of a long time 10+ minutes is NOT uncommon (it has to rebuild dalvik and other stuff)
THEN
When the phone boots hit Always Allow for the memory settings app.
THEN
Setup all your google info again.....
THEN
You should be good to go
AND DEN????????
HAHAHAHAHAHAHA
EDIT:
I am SURE that I left a step out above, just go with the flow and wipe everything under the wipe menu. It's laid out so a monkey can do this stuff...hence the reason I am able to.
Click to expand...
Click to collapse
I hope the possible step left out above does not give me "another" bricked phone.

ejpyle said:
I hope the possible step left out above does not give me "another" bricked phone.
Click to expand...
Click to collapse
I think I may have left out a step if you have apps on your sd card...
NOT WAIT I LEFT OUT THE DO A NANDROID BACK UP FIRST!!!!!!!!!!! DO THAT FIRST!!!! HOLY CRAP I HOPE YOU HAVEN'T DONE ANYTHING YET!!! DO A NANDROID!!!!!!!
Nope no chance at all of that as far as I can tell.
The only bricks we have seen are from people downloading GSM software or dropping a brick on their phone...that sounded funnier in my head.

smw6180 said:
Not to be rude, because you seem like a decent enough person, but please read http://forum.xda-developers.com/showthread.php?t=668905 before asking anything else. Most of your answers are there, and 'search' will find the rest.
Click to expand...
Click to collapse
Because you too seem like a decent person I will share this with you....
I followed a thread on here at the beginning of march to install a ROM and the directions (which I followed exact) bricked my phone. I spent hours reading up on this website to find out after the fact that the RUU might have a bug and some users will have issues. With that said, I decided to ask questions. This site has a lot of cleanup going on (no disrespect to anyone here as you are all VERY intelligent) and I do not think that someone as myself would be comfortable just "searching" for the answer without asking questions first with respect to the experience we have had in the past.

Kcarpenter said:
I think I may have left out a step if you have apps on your sd card...
NOT WAIT I LEFT OUT THE DO A NANDROID BACK UP FIRST!!!!!!!!!!! DO THAT FIRST!!!! HOLY CRAP I HOPE YOU HAVEN'T DONE ANYTHING YET!!! DO A NANDROID!!!!!!!
Nope no chance at all of that as far as I can tell.
The only bricks we have seen are from people downloading GSM software or dropping a brick on their phone...that sounded funnier in my head.
Click to expand...
Click to collapse
LOL I have not done it yet. I am about to copy this nandroid - file name "nandroid-2.0.zip" to my SDCARD. then i will do it.

ejpyle said:
LOL I have not done it yet. I am about to copy this nandroid - file name "nandroid-2.0.zip" to my SDCARD. then i will do it.
Click to expand...
Click to collapse
So you have gotten me curious now, where did you pick up that file at?
My only guess is that someone has posted a nandroid of their device and zipped it. Most of the Rom downloads are ROMNAME.zip....
You can always try to load it, it won't load if its not setup properly inside for a rom.
And about your going back to 1.5 to update to sprints 2.1:
IF YOU UPDATE TO SPRINTS OTA 2.1 UPDATE YOU WILL NOT BE ABLE TO ROOT AGAIN UNTIL SOMEONE FINDS ANOTHER EXPLOIT!!! WHICH COULD BE NEVER!!

Kcarpenter said:
So you have gotten me curious now, where did you pick up that file at?
My only guess is that someone has posted a nandroid of their device and zipped it. Most of the Rom downloads are ROMNAME.zip....
You can always try to load it, it won't load if its not setup properly inside for a rom.
And about your going back to 1.5 to update to sprints 2.1:
IF YOU UPDATE TO SPRINTS OTA 2.1 UPDATE YOU WILL NOT BE ABLE TO ROOT AGAIN UNTIL SOMEONE FINDS ANOTHER EXPLOIT!!! WHICH COULD BE NEVER!!
Click to expand...
Click to collapse
I got it from here....
http://dx.infernix.net/nandroid-2.0.zip

when you boot into recovery, what do you see?
If you rooted correctly and put a recovery image on there there isn't anything else you have to do to enable Nandroid.

ejpyle said:
I got it from here....
http://dx.infernix.net/nandroid-2.0.zip
Click to expand...
Click to collapse
Ok, so this leads me to another question. Where is the thread that links to this download?
The reason I am worried about this file now that I see it:
It's only 942kb - WAY to small for a rom or nandroid.

gunnyman said:
when you boot into recovery, what do you see?
If you rooted correctly and put a recovery image on there there isn't anything else you have to do to enable Nandroid.
Click to expand...
Click to collapse
I had a triangle with an exclamation point.
I am copying the recovery to my SDCARD now... recovery-RA-heroc-v1.5.2

ejpyle said:
I had a triangle with an exclamation point.
I am copying the recovery to my SDCARD now... recovery-RA-heroc-v1.5.2
Click to expand...
Click to collapse
1.6.2 is the latest. Not a whole lot different from 1.5.2 but some bugs where fixed and you can get the nifty Green Nexus Carebear back ground.

Kcarpenter said:
1.6.2 is the latest. Not a whole lot different from 1.5.2 but some bugs where fixed and you can get the nifty Green Nexus Carebear back ground.
Click to expand...
Click to collapse
I copied everything you indicated to my card. When I press HOME and PWR together I get a triangle with an exclamation point. Did this monkey not do something right?

Sprint / HTC Policy

I have officialy given up on repairing my phone. Looks like it's not possible to fix this thing. Just spent the better part of 3 pays (4hours of sleep a night) trying to get my phone fixed. My sister bought this EVO through some work deal and gave me it on Christmas. I rooted it that night, and bricked it 30mins later, because of the newer partition scheme it is currently impossible to get this phone back working...
This is what I have now. A EVO 4G that boots normally to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
A Vol Down + Power Boot boots to this screen. ftp://eto.homeip.net/shared/IMAG0004.jpg
I can also navigate to this screen. ftp://eto.homeip.net/shared/IMAG0005.jpg
Because of the S-OFF it is obvious to those in the know that I rooted my phone.
I'm just wondering if you guys think this scenaro will work.
_________________________________________________________________
Walk into a Sprint Repair Store, tell them my sister just bought the phone new (about a week ago) and gave it to me as a X-Mas gift. I chose to do the latest OTA-Update, and after it stopped booting and only went to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
Where I'd have to pull the battery to turn it off.
They will probably try VolDown+Power and might comment on S-OFF (which I will say I don't know what that is).
Hope they give me a new/refurbished EVO for free or less then $50.
===============================
Questions
* Should I go to a Sprint Store I've never been to? (There are stores within 20miles of me) (Closest knows I root phones, then other I've been into a bunch of times and may have given up on me)
* Should I get the receipt from my sister, who I don't want to tell I rooted/bricked phone
* Call ahead of time and see what they say on the phone?
* Also please give me suggestions of anything that will help
BTW
* Am well within 30days of buying phone, though I'm not sure if my sister bought it through Sprint or not (Think she did though)
* I have pin/name/number on account and can easily activate a different phone they give me.
* Would rather not tell my sister or even get the receipt from her room to keep her from suspecting anything, but can if need be
Thanks for your suggestions, wanted to get this done by the end of the week before I head back down to San Luis Obispo for college. (Where there are fewer Sprint Stores to spam)

I don't know what the policy is.... most likely, as soon as they see where you're at, the tech will figure out that you were trying to root your phone, and you'll be SOL.
Have you tried booting your phone via ADB? Maybe you can go into recovery via adb shell and see if you can go from there....

if you can get it to power up all is not lost, try pushing AMON's recovery via fastboot
Fastboot
Copy recovery-RA-evo-v1.8.0.img in your android-sdk-windows\tools\ folder
Boot your phone into fastboot mode
fastboot devices(press enter) (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-evo-v1.8.0.img(press enter)

Since your phone turns on and you can boot into fastboot. Bricked would mean nothing happens period. There's still hope. Try this thread: http://forum.xda-developers.com/showthread.php?t=780141. There's a video walk-through showing you how to unroot and return to s-on. Then you may be able to start over.
Good Luck!
-kp
Edit: Try GMan's suggestion above 1st.

Sorry guys, itried all that stuff yesterday for several hours in the irc.
*adb doesn't recognize device (if you can help me with this that would be great)
*fastboot works but always gives
Code:
writing 'recovery'... FAILED (remote:image update error)
*flashes in hboot except for Radio_V2 always give
Code:
Parsing...[SD ZIP]
[1] RECOVERY - Fail-PU
Partition update fail!
Update Fail!
It's all in the opening post of the first thread I linked. Wanted to keep that thread about fixing my phone, and this one about getting it back to Sprint / HTC. Thanks

Do you have TEP on this device? If so, and you were to accidentally drop your phone in a very deep lake, river or ocean, you would be covered for loss with a $100 deductible. You can add TEP in the first 30 days, if you don't already have it.

indagroove said:
Do you have TEP on this device? If so, and you were to accidentally drop your phone in a very deep lake, river or ocean, you would be covered for loss with a $100 deductible. You can add TEP in the first 30 days, if you don't already have it.
Click to expand...
Click to collapse
Sprint Insurance right? I don't... I might do that but that's my last resort.

josh4trunks said:
Sorry guys, itried all that stuff yesterday for several hours in the irc.
*adb doesn't recognize device (if you can help me with this that would be great)
*fastboot works but always gives
Code:
writing 'recovery'... FAILED (remote:image update error)
*flashes in hboot except for Radio_V2 always give
Code:
Parsing...[SD ZIP]
[1] RECOVERY - Fail-PU
Partition update fail!
Update Fail!
It's all in the opening post of the first thread I linked. Wanted to keep that thread about fixing my phone, and this one about getting it back to Sprint / HTC. Thanks
Click to expand...
Click to collapse
If you can boot into the hboot just run a ruu and restore the factory Rom, if all fail pm me your number and I will walk you thru it
Sent from my PC36100 using XDA App

shameless bump - completely changed opening post

I could be completely wrong but it's my understanding that, as long as you can get into the hboot, all hope is not lost. I thought I had bricked my wife's Evo when I was rooting it last week.
What worked for me was:
1. Take the SD card out and put it in a PC.
2. Clear out all files on the root of the SD card. (Not sure if this is needed but it's what I did. I left the folders in place though.)
3. Download the appropriate stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=838448 (Thanks xHausx!!)
4. Rename the ROM to PC36IMG.zip and place it on the root of the SD card.
5. Place SD card back in the phone and boot into hboot.
6. Your phone should detect the PC36IMG.zip and take forever to load it before asking you if you want to install. Say yes to the install and let it reboot after the install.
This brought my wife's phone back to stock so I could attempt the root again. My wife's phone is a white 0004 that came stock with 3.30.651.3 on it. I downloaded the 3.30.651.2_PC36IMG.zip from the site above and it worked just fine.
This is what worked for me but results may very. I'm still a nOOb with this, having just came from a Pre, you may want to wait till someone else comfirms that the above will work...
Hope this helps!

haplo1818 said:
I could be completely wrong but it's my understanding that, as long as you can get into the hboot, all hope is not lost. I thought I had bricked my wife's Evo when I was rooting it last week. What worked for me was:
1. Take the SD card out and put it in a PC.
2. Clear out all files on the root of the SD card. (Not sure if this is needed but it's what I did. I left the folders in place though.
3. Download the appropriate stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=838448 (Thanks xHausx!!)
4. Rename the ROM to PC36IMG.zip and place it on the root of the SD card.
5. Place SD card back in the phone and boot into hboot.
6. Your phone should detect the PC36IMG.zip and take forever to load it before asking you if you want to install. Say yes to the install and let it reboot after the install.
This brought my wife's phone back to stock so I could attempt the root again. My wife's phone is a white 0004 that came stock with 3.30.651.3 on it. I downloaded the 3.30.651.2_PC36IMG.zip from the site above and it worked just fine.
This is what worked for me but results may very. I'm still a nOOb with this, having just came from a Pre, you may want to wait till someone else comfirms that the above will work...
Hope this helps!
Click to expand...
Click to collapse
Tried this multiple time with different PC36IMG.zip, always get Failed-PU
Partition Update Error, I might try the 3.30 version though just to make sure.

Won't like my opinion but, you knew the risks of rooting. If you can't fix your phone then you should add the insurance and suck up the deductible fee. You don't deserve (or anyone for that matter) a free replacement for ****ing up your phone. It sucks but that's the risk. They'll normally have you one the next day.

Your phone is definitely not bricked and is fixable. Do you have adb drivers installed on your PC? If not find them and install them then try this: http://forum.xda-developers.com/showthread.php?t=829045?
Since you are already s-off you won't have to do all the steps, but by reading the entire OP you could figure out where to start and what to do. Just to be on the safe side you may want to start at the beginning using HBOOT USB from this screen you posted ftp://eto.homeip.net/shared/IMAG0004.jpg and start completely over. you are not bricked. Just hang in there and someone here will get you hooked up. You are in the right place my friend.
Evo's are really not that easy to fully brick.

I know whats wrong with your phone problem is i don't know how to exactly fix it! When you tried to root it after taking the OTA or upgrading the HBOOT you messed up the partition table thats why you can't flash a rom what you need to do is try to run a ruu back to stock and then try to reroot but untill you get the partition table fixed you have a phone that is nand unlocked and can't flash any rom the ruu rewrites the partition table if your phone came with 3.70 then use that ruu but if you took the ota then run the 3.30 should work don't do a PC36IMG run the RUU in fastboot usb mode

Have you tried using a different SD card? Is it possible that something is corrupt with it? I also hear that you need to have at least 1GB of free space on the card when your trying to flash it.....

Let me just say myself and this guy stayed up late last night working on this phone trying every possible root/unroot method you can think of.
The pc he is using has adb drivers installed but the computer wont recognize his device as a adb device. Fastboot on renders certain commands and we tried all with various recoveries. I hit up a dev and we went thru different things and cant seem to figure this one out
As I told the Josh it can not be bricked because we get the bootloader and fastboot screen, I think its not even the partition but the recovery. Also he has a modified hboot by someone on xda (josh please post the link) which I believe that pc36img is whats causing all the problems.
If anyone could help it would be appreciated!!

Jbcarrera said:
I know whats wrong with your phone problem is i don't know how to exactly fix it! When you tried to root it after taking the OTA or upgrading the HBOOT you messed up the partition table thats why you can't flash a rom what you need to do is try to run a ruu back to stock and then try to reroot but untill you get the partition table fixed you have a phone that is nand unlocked and can't flash any rom the ruu rewrites the partition table if your phone came with 3.70 then use that ruu but if you took the ota then run the 3.30 should work don't do a PC36IMG run the RUU in fastboot usb mode
Click to expand...
Click to collapse
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.

craigbailey1986 said:
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.
Click to expand...
Click to collapse
I'm sure he thought you needed the engineering SPL to be able to flash roms. When I rooted mine back in June with toast's method, that was the way to do it. I rooted my girl's new Evo last month using Unrevoked, and I also downgraded the hboot because I thought I had to in order to flash a custom rom. Fortunately, I was able to do so with no issues.

Cleared all the caches?

craigbailey1986 said:
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.
Click to expand...
Click to collapse
The partition table is screwed but there has to be a way to reset it I knew that method was risky told my friends to stay away from it
Sent from my EVO at the edge of hell

Trying to root - problems [SOLVED]

Hey guys.
I've been attempting this all morning and so far I've had no luck. I have a VodafoneAU Legend which I updated to the official 2.2 yesterday. But now I want to try root.
I've been trying to follow the HBOOT 1.01 guide but there's a few problems. First, I cannot connect to the phone with adb unless it's in htc sync mode. No other mode will work. So when it's time to copy testimage.zip to the card I have to change from sync mode to disk mode, whereby adb loses it's connection. What do I do about this? Is it a driver problem (in Win7 here) or something else?
Thanks,
Dave.

Ok, the first problem were drivers.
Now I can't finish the second guide. When I try using clockwork to install the firmware.zip, the phone just boots to the red triangle. What do I have to do?
Dave.

So I pressed the up button/power combo at the red triangle and get the Android system recovery. Selecting "apply update.zip" says it can't verify. What do I do? Is this guide for my phone or do I need to follow something else?

I don't understand this guys. Anyone help? I'm thinking since this is a step to root the phone, I'm not actually rooted yet so I can't use the clockworkmod? Then what is the guide for? The guides at unlockr don't mention what firmware/hboot they work for so I'm not keen to try them yet.

Read the guide on fake flash. You need the recovery file named "update.zip" in the root of your sd to proceed..
Sent from my Legend using XDA App

whitetigerdk said:
Read the guide on fake flash. You need the recovery file named "update.zip" in the root of your sd to proceed..
Sent from my Legend using XDA App
Click to expand...
Click to collapse
But isn't that what Rom Manager does? Download the update.zip then run it? Man this is getting even harder to understand.
Edit: And this is left out of the HBOOT 1.01 guide because.....????? When I work this out I'll write a PROPPER guide, lol.

Just checked and update.zip is on the card.
So which part of the guide am I getting wrong?

Decided to reinstall phone with the official froyo release and am now ready to try this again. Is there anyone that will walk me through the process? I will write a complete guide if the "gotchas" are still there.

i feel for you ... hope you get it fixed... thats one of the reason i havent dared messing with the phone because i've seen a few post like yours where something didnt go quite as described... for whatever reason... and im sure the answer is out there but just not within the guide instructions... i guess there is no way to gather all gotchas because there are so many environment variables...
good luck
and please share your technique

Just saw gobczak's thread in the developer forum having similar troubles with Vodafone UK phone, getting the red triangle at reboot. I'll keep an eye on his thread and see how he goes with it.

Did you run the stage1 and stage2 bats while in recovery?

dezzadk said:
Did you run the stage1 and stage2 bats while in recovery?
Click to expand...
Click to collapse
No because the guide didn't say to.
The thing is it seems I'm only stuck on the part where the firmware.zip file has to be flashed. The guide says to use clockworkmod for this. But when I try installing the clockworkmod recovery it gives some file verification error. Isn't there ways to do this via the pc, either through those batch files, adb etc? Or will that fake-flash update.zip file work?

jabbado said:
No because the guide didn't say to.
Click to expand...
Click to collapse
As I just posted on the other forum, I think you need to skip that step in guide 2 and go straight onto guide 3 after you have flashed the LEGEIMG.zip, rebooted, and then removed LEGEIMG.zip from the SD card.

Guys I've got to the point of downgrading to 1.31. But when I run the first batch file it just hangs at the "Writing zip" part, with the htc logo on the screen. Is there any way to fix this?

Can someone please explain this part of the guide:
Phone will reboot and find LEGEIMG.zip on your sdcard, copy it into RAM and check it. If you get CID error at this point, then you don't have goldcard.
Click to expand...
Click to collapse
Ok, so I don't get an error. I get nothing. The phone just boots to the fastboot screen. If I press the power button it goes to the hboot screen and I can see the messages of loading LEGEIMG.zip. But the guide doesn't say to press anything.
So should I or shouldn't I press the power button? Also, if I try making the goldcard again, at which point in the guide do I start from again? The entire process or just copying LEGEIMG.zip to card then rebooting phone? I mean, will all the other things like flashing misc1-2.img still be there?

Guys I finally got this working.
The first problem was with the goldcards. For whatever reason formatting them with the win7 format tool just wouldn't work. I had to use the command-line format tool, setting the block size etc manually.
The second problem was the unnecessary steps in the guide. A few people helped me out with this (namely blackbart at the Aus Whirlpool forum), but basically in the second step you can stop after flashing the LEGEIMG.zip. The updating froyo part isn't needed - for my phone anyway.
Then when running the batch files in the third part, for whatever reason the first batch would keep hanging at 'writing zip...' and I needed to remove the battery to unfreeze the phone. flannigan, also from the Aus Whirlpool forums suggested to just go on to the second batch file. This worked!
So my Legend is now finally a true Legend
Anyway, thanks for the help everyone - couldn't have done this by myself.
Dave

Great news, I think we need a new guide focused on rooting for HBOOT 1.01 / Stock Froyo to clear up the inconsistencies in the existing one. It's a minefield for a noob (or a rite of passage!), a revised guide will certainly save a lot of time and frustration for those taking this road in the future.
Sent from my HTC Legend using XDA App

EpicSauce said:
Great news, I think we need a new guide focused on rooting for HBOOT 1.01 to clear up the inconsistencies in the existing one. It's a minefield for a noob (or a rite of passage!), a revised guide will certainly save a lot of time and frustration for those taking this road in the future.
Click to expand...
Click to collapse
I'll write one if ya's want. I wanted to include little tidbits like downloading the apps required (visionary, rom manager etc) from the market then backing them up to the card with Astro so if it goes all wrong and you have to start again, you can just install them all from the card Also on using adb to push the files (roms, img's etc) when the guides say "copy this blah blah". Much quicker than changing to disk mode and back. Sound good?

Sounds good! Happy to help and add my 20c worth along the way. The existing guide has got the meaty bits, a new guide would cull the stuff not relevant, help fill in the gaps and alert to the pitfalls we've fallen into.

jabbado said:
I'll write one if ya's want. I wanted to include little tidbits like downloading the apps required (visionary, rom manager etc) from the market then backing them up to the card with Astro so if it goes all wrong and you have to start again, you can just install them all from the card Also on using adb to push the files (roms, img's etc) when the guides say "copy this blah blah". Much quicker than changing to disk mode and back. Sound good?
Click to expand...
Click to collapse
I agree... i've done my reading since june of last year but then didnt check for another 4 months... and so many how to's pop up with various ways of doing it depeding on the situation... a lot of those howtos were consolidated howtos which sometimes make intermediate steps unenecessary (may be in some cases causes more head aches since it didnt take into considerations on newer version of hboots...etc)... an updated how to will be much appreciated...
And you're right the most important pre requirement is to have a safety net ... so starting with how to create a back up in case you screw it up is a must!
but im glad it worked out for you!

[Q] Charger port broke, phone rooted, what now?

My EVO doesn't charge anymore. Guess my port got broken. My phone is rooted, and I dont have PC syncing capabilities. Is there a way to restore my phone back to the stock sprint rom so i can take it in for service or get a new phone? Does a hard reset restore the stock sprint rom? Im running the MIUI rom As u can tell im sort of a newb

Find a PC36IMG file of a stock, unrooted ROM and flash it through the bootloader.

Get a cheap standalone battery charger on ebay. While you're at it, get a microSD card adapter that you can load into a SD card reader. Charge your battery that way since the micro-usb doesn't work. Pull out your microSD card from the phone and load into adapter. Put an RUU file onto the microsd through your comp then put the microsd back into phone with the charged battery and you should be back to stock.
Another option, just bring to Sprint store and have them fix the micro-usb port. Their policy has changed and they should repair your phone even if it's rooted.

Make sure you have a fully charged battery before going back to stock. Download the unrevoked s-on tool from the unrevoked website, along with the most recent RUU in PC36IMG.zip form. Make sure that the RUU is named correctly - all caps, only one zip at the end. You will not need to add .zip to the end in the process of renaming.
Boot the phone into recovery & flash the s-on zip. Power the phone down and boot into the bootloader via volume down + power buttons. Make sure it says "Ship S-on" at the top. The phone will scan and find the RUU (as long as it's on the root of the card and named correctly), then ask you to update. Choose yes, then wait for it to flash. When it's done, choose yes when it asks you to reboot and you'll be good to go.
While Sprint will fix rooted phones with hardware problems, a broken port is not fixable. You also don't want them flagging your account. You will have to get a new phone, so you can toss any nandroid backups - do not attempt to restore them on your new phone. While it may be possible, you don't want to risk messing up your wimax... along with other things. You can restore user apps with Titanium Backup, but restoring system settings is probably a bad idea. Good luck!

plainjane said:
Make sure you have a fully charged battery before going back to stock. Download the unrevoked s-on tool from the unrevoked website, along with the most recent RUU in PC36IMG.zip form. Make sure that the RUU is named correctly - all caps, only one zip at the end. You will not need to add .zip to the end in the process of renaming.
Boot the phone into recovery & flash the s-on zip. Power the phone down and boot into the bootloader via volume down + power buttons. Make sure it says "Ship S-on" at the top. The phone will scan and find the RUU (as long as it's on the root of the card and named correctly), then ask you to update. Choose yes, then wait for it to flash. When it's done, choose yes when it asks you to reboot and you'll be good to go.
While Sprint will fix rooted phones with hardware problems, a broken port is not fixable. You also don't want them flagging your account. You will have to get a new phone, so you can toss any nandroid backups - do not attempt to restore them on your new phone. While it may be possible, you don't want to risk messing up your wimax... along with other things. You can restore user apps with Titanium Backup, but restoring system settings is probably a bad idea. Good luck!
Click to expand...
Click to collapse
I had the same problem you had. This method worked best for me.

where do i get the most recent RUU in PC36IMG.zip form? I have the stock sprint radio file but its exe.
"RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe"
Do i rename this to PC36IMG.zip or do i need to download something else.
edit:
Or i download this file and rename to PC36IMG.zip?
PC36IMG_SuperSonic_S_Sprint_WWE_3.26.651.6_Radio_2.15.00.07.28_NV_1.40_release_140444-signed.zip

Use the one I'm going to link you to. Rename it to PC36IMG.zip, leave the .zip intact - don't add it again. Then follow the directions I posted earlier.
http://goo-inside.me/evo/stock/ruu/...0.09.01_NV_1.77_003_release_154209-signed.zip
Sent from my PC36100 using Tapatalk

ok thanks!

Another thing for future refrence . I personally keep a folder on my SD card named "Emergency restore" Just in case . It contains the PC36IMG.zip and the Unrevoked S-on tool . Granted in the event the screen was broken or something to that extent and I still had some control over the phone I can still restore back to stock if I am away from my computer at home . Just an idea

ok i turned on the s-on via the "unrevoked-forever-son" tool. I put the image into the sdcard root and it checked the zip file but it didnt ask me to update
loading...PC36D1AG.zip.....no image
loading...PC36D1AG.nbh .....no image or wrong image
then it loads the PC36IMG.zip and checks it, but no update.
Whats wrong?
@SouthernEvo, thats a good idea, thanks

Try downloading again, then booting into the bootloader and letting it scan. You can always try letting the bootloader scan your current one again as well. It doesn't say "no image or wrong image", correct?
I almost recommended running an RUU from your computer, but you can't connect... duh. If it still won't work after redownloading, try a different one.
Sent from my Evo using Tapatalk

im thinking its not updating because im not flashing the latest radio maybe? my version says:
Radio-2.15.00.11.19 do i need to get one after this version in order for it to update?
im downloading another RUU file. Hopefully it may work. As it looks, my phone is already running the latest. Idk...i actually dont know wth im talking about anymore lol
EDIT: Figured out it was my SD card causing the problems. Switched to the stock 8gb card and now it works. Flashed back to Stock. New phone comes Friday

Please, help a n00b. I think I broke my Nexus S 4G

Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.

westinl said:
Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.
Click to expand...
Click to collapse
What version of CWM did you flash?

Pm me and we will use a chat service (aim, yahoo messenger) and I will walk u through it.

My suggestion of what I would do is this. Find a windows computer somehow. Go to the development section and look for the sticky about rooting the ns4g. Look for the link to flash the d720 back to stock. Download all those files to a flash drive. Take the drive to the windows computer and set things up then flash the phone back to out of the box stock.
Then you can go back to the Mac and do the root and 3024 cwm recovery and rename the sh file that puts stock recovery back in at boot time. After all this you can do what you want but I would suggest staying with the stock experience. This might be extreme to fix this but in my opinion, I wouldn't waste time trying to fix it, especially since you are new to this. It's like computers, yeah you could try to fix it but you could be opening a can of worms. It might take less wasted time putting it back to complete stock instead of f-ing around trying to figure out what happened and how to fix it. You could take hours trying to fix an install of windows that keeps falling on it's face, or you could format and install windows fresh and new in maybe thirty minutes. Which is easier?

CM7 will not work at the moment because it still uses 2.3.3, go find instructions for a 2.3.4 Nandroid. if you want though,i heard that supeaosp works on a ns4g.
Sent from my Nexus S using XDA App

westinl said:
Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.
Click to expand...
Click to collapse
Dude, you can't flash regular Nexus S ROMs on the Nexus S 4G.
Reflash the latest clockwork recovery.
Use fastboot flash recovery recovery.img
then...
Go to recovery, mount the USB storage, and put this zip on the usb storage:ROM
Go to recovery and flash that zip

here's the recovery that works. cwm and stock. How many times is this going to happen with new people and this phone in this forum section before a new subsection is made? We are going to be putting out a lot of these unnecessary fires with people making first time mistakes until something is done so as to not confuse them. Some don't realize that there are different versions of the same phone that aren't necessarily compatible with each other.
The way things are set up now, it isn't making this problem go away. I think that a different method should be tried if the current one isn't working too well. I'm flogging a dead horse now......

I'm looking to root my new NS4G as well -- and do it right the first time. On a Mac as well.
If the similarly-suited OP had issues I'm a bit more skeptical about my effort.
A separate forum might be necessary so people with the D720 hardware don't have near-brick experiences.
Sent from my PC36100 using XDA Premium App

soooo....did the op ever get it running again? i wonder if anyone ever took up on his paypal offer