"Handset Diagnostic Interface (DFU) (COM5)" = Bricked not my doing,need help,thanks.
Hi,
I have a ZTE Max Pro.
I was surfing the web looking to download a game {casino card game} and noticed my screen freeze, I tried to shut it down quickly {holding power button} but it wouldn't let me, eventually after a few minutes it shut down.
So I tried to power it back on and it wouldn't power back on. I tried safe mode and every combination ,nothing. All I get is a short vibration and middle light comes on for a second . It won't power on , I tried it while charging and without charger. Even the charge light doesn't come on anymore.
I had 73% battery when this occurred.
So I connected to my computer to see what it's showing up as. This is what I get....
In Device Manager---> Under Ports (COM & LPT) it shows as ---> "Handset Diagnostic Interface (DFU) (COM5)"
I right click to update driver and it says the best " Handset Diagnostic Interface (DFU)" is already installed.
I don't know what's left to do . Thanks for any assistance.
PS: When I go to settings under device and printers etc it shows as unspecified Model
" QHSUSB_BULK " "Handset Diagnostic Interface (DFU) (COM5)"
Related
2.3.4 - unlocked/rooted
Tried several PCs/Macbook. Tried several cables...
Plug the phone into USB and it charges but isn't recognised by the PC/Mac and phone does not recognise it's connected to USB.
Also, power off phone when it's connected to USB it hangs just before powerdown. Progress stops spinning and it sits hung. Unplug USB at this hung point and it powers down immediately.
Boot into recovery mode (Power/Volume up) and connect to USB - Reboot bootloader still not recognised by PC.
In recovery choose Power off whilst USB connected, again it just hangs - 'POWER OFF' highlighted in blue to confirm selection, but phone just hangs at that point unti USB disconnected, at which point it powers down immediately. It will reboot if you choose reboot option from recovery menu...
My phone won't transfer data but charges too. Except mines is a hardware issue. Dropped the phone on its USB port while plugged in. All loose now
Sent from my Nexus S 4G using xda premium
Installed cyan rom. No difference.
Phone still won't shutdown when USB plugged in. As soon as you remove USB down she goes immediately, so as I suspected it's deeper than a ROM issue.
Boot phone into standard recovery mode with USB plugged in, Choose reboot bootloader, info messages displayed
USB Control Init
USB Control Init End
Top line shows 'FASTBOOT MODE'
Still not recognised by PC/Mac.
'ADB devices' shows no devices.
'fastboot devices' shows no devices
Searching around this seems to be a 'known' issue, but the fixes I've seen documented say power down phone whilst plugged into USB, which obviously I can't do as it hangs.
PITA this as I use it as an app development phone
Hi, My phone started lagging, freezing and randomly restarting a few days back, so I decided to back it up and begin flashing to stock rom, but now randomly without any change to software the phone has been bricked!
When connecting to charger phone does not respond and the power button does not work.
However today I found out if I take the battery out and put it back in and connect the phone to my PC the pc does make a noise but dosen't actually display the phone.
So I decided to take the battery out for 5s, then put it back in and hold vol down, power and home button for 5s and then volume up to go to download mode (nothing shwon on screen of phone), but am having no luck!
Odin does not pick my phone up however when I plug my device in under device manager it shows "qualcomm hs-usb qdloader 9008"
Is my phone hard bricked and any way I can fix?
Thanks
Sounds pretty bad, but last ditch effort, install Kies 3 and try the emergency restore or whatever it's called. Good luck.
Sent from my SM-N910T using Tapatalk
Please any help!
My Axon was at the twrp menu at 1% this morning so i went to shut it down to charge it but i havent been able to get it back on since. At first, plugging in the charger would prompt a light vibrate and red LED every few seconds but this has slowly stopped and the red LED only flashes every so often when i hold the power button. I've been trying to get into EDL Mode but with no indication from the phone, along with no indication of connection from the computer, I've been unsuccessful. If anyone could offer me some help to even get into EDL mode so i can flash out of this, that would be great. Thanks
Maybe forcing the EDL mode, using a moded USB cable:
https://forum.xda-developers.com/showthread.php?t=3537990
Search for the cable and instructions on that link
It seems like it's trying to boot into EDL mode but the battery isn't taking a charge. Have you tried connecting the phone to the wall charger for like an hour and then connect it to the PC?
A few weeks ago, my completely unmodified Essential phone froze while charging and wouldn't power back on after I turned it off. I tried all sorts of button combinations held for various amounts of time but couldn't get any response whatsoever from the phone. There was nothing shown on the screen, no backlight, no LED, and no sound or vibration. It also was completely undetected when connected to my computer by USB. Fastboot and ADB don't detect it either.
I replaced the battery out of desperation, which didn't seem to make any difference. After pretty much giving up, I removed the battery so I could store it without the phone draining it.
With the battery removed, I connected the phone to my computer by USB. The phone was undetected at first, but I noticed after leaving it connected for 15 minutes it connects to my computer as "Qualcomm HS-USB QDLoader 9008." It connects consistently every time after 15 minutes. Fastboot and ADB still don't detect it in this mode.
I've read that there's virtually no hope of recovery from this mode without the as-yet-unreleased Firehose programmer. However, I never tampered with the the bootloader, or anything else, on my phone, and the situation seems a little different than most cases of 9008 bricking. I haven't found another case where the phone waits 15 minutes before entering EDL mode. Is there any chance I might be able to do something without the Firehose programmer to get the phone out of EDL mode and continue booting?
I made an EDL USB cable that allows me to ground the D+ USB wire, with the hope I that might interrupt the phone somehow. I tried grounding D+ before waiting 15 minutes to see if it would go into EDL mode immediately, but it didn't. I also tried grounding D+ while in EDL mode, but that had no effect either.
Is there anything else I can try?
There are no solution for now (((
We have no working firehose file for mata...
Two days ago, my tablet didn't turn on, and I just thought that it may be completely drained.
I left it to charge until today, when I wanted to use it.
However, it didn't turn on, in fact it did nothing at all. I noticed that even the usual "charging animation" is missing.
It's not a faulty charger, and the tablet hasn't been damaged, and it was on the stock OS, so it's really weird.
I held all various combinations of Power, Vol+ and Vol-, for various amounts of time without any reaction(display, sound or vibration) whatsoever.
As a last ditch effort, I tried to attach it via USB to my laptop. Same thing here, no filesystem dialogue turning up, adb nothing, fastboot nothing.
Although! I noticed that it can't be completely dead, because `lsusb` shows it as
Code:
Bus 001 Device 013: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Now, my google foo let me down. I found out that as this seems to be some kind of emergency recovery mode, but I could find literally nothing about it related to the Galaxy Tab A7.
Did I miss something? Is it lost forever? Maybe one of you can point me in the right direction...
Thanks!
While connected to pc hold power button plus volume up +down for about 10 seconds i believe. If that brings you to download mode you can flash stock firmware with Odin. Your data will be lost though. Disconnecting the battery cable fron the circuitboard for a few second might be worth a try too. I would try that first but that does mean you should find out how to get the back off. I'm sure youtube can show you how
DerItaliener said:
Two days ago, my tablet didn't turn on, and I just thought that it may be completely drained.
I left it to charge until today, when I wanted to use it.
However, it didn't turn on, in fact it did nothing at all. I noticed that even the usual "charging animation" is missing.
It's not a faulty charger, and the tablet hasn't been damaged, and it was on the stock OS, so it's really weird.
I held all various combinations of Power, Vol+ and Vol-, for various amounts of time without any reaction(display, sound or vibration) whatsoever.
As a last ditch effort, I tried to attach it via USB to my laptop. Same thing here, no filesystem dialogue turning up, adb nothing, fastboot nothing.
Although! I noticed that it can't be completely dead, because `lsusb` shows it as
Code:
Bus 001 Device 013: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Now, my google foo let me down. I found out that as this seems to be some kind of emergency recovery mode, but I could find literally nothing about it related to the Galaxy Tab A7.
Did I miss something? Is it lost forever? Maybe one of you can point me in the right direction...
Thanks!
Click to expand...
Click to collapse
You entered EDL mode, Idk how to get out of it but I know for sure that QDL is EDL mode
I have exactly the same tablet and problem. Have you found a solution? Mine is still under warranty and I think I will use it if there is not an easy solution. Thank you
Try the edl reset command from edlclient.
In my case Samsung official service has replace the tablet motherboard
Sorry mate,
I completely missed your message.
In any case, for completeness’ sake, I also did not manage to get it back to work whatsoever. I tried every tip in this thread, as well as when I got more desperate resorted to trying with every tool on GitHub I could find - without success.
When nothing helped, I got a full refund from Amazon customer service.