[Q] Red Triangle after Ace Hack Kit install. - Desire HD Q&A, Help & Troubleshooting

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

Related

[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] 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] No boot

My dad got a HTC Incredible from ebay and it will not boot. It is stuck in bootloop if I try to just boot it normally. I can get into HBoot, S-on. HBoot version is 1.02.000. Recovery does not work from here. It just goes into bootloop. I've tried flashing various images with hboot as well as using RUU. RUU always gives me a error of 140.
Anyone have any idea of what I need to do?
benpfeil said:
My dad got a HTC Incredible from ebay and it will not boot. It is stuck in bootloop if I try to just boot it normally. I can get into HBoot, S-on. HBoot version is 1.02.000. Recovery does not work from here. It just goes into bootloop. I've tried flashing various images with hboot as well as using RUU. RUU always gives me a error of 140.
Anyone have any idea of what I need to do?
Click to expand...
Click to collapse
You need to unlock the bootloader with the htcdev site unless its already unlocked, and then fastboot flash cwm recovery img.
When I go to the HTCdev site and select the phone then "Begin Unlock Bootloader" nothing happens. I'm assuming it will download an exe or something?
I am able to get the token for the phone through fastboot but I can't seem to get the site to progress past the main screen.
Edit - For some reason Chrome would not work on the site. I had to move to IE to get the process to work.
I was able to flash clockwork recovery but now when I choose to boot into recovery I just see the white HTC Incredible screen.
benpfeil said:
I was able to flash clockwork recovery but now when I choose to boot into recovery I just see the white HTC Incredible screen.
Click to expand...
Click to collapse
Hmm so your unlocked now and can use extended fastboot commands, that may come in handy. What android version and radio version is the phone on?
This is what I can see in HBoot.
***UNLOCKED***
INCREDIBLE XC SHIP S-ON
HBOOT 1.02.0000
MICROP-0417
TOUCH PANEL-ATMEL224_15ab
RADIO-2.15.10.07.07
DEC 21 2011, 23:37:16
Does that help?
benpfeil said:
This is what I can see in HBoot.
***UNLOCKED***
INCREDIBLE XC SHIP S-ON
HBOOT 1.02.0000
MICROP-0417
TOUCH PANEL-ATMEL224_15ab
RADIO-2.15.10.07.07
DEC 21 2011, 23:37:16
Does that help?
Click to expand...
Click to collapse
Yes it does. Ok follow this guide http://forum.xda-developers.com/showthread.php?t=1506258 starting at number 28 and going till the last step.
Sent from my ADR6300 using xda premium
How can I do that when I can't get the device into usb debug mode?
benpfeil said:
How can I do that when I can't get the device into usb debug mode?
Click to expand...
Click to collapse
Crap your right. Ok there is another way here is where fastboot comes in handy.
Download this file http://dinc.does-it.net/Guide_Root_New_Hboot/mtd0.img, and place it on your pc in the same folder as fastboot.exe, the same place you put the unlock_code.bin file. Boot to hboot with the phone connected to the pc, and open a command promt to where the files are. Then type without quotes "fastboot flash misc mtd0.img".
Sent from my ADR6300 using xda premium
C:\Android>fastboot flash misc mtd0.img
sending 'misc' (640 KB)... OKAY [ 0.102s]
writing 'misc'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.216s
No luck
benpfeil said:
C:\Android>fastboot flash misc mtd0.img
sending 'misc' (640 KB)... OKAY [ 0.102s]
writing 'misc'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.216s
No luck
Click to expand...
Click to collapse
Damn. I was trying to get you s-off but im not sure how to do it in your situation other than adb and flashing the misc partition. We have pretty much run out of options. Ruu dosent work, cwm dosent work, you vant flash misc, Let me think some more and i will get back to you.
Sent from my ADR6300 using xda premium
Sounds good. Thanks for all your help so far.
benpfeil said:
Sounds good. Thanks for all your help so far.
Click to expand...
Click to collapse
Ok try this download this http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip, rename it update.zip and place it on your pc in the same folder as fastboot.exe. Then open a cmd prompt and type without quotes "fastboot update update.zip". If it works, see if you can boot.
Really weird error from fastboot.
benpfeil said:
Really weird error from fastboot.
Click to expand...
Click to collapse
That is weird, never seen anything like that before. It seems nothing is working to get the phone going, mabey it has some sort of hardware failure.

