14

I'm trying to interface my nexus 7 with my linux mint machine. The device always shows as offline. I understand that this problem comes from having an adb older than 1.0.31. I keep installing the platform tools rev 21.1 which as of last month is the newest version which should install adb 1.0.31, but every time I run the command 'adb version' it comes back saying it is version 1.0.29. Is there another way to get it to upgrade?

user2045139
  • 141
  • 1
  • 1
  • 5

8 Answers8

34

This solved this problem (running old adb) on Ubuntu:

  1. unplug device
  2. adb kill-server
  3. adb version
    • Android Debug Bridge version 1.0.29
  4. cd to android sdk dir
    • cd /home/XXX/adt-bundle-linux-x86_64/sdk/platform-tools/
  5. copy new adb to /usr/bin
    • sudo cp adb /usr/bin/
  6. adb version
    • Android Debug Bridge version 1.0.31
  7. adb kill-server
  8. adb devices
    • daemon not running. starting it now on port 5037 *
    • daemon started successfully * List of devices attached
  9. plug in the device, and on the device dialog about RSA appeared
  10. accept on device
  11. adb devices
    • List of devices attached
    • 04cefca0e29085aa device
CoPLaS
  • 1,727
  • 12
  • 21
  • This worked for me! I wanted to add, after step 5, I had to close Terminal and re-open. Thanks! – Jameo Sep 16 '13 at 18:33
  • Wow!! This actually helped me a lot.. I had not updated the adb.. I had updated the SDK manager but the adb was still using the old version i.e 1.0.29 not the new one 1.0.31. The steps listed above were very helpful... Now cmd identifies it as a device and no longer shows it as "offline" (Android devices 4.2.2) –  Sep 19 '13 at 17:39
  • 2
    This case is also valid for Windows. The difference is that the folder you should be checking is C:\Windows or C:\Windows\System32 – Syakur Rahman Apr 30 '14 at 02:39
2

Answer for Windows:

You need to check where's your latest driver located and put this value in PATH system variable. To do so:

  1. Open Android SDK Manager (Android Studio/Tools/Android/SDK Manager; or from Eclipse).

  2. In the top left corner (just under menu) you'll see "SDK Path". This is where latest driver located.

  3. Open Control Panel\System and Security\System, click on "Advanced system settings", find button "Enviroment Variables...".

  4. Find the PATH variable in the list (check both lists). Find the old platrorm-tools path. Replace the old path to new onreplace what you have there to SDK Path + "platform-tools" (example "c:\Android2013\sdk\platform-tools").

Mike Keskinov
  • 11,614
  • 6
  • 59
  • 87
1

Following two steps can be performed to solve this issue.

  1. May be there is another adb running in the background. Use adb kill-server to stop the adb servers, and restart adb.

  2. If you want to update adb, it can be done by running SDK Manager from the install SDK location. Upgrade "Platform Tools" to upgrade adb.

  3. The problem stated above may be the same as following. Please check the following post.
    Android 4.2.2 - adb offline, even after SDK upgrade

Community
  • 1
  • 1
Yasir Malik
  • 441
  • 2
  • 9
  • Thanks for your replies. I actually have tried killing the server and restarting, unplugging the device, restarting the computer and the nexus, turning off and on usb debugging on the nexus, reinstalling the sdk and upgrading the platform tools several times over from the manager and from the commandline. – user2045139 Mar 11 '13 at 16:25
  • My sdk versions are currently: API 17, SDK Tools Rev. 21.1 and platform tools 16.0.2. These are the newest tools available, yet somehow when I run the command "adb version" it returns "1.0.29" which is too old to use in debugging an android 4.2.2 device. Does anyone know where I can just download a newer copy of adb? – user2045139 Mar 11 '13 at 16:26
0

You should first check whether proper drivers are installed for your device or not. The following link can help you.

http://developer.android.com/tools/device.html

Also, if you want to upgrade adb there is another way for that. Go to: https://launchpad.net/ubuntu/+source/android-tools/

Click on the quantal version (4.2.2-something). Download the .xz, .dsc, and .tar.gz and ten:

# sudo apt-get build-dep android-tools

# sudo apt-get install libselinux-dev

# dpkg-source -x android-tools*.dsc

# cd android-tools*

# fakeroot dpkg-buildpackage

# cd ..

# sudo dpkg -i android-tools-adb*

This solution was presented here: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1131163

Community
  • 1
  • 1
Yasir Malik
  • 441
  • 2
  • 9
  • Thank you so much. Your directions for updating the adb worked! It debugs every time now! Now I can get on with my project. – user2045139 Mar 12 '13 at 16:51
0

Best solution i found ever is:

  1. Check ur adb version by using command: adb version for windows and ./adb version for Linux system
  2. if it showing 1.0.29 please upgrade it to 1.0.31 because 1.0.29 will not rspond for JB 4.2.X
  3. it will fix ur device offline problem
  4. if ur system already have the new adb(1.0.31) and facing this problem, in that case open sdk and upgrade plateform tool to 16.0.1
  5. restart ur device atleast one time.. :) it will work fine for all the devices...
CSᵠ
  • 10,049
  • 9
  • 41
  • 64
JAGDEESH GAIRA
  • 89
  • 1
0

None of these worked for me.Updating the sdk still showed the older 1.0.29 version. I downloaded the 1.0.31 version from here and replaced the old adb with this and it worked. Now the device is recognized by adb in 4.2.2. Hope this helps someone and saves some time.

thrift
  • 1
0

I resolved this problem on my Windows machine by following these steps:

  1. Install updates from SDK Manager
  2. Copy the corresponding adb files (dlls and exe) to C:\Windows\System32
  3. adb kill-server
  4. adb version

Android Debug Bridge version 1.0.31

Gabriel Mongeon
  • 7,251
  • 3
  • 32
  • 35
tinasuk
  • 1
  • 1
0

I got it resolved by updating the Android Studio.

you can get the update by choosing Help > Check for Updates
(Android Studio > Check for Updates on macOS)

zeeawan
  • 6,667
  • 2
  • 50
  • 56