Unable to connect to host PC using adb shell & SSH

[[[global:former-user]]]

Those adb pull commands are backing up config files on the drone, if it's only accessible through fastboot you'll have to skip those steps and reflash the drone. By default the data partition on the board is not reflashed, so as long as that partition wasn't corrupted the data will still be there.

[tom]

@Mohammad-Saeid-Anwar If you end up flashing and the cam cal files are still missing we can likely provide you with them on request as we back them up before shipping out a drone.

[Mohammad Saeid Anwar]

I tried to flash your latest platform release (0.9). But I have faced the same issue. No ADB shell connection. Please take a look.

[Mohammad Saeid Anwar]

@tom @Alex-Gardner

[tom]

@Mohammad-Saeid-Anwar It seems your device is stuck in fastboot mode so don't worry about trying to pull off the cam cal files. What happens when you run the platform release install script?

[Mohammad Saeid Anwar]

Hello @tom This happened when I ran the platform release install script.

[tom]

@Mohammad-Saeid-Anwar Can you run the following commands on your host PC back to back and post the output here:

lsusb
adb devices
fastboot devices

[Mohammad Saeid Anwar]

@tom said in Unable to connect to host PC using adb shell & SSH:

fastboot devices

hey @tom this is the output.

[tom]

@Mohammad-Saeid-Anwar Hmm try the following:

adb kill-server
adb start-server
adb devices

[Mohammad Saeid Anwar]

@tom It's still same!!

[tom]

@Mohammad-Saeid-Anwar Do you have any other VOXLs that you are able to connect to via. ADB in order to determine that ADB was configured properly on your machine?

[Mohammad Saeid Anwar]

No. I don't have any other voxl.
Yes, it's properly installed. I had previously worked with the same ADB installation. Suddenly, it stopped responding. I also tried with two other machines with proper ADB installations. It showed the same problem (no device found).