hi,
i bricked my u8 clone when i was flashing it with flashtool and it stopped at 25% with an error about DOWNLOAD_CMD_FAILED or something like that (i forgot what the error looked liked) and now it wont turn on but in device manager it says unknown usb device (device descriptor failed) can anyone tell me how to fix it please, below is the screenshot of device manager with the unknown usb device highlighted, oh yeah and the ports (COM & LPT) section is the one i added myself
for some strange reason i left the smartwatch for a few hours, held the power button, plugged in the usb and then it popped up with USB modem driver ( COM3) in device manager and it flashed so this thread is closed now
--------------------------------------- closed ----------------------------------------------------------------------------
Related
Hi Everyone, In an attempt to fix my bricked device with all necessary flash files and drivers installed perfectly, my device is being detected under 'HUMAN INTERFACE DEVICE' as a 'USB INPUT DEVICE' in device manager, according to what i read, my device is suppose to display or be detected as "qulacom HS-USB qloader 9008" under com port. but that isn't happening, i repaired the drivers, re-installed them, formatted my pc and tried it on fresh windows installation. but still the problem is there. i even tried it on several computers but it still detects as USB INPUT DEVICE under Human Interface Devices in device manager. Now i am stuck here with my device dead for the past two weeks. please any one with an idea how to fix this issue?
i will be deeply grateful. Thanks!!
:crying:
Steps Parku said:
Hi Everyone, In an attempt to fix my bricked device with all necessary flash files and drivers installed perfectly, my device is being detected under 'HUMAN INTERFACE DEVICE' as a 'USB INPUT DEVICE' in device manager, according to what i read, my device is suppose to display or be detected as "qulacom HS-USB qloader 9008" under com port. but that isn't happening, i repaired the drivers, re-installed them, formatted my pc and tried it on fresh windows installation. but still the problem is there. i even tried it on several computers but it still detects as USB INPUT DEVICE under Human Interface Devices in device manager. Now i am stuck here with my device dead for the past two weeks. please any one with an idea how to fix this issue?
i will be deeply grateful. Thanks!!
:crying:
Click to expand...
Click to collapse
follow this
1. join in recovery mode (cwm)
2. go mounts and stroge and format system
3 reboot ur device ( Now the loop is eliminated, just a static imagen )
3. dowload drives, firmware , and QNCG
4. install drivers or repair it
5 when the step 4 is done, plug ur device on elife logo and wait for driver installation(like 10 min)
6 use winrar for descompress the firmware
7open GNQC select bp browser, and search in folder firmware a file called BP_imagen
8 try with genereal mode or emergency mode, and click dowload
i did it, its working
u must have patience dont worry
try it, its working
good luck
Still Not Helpful.
andresplata94 said:
follow this
1. join in recovery mode (cwm)
2. go mounts and stroge and format system
3 reboot ur device ( Now the loop is eliminated, just a static imagen )
3. dowload drives, firmware , and QNCG
4. install drivers or repair it
5 when the step 4 is done, plug ur device on elife logo and wait for driver installation(like 10 min)
6 use winrar for descompress the firmware
7open GNQC select bp browser, and search in folder firmware a file called BP_imagen
8 try with genereal mode or emergency mode, and click dowload
i did it, its working
u must have patience dont worry
try it, its working
good luck
Click to expand...
Click to collapse
Actually my device doesn't even come on for me to do all that you said, i tried repairing drivers and all that but it still detects as USB INPUT DEVICE under HUMAN INTERFACE DEVICES. i need my device to detect as qualcomm device before GNQC downloader can detect it. my issue is very different here. because GNQC can't see my device since my device is not being detected the rightful way after all. i will deeply appreciate the solution. Thanks
did u fix it??
U can fix ? I have the same problem since three weeks and nothing... this a a sh*t... only recognized by HID... In other ocassion before of this, i can flash my Gionee but now i cant:crying:
Another one here who saw how the phone bricked after being flashed with GnQc, now when I plug the Usb on the Pc or with wall charger, the red light keep lit and it seems like it will like this forever. I am thinking of trying to get out the screen and disconnect the battery, seems like the phone is stuck on some strange mode.
Thanks.
This feel that not have solution....
Can any one fix it ?
i also got stuck . have given to gionee care they are unable to figure what was the actuall problem
Steps Parku said:
Actually my device doesn't even come on for me to do all that you said, i tried repairing drivers and all that but it still detects as USB INPUT DEVICE under HUMAN INTERFACE DEVICES. i need my device to detect as qualcomm device before GNQC downloader can detect it. my issue is very different here. because GNQC can't see my device since my device is not being detected the rightful way after all. i will deeply appreciate the solution. Thanks
Click to expand...
Click to collapse
the problem for me is that it have recovery stock english(e3) and i can't do anything...
anyone fixed the problem? i have my gionee bricked....
No Boot - No Recovery - No Download Mode Unbrick Guide
Qualcomm HS-USB QDLoader 9008 or Secure booting error (No Boot - No Recovery - No Download Mode) or "QHSUSB_BULK"
Hi team, if you have come here I'm sorry you are having this problem! But my friend and I have been to hell and back trying to fix this problem and we wanted to share our method of success for any poor soul who is experiencing the same thing! For our situation the USB was unplugged half way through flashing a KDZ or going back to stock firmware and created the No Boot - No Recovery - No Download Mode problem.
This has only been tested on the D855.. Just so you know.
First off, here are some links which you may need to have a look at if you have not done so already. Most of the bricking problems have already been extensively talked about by people here on XDA. For the method that works, we had to pull information from everywhere and spent a long time looking for the solution.
How to go back to stock - http://forum.xda-developers.com/showthread.php?t=2785089
Link for TOTs and KDZ's from the above thread - http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/
The Main Fix for the problem - http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853
The G2 version of the fix (for reference if you still have problems 55+ pages) http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
This is your last stop shop if everything is broken and nothing works, involves hardware fix - http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
The problem we encountered several times with all of the described methods above, is that many do not describe important things. While the main fix thread for the Qualcomm HS-USB QDLoader 9008 mode, which is shown in device manager, is very well written and detailed, the programs which are linked in this thread are questionable and haven't worked for many users with some offering to fix for money. We searched the internet and located a working version of the program which worked without giving a "Device was not found in dload trying to flash programmer" like the one provided on the XDA page. Use the links below for a working version from this thread http://androidforums.com/threads/lg-g2-not-turning-on-help.916865/
My first point is if you are having problems with any of the things, CHANGE YOUR USB CABLE or use the stock cable (I know most experienced users know this). The reason for this problem has something to do with different USB cables being made for different purposes and are of different qualities. Having an error on the USB ports gave us only qhsusb_bulk on windows device manager, without Qualcomm HS-USB QDLoader 9008 as well.
If you are still having problems, check your USB ports. It is really important to make sure this isn't the problem or you will be trying to fix this problem endlessly.
First attach the USB cable to the computer. When you plug your phone in, make sure you attempt to enter download mode by holding the volume up button when you plug the USB into your phone. Even though the phone will not enter "Download Mode" It will allow the phone to be detected by your computer (at which point you can release the buttons, it should then show "Qualcomm HS-USB QDLoader 9008" under ports. If this is not displayed you have a problem with the USB cable or port, or your phone is hard bricked and you need to head to the above guide for the hardware fix. If you have followed so far and are wondering what to do from here, once the "Main Fix" guide ends, head over to the "How to go back to Stock" thread above. Your phone should be showing "firmware upgrade" and you can proceed to flash a new updated KDZ on your device then everything will work and your nightmare should be over!
Working Boarddiag - https://drive.google.com/file/d/0BzkqP9M0LLWQUkEyRkZrVHlEbDg/view
Qualcomm USB Drivers (Essential for the aforementioned "Main Fix" above) - https://drive.google.com/file/d/0BzkqP9M0LLWQblF6Vl9OcUkwUDA/view
LG United Drivers (Phone Drivers) - https://drive.google.com/file/d/0BzkqP9M0LLWQUURDTHlYOW5YRms/view
If this helped you to fix your nightmare don't forget to hit the thanks button!
The "Wroking Boarddiag" asks for PW. aside from that, very good find, thanks
detected as qdloader hs usb 9008
board diag- ap check failed device not in downld mode
For all people with Windows 10 an problems with drivers (device is detected by Windows but app is not connecting). Decompress de correct cab for your Windows version, and update the driver "Qualcomm HS-USB QDloader 9008" with the path you used to extract. Now this driver isn't advertising that isn't signed anymore, and all apps will connect with your LG G3
Qualcomm HS-USB QDLoader 9008 2.1.0.5 x86
Qualcomm HS-USB QDLoader 9008 2.1.0.5 x64
Hi, I have the same problem, except that when I connect the usb, it shows up as "LGE AndroidNetUSB Serial Port". I'm not sure if I should try the Qualcomm route?
MrMuli said:
Hi, I have the same problem, except that when I connect the usb, it shows up as "LGE AndroidNetUSB Serial Port". I'm not sure if I should try the Qualcomm route?
Click to expand...
Click to collapse
I just fixed my Lg g3 with this method. Not sure if it will work with AndroidNetUSB
Would like to help for any difficulties. (e.g. Not able to find TOT file) etc.
Thanks to @Orcam & @kryptonite
This did not work. Here's what I tried:
1. Without battery
2. Changed drivers as @shawe_ewahs says
3. With battery
4. Admin and non-admin
5. Changing COM ports
But, every time, I get:
"Device was not found in dload trying flash programmer
TEST Aborted!!"
My LG G3 D851 is in Qualcomm HS_USB QDLoader 9008 (COM 41) so I know it is in the correct mode! Agh, it is very frustrating. Any help is appreciated. Thanks.
Thanks you SOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO much! <3 I finally was able to fix my device *O*
furiify said:
Thanks you SOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO much! <3 I finally was able to fix my device *O*
Click to expand...
Click to collapse
No problem. Hope it didn't take you as long as it took us to find all the right stuff
I'm having this problem, but when I plug in without a battery all that shows up in device manager is "Unknown USB Device (Device Descriptor Request Failed)". I tried to do the hardware fix and was able to force the device to reboot by touching the pins. But all that happens is it disconnects and reconnects from USB without being detected properly.
I should note that when I turn the phone on right now, it stays stuck in the initial LG G3 splash screen. When I plug in without a battery, it shows an empty battery icon with a wire and a triangle question mark.
Any idea what I'm doing wrong? I think if I can just figure out how to get my machine to detect my phone as the qdloader hs usb 9008 I can figure out the rest.
The boarddiag v3.99 version 1 and 2 dont work, they dont even get ejecuted, not eve trying to execute as administrator.
Just wanted to reply since I resolved my issue. It turned out that, despite the apparent inability to boot into download mode, I discovered that if I booted up the phone with a battery in it and plugged into a windows 7 laptop, and held the button down to enter download mode, it eventually let me into download mode. I really can't explain why this worked, but just wanted to put it out there. It was at least a few minutes before I noticed that the laptop chirped and it was showing the install screen in download mode.
Hope this helps someone out.
Dr1t3r said:
The boarddiag v3.99 version 1 and 2 dont work, they dont even get ejecuted, not eve trying to execute as administrator.
Click to expand...
Click to collapse
phaim said:
Just wanted to reply since I resolved my issue. It turned out that, despite the apparent inability to boot into download mode, I discovered that if I booted up the phone with a battery in it and plugged into a windows 7 laptop, and held the button down to enter download mode, it eventually let me into download mode. I really can't explain why this worked, but just wanted to put it out there. It was at least a few minutes before I noticed that the laptop chirped and it was showing the install screen in download mode.
Hope this helps someone out.
Click to expand...
Click to collapse
Sounds like it may be a problem with windows from what you two have said. Perhaps compatibility mode is the way to go. They did release a pretty major windows 10 update since I posted this guide.
I have a bricked Lenovo K30-W I'm trying to fix (freezes on startup). My computer (Windows 10) won't recognise it when I connect it to the USB port. In device manager, the phone is displayed as unknown, with error "Device descriptor request failed". I tried connecting to different USB version ports, I tried installing multiple different drivers and software, but nothing helped. Adb doesn't recognise it as well, even if I boot the phone to fastboot with volume+power buttons. Any other ideas? Thanks.
Update: problem seems fixed. I used another USB cable and plugged it into an older version USB port. It is now recognised.
status: Bricked
Access: No fastboot, No recovery However goes automatically to edl once connected to pc
Device manager recognizes as "Qualcomm HS-USB Qloader 9008 [port x] (x whichever usb port I connect)
all drivers installed.
Attempts:
1)Tried flashing via QFIL which gives an error "Download failed: Sahara fail: QsaharaServer fail: Process failed"
2)MIFlash
I have a laptop windows 10 with only 2 usb ports. As soon as I connect the device using usb cable, device manager shows under LPT/com ports as "Qualcomm HS-USB Qloader 9008 (port 5). Then I opened mi flash (also tried miflash beta), selected a fastboot image folder (extracted from tgz), select flash all, my then press refresh option, the tool will detect the phone as port -com 5 and then I clicked on flash. It'll send some signal to phone for 5 sec, and then stops giving error "cannot read from port com 5". I also tried it with other usb port (detects as port com 4).
please somebody help!
Edit: Used MI flash with Windows 7 compatibility mode. Worked like charm...
Use EDL cable, I just fixed it last week. It stuck at 900E not 9008. No fastboot, no recovery, Sahara failed
lintongprohacks said:
Hold down vol down+power to enter fastboot. Upgrade pc to win 10 to avoid issues as win 10 allows unsigned drivers with prompt
Click to expand...
Click to collapse
Read op. It's not possible to go to fastboot nor recovery. Phone just doesn't respond to anything.
arceuss said:
Read op. It's not possible to go to fastboot nor recovery. Phone just doesn't respond to anything.
Click to expand...
Click to collapse
Makes EDL cable by your self. Just take new cable data. Open the skin and sort green cable with black cable. Thats it.
Plug your phone with edl cable for about 3 second. Then open qfil. Setup qfil properly. Do not press download button yet.
But change your edl cable with normal data able.
Put the normal cable ( not edl cable) into your charging port of your phone.
Then plug in into usb port. As soon as you see Qualcomm 9008 port on Qfil press download button.
Qfil fails because waiting too long to press download button. Just press it immedietly after the qfil recognized the port.
If at the first try fail, repeat the prosses once again.
I now always flashing with qfil never use miui flash tool again..
https://forum.xda-developers.com/redmi-3/help/redmi-3s-hardbrick-t3650498
Charge%? Open if it is described in the subject
use TEST POINT
Thanks it worked for me
Thanks it worked for me
charge it for 12 hours +
Keep it for charging for 12 hours and then start i had such problems earlier.. or remove battery and charge the battery separately... the battery is been drained completely i suppose.
Messing around with my Z3 compact, which was already rooted and I'm sure the bootloader was already unlocked when I first rooted it. Anyways I tried to install Magisk for testing purposes, now I have a non-functional phone. Now I can't boot into recovery mode (I had TWRP) or into the regular mode.
I can boot into fastboot mode (plug in USB + hold Power & Volume UP --> 3 Vibrations --> Blue LED Notification). I checked using flashtoolx64 and it does detect the phone is in fastboot mode.
However when i try to flash the stock firmware, where I have to restart the phone in flashmode (Power off --> hold Volume Down --> Plug in USB), Windows says there is an error recognizing the device. and when I check device manager, it says the USB Device entry is: Unknown USB Device (Configuration Descriptor Request Failed). Could this be a driver issue?
I couldn't find any other solutions for restoring the system without going into flashmode, because it looks like i can't even get that working. I would appreciate any solutions that utilize fastboot mode, since that is the only mode I can get into with the computer recognizing it.
-Edit 1-
Silly me, it turns out I was able to get into flashmode afterall (Power Off > Volume Down > Plug in USB).
After double checking and re-installing the Sony Xperia USB drivers, I thought the phone was done. I tried plugging in the phone using the back USB ports instead of the front and voila flashtools can push the stock firmware. My guess is that the "Configuration Descriptor Request" error I saw in the Device Manager was because I was using the front USB ports on my PC.
-Edit 2-
Apologies, clicked on the wrong forum when it should have been posted in the troubleshooting forum. This thread can be closed/deleted since I figured out what's wrong (see edit 1)