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

Hey guys
I've got a desire which doesn't boot or even charge. There's no light when trying to charge and the PC doesn't even try to show the phone.
I've tried to charge it for a while to see if the battery charges - nothing happening here. I've also tried another battery. It just seems dead.
Any advice whether it can be revived?

Can you boot into Hboot (press and hold volume down and power button for a few seconds when phone is off) or Fastboot (press and hold back and power button for a few seconds when phone is off)?

If u could get in to fastboot then it can be fix. If not then what knows wrong with it.

cheers for the reply guys.
can't get it into hboot or fastboot. it's just dead. looks like it's completely knackered.
Out of warranty etc, so looks like it's a doorstopper.

Desire doesn't release more than two years ago, which is the time for the warranty -> You are still under warranty. So use it.

Can I still use the warranty even if I've rooted it and put on a LeedDroid ROM?
If I can - that would be fantastic

anisjolly said:
Can I still use the warranty even if I've rooted it and put on a LeedDroid ROM?
If I can - that would be fantastic
Click to expand...
Click to collapse
the fact in the matter is that it is DEAD. so even if you were rooted, S-OFF'd, had a custom SPL, had a custom ROM - IT. DOES. NOT. MATTER. If it's dead, they can't tell.
Go for warranty.

Related

bricked device(totaly)

well my friends i did it too. it was all normal(rooted and stuff), and then i turned off device and it wouldn't turn on. my stock hboot was 0.80 and current is 0.83.
the thing is i can charge the mobile but when i press power button red light goes away and nothing happens. device just stays there with no sign of life. tried to pull battery out for whole day but nothing happens when i plug it in, tried to boot without sim and sd card and still nothing. i cant even get into bootloader. Is there some advice or stuff i can try or should i send it back for warranty??
since i ****ed it up completely i recon they wont even trie to repair it and maybe i get another new desire. i loved my amoled screen but if that is the only way then **** it. any help is appreciated
This sounds like an SLCD brick. What did you do to cause this problem? Flash a recovery?
TheLastOne said:
This sounds like an SLCD brick. What did you do to cause this problem? Flash a recovery?
Click to expand...
Click to collapse
i don't have slcd 100% i flashed unrevoked and all was good for 2 days then suddenly booted with 4 vibrations and dead. mobile has no life at all except red and green light when charged
Is there any life when you turn it on? Vibration? Boot sound?
absolutely nothing.
Try the SLCD fix (or rooting method) with a RUU for Amoled Desire if this not work pull battery out press the Power Button and wait 5 minutes and try to control your device with some Java Based Android.. Android device controller if this work your screen seems to be bricked if it not work your device shall be bricked anyway your carrier should repair it sry dir My englisch

Desire: no boot constant vibration

Dear XDA developers,
a few days ago my internet connection started to fail so i decided to normally reboot my HTC desire by using the power button. After the restart it kept rebooting and showing the AlphaRev boot screen. I decided to reflash the phone by using a standard RUU. I tought it all worked out well, untill it crashed at 99%.
When i press the power button, the phone starts a continiuous vibration and shows a black (blanc) screen. I can not enter the bootloader / fastboot / recovery. It seems to react on nothing. I tryed to charge it, in case it was a battery issue, but no luck and no charging led.
I was running Leedroid + root + s-off with H-Boot 0.93.
On the XDA forum i found a way to blindly access the bootloader if there is no screen, this is not working out either.
Can someone help me out? Or is it ready to throw away? Besides that, is it possible to send it for guarantee? Or would there still be rooted/custom rom footsteps on the device?
it sounds like u flashed the wrong ruu. theres 2 types
amoled
or slcd
find out which ur phone is and flash that ruu
I will try but the computer does not recognize the device. Keep you updated.
edit:
Don't think this has anything to do with the screen. On the forum i found a topic with a trick (blind navigating to the recovery screen), but i think nothing happens when i follow this steps.
Maybe the HBOOT got fubar'd. If that's the case, your phone may be bricked. Take it to HTC for a look-see.
alpharev.nl said:
Is there any risk involved?
Yes, there is. Flashing HBOOT will flash a critical part of your phone, if that gets corrupted, your phone WILL be bricked.
[...]
If your phone no longer turns on anymore, please return to HTC for warranty purposes.
Click to expand...
Click to collapse
Do you think the warrenty will void if i send it for repair? Because there hase been a custom ROM and bootloader installed?

[Q] Probably bricked Desire after crash

