Develop Bugs

D851 Hard Brick

I cannot boot into download mode and cannot boot into twrp. The phone will not boot no matter how long i hold the power button and there is no lights. When connected to the pc it shows up as Qcom Dload. Can someone please create a debrick.img. All you need to do is flash this in twrp and send me the debrick file which should end up on your sdcard.
h ttps://www.androidfilehost.com/?fid=23578570567721355

Nit3H8wk said:
I cannot boot into download mode and cannot boot into twrp. The phone will not boot no matter how long i hold the power button and there is no lights. When connected to the pc it shows up as Qcom Dload. Can someone please create a debrick.img. All you need to do is flash this in twrp and send me the debrick file which should end up on your sdcard.
h ttps://www.androidfilehost.com/?fid=23578570567721355
Click to expand...
Click to collapse
This has been tried before and it didnt work for the guy. Have you tried flashing a tot? It has the begining of the emmc so same outcome but you can skip all the sd card work. Good luck if the tot fails and no one steps up ill get you that debrick file just to see if your luck is better.

ThePagel said:
This has been tried before and it didnt work for the guy. Have you tried flashing a tot? It has the begining of the emmc so same outcome but you can skip all the sd card work. Good luck if the tot fails and no one steps up ill get you that debrick file just to see if your luck is better.
Click to expand...
Click to collapse
That was a no go i tried the older dll that bypass model checks but still fails. Guess there is a linux method that worked on the older g2 and someone with a g3 reported success so i already extracted the TOT files i need to dd over from linux.
h ttp://forum.xda-developers.com/showthread.php?t=2582142

Nit3H8wk said:
That was a no go i tried the older dll that bypass model checks but still fails. Guess there is a linux method that worked on the older g2 and someone with a g3 reported success so i already extracted the TOT files i need to dd over from linux.
h ttp://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
Yeah that's probably your best option I have a partitions dump from the tot if yours are not working for some reason. Instead of installing twrp If I was you I would boot into download mode after and flash the tot. I did do a debrick dump with the script that I can get to you tomorrow some time and if that doesn't work tell me and I can give you a link that has 250-500mb range for the dumps from when I was helping the other guy. They weren't made with a script but with terminal emulator but they should be the same thing just bigger because the smaller dumps weren't working for him. Any way here are the partitions just in case https://www.androidfilehost.com/?fid=23622183712472493
---------- Post added at 11:59 PM ---------- Previous post was at 11:36 PM ----------
Oh and before I go to bed another thing you can try if you can send the images over but they don't seem to work. Hunt down the fastboot laf.img send that over then do the rest of the partitions via fastboot instead. Good luck!

Dead phone
Dead in the water. Only qpst seems to see it besides device manager (Qualcomm HS-USB QDLoader 9008). The linux method was for people who get the lg logo. I don't get anything but a black screen. Problem is i don't know enough about the qpst software to guide you on making the files. All i can say is try to make a backup using qpst and provide links. Don't know what else to do.

Nit3H8wk said:
Dead in the water. Only qpst seems to see it besides device manager (Qualcomm HS-USB QDLoader 9008). The linux method was for people who get the lg logo. I don't get anything but a black screen. Problem is i don't know enough about the qpst software to guide you on making the files. All i can say is try to make a backup using qpst and provide links. Don't know what else to do.
Click to expand...
Click to collapse
In order to get you the files someone needs to reboot from the hidden menu into somthing I cant remember. Its not mini os and the d851 lacks the option in hidden menu atleast I didnt see it. The d855 hidden menu has the option and I was going to try it but he ended up sending it in before I got around to flashing the d855 rom. If you want to fix it yourself and can do without a cell phone for a few days I can try but might not be able to get you the files until sunday if it works.

ThePagel said:
In order to get you the files someone needs to reboot from the hidden menu into somthing I cant remember. Its not mini os and the d851 lacks the option in hidden menu atleast I didnt see it. The d855 hidden menu has the option and I was going to try it but he ended up sending it in before I got around to flashing the d855 rom. If you want to fix it yourself and can do without a cell phone for a few days I can try but might not be able to get you the files until sunday if it works.
Click to expand...
Click to collapse
Yeah i will have to wait then can't afford the $175 deductible right now. Thanks for the help. I don't mind waiting just hope i can find a less costly solution know what i mean?

