driver issue - Nexus 4 not recognised

Hi,

I'm trying to write an Android application, but my PC (Windows 7 Professional 64bit) will not recognise my Nexus 4 Android phone for testing and debugging. At the console, the list of devices is empty when I issue the command "adb devices" in the ADT folder: ...\sdk\platform-tools\ (however, on my Linux laptop my phone shows up in the list confirming that the cable is okay and the phone is in developer/debug mode).

I've tried following the instructions here, here, here, and here
... in short the things tried are: checked the LG site for drivers (there are none), download latest Google USB drivers, ensured the phone is in developer mode and USB debugging is enabled, installed the latest drivers via Device Manager (via 'Have Disk' and 'install anyway' or on another attempt by adding the device ID strings to the inf file); I've tried putting the phone in MTP and PTP mode, tried getting the latest drivers via the Android SDK manager, and even tried disconnecting the phone, removing all nonpresent devices, deleting INFCACHE.1 from System32\DriverStore\ then rebooting. Twice.

But the phone still doesn't appear in the list of adb devices.

I'm utterly stumped.
Please help!

Thanks,
Martin

Perhaps the talk of android development and ADB is over-complicating the issue. The fact is, the phone does not even appear as a media device that I can read/write files to. I think if this part could be made to work then I could carry it the rest of the way to get the Android developer stuff working.

Furthermore, I've also noticed today that Windows cannot find a driver for my Microsoft LifeCam VX-800 (and there is no option to download a driver from the website because, allegedly, Windows will find it automatically).

Anyone?

Is there anything I can do to provide more diagnostic information so that someone might be able to help resolve this?

I thought the days were behind us of Windows 'clogging up' to the point where only a reinstall of the OS would fix things, but with over three days and 400+ views without a single reply to the topic I'm beginning to fear that's becoming my only option!

Progress! :)

I ran CCleaner, Malwarebytes, and MSE antivirus but found nothing (aside from typical registry issues identified by CCleaner), then I ran the Intel Driver Update Utility and updated to the latest chipset drivers (& rebooted), I ran the Microsoft hotfix here and ran the Microsoft Diagnose and fix Windows USB problems automatically FixIt Tool ... but none of this helped the situation at all. (I just include it here for reference in case any of these things prove useful to others in a similar situation)

Eventually, I tried Solution 5 from the guide found here, i.e. I uninstalled my Generic USB Hub devices and rebooted. At first this caused a much bigger problem because my front USB ports and card reader all stopped working due to Windows failing to recognise/install the Generic USB Hub device that I'd just uninstalled!! (i.e. the same problem that I was finding with any USB device which wasn't already installed/configured in Device Manager). So to address this I tried having the update utility automatically search online as well as pointing it at 'C:\ plus subfolders' (a lengthy search which still did not resolve the matter). Then browsing online for answers to this new problem I eventually found this thread and tried the advice in the reply by Klaus J Isbruch, in short: browse manually for drivers and enter "c:\windows\winsxs"

This did the trick! The Generic USB Hub was found and installed successfully and then as I plugged in each of the other devices that Windows could not previously install I now saw that it now found appropriate drivers straight away! So my webcam is online and the Nexus 4 phone is recognised. I issued the "adb devices" command in the Android Developer Toolkit and my device was listed, so I loaded up Eclipse and tested my app which is now running in debug mode on my phone! (About time too!!)

I've no idea what when wrong or quite how & why this process fixed it. I've not been this &*$#ed off with Microsoft software since Windows ME, but at least it's working now.