[Q] Idiot With HTC one X stuck in boot loop.

Hello,
I’ve been following guides to root my phone and put a custom ROM onto it. I had no experience in doing this so I thought I would follow an idiots guide and was stupid enough not to back up the original ROM along with not reading up properly on what I was about to do… (yes you can call me names I shall accept it)
The problem I'm having is after putting the custom ROM which was ViperX3.2.0 The phone just stays stuck on the HTC one Tm with beats audio and keeps resetting it self, anyway i can fix it? or have i bricked it.
I'm a complete noobie cause I've been looking around for the past 3 days and still can't find anything (or something I can understand) :angel:
- I've wiped cache, dalvik cache and battery stats
- I go to recovery and click mount sd card nothing happens mount usb storage nothing happens.
- I don't understand next to nothing, need like android for idiots. :good:
- When phones booting up my computer recognises something but has not drivers and fails (But i had drivers and could transfer stuff too and from)
So if you can help i will love you forever
Many Thanks
RIch
I'm going to quote the instructions on the ViperX page. Have you even followed these steps?
Code:
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/showthread.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!
Did you flash the boot.img file in fastboot? fastboot flash boot boot.img followed by fastboot erase cache
tomascus said:
I'm going to quote the instructions on the ViperX page. Have you even followed these steps?
Code:
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/showthread.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!
Click to expand...
Click to collapse
Like I Said I was stupid enough not to follow instruction, where to start. First my Hboot is not 1.31 but 1.12 or somthing. No clue what CID is Trust an idiot like me to do something like this HA.
I never did a nandroid backup, I'm hitting myself for that one quite badly
Apart from that i did everything else HA yes i did do fastboot boot boot.img folowed by somthing to do with cache
Richlilrich said:
Like I Said I was stupid enough not to follow instruction, where to start. First my Hboot is not 1.31 but 1.12 or somthing. No clue what CID is Trust an idiot like me to do something like this HA.
I never did a nandroid backup, I'm hitting myself for that one quite badly
Apart from that i did everything else HA yes i did do fastboot boot boot.img folowed by somthing to do with cache
Click to expand...
Click to collapse
Okay, in fastboot mode, type 'fastboot getvar cidnum' to get your CID number.
then according to that number, go here: http://forum.xda-developers.com/showthread.php?t=1957376
and download your firmware.zip
then use the following commands:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip
tomascus said:
Okay, in fastboot mode, type 'fastboot getvar cidnum' to get your CID number.
then according to that number, go here: http://forum.xda-developers.com/showthread.php?t=1957376
and download your firmware.zip
then use the following commands:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Ahh, i've done what you just said it looks like i'm getting somewhere.
looks like i'm stuck on this one.
C:\fastboot>fastboot flash zip 3.16.61.6.zip
sending 'zip' (12875 KB)...
OKAY [ 1.786s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 5.130s
Just keep trying 'fastboot flash zip (lalala)' until it works.
Afterwards, you need to re-unlock your bootloader with 'fastboot flash unlocktoken unlock_code.bin'
then reflash boot.img 'fastboot flash boot boot.img'
then 'fastboot erase cache'
then reflash recovery 'fastboot flash recovery (lalalaa.img)'
tomascus said:
Just keep trying 'fastboot flash zip (lalala)' until it works.
Afterwards, you need to re-unlock your bootloader with 'fastboot flash unlocktoken unlock_code.bin'
then reflash boot.img 'fastboot flash boot boot.img'
then 'fastboot erase cache'
then reflash recovery 'fastboot flash recovery (lalalaa.img)'
Click to expand...
Click to collapse
I feel bad, wasting your time still. CMD has froze should i cancel ctrl +c? so i apologise in advance
C:\fastboot>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.008s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
also 0kb?
-EDIT-
DONE IT! However i don't have no signal and can't connect to wifi? did i miss a step?
also i would love the opportunity to learn about this stuff starting from the basics, any advice on some reading i should do? i know it's a cheeky question but it's a must I think LOL
But thank you for your time.
Rich
Richlilrich said:
I feel bad, wasting your time still. CMD has froze should i cancel ctrl +c? so i apologise in advance
C:\fastboot>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.008s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
also 0kb?
-EDIT-
DONE IT! However i don't have no signal and can't connect to wifi? did i miss a step?
also i would love the opportunity to learn about this stuff starting from the basics, any advice on some reading i should do? i know it's a cheeky question but it's a must I think LOL
But thank you for your time.
Rich
Click to expand...
Click to collapse
I'm happy for you.
Man, just search and you shall find
Try reflash boot.IMG or if it doesn't work- Full wipe and reflash ROM.
Sent from my HTC One X using xda app-developers app
tomascus said:
I'm happy for you.
Man, just search and you shall find
Try reflash boot.IMG or if it doesn't work- Full wipe and reflash ROM.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Whoopsie, did fastboot flash boot boot.img didn't start up so i thought i would check recovery and earse some caches, theres an error for it to load. (a phone laying down with an exclaimation mark) so i can't do a wipe
Reflash the custom recovery
Fastboot flash recovery recover.img
Fastboot erase cache
Anyway to get the recovery back? so i can try another ROM to see if that could possibly fix the problem, just can't get into recovery D: happy my phone turns on lol however no network or can't connect to wifi
by fashing the boot did nothing but crash it more.
so i had to redo what you taught me, thank you again and i'm back to where i said i was
Flash this one again
http://db.tt/Krlm4dPs
Fastboot flash recovery recovery.img
Rename the downloaded file to recovery.img before you flash !
Mr Hofs said:
Flash this one again
http://db.tt/Krlm4dPs
Fastboot flash recovery recovery.img
Rename the downloaded file to recovery.img before you flash !
Click to expand...
Click to collapse
Many thanks, recovery up and running. now that I know this I'll try to reinstall the ROM.
Are there any reasons why I'm not getting signal or WiFi? along with that from the unlock it seem rather slow,
But I guess it's time for me to experiment, now that i know how to fix it if I mess up
Maybe because of this :
When installing the viper you get a question about the custom kernel ....
Answer with NO !
Mr Hofs said:
Maybe because of this :
When installing the viper you get a question about the custom kernel ....
Answer with NO !
Click to expand...
Click to collapse
I am sure I have done that a few times, going to try re downloading and try to reinstall. May not be installing right,
Thanks
Just signed up to say thanks Mr Hofs for the help you've posted in this thread in particular but also in many other threads I've been referring to over the last 4 hours or so. I was well on my way to brickage following a screwed up attempt to root my HOX, but thanks to you I'm now up and running again. Admittedly I'm back at square one with a non-rooted handset, but I never would've believed that would be such a happy place to be, plus I feel a tiny bit less of a noob now.
Anyway, apologies for crashing your thread Richlilrich - as you were!
Screwed up my One X
tomascus said:
Okay, in fastboot mode, type 'fastboot getvar cidnum' to get your CID number.
then according to that number, go here: http://forum.xda-developers.com/showthread.php?t=1957376
and download your firmware.zip
then use the following commands:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Hey Guy's,
I know this thread is old and many of you might not see this anymore but I'm sure this is where I need to be.
I have a UK Quad Core HOX and rooted fine a while ago.
I placed Cyanogen on for a while and all was running fine but it doesn't have all the tweaks I'd like so looked around for another ROM.
I came across the ViperROM and thought - Great! Exactly what I wanted, checked the reviews - All good, checked my HBoot etc... All seems fine. Went ahead and installed it through CWM (5.8.4.0) like I have done a thousand times before and went and rewrote the boot.img and got a continuous HTC boot loop. Thought hey no harm no fuss and went back into recovery to restore my most recent back-up only to find that they had all gone - My stock recovery my previous tries at other ROMS and most importantly my most recent Backup!!!!
I followed the steps above over and over again, I can re-lock my HOX, reboot into RUU and flash the 3.16.61.6 firmware (and boot img inside zip) and it still bootloop's over and over....... (I can unlock again too)
I've tried adb pushing Stock and custom ROMS to the SD card which says success in windows cmd but says no files on SDcard.
What am I doing wrong?
P.S hboot details are;
Endeveavoru PVT Ship S-ON RL
HBOOT-1.36.0000
CPLD-None
Microp-None
Radio-5.1204.163R.30
eMMC-Bootmode: disabled
CPU-bootmode: disabled
HW Secure boot:enabled
Modem path : off
Nov 16 2012, 18:32:39
Hope someone can help
---------- Post added at 07:29 PM ---------- Previous post was at 07:24 PM ----------
DrUmMiSt said:
Hey Guy's,
I know this thread is old and many of you might not see this anymore but I'm sure this is where I need to be.
I have a UK Quad Core HOX and rooted fine a while ago.
I placed Cyanogen on for a while and all was running fine but it doesn't have all the tweaks I'd like so looked around for another ROM.
I came across the ViperROM and thought - Great! Exactly what I wanted, checked the reviews - All good, checked my HBoot etc... All seems fine. Went ahead and installed it through CWM (5.8.4.0) like I have done a thousand times before and went and rewrote the boot.img and got a continuous HTC boot loop. Thought hey no harm no fuss and went back into recovery to restore my most recent back-up only to find that they had all gone - My stock recovery my previous tries at other ROMS and most importantly my most recent Backup!!!!
I followed the steps above over and over again, I can re-lock my HOX, reboot into RUU and flash the 3.16.61.6 firmware (and boot img inside zip) and it still bootloop's over and over....... (I can unlock again too)
I've tried adb pushing Stock and custom ROMS to the SD card which says success in windows cmd but says no files on SDcard.
What am I doing wrong?
P.S hboot details are;
Endeveavoru PVT Ship S-ON RL
HBOOT-1.36.0000
CPLD-None
Microp-None
Radio-5.1204.163R.30
eMMC-Bootmode: disabled
CPU-bootmode: disabled
HW Secure boot:enabled
Modem path : off
Nov 16 2012, 18:32:39
Hope someone can help
Click to expand...
Click to collapse
Would like to add that I would prefer Viper to stock but stock would help for now
Before going for RUU and stuff, try any other roms.
I'd say do this :
Flash TWRP - Better than CWM anyday.
Go to recovery. Mount USB. Copy Viper (or any other) rom to phone.
Reboot to bootloader.
Flash boot.img.
Fastboot erase cache.
Go to recovery.
Clean install ROM.
Reboot and wait for it. First boot takes pretty long sometimes.
There is no better recovery, a recovery is personal. I'm using CWM now for 2 years....never had a problem with that.....
Now the issue.
How to copy it is in the post above, however before you install the rom you need to make a real good full wipe
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then install the rom...and ofcourse flash the boot.img from the rom.zip
The option to mount in CWM is under mounts and storage copy the rom.zip over and unmount.
The way i personally follow is :
Flash the boot.img (fastboot, bootloader mode) then enter the recovery and follow the above....make sure you unplug the usb cable BEFORE installing the rom.zip

[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...

Categories

Resources