2 回答
Instead of:
adb kill-server
adb start-server
I tried:
sudo adb kill-server
sudo adb start-server
somehow this works. I dont know why.
It sounds like your udev rule is broken and at one point you started the adb daemon as the root user. This is pretty easy to do accidentally since executing adb with any command will launch the daemon if it isn't already started. Using the root user to manually launch the daemon is fine as workaround, but tools like Eclipse that automatically start the service will still attempt to as an unprivileged user (which will cause the reported problem). The proper fix is to follow the official steps under Configuring USB Access.