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 ;-)
Related
I have came accross a android beta phone when it was in its step of development all I know is that it has android 1.0 and the phone looks excatcly like a tmobile dash phone and now my problem is that when I turn on the phone it says operater main screen turn on also says
Cannot find. '/android/bin/hotplug '
Cannot find. '/android/bin/logd '
Cannot find. '/android/bin/debuggerd '
Cannot find. '/android/bin/runtime '
Cannot find. '/android/bin/dbus-daemon '
Can anyone help me get that fix and have it running I really wanna use that phone any help would really appriciated
Are you talking about the Google Sooner?
Good luck finding *any* support for it. A couple of people have asked around here before, but hardly anyone has them.
google sooner
Yeah thats the phone o have what I wanna do is install android donut but I can't because I get that msg when I turn it on
Hey Friend, I've got the same problem as you with Google Sooner, have you ever got any solution?
I tried to connect Sonner on Ubuntu 9.10, command as following, and new problem is my Ubuntu can detect Sonner as 18d1:d00d, and when I run run ./adb devices, nothing listed, and sure that when I typed run ./adb shell, it said no devices found.
■Install Ubuntu Ubuntu
■The version of Ubuntu shouldn't matter. However, our Dev enviornment was tested with Ubuntu 8.10 Server
■Once Ubuntu is installed with the default settings we'll need to edit some system settings to allow the OS to talk with the Sooner Mobile Device.
■touch /etc/udev/rules.d/50-android.rules
■Add the line SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666" where 18d1 is the item listed under lsusb
■chmod a+rx /etc/udev/rules.d/50-android.rules
■Run this as root /etc/init.d/udev restart
■Java for Development
■apt-get install sun-java6-jdk
■apt-get install sun-java6-bin
■sudo update-java-alternatives -s java-6-sun
■Type java -version and javac -version
■It should state Java(TM). The output for javac will just list the version number.
■The Ubuntu OS should now be able to detect the device
■Plug the phone into the computer.
■Type lsusb
■Bus 002 Device 001: ID 0000:0000
■Bus 001 Device 012: ID 18d1:deed
■Bus 001 Device 002: ID 0e0f:0002
■Bus 001 Device 001: ID 0000:0000
■The device ID of 18d1 is the HTC Sooner Device
■Install the Google Android SDK
■From the Android SDK installation directory i.e. /android_sdk_linux_m3-rc22a/tools run ./adb devices
■It should list something similar to
1 53590a1587035cc9 device 0
■To access the Sooner Phone type ./adb shell
I received new Defy XT Dec. 17 from Republic Wireless and wanted to move as many apps as possible to SD card without rooting as discussed elsewhere.
However, after enabling USB debugging on the phone (Settings - Applications - Development) and connecting the phone to the computer with the USB cable here is the message when I type command "adb devices".
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
???????????? no permissions
command "adb version" returns:
Android Debug Bridge version 1.0.31
Apparently my Defy is not recognized and of course no other adb commands work. I'm not using Windows. I'm using Linux, Ubuntu 12.10. I've used adb successfully on same computer with Acer Iconia A100 Tab. Attached file contains pertinent messages in syslog when usb cable from Defy is connected to computer. Any help with why this device not recognized by adb would be appreciated.
hello
ummm .... seemed to be new at using adb tool ...so i am practice on my nook .... anyway ....i enable usb debugging in nook color tools .... then execute this command:
C:\Documents and Settings\XXXXXXX>cd c:\
C:\>cd Android
C:\Android>cd android-sdk
C:\Android\android-sdk>cd platform-tools
C:\Android\android-sdk\platform-tools>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Android\android-sdk\platform-tools>adb connect usb
unable to connect to usb:5555
C:\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
any suggestion
best regards
Hi:
Code:
adb connect usb
Tries to connect to a host named "usb" over TCP (WiFi) port 5555.
Code:
adb usb
Starts the adb server in USB mode.
Note: You can connect to one device over USB at the same time that you are connected to another over TCP (WiFi).
I do that all the time.
You just have to specify which device you want to talk to when using push/pull/shell.
Code:
adb -s nook:5555 shell
My adbsync also works with multiple devices, but that's a separate issue.
Renate NST said:
Hi:
Code:
adb connect usb
Tries to connect to a host named "usb" over TCP (WiFi) port 5555.
Code:
adb usb
Starts the adb server in USB mode.
Note: You can connect to one device over USB at the same time that you are connected to another over TCP (WiFi).
I do that all the time.
You just have to specify which device you want to talk to when using push/pull/shell.
Code:
adb -s nook:5555 shell
My adbsync also works with multiple devices, but that's a separate issue.
Click to expand...
Click to collapse
thx renate so much ....... how about if i hve a dead device or an android device that i didint enable usb debugging mode but my computer can identify it via usb ...... ????
thx
Sent from my NOOK using xda app-developers app
I have a Kubuntu 15.10 linux PC and a S7 Edge Exynos SM-G935FD phone running Android 6.01. The phone is rooted using Chainfire auto-root. Linux and adb don't recognize the phone ... when the phone is connected to the linux PC using a USB cable, the phone doesn't show up in lsusb list of devices or in the adb devices command (either when the phone is in recovery mode or in normal mode). Here's what I've done:
-Enabled Developer Options, USB Debugging and USB Configuration MTP on the phone
-Installed the latest Android SDK including Android 6.0 Support and all available updates on the linux box.
-Created /etc/udev/rules.d/51-android.rules on the line below on the linux box
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
permissions on that file are -rw-r--r-- 1 root root 71 May 4 14:07 /etc/udev/rules.d/51-android.rules
-rebooted the linux box and the phone a million times, and killed/restarted the adb server a million and a half times
I do see messages in the syslog on the linux box in attachment hereto - not sure what they mean. I'd very much appreciate recommendations how to diagnose and/or fix. Thx, Gus
gus_zernial said:
I have a Kubuntu 15.10 linux PC and a S7 Edge Exynos SM-G935FD phone running Android 6.01. The phone is rooted using Chainfire auto-root. Linux and adb don't recognize the phone ... when the phone is connected to the linux PC using a USB cable, the phone doesn't show up in lsusb list of devices or in the adb devices command (either when the phone is in recovery mode or in normal mode). Here's what I've done:
-Enabled Developer Options, USB Debugging and USB Configuration MTP on the phone
-Installed the latest Android SDK including Android 6.0 Support and all available updates on the linux box.
-Created /etc/udev/rules.d/51-android.rules on the line below on the linux box
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
permissions on that file are -rw-r--r-- 1 root root 71 May 4 14:07 /etc/udev/rules.d/51-android.rules
-rebooted the linux box and the phone a million times, and killed/restarted the adb server a million and a half times
I do see messages in the syslog on the linux box in attachment hereto - not sure what they mean. I'd very much appreciate recommendations how to diagnose and/or fix. Thx, Gus
Click to expand...
Click to collapse
Why are you wanting to use ADB or SDK?
Make sure you have Samsung drivers installed.
My pc recognizes my G935F right away.
gus_zernial said:
I have a Kubuntu 15.10 linux PC and a S7 Edge Exynos SM-G935FD phone running Android 6.01. The phone is rooted using Chainfire auto-root. Linux and adb don't recognize the phone ... when the phone is connected to the linux PC using a USB cable, the phone doesn't show up in lsusb list of devices or in the adb devices command (either when the phone is in recovery mode or in normal mode). Here's what I've done:
-Enabled Developer Options, USB Debugging and USB Configuration MTP on the phone
-Installed the latest Android SDK including Android 6.0 Support and all available updates on the linux box.
-Created /etc/udev/rules.d/51-android.rules on the line below on the linux box
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
permissions on that file are -rw-r--r-- 1 root root 71 May 4 14:07 /etc/udev/rules.d/51-android.rules
-rebooted the linux box and the phone a million times, and killed/restarted the adb server a million and a half times
I do see messages in the syslog on the linux box in attachment hereto - not sure what they mean. I'd very much appreciate recommendations how to diagnose and/or fix. Thx, Gus
Click to expand...
Click to collapse
"POWWWWER...SPEEEEED !"
Sent from my Echoe Powered Stig driven G935F
> Why are you wanting to use ADB or SDK?
For the same reason thousands of other developers do
> Make sure you have Samsung drivers installed.
Linux does not require special USB drivers for ADB
> My pc recognizes my G935F right away.
Is your PC running Linux?
And no, don't ask me why I use Linux instead of Windows, as most Android developers do.
Gus
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 ......