VOXL2 bricked
-
Hello,
Recently had a VOXL2 not show on ADB devices/ADB shell. Tried fastboot which works, performed the steps on unbricking the unit. The unit hung up on waiting for ADB Devices. I haven't tried the QDL steps yet.
Tried a new (4) pin harness to the PDU.
Verified all connectors were seated and correctly orientated.Ops of that day
The sentinel worked fine on testing connectivity for WiFi( just hand carried). Came back powered back on and nothing. -
-
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 -
@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.
-
@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)
-
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.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login