Hi everybody,
I have a serious problem with my phone. I installed Aurora V3 without any problems and after I played around for some minutes everything froze and I pulled the battery.
After restart, only the white screen with the green htc logo was displayed and nothing happened. I pulled the battery again and now I cannot even start the phone with volume down + power or back + power. If I plug it into the pc, nothing happens.
Strange is if I charge my phone, there is no led but the bottom part of the back of my phone warms up a little bit.
I don't understand what just happened, I mean there was no flashing involved during the crash.
Some details:
stock hboot S-ON
cmw 5.0.1.0
sdcard 1gb ext4 + fat32
I really hope that you can help me out! What can I do?
Hmm some roms require s off, that could be why
Sent from my HTC Desire using XDA App
If you're phone responds to nothing it's dead. Similar thing happened to me, send it to HTC. Don't worry about whether you've rooted it or not, the fact that it's dead means they won't be able to know and will repair under warranty.
I doubt if one can brick a phone without flashing anything problematic. Can you go into Recovery and wipe everything again and try flashing something different? Maybe your ROM zip is corrupted...
Yeah I've doubt it as well, but I cannot start the phone at all. I tried power, volume down + power and I tried back + power. Nothing works!
I took the phone for repair. They said, they put new software on, but I have my doubts that it actually works.

[Q] G2 won't power on! Please assist!

Hello fellow G2 users.. my G2 phone won't turn on ... I had it rooted for a few months running Sense 2.1 and 3.0 roms then last night I tried going back to stock because the roms kept freezing and causing all sort of problems.. wifi failure, fc prompts.. ok, I had hboot for the desire z then I tired going back to hboot for the g2 ever sense then the phone refuses to turn on and there's only a orange light flashing and sometimes stays still.. please help.. I don't know what to do.. when I try loading boot loader volume down and power nothing happens..
I'm not an ace but bootloader should work, how long are you holding the power button? Does plugging it charge it? Is the battery dead, it have you pulled it? Does ADB see the phone at all? Have you checked the guide you were following?
30 seconds.. I held the power button for 30 seconds it worked before.. now it's not turning on or going into boot loader. . when plugged in it flashes orange.. I pulled the battery out and put it back in and nothing happens just keeps flashing orange.. my computer doesn't' recognize the phone anymore.. I don't know what's going on..
30 second with and without holding down the volume down button? Weird, no flicker on the screen or anything? Sounds like a possible brick, anyone else have any ideas?
Sound like you need a new phone.. coz if you hold down power button and down volume for 30 second it should boot up. If not your phone might brick.
Sent from my HTC Vision using XDA App
What exactly did you do to restore the G2 hboot? Am I reading this correctly that this is exactly when it wouldn't turn on?
a friend of mine tried loading hboot from eng-hboot.. still there's no way it would brick the phone!!.. I don't know what else to do. my computer can't recognize the phone anymore.. I'm trying to use adb reboot-bootloader.. but it says device not found..
Norm23 said:
a friend of mine tried loading hboot from eng-hboot.. still there's no way it would brick the phone!!.. I don't know what else to do. my computer can't recognize the phone anymore.. I'm trying to use adb reboot-bootloader.. but it says device not found..
Click to expand...
Click to collapse
Flashing hboot is a potential way to brick the phone. Flashing recoveries and roms is relatively safe (recoverable), but if you flash a bad copy of hboot, then I think JTAG is your last option.
Do you know exactly what your friend flashed? md5 hash, file name, which fastboot command?
I'm not sure what the file name is called I'll have to ask him. What is JTAG?
PM me if you need help with this I can bring it back from the dead ...
Sent from my GT-I9100 using xda premium
PM me if you need help with this I can bring it back from the dead
Click to expand...
Click to collapse
I am happy that we have someone around with these capabilities, but please get your website working correctly.
Every time I go there and click on a link, it takes like 2 or 3 minutes to come in, rather than fractions of a second - and it seems to do this no matter where I access it, whether home computer, work computer, public wifi or smartphone.....
Not having trouble with any other websites, so might wanna get that fixed
When you connect the charger to the phone if it flashes orange it means it needs battery to boot up wait for about 10 minutes and then try to turn it on with the charger still connected
If it doesn't boot up you have a serious brick

[Q] "Unfortunately, the process com.android.phone has stopped."

