Hi,
I'm in a bit of a problem.
I got this m8 that was supposed to turn on but it doesn't. I got a battery replacement and everything and nothing changed. Long story short, I plugged it into a computer and I get Qualcomm HS-USB QDLoader 9008 in Device Manager.
So basically, I've done a bit of recovery through QFIL before. It says in QFIL there is no previous software version. I think I could revive it with all the QFIL files to flash onto the phone. I've seen the HTC M9 has these files somewhere on XDA.
Please, I'd appreciate it if someone could supply me with these files or some other advice.
Thanks,
Jev
I have a similar problem and so far been unable to find relevant files or information on reviving a bricked M8 using QFIL.
Please help.
ludemon said:
I have a similar problem and so far been unable to find relevant files or information on reviving a bricked M8 using QFIL.
Please help.
Click to expand...
Click to collapse
In the 3 years I've had the device and been on this device forum, I've never seen the files posted or linked; nor seen anyone unbrick from this condition.
That said (for the second poster, and not the OP) be sure it's an actual brick; as you haven't described any of the events that led to the current condition (one of the pitfalls of saying "I have a similar problem" and not actually supplying any specifics). The message "Qualcomm HS-USB QDLoader 9008 " will appear anytime the device is not powered on (including a brick, but other conditions as well). It may be simple as charging the phone for several hours, then holding power+vol up for a minute or so, to force the phone to boot.
HTC One M8 bricked
Thank you redpoint73 for your reply. I bought this phone with the problem existing so don't know much about what lead to the condition. The seller did say that he rooted the phone and issued some fastboot commands, but couldn't remember the details.
I have left the phone connected to a charger for more than 24 hours, but the charging LED is not on continuously, nor regular blinking.
When the phone is connected to a charger or computer the charging LED flashes on for about 1 second, then nothing more.
In the case of computer connection the USB connection sound is heard (but never hear the USB disconnection sound) and Qualcomm HS-USB QDLoader 9008 appears in Device Manager.
I have tried all the various combinations of button pressing as recommended in lots of places, with times ranging from 10 seconds to 30 minutes or more.
At one stage I taped all the buttons down and when connected to a charger the LED blinked in a regular manner.....on for 1 second, off for 1 second, on for about 0.5 second, off for 12 seconds, and then the cycle repeated continuously. When connected to a computer in this condition the USB connect sound is heard at each 0.5 second blink.
I am currently looking, with hope, at various flashing utilities for phones with Qualcomm chipsets.
You say that you have not seen anyone unbrick from this condition. Does this apply to the M8 only as there appears to be more information available for the M7 and M9?
Hello All,
I have the exact same issue ...
It started by showing messages like "android core/services has/have stopped". I rebooted, then there was no mobile network connection -> No IMEI.
I had no worries, that happened also in the past and I could solve it with a dirty flash.
Then I went to Recovery, dirty flashed my ROM (Android Revolution), phone rebooted and started building application cache.
At some point, it started, then some more caching and ... boom, blackout.
It doesn`t respond to anything. No power+volume combination, anything.
I have even opened it up and removed the battery connector.
Without battery, when I connect it to the power source, via USB, the RED light turns on for a second and the Off. ..
Also, when connected to the PC, it is identified as : " Qualcomm HS-USB QDLoader 9008 " .
Are there any repair possibilities, besides motherboard replacement ?
Thank you in advance.
dachriss_13 said:
Hello All,
I have the exact same issue ...
Click to expand...
Click to collapse
It's debatable whether the issue is "exactly" the same (can have various causes and outcomes) but the current condition is similar. Therefore, did you try the suggestions already offered?
Try charging for several hours. Then try holding power+vol up for a minute or so, and see if there is any change. Anything coming on the screen is a good sign (even if it doesn't boot up fully).
I don't see anything in your descriptions that would indicate anything you could have done to truly brick it. It's hard to brick this phone just by flashing ROMs. So unless there just happened to be a battery or other hardware failure at the same time, I don't think it's bricked. And a hardware failure while you were booting up a newly flashed ROM would be an awfully strange coincidence.
Thank you for your reply.
When I reach home, I will connect it to the charger, let it sit overnight and afterwards I`ll try to start it via Power+volume up.
I will get back with feedback.
Hello All,
The approach with the charging does not work ... I left it overnight, more that 10 hours, and it`s in the same state; it doesn`t react to anything.
When I plug it to the PC, it recognized as Qualcomm HS-USB QDLoader 9008.
Any ideas or hints are highly appreciated.
Thank you.
Further to my previous post I opened up my phone and check the voltage at the battery connector and it was only 2.6 volts, so the battery was obviously not being charged via USB.
I charged the battery up to a nominal 3.7v using an external charger connected directly to the connector and then tried all the button pushing scenarios again with no joy. With the battery charged the phone is not recognised by a PC and the charging LED does not illuminate at all. The condition described previously is only achieved with the battery disconnected (or with the battery partly or fully discharged).
Hopefully these observations might help someone diagnose what the problem is.
dachriss_13 said:
The approach with the charging does not work ... I left it overnight, more that 10 hours, and it`s in the same state; it doesn`t react to anything.
When I plug it to the PC, it recognized as Qualcomm HS-USB QDLoader 9008.
Click to expand...
Click to collapse
Try another charger, try the button combo with the charger connected (and also not connected), try just power, or power + vol down (hold each button combo for at least a minute). Play around, and see if anything works. A few folks have had luck just messing with different combinations.
If you can't get the phone to power on, into at least bootloader, where isn't anything you can do. It will only ever be read by the PC as Qualcomm HS-USB QDLoader 9008. That is, short of opening up the phone, but that may or may not work, depending on what the problem is (battery, motherboard, etc.).
Strange, you are the 2nd person today on this forum with the similar issue, of apparent brick after just flashing a ROM: https://forum.xda-developers.com/showpost.php?p=73039334&postcount=7
Makes me wonder if the emmc chips are just going bad (as this is getting to be an old phone) and the ROM flash is the last straw (although it was on the brink of failure anyway).
But this is just a guess, at best.
Hi,
I know this has been a really old thread. I only realised I had replies now . Anyway, thanks for the replies, I really appreciate it. But unfortunately, no hope for my device. I have tried everything. When I plug it in to any charger, it just blinks red/orange(I can't tell which colour) once, and then just stays dead. No button combo did anything.
Thanks,
Jev
Related
Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou
quou2006 said:
Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou
Click to expand...
Click to collapse
Please try to enter the bootloader mode in a bright room as it is very difficult to see in poorly lit environment. Till you enter the bootloader mode your device will not be recognised. Perhaps one of the three keys is getting released..the light button is the usual culprit. Once you are in the bootloader you can reflash.
Thank d_ranade for your answer.
I am sure the screen is 'all black' and I've tried to press the buttons several times.
I think the main problem now is how to enter the Bootloader.
I sometimes find it takes several goes to get into Bootloader mode. If not, have you tried a hard reset?
I've tried whatever i can do. Hard reset is useless too.
quou2006 said:
Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou
Click to expand...
Click to collapse
I have sent you a pm, it should help you.
-Jwrightmcps
Thank Jwrightmcps for your help, but i can not enter the Bootloader ,so can not use mtty to do more.
Unable to start/see bootloader
I seem to have the same problem with my upgraded universal which was working fine for about ten days. Then I installed TomTom on it and again it was all working that evening.
Then, when I turned it on the screen went blank (white), so I re-flashed it, but, part way through the screen went black, so I left it connected for further hour and nothing. I have since been unable to get it to do anything, it is not recognised by activesynch, it will not charge (either from the mains or the USB on either of the batteries) nor will it turn on or respond in any way.
I have unset ‘allow usb connections’. I have tried solidly for +/-10 minutes doing the backlight + on/off button and reset bit - repeatedly, with my wife helping to ensure all buttons were being pressed. All I got was a message from MicroSoft telling me that ‘One of the USB devices attached to this computer has malfunctioned and Windows does not recognize it’. The only positive thing is that every time I do it and depress the reset, the red LED flashes (provided I leave the USB cable in) but at no point have either of us been able to see any writing on the screen.
Any guidance (apart from where to take it for recycling) would be welcome…
It happened to me several times too. Even in the old ROMS. But had learned many things out of it. I removed the battery. Wait for several seconds or maybe minute before placing it back. And after placing it back wait again for some time before doing the "power + light + reset" (bootloader). At some point when I am in the bootloader mode already and reflashing, connected to the PC already, the screen went blank again. So I'm sure that something went wrong again. I repeated the procedure again (removing battery, placing it back etc...) and the reflashing continued. It takes patience (maybe).
After having experienced this so many times, I'm beginning to assume that it is not because the battery is "bad" or there is a problem on the ROM being reflashed. It is on how it (the battery) is connected to the unit. The reason why it does not turn on, charge even if connected to the charger, does not hard reset, does not react to anything... I just don't know.
One thing more, the procedure I said above sometimes does not work at once. But at least I managed to "resurrect" my device several times.
This I am sure, it is not in the ROM that is being flashed or the update...
Hope this helps,
Lelen
lelen, Thanks for your assistance. I tried last night, but it still could not enter the bootloader mode...
I have the same problem =( and i don't know what to do, someone told me that i have to change motherbord to resolve this problem, i hope there are some other solutions.
Dead Uni
I too had this problem. With the device not responding at all and not able to enter bootloader stops mtty from working.
Only way i could get it to work was to take it to an O2 shop to send it away for repair (luckily the O2 XDA range has a 2 year warranty and because its completely dead they cant tell the OS has been modified).
Unfortunatly like the previous post i think it can only be fixed by replacing the mainboard.
Hi all, i found this thread http://forum.xda-developers.com/showthread.php?t=291097&page=6
so many people have the same problem , and nobody found a solution? i can't believe that on all this universals died motherboard, and there is no way to fix it with some special cable or some programm.
yes,i post the last reply of the thread you mentioned above, but nobody can resolve it.
I recommend you remove the battery and leave it over night. Put the battery back on, ensure it is properly mouted and try booting it.
It worked for some, no idea why though. I'm actually suspecting a bad battery mounting, which results in the motherboard unable to detect a battery is iserted, thus refusing to boot.
finally managed to get mine fixed, mine was out of warranty too and sent it off to carphone warehouse express service, took 3 weeks but was fixed with a standard chargeable repair charge of £40
I have a somewhat similar problem but not from upgrading. I accidentally dropped the device after a successful upgrade and the screen got damaged. Someone picked it up, opened it and noticed it was on even though the screen was damaged, and then closed it back. By the time I got it back it was dead and could not come on again. I have since replaced the damaged screen, but the device will not come on and cannot enter bootloader either. The device get warm if the battery is left on.
coolbeans252 said:
finally managed to get mine fixed, mine was out of warranty too and sent it off to carphone warehouse express service, took 3 weeks but was fixed with a standard chargeable repair charge of £40
Click to expand...
Click to collapse
i guess thats what i will have to end up doing
anyone goten repairs done in north america?
( i live in western canada)
got the same problem
sofene said:
I have a somewhat similar problem but not from upgrading. I accidentally dropped the device after a successful upgrade and the screen got damaged. Someone picked it up, opened it and noticed it was on even though the screen was damaged, and then closed it back. By the time I got it back it was dead and could not come on again. I have since replaced the damaged screen, but the device will not come on and cannot enter bootloader either. The device get warm if the battery is left on.
Click to expand...
Click to collapse
hi..please let me know if your device is fixed and how you managed to fix it. my email id is [email protected]
http://forum.xda-developers.com/show...6&postcount=52
Hello everyone,
having major USB issues on my GNex. It's not charging anymore, but when the phone is off, it displays a charging animation. I could get it to charge once since this occurred, I left it plugged in overnight on my Mac (phone turned off). Did the same thing last night, no charge at all.
Mac OSX does not recognize the device, my Windows machine keeps telling me something like "the connected device is not working properly and can't be used... ". This message pops up every few seconds, so I guess it's constantly connecting and disconnecting. I can't access the internal storage on both systems.
My first guess was a hardware defect. But when I try to boot into recovery mode, a screen instantly pops up that shows Andy and displays a message: "Downloading. Do not turn off target.". In the upper left corner it displays " ODIN MODE" in small red letters.
When I press the power button in this screen (there is a big arrow pointing to the button with "start" written in it) the phone just normally reboots.
I can't get into fastboot mode because of this. I can get into CWM Recovery when i use the reboot into recovery option built in the ROM.
I dunno much about Odin (next to nothing). Has it something to do with Samsungs Kies? Could it be that something has put my phone in this "ODIN MODE" and it constantly tries to download something, making the USB port unusable? The port is not completely broken, as the phone displays a charging animation when it's turned off... so there is some connectivity left!
Thoughts coming up that this could be some kind of software issue. If there is a possibility to get out of the Odin Mode, it may solve the problem.
The phone is unlocked and rooted, running AOKP Milestone 5 and franco kernel.
I tried to restore an older nandroid, but it did not change anything.
Would send it in for exchange, but not able to relock the bootloader due to no fastboot access. If it can be confirmed that this is a hardware problem, I have to pay for the repair, I'm fine with that.
Has anybody any ideas that could be helpful? Any help is much appreciated, thank you in advance!
Do a search and you will find at least 30 helpful threads. Basically you only need to replace your USB charging board and it works again. Should be a warranty issue, but Samsung has really been an ass on handling this issue lately and claiming water damage.
I have mentioned it many times here: this problem can be probably solved by thoroughly cleaning your USB with soft toothbrush.
True, I also cleaned my port but it only fixed it temporarily.
Thanks guys. Tried to clean the port, nothing changed.
Ordered an OEM charging board off ebay, hope changing it will fix the issue.
Only thing I'm wondering about is, that the phone is stuck in Odin Mode when I boot it up with Vol. - and the Power Switch. So I downloaded Odin but it does not recognize the phone...
I am also facing the same problem. I am currently using the phone by charging the battery externally. Can someone confirm that changing the USB flex cable is the solution ?
Just posted in another thread but it is definitely the USB port for me. Using an HTC Vision (Google g2)
Hi,
my M8 doesn't turn on anymore. Already tried to change the battery, already tried to start it with VOL+ vor a couple of minutes, tried VOL+ and VOL- for a couple of minutes - nothing. I can't get into bootloader, i can't boot the phone - BUT:
- After connecting the phone to the PC a device "Qualcomm HS-UB QDLoader 9008 (COM10)" shows up
- When putting the charging cable only half the way in the charging LED turns on for 1-2 seconds and then off again
- When trying to do the VOL+ and Power method the charging LED turns on very short every 10-15 seconds as long as i hold the keys
Is it completely dead? Or can i try to flash something with qualcomm tools from here? Its a non-provider phone (HTC_102 i think) and the android variant.
The last thing i did was htcdev unlock after i got it from htc repair where they replaced the motherboard. i installed twrp and then miui7 and after this viperrom and leedroid. With miui it turned on but not every time (i don't know why) but after leedroid it doesn't even get into bootloader.
I don't think this is rom related and more of a hardware issue but maybe you have some ideas. The phone seems to be dead anyway, so let's try something.
Thanks
Dacoco said:
- When putting the charging cable only half the way in the charging LED turns on for 1-2 seconds and then off again
- When trying to do the VOL+ and Power method the charging LED turns on very short every 10-15 seconds as long as i hold the keys
Click to expand...
Click to collapse
What color charge LED?
Orange
Dacoco said:
Orange
Click to expand...
Click to collapse
I have the same issue. Same indicators. Just happened after charging overnight phone seems completely dead. Tried everything. (Light trick, Volume Up & Down w/ Power)
For the most part, if you've charged the phone for several hours, and all your are getting is orange/red LED (I would call it red, but maybe I'm not remembering it correctly) and the button combos don't work, its probably bricked.
Try holding power+Vol up for a minute or so (it will sometimes take that long to reboot, in certain circumstances). Also try Power+Vol up+vol down (but it sounds like you did already).
Also try the button combos with or without the charger attached and plugged in. In can think of at least one user, that had success with the charger plugged in, when they had lost all hope.
Basically, the device will come up with the Qualcomm Download message on your PC anytime the phone is not powered on. So it can be an emmc failure, or a dead battery. You can try replacing the battery, but that can just end up as a disappointment (which looks like may be the case for the OP). Or you can even have the Qualcomm message come up, if the charge is too low. I've had that happen once, gave me a heart attack. Red LED, and no response to button combos. I let it sit on charger for a few hours, then holding power+vol up for a minute made it boot, much to my relief.
---------- Post added at 03:51 PM ---------- Previous post was at 03:49 PM ----------
Dacoco said:
Orange
Click to expand...
Click to collapse
I would have been more hopeful if it was a green LED, appearing for a second when you connected the charger. That would have made me think maybe the charge port is just loose.
Same problem
having the same problem and i have noticed that when I plug it to pc then I shows qgusb dloader and when I press power button or any other button combination then I stop showing as qgusb dloader it appears as device is unplugged and then if I replug it then it won't show anything nor led neither qhusb..But after 10 min or so if I plug it then it again shows led and qhusb and I have also noticed one more thing that if I plug it in charger then led just blink for some microseconds but when I plug it to pc led blinks several times dim solid for 2 3 seconds is there any hope?
I reached this stage by installing unknown ROM .
By the way I have one more HTC one M8 but its from different career (at&t) and it's also rooted and custom rom installed but its in very bad condition just working but i m thinking about replacing motherboard or battery so i can fix it it this idea succesfull ?
narshi shukla said:
I reached this stage by installing unknown ROM .
Click to expand...
Click to collapse
What do you mean "unknown"? Do you mean, you can't remember exactly which ROM you flashed?
I presume you don't mean you flashed something, without knowing what it is.
Do you remember anything about the ROM?
What carrier version of the M8 are you talking about?
S-on? If so, its hard to brick this phone with s-on.
Hello All,
I have the exact same issue ...
It started by showing messages like "android core/services has/have stopped". I rebooted, then there was no mobile network connection -> No IMEI.
I had no worries, that happened also in the past and I could solve it with a dirty flash.
Then I went to Recovery, dirty flashed my ROM (Android Revolution), phone rebooted and started building application cache.
At some point, it started, then some more caching and ... boom, blackout.
It doesn`t respond to anything. No power+volume combination, anything.
I have even opened it up and removed the battery connector.
Without battery, when I connect it to the power source, via USB, the RED light turns on for a second and the Off. ..
Also, when connected to the PC, it is identified as : " Qualcomm HS-USB QDLoader 9008 " .
Are there any repair possibilities, besides motherboard replacement ?
Thank you in advance.
dachriss_13 said:
Hello All,
I have the exact same issue ...
Click to expand...
Click to collapse
Please don't post the same question to multiple threads. One place is enough. It makes it confusing to those trying to help you, and it's therefore against forum rules.
Understood, won`t happen again.
Thank you.
Hey all,
Got a second hand HTC M8 in an auction yesterday and it was marked as being faulty. The usual.
Plugged into my 5V 2A charger. Orange LED came on for about 5 seconds then goes off.
Tried again and again. Eventually got it to stay solid Orange for about 5 minutes before it went off.
Plugged it into my PC and it installs "Care Suite Emergency Recovery".
And that's where I am stuck. I google Care Suite and all I get is stuff related to Nokia.
However, I did come across one that says that it's a "Dead Boot" - Bricked in other words.
Just thought if there is anyway to save this device. Even though it is old, it would be still nice to get it going again.
And I have tried Key combos and nothing (P, V Up, V Down for a minute etc).
I have no idea if the previous owner tried to root the phone or anything. It's anyone's guess.
Any help would be gladly appreciated.
Thanks!
Try charging for several hours (such as overnight) on wall charger (not connected to PC). Then try power+vol up for a minute or 2. Or just power button for a minute or 2.
I don't know what "Care Suite Emergency Recovery" is. But it's normal to get the Qualcomm download mode message when connecting to PC whenever the phone is powered off. That message (Qualcomm download mode) also appears in the case of a true brick (JTAG or new motherboard needed). But it doesn't definitely mean a brick. It just means the PC can't talk to the phone, and that happens if the phone is simply powered off, or battery dead.
I'm assuming/guessing the message "Care Suite Emergency Recovery" is a similar or same symptom.
Oneplus 5T Black screen, No fastboot, No adb, No device manager list
my oneplus 5T was working fine and when i opened messenger, it freezes and screen stop responding then display went black.
I tried charging but nothing displays , no notification on screen showing charging , not even the led which is beside the front camera. I searched and thought it is what is known as hard brick. As per a xda-developer thread, i thought of flashing it but
when i try to connect it with my laptop which is windows 10 nothing is being showed in Device Manager, i tried using another Type C usb , tried with official usb cable,
but nothing came up in device manager. Please help how shall i fix it?
Warranty. Probably the motherboard is fried. You could try the unbricking tool on xda or contact oneplus's customer service.
freyrnygaard said:
Warranty. Probably the motherboard is fried. You could try the unbricking tool on xda or contact oneplus's customer service.
Click to expand...
Click to collapse
I read the unbricking method but that method requires the device to show in device manager. here in my case it is not showing in device manager, i tried all steps, power button for 10-20 sec, power button + vol UP button and other combination as well no luck so far, need help.
Sounds like a dead motherboard..