[SOLVED] [Q] Bricked Desire - Desire Q&A, Help & Troubleshooting

Hi,
I have a problem with my Desire. I have tried things found in other threads, but I can't get it to work.
I have installed Sandvold ICS on it.
I can get to the boot screen, where it stays forever.
I can also get to Recovery, fastboot and Clockworkmod.
I have:
Clockwordmod Recovery v5.0.2.0
PVT1 SHIP S-OFF
HBOOT-6.93.1002
I have tried running the RUU, but it says my battery is below 30%, even though it is fully charged.
I have tried using adb, but my device is not detected. Though it is detected in device manager as Android Bootloader Interface.
Unrevoked doesn't detect it either.
I'm really at a loss.
Any help will be appreciated.

boot into recovery do a full wipe and try re-install the rom or try a different rom also make sure u have the correct hboot and a ext3/4 partition for the rom if it needs 1. when i tested that rom before i had CM7r2 hboot and had a 1gb ext4 partition and it worked fine. check out the op of the rom for exact install instructions
Sent from my HTC Desire

I forgot to mention that it won't mount the sdcard.
It was running fine for a while on the Sandvold rom, but then after it ran out of power it wouldn't boot when I recharged it.

boot into fastboot (power off then hold back + power) plug in via usb and try fastboot commands
fastboot oem enableqxdm 0
fastboot oem eraseconfig
if that fails go to bortaks troubleshooting guide. (desire q&a) first post. i think he covers this problem

Thanks for that! I got it working again!
Turns out that the sdcard didn't work.
Strange that it went out from day to day.
Thank you again!

Edit the thread title to [SOLVED] as anyone with the same problem can find solution.

How?

on ur computer just edit the name/title [Q] Bricked Desire. to [solved] [Q] Bricked Desire
Sent from my HTC Desire

Found it. Had to go to advanced editing to change the title.

Related

