Insufficient permissions for device in Android Studio Workspace running in openSUSE 13.2

I have a rooted Motorola Defy+ running a Cyanogenmod v11 custom ROM (nightly build) created by Quarx. Using Android Studio Workspace,(ASW) v.1.1.0, when I try and debug on this device, I get

????????????[null]

listed in the Choose Device window, with the Logcat window showing

insufficient permissions for device

I would really like to use this device and ROM for debugging purposes.

When I enter lsusb from the command line I get,

Bus 002 Device 002: ID 22b8:431d Motorola PCS

This is the correct device id for Motorola units. I have installed 51-android.rules and 71-android.rules in /etc/udev/rules.d/ with the correct Motorola ids in these files.

I've also tried Revoke USB debugging authority, from Developer Options on the device, with no luck.

I have not tried running ASW as root hoping that there might be another option; is there?

Update: I was able to get in and access ADB by

uvachem-gsmith2:/home/greg/Android/Sdk/platform-tools # ./adb

I then did a kill server, did an SU to root user and restarted the server. I then tried to connect to the device from Android Studio. Got a message on the device about accepting the RSA key from the PC, said "Yes" and then was able to deploy the app to the device. So back to my original question, Is there another way to access this device without logging in as root? It seems as if there is a permission issue on the phone file system that is preventing this...

Update #2 The core problem here was a permission thing. Even though running ADB as root will allow access to the rooted Android device, a better solution is to change permissions in the udev file for this device...resetting 664 to 666, (see answer below). This allows the PC to access the file system on the device.

I had this while using a Linux machine with a Nexus 4 running Android 5.1

The fix was to enable both 'debug over USB' and 'connect as MTP'. The opposite is true when using the same device and Android Studio and adb on OSX though - to allow Android Studio to recognise the handset, I need to disable 'connect as MTP'.

I found a simple answer that worked for me:

adb kill-server
sudo adb start-server
sudo adb devices

You will find your device then. Hope this helps.

Reference: http://itsfoss.com/fix-error-insufficient-permissions-device/

It's simple. Just change your USB mode to File Transfer mode then it works.

Android 8

MTP is no longer available. On my android 8 "Transfer Files" option did not work.

"Transfer photos PTP" Is worked, and Studio showed the device name.

• Steps on your cell phone

1. Open the developer options
2. Enable USB debugging.
3. change USB connection to PTP

• Steps on Linux

1. on console run sudo usermod -aG plugdev $LOGNAME

Android 9

With Android 9 use the option File Transfer.

Changing permissions in this line from /etc/udev/rules.d/51-android.rules,

#Motorola 
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0664", GROUP="plugdev"

to,

#Motorola 
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666", GROUP="plugdev"

resolves this issue in a manner that DOES NOT require running adb as root.

IN my phone Symphony W75, in option USB computer connection-> selecting Connect as Media device(MTP) has solved the problem.

Long to short, I had the same problem with a Prestigio PMP5570C tablet,

all you have to do is to confirm on your tablet that you want to copy data to/from your computer (what i forgot), and add the 2 lines that @portsample wrote.

You can find the idVendor of your device typing

> lsusb

in UBUNTU 12.04, then you get:

> Bus 001 Device 011: ID 2207:0010,

where 2207 is your vendor id. Summed up the question and answer...

I updated my device (Nvidia Shield) that was previously connecting fine, so I knew that the PC setup is correct already. The developer settings seem to have a new layout on Android 7.0.

It is under Settings > Preferences > Developer options > Networking > Select USB configuration

Here, I needed to select PTP and everything works fine again:

This procedure solves the problem for me:

- On the Android device, drag the top menu and select "USB for file transfer"
- Press "Run" again

• Enable USB debugging
• Use USB to transer file

Go to Developer Options -> Default USB Configurations and Change to PTP

Run these two commands in terminal

 sudo adb kill-server
 sudo adb start-server

Should Work!

I made a script for this error. For me it works fine in Fedora 28, but it should work in many Linux distributions. Just create a file with the content of the selfexpanied script. I called it usbDebbugingAndroidStudio.sh
Give him execution permission with: chmod +x usbDebbugingAndroidStudio.sh

