[Q] Desire won't boot (now: Radio_v2 failure) - Desire Q&A, Help & Troubleshooting

[Q] Desire won't boot (now: Radio_v2 failure) - Desire Q&A, Help & Troubleshooting

Hi All,
Sorry another n00b making a n00b thread.
I bought a second hand desire very cheap under the understanding that "stopped booting one day" - so first thing first, if it is bricked, so be it.
Currently it only gets as far as the white HTC screen.
Now, when booting with PWR + Vol Down:
-Revolutionary-
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
RADIO-5.17.05.23
Obviously the PO has been playing around given the unlocked bootloader. I can get into fastboot fine. fastboot devices shows the Serial of the device.
So following the Troubleshooting guide here I attempted to flash a Recovery image as per recommendation. It shows sending and writing recovery.img OK, and the two progress bars display on the phone in line with that. However, when rebooting (fastboot oem gencheckpt), I still can't get into recovery - it goes back to the HTC screen again. Same with fastboot reboot-bootloader if it matters.
***EDIT - kept looking on this forum and it seems as if this bootloader would be write protected against RUU updates? So you can probably disregard what was here. I'll keep looking around, but if anyone has advice feel free!
If I'm missing something silly here, feel free to abuse me while you tell me what it is. Just thought I'd check to see if I'm on the right track or I've failed miserably.
Thanks.

Download the HBOOT downgrader from alpharev.nl (and the stock HBOOT, too).
Flash the
1. stock HBOOT,
2. the downgrader
3. then the RUU of your choice (2.3.3/2.2 depends on you).
As you said, you can get to fastboot, it'll work.
You'll get a stock, unrooted device, but you can root it later on.

davebugyi said:
Download the HBOOT downgrader from alpharev.nl(and the stock HBOOT, too).
Flash the
1. stock HBOOT,
2. the downgrader
3. then the RUU of your choice (2.3.3/2.2 depends on you).
As you said, you can get to fastboot, it'll work.
You'll get a stock, unrooted device, but you can root it later on.
Click to expand...
Click to collapse
Thanks for that - I flashed these in this order from fastboot and then rebooted - I can see that it has taken effect due to seeing "AlphaRev Unlock" now, however, can't get the RUU to go - gets to Rebooting to bootloader, phone reboots and gets stuck in a bootloop (I suppose - HTC screen, black screen, and so on). Eventually it gives up and gives [171] USB CONNECTION ERROR. "Reboot Bootloader" from the fastboot menu does the same thing.
I actually have an Atrix so this is not my daily driver, so nothing too urgent, or in fact tragic if it is a hardware issue. I do appreciate any help though all the same!

Hmm - can be the cable, the drivers.
Even some people said, that using win7 64Bit will get you this error.
I'd check first the drivers. Maybe you have USB Brick as well - search the Dev Thread for a fix - basically 2 commands.

I was just reading up on the USB brick actually, as you say doesn't seem like too much effort anyway.
I am using Win 7 x64 in fact... I will copy all the necessaries to a USB stick and use a WinXP box at work just to make sure. Thanks again!

OK, update -
Same result on a WinXP machine trying to flash via RUU.
When I try fastboot oem enableqxdm 0, I get:
partition_read::Too many bad blocks(out of range)
It does say OK after that though?
If I try to flash a mtd0.img via fastboot (I assume I can't use an SD card given I can't boot) with SuperCID as the CID (either hex edited or with the script) I get:
sending 'misc' (640KB) OKAY
writing 'misc' (640KB) ... FAILED (remote: image update error)
It's late here so I'll search more in the morning, but any guidance would be appreciated.

Should I be erasing the misc partition before attempting to flash mtd0.img? If that's where I've gone wrong I'll kick myself, but thought I should confirm before I break the phone more.
Update:
I grabbed the rom.zip from the temp folder, renamed it to PB99IMG put it on a MicroSD and let the phone do its thing. It worked, in that it performed the update, but Radio_v2 failed - so I assume this means either I have a branded handset that has nothing on the outside (how do I check?) or there is a hardware fault?
Of course, I have S-ON now because everything else worked...

radio failure means you're kinda fu*cked IMO... I mean I know a user who kept trying a RUU who eventually undid the radio fail but ermm.. yeah usually it means a real brick

I figured that might be the case. Given the bootloader was already unlocked when I received the phone, one can assume the previous owner actually knew what they were doing and had already tried to fix it and come to the same conclusion.
I'll update the thread if I manage to fix it, but if anyone else stumbles across this due to similar circumstances, looks like you have your answer.
PS: bortak your troubleshooting thread was an amazing help.
Thanks to all!

yeah just try the RUU a couple of times (like 10 or something) and see what happens.. if you're lucky you might get a break..
or what you could do is flash the 2.3.3 RUU, hope it works, and if you do get stuck in splash HTC will cover you warranty!! just tell them you try to upgrade and it broke!

Related

[Solved] Help: HTC Desire U.S Cellular Hboot 6.93.9999 Black Screen

I am in really desperate need of help! I know many see me as a noob and a new user or whatnot but I just had a major accident with my HTC Desire with U.S Cellular. The phone is about 14 months old now but it is working like new still because I take good physical care of it.
Anyways, today I wanted to install a new Rom with Sense 3.0 from my current 2.2 Froyo from RUU. The Thread for the rom I wanted said that the CM7 r2 partition table was recommended and so I went on following the aplharev site were I had to download the CM7 r2 hboot.img (I already had S-Off and Hboot 1.06.0000 with Root)
I went my way booting into Hboot and then Fastboot on my pc. I used Fastboot commander 1.51 and made the flash for the hboot using CM7 r2. This however, is when the problem resulted. After I flashed my Hboot from the previous 1.06.0000
to the new CM7 r2, my phone screen instantly Blacked out. It was as if it died. Then I figured it may be part of the partitioning, so I Deleted my cache, boot, and entire system (I figured that with a nandroid backup, I was invincible... I was very wrong...)
After everything started getting worse, I figured it was time to reverse back to my nandroid. I clicked the "Flash all/Restore Nand" button but instantly I was given:
STARTING FLASH OF NANDROID FILES.
Flashing "boot" - PLEASE WAIT.
"boot" flash FAILURE.
FLASH OF NANDROID FILES FAILURE - "BOOT" FAILURE.
This is were I knew I was... finished... I can't use my phone as the screen is pitch black, the system is deleted because of my "Genius" self, and because the screen is black as if turned off, I can't access the "Recovery" since I am blind of my actions. I tried looking and spending literally 5-6 hours searching forums, downloading, attempting, and of course, failing.
The only thing I CAN ACCESS is Fastboot. When I power my phone, it vibrates with a dead black screen. If i power on with Volume down following power button again, I can access fastboot on my PC.
If anyone out there with a good heart can help me, that would be the best thing ever for me! I feel soo depressed now because this is my everyday phone and now... I am phoneless... The sooner I get help, the better. I need to know the possibilities to fix this issue :0
Additional Info:
Operating system: Windows.
Tools folder found.
Windows fastboot tools found.
The folder containing the IMG files was not found.
Nandroid folder found.
Nandroid "boot" file found.
Nandroid "data" file found.
Nandroid "system" file found.
All nandroid files set - Restore button enabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 6.93.9999.
Radio version: 2.15.00.11.16.
Main software version: 2.11.573.5.
cid: utsi_001.
cpld: none.
product: bravoc.
mid: pb9940000.
security: off.
build-mode: ship.

