New Security Features for ADB in 4.2.2

---

After upgrading to 4.2.2, some N10 will not be seen by any computer via USB and the only way to remedy it is to shut off USB debugging. On other devices, the computer will see the N10 even if USB debugging is enabled, but running "adb devices" will show the device as offline. This is a problem with the Nexus 7 as well.

UPDATE: Looks like this is a security feature. You will need to update to the latest version of adb if you want to keep using it with 4.2.2.

Sent from my Nexus 7 using Tapatalk HD

Re: Warning: 4.2.2 Breaks ADB and USB Debugging

---

adb works fine for me.
Actually, at first it did show up as "offline" but still worked fine. Then I toggled the adb setting, now it shows up as "device", and still works fine.

I had just finished sideloading, then I see this post - you had me going for a second there..

Sent from my Nexus 10 using xda app-developers app

I only had an issue with WugFresh's Toolkit because of it being "offline". With mskip's Toolkit I had no issues though it did state it was offline.

Originally Posted by noname580

I only had an issue with WugFresh's Toolkit because of it being "offline". With mskip's Toolkit I had no issues though it did state it was offline.

ADB works fine for me with 4.2.2 installed, and I can browse my GNex (toro) from my PC, drag/drop files, etc. All working just fine.

Just update your PC Android SDK to API Level 16 or latest

---

Android 4.2.2 brought up this limitation owing to security breach by ADB-Savy

To enable ADB on your PC, Update your Android SDK-r16 or LATEST, Update the system path for Platform tools --> Execute ADB cdevices command --> check the Device --> Tap Allow on Pop-up. Thats it!

Android Dev site comments :

"When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer. This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog. This requires that you have adb version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher."