Develop Bugs

Possibility of bricking & how to avoid it..

Is anyone manage to brick the phone already?
How likely/ or stupidity you need to actually bricking the phone?
What is a NO NO and how to avoid it?
That's the question.. thanks!

Main thing is read as much as you can before you do any changes, it helps to check what few sites say.
When I rooted my phone I could not get it to run the update part, tried time and time again, one site said "rename the file to update.zip and paste it" then I read on another site to just call it update as it is already a zip file.....and then it worked, small bit of detail like that stopped it working to start with so if I was you I check a few sites and get all the info you need, but also as many would say if you are that unsure dont take the risk and wait for samsung updates with Kies.

voodoochild2008 said:
if you are that unsure dont take the risk and wait for samsung updates with Kies.
Click to expand...
Click to collapse
Kies actually failed to update my phone, I have the Korean Galaxy S SHW-M100S, and it showed an update was available. So, I thought I was bricked for about 30 mins, kept trying to get it to work itself out of the problem in recovery mode, after about 4 tries (1 reboot of Windows, plus changing USB ports and 2nd try with this static new config) eventually it did, thank God.

Do not remove usb while in the middle of flashing with odin
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****

amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
I was gonna say something along the lines of a smart ass, but I can't. That sucks.
why would you do a battery pull?

madjsp said:
I was gonna say something along the lines of a smart ass, but I can't. That sucks.
why would you do a battery pull?
Click to expand...
Click to collapse
I've been flashing all night and wanted to do it "right" this time....realized my SIM and SD card were still in there mid-flash so wanted to pull them and start clean..........................
Yeah....don't do that.
Guess I'll be that "guy" paying a visit to the local AT&T shop tomorrow....
Luckily I'm w/in my 14 days since getting it....

delete. ......

amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
I've removed the cable half way and rebooted, and it was fine..
You simply remove the USB cable, battery again, put the battery in, and you'll be able to get to downloader mode.
The phone seems to have a component that ODIN doesn't touch that is read-only that handles download mode. Most hardware devices tend to have safeguards. I haven't confirmed this, but I've noticed the same applies to NAS devices (which tend to have a special redboot which uses tftp).
I have still yet to have seen any evidence of anyone permanently bricking their phone, but I've seen a few cases of "oops, got it working again".
Remember, Samsung are eager to reduce their support costs, and failsafe's are cheap and easy to add.

yes, the odin doesn't touch the 'bootloader' , or the small piece of code that enable the download mode, so there's no way you can brick the phone.
I have tried to repartition the phone while flashing firmware that has nothing except the csc data (i.e. no kernel, no factory rfs, etc) and the flash procedure went succesfully but in actual fact, my phone contains a new set of partitions that contain nothing except the small csc data.
and i still able to reflash, although I must make sure that the phone is totally shutdown (i.e. take out battery, let it stay for awhile before putting back)

andrewluecke said:
I've removed the cable half way and rebooted, and it was fine..
You simply remove the USB cable, battery again, put the battery in, and you'll be able to get to downloader mode.
The phone seems to have a component that ODIN doesn't touch that is read-only that handles download mode. Most hardware devices tend to have safeguards. I haven't confirmed this, but I've noticed the same applies to NAS devices (which tend to have a special redboot which uses tftp).
I have still yet to have seen any evidence of anyone permanently bricking their phone, but I've seen a few cases of "oops, got it working again".
Remember, Samsung are eager to reduce their support costs, and failsafe's are cheap and easy to add.
Click to expand...
Click to collapse
I thought in the Big FAQ, it said... do not disconnect the usb-cable but to remove the battery if want to interrupt it...
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)

amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
Similar happened to me,although I didnt pull the battery, the phone just disconnected halfway through the flash.
Had half hour of panic,where I thought it was bricked.
Had to do a few battery pulls,restart PC a couple of times and mess around with different USB ports,but finally got it working.
Have flashed a 3 times since without a problem.

chluk2425 said:
I thought in the Big FAQ, it said... do not disconnect the usb-cable but to remove the battery if want to interrupt it...
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
Click to expand...
Click to collapse
That means you shouldn't do any of those things! So don't disconnect usb, don't remove the battery and don't interrupt the process.

