Environment: Ubuntu13.04 64-bit system, has installed JDK1.7.0U25,/usr/local/adt/adt-bundle-linux-x86_64-20130717
Problem: adb devices cannot display any devices.
Solution:
1. view the usb device. Command: lsusb
The result is as follows:
Lee @ asus:/usr/local/adt/adt-bundle-linux-x86_64-20130717/sdk/platform-tools $ lsusb
Bus 001 Device 002: ID 8087: 0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087: 0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b: 0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b: 0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b: 0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b: 0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 0cf3: 3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 001 Device 004: ID 1bcf: 2883 Sunplus Innovation Technology Inc.
Bus 002 Device 003: ID 17ef: 6019 Lenovo
Bus 002 Device 007: ID 2717: 9039
The last 2717: 9309 is that Xiaomi 9309 is vendorId, and is productId.
2. Create the 70-Android.rules file under/etc/udev/rules. d/and run sudo gedit/etc/udev/rules. d/70-android.rules.
Add:
SUBSYSTEM = "usb", ATTR {idVendor} = "2717", ATTRS {idProduct} = "9309", MODE = "0666"
Note: The 70-android.rules file name seems to be randomly named, such as 51-android.rules and 52-android.rules. Note that all punctuation marks are in English.
3. add permissions to 70-android.rules. Command: sudo chmod a + rx/etc/udev/rules. d/70-android.rules
4. restart the udev service. Command: sudo service udev restart
5./adb kill-server, and then./adb devices, there is still no device.
6. Command: echo "0x2717"> ~ /. Android/adb_usb.ini. I don't know what it does.
7. The mobile phone is disconnected and reconnected.
8 ../adb kill-server, and then./adb devices,
OK
It's just a success, but you still need to check the truth.
Recommended reading:
The New Development Board adb under Ubuntu cannot identify and solve the problem