QPST
So it looks like i will need a hex file and mbn partition files vs the bin files that come from the tot file. From what i read in the forums lg offers a 1 year warrenty. So i guess as a last resort i could send it in for service but i would rather try to resolve it myself.

Nit3H8wk said:
So it looks like i will need a hex file and mbn partition files vs the bin files that come from the tot file. From what i read in the forums lg offers a 1 year warrenty. So i guess as a last resort i could send it in for service but i would rather try to resolve it myself.
Click to expand...
Click to collapse
Yeah I got ready to do it last night but got side tracked hopefully tonight

qpst
ThePagel said:
Yeah I got ready to do it last night but got side tracked hopefully tonight
Click to expand...
Click to collapse
I get paid on monday so going to ship it out to LG then. But if you are able to get the hex and mbn and secure boot files let me know i would still like to tinker a bit before that time as i know it will take a few weeks to get the phone back otherwise.

Nit3H8wk said:
I get paid on monday so going to ship it out to LG then. But if you are able to get the hex and mbn and secure boot files let me know i would still like to tinker a bit before that time as i know it will take a few weeks to get the phone back otherwise.
Click to expand...
Click to collapse
Ill be able to tell you tomorrow afternoon if I can do it.

Nit3H8wk said:
I get paid on monday so going to ship it out to LG then. But if you are able to get the hex and mbn and secure boot files let me know i would still like to tinker a bit before that time as i know it will take a few weeks to get the phone back otherwise.
Click to expand...
Click to collapse
I cant seem to get into diag mode or field test mode so I cannot create the files for you :crying: BUT before you completely give up on fixing it take a look at this http://forum.cyanogenmod.org/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery/

Qualcomm MSM8975AC
Hello
I tell them my story, mistakenly doing a ported rom stock LG G3 Marshmallow, I flashed my phone with the stock rom from Marshmallow (model D855) and after that I have bricked the phone. No download mode, no emergency mode, only is recognize for the computer as AndroiNet usb port serial.
Could please you help me to unbrick my lg g3 Phone model d851,t-mobile variant. When I plug in my Phone to computer, this is recognized as lgandroinet port serial but I have made a testpoint (open the mobile) to change the phone mode to Qualcomm HS-USB QDLoader 9008”. I have used tools like boardiag but I get the followin message: “No response from the device. Check PMIC first and if still boot problem, replace AP.” To look at this thread: http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/ ... but report that it is not compatible for ATT and Tmobile variations. I currently have two virtual machines: Window xp 32 bit and Ubuntu 15.04. My client OS is 8.1 Window 64 bit.
I will be very grateful if you can help me to find a solution or can show me which is the correct way. I've been several weeks looking for a solution but I have not been able to fix my cellphone. I hope that my computer still recognizes it.

cesarandres_8911 said:
Qualcomm MSM8975AC
Hello
I tell them my story, mistakenly doing a ported rom stock LG G3 Marshmallow, I flashed my phone with the stock rom from Marshmallow (model D855) and after that I have bricked the phone. No download mode, no emergency mode, only is recognize for the computer as AndroiNet usb port serial.
Could please you help me to unbrick my lg g3 Phone model d851,t-mobile variant. When I plug in my Phone to computer, this is recognized as lgandroinet port serial but I have made a testpoint (open the mobile) to change the phone mode to Qualcomm HS-USB QDLoader 9008”. I have used tools like boardiag but I get the followin message: “No response from the device. Check PMIC first and if still boot problem, replace AP.” To look at this thread: http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/ ... but report that it is not compatible for ATT and Tmobile variations. I currently have two virtual machines: Window xp 32 bit and Ubuntu 15.04. My client OS is 8.1 Window 64 bit.
I will be very grateful if you can help me to find a solution or can show me which is the correct way. I've been several weeks looking for a solution but I have not been able to fix my cellphone. I hope that my computer still recognizes it.
Click to expand...
Click to collapse
I just did the same thing tonight, I'll let you know if I fix it.

