[q] adb shell from any computer - EVO 4G Q&A, Help & Troubleshooting

Is it possible; from any computer, within the command line to run commands on any android devices/phone ie: adb shell, adb devices, adb logcat, adb push that already has android adb/sdk installed?
The reason I asked is cause I installed android sdk/window usb driver on my main laptop with no problems, but I recently purchased another laptop went through the same setup procedure but my adb does not recognize or see my phone when I have it plugged in via usb.
I am at a loss and dont know what to do...

UND3RTAK3R said:
Is it possible; from any computer, within the command line to run commands on any android devices/phone ie: adb shell, adb devices, adb logcat, adb push that already has android adb/sdk installed?
The reason I asked is cause I installed android sdk/window usb driver on my main laptop with no problems, but I recently purchased another laptop went through the same setup procedure but my adb does not recognize or see my phone when I have it plugged in via usb.
I am at a loss and dont know what to do...
Click to expand...
Click to collapse
1) install HTC sync to get the Evo drivers
2) install Android SDK
3) add the tools folder with adb.exe in it to your windows Path or always navigate the command line to that folder.
should work

Related

New to ADB and have a few questions I can't find the answers to...

Now, I have figured out that I have to actually be in the android-sdk-windows\tools folder for ADB to work, but when I type adb devices it just says List of devices attached but doesn't list my Evo.
I have USB debugging on.
An Android ADB/rooting noob guide would be very helpful right now.
criccio said:
Now, I have figured out that I have to actually be in the android-sdk-windows\tools folder for ADB to work, but when I type adb devices it just says List of devices attached but doesn't list my Evo.
I have USB debugging on.
An Android ADB/rooting noob guide would be very helpful right now.
Click to expand...
Click to collapse
Does it have anything there when you type adb devices? Should come up with a HT and some numbers after it....being your device, EVO.
Actually, there is a step by step Guide for EVO root, and a ADB Guide for Beginners
Your device isn't being recoginized check the driver if u r in windows.
Ok, I managed to figure out the cryptic SDK installer and download the USB driver package to android-sdk-windows\usb_driver. I used Device Manager to install the driver and I pointed it to that folder and I get the "Windows was unable to install your ADB".
Are you already Rooted? as for the Drivers, when I plugged in my EVO via USB, it installed drivers...I also copied the HTC Sync that came on the SDCard w/phone, onto my pc. But I did not have to do anything further.
Can I ask what you are trying to do in adb? and is this for the EVO?
use the cd command to make sure you are in the android sdk tools folder
if you want adb to work
what i do
1. use the cd command to go to the directory where my sdk is located which for example is c:\androidsdk\tools
2. there you go
3. if you want shell make sure your device is connected
"adb shell"
and have htc sync from evo's sd card installed
http://myevo4g.net/main/?p=83
Sent from my HTC EVO
download htc sync and install that. i was having the same problems and apparently the usb drivers that get installed with that app are the ones that worked like a charm for me.
Try
Code:
./adb devices
Instead.
--> try" adb start-server "
If your HTC dont show up, it's usually because the ADB server isnt running. Hope this helps =]
I've rooted a hero before and felt pretty confident with android sdk, usb drivers, etc. After spending an hour trying to get it to work on my win 7 64 bit system, I thought it might save someone some time if I posted what finally allowed me to get adb to work.
My problem was the computer wouldn't recognize the EVO as a device. Even after I installed the usb drivers through android sdk. I tried to manually update them through device manager (pointing it to the usb drivers directory) and still no luck.
As the video linked above showed, the missing piece for me was installing htc sync. use the version that comes on the phone. So connect the phone to the computer, mount it as a drive from the phone menu, then copy over the htc sync directory to your computer, then run it. The version on my phone was 2.031. THEN the computer will recognize it with usb debugging turned on and I'm able to adb to the phone through the command prompt.
Hope that helps someone. Sean

[Q] Not able to debug!