zenkinz said:
yes, the odin doesn't touch the 'bootloader' , or the small piece of code that enable the download mode, so there's no way you can brick the phone.
I have tried to repartition the phone while flashing firmware that has nothing except the csc data (i.e. no kernel, no factory rfs, etc) and the flash procedure went succesfully but in actual fact, my phone contains a new set of partitions that contain nothing except the small csc data.
and i still able to reflash, although I must make sure that the phone is totally shutdown (i.e. take out battery, let it stay for awhile before putting back)
Click to expand...
Click to collapse
Are you sure that flashing (through ODIN) in any case never touch that "Download Mode" piece of code ? Even you select all the options in ODIN ?
Can anyone confirm this ? Actually I want to play with Kernel and RFS (have some ideas to try) but afraid of full bricking. So if this download mode is always present then I can play with it without any problem.
Waiting for response.

amerikian said:
I've been flashing all night and wanted to do it "right" this time....realized my SIM and SD card were still in there mid-flash so wanted to pull them and start clean..........................
Yeah....don't do that.
Guess I'll be that "guy" paying a visit to the local AT&T shop tomorrow....
Luckily I'm w/in my 14 days since getting it....
Click to expand...
Click to collapse
Believe me! you can still access the download menu

The bootloader is almost always writeprotected and cannot be overwritten. You would probably have to connect a cable to some internal port like Jtag to be able to reflash the bootloader section. Atleast that is the case in 99% of all bootloaders. Im very certain that you cannot cripple the bootloader.
Sent from my GT-I9000 using XDA App

jackiechan8 said:
That means you shouldn't do any of those things! So don't disconnect usb, don't remove the battery and don't interrupt the process.
Click to expand...
Click to collapse
gosh man, thanks correcting me but if that's the case, what should i do if it doesn't reboot by itself?

take out the battery, wait for 30 to 60 secs, put the battery in and start phone with vol down + menu + power

Don't disconnect the usb or do anything else while flashing!!!
I removed the usb cable when it started flashing (i thinked it was stuck, happens sometimes), and since it does not boot anymore. I press the power button, volUp + home + power, volDown + home + power... nothing happens.... it's dead, doesn't turn on at all...

after all i have read i think it's almost impossible to brick the sgs since you always get back into download-mode. the only case i read where i believe that it's a goner is flashing with the wrong (in this case the at&t) odin version. those guy's just got a white sreen with at&t logo at boot. they didn't get into download mode any more because the button mapping on the captivate is different ... so thats really bad luck, dont't try that at home

jodue said:
after all i have read i think it's almost impossible to brick the sgs since you always get back into download-mode. the only case i read where i believe that it's a goner is flashing with the wrong (in this case the at&t) odin version. those guy's just got a white sreen with at&t logo at boot. they didn't get into download mode any more because the button mapping on the captivate is different ... so thats really bad luck, dont't try that at home
Click to expand...
Click to collapse
well, mine doesn't boot at all, and i flashed (technically not, because i removed the usb cable at the very start) with the RIGHT odin version
Maybe if it fails when flashig sbl (secondary boot loader ) you can't go into download/recovery mode...

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

Desire un-responsive - Please Help

I've seen a couple of threads such as this with no real solution.
I've been happily using my Desire for months without changing roms or whatever (CM7 and s-off) until last night I opened my Dolphin browser and before it loaded the homepage it froze, totally un-responsive. I took the battery out, and to my horror, it was still totally un-responsive. Wouldn't respond to pressing the power button, pressing volume down+power, charger, or usb.
The battery at the time was about 50%, I've had the battery in and out about 100 times now, trying things like leaving the battery out and then trying again, keeping it on 'charge' for a while and trying to get it booted, with no response at all.
This was until an hour ago, I hopefully tried to boot the phone after the battery, sim and sd card had been out for a while and I got a vibration, and then it hung on the flash screen. I had to remove the battery, then tried to boot again with no response, so I left it a while again, put the battery in and got to the bootloader, thought I'd get into recovery and try a nandroid or something, only when I selected recovery it hung on the slash screen again.
Does anyone have any ideas what this is, or how this could be fixed? Damn I hate not being able to use my previously awesome phone!
I apologise for the long post, I'm just trying to give a good explanation of things. I just couldn't see the problem being my battery, only the day before the problem I was telling my friend how great the battery life on my phone is, and that he should give rooting a go and use CM7, this probably hasn't swayed his decision to root his phone.

