I have an Asus Nexus 7 tablet that over a year ago I rooted and flashed and maybe a few other things, I don't fully remember, but I did get it to run the Nitrogen OS successfully, and since then I've used it with no problems. But the other day I plugged it into my PC via USB cable as I always do when I want to load a movie or whatever, and this time my PC refused to have anything to do with it. Immediately upon plugging it into my desktop's USB 3.0 (2.0 port does the same thing) I get this Windows 10 notification: "USB Device Not Recognized. The last USB device you connected to this computer has malfunctioned and Windows does not recognize it." When I check under Device Manager I see a yellow triangle warning under Universal Serial Bus controllers that says, "Unknown USB Device (Device Descriptor Request Failed)." And that's as far as I can go. There is no mention of ASUS, Nexus, or Android anywhere else in Device Manager. I've checked under all the headings.
It seems Windows 10 knows something has been connected when I plug in via USB but it doesn't know what to do with the device. I've searched the Internet high and low for a solution but nothing works. Here's what I've tried:
1) Uninstalled the yellow triangle error driver from Device Manager, checked for new hardware, got the yellow triangle back.
2) Tried updating driver but "You have the latest driver installed."
3) Tried installing USB driver from Google and "the operation completed successfully" but the problem remains even after reboot.
4) Went to Developer Options and ensured USB debugging is turned on and MTP is selected in USB Configuration. When I turn USB Debugging on and off with the Nexus connected via USB, Windows 10 reacts, but only to tell me with each change that I have an "unknown USB device attached," basically all the original error messages. I get the same errors whether I'm set for MTP or Camera or charge only or any of the other options.
5) Learned others have found a bad cable can cause my problem so I located three spare cables around the house and none worked. So I ordered a fresh new data cable from Amazon which arrived today -- but the problem remains.
6) I have a triple-boot PC. All three OS installations are Win10 but installed separately on different drives -- one of them is from the Microsoft Insider program, so should be the latest and greatest -- but I have the exact same problem on all three.
7) Wondered if maybe Linux would work so tried Knoppix live boot disk and even did a full installation of Zorin on a separate HDD. Neither version of Linux recognized that any Android device was attached. I even ran a "find-mtp" Linux program but it saw nothing.
8) Installed Wondershare Mobile Go and Syncios Data Transfer -- both are programs for dealing with Android devices via USB on a PC -- and neither sees my Nexus. And I guess there's no way they could as the Nexus doesn't appear in Device Manager.
8) Reset the Nexus to factory settings. All my apps and so forth are gone but the problem remains exactly the same.
I've been at this for about a week now so there are probably other things I've tried and forgotten about but nothing has worked. If I had another Android device I'd see if the computer recognizes it via USB but I don't have one. Maybe I can get a friend to help me out. I'm grasping at straws.
One more thing -- I don't remember whether I've ever before communicated with this Nexus on my current computer. In May of this year my old Asus MBO failed and I've built a new computer around an Asus Prime X299-A. It's working great, its USB ports are giving me no problems with anything else I throw at them, but I'm wondering of maybe I've got something set wrong in BIOS (UEFI). I've gone through every USB setting I can find in BIOS and no changes offered seem appropriate. But I've tried them this way and that with no apparent effect. And as I said, USB 3.0 and 2.0 are working great for everything else.
And when I wrote that last paragraph it hit me that I should try the spare PC I keep in a closet. Duh. So,
9) Tried a different PC, a spare Win10 system I built from spare parts from my old system plus an el cheapo MBO. This is a TOTALLY DIFFERENT COMPUTER -- but the problem is exactly the same.
It can't be the Nitrogen OS -- I just can't go there. It's been working perfectly for over a year, no glitches whatsoever. How could it suddenly decide to stop connecting via USB? I've pulled all my hair -- totally bald now, but that didn't work either. Any other ideas? Anybody? Toss the Nexus in the trash? That would be no fun. And it does work, though with the factory reset I've erased all the kids movies I was keeping on it for the young ones who occasionally visit and I have no way to put them back. I dunno what to try next ....
Other things to try
Windows 7 or better yet XP
Disable your anti-virus on your pc
Make sure usb debugging turned on for the tablet.
Use an app like drivedroid to see what usb setting work with your phone. (Not what the app is meant for, but the settings wizard is pretty helpful.)
Worst case:
Use the Nexus Root Kit to unroot and return the device to factory image, then reroot and install latest twrp and image of your choice.
Sent from my LGLS992 using Tapatalk
My Nexus 7 2013 connects straight up With Windows 7 Professional on a Lenova M92p "desktop". The Nexus is set via Developer Options for USB Configuration of "MTP (Media Transfer Protocol)". Upon plugging in the Nexus to the Win 7 machine, on the Nexus you swipe down to see a menu for USB options, which defaults to Charging. Then you set it to File Transfers, and Windows autoplay then asks what you want to do, one option of which is "Open Device to View Files". That is Windows 7, which works! In Windows 7 the Nexus 7 appears in Device Manager under Portable Devices.
Windows 10 Professional, which I have on my XPS 13 9370, does not even acknowledge that there is a device connected under Portable Devices. Under Unknown Devices, when right-clicking to Update Driver and choosing among those for Portable Devices, there are many MTP devices from 4 manufacturers including Microsoft (including Kodak 4800 Digital Camera) but none of them load. I get "The device cannot start. (Code 10)". I've read that the correct one is "MTP USB Device" but neither that one nor any MTP device driver loads. Stuck!!
jbabin1 said:
My Nexus 7 2013 connects straight up With Windows 7 Professional on a Lenova M92p "desktop". The Nexus is set via Developer Options for USB Configuration of "MTP (Media Transfer Protocol)". Upon plugging in the Nexus to the Win 7 machine, on the Nexus you swipe down to see a menu for USB options, which defaults to Charging. Then you set it to File Transfers, and Windows autoplay then asks what you want to do, one option of which is "Open Device to View Files". That is Windows 7, which works! In Windows 7 the Nexus 7 appears in Device Manager under Portable Devices.
Windows 10 Professional, which I have on my XPS 13 9370, does not even acknowledge that there is a device connected under Portable Devices. Under Unknown Devices, when right-clicking to Update Driver and choosing among those for Portable Devices, there are many MTP devices from 4 manufacturers including Microsoft (including Kodak 4800 Digital Camera) but none of them load. I get "The device cannot start. (Code 10)". I've read that the correct one is "MTP USB Device" but neither that one nor any MTP device driver loads. Stuck!!
Click to expand...
Click to collapse
I replied earlier but being lazy I didn't log in so here we go again so you'll see I'm the OP. My Win10 Pro desktop recognizes my Nexus 7 nicely since I halfway pried the back off the Nexus and then snapped it back in place. Yep, that's all it took. Apparently something was loose or misaligned inside the Nexus and just fiddling with it fixed it. Yay.
jbabin1 said:
My Nexus 7 2013 connects straight up With Windows 7 Professional on a Lenova M92p "desktop". The Nexus is set via Developer Options for USB Configuration of "MTP (Media Transfer Protocol)". Upon plugging in the Nexus to the Win 7 machine, on the Nexus you swipe down to see a menu for USB options, which defaults to Charging. Then you set it to File Transfers, and Windows autoplay then asks what you want to do, one option of which is "Open Device to View Files". That is Windows 7, which works! In Windows 7 the Nexus 7 appears in Device Manager under Portable Devices.
Windows 10 Professional, which I have on my XPS 13 9370, does not even acknowledge that there is a device connected under Portable Devices. Under Unknown Devices, when right-clicking to Update Driver and choosing among those for Portable Devices, there are many MTP devices from 4 manufacturers including Microsoft (including Kodak 4800 Digital Camera) but none of them load. I get "The device cannot start. (Code 10)". I've read that the correct one is "MTP USB Device" but neither that one nor any MTP device driver loads. Stuck!!
Click to expand...
Click to collapse
Your issue is not similar to the OP who had no connectivity at all in different PCs.
The issue is the driver in your case, may be a clash of drivers. Install USBDview in the PC and using it, uninstall every driver related to USB. Don't worry, since Windows will reinstall any driver needed as and when the peripherals are connected. Restart the PC and disable 'driver signing' and any antivirus program including Windows Defender. Now connect the tab and check if the correct drivers are installed and the tab is recognised. If not, try to update the driver in Device Manager. If even that doesn't work, you may have to reinstall Windows.
Related
Anyone else having these.
It worked only once for me.
I'll plug in my Evo then windows will detect and ATB device and the it will disappear and I dont know where.
The SDCARD will show for a secord or two and then disappear. Anyone else having this issue?
Having the same issues. Will show up, then disappear. Haven't been able to figure out a fix yet.
HTC Sync Update for EVO 4G (Sprint) (2.0.35) | 06.04.2010
http://member.america.htc.com/download/Driver/HTC EVO (Sprint)/HTCSync2.0.35.exe
Please try installing the lastest version of HTC Sync which will inclue the latest drivers for Windows 7 x64.
Already have that downloaded and still getting the appear/disappear issue
Working fine here. Win 7 Ult x64. Evo is auto-detected everytime i plug in... wish i had more info and could help.
yea everything is great on my 64bit Windows 7 Ult... uninstall and reinstall the usb root hubs..?
Everything is working fine here too on my end. No issues connecting the Evo to my Windows 7 x64 system.
I can mount fine, but can't flash RUUs or get HTC sync to actually recognize the phone
With the Hero, Windows 7 x64 would always install the wrong drivers and cause the exact issues described.
Go into Device Manager, find the EVO, and click update driver. Then manually find the driver by going to the HTC Sync directory and installing the Windows 7 x64 drivers. That is what works for the Hero, and it says My HTC in device manager when installed correctly.
Mine works fine. Though it is the first day. We'll see.
ziggy682 said:
With the Hero, Windows 7 x64 would always install the wrong drivers and cause the exact issues described.
Go into Device Manager, find the EVO, and click update driver. Then manually find the driver by going to the HTC Sync directory and installing the Windows 7 x64 drivers. That is what works for the Hero, and it says My HTC in device manager when installed correctly.
Click to expand...
Click to collapse
Yeah the problem with me its that the device disappears from device manager. It wont display at all. It will display briefly as some sort WPD Device and then it will disappear.
I have tried installing the latest HTC Sync software and reinstalling everysingle usb device to no avail.
When I am able to catch the wpd device I trying updating the drive but it doesnt like the HTC windows 7 x64 drivers. It says theyre not 64bit compatible.
For the people having problems...Are you plugging the device into a USB hub or is this straight into your PC/Laptop port? If it is a hub, is it a "powered" hub or one that draws it's power straight from the bus? If it is directly into the machine, what type of machine is it (HP, Dell, custom, etc.)? If it is custom build...what type of motherboard are you using (Asus, MSI, Gigabyte, etc)? (I ask this because some companies implement USB slightly differently and it can cause issues in some configurations)
Secondly, if this is straight into the machine, what other devices are plugged into the same internal connection (keyboard, mouse, scanner, printer, etc.). If the USB ports are in close proximity, it's a good bet they all run off the same internal connector. If only a keyboard and mouse share the connector...what type of keyboard (logitech with LCD, etc). Some keyboard and mouse combinations are high power draws and can overload the internal hub. This would make your phone connect for an instant and disconnect (overload state), since the phohe actually starts to pull power to charge, regardless if you're using it as a disk drive or sync.
All of that info will help us to troubleshoot with you.
Thanks!
Possible fix
I was having the same problems as many of you. I'm using Win 7 64, had the latest version of HTC Sync and the thing just wasn't finding my phone. The only thing that would work was if I restarted my computer and plugged it in. It found my phone right away and loaded up the HTC Sync just fine.
Only problem is, it only works that one time after a reboot of my computer. If I wanted to re-sync again, I would have to restart my computer.
It's an ugly fix, but for those of you that haven't had any luck syncing, this may be your best bet.
Mine with W7 x64 will mount fine every time but if I try to pick internet sharing, it never works. The only thing that pops up is an 'android phone' entry with a yellow triangle exclamation point under 'other devices' in device manager. I've got htc sync installed, and in fact I can use ADB fine... but I can't get normal usb internet tethering to work at all.
yeah its weird...i took my phone to a work machine that has windows 7 32bit and it worked fine on that machine... now i plugged it into my own machine and now my machine is picking it up
Look under device manager and you will see adb device unknown. Install driver and it will change to htc device.
http://depositfiles.com/en/files/yz4rg8u3i 64bit
http://depositfiles.com/en/files/yd61xorii 32bit
I have tried just about everything to get my Xoom to work with my 64bit Windows 7 system, but the various steps do not work. What is even more odd is that I have a laptop with windows 7 64bit enterprise that works perfectly with the Xoom.
So here are the symptoms:
1) When I connect the Xoom without debugging on, it tries to install a driver, but fails with a message about MTP drive failure.
2) When I turn debugging on, it installs a driver and tells me that the Xoom installed, but then my computer goes wonky. I can't open "My Computer", it like Windows Explorer freezes up. As soon as I disconnect the Xoom, my desktop works correctly again and I can go into "My Computer".
A few times i've gotten into "My Computer" after the Xoom installed, but when I double click on the Xoom icon it just times out.
The only difference I can think of between this PC and my laptop is that in the past I've connected my Droid X to this PC, and used those drivers. I'm not sure if it is some sort of issue because of the X or what. I've installed, uninstalled, cleaned, restarted, etc... with the Motorola drivers.
Its driving me nuts. Has nobody else had this problem?
Did you try different USB ports on your computer? I was kind of experiencing the same thing. I'm also running Windows 7 Enterprise x64. My explorer window would freeze up when I tried to transfer data from my PC to the Xoom. While frozen, switching from/to normal/debugging mode would unfreeze things, until I tried copying again.
My problem was resolved when I connected my Xoom to another USB port on my PC, one that was integrated with the motherboard. Previously, I was plugging it into one of the front USB ports.
So my suggestion is to try a different USB port, preferably one that's on the back of your PC.
i ran into the same issue as well.
this was fixed by changing to a different usb cable, and inserting it into a different port.
if you're connecting it to the front of your computer USB connector, try connecting via back of your desktop computer.
this worked for me.
Like another poster has suggested, the usb ports on the front of the base unit or ports on a usb hub might not be powerful enough to run the Xoom. I've had the same thing with external hard drives.
Sent from my Desire HD using XDA App
I've successfully connected my xoom to 3 Win x64 Enterprise boxes.
If I had to guess, I'd say that your front USB ports are either failing or under powered. I assume that you've tried a USB port on the back?
Sent from my Xoom using XDA Premium App
Is anyone else having an issue with Windows 7 not recognizing the Tab?
When I connect via USB, all I get is "USB device is not recognized". I tried loading the drivers from Samsung's website, but the install failed.
Thank you to the community here. I have been reading all of the threads in this forum and gaining a lot of really useful information. I appreciate any help you can offer.
I get USB device not recognized too. However if you wait a few moments, it may still show up as a mass storage device in Windows Explorer.
If it doesn't, make sure USB debugging is disabled in Settings\Applications\Development.
mine said that but...
I installed the driver under win home 7 and when plugging the device it:
said device attached
then loading driver for usb device
then it did say driver not loaded for device but...
when I moved out of the locked home screen it comes up with black screen with usb icon in the middle with connected and press the home key to quick Samsung Kies underneath. It says MTP Application in top left corner of screen. When I goto explorer it's listed as a portable device called GT-P7510 mobile phone
when I double click is says
tablet 26.9 of 27.9 free
double click on that and I see filesystem with:
Alarms
Android
DCIM
Dowload
Movies
Music
Notifications
Pictures
Podcasts
Ringtones
samsungapps
TunnyBrowser
and a file called beforeTime.ini
same issue
If I try to copy anything over-my screen completely freezes and I have to power cycle my laptop. I installed Kies and it looks like the drivers are working- but something just isnt right.
Samsung really screwed everyone on this. Win7, Mac, and Linux users all have problems. They should have just enabled USB mass storage support.
win7
I had no issues and I have a win7 64bit asus ep121 tab. I loaded Anchorman onto my GT and it even asked if I wantwd to convert it from mpeg4.x
I also connected it to my 64-bit W7 without any problems, after a few seconds I could see it's internal storage and start copying files.
Everything working flawlessly here .... Win 7 Pro 64. Sounds like some errant USB devices causing conflict. Run the attached program and remove all old, deleted or unused USB devices than reinstall Samsung drivers.
Want to start this by saying I'm pretty sure this is a pc issue rather than phone issue, I've had similar problems with every android I've owned. I installed drivers through the Nexus 4 toolkit and the tutorial by thesmokingandroid, my PC doesn't even acknowledge the phone. I get the beep when it connects and disconnects but the phone doesn't show up anywhere like my computer or device manager at all. Like I said my older phones would connect most of the time but almost always randomly disconnect/connect. I feel like it's likely a driver thing, never had problems with my iPhones or other things like mouse or keyboard. Is there a way other than a clean windows install to just clean my pc of any android related things like SDK or drivers? Also it's a custom built pc with 5 ports running win7, no ports will work. I added an in tower sd hub and feel like the problems might have started around then but I'm not sure on that. Any suggestions would be nice, not being able to connect my phone is an issue with no removable memory...
edit: Wanted to add that sometimes when I only have my mouse, keyboard, and Xbox controller connected I get those little connect/disconnect beeps at random and the bubble that says this device can perform faster. I'm pretty sure my ports are 2.0 too but I'm not sure how to check that.
Sent from my Nexus 4
I having the same problem. When I'm in fastboot mode my pc doesn't show my phone but when my phone is powered on it shows up on my pc. Anyone know what I'm doing wrong?
Anyone? I'm ready to try reinstalling Windows but would really like to know if there's something a less time consuming I could try first. I can't root or anything so I'm going to have to try something soon.
Same thing happens to me a couple days ago.
My laptop recognized the phones, but it showed nowhere in Device Manager. Adb could see my phone, but as soon as I went to bootloader, my laptop said An USB port is unrecognized
SOLUTION: I use Nexus Root Tool Kit and Google NExus 4 Tool Kit to REMOVE the nexus 4 driver, everything related to nexus 4 is removed. I only used these tools to uninstall the driver, not to install them.
Then I turned off the Windows 7's Automatic Update Driver by Window Update (or some similar names). This is important, because the driver that windows install autimatically doesn't covery the Bootloader Driver. I dont remember how exactly I turned the Automatical Diver Update off. Maybe when the popup "unrecognized USB" appear, I pressed it and there was an option to do that. Or you can search google.
A link to turn the Windows 7 Automatic Driver Installation: http://www.sevenforums.com/drivers/82054-turn-off-windows-7-automatic-driver-installation.html
Restart my computer after that. THen download driver from this http://forum.xda-developers.com/showthread.php?t=2010312 ONly the driver.
THen Install it from DEvice Manager by plugging my phone again.
Finish.
I had the same issue,here's the fix:http://forum.xda-developers.com/showthread.php?t=2036400
In my case,there was no wpdmtp.inf file in windows/inf,hence device wasnt recognised.
I'll give that a shot when I get home thanks.
Sent from my Nexus 4
wareju said:
I'll give that a shot when I get home thanks.
Sent from my Nexus 4
Click to expand...
Click to collapse
Yeah, what causes so much trouble for me is the Windows-7-automatic-driver-installation. It helped me sometimes, but not with the NExus 4 :|
I could not connect my Lumia 950 to a Windows 10 PC using the data cable the phone came with.
When I connect them the phone asks if I want to enable "data connection" I push yes. The PC is installing some 950 firmware or driver but nothing happens. I cannot reach the phone. Any idea?
I could do it before, but now it's impossible, as if drivers were wrong. I reinstalled them and rebooted, but in vain
Same problem here.
On Win 10 64bit my 950 XL are shown in Device Manager under USB Devices but not seen in to Explorer, on Win XP 32bit can see my phone in Explorer but it is not installed properly in Device Manager.
That's ridiculous Microsoft are not able to get communicate their own devices easily by massive usage of windows worldwide.
Missing AirDroid.
media features is needed, for some reason WP phones not show on "Windows 10 N" versions...
also check in devices and printers (in control panel)... right click on windows phone icon and select troubleshot
third and most common reason i notice is problem with USB ports on computer or USB cable...
dxdy said:
media features is needed, for some reason WP phones not show on "Windows 10 N" versions...
also check in devices and printers (in control panel)... right click on windows phone icon and select troubleshot
third and most common reason i notice is problem with USB ports on computer or USB cable...
Click to expand...
Click to collapse
Another way to "troubleshoot" is to just disable or uninstall the device, and then re-scan for all devices, and it'll re-install it fresh (make sure you check the "uninstall drivers" if you try the un-install route).
That said, on recent Release Ring builds, USB is really, really flaky, to the point where even grabbing a few pictures is much easier over WiFi. I assume this will get fixed (it worked fine earlier, and I "upvoted" the issue wherever I could find it), but in the meantime, even if you're connected, enumerating folders/files can take a really, really long time (along with other operations on them), and often crashes the W10 explorer.exe process. The process recovers, and IME if you try enough times, you can get the files this way, but it's quite painful...
I had this problem but it was caused by a targus hub. When I plugged the 950 directly into my PC, and not into the hub, the problem went away. PC recognized 950, folders showed up in seconds. Could be USB-C incompatibility with hub?
Yeah i've got the same thing. So now it works on USB 3.1 typa A or C, but not on my USB 2.0 and 3.0