as title states.
It doesn't seem to be the samsung drivers
as I have uninstalled and reinstalled.
but the Android drivers. I have no Android drivers installed anymore
(the 3 of 4 that installs)
therefore i lose adb connectivity
*This has happened on 2 different Windows 7 installations. (switching between 2 different hdds, on this laptop)
I have usb debug on ofcourse.
I have uninstalled reinstalled latest samsung drivers.
I have installed pdanet drivers.
I have turned off phone, while connected then boot up. still no fix.
I am using acs froyo dk17. But this happened with dk05 as well.
Is there a fix for this?
I've had this problem twice. The way I fixed it was to wipe the sd card. Its a pain but that's what fixed it
Sent from my SPH-D700 using XDA App
If not a driver problem (doesn't sound like it is) the next *usual* suspect would be the usb cable. The samsung cable that shipped with these phones is crap. I got a 6' belkin one on amazon for $8 that has worked flawlessly.
Make sure you're not using a USB port that's on a hub or daughtercard. It should be one that's directly on the motherboard.
I kept fiddling with settings and rebooting both phone and computer and got past this once on my old win7 box. On my new one, I got nowhere after an hour or so. Worked first thing with the same cable on my win xp machine.
Plug your phone into a USB1 only hub, or on the same channel as a usb 1 keyboard or mouse and it will detect just fine... it won't really be useful because it won't be able to flash still (I believe it should detect as a composite device with several facets and only some of those are usb1-only compatible). I believe that the underlying problem is a bad implementation of the usb spec on one of the usb2 only parts, but I didn't feel like digging any deeper. I might try a win xp vm on the same physical hw to see if I can narrow it down to a win7 usb2 + device usb2 compatibility issue. Might be worth making sure our win7 patches are up to date, too.
Sent from my SPH-D700 using XDA App
Thanks for the replies guys.
The usb trick won't work because it's a laptop. And I tried all four of them. I only have windows 7 machines. One being a ultra sff and has like 12 usb ports. It hasn't failed me yet, but happens on the laptop.
It wouldn't hurt to get another cable, a longer one. And my sd is maxed out, I will pull it instead of format.
Thanks all
Sent from my SPH-D700 using Tapatalk
I had this problem. Plugged into the back instead if the hub and reinstalled everything. Now it's working like a charm on all usb ports. Really odd problem.
Sent from my SPH-D700 using XDA App
I had this problem. I was using a USB extension cable that was a bit long. All the other phones and USB devices worked fine with it. EPIC did not want to. I got the impression that EPIC needs more power from the USB port than most of these other devices. For me, skipping the USB extension cable did the trick. I also used a powered USB hub and that worked well too. You might want to try different USB ports. Some may provide more power than others. Also try a powered USB hub (some are built into monitors) if you have access to one.
I had the same issue with my laptop as well. It is most likely the cable. The samsung one is crap. I tried every port and installed the usb drivers a dozen times with no success. Used the cable from my wifes blackberry and worked on the first try. Just pick up a new cable. Try monoprice.com they have awesome deals.
Sent from my SPH-D700 using XDA App
I just had this problem, I switched my cable and then it worked fine.
hayabusa1300cc said:
as title states.
It doesn't seem to be the samsung drivers
as I have uninstalled and reinstalled.
but the Android drivers. I have no Android drivers installed anymore
(the 3 of 4 that installs)
therefore i lose adb connectivity
*This has happened on 2 different Windows 7 installations. (switching between 2 different hdds, on this laptop)
I have usb debug on ofcourse.
I have uninstalled reinstalled latest samsung drivers.
I have installed pdanet drivers.
I have turned off phone, while connected then boot up. still no fix.
I am using acs froyo dk17. But this happened with dk05 as well.
Is there a fix for this?
Click to expand...
Click to collapse
Also make sure your antivirus is off although that's likely not the culprit. Do you install the drivers as administrator?
Try a new cord. If that doesn't work, try deleting/uninstalling the device and/or hub from the device manager - plug the phone in, letting win7 do its worst by not recognizing it, then open the device manager and find the usb hub. try deleting/uninstalling. unplug the phone and scan for hardware changes. I think this may force windows to reinstall the drivers for the usb hub. Disclaimer, it's been a while since I spent significant time fooling with windows computers so take this advice at your own risk - I'm feeling my way like an old man with cataracts trying to find his way around his long-lost childhood home. in the dark. With unfamiliar furniture. In an earthquake. While in a wheelchair. With flat tires....
My computer did this for a while and now it doesn't although it's certainly possible I changed the cord I was using.
The best way to get drivers to work is install PDAnet IMO..
I had driver problems upon driver problems.. swapped cables, etc.
went through all the motions that you all are describing here and what fixed it for me was installing PDAnet. Worked like a charm.
Hope this helps.
I agree about using pdanet for drivers. Unfortunately this problem isn't with the driver not being installed correctly. I got it on one machine and not another, using the same friver. In fact I got it to work on the same machinewith the same driver ... just different ports (one was stuck in usb1/ohci nd worked, the usb2 port never worked on one machine and a usb1 port never worked on a different one).
Sent from my SPH-D700 using XDA App
warlar12 said:
I just had this problem, I switched my cable and then it worked fine.
Click to expand...
Click to collapse
This worked for me when I had the problem. This will be the second time I had a usb cable go bad on me. Maybe I shouldn't buy those cheap ones from China...
I've had this problem with numerous cables on Dell E series laptops with 3 Epics and a Moment. For the life of me I couldn't get the phone to be recognized when using the USB ports on the left side of the machine. Plugged it into the ones on the right and have never had a problem. I think with the Dells it's a low current issue on the left side ports. The shorter the USB cable the better off you'll be if it is a low current problem.
thanks but i did alot of that last night and today, uninstall/reinstall drivers, usb hubs.. nothing
i may need to try another cable because i am workign on a friends epic sunday.
bilestoad said:
Also make sure your antivirus is off although that's likely not the culprit. Do you install the drivers as administrator?
Try a new cord. If that doesn't work, try deleting/uninstalling the device and/or hub from the device manager - plug the phone in, letting win7 do its worst by not recognizing it, then open the device manager and find the usb hub. try deleting/uninstalling. unplug the phone and scan for hardware changes. I think this may force windows to reinstall the drivers for the usb hub. Disclaimer, it's been a while since I spent significant time fooling with windows computers so take this advice at your own risk - I'm feeling my way like an old man with cataracts trying to find his way around his long-lost childhood home. in the dark. With unfamiliar furniture. In an earthquake. While in a wheelchair. With flat tires....
My computer did this for a while and now it doesn't although it's certainly possible I changed the cord I was using.
Click to expand...
Click to collapse
It HAS to be the power differences NOT cable.
Same cable as I charge with, plugged into the front of the computer (hub).
Plugged into the back of the computer recignized the first time.
=USB power
In my case, tried several micro USB cables, no dice. Tried my laptop and desktop, no dice. Tried USB hub or direct to PC usb ports, no dice. Device manager shows the right comm port but all the one-click roots i've tried can't find the phone. USB storage has never mounted for me from day one either.
Sigh, never had this issue with any other Android phone.
Finally figured out my issue. I had set it to "modem" while doing something else in an epst menu rather than "pda". Since I corrected that, works dandy.
I feel so stupid.
Forgive My Brevity. To Be Or Not To Be...
Would using my friends droid x cable work with the Samsung epic?
Sent from my SPH-D700 using XDA App
Related
All of a sudden my pc is not recognizing phone as a usb drive.. It was working perfectly since day one with this phone but since yesterday it wont recognize it.. And even if it does, it takes a very long time. ive treid uninstalling the drivers and reinstalling, as well as turning debugging on and off. My pc is running windows 7 64bit.. I have also tried different roms and nothing.. When connected in debugging mode, it recognizes it immediately and installs drivers by i still cannot view my storage card.. Any help would be appreciatied.. Thanks
Install pdanet on your computer. When it gets to the part about driver installation, select samsung and voila.
Sent from my SPH-D700 using XDA App
Try another USB cable.
rufflez2010 said:
Install pdanet on your computer. When it gets to the part about driver installation, select samsung and voila.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Oops forgot to mention i did that as well.. still not working.. Maybe ill have to buy another usb cable..
jok3sta said:
Oops forgot to mention i did that as well.. still not working.. Maybe ill have to buy another usb cable..
Click to expand...
Click to collapse
:-\ sucks... hey, got to use the emoticons!!!! Ayways, yeah, sounds like the cable is dead. The one from my lg dare doesn= work for data tranfer, so I turned it into my car charger.
Sent from my SPH-D700 using XDA App
Firon said:
Try another USB cable.
Click to expand...
Click to collapse
Seconded. I bought a cheap charging kit and the cable would charge but would not allow file transfer. Took it back, bought another cable and it's fine.
Either the phone is finicky about cables, or it might just require a particular type (probably USB 2.0).
I had this issue also last week. I tried another cable and it worked fine.
But now I am having issues with my usb ports in general. Now they just stop working every once in a while and I am required to restart my laptop.
Don't know if the two problems are related.
Try different USB ports. Like the ones on the back on your computer.
I've been having the same issue. I went out to Radio Shack and bought a new data cable. So far all ports on my laptop, winXP pro 32bit, and my win7 64bit desktop have not had problems.
I'm thinking that the USB cable supplied by Samsung is crap. I tested them both out on the same machine, same port; the new one worked fine, while the stock cable only gave me adb access.
I had this same exact problem. I kept thinking the phone was going bad or something. I tried the cable that came with my Epic & the one that came with my Moment, both didn't work... for some reason it worked find on a Mac though. So when I gave my mom my Moment when I got the Epic she bought an extra micro-USB cable and I decided to try that one, for some odd reason, that one worked.
Still don't know exactly what was going on but a third-party cable fixed the problem for me.
Hope this helps.
After failing again and again and again, reinstalling the drivers, reinstalling KIES (which simply won't work on my machine), removing the battery etc. etc. etc. I just don't know what there is left to do...
When in Win7, the phone is recognized, although Windows tells me that it's not connected to a USB2 hub. In download mode it says connection failed. What else am I supposed to do?
The phone is not branded or anything, applying stuff though update.zip's was never an issue.
So please somebody help me - I'm stuck with JF3
simple, switch to another computer
unless you can find and easy way to make windows forget the USB bugs
you need to also unplug the PC and wait for the PC to power drain, reconnect the PC power cord, and turn the PC back on.
after it goes back to windows try hooking up the phone again, if you get the message about not running in USB2 mode, then it failed
retry after resetting BIOS settings, installing USB2 drivers, etc.
Sent from my GT-I9000M using XDA App
I had a similar problem...
I had a USB 1.1 Port on my Thinkpad T22 and the drivers didnt like it
Use a different computer/USB port
...btw I still like JF3
Now you will probably feel the urge to smack my head against the wall when you read what I'm about to tell you... I don't blame ya... The cause of the "problem" was that I wasn't using the original Samsung USB cable that came with the phone. I just couldn't find it so I decided to use an aftermarket cable which I had lying around. Big mistake... I finally found the USB cord and that fixed everything for me. Beware of aftermarket accessories as the phone will punish you for using them!
that cable might have been a very poor after market version then
i do use a couple of after market USB to micro USB cable with the phone and it works fine
there are bad aftermarket products
and there are quality aftermarket products
I remember having a few mini USB cable with my old G1, and had similar problem. With one cable it was recognising, with the other one didnt.
Don't know what difference they have, but it's indeed wierd!
I was using a nokia usb cable to flash my samsung
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
I am trying to install the Samsung Intercept (Virgin Mobile) on my Windows 7 netbook. I could never connect the device before to either WinXP or Win7. I recently factory reset my phone and after installing the drivers on WinXP, the phone showed that it was connected. I mounted the SD card to the computer and it never showed the drive. I unmounted and disconnected and since then it never connected. I keep getting that it's not recognized.
On my Win7 computer, I installed the drivers (had to force Windows to find the driver). Now the computer senses that it's connected, but it says "the device cannot be started". So I'm thinking that my P.O.S. phone can't figure out wtf USB mode is. It showed it once and that's it.
I've tried probably 3 or 4 different drivers and now I can't figure out how to just start clean. I don't even think I need to because the computer driver installed fine (It says Samsung USB Android whatever when it's connected). I tried with USB debugging on and off.
I even tried to make a virtual Windows XP to try it on a fresh install, but VM won't take unknown USB devices.
I uninstalled all my drivers, even the USB hub drivers, rebooted after the uninstall. No luck.
Before I reinstalled the hub I tried to force XP to the drivers (different ones not the same driver over and over) and now its saying "the file does not contain any information about this device". WTF?!
I'm so confused with this stupid driver that I can't take it anymore. I'm now considering reformatting my computer, but it's not worth it just to root a phone. I'd rather put up with my phone needing a battery pull at least once a day than to lose all my files.
caderyn19 said:
I am trying to install the Samsung Intercept (Virgin Mobile) on my Windows 7 netbook. I could never connect the device before to either WinXP or Win7. I recently factory reset my phone and after installing the drivers on WinXP, the phone showed that it was connected. I mounted the SD card to the computer and it never showed the drive. I unmounted and disconnected and since then it never connected. I keep getting that it's not recognized.
On my Win7 computer, I installed the drivers (had to force Windows to find the driver). Now the computer senses that it's connected, but it says "the device cannot be started". So I'm thinking that my P.O.S. phone can't figure out wtf USB mode is. It showed it once and that's it.
I've tried probably 3 or 4 different drivers and now I can't figure out how to just start clean. I don't even think I need to because the computer driver installed fine (It says Samsung USB Android whatever when it's connected). I tried with USB debugging on and off.
Click to expand...
Click to collapse
I had the same issue too.
Have you tried using another USB cable? If you're using the cable that came with the phone it wont work (well sometimes). What you can do is find or buy another Micro USB cable for your intercept. You can buy one off amazon for less than $10. I brought mine from Best buy for $20. It works fantastically.
scream4cheese said:
I had the same issue too.
Have you tried using another USB cable? If you're using the cable that came with the phone it wont work (well sometimes). What you can do is find or buy another Micro USB cable for your intercept. You can buy one off amazon for less than $10. I brought mine from Best buy for $20. It works fantastic.
Click to expand...
Click to collapse
I was seriously considering another cable because I read in some other threads pretty much what you just told me, but I guess I was one of those "on the twelth time it finally connects" type of situations. I connected it last night and it worked. Just need to update my SDK stuff, make sure I have all my info for SuperOneClick, and cross my fingers lol!
Thank you for your advice. If it stops working I'm gettilng a new cable.
[EDIT] and it stopped working... I knew I should've just rooted when I had it connected, but I wanted to back my stuff up. Looks like I'm getting a new cable lol.
Sent from my SPH-M910 using Tapatalk
[EDIT] You were totally right! It's the cable. I got a Belkin for $15 at Target. I plugged it in and immediately Windows 7 Pro 32-bit detected the drivers, the handset, and installed it. Now time for rooting
I know it's been a couple of months, but I'm curious if you've had any other problems with connecting?
I was having the same problem and I had a few cables that I tried with no luck. I also tried my wife's Blackberry cable, which is a thicker cable that claims to be a "DATA" cable...no go.
I probably will just go buy the Belkin one you referred to if you've had no other problems.
Thanks!
-- Sent from my Galaxy Tab using Tapatalk
GreyCelt said:
I know it's been a couple of months, but I'm curious if you've had any other problems with connecting?
I was having the same problem and I had a few cables that I tried with no luck. I also tried my wife's Blackberry cable, which is a thicker cable that claims to be a "DATA" cable...no go.
I probably will just go buy the Belkin one you referred to if you've had no other problems.
Thanks!
-- Sent from my Galaxy Tab using Tapatalk
Click to expand...
Click to collapse
I actually have had no problems (on my Win7 PC) since the install. As for my XP computer, I just gave up on trying to get it to work. Try completely uninstalling every instance of the Samsung programs (I went through my registry *dangerous*) and all things Android and reboot to a fresh power cycle (like with the phone) so Windows can update all its important files reguarding the driver removal. Then install and THEN plugin.
It literally randomly worked for me. I had the drivers installed properly, but the charging cord gave me "bad driver install". I didn't change a thing and plugged in wth the Belkin and was good to go.
Hope you can get it working! I know the anticipation of phone modding, and I love it! Lol!
Sent from my SPH-M910 using Tapatalk
Ditto, ditto and ditto! I have the same thing with my intercept, except I started on win7/64, could not get anything going. Then created an XP VM - over my dead body - no go.
Using the same cable, if I plug in my Captivate, everything comes up.
For you guys, when you bought a different cable, what did you buy? micro-to-micro USB? Or something else?
J
I usually use the cables that came with my HTC phones. Also I have better luck if I reboot the phone prior to connecting it to the PC.
Hey all. Just got my Galaxy S4 today and I was loving everything about it until... right now. For some reason, the darn USB won't stay connected to the computer. It doesn't matter if it's simply plugged into the computer as an "installer" or as a media device. It'll constantly disconnect and reconnect itself, even when I'm not transferring any files.
It's not the my computer/USB ports, either, since I can transfer files between my HTC Thunderbolt and Nexus 7 fine. I've also tested 2 other USB cables and they all behave the same way.
Anyone know what's going on? Did I get a lemon?
No im in the same boat. Was trying ti connect in today. I reinstalled and un installed the drivers about 4 times. Tried un selecting usb debugging in developers menu. Installed kies and used the drivers from it still no good. Used 3 different usb leads. Phone will still charge from pc and even when im installing the drivers again and connect the phone it will say that your new device is ready to use but still cant access phone, it simply does not show up.
Wouldn mind was working 2 days ago fine. Same usb port and all. And the port is fine cause my old s3 still reads from the same port.
snwman said:
No im in the same boat. Was trying ti connect in today. I reinstalled and un installed the drivers about 4 times. Tried un selecting usb debugging in developers menu. Installed kies and used the drivers from it still no good. Used 3 different usb leads. Phone will still charge from pc and even when im installing the drivers again and connect the phone it will say that your new device is ready to use but still cant access phone, it simply does not show up.
Wouldn mind was working 2 days ago fine. Same usb port and all. And the port is fine cause my old s3 still reads from the same port.
Click to expand...
Click to collapse
same problem with me!
every thing ok with s3 but the problem only with s4
please we need help to solve this problem!
Same problem
I have also been dealing with this for a while now. I have Windows 7 64bit and I have reinstalled the drivers many times through Kies and manually. It seems like the problem is getting worse since initially I could do some file transfer through usb if i fiddled with the device (changing usb ports, unplugging it, etc). Now I am hard pressed to get it to show up on the computer through MTP at all.
This is quite annoying since I am developing an android app and I need a usb connection in order to test it. A fix would be awesome.
I just tested on my sister's laptop and it doesn't have this problem. I clicked around the phone, transferred a 10gb movie, and left it plugged in to see if there were any signs of disconnects. None whatsoever. Odd. Maybe Galaxy S4 just doesn't like something with our computers. This is quite annoying.
I have a fresh Windows 7 64-bit partition I installed the other day so I'll test it out on that and report the results later today.
retsnom said:
I just tested on my sister's laptop and it doesn't have this problem. I clicked around the phone, transferred a 10gb movie, and left it plugged in to see if there were any signs of disconnects. None whatsoever. Odd. Maybe Galaxy S4 just doesn't like something with our computers. This is quite annoying.
I have a fresh Windows 7 64-bit partition I installed the other day so I'll test it out on that and report the results later today.
Click to expand...
Click to collapse
I do same thing, it is worked in another computer.
I am already put fresh win 7 but still same problem..
im on xp(retro yeah ha ha) but just a pc i have for my phones and stuff. But i got it working again by flashing my firmware through odin and its back working. Im blaming when i rooted it that it broke but ill see if it happens again
edit: Can confirm pc is now picking up phone. I just flashed the most recent stock rom for my carrier through odin and as soon as it finished updating its prefect now. Might wait another while to root it now and wait for more devs to jump aboard for more roms
snwman said:
im on xp(retro yeah ha ha) but just a pc i have for my phones and stuff. But i got it working again by flashing my firmware through odin and its back working. Im blaming when i rooted it that it broke but ill see if it happens again
edit: Can confirm pc is now picking up phone. I just flashed the most recent stock rom for my carrier through odin and as soon as it finished updating its prefect now. Might wait another while to root it now and wait for more devs to jump aboard for more roms
Click to expand...
Click to collapse
I'm on stock, no root.
Hi
I don't know if it may help but i noticed the usb doesn't work when the phone is locked.
I did check 'stay active while charging' in dev parameters and i never got disconnected again.
Sent from my GT-I9505 using xda app-developers app
Tested it out on a fresh copy of Windows 7 and it still continuously disconnect. What gives?
taargaa said:
Hi
I don't know if it may help but i noticed the usb doesn't work when the phone is locked.
I did check 'stay active while charging' in dev parameters and i never got disconnected again.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Oops, missed your post. Unfortunately, it disconnects regardless of the phone's state.
My friend's S4 was doing the same thing on his desktop. Every time he would try to transfer pics the phone would disconnect after a few files.
I tried different things from reinstalling drivers to trying to only copy over a couple of files at a time, nothing worked.
Finally I plugged his phone into one of the back usb ports and transferred over 2gb with no problem and no disconnects since.
My guess is the S4 is a power hog and some usb ports just don't supply enough juice. Try plugging it in to a usb port that comes off a motherboard. Don't use the front ports or usb hubs. Hope this helps someone.
dirrtpoor said:
My friend's S4 was doing the same thing on his desktop. Every time he would try to transfer pics the phone would disconnect after a few files.
I tried different things from reinstalling drivers to trying to only copy over a couple of files at a time, nothing worked.
Finally I plugged his phone into one of the back usb ports and transferred over 2gb with no problem and no disconnects since.
My guess is the S4 is a power hog and some usb ports just don't supply enough juice. Try plugging it in to a usb port that comes off a motherboard. Don't use the front ports or usb hubs. Hope this helps someone.
Click to expand...
Click to collapse
I've been trying all kinds of different combinations of USB leads, phone settings and ports all morning and was just about getting ready to start a new Olympic sport of S4 hurling when I came across this post and plugged my USB straight into the back of my machine and it finally works!! Thank you dirrtpoor for your input - a simple fix, but nevertheless it worked.:good:
I suppose it makes sense that a quad core 1.9Ghz phone would be a power hog.
It wouldn't work on my home PC whatever I tried. Front or back USB ports.
On my dads PC sometimes it would display OK and other times "usb device has malfunctioned" (didn't try the rear USB port)
On my work PC it works fine on the rear ports.
I was having the same problem a few days ago, but then I reformatted the SD card, now everything seems OK.
Even the stock gallery app works now...?!
Guys I was having the same problem. For the life of me I couldn't figure out why suddenly my S4 wasn't being recognized by my computer. I finally went into developer options and noticed a "USB Debugging - Debugging mode launches when USB is connected" was turned on. I de-selected that, connected my phone and now my computer recognizes it again. I hope that helps guys, it helped me.
Samsung S4 sync problem
mgrisan1 said:
Guys I was having the same problem. For the life of me I couldn't figure out why suddenly my S4 wasn't being recognized by my computer. I finally went into developer options and noticed a "USB Debugging - Debugging mode launches when USB is connected" was turned on. I de-selected that, connected my phone and now my computer recognizes it again. I hope that helps guys, it helped me.
Click to expand...
Click to collapse
This may be laughably obvious but I'm a former Apple user, which has it's own dedicated USB connector, so I forget sometimes with the Samsung S4, which has a standard (looking) micro USB connector that I need a USB cable that is enabled for syncing as well as charging...not all USB cords with micro connectors on the phone end will carry the data because I imagine Samsung has made their phone's connector require a different wiring in the cable.
I was pulling my hair out yesterday trying to figure out why the computer wouldn't see the phone..then looked at the USB cable and realized I'd plugged a non-syncing cable in. I tried the cable that came with the phone and bingo, worked like it was supposed to.
Hope this helps, sometimes it's the little things we overlook that drive us nuts.
Any way to connect in master storage with out root.
Sent from my GT-I9500 using Tapatalk 4
Use a different usb cable and usb port. I know it sounds stupid but there has definitely been phantom problems which were solved this way, even with something as simple as adb commands
i have same problem. trying all the way but always with the same result...