Possible brick? - Desire Q&A, Help & Troubleshooting

Hi everyone,
I hope someone can help me recover my Desire. Earlier today I tried flashing one of the alpharev HBOOTs to prepare for LeeDroid 3.0.7 Data++ edition. At some point something must have went wrong, because when I tried to do 'fastboot reboot-bootloader' the phone just turned off (or so it seemed...explanation further on). I subsequently tried pushing the power button to turn it back on, to no effect.
After leaving it for a bit (about 15 minutes or so), I decided to disconnect from the PC and pull the battery, since nothing was working. This is where the REAL problem appears. Now my phone refuses to boot, even refusing to vibrate when the power button is pushed. Here are some of my observations:
After pulling the battery and replacing it, then connecting to the charger, the 'charging' LED lights up
When I press power, the 'charging' LED goes off, but nothing else happens (no vibration, no boot sound, no screen action)
Holding the Volume Down key while pressing power (after a battery pull and replace) doesn't change anything regarding the boot process described in the point above
As far as I can tell, attempts to get into recovery/fastboot have failed
Holding the Back key while pressing power (after a battery pull and replace) also doesn't help
I've searched Google for about 3 hours now, and nothing I've come across seems to help. Also, this isn't an SLCD brick, since the phone has an AMOLED screen.
Any help getting the phone up and running will be GREATLY appreciated.
Thanks.

my friend warning are that no matter what DO NOT REMOVE BATTERY or it will possibly brick so in my opinion 95% you bricked your phone

hi, don't sounds good at all...
when you plug and push the power button, what does says your comp???
device unknow... nothing.
worse case scenario would be to put a PB99IMG
look at this to find the one matches with your phone (stock rom version )
http://shipped-roms.com/index.php?category=android&model=Bravo
attached an howto http://dl.dropbox.com/u/22152187/How to Extract the ROM from an RUU.doc
hope this help

Yup you failed to flash the most fatal part of you system(the hboot), and after trying to reboot the first time, you had no way to correct the error, as it is no longer able to load the hboot in order to change anything on the flash-rom. So no pulling the battery didn't change anything, you were already bricked.
No way to bring it back through usb afaik
edit: and no ruu is very unlikely to work as well, as the hboot, which is supposed to flash it doesn't even boot.
only way i know of is jtag, which allows a specialized connector to flash the flash-rom directly through a jtag port on the motherboard, however, the riff box needed is quite expensive(129$). Good luck. I feel sorry for you.

Related

Boot problems - can't get to Tricolor, but boots to Android

