Looks like there are very many possible causes for this. Mine was one of the more unusual.

I updated SDK Tools to 21.1 and Platform-tools to 16.0.1. Verified with adb version that I am running v1.0.31. My development machine is running Windows 7, x64. I have four 4.2.2 devices to test with, a Galaxy Nexus with unlocked bootloader but not rooted, and Nexuses One, 4, 7 & 10, all stock. The Nexus One, being. It turns out I had my ANDROID_SDK_HOME environment variable pointing to an old location which no longer existed.

It hadn't caused any other problems (strangely) but it appears to have been preventing the RSA authentication process from happening. Probably should've seen it when I was checking the PATH variable the other week, but never mind. I found the strange location by running the following and checking the readout: adb kill-server set ADB_TRACE=all adb nodaemon server After updating the location and restarting my PC, it's now working just fine. Thanks to all who responded. I had the same problem and setup. Windows 7, x64, Eclipse Indigo, one user on the device etc.

Android Debug Bridge version 1.0.29. - run remote shell interactively adb shell. - run remote shell command adb emu command. If file is deleted from your desired shared host first try checking different host by clicking on another file title. If you still have trouble downloading.

I tried adb devices using v1.0.31 and under no circumstances did I see a pop up on the device. I tried all sorts of combinations of turning on/off debugging, plugging the USB back and forth, restarting the device etc. Nothing worked. I also tried rooting the device in order to manually copy over the finger print file. However, the device went down beyond repair (not to recommend to anyone). I have more than one Nexus 10 so kept on trying with the other ones.

I am using bootcamp though (using Windows on a Mac laptop) so one last attempt was to try the same thing under OSX. On the first attempt doing./adb devices from the terminal, the popup showed up.

Install vshare on ipad. Download and Install vShare on iOS 9 (iOS 9.0.1, iOS 9.0.1, iOS 9.0.2, iOS 9.1, iOS9.2 and iOS 9.3): vShare for iOS 9 can be installed directly following this simple process. That’s the main reason of this post. If your device is not jailbroken probably you’ll get a minimal error after installation but the following instructions will have the simple steps to fix it.

I accepted the fingerprint and now it's working in OSX. I prefer Windows over OSX so this is not an ideal workaround as I still can't get it to work in Windows. I'll keep an eye open for solutions to this but in the meantime, I hope this helps other people with bootcamp issues. All I can say is the same from above. These are all of the steps that I did to get mine to work. Un-installing all drivers for this phone and other android phones previously used.

Also, if you have any tethering apps installed un-install them as well (pda-net etc). Make sure 'all' updates are complete in Android SDK Manager. Reboot computer and phone. Plug phone in and install the Google drivers from sdk folder.

Reboot again 7. Plugin phone. Mine finally worked after this whole process. – Mar 15 '13 at 16:59. I had this very problem, and found an answer: Either I fat fingered the phone or was not paying attention or it simply did not pop up saying here is the RSA pubkey check to allow for computer, I kept getting offline status.

I followed every direction on the map, from having a LONG list in my rules file to reinstalling ADB 50 times. Yes it does need to be version 1.0.31, which I have. If this is you then read on. Disconnect your device. Use these commands in the terminal, assuming you are using BASH. Adb kill-server sudo bash cd ~ mv.android BAK.android Now that you have effectively removed the initial RSA key, make sure USB Debugging is enabled on the device.

Re-connect the device and pay attention to the screen. Make sure to check the 'remember this computer' box. Problem solved. I had the same problem as OP but originating from an adb.exe copy in C: Windows, much like user1269737 appeared t have. This had precedence in Windows PATH, so no matter how much I updated he SDK, it wouldn't help as the updated ADB wasn't being used.

Someone told me it might have been a version of the Android Studio bundle that installed it there (go figure.). I can't confirm it because: 1. Current AS bundles don't appear to be doing this and. I install a lot of ROM flashers/tools that bundle ADB (XDA Developers stuff).

So I can't confirm it was Android Studio. Protip: use adb version and where adb commands in cmd to check what version you're using and which executable you are running. I tried all the these things and still couldn't get Windows to display the RSA prompt on my Android device. After hours, this is how I got it working: • Connect device to PC via USB • [Windows Key] + [R] > [type] devmgmt.msc • Locate your device in the list • [Right Click] > Uninstall • Download Google USB Driver package: • Extract the zip to your desktop • Back to devmgmt.msc > [Right Click] root of the tree > Scan for Hardware Changes • Locate your device in the list • [Right Click] your device > Install > Choose/Browse files • Browse to the usb_driver folder you extracted to your desktop • Windows will use the Google USB driver instead of the driver for your phone. My problem was that the LG driver was installed on Windows. Once I deleted that and installed the google driver, it works perfectly.