View Single Post
Old 08-11-2021, 07:30 PM   #24
mergen3107
Wizard
mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.
 
mergen3107's Avatar
 
Posts: 1,514
Karma: 5000046
Join Date: Feb 2012
Location: Cape Canaveral
Device: Kindle Scribe
Yes, all these sessions are similar: fresh boot into Android, go to Settings to enable USB debugging, "adb reboot edl", then "python edl loader=loader.file" (and I tried both .elf and .bin) and gives these messages in the same manner each time.

All this happens while Windows 10 is still booted in no-driver-signature mode, otherwise Qualcomm drivers are blocked and edl doesn't even see the device.


Quote:
Originally Posted by Renate View Post

You might use my UsbLog.exe (in the sig).
It's handy for seeing USB connect/disconnects.
Sorry, where is that?
mergen3107 is offline   Reply With Quote