@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:
Latest posts made by czarsimon
-
RE: Unbricking a VOXL 2 - Pass but no ADB?
-
RE: Unbricking a VOXL 2 - Pass but no ADB?
@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.
-
RE: Unbricking a VOXL 2 - Pass but no ADB?
@tom No, the device is not found in fastboot mode.
-
RE: Unbricking a VOXL 2 - Pass but no ADB?
@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
-
RE: Unbricking a VOXL 2 - Pass but no ADB?
Hi @tom I can confirm the VOXL 2s I have are QRB5165M.
-
Unbricking a VOXL 2 - Pass but no ADB?
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 -
RE: IMU Server not working VOXL/RB5 Flight
@Advait-Pandit Did you ever figure this out? We're running into the same problem on multiple VOXL 2s.
-
RE: VOXL 2 /data mount error
@tom I tried restoring the superblock using
mke2fs -n /dev/sda8
to find backups and then trying all of them withe2fsck -b <backup_superblock> /dev/sda8
All of them failed to restore the filesystem. I'm seeing this on multiple VOXL 2s so it's not isolated just to this one. -
RE: VOXL 2 /data mount error
@tom I just tried it, got stuck at the following step even after hard rebooting the device:
... Flashing: modalai_cal | m0054-cal-fs.ext4 [------------------------------------------------------------ ]( 94%) Done Flashing [----------------------------------------------------------------](100%) < waiting for any device > ./flash-system-image.sh: line 624: 36563 Killed: 9 fastboot reboot [INFO] Waiting for ADB, if this takes more than 1 minute power cycle VOXL
Nothing using
adb devices