Unbricking a VOXL 2 - Pass but no ADB?
-
Hi,
I'm trying to follow the steps listed here to unbrick a VOXL 2: https://docs.modalai.com/voxl2-unbricking. However, after the process completes I'm unable to access it through adb. I tried running it on two computers and multiple VOXL 2s with the same results. The following is the output of the QDL Tool:
Selected Flat Build:2024-06-17-1.7.4-M0054-1 Provisioning UFS... {"message": "UFS provisioning succeeded, please reset power to the device\n"} Flashing CDT... {"message": "Flash CDT succeeded\n"} Flashing Flat Build... {"message": "Flash flat build passed\n"}After that and a reboot
adb wait-for-devicehangs for over 5 minutes@czarsimon Can you confirm that you are flashing the correct image for your board? M0054-1 (QRB) vs M0054-2 (QSM)?
https://docs.modalai.com/m0054-versions/#m0054-1-and-m0054-2
-
@czarsimon Can you confirm that you are flashing the correct image for your board? M0054-1 (QRB) vs M0054-2 (QSM)?
https://docs.modalai.com/m0054-versions/#m0054-1-and-m0054-2
-
@czarsimon And after the QDL process are you turning the switch back off and power cycling the board?
-
@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?
-
@czarsimon Okay so with the switch off it is booting to fastboot, are you able to install the SDK at this point?
-
@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? -
@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
-
@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:
Reading along? Create a free ModalAI Forum account to join in.
With an account you can reply, ask your own question, get an email when a ModalAI engineer answers, and mark the reply that solved it. Your place in each thread is saved between visits.
Questions about VOXL, Flight Core, ESCs and ModalAI drones are answered here by the engineers who build them.
Register Login