Develop Bugs

Hard Brick - Quectel QDloader 9008 COM4 Mode, Help needed

Hi All,
Is there any way to recover the phone from the Quectel QDloader 9008 COM mode ? Screen not coming up, no adb or fastboot mode, the only think I see in the Windows Device Manger is that the phone is connected as COM Port.
Thx for any advice.

Have the same issue - were you able to figure out how to fix it?

The only way to fix it would be to have a copy of the ROM that can be flashed in EDL mode, which is the mode your device is in. Google doesn't make EDL-flashable copies of its ROMs available - not a surprise - since that mode is mainly for tech support personnel. I'm afraid your only recourse is to contact Google and see what they can do for you.

freshmike said:
Hi All,
Is there any way to recover the phone from the Quectel QDloader 9008 COM mode ? Screen not coming up, no adb or fastboot mode, the only think I see in the Windows Device Manger is that the phone is connected as COM Port.
Thx for any advice.
Click to expand...
Click to collapse
Phone should still be covered under manufacturer's warranty if anything call it in see you at the phone shut off and did that and they'll replace it

@freshmike what did you do to get to this state?

davidcie said:
@freshmike what did you do to get to this state?
Click to expand...
Click to collapse
No idea, not mine got it from a friend to try to fix. I think the memory is grilled. On the other hand there are so many complains regarding the quality of Pixel phones, I would not want one even as a gift

try it !

Qualcom HS USB Diagnostics 900e

After requesting repair at the official OnePlus Side, they told me to backup my phone(Stock OP 7T). When i connected it to my Windows PC it didnt appear in the Windows Explorer. After some scearching i could find it in the Device Manager under COM5 with the Name given in title. I am worried because when i googled Qualcom Diagnostics i saw that my device might be bricked or smth. But i didnt try to flash any new software or anything alike. i didnt charge my device for over a week so could theren be a connection with missing Power/Battery and this problem. Because my Screen is broken (Blackscreen) I cant see any info might given by the Phone itself. The only sign of functionalty is the detection by Windows.
Maybe someone has Tipps or a Solution for me

Trencosta said:
After requesting repair at the official OnePlus Side, they told me to backup my phone(Stock OP 7T). When i connected it to my Windows PC it didnt appear in the Windows Explorer. After some scearching i could find it in the Device Manager under COM5 with the Name given in title. I am worried because when i googled Qualcom Diagnostics i saw that my device might be bricked or smth. But i didnt try to flash any new software or anything alike. i didnt charge my device for over a week so could theren be a connection with missing Power/Battery and this problem. Because my Screen is broken (Blackscreen) I cant see any info might given by the Phone itself. The only sign of functionalty is the detection by Windows.
Maybe someone has Tipps or a Solution for me
Click to expand...
Click to collapse
If you connect your phone to pc while its off and holding the volume down button it will boot into Qualcomm recovery mode which is what you are seeing. I suggest you find a way to switch it off and boot it up again

Is my supposed non-brickable ZUK Z2 bricked????

