Database Users

loaded wrong rom, stuck on boot screen

Apologies for this stupid question resulting from a stupid mistake. Hoping somebody will be able to walk me through getting out of this.
I successfully rooted my sprint hero, then loaded modaco 3.0 (yes now I know that was bad). On reboot, the phone hangs on the black htc screen, and will respond to nothing.
The only thing I've been able to do is remove the battery, then turn it on in recovery mode. There, I did a wipe data/restore factory setting. Then I rebooted - and got the same boot screen, same problem.
Second try: wiped, toggled to usb, and replaced the 3.0 update.zip with the 1.1 for CDMA, tried to flash it, got this:
can't open /sdcard/update.zip (bad)
When I try to restore, I get these:
(bart) error: run bart via adb
(nandroid) can't open file
Please help! I am out of ideas. Thanks very much in advance.

you'll probably have to take it back to the very beginning......
Get the Sprint RUU stock rom (a couple of posts below this one) and run that
then re-root your hero
Flash one of the roms ON THIS BOARD ONLY!!! Any other Hero rom is meant for the GSM version so it will give you the same headache again.

thanks
Thanks for the quick response! I'll try that.

Hmm, not looking good here. When I tried to install the stock hero RUU I got this error:
no signature
verification failed
which I presume is related to the htc sync requirement for that rom in the unrooting procedure that I did earlier.
Any idea for working around that?

So you used RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe? If not, here is a link to it: link.

david.danaan said:
Second try: wiped, toggled to usb, and replaced the 3.0 update.zip with the 1.1 for CDMA, tried to flash it, got this:
can't open /sdcard/update.zip (bad)
Click to expand...
Click to collapse
Don't use 1.1, grab a later one.
Which recovery? 1.5.x won't let you go back to the main menu without disabling USB-MS again... I don't remember what 1.2.3 did. If worse comes to worst, reboot the phone after copying the file.

gu1dry said:
So you used RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe? If not, here is a link to it: link.
Click to expand...
Click to collapse
Yes, that's the one.
Using recovery 1.5.1. I can try a later rom, see if that works. I think I downloaded 1.3.