[Q] Experienced Magic User needs help with Desire (flashing AmonRA) (

hey guys, need some help:
been flashing radios, roms and spls succesfully in the past year on my htc magic.
recently upgraded to the desire and wanted to start flashing here as well.
i can see the device with adb devices (or fastboot devices), so driver must be installed correctly
but when i fastboot flash recovery (AmonRA) it sends ok but then fails writing with the error "fastboot failed (=remote not allowed)".
the desire has froyo sense stock on it and booting into fastboot gives me this info:
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30_2
Aug 10 2010, 17:52:18
so i have s-off which is good, but why can't i get amonra on the phone?
do i need another hboot? and what about spl?
please someone explain what i'm missing here!
thx,
v.
You could try and use the Android Flasher utility. Makes it easier and I've had no problems with it.
hey, thanx for your answer, and nice prog!
it didn't work though: i booted the phone into fastboot, started the prog and gave it amonra's recovery. it all looked like it worked. the phone also reboots just like it says in the prog. but it still doesn't get the recovery on the phone.
so here's my updated status report, i hope someone can help me out:
i rooted succesfully yesterday (the unrevoked method). the version from their site that you can download now didn't do the trick though, i got the missing CID error that lots of others also get. i searched that problem and found the unrevoked prog in its version 3.2. that one worked. so the phone is rooted and unrevoked also flashed clockwork mod recovery.
i then succesfully flashed a rom (oxygen) and this all works which is nice.
my problem is that i
1.) can't boot into recovery by pressing home + power. i have to fastboot, then choose bootloader, then recovery. this starts clockwork mod.
2.) i can't get amonra to my phone. it won't work via fastboot flash recovery (error mentioned in post #1) or via the program mentioned in post #2.
i'd really like be able to flash recovery and radios via fastboot commands, i'm used to it and i don't like the fact that i get an error when i try this.
what's causing the problem here?
it must also be related to the fact that i couldn't get amonra installed via the program mentioned in post #2.
is it my hboot?
i'm rooted and also s-off.
so what is causing this locked up behavior?
i'd apprecciate any help you can give me,
thx,
v.
Try flashing it from the phone itself.
Place amonra.img in sdcard root directory.
From terminal emulator or over adb type flash_image recovery /sdcard/amonra.img
Then reboot, this can be done from recovery or from android.
already tried that method yesterday (sorry i forgot to mention it).
didn't work either.
i just ran unrevoked again and clicked "custom recovery" and added the amonra recovery. unrevoked ran thru the rooting process and in the end it succesfully flashed amonra. at least i can now use amonra.
but i still can't use any fastboot commands, i always get the "failed (remote: not allowed)" error.
what the hell is going on here?!
greetz,
v.
update:
i flashed a patched hboot from alpharev and this did the trick!
i thought s-off meant i could do all these fastboot commands but i must have been wrong (or some other reason, i don't know).
i downloaded the "PB99IMG_bravo_cm7" zip (because i'm running CM7 at the moment). normally you should flash these via fastboot but as i said this didn't work on my phone so i had to use the alternative method:
"You can also download the corresponding PB99IMG zipfile, put it on your sdcard, and rename it to PB99IMG.zip. Then start the phone in HBOOT mode (VolDown+POWER) to flash the HBOOT without a PC."
now i can finally work with fastboot commands again, no more "failed (remote: not allowed)" errors!
greetz,
v.
Weird. S-Off should allow you to use fastboot commands. Very weird indeed but that's just how it goes sometimes

[Q] Hang on White Screen (HTC)

Dear all, unexpectdly my phone stopped working, it hangs on white screen (HTC) then if i boot into bootloader it doesnot go into recovery , hangs on white HTC screen, then after that i place PC36IMG.zip on root of SD Card it is not detecting it either,
My desire is
PVT 4 S OFF
BRAVO Hboot 0.93
A8181
Regards. Please help me out
It Is also getting hot when i put battery In.. even i tried to flash new recovery using adb but no use, adb is not detecting any device, android 1.0 driver is installed, i was running RCMix Custom ROM. so i knowing all rooting, flashing etc things...please help out.
Regards
Please use the Q&A Forum for questions Thanks
Moving to Q&A
You have to flash recovery with fastboot, fastboot flash recovery recovery.img (put recovery.img in same folder as fastboot)
You could also try running the RUU while booted in fastboot (just connect USB, and run RUU). I believe I did this once... Not 100% sure if it was fastboot or bootloader, just check them both...
kaico said:
You could also try running the RUU while booted in fastboot (just connect USB, and run RUU). I believe I did this once... Not 100% sure if it was fastboot or bootloader, just check them both...
Click to expand...
Click to collapse
When you want to flash ruu, your phone has to be fastboot mode, otherwise it won't get recognized.

[Q] Phone will not boot

Hello!
Here are some details:
BRAVO PVT4 SHIP S-ON
HBOOT 0.93.0001
MICORP-051d
RADIO 5.09.05.30_C
I'm rooted, and was running the latest version of Oxygen (as of a few days ago).
I did a search, but couldn't find anything.
So here is my problem: a few days ago my phone, after installing the latest version of Oxygen, I noticed my phone was shutting down after prolonged use. I thought it was because of overheating, caused by an overclocking problem or something.
Now, however, it won't get past the white loading screen with HTC on it. I can hold volume down and get into HBOOT, but as soon as I select recovery, the same white HTC screen shows up. The screen stays there until I have to remove the battery. It never boots up, and I cannot get into recovery.
I have tried:
Clearing storage from the HBOOT menu
Reflashing Clockwordmod (however, I realized you have to be S-Off to do this, and I can't find any methods that allow me to S-Off from within HBOOT or Fastboot (which is all I can get into)).
The phone is recognized via ADB when in Fastboot, but I don't know where to go from there.
Any help or suggestions would be greatly appreciated. Like I said, I did a fruitless search, but if this question has already been answered, a link would be fantastic as well. Thank you for your time!
If you boot into your HBOOT and then fastboot, You can use the revolutionary tool, to gain S-OFF from there, At the end of it, it shall even ask if you wan to install Clockworkmod, and it is 4.0.1. instead of the offical 2.5.0.7.
New features
I'm running the Revolutionary tool, and it's stuck at "Waiting for device..."
My phone is in Fastboot, connected via USB, and I've downloaded and installed the HTC Desire Fastboot drivers. It's showing all OK in device manager, but the revolutionary .exe won't see it. Am I doing something wrong?
I wouldnt say you were doing anything wrong, Just the phone seems a tad more broken than it looks
http://wiki.rootzwiki.com/index.php/HTC_Desire
I'm following those directions 100%, but it looks like the revolutionary tool won't see my device. Are you sure it can s-off while in Fastboot?
I have no idea where to go from here - I have a useless phone that won't even go into recovery. More help would be amazing.
IWAS HAVING THE SAME PROPLEM
thats wat i did
u can down load this file
update :: I cant put the link :S
google for PB99IMG.zip
Download it
if the name wasnt exact match rename it to PB99IMG.zip
and pull ur sd card put it in card reader
then copy it into sd card root folder
then put the memory back into the phone
press vol down and power
then relase
it will autumatic setup the stok RUU of ur HTC desire
that will remove the rooting and make ur phone brand new
N.P if the instalation didt sucess and said CID incorrect
then u need
gold card
make ur gold card then put the files in ur gold card put it in the phone and enter boot menu
instaltion will sucess this time
worked for me

[Q] Bricked- 3 Vibrates, LED flash on boot. Hboot 2.10, amonRA working - Please help!

Hey everyone.. any help on this would be greatly appreciated, has caused a lot of stress.
The phone was successfully downgraded to hboot 2.10 from hboot 2.18 a while back, s-off was achieved, all things were working perfectly with gingerbread roms and the sort.
I decided I wanted an ICS rom as my main boot-up, but was having difficulties installing it and finding a cooperable kernal/radio to get it to flash..
(looking back this probably wasn't the real issue as to why the ROM wouldn't load, and this base ICS rom that I was drawn to was not at all the one I should have been getting conclusion/direction from)
Anyways, I see now that I was trying to flash an Evo V 4G ICS rom, and in install this rom led me to update an EVO V 4g radio.
This was the rom I was trying to install:
http://androidforums.com/evo-v-4g-a...om-harmonia-3-17-17nov12-ics-sense-3-6-a.html
And in reading up on that lead me to this link
http://androidforums.com/evo-v-4g-all-things-root/648747-update.html
where I flashed the 'OTA_Shooter_ICS_35_S_Sprint_WWE_VM_1.14.652.0-1.13.652.2_release_291083f0wrax77ry0w073p' update.
Soon thereafter I found myself back with S-ON (previously was s-off), with no roms able to install.
I can get adb/sd functionallity in fastboot/hboot and have amonRA 2.3 installed as my recovery that I can get too.
In fact, in amonRA gingerbread roms say they install correctly, and I also have a nandroid backup of 'system' 'restore' 'data' 'cache' 'boot' which I believe I performed before the radio update.
They both say installed/updated correctly (new rom flash/nandroid), but upon rebooting the system, the evo 4G just vibrates 3 times, flashes its LED, and that's it. Blank screen - nothing.
Please, any help on this?
To sum it up:
I flashed the above incompatible radio in attempt to get a rom working which on foresight was for the EVO V 4G instead of the EVO 4G.
Upon doing this my hboot stayed the same (2.10), but it reverted my from S-OFF back to S-ON.
Confusing enough my radio on the hboot menu says '2.15.00.08.08', which is the latest EVO 4G radio according to here:
http://forum.xda-developers.com/showthread.php?t=715485
Hboot 2.10 USB boots fine with vol down + power, have ADB capabilities to it, and recovery boots fine to amonRA.
Much thanks in advance, I really want to get this running again!
echoedge said:
Hey everyone.. any help on this would be greatly appreciated, has caused a lot of stress.
The phone was successfully downgraded to hboot 2.10 from hboot 2.18 a while back, s-off was achieved, all things were working perfectly with gingerbread roms and the sort.
I decided I wanted an ICS rom as my main boot-up, but was having difficulties installing it and finding a cooperable kernal/radio to get it to flash..
(looking back this probably wasn't the real issue as to why the ROM wouldn't load, and this base ICS rom that I was drawn to was not at all the one I should have been getting conclusion/direction from)
Anyways, I see now that I was trying to flash an Evo V 4G ICS rom, and in install this rom led me to update an EVO V 4g radio.
This was the rom I was trying to install:
http://androidforums.com/evo-v-4g-a...om-harmonia-3-17-17nov12-ics-sense-3-6-a.html
And in reading up on that lead me to this link
http://androidforums.com/evo-v-4g-all-things-root/648747-update.html
where I flashed the 'OTA_Shooter_ICS_35_S_Sprint_WWE_VM_1.14.652.0-1.13.652.2_release_291083f0wrax77ry0w073p' update.
Soon thereafter I found myself back with S-ON (previously was s-off), with no roms able to install.
I can get adb/sd functionallity in fastboot/hboot and have amonRA 2.3 installed as my recovery that I can get too.
In fact, in amonRA gingerbread roms say they install correctly, and I also have a nandroid backup of 'system' 'restore' 'data' 'cache' 'boot' which I believe I performed before the radio update.
They both say installed/updated correctly (new rom flash/nandroid), but upon rebooting the system, the evo 4G just vibrates 3 times, flashes its LED, and that's it. Blank screen - nothing.
Please, any help on this?
To sum it up:
I flashed the above incompatible radio in attempt to get a rom working which on foresight was for the EVO V 4G instead of the EVO 4G.
Upon doing this my hboot stayed the same (2.10), but it reverted my from S-OFF back to S-ON.
Confusing enough my radio on the hboot menu says '2.15.00.08.08', which is the latest EVO 4G radio according to here:
http://forum.xda-developers.com/showthread.php?t=715485
Hboot 2.10 USB boots fine with vol down + power, have ADB capabilities to it, and recovery boots fine to amonRA.
Much thanks in advance, I really want to get this running again!
Click to expand...
Click to collapse
You're going to need to upgrade your device to the latest available RUU version (4.67.651.3), unlock your bootloader with HTCDev, flash a custom recovery, root your device, and then downgrade your misc partition (again). That should normalize your device (if one of the earlier steps doesn't do it).
echoedge said:
Hey everyone.. any help on this would be greatly appreciated, has caused a lot of stress.
The phone was successfully downgraded to hboot 2.10 from hboot 2.18 a while back, s-off was achieved, all things were working perfectly with gingerbread roms and the sort.
I decided I wanted an ICS rom as my main boot-up, but was having difficulties installing it and finding a cooperable kernal/radio to get it to flash..
(looking back this probably wasn't the real issue as to why the ROM wouldn't load, and this base ICS rom that I was drawn to was not at all the one I should have been getting conclusion/direction from)
Anyways, I see now that I was trying to flash an Evo V 4G ICS rom, and in install this rom led me to update an EVO V 4g radio.
This was the rom I was trying to install:
http://androidforums.com/evo-v-4g-a...om-harmonia-3-17-17nov12-ics-sense-3-6-a.html
And in reading up on that lead me to this link
http://androidforums.com/evo-v-4g-all-things-root/648747-update.html
where I flashed the 'OTA_Shooter_ICS_35_S_Sprint_WWE_VM_1.14.652.0-1.13.652.2_release_291083f0wrax77ry0w073p' update.
Soon thereafter I found myself back with S-ON (previously was s-off), with no roms able to install.
I can get adb/sd functionallity in fastboot/hboot and have amonRA 2.3 installed as my recovery that I can get too.
In fact, in amonRA gingerbread roms say they install correctly, and I also have a nandroid backup of 'system' 'restore' 'data' 'cache' 'boot' which I believe I performed before the radio update.
They both say installed/updated correctly (new rom flash/nandroid), but upon rebooting the system, the evo 4G just vibrates 3 times, flashes its LED, and that's it. Blank screen - nothing.
Please, any help on this?
To sum it up:
I flashed the above incompatible radio in attempt to get a rom working which on foresight was for the EVO V 4G instead of the EVO 4G.
Upon doing this my hboot stayed the same (2.10), but it reverted my from S-OFF back to S-ON.
Confusing enough my radio on the hboot menu says '2.15.00.08.08', which is the latest EVO 4G radio according to here:
http://forum.xda-developers.com/showthread.php?t=715485
Hboot 2.10 USB boots fine with vol down + power, have ADB capabilities to it, and recovery boots fine to amonRA.
Much thanks in advance, I really want to get this running again!
Click to expand...
Click to collapse
have you tried running a RUU yet? it should restore your phone back to stock radio hboot system and a few other things
Okay, I will try to get the latest RUU up and running.
I see them listed here
http://wiki.rootzwiki.com/HTC_EVO_4G_Downloads
but all the links are dead -- will look for a mirror right now.
I see there are three different methods for flashing the RUU - an update.zip I can flash in amonRA, a PC36IMG I can flash in hboot and an radio.img file I can do in fastboot adb..
I also find a .exe file
RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed.exe
but it's an .exe file?
and they all seem to differentiate in size from a like 10mg PC36IMG to a 220mb version as the .exe is..
so many different choices, what's my best option for the situation
Thanks a bunch for the quick replies!
echoedge said:
Okay, I will try to get the latest RUU up and running.
I see them listed here
http://wiki.rootzwiki.com/HTC_EVO_4G_Downloads
but all the links are dead -- will look for a mirror right now.
I see there are three different methods for flashing the RUU - an update.zip I can flash in amonRA, a PC36IMG I can flash in hboot and an radio.img file I can do in fastboot adb..
I also find a .exe file
RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed.exe
but it's an .exe file?
and they all seem to differentiate in size from a like 10mg PC36IMG to a 220mb version as the .exe is..
so many different choices, what's my best option for the situation
Thanks a bunch for the quick replies!
Click to expand...
Click to collapse
The RUU is run from the PC while you're in fastboot mode. That'll work fine. Or you can use the PC36IMG from here and flash in HBOOT (bootloader).
Cool, thanks.
Okay, I downloaded the .zip and .exe-- ended up using Captain's link to HBoot the RUU by renaming it to PC36IMG.zip
So then booted up in hboot, it detected the PC36IMG -- went through the list.. check, check, check, check, completed and done.
Rebooted the phone, now instead of just a black screen with the 3 vibrations and led flashes, it goes to the "EVO 4G" white screen loader, then 5-10 seconds later, goes blank and does the 3 vibration thing again.
Back to HBoot.
Noticed the only change was the radio oversion now says 2.15.00.11.19 now
So now my next step is to do the HTCDev method I assume?
Fastboot USB'd- phone detected by W7 just fine.
I type in 'fastboot devices' and it detects the phone and gives the serial number, so fastboot seems to be in working order.
I then type in the command 'fastboot oem get_identifier_token'
and am getting the error
C:\Android>fastboot oem get_identifier_token
... INFO[ERR] Command error !!!
OKAY [ 0.008s]
finished. total time: 0.008s
Click to expand...
Click to collapse
and seem to be stuck here.. tried re-installing my htc sync, redid the get_identifier_token command and the same error persists.
Any suggestions?
echoedge said:
Cool, thanks.
Okay, I downloaded the .zip and .exe-- ended up using Captain's link to HBoot the RUU by renaming it to PC36IMG.zip
So then booted up in hboot, it detected the PC36IMG -- went through the list.. check, check, check, check, completed and done.
Rebooted the phone, now instead of just a black screen with the 3 vibrations and led flashes, it goes to the "EVO 4G" white screen loader, then 5-10 seconds later, goes blank and does the 3 vibration thing again.
Back to HBoot.
Noticed the only change was the radio oversion now says 2.15.00.11.19 now
So now my next step is to do the HTCDev method I assume?
Fastboot USB'd- phone detected by W7 just fine.
I type in 'fastboot devices' and it detects the phone and gives the serial number, so fastboot seems to be in working order.
I then type in the command 'fastboot oem get_identifier_token'
and am getting the error
and seem to be stuck here.. tried re-installing my htc sync, redid the get_identifier_token command and the same error persists.
Any suggestions?
Click to expand...
Click to collapse
What does your bootloader screen say? S-ON or S-OFF? What are your HBOOT and radio versions? Because it doesn't sound like the zip file finished installing. It should reboot once during the process, and then continue on flashing for around 10 minutes. Did it do that?
Captain_Throwback said:
What does your bootloader screen say? S-ON or S-OFF? What are your HBOOT and radio versions? Because it doesn't sound like the zip file finished installing. It should reboot once during the process, and then continue on flashing for around 10 minutes. Did it do that?
Click to expand...
Click to collapse
Yes, it did that.. went through all the checkmarks with success down to WiMax I believe was the last one.
It did reset once during the process.. I remember because I was confused, didn't know if it turned off or what, then it turned itself back on, continued with the process and installed the rest of it.
The only thing that changed was the radio version from 2.15.00.08.08 to 2.15.00.11.19 after the RUU/Hboot/PCIMG36 img flash.
Bootloader says... I'll type it all out
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00
Click to expand...
Click to collapse
Should I try re-flashing again using the .exe file, does everything seem right on the bootloader?
Okay, I think I might have put the wrong PC36IMG file directing towards 11.19
(too many files in my Downloads folder )
Lemme try again.. I see the radio version should be 12.19, which is what Captain's link provided
Okay, I used the proper 12.19 PCIMG36 file this time,
now the bootloader says
*** LOCKED (OOW) ***
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.12.19
Dec 21, 2011, 12:50:32
Click to expand...
Click to collapse
Looks like it's back to its original state
I'm assuming it works now, still updating as I type this, will try the token and the other steps to get it back down to 2.10 with s-off and back to where it should be
Thanks for the help guys.
I'll let you know if it works, I'm assuming it will and I know the steps to perform at this stage.
One more question though which got me into this original mess,
do I need to update the kernal/radio/anything in order to get an ICS rom loaded on the Evo 4G?
Or was that issue mute just because I was trying to flash an Evo V 4g/incompatible rom?
Thanks again!!
Okay.. all is going well, but there seems to be something strange going on, don't think it's normal.
After I flashed superuser, I restarted it and it once again went to the black screen with the 3 vibrations.
Took out the battery, put it back in, powered on. Booted to sprint stock.
Enabled USB debugging/disabled Fast Boot.
Then put the USB in, and the notification sound popped up on my computer detecting the phone.. but the phone itself did nothing. It isn't even charging (battery indicator at top stays still).. my settings are set to 'charge only' and 'pop-up and ask me' on connection settings.
Pressed power button, went to restart, and it powered down and again went to black screen with the three vibrations.
Took the battery out, put it back in, turned it on.. went back to sprint stock.
Plugged USB cable in again-- same thing, no pop-up on phone that it's connected, although my computer notifies me that it is.
Tried on two different computers with different USB cables, no luck.
ADB shell doesn't work, no devices found if I try it anyways.
Help
Thanks
echoedge said:
Okay.. all is going well, but there seems to be something strange going on, don't think it's normal.
After I flashed superuser, I restarted it and it once again went to the black screen with the 3 vibrations.
Took out the battery, put it back in, powered on. Booted to sprint stock.
Enabled USB debugging/disabled Fast Boot.
Then put the USB in, and the notification sound popped up on my computer detecting the phone.. but the phone itself did nothing. It isn't even charging (battery indicator at top stays still).. my settings are set to 'charge only' and 'pop-up and ask me' on connection settings.
Pressed power button, went to restart, and it powered down and again went to black screen with the three vibrations.
Took the battery out, put it back in, turned it on.. went back to sprint stock.
Plugged USB cable in again-- same thing, no pop-up on phone that it's connected, although my computer notifies me that it is.
Tried on two different computers with different USB cables, no luck.
ADB shell doesn't work, no devices found if I try it anyways.
Help
Thanks
Click to expand...
Click to collapse
Just as I suspected. Your misc partition is corrupted, causing your sd card to not be recognized, and ADB to be broken. I've been there before, and this is fixable. First, to get your SD card working, you'll need to boot into fastboot (so that your display reads FASTBOOT USB), and from the command prompt on your computer, from the folder where your fastboot.exe resides, type the following command (taken from here - thanks to Calkulin):
Code:
fastboot oem enableqxdm 0
After that completes, boot into recovery. I'd like to check and see if adb will work in recovery - that'll be easier than the alternative, which is flashing a ROM with Wireless ADB enabled, and using those commands to flash the misc partition from the computer. After you get recovery booted, type
Code:
adb devices
at the command prompt and let us know if your device shows up in recovery mode.
Tried going back into hboot.. plugged it in,
was detected, but had to re-install drivers on my w7 machine I noticed.
after i figured out that hboot usb worked, went to recovery, went to restart now.
went to black screen and noticed it is vibrating 5 times now (before it was 3)
took out battery, turned back on, back to sprint stock. still no usb capabilities within the rom.
btw my bootloader now says
** unlocked **
s-on
hboot-2.18.0001
radio-2.15.00.12.19
also,
tried going back into recovery, and re-flashed the superuser file. installed fine.
this time instead of going to 'reboot now' went to shut down.. it shut down fine. I turned it back on, turned on fine.
It only seems to be doing the black-screen and 5 vibrations when I reboot.
Tried plugging it in again to pc, checked settings - nothing.
Am confused now, not sure what's wrong
EDIT:
okay, just read Capt. Throwback's reply AFTER posting this, will give that ago. Thanks CT
Captain_Throwback said:
Just as I suspected. Your misc partition is corrupted, causing your sd card to not be recognized, and ADB to be broken. I've been there before, and this is fixable. First, to get your SD card working, you'll need to boot into fastboot (so that your display reads FASTBOOT USB), and from the command prompt on your computer, from the folder where your fastboot.exe resides, type the following command (taken from here - thanks to Calkulin):
Code:
fastboot oem enableqxdm 0
After that completes, boot into recovery. I'd like to check and see if adb will work in recovery - that'll be easier than the alternative, which is flashing a ROM with Wireless ADB enabled, and using those commands to flash the misc partition from the computer. After you get recovery booted, type
Code:
adb devices
at the command prompt and let us know if your device shows up in recovery mode.
Click to expand...
Click to collapse
I remember having to do that command because my SD card wasn't detected before I flashed the RUU and making this thread.
This is because it was very noticable my SD card wasn't being detected.. any PC36IMG file in hboot wouldn't be detected, and recovery wouldn't mount nor find an sd card. After doing that command above the SD card worked.
But anyways, ADB worked in hboot and I successfully did that command.
ADB did not work in recovery unfortunately.
Are you sure it's an issue of my sd card being detected? My misc partition is probably corrupted I assume which is giving me these errors, but SD card even before doing that above command in hboot and recovery worked fine (was able to browse my sd card/mount it.. flashed superuser on it. I only say that because before when I had to do that command to get the SD working in the beginning of all this the SD card had no access to anything at all, and in recovery would give me a can't mount mnt/mmc*** (or something like that).., that's when I googled the error and found that solution that Calkulin provided.
But i'm not sure.. what are my options now?
echoedge said:
I remember having to do that command because my SD card wasn't detected before I flashed the RUU and making this thread.
This is because it was very noticable my SD card wasn't being detected.. any PC36IMG file in hboot wouldn't be detected, and recovery wouldn't mount nor find an sd card. After doing that command above the SD card worked.
But anyways, ADB worked in hboot and I successfully did that command.
ADB did not work in recovery unfortunately.
Are you sure it's an issue of my sd card being detected? My misc partition is probably corrupted I assume which is giving me these errors, but SD card even before doing that above command in hboot and recovery worked fine (was able to browse my sd card/mount it.. flashed superuser on it. I only say that because before when I had to do that command to get the SD working in the beginning of all this the SD card had no access to anything at all, and in recovery would give me a can't mount mnt/mmc*** (or something like that).., that's when I googled the error and found that solution that Calkulin provided.
But i'm not sure.. what are my options now?
Click to expand...
Click to collapse
You're going to need to flash a ROM with Wireless ADB enabled, or manually use Terminal Emulator to flash the misc partition, as per the instructions in my "Downgrade HBOOT" thread. If you still have the flash_image and mtd-eng.img on your SD card, Terminal might be the easiest way to do it (hopefully it'll let you). If not, we'll have to go the Wireless ADB route, as I did here.
Okay, i'm not sure if it worked or not.
I su'd into terminal and did the commands.
the terminal froze though so I had to take the battery out, but that was after I pressed enter on the three commands..
I noticed in my bootloader it says *** LOCKED ***
and it also says I'm S-OFF..
Now I'm trying to flash over the 11.19 radio PC36IMG.zip but now it seems the bootloader is not detecting my sd card..
I tried the command to get sd working again. That worked okay.
I booted into recovery, and my sd card is mounted and in there I can browse my SD card contents.
But in hboot it tries to detect the PC36IMG.zip and just passes it by.
Did the misc partition commands work properly, what's messing with it now?
I'm still able to ADB/fastboot USB in hboot by the way, it just isn't detecting my PC36IMG file.
Should I try to manually do it, or am I missing something?
Also I booted into the sprint stock rom, plugged in the USB and now that functionality is working fine.. prompts up, charge only, etc.
Seems I'm almost there... :fingers-crossed:
echoedge said:
Okay, i'm not sure if it worked or not.
I su'd into terminal and did the commands.
the terminal froze though so I had to take the battery out, but that was after I pressed enter on the three commands..
I noticed in my bootloader it says *** LOCKED ***
and it also says I'm S-OFF..
Now I'm trying to flash over the 11.19 radio PC36IMG.zip but now it seems the bootloader is not detecting my sd card..
I tried the command to get sd working again. That worked okay.
I booted into recovery, and my sd card is mounted and in there I can browse my SD card contents.
But in hboot it tries to detect the PC36IMG.zip and just passes it by.
Did the misc partition commands work properly, what's messing with it now?
I'm still able to ADB/fastboot USB in hboot by the way, it just isn't detecting my PC36IMG file.
Should I try to manually do it, or am I missing something?
Click to expand...
Click to collapse
If you're back to S-OFF, you might be okay. Try flashing the 4.67 PC36IMG.zip in HBOOT again. After you do that, you should still be S-OFF, if everything is working properly, and hopefully everything else will be working too.
It's also possible that the misc partition flash was incomplete. Since you're now S-OFF, and presumably ADB is working, you should be able to run the commands over USB.
Okay, I had to put in a bigger SD card for it to detect the PC36IMG to detect- installed perfectly.
Also had to reflash amonRA recovery.
I was already S-OFF for whatever reason so yup, after that I was good to go! :good:
Booted to recovery, made a backup, wiped data/factory reset, an flashed an ICS rom. Just booted up, everything is working great
Thanks a bunch everyone (esp Capt. Throwback) for getting this resolved quick and painlessly
Am very relieved to get this working once again as normal, wasn't sure if I would be able
Thanks again!!

[Q] HTC DHD stuck on htc sreen logo

Hello guys
I hope you're all okay
My htc desire hd is stuck on htc logo screen and i read lots of your posts about this topic but I couldn't manage to find a solution.
I tried flashing rooting and other stuff bot none worked.
Please tell me what to do
PS: I cant acces to settings to tick the Usb Debugging and I dont have Clockworkmod installed
Regards
If you can access the phone via adb or hboot (press Vol-Down + Power) then try to flash Clockword Mod and work your way from there (wipe everything, flash new ROM and so on). These instruction are for the EVO but hboot should be almost identical on every phone I guess: How to manually flash a recovery image (via fastboot OR from SD card)
I tried it believe me I tried via SD card and via Commang prompt too but both of them FAILED
Thread Closed​
Please only post a topic once! You were correct the first time, it goes in Q&A http://forum.xda-developers.com/showthread.php?p=42946711#post42946711​

Categories

Resources