Database Users

Phone bricked help

status: Bricked
Access: No fastboot, No recovery However goes automatically to edl once connected to pc
Device manager recognizes as "Qualcomm HS-USB Qloader 9008 [port x] (x whichever usb port I connect)
all drivers installed.
Attempts:
1)Tried flashing via QFIL which gives an error "Download failed: Sahara fail: QsaharaServer fail: Process failed"
2)MIFlash
I have a laptop windows 10 with only 2 usb ports. As soon as I connect the device using usb cable, device manager shows under LPT/com ports as "Qualcomm HS-USB Qloader 9008 (port 5). Then I opened mi flash (also tried miflash beta), selected a fastboot image folder (extracted from tgz), select flash all, my then press refresh option, the tool will detect the phone as port -com 5 and then I clicked on flash. It'll send some signal to phone for 5 sec, and then stops giving error "cannot read from port com 5". I also tried it with other usb port (detects as port com 4).
please somebody help!
Edit: Used MI flash with Windows 7 compatibility mode. Worked like charm...

Use EDL cable, I just fixed it last week. It stuck at 900E not 9008. No fastboot, no recovery, Sahara failed

lintongprohacks said:
Hold down vol down+power to enter fastboot. Upgrade pc to win 10 to avoid issues as win 10 allows unsigned drivers with prompt
Click to expand...
Click to collapse
Read op. It's not possible to go to fastboot nor recovery. Phone just doesn't respond to anything.

arceuss said:
Read op. It's not possible to go to fastboot nor recovery. Phone just doesn't respond to anything.
Click to expand...
Click to collapse
Makes EDL cable by your self. Just take new cable data. Open the skin and sort green cable with black cable. Thats it.
Plug your phone with edl cable for about 3 second. Then open qfil. Setup qfil properly. Do not press download button yet.
But change your edl cable with normal data able.
Put the normal cable ( not edl cable) into your charging port of your phone.
Then plug in into usb port. As soon as you see Qualcomm 9008 port on Qfil press download button.
Qfil fails because waiting too long to press download button. Just press it immedietly after the qfil recognized the port.
If at the first try fail, repeat the prosses once again.
I now always flashing with qfil never use miui flash tool again..

https://forum.xda-developers.com/redmi-3/help/redmi-3s-hardbrick-t3650498
Charge%? Open if it is described in the subject

use TEST POINT

Thanks it worked for me
Thanks it worked for me

charge it for 12 hours +
Keep it for charging for 12 hours and then start i had such problems earlier.. or remove battery and charge the battery separately... the battery is been drained completely i suppose.

Bricked phone but can still get into EDL mode

Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.

daevion0 said:
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
Click to expand...
Click to collapse
I assume you're not on Windows 10 x64? If you aren't, either get a PC with Win10 x64, or do this:
Connect the phone, get into EDL mode. Now go to the Device Manager, and tell me where it appears.
It can appear as:
-"Qualcomm HS-USB QDLoader 9008" under Ports (COM & LPT);
-"ZTE DFU Interface, under Ports too; or
-"QUSB_BULK" under Universal Serial Bus devices or unknown devices.
If it appears as the DFU stuff, you'll have to follow the 4th category brick repair guide. If it appears as QDLoader, right click on it, then Properties, then go to Bits per second and put the number at 115200 or 128000 if it's not there. Then hold the 3 buttons (vol and power) until Windows beeps and the device manager spazzes and the phone flashes the red led, then try MiFlash again.
If it appears as QUSB_BULK, uninstall the driver (tick delete driver software too) and restart edl.

Choose an username... said:
I assume you're not on Windows 10 x64? If you aren't, either get a PC with Win10 x64, or do this:
Connect the phone, get into EDL mode. Now go to the Device Manager, and tell me where it appears.
It can appear as:
-"Qualcomm HS-USB QDLoader 9008" under Ports (COM & LPT);
-"ZTE DFU Interface, under Ports too; or
-"QUSB_BULK" under Universal Serial Bus devices or unknown devices.
If it appears as the DFU stuff, you'll have to follow the 4th category brick repair guide. If it appears as QDLoader, right click on it, then Properties, then go to Bits per second and put the number at 115200 or 128000 if it's not there. Then hold the 3 buttons (vol and power) until Windows beeps and the device manager spazzes and the phone flashes the red led, then try MiFlash again.
If it appears as QUSB_BULK, uninstall the driver (tick delete driver software too) and restart edl.
Click to expand...
Click to collapse
I'm on win10 64bit

