Timeline for adb devices command not working
Current License: CC BY-SA 2.5
13 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 23, 2017 at 10:31 | history | edited | URL Rewriter Bot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
Apr 1, 2011 at 9:00 | vote | accept | MountainX | ||
Apr 1, 2011 at 9:00 | |||||
Apr 1, 2011 at 8:59 | comment | added | MountainX | Hey EboMike and RivieraKid, I need to pick both your responses as answers. I'm not sure if I can select two answers, however. Thanks for your help! | |
Apr 1, 2011 at 8:46 | comment | added | MountainX | Strange... I could access the GTablet without running adb server as root. But I had to run adb as root to see the Moto Droid. | |
Apr 1, 2011 at 8:31 | comment | added | EboMike | Did restart the adb server as root? | |
Apr 1, 2011 at 8:29 | comment | added | MountainX | now I see the problem from my #1 all the time: $ sudo adb devices List of devices attached ???????????? no permissions | |
Apr 1, 2011 at 8:28 | comment | added | MountainX | This resolved item #2 of my original 3. $ sudo ln -s /opt/android-sdk-linux_x86/platform-tools/adb adb me@desktop:/usr/local/sbin$ ls -la lrwxrwxrwx 1 root root 45 2011-04-01 04:26 adb -> /opt/android-sdk-linux_x86/platform-tools/adb | |
Apr 1, 2011 at 8:16 | comment | added | EboMike | Specify the full path then when you run adb as root. | |
Apr 1, 2011 at 8:02 | comment | added | MountainX | Here's a strange thing. I get different results from "which adb" depending on whether I run it as root or run it with sudo. Here's output $ sudo which adb $ | |
Apr 1, 2011 at 8:00 | comment | added | MountainX | Hope you can read this. (I don't know how to format comments to include newlines.) adb IS in the path of my root user. I pasted the which adb command in my original post. The path is /opt/android-sdk-linux_x86/platform-tools/adb. $ sudo -s root@desktop:# echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin:/opt/android-sdk-linux_x86/tools:/opt/android-sdk-linux_x86/platform-tools | |
Apr 1, 2011 at 7:48 | comment | added | EboMike |
adb is not in the path of your superuser. Enter which adb to find out which path it's in, then add that to root's path.
|
|
Apr 1, 2011 at 7:37 | comment | added | MountainX |
didn't work. Details: me@desktop:/opt/android-sdk-linux_x86/platform-tools$ sudo adb kill-server sudo: adb: command not found me@desktop:/opt/android-sdk-linux_x86/platform-tools$ adb kill-server me@desktop:/opt/android-sdk-linux_x86/platform-tools$ sudo adb start-server sudo: adb: command not found
|
|
Apr 1, 2011 at 7:27 | history | answered | EboMike | CC BY-SA 2.5 |