stevoh84 said:
I've seen a couple of threads such as this with no real solution.
I've been happily using my Desire for months without changing roms or whatever (CM7 and s-off) until last night I opened my Dolphin browser and before it loaded the homepage it froze, totally un-responsive. I took the battery out, and to my horror, it was still totally un-responsive. Wouldn't respond to pressing the power button, pressing volume down+power, charger, or usb.
The battery at the time was about 50%, I've had the battery in and out about 100 times now, trying things like leaving the battery out and then trying again, keeping it on 'charge' for a while and trying to get it booted, with no response at all.
This was until an hour ago, I hopefully tried to boot the phone after the battery, sim and sd card had been out for a while and I got a vibration, and then it hung on the flash screen. I had to remove the battery, then tried to boot again with no response, so I left it a while again, put the battery in and got to the bootloader, thought I'd get into recovery and try a nandroid or something, only when I selected recovery it hung on the slash screen again.
Does anyone have any ideas what this is, or how this could be fixed? Damn I hate not being able to use my previously awesome phone!
I apologise for the long post, I'm just trying to give a good explanation of things. I just couldn't see the problem being my battery, only the day before the problem I was telling my friend how great the battery life on my phone is, and that he should give rooting a go and use CM7, this probably hasn't swayed his decision to root his phone.
Click to expand...
Click to collapse
did you try rebooting it without sdcard?

If you manage to get it running , try to flash a shipped ROM - it should unroot you and fix any software problems . Try taking it back to your carrier as that sounds more like a hardware problem.

you are stuck on HTC screen are you not? Then this is the exact same situation is it not?
bortak's Troubleshooting Guide said:
S-ON
"I'm S-ON, I can't boot recovery, and my phone doesn't boot "
This is a bit of a worse situation, as you cannot flash system critical parts such as the recovery image and just restore a backup. This unfortunately means that you will lose all of your data when you attempt to fix the phone.
[STEP1]- Make sure that you have a goldcard. If not, create one from the tutorial.
[STEP2]- Battery pull. Hold the BACK button and the POWER button to boot into FASTBOOT mode.
[STEP3]- Download the latest WWE RUU from here
[STEP4]- Run the RUU and wait for completion WARNING: DO NOT, BY ANY CIRCUMSTANCES INTERRUPT THE PROCESS - THIS WILL MORE THAN LIKELY END UP WITH A BRICKED PHONE - NOT EVEN IF GOD HIMSELF TELLS YOU TO DO SO, OR IF THE US PRESIDENT THREATENS YOU WITH THERMO-NUCLEAR WAR
[STEP5]- Once the phone is booted, you are now returned completely to stock. You will need to re-root again, and I'd recommend S-OFF
Click to expand...
Click to collapse
P.S. Remember to read disclaimer on the thread.

kmaq said:
did you try rebooting it without sdcard?
Click to expand...
Click to collapse
I have tried booting without sdcard with no luck.

Walter1115 said:
If you manage to get it running , try to flash a shipped ROM - it should unroot you and fix any software problems . Try taking it back to your carrier as that sounds more like a hardware problem.
Click to expand...
Click to collapse
I would love to try that, only I can't boot the phone at all, not even into recovery.
bortak said:
you are stuck on HTC screen are you not? Then this is the exact same situation is it not?
P.S. Remember to read disclaimer on the thread.
Click to expand...
Click to collapse
I've changed the HTC screen to a Google one, but yes, formally the HTC screen.
I will try and get to the bootloader/fastbootagain, only I have not been able to get to that today. I'm going to download an RUU, and try and flash it, although I'm not sure how if I can't get into recovery? Any help there?

