You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I've tried: two different USB-C cables, my 3X's OBD-C and an Apple USB-C. Laptop (Chrome/Ubuntu) and S26 phone (Chrome/Android). Power from 5V Dell charger and from 12V car harness.
I'm getting the same error on my Debian testing laptop with a Comma 4.
lsusb:
╚═ $ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 27c6:609c Shenzhen Goodix Technology Co.,Ltd. Goodix Fingerprint USB Device
Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 003 Device 013: ID 1050:0406 Yubico.com Yubikey 4/5 U2F+CCID
Bus 003 Device 091: ID 3801:9008 Qualcomm CDMA Technologies MSM QUSB_BULK_CID:0402_SN:5105F421
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
I believe Bus 003 Device 091: ID 3801:9008 Qualcomm CDMA Technologies MSM QUSB_BULK_CID:0402_SN:5105F421 is the Comma 4.
I had a similar issue. I had AI debug my system and it uncovered 2 things:
The WebUSB can enumerate the device, but was missing user write permission which resulted in the LOST_CONNECTION
Solved via udev rule. Note: this is the script I had it run. I have a 3X, so I'm not sure where it got the 4 vendor id from. Your mileage may vary
sudo tee /etc/udev/rules.d/99-comma-qdl.rules <<'EOF'# comma 3/3X QDLSUBSYSTEM=="usb", ATTR{idVendor}=="05c6", ATTR{idProduct}=="9008", MODE="0666", TAG+="uaccess"# comma four QDL (harmless to include)SUBSYSTEM=="usb", ATTR{idVendor}=="3801", ATTR{idProduct}=="9008", MODE="0666", TAG+="uaccess"EOF
sudo udevadm control --reload-rules
sudo udevadm trigger
Then, unplugging and plugging back in via the same 1/2 order that the site describes.
After solving that, the flash started but failed at ~33% of the download. This was related to attempting to do the flash in an Incognito chromium window.
Activity
simontheflutist commentedon Aug 8, 2026
error when using my Apple USB-C
Bug Report - flash.comma.ai
Device: comma four
Serial: N/A
Error: LOST_CONNECTION
Step: CONNECTING
Last Message: N/A
OS: Linux
Sandbox: None detected
Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/151.0.0.0 Safari/537.36
URL: https://flash.comma.ai/
Time: 2026-08-08T00:28:38.434Z
Console Logs
simontheflutist commentedon Aug 8, 2026
power from car harness, data from laptop
Bug Report - flash.comma.ai
Device: comma four
Serial: N/A
Error: LOST_CONNECTION
Step: CONNECTING
Last Message: N/A
OS: Linux
Sandbox: None detected
Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/151.0.0.0 Safari/537.36
URL: https://flash.comma.ai/
Time: 2026-08-08T00:39:04.991Z
Console Logs
simontheflutist commentedon Aug 8, 2026
On my Android phone, USB-C to data port simply doesn't work. The device just boots normally and doesn't show up in flash.comma.ai.
simontheflutist commentedon Aug 8, 2026
What I've tried: two different USB-C cables, my 3X's OBD-C and an Apple USB-C. Laptop (Chrome/Ubuntu) and S26 phone (Chrome/Android). Power from 5V Dell charger and from 12V car harness.
simontheflutist commentedon Aug 8, 2026
Tried a third USB cable of unknown provenance. Same error. Chrome with and without incognito mode.
simontheflutist commentedon Aug 8, 2026
Same error on a fourth USB cable. Support ticket 82804.
stefpi commentedon Aug 8, 2026
work around for now
start a chrome instance with a fresh user data directory:
and then run the flash process as normal
stefpi commentedon Aug 8, 2026
another good place to look when stuff like this happens is:
chrome://device-log/for example. I was also having connection issues and the following was in my device log:

this is a bad experience though, so we need to figure out why this happens in the first place
adeebshihadeh commentedon Aug 8, 2026
Looks like a permission issue?
stefpi commentedon Aug 8, 2026
my chromium was installed from the ubuntu app center via
snapwhich requires a connection to raw-usb snap package in order for flash to work.in comparison, my google chrome installed via .deb from google website runs outside of sandbox and doesn't need anything.
simontheflutist commentedon Aug 8, 2026
my Google Chrome is installed via deb too. Before trying your workaround @stefpi this is the error I get in device-log:
simontheflutist commentedon Aug 8, 2026
@stefpi even with your user-dir workaround, I get the same error.
Bug Report - flash.comma.ai
Device: comma four
Serial: N/A
Error: LOST_CONNECTION
Step: CONNECTING
Last Message: N/A
OS: Linux
Sandbox: None detected
Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/151.0.0.0 Safari/537.36
URL: https://flash.comma.ai/
Time: 2026-08-08T02:28:09.761Z
Console Logs
andiradulescu commentedon Aug 8, 2026
permission error for #227 (comment) reported in #110
might be a good time to put a PR to detect this case and show the user the command it needs to run
simontheflutist commentedon Aug 8, 2026
@andiradulescu that report is for snap install chromium. I'm on Google's deb:
andiradulescu commentedon Aug 8, 2026
@simontheflutist yes, I read, I forgot to quote #227 (comment)
andiradulescu commentedon Aug 8, 2026
@simontheflutist I know it might sound stupid, but did you try to run the snap command, though?
actually nevermind, impossible to be this
andiradulescu commentedon Aug 8, 2026
Could you run these while the comma four is connected, ideally also while attempting the connection in flash.comma.ai?
Then:
Where BBB/DDD are the ones you see in the chrome logs.
cwiggs commentedon Sep 6, 2026
I'm getting the same error on my Debian testing laptop with a Comma 4.
lsusb:
I believe
Bus 003 Device 091: ID 3801:9008 Qualcomm CDMA Technologies MSM QUSB_BULK_CID:0402_SN:5105F421is the Comma 4.Some udev results:
output of
udevadm info --query=all --name=/dev/bus/usb/003/092cwiggs commentedon Sep 6, 2026
I had chromium via flatpak installed. I ran
flatpak override --user --filesystem=/run/udev:ro org.chromium.Chromiumbut that did not fix it.I also switched to a .deb version and have the same error.
cwiggs commentedon Sep 6, 2026
I also tried:
Both resulted in the same error.
devzeebo commentedon Sep 18, 2026
I had a similar issue. I had AI debug my system and it uncovered 2 things:
Solved via udev rule. Note: this is the script I had it run. I have a 3X, so I'm not sure where it got the 4 vendor id from. Your mileage may vary
Then, unplugging and plugging back in via the same 1/2 order that the site describes.
chromium --user-data-dir="/tmp/comma-flash-chrome" https://flash.comma.ai/I'm running Arch and installed chromium via pacman