Unbrick Voxl2

[CJ]

This post is deleted!

[CJ]

@wilkinsaf Yes, I've download from snap store. Thanks for your tips. I'll try to download using git clone.

[CJ]

@CJ said in Unbrick Voxl2:

@wilkinsaf Yes, I've download from snap store. Thanks for your tips. I'll try to download using git clone.

The git clone version works but still unable to adb to the drone after successfully flashed.

[CJ]

@tom After I've flashed the drone, I'm not able to adb.

The usb connection shows as fastboot (see image below) instead of

Bus 001 Device 022: ID 05c6:901d Qualcomm, Inc. KONA-QRD _SN:21217FEB

Can you advise how to fix this?

[CJ]

This post is deleted!

[tom]

@CJ That may be okay, I would try forcing the voxl2 into fastboot using the SW2 button as seen here: https://www.youtube.com/watch?v=IM3PnW7cipQ

then flashing the latest SDK release

[CJ]

@tom Hi, I've completed the flashing of latest SDK release. But I'm not able to adb shell into the drone.

The condition remains the same even after I did a power cycle, adb kill-server and adb start-server. Pls help.

[tom]

@CJ What operating system are you running? Are you using a virtual machine? I haven't seen this error before myself

[CJ]

@tom Hi Tom,
The OS is ubuntu 22.04 and not on virtual machine.
It seems like it cannot come out of fastboot mode and waiting for adb connection.

[tom]

@CJ After rebooting, what do you see with lsusb?

[CJ]

@tom Pls see the image below. The Google Inc.... (fastboot) is the drone usb.

[tom]

@CJ If another QDL flash doesn't solve it, this might require an RMA for us to investigate: https://www.modalai.com/pages/rma

[CJ]

@tom What will be the likely cause for the drone not getting out of fastboot mode?

[tom]

@CJ Unkown. Were you ever able to QDL successfully?

[CJ]

@tom Yes, the QDL is successful.

And installing the SDK is also successful but it just wait for adb interface to be up, which the usb is still in fastboot mode after power cycle.

[tom]

@CJ This is definitely abnormal which makes me think something hardware / power wise is causing the voxl2 to boot directly to fastboot. Your easiest resolution may be to submit an RMA so that you don't risk damaging your board further taking apart the drone

[ck]

@tom , may I know what is the likely component that might need to replace to resolve this issues as the RMA cost of sending the drone may outweigh the replacement.

[tom]

@ck Can't give you an answer as it would require an inspection from our team

[ErezI]

Hi,

I had the same problem.

You can try to transfer to the normal operation (& ADB)
by:
fastboot continue

and disconnect-connect the USB cable in order to enable
the USB change to ADB.

Erez