View Single Post
Old 04-07-2022, 06:11 PM   #31
Renate
Onyx-maniac
Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.
 
Posts: 3,941
Karma: 17500001
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
Something very screwy is going on here. Does everybody have a bogus fastboot from Hades or what?

Ok, on my Android page, down the middle is "imxlink.exe". It's a utility for something else but it will give you a quick and dirty test. Keep your eye on the little flashy "LEDs" that pop up. Do this when your device is supposedly in fastboot mode already. It should flash yellow and say something similar:

Code:
C:\>imxlink.exe
Waiting for bootloader or Fastboot or ADB...
product     surfna
version     0.5
C:\>
It shouldn't sit there waiting. If your device is in ADB it will end quickly saying ADB, blah, blah.


Ok, my fault (again).

Apparently fastboot will only work with the correct interface GUID.
You can't use Zadig for it. I just tried. (Interestingly enough, my little imxlink.exe can talk to it just fine).
Find your device under Device Manager (devmgmt.msc) and do auto install of best driver.

Last edited by Renate; 04-07-2022 at 06:24 PM.
Renate is offline   Reply With Quote