I think Alpharev meant to be for Bravo not Bravoc, flash downgrade reboot fastboot and flash RUU, hope this helps
Sent from my HTC Desire using XDA Premium App

Alright. So how would that be in a step by step situation?
How do I flash the RUU? I'm sorry but I am still a noob learning

Jesus. Why do you cdma users keep doing this?
You're going to be lucky if you haven't bricked your device.
All you can really do is see if you can ruu. Of course, the Rom won't fit in the cm7 so you're going to have to hope your ruu's hboot will be a higher version. If not you'll have to flash the downgrade image first.
Best of luck
Sent from my HTC Desire using Tapatalk

Ok then. I have downloaded the HTC 2.2 Froyo RUU from U.S Cellular linked by HTC website but now how do I flash it? It is an exe file. I am still trying to understand how to do all this :0 I am really sorry for annoying anyone

It runs from a windows pc. Put your phone in Fastboot (from off hold back and press power) connect usb and run ruu
Sent from my HTC Desire using Tapatalk

Alright. I powered on phone into Hboot then fastboot (Windows 7 makes the USB detection sound when fastboot is detected). I am still blind since the black screen shows no image. Anyways, I started off running the "HTC Desire Froyo 2.11.573" RUU that I downloaded from HTC/U.S Cellular website (171Mb) and then I clicked the "Next" screen following up by another "Next" and then the big rectangular box saying "Verifying Information on your Android phone. Please wait..." but after about 30 seconds I get a error:
"ERROR [170]: USB CONNECTION ERROR
This error message will appear when the Android phone is not correctly connected to the host PC. It might be a USB connection problem or a PC USB driver problem. Make sure the Android phone is connected to the host PC correctly and/or check if the PC driver matches the Android phone."
I have Fastboot Commander V.1.51 running and it detects usb just fine as I can display the system info with it, so I don't see how the RUU is not finding the Desire under Fastboot.
So then I flashed the hboot with the "bravo_downgrade.img" from AplhaRev website
like you guys stated and then re approached the situation with the same process. Still keep getting the errors of "ERROR [170]: USB CONNECTION ERROR"
I don't know what to do now... Any additional advice? Am I on the right track? Maybe I'm missing something? If all goes or seems worse, I do have a school friend with the SAME HTC Desire CDMA with U.S Cellular carrier like me. He is updated with Froyo 2.2 and his phone works just as fine as mine once did before my idiot self caused this mess. He however, has no root nor S-Off.
So what can I do now? Gold card attempt maybe? I have not read anything about this but I only heard that it helps recover "bricked" Desire that is SLCD. Another slight problem, I don't know if my Desire is SLCD or not... I know only that it is CDMA *I know, frustrating dealing with a noob like me*.
It sucks not having a phone. 1 day already. I can only have patience until I finally fix my phone with the help of a good heart.

Power to fastboot power and back button..
Will fastboot recognize your phone?
Fastboot devices
If you get long number that is a good sign
You must run RUU or any fastboot command while you are in fastboot mode, not hboot
Should be long number
Sent from my HTC Desire using XDA Premium App

Ok still no go. I ran what you said "fastboot devices" using Fastboot Commander V.1.51 and got the following:
-----------------------------------.
Running fastboot command - PLEASE WAIT.
###Calling fastboot with: devices###
HT0BTHM01381 fastboot
********************************
After I got this, I ran the RUU again, and still getting "ERROR [170]: USB CONNECTION ERROR"

fastboot see your device that is good
extract rom.zip from ruu (see video in step 7 of bortak guide)
then
1 fastboot oem rebootRUU
2 fastboot devices - if you see your htxxxxxxxxxxxx no. then go to step 4
3 if not pull battery out anf boot to fastboot and start from step 1 again
4 fastboot flash zip rom.zip
5 fastboot reboot-bootloader

Alright then. Sorry for late reply. I had an intense amount of much school work to get done from Calculus and other major subjects but I managed to follow your directions and the RUU just won't detect the darn phone! Keep getting USB Error not stop. So I decided to use my brain.
I extracted the ROM from RUU in the "%TEMP%" folder and kept it in "MY Documents". After, I took a deeper look into the Rom using Winrar, and found this file "hboot_8x50_1.06.0000.img". I wondered... Hm.... What if I extract it from Rom, and flash it into my current 6.93.9999 Hboot? So I did.
After, the minute It was flashed, WOLA! I have a working SCREEN AGAIN! I can SEE! Now however, a few things have changed.
SPL/hboot version: 1.06.0000.
Radio version: 2.15.00.11.16.
Main software version: 2.11.573.5.
cid: utsi_001.
cpld: none.
product: bravoc.
mid: pb9940000.
security: on.
build-mode: ship.
My S-ON is back and I have no boot screen what so ever. EX: If I power off phone and back on, it INSTANTLY goes into hboot screen. Doesn't even bother with an "HTC LOGO". *May be because I deleted all the partitions of boot, system, ect.
Moving on, tried running RUU again. Not a single working method! USB ERROR.
Then I tried flashing the "rom.zip" extracted from the RUU using Fastboot Commander but after about 1 minute I get this:
********************************
###Calling fastboot with: flash zip C:\Users\Jona\Downloads\HTC Desire Froyo 2.11.573 ROM\PB99IMG.zip###
sending 'zip' (167226 KB)... OKAY [ 28.390s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: not allowed)
finished. total time: 53.580s
********************************
Any idea's what to approach next? I am SUPER happy I can see my screen again, but I must repair what is broken first. Should I take action to "S-OFF" again?
I am trying to think now and here is what I suppose I should/can do.
S-Off then somehow flash Clockwork Mod into Recovery and then from there, Flash back my Nanodroid through Recovery. Would that work? What do you all think?

Why did you flash hboot only? Whole rom flashing via pb99img method not working?
For s-off you need system booted, you can't s-off from fastboot/hboot. Youre booting there because no boot and recovery been flashed. Try to flash it with goldcard via pb99img zip in root of your sdcard?
Sent from my HTC Desire using XDA Premium App

Aww man really? I totally forgot about that... I tried copying the pb99.img on my SD card and now that I can see, attempted waiting in hboot for the files to load but after they did, I't quickly should something like "SD Checking: PB99DIAG.zip"
But then it said
No image file.....
No image file.....
No image file.....
And it returned to hboot.
At this point, I started losing hope. I wanted to cry... What could I do?! No phone for 3 days.... I was a failure...
But then, only then, I took a break and powered off phone. Looked around my shallow apartment and thought, what now...
5 minutes I returned to the phone, took SD card out, blew on it, inserted it back in my Desire, and powered on into Hboot, waited again for the *Miracle* to happen, and WALA! It started loading the zip?!!! WHAT?! NO WAY! Heart pounding I eagerly stared at the phone. "Click Vol + Start Update" I clicked!
Then the 6 steps for updating appeared! 1 = OK 2 = OK
10 minutes later, I booted and back to normal From here, I can S-OFF, Get back Recovery ClockMod, and restore Nandroid. Thanks guys for assisting me well I have never been happier! I shall give you all Thumbs Up and close thread.
Out of curiosity, I should never bother to flash the Hboot EVER again correct? Only GSM phones can do this... So as a CDMA user, I should only flash roms under recovery and leave the hboot radio, recovery, and hboot alone?

Glad to hear that... Take this as warning you can flash anything what you want but only one condition: all stuff MUST be designed for Desire CDMA
Sent from my HTC Desire using XDA Premium App

