Android ADB shell cannot be started: insufficient permissions for device Solution

My platform: Ubuntu 10.04

Solution 1:Lsusb, view the vendorid, and add or modify the 51-android.rules file in the/etc/udev/rules. d/directory.
Add a record:
Subsystem = "USB", sysfs {idvendor} = "XXXX ",
Mode = "0666" where XXXX is the value obtained through lsusb

The following are common cases:
# HTC
Subsystem = "USB", sysfs {idvendor} = "0bb4", mode = "0666"
# Motorola
Subsystem = "USB", sysfs {idvendor} = "22b8", mode = "0666"
# ACS 0502
Subsystem = "USB", sysfs {idvendor} = "0502", mode = "0666"
# Dell 413c
Subsystem = "USB", sysfs {idvendor} = "413c", mode = "0666"
# Huawei 12d1
Subsystem = "USB", sysfs {idvendor} = "12d1", mode = "0666"
# LG 1004
Subsystem = "USB", sysfs {idvendor} = "1004", mode = "0666"
# NVIDIA 0955
Subsystem = "USB", sysfs {idvendor} = "0955", mode = "0666"
# Samsung 04e8
Subsystem = "USB", sysfs {idvendor} = "04e8", mode = "0666"
# Sharp 04dd
Subsystem = "USB", sysfs {idvendor} = "04dd", mode = "0666"
# Sony Ericsson ofce
Subsystem = "USB", sysfs {idvendor} = "0fce", mode = "0666"
# ZTE 19d2
Subsystem = "USB", sysfs {idvendor} = "19d2", mode = "0666"

Solution 2:
Write only one sentence in 51-android.rules:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666"  

Kill Solution

From: http://www.cppblog.com/kongque/archive/2011/04/02/143247.html