Unbricking a VOXL 2 - Pass but no ADB?
-
@tom Yes correct
-
@czarsimon Does the board enumerate via
lsusb? If so, what do you see? -
@tom With the QDL switch in the ON position:
Bus 002 Device 010: ID 05c6:9008 Qualcomm, Inc QUSB_BULK_CID:0412_SN:68E7EC23
With the QDL switch in the OFF position:
Bus 002 Device 010: ID 18d1:d00d Google Inc. Android Serial: f75e1ba6 -
@czarsimon Okay so with the switch off it is booting to fastboot, are you able to install the SDK at this point?
-
This post is deleted! -
@tom No, the device is not found in fastboot mode.
-
@czarsimon I can see by the output that the device is in fastboot mode, but it is still possible that fastboot itself isn't picking it up if the permissions on your machine aren't correct. If you try flashing the board with
sudodoes it detect the device? -
@tom The system image flashes with sudo, but the SDK does not; no adb devices are showing up and lsusb shows the same output after the flash.
-
@czarsimon Can you verify whether your board has a QSM8250 (M0054-2) or a QRB5165 (M0054-1) and that you're flashing the correct QDL image as well as kernel choice when flashing the SDK?
https://docs.modalai.com/m0054-versions/#m0054-1-and-m0054-2
-
@tom This is the SOM, our company only gets the QRB5165M and we've been flashing the same system image for months so I'm confident that's not where the issue is:
-
@czarsimon When you run through the QDL process how long does it take for the flash to finish? seconds? minutes?
Also, are you able to ADB onto functional devices on this machine? Want to rule it weird permission issues
