I’ve tried searching for the error but couldn’t find any useful results. Any ideas on what to do next?
I found this documentation on the source of the error but my Internet searching isn’t turning up much else:
int libusb_open(libusb_device *dev, libusb_device_handle **devh) Open a device and obtain a device_handle. Returns 0 on success, LIBUSB_ERROR_NO_MEM on memory allocation problems, LIBUSB_ERROR_ACCESS on permissions problems, LIBUSB_ERROR_NO_DEVICE if the device has been disconnected and a LIBUSB_ERROR code on other errors.
I confess I haven’t. I’ll try there and see if I can find success. If so, I will close this thread. I don’t want to hijack it with my particular issue.
Was using Qubes OS. Used a PureOS live image, a USB-A to C adapter, and followed the guide linked in my first post for success. I believe the USB-A to C adapter is a critical requirement for flashing success. I would want others to validate with their experience. I was previously using C to C and getting a lot of errors.
Then it stands to evidence that it was an issue with my USB-C to C cable. My suggestion to future readers to consider the cable as a potential source of issue. I received Error: Unknown Command: FB: reboot errors until I swapped out the cable. And then I received the LIBUSB error with Qubes. And then once I used a PureOS image with the right cable did I get a successful flash.
Cable, yes, but also cable orientation. If you use USB-C then there are 4 orientations. That’s another reason I am happy to use a USB-A to USB-C cable (only 2 orientations). But to be honest I’ve never had a problem with getting into Serial Download mode (for Jumpdrive, reflash, and other things).
I did not know that. I saw some posts about trying different cable orientations but felt like it was better to try A to C instead. So I appreciate the knowledge. One of the highlights of being in this community is the knowledge transfer. Thanks for that.