# What is the correct process to recover the voxl 2?

Source: https://forum.modalai.com/topic/1927/what-is-the-correct-process-to-recover-the-voxl-2
Category: VOXL 2 and VOXL 2 Mini (https://forum.modalai.com/category/26/voxl-2-and-voxl-2-mini)
Tags: voxl-2
Posted: 2023-03-09 00:55:51 UTC by m1baldwin
Replies: 7 · Views: 1797

## m1baldwin · 2023-03-09 00:55:51 UTC

The instructions on the documentation for re-flashing the system image on the voxl 2 doesn't quite match what the latest scripts from the voxl2 platform 0.9 image tar provide. The package provides an "install.sh" script as the entry point for re-flashing. The instructions mention there should be a "flash-full.sh" script. 

Assuming the above is supposed to be the correct script, I did try putting my voxl 2 into fastboot state and running the install script. It was able to identify the partition and reset the board, but it hangs at the "Waiting for ADB" step. The voxl 2 is showing up in dmesg as a Qualcomm device, but adb doesn't show it as available, hence it hanging at the waiting for adb step. 

Any ideas on what to try?

## Reply by tom (ModalAI staff) · 2023-03-09 01:07:10 UTC

@m1baldwin You're right, the newer releases changed the name to `install.sh`

Can you post the output of `lsusb` on your host PC so we can see exactly what state the VOXL2 is booting into?

## Reply by m1baldwin · 2023-03-09 13:54:29 UTC

Output from lsusb when voxl2 has been placed in fastboot mode:

mb@mb-HP-EliteBook-840-G7-Notebook-PC:~/Downloads/voxl2_platform_0.9$ lsusb
Bus 004 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 002 Device 017: ID 18d1:d00d Google Inc. 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 06cb:00df Synaptics, Inc. 
Bus 001 Device 002: ID 04f2:b6bf Chicony Electronics Co., Ltd 
Bus 001 Device 004: ID 8087:0026 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Lsusb after the flashing and while the script waits for adb to come back up
mb@mb-HP-EliteBook-840-G7-Notebook-PC:~/Downloads/voxl2_platform_0.9$ lsusb
Bus 004 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 002 Device 018: ID 05c6:901d Qualcomm, Inc. 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 06cb:00df Synaptics, Inc. 
Bus 001 Device 002: ID 04f2:b6bf Chicony Electronics Co., Ltd 
Bus 001 Device 004: ID 8087:0026 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

dmesg output for fastboot mode:
[755391.801828] usb 2-1: new SuperSpeed Gen 1 USB device number 17 using xhci_hcd
[755391.823072] usb 2-1: New USB device found, idVendor=18d1, idProduct=d00d, bcdDevice= 1.00
[755391.823082] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[755391.823087] usb 2-1: Product: Android
[755391.823092] usb 2-1: Manufacturer: Google
[755391.823096] usb 2-1: SerialNumber: 9ce13470

dmesg for after fastboot, while waiting for adb to become available:
[755509.829081] usb 2-1: new SuperSpeed Gen 1 USB device number 18 using xhci_hcd
[755509.856499] usb 2-1: New USB device found, idVendor=05c6, idProduct=901d, bcdDevice= 0.00
[755509.856508] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[755509.856513] usb 2-1: Product: QUSB_BULK_SN:A07D5C7A
[755509.856517] usb 2-1: Manufacturer: Qualcomm CDMA Technologies MSM
[755509.856520] usb 2-1: SerialNumber: 9ce13470

## Reply by tom (ModalAI staff) · 2023-03-09 17:54:11 UTC

@m1baldwin I would double check that your SW2 switch is OFF. If it is, it seems as though your VOXL2 may be in a bricked state and can be recovered via. QDL: https://docs.modalai.com/voxl2-qdl/

## Reply by m1baldwin · 2023-03-09 18:01:57 UTC

Yes, SW2 is in "off" state, so looks like voxl 2 is bricked. I'll try out the qdl instructions and come back with updates.

## Reply by m1baldwin · 2023-03-09 21:53:33 UTC

@tom That qdl reset did the trick, thanks!

## Reply by Dmytro Stolbovyi · 2025-10-16 14:32:47 UTC (in reply to tom)

@tom Hello. Could you please update this link as it doesn't work. I met with the same situation and need you assistance to recover voxl2

## Reply by tom (ModalAI staff) · 2025-10-16 18:06:31 UTC (in reply to Dmytro Stolbovyi)

@Dmytro-Stolbovyi Here is the updated link: https://docs.modalai.com/voxl2-unbricking/