Hello all,
I've searched and found some things, but nothing that matches my problem.
HTC Kaiser, branded Swisscom. HardSPL, I don't remember the version. Trying to get to tricolor screen, no key combo works. Camera+reset w/stylus, camera+power, even the two soft keys to reinstall the rom in memory.
After pulling the battery (and waiting more than 5 minutes) and inserting again, pushing the power button turns on the green LED, but goes no further, even after waiting up to 10 minutes. Pulling the battery, then plugging in the USB charger (without presses the power button) will flash a white screen after 7 seconds, then a pause of another 10 seconds, then the phone boots in to Android (again, without pushing the power button, just plugging in the USB cable.
Once in Android, everything works (except the factory reset, it just hangs forever). I need to install WM 6.5 ROM.
Tried the KAISDIAG.NBH and the 329 HardSPL recovery, but no reaction and still can't get to the tricolor.
One last piece of information, when I plug in the USB data cable, the phone flashes the "USB connected" message, and then repeatedly flashes it again every 3 seconds. The computer makes the USB connected sound, but no communication and the KaiserCustomRUU.exe can't see the phone.
Any suggestions to get to the tricolor? It unusual to turn on the phone by just plugging in the USB cable.
Thank you and great work.
Try power+camera+stylus pressing the reset.
A while back the charging behaviour was changed, so that now plugging in a charger, or usb, boots the phone, ( previously we could not charge if it was switched off).
Your problem of `losing` the bootloader has been seen before, but is rare, and seems to have no definite cause, the last time I remember seeing it turned out to be a faulty camera button.
Sent from my HTC Dream using Tapatalk
Thanks and one more question
Thanks Zenity.
I'll continue working on it. One quick question, is there a command in Android to force a hard reset or to the boot loader?
Camera Button
Ok, after searching more (due to Zenity's suggestion) and reading other threads, I don't think it's a faulty (Fawlty?) camera button.
Somehow, the phone takes along time to boot, and must use some info from the bootloader, as it loads Android.
But all attempts to get into the bootloader fail. I can't establish communication by USB, but I think I will focus my efforts there. I've pushed and help all the buttons in different combinations for too long.
I'll let you know, and thanks again!
Ok, done some research into way to detect that the camera button is functioning, ( since this button is vital in getting the bootloader), no luck yet, but research continues, looking at remapping the camera button using atools, just so i can get a response of some sort, ( normally the camera button does nothing in android, it's unmapped).
Edit: nope, atools won't help, won't let me remap the camera button.
Atools-keymapper remap the key only in the android GUI not in kernel so any change doesn't effect directly the kernel.
Yeah, realised that, just thought there might have been an easy way of diagnosing the camera button, to see if it was at least functioning, but if it's not enabled at kernel level then it will be difficult to test without disassembly and getting a meter on it.
Sent from my HTC Dream using Tapatalk
Update - Android.process.acore
Hey all, still trying to connect by USB to use the CustomRUU tool. Now when I plug in the USB, I get a repeating 'Process android.process.acore has stopped etc".
when I click force close, it pops up again and again.
Pulled the battery, and rebooted. Now it boots repeatedly, it shows the splash screen, right when it should go to the Android home screen, it reboots.
Any ideas? Thank you!
probable that the FC and subsequent reboot corrupted the data partition, which is known to happen when the device shuts down unexpectedly.
You can try a 'fix permissions', and 'clear dalvik cache', but normally it takes a wipe and re-install of the system, you may get away with not clearing data, but it's often safer to go for the full wipe of system and data.

[Q] Tried to install Beatmod ICS, stuck on "screensaver" usb and recovery won't work

[Q] Tried to install Beatmod ICS, stuck on "screensaver" usb and recovery won't work
Hi guys,
I've watched the n00b video and been googling for the last few hours as well as reading through various pages on the XDA forum. I've found a lot of problems that are kinda similar and tried various solutions but don't seem to be quite getting there.
Basically I had Virtuous Affinity as the OS and clockworkmod installed (should be the most up to date versions of both, they were put on no more than a week ago) as well. I also had a backup of current OS and so on on the SD card, as well as the original zip of the rom.
I decide I want to give ICS a go and so I downloaded the betamod ICS and then loaded it. It asked me if I wanted to do a dalvik cache wipe, a dalvik cache + data wipe and a third option I don't recall. I went with the dalvik cache wipe (at the time I was under the impression that was the correct course of action) then put it back in my pocket while ICS installed.
I get my phone out of my pocket later and it's kinda stuck on what looks like (but logically isn't, I'm guessing it was meant to be a splash screen type thing while ICS installed or some such) a screensaver which just loops endlessly. The only thing you can really do is take the battery out and turn her on again, in which case you once again end up in the endless screensaver loop.
I've tried booting to recovery using volume - and the power button and unfortunately it just boots straight into the looping screensaver again.
Getting a bit worried and feeling adventurous I tried seeing what I could do with ADB, however the computer seemed unable to recognise that any device was connected with ADB devices not listing anything.
I've read up a lot and I'm at a loss as to what to do - there's a rom on the SD card and there also should have been a backup but I just can't get it into recovery.
I do have the ability to view the SD card on another device and interact with it, so if there's a potential SD fix, that's certainly not out the window.
But yeah, I'm clueless how to proceed here and very green at the whole rom business. Can anyone advise what I might try to do from here? I don't care what state I end up going back to, or if I lose my data, I can get all that back, I just want the phone in some semblance of basic operation.
I'll be keeping an eye on the thread, if I've left out any pertinent data ask away and thanks in advance for anyone with a clue how I can fix this mess .
EDIT: Post may be better off in ICS thread above and I do apologise if so, I would move it but I seem unable to delete it.
Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.
ik222 said:
Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.
Click to expand...
Click to collapse
I have, it doesn't work. I've left the battery out for a fairly long period. Volume - + power still just brings it back to the "screensaver" loop.
Thanks for the suggestion though.
Turn the phone off completely; pull the battery out for a bit then replace it and don't touch anything. Don't try to turn it on. Plug the phone by usb to your pc (still turned off). At the command prompt in the folder containing adb.exe type "adb reboot recovery" - the phone should power on and go to recovery where you can wipe properly and reflash whatever you want.
You should be able to boot to recovery using the volume down + power button combo (hold the volume-down key, then press and hold the power button and keep both held until you get to the bootloader menu); the only thing that's wrong with your phone is that you've flashed one ROM over another without wiping it first, so the ROM can't load but this shouldn't affect your bootloader or recovery.
Worst case you can flash a RUU which will restore it to the official firmware; you'll then need to re-root and re-install a recovery image to be able to flash custom ROMs again.
Very helpful post, thanks! I'll try all that and see how I go, I'll post if I still have trouble.
Yeah I dunno why I can't boot to recovery it's weird. The volume button wasn't working, so I removed it and am pressing in the volume down portion of the volume button with a pen while holding down the power button. It's possible perhaps I'm not successfully depressing volume down, but I'm 99% sure I am and that that's not it. I am however doing it as you and other guides advise, depress volume down, hold it and then depress power and hold both for about three seconds, no joy!
Anyway, as said, I'll try what you're recommending and see how I go. Thanks!
hopscotchjunkie said:
At the command prompt in the folder containing adb.exe type "adb reboot recovery"
Click to expand...
Click to collapse
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.
Ethicistabdiel said:
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.
Click to expand...
Click to collapse
Yeah that was what I meant; I've got a feeling that that only works when the phone is powered off if you had USB debugging activated on the phone beforehand, so if that's not working that might be why.
c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.
Accidental double post, sorry.
You need to try get into recovery mode, where you can do a full wipe and see if that fixes anything.
Firstly, remove your battery then re-install it, your phone should still be turned off at this stage. Press and hold the volume down button, then additionally press and hold the power butter, until something appears on the screen. If the bootloader appears, you can then boot into recovery from there.
If the above fails to work, report back with your results and hopefully something else will be suggested.
Ethicistabdiel said:
c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.
Click to expand...
Click to collapse
Your only other option to get into recovery is the volume-down/power-on combination. Like I said, I can't think why that's not working unless it's related to your missing volume button (maybe it's not maintaining a constant pressure on the button when you're using whatever to press through the hole).
If you still can't get that to work, I would suggest finding a stock RUU and flashing that. It's an .exe file that runs from your PC and will return your ROM, bootloader and radio back to stock. Obviously that means you'll lose root and your custom recovery so you'll need to do all that again from scratch. There's a sticky in the dev section with a link to a thread with various RUUs (it's named something along the lines of "shipped & test ROMs" - I'll check that and link to it once I've dragged myself out of bed to the computer). You'll lose all your data, but if you took a backup beforehand you can restore that once you're back up and running.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.
http://forum.xda-developers.com/showthread.php?t=824357&page=5
Guessing you mean that as far as the ruu thread. Am downloading a stock rom atm, with shaped internet till tomorrow, meh! Will see how I go. Have a feeling phone was probably Vodafone branded at stock though, so that could make for extra fiddling but yeah, fingers crossed.
If you are able too install a stock-rom you can work from their than install 4EXT recovery
touch than you doen't need the volume buttons.
I downloaded the most recent stock rom on the link above. When I try to install it though, phone off or on, it advises a USB connection error. Is this likely to be because I originally had vodafone stock and need to make a gold card, or should it still at least be recognising it? It does advise not to run any programs on the phone or anything when while installing the update, but of course, as long as my phones turned on it's stuck on the damned screensaver loop.
http://forum.xda-developers.com/archive/index.php/t-841890.html
Gonna give that a go, fingers crossed!
D'oh, just found out my mobile was Three at stock and not Vodafone, the search continues .
Gah, I'm about tearing my hair out here, I want my damned phone back . Stuck using a $79 Huwawei Vodafone thing at the moment and it's so so so awful.
Anyway. I was under the impression that making a goldcard would mean I could RUU a non-Three stock rom on the phone. I made a goldcard following these instructions; http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
Then I turned the phone on as the RUU advises, (meaning it's scrolling through the feckin' "screensaver") and start the process and once again get a USB connection error.
What's the better process at this stage, try and take it back to Three stock? I don't see how I can at the moment, the only Three stock I can find seems to be rom, not RUU, meaning I'd need to load from the phone, which I can't due to no recovery. Or should I keep trying to get the goldcard thing to work, maybe try some different RUU's or something?
I'm open to any other suggestions as well. Had a bit more of a fiddle around with my volume down button, no matter what I do though, I can't get recovery mode. Always boots first to the white HTC screen and then starts the infernal "screensaver" loop.
Ethicistabdiel said:
Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.
Click to expand...
Click to collapse
How come the volume down button be broken. When you were using Affinity Rom weren't you able to use your volume button for music. Remove SD card from phone then press "First - Volume down gently for 2 sec" & press-hold power button when it goes into bootload place your sd card back select option "REBOOT RECOVERY". I think your panicking too much just be patient nothing is wrong, i think your just hurrying it up...
The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .
Ethicistabdiel said:
The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .
Click to expand...
Click to collapse
The only option i can think of is "Fix your volume button from your nearest Service centre". Without that you cant do anything. I am Sorry....

Help - blank screen and cannot access boot menu

A friend has asked me to look at his Wildfire, he said it was updating the Market and then blank screened. Since then it will not turn on, vibrates, then nothing.
I suspected screen (replaced a few wildfire ones now) but no sign of life from touch buttons, volume key, etc - so suspect it is bricked.
Tried to flash it with RUU but the phone will not go into the boot menu via volume down & power on. I've tried numerous times and it went into boot menu once, but you could not select anything, no keys working.
Hooked up to laptop and laptop could see it, but when you try to run the RUU you get Error 170, probably becaused it's not actualy in USB Boot mode.
Has anyone seen this? Any other tricks to get it into boot menu? Anything I can run from laptop or SD card to force it into a recovery or boot menu?
This is a stock ROM phone, not modified at all.
Any help much appreciated*
I have a way but I cant remember it lol
If I can remember when I get home, i'll re-post.
OK, cool
Made slight progress today, even though I had the boot menu come up once yesterday, but no response from keys, I did notice that even though I was trying to access boot menu, it was actually acting like it was in the menu, just blank screen, i.e. if I held power button afterwards I got no vibration, but if I did pull battery and hold power, I did, as if it was booting up.
I wonder if in actual fact the screen is dead, but also there is a software hang up, as if display was dead, you would still be able to swipe the screen, get touch keys to light up when pressed, etc.
Anyway, so I went into boot mode, blank screen, pressed power anyway which would be FASTBOOT - right?
Hooked up to PC, ran an RUU and it connected OK, went through process but failed on ID, because the phone has a T-Mobile ROM and I was trying to flash with non-branded one.
So I either need to find a T-MOB UK RUU, I found one but it wouldn't run, or I need to create a goldcard (can I do that with a semi bricked device?) and go down that route.
Either way, I'm pretty sure the LCD is dead, so for the sake of £7.50 I'll replace that first, even if it has got further issues, having a working LCD will help!!
yeah get the screen fixed first.
you will only have to fix the screen later and the hassle of trying to fix a phone with broken screen, to have to have it fixed later anyway isnt really the most logical way of doing things

[Q] HTC Desire Charge OK but does not boot at all

Hi All
First thanks for a very good and informative forum.
======================
This was my first post/question and was placed in wrong section. Now it replaced. - Sorry for that!
======================
Information:
HTC Desire
rooted
S-OFF
EXT4 recovery
rom: runnymix...
sd-card partioned(by EXT4 recovery)
AMOLED
Motherboard and ribboncable was changed one month ago on warranty.
Symtpoms:
- Charges normally: orange charging/green full charge. Flashing orange/green without battery
- Cant NOT boot at all
- cant get into bootloader vol down + pwr
- can not be detected buy PC
- Battery inserted and charging: When pressing power to turn on => charge light goes off - and nothing happens. Leaving it in this condition for a while: the phone(mainboard) gets warm.
The phone was functioning perfectly before my son installed bootmanager app. He uninstalled the bootmanager app again without making any changes to the phone. It took long time (like freezing), so he did pull the battery out!!
Any help? Tried a lot of searches, none of them was as my problem.
Thank you
Hi! Have you tried to leave the phone without the battery for 1-2 minutes and tried a reboot?
Take the battery out, unplug it, hold power for 30 secs to get any remaining juice out.
Leave the phone for 24 hours (with battery out etc.)
Stick the battery back in, try again.
bortak said:
Take the battery out, unplug it, hold power for 30 secs to get any remaining juice out.
Leave the phone for 24 hours (with battery out etc.)
Stick the battery back in, try again.
Click to expand...
Click to collapse
What would be the cause for such a behaviour? I'm a little curious (and relatively new to the android scene)!
OT: I've took a look to your troubleshooting guide, good job indeed!
Ryther said:
What would be the cause for such a behaviour? I'm a little curious (and relatively new to the android scene)!
OT: I've took a look to your troubleshooting guide, good job indeed!
Click to expand...
Click to collapse
Really no idea, and what I told you to do is not guarantee'd to work, it may help though.
And thanks, it sure has cut down repeat posts about repeat problems by about 90% here.
Thank you all for your replies.
I did leave the phone without battery for several days - same problem.
But I did not try to press the pwr for 30 secs without battery. I will try when I get home.
I tried following:
- take battery out and reset it. then hold vol dwn + pwr -> Nothing
- take battery out and reset it. then hold back + pwr -> Nothing
By the way, if I press pwr to turn phone on, it does not come up, but leaving it for a while it gets warmer.
It looks like the CPU is trapped in a loop and running at full speed!
Could a riff box repair it?
do a battery pull then hold back & power. That usually boots into fastboot mode, see if the phone is recognised with
Code:
fastboot devices
if it is run the 2.3 RUU.
Dear bortak
I have tried. It does not enter fastboot.
command "fastboot devices" returns blank.
command "adb devices" returns empty list
command "adb reboot-bootloader" givers "device not found error"
RUU gives usb error.
have you installed the proper drivers on your pc for it to connect with the phone?
If so, when you attempt boot into fastboot and connect your phone through USB do you get the "device connected to windows" sound, like when plugging in and external driver or usb?
Because if not even that sound gets played it most likely means that your phone isn't even able to get into fastboot or hboot...
windows does NOT play any "device connected to windows" sound at all.
I have all drivers installed correct on my windows 7. My other HTC devices (desire s, wildfire, wildfire s) connects correctly to the PC and I can get the serial numbers of them using "fastboot devices" command.
Now on work, I tried a windows XP - same problem no connection - no sound.
This desire does NOT get into hboot nor fastboot. I think taht the "bootsector" is correpted.
I even used a Goldcard (made thru wildfire) - not working either.
So fixing it thru USB the normal way is not working.
Is there any way to force the device to boot up from SD card??
I have several backups of the phone system on my 8GB SD card.
You have to find a way to re-flash the hboot. That causes the blank screen display. May be a bad hboot install or something :0 Unless you have S-off and can be detected in fastboot, you can reflash hboot, otherwise you will have to try the blind flash method using PB.IMG. Best I could think of.
Sent from my PB99400 using XDA
@Jonicraw, thank you for your suggestion.
Where to get the HBOOT PBxxxx.IMG for this desire?
And how to flash it blindly, since I have black screen and no connection to PC.
AbuTarboosh said:
Hi All
First thanks for a very good and informative forum.
======================
This was my first post/question and was placed in wrong section. Now it replaced. - Sorry for that!
======================
Information:
HTC Desire
rooted
S-OFF
EXT4 recovery
rom: runnymix...
sd-card partioned(by EXT4 recovery)
AMOLED
Motherboard and ribboncable was changed one month ago on warranty.
Symtpoms:
- Charges normally: orange charging/green full charge. Flashing orange/green without battery
- Cant NOT boot at all
- cant get into bootloader vol down + pwr
- can not be detected buy PC
- Battery inserted and charging: When pressing power to turn on => charge light goes off - and nothing happens. Leaving it in this condition for a while: the phone(mainboard) gets warm.
The phone was functioning perfectly before my son installed bootmanager app. He uninstalled the bootmanager app again without making any changes to the phone. It took long time (like freezing), so he did pull the battery out!!
Any help? Tried a lot of searches, none of them was as my problem.
Thank you
Click to expand...
Click to collapse
im also same problem wont to solution
asad_sah said:
im also same problem wont to solution
Click to expand...
Click to collapse
Had the same problem. Mine could not charge at all and could not enter fastboot/recovery. Send the phone to HTC. I got back the phone with a new battery.
asad_sah said:
im also same problem wont to solution
Click to expand...
Click to collapse
Same s**t for me ... I tried everything you try and no results !
Come on experts ... somebody must have knowledge to fix this common problem.
What about an "Unbrick Jig" like the one for samsulng galaxy:
MICRO USB JIG DOWNLOAD MODE DONGLE FOR SAMSUNG GALAXY S2/I9100/I9000
This device may force the cpu to boot from usb, getting it in "boot flashing" condition.
AbuTarboosh said:
Come on experts ... somebody must have knowledge to fix this common problem.
What about an "Unbrick Jig" like the one for samsulng galaxy:
MICRO USB JIG DOWNLOAD MODE DONGLE FOR SAMSUNG GALAXY S2/I9100/I9000
This device may force the cpu to boot from usb, getting it in "boot flashing" condition.
Click to expand...
Click to collapse
No such things exists for the Desire.
Tell me what state the phone is currently in now?
Yet no solution for this problem...
STATUS for my device is:
Problem solved by changing the motherboard.
I hoped we could find a good solution for this.
I have the same problem but my phone is already on it's 3rd motherboard. I suspect the battery might be the problem but cannot get any answer as to what the voltages should be. I have already submitted a post headed Battery Voltage but it hasn't attracted a reply.
Hi there,
I got the same problem.
Can I send the phone to HTC even if I have rooted it? I also opened it a few weeks ago to replace the broken touchscreen. Do I still have warranty?
Greetings
Mika

Just another person who has Hard Bricked his M8

Hello Everyone
TL;DR Screen doesn't come on at all, battery led only flashes while it is rebooting (More details below), and When plugged in to my windows pc, a bunch of "Local Disk Found" pop up, some of the volumes I can access, most I cannot.
I have searched and searched the internet the past 24 for solutions, and have yet to find one. So imma walk you through what led up to the issue, as well what solutions I have tried.
Yesterday while I was trying to update my rom, I ended up getting stuck in what I thought was a boot loop. I then decided to hard reset my phone and go into recovery in hope to try to reinstall the rom. To my surprise, I could not access the internal sd card in the phone. Data was unmounted in the "Mount" settings and I could not what so ever remount it. After this I tried to side load it, but to no avail.
In response to all my attempts to fix the phone at that point, in frustration, I just said "**** it" and went into factory reset in the bootloader. This is where the hard brick happened. At this point, the screen would not come one, and the battery led was not lit when plugged in. I tried letting my phone charge over night and then, tried the "Battery Recalibrate method". I then tried the "Hold Pwr + Volume up for 10 seconds, then Power + volume Down until you access the bootloader"
After that, I then thought that the firmware was corrupted, so I tried to see if I could push an img to the phone, however fastboot does not see the device. I tried RUU, it does not see the device. I tried the HTC Unbrick method by Dexter that required me to install ubuntu and do some things in terminal, that also did not find the device. And here I am stuck. One thing unique to my situation that I have yet seen reported in the countless threads I have searched, is that when I plug my phone to my pc, a large amount of disk drives are found. Most of them are not accessible, but there are a couple that I can go in and see files for. Windows asks me if I want to format the ones I can't access. When hooked to my pc, I tried the the Power + volume button combinations, the only thing that seems to happen off of this is that my phone seems to reboots, and the battery indicator briefly shows.
Anyways, this is all I can remember. Any help would be GREATLY appreciated. I don't really think it is a hardware related issue since my phone does somewhat boot. However it seems it can't get to a bootloader what so ever.
Try holding power and vol up for a long time, like a minute or more. Try with and without charger attached, and after sitting on charger overnight.
If the bootloader is intact, the phone is likely not truly bricked (recoverable). And I don't see how you could have damaged hboot by the actions you mentioned.
What is the phone's original CID (carrier version) and are you s-on or s-off?
redpoint73 said:
Try holding power and vol up for a long time, like a minute or more. Try with and without charger attached, and after sitting on charger overnight.
If the bootloader is intact, the phone is likely not truly bricked (recoverable). And I don't see how you could have damaged hboot by the actions you mentioned.
What is the phone's original CID (carrier version) and are you s-on or s-off?
Click to expand...
Click to collapse
Verizon is the carrier version, and I am s-off.
Held vol + up for 5 minutes both with and without the charger. One time with the charger into my computer, and another into the wall. When it was in my pc, I can tell its doing nothing but rebooting over and over by the notification sound, and the constant "Found new disk" notifications I got. However still no luck, no screen turns on, no sign of hboot. I'm hoping to have some luck after leaving it on charge overnight and trying again.
TheBizkit said:
Held vol + up for 5 minutes both with and without the charger. One time with the charger into my computer, and another into the wall. When it was in my pc, I can tell its doing nothing but rebooting over and over by the notification sound, and the constant "Found new disk" notifications I got. However still no luck, no screen turns on, no sign of hboot. I'm hoping to have some luck after leaving it on charge overnight and trying again.
Click to expand...
Click to collapse
So still nothing after leaving it on charge overnight and I held vol + up for about 5 minutes. Things seem grim.
I think the proper thing to do when you discovered internal storage was not mountable, would have been to use the TWRP option to format internal storage (in Advanced Wipe options).
But now I'm baffled as to what happened that would have rendered the phone unable to boot into fastboot mode. Fastboot won't recognize the device if you can't boot into fastboot mode, which leaves use kinda stuck.
So you didn't try to flash anything during the course of all this troubleshooting?
What you did - "Hold Pwr + Volume up for 10 seconds, then Power + volume Down until you access the bootloader" is totally wrong
I used to get this bunch of local disk pop-up and this is how I get out the problem
Connect the device to pc, you can hear notification sound on pc that device is connected. Ignore all those bunch of local disk pop-up
Press & hold both power button & volume up button until you hear another notification sound that device is disconnected from PC (that's the indication that device is restarted)
Release both power & volume up button and quickly press & hold volume down button (only this one button)
This should get you on bootloader
redpoint73 said:
I think the proper thing to do when you discovered internal storage was not mountable, would have been to use the TWRP option to format internal storage (in Advanced Wipe options).
But now I'm baffled as to what happened that would have rendered the phone unable to boot into fastboot mode. Fastboot won't recognize the device if you can't boot into fastboot mode, which leaves use kinda stuck.
So you didn't try to flash anything during the course of all this troubleshooting?
Click to expand...
Click to collapse
No, nothing was flashed except the original Rom update that got this snowball rolling (Not saying its the roms fault, most likely mine).
ckpv5 said:
What you did - "Hold Pwr + Volume up for 10 seconds, then Power + volume Down until you access the bootloader" is totally wrong
I used to get this bunch of local disk pop-up and this is how I get out the problem
Connect the device to pc, you can hear notification sound on pc that device is connected. Ignore all those bunch of local disk pop-up
Press & hold both power button & volume up button until you hear another notification sound that device is disconnected from PC (that's the indication that device is restarted)
Release both power & volume up button and quickly press & hold volume down button (only this one button)
This should get you on bootloader
Click to expand...
Click to collapse
This is the one combination I forgot to mention in the op, sorry for that.
But I have tried this, before and after your post, still no luck.
If it worth mentioning, I can just hold power + down and it still reboots over and over. As well as just power. As a matter of fact, all button combinations reboot the phone over and over.
TheBizkit said:
If it worth mentioning, I can just hold power + down and it still reboots over and over. As well as just power. As a matter of fact, all button combinations reboot the phone over and over.
Click to expand...
Click to collapse
I thought the screen was dead? If so, how do you know its rebooting?
redpoint73 said:
I thought the screen was dead? If so, how do you know its rebooting?
Click to expand...
Click to collapse
By it constantly connecting and disconnecting from my pc. If that doesn't mean its rebooting, then I guess I'm mistaken.
TheBizkit said:
By it constantly connecting and disconnecting from my pc. If that doesn't mean its rebooting, then I guess I'm mistaken.
Click to expand...
Click to collapse
Well, it might mean that.
If it in fact is rebooting over and over on its won, simply holding the vol down button for a long time, should put you into bootloader (on the next reboot "cycle"). Again, assuming it is in fact rebooting, and that bootloader is intact.

Categories

Resources