I have a Desire HD, rooted with Visionary, ENG S-OFF, Radio S-OFF, Super-CID and SimUnlock'd, I installed ClockworkMod using ROM Manager and chose to boot into recovery, the phone now doesn't boot whatsoever, when turning on it vibrates 3 times and the amber LED flashes continuously about every second. If I hold down and press power, the phone vibrates 5 times and a green LED flashes instead, but nothing on the screen. Back and Power does the same as turning it on normally. When plugged into USB, my computer searches for the Qualcomm CDMA Technologies MSM driver which it cannot find...
Does anyone have any idea how I can get the phone into recovery mode, fastboot mode, or any other mode where I can flash a RUU?
Thanks, Jordan.
:::im not sure about this, and whatever happens, im not responsible, this is entirely your decision:::
But if i was in your shoes, given that it doesnt want to open at all but just flashes (the LED), ... , i would take the battery out and try again.
But if this keeps happening, then you should sent it to HTC.
Take your battery out, then try and flash into recovery mode
If you get into recovery mode then either install a new Rom or if you backup your Rom restore it
Sent from my Desire HD using XDA App
Taking the battery out and putting it back in does nothing, left the battery out for hours, nothing. No way to get into recovery...
If u flashed a 2.x.x.x version of CWM u could try use the bug thats now corrected in 3.x versions.
By taking the battery out then plugging USB in to charge and replace the battery. that used to start my DHD into recovery. if u flashed the 3.x.x..x CWM it wont have that bug.
^it's actually a feature which was removed...^
Sent from my Desire HD using XDA App
As long as your DHD vibrates, shows LED.. it is not bricked if I am not wrong. Wait for some senior member to reply your question. You might need to erase recovery via fast boot (just a thought, I am not sure).
b_bhavu said:
As long as your DHD vibrates, shows LED.. it is not bricked if I am not wrong. Wait for some senior member to reply your question. You might need to erase recovery via fast boot (just a thought, I am not sure).
Click to expand...
Click to collapse
Which of course works only if you can get into fastboot.
@OP: If you connect your phone to the computer and turn it on, does the computer recognise it?
as he said, windows searches for "Qualcomm xxx"-drivers.
i had a similar issue with my nearly-bricked hd2 some months ago.
but you know: hd2 and dhd aren't really the same when compared on bootloader level
DN41
Can't get into fastboot mode because pressing down and power just makes the phone vibrate 5 times and show a green LED. The phone failed to boot after installing CWM, which was v3 anyway, but obviously isn't present if it fails to boot into recovery in any form. I sent the phone away with Vodafone to get repaired under warranty, but they sent it back today saying it's water damaged and they won't go any further into fixing it. My house mate dropped the phone in the bath once, it worked fine afterwards, no problems whatsoever until now. It's obviously not water damage that caused this, but vodafone refuses to take a look... Am I gonna have to resort to a third party repair center? or replace my friends damn expensive phone... Any ideas?
JordanT92 said:
Can't get into fastboot mode because pressing down and power just makes the phone vibrate 5 times and show a green LED. The phone failed to boot after installing CWM, which was v3 anyway, but obviously isn't present if it fails to boot into recovery in any form. I sent the phone away with Vodafone to get repaired under warranty, but they sent it back today saying it's water damaged and they won't go any further into fixing it. My house mate dropped the phone in the bath once, it worked fine afterwards, no problems whatsoever until now. It's obviously not water damage that caused this, but vodafone refuses to take a look... Am I gonna have to resort to a third party repair center? or replace my friends damn expensive phone... Any ideas?
Click to expand...
Click to collapse
does your phone carrier offer extended warranty? as in full coverage?... basically i did this once.. my gf got pissed (as they do).. and basically tossed her phone towards me lol missed completely.. bounced off a wall, then off a metal heater, and then the floor.. thus .. screen completely broken.
We went onto our carriers website, added a 3 dollar a month full coverage warranty (12 month commitment). and after 2 weeks sent it in .. fully repaired 2 week later ...
Related
Long story short, I flashed under the recovery console a wrong bootloader image(only the bootloader, nothing else). Now the phone doesn`t turn on, charging led dead, screen dead, everything dead, usb connection dead. Fastboot devices won`t give me anything, adb also nothing, in computer`s device manager also nothing detected. Any ideeas? Thanks!
I am afraid its a hard brick!
Sent from my HTC Desire using xda premium
I kinda thought the same way. Now I`m hoping for that miracle with..pulling the battery out and waiting a few hours to "heal" to happen, if not it`s just another brick in the wall?
What "bootloader.img" did u flash?
Vodafone UK 2.33.161.6 PB9920000 from htc bootunlocker site http://www.htcdev.com/bootloader/ruu-downloads
Mihut84 said:
Vodafone UK 2.33.161.6 PB9920000 from htc bootunlocker site http://www.htcdev.com/bootloader/ruu-downloads
Click to expand...
Click to collapse
You only flashed the bootloader? Not the entire ruu?
Unless you get to boot somehow, your phone is a genuine brick.
Yes, only the bootloader. Any ideea how to get it to boot?
Maybe a buspirate can revive a hard brick?
Alive again
So, I made it boot again, using jtag, reflashed the right bootloader. But when I go to hboot and try to flash the rom from the micro-sd, it vibrates a few times and that`s it, doesn`t do anything, buttons stop working. Tried to flash it with fastboot via usb, same thing, tried the RUU utility, and when it says rebooting into bootloader, it also vibrates and dies. In hboot it gets stuck at checking the zip and parsing. So, last night I decided to give up, but then I remembered I saw on the internet some heat related problems, although my htc didn`t got hot or anything, so I put it in the freezer at -18 degrees celsius for half an hour, without the battery and micro-sd. After about 30 min, I put the battery and micro-sd, and for my surprise, it flashed it from the micro-sd, no errors, it booted, got it working. Ok, I removed the battery and let it dry a few hours. Put the battery back, turned it on, it gets stuck in bootloop. Put it back to freezer for 30 mins, works flawless. So, I believe there is a hardware problem, more likely electrical contacts on the board, since i don`t feel any heat coming out from the phone.
First off, S-off phone
So, I've been running the GPE rom posted by Joel for a while now with no issues... Today a friend wanted to see the phone, so I pulled it out of my pocket; hit power; nadda...
So I held power down for a while; got teh HTC screen; then nadda.
So we then attempted to get into recovery, power + vol down then selected recovery... Nadda, just a black screen.
I then redownloaded TWRP and fastboot flash recovery recoveryname.img, it tries to push it then it'll throw an error saying: "remote: image update error"
I looked around and found a thread with full directions with an RUU.. So I tried doing that, hwoever after clearing the cache via fastboot, when I try to do fastboot oem rebootRUU nothing happens.... sometimes teh screen goes blank, sometimes not.
Anything else I can try? I'm really wondering if it isn't defective hardware... .only had it 2 weeks too...
You are sure the phone is fully charged right ?
Sent from my Nexus 7 using Tapatalk 4
dottat said:
You are sure the phone is fully charged right ?
Click to expand...
Click to collapse
i was going to say the same thing. not sure how but i sometimes pull the phone out of my pocket with the screen on... so who knows which programs could have been tapped and running if it's bumping around in your pocket.
This is one of the reasons Verizon requires locked bootloaders now on all their phones. If the phone isn't even turning on, your first step should never be to try flashing a custom recovery or RUU (?!). If the phone has no charge and dies in the process, you could potentially brick it for good.
Sorry if that came across harsh, but... honestly, try charging your phone overnight first.
wireroid said:
This is one of the reasons Verizon requires locked bootloaders now on all their phones. If the phone isn't even turning on, your first step should never be to try flashing a custom recovery or RUU (?!). If the phone has no charge and dies in the process, you could potentially brick it for good.
Sorry if that came across harsh, but... honestly, try charging your phone overnight first.
Click to expand...
Click to collapse
Guess I should have put more details in the first post... when I got it into TWRP the first time it showed an 88% charge. I attempted to restore a backup and inside the recovery it would say it failed reading the memory and then it couldn't browse anything.
If I attempted to simply factory reset inside the recovery it would just lock up. If I tried to flash a rom via zip, it would lock up...
After a few times of rebooting it into the recovery I couldn't even click anything inside it without locking up.
it was at that point I tried to flash a different recovery and started getting the errors...
Anyways, more I researched it simply was a bad phone with defective hardware.
all good...
I was messing around with my phone and entered recovery mode (PhilZ Touch) and I kept tapping the empty part of the screen. Then the screen turned off, but on again after a few seconds. Then the phone wouldn't boot past recovery mode. I was stuck!
I researched the problem online and found another forum that posted a flashable "fix". So, I flashed it and then to my horror, realized that the zip was meant for a completely different phone!
Now my phone won't display anything on the screen, won't enter into Bootloader/Download Mode nor Recovery. I can't even do a Cold Reboot!
When I plug the phone into my computer though, Windows makes the USB connected dinging sound and attempts to install drivers but fails. In Device Manager, there is now a QHSUSB_DLOAD entry that appears and disappears depending on whether my phone is plugged in or not.
Does anyone know how to fix this and get the phone up and running again?
Preferably ASAP!? I literally have no phone... not even a landline!
Bro am in tha same boat...am about to send mines off to mobiletechvideos and they'll fix it for 50$ thats the only option ppl been saying...i tried the other way but its a headace and it dosent work for me ...
I ended up solving my problem, but not in the way I wanted. Since my phone was 100% dead, I went back to ATT since it was still under warranty. I told them a story about how the phone had been malfunctioning lately and then just completely died. They replaced the phone under warranty, so now I have a brand new one.
There definitely doesn't seem to be any easy way out of this problem once it strikes. I still don't know what happened to make the phone unable to boot out of recovery, even after wiping stuff, factory reseting, and reflashing roms. All I do know is that I have never had a problem with PhilZ until I started to rapidly tap the blank part of the screen (I like how it vibrates... I'm weird like that). This caused the recovery to never want to exit. Every time I reboot the phone, it automatically went to recovery, even after a full power off or battery pull.
Nevertheless, I am still going to root and mod my phone... just carefully.
You have a hard brick, which is nearly impossible to fix.
Sent from my LG-E980 using Tapatalk
Okay, I have never had to create a thread for this kind of thing. I have always been able to solve these issues. This time around, I have ran out of ideas. I have been searching and searching Google, Xda and any other Android forum. I have seen multiple threads with this problem, some cases exactly like mine. Not one thread with this problem ends with a solution, they're all just dead ends. My HTC 10 started doing this a couple days ago after a notification popped up saying that I was using an incompatible charger after using a Samsung USB cable on a Quickcharge 3.0 car charger. 30 minutes later, my capacitive touch buttons were not responding. So, I just figured that I would reboot and everything would be fine. Now, my phone is stuck in a bootloop with no signs of recovery. The only thing it will boot into is the white bootloader screen. Trying to boot into recovery or download just throws it back into a bootloop. When its powered off and I put it on a charger, the charging animation will show for about 15 seconds then, back into a bootloop. Trying to use a RUU.exe doesnt work, just a message shows up saying that my phone is below 30% charge. The device will show up in fastboot devices when its in the bootloader but, its useless. Trying to flash anything in fastboot fails or does nothing. The bootloader doesnt recognize 2PS6IMG.zip in the sd card. I really need my phone for work and cant afford to wait for HTC to repair it, especially since Hurricane Harvey hit their repair center in Houston. I've taken out the Sd Card and sim to see that would help but nothing. I let it die completely and still nothing.
My bootloader screen shows
Status: Official
***Unlocked***
***S-OFF***
I have been running Viper 3.5.0 for awhile.
This is my last option to see if anyone else has got through this problem without sending it off.
Thank you
bmx4lfe said:
Okay, I have never had to create a thread for this kind of thing. I have always been able to solve these issues. This time around, I have ran out of ideas. I have been searching and searching Google, Xda and any other Android forum. I have seen multiple threads with this problem, some cases exactly like mine. Not one thread with this problem ends with a solution, they're all just dead ends. My HTC 10 started doing this a couple days ago after a notification popped up saying that I was using an incompatible charger after using a Samsung USB cable on a Quickcharge 3.0 car charger. 30 minutes later, my capacitive touch buttons were not responding. So, I just figured that I would reboot and everything would be fine. Now, my phone is stuck in a bootloop with no signs of recovery. The only thing it will boot into is the white bootloader screen. Trying to boot into recovery or download just throws it back into a bootloop. When its powered off and I put it on a charger, the charging animation will show for about 15 seconds then, back into a bootloop. Trying to use a RUU.exe doesnt work, just a message shows up saying that my phone is below 30% charge. The device will show up in fastboot devices when its in the bootloader but, its useless. Trying to flash anything in fastboot fails or does nothing. The bootloader doesnt recognize 2PS6IMG.zip in the sd card. I really need my phone for work and cant afford to wait for HTC to repair it, especially since Hurricane Harvey hit their repair center in Houston. I've taken out the Sd Card and sim to see that would help but nothing. I let it die completely and still nothing.
My bootloader screen shows
Status: Official
***Unlocked***
***S-OFF***
I have been running Viper 3.5.0 for awhile.
This is my last option to see if anyone else has got through this problem without sending it off.
Thank you
Click to expand...
Click to collapse
Hold down the power button and vol down until your phone reboots. It'll take 20 seconds or so, and the capacitive button lights should flash until it reboots.
That should take you to download mode where the RUU.zip on your SD can be flashed.
If that doesn't work, try power + vol up + vol down, then switching to power + vol down when the screen goes black. I think I remember having to do that once when I first got the 10 for a different problem, but it could have been a different device
Hi everyone, had the phone for few years, one day it died and never booted again. Nothing was flashed at the time, my son was using it and I read that some phones, if they got hot enough playing games, the nand will get erased and the phone is borked.
All I get is the white HTC screen.
If I hold the volume + and - I will get to the screen attached.
If I select download mode, the phone will reboot and a black HTC screen will appear, but then the phone will reboot after 1-2 seconds, back to the white HTC screen.
Same with bootloader mode.
I have downloaded 0PJAIMG_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.2.zip and copied it to a 32GB sd card, and tries to get it to flash via download mode using the process above, but nothing happens and the phone reboots within 1-2 seconds.
Is there any way I can revive this phone? or just throw it in the trash?
Thanks!
shpitz461 said:
Hi everyone, had the phone for few years, one day it died and never booted again. Nothing was flashed at the time, my son was using it and I read that some phones, if they got hot enough playing games, the nand will get erased and the phone is borked.
All I get is the white HTC screen.
If I hold the volume + and - I will get to the screen attached.
If I select download mode, the phone will reboot and a black HTC screen will appear, but then the phone will reboot after 1-2 seconds, back to the white HTC screen.
Same with bootloader mode.
I have downloaded 0PJAIMG_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.2.zip and copied it to a 32GB sd card, and tries to get it to flash via download mode using the process above, but nothing happens and the phone reboots within 1-2 seconds.
Is there any way I can revive this phone? or just throw it in the trash?
Thanks!
Click to expand...
Click to collapse
Don't trash it yet!
Do you have a custom recovery?
If not you can "RAM" boot TWRP. While in the bootloader screen do this:
Code:
./fastboot.exe boot twrp-3.0.2-0-hima.img
Then with MTP enabled you should at least be able to look at your files (assuming not HOT deleted like you mentioned).
There's something called "RUU" we can try next, it's a (HTC) way to bring your phone back to stock. But try to save your files first!
Thanks, I will give it a try.
I don't care about any data on the phone, just trying to make it function again.
I let the battery drain over-night, I'll see if I can do anything with it.
Thanks for your input!
Note it doesn't look like the RUU files are hosted on HTC anymore.
Here's the full filenames I have downloaded and used in the past.
- RUU_HIMA_UL_M60_SENSE70_TMUS_MR_TMOUS_3.39.531.7.exe
- RUU_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6
A quick google should let you find them but a little frustrating to not get it direct from HTC (security risk anyone?).
I was messing with it last night, after I let it completely drain it won't charge anymore. If i connect it to a charger, or to a pc, it will turn on for 1-2 seconds, then turn back off, and do the same again and again.
Thanks for your help but looks like I can't do anything to it at this point. Not sure if the battery can be charges externally.