# VOXL no ADB access

Source: https://forum.modalai.com/topic/2485/voxl-no-adb-access
Category: General Questions (https://forum.modalai.com/category/2/general-questions)
Posted: 2023-07-25 10:07:57 UTC by SHofmeester
Replies: 7 · Views: 1560

## SHofmeester · 2023-07-25 10:07:57 UTC

Hi,

On one of our VOXLs I tried to access it using `adb shell`, but it couldn't find the device. It also doesn't show up when I use `adb devices`.
When I used this [procedure](https://docs.modalai.com/unbrick-voxl/#unbricking-procedure-for-voxl-and-voxl-flight) (that has worked on another device before), it keeps saying `Waiting for fastboot...`.

Is there another method?

Thanks in advance!

## Reply by tom (ModalAI staff) · 2023-07-25 16:56:24 UTC

@SHofmeester What does the device enumerate as with `lsusb`?

## Reply by SHofmeester · 2023-07-26 13:13:14 UTC (in reply to tom)

Hi @tom,

I tried `lsusb` both regularly and with the fastboot method from the unbricking procedure. But it didn't recognize the device. The result of `lsusb` was the same when it was plugged in and when it wasn't plugged in. I tried with another VOXL and it did recognize it.

## Reply by tom (ModalAI staff) · 2023-07-26 16:57:48 UTC (in reply to SHofmeester)

@SHofmeester Interesting, can you try with a different USB cable / port? How are you powering your VOXL?

## Reply by SHofmeester · 2023-07-31 10:01:23 UTC (in reply to tom)

@tom 
I'm powering the VOXL with the standard power module delivered with the VOXL.

I have tried different cables and ports, but the results are the same. Those are cables and ports do work with another VOXL we have.

Is there a specific location on the board we can measure with a multimeter to see if the VOXL is still functioning correctly on a hardware level? Or is that too difficult or dangerous?

## Reply by tom (ModalAI staff) · 2023-07-31 22:09:53 UTC (in reply to SHofmeester)

@SHofmeester I would recommend submitting an RMA: https://www.modalai.com/pages/rma

## Reply by majjam · 2023-07-31 23:31:04 UTC

I had the exact same problem on my Ubuntu 18.04 machine with the VOXL 2. 

To fix this, I had to restart the adb server with sudoers permissions. Maybe this will help:

```
adb kill-server
sudo adb start-server
```

## Reply by tom (ModalAI staff) · 2023-07-31 23:33:36 UTC (in reply to majjam)

@SHofmeester Another thing I just thought to try::

run `sudo dmesg -wH` and see if you see the VOXL enumerate when you plug it in to your machine