Why does adb return offline after the device string?

J

20

58

I use "adb devices" to get following result. Only one device is connected to PC by USB, but we get 8 lines of result.

Could anyone suggest the reason?

WH96TNE00361    offline
WH96TNE00361    offline
WH96TNE00361    offline
WH96TNE00361    offline
WH96TNE00361    offline
WH96TNE00361    offline
WH96TNE00361    offline
WH96TNE00361    offline

Jolty answered 17/11, 2011 at 5:34 Comment(2)

please refer following link for the answer. its faster: https://mcmap.net/q/21944/-android-adb-device-offline-can-39-t-issue-commands – Jannette 13/6, 2013 at 19:36

Most of these answers are some variant on "upgrade adb" and or / "reinitialize stuff." The one that solved it for me was Krystian's below. ADB was switched to wifi mode so wouldn't work over USB. I bet a lot of people have that problem. – Justifiable 26/8, 2013 at 23:39

A

80

Try the following:

Unplug the usb and plug it back again.
Go to the Settings -> Applications -> Development of your device and uncheck the USB debugging mode and then check it back again.
Restart the adb on your PC. adb kill-server and then adb start-server
Restart your device and try again.

Athene answered 1/4, 2012 at 17:42 Comment(7)

5. Upgrade to the newest SDK / adb, if your device is >=4.2.2 – Sporran 15/8, 2013 at 21:10

I fixed the issue (on my Nexus 5) by going to the notification area, tapping on the USB connected and unchecking "Use as Media" or something. Now it shows correctly in adb. – Shayshaya 30/1, 2014 at 5:48

in my case it was simply because my device was displaying a dialog "allow RSA" and I didn't notice :0. Just allowed "always" and the device now appears as "device" instead of "offline" – Giorgione 7/2, 2014 at 21:12

Here's what worked for me, after upgrading, trying everything, etc. It was what scottastic suggested, I switched my phone from MTP to a PTP (camera) device, and this brought the RSA prmopt up. Now it's connected as adb. I was even able to switch it back to MTP afterwards. – Mona 10/3, 2014 at 0:25

doesn't work for me either. the strange thing is android studio has no problem detecting the device but I cannot from the command line – Roshan 21/10, 2014 at 13:49

I didn't even know what adb was but mine was turned off for some reason O_O. All I had to do was step 2 and 3. Thanks so much!! – Paramount 21/11, 2019 at 10:17

Unfortunately these 4 steps didn't work for me. I can't figure out how to get my device to pair to ADB again. – Euphuism 3/1, 2021 at 22:20

S

35

To complete the previous answers, another possible solution is to change the USB socket in which your cable is plugged in.

I had this problem (with the classical answer about using adb kill-server / start-server not working) and it solved it.

Actually, it took some time to find that because Windows was correctly recognizing the device in my first socket. But not ADB. As Windows was recognizing the device, I had no real need to test other USB physical sockets. I should have.

So you can try to plug the cable in all your USB physical sockets directly available on your computer. It did worked for me. Sometimes the USB sockets are not managed the same way by a computer.

Staffer answered 28/5, 2012 at 14:9 Comment(4)

This worked for me! Thanks! Because I was thinking of throwing the damn thing out the window. I had to plug it to a red/pink coloured USB slot (3.0) – Adenine 23/6, 2012 at 11:48

Switching USB ports fixed this for me when nothing else did. Thanks! – Veneer 10/1, 2013 at 16:4

Windows 8 here and for whatever reason this also fixed my problem! – Oilskin 9/5, 2013 at 3:31

This was for me. I was using a front panel usb on my case. On the second front panel port, I had connected a steering wheel, and because of this it was not working. When I've disconnected the wheel it was working ok. Oh and it was also working with the other 50 usb ports I had available, including even the keyboard ones. That scumbag one I was using, didnt. – Laity 27/2, 2016 at 9:23

J

22

Beginning from Android 4.2.2, you must confirm on your device that it is being attached to a trusted computer. It will work with adb version 1.0.31 and above.

Jeramyjerba answered 21/2, 2013 at 13:17 Comment(8)

This is very likely the problem I'm having as it only started when I upgraded to 4.2.2, however, no matter what I do I can't get any popup to appear that asks me to authenticate. – Sucrose 23/2, 2013 at 13:55

