Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Collapse
Brand Logo

ModalAI Forum

  1. ModalAI Support Forum
  2. General Questions
  3. Failing to boot

Failing to boot

Scheduled Pinned Locked Moved Unsolved General Questions
2 Posts 2 Posters 2.1k Views 1 Watching
  • 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.
  • John KellerJ Offline
    John KellerJ Offline
    John Keller
    wrote on last edited by
    #1

    I was using the voxl2 on my starling 2 drone out in the sun for a few hours on a ~80 F day. Commands which would normally be responsive like ros2 topic echoing, etc. were taking a long time to output any text so I thought it might be overheating and powered it off.

    A few days later I tried turning it on and it doesn't boot up. I can't connect over adb shell. I get the following output from dmesg when plugging it in:

    [31549.649340] usb 1-9: new high-speed USB device number 15 using xhci_hcd
    [31549.800919] usb 1-9: New USB device found, idVendor=05c6, idProduct=900e, bcdDevice= 0.00
    [31549.800933] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [31549.800937] usb 1-9: Product: QUSB_BULK_SN:C67DF5D4
    [31549.800941] usb 1-9: Manufacturer: Qualcomm CDMA Technologies MSM
    [31549.800944] usb 1-9: SerialNumber: 22d3828

    I see this in lsusb

    Bus 001 Device 015: ID 05c6:900e Qualcomm, Inc. QUSB_BULK_SN:C67DF5D4

    fastboot devices doesn't list anything.

    Is there a way to fix or debug this? Thank you.

    Alex KushleyevA 1 Reply Last reply
    0
    • John KellerJ John Keller

      I was using the voxl2 on my starling 2 drone out in the sun for a few hours on a ~80 F day. Commands which would normally be responsive like ros2 topic echoing, etc. were taking a long time to output any text so I thought it might be overheating and powered it off.

      A few days later I tried turning it on and it doesn't boot up. I can't connect over adb shell. I get the following output from dmesg when plugging it in:

      [31549.649340] usb 1-9: new high-speed USB device number 15 using xhci_hcd
      [31549.800919] usb 1-9: New USB device found, idVendor=05c6, idProduct=900e, bcdDevice= 0.00
      [31549.800933] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
      [31549.800937] usb 1-9: Product: QUSB_BULK_SN:C67DF5D4
      [31549.800941] usb 1-9: Manufacturer: Qualcomm CDMA Technologies MSM
      [31549.800944] usb 1-9: SerialNumber: 22d3828

      I see this in lsusb

      Bus 001 Device 015: ID 05c6:900e Qualcomm, Inc. QUSB_BULK_SN:C67DF5D4

      fastboot devices doesn't list anything.

      Is there a way to fix or debug this? Thank you.

      Alex KushleyevA Offline
      Alex KushleyevA Offline
      Alex Kushleyev
      ModalAI Team
      wrote on last edited by
      #2

      @John-Keller , please try https://docs.modalai.com/voxl2-unbricking/

      1 Reply Last reply
      0

      Reading along? Create a free ModalAI Forum account to join in.

      With an account you can reply, ask your own question, get an email when a ModalAI engineer answers, and mark the reply that solved it. Your place in each thread is saved between visits.

      Questions about VOXL, Flight Core, ESCs and ModalAI drones are answered here by the engineers who build them.

      Register Login
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      ModalAI
      Categories Recent Tags ModalAI.com Docs
      © 2026 ModalAI® · Accelerating autonomy for smaller, smarter, safer drones · Powered by NodeBB
      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups