Database Users

adb device not found ubuntu 10.10

I am fairly new to linux so I could be missing something simple but when I type adb devices i get a blank reply. It doesn't say "no devices" or anything, it just doesn't show anything. But if I run adbwireless from my phone, i can run adb connect ip adress :5555 and connect just fine. I have also noticed that the only time ubuntu will see my phone at all is if usb debugging is off. I'm not sure if those two are related or not. any suggestions?

4nic8 said:
I am fairly new to linux so I could be missing something simple but when I type adb devices i get a blank reply. It doesn't say "no devices" or anything, it just doesn't show anything. But if I run adbwireless from my phone, i can run adb connect ip adress :5555 and connect just fine. I have also noticed that the only time ubuntu will see my phone at all is if usb debugging is off. I'm not sure if those two are related or not. any suggestions?
Click to expand...
Click to collapse
WORKS FOR EPIC 4G!!!!!
This worked for my BH2 but it may need some tweaking on the rules file to make it work, but I will double check it when I get home.
After downloading the SDK, I moved the adb to the (in my pc is like this) ~/android/tools/ folder and ran the chmod a+rwx adb command.
After this, I took the rules file (attached) and I moved it to the /etc/udev/rules.d/ folder (logged as root). After doing this, I ran the following commands:
su [then placed the password]
chmod a+x 51-android.rules
chown root:root 51-android.rules
Once done, I restarted the PC and its working 100%, I ran the lsusb command to confirm the connection of the device and then a ./adb devices an I got positive return!
Note: Attachment updated!

Thank you for the suggestion. I ran the commands as you said, using the 51-android.rules that i already had and i still get a blank response when running
Adb devices.
However, since running those commands, its mounting my sd on the desktop with or without usb ebugging. So the commands you provided did fix something, just not adb!
Sent from my SPH-D700 using XDA App

4nic8 said:
Thank you for the suggestion. I ran the commands as you said, using the 51-android.rules that i already had and i still get a blank response when running
Adb devices.
However, since running those commands, its mounting my sd on the desktop with or without usb ebugging. So the commands you provided did fix something, just not adb!
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I will tune the Rules file and test and let you know. Most of the time, when it doesn't work, its the rules file who has the problem.

4nic8 said:
Thank you for the suggestion. I ran the commands as you said, using the 51-android.rules that i already had and i still get a blank response when running
Adb devices.
However, since running those commands, its mounting my sd on the desktop with or without usb ebugging. So the commands you provided did fix something, just not adb!
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
FIXED!!!! download this file and it will work 100%!
Also, please follow my instructions above in the same order.

