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.
Hi,
Phone: Galaxy S I9000
ROM : XXJVU, Rooted
Linux : Ubuntu 11.10
"Usb debuging" ticked in settings.
Usb cable is connected and adb works in Windows 7.
lsusb out put:
Code:
Bus 002 Device 008: ID 04e8:681c Samsung Electronics Co., Ltd Galaxy Portal/Spica Android Phone
681c <-- It means "debuging mode" so, why adb didn't detect device ?
adb shell out put:
Code:
error: device not found
SOLUTION:
My adb file was old or crupted. and new one working like charm ;-)
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.
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 ......
I went throug over 20 forums sites videos none of them helped me I forcfully manually installed abd drivers reconizes when the phone is on adb devices but when I do adb reboot bootloader and do adb devices nothing pops up in device manager I changed the driver around few times till shows norhing killed adb server truned it back on nothing rebooted my pc use diffrent usb port have nothing plugged into any other port Have owm unlocking bootloader is unlocked usb debugging is on I did put media transfer for files them ptp for pictures still no change I installed lg air drive thing still get same resutls. When I do fastboot devies it shows up there in bootloader or not.
adb push dirtycow /data/local/tmp
adb push recowvery-applypatch /data/local/tmp
adb push recowvery-app_process64 /data/local/tmp
adb push recowvery-run-as /data/local/tmp
I have to push those commands but I dont know how with fastboot command since there is no adb devices I tried also on 5 different os using android tool kit latest's android usb drivers some adb installer thing where you select Y for all options I tried on parrot os kali linux windows 10 pc and two windows 7 pc I have windows 7
I tried almost everything an the driver shows up in device manager please help
BTW It wasnt like that before it was before under android device tab as a good adb device lge adb device I tried them all
LG V20 android 7.0 T-Mobile I have 7.0 Build Number NRD90M Soft Version H91810q
st0rm1 said:
I went throug over 20 forums sites videos none of them helped me I forcfully manually installed abd drivers reconizes when the phone is on adb devices but when I do adb reboot bootloader and do adb devices nothing pops up in device manager I changed the driver around few times till shows norhing killed adb server truned it back on nothing rebooted my pc use diffrent usb port have nothing plugged into any other port Have owm unlocking bootloader is unlocked usb debugging is on I did put media transfer for files them ptp for pictures still no change I installed lg air drive thing still get same resutls. When I do fastboot devies it shows up there in bootloader or not.
adb push dirtycow /data/local/tmp
adb push recowvery-applypatch /data/local/tmp
adb push recowvery-app_process64 /data/local/tmp
adb push recowvery-run-as /data/local/tmp
I have to push those commands but I dont know how with fastboot command since there is no adb devices I tried also on 5 different os using android tool kit latest's android usb drivers some adb installer thing where you select Y for all options I tried on parrot os kali linux windows 10 pc and two windows 7 pc I have windows 7
I tried almost everything an the driver shows up in device manager please help
BTW It wasnt like that before it was before under android device tab as a good adb device lge adb device I tried them all
LG V20 android 7.0 T-Mobile I have 7.0 Build Number NRD90M Soft Version H91810q
Click to expand...
Click to collapse
adb and fastboot are totally different processes. Replace the 'adb' command with 'fastboot' and it should work.