ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Bricked VOXL2

    VOXL 2
    2
    2
    15
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      roy.crosthwaite
      last edited by roy.crosthwaite

      Greetings,
      I have a fully bricked VOXL2 on a Starling 2 Max. I have gone through the forum and documents processes without success and have concluded that there is way more wrong than a typical unbricking can fix. Give you a little history here... This thing has bricked a couple of times and I was able to easily make a full recovery. I updated the SDK to 1.5.0 after the first bricking and everything seemed to be OK. I was going to test a new GPS module (issue submitted under a different forum topic) and had the WiFi set to AP mode so I could connect wirelessly. I powered everything up on the bench, connected via ADB and ran voxl-inspect-gps to see if the new module was detected, and it was. Thinking everything was GTG, I powered down and took the drone outside to verify that it could see satellites. Powered it up and waited for the SSID to become visible and it never did, even after a couple of power cycles. So, back to the bench with it.
      I attempted to do yet another unbricking only to discover that I couldn't communicate with it via USB. adb shell returns no device found and putting it into fastboot (presumably) and fastboot doesn't detect a device either. The only way I see the device is with lsusb or the web interface shown below.Screenshot from 2025-11-06 15-11-45.png
      Screenshot from 2025-11-11 11-13-52.png
      I find it interesting that it can be detected but not respond to external commands - the lights are on but nobody is home.

      So, where do I go from here?
      Current configuration:
      system-image: 1.8.04-M0054-14.1a-perf
      kernel: #1 SMP PREEMPT Mon Mar 24 22:31:58 UTC 2025 4.19.125
      hw platform: M0054
      mach.var: 1.0.1
      SKU: MRB-D0012-4-V2-C29-T9-M24-X0
      voxl-suite: 1.5.0

      N. ChenN 1 Reply Last reply Reply Quote 0
      • N. ChenN
        N. Chen @roy.crosthwaite
        last edited by

        @roy-crosthwaite said in Bricked VOXL2:

        The only way I see the device is with lsusb or the web interface shown below

        I've just received the voxl2, so not a lot of experience with it. Just for me to understand-- why not try to unbrick it with the qdl webUI, as it is the only tool that detects it? I'm asking since I have the my board at the same exact state, but this webUI tool failed, so I'm wondering if you know something that I don't (like whether seeing the device via fastboot is a prerequisite for the unbricking).

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Powered by NodeBB | Contributors