Hi,
After I've done the updated the firmware successfully, I rebooted the phone but after it switched off, it didn't turn on again. I've tried to keep pressed power button for a while but it is the same, neither if I connect it to the charger. If I try to connect to pc with the USB cable, it isn't recognized and in Device Manager it is "Unknown device" with the error "Device descriptor request failed"
Is there something I can do? :crying:
It is a Huawei Ascend G6-U10
Thanks
Update:
The phone now is being recognized as Alcatel HS-USB QDLoader 9008. I'm trying to follow the guide here but the multidownload tool after the "rebooting handset" part, outputs a "download boot loader fail"
Is there something I can do?
Thanks
same problem
ponzaro said:
Update:
The phone now is being recognized as Alcatel HS-USB QDLoader 9008. I'm trying to follow the guide here but the multidownload tool after the "rebooting handset" part, outputs a "download boot loader fail"
Is there something I can do?
Thanks
Click to expand...
Click to collapse
I have same problem .:crying: "download boot loader fail"
Related
Hey folks!
My Nexus 5 suddenly stopped launching. When I connected it to PC, under Device Manager it was listed as QHSUSB_BULK. After installing proper drivers it changed to Qualcomm HS-USB QDLoader 9008 Serial Port (COM11). Then I launched BoardDiag v2.99a and tried to restore device. AP test passed, but EMMC test failed with message 'failed to open partition from EMMC'. When I tried to check it again, I receved a message 'device not found in dload trying flash programmer'. Then I tried to force device to reconnect by holding vol+, vol- and power buttons. Again, AP test passed, but EMMC failed.
Is there any hope for my Nexus, or is this 100% bricked?
Thanks in advance!
[Q] Bricked. Erased/messed up bootloader. Win recognized as "HS-USB QDLoader 9008".
Hello.
Finally I hard bricked my Photon Q. I think I erased an unlocked bootloader. Right now phone cannot boot into fastboot mode. Power+Vol up, Power+Vol down held long do nothing. After connecting to Windows PC, phone is recognized as "HS-USB QDLoader 9008". I found drivers on the net. RSDlite recognizes device, but flashing fails with message that it cannot switch phone from download mode. I found QPST service software used to flash bootloader. Right now I think the problem is that I don't have proper bootloader images for Photon Q, and to be honest, I don't really know what options to use (the software seems quite complicated).
Has anyone encoutered (and solved) similar issues? Do you have any ideas, what to do? I tried some generic Qualcomm files, but couldn't flash them.
Anyone, please, help me, if you can.
Chris
Hello, I've recently tried to install firmware on my LG P710 using LGFlashTool and it failed and now I don't have any emergency mode, it stays at a black screen, connected to USB and being detected only as Qualcomm HS-USB QDLoader 9008.
I've tried this tutorial http://forum.xda-developers.com/optimus-l3-l5-l7-l9-ii/general/unbrick-lg-l7-ii-single-dual-t3166282 but my device won't get into QDL 9006 mode with error "Image Download Failed. Cookie (if present) not received."
What can I do from here? Or should I try something totally different?
Thanks in advance.
Hi all,
I have a OnePlus One that's hardbricked (it doesn't show any forms of life).
I followed this guide, but I'm stuck. I installed QPST Drivers, and Qualcomm 2012 Drivers (although after installing this one, I get a message stating that the newest drivers are already installed.).
At the moment, my device is recognized in device manager as "Qualcomm HS-USB- QDLoader 9008 (COM10)" and sometimes it doesn't get recognized at all. The device manager will then say "unknown device".
When the device is recognized as "Qualcomm HS-USB- QDLoader 9008 (COM10)", it doesn't get recognized by the OnePlusRestoreTool (even if I run it in administrator mode).
I'm using Windows 7.
Could any of you perhaps help me find a solution?
Thanks in advance!
Robert
SITUATION:
hello , My phone is an asus x014d. recently I switched it off , and it just would not boot up again.
when i press the power on button it shows "powered by android" then the "asus" logo.
PROBLEMS:
- I CANNOT ENTER RECOVERY MODE (by doing the power on + vol up)
- I CANNOT ENTER TO FASTBOOT
- Device manager only identifies device as "qualcomm hs-usb diagnostics 9006" instead of "qualcomm hs-usb diagnostics 9008"
- when QFIL for unbricking it yields error "sahara fail"
- when using eMMC software Download the errors i get are "timeout waiting" , box dialog "cookie(if present) not received"
- managed to get into qualcomm hs-usb diagnostics 9008 mode but i can only manage to do that after getting to 9006 then flashing stock rom with RAW HDD TOOL then i am able to get into 9008.
TL;DR - DESCRIPTION (**NOOB ALERT**)
after research , i found out that my phone is bricked. i learnt that i have to get my phone identified by the computer through the "qualcomm usb drivers" then flash through "QFIL" a tool used for unbricking devices that have qualcomm processors.
i was able to successfully install the drivers , and plug my phone to the pc it shows that it is charging so i press the power plus volume up , then phone switches off and device manager never shows me the "qualcomm hs-usb diagnostics 9008" unless after switching off i immediately press volume down then device manager shows me "qualcomm hs-usb diagnostics 9006".
QPST will not flash the device if it is on "qualcomm hs-usb diagnostics 9006" so i learnt how to format the eMMC with raw HDD tool and whenever i formatted the eMMC with the stock rom , the pc would identify the device under PORTS > "qualcomm hs-usb diagnostics 9008"
when using QPST i am given the error "sahara fail" , and when using eMMC software downloader i get the error "cookie not received" and sometimes timeout.
i cannot attempt to get my phone to revive my phone (it sticks on a logo and when it is completely off and plugged in it shows a battery charging animation).
- any insight on how to solve this?
- Is it a Software issue that can be solved without the intervention of hardware? is my issue strictly a hardware issue? (e.g malfunctioning logic board)?
i am ready to provide images and files or any further clarification if needed.
any help or guide into this issue would be greatly appreciated thanks for investing time into helping me and others.
AdelTheConfused said:
SITUATION:
hello , My phone is an asus x014d. recently I switched it off , and it just would not boot up again.
when i press the power on button it shows "powered by android" then the "asus" logo.
PROBLEMS:
- I CANNOT ENTER RECOVERY MODE (by doing the power on + vol up)
- I CANNOT ENTER TO FASTBOOT
- Device manager only identifies device as "qualcomm hs-usb diagnostics 9006" instead of "qualcomm hs-usb diagnostics 9008"
- when QFIL for unbricking it yields error "sahara fail"
- when using eMMC software Download the errors i get are "timeout waiting" , box dialog "cookie(if present) not received"
- managed to get into qualcomm hs-usb diagnostics 9008 mode but i can only manage to do that after getting to 9006 then flashing stock rom with RAW HDD TOOL then i am able to get into 9008.
TL;DR - DESCRIPTION (**NOOB ALERT**)
after research , i found out that my phone is bricked. i learnt that i have to get my phone identified by the computer through the "qualcomm usb drivers" then flash through "QFIL" a tool used for unbricking devices that have qualcomm processors.
i was able to successfully install the drivers , and plug my phone to the pc it shows that it is charging so i press the power plus volume up , then phone switches off and device manager never shows me the "qualcomm hs-usb diagnostics 9008" unless after switching off i immediately press volume down then device manager shows me "qualcomm hs-usb diagnostics 9006".
QPST will not flash the device if it is on "qualcomm hs-usb diagnostics 9006" so i learnt how to format the eMMC with raw HDD tool and whenever i formatted the eMMC with the stock rom , the pc would identify the device under PORTS > "qualcomm hs-usb diagnostics 9008"
when using QPST i am given the error "sahara fail" , and when using eMMC software downloader i get the error "cookie not received" and sometimes timeout.
i cannot attempt to get my phone to revive my phone (it sticks on a logo and when it is completely off and plugged in it shows a battery charging animation).
- any insight on how to solve this?
- Is it a Software issue that can be solved without the intervention of hardware? is my issue strictly a hardware issue? (e.g malfunctioning logic board)?
i am ready to provide images and files or any further clarification if needed.
any help or guide into this issue would be greatly appreciated thanks for investing time into helping me and others.
Click to expand...
Click to collapse
Try with official ASUS drivers or, try to use the com port mounted on the back of the motherboard, maby.. i wouldnt suggest it to use to com port. it would require some hardware knowledge