After flashing the wrong kernel, my Rogers E971 is hard bricked. Cannot access download, fastboot or recovery mode. ADB does not recognize the device. It was showing up in device manager as QHSUSB_DLOAD, I found the drivers and installed them, and now it shows up as Qualcomm HS-USB QDLoader 9008 (COM9). I've tried configuring QPST and using eMMC Software Download App, but everytime I click Download it gives this error: "Image Download Failed. Cookie(if present) not recieved."
Aside from JTAG repair, do I have any options?
Any help would be appreciated.
Thanks
sampeto said:
After flashing the wrong kernel, my Rogers E971 is hard bricked. Cannot access download, fastboot or recovery mode. ADB does not recognize the device. It was showing up in device manager as QHSUSB_DLOAD, I found the drivers and installed them, and now it shows up as Qualcomm HS-USB QDLoader 9008 (COM9). I've tried configuring QPST and using eMMC Software Download App, but everytime I click Download it gives this error: "Image Download Failed. Cookie(if present) not recieved."
Aside from JTAG repair, do I have any options?
Any help would be appreciated.
Thanks
Click to expand...
Click to collapse
I believe thats a hard brick..!!..since its showing HS USB in device manager..
Search for "TeenyBit for Lg Optimus G" in google. Youll easily unbrick your phone there.
Sent from my LG-E975 using xda app-developers app
I also had this problem and gave on warranty and they change mainboard
Envoyé de mon Nexus 7
Dear friends
I have a Wileyfox Swift phone bricked after trying to fastboot flash another OS.
Unfortunately It's completely dead now: It doesn't turn on, Its doesn't blink or shows no sign of connecting or recharging... In fact it is the pure meaning of a hard bricked phone
I tried many procedure and none of them worked. The phone is recognized by PC and is shown as "Qualcomm HS-USB QDLoader 9008" in Device Manager (I installed driver).
It would be appreciated soooo much if you could help me with this situation... Please...
I attempted to flash Dirty Unicorn from they're site, which appeared to go well, then I proceeded to flash the TWRPinstaller.zip that was suggested from the maintainer for our device. when I tried to reboot from recovery I got a no OS message. I ignored the message and attempted to reboot. Now the phone doesn't normally power on or off(which may change once the battery dies), no boot animation, no recovery, no fastboot recognition. The computer recognizes the phone as Qualcomm HS-USB QDLoader 9008. I googled for hours last night trying to fix to no avail. Has any of our great devs found a way to atleast recover the bootloader screen. I think I can handle it myself from there with adb.
Solved: Use the first blank flash from the link to get back to bootloader screenhttps://firmware.center/firmware/Motorola/Moto%20Z2%20Force/Blankflash/
From bootloaderscreen put your ADB skills to work. I'm not too good with guides but this just saved me $175
mookiexl said:
I attempted to flash Dirty Unicorn from they're site, which appeared to go well, then I proceeded to flash the TWRPinstaller.zip that was suggested from the maintainer for our device. when I tried to reboot from recovery I got a no OS message. I ignored the message and attempted to reboot. Now the phone doesn't normally power on or off(which may change once the battery dies), no boot animation, no recovery, no fastboot recognition. The computer recognizes the phone as Qualcomm HS-USB QDLoader 9008. I googled for hours last night trying to fix to no avail. Has any of our great devs found a way to atleast recover the bootloader screen. I think I can handle it myself from there with adb.
Click to expand...
Click to collapse
I did the same, got the same. Can't confirm the Qualcomm HS-USB QDLoader 9008 device will be there.
No charge, no screen, does not turn on/off, no vibration. Worst: no bootloader... Again, could be different if the battery dies.
mookiexl said:
Solved: Use the first blank flash to from the link to get back to bootloader screenhttps://firmware.center/firmware/Motorola/Moto%20Z2%20Force/Blankflash/
From bootloaderscreen put your ADB skills to work. I'm not too good with guides but this just saved me $175
Click to expand...
Click to collapse
Three questions:
1. File there is NDX26.183-15_17. Is it the same for OPXS27.109-34-10 on which I'm now? I suppose I need to use the "Oreo" version (2nd file in the list).
2. Which tool/software did you use to flash it? Is there a step by step tutorial?
3. You say "from bootloader screen". What about if we do not have a bootloader screen but a black brick in our hands?
Technical said:
I did the same, got the same. Can't confirm the Qualcomm HS-USB QDLoader 9008 device will be there.
No charge, no screen, does not turn on/off, no vibration. Worst: no bootloader... Again, could be different if the battery dies.
Three questions:
1. File there is NDX26.183-15_17. Is it the same for OPXS27.109-34-10 on which I'm now? I suppose I need to use the "Oreo" version (2nd file in the list).
2. Which tool/software did you use to flash it? Is there a step by step tutorial?
3. You say "from bootloader screen". What about if we do not have a bootloader screen but a black brick in our hands?
Click to expand...
Click to collapse
Answers
1.NDX26.183-15_17 (All it does is get your boatloader screen back
2. If you go to the device menu on your computer and your phone reads as Qualcomm HS-USB QDLoader 9008, all you have to do is click on the Blank flash all file and from the extracted folder and command prompt will do the rest. If the device is not recognized QDLoader 9008 then you will need to download qualcomm drivers to your computer
3.That is exactly what the file is for. Getting your black brick to at least the bootloader screen. From there you can adb recovery or stock rom.
What I ended up doing was adb push the bootable TWRP from the this thread https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932.
Flash the TWRP the official for our device from they're site(the bootable TWRP will give you access to extsd and thats where I had the official TWRP )
Rebooted back to bootloader and adb the firmware files for my device from the AOISP thread and rebooted my phone and I was booting DU.
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Dany XP said:
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Click to expand...
Click to collapse
Before connecting the phone, start the blankflash program. Maybe you have to repeat it a couple of times. Also try different cables, ports and computers.
Dany XP said:
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
mookiexl said:
Answers
1.NDX26.183-15_17 (All it does is get your boatloader screen back
2. If you go to the device menu on your computer and your phone reads as Qualcomm HS-USB QDLoader 9008, all you have to do is click on the Blank flash all file and from the extracted folder and command prompt will do the rest. If the device is not recognized QDLoader 9008 then you will need to download qualcomm drivers to your computer
3.That is exactly what the file is for. Getting your black brick to at least the bootloader screen. From there you can adb recovery or stock rom.
What I ended up doing was adb push the bootable TWRP from the this thread https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932.
Flash the TWRP the official for our device from they're site(the bootable TWRP will give you access to extsd and thats where I had the official TWRP )
Rebooted back to bootloader and adb the firmware files for my device from the AOISP thread and rebooted my phone and I was booting DU.
Click to expand...
Click to collapse
Can somebody please help me, my laptop isn't even detecting my device as QDLoader 9008, can you please tell me which windows os version did you use, also did you use the usb cable came in the box and did you use usb 2.0 port or 3.0?
LØNEWØLF said:
Can somebody please help me, my laptop isn't even detecting my device as QDLoader 9008, can you please tell me which windows os version did you use, also did you use the usb cable came in the box and did you use usb 2.0 port or 3.0?
Click to expand...
Click to collapse
Well, you need of course, Qualcomm loader driver, to at least having your device recognized as 9008. There u go: https://www.androidbrick.com/download/latest-2017-qualcomm-diag-qd-loader-windows-10-drivers-signed/
After that, go ahead with blankall and stuff...
P.s. and yes ..stay away from USB 3.0! ???
Dany XP said:
Well, you need of course, Qualcomm loader driver, to at least having your device recognized as 9008. There u go:
After that, go ahead with blankall and stuff...
P.s. and yes ..stay away from USB 3.0!
Click to expand...
Click to collapse
Thanks for the reply bro....but I have that driver installed...I installed before connecting it....still not detecting... I'm gonna try this once more in my friend's pc... let's see what happens
LØNEWØLF said:
Thanks for the reply bro....but I have that driver installed...I installed before connecting it....still not detecting... I'm gonna try this once more in my friend's pc... let's see what happens
Click to expand...
Click to collapse
I know it's a long shot but...do u have any other Qualcomm device to try?
U can enter EDL mode with adb command "adb reboot edl". Yes, it's that simple. ?
Dany XP said:
I know it's a long shot but...do u have any other Qualcomm device to try?
U can enter EDL mode with adb command "adb reboot edl". Yes, it's that simple. ?
Click to expand...
Click to collapse
OK I'll try...but how would I get back from edl to Normal without doing anything in the edl?
LØNEWØLF said:
OK I'll try...but how would I get back from edl to Normal without doing anything in the edl?
Click to expand...
Click to collapse
Uh...good question
Upgrade:
I need some files to run QFIL:
prog_emmc_firehose_8996.mbn (.elf)
rawprogram0.xml
patch0.xml
https://forum.xda-developers.com/ha...e-progemmcfirehose8996-mbn-elf-qfil-t3867750/
---------------------
Brick black screen Qualcomm HS-USB QDLoader 9008 (COM20). I need help please
Please, I need a lot of help. I will give you all the details I can.
I have always used the following ROM:
G891AUCS2API2_CL8737252_QB10881022_REV02_user_low_ship_MULTI_CERT
I have never had problems with this ROM. I wanted to try the AT & T ROM pirmera (it's an official ROM) and I installed it with modified Odin3 3.12. I have always used this Odin without problem. The ROM that has generated the problem is this:
SM-G891A_G891AUCU1APG7_ATT_Full_Repair_Frimware
I installed it with the same options as ROM REV02, so the problem is not Odin's. I think the problem is having downloaded Android version.
When I installed the ATT_Full_Repair_Frimware ROM, Odin said there was success. However, the phone did not turn on.
I tried to charge the phone, without success. Neither does any combination of buttons work.
When I connected the mobile to the computer, a driver was installed:
Qualcomm HS-USB QDLoader 9008 (COM20)
I also think that I read something from QFIL.
This is the only thing I have achieved. Odin does not work in this mode. I'm finding some weird Internet programs:
qpst.win_.2.7_installer_00472.4
Qualcomm Premium Tool V2.4 cracked + WORKING KEYGEN
This is a very difficult case for me and the people in my group of computer friends do not have the ability to solve this problem either. Only XDA can help me.
@NotSoMiniGun, please.
@Slade8525, please.
@activefan01, please.
Hello,
My device randomly shut down the other day and won't come back to life at all.
It doesn't go into fastboot or recovery mode, it just shows up in windows as Qualcomm HS-USB QDLoader 9008. From what I understand, this means the phone is in "EDL Mode"?
I have tried:
- Letting the battery completely drain and attempt to turn it on
- Using the recovery tools Google provides
- Using android platform tools to trigger fastboot/recovery
Nothing seems to be working at the moment. I am a bit noob-ish, so maybe there's a troubleshooting step I missed?
I'd like to get this device recovered. Has anyone run into this issue and solved it? Any advice is appreciated!
Thanks in advance!
Unfortunately there is no way to recover the device, as the software and files required are not publicly available. You could have it repaired but they will just replace the main board.