megabiteg said:
FIXED!!!! download this file and it will work 100%!
Also, please follow my instructions above in the same order.
Click to expand...
Click to collapse
thank you for the suggestion dude, but i think that actually took me back a step, now my sd wont mount anymore. i had a 51-android.rules file already and i deleted it. maybe i will just have to still with adbwireless =(

4nic8 said:
thank you for the suggestion dude, but i think that actually took me back a step, now my sd wont mount anymore. i had a 51-android.rules file already and i deleted it. maybe i will just have to still with adbwireless =(
Click to expand...
Click to collapse
mmmm..
I've tested this with several other friends that use Ubuntu 10.10 and it works fine for them. Are you following step by step on my OP?
Also are you on a desktop or laptop? Please note that while you have USB Debugging on the option to mount your SD card will not be prompted.
If your using a Desktop, please refrain of using front side USB ports. If you need additional help, let me know, I'll be glad to help you getting it working.
send me what the lsusb command dumps if you can, that can help me tweak the rules file for you.

Thanks! after some trial and error..the zip file in the first post worked for me!
FYI, you can just run this command instead of restarting your computer:
Code:
sudo udevadm control –reload-rules; sudo reload udev; adb kill-server; adb devices

Same problem
Hello, I have the same problem, adb don't detect my tablet. I do it from my laptop and this is the lsusb exit:
[email protected]:~$ lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 007: ID 18d1:0001 Google Inc.
Bus 001 Device 002: ID 174f:a311 Syntek 1.3MPixel Web Cam - Asus A3A, A6J, A6K, A6M, A6R, A6T, A6V, A7T, A7sv, A7U
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$
Click to expand...
Click to collapse
Is it possible that the integrated webcam generates the conflict? how can I disable it on Ubuntu 10.10?
Thanks

One thing I've noticed is that my phone will come right up (with debugging turned on) on certain usb ports but won't on others. Might be worth trying different USB ports just to see if it makes a difference.
Was this way on both my desktop and my netbook (both running Ubuntu 10.10).

Thanks flatspin, I have tried all my 4 usb ports without luck.

Solved, I forgot to put the tablet on adb mode at boot time.

[Q] Hauwei Ascend M860 Why do you hate me?

Ok,
So Ive been scouring the net to find out if there is anyway I can get my device to be recognized. So far I've tried:
Windows 7 Ultimate 64bit, phone goes into storage mode and loads the drivers. although the drivers are not signed so windows refuses to load them, nice microsoft.
Ubuntu 10.04 64bit, ok i've installed usb_modeswitch and setup a bunch of udev rules (attached) and I can get the device to be detected but not recognized ie if I execute
Code:
adb devices
I get
Code:
List of devices attached
???????????? device
if I try
Code:
adb shell
I get dropped right into the user shell on the device. *Nice* score one for linux, but this doesn't do me much good because if I try to bring up the dalvik monitor it refuses to recognize the device grrr bad linux
I've attached my udev rules and a listing from when I tried to start the dalvik monitor, if anybody has some idea how I can get either windows to load the provided drivers or ubuntu to recognize the device I would be eternally greatfull
Thanks
Tired and wear from trudging around the net all day
Ben

Mounting the Xoom in Linux (as well as adb)

The xoom can mount just fine on Linux but it is an MTP not a Mass Storage device.
Disclaimer: I am not responsible for any damage to your device, computer, relationship, etc.... The following is meant as a guideline and worked for me but as always use your head.
I did this on my Kubuntu Maverick laptop, but it should apply to most *buntus plus debian. Other flavors should be similar, post a request and I will help if I can. I am familiar with Suse and RHEL/Centos as well but beyond those it will be guess work.
The first thing I would recommend doing is making the device read/write to normal users.
Code:
sudo touch /etc/udev/rules.d/51-android.rules
echo "SUBSYSTEM==\"usb\", SYSFS{idVendor}==\"22b8\", MODE=\"0666\"" |sudo tee -a /etc/udev/rules.d/51-android.rules
sudo /etc/init.d/udev restart
NOTE: This also "fixes" adb so it is useable with the xoom as a normal user. If that is all you want you can stop here.
NOTE 2: You could also set an OWNER rather than changing MODE but I chose the most common route for this example/
Now install either mtp-tools or mtpfs for mounting using FUSE. Since I went the fuse route that is what I will conver here. (I installed the mtp-tools package but beyond using it to debug getting mtpfs to work I have never used it before.)
Assuming you already have fuse configured, for (k|x)ubuntu or debian :
Code:
sudo apt-get install mtpfs
If you do not have fuse already configured then do that first. Look it up online if you have any questions. If you get stuck I will try and help but this post is not about how to configure FUSE.
After that it is simple. Plugin your xoom and from the command line type:
Code:
mtpfs mountpoint
and to dismount it
Code:
fusermount -u mountpoint
so in my case I mount it in a subdirectory under home called xoom
Code:
mtpfs /home/janetpanic/xoom
fusermount -u /home/janetpanic/xoom
I have confirmed moving files to and from the actual directories but not from the meta "playlists" directory. I hope that helps...
EDIT: Fixed Typo... had "(idVendor)" instead of the correct "{idVendor}"

Thanks for sharing your workaround. Unfortunately, it's no joy here. After following the procedure described, the terminal returned no error, but on trying to open the Xoom directory via Nautilus, I received the following message:
Code:
Error: Error stating file '/home/sog/Xoom': Transport endpoint is not connected
Please select another viewer and try again.
Unmounting proceeds without error.
Distribution: Ubuntu Lucid x64

Did you connect your xoom before or after you mounted? The most likely problem is the undeveloped configuration .
Change the line in 51-android.rules to
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", SYMLINK+="libmtp-%k", MODE="0666"
[\code]
Restart udev and then do a "ls -lah /dev/libmtp*" with the device attached and list the output. I need to figure out if the problem is the udev rule or elsewhere.
If the ls does not show any files then send the result of "lsusb |grep Motorola" which better list a line or there is something weird going on.
Sent from my Xoom using XDA App

Updated 51-android.rules as directed, then:
[email protected]:~$ ls -lah /dev/libmtp*
lrwxrwxrwx 1 root root 15 2011-02-27 19:59 /dev/libmtp-1-4 -> bus/usb/001/004
[email protected]:~$ lsusb | grep Motorola
Bus 001 Device 004: ID 22b8:70a8 Motorola PCS

Wait, you aren't able to get the Xoom to mount as a mass storage device?
ed. The leaked Xoom manual suggests it support mass storage. Phew. You were scaring me there a bit.

as far as I know, it's been confirmed that the current stack does not support mass storage, only mtp.

sogrady said:
as far as I know, it's been confirmed that the current stack does not support mass storage, only mtp.
Click to expand...
Click to collapse
Which stack, Linux or Honeycomb's? Where is it confirmed?
Non-working mass storage is a potential deal breaker.

honeycomb's. see here or here for details.

Thanks for the links.
This is a real WTF.

Can someone try running this attached apk to see if it enables mass storage? (It just runs enable, it won't run disable, so I don't know what will happen, it might cause apps to crash but rebooting should fix it, standard disclaimers apply, you run this at your own risk, etc., etc., etc.)
I don't have a Xoom, otherwise I'd try this myself.
Relevant code snippet for those interested:
Code:
StorageManager s = (StorageManager)getSystemService(Context.STORAGE_SERVICE);
Class c = s.getClass();
Method m = null;
try
{
m = c.getMethod("enableUsbMassStorage", (Class[]) null);
m.invoke(s);
}
catch(Exception e)
{
// TODO Auto-generated catch block
e.printStackTrace();
}
There may even be an easier way to achieve this -- I can't verify for myself because Honeycomb isn't in AOSP -- it doesn't work in the sim, but it might on a device: run adb shell, then run "am start -n com.android.systemui/.usb.UsbStorageActivity".

ydaraishy said:
Can someone try running this attached apk to see if it enables mass storage? (It just runs enable, it won't run disable, so I don't know what will happen, it might cause apps to crash but rebooting should fix it, standard disclaimers apply, you run this at your own risk, etc., etc., etc.)
I don't have a Xoom, otherwise I'd try this myself.
There may even be an easier way to achieve this -- I can't verify for myself because Honeycomb isn't in AOSP -- it doesn't work in the sim, but it might on a device: run adb shell, then run "am start -n com.android.systemui/.usb.UsbStorageActivity".
Click to expand...
Click to collapse
I ran the activity manager command and it brought up the usb mass storage screen but did not mount on computer. Also ran the apk but did not mount. Awesome job though. keep fighting the good fight

sogrady said:
Updated 51-android.rules as directed, then:
[email protected]:~$ ls -lah /dev/libmtp*
lrwxrwxrwx 1 root root 15 2011-02-27 19:59 /dev/libmtp-1-4 -> bus/usb/001/004
[email protected]:~$ lsusb | grep Motorola
Bus 001 Device 004: ID 22b8:70a8 Motorola PCS
Click to expand...
Click to collapse
Well that is interesting . You have read write privileges on the xoom. Sounds like it is a fuse configuration issue. Do you have any other fuse file systems you run?
Sent from my Xoom using XDA App

bigrushdog said:
I ran the activity manager command and it brought up the usb mass storage screen but did not mount on computer. Also ran the apk but did not mount. Awesome job though. keep fighting the good fight
Click to expand...
Click to collapse
Damn it. Looks like I actually need a device to get it working, and the AOSP drop. It's so moronic why they disabled mass storage.
Hmm. Can someone run, from adb shell, the output from "mount", and "ls /sys/devices/platform" for me?

Never mind. Mass storage has been defined out of the stingray (Xoom) kernel. It's not even in the default kernel.
To get mass storage support, be prepared to build your own kernel and reflash the device (once that's done, the am command above or the enabler app will work properly).

I've founded a working(ish) solution. This Xoom forum post details an approach that permits transfer of video/music/etc to the Xoom via Linux.
Couple of caveats:
1. The gnomad2 application is very unstable. Crashes frequently.
2. It appears to be write-only: I have not been able to delete files from the Xoom using this interface.

Thanks for the instructions to connect to a xoom tablet via Linux! However, I'm using Opensuse 11.3 and 11.4 on two different systems. I did install the mtp-tools with no issues, however, there is NO file by the name of mtpfs. A search on the net does not reveal it either. Where do I get this, or what package is it part of? Thanks again. If I can't get this tablet to connect to my linux box, I will have to take it back, since I do NOT use winbloze or Mac. Pretty short sited of Motorola IMHO.

Personally, I've given up on MTP + Linux Combo. I just use a straigt FTP transfer over wifi ( FTP Server on tablet ). It's about the same speeds.

any headway on this...
i am getting the: Transport endpoint is not connected error still and i have no real experience with FUSE so im stuck to using windows for any transferring.

stlsaint said:
i am getting the: Transport endpoint is not connected error still and i have no real experience with FUSE so im stuck to using windows for any transferring.
Click to expand...
Click to collapse
try following the directions in this thread:
http://forum.xda-developers.com/showthread.php?t=981774
They are basically a superset of what I posted. If you still have trouble after that post in either thread (this one or that one) and I will try and help as best I can.

followed the thread up unto the fstab part as i dont wan to edit my fstab without confirmation that it will work. But i get the exact same error with the endpoint text. I am trying this on Crunchbang linux which is based off debain the same way ubuntu is. I am probably going wrong with FUSE somehow but i have never messed with it so i dont know how to troubleshoot it.

Nexus 4 not being recognized by adb (Ubuntu 12.10)

Hi all,
I am trying to connect my Nexus 4 device to my computer via USB. I am currently running Ubuntu 12.10 with the latest Android SDK installed.
The problem is that I can't seem to properly connect the Nexus 4 so that I can see the device in the devices list of adb (using ./adb devices).
An entry to the USB rules list has already been added, which is this one:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee5", MODE="0666"
The file is named "99-nexus4.rules" and properly chmodded.
The output of lsusb is:
Code:
Bus 002 Device 012: ID 18d1:4ee5 Google Inc.
I have already tried to restart the adb server several times, but with no success. Starting the server as root didn't help either. I choose to mount the phone as MTP device on the phone itself.
Currently I am lost about what the problem is in this case. I would love to hear some feedback from you guys.
Thanks in advance!

Is adb enabled on your phone ?
Did you restart udev or rebooted ?
btw, saw this and work allot better than standard 12.10 mtp
http://www.webupd8.org/2013/01/upgrade-to-gvfs-with-mtp-support-in.html
lvandam said:
Hi all,
I am trying to connect my Nexus 4 device to my computer via USB. I am currently running Ubuntu 12.10 with the latest Android SDK installed.
The problem is that I can't seem to properly connect the Nexus 4 so that I can see the device in the devices list of adb (using ./adb devices).
An entry to the USB rules list has already been added, which is this one:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee5", MODE="0666"
The file is named "99-nexus4.rules" and properly chmodded.
The output of lsusb is:
Code:
Bus 002 Device 012: ID 18d1:4ee5 Google Inc.
I have already tried to restart the adb server several times, but with no success. Starting the server as root didn't help either. I choose to mount the phone as MTP device on the phone itself.
Currently I am lost about what the problem is in this case. I would love to hear some feedback from you guys.
Thanks in advance!
Click to expand...
Click to collapse

nardusg said:
Did you restart udev or rebooted ?
Click to expand...
Click to collapse
Yes, every time after I changed something in the rules list I restarted udev and rebooted as well.

Do you have java installed properly? Here is the post I used to get adb working on Ubuntu 12.10 (its post #62 the OP was for Ubuntu11). It didn't work till I set the proper permissions as stated in the post under editing the udev rules (line in post where it shows sudo gedit /etc/udev/rules.d/99-android.rules). I did a 64-bit install and it worked perfectly. Basically what you are doing is manually entering the Nexus 4 into the list of devices as its not there by default.
http://forum.xda-developers.com/showthread.php?p=19446284

That solution worked for me! Many thanks.

ADB stays 'unauthorized' on Linux

Hey all,
I just wasted a few hours getting my axon 7 to connect to my pc running ArchLinux without luck.
lsusb gives me the following:
Code:
$ lsusb
Bus 002 Device 014: ID 19d2:0306 ZTE WCDMA Technologies MSM
I think I've tried just about every combination of udev rules I could find on the internet. At the moment they are:
Code:
$ cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0306", MODE="0666", GROUP="adbusers"
SUBSYSTEM=="usb",ATTRS{idVendor}=="19d2",ATTRS{idProduct}=="0306",SYMLINK+="android_adb", GROUP="adbusers"
My user is a member of 'adbusers' and my phone is in USB debugging mode, also the USB thing is set to MTP.
Still, adb devices gives the following:
Code:
$ adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
6f7f7da7 unauthorized
The phone also never asks for confimation or anything like that.
Has anyone here encountered something similar or know what I'm missing?
Thanks in advance

unrealpowerz said:
Hey all,
I just wasted a few hours getting my axon 7 to connect to my pc running ArchLinux without luck.
lsusb gives me the following:
I think I've tried just about every combination of udev rules I could find on the internet. At the moment they are:
My user is a member of 'adbusers' and my phone is in USB debugging mode, also the USB thing is set to MTP.
Still, adb devices gives the following:
The phone also never asks for confimation or anything like that.
Has anyone here encountered something similar or know what I'm missing?
Thanks in advance
Click to expand...
Click to collapse
I had the same problem in Windows when using a custom rom. Enabling 'adb over network' solved it for me (the 'Allow USB debugging' window came up). even though it's seemingly unrelated

If that doesn't work try adb while phone is in TWRP (if you have it)

Hey fellow arch user here, (pacman ftw)
I had this same problem earlier with adb and fastboot. The solution is to run adb and fastboot commands as superuser. ie sudo fastboot ..... and sudo adb ......