Having searched far and wide for a solution for my problem (and stumbling across the fact that it is great that the ZUK Z2 is really not brickable) I wonder if there is not one...?
I was simply attempting to flash the Lineage rom (coming from AEX) but kepy getting an Error 7 (if I remember correctly), which is apparently fairly common, but for which none of the proposed solutions was working for me.
It was suggested to carry out a FULL WIPE (so I did this, including internal storage).
I then installed an alternative recovery mode to TWRP (the current one), without actually removing TWRP...so possible conflict here...?
So:
There is currently no OS on phone
I can open my phone in fastboot mode
Impossible to open recovery mode (which is the real killer)
Impossible to get phone recognised as external drive (and hence modify what is on it) - I can get it recognised by the device manager but only as QL.... not my actual phone
Impossible to communicate with phone through adb (logic, since phone not recognised
Since I cannot communicate with the phone in any way OR get the phone into recovery mode, my hands are tied as I see it...I really don't know what can be done from here :crying:
If anyone has any idea of how my phone could be saved, your help would be VERY MUCH appreciated
Thank you in advance for any feedback at all.
Charlie

chazhammer said:
Having searched far and wide for a solution for my problem (and stumbling across the fact that it is great that the ZUK Z2 is really not brickable) I wonder if there is not one...?
I was simply attempting to flash the Lineage rom (coming from AEX) but kepy getting an Error 7 (if I remember correctly), which is apparently fairly common, but for which none of the proposed solutions was working for me.
It was suggested to carry out a FULL WIPE (so I did this, including internal storage).
I then installed an alternative recovery mode to TWRP (the current one), without actually removing TWRP...so possible conflict here...?
So:
There is currently no OS on phone
I can open my phone in fastboot mode
Impossible to open recovery mode (which is the real killer)
Impossible to get phone recognised as external drive (and hence modify what is on it) - I can get it recognised by the device manager but only as QL.... not my actual phone
Impossible to communicate with phone through adb (logic, since phone not recognised
Since I cannot communicate with the phone in any way OR get the phone into recovery mode, my hands are tied as I see it...I really don't know what can be done from here :crying:
If anyone has any idea of how my phone could be saved, your help would be VERY MUCH appreciated
Thank you in advance for any feedback at all.
Charlie
Click to expand...
Click to collapse
Which recovery comes when you choose recovery option when you choose recovery by pressing start when phone is powering on before zuk logo..
You can use cable method (by shorting cable and going to edl mode) and qpst to safety.

sanjay.2704 said:
Which recovery comes when you choose recovery option when you choose recovery by pressing start when phone is powering on before zuk logo..
You can use cable method (by shorting cable and going to edl mode) and qpst to safety.
Click to expand...
Click to collapse
Thank you very much for your suggestion, Sanjay, it is very much appreciated :good:
When I choose recovery, everything just "hangs" - black screen that doesn't go anywhere (that's why I thought that maybe there was some kind of conflict, where the phone didn't know how to chose between the two options perhaps (pure specuclation!)
I have tried the solution you suggest, but it didn't work for me.
I will re-attempt this an extra ten times or so (you never know) just in case, and let you know how things go.
This one:
(https://forum.xda-developers.com/lenovo-zuk-z2/how-to/reboot-to-edl9008-modetotally-bricked-t3720932)

OK, so still no luck...
I used a method to use some tinfoil in the usb to get the device recognised in the device manager - it appears as => Android Device >> ShenQi Composite ADB Interface
The phone is in fastboot mode at this stage.
However, in ADB still no recognition of the phone
When entering "adb devices" I get "List of devices attached" and then blank
If I try "fastboot oem edl" I get < waiting for device >
"Adb reboot edl" gives me => "error: device not found"d
So essentially it still comes down to the fact that my device is not detected...although strangely there are signs of life in device manager (although I don't know what ShenQi Composite ADB Interface refers to ???)
Alternatively I see that it is possible to actually buy an EDL cable from China or something (https://www.magnetforensics.com/blog/qualcomm-phone-edl-mode/)
This appears to be restricted to other devices, but similar issue:
https://www.xda-developers.com/exploit-qualcomm-edl-xiaomi-oneplus-nokia/
Other devices can also use what’s known as a “deep flash” cable, which is a special cable with certain pins shorted to tell the system to instead boot into EDL mode. Old Xiaomi devices can utilize this method, along with the Nokia 5 and Nokia 6. Other devices will also boot into EDL mode when they fail to verify the SBL.
Does anyone know if this would actually work with an EDL cable approach???
Any other ideas out there?
I'd be willing to give someone some money if they were able to work through this issue with me, if they think that there is a solution here..else the phone is just spare parts :-/
Thank you in advance,
Charlie

For a little added information, the other recovery was: TWRP Red Wolf
(https://zukfans.eu/community/thread...r-image-error-7-installing-a-custom-rom.8347/)
While flashing this with TWRP there was an option to flash to.... I don't remember the options and can no longer consult to check, BUT at 2am, about to give up, and not knowing exactly what to select, I selected about 3 options at this stage
I believe there were something like 5 options and I selected "boot" I think, plus..?
Very stupid of course and obviously I was too confident in not creating a problem that couldn't be solved!
I have been playing around with flashing ROMs etc for the last 10 years, over 3/4 different devices and despite having read all the warnings, since over this time I have never had any issues, I kind of considered it to be almost impossible to get into a situation where things are irretrievable...so my comuppance :-/
Again, if anyone has any ideas, I would greatly appreciate

chazhammer said:
OK, so still no luck...
I used a method to use some tinfoil in the usb to get the device recognised in the device manager - it appears as => Android Device >> ShenQi Composite ADB Interface
The phone is in fastboot mode at this stage.
However, in ADB still no recognition of the phone
When entering "adb devices" I get "List of devices attached" and then blank
If I try "fastboot oem edl" I get < waiting for device >
"Adb reboot edl" gives me => "error: device not found"d
So essentially it still comes down to the fact that my device is not detected...although strangely there are signs of life in device manager (although I don't know what ShenQi Composite ADB Interface refers to ???)
Alternatively I see that it is possible to actually buy an EDL cable from China or something (https://www.magnetforensics.com/blog/qualcomm-phone-edl-mode/)
This appears to be restricted to other devices, but similar issue:
https://www.xda-developers.com/exploit-qualcomm-edl-xiaomi-oneplus-nokia/
Other devices can also use what’s known as a “deep flash” cable, which is a special cable with certain pins shorted to tell the system to instead boot into EDL mode. Old Xiaomi devices can utilize this method, along with the Nokia 5 and Nokia 6. Other devices will also boot into EDL mode when they fail to verify the SBL.
Does anyone know if this would actually work with an EDL cable approach???
Any other ideas out there?
I'd be willing to give someone some money if they were able to work through this issue with me, if they think that there is a solution here..else the phone is just spare parts :-/
Thank you in advance,
Charlie
Click to expand...
Click to collapse
Edl cable approach would work for you.. Here is the thread guide for you..
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/deep-flash-revive-zuk-z2-hard-brick-t3577146..
Also I would suggest to stick to official twrp as that's more stable as compared to redwolf..
Hit thanks if it helps.

Thank you again Sanjay.
I have ordered a new lead (to cut open and attempt this intervention)!
I will let you know how I get on.

OK, I have done the cable trick and PORTS shows up in the device manager as "Qualcomm HS-USB QDLoader 9008 (COM5)", which seems to correspond with what was needed.
What should I do next exactly ?
The phone no longer actually shows any signs of life - I hope this is normal

chazhammer said:
OK, I have done the cable trick and PORTS shows up in the device manager as "Qualcomm HS-USB QDLoader 9008 (COM5)", which seems to correspond with what was needed.
What should I do next exactly ?
The phone no longer actually shows any signs of life - I hope this is normal
Click to expand...
Click to collapse
You can go ahead with qfil now.. You should see same port in qfil as well.
Once qpst is completed phone should boot up..

After some issues with the Sahara error (needed to update to edl mode and press download immediately) I finally managed to flash back to stock ROM
Thank you for all of your help!!!

Help with Hardbricked g4 h735ar

Hello, I need help with my LG, the cell phone ran out of battery while updating firmware, now I cannot enter download mode, nor fastboot, and the recovery does nothing, when I turn on the cell phone it always ends up in a black screen with a text of the type "CMD" putting a number and something of "udc_start" and that's it.
windows 10 makes the normal beep but does not recognize the model, in the device manager "android device" appears with the warning sign that there are no drivers.
LGUP does not recognize the device
The only way I had to "make windows recognize it" was with "QFIL" and touching the two pins on the motherboard, in the program it says:
"qualcomm hs-usb qdloader 9008 (com4)"
I have never flashed a cell phone bios or a bootloader if I misunderstand (I am relatively new to android), I have only flashed "the operating system" in this case a 1gb .kdz
I have no idea how to do this, if I don't misunderstand, I need a .mbn (I think it's the bios), which is compatible with QFIL, which I couldn't find in all of google.
I've come across other .mbn of "similar" g4 models, I wonder if it will work if I at least try them.
They may not work perfectly, but at least turn on.
What do you suggest? I feel lost in an ocean t-t

Wachecheiro said:
Hello, I need help with my LG, the cell phone ran out of battery while updating firmware, now I cannot enter download mode, nor fastboot, and the recovery does nothing, when I turn on the cell phone it always ends up in a black screen with a text of the type "CMD" putting a number and something of "udc_start" and that's it.
windows 10 makes the normal beep but does not recognize the model, in the device manager "android device" appears with the warning sign that there are no drivers.
LGUP does not recognize the device
The only way I had to "make windows recognize it" was with "QFIL" and touching the two pins on the motherboard, in the program it says:
"qualcomm hs-usb qdloader 9008 (com4)"
I have never flashed a cell phone bios or a bootloader if I misunderstand (I am relatively new to android), I have only flashed "the operating system" in this case a 1gb .kdz
I have no idea how to do this, if I don't misunderstand, I need a .mbn (I think it's the bios), which is compatible with QFIL, which I couldn't find in all of google.
I've come across other .mbn of "similar" g4 models, I wonder if it will work if I at least try them.
They may not work perfectly, but at least turn on.
What do you suggest? I feel lost in an ocean t-t
Click to expand...
Click to collapse
Check out this thread:
[GUIDE][9008][EDL|QDL][QUALCOMM ONLY] Unbrick via external sdcard (no QFIL!)​The author is the definitive LG G4 hard-brick answer guy with possible solutions. You may be able to get some help there.

sdembiske said:
Check out this thread:
[GUIDE][9008][EDL|QDL][QUALCOMM ONLY] Unbrick via external sdcard (no QFIL!)​The author is the definitive LG G4 hard-brick answer guy with possible solutions. You may be able to get some help there.
Click to expand...
Click to collapse
I'll take a look at it, thanks

Seems like a similar problem as I had, that's not gonna work though. The only way to fix it is to use a firehose which you can use a one from a Cyanogen MSM8939 device.

Qualcomm HS-USB QDLoader 9008 Issue

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.