Database Users

[SOLVED] 2.1 Rooting issue & GSM Hero (White screen, green htc logo, stuck)

[Solved]
Hi there.
I got hold of this second hand phone.
I dont think its been modified in any way yet.
Last night the phone asked me about doing a update. So i did.
After the green progress bar completed i got to a white screen containing a green htc logo. And its stuck there in a loop.
So... I cant turn my device on... whyyyy? :'(
All i can do is to get into the standard htc recovery.
And into the hboot. Some place there it says:
HERO CVT SHIP S-ON
HBOOT-1.76.0007 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.15.11
Aug 4 2009,19:43:30
I have done a wipe and a hard reset. Still it get this white screen on death. (WSOD) Im sodding of to bed...
You now know that it doesnt have a nandroid backup, and that I cant connect the phone via a usb connection to pc. And I dont have any custom recovery installed.
Ive tried to recover from a offical rom with a update.zip copied with a card reader onto the sd. Ive tried a few. The recovery see's the file. But when i try to install it it says "Verification failed Installation aborted"
Ive tried the recovery-RA-hero-v1.7.0.1.img, but without a usb I cant figure out how. Is there a way around for installing RA with just a sd card?
Please, does anyone have a good solution here.
Or some helpfull info to point me in the right way.
Sincererly,
Thor

See these threads similar,... Should be easy to sort.
http://forum.xda-developers.com/showthread.php?t=786938
and http://forum.xda-developers.com/showthread.php?t=787483

Good morning
Thanks, ive been looking at that.
My Win7 pc wouldnt show the ADB Interface in manage devices.
Only thing that pops up is a disk drive called HTC Android Phone USB Device, USB Mass Storage Device and a USB Composite Device.
Im gonna try this on my windows xp machine later today.
Hope it finds my phone, if not... what can i do?

So you need to update drivers as per the link in those threads,... Have you done that already pal?
Sent from my HTC Hero using XDA App

Hi again
Yes, I followed every step on that RUU driver guide on my win 7. But the drivers doesnt pop up as they should.
So I cant install the correct drivers since it doesnt show.

Halfway solution!
I got a breakthrough.
1. Remove the battery and replace it.
2. Hold volume down/up and tap power button. (htc enters hboot)
3. Taps back (enters fastboot)
4. Connects USB Cable (fastboot changes to fastboot usb)
5. Computer finds device My HTC.
Then i run this:
_HTC Hero_RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe
I got this from the htc pages. The software says i have ROM version 3.32.405.1
So i have a newer one installed then the one they have on web!?
I choose update on the software, now it tries to install 2.73.405.5
I got a half working usb connection now.
Fastboot restarted and changed to RUU USB.
Then i get a Error: 140 / 131 Bootloader version fail.
Can it be that the hard reset ive done messed up the bootloader version.
For me it looks like the phone is still in a new version ROM.
Anyone vise got anything to say about this?
Kind regards,
Thor

Aha,.... Ok, thats probs because the RUU you're using is older than the ROM already installed.
Try this one... RUU_Hero_HTC_WWE_3.32.405.1_R_Radio_63.18.55.06P_6 .35.15.11_release_signed.exe
That is the unbranded ROM,...

Wow
Suddenly everything klicked back into place!
Im past the white screen of death!
That RUU link was flawless for my device.
And the fastboot RUU USB installed everything.
Im back in business.
Much appericated m8

No problem. Now do us a favour and put [SOLVED] into your thread title. Thanks.

So...
Any suggestions on what i should do with it now?
Gotta root it i guess.
Then install recovery RA.
Any suggestions for a good rom to try?
Thanks again,
Thor

theres loads, but my suggestion would be villainrom 12 for a 2.1 sense rom, or froydvillain for a 2.2 rom

Ok
How do i know if i have a 2.1 sense rom or a 2.2 rom?
Or was that a dumb question from me, since you meant to install those?
Im kind of new, just left ye olde nokia behind

lol... Ok,... So you used the 3.32 RUU yeah? That is stock 2.1. If you used the other one, that is 1.5. Use BTDAGs guide in my sig to find out how to flash custom ROMs.
I also recommend Villain 12 for 2.1,... Or Froyd for 2.2. Depends if you like the SenseUI or not. Take a look at both in the Dev section.

