Database Users

How to make adb work?

I've searched a lot, but did not find a solution.
When I connect my HTC Kaiser with Android Ion 1.5 on the top to my Linux box (all UDEV settings are as recommended), the adb utility (launched as root) does not recognize it correctly. It shows a set of questionmarks instead of the device name:
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? device
adb basic commands (pull/push/install/shell) work, though, but DDMS does not work and I can't debug my application when the device is attached.
Does somebody have a solution?

You need to run the adb server as root. Use su or sudo to run these:
Code:
./adb kill-server
./adb start-server
You can then use adb and ddms as a normal user. If you use fastboot, you may find you need to run that as root as well.

it is root
Super Jamie said:
You need to run the adb server as root. Use su or sudo to run these:
Code:
./adb kill-server
./adb start-server
You can then use adb and ddms as a normal user. If you use fastboot, you may find you need to run that as root as well.
Click to expand...
Click to collapse
Like I mentioned in my question - I do run adb as root.
When it's launched not as root, I can not even do "adb shell" and
"adb devices" shows:
"????????????? Permission denied". So, it is root, I assure.
BTW, on my work Windows 2k3 machine I can use ddms, but
"adb devices" still shows some garbage letters instead of the device name.
Sorry for my English, if my explanation is not clear.

ubuntu abd

What exactly do I need to use adb in ubuntu 10.4
I cannot get anything to work and I'm not too familiar with linux.
I have the sdk downloaded and my terminal opened up to my tools directory, but I literally cannot figure out what I'm doing, no commands work and I can't even find my device (adb devices)
I have exclusively used windows for adb on my previous two phones, but I'm using ubuntu more and more so I would like to be able to use adb in it.

Easy.
cd /path/to/sdk/tools
./adb

ADB doesn't recognize my incredible in 10.4 when I do ./adb devices it is blank.

I've tried with the phone set to charge only and to disk drive.
I've tried following this:
a couple of topics concerning a rules file in /etc/udev/rules.d
I greated a 51-android.rules file and it looks like this now:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct} =="0ff9", MODE="0600", OWNER="mbambic"
I've restarted udev a few times and killed the adb server and done ./adb devices to restart it, no luck.

Do you guys have USB Debugging enabled?
Applications -> Development -> USB Debugging. MUST be checked.

x.v_ said:
Do you guys have USB Debugging enabled?
Applications -> Development -> USB Debugging. MUST be checked.
Click to expand...
Click to collapse
yes, I've used adb numerous times on windows

http://developer.android.com/guide/developing/device.html
I'm no expert, but this is what I followed and my phone shows up in adb devices.

OK, that was my bad with debugging not on.
Now I'm getting the following:
#./adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? no permissions
I've tried with and without the rules file I created in /etc/udev/rules.d called 51-android.ruleswith the following entries that has been chmod a+rx
version 1
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
or version 2
UBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct} =="0c9e", MODE="0600", OWNER="myusername"
or version 3
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666"
based on this info:
$ lsusb
Bus 001 Device 022: ID 0bb4:0c9e High Tech Computer Corp.

Got it:
edited the rules file:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", SYMLINK+="android_adb", ATTRS{idProduct} =="0c9e", MODE="0666"
Rebooted phone
Turned on disk drive
restarted udev
killed adb and started again

I keep getting no command 'adb' found when I try to type any command

I keep getting no command 'adb' found when I try to type any command
Click to expand...
Click to collapse
Assuming you downloaded the sdk pack, your problem is that adb isn't in your path. Take a look at h t t p://developer.android.com/sdk/installing.html. To just temporarily add it, at the shell prompt enter:
Code:
export PATH=${PATH}:<your_sdk_dir>/tools
Also, you may have permission problems when running adb. The easiest way around this is to run adb as root, i.e.: sudo adb (but you'll also have to add adb to root's path then).

mtxpert said:
Got it:
edited the rules file:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", SYMLINK+="android_adb", ATTRS{idProduct} =="0c9e", MODE="0666"
Rebooted phone
Turned on disk drive
restarted udev
killed adb and started again
Click to expand...
Click to collapse
Ok, so you used both lines in your 51-android.rules file? Interesting, so you're making the driver specific to the DI? I've been operating with just the first line, which allows to use the DI and the G1, but then again, I've also been unsuccessful at rooting
br125 said:
I keep getting no command 'adb' found when I try to type any command
Click to expand...
Click to collapse
In Linux Mint 9 x64 Isadora (much the same as Ubuntu 10.04 Lucid Lynx), I added the path command to my bashrc file in ~/user. Not sure how to make it global (prob would go somewhere in the mysterious&powerful /etc), but I'm the only user on my system, so for my purposes that doesn't matter

