Home / Questions / 2398
Accepted
Angel Angel
Asked: 2020-01-12 13:22:26 +0800 CST 2020-01-12 13:22:26 +0800 CST

connect android via usb adb devices various errors (xxxxxxxxxx no permissions) OS type UNIX

  • 772

Trying to connect an android device I am having errors of the type:

command shell:

./adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

command shell:

./adb devices
List of devices attached
xxxxxxxxxxxx    no permissions
android

2 Answers

  1. Best Answer

    If you have never been able to use it before, you adbcan try to configure it in the way shown below, if, on the contrary, it is a specific error, you can go to the end of the answer, and try one of the solutions that are mentioned:

    -1. We create the following file as root.

    touch /etc/udev/rules.d/51-android.rules

    -two.

    chmod a+r /etc/udev/rules.d/51-android.rules

    -3. Now with the created file we open it with an editor so that we can edit in it to add some lines with the following format:

    #x-x-x-x-x-x
SUBSYSTEM=="usb", ATTR{idVendor}=="xxxx", MODE="0666", GROUP="plugdev"

    We ATTR{idVendor}==”xxxx”will change the “xxxx”for the code that corresponds to our device, at this point you can obtain it in two ways.

    The first one I consider faster using the lsusb command, if you do not have it you can download it, but it is not necessary, if you choose not to download it you can do it the second way below.

    first way.

    We launch lsusbin the Shell and we will get something similar to the following:

    lsusb
//..
Bus 001 Device 006: ID xxxx:xxxx ............................... 
Bus 001 Device 008: ID 12d1:1038 Huawei Technologies Co.........
Bus 001 Device 007: ID 0333:0330 ...........................
//..

    We look for the line where it shows us the device that we are going to add, if it is not so clear, we connect and disconnect using lsusbeach other, to see which one it is.

    We take the first number after the ID in this case it is 12d1. And it is the one that we apply to the format that we write in the file.

    file -> /etc/udev/rules.d/51-android.rules

    #Huawei
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666", GROUP="plugdev"

    Second Way.

    You look for the manufacturer's brand in the following list, copy it or write it to the /etc/udev/rules.d/51-android.rules file.

    #Acer
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0664", GROUP="plugdev"
#ASUS
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0664", GROUP="plugdev"
#Dell
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0664", GROUP="plugdev"
#Foxconn
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0664", GROUP="plugdev"
#Fujitsu & Fujitsu Toshiba
SUBSYSTEM=="usb", ATTR{idVendor}=="04c5", MODE="0664", GROUP="plugdev"
#Garmin-Asus
SUBSYSTEM=="usb", ATTR{idVendor}=="091e", MODE="0664", GROUP="plugdev"
#Google
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", GROUP="plugdev"
#Haier
SUBSYSTEM=="usb", ATTR{idVendor}=="201e", MODE="0664", GROUP="plugdev"
#Hisense
SUBSYSTEM=="usb", ATTR{idVendor}=="109b", MODE="0664", GROUP="plugdev"
#HTC
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0664", GROUP="plugdev"
#Huawei
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0664", GROUP="plugdev"
#K-Touch
SUBSYSTEM=="usb", ATTR{idVendor}=="24e3", MODE="0664", GROUP="plugdev"
#KT Tech
SUBSYSTEM=="usb", ATTR{idVendor}=="2116", MODE="0664", GROUP="plugdev"
#Kyocera
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0664", GROUP="plugdev"
#Lenovo
SUBSYSTEM=="usb", ATTR{idVendor}=="17ef", MODE="0664", GROUP="plugdev"
#LG
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0664", GROUP="plugdev"
#Motorola
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0664", GROUP="plugdev"
#MTK
SUBSYSTEM=="usb", ATTR{idVendor}=="0e8d", MODE="0664", GROUP="plugdev"
#NEC
SUBSYSTEM=="usb", ATTR{idVendor}=="0409", MODE="0664", GROUP="plugdev"
#Nook
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0664", GROUP="plugdev"
#Nvidia
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0664", GROUP="plugdev"
#OTGV
SUBSYSTEM=="usb", ATTR{idVendor}=="2257", MODE="0664", GROUP="plugdev"
#Pantech
SUBSYSTEM=="usb", ATTR{idVendor}=="10a9", MODE="0664", GROUP="plugdev"
#Pegatron
SUBSYSTEM=="usb", ATTR{idVendor}=="1d4d", MODE="0664", GROUP="plugdev"
#Philips
SUBSYSTEM=="usb", ATTR{idVendor}=="0471", MODE="0664", GROUP="plugdev"
#PMC-Sierra
SUBSYSTEM=="usb", ATTR{idVendor}=="04da", MODE="0664", GROUP="plugdev"
#Qualcomm
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0664", GROUP="plugdev"
#SK Telesys
SUBSYSTEM=="usb", ATTR{idVendor}=="1f53", MODE="0664", GROUP="plugdev"
#Samsung
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0664", GROUP="plugdev"
#Sharp
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0664", GROUP="plugdev"
#Sony
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", MODE="0664", GROUP="plugdev"
#Sony Ericsson
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0664", GROUP="plugdev"
#Teleepoch
SUBSYSTEM=="usb", ATTR{idVendor}=="2340", MODE="0664", GROUP="plugdev"
#Toshiba
SUBSYSTEM=="usb", ATTR{idVendor}=="0930", MODE="0664", GROUP="plugdev"
#ZTE
SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", MODE="0664", GROUP="plugdev"
#ZUK
SUBSYSTEM=="usb", ATTR{idVendor}=="2b4c", MODE="0664", GROUP="plugdev"

    /etc/udev/rules.d/51-android.rules file for a device Huaweiwould be the following.

    #Huawei
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0664", GROUP="plugdev"

    -4. We verify that your user (normal not as root) is within the group plugdevwith the command groupsif it is not found we add it.

    -5. Now we go to the directory where we have the Home/Android/Sdk/toolsand we create the file adb_usb.ini, we do this as a normal user and we write the following inside it:

    0x12d1

    and we save, the number 12d1corresponds to the same one that we used previously, if it were another, it would be 0x????.If we introduce or have several devices, one will be added per line in the same file.

    -6. In this directory Home/Android/Sdk/toolswe execute the following:

    ./android update adb

    -7. Now with superUser permissions:

    @:/home//Android/Sdk/platform-tools# ./adb kill-server
@:/home/Android/Sdk/platform-tools# ./adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
@:/home/Android/Sdk/platform-tools# ./adb devices
List of devices attached
3xxxxxxxxxx device

    sources -> http://developer.android.com/tools/device.html

    If you already had it configured, you can try the following:

    sudo service udev restart

    Now with superUser permissions:

    @:/home//Android/Sdk/platform-tools# ./adb kill-server
@:/home/Android/Sdk/platform-tools# ./adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
@:/home/Android/Sdk/platform-tools# ./adb devices
List of devices attached
3xxxxxxxxxx device
    • 5

  2. If you need it to work fast go to the folder where adb is located and stop it:

    ./adb kill-server

    Then you start it again but with superuser permissions:

    sudo ./adb start-server

    When checking the connected devices it should work fine

    • 0