Database Users

[Q] Won't connect to PC?

I'm having problems getting the phone to mount 100% of the time in Mass Storage mode. Occasionally it'll connect, but especially it seems when it's plugged in with the EVO it just won't get a connection. It charges fine, it shows up as a drive, but it doesn't give me access to any files or anything.
I'm using the USB drivers from the Samsung webpage specifically for the Epic 4G.

Disable "USB Debugging"

Pops_G said:
Disable "USB Debugging"
Click to expand...
Click to collapse
Try that. For some reason I couldn't mount my phone as a drive until I turned off USB debugging. Settings -> applications -> development (i believe)
I have windows 7 64bit and it works every single time now. I've transferred tons of stuff. I never even formatted my card.

RE
I couldn't get it to connect (driver installed incorrectly etc) when connecting the phone to the front port of my PC, but it worked immediately when I plugged it into the rear of the desktop.

Pops_G said:
Disable "USB Debugging"
Click to expand...
Click to collapse
I can contest to this disable usb debugging.

USB debugging has been disabled, used multiple ports, etc. and still having problems. Reinstalled drivers, manually added drivers, nothing is biting. I've also tried disabling driver signing, doing everything I can with that off and still nothing. Windows 7 Ult 64-bit in case you're curious.

Just got my Epic and had the same problem. Oddly enough though it worked with other USB ports on my computer, just not the front/top ports.
I've seen this problem before, I just cant remember where though.

Hmm, i have a Mac and the memory card is not mounting at all. had to take out microSD card and use USB card reader. Had no problems with other HTC Android phones connecting to my Mac (Hero, Evo).

Install USB Driver for the Epic.
dito33

dito33 said:
Install USB Driver for the Epic.
dito33
Click to expand...
Click to collapse
Epic USb drivers? I doubt thats needed. Maybe a updated USB driver for your computers USB ports.

Try a different usb cable I had the same issues changed the cable and no more link issues at all.

This is a rather common problem it seems like. I fixed it by using a powered USB hub. Also try using a different port, certain ports seem to not have the power needed even if the phone looks connected.
Sent from my SPH-D700 using XDA App

[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

Windows 7 64 Bit Enterprise USB Problems

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

USB 3.0 problems?

Hey I have been trying the usb 3.0 on my phone and computer obviously i have usb 3 on my pc and when ever i seem to open the file browser for my note using windows explorer it crashes almost instantly (Windows explorer is not responding) havent tried messing about with any drivers as this shouldnt be the issue, ive tried using different usb ports and enabled the usb 3.0 option on the phone?
Sent from my SM-N9005 using XDA Premium 4 mobile app

So are you using Win 8/7? A recent upgrade to OS? Using Win 8.1? Do you have USB 2.0 ports that have this crashing problem when you try and reproduce the issue or have you only tried the USB 3.0 ports only?

I have same problem
nk7 said:
So are you using Win 8/7? A recent upgrade to OS? Using Win 8.1? Do you have USB 2.0 ports that have this crashing problem when you try and reproduce the issue or have you only tried the USB 3.0 ports only?
Click to expand...
Click to collapse
I have same problem.If some one can help me, please help me.
I am using it on win 7, usb 3.0
when i am using note 3 on usb 3.0 with usb 3.0 mode selected at phone end, my pc explorer stops responding to it.
As soon as i switch to usb 2.0 at phone end(MTP Device) it starts working, even if i connect it to usb 3.0 port at PC end and switch it to MTP, it starts working.
any help is appriciated.

it's not as fast as i expected

This happens to me on literally every Android phone on every PC and laptop. XP, 7 Pro, 8 Pro, 8.1, USB2, USB3, makes no difference. It usually takes 12 minutes to load the device, and the second I click anything, it crashes explorer.exe.
It started since they got rid of USB Mass Storage. God I miss that, MTP is sheer rubbish, even iTunes is faster and more stable...

Try to reinstall your usb 3.0 hub drivers.

usb 3.0
Hey there, I have had the same problem. And here is what worked for me and hopefully work for you. In order for the USB 3.0 to work on your note 3, you have to activate developers mode. If already not. Settings-->General-->About device-->And look for "build number" (second last option) tap it seven times, it should give you a message each time you tap that says "you are 4 steps away from becoming a developer" and after you have tapped it 7 times it should say "developer mode enabled" and in about devices you should now have the dev options. Select it and check USB debugging. Un-check it and unplug your USB and re-plug it in to the USB 3.0 port i should connect as a media device. :laugh:

Has anyone found a solution to this issue? Obviously USB Debugging was not the solution. Is this more of a windows problem, android problem or samsung?

gmasterfj said:
Has anyone found a solution to this issue? Obviously USB Debugging was not the solution. Is this more of a windows problem, android problem or samsung?
Click to expand...
Click to collapse
Android.
Specifically, it's the Mass Transfer Protocol.
The device is connected as a Media Device now, meaning it isn't actually a drive. It can only support one action at the same time (So if your virusscanner is set to scan external media, you can forget opening it, as it's 'busy', resulting in a freeze and a crash.), has to work through a thousand little corners just to open, and everything done has to be converted first.
Whomever cooked up that protocol should have his head bashed in for his stupidity.

So...?
Still no solution ?
Personnaly, at least the debug mode trick made the 3rd option appear as I connect the device, but as soon as I try and check it, well an error message comes "impossible to use USB 3.0".
Is there an alternative to this mass storage protocol? is this the real reason why they didn't put usb 3.0 on the note 4? No one can make it work? not even with tweaks, xposed modules, etc?

N9005 USB problem

So recently I noticed my PC can't connect to my phone for some reason, it used to work and it still charges it.
The note shows up as SAMSUNG_Android at Devices and Printers and it shows up as SAMSUNG Mobile USB Composite Device and SAMSUNG Mobile MTP Device.
I thought it could be the cable but it still charges my phone, although it looks like that the phone disconnects and reconnects really quickly when I play with it so it could be some connection problem.
I've read that it could be BC 1.1 (fast USB3 charging) but I tried both USB2 and USB3 and it still does this and it did work before.
I've tried removing the drivers and reconnecting it, reinstalling the drivers, disabling antivirus.
If you can help I'd appreciate it!

After installing a new kernel (to use GLTools) the USB started working again, the downside is I can't update the phone through kies (or do anything through kies), if you have a solution to the kies problem post here please.