Develop Bugs

[Q] Desire Brick with just fastboot

Hello,
I am reading for hours and lost the overview...
My Desire had CM7 installed and had many reboots lately (maby caused by juice defender or the dalvic cache on the ext) but now it just wont boot at all. Not even into recovery.
Bootloader and Fastboot work but I cant flash anything or boot a recovery
S-ON
HBOOt-0.93.0001
RADIO-5.11.05.27
Code:
fastboot flash recovery recovery-clockwork-2.5.1.3-z71.img
sending 'recovery' (3742 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
Code:
fastboot boot recovery-clockwork-2.5.1.3-z71.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
I am using a Mac but could also use a Win7 or Ubuntu maschine if this is necessary...
Please help

Ruu?
Sent from CM7

Is the custom recovery flash failing because the phone is s-on?
If so would it help to run alpharev on it?
Not sure, just a thought!

From what I understood you need to be able to boot to use alpharev or RUU?
I started the RUU .exe and stole the ROM.zip from TEMP but either the CID is not correct (I have VODAP102) or the version is older since CM7 is 2.3.3 I guess.

00droid said:
Is the custom recovery flash failing because the phone is s-on?
Click to expand...
Click to collapse
I guess so. Isn't S-OFF the thing you need to flash custom roms? I had it rooted and installed the recovery with clockwork or so from within OS without changing S-ON.
I got a UK VODA RUU to start at least (SD inside, sim not) but fails with ERROR[170] USB-Connoction Error
Afterwards it booted magically, I could backup data, flash LeeDroid to (what I thought) would solve the instability problem but it crashed again (connected cable is not good). And now its the same all over again but this time I cannot reproduce the luck from the first time.
Should I keep trying and then S-OFF, dwongrade bootloader and upgrade radio? What else could I do.
But I dont think the attepted flashing will work again...

magreet said:
From what I understood you need to be able to boot to use alpharev or RUU?
I started the RUU .exe and stole the ROM.zip from TEMP but either the CID is not correct (I have VODAP102) or the version is older since CM7 is 2.3.3 I guess.
Click to expand...
Click to collapse
Hmm, I think you're right actually, it's been a while since s-off for me!

S-OFF is indeed needed to flash the custom recovery via fastboot.
RUU - so probably you need a branded RUU for your phone (VODA-Germany VODAP102).
Or do the above mentioned method - take the ROM.zip and put it on your SD Card, but RENAME it to PB99IMG.zip.
Since you are branded, you need to create a goldcard, to avoid CID error:
Here's how

The phone needs to boot to create a GoldCard Luckily this happens from time to time.
But since 2.3.3 is newer than the newest 2.2 RUU the GoldCard CID fix wont work in my oppinion...

Even I am struck with the same issue. Only fastboot access with an Orange desire. I do not have a gold card to try out anything.
My phone's CID: ORANG001
Bootloader throws up the following error:
Loading...[PB99DIAG.zip]
No image!
Loading...[PB99DIAG.nbh]
No image or wrong image!
Loading...[PB99IMG.zip]
No image!
Loading...[PB99IMG.nbh]
No image or wrong image!
Any suggestions?

Could you flash a RUU from within Windows? I tried many, at least one of them tried to start and failed but the phone started at least. If a boot loop occurs remove the battery and retry as long as it takes. Worked for me.
Maybe without sim.

Some people reported being able to boot WITHOUT sd in the phone. Try it.

[Q] Bricked or is there still hope?

I'm messing around since 3 days with a non working Desire.
I was trying to root that Vodafone UK Branded Phone with a goldcard, but it somehow did't really work stable.
So I managed it to install a RUU in order to revert it and begin the Process from the beginning on:
1.This was the RUU, and everything went fine: RUU_Bravo_Froyo_Vodafone_UK_2.33.161.2_Radio_32.49.00.32U_5.11.05.27_release_157522_signed
2.Then I tried to downgrade my HBOOT from 0.93.0001 to 0.80 using the method in this thread (with goldcard!)
3. During the installation of the PB99IMG.zip something went wrong and (maybe a mismatch with goldcard or the mtd0.img, i still don't know / understand) HBOOT could not be updated and RADIO-V2 also
4. now I cant boot the Phone at all or issue adb commands (I think the phone needs to be fully booted and USB-debbug-enabled for this) so I cant follow any of the solutions wich I found in the last two days. A PB99IMG.zip is also not flashable in HBOOT since it just cancels after "Checking..[PB99IMG.zip]" and returns back to the HBOOT screen.
Here's my phones specs:
CID: VODAP102
PVT4
S-ON
HBOOT 0.93.0001
MICROP-051d
SLCD
RADIO 5.11.05.27
If someone has an idea where to start, any help would be greatly apreciated. If someone is even willing to assist via instant messaging or skype I would be happy to compensate his time with a donation via paypal! Thank you in advance!
EDIT: SOLVED!!!
cosine83 from the unrevoked IRC channel solved it for me!!
I was able to enter RUU mode and flash the PB99IMG.zip in 2 quick steps!
In fastboot mode:
1.fastboot oem rebootRUU
2.fastboot flash zip PB99IMG.zip
huge thanks!!!

Hello sorry for that
but the good news is your phone is not dead, do you red this
http://forum.xda-developers.com/showthread.php?t=750888
I think your fix is here : http://forum.xda-developers.com/showthread.php?p=7602850#post7602850
hope it can help you

what happens if you hold vol down + power when the phone is off?

Good idea. I forgot to ask
Sent from my HTC Desire using XDA Premium App

Droidxda said:
Hello sorry for that
but the good news is your phone is not dead, do you red this
http://forum.xda-developers.com/showthread.php?t=750888
I think your fix is here : http://forum.xda-developers.com/showthread.php?p=7602850#post7602850
hope it can help you
Click to expand...
Click to collapse
Trying this right now, almost gave up on this...
vol down + power brings me to the regular hboot manu and i can also enter fastboot...

Regular 0.93 ?
Do you try unrevoked?
Sent from my HTC Desire using XDA Premium App

Droidxda said:
Regular 0.93 ?
Do you try unrevoked?
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
for unrevoked I need my phone booted up and have debugging enabled as far as i know, but I cant boot it...
EDIT: I followed your guide from HERE but the result is still the same. I am not able to flash the PB99IMG.zip HBOOT reads it (the blue bar on the right top goes all the way up but then comes "Checking..[PB99IMG.zip]" and the procedure just aborts.
I think it must have something to do with a wrong mtd0.img which was flashed during my first attempt to downgrade (mybe not matching the PB99IMG???) or there is a problem with the goldcard (i am very certain that I did everythin correct with the gc, did it manually and also tith the gc-maker)

On the fastboot menu, could you access a recovery?
Sent from Desire Bravo with xda App. Leedroid ROM HD port inside.

Droidxda said:
On the fastboot menu, could you access a recovery?
Sent from Desire Bravo with xda App. Leedroid ROM HD port inside.
Click to expand...
Click to collapse
well I can select the "recovery" from the Hboot menu and also try flashing an update.zip, but every time I do this I get:
E:failed to verify whole-file signature
E:signature verifivation failed
Installation aborted

The best way should find a correct hboot P99IMG.zip and put it on the SD
Should ask to unrevoked team by the irc channel.
Sent from Desire Bravo with xda App. Leedroid ROM HD port inside.

cgorki said:
well I can select the "recovery" from the Hboot menu and also try flashing an update.zip, but every time I do this I get:
E:failed to verify whole-file signature
E:signature verifivation failed
Installation aborted
Click to expand...
Click to collapse
**** I know this message, but I can't remember.
EDIT - hboot 0.93 ?
Sent from Desire Bravo with xda App. Leedroid ROM HD port inside.

I thought it wasn't possible to change hboot until you s-off? or does a goldcard make it possible when s-on?
if you can access the bootloader menu (vol down + power) then you should be able to fix your phone.

Do you try to install an ruu Rom?
Sent from Desire Bravo with xda App. Leedroid ROM HD port inside.

Boot the phone into bootloader menu.
connect usb cable.
in command prompt load the SDK folder, instead of typing adb.exe type fastboot.exe.
place the hboot you want into the "platform-tools" folder in the SDK directory - if its in the pb99img.zip then extract the .img file from there and place just that file into the folder.
type "fastboot flash hboot *name-of-file.img*"
if this works then type
type "fastboot reboot-bootloader"
type "fastboot erase cache"
Not sure it will work though as you are S-ON.
However you should be able to flash a recovery through the same way, type "fastboot flash recovery *name.img*". Not sure if this will help fix it, but if you can access recovery then its a start! Obviously you'll need to download a recovery first and place it into the platform-tools folder.

himeshladva said:
Boot the phone into bootloader menu.
connect usb cable.
in command prompt load the SDK folder, instead of typing adb.exe type fastboot.exe.
place the hboot you want into the "platform-tools" folder in the SDK directory - if its in the pb99img.zip then extract the .img file from there and place just that file into the folder.
type "fastboot flash hboot *name-of-file.img*"
if this works then type
type "fastboot reboot-bootloader"
type "fastboot erase cache"
Not sure it will work though as you are S-ON.
However you should be able to flash a recovery through the same way, type "fastboot flash recovery *name.img*". Not sure if this will help fix it, but if you can access recovery then its a start! Obviously you'll need to download a recovery first and place it into the platform-tools folder.
Click to expand...
Click to collapse
doubt that this will work with s-on, but trying anyways!!
thank you!

cgorki said:
doubt that this will work with s-on, but trying anyways!!
thank you!
Click to expand...
Click to collapse
would probably give the recovery option a go first..

himeshladva said:
would probably give the recovery option a go first..
Click to expand...
Click to collapse
C:\1>fastboot flash recovery cwm.img
sending 'recovery' (3366 KB)... OKAY [ 0.488s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.958s
EDIT: Is there a way to issue ADB commands to the phone without having it booted up?

cgorki said:
C:\1>fastboot flash recovery cwm.img
sending 'recovery' (3366 KB)... OKAY [ 0.488s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.958s
EDIT: Is there a way to issue ADB commands to the phone without having it booted up?
Click to expand...
Click to collapse
You can if you are able to access recovery.. or try to just turn the phone on and see.
Also, take a read through this.. maybe it will help.
http://www.askabouthugo.com/general...n-fastboot-with-remote-signature-verify-fail/

Not sure what else can be done if that doesn't help.
Would be best to join unrevoked IRC channel as they would know a lot more about it..

himeshladva said:
Not sure what else can be done if that doesn't help.
Would be best to join unrevoked IRC channel as they would know a lot more about it..
Click to expand...
Click to collapse
I'm talking to some of the guys from the IRC, so far no solution in sight. Maybe tomorrow there are some ppl online who are familiar with the HTC Bravo GSM...

[Q] Phone bricked, android flasher won't work

I have a htc desire with the alpharev bootloader(CM7 r2). I am stucked with the htc screen with the signs in every corner. I tried this guide:
RUU PROBLEMS
"I tried using a RUU, but it failed, and now my phone is stuck on a black HTC Screen with /!\ In every corner!"
Possible Causes:
- You were S-OFF and you flashed a custom bootloader from alpharev
- You didn't check the MD5 Sums before proceeding, and the download may have been corrupted.
- You tried using the wrong RUU
[5]Fixing your problem
Your phone is stuck in RUU mode. RUU mode is like fastboot mode, and can still receive fastboot commands, therefore it can be easily "fixed". It helps to have a goldcard for this problem, so that you can use any RUU you want.
S-OFF
[STEP1]- download "Bravo Stock" from Alpharev
[STEP2]- download Android Flasher
[STEP3]- use android flasher to flash "Bravo Stock"
[STEP4]- run the RUU again and wait for it to finish
S-ON
If you're S-ON it eliminates the possibility of you having a custom bootloader, and the only possibility now is that the RUU was corrupted or you used the wrong RUU for your device. Therefore, for this process you need a goldcard.
[STEP1]- Create the goldcard from the tutorial
[STEP1]- Use the WWE RUU
Click to expand...
Click to collapse
I am S-off but the android flasher doesn't recognize my phone (I doesn't show any log line in the program and just hangs) . The android-usb-driver is installed and I can see the device in de device manager from windows. When I try to reflash it with a RUU I get error 152, image update error and a failed with the "system" part.
Does someone know what I am doing wrong? I tried it with Windows 7 And a clean XP installation (without htc sync)
When I try it with the sdk tools I got this:
C:\tools>fastboot.exe flash recovery c:\hboot.img
sending 'recovery' (512 KB)... OKAY
writing 'recovery'... FAILED (remote: image error! (BootMagic check fail))

make sure you've installed fastboot drivers.. then try again. Also error 152 means you don't have a goldcard. This is necessary.
Or if you're lazy and you don't want to faff with all that.. you could try a quite risky procedure (because if something goes wrong there's no un-f*cking it) and flash the 2.3.3 RUU from HTCdev.com which requires you to do nothing but run the RUU.

[Q] bricked (challenge to members)

MARVEL PVT SHIP S-ON RL
HBOOT 1.09.0099
MICROP-0451
RADIO-7.57.39.10M
Feb 8 2012, 18:29:31
Hello,
Recently my htc wildfire S crashed and only boots to Hboot mode..
cannot go to recovery and cannot do factory reset.. when i press these options the phone just reboots to hboot mode
the phone can be detected via usb and i do get hboot usb plug detection as well fastboot usb mode..
I have tried hundreds of possibilities to flash but failed..
Have tried the RUU method via computer whereby i get different errors and also tried different RUU but unsuccessful
The last RUU that i had used to root my phone was
RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed
which worked well for one year but crashed after reseting to factory settings
now..
when my bootloader is unlocked i got error 155 image error
when my bootloader is relocked i get error 140 bootloader version error
both ways it stops during verifying for signature
and on the phone it shows main version older.. update failed
have tried to place PM76IMG.zip on sdcard but the phone reads as wrong or no image
(and this goes for different RUU as well)
have tried to use fastboot via cmd commands but get
FAILED (remote: 12 signature verify fail)
or
FAILED (remote: 43 signature verify fail)
images do load without problem but fail after signature checking
there is no other RUU newer than 2.26
cannot downgrade hboot cause cannot access my phone just hboot mode only
cannot do flash recovery as i have tried many recovery images all failing as well as clockword mode recovery image
PLEASE HELP load the ROM and make the phone usable again

Did you make a Gold card before placing PG76IMG in SD card?

tahaice said:
MARVEL PVT SHIP S-ON RL
HBOOT 1.09.0099
MICROP-0451
RADIO-7.57.39.10M
Feb 8 2012, 18:29:31
Hello,
Recently my htc wildfire S crashed and only boots to Hboot mode..
cannot go to recovery and cannot do factory reset.. when i press these options the phone just reboots to hboot mode
the phone can be detected via usb and i do get hboot usb plug detection as well fastboot usb mode..
I have tried hundreds of possibilities to flash but failed..
Have tried the RUU method via computer whereby i get different errors and also tried different RUU but unsuccessful
The last RUU that i had used to root my phone was
RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed
which worked well for one year but crashed after reseting to factory settings
now..
when my bootloader is unlocked i got error 155 image error
when my bootloader is relocked i get error 140 bootloader version error
both ways it stops during verifying for signature
and on the phone it shows main version older.. update failed
have tried to place PM76IMG.zip on sdcard but the phone reads as wrong or no image
(and this goes for different RUU as well)
have tried to use fastboot via cmd commands but get
FAILED (remote: 12 signature verify fail)
or
FAILED (remote: 43 signature verify fail)
images do load without problem but fail after signature checking
there is no other RUU newer than 2.26
cannot downgrade hboot cause cannot access my phone just hboot mode only
cannot do flash recovery as i have tried many recovery images all failing as well as clockword mode recovery image
PLEASE HELP load the ROM and make the phone usable again
Click to expand...
Click to collapse
Your recoverys are not flashing as you have relocked your bootloader pal. Try flashing the stock recovery from hboot this should at least have a factory reset option. Failing this, you should try re-unlocking your bootloader and then flashing cwm.
If all of this fails then you will need to gain access to an xtc clip, make the phone s-off and then flash any ruu you want bump this thread if you need anymore help
Sent from my Nexus 7 using Tapatalk HD

varun26296 said:
Did you make a Gold card before placing PG76IMG in SD card?
Click to expand...
Click to collapse
thanks for reply
i did not make a gold card.. my phone crashed on me without consent lol..
and i cannot make one now coz there is no shell or rom on my phone.. just bootloader and thats it..
unless there is a way around to make a goldcard via fastboot menu??

heavy_metal_man said:
Your recoverys are not flashing as you have relocked your bootloader pal. Try flashing the stock recovery from hboot this should at least have a factory reset option. Failing this, you should try re-unlocking your bootloader and then flashing cwm.
If all of this fails then you will need to gain access to an xtc clip, make the phone s-off and then flash any ruu you want bump this thread if you need anymore help
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for reply
none of the recoverys are flashing either bootloader is unlocked or relocked.. Tried even flashing CWM but all i get is errors that image verify fail!! unless i am going somewhere wrong..??
My phone is S-ON is there no around this without an xtc clip..?? coz thats another issue

tahaice said:
Thanks for reply
none of the recoverys are flashing either bootloader is unlocked or relocked.. Tried even flashing CWM but all i get is errors that image verify fail!! unless i am going somewhere wrong..??
My phone is S-ON is there no around this without an xtc clip..?? coz thats another issue
Click to expand...
Click to collapse
What errors are you getting when trying to flash cwm via fastboot while the bootloader is unlocked. Be specific please
Also their is no other way to s-off bar the xtc clip. But, once you have s-off trouble shooting bootloader/ruu issues is far easier
Sent from my Nexus 7 using Tapatalk HD

heavy_metal_man said:
What errors are you getting when trying to flash cwm via fastboot while the bootloader is unlocked. Be specific please
Also their is no other way to s-off bar the xtc clip. But, once you have s-off trouble shooting bootloader/ruu issues is far easier
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
#heavymetal
when UNLOCKED
image update error
when RELOCKED
signature verify fail
i tried flashing CWM version 5.0.2.8 image file..
(the same happens while flashing other files!!)

tahaice said:
#heavymetal
when UNLOCKED
image update error
when RELOCKED
signature verify fail
i tried flashing CWM version 5.0.2.8 image file..
(the same happens while flashing other files!!)
Click to expand...
Click to collapse
Ok while unlocked, take your cwm recovery image and rename it to recovery.img if you have not already.
Then boot into fastboot and use the command
Fastboot boot recovery recovery.img
Hopefully it will boot into the recovery. This is only tempoary, do not reboot until you have wiped everything. Check and see if it boots after full wipes.
If this fails you will need a xtc clip...
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
---------- Post added at 09:45 PM ---------- Previous post was at 09:04 PM ----------
heavy_metal_man said:
Ok while unlocked, take your cwm recovery image and rename it to recovery.img if you have not already.
Then boot into fastboot and use the command
Fastboot boot recovery recovery.img
Hopefully it will boot into the recovery. This is only tempoary, do not reboot until you have wiped everything. Check and see if it boots after full wipes.
If this fails you will need a xtc clip...
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Edit: the more i look into this the more it doesn't look good to be honest pal, most people who get into this state send it back to the manufacturer and get the motherboards replaced....
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium

heavy_metal_man said:
Ok while unlocked, take your cwm recovery image and rename it to recovery.img if you have not already.
Then boot into fastboot and use the command
Fastboot boot recovery recovery.img
Hopefully it will boot into the recovery. This is only tempoary, do not reboot until you have wiped everything. Check and see if it boots after full wipes.
If this fails you will need a xtc clip...
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
---------- Post added at 09:45 PM ---------- Previous post was at 09:04 PM ----------
Edit: the more i look into this the more it doesn't look good to be honest pal, most people who get into this state send it back to the manufacturer and get the motherboards replaced....
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
tried again all possibilities..
with fastboot boot recovery recovery.img it does download successfully and writes booting.. however after the phone has booted by itself the htc screen shows up (with white background) and directly goes into fastboot menu without other options...
Maybe i am uploading wrong recovery image??
if its loading into bootloader menu that means my phone is soft bricked right?? which can be undone??
my dilemma is that i live in a third world country with no htc service providers or good phone repair shops who would have an xtc clip..

tahaice said:
tried again all possibilities..
with fastboot boot recovery recovery.img it does download successfully and writes booting.. however after the phone has booted by itself the htc screen shows up (with white background) and directly goes into fastboot menu without other options...
Maybe i am uploading wrong recovery image??
if its loading into bootloader menu that means my phone is soft bricked right?? which can be undone??
my dilemma is that i live in a third world country with no htc service providers or good phone repair shops who would have an xtc clip..
Click to expand...
Click to collapse
The main issue is that it should still boot into the recovery via fastboot regardless of its working state from what i have read the main nand seems to have some sort of error that it cannot over write so its not letting you boot anything weither that is a fail safe or not i dont know. At this point a xtc clip would be your last hope, but i cannot guarrentee it would work... I have an xtc clip, but i dont want to post it outside of the uk ......
Sent from my Nexus 7 using Tapatalk HD

Were you overclocked ? Were you using some sort of memory script ?
I'd say your best option is to have it sent back, smells like a burnt motherboard.

heavy_metal_man said:
The main issue is that it should still boot into the recovery via fastboot regardless of its working state from what i have read the main nand seems to have some sort of error that it cannot over write so its not letting you boot anything weither that is a fail safe or not i dont know. At this point a xtc clip would be your last hope, but i cannot guarrentee it would work... I have an xtc clip, but i dont want to post it outside of the uk ......
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
thanks for your help heavy metal.. seems i am left with a dead fone after all RIP :crying:

omnomnomkimiiee said:
Were you overclocked ? Were you using some sort of memory script ?
I'd say your best option is to have it sent back, smells like a burnt motherboard.
Click to expand...
Click to collapse
no didnt mess with phone settings.. didnt overclock it.. and no memory scripts.. though had installed avast anti-theft software.. would it have played a part? but i remember uninstalling the software before resetting my to factory settings!!

im sorry for your loss man what do you think you will do with the device? bin?

Recover soft-bricked HTC Wildfire S
tahaice said:
no didnt mess with phone settings.. didnt overclock it.. and no memory scripts.. though had installed avast anti-theft software.. would it have played a part? but i remember uninstalling the software before resetting my to factory settings!!
Click to expand...
Click to collapse
Hi tahaice!.
I just recovered an HTC Wildfire S A510e for a friend with a problem similar to yours!
He entered on HBOOT and wiped & format some partitions: data/factory reset, system, data, sdcard, etc.....
I read quickly your problem and I think that this can help you:
1.- Download the correct RUU from: androidfiles.org/ruu/?developer=Marvel_MarvelC
For instance, I used RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed for Spain (Device was with last update, my friend was sure).
You can check it on HBOOT:
MARVEL PVT SHIP S-ON RL
HBOOT 1.09.0099
MICROP-0451
RADIO-7.57.39.10M
Feb 8 2012, 18:29:31
Click to expand...
Click to collapse
And when you finish restore: go to Settings/About phone/Software info/More. Base band version must match the file you used (you will not restore radio.img, if not needed).
2.- Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be folders with long names (C:\Users\lefe\AppData\Local\Temp\{9739F95A-99D7-43BA-8AB6-E4F02264D361}\{50F2F878-636A-496F-A7CB-544C067E0C4B} for instance).
Inside one of them you will find the file rom.zip from RUU. Open it with 7zip and extract recovery.img, boot.img and system.img. Put it in the location you preffer (C:\Users\lefe\HTC Wildfire S A510e\ADB in the example).
You also need adb.exe, AdbWinApi.dll and fastboot.exe. Copy from the folder you found the file rom.zip (or from Android SDK tools if you have installed it).
3.- Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
As you say, this is not needed in your case because your phone goes directly. Just plug.
4.- Open a command prompt in Windows and navigate to the folder where you unpacked ADB / installed Android SDK tools. Flash the stock images extracted in step 2 above using the following commands (Remember to turn your firewall off):
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Click to expand...
Click to collapse
Example (what I did):
Code:
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash boot boot.img
sending 'boot' (2870 KB)...
OKAY [ 1.336s]
writing 'boot'...
OKAY [ 1.650s]
finished. total time: 2.994s
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash recovery recovery.img
sending 'recovery' (3494 KB)...
OKAY [ 1.572s]
writing 'recovery'...
OKAY [ 1.970s]
finished. total time: 3.554s
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash system system.img
sending 'system' (259862 KB)...
OKAY [ 31.535s]
writing 'system'...
OKAY [ 64.846s]
finished. total time: 96.393s
5.- Finally, in your phone go to HBOOT menu and make a FACTORY RESET.
If needed, PowerOff device (remove battery for 3 seconds) and Boot the phone into bootloader (hold down volume and press power).
That's all!!.
I hope you get lucky!
[Plz, mark thread as Solved if that helped you, other users will love to read it when googling]

heavy_metal_man said:
im sorry for your loss man what do you think you will do with the device? bin?
Click to expand...
Click to collapse
right now its hidden deep inside my cupboard.. dont want to see it near me!! a disappoinment

bolzass said:
Hi tahaice!.
I just recovered an HTC Wildfire S A510e for a friend with a problem similar to yours!
He entered on HBOOT and wiped & format some partitions: data/factory reset, system, data, sdcard, etc.....
I read quickly your problem and I think that this can help you:
1.- Download the correct RUU from: androidfiles.org/ruu/?developer=Marvel_MarvelC
For instance, I used RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed for Spain (Device was with last update, my friend was sure).
You can check it on HBOOT:
And when you finish restore: go to Settings/About phone/Software info/More. Base band version must match the file you used (you will not restore radio.img, if not needed).
2.- Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be folders with long names (C:\Users\lefe\AppData\Local\Temp\{9739F95A-99D7-43BA-8AB6-E4F02264D361}\{50F2F878-636A-496F-A7CB-544C067E0C4B} for instance).
Inside one of them you will find the file rom.zip from RUU. Open it with 7zip and extract recovery.img, boot.img and system.img. Put it in the location you preffer (C:\Users\lefe\HTC Wildfire S A510e\ADB in the example).
You also need adb.exe, AdbWinApi.dll and fastboot.exe. Copy from the folder you found the file rom.zip (or from Android SDK tools if you have installed it).
3.- Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
As you say, this is not needed in your case because your phone goes directly. Just plug.
4.- Open a command prompt in Windows and navigate to the folder where you unpacked ADB / installed Android SDK tools. Flash the stock images extracted in step 2 above using the following commands (Remember to turn your firewall off):
Example (what I did):
Code:
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash boot boot.img
sending 'boot' (2870 KB)...
OKAY [ 1.336s]
writing 'boot'...
OKAY [ 1.650s]
finished. total time: 2.994s
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash recovery recovery.img
sending 'recovery' (3494 KB)...
OKAY [ 1.572s]
writing 'recovery'...
OKAY [ 1.970s]
finished. total time: 3.554s
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash system system.img
sending 'system' (259862 KB)...
OKAY [ 31.535s]
writing 'system'...
OKAY [ 64.846s]
finished. total time: 96.393s
5.- Finally, in your phone go to HBOOT menu and make a FACTORY RESET.
If needed, PowerOff device (remove battery for 3 seconds) and Boot the phone into bootloader (hold down volume and press power).
That's all!!.
I hope you get lucky!
[Plz, mark thread as Solved if that helped you, other users will love to read it when googling]
Click to expand...
Click to collapse
thank bolzass for ur reply..
without doubt we have the same ROM version and i had downloaded the same RUU from androidfiles website.. but still getting those silly errors despite following each step carefully!! i dont know what has gone wrong

BY THE WAY I CANNOT ERASE USERDATA
it says FAILED (remote: not allowed)
can this be causing other errors???

tahaice said:
right now its hidden deep inside my cupboard.. dont want to see it near me!! a disappoinment
Click to expand...
Click to collapse
At this point its probably for the best
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium

tahaice said:
thank bolzass for ur reply..
without doubt we have the same ROM version and i had downloaded the same RUU from androidfiles website.. but still getting those silly errors despite following each step carefully!! i dont know what has gone wrong
Click to expand...
Click to collapse
Ops!?!?..., Can you detail these errors?.
I'm also reading your message bellow about erasing Userdata...:$, detail also this scenario so we can think about your concret issues.
Keep fighting till you're sure there's nothing to do...

[Q] After downgrade touch don't work

My HTC wildfire touch don't work after downgrade from 2.34.186.1 to from 2.34.186.1.
The branding ist 1und1. After this i try to find the original OTA 2.34.186.1 to upgrade
to the old one that was on the phone before. - no way - i don't found
After this i unlocked the bootloader and i think that there is a way to upgrade any firmware
but its not possible.
My bootscreen:
*** UNLOCKED ***
BUZZ PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0622
RADIO-3.35.15.31
Dec 13 2011,12:08:54
The HTC boot normaly to the lock screen but the touch don't work.
Anyone an idea to solve my problem an install another rom?

Here is another thread that discusses a similar issue.
Hope it'll help.
http://forum.xda-developers.com/showthread.php?t=1056767
Sent from my G9 using Tapatalk

Pretendde said:
My HTC wildfire touch don't work after downgrade from 2.34.186.1 to from 2.34.186.1.
The branding ist 1und1. After this i try to find the original OTA 2.34.186.1 to upgrade
to the old one that was on the phone before. - no way - i don't found
After this i unlocked the bootloader and i think that there is a way to upgrade any firmware
but its not possible.
My bootscreen:
*** UNLOCKED ***
BUZZ PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0622
RADIO-3.35.15.31
Dec 13 2011,12:08:54
The HTC boot normaly to the lock screen but the touch don't work.
Anyone an idea to solve my problem an install another rom?
Click to expand...
Click to collapse
Hmmm. This is going to be hard to get out of as you upgraded your Hboot. Does the phone still register fastboot commands? Also what downgrade thread did you follow?
Sent from my HTC Sensation using Tapatalk

It dont work at update with ruu shows the version 2.46.0.0 of the divece rom....
The update prozess stops and there is " FEHLER [155] : ABBILD-UPDATE-FEHLER " (IMAGE UPDATE ERROR)
The same with the PC49IMG.zip on microsd card:
RUU
Security fail!
Update Fail!

Pretendde said:
It dont work at update with ruu shows the version 2.46.0.0 of the divece rom....
The update prozess stops and there is " FEHLER [155] : ABBILD-UPDATE-FEHLER " (IMAGE UPDATE ERROR)
The same with the PC49IMG.zip on microsd card:
RUU
Security fail!
Update Fail!
Click to expand...
Click to collapse
That's not what I mean, to unlock your bootloader you would have had to issue the command fastboot OEM unlock, or fastboot flash OEM unlock unlock_token.bin or something similar. These types of commands are the ones I'm interested in I want to see if you can flash clockworkmod recovery pal.
Sent from my HTC Sensation using Tapatalk

I downgraded with the standard buzzdowngrade.zip package, step1 but the goldcard-step fail.....i flashed after hboot downgrade RUU_Buzz_Vodafone_DE_1und1_1.19.186.3_Radio_13.45.55.24_3.35.15.31_release_133745_signed.exe
Than was the problem with the touch ... it dont work.
After this i tryed many ruu's ....no way.
Than i downloaded from htcdev - PC4910000_Buzz_Froyo_hboot_1.02.0000_R3.exe and flashed and unlocked with Unlock_code.bin
I was thinking i would be able to unlock and update every rom

Pretendde said:
I downgraded with the standard buzzdowngrade.zip package, step1 but the goldcard-step fail.....i flashed after hboot downgrade RUU_Buzz_Vodafone_DE_1und1_1.19.186.3_Radio_13.45.55.24_3.35.15.31_release_133745_signed.exe
Than was the problem with the touch ... it dont work.
After this i tryed many ruu's ....no way.
Than i downloaded from htcdev - PC4910000_Buzz_Froyo_hboot_1.02.0000_R3.exe and flashed and unlocked with Unlock_code.bin
I was thinking i would be able to unlock and update every rom
Click to expand...
Click to collapse
Ok so fastboot works, good good. Do you have clockworkmod recovery installed? If not follow my thread for rooting hboot 1.02.0000 and install clockworkmod but go no further.
Also just for your information the ruu will not install because of
1. Your honor is higher than the ones in the RUU,
2 your bootloader is unlocked.
We need to downgrade you to the WWE rom with hboot 1.01.0001 and hopefully that will restore your touch panel to working order
Sent from my HTC Sensation using Tapatalk

Clockworkmod recovery is installed, rooting hboot 1.02.0000 o.k.
and now?

Pretendde said:
Clockworkmod recovery is installed, rooting hboot 1.02.0000 o.k.
and now?
Click to expand...
Click to collapse
ok so what we want to do know is downgrade your hboot to 1.01.0001 so to do that we need your misc partition to be edited. as such i would like you to boot the phone into clockworkmod recovery and connect it to the pc with a usb cable. windows should install the drivers if it has not done so already.
next you will need to set up your command prompt for using adb/fastboot commands.
then we will pull a copy of your misc partition to your sdcard and then copy it into your windows adb folder.
then you will upload that image to me, i will make the necessary changes and then re-upload for you.
then you will flash it to the phone all going well, re-lock your bootloader and then downgrade your hboot and rom and hopefully regain touch input
then as an extra if you want to use a rooted version of that german ruu you were trying to flash i can make you a "safe to flash" version
ok, so....
step 1. Connect your wildfire up to your pc In clockworkmod recovery mode.
step 2. open a command prompt within your adb/fastboot folder. (the same one you used to flash clockworkmod recovery)
step 3. enter the following commands one at a time. copy paste is recommended.
Code:
adb shell
su
cat /dev/mtd/mtd0 > /sdcard/misc.img
exit
exit
adb pull /sdcard/misc.img misc.img
step 4. Upload this file to somewhere like dropbox or media fire and then send me a link to it.

in command prompt
su
/sbin/sh: su: not found
what i do wrong?

Pretendde said:
in command prompt
su
/sbin/sh: su: not found
what i do wrong?
Click to expand...
Click to collapse
OK just skip that and move onto the next bit.
Sent from my Nexus 7 using Tapatalk

I attached this file here, i hope it is o.k.
It takes a while until i found out to mount the SD card before

Pretendde said:
I attached this file here, i hope it is o.k.
It takes a while until i found out to mount the SD card before
Click to expand...
Click to collapse
okey dokey, here is your new misc image. extract it into your adb folder.
i have edited this so it will re-lock your bootloader automatically once you have flashed it. one problem solved
also download this package, it has some tools you will need and the WWE rom you need to flash
lastly we need to make a goldcard. this will be hard given that your touch screen is non-functional. as such you will need a different, working android phone and YOUR sdcard. this trick is sdcard specific so dont swap them about
ok once you are ready with the right stuff, do these steps.
step 5. now we need to make a gold card. if you already have one, you can skip this part. first using your working android phone, download and install Goldcard helper from the android market. Run the app and copy down your SD cards reverse cid. double check it
step 6. now go to this website here and enter in your reverse cid. it will then let you download a goldcard.img.
step 7. now go back to the package you downloaded earlier with the WWE rom (named 1.01.zip) in it and run the goldcardtool.exe, this will flash the goldcard to your sd card. Warning! this will format your card!! in order to achieve this you will have to mount the sdcard from clockworkmod recovery to the computer, use mount usb storage and not mount sdcard.
step 8. once that is done we are now ready for the final push

Now the gold card is ready, i leave al the data on the goldcard, its not been formatted. Goldcard tool says, G: Goldcard is now ready.
The new misc image, must be copy to the phone ?

Pretendde said:
Now the gold card is ready, i leave al the data on the goldcard, its not been formatted. Goldcard tool says, G: Goldcard is now ready.
The new misc image, must be copy to the phone ?
Click to expand...
Click to collapse
ok from here copy the Nmisc.img to your sdcard and do not rename it, leave it on the sd card within no folders.
then connect up the phone in clockworkmod recovery again, and mount the sdcard with mount sdcard and not usb mass storage.
lastly make sure that the 1.01.zip is in your adb folder.
issue the following commands.
Code:
adb shell
(your shell symbol should be a #)
flash_image misc /sdcard/Nmisc.img
exit
(now it should not be a #)
adb reboot bootloader
The phone should not reboot into bootloader and should say at the top locked OOW.
This is ok, if it does not say this then your misc image was not flashed.
if all is well issue these commands.
Code:
fastboot oem rebootRUU
fastboot flash zip 1.01.zip
This will state an error, and that it needs to be reflushed. this is what we want, if any other issue your goldcard may have failed.
repeat the last command to reflush.
Code:
fastboot flash zip 1.01.zip
(this will take a while.)
fastboot reboot
the phone should reboot into the WWE stock rom and hopefully your touch screen will be working again. if it is proceed to s-off with revolutionary here ignore all but revolutionary and then if you want the german ruu as a safe flash rom send me a link to the ruu and I will make it. but it make take a few days.
im at work atm so my replys will be delayed pal, good luck

INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 63.656s
i flashed 3 times....

Pretendde said:
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 63.656s
i flashed 3 times....
Click to expand...
Click to collapse
Your gold card has failed. Format the sdcard and then reissue the fastboot commands.
Sent from my HTC Sensation using Tapatalk

Yes the goldcard was bad, now its okay but n ow a new error :
INFOsignature checking...
FAILED (remote: not allowed)
finished. total time: 56.078s
flashed 5 times ...same error

Pretendde said:
Yes the goldcard was bad, now its okay but n ow a new error :
INFOsignature checking...
FAILED (remote: not allowed)
finished. total time: 56.078s
flashed 5 times ...same error
Click to expand...
Click to collapse
Does your bootloader still say locked?
Sent from my HTC Sensation using Tapatalk

heavy_metal_man said:
does your bootloader still say locked?
Sent from my htc sensation using tapatalk
Click to expand...
Click to collapse
yes
*** locked (00w) ***