Hey!
I have a PVT1 Desire, running Stock 2.2.2. I was just browsing xda, and put it on my desk. Then, 10 minutes later, i tried to turn it on, and nothing happens! I naturally put it on the charger, nothing happens, no orange light! So i try the battery in another phone, and that phone boots fine! So i try another battery in my desire, and it is not turning on. Can not boot to hboot or anything. Isn't recognized by pc. Anyone have a solution?
here u go
http://forum.xda-developers.com/showthread.php?t=1275632
2012katas said:
here u go
http://forum.xda-developers.com/showthread.php?t=1275632
Click to expand...
Click to collapse
The point is, my desire is not just soft-brick. It is a hard-brick. I don't see any mention of hard bricks there.
You have something in my signature (how it works) just go there and see it yourself.
nlooooo said:
You have something in my signature (how it works) just go there and see it yourself.
Click to expand...
Click to collapse
So magically my radio or hboot bricked itself?
Hello friends,
my Desire X was acting very strange, the screen suddenly changed the colors and went on and off for 3 seconds, and after that everything was ok. I decided to turn it off and I did, but now I can't turn it on ... I tried a factory reset. i.e. remove and replace the battery, hold down the volume button and then press the power button, but didn't work. Still when I plug it in my computer, the led turns on but I can't access the phone using the computer since it doesn't turn on. I don't think the power button is broken because it was working just fine before this. I had to send the phone to 3 different gsm services and they all said they can't do it because the model it's to recent and they can't find the software. Does anybody know what's the solution for my problem ? Thanks!
Related
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
Hey guys,
i was trying to root the Desire of my uncle, it is a german TMobile branded device with HBoot 0.75.
I used the instructions of the third post in this thread
http://forum.xda-developers.com/showthread.php?t=696189
After that i bricked the display i dont know why. The i tried to unbrick the display using the instrunctions of this thread
http://forum.xda-developers.com/showthread.php?t=748498
Now i have a Desire that does nothing, no vibration, my computer don't recognise it when i plug in the usb plug, the phone seems dead. The only thing the phone is doing is when it charges the battery, the orange/green leds are blinkng.
Is the phone dead, or can it be recovered in some way?
Unbrick a SLCD is very painful - had to do this myself. The instructions to unbrick are correct. The problem is blind navigating through the Bootloader menu. Sometimes its not responding to Vol-Up or Down at all - so you can't say if you really got to the right point at the Bootloader menu.
Hardest thing for me was to get into Recovery at all. Just give your phone 10s minimum between all steps.
m0rph3us said:
Hey guys,
i was trying to root the Desire of my uncle, it is a german TMobile branded device with HBoot 0.75.
I used the instructions of the third post in this thread
http://forum.xda-developers.com/showthread.php?t=696189
After that i bricked the display i dont know why. The i tried to unbrick the display using the instrunctions of this thread
http://forum.xda-developers.com/showthread.php?t=748498
Now i have a Desire that does nothing, no vibration, my computer don't recognise it when i plug in the usb plug, the phone seems dead. The only thing the phone is doing is when it charges the battery, the orange/green leds are blinking.
Is the phone dead, or can it be recovered in some way?
Click to expand...
Click to collapse
re: blinking: are they on, or actually blinking? when mine is charging I have a solid orange and when it is 100% I have a solid green LED.
Could it be a USB brick and a SLCD brick at the same time?
Have you tried to get the computer to recognise it in either fastboot or recovery mode?
Code:
plug it into the computer (turned off)
vol down+power=bootloader. was there a *ding*?
if not, press power again. you should be in fastboot now. any ding now?
if not, press power again (back to bootloader), wait ~10 seconds, press vol down, then power. you should now be in the recovery screen that would usually have a red exclamation mark in it. any luck with the *ding*?
if there is a *ding* coming from your computer then it can still be accessed from the PC and therefore should a ~relatively~ straightforward fix.
mountnorth said:
Hardest thing for me was to get into Recovery at all. Just give your phone 10s minimum between all steps.
Click to expand...
Click to collapse
its to do with the fastboot etc having to load the pm99.img files, and that takes ~10-15 seconds. the phone won't respond before it loads these in the bootloader.
nzdcoy said:
re: blinking: are they on, or actually blinking? when mine is charging I have a solid orange and when it is 100% I have a solid green LED.
Click to expand...
Click to collapse
When it is charging the red led is permanet on, when it has fully charged the green led is on.
vol down+power=bootloader. was there a *ding*?
if not, press power again. you should be in fastboot now. any ding now?
if not, press power again (back to bootloader), wait ~10 seconds, press vol down, then power. you should now be in the recovery screen that would usually have a red exclamation mark in it. any luck with the *ding*?
Click to expand...
Click to collapse
No *dings* no matter what i do.
Any other suggestion?
red? I didn't know the desire had a red LED, it certainly doesnt show up in a logcat on the blinker app.
do the keys light up when attempting to turn it on?
nzdcoy said:
red? I didn't know the desire had a red LED, it certainly doesnt show up in a logcat on the blinker app.
do the keys light up when attempting to turn it on?
Click to expand...
Click to collapse
Sorry i mean the orange led.
When i try to turn it on nothing happens, no vibration, no key lights. The only thing that happen is the orange led turns off.
m0rph3us said:
Sorry i mean the orange led.
When i try to turn it on nothing happens, no vibration, no key lights. The only thing that happen is the orange led turns off.
Click to expand...
Click to collapse
Unfortunately I don't know how much more help I could be.
all I could suggest is trying to flash said fixes completely blindly again in hopes you screwed it up the first time (using a MicroSD card adaptor to put necessary files on the card).
I guess the next option is to try at Modaco if you haven't already, or see if T-Mob can replace (whether or not you tell them the full story is up to you)
sorry I couldn't be more help
nzdcoy said:
Unfortunately I don't know how much more help I could be.
all I could suggest is trying to flash said fixes completely blindly again in hopes you screwed it up the first time (using a MicroSD card adaptor to put necessary files on the card).
I guess the next option is to try at Modaco if you haven't already, or see if T-Mob can replace (whether or not you tell them the full story is up to you)
sorry I couldn't be more help
Click to expand...
Click to collapse
Thank you nzdcoy, i have already tried all the fixes but nothing to do. I will buy this jtag
http://www.jtagbox.com/
and try te resurrection option if that does not work, i will try to read the whole nand content of my desire and write it to the desire of my uncle, maybe that will work.
Hey guys, I'm normally silent in these forums 'cause I've never had a brick, just by reading correctly. This problem I'm having isn't a flashing brick! What happened is the following:
I know that the DHD in combi with my BT car radio is somewhat difficult (because of bad HTC coding). It seems that when I have my facebook friends in my contacts that the DHD starts slowing down and eventually hang when connected to the radio, because my radio tries to get every contact including it's info. Normally I do not sync my FB contacts with my DHD however I must have mistakingly done this.
Today I connected to my car radio and after getting out of the car my DHD showed that it was still connected (a sign that my DHD had the hang problem again). I turned of BT (took a hell of a time) and contiued on. When I came back I tried connecting the DHD again, however when I pushed the BT checkmark in settings it showed BT on, but no BT connection came up. So I went into BT settings only to find that BT wasn't turned on, then in the BT settings I checked turn BT on.
At that moment my DHD hang instantly, no inputs were registered at all. I waited a few minutes but nothing changed (I could still see the screen frozen at turning on BT). So I took out the battery and reinserted it, but when a pushed the power, the phone vibrated thrice and then did not boot, but only showed a flashing amber led.
I have rooted, S-offed and did the whole shebang to flash my DHD once. This was a long time ago and I haven't had any problems, all was OK. So at first I tried to search the forums, what might have happened. No post seems to be the same as my problem, because everyone is having these problems after an incorrect flash (my flash was correct, cause I've been using the ROM for more than 4 months!). Still I tried the solutions given in these posts (enter fastboot and flash again).
But it seems my DHD won't go into fastboot. When I hold VOLdown&power my DHD vibrates 5 times and shows a steady green led. So I thought maybe flashing a new ROM resolves the problem. If I cycle the battery and then connect is to my computer, my DHD goes into Clockwork recovery. From there I flased a new ROM to my DHD (update.zip method), but to no avail. I've factoryresetted, cleared al data, wiped battery stats, all to no avail...
As of this moment I'm at the end of my knowledge, I've done everything I know could have helped, but nothing did. Therefore I'm asking you, the Oracle of XDA (users), please does anyone have any clue what happened to my DHD and if so, how do I resolve the problem!
Thanks in advance for every little motivation/obligation you show be giving me your insights!
Info:
ROM: Android Revolution HD 2.0.9
CWM Recovery: 2.5.1.3
I've allready wiped battery stats as per this topic!
Additional thoughts: Might a hardware fault be the reason? Because it happened after some problems with BT, and also because I'm still able to correctly flash new ROMS with CWM though the problem remains?
Allright, so nobody know an answer I'm guessing... I've started the replacement process with my insurance company. However I'd still would like it if someone would know what the heck I did wrong...
Have you tried flashing a new radio, as that is what controls the hardware?
All a new ROM will do is update the RIL, not the radio.
http://forum.xda-developers.com/showthread.php?t=896597
Sent from my Desire HD using Tapatalk
It does more than likely seem like a hardware fault so it cant really be solved with software changes. Although I still would have tried to flash an RUU which updates basically everything on the phone to bare stock.
Use an RUU via your pc (v2.36 or lower so you can root it again) to restore to an out of the box state.
Allright guys, thanks for your ideas! I'm however experiencing problems trying your idea's. fFashing a radio or flashing a stock rom are not possible, because I need a connection with my computer. This connection is not possible, if I start the phone normally (or with vol down) I get the amber flashing light or the green steady light. Both do not connect to my pc, I get some device "Qualcomm CDMA Technologies MSN" for which windows can't find any drivers. When I let the DHD go into QWM recovery, the RUU won't find the DHD.
So I've tried extracting the RUU rom en putting this on the SDCARD of the DHD, but when I try to install it via CWM Recovery it says that it's an invalid file...
I actually bricked mine on purpose, and the thing that happened when it got bricked was that no lights and no life at all we're visible on the phone...
Atleast you get shakes and lights, thats a good sign!
Sadly i don't know what has to be done to restore it, but maybe Jkoljo does, PM him about your problem, if you get an assistance and some solving, write back here for your solution for others to use in the future!
They hang out in the Android Revolution HD IRC Channel, thats where i would go tbh.. Live support ftw!
Edit: While reading your above statement, it seems your drivers may be faulty in windows, redownload HTC Sync from htc.com, install, reboot, and try again.
The "Qualcomm CDMA ..." notification on the PC is a sign for the Qualcomm service mode. Also the 3 vibrates and the orange light is an indicator for that. You can enter this mode by pressing vol+ and power your device.
Stupid question, but is it possible that your vol+ button is stuck or something like that?
And you said you're able to enter CWM? how? I'm asking because you said you can't enter the bootloader.
I'll do some research when i get home today.
Meanwhile Try if ADB/Fastboot sees your phone
Edit: just checked my theory of the broken vol+ button: i held down my vol + button, took my battery out, reinserted it and powered up my phone. Result: 3 vibrates and a flashing orange light.
Then i did the same, but held down vol - ( vol+ still pressed). Result: your second phenomenon: a few vibrates and the green light stays on.
So I think this proves my theory because this is exactly what you described
I suggest you to play a bit with the vol+ button. Maybe the button will work again then
Sent from my Desire HD using Tapatalk
Well, I'm gonna fire up IRC then and try get some help. It's indeed not bricked as far as I'm guessing cause I do indeed have lights and I'm able to boot into CWM!
Flussen said:
The "Qualcomm CDMA ..." notification on the PC is a sign for the Qualcomm service mode. Also the 3 vibrates and the orange light is an indicator for that. You can enter this mode by pressing vol+ and power your device.
Stupid question, but is it possible that your vol+ button is stuck or something like that?
And you said you're able to enter CWM? how? I'm asking because you said you can't enter the bootloader.
I'll do some research when i get home today.
Meanwhile Try if ADB/Fastboot sees your phone
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Right I'm guessing this is my problem! Just two days prior to resetting I started having problems with my VOL+ button (wouldn't work, only VOL- worked). So I'm guessing my hardware VOL+ button is broken and stuck to pressed...?
To answer your question about CWM: When I take out the battery so the phone is powered down, then reinsert the battery, connect the phone to the adapter or my computer (without pressing the power button), the phone boots into CWM after about 1 minute!
So after consolidating all the answers I'm guessing this is my problem: Hardware VOL+ is constantly pressed, therefore the phone boots consequently into Qualcomm service mode. Everything seems to be OK (flashing able to CWM), though just this little VOL+ problem puts my phone into an unusable brick...
The problem is that I'm not able to repair this myself (when I would try this, I'm guessing I'll break the seals therefore my insurance won't pay)... Anyone an idea how to circumvent the VOL+ button problem, without opening up my phone?
bdacier said:
Well, I'm gonna fire up IRC then and try get some help. It's indeed not bricked as far as I'm guessing cause I do indeed have lights and I'm able to boot into CWM!
Right I'm guessing this is my problem! Just two days prior to resetting I started having problems with my VOL+ button (wouldn't work, only VOL- worked). So I'm guessing my hardware VOL+ button is broken and stuck to pressed...?
To answer your question about CWM: When I take out the battery so the phone is powered down, then reinsert the battery, connect the phone to the adapter or my computer (without pressing the power button), the phone boots into CWM after about 1 minute!
So after consolidating all the answers I'm guessing this is my problem: Hardware VOL+ is constantly pressed, therefore the phone boots consequently into Qualcomm service mode. Everything seems to be OK (flashing able to CWM), though just this little VOL+ problem puts my phone into an unusable brick...
The problem is that I'm not able to repair this myself (when I would try this, I'm guessing I'll break the seals therefore my insurance won't pay)... Anyone an idea how to circumvent the VOL+ button problem, without opening up my phone?
Click to expand...
Click to collapse
Do you have needles at home? The ones you use when you repair cloth.. Try using one very carefully behind the volume +, you could also take a bit of A4 Paper, cut out some of it and make it fit between the gap of the Volume button, and try getting dirt out of there.
Allright, I've tried cleaning the VOL+ key but it still won't work. As a matter of fact I can feel a little "click" when pressing the VOL+ key, so I'm guessing the mechanical part of the key is working correctly. However when in CWM I can only use the VOL- key to switch thru the options, VOL+ is not registered by the phone. Therefore my assumption is that the there's a problem on the PCB with the VOL+ key, ergo a hardware fault... Insurance has been called and I'm up for a switch, now let's hope the insurance doesn't figure out I've rooted and installed another ROM than stock!
At least I wan't to thank all of you who've tried to help me! My ego has been saved, knowing it's indeed a hardware fault .
Cant you use adb within cwm to adb reboot bootloader?
Sent from my Desire HD using Tapatalk
bdacier said:
Allright, I've tried cleaning the VOL+ key but it still won't work. As a matter of fact I can feel a little "click" when pressing the VOL+ key, so I'm guessing the mechanical part of the key is working correctly. However when in CWM I can only use the VOL- key to switch thru the options, VOL+ is not registered by the phone. Therefore my assumption is that the there's a problem on the PCB with the VOL+ key, ergo a hardware fault... Insurance has been called and I'm up for a switch, now let's hope the insurance doesn't figure out I've rooted and installed another ROM than stock!
At least I wan't to thank all of you who've tried to help me! My ego has been saved, knowing it's indeed a hardware fault .
Click to expand...
Click to collapse
I've got the exact same problem! I don't have insurance on it though. And, im a day late for warranty.
What am i supposed to do? Any suggestions? Will htc deny my request to fix it coz it had a custom firmware?
Any help of any sort is appreciated.
I had exactly the same problem, and I'm sorry to say that I had to have it repaired. My button would also "click", but not register.
Maybe if you are buy a new power button from eBay?
Realising this is an old thread, but still:
I was just experiencing the same problem after I did a reboot to let one of my friends borrow my DHD to turn off the PIN code check on his SIM.
It started with the blinking lights (black screen), then I pulled the battery and found that my DHD was only accessible through ADB in recovery mode.
Did a couple of "ADB reboot" without any success, then tried using "ADB reboot recovery", which seemed to work (still black screen though), and then I did a "ADB reboot".
Back to normal!
hi , i had this issue too , its bcz of the moisture ur cell phone has absorb and as HTC desire HD very sensitive with its volume rocker area , the first thing that will be affected with moisture is ur volumer rocker circuit , try making it dry with a hair dryer blower or place ur phone in a rice sack for a day .
i am sure it will work .
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
A friend of mine had a pretty messed up HTC Incredible. He asked me to take a look at fixing and unrooting it (rooted via Unrevoked 3). I factory reset and got the phone to boot, which it hadn't been able to do. Found the unroot method for unrevoked, downloaded the PB31IMG.zip copied to SD card, proceeded to HBOOT and updated. Then volume up to reboot the phone. After this, the phone shut off and didn't boot. I didn't think anything of it and attempted to turn the phone on. After a few seconds a single vibrate and nothing on screen. I removed the battery and attempted to HBOOT, no screen response. After pulling the battery and plugging the phone in the charge LED will light but other than that, no response from the screen or the lighted home screen buttons.
I saw some similar situations and plugged the phone into my computer only to find that the Qualcomm CDMA drivers were not found.
Is this fixable or is it hard bricked?
Thanks for any help or direction in advance.
Shenaniganry said:
A friend of mine had a pretty messed up HTC Incredible. He asked me to take a look at fixing and unrooting it (rooted via Unrevoked 3). I factory reset and got the phone to boot, which it hadn't been able to do. Found the unroot method for unrevoked, downloaded the PB31IMG.zip copied to SD card, proceeded to HBOOT and updated. Then volume up to reboot the phone. After this, the phone shut off and didn't boot. I didn't think anything of it and attempted to turn the phone on. After a few seconds a single vibrate and nothing on screen. I removed the battery and attempted to HBOOT, no screen response. After pulling the battery and plugging the phone in the charge LED will light but other than that, no response from the screen or the lighted home screen buttons.
I saw some similar situations and plugged the phone into my computer only to find that the Qualcomm CDMA drivers were not found.
Is this fixable or is it hard bricked?
Thanks for any help or direction in advance.
Click to expand...
Click to collapse
Are you sure your pressing vol down and power and not vol up and power to get to hboot? Your pc shouldn't be looking for the qualcomm drivers unless you put your phone into diagnostic mode. There are 2 ways to do this, by hitting vol up and power while the phone is off, or by dialing ##diag on the phone pad from within a rom.
I'm sure I was hitting vol down, I used HBOOT to factory reset the phone before attempting to unroot.
So, if the phone is in diagnostic mode is there any way to take it out of it? I've heard this is a death sentence for Incredibles.
Shenaniganry said:
I'm sure I was hitting vol down, I used HBOOT to factory reset the phone before attempting to unroot.
So, if the phone is in diagnostic mode is there any way to take it out of it? I've heard this is a death sentence for Incredibles.
Click to expand...
Click to collapse
Pulling the battery should dissable diag mode. But obviously its not. Not sure mabey someone else will chime in.
cmlusco said:
Pulling the battery should dissable diag mode. But obviously its not. Not sure mabey someone else will chime in.
Click to expand...
Click to collapse
Yeah, I've pulled the battery multiple times. Can't get the screen to respond to anything. Hopefully someone will, thanks for your help!
Solved.
I used another phone to format the SD card and then blind flashed a ginger bread image via HBOOT. Thanks for everyone's help and XDA in general being awesome. Thanks!
EDIT: Special thanks cmlusco. Turns out another of his posts from a few weeks ago ended up solving my problem.
Shenaniganry said:
I used another phone to format the SD card and then blind flashed a ginger bread image via HBOOT. Thanks for everyone's help and XDA in general being awesome. Thanks!
EDIT: Special thanks cmlusco. Turns out another of his posts from a few weeks ago ended up solving my problem.
Click to expand...
Click to collapse
How can you do that?