# VOXL2 troubleshooting

Source: https://forum.modalai.com/topic/4445/voxl2-troubleshooting
Category: VOXL 2 and VOXL 2 Mini (https://forum.modalai.com/category/26/voxl-2-and-voxl-2-mini)
Tags: voxl-2
Posted: 2025-05-20 17:58:45 UTC by claw
Replies: 13 · Views: 1946

## claw · 2025-05-20 17:58:45 UTC

I have two VOXL2 boards as parts of Starling drones. They were both unresponsive to ADB so I reinstalled the base firmware using the unbrick procedures. I was able to get a successful result from QDL for both the provisioning and flat build install, however, ADB from my Linux machine does not find the devices. How do I troubleshoot this further?

Thank you

## Reply by Moderator (ModalAI staff) · 2025-05-21 14:26:39 UTC

@claw what does ```lsusb``` report?

## Reply by claw · 2025-05-22 19:36:44 UTC (in reply to Moderator)

@Moderator here is a screenshot before and after plugging the usb cable in:

![7eda5c82-560e-4fdb-8e27-11e1904e93d7-image.png](https://forum.modalai.com/assets/uploads/files/1747942592838-7eda5c82-560e-4fdb-8e27-11e1904e93d7-image.png)

## Reply by tom (ModalAI staff) · 2025-05-23 19:54:07 UTC (in reply to claw)

@claw It looks as though the board is booting into fastboot. At this point you should be able to install the voxl2_SDK with `./install.sh`

## Reply by claw · 2025-05-23 20:18:51 UTC (in reply to tom)

@tom oh, ok. I thought I'd have adb from the firmware. My mistake. Thanks for the help.

## Reply by claw · 2025-05-25 15:59:36 UTC (in reply to claw)

@tom I tried to install the SDK but it failed. 
I did re-read the instructions for unbricking which do say that ADB should be available after installing the flat build. Is there a mechanism for returning the boards for repair?

![e8165df7-6cf4-4744-8b01-78bf36c921c4-image.png](https://forum.modalai.com/assets/uploads/files/1748188767937-e8165df7-6cf4-4744-8b01-78bf36c921c4-image.png)

## Reply by tom (ModalAI staff) · 2025-05-27 16:56:04 UTC (in reply to claw)

@claw Can you double check that you're loading the correct QDL image? You'll need to determine whether your board is an M0054-1 or M0054-2

https://docs.modalai.com/m0054-versions/#m0054-1-and-m0054-2

## Reply by claw · 2025-05-27 19:36:31 UTC (in reply to tom)

@tom i did check that initially and again before I loaded it this last time. We have the older version boards.

## Reply by tom (ModalAI staff) · 2025-05-27 19:55:29 UTC (in reply to claw)

@claw Are you running Ubuntu natively? If so, what version?

## Reply by claw · 2025-05-28 16:26:45 UTC (in reply to tom)

@tom yes, 22.04

## Reply by tom (ModalAI staff) · 2025-05-28 17:37:08 UTC (in reply to claw)

@claw I would try installing the SDK with `./install.sh -w` to wipe all partitions and start fresh.

If that doesn't work it may be worth submitting an RMA: https://www.modalai.com/pages/rma

## Reply by claw · 2025-05-28 18:33:51 UTC (in reply to tom)

@tom thank you. I'll give that a shot.

## Reply by claw · 2025-05-28 21:08:18 UTC (in reply to claw)

@tom That completed successfully, but still doesn't provide adb. Also, lsusb still shows the fastboot device whereas the other Starlings that are working show a qualcom device.

## Reply by tom (ModalAI staff) · 2025-05-28 21:28:10 UTC (in reply to claw)

@claw That is definitely not the expected behavior, I recommend going through the RMA process