ADB shell device not found resolves

Source: Internet
Author: User

After connecting the device under Ubuntu12.04, it is shown:device not found, the workaround is as follows:

Try it first:

ADB kill-server

ADB start-server

ADB shell

If you can't, follow the steps below.

1) First enter the user directory

CD ~

Ls-al

You can see a/.android directory.

CD. Android

There should be a Adb_usb.ini file that is not created.

Touch Adb_usb.ini

2) Use LSUSB to see the vid of the connected device.

Connect the device first, run

[Email protected]:~/.android$ Lsusb
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 002:id 8087:0024 Intel Corp Integrated rate Matching Hub
Bus 002 Device 002:id 8087:0024 Intel Corp Integrated rate Matching Hub
Bus 003 Device 002:id 1234:0010
Bus 001 Device 003:id 1bcf:2883 sunplus Innovation Technology Inc.
Bus 003 Device 007:id 192f:0916 Avago Technologies, Pte.

Unplug the device and run it again

[Email protected]:~/.android$ Lsusb
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 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 003:id 1bcf:2883 sunplus Innovation Technology Inc.
Bus 003 Device 007:id 192f:0916 Avago Technologies, Pte.

Comparison found

The Bus 003 Device 002:id 1234:0010 is connected.

0x1234 is the vid, behind the 0x0010 is the PID, write down these two values.

3) Open the Adb_usb.ini file you just created

sudo gedit Adb_usb.ini

Put the following inside the gedit.

# ANDROID 3RD Party USB VENDOR ID LIST--does not EDIT.
# Use the ' Android update adb ' to GENERATE.
# 1 USB VENDOR ID PER line.
0x1234

The last line of 0x1234 is the vid of the device you just wrote down.

If you have adb_usb.ini~ this file, add it.

sudo gedit adb_usb.ini~

Note: The first time I hit the top of the Rockchip is OK, but I do not know how to do after a long time, the back must be called once RK himself compiled by the ADB can be re-use of the JDK standard ADB.

4) Run as root

sudo su

ADB shell

You should see the device connected to it.

5) Finally, if you want to connect as a normal user, you can add the owner parameter in the/etc/udev/rules.d/51-android.rules.

subsystem== "USB", attr{idvendor}== "1234", attr{idproduct}== "0010", mode= "0666", owner= "Alex"

1234 and 0010 are both vid and pid,owner fill in the username.

Save exit. Can be shipped as a normal user

ADB shell device not found resolves

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.