# Voxl stuck in waiting after unbricking

Source: https://forum.modalai.com/topic/520/voxl-stuck-in-waiting-after-unbricking
Category: Development Drones (https://forum.modalai.com/category/44/development-drones)
Tags: voxl, m500
Posted: 2021-10-26 21:27:49 UTC by ashwin-umdlife
Replies: 9 · Views: 3454

## ashwin-umdlife · 2021-10-26 21:27:49 UTC

Hi Dev Team/ Community Members,

We have procured a few m500 drones from ModalAI. One of them is having the exact same issue as posted [here](https://forum.modalai.com/topic/402/voxl-stuck-in-waiting-for-device-after-unbricking) by one of the users.
We are able to communicate with other devices with adb.
We are using ModalAIs power adapter.

We tried the following but was unsuccessful:

* list item adb kill-server

* list item Using other computers to flash

We can flash other devices with the usb-expansion-fastboot module but not this particular m500 drone.

## Reply by modaltb (ModalAI staff) · 2021-10-26 22:05:50 UTC

Hi @ashwin-umdlife , sorry we crossed threads, see here: https://forum.modalai.com/topic/518/unable-to-unbrick-modalai-voxl-m500

## Reply by ashwin-umdlife · 2021-10-27 12:55:23 UTC (in reply to modaltb)

@modaltb said in [Voxl stuck in waiting after unbricking](/post/2427):
> Hi @ashwin-umdlife , sorry we crossed threads, see here: https://forum.modalai.com/topic/518/unable-to-unbrick-modalai-voxl-m500

@modaltb This post is quite different from https://forum.modalai.com/topic/518/unable-to-unbrick-modalai-voxl-m500. 

Here I am able to fastboot and start writing an image but gets stuck at the part were the board reboots and waits for the device. Please see this https://forum.modalai.com/topic/402/voxl-stuck-in-waiting-for-device-after-unbricking post. @Chad-Sweet recommended using `adb kill-server` and the user tried a different PC to flash. But both these methods didn't work for us.

## Reply by ashwin-umdlife · 2021-11-01 13:10:30 UTC

@modaltb @Chad-Sweet This issue has happened to another drone of ours. Could you please take a look at this ?

## Reply by modaltb (ModalAI staff) · 2021-11-01 15:34:17 UTC

Hi @ashwin-umdlife ,

We might need to setup a screen share if possible, can you let me know what timezone and then I'll try to schedule something.

From what I understand, you have attempted to re-flash the VOXL system image on QTY2 units now and both proceed through the process but are stuck at `[INFO] Waiting for device...` 

In the platform release download folder, can you please go here and try to run this script directly?

```
cd voxl_platform_3-3-0-0.4.6-b/system-image
sudo ./flash_build_apps.sh
```

If after this you are still stuck in `[INFO] Waiting for device...`, can you try:

- run `fastboot devices` or `sudo fastboot devices`
- if a device shows up, then  run `sudo fastboot reboot` to bring it out of fastboot (hopefully)

Thanks for your patience.

## Reply by modaltb (ModalAI staff) · 2021-11-01 15:39:41 UTC

Hi @ashwin-umdlife ,

We might need to setup a screen share if possible, can you let me know what timezone and then I'll try to schedule something.

From what I understand, you have attempted to re-flash the VOXL system image on QTY2 units now and both proceed through the process but are stuck at `[INFO] Waiting for device...` 

In the platform release download folder, can you please go here and try to run this script directly?

```
cd voxl_platform_3-3-0-0.4.6-b/system-image
sudo ./flash_build_apps.sh
```

If after this you are still stuck in `[INFO] Waiting for device...`, can you try:

- run `fastboot devices` or `sudo fastboot devices`
- if a device shows up, then  run `sudo fastboot reboot` to bring it out of fastboot (hopefully)

Thanks for your patience.

## Reply by ashwin-umdlife · 2021-11-01 22:14:38 UTC

@modaltb Tried all the steps mentioned above. But unfortunately nothing works.

Can we please schedule a meeting? How can I contact you?

## Reply by ashwin-umdlife · 2021-11-02 07:39:26 UTC (in reply to modaltb)

@modaltb I have an email to contact@modalai.com from our company email.

## Reply by modaltb (ModalAI staff) · 2021-11-02 17:12:54 UTC

Invite sent, we can do a screen share and see what's up.  thanks!

## Reply by wilkinsaf · 2022-11-14 22:16:36 UTC

Wanted to update this by saying I experienced same issue, but I resolved this by disconnecting tracking camera that had been installed upside down. So, if anyone is reading this in the future....try disconnecting your cameras attached to the board