Ok
Yes, I definitly want to have the Sense UI.
So then i wanna try out installing a villainrom 12 on a 2.1 sense rom.
Settings - Software Information now says:
Firmware version: 2.1-update1
Baseband version: 63.18.55.06PU_6.35.15.11
Kernel version: 2.6.29-063c4d24 [email protected] #1
Build number: 3.32.405.1 CL191507 release-keys
Software number: 3.32.405.1
This is what i have on it now.
I tried doing the phone software update again, when it asked me again.
Got the same error. So I did the usb install over again. All ok again.
Note: The update it tries out is 3.32.405.2 (5.87MB)
So... can i follow BTDAG's guide from here?
Or do i have to downgrade or update something first?
Guess i have to choose Superuser for Android 2.0~2.2 when i do the rooting with androot.
I got a problem in that guide when typing su in the terminal window.
I didnt get the "Super User Request Prompt" as it told about.
Ive now tried terminal from both usb and the terminal emulator.
WHen i try to do the SU or the flash_image recovery command i get permission denied!?
Without su rights i can do the flash_image recovery /sdcard/recovery.img command, since i need the su permissions.
Thanks again,
Thor

Hi again
I cant seem to get the SU rights i need.
Ive used universal nandroid for the rooting! (it tells its now ok)
But i cant flash in the custom recovery image.
Ive now tried a different approach:
1. Installing the ROM Manager and trying out ClockworkMod recovery(its installs ok)
2. Then I boot into recovery by holding the home(house) and power on, I get the white screen of htc death again and it goes into a black screen with a red triangle and a ! on it.
3. Then I release home and power on.
4. Presses down volume up and taps power on.
5. The hero boots into the standard recovery!?
(I think the way im starting up, are reflashing the recovery. am i right?)
Clockwork also have a "flash RA 1.7 recovery" option, ive tried that one too.
But with the same result...
Any one know about this?
Best regards,
Thor Elvin

Solution for life!
After a lot of surfing i found it!
This great tut worked for my device:
http://www.villainrom.co.uk/forum/s...o-Root-The-2.1-RUU-or-OTA-Update-For-The-Hero
I got a blue carebear in the background, and im making a big grin!
Now im rooted and backed up.
Great thanks to Pulser for a great tut.
Edit: VillainROM12 installed 1
PEACE Y'ALL!!!

QUOTE=thorelvin;8284640]After a lot of surfing i found it!
This great tut worked for my device:
Pulser did...
I got a blue carebear in the background, and im making a big grin!
Now im rooted and backed up.
Edit: VillainROM12 installed 1
PEACE Y'ALL!!![/QUOTE]
Dude, nice that you got sorted. I have kids so Carebears are good to have around. Respect to Carebears, and at the same time it would be cool and revisit the forum and thank Pulser, else thank him here as Pulser_g2 (i think). He sort of wrote, reworked the tut originally from the cdma version here. Sorted me too going 2.1 to 2.2. I had shedloads of fun with roms in between but its only thanks to him.
I guess this could be classed as one of those "Circle of life" philosophy budhist type **** things cuz the answer was really where you started, but for me... its all about takin care of the Carebears....
For the record his contract ends around May so get your Hero fix requests in early...!
Soz Pulser... And massive thanks for the opening to a new dimension for my hero...

[Q] What can I do? (Stuck in Fastboot)

I was using the new HTC Gratia Rom that was posted in the development forum, was restoring some apps with Titanium Backup manager when my phone rebooted, then it got stuck in a boot loop. I wiped it and rebooted again but no joy, stayed stuck in the loop.
Anyway, I recently installed a new recovery image, one of the ones for jailbreaking the PS3, so I have no USB access. Also it has a few extra options for wiping than the Amon RA recovery, and I guess I shouldn't have used the format boot option! Now on bootup all I get is "FASTBOOT USB", though I can still get into the psfMod recovery image.
That isn't much use to me though, as I stupidly deleted my nandroid backup and the update.zip file from my SD Card earlier while tidying it up a little bit. I don't have any other way of accessing the SD card and attempts to push another recovery image (with USB access) have failed.
I've also tried to install RUU's, both a T-Mobile UK one and a WWE one. That results in the following error: "ERROR [140] BOOTLOADER VERSION ERROR".
I guess because the current image version is: 3.31.110.1 and the RUU is only: 2.73.110.26. I don't think there's an RUU of this version available, from reading it sounds like it was an OTA, it's not something I installed myself, T-Mobile sent me this phone recently after my screen stopped working properly.
If you've managed to read this far without falling asleep, any suggestions would be welcome hopefully not just that I should buy a card reader cos I could do with getting my phone going again asap.

