title: Android ADB device offline, can't issue commands
body: <p>I can't connect to my device anymore using <a href="http://en.wikipedia.org/wiki/Android_Debug_Bridge" rel="noreferrer">ADB</a> through the command line or in <a href="http://en.wikipedia.org/wiki/Eclipse_%28software%29" rel="noreferrer">Eclipse</a>.</p>
  
  <p>Running the command</p>
  
  <pre><code>adb devices
  </code></pre>
  
  <p>returns the device name, but it says it's offline.</p>
  
  <p>Things I've tried.</p>
  
  <ol>
  <li>Toggled Android debugging mode</li>
  <li>Reinstalled the Google USB driver</li>
  <li>Restored the OS to a previously working backup (<a href="http://en.wikipedia.org/wiki/CyanogenMod" rel="noreferrer">CyanogenMod</a>)</li>
  <li>Swapped the USB cord</li>
  <li>Rebooted the phone/computer multiple times</li>
  <li>Updated the Android SDK</li>
  </ol>
  
  <p>I really don't have any clue what's going on. Anything else you think I can try, I'm all ears.</p>
  
  <p><strong>To be clear, if you're having this same issue the problem is probably an out-of-date SDK. As of 4.2.2 there is a security feature that requires you to confirm the RSA fingerprint of the connecting device. Open the SDK manager and update the tools! Then reboot.</strong></p>