![]() The Qualcomm driver exposes the device using a serial port. Why did I choose to use WinUSB instead of the Qualcomm driver? There are a couple of reasons: I get errors you had several posts with several questions so I'll answer them here. If I use the zadig tool to change the driver to WinUSB, then those tools can't communicate with the device. I've tried all 3 firehose files on your site, but the tools just hang after writing the programmer to the phone (at least I'm assuming they are able to do that) when having them do simple commands, like listing out the partitions, etc. Those other tools require configuring them to tell them which port it is using. In Device Manager, it shows the device under the Ports section and shows that it is on COM12 or COM13, etc. For all of those, it *seems* like I have to leave the default Qualcomm EDL driver in place. While I was waiting for the firmware to download, I grabbed some other tools online. ![]() I figured I'd test your tool to make sure I can connect to my phone properly *before* some future incident where I will need to use it. It must use WinUSB." Can you explain more about why this is? The official EDL driver is not compatible with this programming tool. On your web page for the tool, you wrote, "Please note that Qualcomm has an official EDL driver that will install by default.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |