Develop Bugs

Hard-Bricked E971, Help?

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

[HELP] Bricked my Nexus 5x...

So i've bricked my Nexus 5x (h791) 32gb by flashing the Nexus 5 bootloader onto it. i've been searching for a few days and managed to get phone phone to switch between "qualcomm HS-USB QDLoader 9008" and " QHSUSB_BULK"
it shows as unknown model on LGUP when i force the "LGE Android Platform USB serial port" or "LGE Mobile USB serial Port" other than that it wont show up in LGUP.
I have tested this on 2 windows machines. one being windows XP the other windows 10. i do have a pc running ubuntu which i can use but i wouldnt know where to start when using that.
Any help or advice would be much appreciated!

you find any solution? i have the same problem but i am iam in fisrt phase qualcomm 9008. i searcing 3 days but i find results only for nexus 5 not 5x . pls anyone may help us

me to , have this problem , it's been a week .
i don't know why 5x have download mode .

looking for the same solution ... Nexus 5X bricked with Qualcomm 9008 if you got anything please contact me for djbebe at g55gle

this might help
use BoardDiag

Duckscreen said:
use BoardDiag
Click to expand...
Click to collapse
Latest available BoardDiag does not support N5X..
I asked LG service, and that DONT HAVE any software for 5x, so only way is replace entire motherboard.
So, at the moment, 5x with broken GPT or boot - is not repairable... I will try to flash a full-flash in new empty EMMC, and replace chip, but so many risks.

spastikitten said:
So i've bricked my Nexus 5x (h791) 32gb by flashing the Nexus 5 bootloader onto it. i've been searching for a few days and managed to get phone phone to switch between "qualcomm HS-USB QDLoader 9008" and " QHSUSB_BULK"
it shows as unknown model on LGUP when i force the "LGE Android Platform USB serial port" or "LGE Mobile USB serial Port" other than that it wont show up in LGUP.
I have tested this on 2 windows machines. one being windows XP the other windows 10. i do have a pc running ubuntu which i can use but i wouldnt know where to start when using that.
Any help or advice would be much appreciated!
Click to expand...
Click to collapse
Have you got the phone back to life??

[SOLVED][DEB/FLO] Drivers Required

I have been experimenting with my nexus 7 2013 and the diagnostic mode. I have had issues finding appropriate drivers for the tablet's diagnostic mode. Whenever I switch to the diagnostic mode the windows driver manager shows up the devices as in the image.
Can someone please provide me with diagnostic drivers for the nexus 7 2013.

jared.leto said:
I have been experimenting with my nexus 7 2013 and the diagnostic mode. I have had issues finding appropriate drivers for the tablet's diagnostic mode. Whenever I switch to the diagnostic mode the windows driver manager shows up the devices as in the image.
Can someone please provide me with diagnostic drivers for the nexus 7 2013.
Click to expand...
Click to collapse
Here is QPST Diagnostics driver and all other USB drivers from Google.

k23m said:
Here is QPST Diagnostics driver and all other USB drivers from Google.
Click to expand...
Click to collapse
Hey thanks... I have tried these... they work too but still the QPST functions won't happen.... they just show errors relating to connectivity.

jared.leto said:
Hey thanks... I have tried these... they work too but still the QPST functions won't happen.... they just show errors relating to connectivity.
Click to expand...
Click to collapse
To enter Qualcomm Diagnostics mode please try:
turn N7 off
press and hold both vol buttons
plug in PC USB
Windows device manager should display a new item with hardware ID: VID_05C6&PID_9008
If not, please quote the VID/PID you get.

k23m said:
To enter Qualcomm Diagnostics mode please try:
turn N7 off
press and hold both vol buttons
plug in PC USB
Windows device manager should display a new item with hardware ID: VID_05C6&PID_9008
If not, please quote the VID/PID you get.
Click to expand...
Click to collapse
I get that in my device manager. Any idea how to use it with QPST programs? I need it to work so that I can fix my IMEI number.

jared.leto said:
I get that in my device manager. Any idea how to use it with QPST programs? I need it to work so that I can fix my IMEI number.
Click to expand...
Click to collapse
In 9008 mode the driver from QPST Diag package should register without an error and a new COM port will be available. Then QPST apps will work. I don't have a deb model but IMEI number must be in fsg - mmcblk0p8 partition I guess.

{Solved}I gotta super slim brick !!!!

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

Xiaomi mi a2 lite fastboot drivers?????

tell me where they are and i used universal adb and fastboot drivers when I went to unlock bootloader adb was working pretty well with the drivers however fastboot wasn't cuz it didn't show my device in fastboot device even if it was plugged to the pc

Attached

mr.onegin said:
Attached
Click to expand...
Click to collapse
but is it really safe i dont want my pc destroyed

succaBYLTA said:
but is it really safe i dont want my pc destroyed
Click to expand...
Click to collapse
Drivers are safe but flashing or unblocking anything never was
Actually there is a thread on XDA all ready official-tool-windows-adb-fastboot-and-drivers-15-seconds-adb-installer but drivers I presented are from another forum exactly for this device.

mr.onegin said:
Drivers are safe but flashing or unblocking anything never was
Actually there is a thread on XDA all ready official-tool-windows-adb-fastboot-and-drivers-15-seconds-adb-installer but drivers I presented are from another forum exactly for this device.
Click to expand...
Click to collapse
Well also is QDLoader setup 64-bit safe cuz when i opened QDloader setup for 64-bit It opened alot of cmds and that was sus for me so is It safe

mr.onegin said:
Drivers are safe but flashing or unblocking anything never was
Actually there is a thread on XDA all ready official-tool-windows-adb-fastboot-and-drivers-15-seconds-adb-installer but drivers I presented are from another forum exactly for this device.
Click to expand...
Click to collapse
And also What does QDLoader even does? I AM pretty New to this

succaBYLTA said:
And also What does QDLoader even does? I AM pretty New to this
Click to expand...
Click to collapse
First Google result...
QDLoader
This package (Qualcomm_QDLoader_HS-USB_Driver_64bit_Setup.zip) contains Qualcomm HS-USB QDLoader 9008 Drivers for Windows 10/7/8/8.1 64-Bit OS. This Qualcomm QDLoader Driver helps in detecting the device when it is connected to PC in EDL Mode or Download Mode.
This Qualcomm HS-USB Driver package is for 64-bit OS, you can download the 32-bit version of the driver here. If you would like to install the drivers manually, download these Qualcomm Drivers.

I installed all of them but still I cannot flash anything from fastboot. What can I do?