Database Users

Windows 7 x64 and EVO 4G Connectivity issues?

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

[Q] Aaaaarrrrgh. USB drivers not working under Windows 7/64

OK, I've now officially burned 4 hours trying to get my Epic to work properly with Windows 7 (64 bit) for anything besides mounting it as a USB drive.
I tried the (32-bit?, and only?) driver Samsung seems to officially have for the Epic 4G.
I tried the 64-bit driver(s) apparently intended for Kies.
I've installed, uninstalled, shutdown-after-uninstall-instead-of-reboot, and sacrificed 3 chickens to the appropriate gods.
I temporarily made TouchWiz the homescreen instead of LauncherPro.
I made sure the phone was in "PDA" mode and NOT "modem" mode (##8778##, I think).
I've updated everything Windows Update will touch, then installed the Asus P5N-D motherboard chipset drivers straight from Asus' international site, just for good measure.
I've attempted to upgrade the Google USB driver through tools (the app that gets launched when you just type "android" from a command prompt).
Oh, I also made sure that USB Debugging was NOT enabled when I connected the phone for the first time after supposedly installing the Samsung USB drivers. Two of the drivers installed correctly. Then I enabled USB debugging, reconnected USB, and ended up (for the Nth time):
SAMSUNG Android USB Composite Device: v/ Ready to use
CDC Abstract Control Model (ACM) O Installing driver software... (for 20+ minutes)
S3C6410 Android ADB O Installing Driver Software (for 20+ minutes)
USB Mass Storage Device v/ Ready to use
For the record, I have a core2quad 9600 running at ~2.6GHz with SSD, so it seems almost inconceivable that it could legitimately take 20+ minutes to install ANYTHING.
In Device Manager, I have at least one "Other Devices" entry that just refuses to die -- Universal Serial Bus (USB) Controller. I've tried deleting it, uninstalling it, uninstalling it and shutting down (vs restarting windows), the works. NOTHING will kill it, or at least it won't stay dead when I try. Worse, when I try reinstalling the Samsung drivers, I usually get a message along the way that installation of the drivers for the Universal Serial Bus (USB) Controller failed, even though it's not even connected.
This is driving me insane. It worked fine under Vista/32, but I've never been able to get it to work properly since I got the SSD and Win7/64. Specifically, I've never been able to get ADB to work, and the USB driver situation appears to be completely fsck'ed.
Is there some secret strategy I'm forgetting for making Windows forget everything it thinks it knows about a corrupted USB driver installation and making it start over from a clean slate? I think the problem is that I have a driver that's latched onto something, refuses to be deleted, and won't allow itself to be overwritten.
Before I waste any more time on this, can anybody recommend any specific things to try? I have to get this working tonight

bitbang3r said:
OK, I've now officially burned 4 hours trying to get my Epic to work properly with Windows 7 (64 bit) for anything besides mounting it as a USB drive.
I tried the (32-bit?, and only?) driver Samsung seems to officially have for the Epic 4G.
I tried the 64-bit driver(s) apparently intended for Kies.
I've installed, uninstalled, shutdown-after-uninstall-instead-of-reboot, and sacrificed 3 chickens to the appropriate gods.
I temporarily made TouchWiz the homescreen instead of LauncherPro.
I made sure the phone was in "PDA" mode and NOT "modem" mode (##8778##, I think).
I've updated everything Windows Update will touch, then installed the Asus P5N-D motherboard chipset drivers straight from Asus' international site, just for good measure.
I've attempted to upgrade the Google USB driver through tools (the app that gets launched when you just type "android" from a command prompt).
Oh, I also made sure that USB Debugging was NOT enabled when I connected the phone for the first time after supposedly installing the Samsung USB drivers. Two of the drivers installed correctly. Then I enabled USB debugging, reconnected USB, and ended up (for the Nth time):
SAMSUNG Android USB Composite Device: v/ Ready to use
CDC Abstract Control Model (ACM) O Installing driver software... (for 20+ minutes)
S3C6410 Android ADB O Installing Driver Software (for 20+ minutes)
USB Mass Storage Device v/ Ready to use
For the record, I have a core2quad 9600 running at ~2.6GHz with SSD, so it seems almost inconceivable that it could legitimately take 20+ minutes to install ANYTHING.
In Device Manager, I have at least one "Other Devices" entry that just refuses to die -- Universal Serial Bus (USB) Controller. I've tried deleting it, uninstalling it, uninstalling it and shutting down (vs restarting windows), the works. NOTHING will kill it, or at least it won't stay dead when I try. Worse, when I try reinstalling the Samsung drivers, I usually get a message along the way that installation of the drivers for the Universal Serial Bus (USB) Controller failed, even though it's not even connected.
This is driving me insane. It worked fine under Vista/32, but I've never been able to get it to work properly since I got the SSD and Win7/64. Specifically, I've never been able to get ADB to work, and the USB driver situation appears to be completely fsck'ed.
Is there some secret strategy I'm forgetting for making Windows forget everything it thinks it knows about a corrupted USB driver installation and making it start over from a clean slate? I think the problem is that I have a driver that's latched onto something, refuses to be deleted, and won't allow itself to be overwritten.
Before I waste any more time on this, can anybody recommend any specific things to try? I have to get this working tonight
Click to expand...
Click to collapse
I had the same problem, but found out that its all b/c of my cheap 99cent usb cable. When I use the official usb cable that came with the phone it works fine.

Argh. It appears I've forgotten rule #27,326 of Android -- don't believe the error messages. Half the time they're wrong, and the other half of the time something is lying to you. Despite having the USB driver that I can't get rid of or fix and the error messages announcing that installation failed, it seems to work. At least, adb logcat works, and I was able to deploy an app from Eclipse to the phone right now.
(goes to bash head against wall in frustration)
Oh, I'm using the cable that came with the phone ;-)

Which particular driver did you end up with? I tried using the Samsung Moment drivers (saw a vid on Youtube using these as a substitute for the Intercept handset), and though I got similar errors as you - and supposed fixes - my Eclipse was never able to connect to the handset to debug an app, grab screen shots, or anything. Would love to figure out how to get my Intercept to work with my Win 7 64-bit setup.

First of all, a large number of people (myself included) agree that the stock USB-microUSB cable sucks balls. I ran into the same problems you're having, and then they magically went away when I replaced my cable. You can find super-cheap cables on Amazon.com, or if you're a "gotta have it now!" type I know the Radio Shack cable works great, I have it.
Secondly, I know the drivers on http://forum.xda-developers.com/showpost.php?p=7933592&postcount=1 work, they're what I'm using.
I would imagine you just need to replace that stock cable. Sometimes certain things will work, but I had almost exactly the same problems as you and they all went away when I changed my cables.
Also, try to use a USB socket that's directly attached to your motherboard, i.e., a USB port on the back of your PC, as apposed to front- or top-mounted USB ports, since those add extra hardware and connections that could decrease reliability.
Good luck!

For what it's worth, I am using the drivers from Samsungs website on all of my windows 7 x64 computers. Haven't had any problems.
Sent from my SPH-D700 using XDA Premium App

Use this to remove any residual drivers from your computer before installing your new drivers. It is a very useful tool when you have driver conflicts that may be happening.
http://www.multiupload.com/3PC2BBAFSO
Then use these drivers, they've worked on my many machines with Win 7 64 bit:
http://www.multiupload.com/LLOCCAMUT4
Wow just realized how old this thread is. LOL

heathmcabee said:
Wow just realized how old this thread is. LOL
Click to expand...
Click to collapse
Hmmm, I hadn't realized that! Why the Hell did CirrusFlyer resurrect this thread?

I had the same problem and the problem ended up being my new dell xps core i7 tower. Use a powered usb hub such as your monitor with the usb hub ( if you have one) and it will solve your headaches. I am willing to bet money this will work, everyone I know that has had the same problem has solved it this way.
Sent from my SPH-D700 using XDA Premium App

The usb socket directly attached to my motherboard was the problem a powered usb hub for some weird reason made it driver up every damn time and still works today.
Sent from my SPH-D700 using XDA Premium App

Cpagent is 100% correct on the powered usb port causing issues. And that goes for multiple devices for an assortment of usb drivers... I have to deal with it all the time with my customers (that's assuming I've already exhausted every other software possibility... for this reason I only work on customers phones on an older xp 32 pc with proper hardware) it really ticks me off how little software developers.care about adapting basic drivers to be compatible with the machines most commonly used by the people who actually have to use said software/hardware ...
Lol.... /rant
Sent from my DROIDX using XDA App

Still nothing. CDC serial is not installed.

sly21 said:
Still nothing. CDC serial is not installed.
Click to expand...
Click to collapse
That one is a Pain in the ass. Took 35 minutes on my laptop!
Sent from my SPH-D700 using XDA App

Win7 64 not recognizing 10.1

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.

PC wont recognize device for file transfer

Just recently i tried to transfer for the first time, some wallpapers to my phone, and when i plug in the usb, the phone starts to charge normally but i cannot figure out why i cant transfer files from pc to phone or vice versa.
When i plug it in, it gives me the option to select what to "Use USB for", but when i select either MTP (file transfers) or PTP (transfer photos or files), nothing happens. I cannot browse the phone to pick anything at all.
When i go to device manager on PC i see under Portable devices the name of my phone (Moto G4 Play) but it has an exclamation point next to it. I have tried to uninstall and re-install or even update the driver but it will remain this way (if i click its propierties it tells me "This Device cannot start. Code 10"
Is there anything else i can do either on my phone or pc to make this work?
Other info:
Already downloaded motorola device manager to see if it would help but nope.
My PC OS is windows xp (yeah, i know... :laugh

My PC OS is windows xp
Click to expand...
Click to collapse
That probably explains everything
I don't think there are compatible drivers for Windows XP..

Long term support for WinXP ended three whole years ago. Though what I noticed with CM and Lineage is that the first time the phone is set up, it won't enable MTP even if checked. You have to reboot the phone and then MTP will actually enable properly.

Also, it may happen with 3rd party cables too. I myself faced this issue with Boat Indestructible cable, then I used the original cable that came with phone and successfully done it. But I still can't understand, how that cable can transfer data to/from other phones....

Just another bit of info:
Today while trying to make it work, i updated the driver from the Device Manager again and somehow i could access the phone as intended.
The problem is that after a few seconds, the window closes on its own! Then i have to redo the whole process and It gives me access again but every time, after a few seconds, the browsing window closes on its own!
I have tried with other cables and no dice, tried also rebooting phone and pc and also tried plugging it to all available usb ports. Any other tip or method i can try?

Try another pc to discard things (so you know if it's the pc or the phone)

My PC doesn't recognize my Nexus 7 2013

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.