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 my LG G3 D858HK 32GB is hard BRICKED

Please could an expert help me unbrick my device, I flashed lollipop autorec on Marshmallow:/ I tried willcracker but stuck in BoardDiag v2.99a with ERROR – MAX number of partition.
In my Device manager I get Qualcomm HS-USB QDLoader 9008. Been trying for a week now!!! HHHHEEEEELLLPPPPPPPPPP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

HD2wally said:
Please could an expert help me unbrick my device, I flashed lollipop autorec on Marshmallow:/ I tried willcracker but stuck in BoardDiag v2.99a with ERROR – MAX number of partition.
In my Device manager I get Qualcomm HS-USB QDLoader 9008. Been trying for a week now!!! HHHHEEEEELLLPPPPPPPPPP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Try to go download mode if you can...switch of your phone....hold volume up and connet the cable see if you able to enter dowload mode then flash a kdz....kdz would be different from your current version....for example if you have v30b flash v30c

i also have the same issue. im now looking for partition.txt file anyone has it?

Espinosa_Rommel said:
i also have the same issue. im now looking for partition.txt file anyone has it?
Click to expand...
Click to collapse
U can extract it from kdz via boarddiag
my phone had error when detect emmc , I couldn't find the way to unbrick it
Sent from my Optimus G using XDA-Developers mobile app

paul_zm said:
U can extract it from kdz via boarddiag
my phone had error when detect emmc , I couldn't find the way to unbrick it
Sent from my Optimus G using XDA-Developers mobile app
Click to expand...
Click to collapse
after i extract tot and kdz theres no partition.txt inside. boarddiag show "not responding"

Anik49 said:
Try to go download mode if you can...switch of your phone....hold volume up and connet the cable see if you able to enter dowload mode then flash a kdz....kdz would be different from your current version....for example if you have v30b flash v30c
Click to expand...
Click to collapse
No I can't get download mode but is seen in device manager as Qualcomm HS-USB QDLoader 9008. Every time I try BoardDiag v2.99a it stops with this, "ERROR – MAX number of partition". Only sign of life is red and blue LED flashing. If I pull the battery and connect USB without battery holding volume up it shows a connection symbol on the phone screen.

I am on the same page
Is there any fix for this error message ?
Thanks
Paolo

lg g4 h818p no recovery,no download,stuck on logo and no QDLoader 9008

https://www.youtube.com/watch?v=91iQV5hm-Yw
this video above is my situation. when i go to download mode it redirects to lg logo.
i cant find a way that my pc detects my lg g4.
when i check in device manager there is no device either qualcom or qdloader
HELP ME PLEASE!

up

august28th330 said:
https://www.youtube.com/watch?v=91iQV5hm-Yw
this video above is my situation. when i go to download mode it redirects to lg logo.
i cant find a way that my pc detects my lg g4.
when i check in device manager there is no device either qualcom or qdloader
HELP ME PLEASE!
Click to expand...
Click to collapse
I have the same problem, i used Win32 to write system.img then "EMMC_ROM1_032G74_1803230737_00000000_20000000" on SD card to enter download mode but i get bootlooped after like 5sec i get in dw mode.
I used QFIL but it fails all the time.
Idk what else to try...

up

to acess QDLoader 9008 you need to short two pings in the motherboard

el.adnane said:
to acess QDLoader 9008 you need to short two pings in the motherboard
Click to expand...
Click to collapse
so i should open my lg g4? is it safe?

august28th330 said:
so i should open my lg g4? is it safe?
Click to expand...
Click to collapse
its already wasted so there is nothing wrong in trying but if u dont know let someone else do it

{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?