daevion0 said:
I'm on win10 64bit
Click to expand...
Click to collapse
Then do everything I described above or just try another PC. It always happens that one PC can be decided not to let you unbrick your phone for some reason

Choose an username... said:
Then do everything I described above or just try another PC. It always happens that one PC can be decided not to let you unbrick your phone for some reason
Click to expand...
Click to collapse
Is there no other option? is there no other way to at least get fast boot mode back on my phone?

daevion0 said:
Is there no other option? is there no other way to at least get fast boot mode back on my phone?
Click to expand...
Click to collapse
Lol nope, not if EDL is not working for you. You still didn't tell me whether you have a DFU brick or not. If you do have a DFU brick the only surefire way is to disassemble your phone and short a testpad, so don't complain.
Try what I told you above. It may be that it's set at 9600 baud

daevion0 said:
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
Click to expand...
Click to collapse
1. You must use "Qualcomm HS-USB QDLoader 9008" driver (there is another one call zidag but it's not work here)
2. As soos as you enter EDL mode, you must press "Flash" as quick as possible

i'm in a similar situation... i did "fastboot oem lock" and now i'm in a loop trying to boot the phone, after the 3time it enters edl (i see the red light).
My model is de G model (2017G) can i use miFlash just to restore the recovery and fastboot?
i had installed lineageOS, when connecting my phone it says that is the U model (2017U) but i think is only a label tag from the rom...
Thansks for the help!!

A 64 bit computer is not really necessary, however it is adviced.
I used a 32bit laptop running Win 10 to rescue mine.
Drivers seem to be a major problem, having the correct up to date drivers is a must.
Also try using Edl Tool and the Axon7 tool kit to access flashing.
Zadig drivers can help in some instances.
With the error you are receiving, have you tried another Edl package?
I was using an Edl package that would not finish flashing either, try a different package and make sure its correct for your phone.
I hope you get it sorted

The hello read package does occur when the phone is not really EDL mode anymore. You always have to restart the phone and boot manually into EDL mode with + - Power and you have to reboot everytime you did or if the hello error happens.
Look under device manager if it says Qualcomm instead of ZTE Device Handset. If that is the case you can build your own EDL cable.
"First I opened the cable and cut the Black and green open, then I connected all the black and green one together and pressed the power button until the red led was gone and 2 additional seconds.
After that I disconnected the modded cable and connected the Phone to the PC with the orginal cable and it showed up as Qualcomm HS-USB QDLoader 9008. "
You can install the qualcomm drivers under the MiFlash tab in the latest version.

i finally solve my issue following the guide: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898 there is also a resume on https://forum.xda-developers.com/axon-7/how-to/guide-dfu-unbrick-guide-disassembly-t3731152

[HELP THREAD] Hard Bricked OPPO a37f wont show any signs of life

Hey, I locked myself out of my old phone and wanted to flash the original rom onto the device but hard bricked it in the Process. Now it wont show any signs of life at all. It gets detected as "Qualcomm HS-USB QDLoader 9008 (COM5)" in QFIL but when I try to download the files via .xml I only get the message
Code:
RAWPROGRAM file path: C:\A37fEX_11_A.07_160614\rawprogram2.xml
PATCH file path:C:\A37fEX_11_A.07_160614\patch0.xml
Start Download
Program Path:C:\A37fEX_11_A.07_160614\prog_emmc_firehose_8936.mbn
COM Port number:5
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:Unable to download Flash Programmer using Sahara Protocol
Download Fail:Sahara FailSahara Fail
Finish Download
I would really appreciate some help as I tried for hours to solve this problem but can't find a solution that seems to work for me.

It's probably a driver issue. Try using another computer or reinstalling the drivers.

LenBanana said:
Hey, I locked myself out of my old phone and wanted to flash the original rom onto the device but hard bricked it in the Process. Now it wont show any signs of life at all. It gets detected as "Qualcomm HS-USB QDLoader 9008 (COM5)" in QFIL but when I try to download the files via .xml I only get the message
I would really appreciate some help as I tried for hours to solve this problem but can't find a solution that seems to work for me.
Click to expand...
Click to collapse
1. Driver problrm
2. Long press button - & + together or - only or - & power
3. Open ur phone cover disconnected battery pin & connect again

Axon 7 die after update.

Hi everyone.
I tried to update my axon to oreo but I saw an error and process was aborted.
Now I can't turn on my phone. Vibration, red lamp blink and that's all.
Is there any chance to save my phone ?
Please help.

@rym199: Judging by your topic's title, I thought you had a hardware failure. If you can get into EDL mode, then you can reflash a stock ROM of your choice. If MiFlash/Axon 7 EDL Tool can't detect the phone, then you are probably in DFU mode, in which case you will need to use the DFU MultiDL Tool to switch from DFU to EDL. Then you can flash it and start clean.

rym199 said:
Hi everyone.
I tried to update my axon to oreo but I saw an error and process was aborted.
Now I can't turn on my phone. Vibration, red lamp blink and that's all.
Is there any chance to save my phone ?
Please help.
Click to expand...
Click to collapse
Doubt you'll be able to do much with the above info
With the phone off, hold Vol UP and Vol DOWN, then insert the USB cable (it has to be connected to the PC on the other end already). After that, go to Device Manager on your PC and check under the Ports (COM & LPT) tab. If it says Qualcomm HS-USB QDLoader 9008, just use EDL Tool (by djkuz, check on the ROMs, kernels, development section) with a file that corresponds to the model of your phone (by the way, which is the phone model as stated in the back?).
If it says DFU then you'll have to follow raystef's guide on how to use the new DFU tool, then use EDL tool

Choose an username... said:
Doubt you'll be able to do much with the above info
With the phone off, hold Vol UP and Vol DOWN, then insert the USB cable (it has to be connected to the PC on the other end already). After that, go to Device Manager on your PC and check under the Ports (COM & LPT) tab. If it says Qualcomm HS-USB QDLoader 9008, just use EDL Tool (by djkuz, check on the ROMs, kernels, development section) with a file that corresponds to the model of your phone (by the way, which is the phone model as stated in the back?).
If it says DFU then you'll have to follow raystef's guide on how to use the new DFU tool, then use EDL tool
Click to expand...
Click to collapse
When I connect to PC there is a Qualcomm like you wrote. I try tomorrow, Thank you so much

@Choose an username...: I was intentionally vague because I wanted the OP to do his own research. Give them just enough info to get started, then it's up to them to do the rest. Searching Google isn't hard. And I was a bit pressed for time.

Choose an username... said:
Doubt you'll be able to do much with the above info
With the phone off, hold Vol UP and Vol DOWN, then insert the USB cable (it has to be connected to the PC on the other end already). After that, go to Device Manager on your PC and check under the Ports (COM & LPT) tab. If it says Qualcomm HS-USB QDLoader 9008, just use EDL Tool (by djkuz, check on the ROMs, kernels, development section) with a file that corresponds to the model of your phone (by the way, which is the phone model as stated in the back?).
If it says DFU then you'll have to follow raystef's guide on how to use the new DFU tool, then use EDL tool
Click to expand...
Click to collapse
It works ! EDL mode with 8.0 custom Oreo = my phone alive Thank you guy's !

DEAD Black Shark 2 Pro [Global] (Need Help!)

Hi, I own a BS2 Pro Global and it suddenly froze and shutdown, it happened several times and now it's completely dead. It won't charge and boot up. When I connect it to a PC my PC detects it but no signs of power from the device.
In my 'device manager' it says "Qualcomm HS-USB QDLoader 9008 (COM#)"
it's also detected by Mi Flash tool but I don't have anything to boot from.
*If you guys know where I can download a fastboot file or if you have can you please share it with me T_T

did
jlrivera1125 said:
Hi, I own a BS2 Pro Global and it suddenly froze and shutdown, it happened several times and now it's completely dead. It won't charge and boot up. When I connect it to a PC my PC detects it but no signs of power from the device.
In my 'device manager' it says "Qualcomm HS-USB QDLoader 9008 (COM#)"
it's also detected by Mi Flash tool but I don't have anything to boot from.
*If you guys know where I can download a fastboot file or if you have can you please share it with me T_T
Click to expand...
Click to collapse
did you solve your problem?