stevoh84 said:
I would love to try that, only I can't boot the phone at all, not even into recovery.
I've changed the HTC screen to a Google one, but yes, formally the HTC screen.
I will try and get to the bootloader/fastbootagain, only I have not been able to get to that today. I'm going to download an RUU, and try and flash it, although I'm not sure how if I can't get into recovery? Any help there?
Click to expand...
Click to collapse
[STEP2]- Battery pull. Hold the BACK button and the POWER button to boot into FASTBOOT mode.
Click to expand...
Click to collapse
you don't need recovery

bortak said:
you don't need recovery
Click to expand...
Click to collapse
Made a noob error there and didn't have the udb plugged in. Got fastboot up, and downloading an RUU, will let you know how I get on, thanks for the help.
Would you advise, running my previous nandroid, once I get up and running again?

stevoh84 said:
Made a noob error there and didn't have the udb plugged in. Got fastboot up, and downloading an RUU, will let you know how I get on, thanks for the help.
Would you advise, running my previous nandroid, once I get up and running again?
Click to expand...
Click to collapse
up to you, doesn't make a difference

Thanks for the help, unfortunately when I got the RUU downloaded and the bootloader downgrader I now can't get the phone into fastboot! Rather gutted, as I could get it there the other day, now I may have to accept defeat!

What happens when you try to get to fastboot mode? How do you do it? Try to boot into hboot, then press power button and you should be in fastboot mode.

stevoh84 said:
Thanks for the help, unfortunately when I got the RUU downloaded and the bootloader downgrader I now can't get the phone into fastboot! Rather gutted, as I could get it there the other day, now I may have to accept defeat!
Click to expand...
Click to collapse
NEVER accept defeat with Android. Try my guide for help.

MatDrOiD said:
What happens when you try to get to fastboot mode? How do you do it? Try to boot into hboot, then press power button and you should be in fastboot mode.
Click to expand...
Click to collapse
I can't get into any sort of boot mode, I've tried leaving it for days and trying the button sequences, I've tried having it plugged in for a day, and then trying, with no luck!
bortak said:
NEVER accept defeat with Android. Try my guide for help.
Click to expand...
Click to collapse
I will have a look, I will try anything really! just need some more ideas....

bortak said:
NEVER accept defeat with Android. Try my guide for help.
Click to expand...
Click to collapse
I may have to accept defeat, but I don't think I will be blaming Android, more than likely a drop of the phone in the past that has taken it's toll or something.
Sadly nothing in the contents of your quite excellent guide jumped out at me as relating to my problem.
But, thanks for helping and your advice.

stevoh84 said:
I may have to accept defeat, but I don't think I will be blaming Android, more than likely a drop of the phone in the past that has taken it's toll or something.
Sadly nothing in the contents of your quite excellent guide jumped out at me as relating to my problem.
But, thanks for helping and your advice.
Click to expand...
Click to collapse
Ahh well that's a shame, get HTC to fix it for you

bortak said:
Ahh well that's a shame, get HTC to fix it for you
Click to expand...
Click to collapse
I have been onto them. The response from HTC was amazing, after detailing in an email my phone is dead, won't respond and won't turn on.
I was told, 'while the phone is on, remove the battery and sim and perform a soft reset, if this fails, perform a factory reset, through settings'
I replied asking them how much it will be for them to fix it, they haven't replied! Maybe they don't do weekend!
So if I send it off to them, are they going to frown upon me for fiddling with the phone and rooting etc?

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

[Q] My Phone Vibrates Continuously as I hold the Power Button to Turn it on

Hello, everyone, I have a problem with my phone.
Before the problem, I was rooted without any custom roms. I have never installed any custom roms on my phone. I have always been stock, but rooted.
This morning, T Mobile pushed an updated to my phone. I did some research (not sure if I did enough) and apparently it was the UVLDE update. So I clicked it, phone restarted in 5 seconds, and restarted in clockwork mod, I believe. It was the screen that allows me to reboot along with some other options and is navigated by pressing up and down on the volume buttons.
I pressed reboot phone and the phone rebooted and worked normally throughout the day.
Now, I wake up (and I am not sure what happened, maybe I accidentally turned the phone off in my sleep) and I attempt to turn the phone on and it vibrates consecutively, on and off, and sometimes the screen blinks.
Is there any way I can fix this issue?
Thanks for your time. I performed a search, but I couldn't find the issue or I couldn't find any keywords.

