Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

After upgrade Android on Nexus to 4.2.2, Eclipse shows target unknown for device?

I just upgraded my phone to 4.2.2, but now i cannot use it in eclipse anymore.

enter image description here

I tried rebooting the device, reset my debug-settings but I cannot get it to work anymore.

I saw it is already a registered issue. There are some new security enhancements, so there should be a dialog (see here at bottom) but this dialog doesn't appear. I don't have several accounts on the phone, which is pointed out in the issue..

Anyone any suggestions?

EDIT: Look at accepted answer below, this should cover all cases. In my case, there were some packages missing, which weren't shown in the Android SDK Manager. I just found the Packages -> Reload in the Android SDK Manager... And I thought this happens automatically

like image 976
longi Avatar asked Feb 22 '13 19:02

longi


3 Answers

You need three things in order to make sure this update goes smoothly:

  1. Make sure your device is actually running 4.2.2 and the problem is not something else
  2. Your SDK is updated to the latest tools. The adb binary in all but the latest version does not support the 4.2.2 security enhancements.
  3. You are on the main account of your device in case of multiple user accounts.

Connect your Device to your computer and execute adb devices (make sure USB debugging is enabled). You should see something like this:

3tiu52839ry082j3 offline

Right about now, there should be a dialog on your device that looks something like:

enter image description here

Check the Always allow from this computer box if you want and click OK.

That's about it.

Some other things to check:

  • Make sure your USB cable isn't broken. Sometimes, the smaller cables break inside the main one, and your device may charge but have no data connection. Try with a different cable, or try accessing files on the device over USB (this will go fine if your cable is fine)
  • Make sure you're using the newest version of adb. Even after I updated my SDK tools, I couldn't get my device authorized when using adb. I eventually figured out that the Nvidia install of the NDK and SDK tools had updated my PATH variable to use the adb from that install, which wasn't the latest update. By using the adb in my newly updated install, I was able to get it all working.
like image 104
Raghav Sood Avatar answered Oct 18 '22 23:10

Raghav Sood


For me it was solved by changing Nexus 7 tablet to "Camera(PTP)" mode. Check out this blog post on how to do it. After USB connection of Nexus 7 and confirming digest on Nexus 7, also connecting through TCP/IP with ADB worked.

like image 10
zhivko Avatar answered Oct 18 '22 22:10

zhivko


Wierdly, unchecking and rechecking the "Allow USB Debugging" option popped me the window and selecting "ok" solved my problem.

like image 3
ckp Avatar answered Oct 18 '22 22:10

ckp