Alright. I will just stay away from flashing Radio, Hboot. No reason to do so anyways :7 Thanks again!
Sent from my HTC Desire (CDMA)

Definitely as all radios and hboots are gsm and would usually brick your device. You've been very lucky
Sent from my HTC Desire using Tapatalk

I know. I am simply grateful and glad it is over. But hey, I learned soo much more about all this hboot and fastboot because of this. Good experience ^.^ Oh, one final noob Question. How to close the thread as solved? Using XDA Premium app
Sent from my HTC Desire (CDMA)

Jonicraw said:
I know. I am simply grateful and glad it is over. But hey, I learned soo much more about all this hboot and fastboot because of this. Good experience ^.^ Oh, one final noob Question. How to close the thread as solved? Using XDA Premium app
Sent from my HTC Desire (CDMA)
Click to expand...
Click to collapse
Leave it as it maybe somebody will learn from it
Sent from my HTC Desire using XDA Premium App

kotag82 said:
Leave it as it maybe somebody will learn from it
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
Yes, however, there is no harm in going to advanced edit on post one and putting [Solved] at the begining of the thread title

[Q] Trying to revert to stock, whats next?

After some success following the wiki, and Nipqers help, I was able to load a rom onto my new A7272 Desire Z. I bought the phone to use on AT&T's network in the US, but have unfortunately found out that I bought the wrong version. Luckily I can return/exchange the phone. So now I have been working to revert the phone back to stock, and of course I didn't back up the factory setup as I thought I was keeping it.
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC10*****)
MICROP-0425
RADIO-26.02.01.15_M2
I'm not great with ADB or DOS, but everything worked correctly on the install until the verify gfree step. Now that I'm reverting, I thought the gfree backup file should help me turn back S-ON, if only I could figure out how to push it with ADB. But then I thought maybe I should just run one of the OEM shipped ROMs, since I need all the software anyway, and that might turn S-ON as well. So I downloaded and ran...
RUU_Vision_HTC_WWE_1.82.405.1_R_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_168383_signed.exe
...Still not knowing for sure if that is even the correct shipped ROM for my A7272. I ordered a Desire Z, the phone body just says HTC, but when I first powered it on I thought I remembered seeing a splash screen with "Tmobile G2" pop up. Am I loading the wrong ROM?
When I did try run it, I kept getting an error 120 about phone power being too low, even though it's completely charged, or an error 170 about a bad connection. What am I doing wrong?
Or if I can't fix it, anyone want to trade an A7272 for a A7275
Any help would be greatly appreciated. Thanks.
Thanks!

Check my guide for returning to stock and unrooting http://forum.xda-developers.com/showthread.php?t=1442988
-Nipqer

Nipqer said:
Check my guide for returning to stock and unrooting http://forum.xda-developers.com/showthread.php?t=1442988
-Nipqer
Click to expand...
Click to collapse
Your guide does look a little easier, I will try it out tonight. Thanks again Nipqer!
UPDATE: Ok so I got stuck on section 2... phone is set to charge only default, downloaded fastboot and correct rom, put the windows exe and DZ_PC10IMG.zip in the same folder on my computer, ran the exe, put the phone in fastboot and it says "FASTBOOT USB" across the top. I opened a command prompt on my computer, pointed it at the folder with fastboot, but when I enter "fastboot-[OS] devices" while in that folder I get an error, "...is not recognized as an internal or external command, operable program, or batch file."
I'm sure I'm just missing something simple... I did also try renaming the file to "PC10IMG", and flashing via HBOOT. It scans and loads the file, but the phone doesn't change after install and reboot. It looks exactly the same (energy rom) as it did before.
Thanks again for the help!

Bump for me still being stuck
So where/how do I enter the "fastboot-[OS] devices" command?

replace os with windows, or mac, or linux
or depending on the title simply
fastboot devices
Sent from my HTC Vision using xda premium

Wow, I feel stupid for not realizing [OS] meant pick which one and type it Thanks for the help!
Unfortunately, I'm still stuck in Section 2...
When I run the rebootRUU command, DOS prompt says "...OKAY", but the phone just says on a black screen with and white HTC logo in the middle. Is that correct? On my previous phones the RUU screen was the screen with red/white/green/yellow color bars... just double checking, as it's still not working correctly.
It does start flashing/sending the zip, then fails, "FAILED (remote: 22 loading zip info fail)".
So I did try to flash it a second time as the instructions stated it would fail, but it fails again. Then upon restart nothing changed, still looking at the previous ROM.
Am I doing something wrong, or is there anything else I could try?

so your old phone was a g1, mt3g or something huh... i think your in the right place but ive never reverted back to stock. any reason you need to do this, dont all g2/dz phones that are unlocked have the proper cellular bands for att? i guess im not sure why it isnt running the update but im sure nipqer has an idea
Sent from my HTC Vision using xda premium

I'm throughly confused myself... I as well thought all the Desire Z's could do ATT 3g, which is why I bought the cheapest, new Desire Z that I could find, which ended up being a A7272. Then I found out that the A7272 can't do ATT 3g just EDGE ( as it only supports Tmobile 3g). Apparently I need a A7572 for ATT 3g, live and learn.
While I was figuring all that out, I unlocked, rooted, and flashed my favorite chef's Energy rom to the Desire Z via the Wiki. When it first booted up the phone there was a splash screen that said Tmobile and G2 on it, but I didn't think anything of it as I was flashing it anyway. The case only says HTC above the screen, no where does it say Tmobile, so I'm guessing it's a Desire Z that was flashed to G2 (even though I was told it was "new"). I didn't back it up and here I am trying to revert.
Anyway, when I try to flash the DZ_PC10IMG.zip, I get this...
C:\Users\Home\Desktop\fastboot>fastboot-windows flash zip DZ_PC10IMG.zip
sending 'zip' (288060 KB)... OKAY
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 22 loading zip info fail)
So I thought I'd try the G2 version, and when I try to flash G2_PC10IMG.zip, I get the same error, except that it's a "24" instead of a 22.
I can supposedly flash either one just fine with hboot and the sd card, but then nothing updates/is changed on the phone after I reboot out of hboot.
Radio is 26.02.01.15_m2
Any help is hugely appreciated, I'm ready to throw this thing at a wall.

