[android-developers] Unable to authorize adb on Windows 7 after set of 10/8/13 Microsoft patches applied
I have a new problem with my Android development environment. In it's simplest form, I have a Windows 7 PC and a stock unrooted Nexus 4. I have been developing via this environment for at least six months. I'm using the ADT bundle. I've on R 22.2.1 SDK tools. My ADB is 1.0.31. Basically, from what I can tell, I've got the latest everything, except not the latest Android Studio stuff. I'm primarily work with my Nexus 4, but every once and a while, I try it out on a Nexus One and a Nexus 7.
This environment has been working well form me for at least the last six months. On Thursday 10/10/13, I installed all this months Microsoft patch Tuesday updates. My system was working fine on Wednesday, I installed the updates on Thursday. On Friday, I got back to work and was not able to connect adb to my Nexus 4.
Obviously I have looked online for a solution. The thing that is actually surprising me here is that I fully expected other people to have this same problem. But I haven't seen a single sign that anyone else is encountering this problem. There are tons and tons and tons of people having problems with adb over the years, but that's all old stuff with old well known solutions.
I've tried so many combinations of things. Reboots. Different USB cables. Different USB ports. Different PC drivers. I've fully uninstalled the Google USB drivers and reinstalled them.
When I attempt to turn debugging on in my N4, I first turn developer options on, then I enable USB debugging. I hear the PC beep indicating that it needs to do some driver stuff. From what I can tell, that is all working. When I run the old 'adb devices', I get the serial number of the N4 followed by "unauthorized". On the device, the authorize dialog never appears. I used to have this PC set as remembered by the device. I've tried the "Revoke USB debugging authorizations" many times.
I have tried every combination of enabling developer options, MTP vs PTP modes, and setting these before and after the device is physically connected to the computer.
Here are a few key this works and that doesn't work facts. My primary PC is Windows 7. ADB will work with my Nexus One. It will not work with my Nexus 4 and Nexus 7 (both are running stock unrooted 4.3). This makes me think the problem is in the authorization part of things vs a basic connectivity thing.
I have access to a Vista machine. I applied all the Microsoft patches for this month to that Vista machine, and it does not have this problem. Vista fine, Windows 7 not fine.
fastboot is able to communicate with the N4.
I was going to roll back the Microsoft updates, but I do not have a system restore point old enough available.
I'm open to trying anything I've already tried over again, but I really think this is a new problem. Although, since I'm the only one who seems to have this, who knows.
I am completely making this up. It's like adb doesn't know who the PC is anymore, but doesn't know it doesn't know, so when it sends the 'do you authorize me' command to the N4, it's sending an invalid fingerprint, and the N4 silently ignores it.
Anyway, thank you for any help. Lee
-- This environment has been working well form me for at least the last six months. On Thursday 10/10/13, I installed all this months Microsoft patch Tuesday updates. My system was working fine on Wednesday, I installed the updates on Thursday. On Friday, I got back to work and was not able to connect adb to my Nexus 4.
Obviously I have looked online for a solution. The thing that is actually surprising me here is that I fully expected other people to have this same problem. But I haven't seen a single sign that anyone else is encountering this problem. There are tons and tons and tons of people having problems with adb over the years, but that's all old stuff with old well known solutions.
I've tried so many combinations of things. Reboots. Different USB cables. Different USB ports. Different PC drivers. I've fully uninstalled the Google USB drivers and reinstalled them.
When I attempt to turn debugging on in my N4, I first turn developer options on, then I enable USB debugging. I hear the PC beep indicating that it needs to do some driver stuff. From what I can tell, that is all working. When I run the old 'adb devices', I get the serial number of the N4 followed by "unauthorized". On the device, the authorize dialog never appears. I used to have this PC set as remembered by the device. I've tried the "Revoke USB debugging authorizations" many times.
I have tried every combination of enabling developer options, MTP vs PTP modes, and setting these before and after the device is physically connected to the computer.
Here are a few key this works and that doesn't work facts. My primary PC is Windows 7. ADB will work with my Nexus One. It will not work with my Nexus 4 and Nexus 7 (both are running stock unrooted 4.3). This makes me think the problem is in the authorization part of things vs a basic connectivity thing.
I have access to a Vista machine. I applied all the Microsoft patches for this month to that Vista machine, and it does not have this problem. Vista fine, Windows 7 not fine.
fastboot is able to communicate with the N4.
I was going to roll back the Microsoft updates, but I do not have a system restore point old enough available.
I'm open to trying anything I've already tried over again, but I really think this is a new problem. Although, since I'm the only one who seems to have this, who knows.
I am completely making this up. It's like adb doesn't know who the PC is anymore, but doesn't know it doesn't know, so when it sends the 'do you authorize me' command to the N4, it's sending an invalid fingerprint, and the N4 silently ignores it.
Anyway, thank you for any help. Lee
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
posted by twitter @ 6:16 PM
0 Comments
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home