Dear's, My phone has been dead it's don't boot into download or recovery mode when I connect it to the
laptop it's shown as Qualcomm HS-USB QDLoader 9008, I have been tired to search for resolve this problem
I need full support please, like make sd card boot, and the file that I need it to repair emmc also explain how to do all things
because I have no idea to how to do it, thanks in advance for all:laugh::laugh:
Related
Hi all, I'm new here and i have a malfunctioned phone so thought I'd give this a shot and learn some stuff from you guys..
I have a bricked galaxy s3 which cant get into download mode. Computer detects it as Qualcomm HS-USB QDloader 9008 in device manager and QPST software sees it in download mode via the same COM port.
Now I want to know... is there any luck is this phone completely dead? and what if i send it back for repair (i took it for JTAG and i was told the chip that boots the phone is burnt out when flashing a corrupted rom)
If you have any info or experience regarding this your help is much needed and appreciated.
4tunecookie said:
Hi all, I'm new here and i have a malfunctioned phone so thought I'd give this a shot and learn some stuff from you guys..
I have a bricked galaxy s3 which cant get into download mode. Computer detects it as Qualcomm HS-USB QDloader 9008 in device manager and QPST software sees it in download mode via the same COM port.
Now I want to know... is there any luck is this phone completely dead? and what if i send it back for repair (i took it for JTAG and i was told the chip that boots the phone is burnt out when flashing a corrupted rom)
If you have any info or experience regarding this your help is much needed and appreciated.
Click to expand...
Click to collapse
It is hard bricked my friend a lot of us have suffered this also, JTAG or maybe warranty is your only option.
I used the LG Flash Tool 2014 for my device to try to recover from a bricked phone. And I think i made it worse after using the kdz file and it completed 100%. I took the battery out and unplugged the phone when it was done. It wont even show anything on the screen now or go into recovery mode. But I do show RELINK HS-USB QDLoader 9008 (COM5) under the device options in my device manager when I connect the phone to the computer. Also it does make the device connected sound when I plug it in the computer. What can I do to get out of this mess? Thanks in the advance for any help that I can get.
Any help will be appreciated. THanks.
Can someone be kind enough to make a Debrick.img from their working sm-g3815? been searching for some days now. phone's dead as it wont boot to dl mode/recovery mode but computer recognizes the phone as 'qualcomm hs-usb qdloader 9008'
hi guys
i have pixel 128gb g-2pw4200 and after reboot my device dont turn on and dont have any response
i dont have a recovery fastboot and ....
in my device manager detect as CPU (detect only as Qualcomm HS-USB QDLoader 9008)
how can i fix it?!?!
Thanks
when you hold down the vol-down and power, does it send you to the bootloader screen?.
Is your bootloader locked?
Did you do anything non-standard to it (like load a ROM, kernel, etc)?
Looks like someone else had the same issue: https://forum.xda-developers.com/pixel-xl/help/help-pixel-xl-hs-usb-qdloader-9008-mode-t3574278
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