I upgraded to the latest SDK (I had 1.0.29 or something, and now I have 1.0.31 (is that what you meant by 1.0.3?) and it now pops up. – Sucrose 23/2, 2013 at 15:51

@Sucrose Be sure you have "Settings->Developer Options->USB" debugging enabled. Then attach your device to a host, then your device should show a pop-up; you only need to confirm you trust this host. – Jeramyjerba 25/2, 2013 at 9:56

@Pointy please see my answer to crdx above – Jeramyjerba 25/2, 2013 at 9:56

@Jeramyjerba as far as I can tell the Nexus 7 tablet doesn't do that. – Divert 25/2, 2013 at 14:38

@Divert are you sure that you have Android 4.2.2 ? – Jeramyjerba 25/2, 2013 at 15:46

@Jeramyjerba Android 4.2.2, Build JDQ39 - I'm in dev mode, and the tablet says so, but plugging it in to my workstation results in no popup or anything. – Divert 25/2, 2013 at 15:54

... but adb version is only reporting 1.0.29; that's odd because I just installed it a few days ago ... – Divert 25/2, 2013 at 15:55

P

13

 adb kill-server
 adb start-server

that solved my problem

Pericarditis answered 17/1, 2012 at 13:21 Comment(1)

I used to re-plugin usb wire, This solution freed my hands. – Schwartz 7/1, 2021 at 20:18

W

11

I've had a similar issue with one of my phones. I was unable to connect and use usb debugging on any of my computers. In the end, I had to restart the usb debugging on the phone manually [doing so using the Developer menu was not enough].

There's only one command you have to run on your phone [I did it using Terminal Emulator app]:

adb usb

And that was it.

Hope this helps someone in the future.

Wyant answered 25/8, 2012 at 10:33 Comment(3)

This was my issue. I had switched to using ADB over wifi by typing "adb tcpip 5555" and then tried to use ADB when the wifi was down. You can end up in quite a bind if you don't have a terminal installed on your device! Crazy that there isn't one included by default. – Justifiable 26/8, 2013 at 23:37

hmmm I just installed Terminal Emulator and tried using that command, but it said the command wasn't found. how did you manage to get adb commands on the device itself? – Phil 12/2, 2015 at 5:23

@Phil hm, just typed the command, I had to do nothing. Tested on Galaxy S2 and S5. – Wyant 7/4, 2015 at 8:6

A

10

You may also try downloading newest version of adb http://developer.android.com/tools/help/adb.html

Antispasmodic answered 7/2, 2013 at 2:32 Comment(2)

This is the solution if you just upgraded to Android 4.2.2; they added a thing where you need to whitelist a computer before it can debug the phone, and the old SDK doesn't support it – Chancellorship 21/2, 2013 at 8:3

That's what it was for me...the adb in my path was from 4.2.1, instead of the one in my build system, 4.2.2. – Himes 22/2, 2013 at 16:40

U

5

Reboot the device. This always fixes it on Mac OS, whereas adb kill-server does not.

Untutored answered 20/9, 2012 at 3:43 Comment(0)

A

5

On my Galaxy Nexus with Android 4.2.2, I had the same problem initially, 'adb devices' was showing the device but with offline status (USB debugging was initially active on my device).

These are the steps I took to remedy the situation :

Disable USB debugging (Device not connected to PC)
Re enable USB debugging
Now connect to your PC, now a pop up on the device (not on PC) will ask you for authenticating the PC, Thats it...

adb devices now lists both device id and no offline.

Antifriction answered 23/2, 2013 at 13:28 Comment(2)

This is very likely the problem I'm having as it only started when I upgraded to 4.2.2, however, no matter what I do I can't get any popup to appear that asks me to authenticate. – Sucrose 23/2, 2013 at 13:54

I upgraded to the latest SDK and it now pops up. – Sucrose 23/2, 2013 at 15:51

P

3

I post here my question just in case is helpful for somebody else. My problem was that my colleague was connected to the same device and I was not able to connect to the same device.

Note: I had this problem with Amazon Fire TV connecting over Wifi.

There are 2 solutions:

Easy to "drop" his connection (sorry buddy :)

Restart the device
adb kill-server
adb start-server
adb connect device-ip

A bit more difficult but two clients can use the same device (use different TCP ports)

Please look at this answer

Pourpoint answered 25/11, 2016 at 10:59 Comment(0)

H

2

For me with Android 4.1.1 only rebooting device works

Hayfork answered 24/4, 2013 at 19:19 Comment(0)

E

1

Run SDk Manager and install Android SDK Tools and Android SDK Platform-tools updates. ADB must be updated to a new version for 4.2.x

Electroplate answered 9/3, 2013 at 10:38 Comment(1)

That's it. Also, please remember that sometimes you [or something else] may install adb in a different location and create a symlink in /usr/bin . Make sure you run the correct, updated, one – Wyant 19/2, 2015 at 7:58

P

1

I had the same issue and none of the other answers worked. It seems to occur frequently when you connect to the device using the wifi mode (running command 'adb tcpip 5555'). I found this solution, its sort of a workaround but it does work.

Disconnect the usb (or turn off devices wifi if your connected over wifi)
Close eclipse/other IDE
Check your running programs for adb.exe (Task manager in Windows). If its running, Terminate it.
Restart your android device
After your device restarts, connect it via USB and run 'adb devices'. This should start the adb daemon. And you should see your device online again.

This process is a little lengthy but its the only one that has worked everytime for me.

Pleiades answered 30/5, 2013 at 7:55 Comment(0)

F

1

Had this on client's machine it turned out he had an out of date version of adb installed via website offering adb and fastboot. The client in question didn't want to install the whole SDK because of perceived bloat :S .

So if you're seeing offline make sure you've downloaded and using the latest adb. I ended up emailing him adb executable.

Also worth checking that the adb you are using is the correct one in the Path. i.e on Mac

$ which adb
/Users/me/dev/adt-bundle-mac-x86_64/sdk-macosx/platform-tools/adb

Faunia answered 22/10, 2014 at 8:34 Comment(0)

U

1

if non of the steps work from the above. my device still offline after connected through wifi. i did the following:

go to your device...

go to settings.
go to developer options.
Allow adb debugging in charge mode only.
repeat the steps as you always do . which is:

a. connet your usb on chargemode only. b. open command write: - adb tcpip 4455 - adb connect 192.168.1.11:4455 b. disconnect usb.

now everythings work for me .

Unpriced answered 17/7, 2020 at 6:17 Comment(0)

A

0

make sure the device is set for usb debugging
Have the adb client running (e.g. via "adb usb" or adb start-server"
LEAVE the device connected via usb!!!
AND THEN reboot the device.

This always brings my Motorola MB525 "online" again, after adb complains it would be "offline". I'm using OSX btw.

Anchoveta answered 10/6, 2012 at 20:12 Comment(0)

O

0

I made adb working on Android 4.4.2 with GT-N8010 (Samsung tablet) after setting device in authorized mode once upgraded adb to SDK version.

~/local/opt/Android/Sdk/platform-tools/adb
Android Debug Bridge version 1.0.32

While It did not work using :

adb version   
Android Debug Bridge version 1.0.31

Shiped in Ubuntu LTS version :

apt-cache show android-tools-adb  | grep Version
Version: 4.2.2+git20130218-3ubuntu23

This link may help then

Can't connect Nexus 4 to adb: unauthorized

Obannon answered 18/5, 2015 at 10:24 Comment(0)

H

0

After wasting hours on it, I have updated my version of adb and now adb devices shows my device online and I can run the app on it again.

Halflife answered 13/7, 2015 at 12:5 Comment(0)

B

0

also make sure adb isn't running in your processes automatically. If it's there right click open file location, figure out what is starting it, kill it with fire. Run the updated adb from an updated android sdk platform tools. This was the issue with mine, hope it helps someone.

Bewitch answered 12/8, 2015 at 20:8 Comment(0)

B

0

What did me in is was that multiple unrelated software packages just happened to install adb.exe -- in particular for me (on Windoze), the phone OEM driver installation package "helpfully" also installed adb.exe into C:\windows, and this directory appears in %PATH% long before the platform-tools directory of my android SDK. Unsurprisingly, the adb.exe included in the phone OEM driver package is MUCH older than the one in the updated android sdk. So adb worked just fine for me until one day something caused me to update the windows drivers for my phone. Once I did that, absolutely NOTHING would make my phone status change from "offline" -- but the problem had nothing to do with the driver. It was simply that the driver package had installed a different adb.exe - and a MUCH older one - into a directory with higher precedence. To fix my installation I simply altered the PATH environment variable to make the sdk's adb.exe have priority. A quick check suggested to me that "lots" of different packages include adb.exe, so be careful not to insert an older one into your toolchain unintentionally.

I must really be getting old: I don't ever remember such a stupid issue taking so endlessly long to uncover.

Basuto answered 14/1, 2016 at 19:9 Comment(0)

I

0

Check that the ADB version that you are running is newer than the version of the OS on the connected devices. For me, updating the ADB helped to get the device online.

Interim answered 22/4, 2016 at 10:28 Comment(0)

Recommended topics

Hot tags