I think I've successfully unbricked our Starling 2 Max QRB5165M with the VOXL 2 QDL Image 14.1a_1.7.8 image. I can now get into it with adb shell. I then reboot it into fastboot by holding the SW1 button while plugging it into wall power and then the USB cable to an Ubuntu host. I can then see it with fastboot devices. However, I can't seem to be able to flash it with the SDK. I've so far tried 1.1.3, 1.3.5, and 1.4.5, but they all fail at the same step:

nvidia@ubuntu:~/voxl2_SDK_1.3.5/system-image$ ./flash-system-image.sh -f
Detected OS: Linux


=======================================================================================================
BOARD IN FASTBOOT, CAN'T DETECT HARDWARE VERSION.
Please determine hardware version, -1 (QRB5165M) or -2 (QSM8250)

See docs.modalai.com/m0054-versions for more info.
=======================================================================================================

=======================================================================================================
In order to support all of VOXL's camera configurations, specific drones require differing kernel images.
Please select your drone hardware to proceed with flashing the appropriate kernel image.
=======================================================================================================

PLEASE SELECT WHICH KERNEL TO FLASH
1. M0054-1 -> QRB5165M, Starling (D0005), Sentinel (D0006), FPV (D0008), D0010, PX4 Dev Kit (D0011)
2. M0054-1 -> QRB5165M w/ M0173 Camera Breakout Board, Starling 2 Max (D0012), Starling 2 (D0014)
3. M0054-2 -> QSM8250, Starling (D0005), FPV (D0008)
4. M0054-2 -> QSM8250 w/ M0173 Camera Breakout Board, Starling 2 Max (D0012)
5. M0104-1 -> QRB5165M, Stinger (D0013)
6. M0104-2 -> QSM8250

Select your choice from above options: 2

Installer Version: 1.0
Image Version:     1.7.10
Board Version:     M0054-1 (var00.1)

Please power off your VOXL, connect via USB,
then power on VOXL. We will keep searching for
an ADB or Fastboot device over USB
[INFO] Found fastboot device
[WARNING] This system image flash is intended only for the following
          platform: VOXL2 (m0054) 

          Make sure that the device that will be flashed is correct.
          Flashing a device with an incorrect system image will lead
          the device to be stuck in fastboot.

Would you like to continue with the VOXL2 (m0054) system image flash?
1) Yes
2) No
#? 1
[INFO] checking partition system::0xD3B5D7000
[INFO] {system::0xD3B5D7000} partition returned size {0xd3ddd7000}, expected {0xd3b5d7000}
[WARNING] Partition layout was found to be incorrect, this requires
          flashing the full partition table. Flashing the partition
          table will also flash every partition causing all data on
          the device to be lost.

When doing a full flash, make sure to backup any important files

Would you like to continue with the full wipe/flash now?
1) Yes
2) No
#? 1
[INFO] Found all required files

Rebooting into bootloader                          OKAY [  0.000s]
Finished. Total time: 0.754s
Flashing: xbl_config_a | xbl_config.elf
[                                                                ](  0%)
Flashing: xbl_config_b | xbl_config.elf
[---                                                             ](  5%)
Flashing: xbl_a | xbl.elf
[-------                                                         ]( 11%)
Flashing: xbl_b | xbl.elf
[----------                                                      ]( 16%)
Flashing: abl_a | abl.elf
[--------------                                                  ]( 22%)
Flashing: abl_b | abl.elf
[-----------------                                               ]( 27%)
Flashing: modem_a | NON-HLOS.bin
[---------------------                                           ]( 33%)
Flashing: modem_b | NON-HLOS.bin
[------------------------                                        ]( 38%)
Flashing: devcfg_a | devcfg-m0054-1-v8.mbn
[----------------------------                                    ]( 44%)
Flashing: devcfg_b | devcfg-m0054-1-v8.mbn
[--------------------------------                                ]( 50%)
Flashing: dsp_a | dspso.bin
[-----------------------------------                             ]( 55%)
Flashing: dsp_b | dspso.bin
[---------------------------------------                         ]( 61%)
Flashing: boot_a | m0054-1-var00.1-kernel.img
[------------------------------------------                      ]( 66%)
Flashing: boot_b | m0054-1-var00.1-kernel.img
[----------------------------------------------                  ]( 72%)
Flashing: system | qti-ubuntu-robotics-image-m0054-sysfs.ext4
[-------------------------------------------------               ]( 77%)

[ERROR] Failed to flash partition: system

Sending sparse 'system' 1/5 (785306 KB)            OKAY [ 22.969s]
Writing 'system'                                   OKAY [  0.000s]
Sending sparse 'system' 2/5 (767436 KB)            OKAY [ 27.450s]
Writing 'system'                                   FAILED (remote: 'Error: Last flash failed : Device Error')
fastboot: error: Command failed

This has been the case both with ./install.sh and ./flash-system-image.sh -f as seen above. Any further suggestions?

@modaltb This simplest fix for us was to just change the hardcoded 'C' to a hardcoded 'A' and rebuild the deb. It's not the "proper" solution, but it should let us fly legally.

On a Starling 2 Max, I'm running voxl-remote-id to get the Remote ID serial number so that we can register with the FAA and fly. However, that script produces an invalid serial number, and I'd like to know your intended behavior. The format is supposed to be your ICAO ID ("1814"), plus the length (a value 1 to F representing the length of the next part, but which is hardcoded as "C" in voxl-remote-id/src/main.c), plus the manufacturer's serial number (which is read in from /sys/devices/soc0/serial_number). However on our drone, that last bit is only 10 characters long (e.g. 0123456789). In this case, the script currently generates a value of 1814C0123456789, which is invalid. The voxl-remote-id script definitely needs fixed, but how so? Should it be something like 1814A0123456789 or 1814C012345678900?