Related
[LG G3][Hard Brick] - error "Failed during loading flash programmer" on BoardDiag
Hello everyone,
First of all, sorry if I'll make grammar mistakes. I'm french and still learning english.
I have hard bricked my LG G3 (D855, 20T, EUR, 32 Go) after flashing a .zip... I tested everything but nothing fixed that... I am exhausted... Please help me !
I followed this thread ( http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853 ) to unbrick the phone.
Step 1 : Worked fine
I've installed Qualcomm drivers, now I have "HS-USB QDLoader 9008(COMx)" in Device Manager on Windows 10 and extracted the .tot files using BoardDiag
Step 2: Error
BoardDiag says "Device was not found in dload trying flash programmer"... Found a fix (remove the battery -> unplug cable -> replace battery -> plug the cable) but NOW the @#|²! error is "Failed during flash programmer" I'm becoming crazy !!
Please help me how to fix this MOD EDIT: profanity removed
ive fixed alotta bricks and ive never gotten board diag to work...i think the verison we have access to is the correct one..its a fake...no matter which phone it'll give that message
Ok but what do you recommand me ?
Up
please
Found this old thread and would like to add some info for future searchers
I was getting the same error "Device was not found in dload trying flash programmer" no matter what usb cable I used and for how long I kept pins shorted. I was using Windows 7 64 bit
And then just out of curiosity I installed Windows 7 32 bit, updated it to the latest, installed 32bit Qualcomm 9008 driver, installed all VC runtimes - and it worked!
Hope this helps someone in future
My phone is hard bricked. No LCD, no charging LEDs. Only showing up in EDL mode as Qualcomm Hs-USB QDLoader 9008 in the device manager. It happened when I tried to install the latest MIUI 9 weekly rom 7.9.15 from xiaomi.eu. I've spent the last few hours trying everything I could find. I can get MiFlash to see the device but I get different errors depending on the version of Mi Flash. Ive opened the phon eup, tried with/without the battery, tried shorting the two pins on the mobo mentioned in this thread
https://forum.xda-developers.com/showpost.php?p=68205960&postcount=24
I've tried three different computers, windows 10, windows 7 both 64 bit. Disabled driver verification. Tried many different global ROMs but still get the following errors depending on the version of miflash:\
-cannot read from COM port
-Reached the end of the file. (0x80070026: ReadRobust failed)
-cannot receive hello packet
Bottom line is that the phone is in a weird state and doesn't seem to communicate properly with the miflash tool.
Anyone have any clue what else i can try? I hate to lose my beloved mimax!
Thanks guys
seti007 said:
My phone is hard bricked. No LCD, no charging LEDs. Only showing up in EDL mode as Qualcomm Hs-USB QDLoader 9008 in the device manager. It happened when I tried to install the latest MIUI 9 weekly rom 7.9.15 from xiaomi.eu. I've spent the last few hours trying everything I could find. I can get MiFlash to see the device but I get different errors depending on the version of Mi Flash. Ive opened the phon eup, tried with/without the battery, tried shorting the two pins on the mobo mentioned in this thread
https://forum.xda-developers.com/showpost.php?p=68205960&postcount=24
I've tried three different computers, windows 10, windows 7 both 64 bit. Disabled driver verification. Tried many different global ROMs but still get the following errors depending on the version of miflash:\
-cannot read from COM port
-Reached the end of the file. (0x80070026: ReadRobust failed)
-cannot receive hello packet
Bottom line is that the phone is in a weird state and doesn't seem to communicate properly with the miflash tool.
Anyone have any clue what else i can try? I hate to lose my beloved mimax!
Thanks guys
Click to expand...
Click to collapse
What happens by trying to go into TWRP?
Enviado desde mi MI MAX mediante Tapatalk
I flashed eu rom yesterday?
What exactly happened??
Thanks for the answer guys following are my responses.
Albertkuba said:
What happens by trying to go into TWRP?
Absolutely nothing happens with any button combination. The screen remains dark. When I unplug the battery and plug it back in ic the computer recognizing it as an edl device 9008
Enviado desde mi MI MAX mediante Tapatalk
Click to expand...
Click to collapse
hassan_eldhraawy said:
I flashed eu rom yesterday?
What exactly happened??
Click to expand...
Click to collapse
I had Nigel's lineage ROM running perfectly on my phone. I got an itch to Try out the new MIUI 9. Downloaded the latest ROM and then the latest Superuser. Installed both of them and tore up. The ROM installed fine without any error messages. While installing SuperSU the phone just died. it was plugged into power so not sure why the screen just went dark.
Chek http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Do "Guide on how to recover “Qualcomm HS-USB QDLoader 9008” MODE", Fastboot MIUI rom has all files needed for QFill:
MIUI 9 Global Beta ROM(fastboot) 7.9.15
1 - images/prog_emmc_firehose_8976_ddr.mbn
2 - images/rawprogram0.xml
3 - images/patch0.xml
in fastboot mode run flash_all.bat
Let us know how it went...
nijel8 said:
Chek http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Do "Guide on how to recover “Qualcomm HS-USB QDLoader 9008” MODE", Fastboot MIUI rom has all files needed for QFill:
MIUI 9 Global Beta ROM(fastboot) 7.9.15
1 - images/prog_emmc_firehose_8976_ddr.mbn
2 - images/rawprogram0.xml
3 - images/patch0.xml
in fastboot mode run flash_all.bat
Let us know how it went...
Click to expand...
Click to collapse
Thank you Nigel for your input. I will give this a try and get back with you.
Hi Nigel, I followed the guide exactly as indicated using windows 10. I get an error at the end when I hit download in Qfil. My phone is in the OLD “Qualcomm HS-USB QDLoader 9008” mode.
QFIL LOG:
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
EDIT: I would like to add that I have driver signing off and tried a win 10 and 7 computer with the exact same results. I'm beginning to think that my phone is pretty much a lost casue :,(
seti007 said:
Hi Nigel, I followed the guide exactly as indicated using windows 10. I get an error at the end when I hit download in Qfil. My phone is in the OLD “Qualcomm HS-USB QDLoader 9008” mode.
QFIL LOG:
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
EDIT: I would like to add that I have driver signing off and tried a win 10 and 7 computer with the exact same results. I'm beginning to think that my phone is pretty much a lost casue :,(
Click to expand...
Click to collapse
Is this screenshot real? Why are you using 8675_W00 device firmware files from the guide literally!? Use miui rom link I gave you for hydrogen...
nijel8 said:
Is this screenshot real? Why are you using 8675_W00 device firmware files from the guide literally!? Use miui rom link I gave you for hydrogen...
Click to expand...
Click to collapse
You have a keen eye Nigel. Yes I messed up the first time and used the wrong folder. Afterwards, I tried this with the proper folder with the correct firmware from the link you provided. Tried putting it in root drive and renamed the folders so there were no spaces. Even tried a newer fastboot firmware but still the same result. Looking around on google, apparently the Sahara error is very common and no real solution.
Thanks again for your help Nigel.
Hi Nigel, I'm wondering if you or anyone else who feels up to the challenge would be willing to work on this phone? I can send it to you with a self addressed envelope. I'm willing to pay for your time. I have exhausted all options but nothing has helped. would be great to have my phone back . If anyone is willing to take me up on this, please pm me. Thanks
Hello sirs, I hope you can help me.
I have a mi6 that turned into a brick. Hold the buttons to it to give restart / download mode or put it to load. He does not respond to anything.
However,
By putting it on your computer it recognizes you as Qualcomm QDLoader 9008.
I wonder if I can recover it yet. or unfortunately it turned a paper weight.
DL Xiaomi flash tool and flash fastboot rom. It will be fine.
icrunchbanger said:
DL Xiaomi flash tool and flash fastboot rom. It will be fine.
Click to expand...
Click to collapse
I tried to do this form, downloaded all the miui site drivers, adb fastboot and cualcomm driver.
How to run my flash with a last method with the xiaomi global mi6 I got the following error:
"Cannot receive hello packet Xiaomi Device"
The program tried a few more times and nothing more.
What can I be doing wrong? Do you have another option? because he is in what they call DeadBrick (I discovered this term only now, after searching the forums)
XeeXa said:
I tried to do this form, downloaded all the miui site drivers, adb fastboot and cualcomm driver.
How to run my flash with a last method with the xiaomi global mi6 I got the following error:
"Cannot receive hello packet Xiaomi Device"
The program tried a few more times and nothing more.
What can I be doing wrong? Do you have another option? because he is in what they call DeadBrick (I discovered this term only now, after searching the forums)
Click to expand...
Click to collapse
I know, i was there. Reboot your computer and start again.
I restarted and tried again.
I formatted and installed only the drivers and the error continues.
I tried with miflash 2015 until version miflash2017
I think, you device isn't in EDL mode. You open back cover of device. Make test point for QDL 9008. Then, you flash fastboot rom by Mi flash tool. It's very simply. I made it for unbrick my Mi6 several times.
See video here.
https://youtu.be/vSNRQdUuNYw
bahuy2003 said:
I think, you device isn't in EDL mode. You open back cover of device. Make test point for QDL 9008. Then, you flash fastboot rom by Mi flash tool. It's very simply. I made it for unbrick my Mi6 several times.
See video here.
Click to expand...
Click to collapse
Is this the only way to put the phone in edl mode?
Yes, it's only way for Mi6, which is locked bootloader.
Seems like I succesfully bricked my OP9Pro. Tried to restore in MSMDownloadTool v4.0. Oneplus 9 Pro LE2123.
Phone is detected correctly in Windows device manager(QDLoader 9008, I get to EDL by holding Vol+ and Vol- buttons and connecting the cable). When I try to flash, MSM breaks on Sahara communication failed(FH: 258).
Qualcomm drivers are from Windows Update Center(I connect my phone in EDL mode, click Update and in optional updates section there is the needed driver - Qualcomm Incorporated - Ports).
What should I do?
I saw a python EDL workaround script, but I'm not sure if helps me or if it even works (saw it somewhere on xda, the only thing I remember that it was in some of oneplus's devices thread and the sript name was edl.py, sorry
Tried on one laptop(Acer Nitro< none of the ports gave a succesful result). Gonna try on my second(Asus ROG GL702VMK, it seems to have better ports connection). Gonna write an update message.
I can't get to fastboot, recovery, etc. Phone seems to give no signs of life, there is even no charging notification when the cable is connected(but maybe phone isn't turned off actually, not sure)
You need to click the box to "use lite firehose" beforehand running your msm. And change target to OS or EU depending on which one ur using
Shooter7889 said:
You need to click the box to "use lite firehose" beforehand running your msm. And change target to OS or EU depending on which one ur using
Click to expand...
Click to collapse
Thanks for advice, I got further but now it stopped on Param Preload with "Device not match image"
I use MSMDownloadtool for EU and my phone is EU version(LE2123)
So, I am kinda happy cuz I booted to system.
I used this guide(https://forum.xda-developers.com/t/global-us-unbricking-guide.4370463/). Used MSM Download tool with Indian f/w.
Then I tried to return to EU version, but I got the same param preload error. I used this version of MSM and it flashed successfully.
So now I guess the issue is solved. Thanks @Shooter7889 for ur advice with lite firehose
Uncheck "check sha256" for mismatch device issue. Or find correct msm. You're welcome. I had same issue after bricking my 9pro and not being able to run msm successfully.
Hi all
well in a nutshell a friend's good old pixel 2 xl finally had the issue of black screen and only qbulk being detected by the PC.
After a bit of googling i found a Qualcomm loader and some firehose files from github.
However it fails on with error sahara protocol cannot establish connection.
I read that maybe i needed to short pins on the board to go into edl test mode, but dont know which ones i have attached a picture
Any suggestions would help
Can't help you with the pins. I can however tell you that based upon my experiences with my Lenovo tablet, using Xiaomi's MiFlash software proved a lot more reliable than Qualcomm's tools when trying to restore the firmware through the low level interface.
Strephon Alkhalikoi said:
Can't help you with the pins. I can however tell you that based upon my experiences with my Lenovo tablet, using Xiaomi's MiFlash software proved a lot more reliable than Qualcomm's tools when trying to restore the firmware through the low level interface.
Click to expand...
Click to collapse
i will give it a try thank you, is it the same way for xiaomi to short pins in order to get to edl test mode ?
I don't know.
Well, there has to be a reason that the phone ended up in this state.
My guess is a hardware fault, and if that's the case, you'll need to replace the motherboard.
Some phones can end up this way if you do something stupid while flashing a rom, but I've never heard about that on a Pixel.
code777 said:
Hi all
well in a nutshell a friend's good old pixel 2 xl finally had the issue of black screen and only qbulk being detected by the PC.
After a bit of googling i found a Qualcomm loader and some firehose files from github.
However it fails on with error sahara protocol cannot establish connection.
I read that maybe i needed to short pins on the board to go into edl test mode, but dont know which ones i have attached a picture
Any suggestions would help
Click to expand...
Click to collapse
If your device is not properly detected, because it is not properly in EDL mode, then, there's not a tool that can detect it or work with.
When the kernel refuses to start because of a failed upgrade or something, then the device enters automatically to Qualcomm/EDL mode, but the first you'll see, it is detected in device manager as QBulk or Qualcomm HS-UB-Diagnostics 900E, then you have to update the drivers to Qualcomm HS-USB QDloader 9008 to get it.
This is an example of my other device, by fortune my P2XL is working fine besides the bootloader can't be unlocked.
SubwayChamp said:
If your device is not properly detected, because it is not properly in EDL mode, then, there's not a tool that can detect it or work with.
When the kernel refuses to start because of a failed upgrade or something, then the device enters automatically to Qualcomm/EDL mode, but the first you'll see, it is detected in device manager as QBulk or Qualcomm HS-UB-Diagnostics 900E, then you have to update the drivers to Qualcomm HS-USB QDloader 9008 to get it.
This is an example of my other device, by fortune my P2XL is working fine besides the bootloader can't be unlocked.
Click to expand...
Click to collapse
Hello, i think i installed it correctly tried on two different computers with one "unsigned" driver with the windows drive signature turned off and then with a driver from Microsoft's own website which is signed i still gate the same issue.
Tired with couple of version of QPST with the latest i found being QPST_2.7.496, tried with a couple of firehose files there is a github repo with most of them 8916 often pops up in google 2xl topics and one zip which was named 2XL had in it prog_ufs_firehose_8998_ddr.elf not sure if its the correct one :
ERROR: function: rx_data:246 Error occurred while reading from COM port
ERROR: function: sahara_main:982 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
So i am stuck to this point now , ANY suggestions will be appreciated
code777 said:
Hello, i think i installed it correctly tried on two different computers with one "unsigned" driver with the windows drive signature turned off and then with a driver from Microsoft's own website which is signed i still gate the same issue.
Tired with couple of version of QPST with the latest i found being QPST_2.7.496, tried with a couple of firehose files there is a github repo with most of them 8916 often pops up in google 2xl topics and one zip which was named 2XL had in it prog_ufs_firehose_8998_ddr.elf not sure if its the correct one :
ERROR: function: rx_data:246 Error occurred while reading from COM port
ERROR: function: sahara_main:982 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
So i am stuck to this point now , ANY suggestions will be appreciated
Click to expand...
Click to collapse
To start with, the correct installation of these drivers is mandatory, otherwise, you can't advance further, if you have a message of success, then it's done, if not, you may redo the steps.
Microsoft doesn't own any of the needed drivers here. All relies on Qualcomm, it contains the lot of variants, from all of them, one is all you need.
If the issue is with QPST, I saw a QPST thread in XDA, just search for it.