[Q] ADB troubles on Kubuntu Natty

If this is the wrong forum, please feel free to move my post. I figured the devs here might be the best source of information to start with.
My laptop is running Kubuntu 11.04 and fully updated. I've followed all the various (and somewhat inconsistent) posts on the web about getting ADB to run on USB connections under Linux. I am successful getting ADB to see my G2 phone, but not my Nook Color.
Here's my /etc/udev/rules.d/51-android.rules:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
The permissions are set correctly, at 644. I've tried both ATTR and ATTRS; it doesn't seem to matter which.
Some, but not all, posts about getting ADB to work also indicated the requirement of another file, .android/adb_usb.ini. The presence or absence of this file seems to have no effect. Regardles, here's mine:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0bb4
2080
No matter what I attempt (even including reboots, thinking that restarting udev wasn't sufficient), ADB sees only my G2 and never my Nook:
Code:
List of devices attached
SH0C7R200734 device
Despite the fact that my Nook otherwise works fine on my Kubuntu box; lsusb sees it:
Code:
Bus 001 Device 008: ID 2080:0002
And I can mount its drives and Calibre is also very happy with it.
I'm running ManualNooter 4.6.16 with Dalingrin's 063011 Froyo EMMC kernel. In Nook Color Tools, USB debugging is enabled and auto mount is disabled.
I'm stuck at what to try next. Any thoughts?

[Q] Rooting my T-Mobile G2 with Ubuntu

First of all, I have the T-Mobile G2 with the Gingerbread OTA update. I am running Ubuntu 11.10 on a netbook. I have tried to follow the instructions for rooting my phone, but I am getting stuck trying to install the Google USB driver in the SDK manager. Any suggestions on how to get past this roadblock?

mrfilbert said:
First of all, I have the T-Mobile G2 with the Gingerbread OTA update. I am running Ubuntu 11.10 on a netbook. I have tried to follow the instructions for rooting my phone, but I am getting stuck trying to install the Google USB driver in the SDK manager. Any suggestions on how to get past this roadblock?
Click to expand...
Click to collapse
no need for usb drivers in linux
you have to be sure that you are su on your pc... (i have fedora)
i think ubunto it´s sudo, isn´t it?
and before you can see your device through adb you have to type "./adb kill-server" and then "./adb start-server"
... then "./adb devices" and so on

Thanks. I tried ./adb devices and it gave me the following:
List of devices attached
???????????? no permissions
???????????? no permissions
Since I do not see a serial number, do I need to re-install something?

mrfilbert said:
Thanks. I tried ./adb devices and it gave me the following:
List of devices attached
???????????? no permissions
???????????? no permissions
Since I do not see a serial number, do I need to re-install something?
Click to expand...
Click to collapse
no that happens because you are not root on your pc...
in fedora i have to do the following to see my device:
su (enter)
then enter password
i get this symbol: # = means i´m root on my pc
then i go to my platform-tools directory (cd whatever)
./adb kill-server
./adb start-server
./adb devices ...now you should see your device
then start the rooting procedure, good luck

Use 'sudo su' in ubuntu to get a root prompt.
otherwise you have to set a 51-android.rules file (instructions here http://developer.android.com/guide/developing/device.html)
-Nipqer

VS980 Linux "no permissions" issue

For the life of me, I cant get my G2 (VZW) vs980, to connect via ADB in Linux Mint 16.
I tried adding both of these entries in 51-android.rules
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004:6246", MODE="0666" #LG G2
SUBSYSTEM=="usb", SYSFS{idVendor}=="0604", MODE="0666" #LG G2 attempt 2
But I still end up with this:
Code:
[B][COLOR=SeaGreen][email protected] ~ $[/COLOR][/B] lsusb
Bus 002 Device 004: ID 5986:0148 Acer, Inc
Bus 002 Device 006: ID 1004:6246 LG Electronics, Inc.
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[B][COLOR=SeaGreen][email protected] ~ $[/COLOR][/B] adb devices
List of devices attached
???????????? no permissions
[B][COLOR=SeaGreen][email protected] ~ $[/COLOR][/B]
Anyone else have this problem? Ive done about 3 days of searching for a post that would help, or anything else that would help me fix it, but nada!

I've had this problem with adb in the past on Linux Mint. The solution I found was to start the adb server as root:
Code:
adb kill-server
sudo adb start-server
Once the server is started, you should be able to run everything as a normal user. If this works, you might be able to write an init.d script to start the server at boot if you don't want to have to run it as root whenever you need to connect to your phone. I'm on Arch Linux now, and have a systemd service enabled at boot to do just that.
Hope this helps!

flutterguy317 said:
I've had this problem with adb in the past on Linux Mint. The solution I found was to start the adb server as root:
Code:
adb kill-server
sudo adb start-server
Once the server is started, you should be able to run everything as a normal user. If this works, you might be able to write an init.d script to start the server at boot if you don't want to have to run it as root whenever you need to connect to your phone. I'm on Arch Linux now, and have a systemd service enabled at boot to do just that.
Hope this helps!
Click to expand...
Click to collapse
I cant seem to get the second command to go. It doesnt recognize "adb" as a command if I precede it with "sudo". I cant start a root terminal either, and then do "adb start-server". Strange

chevycam94 said:
I cant seem to get the second command to go. It doesnt recognize "adb" as a command if I precede it with "sudo". I cant start a root terminal either, and then do "adb start-server". Strange
Click to expand...
Click to collapse
Hmm, that's strange. I'm assuming that adb is in your user's PATH since you can run it as a normal user, but it might not be in the root user's PATH. You can check to see if the directory which contains adb is in the root PATH using:
Code:
sudo printenv PATH
If it isn't, it might be worth a shot to try to run it with sudo using the absolute path... Should be something like:
Code:
sudo /opt/android-sdk-linux/platform-tools/adb start-server
Of course, the actual path will change depending on where adb is located.

flutterguy317 said:
Hmm, that's strange. I'm assuming that adb is in your user's PATH since you can run it as a normal user, but it might not be in the root user's PATH. You can check to see if the directory which contains adb is in the root PATH using:
Code:
sudo printenv PATH
If it isn't, it might be worth a shot to try to run it with sudo using the absolute path... Should be something like:
Code:
sudo /opt/android-sdk-linux/platform-tools/adb start-server
Of course, the actual path will change depending on where adb is located.
Click to expand...
Click to collapse
Even trying to specify an absolute path results in it saying it cant find that command (adb). Thats stupid. sudo should just give elevated privileges, but it keeps the following command from ever functioning.....Grrrrrr

chevycam94 said:
Even trying to specify an absolute path results in it saying it cant find that command (adb). Thats stupid. sudo should just give elevated privileges, but it keeps the following command from ever functioning.....Grrrrrr
Click to expand...
Click to collapse
Huh, that's very strange... If you cd to the directory where adb is, can you run it there? Theoretically, this should work:
Code:
cd /path/to/adb
sudo ./adb start-server
Since you're acting as superuser, there shouldn't be any permission issues when accessing adb... Maybe try copying adb to your home directory and run it there?

flutterguy317 said:
Huh, that's very strange... If you cd to the directory where adb is, can you run it there? Theoretically, this should work:
Code:
cd /path/to/adb
sudo ./adb start-server
Since you're acting as superuser, there shouldn't be any permission issues when accessing adb... Maybe try copying adb to your home directory and run it there?
Click to expand...
Click to collapse
Thank you! That seems to have done it. Now, I just need to automate it somehow.

chevycam94 said:
Thank you! That seems to have done it. Now, I just need to automate it somehow.
Click to expand...
Click to collapse
Glad you got it to work! I would imagine you could just stick those commands into a shell script or create an init.d script that runs at boot to automate it.

chevycam94 said:
Thank you! That seems to have done it. Now, I just need to automate it somehow.
Click to expand...
Click to collapse
maybe you two linux guys can help me, Im running Ubuntu 14.04 on my laptop device is showing connected but no adb or fastboot (bricked atm)
[email protected]:/home/mesi# lsusb
Bus 001 Device 006: ID 2232:1029
Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 037: ID 1004:6246 LG Electronics, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 006: ID 046d:c248 Logitech, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:/home/mesi# adb devices
List of devices attached
[email protected]:/home/mesi# adb devices
List of devices attached
07a100c3 device
showing device in list but not with abd. second attempt is with nexus7 as 07a100c3. (only connecting one device at a time)
Ive been running ubuntu for about 4 years now and havent gone back to win except to fix parents computers. lol knida new to these forums so forgive me while Im still learning proper etiquette. Ive posted a question in the help and troubleshooting @ http://forum.xda-developers.com/showthread.php?t=2762672 without any responses yet. I would be much obliged if you could at least point in the right direction. (hopefully not to the log-out screen) again, thanks.