So I am a bit done with just flashing other roms to my kaiser and also want to develop some apps and want to experiment with making my own roms, but initially just porting roms from other devices like the HTC wildfire. But I am not able to use debugging:
So this is what I have done I have installed the android sdk and also installed the ADT plugin for eclipse. Then I have compied the android-sdk file to the root of my c drive so it is easier to use the command line interface with this file. I then run the following commands in the cmd, as admin:
adb kill-server
adb start-server
adb devices
And here is where the **** just hits the fans I am unable to see my device in the list of devices. While my device is recognized by the computer as ADB Interface > HTC Dream Composite ADB Interface in the device manager section. (But I must note that when I click on the device it is noted: "Device cannot start. (code 10)" ) Also when I double click on the device in the regular computer windows (where all your hd's are showed) the file system of the device is empty!
So does anyone have any advice?
Have you test it from a live usb or CD GNU/Linux like Ubuntu?
Nope, I hoped that it would work in Windows, but I will try it in Linux if that would solve it.l But can you see anything that i am doing wrong or is it just Windows
I always have problems with USB management on Windows, all versions...with all my computers. Linux kernel seems to be better, imho, for USB.

adb Problem

Heya,
I'm in the process of getting permaroot and I got a problem with adb commands which is really annoying.
Whenever I fire up an adb command, either in dos or adb shell, it works with a chance of 50/50. It can happen that I fire the command and nothing happens but a cursor, then I have to ctrl+c out and try it again.
And this sucks especially when I have to do several commands in a row in the shell -.-
What kind of commands, how are you connecting it to the computer, what kind of computer (windows, OSX, Linux?) what Rom? Are you connecting thru a USB hub (powered or unpowered), are you using the latest android SDK that matches your Rom's version?
Basically a lot of information needs to be mentioned.

AT&T S3 not seen by ADB

Ok... i've gone through the steps in the one thread to get the phone rooted and everything without tripping the flash counter. At least the rooting with ODIN part. Been trying to flash CWM Touch for it, but for the life of me can't get the S3 to enter debugging mode over USB so that it can be seen by ADB to do so. I have Debugging over USB checked in the settings on the phone, i've rebooted the phone several times... it just never seems to enter debugging mode (or at least not like on my old Atrix 4G, where it actually told you in the notification bar that debugging was enabled).
It doesn't say debugging enabled. Do you have Kies installed? If so make sure it isn't running. Plug in the phone and type adb devices. If detected adb will report a serial number.
gunnyman said:
It doesn't say debugging enabled. Do you have Kies installed? If so make sure it isn't running. Plug in the phone and type adb devices. If detected adb will report a serial number.
Click to expand...
Click to collapse
I had installed Kies... tried hooking it up, still wouldn't list in ADB. uninstalled Kies, but kept the drivers installed. And i only mentioned the idea of it saying Debugging enabled when you connect the USB cable because my Atrix 4G said that every time from the get-go.
Also odd.... looked into the SuperUser app... and the log shows several allowed access attempts from "shell"... yet never seemed that way in ADB.
I had the same problem... try going in to the "services" settings and update the driver to Android ADB composite. Other than that, my suggestion is to make sure Kies finds the drivers for both Camera mode and USB mode by toggling the selection while plugged in to Kies.
Sent from my SGH-I747M using xda app-developers app
Your last resort would be to remove the drivers and reinstall them... Don't install Kies...
Or do you think i might have better luck in Ubuntu? Have that installed on my desktop as well.
edit: well... that's odd. booted into Ubuntu, installed the linux Android SDK and everything, got everything set up. opened the terminal, and just checked the devices without being in the ADB Shell... and a device showed up. launched the adb shell... checked devices again... nothing showed up, as on Windows. Figured what the hell, and did the command to install the recovery, and it worked.
elementaldragon said:
Or do you think i might have better luck in Ubuntu? Have that installed on my desktop as well.
Click to expand...
Click to collapse
It seems to be a driver issue, kies interfering, or a component is missing, or all of that, so I'd start your windows driver and software over fresh...
Uninstall Kies
Uninstall the drivers
Reboot
Install the drivers
Install the Java JDK (64bit has never worked for me, even though the drivers are 64bit)
Install the Android SDK
Use the Android SDK to get the Platform Tools and the Google USB Driver
than adb devices should show a phone
---------- Post added at 11:25 AM ---------- Previous post was at 11:24 AM ----------
elementaldragon said:
edit: well... that's odd. booted into Ubuntu, installed the linux Android SDK and everything, got everything set up. opened the terminal, and just checked the devices without being in the ADB Shell... and a device showed up. launched the adb shell... checked devices again... nothing showed up, as on Windows. Figured what the hell, and did the command to install the recovery, and it worked.
Click to expand...
Click to collapse
sometimes ADB Devices returns nothing for me, but theres a phone there, it would say nothing connected or to some effect if it didn't find anything...
Yea... every time i entered "adb devices" in the Windows command prompt, it always said "List of detected devices" or whatever it says, but nothing would be there, and if i tried the command to install the recovery it would say it was not a valid directory or whatever. Didn't show up on Ubuntu either, but it still worked...
EDIT/UPDATE: I was using a USB 3.0 port which apparently ADB didn't like (though ODIN rooting on that USB port worked fine...). I switched to another USB port and suddenly it worked!
Sorry to resurrect an old thread but I guess it's better than creating a new one for the same purpose...
Doesn't seem like this was resolved and I haven't been able to get my S3 to connect to ADB. I'm running Windows 7 Ultimate 64 Bit.
I had this driver already installed:
ATT_I747_GSIII_Samsung_USB_Driver_v1_4_6_0
I enabled USB debugging and it wouldn't connect. I installed Kies, still wouldn't connect. I uninstalled the driver and Kies and rebooted. Reinstalled "ATT_I747_GSIII_Samsung_USB_Driver_v1_4_6_0", installed the Google USB driver, still won't connect.
I'm still not sure if I'm supposed to see any sort of notification in my bar showing that USB debugging mode has been executed but I'm definitely not getting anything like that.
Code:
D:\APPS\ANDROID\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
891b0876 offline
D:\APPS\ANDROID\android-sdk-windows\platform-tools>adb devices
List of devices attached
Yea, when i finally was able to use ADB to push a recovery onto my S3, it never actually showed up if i checked the devices in ADB Shell. Well... it DID, but not if i already typed the SU command before "adb devices".
hey guys
i have same problem i wanna adb my galaxy s3 rogers (att) i am trying to do the root no tripping flash counter so i got to the adb shell part
i dont know what else to do to make my computer recognize my phone ??
i installed sdk and extract/installed it in the c:\android folder of my comp i let sdk installed all the things it needs to took a while
so whats left? i have my phone usb connected to comp and debuging on i type adb shell it says adb is not recognized internal or external command???
do i need to have somthing open on the phone b4 openning command?
pleaaase help lol
thanks
You need to navigate to the folder where adb is actually located (platform-tools)
You don't have to use adb, you can use the same commands on terminal emulator

[Q] adb shell returning device offline

I have all the JDK and Android SDK components installed on my Windows 7 box. I have enabled USB Debugging and when I try to run adb shell I get the following error:
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb shell
error: device offline
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb devices
List of devices attached
5099ba28 offline
Shows the device attached to my PC.
I have killed and restarted the adb server, rebooted my phone, no luck.
I have never had a problem before with adb. Do you need to use the USB 3.0 cord that was included with the Note 3 or will a regular mico USB work?
stevetrooper said:
I have all the JDK and Android SDK components installed on my Windows 7 box. I have enabled USB Debugging and when I try to run adb shell I get the following error:
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb shell
error: device offline
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb devices
List of devices attached
5099ba28 offline
Shows the device attached to my PC.
I have killed and restarted the adb server, rebooted my phone, no luck.
I have never had a problem before with adb. Do you need to use the USB 3.0 cord that was included with the Note 3 or will a regular mico USB work?
Click to expand...
Click to collapse
regular should work. That is just the data transfer speed.
Have you tried this? http://forum.xda-developers.com/showthread.php?t=2247471
Figured out the problem, I needed to upgrade my adb to the latest version (1.0.31). When I ran the adb shell, a pop-up window appeared on the Note 3 and I confirmed. Now I am able to access.
stevetrooper said:
Figured out the problem, I needed to upgrade my adb to the latest version (1.0.31). When I ran the adb shell, a pop-up window appeared on the Note 3 and I confirmed. Now I am able to access.
Click to expand...
Click to collapse
Yeah, the new adb(d) (6 months back, iirc) added some security where you have to confirm the rsa fingerprint of each machine you connect to. It's a little annoying, because you HAVE to connect adb via USB first, and only then can you use adb via wireless, which is all I ever use anymore.
(edit: adb security added in 4.2.2, which was released in february)

Categories

Resources