Develop Bugs

[Q] Bricked my Defy - Any chances of bringing it back?

Hi all.
I know there are many threads about this, but there was no solution for my problem anywhere out there
Yesterday I got my Defy back from repair (broken speaker) and switched it on - I wondered why there is the vodafone 360 (I'm in germany) logo coming up, because it was not there before I sent it to repair... I immediately switched it off, to flash the de-blurred version (JRDNEM_U3_2.34.1) from and-developers.com which worked on the device before, without any problems.
After flashing it with RSDlite and got a PASS, it did not reboot - but it was still recognized by the Computer (USB-connecting sound on Windows) and RSDlite! So I tried to flash it again, but the problem persists. I already tried the McGyver-USB-cable-method and various battery-out-pressing-button-battery-in-again solutions... no chance. After a few hours testing, the phone stopped being recognized by the computer, too! I did not flash again and the white LED is still lighting up, when I plug the cable into the computer.
I left the phone with the USB-cable plugged into the computer over the night (6 hours), hoping it will charge (assuming I got the battery drained by testing too much) but the situation is still the same this morning.
I think I REALLY bricked it and have to send it to the shop, which also fixed the speaker (which I did not get to test yet ) - I would like to see a different approach, because I know I will get that ****ty vodafone 360-ROM on my phone again
Any help is appreciated.
Thanks,
hitti

They have updated your software to 2.51 when they gave it back. It is foolish of you not to even check before flashing it. Flash the 2.51 or chinese froyo sbfs.
Sent from my MB525 using XDA App

Yes, that's right - I should have checked it before.
I can't flash anything, because my computer does not "see" the phone anymore
Edit:
I sent it back to that shop, which repaired it before - hoping they get it fixed.

But u cud just flash 2.51. Well, anyway.
Sent from my MB525 using XDA App

Turn off your phone (by pulling battery if necessary). Press and hold the volumn up button and turn on the phone to open the boot loader page. Then plug in the usb cable and flash the 2.51 rom.

ABC_Universal said:
Turn off your phone (by pulling battery if necessary). Press and hold the volumn up button and turn on the phone to open the boot loader page. Then plug in the usb cable and flash the 2.51 rom.
Click to expand...
Click to collapse
ABC is right..the problem is you might just get a blank screen but it gets detected by RSD. This happened to me before and thought I bricked my Defy, which almost made me shat bricks! But since you sent it in already..hopefully they fixed it if not, you can do it yourself.

http://forum.xda-developers.com/showthread.php?t=884105
download and flash....it worked for me...

I tried all kinds of combinations of pushing buttons and putting batteries in and out - it was not recognized by the computer or RSDlite at all. Thanks for helping, anyway

Maybe the battery is discharged
Do you know any person who has a Defy to let you the battery, and then reflash?

[Q] How to unbrick my dead boot Desire HD

Hey Geeks,
I need some help and I bet that you could help me!
I ve used the search engine to not post anything someone did before. But there was nothing that could help me.
First I ll describe you what I ve done to brick my Desire HD:
My phone is rooted, S-OFF, ENG S-OFF with CM 7. After installing the new ROM I wasn`t able to install anything from the amrket. So I ve looked up for the reason and tried different things to sovle it. I ve read somewhere that it could help to add a partition to my SD-card. So I ve used the ROM Manager to format my sd card and create a partition.
ROM Manager asked me if I am sure bla bla... you know what I mean. After giving ROM Manager su-permission my phone shuts down. From there on nothing happened. (and still no patition on my sd card).
It`s not reacting to the power button, to the volume-down + power button nor is blinking my LED when I connect it to the USB-Port. Seems like it`s out of energy (but my akku was charged before I ve stzarted with the partition of my sd card).
I ve tried to put out the akku for several minutes. No reaction.
Removing SD-Card before pushing the power button: No reaction
Plug in to charge battery without hitting any button... some hours later: still no reaction
Formating SD-Card: No reaction
Then I ve tried to install the RUU 1.32., saved it on my sd-card, plugged phone in to start... my pc is not detecting my phone.
And now I am helpless

So it doesn't boot at all? Because if it doesn't, you are pretty much screwed...no boot -> no access -> no fix, but I don't believe that you can screw your phone up that badly by partitioning your sd-card.
Unless someone has a fix for this (and the problem doesn't solve itself somehow), your best bet is to send your phone to HTC for a repair, they probably won't charge you anything if it is still covered under warranty, since they can't really check for any modifications if it doesn't boot. It is probably a hardware problem any way.

frosty_ice said:
So it doesn't boot at all?
Click to expand...
Click to collapse
Nope, nothing happened.
frosty_ice said:
it is still covered under warranty, since they can't really check for any modifications if it doesn't boot. It is probably a hardware problem any way.
Click to expand...
Click to collapse
THIS makes me happy, but I would prefer any other solution.

Sleipnir1985 said:
Nope, nothing happened.
THIS makes me happy, but I would prefer any other solution.
Click to expand...
Click to collapse
The fact that it doesn't boot at all is a good thing for send it back for warranty purpose. But if you formated your sd-card, you lost root anyway. You have to make a backup of your SD-Card before you format/partition it, and then copy everything back.
And your initial issue was maybe due to an outdated version of Gapps...

why should he loose root if he formats his sd-card? you have root even without an sd-card.
if nothing helps to get your DHD back to life, you probably have to send it to HTC. but I think it's covered by warranty since it's (probably) a hardware fault.
btw, i think i've seen a thread like this somewhere here yesterday... i'll have a look and post a link if i find something
Edit: found it! http://forum.xda-developers.com/showthread.php?t=1013582&page=2
look at page 2. there are some people with the same problem, but there is no solution yet.

But you do have CWM-Recovery on it don't you?
And if, can you get into Recovery?
Had similar Problems, once...
But my phone only showed the white HTC Logo and that was it....
What i did was the following... flashed Revory via Fasbootload from Computer...
Next, i formatted my sd card via computer and copied a new Rom.zip onto it.
In my Case, leedroid.
Next, i just flashed it and it happened to work again, luckily.

he can't even boot into the bootloader.

Flussen said:
why should he loose root if he formats his sd-card? you have root even without an sd-card.
if nothing helps to get your DHD back to life, you probably have to send it to HTC. but I think it's covered by warranty since it's (probably) a hardware fault.
btw, i think i've seen a thread like this somewhere here yesterday... i'll have a look and post a link if i find something
Edit: found it! http://forum.xda-developers.com/showthread.php?t=1013582&page=2
look at page 2. there are some people with the same problem, but there is no solution yet.
Click to expand...
Click to collapse
Hardware fault or not, rooting voids warranty. Let's hope that they can't inspect the internal memory.
Anyway, is the phone reacting to connecting to a proper charger (try to leave it plugged in for a couple of hours even if the LED doesn't light up)? The other thing you could try is to find a friend with a DHD and swap the batteries just to try if somehow you managed to kill your battery.

hi Sleipnir1985,
go back to your shop,
when did you buy it? they must take it for service, or they give you new one.
it is only best solution in this case
if you take battery out for 5! min, then plug it in and hold volume down then push power button - nothing happened, this is it, the end...
cheers/

tkolev said:
Hardware fault or not, rooting voids warranty. Let's hope that they can't inspect the internal memory.
Click to expand...
Click to collapse
yes, but HTC replaces your phone if it's a hardware and not a software fault. a friend of mine got his DHD replaced with eng hboot, radio S-OFF, custom rom and so on. and lots of people here on XDA also.

Here`s another mate with the same problem.
I am going to give my HTC to the shop this evening. Push your thumbs that I ll get a new one

here is an other brick htc hd g10
cause by rom mananger.

hzjinjie said:
cause by rom mananger.
Click to expand...
Click to collapse
That was a bug with an older version of ClockWorkMod Recovery - http://forum.xda-developers.com/showthread.php?t=1043160 and has now been fixed.

Hi all,
My DHD is bricked (I think).
When I try to access to the recovery the phone vibrate 3 times and nothing on the screen
When I send : "adb devices" it replies HT0xxxxxxxxxxx recovery.
The HBOOT driver is installed and in the peripheral manager my DHD appears : android USB devices
What can I do ??
Help me please and sorry for my bad English !!

Welcome to XDA.
Please start a new thread on this issue.

this Problem same my DHD i'dont know my DHD die or not .
If You repair your DHD ok pls share with me.
I'm live in Viet nam.
Thanks.

datcvn said:
this Problem same my DHD i'dont know my DHD die or not .
If You repair your DHD ok pls share with me.
I'm live in Viet nam.
Thanks.
Click to expand...
Click to collapse
Same problem here. It is out of warranty date.
I am a Vietnamese too.

Help meee. Htc desire hd ace
my phone is brickeo anyone know what I can do? No power or bootloader or CWM.
I was root, but returned to its factory version of AT & T gingerbread rom. I did not like and wanted to go back to being root but not knowing how I Birck the cell. I need a solution please

germancalvobolivar said:
my phone is brickeo anyone know what I can do? No power or bootloader or CWM.
I was root, but returned to its factory version of AT & T gingerbread rom. I did not like and wanted to go back to being root but not knowing how I Birck the cell. I need a solution please
Click to expand...
Click to collapse
Please tell me that you did not factory reset via bootloader
Sent from my ATRIX HD using Tapatalk

Help meee. Htc desire hd ace, htc inspire 4g at&t
marknoll said:
Please tell me that you did not factory reset via bootloader
Sent from my ATRIX HD using Tapatalk
Click to expand...
Click to collapse
Thank you. I did as he told me the official website of HTC, step by step. When I finished the phone worked well, but then I got bored of gingerbread quiser again become root, and that's when my phone brick. Now not light, it does not go bootloader fastboot, CWM, nothing. Only if I turn volume + volume - and power, virbra 7 times and LED lights green battery and nothing more. It does nothing, it is a brick
htc. com/ us/ support/ htc-inspire-4g -att/ news/
RUU_Ace_Sense30_S_Cingular_US_3.20.502.63_Radio_ 12.69c.60.29U_26.09.13.17_M_release_ 335423_ signed.exe

[Q] Yet another bricked Defy: no response at all

Disclaimer:
I have the same problem this guy have:
http://forum.xda-developers.com/showthread.php?t=1036327
But no one in the thread was able to understand him, so I'm trying to open a new thread to organize the thoughts (there are too many people with too many problems posting there).
What happened:
I have a 1-month-old Defy. On the 2nd day I already had it rooted, running froyo (with Pays ROM), overclocked, undervolted and all this stuff. Three days ago, suddenly, it started to FC apps randomly. So I wiped. Then it became stuck on M logo. No big deal.
I tried then to reflash the SBF via RSDLite, but for some reason I only had the previous SBF (3.4.2-155-2) and my phone was running on 3.4.3-11. Don't know if it has downgradeability issues, but I couldn't flash it. It threw some checksum errors in the process and wasn't able to finish the process. Then my phone became "Code Corrupt". I was still able to see it in RSDLite. No big deal.
I didn't know the battery wouldn't charge in the bootloader screen, so I quickly ran into a "Battery Low / Cannot Program" state. It was written in the screen what happened. I knew what I had to do. No big deal.
I read about the MacGyver method, but prefered instead to use a universal charger to charge my battery. Was charging all night, seem to work on other defy (tested it later). But, now, my phone makes no response to battery insertion. Not even power+vol up, nothing. No white led, no bootloader, no code corrupt, no nothing. Ok, that's a big deal.
If I connect it to USB, nothing happens. No driver instalation, no device recognized, no RSDLite, no bootloader, no white led. Nothing.
The only response I have from the phone is: if I pull the battery and put it again while connected to USB, the computer will make an USB connection sound, then 2 seconds later, it makes an USB disconnection sound. If I open the device manager, it shows the Motorola Device for 2 seconds (OMAP something) and then it desapears. So I'm not able to see it in RSDLite.
I tried even to power up the phone with the MacGyver-crafted USB cable (with and without battery inserted together), but the computer response is the same. That is the only thing that makes me believe that my Defy isn't entirely dead. But isn't much useful after all.
Hope I explained it well. I'm one of those guys who doesn't speak english well, so I hope you guys understand me . Thanks in advance.

I would really like to be helpful, but it looks, that you tried everything. Only one thing. Try to check the battery voltage and if you can, try another battery in your phone. The charger could broke your battery, even if it one time worked in another phone.

Try reinstall usb drivers, rsdlite, different usb port, and different pc.

@peetr_
The battery seems to still work, as putting it in the phone makes it to be recognized (for 2 seconds) on the PC. Also, the phone seems to get a little warm while with the battery.
@ABC_Universal
I tried. Installed all the drivers in another PC I have here and tried the same methods I said before. Same results.

If you're planning to dumb the phone into a dumb site.. let me know when and where...
Ok... you need to narrow down the possibility here by putting another full charged battery and see if the phone do get connected status via PC. External charger might just toast your battery if you read carefully your entire story back starting from this line "I didn't know the battery wouldn't charge in the bootloader screen, so I quickly ran into a "Battery Low / Cannot Program" state. It was written in the screen what happened. I knew what I had to do. No big deal."
External charger might giving out totally different voltage/current rating from the defy own charger.

im having the same issue, did you solve it?

im having the same issue, did you solve it?

try putting a different Defy's battery, doesn't work just give it for RMA... you'll get a replacement. looks like a hardware problem to me...

You have tried the McGyver-trick?

I tried using another battery in it and didn't work. I was far from a computer when I tried, so I didn't check if I was able to connect it to PC (even if the screen was totally black). But if it was a battery problem, I was expecting at least the bootloader to appear, but still nothing happened.
I took it to RMA two weeks ago. Here in Brazil they take too long to return it =/. Still waiting.
skattegat: I tried. With and without battery inserted together. Both cases, I was only able to listen the USB connection start and end, 2 seconds later. I know the cable was working because even without battery, when I touch the wires, I was able to listen the usb connection sound.

Ok. At least you have the time now to enjoy your sunny weather in Brazil...

RSD lite sucks... Well it doesn't suck but it refuses to work anymore no matter what I do!
Use sbf_flash in linux and it should do the trick! PM me if you need help

First flash the sbf. Then enter stock recovery and do the recovery from there. Flashing does not wipe cache. But after the flash the recovery will do the wipe automaticly.
Sent from my MB525 cm7quarx

Just a follow up:
My phone returned today from the warranty. Is fully working now, but I noticed the IMEI has changed. So I guess they changed the entire circuit.
It's not helpful for those who have the same problem, but I'm happy again

i have problem too..
I made a mistake in ROM CM7: I "install the 2nd init". and the results stuck on the boot logo .. : (
I finally went into the boot loader, then flash again use 3.4.2_177 SBF-005_NORDIC (do not wipe the data) .. remain stuck at the boot logo. and I try to use flash SBF-Stock.UKTmobile 3.4.3_11 (not wipe the data) and the results .... still stuck>> it's just an animated logo appears only.
AND THEN ---------------------------------
for this case:
I want to get into stock recovery:
1. defy turn off, turn the power button + volume down (hold a while)
2. logo appears>> android +! (the menu does not appear anything)
3. and I do not know anymore what should I do: (
please help me Quarx
thanks before

Don't see why you should ask the same question in multiple topics. My answer still is the same:
If pushing the lower right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App

Fotogravin said:
Don't see why you should ask the same question in multiple topics. My answer still is the same:
If pushing the lower right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
it's work..!! sorry i ask same question on other thread.
i'm so confuse
makasih gan

hey omneon are you able to solve your problem..plz help me man mine defy is stuck on m logo. same problem like your..

Vibrates 7 times

I just rooted my HTC Desire and installed CM7 on it (loved it on my HTC Legend). But suddenly today, after I turned Wifi on, it started rebooting all the time, couldn't do anything to stop it. I thought "Hey, there was the radio flash thing in the tutorial that I didn't do yet, I'll try that out" so I flashed the radio. Then I chose reboot system, but it just booted to a logo with an android coming out of a trash can, and looked kinda stuck there. So I took out the battery and plugged back in. Now if I try to turn it on, it'll just vibrate 7 times - no picture or anything. Also there's no LED when I plug it to the charger.

I had those 7 vibrates too.
Happened after i flashed the cm7 hboot over my stock hboot while trying to enter recovery. After i re-flashed my recovery using fastboot, everything worked again. What happens if you try to power up while holding down vol- ? Did you use fastboot or your phones recovery mode to install the radio?

I am not able to start in recovery or anything. I tried vol. down + power and back + power and no matter what I try, it just vibrates 7 times. I used the recovery mode to install the radio.

You could try to connect your phone via usb and check if fastboot discovers your device. If yes, flash hboot and recovery using fastboot. If not, well... i dont have a clue. Sorry :/

Computer discovers nothing when I plug in the phone.

Bad news when u pulled battery u interrupt the process n u now have a bricked device I would b very surprised if u managed to do anything
Pulling battery when doin a radio update is a BIG NO NO I'm sorry but ur stuck with a 400+ mirror now
Please look at this link
http://www.google.co.uk/m/search?site=images&client=ms-android-htc&hl=en&gl=uk&source=mog&aq=&oq=&aqi=&fkt=&fsdt=&cqt=&rst=&htf=&his=&maction=&q=android+radio+update#i=95
If that the image u saw when u pulled battery ur defo screwed
The Best Things Come To Those Who Wait

Your link doesn't work.. I found a picture of what was showing when I unplugged the battery, but I'm not allowed to post links to other sites on these forums yet.

U need to copy the link for some reason its not showing up
Pm the link u have
The Best Things Come To Those Who Wait

Inrego said:
Your link doesn't work.. I found a picture of what was showing when I unplugged the battery, but I'm not allowed to post links to other sites on these forums yet.
Click to expand...
Click to collapse
inrego
yes the image u just sent me is correct
the image showing would of ment it was installing the radio and because u pulled battery u have corrupt the flash and unfortuntly bricked ur device
i will look for a solution on the net but im not sure if ill find anythink sorrry

Inrego said:
Your link doesn't work.. I found a picture of what was showing when I unplugged the battery, but I'm not allowed to post links to other sites on these forums yet.
Click to expand...
Click to collapse
heres a few thread about some pulling battery on radio flash
http://android.modaco.com/content/g...m/304368/can-the-nexus-one-be-bricked/#entry0
http://android.modaco.com/content/h...50/help-cannot-turn-on-after-flash-new-radio/
i cant find anythink about fixin the issue sorry

Well thanks alot for trying. At least it seems like it shouldn't be too hard to get a replacement unit..

Inrego said:
Well thanks alot for trying. At least it seems like it shouldn't be too hard to get a replacement unit..
Click to expand...
Click to collapse
all depends on if ur on warranty if u have receipt and warranty then all is ok with out them u stuck basically
sorry couldn't help more hopefully lesson learnt playing with radio is risky business

Yea got warranty and reciept and all that, so np there

Inrego said:
Yea got warranty and reciept and all that, so np there
Click to expand...
Click to collapse
nice one then just make up a bull**** reason ok well hope u get a replacement

Wait a minute...
Inrego said:
Well thanks alot for trying. At least it seems like it shouldn't be too hard to get a replacement unit..
Click to expand...
Click to collapse
For the record to help some of you out who ended up here Googling: I had a similar issue. My HTC Desire SV did not boot, and when charging, only had an orange flashing light, and the phone vibrated 7 times. I did 2 things that got it back up:
1) left the phone off for say 10 minutes (I read about overheating issues in general, although the phone did not feel hot).
2) removed the battery for a couple of minutes.
VERY IMPORTANT: for step 2: make sure to have the battery removed long enough to drain internal charge. I removed and installed the battery in a second or so at first, and still the phone did not boot. After leaving out the battery long enough, it booted again. It appears to me that the issue in my case was a rather big internal charge capacity which kept internal state (memory and/or CPU?) from booting. Hope this helps...

[Q] Dead phone after update, any way to bring it back

Hi guys, need very quick help from you, as I think I have bricked the phone which suppose to be a Christmas gift for may son. I was trying to revert phone from root and custom rom to stock. I've downloaded older OTA update (one of very first ones with android 2.2) an installed it in bootloader. Phone booted fine, and I went for official update. It showed to me there is update available to android 2.3. I have downloaded it and phone rebooted in to update mode. After progress bar gone to the end it disappeared and phone stayed in that update mode (logo with phone and green arrows shaped it to circle) for nearly half an hour. I though, some thing had to vent wrong so I decided to turn off phone, but power button gave no effect, so I pulled battery out for few seconds. After I have putted it back phone never turned on again. I mean is completely not responding. Pressing power button for even minute doesn't wake it up, it is not possible to go to the bootloader. There is no characteristic vibration when it turns on. Basically it behaves like there is no battery in socket but there is, and it is fully loaded as I charged it before updating. When phone plugged to AC or computer LED is not lighting as well whatsoever.
Please, can any one help with this one? I in rush as phone is a Christmas present for my son who lives in Italy and I supposed to ship this today to make it arrive b4 Christmas. This is why I can not spend to much time on searching forums.
Thank you

Check battery pins
hedeon said:
Hi guys, need very quick help from you, as I think I have bricked the phone which suppose to be a Christmas gift for may son. I was trying to revert phone from root and custom rom to stock. I've downloaded older OTA update (one of very first ones with android 2.2) an installed it in bootloader. Phone booted fine, and I went for official update. It showed to me there is update available to android 2.3. I have downloaded it and phone rebooted in to update mode. After progress bar gone to the end it disappeared and phone stayed in that update mode (logo with phone and green arrows shaped it to circle) for nearly half an hour. I though, some thing had to vent wrong so I decided to turn off phone, but power button gave no effect, so I pulled battery out for few seconds. After I have putted it back phone never turned on again. I mean is completely not responding. Pressing power button for even minute doesn't wake it up, it is not possible to go to the bootloader. There is no characteristic vibration when it turns on. Basically it behaves like there is no battery in socket but there is, and it is fully loaded as I charged it before updating. When phone plugged to AC or computer LED is not lighting as well whatsoever.
Please, can any one help with this one? I in rush as phone is a Christmas present for my son who lives in Italy and I supposed to ship this today to make it arrive b4 Christmas. This is why I can not spend to much time on searching forums.
Thank you
Click to expand...
Click to collapse
After reading what you said i think that you placed battery wrong. Check the pins inside the phone with battery pins.

whiperhack said:
After reading what you said i think that you placed battery wrong. Check the pins inside the phone with battery pins.
Click to expand...
Click to collapse
That was my first idea too but, no m8, battery is placed ok....

Try pressing volume down+power button for a while then leave the power button while still pressing the voulme key. You should boot into the bootloader.

if4ct0r said:
Try pressing volume down+power button for a while then leave the power button while still pressing the voulme key. You should boot into the bootloader.
Click to expand...
Click to collapse
Tried that too, still dead

Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.

if4ct0r said:
Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.
Click to expand...
Click to collapse
I understand I should not be worried that all of these RUU's are listed as for model: ACE?

Not at all. 'Ace' is the codename HTC gave to Desire HD/Inspire. Just choose the RUU that fits your location(i.e. WWE stands for WorldWide Edition).

if4ct0r said:
Not at all. 'Ace' is the codename HTC gave to Desire HD/Inspire. Just choose the RUU that fits your location(i.e. WWE stands for WorldWide Edition).
Click to expand...
Click to collapse
OMG! I was previously looking for stock roms and everytime I ended up on that site from your link I was annoyed that someone is giving a wrong link to roms for wrong phone. Silly me!
I am downloading right now.

if4ct0r said:
Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.
Click to expand...
Click to collapse
No it says phone not connected (error[170])

hedeon said:
No it says phone not connected (error[170])
Click to expand...
Click to collapse
My idea is to double check again the battery position in the socket and if it is ok try to leave it 5 minutes alone on the AC adapter. If this will not give good results, go to the appropriate HTC representative.

when you connected it to your computer... did it ask you to install qload drivers?
if not, go into device manager on your computer, then plug in your phone. If you see an unknown device that shows as qload something or other, then sorry to say, its bricked.
The only way to recover it now is via jtagging or replacing the mainboard (which generally is what they do when you send it in for warranty repair)

whiperhack said:
My idea is to double check again the battery position in the socket and if it is ok try to leave it 5 minutes alone on the AC adapter. If this will not give good results, go to the appropriate HTC representative.
Click to expand...
Click to collapse
Yes, I thought about it as phone behave like it has no power at all. But this is not the case, as I have been flipping that and another battery in every possible position. And I know which one is correct as I can see where pins are in battery pocket. I left it alone under charging and other time with no battery at all hoping that will hard reset phone. No effect at all .
JSLEnterprises said:
when connected to your computer... did it ask you to install qload drivers?
if not, go into device manager on your computer, then plug in your phone. If you see an unknown device that shows as qload something or other, then its bricked, sorry to say
Click to expand...
Click to collapse
I had drivers previously installed. But I am not entirely sure are we talking about same thing as I don't know what QLOAD is. Anyway comp doesn't see any recognised or unrecognised device that could be my phone...
I am not worrying about damn phone as if it is hard bricked tech guys in service will not probably spot that it was rooted. So they will replace, or if not I will go to insurance company. Problem is it takes to much time, I wont make it b4 Christmas.
Thank you guys,
anyone has some other ideas? Please...

desperation bump

Sorry.. It really seems to be beyond software-repair, If it cannot boot in the bootloader or be recognized by PC there's really not much we can do. We need the device to start in some way.
Although one last thing that we haven't tried and can try is to see if it can be accessed via adb or fastboot. (Although I highly doubt it since the RUU also wasn't working).
I've attached the adb and fastboot files required to test that. Extract it, double-click on StartHere.bat and type "fastboot reboot" or "adb reboot". If it returns an error citing device not found then this too has failed.
(This probably wont work.. desperate action)
Another silly thing that might be tried is to try to put your phone on charging via a charger(not USB via PC) and then try to switch it on. Try normal switching, switching on to bootloader(volume down press)...
If these don't work then you really should give it to the repair center.. you're right that they wont probably realise that it was rooted and would probably change the main board.