And run it: sudo ./usbDebbugingAndroidStudio.sh

After that check the list displayed by the command lsusb and introduce the Id of your device. For example: My output was: Bus 006 Device 002: ID 05c6:9091 Qualcomm, Inc. So I type 05c6 and press enter.

The script:

#!/usr/bin/env bash


#This script configure Android Debug Bridge permissions to solve the following
#error: com.android.ddmlib.AdbCommandRejectedException: insufficient permissions for device
#This error is produced when you try to install an APK from Android Studio in your device.
#You can check the vendorId here:
#https://developer.android.com/studio/run/device#setting-up
#If your device's brand isn't listed check the info displayed by the command lsusb

lsusb
#My output was:
#Bus 006 Device 002: ID 05c6:9091 Qualcomm, Inc.
#The id for this line is 05c6
echo -n "Enter the id of your mobile device: "
read usbProviderId
cd /etc/udev/rules.d/
sudo touch 51-android.rules
(
sudo cat << _EOF_
SUBSYSTEM=="usb", ATTR{idVendor}=="$usbProviderId", MODE="0666", GROUP="plugdev"
_EOF_
) | sudo tee 51-android.rules

#Give read and write permissions to the file
sudo chmod a+r /etc/udev/rules.d/51-android.rules

#Kill the Android Debug Bridge server to restart it
cd $HOME/Android/Sdk/platform-tools
sudo ./adb kill-server

#If this still doesn't work unplug the usb cable and connect again.
#And repeat the last step Kill the ADB server.

What the F... ! :) Note : I have seen it on android 8.1 on a One+5t...

Even we do all of above, it is necessary to make something on your android device .. in addition to go in dev options menu (usb debug) (don't hesitate to reset "cancel authorization" or something like this (I am in french version ;) )

If some people meet the same problem than me, maybe it could be usefull for you too : Don't forget to authorize devices in your phone (each time of usb connect on the android device if you don't select always box). Beside, you can suppress the old authorized devices on your phone and start with proper parameter to authorize clearly your pc on your android device

When you connect the android device, a pop up or notification ask to authorize a mac address or equivalent to the device : authorize it if you want to authorize connection between your linux pc and your android device.

It is necessary to obtain autorisation on your android device when you use connect the usb cable (if you don't accept all the time but if it is the first time this box is going to appear on your devices) if you don't do it, adb devices show unauthorized even all rights are good (666, UDEV etc)

Note : thank you for your precious help. A last thing, sorry for my english

I'm facing this issue while run flutter app from android studio 4.1, i did remove usb cable and plug into second usb port and its working :),

I'm writing this if someone face same issue then they can get help.

For me and possibly many others the issue is to do with access rights to devices on the machine. Now that this is well documented in the android documentation, I think the best solution is here

On Debian based Systems you can run lsusb or dmesg to get vendor id if your vendor does not exist on the given list

I have face the same problem and i have resolved this by Adding the path of your_android_sdk_path to the environment variable like

sudo export $PATH:/your_android_sdk_path/platform-tools/adb

its your wish how you want to add this to your account or system wide by editing these file ~/.bashrc file or ~/.profile or /etc/profile, /etc/bash.bashrc, or /etc/environment if u want to add to system wide access.

and then create the link of that in bin

sudo ln -s /your_android_sdk_path/platform-tools/adb /bin/adb

if you have used adb devices or any command then first kill the server like

adb kill-server

then start the server like

adb start-server
adb devices

now you can see your devices are listed properly without an issue

As the error message said, it is a permission insufficient problem. In my experience, it only happened on my Linux machine, and works well on MacOS and Windows. Launching your Android Studio with root permission could avoid this problem.

$sudo /your_android_studio_path/bin/studio.sh

In my situation:

cd /etc/udev/rules.d/
sudo chmod a+r ./*.rules  #the name of your rules files.

Then,I can use adb without this error.

if accepted answer not worked for you then just simple follow steps: Just open your android studio terminal:-

adb kill-server

adb start-server

it worked for me.

Same issue on Fedora 32, to fix this try this:

adb kill-server
adb start-server

Without running Linux sudo apt-get install adb. Don't forget to enable USB debugging.

Ref: https://developer.android.com/studio/run/device