mxpxboi said:
I just did the same thing tonight, I'll let you know if I fix it.
Click to expand...
Click to collapse
Hello,
What is your phone and variant model? Do you have D851 model?

Yeah D851, Black Screen and only connects as "LGE androidnet usb serial port"
Tried flashing TOT file and I get the error "Model Information Check FAIL!"

mxpxboi said:
Yeah D851, Black Screen and only connects as "LGE androidnet usb serial port"
Tried flashing TOT file and I get the error "Model Information Check FAIL!"
Click to expand...
Click to collapse
Hello,
I will try help you, first of all you must to change the Qualqomm mode in your phone, namely change usb LGE Androinet by QDloader 9008. For this you must remove the battery from the phone, open the phone and use copper cable or tweezers and you must to touch two points on the mainboard in order to force Qualcomm mode on your phone. I have attached photos to guide you in this process. You must touch two points (without battery) and connect the usb cable to the computer. You'll hear a sound that indicates that qualcomm is active otherwise could see a battery warning on the screen. If this happens, you must disconnect the usb cable and repeat the process.
The second thing you're going to do is install the drivers appropriate for Qualcomm mode. Please follow this thread: http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
This is the download link for the drivers referred to the post: http://forum.xda-developers.com/attachment.php?attachmentid=3261089&stc=1&d=1428980071
Now your computer will recognize the cellular in the indicated mode (Relink HS-USB QDloader 9008).
The next step is to use the Boarddiag tool in this post but in the root folder, place the file sbl1.mbn which is located in the folder that you extract the file TOT.
I am currently uploading a package that includes bordiag tool, sbl1.mbn file, and TOT file extracted. When the upload is complete, I could tell you what is the download link, this contain the version of Boardiag that will work in our model. Currently my phone lg g3 D851 (chip MSM8975AC) was revived.

cesarandres_8911 said:
Hello,
I will try help you, first of all you must to change the Qualqomm mode in your phone, namely change usb LGE Androinet by QDloader 9008. For this you must remove the battery from the phone, open the phone and use copper cable or tweezers and you must to touch two points on the mainboard in order to force Qualcomm mode on your phone. I have attached photos to guide you in this process. You must touch two points (without battery) and connect the usb cable to the computer. You'll hear a sound that indicates that qualcomm is active otherwise could see a battery warning on the screen. If this happens, you must disconnect the usb cable and repeat the process.
The second thing you're going to do is install the drivers appropriate for Qualcomm mode. Please follow this thread: http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
This is the download link for the drivers referred to the post: http://forum.xda-developers.com/attachment.php?attachmentid=3261089&stc=1&d=1428980071
Now your computer will recognize the cellular in the indicated mode (Relink HS-USB QDloader 9008).
The next step is to use the Boarddiag tool in this post but in the root folder, place the file sbl1.mbn which is located in the folder that you extract the file TOT.
I am currently uploading a package that includes bordiag tool, sbl1.mbn file, and TOT file extracted. When the upload is complete, I could tell you what is the download link, this contain the version of Boardiag that will work in our model. Currently my phone lg g3 D851 (chip MSM8975AC) was revived.
Click to expand...
Click to collapse
Good morning, please try downloading this package;
https://mega.nz/#!5lRGUZqZ!HZXaf4SP_PtuPEkg0ycdWXZP977_lBdVVqkI1P8DVtU
I'm not sure if it will work for your model, please performs the tests at your risk. Let me clarify that this is the same boarddiag version , only I try added the files needed.
Within the. 7z, there is a file called "TOT Extract", please extract it and open application BoardDiag. In the section "Target Dir" choose the path where you extracted the file.
Please inform me as it was with the tests.