if4ct0r said:
Sorry.. It really seems to be beyond software-repair, If it cannot boot in the bootloader or be recognized by PC there's really not much we can do. We need the device to start in some way.
Although one last thing that we haven't tried and can try is to see if it can be accessed via adb or fastboot. (Although I highly doubt it since the RUU also wasn't working).
I've attached the adb and fastboot files required to test that. Extract it, double-click on StartHere.bat and type "fastboot reboot" or "adb reboot". If it returns an error citing device not found then this too has failed.
(This probably wont work.. desperate action)
Another silly thing that might be tried is to try to put your phone on charging via a charger(not USB via PC) and then try to switch it on. Try normal switching, switching on to bootloader(volume down press)...
If these don't work then you really should give it to the repair center.. you're right that they wont probably realise that it was rooted and would probably change the main board.
Click to expand...
Click to collapse
Sigh... I got "waiting for device" forever in CMD... As you said, it's dead. Gonna send it to HTC in Monday...
Thank you all, appreciate your time

Hello hedeon,
I have the same experience today, as you state in the first post in this thread.
Did you, and how solve the problem?
Is there people with the same problem? This morning I receive notification about system update for my HTC Desire HD. The rest is exactly same problem from the top of this story = death + death + death.....

The problem is that you PULLED THE BATTERY WHILE UPDATING! Have some paitience. I switched on my DHD after 3 months and it needed updating. Takes around 20 mins to complete update
Sent from my HTC Desire HD A9191 using xda premium

GuyInTheCorner said:
The problem is that you PULLED THE BATTERY WHILE UPDATING! Have some paitience. I switched on my DHD after 3 months and it needed updating. Takes around 20 mins to complete update
Sent from my HTC Desire HD A9191 using xda premium
Click to expand...
Click to collapse
May be, but updating started with downloading, then resetting, and then green line was growing up to 1/3 of total size, and at that size stay more then 20 min. Then I try to to push every button, and every combination of buttons, and after 10 minutes more I had pull battery out.
Was it too impatient ?

What was the Android version before you rooted if you can remember and which tool did you use to root?
From what you wrote earlier, it asked you for a 2.3 update which means you probably flashed a Froyo RUU as stock, to bring the phone back to stock ofc.
However, if your DHD came with stock Gingerbread, flashing a Froyo RUU will most definitely screw the phone. I'm not sure if it's beyond repair atm or not, but if that was the case, even if you didn't mess with the battery, chances are the phone would never boot anyway.
Look into AAHK thread, I think there is a good how to there.