You got access to another phone which uses a micro SD? Could use that to put the zip onto the card.
Making a goldcard springs to mind as well
Sent from my HTC Hero using XDA App

Thanks for the tip, I had considered this already but I thought my brothers Legend (he doesn't live close) was my best bet. Turns out I had access to an N95 that did the trick

same problem
im a complete n00b
screen got replaced last month. new software was installed im guessing.
tried to use the tmobile ruu's to repair. there isnt one i can use though.
tried putting an engineering spl onto my sd card and using fastboot not really sure what happened there but it did not work.
does anyone have the appropriate update in zip format. not sure how i will get it to work but im trying all the things i read.
i do have backups but im not really sure what to do with them.
other than htc has anyone ever created an ruu?
mithdol

mithdol said:
im a complete n00b
screen got replaced last month. new software was installed im guessing.
tried to use the tmobile ruu's to repair. there isnt one i can use though.
tried putting an engineering spl onto my sd card and using fastboot not really sure what happened there but it did not work.
does anyone have the appropriate update in zip format. not sure how i will get it to work but im trying all the things i read.
i do have backups but im not really sure what to do with them.
other than htc has anyone ever created an ruu?
mithdol
Click to expand...
Click to collapse
What is the problem with urs exactly?

the problem is that im stuck in a cyanogen boot loop.
i have access to the generic fastboot only. therefore i have no ability to repair my phone from within the phone itself.
my phone is currently on hboot 1.76.0007.
i thought i had flashed clockworkmod. but for some reason or another beyond me it has disappeared.
the version of android i have running is 2.1, the tmobile version. the update number is 3.31.110.1. i understand that is the perfected spl version.
i have tried to fix using the ruu files. but i understand that the version on my phone as an ota update. therefore no ruu is applicable at this time.
i have tried many methods mentioned in various forums with no success.
thanks for responding to my post so quickly.
mithdol

Problem solved now
and the solution was so obvious............

...and what was that obvious solution? Because I'm facing a similar problem...
Thx in advance!

Rooting fails to update radoi

I have read through these forums for the past 12 to 20 hours, but I am still stuck. I followed regaw_leinad's tutorial on rooting my Evo. Everything was fine until it rebooted and tried to load the PC36IMG.zip. The bootloader was skipped and the radio update failed. Now I cannot do anything.
I get into the recovery mode, Windows shows the Android Composite ADB Interface in Device Manager, but adb devices shows the Evo as offline. I have reformatted the sdcard, copied the PC36IMG.zip file back on to the card with a card reader, re-ran the update, but it is always the same. The radio update always fails, the entire update fails and the phone stays in an offline mode. Is there anything I am missing here?
Just rebooting the phone only gets me to the logo and stays there forever. When I reboot holding the down vol I get:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.02.0000
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.09.01
Oct 14 2010, 19:14:47
I have also posted this in the developers area, but received no responses.

larrythethird said:
I have read through these forums for the past 12 to 20 hours, but I am still stuck. I followed regaw_leinad's tutorial on rooting my Evo. Everything was fine until it rebooted and tried to load the PC36IMG.zip. The bootloader was skipped and the radio update failed. Now I cannot do anything.
I get into the recovery mode, Windows shows the Android Composite ADB Interface in Device Manager, but adb devices shows the Evo as offline. I have reformatted the sdcard, copied the PC36IMG.zip file back on to the card with a card reader, re-ran the update, but it is always the same. The radio update always fails, the entire update fails and the phone stays in an offline mode. Is there anything I am missing here?
Just rebooting the phone only gets me to the logo and stays there forever. When I reboot holding the down vol I get:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.02.0000
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.09.01
Oct 14 2010, 19:14:47
I have also posted this in the developers area, but received no responses.
Click to expand...
Click to collapse
Try using the PC36IMG from the thread below, you should be able to use adb through the hBoot or you can just pull the sd card and use an adapter.
http://forum.xda-developers.com/showthread.php?t=838448

I had not read this post yet, but I got a different version of PC36IMG.zip and tried again. It failed the radio update and got a new failure on the IC update. BUT, I can now get into recovery mode and the phone is shown as recovery to adb. I can push to the phone now. I cannot recover yet. Also, I cannot get into adb shell, either. I am now getting a a new error when I run Unrevoked3. It says Device "exec'/system/bin/sh' failed:No such file or directory". So I'm closer, but not there yet. I guess I really hosed up the phone.
I will try the files from this post as soon as they finish downloading.

xHausx said:
Try using the PC36IMG from the thread below, you should be able to use adb through the hBoot or you can just pull the sd card and use an adapter.
http://forum.xda-developers.com/showthread.php?t=838448
Click to expand...
Click to collapse
I don't know if this will help you, it was added after the new Hboot however. However, the first link the OP posted is for a sadly out of date thread now. You should look at http://forum.xda-developers.com/showthread.php?t=829045 if it still doesn't work. If anything, get a un-root PC36img, and start over.

Had the same issue when I rooted my wifes evo. Then I ran unrevoked forever which gave me "s-off" then I was able to flash radios

Still no joy
So far this morning, I have tried:
Running the PC36IMG.zip that came from one of the older threads. Same thing.
Pushing the moveme folder to the sdcard on the phone. It gives no errors, but there is nothing on the card. Just empty. Pulled the card out and copied the folder to the sdcard using a card reader and put it back in the phone. Nothing changed. Copied the eng-PC36IMG.zip file to the card and renamed it PC36IMG.zip. Ran the update but get the same results.
I am downloading what the thread says is an un-root PC36IMG.zip file. I will see if that works.
I see that the big issue for my phone appears to be that I cannot get to S-OFF, which keeps me from getting into the adb shell. I will try all of the suggestions and see what happens.

Thanks all
I used different PC36IMG.zip and got my phone working again. I have still not seen my phone get to S-OFF yet. But for now, I have a phone again.
I will try to root again using the post from yesterday you directed me to.

larrythethird said:
I used different PC36IMG.zip and got my phone working again. I have still not seen my phone get to S-OFF yet. But for now, I have a phone again.
I will try to root again using the post from yesterday you directed me to.
Click to expand...
Click to collapse
did you try the unrevoked forever?

any legit fixes?

You need to use the Hboot 2.02 root like a boss method, unrevoked doesn't work with hboot 2.02 here is the link: http://forum.xda-developers.com/showthread.php?t=829045

[Q] Bricked Wildfire after attempted Froyo Update, Please help!

First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !

Undeadllama said:
First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !
Click to expand...
Click to collapse
You'll need a goldcard and an RUU. Look up how to make a goldcard and let me know when you have one

Wow, thanks for the quick reply
I did try creating a goldcard yesterday (using android.modaco.com/content/software/308798/pc-application-goldcardtool/). So assume I DO have one for the time being...
however if it doesn't work and I need to create a new goldcard:
Since I can't get into adb or boot up android and therefore can't access my sd card through my phone I presume il have to go out and buy a cheap card reader tomorrow.
Also, I have to run this command again:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
But if I can't get into adb how would I go about doing this, can I get the CID of the sd card from a card reader?
As for the RUU, there's many to choose from on shipped-roms.com, does this sound about right?
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35.15.19_release_130442_signed.exe
Thank you so much for your help.

This this a decent guide from Paul over at MoDaCo.

Ok disregard my last post about a card reader... I managed to borrow a friends android phone since it appears goldcard's are specific to the sd card, not the phone. So after following the instructions I now definitely have a goldcard.
Also have the RUU mentioned in the previous post.
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35. 15.19_release_130442_signed.exe
Is this right, and what do I do with these now to get them on my phone? Ive tried running the RUU whilst in Hboot and in recovery but it wont recognise my phone, presumably because adb isn't working.
Thanks again for the help.

There is another way to do it when it can only get into hboot. I'll look today for the method and let you know.
Sent from my HTC Wildfire using XDA App

Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions

Undeadllama said:
Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions
Click to expand...
Click to collapse
Yeah that's the method I was going to suggest, glad you sorted it out.
It's the fact that they lock out fastboot and stuff. If we had S-OFF from the factory, fixing these things would be so much easier

Hi,
how were you able to do this?
"Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system. "
Thanks

Is my Hero bricked? What should I do?

Hello everyone!
First off I'd like to start by telling you I'm new here and I don't know much about rooting so I'm reffering to you for help... Here is what happened... I have a G2 Hero, running android 2.1. So one day I decided to root it and install a custom rom. I downloaded Universal Androot-1.6.2-beta5 and ran it on my mobile.
Afterwards I formatted my sd card then restarted the device and downloaded rom manager from the market and flashed Clockwork. After this I put CyanogenMod-6.1.0-RC1 in the root dir of my sd card, tried to install it from [HOME] + [PWR] buttons menu and an error saying [status 7] showed up... Now im stuck in an endless bootloop... I cannot sync the device with my computer, cannot hard reset.. I can access Hboot menu but there isnt anything I can do...
What should I do to restore it to stock and then try the whole thing again but with a new rom? Thanks in advance!

Anyone?

Have you tried running an official HTC RUU? They can be found in a thread on the development page
Sent from my HTC Hero using XDA App

you have to search for "RUU for htc hero gsm". There's an official website for that. Download RUU (about 80-90mbytes as i remember) and start it. As i remember you should power your phone in HBOOT mode (VOL DOWN + POWER), connct to PC and run RUU and follow the wizard.
It will flash stock 1.5 android.
After reeboot it should inform you that there's an update, but if you want to flash different recovery, you shouldn't update your phone.
Then you should follow "How To - Root Your HTC Hero in One Click" (can't post links yet).

Ok first of all thank you guys for the help! So I downloaded RUU_Hero_HTC_WWE_2.73.405.66_WWE_test_signed_NoDri ver.exe from the main thread. At first I had some connection problems but then I switched the front panel USB to one of the rear which are 2.0 and continued. Now I'm stuck at a later step. Tried to update it but an error message saying "ERROR[131]: CUSTOMER ID ERROR Please get the correct ROM UPDATE UTILITY and try again" displays. Which RUU would you recommend?

I used official RUU from htc.com site. It just worked for me.
This one is in Polish, but i believe, you will find one in your language or in English
http://www.htc.com/pl/supportdownload.aspx?p_id=283&cat=2&dl_id=671
//edit
You must provide a valid serial number from sticker behind the battery and select a corresponding file. It will be only one i think
//edit2
There's something more about this error 131:
http://androidforums.com/707610-post16.html
Apparently you just used wrong RUU... Try one from prev link.

Ok, soI downloaded RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver from the official HTC website and go past last error but afterwards I encounter another one. This time it is "ERROR[140] BOOTLOADER VERSION ERROR, Please get the correct ROM Update Utility and try again"
Any suggestions this time?

hskiller said:
Ok, soI downloaded RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver from the official HTC website and go past last error but afterwards I encounter another one. This time it is "ERROR[140] BOOTLOADER VERSION ERROR, Please get the correct ROM Update Utility and try again"
Any suggestions this time?
Click to expand...
Click to collapse
You could try the carrier one if you got it from Orange flash the ruu which is for Orange uk

Nope, my phone is from Europe but I dont think I got my cd... I'll sure search for it. Any other suggestions?

Maybe you can find a workaround there:
http://forum.xda-developers.com/showthread.php?t=684504

I am currently trying with this one:RUU_Hero_HTC_WWE_2.73.405.38_WWE_release_signed_NoDriver. But it seems to be stuck on "Sending.....Updating the ROM image on your Android phone" The progress bar on the phone's display is almost complete but wont move anymore. I have waited for 20 minutes now...
EDIT: I finally fixed it! I didn't realise I had to have the same RUU version like my software version. Thought I had to downgrade. Nevermind it's all OK now and it's time to try the whole rooting and custom ROM process again
I want to thank all of you guys that helped me!

Good for you man
Just out of pure couriosity, what rom will U use afrer your phone get rooted?

You have to use your carrier related stock rom/exe. What is your carrier?
Perdita2000
Sent from my Hero using XDA App

I havent decided yet. It will definitely be some Android 2.2 ROM Maybe Elelinux Speedmachine.