# Cannot communicate over adb/fastboot after flashing image
Source: https://forum.modalai.com/topic/3263/cannot-communicate-over-adb-fastboot-after-flashing-image
Category: General Questions (https://forum.modalai.com/category/2/general-questions)
Posted: 2024-03-26 21:44:01 UTC by Kashish Garg 0
Replies: 19 · Views: 4351
## Kashish Garg 0 · 2024-03-26 21:44:01 UTC
Followed instructions from here: https://docs.modalai.com/voxl2-unbricking/ , flashing VOXL 2 QDL Image 14.1a_1.1.2
We cannot connect to the shell of the voxl2 through adb nor fastboot and have gone through the instruction set multiple times.
We noticed on the other working starling we have the system image version is 1.6.2-M0054-14.1a-perf
Any and all help is appreciated to getting this board unbricked.
## Reply by Alex Kushleyev (ModalAI staff) · 2024-03-27 22:05:01 UTC
@Kashish-Garg-0 , can you clarify if you went through the unbricking procedure completely or did it fail at some point? did you try to repeat the unbricking procedure?
## Reply by Kashish Garg 0 · 2024-03-28 14:44:50 UTC (in reply to Alex Kushleyev)
@Alex-Kushleyev Thanks for the quick reply!
Went through the unbricking process three times, the output from the qdl command matched exactly what was in the unbricking guide and there were zero indications of any errors throughout the process
## Reply by Alex Kushleyev (ModalAI staff) · 2024-03-28 14:47:27 UTC (in reply to Kashish Garg 0)
@Kashish-Garg-0 , so right after the procedure you were able to turn off SW2 and log into the board using adb?
## Reply by Kashish Garg 0 · 2024-03-28 15:34:47 UTC (in reply to Alex Kushleyev)
@Alex-Kushleyev I was able to turn off SW2, but I was unable to log into the board using adb. I tried reinstalling adb on my machine, I tried multiple machines and multiple usb-c cables. We have another, working, starling and we are able to log into adb there, so we are pretty sure it has to do with this voxl2 specifically.
## Reply by Alex Kushleyev (ModalAI staff) · 2024-03-28 15:59:24 UTC (in reply to Kashish Garg 0)
@Kashish-Garg-0 , thanks for clarifying. Was this board working originally and then something happened or was it "dead" when you received it?
## Reply by Kashish Garg 0 · 2024-03-29 16:55:23 UTC (in reply to Alex Kushleyev)
@Alex-Kushleyev it was working and we accidentally removed glibc in an attempt to upgrade it. Meaning we couldn't access the shell anymore.
## Reply by Alex Kushleyev (ModalAI staff) · 2024-03-30 01:29:16 UTC (in reply to Kashish Garg 0)
@Kashish-Garg-0 , I understand.
Can you try this procedure to force into fastboot and then perform SDK install?
https://docs.modalai.com/voxl2-voxl2-mini-system-image/#force-voxl-2-into-fastboot
## Reply by Kashish Garg 0 · 2024-04-01 15:34:59 UTC (in reply to Alex Kushleyev)
@Alex-Kushleyev Hey Alex, we have gone through this procedure a few times, even had a partner to make sure the button was being pressed appropriately. When running fastboot devices, no device gets identified.
## Reply by Alex Kushleyev (ModalAI staff) · 2024-04-01 19:08:43 UTC (in reply to Kashish Garg 0)
@Kashish-Garg-0 , I understand, thanks for clarifying.
My colleague, who has more experience with this, was out of office last week, coming back tomorrow. I will make sure he takes a look at your post, he may have some suggestions. @tom
Alex
## Reply by tom (ModalAI staff) · 2024-04-02 20:02:01 UTC (in reply to Kashish Garg 0)
@Kashish-Garg-0 With your device plugged in to your host pc via usb, what do you see with `lsusb` on your host PC?
## Reply by Kashish Garg 0 · 2024-04-05 15:36:46 UTC (in reply to tom)
@tom
```
Bus 005 Device 008: ID 05c6:900e Qualcomm, Inc.
```
Thanks for your help!
## Reply by tom (ModalAI staff) · 2024-04-05 16:57:37 UTC (in reply to Kashish Garg 0)
@Kashish-Garg-0 Okay so the device is booting into EDL mode, which is what is used for QDL flashing. Can you confirm that the EDL switch is turned off?
## Reply by Kashish Garg 0 · 2024-04-05 18:21:27 UTC (in reply to tom)
@tom Yes the EDL Switch is turned OFF, pointing away from the Processor
## Reply by tom (ModalAI staff) · 2024-04-05 18:50:39 UTC (in reply to Kashish Garg 0)
@Kashish-Garg-0 And when you went through the QDL process did the QDL flashing complete as expected? Should take around 10 minutes to complete
## Reply by Kashish Garg 0 · 2024-04-05 20:11:33 UTC (in reply to tom)
@tom I just re ran it and it took around 7 minutes or so and gave the appropriate output:
```
FIREHOSE READ:
FIREHOSE READ:
FIREHOSE READ:
FIREHOSE WRITE:
FIREHOSE READ:
FIREHOSE READ:
```
## Reply by tom (ModalAI staff) · 2024-04-05 20:55:08 UTC (in reply to Kashish Garg 0)
@Kashish-Garg-0 And then if you remove and replace both power and usb is it still booting to that same mode?
## Reply by Kashish Garg 0 · 2024-04-09 14:41:17 UTC (in reply to tom)
@tom You mean is it going to EDL mode after replacing power/usb and moving the EDL Switch to off?
```
Bus 005 Device 011: ID 05c6:900e Qualcomm, Inc. USB2.0 Hub
```
Is what is being printed with lsusb now
## Reply by tom (ModalAI staff) · 2024-04-09 17:48:16 UTC (in reply to Kashish Garg 0)
@Kashish-Garg-0 Sounds like we'll have get an RMA going for this one: https://www.modalai.com/pages/rma
## Reply by tom (ModalAI staff) · 2024-05-02 16:36:15 UTC (in reply to Kashish Garg 0)
@Kashish-Garg-0 It's possible your board has a QSM8250 (M0054-2) instead of a QRB5165 (M0054-1), see here for the diffs: https://docs.modalai.com/m0054-versions/#m0054-1-and-m0054-2
If that is the case then you will have to QDL using a different build, which you can download from downloads.modalai.com, look for `M0054-2 Starling QDL Image 1.7.4 2024-02-09-1.7.4-M0054-2.zip` under the "All" category