Related
Does anyone know if the Galaxy S is supposed to transfer drivers when attached to a machine via usb? I've tried installing samsung usb drivers/multiple kies versions on both xp and windows 7 x86 machines however I've not once got the device installed. The first machine I tried it on did register the device Samsung_android had been attached however after factory resting it now appears as 'unkown. If it does install drivers, would it be possible to retrieve them from the galaxy s source? Would flashing the phone with a custom rom include the device drivers?
I would really appreciate any suggestions, I love the device but I've been trying to resolve this issue since I bought the phone
By default it uses Kies when you connect it via USB, go into options - About Phone - USB Settings and choose "ask me what to do" then you can choose MTP to mount it as a USB drive, choose it as a modem, etc. You need to go into the slide-down notifications menu and click on MTP mode then. For Mac's you need to enable USB debugging as well.
Thanks for your reply however I've tried connecting using each of the connection options. I am given the option to mount the internal SD card and lists 'MTP conneced' but the machine it's connected to still lists 'unkown device' within dev manager. I've also tried enabling USB debugging but even adb doesn't list the galaxy s.
Regardless of the device setting windows still displays 'device not recognized'. I've looked at the drivers within samsung\usb_driver but the folders are listed by development alias so its hard to determine which driver is for the i9000 I read on a forum that someone had this problem and Samsung replaced the drivers on the galaxy, I'm not sure if that's true or it was some other fix but if the galaxy does provide the machine with drivers maybe I can extract them and install directly to the machine
I don't have access to the NAND as I have not rooted it, but if you want I can do a directory listing of the internal SD and you can see what you are missing. I can then copy the files for you.
Tachikoma_kun said:
I don't have access to the NAND as I have not rooted it, but if you want I can do a directory listing of the internal SD and you can see what you are missing. I can then copy the files for you.
Click to expand...
Click to collapse
I like this community already, thanks mate but you don't have to go to the trouble. I returned the device to vodafone for a replacement. The replacement connected first time and I can now access the device without any problems
No doubt others will have this issues so...
Galaxy S "unknown Device" - If you have tried
Installing Samsung USB drivers for your operating system (There are both x86(32bit) and x64(64bit) versions of these drivers for windows.
Setting the Galaxy S to MTP on usb connect (Settings>About Phone>USB settings
Resetting your Galaxy S to factory settings (Settings>Privacy>Factory Reset)
Enabling usb debugging (Settings>Application>Development)
Formatting your internal SD card (Settings>SD Card..) Unmount before and re mount after formatting
Installing various versions of keis bloatware
and your Galaxy S is still listed as "unknown device" within windows device manager. Try taking it back to the store and asking for a replacement, this was the only step which worked for me and it worked first time Remember to explain all the steps you've taken and if you have to, ask for a demonstration of the device successfully connecting before you accept that there isn't an issue.
No worries, glad you are sorted now.
Ok, I've just upgraded to windows 7. I was pretty psyched about the whole thing, and my computer seems like a whole new machine, coming from XP 32 bit.
So one thing I'm attempting to get adb to work with my phone. Heres my first problem - right off the bat, my computer doesnt recognize my phone as anything but an unknown device. YES I'VE TRIED DEBUGGING, DISK DRIVE, ETC., but nothing works.
I go to device manager, all I see is unknown device. Ok fine. I download the adb files that allow you to download the Android 2.1 thing and usb drivers. Still nothing works. I go to device manager, try to update the drivers for said "unkown device" and i get a message "the drivers are the newest up to date" or something. I try downloading the 64-bit HTC Hero drivers, same thing. I download and install HTC Sync, same thing.
I get this message when I plug the phone in...
"USB Device not recognized
One of the usb devices attached to this computer has malfunctioned, and Windows does not recognize it. For assistance in solving this problem, click this message"
So my question is, how do i get my computer to recognize my phone, even as storage device??
jasongthang said:
Ok, I've just upgraded to windows 7. I was pretty psyched about the whole thing, and my computer seems like a whole new machine, coming from XP 32 bit.
So one thing I'm attempting to get adb to work with my phone. Heres my first problem - right off the bat, my computer doesnt recognize my phone as anything but an unknown device. YES I'VE TRIED DEBUGGING, DISK DRIVE, ETC., but nothing works.
I go to device manager, all I see is unknown device. Ok fine. I download the adb files that allow you to download the Android 2.1 thing and usb drivers. Still nothing works. I go to device manager, try to update the drivers for said "unkown device" and i get a message "the drivers are the newest up to date" or something. I try downloading the 64-bit HTC Hero drivers, same thing. I download and install HTC Sync, same thing.
I get this message when I plug the phone in...
"USB Device not recognized
One of the usb devices attached to this computer has malfunctioned, and Windows does not recognize it. For assistance in solving this problem, click this message"
So my question is, how do i get my computer to recognize my phone, even as storage device??
Click to expand...
Click to collapse
try uninstalling htc sync and using a different usb port. does that work?
And to address how to get it to recognize as a drive, when you plug it in you should be presented with options where you can make it a disk drive. Or pull down your notification bar and change the type.
elegantai said:
And to address how to get it to recognize as a drive, when you plug it in you should be presented with options where you can make it a disk drive. Or pull down your notification bar and change the type.
Click to expand...
Click to collapse
On the phone yes, I can select a different type. On my computer, I just get that unknown device message.
And out of the blue I just tried a different USB port, and now it works as a storage device.
Did you restart the computer after installing the drivers? Sometimes mine gets a little goofy like that.
jasongthang said:
On the phone yes, I can select a different type. On my computer, I just get that unknown device message.
And out of the blue I just tried a different USB port, and now it works as a storage device.
Click to expand...
Click to collapse
i had that issue with one of my usb ports too. i think sometimes a bank of usb ports are used as basically a usb hub, and the evo doesn't like that, from what i understand.
Reboot comp, reboot EVO. Connect 'em, and then go into Device Manager, uninstall the "unknown device" (EVO), and then have it scan for new devices. Now, when it says scanning for drivers (or something to that effect) look for an advanced or "skip checking Windows Update for drivers" option. Then navigate to the ADB drivers in the Android SDK and tell it to use those. Make sure you have USB Debugging turned on, and EVO's set for "Charging Only".
If that still doesn't work, then there's an incompatibility with your computer's USB controller and Win7.
drmacinyasha said:
Reboot comp, reboot EVO. Connect 'em, and then go into Device Manager, uninstall the "unknown device" (EVO), and then have it scan for new devices. Now, when it says scanning for drivers (or something to that effect) look for an advanced or "skip checking Windows Update for drivers" option. Then navigate to the ADB drivers in the Android SDK and tell it to use those. Make sure you have USB Debugging turned on, and EVO's set for "Charging Only".
If that still doesn't work, then there's an incompatibility with your computer's USB controller and Win7.
Click to expand...
Click to collapse
lol, I did all that a few times, but im sure its not an incompatibility issue. probably just a skipped step somewhere.
jasongthang said:
lol, I did all that a few times, but im sure its not an incompatibility issue. probably just a skipped step somewhere.
Click to expand...
Click to collapse
If your computer is old enough, incompatibility is a possibility. See if there's other ports you can use, like on a different side of the case. Also, what brand computer?
--Swyped from my EVO using XDA App.
drmacinyasha said:
If your computer is old enough, incompatibility is a possibility. See if there's other ports you can use, like on a different side of the case. Also, what brand computer?
--Swyped from my EVO using XDA App.
Click to expand...
Click to collapse
stop! lol its fine. it works. i guess i should have stated that i've been on these forums for quite a while, and have flashed and rooted a few different phones using this computer, but with xp.
i just switched to windows 7, and of course lost all my drivers, and everything I had saved would have to be switched to 64-bit. I just couldnt get anything to work, but it seems to work now.
and I dont know what brand necessarily this computer is. i built it. I do have a dell keyboard though.
Hi.
Have Boostmobile Epic that came unrooted.
Downloaded drivers and phone shows in device manager under com ports.
Tried 11 USB cables then saw a video from qbking and bought a blackberry to use its cable making it 12 cables, none work.
Tried 2 computers with Vista and Win 7 x64.
Epic won't communicate with either comp with debugging on or off.
As i said in topic, one click root won't work. Says Phone is not connected.
I also cannot sideload content onto SD card because it does not show in My Computer.
It has been flashed to boost so i assume it has communicated with a PC in the past.
What can i do to fix this?
Reboot pc and phone then try again. If that doesn't work then uninstall drivers from pc then install again. Reboot pc after install after reboot plug in epic then wait for it to finish installing drivers then reboot both again then use odin.
You can also connect the phone with usb debugging on, then go into device manager on the computer and look for "other" or samsung android in USB section. Click on that and select update drivers and let windows update search and install drivers...it takes awhile.
just did the uninstall drivers then reboot both thing.
Driver installation shows device ready to use as...
SAMSUNG USB Composite Device
SAMSUNG Mobile Modem #2
SAMSUNG Mobile Modem Diagnostic Serial Port (WDM) (COM5)
All ready to use.
But Still not showing in my computer for file transfer or working in usb debugging mode for root.
PHug said:
just did the uninstall drivers then reboot both thing.
Driver installation shows device ready to use as...
SAMSUNG USB Composite Device
SAMSUNG Mobile Modem #2
SAMSUNG Mobile Modem Diagnostic Serial Port (WDM) (COM5)
All ready to use.
But Still not showing in my computer for file transfer or working in usb debugging mode for root.
Click to expand...
Click to collapse
Try the update driver choice in device manager. The CDC driver is missing. I think it loads 5 drivers if I remember correctly with USB on...yeah the mass storage driver is missing too. Let Windows update find them all.
kennyglass123 said:
Try the update driver choice in device manager. The CDC driver is missing. I think it loads 5 drivers if I remember correctly with USB on...yeah the mass storage driver is missing too. Let Windows update find them all.
Click to expand...
Click to collapse
Hi, thanks for help.
Just tried uninstalling everything and letting windows find drivers. Windows found a different driver package from S3 studio or something but I still get no mass storage or root.
I've read you can root and install roms without a computer Guess that will have to be my route.
As far as mass storage goes... It's annoying but I pulled the back off and put SD card directly into computer
You are sliding down the pulldown on your epic screen and pushing mount sd card for mass storage right?
jbadboy2007 said:
You are sliding down the pulldown on your epic screen and pushing mount sd card for mass storage right?
Click to expand...
Click to collapse
Yeah, the robot pic turns from green to orange but it never actually connects to either computer.
Going to my brothers house soon to check his 2 computers, he says his Thunderbolt will only work on one.
PHug said:
Yeah, the robot pic turns from green to orange but it never actually connects to either computer.
Going to my brothers house soon to check his 2 computers, he says his Thunderbolt will only work on one.
Click to expand...
Click to collapse
Some computers are finicky and will only work on the USB port used to install the drivers. Odin only works on the left side of my laptop and mass storage works on the right...go figure!
The fact that the phone thinks it connects and the computer probably makes the connection noise shows there is still a driver problem. Did you reboot the computer and phone after the full driver installation?
Yes I restarted both several times while installing/uninstalling
Drivers... I have just accepted that I need to remove the card to sideload content.
On a side note, I am now afraid to root my phone and change the roms because I'm on boostmobile and will be unable to connect phone to a computer to fix if something goes wrong.
Sent from my SPH-D700 using Tapatalk
after you install drivers, reboot, then plug in your phone w debugging on, it should install a bunch of drivers, then take forever on modem, unplug and replug the usb from the phone really fast, this should trip it up into moving to the next device... there should be at least two or three more. If you have GB loaded for some reason the RNDIS drivers are wonky. Make sure you use a USB port on your motherboard, not on a PCI, not on a front port... the drivers are acting weird lately, like they changed em up a bit... idunno... but once you get a setup, dont mess with it! Hope somethin helps... Its almost guaranteed the drivers, unless the Boost is the issue, idunno...
ive had that same problem ever sense ive got the phone, what if you havent given up there is another way for you to connect to your computer. It is very simple and fast it is how i connect now and it works every time.
1. Have computer on and Phone off
2. Boot your phone into ClockworkMod 3.1.0.1 (Power/camera/volume down)(it must be this version of clockwork)
3. Go to mounts and storage
4. On the bottom of the menu you must click mount usb storage.
5. Plug your phone into the computer and your computer should recognize your phone now.
Also if your on Vista / Win7 you should run the command line (cmd) or the bat file to root with admin rights: Right click cmd or the run.bat and select run as administrator and that hould help.
Sent from an Epic with 4G
I don't think the drivers for samsung are 64 bit compatable. If you got the drivers from samsung it should state that.
Sent from my lean mean drunken machine useing XDA Premium and a 12 pack of Sam Lager
tazfanatic said:
I don't think the drivers for samsung are 64 bit compatable. If you got the drivers from samsung it should state that.
Sent from my lean mean drunken machine useing XDA Premium and a 12 pack of Sam Lager
Click to expand...
Click to collapse
The ones installed through Windows Update run fine on my 64 bit Windows 7 Laptop.
kennyglass123 said:
The ones installed through Windows Update run fine on my 64 bit Windows 7 Laptop.
Click to expand...
Click to collapse
good to know.
Hey guys,
I've been wary to flash the ROM of my Nexus 7, as it actually boots into the normal OS and does everything fine.
The basic problem is that I can't transfer anything to and from the device over USB. USB debugging is on and I have tried PTP and MTP.
One of the solutions I have been looking at is bad drivers on Windows' part, and that is where I am currently blocked. If USB debugging is off, Windows refuses to acknowledge my tablet's existence. If debugging is on, some drivers from Microsoft automatically install and the tablet is labeled as "unknown device".
My USB controller is up to date with the correct drivers provided by ASUS for my motherboard (ASUS Z87-A). I recently re-installed Windows 7 to put it on a larger SSD, and with this same motherboard, it now does not detect correctly.
If I try to uninstall the "unkown device" it simply disappears until I unplug and replug in the tablet. If I try to manually direct it to the correct drivers, it tells me that the USB drivers are incompatible with my device. The USB drivers are the ones downloaded directly from Google.
I can still access the fastloader.
If you need more information, just let me know.
Allane176 said:
Hey guys,
I've been wary to flash the ROM of my Nexus 7, as it actually boots into the normal OS and does everything fine.
The basic problem is that I can't transfer anything to and from the device over USB. USB debugging is on and I have tried PTP and MTP.
One of the solutions I have been looking at is bad drivers on Windows' part, and that is where I am currently blocked. If USB debugging is off, Windows refuses to acknowledge my tablet's existence. If debugging is on, some drivers from Microsoft automatically install and the tablet is labeled as "unknown device".
My USB controller is up to date with the correct drivers provided by ASUS for my motherboard (ASUS Z87-A). I recently re-installed Windows 7 to put it on a larger SSD, and with this same motherboard, it now does not detect correctly.
If I try to uninstall the "unkown device" it simply disappears until I unplug and replug in the tablet. If I try to manually direct it to the correct drivers, it tells me that the USB drivers are incompatible with my device. The USB drivers are the ones downloaded directly from Google.
I can still access the fastloader.
If you need more information, just let me know.
Click to expand...
Click to collapse
When you first got the device, did you go straight into fastboot without booting it and plugging it in while in Android? Does that question even make sense?
Allane176 said:
Hey guys,
I've been wary to flash the ROM of my Nexus 7, as it actually boots into the normal OS and does everything fine.
The basic problem is that I can't transfer anything to and from the device over USB. USB debugging is on and I have tried PTP and MTP.
One of the solutions I have been looking at is bad drivers on Windows' part, and that is where I am currently blocked. If USB debugging is off, Windows refuses to acknowledge my tablet's existence. If debugging is on, some drivers from Microsoft automatically install and the tablet is labeled as "unknown device".
My USB controller is up to date with the correct drivers provided by ASUS for my motherboard (ASUS Z87-A). I recently re-installed Windows 7 to put it on a larger SSD, and with this same motherboard, it now does not detect correctly.
If I try to uninstall the "unkown device" it simply disappears until I unplug and replug in the tablet. If I try to manually direct it to the correct drivers, it tells me that the USB drivers are incompatible with my device. The USB drivers are the ones downloaded directly from Google.
I can still access the fastloader.
If you need more information, just let me know.
Click to expand...
Click to collapse
Use this as a possible quick-fix (not all mode combinations will work right): http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi, then reboot.
Use this as a more complete fix (recommended in your case): http://forum.xda-developers.com/showthread.php?p=50253887#post50253887
Aerowinder said:
When you first got the device, did you go straight into fastboot without booting it and plugging it in while in Android? Does that question even make sense?
Click to expand...
Click to collapse
That would have been roughly a year ago. I believe I did boot straight into the OS.
mdamaged said:
Use this as a possible quick-fix (not all mode combinations will work right): http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi, then reboot.
Use this as a more complete fix (recommended in your case): http://forum.xda-developers.com/showthread.php?p=50253887#post50253887
Click to expand...
Click to collapse
To the first quick-fix, the ADB drivers are installed, but they are not the drivers that are utilized when the Nexus 7 is plugged in. Like I said, it instantly installs some generic Microsoft drivers, and refuses to recognize the ABD drivers are compatible for the device.
As such I can't even begin with option 2.
Allane176 said:
That would have been roughly a year ago. I believe I did boot straight into the OS.
To the first quick-fix, the ADB drivers are installed, but they are not the drivers that are utilized when the Nexus 7 is plugged in. Like I said, it instantly installs some generic Microsoft drivers, and refuses to recognize the ABD drivers are compatible for the device.
As such I can't even begin with option 2.
Click to expand...
Click to collapse
With the device plugged in, go into device manager and find the device, uninstall that device, and make sure you check the box to uninstall the drivers from the system, then leaving the N7 plugged in to the PC, reboot the N7, as it comes up it should redetect, it's important to leave the device plugged in while it is rebooting.
mdamaged said:
With the device plugged in, go into device manager and find the device, uninstall that device, and make sure you check the box to uninstall the drivers from the system, then leaving the N7 plugged in to the PC, reboot the N7, as it comes up it should redetect, it's important to leave the device plugged in while it is rebooting.
Click to expand...
Click to collapse
There is no check box to uninstall the drivers: imgur.com/PhL4UNt
Where "unknown device" is my N7. Still, I tried rebooting it while leaving it plugged in, and it would not recognize correctly.
Allane176 said:
There is no check box to uninstall the drivers: imgur.com/PhL4UNt
Where "unknown device" is my N7. Still, I tried rebooting it while leaving it plugged in, and it would not recognize correctly.
Click to expand...
Click to collapse
You may want to make sure you are not using a hub or USB 3.0 port for this btw.
Put the device into in MTP mode with debugging on, unplug the device, then download these, unzip them somewhere, right click on the unknown device associated with your Nexux 7, click Update driver software, click "Browse my computer", navigate to where you saved the unzipped contents, and select usb_driver folder, let it do its thing, reboot your PC. Plug the device back in, preferably into a different USB port then what you have been using, it should then show up as a Google ADB driver (or similar), you can test it with the command: adb devices see if that works, if not, leave the device plugged in, and reboot the device.
Let me know if that works or not, and I will continue in a new post.
mdamaged said:
You may want to make sure you are not using a hub or USB 3.0 port for this btw.
Put the device into in MTP mode with debugging on, unplug the device, then download, unzip them somewhere, right click on the unknown device associated with your Nexux 7, click Update driver software, click "Browse my computer", navigate to where you saved the unzipped contents, and select usb_driver folder, let it do its thing, reboot your PC. Plug the device back in, preferably into a different USB port then what you have been using, it should then show up as a Google ADB driver (or similar), you can test it with the command: adb devices see if that works, if not, leave the device plugged in, and reboot the device.
Let me know if that works or not, and I will continue in a new post.
Click to expand...
Click to collapse
Ok, plugged directly into a USB 2.0 port at the back of my motherboard. Recognized as Unknown Device when plugged in, disappears completely when unplugged.
So, here's exactly what I did: Plugged in device -> clicked on "Update Driver software" -> unplugged device -> Browse my computer for driver software -> directed to correct location -> replies: "The best driver software for your device is already installed", and it is not using the ADB drivers.
Going into "Driver Details" tells me that there are no drivers that have been installed.
Allane176 said:
Ok, plugged directly into a USB 2.0 port at the back of my motherboard. Recognized as Unknown Device when plugged in, disappears completely when unplugged.
So, here's exactly what I did: Plugged in device -> clicked on "Update Driver software" -> unplugged device -> Browse my computer for driver software -> directed to correct location -> replies: "The best driver software for your device is already installed", and it is not using the ADB drivers.
Going into "Driver Details" tells me that there are no drivers that have been installed.
Click to expand...
Click to collapse
Don't unplug the device, do like this, put it in MTP/debug on, leave it plugged in, "Update Driver software" -> Browse my computer for driver software -> direct to correct location.
I know my method works, I've done it to that laptop, my htpc, and my gaming rig flawlessly.
You may have to use a tool to remove all instances of those drivers and reboot, Wugs toolkit has the app, let me see if I can find the direct download for the app or you can just download and install Wugs Toolkit.
Here is the app, but I'd still recommend you install Wugs NRT, as the kit has a walk-through telling you which device IDs to look for to remove. Here is the actual tool wugs uses: http://www.nirsoft.net/utils/usb_devices_view.html, but again, unless you know which ones to remove, you're better off using Wugs tool kit device drivers walkthrough built into NRT.
mdamaged said:
Don't unplug the device, do like this, put it in MTP/debug on, leave it plugged in, "Update Driver software" -> Browse my computer for driver software -> direct to correct location.
I know my method works, I've done it to that laptop, my htpc, and my gaming rig flawlessly.
You may have to use a tool to remove all instances of those drivers and reboot, Wugs toolkit has the app, let me see if I can find the direct download for the app or you can just download and install Wugs Toolkit.
Here is the app, but I'd still recommend you install ], as the kit has a walk-through telling you which device IDs to look for to remove. Here is the actual tool wugs uses: , but again, unless you know which ones to remove, you're better off using Wugs tool kit device drivers walkthrough built into NRT.
Click to expand...
Click to collapse
Well, NRT is precisely where I started this whole thing.
Here is a picture detailing where the Nexus 7 is connected, and for reference, ALL the USB ports on my case, be it at the front or from the motherboard, are controlled by a hub: imgur.com/pP5ZbMv
Every other device's location is described as "Location 0" except for the Nexus 7 when it's connected.
Unfortunately at this point I'm probably just going to use Dropbox to transfer files when I need to.
Allane176 said:
Well, NRT is precisely where I started this whole thing.
Here is a picture detailing where the Nexus 7 is connected, and for reference, ALL the USB ports on my case, be it at the front or from the motherboard, are controlled by a hub: imgur.com/pP5ZbMv
Every other device's location is described as "Location 0" except for the Nexus 7 when it's connected.
Unfortunately at this point I'm probably just going to use Dropbox to transfer files when I need to.
Click to expand...
Click to collapse
I guess something is trashed in your system, maybe using a previous motherboard driver would work, dunno, sorry it didn't work out.
mdamaged said:
I guess something is trashed in your system, maybe using a previous motherboard driver would work, dunno, sorry it didn't work out.
Click to expand...
Click to collapse
Well thank you very much anyway. I'm sorry I couldn't have been more clear initially.
Allane176 said:
Well thank you very much anyway. I'm sorry I couldn't have been more clear initially.
Click to expand...
Click to collapse
No problem, maybe you'll work on it again and you'll figure it out. Also, you can use airdroid for transfer of files, I hear it works really well.
I've been eager to try Scott Crosler's new CM11 but didn't have time until tonight. To ensure cleanliness, at the bootloader I erased cache, system and userdata. I've flashed ROMs dozens of times, and as usual, there were no problems with fastboot recognizing the device.
I then entered CWM, and it was the darndest thing: three fast USB connection beeps and this error:
"Windows could not install driver software for your device."
But I've had the generic USB drivers installed for two years! At first I thought it was interference from the Samsung drivers when reflashing my wife's tablet, but I tried our two laptops, same result. No matter that I right-clicked "Nexus 7" in Device Manager and pointed it to freshly downloaded drivers, even that I tried installing drivers using the SDK Manager,
"Windows could not install driver software for your device."
I've read that turning off USB debugging helps, but um, with an erased /system, I had nothing to boot into!
Normally I prefer flashing via ADB sideload. To get up and running again, I flashed TWRP and used its feature of mounting USB-OTG and flashing from an external drive. Once I got into CM11, I turned on and off USB debugging, but I still can't install the USB drivers, and ADB can't recognize any devices. At least there's flashing via external flash drives.
Has anyone had the like?
didn't see win 8.1 mentioned but thought this may help? http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908. I have had problems with drivers in past. adb composite are the ones that work for me. I simply removed drivers under android devices in device manager then plugged in device. GL.
Windows 7 here, but thanks for the suggestion anyway.
This morning I can connect it as a media device, and it's in Device Manager just fine as "Nexus 7." But turning that off, it becomes "flo" in Device Manager and can't find the updated drivers. And either way, I still can't get it recognized while in recovery mode. Ah well, as I said, at least TWRP has the option to mount USB OTB and flash files from an external drive.
Let me add that I already tried another cable (for our Samsung tablet), and tonight I see that I can connect it in MTP mode. In MTP mode, it shows up just fine in Device Manager (under Portable Devices), but turning off MTP throws it under Other Devices with the dreaded ! (and I just can't get it to install the driver no matter where I point it to). And no matter what combination I try, I still can't get ADB to recognize it at all.
Although this is for Windows 8.1 it may apply to your situation: http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908
As I e-mailed you, sfetaz's suggestion of USBDeview is part of the solution! I still can't get it recognized in booted Android as anything but a media device, but now it's fine during recovery. Darndest thing I ever saw in 19 years of dealing with Windows drivers.
http://www.nirsoft.net/utils/usb_devices_view.html
Then in an old bookmark, I tried Koush's universal ADB drivers.
http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Even if USBDeview hadn't helped, it was still good to clear out all the old devices I no longer use. Definitely a handy utility to keep around and recommend.