set up device for development (???????????? no permissions)

What works for me is to kill and start the adb server again. On linux: sudo adb kill-server and then sudo adb start-server. Then it will detect nearly every device out of the box.

Nothing worked for me until I finally found the answer here:http://ptspts.blogspot.co.il/2011/10/how-to-fix-adb-no-permissions-error-on.html

I'm copying the text here in case it disappears in the future.

Create a file named /tmp/android.rules with the following contents (hex vendor numbers were taken from the vendor list page):

SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="0502", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="0b05", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="413c", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="0489", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="091e", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="24e3", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="2116", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="0482", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="17ef", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="1004", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="0409", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="2080", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="2257", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="10a9", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="1d4d", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="0471", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="04da", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="1f53", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="04dd", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="0930", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="19d2", MODE="0666"SUBSYSTEM=="usb", ATTRS{idVendor}=="1bbb", MODE="0666"

Run the following commands:

sudo cp /tmp/android.rules /etc/udev/rules.d/51-android.rulessudo chmod 644   /etc/udev/rules.d/51-android.rulessudo chown root. /etc/udev/rules.d/51-android.rulessudo service udev restartsudo killall adb

Disconnect the USB cable between the phone and the computer.

Reconnect the phone.

Run adb devices to confirm that now it has permission to access the phone.

Please note that it's possible to use , USER="$LOGINNAME" instead of , MODE="0666" in the .rules file, substituting $LOGINNAME for your login name, i.e. what id -nu prints.

In some cases it can be necessary to give the udev rules file a name that sorts close to the end, such as z51-android.rules.

Enter the following commands:

# cd to adb for sudocd `which adb | sed -e "s/adb//"`adb kill-serversudo ./adb start-server./adb devicesThis happens when you are not running adb server as root.