-
-
Notifications
You must be signed in to change notification settings - Fork 392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
COMMAND LINE QUITS AFTER DEVICE DETECTED #595
Comments
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): |
Same issue. I can't use your solution. No adb/fastboot. Windows 10 doesn't work for me. I tried on two machines and Zadig with libusb-win32, WinUSB and usbdk. Same. Any more ideas? |
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. Found another thread on this topic, one guy suggested WinUSB driver, I tried. No luck. |
The text was updated successfully, but these errors were encountered: