Show better error descriptions

[incognitojam]

Instead of showing "Flash failed" with generic instructions, we might know the cause of a particular error.

Examples:

• NotFoundError: Failed to execute '*' on 'USBDevice': The device was disconnected.
  • Most likely caused by the device being unplugged/faulty cable
• NetworkError: Failed to execute '*' on 'USBDevice': A transfer error has occurred.
  • The device has stopped responding or we are unable to communicate with the device. Either an issue with qcserial driver being bound to the device, the device is in a bad state, or the power delivered to the device is not enough.
• SecurityError: Failed to execute 'open' on 'USBDevice': Access denied.
  • This may be caused by udev rules preventing communication with the device - example rules here
• NetworkError: Failed to execute 'claimInterface' on 'USBDevice': Unable to claim interface.
  • Likely caused by qcserial driver being bound to the device.

[incognitojam]

With a comma three (serial 696f4917) and single USB cable (no power delivered to OBD-C port) I encountered the A transfer error has occurred. error today. I'm not sure what percentage it reached but it had almost finished flashing system.

I don't have a process for debugging this yet - I wonder whether QDL sent us any error response before we lost connection and whether qdl.js isn't reporting it

[incognitojam]

I tried again and got the same error. Trying a third time but with power delivered to the OBD-C port was successful.

Will see if this is still an issue after flashing is fast (no unsparsify)