Posts made by lhermosillo

@N-Chen

Yea, I pretty much have given up on recovering those flight logs and am more concerned now with saving the VOXL itself.

I've tried that process and keep seeing this message when flashing:

{"message": "modal hello\n[MODALAI] test log\n\n[MODALAI] Executing usb_open\n[MODALAI] Completed usb_open\n[MODALAI] Executing sahara_run\n\n\nFlash flat build failed\n"}

@tom

Hi,
I tried it, and got this result:

Flashing Flat Build...
{"message": "modal hello\n[MODALAI] test log\n\n[MODALAI] Executing usb_open\n[MODALAI] Completed usb_open\n[MODALAI] Executing sahara_run\n\n\nFlash flat build failed\n"}

Hi all,

I'm attempting to recover the last flight logs from a VOXL 2 that suffered a crash. The VOXL 2 appears to power on normally (LEDs light up, board shows no visible damage), but it will not allow me to connect via ADB, SSH, or fastboot.

When connected to a PC, the device shows up as: Qualcomm HS-USB QDLoader 9008, so EDL.

My goal:
I'm trying to recover flight logs from the onboard UFS storage before re-flashing the system image.

What I've tried:

• Installed Qualcomm USB drivers to recognize Qualcomm HS-USB QDLoader 9008 as COM5
• Installed QPST/QFIL 2.7.460 (digitally signed Qualcomm build)
• Tried accessing partitions via QFIL's Partition Manager using various prog_firehose_ddr.elf files
  Every attempt so far results in:

ERROR: function: sahara_rx_data: Unable to read packet header. Only read 0 bytes.
ERROR: function: sahara_main: Sahara protocol error
ERROR: function: main: Uploading Image using Sahara protocol failed
Download Fail: Sahara Fail: QsaharaServer Fail: Process fail

Hardware Information:

• Model: VOXL 2 (M0154)
• Software was likely VOXL2 SDK 1.40?
• I've accessed VOXL2 QDL Image 14.1a_1.7.8, VOXL2 QDL Image 14.1a_1.1.2, and M0054-2 Starling QDL Image 1.7.4, for their prog_firehose_ddr.elf files and none have worked.

Questions:
Before proceeding with ModalAI's QDL web-based flashing tool (which I understand will wipe the UFS storage), I'm trying to confirm:

• Is there a VOXL 2 M0154 specific QDL image that includes the correct prog_firehose_ddr.elf for data recovery?
• Can the modal-qdl CLI or GUI tools be used in a non-destructive way to read partitions, similar to QFIL's "Read Data" function?
• If not, is there any safe way to extract the partitions regarding flight logs before flashing the board back to factory state?

System Setup:

• Host: Windows 11 + Ubuntu (WSL2)
• Device Manager shows: Qualcomm HS-USB QDLoader 9008 (COM 5)
• When attaching the Bus ID from Windows to WSL, lsusb shows: Bus 001 Device 003: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Any help or access to the proper prog_firehose_ddr.elf for M0154 would be greatly appreciated.
My main priority is preserving those flight logs to narrow down what went wrong during a simple arm test.

Images:
(This VOXL 2 was from a legacy flight deck)

(QFIL Tool attempts for data recovery)

Hi Support,

I have a VOXL 2 which I cannot connect to anymore. It was working fine for hours until it suddenly started kicking us out of our ADB connection and flashing its DS2 LED.

Unusual symptoms:

• DS2 - User Controllable RGB LED: Flashes green LED very fast, instead of solid green
• D1 - When I plug in USB-C, D1 starts flashing green in bursts.

Specific Issue:

• Can't connect to the VOXL 2 through ADB anymore
• We have multiple other VOXLs' which work fine with our cables and connections

We've tried fast-booting into it and switching into QDL to no avail as it won't show up on any of the USB lists.

Thanks