VOXL2 bricked
-
-
Bus 004 Device 043: ID 05c6:901d Qualcomm, Inc. QUSB_BULK_SN:ACA1BAE9
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 0bda:b00c Realtek Semiconductor Corp. 802.11ac WLAN Adapter
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 05c8:0b05 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP True Vision HD Camera
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -
@McMason Follow the instructions here in order to restore your VOXL2 to a functioning state: https://docs.modalai.com/voxl2-qdl/#summary
-
@tom thank you sir I just pushed on and we are getting somewhere now. Thank you all
-
@tom after the QDL process I am now able to see the vehicle "ADB Devices". I am not however able to see the device in "Fastboot Devices." I cant find anything through the forum for this point. I checked the version while in the "ADB Shell" and it matches what was flashed, and pointed to continue with the latest system image procedure.
-
ultimately looking for confirmation to continue or be pointed to other steps needed. Any guidance is appreciated.
-
@McMason VOXL2 can either be in ADB mode or Fastboot mode, not both at the same time.
One can go from adb to fastboot using “adb reboot bootloader” or from fastboot to adb using “fastboot reboot” or by power cycling.
In order to flash the platform release on top of your newly QDL’ed VOXL2 you can use the “install.sh” script that is packaged in with the platform release. Look for “VOXL2_Platform_0.9” on downloads.modalai.com
(Apologies writing this on my phone, can send actual links shortly)
-
@McMason If you're having trouble getting into fastboot via. the command line you can follow this tutorial (https://www.youtube.com/watch?v=IM3PnW7cipQ) to force it into fastboot via. a button
-
Hi @tom ,
I've tried the steps listed above, when i try fastboot reboot it gets hung up on waiting for any device. Going back the initial post, I can see the device under ADB devices, forcing into fastboot and running fastboot devices-there is no output just goes to another command line. When i try ADB devices nothing is listed so it seems like it went into fastboot. When i run install.sh command it gives the failed to boot into fastboot exiting line. When i try to run the install.sh from power on there is a found adb device-rebooting to fastboot. Then it says failed to boot to fastboot.
-
@McMason After attempting to force it into fastboot via. the button, what do you see in
lsusb?Also, it can be helpful to run
dmesg -wHin a terminal window to monitor the devices as they are being detected by the host system. -
Hi @tom,
Thank you for your help, I got it going and is now back to a usable state! -
This post is deleted!