So first off yes, you aren't booting past the HTC screen because you flashed the wrong rom. However you aren't bricked. It's almost impossible to do once you're rooted and have RA's recovery installed unless you flash radios and stuff which you shouldn't.
Explanations for your other problems:
1. RUU doesn't work on the phones that are coming from the factory with 1.56. http://geekfor.me/news/sprint-ruu-fails/
There is a possible work-around but it's pretty detailed and I haven't gotten it to work. But you don't need to RUU if you can get in to RA.
2) (nandroid) can't open file is likely caused by RA 1.5.1. It had a bug that corrupted the backups. 1.5.2 is out. But for now don't worry about that cause your backup already sounds corrupted, nothing you can do.
3) can't open /sdcard/update.zip (bad). To me that sounds like your update was just corrupted.
How to fix it:
1. Boot in to recovery. With phone powered off hold your home button and then power.
2. Download fresh rom from http://geekfor.me/new-release/fresh-rom-1-0/ (what can I say... I'm partial. )
3. Within RA enable USB toggle and copy fresh rom to the root of your sdcard. Don't worry about renaming it to update.zip
4. Disable usb toggle. Go to flash zip from SD and choose fresh. That should be it. If you get the error saying the zip is bad then compare your downloaded copy with the md5 hash check on the download page (google it if you aren't sure how). If it matches then it's possible you have a bad sdcard. If it doesn't match then your downloads are crappy.

working!
Got it working by flashing the modaco v1.3a - must have been a bad update.zip before like you said. Thank you so much for the help and clear explanations, I was really worried I had bricked it.

David, now that it is working, I would recommend updating your recovery to 1.5.2.

I just want to thank everyone that posted to this reply I honestly thought that I bricked my phone and thank to you guys I was able to revive it. Thank you again.

Have to admit I need some help with rooting

Ok so this is whats been happening. I have an eris im trying to load a custom rom on after I did the 2.1OTA
When I came out to XDA to use the root I was at first confused since it was all going from 1.5 to 2.1. After reading further I read reports that 2.1OTA is rootable just like 1.5 as long as I follow the proper steps.
I: Gaining root
An unlocked hboot will allows us to flash in a modified IMG ROM signed with test keys as supposed to requiring an official ROM from HTC. This will open us to be able to flash a modified recovery.
1. Download this file: PB00IMG.zip (md5: 63eacc5ede3b179f95dc22d8ef585f94)
2. Place PB00IMG.zip onto the root directory of your sdcard.
3. Power down your phone.
4. Hold Volume Down while you Power On. This should bring you to a screen saying "HBOOT" and some other stuff. Wait for it to load the image, and it will say Push Activate. Push the trackball button to continue. The process will take around 5-10 minutes. The first time your phone boots up it will take a lot longer than normal.
Click to expand...
Click to collapse
I think this is where things go wrong. When this was attempted it I saw that my bootloader was now reading 1.49 (phone never been rooted before) instead of the one people report you need to root which is 1.47
It loaded up under 2.1 still and I believe its still the 2.1OTA so I head on to next step for recovery img. something seems to have gone wrong with it too (possibly me messing up the sdk) as now when I try to load any recovery images via fastboot "FAILED <remote: not allow>
Now the more trouble part is now that its ready I follow the instructions on how to actually load the rom through the recovery and SD card method. I believe my recovery is not what its supposed to be either as when it loads I see an android next to a caution symbol with a yellow ! and when the recovery screen is brought up I only have 4 options. Ill type abit what I see
"
Android system recovery <2e>
Use volume key to highlight:
click power key to select.
Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cache partition
E:Can't open /cache/recovery/command"
Now I have tried the instruction of wiping first with a data and cache wipe but it does not give me any options after that on to flash from sdcard
IV: Flashing a custom ROM
1. Download the Rooted 2.1 v0.8T2 zip file.
2. Copy the WHOLE zip file to the root directory of your SD card. (You can enable USB-MS enable from your shiny new recovery to mount your phone as a USB Mass Storage device.)
3. Choose Wipe. Choose data/factory Reset (In the stock ROM, the dalvik is stored in the data and you don't have an EXT partition... yet.)
4. Choose Flash zip from sdcard. Find the eris_0_3.zip file.
5. Wait until it shows as complete and choose reboot system now.
Click to expand...
Click to collapse
I have tried putting different ROM's on my sdcard. I attempted to downgrade using the tutorial provided and using the official RUU from PCD's website. (which both didnt work as downgrade would stop at recovery or RUU states wrong bootloader version towards the middle of the load) and I tried even renaming the ROM's to update.zip the message I get everytime is the same with 2 results one for the rom without the update.zip and one with it.
(with update.zip)
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
(without update.zip)
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Also for those wondering I followed the method of installing drivers and using debugging mode ....all drivers seem to be working fine.
Also just for further info when I run the RUU to try and downgrade my bootloader goes back to showing 1.47 but the radio is still 2.40 if this gives and help
If some could first tell me where I went wrong and then where to go from here I will be most appreciative and im even willing on putting out a reward if someone can do this for me quickly (I am poor some it wont be a big reward but it will be something)
Thanks for any help.

This means you are on the leaked version now and there is nothing that can be done as of right now.

K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?

ca2l3vin said:
K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?
Click to expand...
Click to collapse
So you saying you had 1.5, then got the OTA update from Verizon?
If that is true, are you sure you downloaded the correct root image? Cuz if I remember correctly, the non root one is named the samething. But I could be wrong as I never tried leak.

sounds like you got a bad pb001.img file.

ca2l3vin, it sounds like you may have downloaded and flashed the wrong PB00IMG.zip file. Where did you get it from?

nevermind addressed my issue

As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5

ca2l3vin said:
As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5
Click to expand...
Click to collapse
I hate linking back to another forum, but I used this guide and it worked flawlessly for me.
http://androidforums.com/all-things-root-eris/53963-guide-stock-1-5-latest-root-2-1-a.html
Did not check your link to see if its teh same but I can vouch that this one is 100% working.

af man...seriously!

out of curiously i reboot my phone via power + volume up and saw my hboot version 1.49.... it's werid because I had my phone rooted long ago when I was running on 1.50. Anyway, I'm still able to boot into Amon_RA's recovery and using Tainted Vanilla ROM as of now. I'm thinking it might be because of *228 actually reprogrammed SPL somehow, because i saw glimpse of message during programming phase, it said "SPL unlocked" and "OTA update completed"

HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA

ca2l3vin said:
HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA
Click to expand...
Click to collapse
Glad I could help. Aloysius is also a very good one to check out. Heard there are issues with v12 but v11 maps is solid!

Froyo 2.2 Verification failed

Im having the worst time in the world trying to get this froyo for my evo. I have it in the root of the sd card, "O:" and removed known file extensions just to make sure its update.zip and not update.zip.zip.
everything is what it should be according to every post ive looked at. Yet no matter what I do, i still get signature verification failed, installation aborted.
Any ideas?!

I could the same thing last night. But what I had to do was to update to 1.47 then go in and update it another time name the file update and that is it. And it should work.
Sent from my PC36100 using XDA App

This is how it's done.
Follow the step by step directions I copied from androidpolice below. When you get to step 8, you will most likely see the red triangle with exclamation point. Don't worry. Just hold the up volume button and press the power key. This will activate the menu where you will see "apply update.zip". Proceed with step 8. It takes care of the rest.
We’ve provided some simple instructions for installing the update:
1. Download the update file and rename it to update.zip.
Note #1: DO NOT UNZIP THIS FILE
Note #2: Make sure you didn’t rename this to update.zip.zip by accident, if your Windows is configured to not show file extensions.
2. Place in the root of your SD card (connect via USB and mount as a drive, transfer via bluetooth, download directly on the phone – pick your poison).
3. Reboot into recovery mode (hold the Volume Up button while your phone is booting).
4. You will be presented with the boot loader. The Volume Up/Down buttons navigate the menu, and the Power button selects.
Note: you may see the red exclamation (!) point at this stage. Try mashing the up/down/power buttons and wait for 10-15 seconds. The recovery should eventually come up.
5. Select Bootloader.
6. Scroll down to Recovery and select it.
7. The phone will reboot again, this time into recovery.
8. Select “apply update.zip” or “install from .zip” (depending on your recovery image).
9. The installation process will take 15-20 minutes and a few reboots.
10. Enjoy!

i can get to that point just fine, its the install that fails due to signature verification failure, i have followed all the steps to prevent any mishaps, but still cannot get past it.

I think I had the same issue with the file after I renamed it update.zip (it was hidden and already there). I renamed it but did not help.
I would recommend deleting it from the card and downloading a fresh copy of the update. Copy it to the SD card and try again.
This is the source I used and it worked.
herehttp://www.megaupload.com/?d=LCONCXF1

xcodesterox said:
i can get to that point just fine, its the install that fails due to signature verification failure, i have followed all the steps to prevent any mishaps, but still cannot get past it.
Click to expand...
Click to collapse
You are probably going to need to download a different file, as a lot of the mirrors here are corrupted. If your file size is 70 something, that is corrupt. The correct file size is 80 something (sorry, I'm on my phone).
Look for a different mirror to download from.

Did everything and nothing, not even the (!) thing, everytime I scroll down to recovery it just takes me back to the main menu (bootloader) and nothing seems to work, am I doing something wrong?

yeah ive only downloaded the 84mb ones, i even had the original from HTC with no results. my evo refuses to evolve lol

-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.

fsuwade said:
I could the same thing last night. But what I had to do was to update to 1.47 then go in and update it another time name the file update and that is it. And it should work.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Im Hoping thats what the case is, I'm installing 1.47 now, if this doesnt work then im at a loss

well, no luck. i guess i have to wait till the 3rd

I had to remove all the excess files from my sd card root for it to finally work correctly. I think the only thing i had left on my sd card root were folders and the froyo renamed to update.zip

If you are rooted why not boot into recovery and install update from zip. Note that this option will un-root your phone in the process. There are also post on the forum with the stock Rom for non rooted phones, if you are not rooted. You can try using that file rather than the one you got. This may get u on 2.2 b4 u know it.
http://WWW.rootznculture.com

Kornsaq said:
I had to remove all the excess files from my sd card root for it to finally work correctly. I think the only thing i had left on my sd card root were folders and the froyo renamed to update.zip
Click to expand...
Click to collapse
I have many folders and I cleaned up the excess files, still though, no result.
thanks for the tip though, i got really excited to try that,.

jahnile said:
If you are rooted why not boot into recovery and install update from zip. Note that this option will un-root your phone in the process. There are also post on the forum with the stock Rom for non rooted phones, if you are not rooted. You can try using that file rather than the one you got. This may get u on 2.2 b4 u know it.
http://WWW.rootznculture.com
Click to expand...
Click to collapse
Im rooted, i tried being rooted, and unrooted. Ive been going at it since it released when i was at the movies.
thanks for the tip

Same problem
Hey xcodesterox.
I had the exact same issue and even download the linked file from ckombo.
I was finally able to get it to work.
What was happening for me was, I would download the file and my Mac is set to unzip a downloaded file from Safari, I would then just zip it myself after this. This was not working so I switched to Firefox, where I do not have it set to autoextract, and therefore I did not have to re-zip. THAT time it worked.
I hope you had the same issue.

Ok so you said right now you are in rooted. You should try removing all zip files that are current on the root of your SD card. U can back it up to your pc. Then use the file/ method found in this post. http://forum.xda-developers.com/showthread.php?t=740319
http://WWW.rootznculture.com

1:42am day two and im finally enjoying my fozen yogurt.
if anyone cares, i had to use the rooted version of this update, so its still a mystery as to why it wouldnt install. thanks for everything

I had some problems workign so i did this
1.did factory reset(backup date)
2.did the ruu 1.47 update
3.copy zip file to sd (drag and drop in windows, just dont drop into esisting file and dont unzip)
4.name the file update windows will add the .zip checkby right clicking on the file going to preferances then details tab (in win7 anyway)
5.power down phone
6.reboor by holding vol down and power wait for it to read you card
7.might get a cant open cache error, didnt prevent my update
8. using vol keys nav down to recovery, hit power button to select
9.vol down to highlight the update.zip file and powr to select
i was running 1.17 firmware so i had to update from that to 1.32 then 32-47 so check your version and update accourding, is it worth it? my bat life does seem a lil better flash is smother than the flash update i ran in 2.1, and browsign does seem smother, also landscape mode works in both left and right!

Where did you found this rooted version? I have the same problem...

OFFICIAL: update.zip is finally here! :D

Ladies and gentlemen, if you are getting impatient on waiting to get your scoop of FroYo...this is NOT the RUU, so it will not wipe any memory off your phone...PLEASE READ EVERYTHING CAREFULLY BEFORE YOU BEGIN!
Quick Note: While one of the great things about the update.zip is that you are not required to clear your memory...i have found from personal experience that your phone will run much smoother by doing a factory reset(much like it would by wiping your hard drive on the computer). This has nothing to do with the update.zip....people who recieved the OTA from Verizon have also reported lots of bugs with updating.
First off, ensure that you have the Stock 2.1 ROM with first OTA, it WILL NOT work otherwise.
software/Build version will read as the following: 1.22.605.2...if it is 1.22.605.0, the update wont work...please go here to update it http://forum.xda-developers.com/showthread.php?p=7933281#post7933281
Directions:
-Drop the update.zip provided at the bottom of the page on to the Root of your SD card.(Just to clarify the "root" of your sd card means you just drag and drop the file to your SD card. DO NOT put it in any folders!)
- Turn your phone off.
- Press and hold the Volume Down and Power at the same time to boot into HBOOT.
-
When the white HBOOT screen appears, use the volume button to move down to “RECOVERY.”
- Press the Power button to select “RECOVERY.”
- When the triangle and exclamation appears, hold the Volume Up and Power button at the same time.
- Using the volume button, scroll down to “apply sdcard:update.zip” and select it.
-Your phone should update now, but it will take some time
enjoy your FroYo everyone ...and a very special thanks to teslatech at Android Central for pulling the .zip from his phone
Update.zip here....http://www.4shared.com/file/aI_WeWN7/update.html
Or here...http://www.megaupload.com/?d=6MC4BIEG
All issues should be resolved at this point...PLEASE REPORT IF YOU HAVE ANY OTHER ISSUES!
EDIT:>>>>>>>>Youur Baseband should read as followed to perform this update....1.00.03.04.06...if it doesnt please follow this link to downgrade your phone to stock Android 2.1 http://androidforums.com/incredible-all-things-root/99828-video-howto-unroot-incredible-downgrading.html <<<<<<<<<<<<<<
Follow this link for rooting directions AFTER you install the update.zip ...http://www.droid-life.com/2010/09/07/unrevoked-3-2-drops-1-click-root-for-2-2-on-droid-incredible/

Better link:
http://android.clients.google.com/p...on_WWE_3.21.605.1_1.22.605.2_release_sign.zip

Berzerker7 said:
Better link:
http://android.clients.google.com/p...on_WWE_3.21.605.1_1.22.605.2_release_sign.zip
Click to expand...
Click to collapse
thankyou, i wasnt sure how to make a link for it...but either way...i want everyone to thank him, lol...i was just complaining to someone else right before him about not putting the update up. So he is our savior

The assumption is that you download, rename as update.zip, place in your sdcard root and then go to recovery?

krelvinaz said:
The assumption is that you download, rename as update.zip, place in your sdcard root and then go to recovery?
Click to expand...
Click to collapse
Im not completely sure yet...we are trying to figure that out over at android central...dont worry, i will have everything sorted out shortly

Yes, that's all that's required, rename to update.zip, apply this.
Make sure you're software version is 1.22.605.2 before you apply this update. If you installed the OTA from a couple months ago, you should be fine.

If anyone still doubted the RUU was not the same as the OTA, it is. I've compared all the files which aren't patch files and they are identical matches.

rmk40 said:
If anyone still doubted the RUU was not the same as the OTA, it is. I've compared all the files which aren't patch files and they are identical matches.
Click to expand...
Click to collapse
I never said it wasnt, did i?...some of us dont want to use the RUU, cuz it wipes the memory off the phone...the update.zip doesnt..and we have been scrambling for days to get it

Copied to update.zip on the sdcard, went to recovery.... just sits there with black device and red triangle !
Been about 5 mins, nothing further, no indication it saw anything.

schwartzman93 said:
I never said it wasnt, did i?...some of us dont want to use the RUU, cuz it wipes the memory off the phone...the update.zip doesnt..and we have been scrambling for days to get it
Click to expand...
Click to collapse
If it sounded like I was downing getting the update.zip, sorry about that. That was not my intention. Thanks for getting it to us.
I was just pointing out for the folks who still thought it was different that I've done an MD5 comparison and they're identical.

krelvinaz said:
Copied to update.zip on the sdcard, went to recovery.... just sits there with black device and red triangle !
Been about 5 mins, nothing further, no indication it saw anything.
Click to expand...
Click to collapse
Press volume up + power button, which brings up the recovery menu. Then apply update.zip.

krelvinaz said:
Copied to update.zip on the sdcard, went to recovery.... just sits there with black device and red triangle !
Been about 5 mins, nothing further, no indication it saw anything.
Click to expand...
Click to collapse
yea, same here...we are trying to figure it out over at android central...sorry i posted this thread up...i just got so gitty...we will have it figured out asap though

rmk40 said:
Press volume up + power button, which brings up the recovery menu. Then apply update.zip.
Click to expand...
Click to collapse
thanks. but the update failed.
E: Can't open /cache/recovery/command
-- Install from sdcard...
verifying update package...
installing update...
Verifying current system...
asser failed: very long string
E: Error in /sdcard/update.zip
(Status 7)
Installation Aborted

krelvinaz said:
thanks. but the update failed.
E: Can't open /cache/recovery/command
-- Install from sdcard...
verifying update package...
installing update...
Verifying current system...
asser failed: very long string
E: Error in /sdcard/update.zip
(Status 7)
Installation Aborted
Click to expand...
Click to collapse
we are trying our best...im sorry for prematurely posting this up...as you can see i changed the title in hopes that someone can help

I'm total noobe and probably should hold my tongue but what of you rename to the proper pb...img.z
ip? I forget the numbers for the incredible.
Sent from my ADR6300 using XDA App

krelvinaz said:
thanks. but the update failed.
E: Can't open /cache/recovery/command
-- Install from sdcard...
verifying update package...
installing update...
Verifying current system...
asser failed: very long string
E: Error in /sdcard/update.zip
(Status 7)
Installation Aborted
Click to expand...
Click to collapse
The assert error indicates there is something on the phone configuration it doesn't like. It is not because the download file failed. that succeeded and matched the correct checksum's. Confirmed this with Unrevoked on IRC.
Just in case someone else gets this.
looks like I will use the RUU update instead. Will do it from work since I only have Win7 here.

marcmarshall said:
I'm total noobe and probably should hold my tongue but what of you rename to the proper pb...img.z
ip? I forget the numbers for the incredible.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
i have successfully got it working under update.zip...i will post up a new thread shortly
....but can someone tell me how to delete this one?

Intriguing
Alright so after playing round a bit I've had some interesting luck.
After downloading the file I renamed it to update.zip, placed it within the root of my sd card and proceeded to turn the phone off.
After entering Hboot ( Volume Down + Power ) I launched recovery.
At the recovery screen the phone with a red triangle, I did Volume up + Power to bring up the recovery options and chose Apply update : sd card
It took a few minutes to load, asked me to select reboot from menu. Loaded the 2.2 splash and I now have froyo.
My question is, Couldn't this be done from clockwork as well as there is an SD update from there as well?

Hack.Me said:
Alright so after playing round a bit I've had some interesting luck.
After downloading the file I renamed it to update.zip, placed it within the root of my sd card and proceeded to turn the phone off.
After entering Hboot ( Volume Down + Power ) I launched recovery.
At the recovery screen the phone with a red triangle, I did Volume up + Power to bring up the recovery options and chose Apply update : sd card
It took a few minutes to load, asked me to select reboot from menu. Loaded the 2.2 splash and I now have froyo.
My question is, Couldn't this be done from clockwork as well as there is an SD update from there as well?
Click to expand...
Click to collapse
Unfortunately...im the wrong person to ask, lol...im not good when it comes to rooting

Reason I ask is because it could potentially save a lot of time and effort on the peoples part of having to return to stock etc.... assuming they are running the correct version and baseband pre update. But then again, the update could perhaps check to ensure the stock recovery is in place before hand. Had I not just have updated I would try it myself.
Perhaps we could find a guinea pig to try updating via clockwork...

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