Hello, my phone Lumia 920 was bricked and it doesn't boot up or respond to any of the input combinations(Vol up +power ) or ( Vol. down + power) it's just showing a black screen and when I connected it to a windows 7 pc it showed as (QHSUSB_DLOAD) and windows failed to install drivers for it I searched online and I reached the Qualcomm drivers for (QHSUSB_DLOAD) mode and now the device is readable as (Qualcomm HS-USB QDLoader9008) in the Ports(COM & LPT) section in device manager and can't do anything beyond that ... any help on how to recover this state to a normal working one using any method even if on a Linux based system computer? I need real help
Hi,
I have a following problem with my Redmi 4X. I tried to flash new rom and reboot my phone on twrp. When the phone shut down nothing happens anymore just black screen. No fastboot or recovery mode. When I contact the phone to Windows pc it shows in device manager: Qualcomm HS-USB Diagnostics 900E (COM20). I have tried to flash new rom with QFIL and Miflash (tried to change the driver to Qualcomm HS-USB QDLoader 9008).
With QFIL the error is: Download Fail: Switch to EDL FailFailed to switch to Emergency Download mode.
With Miflash the error is: Cannot receive hello packet. MiFlash is trying to reset status!
Any suggestions?
https://www.youtube.com/watch?v=uxrhJkSZc6E
Already tried that. Doesn't seem to change a thing.
Shouldn't it turn the driver to "Qualcomm HS-USB QDLoader 9008" after test point method?
This is what shows in command prompt:
C:\Windows\system32>adb reboot edl
error: device '(null)' not found
C:\Windows\system32>adb devices
List of devices attached
C:\Windows\system32>
k4rpp4 said:
Shouldn't it turn the driver to "Qualcomm HS-USB QDLoader 9008" after test point method?
This is what shows in command prompt:
C:\Windows\system32>adb reboot edl
error: device '(null)' not found
C:\Windows\system32>adb devices
List of devices attached
Click to expand...
Click to collapse
After the test point method you will see a new "9008" device in the Device Manager.
Then all of the above commands will be completely irrelevant and useless.
In the 9008 mode use MiFlash, not QFIL/QPST, to reflash your phone.
Cheers!
The test points seems to change nothing. I think that after the " adb devices" command I should see my device listed but that is not the case and therefore impossible to flash rom. Somehow I should be able to change the "900E mode" to "9008 mode" without changing the driver manually and I think the test point method should do just that.
Here is video of what I have tried to do. If someone could point out what to do differently to get the flash work I would be very grateful.
https://drive.google.com/open?id=1aOkb3FCBzanMUW3WSdyuxyQO-33rdsBv
Windows 10 will not accept the 9008 driver because the driversignature ist not signed from Microsoft.
If you will unbrick it with Windows 10 64bit look here: https://www.youtube.com/watch?v=2d8KEruHWPg
and here: https://www.maketecheasier.com/install-unsigned-drivers-windows10/
Had allready done that also. Gave it another try without success
k4rpp4 said:
Had allready done that also. Gave it another try without success
Click to expand...
Click to collapse
Is the Qualcomm 9008 driver now installed?
Did you start the mi-flash tool with administrator privileges?
I installed the Qualcomm drivers but device manager still shows 900E driver unless I manually change it to 9008.
edit:
I finally succeeded with test point method. Now flashing. Im so grateful to you ConradB.
k4rpp4 said:
I installed the Qualcomm drivers but device manager still shows 900E driver unless I manually change it to 9008.
edit:
I finally succeeded with test point method. Now flashing. Im so grateful to you ConradB.
Click to expand...
Click to collapse
Perfect :good:
Bro please help my device in bricked
k23m said:
After the test point method you will see a new "9008" device in the Device Manager.
Then all of the above commands will be completely irrelevant and useless.
In the 9008 mode use MiFlash, not QFIL/QPST, to reflash your phone.
Cheers!
Click to expand...
Click to collapse
Thank you buddy .. Your 4 years old post help me to turn on my hard brick redmi 4x.
I don't know the actual reason of hard brick but The situation was my phone was in condition like
1. Possible to go in fastboot mode
2. When turning on there is only mi logo for fraction of second.
I tried test point method as described . It turned on in one attempt..I just want to add something. I face some issues after test point flashing . So I just flash miui again . Then It's working perfectly fine. After Test point flash check your battery. Maybe fully drained. Just charge it and turn it on..
I am posting this just for Information..
sayan990 said:
Thank you buddy .. Your 4 years old post help me to turn on my hard brick redmi 4x.
I don't know the actual reason of hard brick but The situation was my phone was in condition like
1. Possible to go in fastboot mode
2. When turning on there is only mi logo for fraction of second.
I tried test point method as described . It turned on in one attempt..I just want to add something. I face some issues after test point flashing . So I just flash miui again . Then It's working perfectly fine. After Test point flash check your battery. Maybe fully drained. Just charge it and turn it on..
I am posting this just for Information..
Click to expand...
Click to collapse
I do had same issue with my mobile but even when I tried to flash MIUI I got "ACK count don't match" attached img
so I can connect my bricked phone to a Windows PC by shorting the test points. But the device (Qualcomm HS-USB QLoader xxx) also keeps on disappearing in Device Manager. In most cases, the device only shows up in Device Manager for 1 second and disappears immediately.
Any ideas on how to fix?
Thanks
edit1: tried on a laptop running Windows 10 and another laptop running Windows 7.
edti2: My phone is stuck in a bootloop. I cannot even get it to boot into fastboot mode.
My Zenfone 4 ZE554KL is bricked and only shows on windows Qualcomm HS-USB QDLoader 9008, after I tried to debrick it from fastboot, using a firmware raw image, and putting the incorrect fastboot reboot command
"fastboot reboot emergency" and now is after I plug the usb stick it shows on windows as the QComm Com port but I tried to see guides, read everything, tried to use QFIL to check if something works and QPST
But still without success
Current phone status is a black screen and nothing else, already attempted to hold power, some few sequences with Vol Up, Vol Down still nothing.
Hi i got an ASUS ROG 3 I003DD ZS661KS - 6A017CN TENCENT edition bricked while updating any solution? I tried everything from computer but not opening at all, screen total black and no recovery mode starts,
Any help is appreciated
what is the device showing identified as under device manager when plugged in from the side port?
Nothing black screen, i tried up down button and power but nothing, few days ago recovery mode worked now nothing.. i tried to look some programm for force boot the phone through pc but all websites link are empty, I don’t know what to do.. i was updating the phone then this happened..
Get the device in EDL mode with working Qualcom drivers and a good connection to your pc. Then follow below guide, all needed looks to be there. You can get the device in EDL mode with a flash cable that you can buy cheap or make one yourself from a USB cable - there are guides online for doing that too.
[UNBRICK/RAW] Revive your bricked ASUS ROG Phone 3 [23-NOV-2021]
Unbrick your ASUS ROG Phone 3 for free!! Don't pay for this stuff anywhere, it's your device and you deserve the right to fix it yourself. I noticed some people in the community charging upto 50$ for the firmware which should've been free from...
forum.xda-developers.com
I connected the phone with EDL cable the computer recognize as Qualcom device etc.. but
i tried to flash the raw stock firmware trough pc and EDL cable but nothing says Sahara error mode while the process