Hi guys, I'm very sorry if this has been solved already but I've been searching a lot now and none of the methods seemed to help me. I'm running a One X International. Until yesterday, I was running one of the older Cyanogenmod 10 Nightly builds but due to some performance issues and whatnot (nothing major), I decided to finally put in some work to update my phone to 10.1. My HBOOT was still on one of the older versions so after searching around, it seemed reinstalling the stock ICS and then doing some OTA updates would be the easiest way (for a n00b like me).
After doing so, I unlocked my bootloader again, re-rooted my phone, installed a newer version of CWM Recovery and finally flashed the latest stable build of CM 10.1. My first problem came after rebooting, where it would just hang at the Cyanogenmod ring loop and nothing else. I booted back to recovery and wiped everything (cache, data, dalvik etc.) and did a factory reset then reflashed the rom. This time it booted up but then, the "Unfortunately, the process com.android.phone has stopped." kept popping up. I literally can't do anything (there's a microsecond of space after I click OK before it would pop up again). I have read some people suggesting to others that they need to do a factory reset but I've tried doing that and it still didn't work. I've even tried installing the latest Nightly build of CM10.1 but it still didn't seem to make any difference.
Could someone please offer some advice? Thanks a lot in advance.
I had this problem and it was an hardware fault, so the only thing i could to was to send back the phone to HTC and get a new one...
MarcusJKX said:
Could someone please offer some advice? Thanks a lot in advance.
Click to expand...
Click to collapse
Did you flash the boot image?, and if so, did you fastboot erase cache after flashing the boot image?
matt95 said:
I had this problem and it was an hardware fault, so the only thing i could to was to send back the phone to HTC and get a new one...
Click to expand...
Click to collapse
I'm hoping that it's not and somehow I doubt it since I didn't have any problems like this until what I described earlier.
Did you flash the boot image?, and if so, did you fastboot erase cache after flashing the boot image?
Click to expand...
Click to collapse
I'm sorry, I'm not quite sure what you mean. Do you mean Boot image as in the bootloader? I didn't touch the bootloader except that it got upgraded whilst I updated the official HTC rom and also when I unlocked it. But I did erase everything before flashing.
MarcusJKX said:
I'm sorry, I'm not quite sure what you mean. Do you mean Boot image as in the bootloader? I didn't touch the bootloader except that it got upgraded whilst I updated the official HTC rom and also when I unlocked it. But I did erase everything before flashing.
Click to expand...
Click to collapse
he means
Code:
fastboot flash boot boot.img
matt95 said:
I had this problem and it was an hardware fault, so the only thing i could to was to send back the phone to HTC and get a new one...
Click to expand...
Click to collapse
matt95 said:
he means
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I don't think I did this. What is it for? I don't remember reading it in any guides although I read so many that I might've have forgotten.
MarcusJKX said:
I don't think I did this. What is it for? I don't remember reading it in any guides although I read so many that I might've have forgotten.
Click to expand...
Click to collapse
you have to flash the boot.img everytime u flash different rom
it is inside the zip file of the rom just extract it from there and take your phone to the bootloader and flash the boot.img...thn it will work perfectly
have a good read on how to flash a rom
http://forum.xda-developers.com/showthread.php?t=2069904
ll_r1d0_ll said:
you have to flash the boot.img everytime u flash different rom
it is inside the zip file of the rom just extract it from there and take your phone to the bootloader and flash the boot.img...thn it will work perfectly
Click to expand...
Click to collapse
Thanks a lot! I can't right now because like an idiot, I was in a rush before coz I had to leave for a few hours and really needed my phone so I thought maybe I'd try redoing the process. I got to the stage where I relocked the bootloader, factory reset, erased the rom, cache and pretty much everything but then I had to leave. Now that I'm back, the phone is out of battery coz I had it plugged in but it just wouldn't shut down for some reason so the screen remained on the bootloader wasting a ton of battery. This had happened yesterday when I was doing this and the battery would charge really slowly since the screen was constantly on. Do you know why this is? I don't think it's a hardware issue since after installing the stock rom yesterday, it could turn the phone off through the bootloader, recovery or just in the actual OS.
MarcusJKX said:
Thanks a lot! I can't right now because like an idiot, I was in a rush before coz I had to leave for a few hours and really needed my phone so I thought maybe I'd try redoing the process. I got to the stage where I relocked the bootloader, factory reset, erased the rom, cache and pretty much everything but then I had to leave. Now that I'm back, the phone is out of battery coz I had it plugged in but it just wouldn't shut down for some reason so the screen remained on the bootloader wasting a ton of battery. This had happened yesterday when I was doing this and the battery would charge really slowly since the screen was constantly on. Do you know why this is? I don't think it's a hardware issue since after installing the stock rom yesterday, it could turn the phone off through the bootloader, recovery or just in the actual OS.
Click to expand...
Click to collapse
the phone never charges in the bootloader ....as ur phone is off right now just plug it to a wall charger and leave it for around 2-3 hours and check if the Red LED turns on which will show that your phone is charging
ll_r1d0_ll said:
the phone never charges in the bootloader ....as ur phone is off right now just plug it to a wall charger and leave it for around 2-3 hours and check if the Red LED turns on which will show that your phone is charging
Click to expand...
Click to collapse
Aha didn't know that! Well I did leave it on the charger before i left although it was on the bootloader so like you said, it didn't charge. But when i came back (several hours later), the screen was black and the red LED was not on. Again like an idiot, I tried to turn it on and it went into the bootloader although it said that the battery is critically low. I then tried restarting it and now it's staying on the HTC Quietly Brilliant screen. Does it charge here? The red LED is on. If i press power+vol down then it would go into the bootloader so i guess it's not bricked right?
MarcusJKX said:
Aha didn't know that! Well I did leave it on the charger before i left although it was on the bootloader so like you said, it didn't charge. But when i came back (several hours later), the screen was black and the red LED was not on. Again like an idiot, I tried to turn it on and it went into the bootloader although it said that the battery is critically low. I then tried restarting it and now it's staying on the HTC Quietly Brilliant screen. Does it charge here? The red LED is on. If i press power+vol down then it would go into the bootloader so i guess it's not bricked right?
Click to expand...
Click to collapse
nop its not bricked and if your phone is now on just press the power button for few seconds until the 3 buttons flash and it wll turn off and when your phone will have enough battery charged it will automatically turn on (my htc one x do this) and dn you continue the steps dat i told you
ll_r1d0_ll said:
nop its not bricked and if your phone is now on just press the power button for few seconds until the 3 buttons flash and it wll turn off and when your phone will have enough battery charged it will automatically turn on (my htc one x do this) and dn you continue the steps dat i told you
Click to expand...
Click to collapse
Hmm i still can't turn it off. After holding the power button and waiting for the 3 buttons to flash, it would just reboot into the HTC screen. But it seems to be charging because when I booted into the bootloader just then, it doesn't say "power critically low" anymore.
By the way, whilst we're on the subject, do you know if it's possible to disable the ability to restart the phone by holding down the power button even when the phone is locked? I have quite a bulky case (from Ballistic) which makes the power button stick out a bit and sometimes when it's in my jeans and I kneel down to tie my shoelace, my leg would press into the button making the phone restart. This doesn't happen with the iPhone for example. on the iPhone, when the screen is locked, the power button doesn't give any response and even when the screen is unlocked, holding down the power button will only display the option to shut it off. This has always annoyed me on the One X (don't know if this is the case for other Android phones).
MarcusJKX said:
Hmm i still can't turn it off. After holding the power button and waiting for the 3 buttons to flash, it would just reboot into the HTC screen. But it seems to be charging because when I booted into the bootloader just then, it doesn't say "power critically low" anymore.
By the way, whilst we're on the subject, do you know if it's possible to disable the ability to restart the phone by holding down the power button even when the phone is locked? I have quite a bulky case (from Ballistic) which makes the power button stick out a bit and sometimes when it's in my jeans and I kneel down to tie my shoelace, my leg would press into the button making the phone restart. This doesn't happen with the iPhone for example. on the iPhone, when the screen is locked, the power button doesn't give any response and even when the screen is unlocked, holding down the power button will only display the option to shut it off. This has always annoyed me on the One X (don't know if this is the case for other Android phones).
Click to expand...
Click to collapse
very good now ur phone is charging and i hope u have flashed the boot.img too well i also have that issue with that button :/ but i keep the phone in the opposite direction like the headphone jack side goes inside pocket and the mic side is on the outside whn inside the pocket ....thats the only idea i use :/
ll_r1d0_ll said:
very good now ur phone is charging and i hope u have flashed the boot.img too well i also have that issue with that button :/ but i keep the phone in the opposite direction like the headphone jack side goes inside pocket and the mic side is on the outside whn inside the pocket ....thats the only idea i use :/
Click to expand...
Click to collapse
Yeah I guess that's the only solution then. Glad I'm not the only one!
I just got home and it looks like I was wrong. The phone's screen was off and no red LED lights were showing even though it's plugged into the wall. I disconnected it and waited a few seconds and then reconnected it and after a couple of minutes, the red LED came back but it also started up into the bootloader automatically...this thing just won't stay off!! I will see what happens after an hour or so but at the moment, I can't think of what else I can do to shut it off to charge it.
By the way, as I said earlier, I have now resetted everything, cleared everything and relocked my bootloader. Can I flash the unlock_code.bin I got previously from HTC or has my Token ID changed now and I need to obtain a new one? I did a Google search and it sounds like it will have now changed but I just wanna make sure.
EDIT: ok I need to go to bed now but I just realised that the reason why it won't switch off is BECAUSE it is plugged in. After unplugging it and selecting Power Down from the bootloader menu, it's now switched off. But as soon as i plug it in again, the screen lights up again. I guess i have to leave it like this and hope that it charges overnight but I'm a bit worried that it's not so good for the screen not to mention it seems to get a little warm after awhile. We'll see...
MarcusJKX said:
Yeah I guess that's the only solution then. Glad I'm not the only one!
I just got home and it looks like I was wrong. The phone's screen was off and no red LED lights were showing even though it's plugged into the wall. I disconnected it and waited a few seconds and then reconnected it and after a couple of minutes, the red LED came back but it also started up into the bootloader automatically...this thing just won't stay off!! I will see what happens after an hour or so but at the moment, I can't think of what else I can do to shut it off to charge it.
By the way, as I said earlier, I have now resetted everything, cleared everything and relocked my bootloader. Can I flash the unlock_code.bin I got previously from HTC or has my Token ID changed now and I need to obtain a new one? I did a Google search and it sounds like it will have now changed but I just wanna make sure.
EDIT: ok I need to go to bed now but I just realised that the reason why it won't switch off is BECAUSE it is plugged in. After unplugging it and selecting Power Down from the bootloader menu, it's now switched off. But as soon as i plug it in again, the screen lights up again. I guess i have to leave it like this and hope that it charges overnight but I'm a bit worried that it's not so good for the screen not to mention it seems to get a little warm after awhile. We'll see...
Click to expand...
Click to collapse
no u just have to use the old unlock unlock_code.bin ....just charge it for 1-2 hours only and flash the boot.img in the bootloader and your go to go
ll_r1d0_ll said:
no u just have to use the old unlock unlock_code.bin ....just charge it for 1-2 hours only and flash the boot.img in the bootloader and your go to go
Click to expand...
Click to collapse
Thanks a lot man. So turns out that once again, it wasn't actually charging and the phone was dead when I woke up. So then I found another thread where someone had a similar issue and this was suggested:
mevorach said:
Hi
I have a solution for you
make a batch file :
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
put this file in the directory where you have fastboot.exe adb.exe and all other
files , also put the unlock.bin file that you have from htcdev
put your phone to bootfsatusb , and run the batch file , you will see the voltage
off the battry each time it loop , after an hour or two you will have enough power(~3.68mv) to unlock it , then charge it and do what ever you want
Click to expand...
Click to collapse
I did that and left it for a couple of hours and then the battery was at a high enough level for me to get to work again. I went through everything again remembering to flash the boot.img before flashing my new ROM and now everything is working perfectly! By the way, that guide written by hasoon2000 made a mistake I think. He said to flash the boot.img AFTER flashing the new rom which I did but then still got that com.android.phone problem. But then I flashed it again BEFORE flashing CM10.1 and now everything is smooth as butter.
Anyways, thanks all for your help. I really appreciate it!
MarcusJKX said:
Thanks a lot man. So turns out that once again, it wasn't actually charging and the phone was dead when I woke up. So then I found another thread where someone had a similar issue and this was suggested:
I did that and left it for a couple of hours and then the battery was at a high enough level for me to get to work again. I went through everything again remembering to flash the boot.img before flashing my new ROM and now everything is working perfectly! By the way, that guide written by hasoon2000 made a mistake I think. He said to flash the boot.img AFTER flashing the new rom which I did but then still got that com.android.phone problem. But then I flashed it again BEFORE flashing CM10.1 and now everything is smooth as butter.
Anyways, thanks all for your help. I really appreciate it!
Click to expand...
Click to collapse
glad to know that your htc one x is running like a fire well that method is just to show the current battery level nothing else ...and i had flashed the boot.img after the room but it worked for me cux i did fix permission wipe davlik cache and partition cache too...on some roms it works for me and on some roms it doesnt..well its better if you flash the boot.img before installing the room well um glad to help you and sort out your problem

Categories

Resources