Develop Bugs

[Q] DHD bricked?

Hi all,
Im having a little trouble with my dhd. It won't boot up !
I can get into HBOOT, but thats it. (ie. no recovery CWM)
When trying to boot normally it hangs at spash screen.
so far i have tried:
- fastboot flashing (system.img dosn't flash (for known reasons))
- this thread (http://forum.xda-developers.com/showthread.php?t=841890) (tried with 2 different RUUs)
everything seemed to go according to plan, but still exactly the same problem.
- I've even tried flashing back the stock spash screen via fastboot in preperation to send it back to tmobile/htc to fix BUT, despite fastboot telling me flashing was succsessful, i still have my custom splash!
- pulling my hair out!
ive got eng hboot s-off radio s-off supercid and stuff??
my hboot info screen looks like this:
ACE PVT ENG S-OFF
HBOOT-0.85.2007 (PD9810000)
MICROP-0438
RADIO-26.04.02.17_M2
eMMC-boot
Oct 11 2010, 12:44:14
SYSTEM INFO
SN-HT0CPRX05836
LCD-SHARP
TOUCH PANEL-SYN3KT_0108
Commit-7eafc656
OS ver.-1.39.110.1
IMEI-
CID-11111111
RAM-768MB
eMMC-Sandisk 2223MB 4554751sectors
Thanks in advance to anyone with ideas

Which cw recovery is installed?
Sent from my Desire HD using XDA App

First question, what did you do immediately before you turned you DHD off, hence the reboot?
From the bootloader can you enter fastboot? You should be able to flash recovery from there. You mention "for known reasons" what are these?

Hi pwraggcan,
I'm not too sure? and I'm not sure how I can check either, as I can only enter hboot/fastboot.
AndyHarney,
As far as I can remember I was using my phone as normal. (no risky installs/flashes to speak of). Then overnight it ran out of battery, and now won't boot up .. ?
fastboot flash system system.img returns:
sending 'system' (410134 KB)... FAILED (remote: data length is too large)
finished. total time: 0.006s
fastboot flash recovery recovery.img returns:
sending 'recovery' (8701 KB)... OKAY [ 1.494s]
writing 'recovery'... OKAY [ 0.837s]
finished. total time: 2.331s
but when I choose 'RECOVERY' form hboot menu it still hangs on splash.

jason9 said:
Hi pwraggcan,
I'm not too sure? and I'm not sure how I can check either, as I can only enter hboot/fastboot.
AndyHarney,
As far as I can remember I was using my phone as normal. (no risky installs/flashes to speak of). Then overnight it ran out of battery, and now won't boot up .. ?
fastboot flash system system.img returns:
sending 'system' (410134 KB)... FAILED (remote: data length is too large)
finished. total time: 0.006s
fastboot flash recovery recovery.img returns:
sending 'recovery' (8701 KB)... OKAY [ 1.494s]
writing 'recovery'... OKAY [ 0.837s]
finished. total time: 2.331s
Click to expand...
Click to collapse
So you have recovery, and you're rooted, well I'd say install a ROM as ROMS flash system, boot and cache img files. Sending a 410mb file ofver adb seems a bit risky. Also, if you have no ROMs on the SD Card go into recovery, mounts and storage and at the bottom is usb or something.

MrYuiM,
I don't mean to act the fool, but I don't fully understand you're post.
"well I'd say install a ROM as ROMS flash system, boot and cache img files"
not sure how I can go about doing this? using fastboot?
"Also, if you have no ROMs on the SD Card go into recovery"
which ROMs do you mean? I have on my sdcard "LeeDrOiD_HD_V1.5.1.zip" and others. I also have some nandroid backups.
Currently, I have not found a way to enter recovery..
P.S I apologize for spewing my ignorance all over this thread.

Get PD98IMG.zip from my downgrade guide, put it into your SD card and go to the bootloader. Then tell us what what happens.
By the way, you still have fully warranty despite the fact that your device has S-OFF. There is nothing about software mods in warranty terms. For example mike1986 sent his phone to HTC's service center, it was S-OFF and it even had a custom ROM in it, and they did not complain.

jkoljo said:
Get PD98IMG.zip from my downgrade guide, put it into your SD card and go to the bootloader. Then tell us what what happens.
By the way, you still have fully warranty despite the fact that your device has S-OFF. There is nothing about software mods in warranty terms. For example mike1986 sent his phone to HTC's service center, it was S-OFF and it even had a custom ROM in it, and they did not complain.
Click to expand...
Click to collapse
When I asked HTC they were pretty stern on the fact that rooting voids their warranty despite it not being in the guidelines :/

jason9 said:
MrYuiM,
I don't mean to act the fool, but I don't fully understand you're post.
"well I'd say install a ROM as ROMS flash system, boot and cache img files"
not sure how I can go about doing this? using fastboot?
"Also, if you have no ROMs on the SD Card go into recovery"
which ROMs do you mean? I have on my sdcard "LeeDrOiD_HD_V1.5.1.zip" and others. I also have some nandroid backups.
Currently, I have not found a way to enter recovery..
P.S I apologize for spewing my ignorance all over this thread.
Click to expand...
Click to collapse
To enter recovery turn your phone off completely and plug it into the charger, recovery will auto open. Also, everyone starts off somewhere.
But go with jkoljo first as he is more experienced

Hi jkoljo,
Downloading now,
It's also a big relief to hear that software modding dosn't effect warrenty *phew*

jason9 said:
Hi jkoljo,
Downloading now,
It's also a big relief to hear that software modding dosn't effect warrenty *phew*
Click to expand...
Click to collapse
Good luck mate, report back on how it goes

Might be futile but you could try a different recovery. If you're s off it should work. Try a 2.x.x.x then a 3.x.x.x. flashing from fastboot, it could be that. If the pd98img doesn't work then it might be a faulty motherboard and htc will have to fix it.
Sent from my Desire HD using XDA App

I tried jkoljo advice, but still no dice! ... (hey that rhymes!)
One thing I noticed as it was checking SD card: -
SD Checking...
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nbh]
No image or wrong image!
Loading...[PD98IMG.zip]
are those errors normal?!
just to clarify, after jkoljo's PD98IMG.zip update, I reboot and it hangs at my custom spash screen, just as before.
It's as if I hadn't tried to update/recover at all!
Anyways, Thankyou all for your help, assistance and advice.
I have to go out now, but ill be back tomorrow to try again.

It seems that you have to format your SD card. Do a full format to FAT32 (no quick format), and try it again.

Ok, formatted and tried again.
But same results as my last post.
I even tried with 2 SD's (4gb + 8gb).
Does this mean my phone is not recoverable..?
....I hope not..

oopes, delete this post please

pwraggcan said:
Try flashing a different recovery while in fastboot.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Could you recommend one?
The only one I've ever known is CWM.
Also I don't have much faith in fastboot right now.
When I flashed my stock splash, it said 'OK' but never changed!
Thanks pwraggcan

Try flashing a different recovery while in fastboot.. Try the stock one first and if you can boot into recovery wipe data/factory reset.
fastboot flash recovery nameofrecovery.img
recovery zip attached. good luck.

Thanks for the suggestion pwraggcan,
I tried that recovery.. and it flashed 'OK' but still no change from my previous attempts.
Soo... Shall I call this a write-off and let HTC deal with it..
Or are there any last ditch solutions I could be trying.
Jason9

As a last resort try the attached recovery. If this recovery doesn't work it's gotta be a hardware issue. I'm thinking if you backed up with a 2 series cw recovery then updated the recovery with rom manager to a 3 series cw recovery it won't let restore the backup. So, try the attached and fingers crossed, you're up and running. Probably won't sort it but definitely worth a try.

[Q] Red Triangle after Ace Hack Kit install.

I really hope someone here can help.
Several months ago I rooted my phone using the Ace Hack Kit and have been having fun installing several different ROM's without issue.
However I was flashing the ROM's without wiping the cache and was advised to always do this. So I decided to return to stock using the RUU tool and all was fine, however I went back to AHK to root the phone again and accidentally used an older version. The version I used is "Introducing Ace Advanced Hack Kit (03-10-2011)" and not the latest "aahk-11092012". during the flash there was an error regarding the "radio failure" and I attempted to run the flash again, but now all I get is the black screen with red triangle and system is frozen. I can reboot to the bootloader but no matter what I choose Recovery or Factory Reset it still ends up the same way.
Basically had I permabricked this phone or is there a way to recover it? I have been through the similar threads here but can seem to figure out a decent answer to the issue.
I appreciate the time taken to read and hope someone has the skills I lack !

What does the bootloader say at the top? Did AAHK have any output?

bananagranola said:
What does the bootloader say at the top? Did AAHK have any output?
Click to expand...
Click to collapse
The bootload shows the following:
ACE PVT SHIP S-OFF RL
HBOOT-2.00.0027
MICROP-0438
RADIO-26.03.02.26_M
eMMC-BOOT
SEP 7 2011,19:06:25
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Cheers for any help you can provide.

ToffeeArab said:
The bootload shows the following:
ACE PVT SHIP S-OFF RL
...
Click to expand...
Click to collapse
Don't worry, you're still S-OFF so you're fine. You just need to flash a custom recovery, then flash a new ROM from that. In my signature there's a link to a thread labeled Ace Think Tank; in post #7 of that thread, there's a PDF that will explain how to flash a custom recovery.
For future reference, it's a bit overkill to run a RUU just to clear caches. You can wipe all partitions from recovery without needing to do that.

bananagranola said:
Don't worry, you're still S-OFF so you're fine. You just need to flash a custom recovery, then flash a new ROM from that. In my signature there's a link to a thread labeled Ace Think Tank; in post #7 of that thread, there's a PDF that will explain how to flash a custom recovery.
For future reference, it's a bit overkill to run a RUU just to clear caches. You can wipe all partitions from recovery without needing to do that.
Click to expand...
Click to collapse
Thanks for that. I'll have a look there.
Cheers.

Have read that and have attempted to do the following
http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
[NOOB] Flashing a custom ROM & getting it to boot IF bootloader is htcdev unlocked
When it run the command "fastboot flash recovery recovery.img" the command prompt tries to run the command and sits there with < waiting for device >.

ToffeeArab said:
Have read that and have attempted to do the following
http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
[NOOB] Flashing a custom ROM & getting it to boot IF bootloader is htcdev unlocked
When it run the command "fastboot flash recovery recovery.img" the command prompt tries to run the command and sits there with < waiting for device >.
Click to expand...
Click to collapse
Wait, not that. That is for people who rooted using another method. I can't remember where it is in the doc off the top of my head, but look for a part about flashing a custom recovery.
Or you could wait until glevitan, the author, pops up here.

ToffeeArab said:
Have read that and have attempted to do the following
http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
[NOOB] Flashing a custom ROM & getting it to boot IF bootloader is htcdev unlocked
When it run the command "fastboot flash recovery recovery.img" the command prompt tries to run the command and sits there with < waiting for device >.
Click to expand...
Click to collapse
ToffeeArab, red triangle is stock recovery. That means that you have to flash CWM again from fastboot. Do the following:
Boot in fastboot USB
In the PC open a cmd as admin
Type: fastboot devices (and you should get your serial number)
Type: fastboot oem rebootRUU (you will get a black screen with silver HTC)
Type: wget http://dl.dropbox.com/u/30674730/cwm-5.0.2.7-ace.zip
Once the above download is done, type: fastboot flash zip cwm-5.0.2.7-ace.zip
When it is done (you will get OKAY. finished in the command prompt) Type: fastboot reboot-bootloader
Then choose recovery and you should be getting CWM recovery. From there you know what to do
Hope it helps!

glevitan said:
ToffeeArab, red triangle is stock recovery. That means that you have to flash CWM again from fastboot. Do the following:
Hope it helps!
Click to expand...
Click to collapse
Done all that and seems to be doing something. I have OKAY in the command prompt but the DHD is sitting wit the silver HTC and the green progress bar, but it has stopped at bout 80% of the way and is now not moving. Call me a coward (LOL) but I'm too scared to switch it off !!!!
PS - been trying to fix this for over 24 hours and I am grateful for the help.

Ignore last one.
Missed the last command ! NOOB ALERT
Seems to be running now and trying ICS

ToffeeArab said:
Ignore last one.
Missed the last command ! NOOB ALERT
Seems to be running now and trying ICS
Click to expand...
Click to collapse
Don´t worry in the Hack Kit IRC channel we have this saying: "...GREEN BAR IS LIKE TITS ON A SNAKE: INTERESTING BUT USELESS..."
The green bar usually gets stuck in that percentage. Just reboot bootloader and you will be ok..:cyclops:

:good::good::good::good::good::good::good:
All working now with ICS on.
You have done in 20 minutes what I tried on over 24 hours.
Very much appreciated.
Glenvitan - name a charity and I'll make a donation or if you take paypal for your ongoing work let me know.

ToffeeArab said:
:good::good::good::good::good::good::good:
All working now with ICS on.
You have done in 20 minutes what I tried on over 24 hours.
Very much appreciated.
Glenvitan - name a charity and I'll make a donation or if you take paypal for your ongoing work let me know.
Click to expand...
Click to collapse
Thanks man, but donation is not necessary. I appreciate it. Glad you are working again. :laugh:

glevitan said:
Thanks man, but donation is not necessary. I appreciate it. Glad you are working again. :laugh:
Click to expand...
Click to collapse
The wife also says thanks. Apparently I've not been great company today with my head stuck to my monitors !!

ToffeeArab said:
The wife also says thanks. Apparently I've not been great company today with my head stuck to my monitors !!
Click to expand...
Click to collapse
Press his thanks button.
EDIT: haha, I see that you have.

Same issue, INFOsignature checking fail
I'm having the same issues with the red triangle, but I can't get past the flash step.
c:\aahk-11092012>fastboot flash zip cwm-5.0.2.7-ace.zip
sending 'zip' (3643 KB)... OKAY [ 0.621s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.085s
If anyone could assist me with this, I would greatly appreciate it.

fobgoblin said:
I'm having the same issues with the red triangle, but I can't get past the flash step.
c:\aahk-11092012>fastboot flash zip cwm-5.0.2.7-ace.zip
sending 'zip' (3643 KB)... OKAY [ 0.621s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.085s
If anyone could assist me with this, I would greatly appreciate it.
Click to expand...
Click to collapse
Red triangle is stock recovery. Unless you have unlocked the bootloader you can not flash a partition such as recovery.
I am assuming that you are S-ON
Sent from my GT-N7000 using xda app-developers app

[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] Updating Advise

Hi had my one x for a while now brought it already rooted but think its time to update it so looking for advise how to go about it ive not done it before on android but can follow instructions below is what its running now from what i can see would need kernel and rom update but want to make sure i do it right thinking of cm-11
Android Version 4.2.1
Baseband version 2.1204.135.20
Kernel version 2.6.39.4-g91b0976
[email protected] #2012122917
sat dec29 16:19:23cwt 2012
Build Number
tg-endeavoru-userdebug 4.2.1 JOP40D
eng.adrian.20130113.165459 test-keys

Get the outcome of :
Fastboot getvar all
And post the outcome here and delete the SERIAL NUMBER & IMEI

Mr Hofs said:
Get the outcome of :
Fastboot getvar all
And post the outcome here and delete the SERIAL NUMBER & IMEI
Click to expand...
Click to collapse
Right think ive found what you asking for
c:\adb>fastboot getvar all
INFOversion: 0.5a
INFOversion-bootloader: 1.12.0000
INFOversion-baseband: 2.1204.135.20
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.17.401.2
INFOserialno:
INFOimei:
INFOproduct: endeavoru
INFOplatform: HBOOT-T30S
INFOmodelid: PJ4610000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 3778mV
INFOdevpower: 55
INFOpartition-layout: None
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: None
INFOhbootpreupdate: 2
INFOgencheckpt: 0
all: Done!
finished. total time: 0.826s

Oke, this is a ruu that flashes the phone back to factory stock. So all stuff will be gone so backup what you want/need
Make sure the bootloader is relocked :
Fastboot oem lock
Then keep the phone in the bootloader and execute the ruu.exe with admin rights on the pc !
http://www.androidruu.com/getdownlo...Radio_5.1204.162.29_release_302015_signed.exe
When the ruu is done you check inside the settings menu manually for software updates and apply all updates you can get. The last one is android 4.2.2 sense 5.

right ive tried the above locked boot loader and run ruu it geets as far as signature update then get error 132 signarure error and under says please get the correct rom update and try againand now phone stuck in boot loader cant boot down to allow charge so what next thanks

Oke run this one instead
http://www.persianhtc.net/index.php...Radio_2.1204.135.20_release_274900_signed.exe

Ok will do will get back to you after thanks for the help at least i learning as i go lol

ok that one worked its booting up now

Oke then try the 3.14 once more if you dont get official ota's

There was a small update that worked with a larger one next but as battery low will try that one tomoz and let you no how its coming on any way of to bed thanks for helping hopefully get some more done tomoz

Niice, I will keep an eye out

Ok updates all done unlocked boot loader and switched usb debugging back on in Developer options
whats next to do

Edit :
You want CM 11 on the device ?

Mr Hofs said:
Edit :
You want CM 11 on the device ?
Click to expand...
Click to collapse
I installed that file link you gave was thinking of cm11 or viperx have downloaded viperX_4.0.7 and pulled out the boot image so at moment have a folder on desktop with zip viperx_4.0.7 and the boot image beside it
then found these instructions
1 Make sure your that your HBOOT is 1.31 or greater
2 Check if you CID is supported, visit http://forum.xda-developers.com/show....php?t=1957376 for updates. Cheers Mike
3 Unlock your bootloader via HTCDev and install a custom recovery.
4 Download the ROM and place it on your virtual SD card.
5 Do a nandroid backup!
6 Extract boot.img from ROM zip and flash it using ‘fastboot flash boot boot.img’.
7 Use 'fastboot erase cache' to avoid boot issues.
8 Go into recovery and install the ROM.
9 Please choose fullwipe if you are asked, highly recommended if you go from one rom from another rom.
10 Reboot the device and enjoy!
1 my hboot is 1.72.0000
2 ? i no my CID is HTC_001 according to CID Getter dont no what that means ?
3 this done and custom recovery you gave in and when click on recovery it comes up so tha all works
4 have it on pc at moment but do no how to stick it on phone sd
5 Do What lol
And not dared to do rest with out getting support first dont want to brick my phone

DevilsDonut said:
I installed that file link you gave was thinking of cm11 or viperx have downloaded viperX_4.0.7 and pulled out the boot image so at moment have a folder on desktop with zip viperx_4.0.7 and the boot image beside it
then found these instructions
1 Make sure your that your HBOOT is 1.31 or greater
2 Check if you CID is supported, visit http://forum.xda-developers.com/show....php?t=1957376 for updates. Cheers Mike
3 Unlock your bootloader via HTCDev and install a custom recovery.
4 Download the ROM and place it on your virtual SD card.
5 Do a nandroid backup!
6 Extract boot.img from ROM zip and flash it using ‘fastboot flash boot boot.img’.
7 Use 'fastboot erase cache' to avoid boot issues.
8 Go into recovery and install the ROM.
9 Please choose fullwipe if you are asked, highly recommended if you go from one rom from another rom.
10 Reboot the device and enjoy!
1 my hboot is 1.72.0000
2 ? i no my CID is HTC_001 according to CID Getter dont no what that means ?
3 this done and custom recovery you gave in and when click on recovery it comes up so tha all works
4 have it on pc at moment but do no how to stick it on phone sd
5 Do What lol
And not dared to do rest with out getting support first dont want to brick my phone
Click to expand...
Click to collapse
1: OKE
2: Not important (skip this)
3: Make sure you flash this recovery https://www.dropbox.com/s/yqzlpqo8illa53j/Philz recovery 5.15.9.img
rename it to recovery.img and flash it :
fastboot flash recovery recovery.img
fastboot erase cache
4: i write this at a later point
5: Enter the recovery and tap the "Backup & restore"menu and make a backup (let it run and when finished you go to my new steps)
NEW STEPS :
1: tap the mounts & storage menu - mount USB storage (then wait until it pops up on the pc, can take minutes so give it time)
2: copy the rom.zip to the sdcard
3: tap power options - reboot to bootloader
4: flash the boot.img from the viper x rom.zip :
fastboot flash boot boot.img
fastboot erase cache
5: unhook the usb cable and enter the recovery
6: make a full wipe :
factory reset
wipe cache partition
advanced - wipe dalvik cache
mounts & storage - format cache, data and system (do NOT press sdcard)
then install zip from sdcard - choose zip from sdcard and install the viper x rom.zip. The aroma installer pops up and you choose no wipe and a full rom install......reboot and done

do i chose install without wiping or perform a full wipe
Mr Hofs said:
1: OKE
2: Not important (skip this)
3: Make sure you flash this recovery https://www.dropbox.com/s/yqzlpqo8illa53j/Philz recovery 5.15.9.img
rename it to recovery.img and flash it :
fastboot flash recovery recovery.img
fastboot erase cache
4: i write this at a later point
5: Enter the recovery and tap the "Backup & restore"menu and make a backup (let it run and when finished you go to my new steps)
NEW STEPS :
1: tap the mounts & storage menu - mount USB storage (then wait until it pops up on the pc, can take minutes so give it time)
2: copy the rom.zip to the sdcard
3: tap power options - reboot to bootloader
4: flash the boot.img from the viper x rom.zip :
fastboot flash boot boot.img
fastboot erase cache
5: unhook the usb cable and enter the recovery
6: make a full wipe :
factory reset
wipe cache partition
advanced - wipe dalvik cache
mounts & storage - format cache, data and system (do NOT press sdcard)
then install zip from sdcard - choose zip from sdcard and install the viper x rom.zip. The aroma installer pops up and you choose no wipe and a full rom install......reboot and done
Click to expand...
Click to collapse

Just to let you no I went with without wiping option and seems to be running ok
Sent from my HTC One X using Tapatalk

Nice....so i guess .....
CASE CLOSED !

Mr Hofs said:
Nice....so i guess .....
CASE CLOSED !
Click to expand...
Click to collapse
First of Thank you
So if i wanted to install another rom would i be just following the steps in the last post
BTW its done wonders for my phone before i was putting it on charge after 3/4 of hours use lasted much longer today and would discharge when plugged in and running waze also it not running like its sitting in the oven it was getting so hot just surfing web or using it for waze i could hardly touch the back of it today it only got warm when sun was beaming on it
So all in wish i got bottle to do it a year ago lol
And for anyone reading this looking at post times wondering why it took so long for me to reply each time its because i am dyslectic and have minor learning difficulty's so i was having to read over and over go watch youtube and learn every bit of the process worst is bit by next week i will have forgot how i did it and would have to start from the beginning so again Thank you Mr Hofs for your help i wouldent have done it with out your help

Nice words there mate, enjoy the phone !

[SOLVED] [Q] I'm not sure what's wrong

I've successfully rooted, and unlocked bootloader.
I can't seem to install any ROM. I've tried two CM11 Nightly versions, and the latest Beanstalk ROM.
I get a status 7 error.
I've tried:
editing the CM11 zip file to remove the "assert..." line of code.
using TWRP recovery
Nothing has worked.
I have Hboot 1.12
The only CWM recovery that I can use is version 5.8.4.0. If I use a newer version, whenever I boot into recovery, it's just a blank screen. (I've tried 6.0.4.5 and 6.0.4.8, neither came up with anything) I've downloaded them from different sources. So it's not a corrupt download.
TWRP recovery brings up the same status 7 error. It still comes up with an error if I remove edit the ROM zip file.
What am I doing wrong?

I just tried flashing the latest recovery again, and I got this:
C:\AndroidSDK\sdk\platform-tools>fastboot flash recovery recovery-clockwork-touc
h-6.0.4.8-evita.img
sending 'recovery' (8644 KB)...
OKAY [ 1.285s]
writing 'recovery'...
(bootloader) Format partition SOS done
FAILED (remote: (0000000a))
finished. total time: 1.504s
So I tried the non-touch version:
C:\AndroidSDK\sdk\platform-tools>fastboot flash recovery recovery-clockwork-6.0.
4.8-endeavoru.img
sending 'recovery' (8100 KB)...
OKAY [ 1.197s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.706s]
finished. total time: 1.903s
Waited a minute, then rebooted into recovery. It worked, but all I have are the instructions, minus the ability to do anything.
So it looks like the file attached.
EDIT: No idea what happened before, but booted back into recovery and the CWM recovery worked this time.
Going to try installing the ROMs now...froze on wiping data. So I rebooted, now CWM recovery is blank again.
For reference this is what it says on the bootloader page:
***UNLOCKED***
ENDEAVORU PVT SHIP S-ON RL
HBOOT - 1.12.0000
CPLD-None
MICROP-None
RADIO-2.1204.135.20
eMMC-bootmod: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Jun 28 2012, 11:31:28

Wait a minute....
I'm new to Custom ROMs, and I've only ever flashed a custom ROM on my Sony Phone, which used flashtool. So I'm quite new at this.
But do I flash boot.img before I install the ROM?

ldAbl said:
Wait a minute....
I'm new to Custom ROMs, and I've only ever flashed a custom ROM on my Sony Phone, which used flashtool. So I'm quite new at this.
But do I flash boot.img before I install the ROM?
Click to expand...
Click to collapse
first too low hboot, send the result from command fastboot getvar version-main

Thant said:
first too low hboot, send the result from command fastboot getvar version-main
Click to expand...
Click to collapse
I can't quite get that now. As I just tried to update the phone via the stock method, and now it's updating to Jelly Bean.
Will this update the Hboot as well?
I managed to get the CID as well, which is OPTUS001
And I was reading up on other people who have had this:
http://forum.xda-developers.com/showthread.php?t=2063425
http://forum.xda-developers.com/showthread.php?t=2054979
http://forum.xda-developers.com/showthread.php?t=2221171
http://forum.xda-developers.com/showthread.php?t=2156686

Signal drop
Hi, a few weeks ago, I tried ARHD 33.1 on my HTC ONE x international version, but i had signal drops. Some suggestions? Now I am using Maximus HD, and I'm not having that problem anymore. But the problem is that I want ARDH, it seems much better at battery life.

Andrew E. said:
Hi, a few weeks ago, I tried ARHD 33.1 on my HTC ONE x international version, but i had signal drops. Some suggestions? Now I am using Maximus HD, and I'm not having that problem anymore. But the problem is that I want ARDH, it seems much better at battery life.
Click to expand...
Click to collapse
are you flash the boot.img from rom archive?

Thant said:
first too low hboot, send the result from command fastboot getvar version-main
Click to expand...
Click to collapse
Code:
C:\AndroidSDK\sdk\platform-tools>fastboot getvar version-main
version-main: 2.17.980.6
finished. total time: 0.008s
I tried updating to JellyBean through the stock updater, but when it finishes downloading, it tells me to reboot so the install can start, I reboot, but it boots into TWRP recovery. I think it's trying to boot into the stock recovery. How do I restore the stock recovery, or solve this problem?
Solved it. Followed the instructions here on Android Authority. (can't post link)
Now h-boot is version 1.36, hopefully this is high enough to install custom ROM.
I can now go into the latest version of CWM, but... I forgot to enable USB debugging...
Now I think I'm bricked. I actually made a nandroid backup before wiping the data, but it seems to have disappeared.
Is there anyway that I can fix this?
UPDATE:
I flashed the latest version of TWRP, and then mounted USB storage. I then moved the roms onto the device.
For some reason, I couldn't mount the SDcard through CWM, only through TWRP. I read that you can also use Phil's recovery. I also pasted the nandroid backup I had made at the very beginning. Flashed latest version of CWM, and boot.img again, just in case.
Then installed PACman ROM, and GAPPS. It's working now.
Thread solved.

Thant said:
are you flash the boot.img from rom archive?
Click to expand...
Click to collapse
yup