Mr. Holmes said:
Hello, everyone, I have a problem with my phone.
Before the problem, I was rooted without any custom roms. I have never installed any custom roms on my phone. I have always been stock, but rooted.
This morning, T Mobile pushed an updated to my phone. I did some research (not sure if I did enough) and apparently it was the UVLDE update. So I clicked it, phone restarted in 5 seconds, and restarted in clockwork mod, I believe. It was the screen that allows me to reboot along with some other options and is navigated by pressing up and down on the volume buttons.
I pressed reboot phone and the phone rebooted and worked normally throughout the day.
Now, I wake up (and I am not sure what happened, maybe I accidentally turned the phone off in my sleep) and I attempt to turn the phone on and it vibrates consecutively, on and off, and sometimes the screen blinks.
Is there any way I can fix this issue?
Thanks for your time. I performed a search, but I couldn't find the issue or I couldn't find any keywords.
Click to expand...
Click to collapse
Maybe a brick? And questions go in the questions section for future reference.
Sent from my SGH-T989 using xda premium

Thanks. I'll remember that for the future.
I don't know if it's a brick or not. I haven't tried anything fancy yet. I'm looking for assistance before I go any further, if there is any further place to go.

Mr. Holmes said:
Thanks. I'll remember that for the future.
I don't know if it's a brick or not. I haven't tried anything fancy yet. I'm looking for assistance before I go any further, if there is any further place to go.
Click to expand...
Click to collapse
If you have clockwork mod on your phone and you can get to the clockwork mod menu, go to mounts and storage and plug your phone into your computer and click mount usb storage and copy this rom to your phone.
http://theunlockr.com/2011/11/29/how-to-unroot-the-samsung-galaxy-s-ii-t-mobile-version/
Then go to install zip from sd card and pick the one you just copied to your phone. It'll put you back on stock 2.3.5 hopefully that will work and if it does you will have to re root your device because this zip puts your phone to completely stock and removes the root. Hopefully this works for you it has for me in the past good luck.
Sent from my SGH-T989 using xda premium

Update.
I plugged it in to my computer via the USB.
Apparently, the computer can't recognize itbecause the device has malfunctioned (not sure how accurate that is), but the phone has turned on and I can use it.
I know the problem still, exists, so should I still follow your advice, JPOKeefe's, and go completely back to normal after erasing everything? I have no problem doing that to save my phone.
Modification:
Maybe the battery was just dead... which is why it's 0 % charged and it won't turn on after it was working perfectly before I slept.
If that is the case, then I am prepared to defend my intelligence! I guess it's just some paranoia from the update this morning that didn't actually go through.

Mr. Holmes said:
Update.
In plugged it in to my computer via the USB.
Apparently, the computer can't recognize itbecause the device has malfunctioned (not sure how accurate that is), but the phone has turned on and I can use it.
I know the problem still, exists, so should I still follow your advice, JPOKeefe's, and go completely back to normal after erasing everything? I have no problem doing that to save my phone.
Click to expand...
Click to collapse
Honestly you don't NEED to do it but if your phone is messing up and wont boot maybe you should go back to stock and re root when you read and learn more and feel more comfortable having a root.

Thanks for you quick replies.
I ninja edited my post, by the way. I'll give it a moment to charge and see what happens.
The phone was acting slightly stupid this morning after I attempted that update, so I guess I had to be sure it wasn't something drastic.
I have been comfortable with the root I had. If this phone bricks or blows up, then I have an excuse to get a GS3. Because, you know, I might as well. =p

Mr. Holmes said:
Thanks for you quick replies.
I ninja edited my post, by the way. I'll give it a moment to charge and see what happens.
The phone was acting slightly stupid this morning after I attempted that update, so I guess I had to be sure it wasn't something drastic.
I have been comfortable with the root I had. If this phone bricks or blows up, then I have an excuse to get a GS3. Because, you know, I might as well. =p
Click to expand...
Click to collapse
Just hit the thanks button!
And i have to wait till december for GSIII thats when my contract is up /:

Questions go in the Q&A section