Happening Now (10PM - 11:30PM ET): AMA With Honor Product Manager. Ask a question, win one of 3 Honor View 10s.
FORUMS
Remove All Ads from XDA

[Q] adb devices returns '??????????????? no permissions'

17 posts
Thanks Meter: 4
 
By JAMCx, Junior Member on 7th August 2014, 02:29 PM
Post Reply Email Thread
This is just with Linux Mint- works in OS X.
adb in Mint works with Nexus 4 and One X every time but the OPO won't show up at all whether stock OS or Mahdi.
Any way to fix?
 
 
7th August 2014, 03:40 PM |#2  
DuckMcQUack's Avatar
Senior Member
Flag Rome
Thanks Meter: 103
 
More
Quote:
Originally Posted by JAMCx

This is just with Linux Mint- works in OS X.
adb in Mint works with Nexus 4 and One X every time but the OPO won't show up at all whether stock OS or Mahdi.
Any way to fix?

Did u allow your pc from the phone when connecting it to adb? O_o
7th August 2014, 05:29 PM |#3  
bud77's Avatar
Senior Member
Flag Near Paris
Thanks Meter: 486
 
Donate to Me
More
Quote:
Originally Posted by JAMCx

This is just with Linux Mint- works in OS X.
adb in Mint works with Nexus 4 and One X every time but the OPO won't show up at all whether stock OS or Mahdi.
Any way to fix?

Just "sudo adb devices"

Happens to me on my ubuntu build VM too
7th August 2014, 05:42 PM |#4  
OP Junior Member
Thanks Meter: 4
 
More
Quote:
Originally Posted by bud77

Just "sudo adb devices"

Happens to me on my ubuntu build VM too

Didn't work. The OTO does not show up in Mint as a connected device for some reason while the Nexus 4 and One X do and they respond to adb devices.
The OTO says connected as media device, android debugging enabled. Again it does connect and respond in OS X.
7th August 2014, 05:48 PM |#5  
bud77's Avatar
Senior Member
Flag Near Paris
Thanks Meter: 486
 
Donate to Me
More
Quote:
Originally Posted by JAMCx

Didn't work. The OTO does not show up in Mint as a connected device for some reason while the Nexus 4 and One X do and they respond to adb devices.
The OTO says connected as media device, android debugging enabled. Again it does connect and respond in OS X.

Did yo follow these steps already ?

Quote:

If you're developing on Ubuntu Linux, you need to add a udev rules file that contains a USB configuration for each type of device you want to use for development. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. For a list of vendor IDs, see USB Vendor IDs, below. To set up device detection on Ubuntu Linux:

Log in as root and create this file: /etc/udev/rules.d/51-android.rules.

Use this format to add each vendor to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"

In this example, the vendor ID is for HTC. The MODE assignment specifies read/write permissions, and GROUP defines which Unix group owns the device node.

Note: The rule syntax may vary slightly depending on your environment. Consult the udev documentation for your system as needed. For an overview of rule syntax, see this guide to writing udev rules.
Now execute:
chmod a+r /etc/udev/rules.d/51-android.rules

(From here)
7th August 2014, 07:53 PM |#6  
OP Junior Member
Thanks Meter: 4
 
More
Quote:
Originally Posted by bud77

Did yo follow these steps already ?



(From here)

Above my pay grade ... I'll just plug it in the Mac
Thanks though.

Just plugged it into a W7 Pro machine and it saw it as a portable device and let me browse the folders without any tweaking.
15th October 2014, 06:25 PM |#7  
Senior Member
Thanks Meter: 116
 
More
Wink
Quote:
Originally Posted by JAMCx

Above my pay grade ... I'll just plug it in the Mac
Thanks though.

Just plugged it into a W7 Pro machine and it saw it as a portable device and let me browse the folders without any tweaking.

Just had the same problem and solved it by creating the file above.

Create the file
sudo vim /etc/udev/rules.d/51-android.rules

add the line below:
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666", GROUP="plugdev"

and reload the the new rules by using this command (or reboot ):
sudo udevadm control --reload

unplug the device and plug it back in and now "sudo adb devices" should show the correct name and status.
The Following User Says Thank You to hugoprh For This Useful Post: [ View ] Gift hugoprh Ad-Free
18th October 2014, 04:43 PM |#8  
zaphodbeeb's Avatar
Senior Member
Betelgeuse
Thanks Meter: 490
 
Donate to Me
More
Do sudo bash, then password, the adb and fastboot work fine for me. If using windows cmd, run as admin.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread