Database Info

USB unknown device

I've tried the drivers from Samsung, Keis, ODIN one click. None of them worked on 4 different machines, Windows 7 both x64 and x86(which was a fresh install), and two Windows XP machines. I tried it on Ubuntu(10.04 LTS) and that recognized the captivate.
Anyone know how to get one of those to correctly recognize my Captivate so I don't stuck on Samsung's/AT&T's 2.2

uninstall all of the driver that you downloaded. uninstall kies. then go to samsung.com search for the captivate, choose you phone, click the 'i own this' button. then go to get downloads, software. click on the .zip file icon next to usb drivers. if that didnt work uninstall them then download kies again. if it still doesn't install them, open kies, click menu, reinstall drivers

What is it that you're trying to do?
Sent from my SAMSUNG-SGH-I897 using XDA App

If it is coming up unknown device try another port. You may want to try another microusb cable as well.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

I've always had luck with the drivers in the captivate aio toolbox. Even on a fresh win7 64bit when I replaced my boot drive with a ssd a month ago.

Samsung really failed at the USB drivers for the Captivate. I would expect to be able to install the drivers from their website. Plug in my phone, and have it working.
trell959 said:
uninstall all of the driver that you downloaded. uninstall kies. then go to samsung.com search for the captivate, choose you phone, click the 'i own this' button. then go to get downloads, software. click on the .zip file icon next to usb drivers. if that didnt work uninstall them then download kies again. if it still doesn't install them, open kies, click menu, reinstall drivers
Click to expand...
Click to collapse
I tried that before, didn't work.
bornjamerican said:
What is it that you're trying to do?
Click to expand...
Click to collapse
I'm trying to:
1) connect as a mass storage devices. Yes I know turn on USB debugging and to mount the drive.
2) flash back to stock 2.1 or root my phone so I can install a custom ROM on it. Might go with CM7/MiUi or something from Team Phoenix. So use Odin3
shinji257 said:
If it is coming up unknown device try another port. You may want to try another microusb cable as well.
Click to expand...
Click to collapse
Tried all of the ports on the computers. I don't have another microusb cable to test to see if that's the problem, but I'll check that tomorrow.
Johnnie5000 said:
I've always had luck with the drivers in the captivate aio toolbox. Even on a fresh win7 64bit when I replaced my boot drive with a ssd a month ago.
Click to expand...
Click to collapse
I'm going to try a fresh install of windows 7 32-bit with aio toolbox see if that works.
Tried my friends brand new microUSB cable. It worked.

I have tried 4 known good cables know, 4 different computers and every USB port available on all 4 of the PCs I tried. Only once did it identify the device and install the drivers and I was able to root it but I still can't sideload because after the reboot after rooting it is back to device not recognized/unknown device. This has been a total pain. Any suggestions? I'm not with AT&T any more so I am out of luck for just bringing it into a store and asking them to take care of it.
Edit: Sorry for bumping an older post but I did it instead of starting a new thread.

rmriggin said:
I have tried 4 known good cables know, 4 different computers and every USB port available on all 4 of the PCs I tried. Only once did it identify the device and install the drivers and I was able to root it but I still can't sideload because after the reboot after rooting it is back to device not recognized/unknown device. This has been a total pain. Any suggestions? I'm not with AT&T any more so I am out of luck for just bringing it into a store and asking them to take care of it.
Edit: Sorry for bumping an older post but I did it instead of starting a new thread.
Click to expand...
Click to collapse
If you're just trying to transfer apk files to it for sideloading, you can use a wifi transfer app. I use Wifi File Explorer and it's great. You can connect to your phone via web browser and upload/download anything on the SD card.
Another option is to use an external SD card that you can remove and plug into your computer, transfer the files to it, then insert it back into the phone.
This won't work for connecting to PC apps like Odin, Heimdall, or Kies, but for simple file transfers it works like a charm.
Additionally, regarding other usb cables, you didn't mention what types of cables you used, so I'll throw in another thought. The cables that come with the Captivate don't work on some PCs (like my new iMac). Third-party, generic usb cables might not work, either (I tried some and got a whole lot of fail). The only cable that works for me is the one that came with my wife's Motorola phone. If you haven't tried one yet, I would recommend getting your hands on a Motorola cable and testing it out. You'll immediately notice the cable is much thicker. I don't know if that has anything to do with why it works when others don't, but there's something about that cable that others don't have.

Bad Phone?
Could it be the phone port is having issues?
I've had the same problem and it seems that the port on the Captivate is shot which may be your issue. it will always charge; but tends to cause a lot of profanity when trying to get a PC connection to transfer files or flash it. It will be seen, then immediately play the 'unplugged' sound from windows. I've sat there and had it play the tones of plugged in and un plugged over and over again just by tilting the phone from side to side. No matter what cables I use (tried several but they are all samsung due to the recessed port). If it establishes the connection; I have to be very still with it or it'll lose it. If it loses it; I get unknown device messages or not functioning messages on that port until I reboot the PC.
Trying to flash anything via ODIN takes a lot of patience.
Those same cables / USB ports are used on my wife's Focus without ever having a problem. I wrote it off as too much flashing / overclocking of my phone but am not sure.

hi i was having this issue as well. i solved it by:
1. download a good & stable miui rom, rename it to update.zip and place it into your sd card. i took the sd card out of the phone and used a adapter to connect the sd card to my PC since i can't access my sd card through the usb port.
2. put the sd card back into my phone, turn off my phone. press and hold volume up and down buttons, then press n hold the power button till the screen shows something.
3. select install from sd. wait until the installation finishes and select reboot the phone.
4. when you're in your new miui rom, try to connect your phone to the pc via usb port again.
this worked like charm for me.
about the miui rom, i suggest you to use the one from miuiandroid.com (the UK version)
after flashing the rom im able to connect via usb and use mass storage.
hope this helps

Also, when you uninstall drivers, don't forget to look in the program files for anything that may have been left behind and delete it.

From the description it sounds strongly like you are actually experiencing a port failure which is common on the Galaxy S devices. PM me if you need this repaired...

Only try another usb cable, i bricked my cappy with a bad contact cable on odin, unknown device too, new cable=i897 device on windows notifications
try and feedback!

strange, this only happened to my when i soft bricked my phone. try connecting it to your computer in download mode

I had this issue once before. Here is what I did which resolved the problem. I was using a windows 7 PC
1. Download the ADB kit and extract it to C drive.
2. Connect your mobile to the PC on USB port
3. Wait for the drivers to be installed automatically (it might give you a failed to install message)
4. Never mind that message. Open Device Manager
5. In Device Manager, if you expand the "Universal Serial Bus Controllers", you'll see a device that has yellow question mark against it. This is your phone and since drivers are not installed properly, it has the question mark.
6. Right click that device, and select "Update Driver".
7. IN the window that comes up, select "I'll select a driver".
8. Browse to the folder where you have extracted the ADB kit on C drive
9. Check include subfolders and click Next.
10. The drivers should be be installed and your device should be identified by the computer.
Let me know if it works for you.

[Q] adb is not working, even in Emulator on the Galaxy Tab (P1000)

Okay here is the thing, I am a bit of an advanced user, and have been flashing ROM's for quite a while, so i am not a noob and I have already tried everything in the book to fix my problem.
Info:
1- Drivers installed on Windows 7 and have been working for the past 4 months.
2- USB Debugging ticked
3- Windows recognizes the Galaxy Tab 7" GSM (P1000 International)
Problem:
1-Running "adb shell" in adb results in: error: device not found
2-CWM Restore stops at android_secure.img not found and aborts.
How did it happen (Detailed):
1- Was on Overcome 2.0.1 "Hermes" and found out that there was an update on kies from someone.
2- Decided to restock
3- Flashed P1000JPJM5 (I already did that quite a few times and no problems ever occurred from that)
4- When i restocked i wanted to root, so i went into settings>Application>developement> and ticked USB Debugging
5- Plugged in USB and I opened up Super One Click Root v1.7 and hit Root, however, Nothing happened and it was "Waiting for device" forever.
6- tried Super One Click root v1.9 with the same result
7- Opened adb and typed "adb shell" and got error: device not found.
8- I downloaded Better Terminal app from the market and tried "adb shell" and i got "Adb not found" as a result
9- I wanted to root my device to use the Bootloader Batch and change my protected boot loaders
10- tried everything, Restore factory from 3e Recovery, Doing the same from Setting>Privecy, Flashing the same ROM Over and Over again with no luck
11- learned later that flashing ChainFire's Gingerbread P1000XXJMQ is safe on protected boot Loaders so i did that
12- the problem persisted and i just cant use adb
13- I had a CWM Backup done so i thought doing a restore might solve the problem, but that resulted in a failure in restore. it stops at android_secure.img not found and aborts restore.
If anyone kow's a solution or at least knows what might have gone wrong Please shed some light on how to go about this issue.
Thanks

While the device is plugged in, go to device manager and delete/uninstall the device. Should ask you if you want to delete the driver files also, check the box and go.
After that it will probably ask you to restart, restart the computer and reinstall the device with the google drivers.

pwolfamv said:
While the device is plugged in, go to device manager and delete/uninstall the device. Should ask you if you want to delete the driver files also, check the box and go.
After that it will probably ask you to restart, restart the computer and reinstall the device with the google drivers.
Click to expand...
Click to collapse
well its like i said earlier it is NOT a driver issue.
I mean even Emulater apps from within the Tab are not recognizing ADB

DistortedWisdom said:
well its like i said earlier it is NOT a driver issue.
I mean even Emulater apps from within the Tab are not recognizing ADB
Click to expand...
Click to collapse
Did you at least try what I suggested?

I can't get my galaxy tab to be seen by adb either. At least not since upgrading to Gingerbread.
I'm using the
"sprint_p100_Samung_GALAXY_Tab_USB_Drivers.msi" file from the Samsung web site.

[Q] SK4G not being recognized on PC

I originally posted this inside the Glorious Overdose V2 thread, but decided to post here as well.
For some reason my computer won't recognize my Sidekick when I plug it in via usb. I do have the samsung drivers installed and it will read my friends Samsung Droid Charge just fine, but when I plug my Sidekick in it comes up saying "USB Device Not Recognized". So far I've tried uninstalling and reinstalling the drivers from the device manager to no avail. Wondering if anyone has an idea as to what it could be. I've also tried googling the solution and everyone says to just uninstall and reinstall the drivers and it should work. Now the phone is not plugged into a USB Hub, extender, or case, it is plugged directly into a usb port on the mother board.
PC Specs just in case:
Motherboard - Gigabyte GA-970A-D3
OS - Windows 7 Ultimate x64
CPU - AMD FX-4100
Memory - 8GB DDR3 1066
Phone:
T-Mobile Sidekick 4G running Glorious Overdose V2
Nothing added just the rom and some apps/games.
I have tried with USB Debugging on and off, either way does not work.
Update: I have since tried Kies mini, as well as the drivers found on Softpedia. Neither of those worked, so I just got done reformatting and reinstalling Windows hoping that would work. At first it did not, right now I am running windows update to see if that was the issue, I'll update of what the outcome is.
Update: After installing all available Windows updates it's still not recognizing the phone. Now no matter what it's saying it's an Unknown Device. Even after I try and do a manual driver update and tell it to look in the folder with the driver files from Softpedia. I'm at a complete loss now.
If anyone has any idea's please let me know.

What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.

Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA

Jax184 said:
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Click to expand...
Click to collapse
It's set to USB Debugging. But even then, it should read as something else other then Unknown Device when I plug it in. I have tried plugging it in and selecting Mass Storage, still comes up as Unknown Device.
HewettBR said:
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Click to expand...
Click to collapse
I've thought about that, and from everything I can see it's either the ROM or the drivers. So we'll see...I'll probably try a different ROM and see what happens.

I suggest turning USB debugging off and mass storage on, for how you'll be using it. And recall that you have to change this stuff with the USB cable unplugged.

I've tried that, and after talking with the T2 Technical Support from Samsung for 45min today, the only option left is to send the phone in to get worked on. Though, I'm going into the T-Mobile store and see if they can't replace the phone or give me a loner while this one is out getting repaired.

More info request.
Can you provide us with the names and links to the drivers you have tried?

DuctTapedGoat said:
Can you provide us with the names and links to the drivers you have tried?
Click to expand...
Click to collapse
Kies Mini - http://www.samsung.com/us/support/owners/product/SGH-T839HABTMB
Softpedia - http://drivers.softpedia.com/get/MOBILES/Samsung/SAMSUNG-USB-Driver-1480.shtml
As well as the Samsung Vibrant drivers from both of those sites.

Samsung SideKick 4G Drivers
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.

DuctTapedGoat said:
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
Click to expand...
Click to collapse
Thank you, I tried unpacking them to a folder on C:\ went into Device Manager, right clicked on the Unknown Device, Update Driver Software..., Browse My Computer for Driver Software, Set the search to C:\, and still saying Unknown Device is the best driver software for it. No idea why it's doing this.

Proper Driver Update
What is going on is that Windows is seeing a more recent signature file attached to the SK4G drivers on your computer (I don't believe anything at all is wrong with your device) than the working ones there.
First, in Add/Remove Programs, uninstall the Samsung Kies and Samsung Driver pack you installed earlier. Now...
Go into on your PC:
://windows/system32
And locate the same file names, cut them all, and paste them in a temporary folder you create, preferably on the desktop or something similar. You may not find every file, and that's okay, just the ones you can find. Next, you will be wanting to paste the driver files from the package I uploaded. Now, turn off Automatic Updates, so it doesn't automatically install drivers upon connection. Reboot the computer, double check and make sure Automatic Upates are off when you log back on. Now, connect the device and see if it gives you the same results. By removing the old drivers which don't work, you'll be able to force it to the ones we know work, and you /should/ have success. As well - USB data debugging active and activating connection for data transfer via the notification pulldown menu would be the best way to do this initially.

Would I be looking in c:\windows\system32\drivers for the same file names as the ones you packed up?

Ok, so the only one I could find in the drivers folder was modem.sys. But it will not let me move/replace the one that's already in there. It's telling me access is denied, same thing when I try and set the permissions it will not let me. I am logged in as an Administrator, as well it says it when I log in as THE Administrator account. So yeah...

Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?

DuctTapedGoat said:
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
Click to expand...
Click to collapse
I tried plugging the phone in, still showing up as Unknown Device. Tried UnlockRoot.com's program, no change. Installing the Android SDK right now, as well as I tried deleting the INFCACHE.1 file, and no change with that either. Once I'm done installing the Android SDK I'll redelete the INFCACHE.1 file and restart and try the phone again.
I did go in and check the mounts in recovery and they were set to:
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
Thank you for your help so far.
UPDATE: So after installing the Android SDK, deleting the INFCACHE.1 file, restarting, and then plugging the phone in, comes up and says the USB Device is Not Recognized. Then goes to search the preconfigured driver folders, and fails to install the driver for Unknown Device. And ADB Devices shows no devices as well(didn't think it would, but yeah).
UPDATE: So after using my friends phone as a conduit to throw the Stock Odexed KJ2 w/ Root(http://forum.xda-developers.com/showthread.php?t=1328698) onto my SDCard and flashing that the phone seemed to go into a soft brick at pre-boot screen(where it says SAMSUNG T-Mobile blah blah blah). Mind you this would freeze before it was even able to get into recovery. So I took it into T-Mobile and they are doing a manufacturer warranty replacement. So hopefully this next phone will be able to connect to the computer and be read correctly.

i9023 - HELP! "No Boot or Recovery IMG & can't connect via USB

Hi guys,
I just have received a i9023 from a friend to repair. I put fastboot on and the device is unlocked, then I copied over Matr1x kernel via USB to the SD card and flashed CMW to recovery.
From here things went bad.
When trying to update the kernel to Matr1x, it showed that the file wasn't on the SD card anymore, so I tried to mount the SD card to copy it back, but it my computer wouldn't see it. Since then I tried many things to get the USB working - updating drivers etc... after awhile I decided to format SD card, which didn't help, so I formatted all the partitions on the phone.
Now, every time the phone comes on, it boots straight to fastboot, but also the PC will still not recognise the phone via USB.
I've tried getting into Download mode and using ODIN to flash a new kernel & ROM, but this wont work without USB working.
Can anyone help?
PS. I have read many other guides and posts, but nothing has helped.
Many thanks.

*Bump*

Are you running Ubuntu or similar? You need to be root to use fastboot and edit the right config files
wait, did you go to the mount menu in cwm? You can mount as usb storage in that menu... Are you saying it doesn't show up on your computer? Are you running windows?

I've a friend in the same situation.
We managed to make the phone recognizable using pda.net driver for nexus S, but weren't abel to find a single tar file to use on Odin.
Seems that all stocks rom were deleted from any storage.

bedalus said:
Are you running Ubuntu or similar? You need to be root to use fastboot and edit the right config files
wait, did you go to the mount menu in cwm? You can mount as usb storage in that menu... Are you saying it doesn't show up on your computer? Are you running windows?
Click to expand...
Click to collapse
Yes, I tried to mount as USB Storage in the Recovery Menu - didn't work, but now, I've only got fastboot - Booting up the phone normally jumps straight to fastboot, trying to boot into recovery doesn't work (just the fallen over Android pic with the red "!" on his chest).
I'm using Windows 7 and computer will not recognise the phone at all (it was working before this & the MicroUSB port is not damaged).
My GT-i9100 works perfectly via USB.
Piemo said:
I've a friend in the same situation.
We managed to make the phone recognizable using pda.net driver for nexus S, but weren't abel to find a single tar file to use on Odin.
Seems that all stocks rom were deleted from any storage.
Click to expand...
Click to collapse
If I can get it to connect to my PC so I can throw a stock ROM on there via ODIN I should be right (Pretty sure SAMFIRMWARE has some).

I've found often that the sdcard only gets mounted when you "choose zip from sdcard" in recovery. I panicked once with a galaxy s when I had forgot to put any rom on the sdcard and couldn't mount it subsequently. Ended up using heimdall with success. Also make sure you have latest version of fastboot, from platform tools 4.0.3.

Yeah, try Odin

If you can download sdk with the google drivers and install the drivers through device manager, you should be able to get your usb to connect again to fastboot. There is a bootloader driver inside the kit!

twadda218 said:
If you can download sdk with the google drivers and install the drivers through device manager, you should be able to get your usb to connect again to fastboot. There is a bootloader driver inside the kit!
Click to expand...
Click to collapse
Yeah, it is definitely not connecting via fastboot. Windows 7 just comes up with UNKNOWN DEVICE., as does my WinPX machine. It's very strange.

Can you try Ubuntu? Any luck with Odin?

KLoNe1 said:
Yeah, it is definitely not connecting via fastboot. Windows 7 just comes up with UNKNOWN DEVICE., as does my WinPX machine. It's very strange.
Click to expand...
Click to collapse
Does it say unknown device in device manager?
Sent from my ice cream powered Nexus S

I don't have a machine with Ubuntu on it unfortunately.
Yes, Unknown Device in Device Manager - it won't accept it when I point the new driver to the modified Google USB .inf file

KLoNe1 said:
I don't have a machine with Ubuntu on it unfortunately.
Yes, Unknown Device in Device Manager - it won't accept it when I point the new driver to the modified Google USB .inf file
Click to expand...
Click to collapse
Did you click the "Have disk" option, point it at the file then click one of the options? That's what I had to do
Sent from my ice cream powered Nexus S

DarkhShadow said:
Did you click the "Have disk" option, point it at the file then click one of the options? That's what I had to do
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Yes, I did - it said that this inf (driver) doesn't contain information about the device in question.

I think I came across a USB driver problem once that was rectified by deleting the relevant keys from the registry. Could be worth looking into.
EDIT: Found it!
Open regedit and navigate to
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Enum > USBSTOR
and look for any devices that could be your nexus s.
I think they might be these:
Disk&Ven_Android&Prod_UMS_Composite&Rev_0001
Disk&Ven_Google&Prod_File-CD_Gadget&Rev_0000
You should be able to delete them (if not, change the permissions).
Then reboot and hopefully next time you plug in your phone, the drivers will reload.

Many thanks for all your help everyone; unfortunately I still have yet to figure out how to get this working. Please keep throwing out your ideas
bedalus said:
I think I came across a USB driver problem once that was rectified by deleting the relevant keys from the registry. Could be worth looking into.
EDIT: Found it!
Open regedit and navigate to
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Enum > USBSTOR
and look for any devices that could be your nexus s.
I think they might be these:
Disk&Ven_Android&Prod_UMS_Composite&Rev_0001
Disk&Ven_Google&Prod_File-CD_Gadget&Rev_0000
You should be able to delete them (if not, change the permissions).
Then reboot and hopefully next time you plug in your phone, the drivers will reload.
Click to expand...
Click to collapse
I gave this a go as it sounded like a great idea, but unfortunately it still isn't working.
I ended up deleting the drivers it was installing which wouldn't work & now it will only show up as 2x Unknown device under 'Portable Devices' heading.

I think you should try installing ubuntu, and the android sdk so you have access to fastboot again.

Can't get internal SD to mount on computer

When I plug my phone in I have no way to transfer files to and from the Nexus 5. Nothing comes up. Tried updating the drivers, but nothing works. Please help.

I haven't been able to do this either, anyone wanna help?

connect phone to pc via usb
go to Device Manager
right click anything that looks like the phone and uninstall drivers
unplug phone
restart pc
connect phone to pc via usb
let it install drivers automatically
fixed?
Sent from my Nexus 5 using xda app-developers app

n7of9 said:
connect phone to pc via usb
go to Device Manager
right click anything that looks like the phone and uninstall drivers
unplug phone
restart pc
connect phone to pc via usb
let it install drivers automatically
fixed?
Click to expand...
Click to collapse
Nope, still nothing. My Razr HD comes up fine, but not the Nexus 5. Think it's a conflict in drivers?

Tweaken said:
Think it's a conflict in drivers?
Click to expand...
Click to collapse
definitely...the only time i ever had Nexus driver issues was when i changed from HTC to Nexus
the best i can offer is how i fixed it...get a copy of Wug's Nexus Root Toolkit and follow his instructions from deleting all other drivers and installing new ones...he offers (i think) 4 different options and you just work your way through them until one stick (the RAW drivers always work for me)
and note that the Toolkit doesn't work on 4.4 yet, so only use it to clear and update drivers
http://forum.xda-developers.com/showthread.php?t=1766475

n7of9 said:
definitely...the only time i ever had Nexus driver issues was when i changed from HTC to Nexus
the best i can offer is how i fixed it...get a copy of Wug's Nexus Root Toolkit and follow his instructions from deleting all other drivers and installing new ones...he offers (i think) 4 different options and you just work your way through them until one stick (the RAW drivers always work for me)
and note that the Toolkit doesn't work on 4.4 yet, so only use it to clear and update drivers
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Sweet, that did it. Uninstalled Motorola drivers, uninstalled Google ADB driver, restarted, plugged in phone, voila!

Tweaken said:
Sweet, that did it. Uninstalled Motorola drivers, uninstalled Google ADB driver, restarted, plugged in phone, voila!
Click to expand...
Click to collapse
n7of9 said:
definitely...the only time i ever had Nexus driver issues was when i changed from HTC to Nexus
the best i can offer is how i fixed it...get a copy of Wug's Nexus Root Toolkit and follow his instructions from deleting all other drivers and installing new ones...he offers (i think) 4 different options and you just work your way through them until one stick (the RAW drivers always work for me)
and note that the Toolkit doesn't work on 4.4 yet, so only use it to clear and update drivers
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Thank you n7of9 the link you provided worked for me.

Another solution...
Plug the phone into your computer. Go to "Device Manager" and find the Nexus <x> device where-ever it's listed (may not be called "Nexus...", though on my machine with the real drivers it was).
Right click, choose "update driver software"
Select "browse my computer"
Select "let me pick..."
Choose the option. "usb composite device"
Apply and close all windows.
Disconnect and reconnect the phone to the computer.
The phone will now allow you to move files to it properly. Something weird with proper phone drivers. I believe you need to reverse this if you need to use ADB again in the future.

This worked and also fixed another popular issue
Not only does this fix the MTP connection issue to move folders to root folder. But it also now allows me to see the preview thumbnails of my media! This was a huge problem on my other phones and many many people including me were never able to fix that. All the ideas to get around or create USB Mass Storage instead of MTP after 4.1 were fails.
Cosmicevo said:
Another solution...
Plug the phone into your computer. Go to "Device Manager" and find the Nexus <x> device where-ever it's listed (may not be called "Nexus...", though on my machine with the real drivers it was).
Right click, choose "update driver software"
Select "browse my computer"
Select "let me pick..."
Choose the option. "usb composite device"
Apply and close all windows.
Disconnect and reconnect the phone to the computer.
The phone will now allow you to move files to it properly. Something weird with proper phone drivers. I believe you need to reverse this if you need to use ADB again in the future.
Click to expand...
Click to collapse

Cosmicevo said:
Another solution...
Plug the phone into your computer. Go to "Device Manager" and find the Nexus <x> device where-ever it's listed (may not be called "Nexus...", though on my machine with the real drivers it was).
Right click, choose "update driver software"
Select "browse my computer"
Select "let me pick..."
Choose the option. "usb composite device"
Apply and close all windows.
Disconnect and reconnect the phone to the computer.
The phone will now allow you to move files to it properly. Something weird with proper phone drivers. I believe you need to reverse this if you need to use ADB again in the future.
Click to expand...
Click to collapse
Worked perfect, thanks

what worked for me
In windows 8.1
I plugged in my nexus and browsed to device manager in control panel
I uninstalled the device (and deleted the driver)
I unplugged the nexus 5
I plugged it back in
Windows recognized it as a proper MTP device
I think the problem was something to do with windows recognizing it as an ADB device (I had installed the toolkit before etc)
This fixed it for me

openlatedotorg said:
Worked perfect, thanks
Click to expand...
Click to collapse
Hi,
I did all the steps mentioned, and ran the driver test - everything works fine, success.
However, I still cant see my device in "This PC"...
What is even more weird, that it only disappeared couple of days ago, and I didnt do anything to my computer at all....
Any other way to get devices to show? (Nexus 10 or Nexus 4 stopped showing too).....
Maybe problem is that it is being shows as ACER ADB Interface? But i cant change that to MTP anyway..