Fix for ADB in Ubuntu 9.10 (32bit)

Discussion in 'Android Hacks and Help' started by Linux_Fan, Dec 27, 2009.

  1. Linux_Fan
    Offline

    Linux_Fan New Member

    Joined:
    Dec 27, 2009
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    I figured I would post this fix just in case anyone was having problems w/ adb in Ubuntu like I was having. I am no Linux Guru, if there is a better way of fixing this problem let me know :)

    After Rooting the phone and installing Android SDK, when trying to run adb I would get this:

    $ adb devices
    List of devices attached
    ???????????? no permissions

    I fixed this by:

    Code:
    sudo gedit /etc/udev/rules.d/10-motorola-droid.rules
    In the blank area copy and paste this, inserting your user name in place of <insert user name>:
    Code:
    SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct} =="41db", MODE="0600", OWNER="<insert username>"
    Save and Exit.

    Restart the udev by:
    Code:
    sudo service udev restart
    Restart adb:
    Code:
    adb kill-server
    adb start-server
    
    You should see the message:
    * daemon not running. starting it now *
    * daemon started successfully *

    Now when you adb devices your phone should show.
     
    Last edited: Dec 28, 2009
  2. tdawg5480
    Offline

    tdawg5480 Member

    Joined:
    Nov 25, 2009
    Messages:
    370
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    CT
    Ratings:
    +0
    I did a command off top of my head i think it was adb start-server I believe or something similar
     
  3. Berzerker
    Offline

    Berzerker Member

    Joined:
    Dec 22, 2009
    Messages:
    331
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    It's more secure to make a 10-motorola-droid.rules file instead of a general android rules file. and to put
    Code:
    SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct} =="41db", MODE="0600", OWNER="<insert username>"
    as the line.

    And the command is "sudo service udev restart"
     
  4. Linux_Fan
    Offline

    Linux_Fan New Member

    Joined:
    Dec 27, 2009
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    My love for you is like a truck, BERZERKER!!!

    I tested your code and worked perfect.. I am editing my original post. Thanks
     
  5. Berzerker
    Offline

    Berzerker Member

    Joined:
    Dec 22, 2009
    Messages:
    331
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    I love that movie.

    Don't forget "adb kill-server" and "adb start-server"
     
  6. Linux_Fan
    Offline

    Linux_Fan New Member

    Joined:
    Dec 27, 2009
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Yeah.. the movie was awesome. I actually live about 30min north from where the Quick Stop was located in Leonardo, NJ. Thanks again for the help with ubuntu.
     
  7. mammlouk
    Offline

    mammlouk Member

    Joined:
    Dec 13, 2009
    Messages:
    316
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    I had forgotten that I made udev rules when I setup adb and proxoid to tether. I used a guide that was halfway ported from the g1. ;)

    I am creating tutorials for my site droidboots.com and being a linux user I am starting with linux tutorials first! Basically I am going to start the tutorials from zero and work through getting your phone recognized (udev on Linux, drivers on Windows), installing the Android SDK, and then pushing a boot animation to your Droid.

    Since I don't remember the link for where I got my infor originally and your post is so concise I would like your permission to use it for creating my tutorial. Let me know what you think.
     
  8. Linux_Fan
    Offline

    Linux_Fan New Member

    Joined:
    Dec 27, 2009
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Glad the tutorial helped! You can use it, if you want.
     
  9. mammlouk
    Offline

    mammlouk Member

    Joined:
    Dec 13, 2009
    Messages:
    316
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    Great, I've built a tutorial with screenshots and everything. After I get it into a nice looking PDF I will post both the tutorial and a downloadable file on my site.
     
  10. SoCalMiles
    Offline

    SoCalMiles Member

    Joined:
    Jan 10, 2010
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    Having trouble still.. I followed the directions verbatim...Tried it 3 times. Still getting:
    $ adb devices
    List of devices attached
    ???????????? no permissions
     
  11. SoCalMiles
    Offline

    SoCalMiles Member

    Joined:
    Jan 10, 2010
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    yeah i don't know what I'm doing wrong
     
  12. Linux_Fan
    Offline

    Linux_Fan New Member

    Joined:
    Dec 27, 2009
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    make sure the in the info you cut and paste you insert your user name. like "SoCalMiles", without the <>.
     
  13. SoCalMiles
    Offline

    SoCalMiles Member

    Joined:
    Jan 10, 2010
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    Thanks that's exactly what I needed to do. You are the man. Just switched from Windows to Linux and that was the last thing I needed working...you're the best.
     
  14. 16670
    Offline

    16670 New Member

    Joined:
    Feb 10, 2010
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    One thing to note, after you
    Code:
    sudo restart udev
    , you need to make sure you unplug and plug in THEN try
    Code:
    adb devices
    then this should show up. I t seems very simple, however it is easy to look over....i did :icon_eek:

    You can try a
    Code:
    lsusb
    and then you should see Motorola PCS or something like that. The first half of the ID is the vendor ID, and the second half is the device ID respectively.

    Thank you btw Linux_Fan, try his way first then if that doesn't work try this:

    Code:
    sudo gedit /etc/udev/rules.d/99-android.rules
    
    then once the window opens input this

    Code:
    SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", SYMLINK+="android_adb", MODE="0666"
    ctrl+s then ctrl+q
    restart udev, unplug and plug-in the device, and it should now show up, ensure USB debugging is enabled on your DROID!.

    Hope that helps, it did for me! :icon_ banana:
     
  15. radsaq
    Offline

    radsaq Member

    Joined:
    Nov 17, 2009
    Messages:
    60
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    Better yet is something like MODE="660" and GROUP="plugdev" or one of the other groups that debian/ubuntu use for access to various kinds of devices.
     
Search tags for this page

adb ubuntu 9.10

,
install adb on ubuntu 9.10
,
no permissions adb motorola droid