fpv-wtf / wtfos

A framework for modifying the firmware of DJI FPV Goggles and Air Units
https://fpv.wtf
MIT License
266 stars 12 forks source link

Could not connect to device, make sure that adb server is not running on your machine (adb kill-server) and that you are not connected in another tab/window. #68

Closed levin-wy closed 1 year ago

levin-wy commented 1 year ago

When I connet the DJI Air Unit,it show me this: Could not connect to device, make sure that adb server is not running on your machine (adb kill-server) and that you are not connected in another tab/window.

vjvenida commented 1 year ago

I have the same error.. Are you able to fix this error? thanks

levin-wy commented 1 year ago

I haven't found a way.

vjvenida commented 1 year ago

I'm trying this fix right now. I think you should too..

https://github.com/fpv-wtf/wtfos-configurator/issues/230

vjvenida commented 1 year ago

dude, fixed mine.. its now working. Run butter, update dji assistant 0606 then re-root goggle then install wtfos. https://github.com/fpv-wtf/margerine/wiki/Troubleshooting#wtfos-install-stuck-in-a-loop

vjvenida commented 1 year ago

WTFOS Team, Thank you so much for this!

yak-54 commented 1 year ago

Hi i have this issue as well with an air unit i did update v1 googles is fine i did one air unit as well its fine went to do one more air unit and all i get is this

Could not connect to device, make sure that adb server is not running on your machine (adb kill-server) and that you are not connected in another tab/window

suprchunk commented 1 year ago

Same here. Worked last week, on the same unit.

j005u commented 1 year ago

This issue should be fixed by going to https://fpv.wtf/root and re-rooting. Sometimes you may have to do it multiple times during an install process.

Tracking this as a recursion here: https://github.com/fpv-wtf/wtfos-configurator/issues/176

j005u commented 1 year ago

Closing, todays version of the configurator should further reduce weird errors during rooting.

If anyone here still can't root, please re-open with a new issue and a specific description of your situation.