cesarandres_8911 said:
Good morning, please try downloading this package;
https://mega.nz/#!5lRGUZqZ!HZXaf4SP_PtuPEkg0ycdWXZP977_lBdVVqkI1P8DVtU
I'm not sure if it will work for your model, please performs the tests at your risk. Let me clarify that this is the same boarddiag version , only I try added the files needed.
Within the. 7z, there is a file called "TOT Extract", please extract it and open application BoardDiag. In the section "Target Dir" choose the path where you extracted the file.
Please inform me as it was with the tests.
Click to expand...
Click to collapse
Thank you SOOO much for your help so far.
I installed Qualcomm Drivers and touched the points and it connected.
But it says that the Drivers are blocked due to not being digitally signed.
And it's showing up in Device Manager as "Qualcomm HS-USB QDLoader 9008" with an exclamation point.
I am posting screen shots.'
You didn't have this issue?
What steps do I do in the BoardDiag exactly? Just add the directory with the file and hit start?

@mxpxboi it seems you're using windows 8/above, you have to disable driver signature, here is how to do it https://learn.sparkfun.com/tutorial...abling-signed-driver-enforcement-on-windows-8
Sent from my LG-D801 using Tapatalk

How to set device tampered back to false?

I will explain how to set the device tampered back to "false" on the Wileyfox Swift.
Required:
7z
WFS.7z (https://drive.google.com/file/d/0B6Ge199bCD5_NF9RWGhVLVhxajA/view?usp=sharing)
Windows 7 or 8
Driver Signature Enforcement disabled
Step 1: Brick the device on purpose
Hold Volume Up button+Volume Down button while plugging in USB
You should be see QHS_USB BULK in Device Manager
S
Step 2: Install Driver
Reboot with Driver Signature Enforcement disabled ( Google if you must)
Plug device in and make sure you see QHSUSB BULK in Device Manager
If you see Relink HS QDLoader 9008 uninstall it and delete driver software
Then refresh and you should see QHS USB BULK
Manually Update Driver software and navigate to driver folder extracted in WFS.7z
Step 3 : Install QPST provided in WFS.7z
I think its pretty straight forward
Step 4: Flash Firmware
Open QFil
Select Port and choose your device if not already chosen
Select Flat Build
Programmer Path must be prog_emmc_firehose_8916.mbn in the Maincode folder from WFS.7z
Build Path should automatically appear
Hit load XML.
Click rawprogram_upgrade.xml
Click patch0.xml
Click Download
Once done remove and reinsert battery
Step 5: Verify Tampered:False
boot into fastboot
type the following:
fastboot oem device-info
and it should say Device tampered : false and Device Unlock : False
NB: If you get a SaharaDownload fail or something just remove battery and USB for 5 seconds. Plug battery in. Then plug USB in.
NB: I do not accept any responsibility for damaged devices or anything. You point your finger at me and I will laugh at you
If it works don't hesitate to donate me a cup of coffee
PayPal : [email protected]

yasteellutch said:
Step 2: Install Driver
Reboot with Driver Signature Enforcement disabled ( Google if you must)
Plug device in and make sure you see QHSUSB BULK in Device Manager
If you see Relink HS QDLoader 9008 uninstall it and delete driver software
Then refresh and you should see QHS USB BULK
Manually Update Driver software and navigate to driver folder extracted in WFS.7z
Click to expand...
Click to collapse
This does not work for me, no matter wht I try, in the device manager I just get "Android" with a yello triangle.
No manual driver install / update (or update via windows update) solve that problem.
Try it on two Windows 7 PCs (x32 & x64) with Firewall, Antivirus and driver signature are disabled.
On a Windows 10 PC, the device connects as "Marshall London Device".

I don't think ur swift is bricked

when puting battery in jut get the screen "wileyfox"; recovery does not start (vol- and pwr) but fastboot mode ist working (vol+ and pwr). so it's not bricked?
so I repeat step 1 but still in windows 7 device manager having "Other Devices -> Android" with no yellow triangle.

I get SaharaDownload fail. Removing battary is useless. What else can i try? Thanks in advance

Now you get Sahara Fail. I think this is some sort of 'Lock Mode'. I fixed it by removing battery. Reinserting battery and immediately plugging in USB and hitting download

yasteellutch said:
Now you get Sahara Fail. I think this is some sort of 'Lock Mode'. I fixed it by removing battery. Reinserting battery and immediately plugging in USB and hitting download
Click to expand...
Click to collapse
I try and try do it again but i have only got sahara fail again and again.....

void2000 said:
I try and try do it again but i have only got sahara fail again and again.....
Click to expand...
Click to collapse
Upload a screenshot

yasteellutch said:
Upload a screenshot
Click to expand...
Click to collapse
Probably I have to use a special cable?

See it gets the SharaVersion right so I'm guessing that phone is in a correct state. The problem there could be that it didn't decompress properly. Maybe the integrity of your decompressed WFS.7z is not intact. Go to Android One(2nd Gen) dedicated page. I got help there. I guess all you need is to look there.

Maybe u didn't installQPSt right or the driver is a issue. I flashed stock like 3 days ago and it works perfectly

cyaneo said:
This does not work for me, no matter wht I try, in the device manager I just get "Android" with a yello triangle.
No manual driver install / update (or update via windows update) solve that problem.
Try it on two Windows 7 PCs (x32 & x64) with Firewall, Antivirus and driver signature are disabled.
On a Windows 10 PC, the device connects as "Marshall London Device".
Click to expand...
Click to collapse
Hey @cyaneo. If you still have the Yellow Android triangle this is because your drivers aren't installed correctly. I tried it. But that also means your fastboot is working.

Hi all,
Ive been a way from Android for a long time so I'm no expert but the method posted above failed for me. Like others, all my PC would recognise the phone as was "Marshall London Device" and essentially my phone was useless.
Can I ask why we need to erase and/or brick the phone?
Instead what worked for me was to reboot into fastboot mode, download Cyanogen OS signed zip, extract and run flash-radio.sh, then flash recovery and system manually. Reboot phone into working OS and then turn off OEM Unlock.
Once that's done I rebooted into fastboot and confirmed bootloader was locked and that tampered was false (as an official signed OS is installed I take it?).
Anyway as I say, I'm no expert but surely that's an easier and cleaner way than erasing/bricking a phone and only needs fastboot and the latest official signed rom from Cyanogen OS directly?

void2000 said:
Probably I have to use a special cable?
Click to expand...
Click to collapse
Hi,
This is my first post. (active lurker previously) hopefully its not too late.
In my experience on other device running 8916, a sahara failure can be overcame by holding the power button when entering download mode. (E.g: if you enter download mode by pressing and holding vol+/- simultaneously and plugging in usb cable, try holding the power button as well when you plug in the cable). This is normally a result of battery too low.

After bricking my Swift with some gymnastics around Android One firmware images, this tool worked flawlessly!
I was a bit confused when it came to the part of deleting/ manually reinstalling the driver. After the device was shown as "QHS_USB BULK", I manually installed the " Relink HS QDLoader 9008". Everything else went really smoothly. The device is good as new
For the adventurous ones with a Swift- this is one tough little phone. Hard-brick ain't a reason to stop

Pak0St said:
After bricking my Swift with some gymnastics around Android One firmware images, this tool worked flawlessly!
I was a bit confused when it came to the part of deleting/ manually reinstalling the driver. After the device was shown as "QHS_USB BULK", I manually installed the " Relink HS QDLoader 9008". Everything else went really smoothly. The device is good as new
For the adventurous ones with a Swift- this is one tough little phone. Hard-brick ain't a reason to stop
Click to expand...
Click to collapse
Lol I agree. This baby took some hits. I clocked it to 1.6 at stable. At 1.9 she became instable and started crashing #YeahITakeRisks

xfile087 said:
Hi all,
Ive been a way from Android for a long time so I'm no expert but the method posted above failed for me. Like others, all my PC would recognise the phone as was "Marshall London Device" and essentially my phone was useless.
Can I ask why we need to erase and/or brick the phone?
Instead what worked for me was to reboot into fastboot mode, download Cyanogen OS signed zip, extract and run flash-radio.sh, then flash recovery and system manually. Reboot phone into working OS and then turn off OEM Unlock.
Once that's done I rebooted into fastboot and confirmed bootloader was locked and that tampered was false (as an official signed OS is installed I take it?).
Anyway as I say, I'm no expert but surely that's an easier and cleaner way than erasing/bricking a phone and only needs fastboot and the latest official signed rom from Cyanogen OS directly?
Click to expand...
Click to collapse
Of course there is. Don't get me wrong I understand your point. But you need to remember there are log files and a bunch of other stuff lying around if you fastboot. When you use QFil it basically rewrites all the partitions thus no logs. I returned my first Swift with the IMEI issue and they gave me a new one in a week

Hi,
my Swift is also Bricked.... that means no bootloader boot or etc. i tried to flash the phone with this method but no success. my error with QFIL is this
COM Port number:20
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
bei QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
bei QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Click to expand...
Click to collapse
Thanks for response

Error
Download failded
Code:
Dowload fail:House fail failed to Upload the emmc images to phone using firehouse

vadimnew said:
Download failded
Code:
Dowload fail:House fail failed to Upload the emmc images to phone using firehouse
Click to expand...
Click to collapse
You made a mistake @vadimnew

[HELP] G3 Hardbrick Help! URGENT!

Here's my case:
I've got a LG G3 F400L (Korean LGU Variant), its on Marshmallow(6.0), and for all I know I used the Autorec program for Lollipop, and apparently got my bootloader corrupted; No led flashing, no display. But the Qualcomm 9008 serial port is shown on the device manager and I can use Boardiag to detect it. I know, irony and idiocy made this dilemma.
Diagnostics:
I've used Boardiag 2.99a by willcracker and yes I've checked "AP check" and "EMMC TEST" and both are tagged as "Pass", but when it comes to the "SDRAM TEST" it throws off an error indicating that there is a flash error on partition "boot" along with a 0x3000 and I can't progress beyond that, I've also tried to use the "Restore Device" option to revive it but still the later error still persists.
I've also tried Smart Boot Diagnostics but the problem is that my device's AP Chip doesn't exist on the current version of the tool.
What I would like to press on:
I would want to resolve this on my own and that no amount of suggesting on sending this to the service center would yield fruit. Please do understand, I would also like this to be a thread that can help me and other on resolving their corrupted bootloader units.
Please, can someone help me on my dilemma. Thank you very much. Any amount of help is appreciated.

Try using board diag with the battery unplugged.
Sent from my SM-G935T using Tapatalk

Already tried that but still nothing works.
Current situation:
Alas, I've accessed fastboot and had wiped the boot partition, but now the USB is detected as "LGE AndroidNet USB Serial Port."

FeitX said:
Already tried that but still nothing works.
Current situation:
Alas, I've accessed fastboot and had wiped the boot partition, but now the USB is detected as "LGE AndroidNet USB Serial Port."
Click to expand...
Click to collapse
You need to short with a cable internet connection I do this last night and changes for Qalcomm USB in the same time...After that, you need to open BoarDiag and do the process. If you can´t enter in download mode, you need in BoarDiag pass the USERDATA
I follow this link: http://open-freax.fr/guide-unbrick-your-lg-g3/

[HARDBRICK] D855; Boarddiag & flashtool not working

I'm fixing a D855 model which I hardbricked by accident. This is what I tried so far but still unsuccessful:
1. I used the method which involved shorting the pins in order for my PC to detect it as Qualcomm USB QDloader (something). I used the BOARDDIAG v2.99c as it's the only version that could detect my phone connected. Newer versions doesn't seem to work. I flashed all the partitions, even the userdata and system (which the tutorial doesn't recommend as it takes very long; it took me more than 12 hrs+). After flashing the sli, which is supposed to be flashed last, my phone boots to kernel panic mode. From this point, my phone can be seen as LGE androidnet port (COM41) (sorry I'm just typing this from memory)
2. From the kernel panic mode, I used the LG flash tool to flash a D855 TOT and a LG8974.dll. However, it still cannot detect my phone model. IMEI and PID still comes out as null. Back to #1, the reason I also flashed userdata and system partition because flash tool still cannot detect my phone. I was hoping to boot it up using the 1st method but it keeps on throwing it to kernel panic mode.
Any suggestions how to revive my LG G3?

hey, i have the same issue, did you find any sulotion?

Question [SOLVED] Bricked OP9Pro, can't get to fastboot, sahara communication failed

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.