# Unbricking a VOXL 2 - Pass but no ADB?

Source: https://forum.modalai.com/topic/4058/unbricking-a-voxl-2-pass-but-no-adb
Category: General Questions (https://forum.modalai.com/category/2/general-questions)
Posted: 2025-01-03 17:24:15 UTC by czarsimon
Replies: 13 · Views: 2518

## czarsimon · 2025-01-03 17:24:15 UTC

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-device` hangs for over 5 minutes

## Reply by tom (ModalAI staff) · 2025-01-03 21:41:57 UTC

@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

## Reply by czarsimon · 2025-01-03 21:49:41 UTC (in reply to tom)

Hi @tom I can confirm the VOXL 2s I have are QRB5165M.

## Reply by tom (ModalAI staff) · 2025-01-04 23:30:32 UTC (in reply to czarsimon)

@czarsimon And after the QDL process are you turning the switch back off and power cycling the board?

## Reply by czarsimon · 2025-01-06 15:36:24 UTC (in reply to tom)

@tom Yes correct

## Reply by tom (ModalAI staff) · 2025-01-06 17:28:51 UTC (in reply to czarsimon)

@czarsimon Does the board enumerate via `lsusb`? If so, what do you see?

## Reply by czarsimon · 2025-01-06 22:29:10 UTC (in reply to tom)

@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`

## Reply by tom (ModalAI staff) · 2025-01-06 23:21:04 UTC (in reply to czarsimon)

@czarsimon Okay so with the switch off it is booting to fastboot, are you able to install the SDK at this point?

## Reply by czarsimon · 2025-01-07 14:44:44 UTC (in reply to tom)

@tom No, the device is not found in fastboot mode.

## Reply by tom (ModalAI staff) · 2025-01-07 17:55:35 UTC (in reply to czarsimon)

@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 `sudo` does it detect the device?

## Reply by czarsimon · 2025-01-16 16:35:33 UTC (in reply to tom)

@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.

## Reply by tom (ModalAI staff) · 2025-01-16 17:28:07 UTC (in reply to czarsimon)

@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

## Reply by czarsimon · 2025-01-20 15:53:44 UTC (in reply to tom)

@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:

![D9A703E0-16D4-4F5A-A0BC-90FC297A6BDC.jpg](https://forum.modalai.com/assets/uploads/files/1737388366967-d9a703e0-16d4-4f5a-a0bc-90fc297a6bdc.jpg)

## Reply by tom (ModalAI staff) · 2025-01-20 17:40:55 UTC (in reply to czarsimon)

@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