search

bkerler / edl

Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
GNU General Public License v3.0
1.66k stars 385 forks source link

COMMAND LINE QUITS AFTER DEVICE DETECTED #595

Open atharva288 opened 1 month ago

atharva288 commented 1 month ago

Screenshot (297)

arkdamenen commented 1 month ago

I had exact same issue. Without disconnecting the cable I needed to restart the device. If it would hang for whatever reason, the restart was only my salvation

In my case I used adb for that purpose (to leave the EDL mode I simply held the power button): adb reboot edl

trekronor commented 1 month ago

Same issue.

I can't use your solution. No adb/fastboot.

Windows 10 doesn't work for me. Linux on the same machine does indeed work.

I tried on two machines and Zadig with libusb-win32, WinUSB and usbdk. Same. Would really like it to work on Windows.

Any more ideas?

arkdamenen commented 1 month ago

By meaning that on Linux it works, but not on Windows, do you mean on Linux you go further than "Device detected" or what do you mean specifically?

Also, do you have an EDL cable or access to the EDL test points?

trekronor commented 1 month ago

By meaning that on Linux it works, but not on Windows, do you mean on Linux you go further than "Device detected" or what do you mean specifically?

Also, do you have an EDL cable or access to the EDL test points?

Thanks for the reply. Yes with the Linux LiveDVD I can do edl printgpt and get results. EDL test points. On Win10, same AMD-machine, the command just end.

Found another thread on this topic, one guy suggested WinUSB driver, I tried. No luck. My guess is a Windows 10 update has done something. I will investigate more..

haitham-taher commented 2 weeks ago

Screenshot (5)

It will work with you to set up the port through this program and this option until it appears with you in device management like this.