I think that radio causes issues sometimes with trying to downgrade, you should flash a new radio from the radio thread and then try flash a stock rom again.
(I'd say go with the Vision_RADIO_12.28b.60.140e_26.03.02.24 radio)
-Nipqer

Nipqer said:
I think that radio causes issues sometimes with trying to downgrade, you should flash a new radio from the radio thread and then try flash a stock rom again.
(I'd say go with the Vision_RADIO_12.28b.60.140e_26.03.02.24 radio)
-Nipqer
Click to expand...
Click to collapse
You were absolutely right on both counts!!! I found and flashed that radio, and tried the DZ_PC10IMG one more time, well two more times, and it worked like a charm! That was the first time I've seen it work correctly, just awesome... You are a genius sir, and I won't call you Nipqer, as you noted it's not your name But thank you so much sir!
If can bother you with one last question... I tried pushing my part7 backup to turn S-ON, but nothing changed, I'm still S-OFF. When I tried to follow the instructions for not having that part7 back up, I'm not sure where I find the ORIGINAL_CID?

The command 'dd if=/dev/block/mmcblk0p17 bs=1 count=8 2>/dev/null; echo' will spit out an 8 character string, probably something like HTC__111.
That is your original cid.
-Nipqer

Nipqer said:
The command 'dd if=/dev/block/mmcblk0p17 bs=1 count=8 2>/dev/null; echo' will spit out an 8 character string, probably something like HTC__111.
That is your original cid.
-Nipqer
Click to expand...
Click to collapse
Unfortunately that does not happen when I enter that string... It just copies that same string to the next line, and then leaves me back at the shell prompt...

weird. you could try get it with fastboot, 'fastboot oem readbcid'
Though you probably need an eng hboot to use that command.
The phone is just an unbranded DZ from the states right? Just set the cid to HTC__001, pretty sure thats default for a US phone
-Nipqer

Bootloop, Recovery loop!!! ADB/FASTBOOT/HBOOT HELP!

Hey guys,
Here's the basic situation. I got this phone from a friend who knows nothing about flashing/rooting/etc. And yet he had flashed the phone with MUIU and ended in a bootloop. I fixed it for him. A month later my friend decided to flash it from Verizon to Frawg. Apparently a customer rep did the whole thing for him, long story short, it is stuck in a boot loop with the white HTC screen.
I figure the boot.img is corrupt. It also goes straight to a the white HTC screen loop whenever you select recovery or factory reset from HBOOT.
I have tried PB31IMG.zip flashing (multiple stock/recovery imgs/ROMS with no luck) - its S-ON btw.
I have tried fastboot adb which I am fairly knowledgable in, I know the environmental paths, and the drivers are correct, it all works with my other androids.
When flashing any ROM/recovery image/anything, I always get a failure message stating its missing signatures. This occurs when using fastboot recovery (path) commands to flash individual recovery images as well as the fastboot boot and fastboot update PB31IMG.zip commands.
I have tried to S-Off using HTCDEV method. But even when attempting the fastboot oem get_identifier_token I get a failure bootrom message <bootrom> [ERR] Command error!!!
RUU is no luck... even charged it says I have less than 30%battery error, when I get it to work after erasing cache on adb, it will say resetting bootloader, and once it has reset the phone, the phone ends up connecting via USB with a black screen as CDMA technologies to my pc. RUU then says USB has been disconnected. I can only access the USB driver while in HBOOT and FASTBOOT.
So basically the microsd flash method, adb flash method, and RUU are no goes at this point unless there's something I am doing wrong (I have been researching so many different forums, and discussions and have found a handful like my situation with no solution.
This is a last cry before I render my friends phone a paperweight. Thank you for anything! :good:
SPECS:::
INCREDIBLEC XC SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.07.07
JULY 23 2010,10:06:51

ragus15 said:
Hey guys,
Here's the basic situation. I got this phone from a friend who knows nothing about flashing/rooting/etc. And yet he had flashed the phone with MUIU and ended in a bootloop. I fixed it for him. A month later my friend decided to flash it from Verizon to Frawg. Apparently a customer rep did the whole thing for him, long story short, it is stuck in a boot loop with the white HTC screen.
I figure the boot.img is corrupt. It also goes straight to a the white HTC screen loop whenever you select recovery or factory reset from HBOOT.
I have tried PB31IMG.zip flashing (multiple stock/recovery imgs/ROMS with no luck) - its S-ON btw.
I have tried fastboot adb which I am fairly knowledgable in, I know the environmental paths, and the drivers are correct, it all works with my other androids.
When flashing any ROM/recovery image/anything, I always get a failure message stating its missing signatures. This occurs when using fastboot recovery (path) commands to flash individual recovery images as well as the fastboot boot and fastboot update PB31IMG.zip commands.
I have tried to S-Off using HTCDEV method. But even when attempting the fastboot oem get_identifier_token I get a failure bootrom message [ERR] Command error!!!
RUU is no luck... even charged it says I have less than 30%battery error, when I get it to work after erasing cache on adb, it will say resetting bootloader, and once it has reset the phone, the phone ends up connecting via USB with a black screen as CDMA technologies to my pc. RUU then says USB has been disconnected. I can only access the USB driver while in HBOOT and FASTBOOT.
So basically the microsd flash method, adb flash method, and RUU are no goes at this point unless there's something I am doing wrong (I have been researching so many different forums, and discussions and have found a handful like my situation with no solution.
This is a last cry before I render my friends phone a paperweight. Thank you for anything! :good:
SPECS:::
INCREDIBLEC XC SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.07.07
JULY 23 2010,10:06:51
Click to expand...
Click to collapse
Try this ruu its the newest officially signed ruu, so it will work with s-on. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip Place it on your sdcard in no folders and boot to hboot. It should find the file and prompt to press vol up to install. If it errors or dosent find it backup and format your sdcard fat32 with a pc and try again.
The reason the fastboot identifier dosent work is because you need to be on the 1.02 or 1.07 hboot to be able to unlock it. The ruu above will give you 1.07.
From there you can unlock the bootloader, fastboot flash recovery, and flash su thru recovery, then you will be rooted. Then if desired you can downgrade and get s-off.

I'm having a similar problem, but after using the PC-side RUU program, the PC reported the installation as failed while the phone hung on black screen with a full progress bar and 'htc', along with a single exclamation point at the end of the bar. When I unplugged the phone from the computer, it returned to the HBOOT screen where there were a number of phone elements and 'OK' in blue text, above a partition error and write failed message.
I did a battery pull to try the RUU's 'advanced recovery', and the phone now no longer boots.
I have no idea what shenanigans this is. No kernel screen, HBOOT is inaccessible, no charging light while plugged in, I've tried different SD cards and without any... I can't get it to respond at all.
Halp?

Trygon said:
I'm having a similar problem, but after using the PC-side RUU program, the PC reported the installation as failed while the phone hung on black screen with a full progress bar and 'htc', along with a single exclamation point at the end of the bar. When I unplugged the phone from the computer, it returned to the HBOOT screen where there were a number of phone elements and 'OK' in blue text, above a partition error and write failed message.
I did a battery pull to try the RUU's 'advanced recovery', and the phone now no longer boots.
I have no idea what shenanigans this is. No kernel screen, HBOOT is inaccessible, no charging light while plugged in, I've tried different SD cards and without any... I can't get it to respond at all.
Halp?
Click to expand...
Click to collapse
Sorry but it sounds like the phone is bricked, and unrecoverable. If it wont boot, or boot to hboot, there really is no way to even try anything. Does it turn on at all?

cmlusco said:
Sorry but it sounds like the phone is bricked, and unrecoverable. If it wont boot, or boot to hboot, there really is no way to even try anything. Does it turn on at all?
Click to expand...
Click to collapse
Holy cow, props on the quick reply. You're pretty much confirming my fears. I've tried a few combinations of battery and usb connections, but there's no vibration nor ADB signal.
I can't say I've ever seen a stock utility behave this way, so user beware. It's also worth noting that I have no history on this phone's modifications - Just that it was S-ON and locked when I got it, in bootloops between kernel and ROM, and attempting to access recovery looped it too.

cmlusco said:
Try this ruu its the newest officially signed ruu, so it will work with s-on. Place it on your sdcard in no folders and boot to hboot. It should find the file and prompt to press vol up to install. If it errors or dosent find it backup and format your sdcard fat32 with a pc and try again.
The reason the fastboot identifier dosent work is because you need to be on the 1.02 or 1.07 hboot to be able to unlock it. The ruu above will give you 1.07.
From there you can unlock the bootloader, fastboot flash recovery, and flash su thru recovery, then you will be rooted. Then if desired you can downgrade and get s-off.
Click to expand...
Click to collapse
Good news and bad news,
Good news: upgrade worked, and I was able to unlock the boot-loader via HTCDEV.
Bad news: I can flash recoveries all day long, boot images, etc via fast-boot and it shows the bars when flashing on my phone. But when I click recovery, I still get a white HTC splash screen. I think that the NV.img was messed up being that they flashed Frawg or Straight talk over to the network. What can I do? As far as I know there is no way for me to S-OFF, am I softbricked? Maybe there is a way to repair the kernel? IDK, any suggestions at this point would be amazing.

ragus15 said:
Good news and bad news,
Good news: upgrade worked, and I was able to unlock the boot-loader via HTCDEV.
Bad news: I can flash recoveries all day long, boot images, etc via fast-boot and it shows the bars when flashing on my phone. But when I click recovery, I still get a white HTC splash screen. I think that the NV.img was messed up being that they flashed Frawg or Straight talk over to the network. What can I do? As far as I know there is no way for me to S-OFF, am I softbricked? Maybe there is a way to repair the kernel? IDK, any suggestions at this point would be amazing.
Click to expand...
Click to collapse
The ruu should have flashed a correct nv img. Have you tried flashing amon ra recovery, or did you see if you could access the stock recovery after you did the ruu?

cmlusco said:
The ruu should have flashed a correct nv img. Have you tried flashing amon ra recovery, or did you see if you could access the stock recovery after you did the ruu?
Click to expand...
Click to collapse
I can retry the RUU to make sure it was correctly downloaded. After the 1st RUU attempt, I still had a straight to white htc screen loop when choosing the recovery. I have tried Clockwork, stock, and Amon Ra recoveries via the fastboot flash recovery recovery.img method and also the fastboot boot recovery.img methods.

ragus15 said:
I can retry the RUU to make sure it was correctly downloaded. After the 1st RUU attempt, I still had a straight to white htc screen loop when choosing the recovery. I have tried Clockwork, stock, and Amon Ra recoveries via the fastboot flash recovery recovery.img method and also the fastboot boot recovery.img methods.
Click to expand...
Click to collapse
Did you try erasing recovery before flashing?
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Can you boot to the os or no?

cmlusco said:
Did you try erasing recovery before flashing?
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Can you boot to the os or no?
Click to expand...
Click to collapse
I have tried fastboot erase recovery followed by the flash and still get the white HTC image. I am not able to boot the os... i get white HTC splash image over and over, and the USB driver that tries to mount to my desktop in the bootloop is not Android 1.0, it is CMDA technologies. I have no idea what that is or if that has to do with the previous frawg/straight talk flash attempts.

[Q] Failed remote signature verify fail. Phone stops on fastboot

Okay, i have a problem with an old phone, I believe its perm bricked, but wanted to check...
It is currently S-ON, and i have no way to turn off, its has no operating system, and the screen does not turn on. however i can turn the phone on, it does vibrate, and i can use fastboot commands.
Anyone got any idea's or shall i bin it?
C:\and\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.80.0000
(bootloader) version-baseband: 4.06.00.02_2
(bootloader) version-cpld: None
(bootloader) version-microp: 051d
(bootloader) version-main: 1.21.405.2
(bootloader) serialno: **************************
(bootloader) imei: ********************
(bootloader) product: bravo
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9920000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4192mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6175d920
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 0.006s
C:\and\sdk\platform-tools>

It's not a permanent brick if you can send and receive commands...
Your other posts have been for desire s, are you sure you're posting this in the right place? This is desire (bravo) forum.
If it's definitely a desire, look at the troubleshooting guide stickied to the top of q&a. Likely you'll just need to run an RUU, use the 2.3.3 GB one
If it's actually a desire s, search over there, although looks like you've tried running an ruu before

eddiehk6 said:
It's not a permanent brick if you can send and receive commands...
Your other posts have been for desire s, are you sure you're posting this in the right place? This is desire (bravo) forum.
If it's definitely a desire, look at the troubleshooting guide stickied to the top of q&a. Likely you'll just need to run an RUU, use the 2.3.3 GB one
If it's actually a desire s, search over there, although looks like you've tried running an ruu before
Click to expand...
Click to collapse
Yep got the Desire S because i couldn't fix this one years ago.
This is the HTC Desire (Bravo), it was s-off, i tried turning it back to factory settings, IE: S-ON, and a RUU on it, and then it ended up not booting up and the screen stop turning on, i was thinking I may have put the wrong RUU on it, as I believe I was drunk at the time (future warning to all, never flash your phone when drunk!)
When i try to run a RUU, i get errors, normally error with Signature Error. (its a Vodafone locked phone) I have used the RUU for Vodafone UK (latest).

mike989e said:
Yep got the Desire S because i couldn't fix this one years ago.
This is the HTC Desire (Bravo), it was s-off, i tried turning it back to factory settings, IE: S-ON, and a RUU on it, and then it ended up not booting up and the screen stop turning on, i was thinking I may have put the wrong RUU on it, as I believe I was drunk at the time (future warning to all, never flash your phone when drunk!)
When i try to run a RUU, i get errors, normally error with Signature Error. (its a Vodafone locked phone) I have used the RUU for Vodafone UK (latest).
Click to expand...
Click to collapse
sounds like you might have used an SLCD RUU form AMOLED or something like that, which is why you can't see screen.
so can you still get to bootloader screen (turn it off, then vol down + power)? post the output.
are you on a custom hboot?
can you still get into recovery and simply flash another rom just to get it to boot up at least?
you can also try flashing another recovery, recommend 4ext (see my sig), flash it through fastboot, guide if you haven't already set it up. then try to boot into it, full wipe and flash a new rom.
otherwise, if you are looking to get it to s-on and sell it:
look at the troubleshooting guide stickied to the top of q&a. Likely you'll just need to run an RUU, use the 2.3.3 GB one
Click to expand...
Click to collapse
post the exact output if you're still getting errors. however i'm pretty confident it was never a "permanent brick" and you can get it to boot up

eddiehk6 said:
sounds like you might have used an SLCD RUU form AMOLED or something like that, which is why you can't see screen.
so can you still get to bootloader screen (turn it off, then vol down + power)? post the output.
are you on a custom hboot?
can you still get into recovery and simply flash another rom just to get it to boot up at least?
you can also try flashing another recovery, recommend 4ext (see my sig), flash it through fastboot, guide if you haven't already set it up. then try to boot into it, full wipe and flash a new rom.
otherwise, if you are looking to get it to s-on and sell it:
post the exact output if you're still getting errors. however i'm pretty confident it was never a "permanent brick" and you can get it to boot up
Click to expand...
Click to collapse
Nope the Screen doesn't come on at all, it comes on for a split second as in, the screen powers up, nothing on the display, then stays like that. it does boot to bootloader(fastboot) though by default, don't need to press vol down + power.
screen works though, so its confusing...
Oh also i cannot get to adb only fastboot

mike989e said:
Nope the Screen doesn't come on at all, it comes on for a split second as in, the screen powers up, nothing on the display, then stays like that. it does boot to bootloader(fastboot) though by default, don't need to press vol down + power.
screen works though, so its confusing...
Oh also i cannot get to adb only fastboot
Click to expand...
Click to collapse
almost certain you flashed wrong SLCD RUU for amoled or vice versa like i said. which is why you don't see anything...
(actually i realised you can't flash a recovery because it's now s-on, ignore that bit of previous advice about fastboot commands etc.)
so i believe all you have to do...i'll keep mentioning it until you try it:
look at the troubleshooting guide stickied to the top of q&a. Likely you'll just need to run an RUU, use the 2.3.3 GB one
Click to expand...
Click to collapse
number 5 on the guide

eddiehk6 said:
almost certain you flashed wrong SLCD RUU for amoled or vice versa like i said. which is why you don't see anything...
(actually i realised you can't flash a recovery because it's now s-on, ignore that bit of previous advice about fastboot commands etc.)
so i believe all you have to do...i'll keep mentioning it until you try it:
number 5 on the guide
Click to expand...
Click to collapse
I get a bootloader version error, code 140 when i try to install lol

mike989e said:
I get a bootloader version error, code 140 when i try to install lol
Click to expand...
Click to collapse
done a bit of research for you, i thought the bootloader 140 error was for trying to install an older version. 2.3.3 GB RUU is the newest, so should work.
found another guide for you. didn't have time to read it all for you, not sure if a goldcard is required, no harm in making one anyway.
i'm still certain it's possible to get your phone working again, just takes some reading

eddiehk6 said:
done a bit of research for you, i thought the bootloader 140 error was for trying to install an older version. 2.3.3 GB RUU is the newest, so should work.
found another guide for you. didn't have time to read it all for you, not sure if a goldcard is required, no harm in making one anyway.
i'm still certain it's possible to get your phone working again, just takes some reading
Click to expand...
Click to collapse
cannot make a goldcard mate, i cannot get to ADB, as device does not boot past fastboot, and even according to that guide you need to boot the device up to use adb.
Thanks for your help though, i think it is dead, think i'll just bin it

mike989e said:
cannot make a goldcard mate, i cannot get to ADB, as device does not boot past fastboot, and even according to that guide you need to boot the device up to use adb.
Click to expand...
Click to collapse
no, you don't need to be booted into the OS:
If you dont have a goldcard, you might try to create one at this point. This may work only for some people. Try to see if Recovery can be booted up. Poweroff phone, then power it on by pressing Vol- and Poweron key, then wait 30sec and press Vol Down and Poweron button again. At this time, phone gets detected in Windows (as shown by the icon in the bottom right of taskbar and a notification sound.
Type:
Code:
adb devices
If this displays a code SH**** after "List of devices", you're in luck. You can issue an adb command and get a CID of your device, following which you can create a goldcard.
Click to expand...
Click to collapse
the goldcard is just very useful to have in case you have this kind of situation.
i'm still very surprised the 2.3.3 RUU doesn't work. another thing you could try is to use the 2.3.3 GB RUU again, but use the PB99IMG.zip method, by extracting the rom.zip from the RUU
Thanks for your help though, i think it is dead, think i'll just bin it
Click to expand...
Click to collapse
as long as you can get to a bootloader screen, it's almost certainly not dead. your symptoms are EXACTLY as that guide states. it's your device, might as well get it working again
a real brick is literally nothing, no response, no LED, nothing. most people who think their device is 'bricked' is never actually bricked.

as long as you get to fastboot no problem. just download the pb99img from the latest 2.3 official upgrade then throught fastboot (back+power) enter in to fastboot RUU update mode then flash the zip with the command fastboot flash zip rom.zip . you dont need even an sd card to do that. just wait to procces to finish then fastboot reboot and your done. first boot takes few minutes longer but you wont have problems.

theres a couple of problems i have, 1 i have no screen, even when i fastboot. so i wont know if it fails, secondly my issues is that the image version number is to high on my phone. hence why i am getting the 140 error. as i have installed a number of roms off here the version number is to high.
off the top of my head, i cannot remember the number, however, on 2.3.3 is got a .17. in it, mine instead of that has .27. which means mine cannot install the standard 2.3.3 software, if i knew how to change the image number to higher than mine, and repackage it i could install it. but i don't know how. as i recall there was a thread about this years ago, but not sure if it was ever solved. i did look for it.

Okay, this is not fixable in my opinion.
Summary:
I have a HTC Desire GMS, I flashed it along time ago, which buggered something! Now the screen does not come on, there is no system installed, and i can only access fastboot from usb.
I cannot use commands like "fastboot oem", It can find the device. I believe this is because the phone is S-ON, and HBOOT is 0.80
My device has a Customer ID of VODAP001 so i assume i need to use a Vodafone ROM
I have tried a number of different versions of ROMs in a few different methods.
RUUS Tried - RUU_Vodafone_UK_2.33.161.2 - RUU HTC_WWE_2.29.405.5 - RUU HTC_WWE_2.09.405.8 - OTA_2.29.405.5
I have tried changing the rom.zip to PD99IMG.zip, but as the screen doesn't work, i do not know what the error is.
When i try to use FASTBOOT to run the ROM, i get a number of different errors, ranging from CUSTOMERID Error to Signature Error.
Installing via RUU i get the same errors as above, or more often than not, i get USB Connection error (i have installed drivers)
So i'm thinking lost course. As i would need a Vodafone UK Customer ID, with a worldwide (405) Signature higher than 1.2x.405.x
Thanks everyone for your help!

mike989e said:
Okay, this is not fixable in my opinion.
Summary:
I have a HTC Desire GMS, I flashed it along time ago, which buggered something! Now the screen does not come on, there is no system installed, and i can only access fastboot from usb.
I cannot use commands like "fastboot oem", It can find the device. I believe this is because the phone is S-ON, and HBOOT is 0.80
My device has a Customer ID of VODAP001 so i assume i need to use a Vodafone ROM
I have tried a number of different versions of ROMs in a few different methods.
RUUS Tried - RUU_Vodafone_UK_2.33.161.2 - RUU HTC_WWE_2.29.405.5 - RUU HTC_WWE_2.09.405.8 - OTA_2.29.405.5
I have tried changing the rom.zip to PD99IMG.zip, but as the screen doesn't work, i do not know what the error is.
When i try to use FASTBOOT to run the ROM, i get a number of different errors, ranging from CUSTOMERID Error to Signature Error.
Installing via RUU i get the same errors as above, or more often than not, i get USB Connection error (i have installed drivers)
So i'm thinking lost course. As i would need a Vodafone UK Customer ID, with a worldwide (405) Signature higher than 1.2x.405.x
Thanks everyone for your help!
Click to expand...
Click to collapse
i'm confused whether the screen comes on at all now. you said previously you could get into bootloader screen, is this still the case?
can you try to get to select recovery, then connect and see if it connects to adb at all as stated in the guide? if so then you're in luck and can create a goldcard. once that's done you should be able to run any SLCD RUU as it will skip the CID check. you need to find some way of communicating via adb. some links are down, so manual method may be another way.
have you read those guides very slowly and tried everything? posting there may also help. droidzone is still active and will be the expert on solving this.
your issue is one of the more difficult to solve, i think it's still possible, goldcard is the key here.

eddiehk6 said:
i'm confused whether the screen comes on at all now. you said previously you could get into bootloader screen, is this still the case?
can you try to get to select recovery, then connect and see if it connects to adb at all as stated in the guide? if so then you're in luck and can create a goldcard. once that's done you should be able to run any SLCD RUU as it will skip the CID check. you need to find some way of communicating via adb. some links are down, so manual method may be another way.
have you read those guides very slowly and tried everything? posting there may also help. droidzone is still active and will be the expert on solving this.
your issue is one of the more difficult to solve, i think it's still possible, goldcard is the key here.
Click to expand...
Click to collapse
Sorry there was some confusion there, the screen does not come on at all, i get to the bootloader as in it loads on the phone, i cannot see it though, and can connect using my pc to use fastboot. i do not believe i cannot get into recovery, as i am not sure where im loading into, it is somewhere that i can use fastboot. yes i have read through them, and thank you for those! and tried everything other than the gold card. will try to do that but as i don't have a screen that works as i installed a SLCD instead of the correct screen firmware i'm not sure how it will help.

mike989e said:
Sorry there was some confusion there, the screen does not come on at all, i get to the bootloader as in it loads on the phone, i cannot see it though, and can connect using my pc to use fastboot. i do not believe i cannot get into recovery, as i am not sure where im loading into, it is somewhere that i can use fastboot. yes i have read through them, and thank you for those! and tried everything other than the gold card. will try to do that but as i don't have a screen that works as i installed a SLCD instead of the correct screen firmware i'm not sure how it will help.
Click to expand...
Click to collapse
i'm still a bit confused as i've never experienced it, only read others. so you can't even see the bootloader screen at all anymore, i thought that still works even in your situation (for clarity it's the white background with BRAVO SHIP S-ON at the top). does it still boot to bootloader screen straight away every time you try to power on normally?
or if you leave it after trying to power it on normally, does it get to boot sound? if so it still installed, you just have no screen. wait a minute until it boots up, then try connecting and see if you can communicate with adb.
at least fastboot is communicating so it's doesn't feel like a lost cause.
if above doesn't work boot to bootloader anyway (vol down + power), wait for a few seconds. then press volume down once, then power to select recovery. then try as before to get it to communicate as stated in the guide. have you tried this?
i haven't read all of it, but i believe you need at least 'adb devices' to work! then goldcard...

eddiehk6 said:
i'm still a bit confused as i've never experienced it, only read others. so you can't even see the bootloader screen at all anymore, i thought that still works even in your situation (for clarity it's the white background with BRAVO SHIP S-ON at the top). does it still boot to bootloader screen straight away every time you try to power on normally?
or if you leave it after trying to power it on normally, does it get to boot sound? if so it still installed, you just have no screen. wait a minute until it boots up, then try connecting and see if you can communicate with adb.
at least fastboot is communicating so it's doesn't feel like a lost cause.
if above doesn't work boot to bootloader anyway (vol down + power), wait for a few seconds. then press volume down once, then power to select recovery. then try as before to get it to communicate as stated in the guide. have you tried this?
i haven't read all of it, but i believe you need at least 'adb devices' to work! then goldcard...
Click to expand...
Click to collapse
Ok, It does not have a white background, the screen simply does not power on at all. (this happened after a flash, no knocks or bangs to the phone. So i don't think the screen is damaged.)
Before, it did have the white background. Yes, i believe it is booting into the bootloader when i try to start up. as thats how i am using Fastboot.
There is nothing in the system folder, "fastboot oem boot" shows nothing. i believe the phone is completely blank other than the HBOOT 0.80
i have tried that, it simply reboots back into bootloader, as i had a 3rd party recovery.
I was returning this to unrooted when this happened.
I cannot get the gold card to work on any of my microsd cards... so i will need to purchase a few to see if i can get it to work!

mike989e said:
Ok, It does not have a white background, the screen simply does not power on at all. (this happened after a flash, no knocks or bangs to the phone. So i don't think the screen is damaged.)
Before, it did have the white background. Yes, i believe it is booting into the bootloader when i try to start up. as thats how i am using Fastboot.
There is nothing in the system folder, "fastboot oem boot" shows nothing. i believe the phone is completely blank other than the HBOOT 0.80
i have tried that, it simply reboots back into bootloader, as i had a 3rd party recovery.
I was returning this to unrooted when this happened.
I cannot get the gold card to work on any of my microsd cards... so i will need to purchase a few to see if i can get it to work!
Click to expand...
Click to collapse
you shouldnt have a custom recovery installed any more, the RUU should overwrite it to stock recovery. you won't be able to do anything with stock recovery per se, but the guide seems to indicate that you may be able to communicate with the device via adb.
still surprised the 2.3.3 RUU didn't work, I thought it's the highest version number so shouldn't have any problem.
I'm running out of ideas tbh, I'd still recommend posting the issue in the droidzone guide, hopefully he'll reply as he'd most likely know how to solve it.

[Q] DHD woes

Hi all,
Been having problems with my DHD for ages now - got myself a GS3 after a while so had kind of given up on it but now I really want to get it back to life as a backup (and for a temp replacement for my gf who got her phone driven over yesterday!). I've seen loads of similar problems to mine, but after searching here for months and following several soutions to one point or another, I always seem to get some kind of error that no-one else is getting and from there it branches off into new problems/methods. Kind of getting sick of going in circles so here I am asking for some DHD justice!
The problem is this:
A few months back the DHD started freezing/restarting intermittently (something to do with Sense I think, but tried the goldcard method of rooting it a few weeks before which failed, not sure if this could have affected things but it didnt seem to have any noticable effect for a while anyway) then eventually got either stuck in a loop on the carriers logo animation or hanging at the white background/green HTC logo screen. Couldn't get any further. Did a factory reset but the problem persisted. After a few weeks I came back to it and found that very occasionally I could get the phone to start up and get on the home screen. I can do a few things (like enabling USB debugging luckily) there but get DOZENS of notifications that various processes are failing and eventually the phone reboots or jumps to the HTC logo screen again. Either this happens before I can do very much on the phone or some process fails and nothing happens. So really I need a solution thats mostly PC based - but pretty much every program or command line operation fails to actually see the phone. I'm assuming here what I need to do it flash a new ROM to replace what I also assume is a corrupt existing one? I've tried RUU .exe type fixes - which don't see the phone. Most of the command line instructions fail to see the phone either. The phone isn't rooted so I'm guessing this would need to be done to flash a new ROM (a working version of the stock one would be fine for what I need it for but having a custom one would be nice). I've got nowhere with trying to flash ROMs as is (not rooted, S-ON), and also nowhere with various root/s-off tools. TBH I'm not really sure which stage of the process I need to be trying first. The other day the phone suddenly booted ok without the notifications and worked for around 6 hours before something made it reboot and return to the boot loop.
On the HBOOT screen I have the following:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.28_M2
eMMC-boot
Trying to boot into recovery just gets me the red triangle screen. Trying a new image from SD doesnt work as it doesnt see the card mounted.
Thanks for taking the time to read my tale of woe. Anyone got an idea where to start with this?

MerkyBlud said:
Hi all,
Been having problems with my DHD for ages now - got myself a GS3 after a while so had kind of given up on it but now I really want to get it back to life as a backup (and for a temp replacement for my gf who got her phone driven over yesterday!). I've seen loads of similar problems to mine, but after searching here for months and following several soutions to one point or another, I always seem to get some kind of error that no-one else is getting and from there it branches off into new problems/methods. Kind of getting sick of going in circles so here I am asking for some DHD justice!
The problem is this:
A few months back the DHD started freezing/restarting intermittently (something to do with Sense I think, but tried the goldcard method of rooting it a few weeks before which failed, not sure if this could have affected things but it didnt seem to have any noticable effect for a while anyway) then eventually got either stuck in a loop on the carriers logo animation or hanging at the white background/green HTC logo screen. Couldn't get any further. Did a factory reset but the problem persisted. After a few weeks I came back to it and found that very occasionally I could get the phone to start up and get on the home screen. I can do a few things (like enabling USB debugging luckily) there but get DOZENS of notifications that various processes are failing and eventually the phone reboots or jumps to the HTC logo screen again. Either this happens before I can do very much on the phone or some process fails and nothing happens. So really I need a solution thats mostly PC based - but pretty much every program or command line operation fails to actually see the phone. I'm assuming here what I need to do it flash a new ROM to replace what I also assume is a corrupt existing one? I've tried RUU .exe type fixes - which don't see the phone. Most of the command line instructions fail to see the phone either. The phone isn't rooted so I'm guessing this would need to be done to flash a new ROM (a working version of the stock one would be fine for what I need it for but having a custom one would be nice). I've got nowhere with trying to flash ROMs as is (not rooted, S-ON), and also nowhere with various root/s-off tools. TBH I'm not really sure which stage of the process I need to be trying first. The other day the phone suddenly booted ok without the notifications and worked for around 6 hours before something made it reboot and return to the boot loop.
On the HBOOT screen I have the following:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.28_M2
eMMC-boot
Trying to boot into recovery just gets me the red triangle screen. Trying a new image from SD doesnt work as it doesnt see the card mounted.
Thanks for taking the time to read my tale of woe. Anyone got an idea where to start with this?
Click to expand...
Click to collapse
1. S-off your device
2. Use android flasher
3. AND easily flash flash recovery thorough this software....
Sent from my HTC Desire HD using xda premium

MaratabHashmi said:
1. S-off your device
2. Use android flasher
3. AND easily flash flash recovery thorough this software....
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
S-off requires rooting it first, am I right? Not having much luck with that - HTC Quickroot claims its been done but none of the apps such as SuperUser are present when it reboots...

Suggestions anyone? efforts to S-OFF not working so far...:fingers-crossed:

You don't need to root if all you want to do is run a RUU. Are you trying to do it through ADB or fastboot? Is the RUU you're trying compatible with your phone's region?

bananagranola said:
You don't need to root if all you want to do is run a RUU. Are you trying to do it through ADB or fastboot? Is the RUU you're trying compatible with your phone's region?
Click to expand...
Click to collapse
I'm trying running the .exe file from the pc, I'm 99.9% sure its the correct region (3UK stock). It gets as far as bringing up a screen with a grey HTC logo while the PC says 'waiting for bootloader' before I get an error message saying the USB connection is lost (tried 3 different cables and there is no issue with faulty cables, or either end being unplugged, ). ADB doesnt see the phone as connected. Fastboot doesnt seem to do much as usually when the phone reboots as part of the process it freezes or goes back into bootloop. I've tried putting ROMs on the sd card and updating from the recovery menu but the phone doesnt see the card as mounted in this mode (when it does boot and run ok for a few minutes it does eventually see the card).

I'm confused. You have a recovery menu? Is your phone's bootloader unlocked?

Sorry, I mean the menu accessed through power on + vol down. No, tried unlocking it through the HTC site but no joy.

That's the bootloader. What procedure are you using for fastboot?

Via ADB commands - havent tried with fastboot methods recently though so I forget which particular guide I was using. I'm sure there are all kinds of noob alarms and flashing lights going off somewhere

You cannot run a RUU from adb. Only fastboot.

Where do I start with this then? I have the fastboot pc files installed already but didn't get anywhere, seem to remember the phone rebooting from a command and then just going back to the logo bootloop before it could progress - very possibly doing something wrong though.
Update: Tried the following:
Ran the RUU.exe until the wizard comes up. While the RUU wizard was open, found the temporary folder it created.Found ROM.zip. Opened it, extracted recovery.img. Put it in the location where Android SDK tools is installed. Booted the phone into bootloader, gone to FASTBOOT USB. Opened a command prompt, navigated to the folder with Android SDK tools. Entered:
fastboot flash recovery recovery.img
BUT still getting an error: "'fastboot' is not recognized as an internal or external command, operable program or batch file." :S

MerkyBlud said:
Where do I start with this then? I have the fastboot pc files installed already but didn't get anywhere, seem to remember the phone rebooting from a command and then just going back to the logo bootloop before it could progress - very possibly doing something wrong though.
Update: Tried the following:
Ran the RUU.exe until the wizard comes up. While the RUU wizard was open, found the temporary folder it created.Found ROM.zip. Opened it, extracted recovery.img. Put it in the location where Android SDK tools is installed. Booted the phone into bootloader, gone to FASTBOOT USB. Opened a command prompt, navigated to the folder with Android SDK tools. Entered:
fastboot flash recovery recovery.img
BUT still getting an error: "'fastboot' is not recognized as an internal or external command, operable program or batch file." :S
Click to expand...
Click to collapse
You need to change to the correct folder on your PC where your fastboot.exe file is, thats why your getting your error.
Why you trying to flash stock recovery? Unless I missed it, From what I can see on your posts your still s-on, so you can't flash anything like that from fastboot anyway.
Sent from my GT-I9505 using xda app-developers app

The error you're getting is that your computer can't find the fastboot file. It's not an error from fast out itself. Open the folder with fastboot in it, shift-rightclick, and choose "open command window here." Also, I thought you were running a RUU, not actually using fastboot to flash images. If you want to flash stuff you need to unlock bootloader.

bananagranola said:
The error you're getting is that your computer can't find the fastboot file. It's not an error from fast out itself. Open the folder with fastboot in it, shift-rightclick, and choose "open command window here." Also, I thought you were running a RUU, not actually using fastboot to flash images. If you want to flash stuff you need to unlock bootloader.
Click to expand...
Click to collapse
Yeah, I was initially trying to run the RUU.exe but that method wasn't working as I mentioned, so I tried extracting the rom it created and flashing that via fastboot.(Didn't know that shift/rightclick thing, thanks). As for s-off I haven't found a way of doing that without rooting, hence why I thought I couldn't get anywhere without rooting the phone first.
When I try and unlock the bootloader ( at http://www.htcdev.com/bootloader/ruu-downloads) , it wants to update the HBOOT first, this is how far I get with the process:
"BEFORE beginning the Unlock Bootloader process your product requires that you update the ROM to the version listed in the table below first, then download the RUU next to it to enable the unlocking capability.
To install the RUU, simply follow these instructions:
On your phone, enable USB debugging. (From the Home screen, MENU > Settings > Applications > Development > Check USB debugging)
Connect your phone to the computer using the USB cable that came with your phone. Wait a moment for your computer to identify your phone, this may take a few minutes. After your computer has found your phone, double click on the RUU to start the process"
I get as far as bringing up a screen with a grey HTC logo while the PC says 'waiting for bootloader' before I get an error message saying the USB connection is lost (so exactly the same problem trying to update the HBOOT as trying to run the RUU.exe) so I'm not sure how I'm going to unlock the bootloader if this method isn't working - direct .exe method doesnt work, and the process I need to unlock the bootloader so I can flash via fastboot doesnt work for the same reason.

Have you tried booting into bootloader and choosing fastboot before trying the RUU?

Yep. Same USB connection error despite having 'FASTBOOT USB' showing....

Type "fastboot devices." What does it say? Do you have your drivers from HTC Sync installed?

Hi all, had the phone working ok for a while, it wanted to do a software update which froze at 12%, however after cancelling it the phone seems to be problem free. Dont really get this as surely the incomplete update wouldnt take..? but something must have changed. The phones been ok for over a week now although I havent rebooted it or let the battery run flat...still dont trust it entirely!

Develop Bugs

welcome