[Q] adb shell returning device offline - T-Mobile Samsung Galaxy Note 3

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)

Related

[q] adb shell from any computer

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

[q] ADB Mac can't find galaxy nexus

Anybody get adb shell working on mac in terminal? Device doesn't even show up for me
Same issue here....
i got it to be recognized on my windows computer, but when i pull packages.xml nothing shows up anywhere.
No issues here; ensure developer/USB debugging is turned on and you are using a newer platform tools from Google.
You should be on platform tools Rev 9 or higher.
(If you downloaded the SDK go to the directory in shell/terminal on your mac, cd tools, then run ./android
This will let you do GUI based updates to the tools
In case you never had the SDK - I have posted my working Mac ADB and fastboot's here.
I have the same issue. I don't get it to be recognized when using ./adb usb or ./adb devices.
OS : Mac os X Lion 10.7.2
has anyone figured this out?
as far as I know I am running the latest SDK... but I will double check.
frustrating.
has anyone tried connected via Parallels?
UPDATE - just confirmed my SDK is at v15, so that can't be the issue.
Also - NPS_CA, your abd didn't work any better than mine - still not showing up.
make sure easy tether isn't installed on mac

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

adb and fastboot not working

I want to unlock and root my N7 LTE but adb and fastboot are not working, I enabled developer options and usb debugging, fastboot and adb work fine with my HTC One. I tried several cables.
My system: win8.1 64 bit (usb 2)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
SH34EW901467 device
edit: it also tried on a win7 64 bit, as ptp, mtp and none and it still doesn't show up
godutch said:
I want to unlock and root my N7 LTE but adb and fastboot are not working, I enabled developer options and usb debugging, fastboot and adb work fine with my HTC One. I tried several cables.
My system: win8.1 64 bit (usb 2)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
SH34EW901467 device
edit: it also tried on a win7 64 bit, as ptp, mtp and none and it still doesn't show up
Click to expand...
Click to collapse
found a solution, I googled for the device hardwareid and found the universal adb drivers, installed these and now adb and fastboot work

[Q] adb on Mac OSX

Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
http://www.mylgphones.com/tag/usb-drivers try these drivers
That's the ones that didn't work.
Same problem here... Any luck?
Change the USB mode to PTP and you should get the RSA prompt.
anod said:
Same problem here... Any luck?
Click to expand...
Click to collapse
Yes I have install Google universal usb drivers worked for me search on Google for them
PTP worked for me, no LG driver installed.
Just got my G3 on Verizon, cannot see the device over ADB either on Mac OSX
I tried MTP, PTP, and Charge only both with and without LG drivers installed. Since it's OSX, there are no Google Universal USB drivers.
Android File Transfer opens up fine, but ADB doesn't show the device. Quite fishy indeed.
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
May I ask how you managed to connect your phone to your mac via MTP? I am unable to get any kind of connection to my mac.
On windows it works finde, I can open the internal and external sd card and copy files from and to the device, I would be more than happy to achive the same on my mac.
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
Hi there, you will first need to enable USB Debugging. Head over to Settings > General > About Phone > Software Information. Tap Build Number 5 times, and you'll unlock the Developer options.
Go to Settings > Developer options, and check USB Debugging. From there, ADB should work. Good luck!
OK, so I installed the new drivers, rebooted, and got ADB to recognize my LG, and was able to debug successfully. Now Android File Transfer doesn't see it, nor does Finder show the device. What am I missing?
It's broken, I saw a tweet from jcase regarding the issue. I have the same problem. I just adb push/pull when necessary for now.
Sent from my LGLS990 using XDA Free mobile app
EDIT - It wasn't jcase, it was @utoprime
Mine works fine on my Mac
faded03cobra said:
Mine works fine on my Mac
Click to expand...
Click to collapse
You have adb and MTP works? What OSX version?
Sent from my LGLS990 using XDA Free mobile app
Solution
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
I know this is a seriously old thread, but for future reference - if your device is NEVER recognised by adb from the start, no matter how much you add the vendor etc, open up Terminal.app and type this in:
cd ~/.android/
rm adbkey adbkey.pub
This will navigate to android's folder and remove the RSA keys your computer uses to identify with the phone. If the address of the folder is wrong you can alter the first line to whatever is appropriate.
KAR0SH1 said:
I know this is a seriously old thread, but for future reference - if your device is NEVER recognised by adb from the start, no matter how much you add the vendor etc, open up Terminal.app and type this in:
cd ~/.android/
rm adbkey adbkey.pub
This will navigate to android's folder and remove the RSA keys your computer uses to identify with the phone. If the address of the folder is wrong you can alter the first line to whatever is appropriate.
Click to expand...
Click to collapse
Seriously old, and seriously unresolved (for me and a few people on reddit, at least). Still have not succeeded at getting ADB to detect G3 on USB, tried running the -usb flag on the cli and everything. Is there a working process yet? Verizon seems to be the outlier here as well...
Just worked for me on OSX Yosemite with a D855 on V10l:
- Update ADB (android platform tools)
- Install LG Driver (link is in this thread)
- Reboot
- run "rm ~/.android/adbkey" and "rm ~/.android/adbkey.pub"
- run "adb devices" (you should now see your G3)
- run "adb kill-server" (just to make sure there is no interference)
- quit all applications on your phone and go to home screen
- run "purpledrake_osx.command" which should now work
Inbetween (guess it was directly after running "purpledrake_osx.command") you should get a permission request on your phone which you should allow
Thanks
_ranch said:
Change the USB mode to PTP and you should get the RSA prompt.
Click to expand...
Click to collapse
Thanks, this works for me on El Captain
Also on El Capitan:
After enabling developer settings + USB debugging on phone (see earlier in thread),
Removing the adbkey + pub from the users .android folder (see earlier in thread),
and connecting with PTP,
It finally works

Categories

Resources