Note that there are some explanatory texts on larger screens.

plurals
  1. POadb devices command not working
    primarykey
    data
    text
    <p>I'm running Ubuntu 10.10 64 bit. I have ia32-libs installed along with Android Debug Bridge version 1.0.26.</p> <p>My problem(s):</p> <ol> <li><code>adb devices</code> >>> ???????????? no permissions</li> <li><code>sudo adb devices</code> >>>> sudo: adb: command not found</li> <li><code>adb shell</code> >>> error: insufficient permissions for device</li> </ol> <p>I guess these are all related. Here's the relevant info.</p> <pre><code>$ echo $PATH /home/me/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/opt/android-sdk-linux_x86/tools:/opt/android-sdk-linux_x86/platform-tools $ which adb /opt/android-sdk-linux_x86/platform-tools/adb $ adb devices * daemon not running. starting it now on port 5037 * * daemon started successfully * List of devices attached ???????????? no permissions $ sudo adb devices sudo: adb: command not found $ adb shell error: insufficient permissions for device </code></pre> <p>I get the same results with a rooted Moto Droid running CM6.1 and a rooted G-Tab running a CM7-based ROM.</p> <p>I have reviewed the following related posts:</p> <ul> <li><a href="http://forum.xda-developers.com/archive/index.php/t-522827.html" rel="nofollow noreferrer">http://forum.xda-developers.com/archive/index.php/t-522827.html</a></li> <li><a href="http://ubuntuforums.org/archive/index.php/t-1164359.html" rel="nofollow noreferrer">http://ubuntuforums.org/archive/index.php/t-1164359.html</a></li> <li><a href="https://stackoverflow.com/questions/2517493/adb-command-not-found-in-linux-environment">adb command not found in linux environment</a></li> </ul> <p>I tried most (not all) of the suggestions and I have not been able to resolve my issue. The things I didn't try seemed inappropriate. I would appreciate a few more tips and I'll keep troubleshooting.</p> <p>One thing I didn't try was editing /etc/udev/rules.d/70-android.rules. Is that likely to be the issue? I can't see how that would cause "sudo: adb: command not found". Maybe my problems are not all related. Anyway, at this point I think I need some input from other people because I don't believe I have a path problem or the other common problems discussed in those other posts.</p> <p><strong>EDIT: SOLVED</strong> thanks to EboMike and RivieraKid. This was actually two different problems:</p> <ol> <li><p>Item #2 above (sudo: adb: command not found) was solved by making a symlink as follows:</p> <pre><code>$ sudo ln -s /opt/android-sdk-linux_x86/platform-tools/adb /usr/local/sbin/adb </code></pre> <p>That allowed me to then do as EboMike suggested and use <a href="https://stackoverflow.com/questions/3127539/ubuntu-android-device-debug/3129903#3129903">this solution</a>. Doing that was required for my Moto Droid. (Running adb as sudo was <em>not</em> required for my Viewsonic G-Tablet, however.)</p></li> <li><p>My other two items were resolved by implementing the udev rule as RivieraKid suggested (from this <a href="http://developer.android.com/guide/developing/device.html" rel="nofollow noreferrer">link</a>).</p></li> </ol>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload