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
Related
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
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.
Hi,
I'm having a real though time trying to connect my galaxy s1 to a pc. Have tried everything, like kies, direct connection, reseted the device, and no joy.
When I plug the cable it makes that sound as it is connecting but it doesn't show in the PC anywhere, nor even in Device manager.
It can get pwr from the usb cable when is connected; already tried with another cable and same thing.
My final goal is to unlock it.
thanks for any help
have you tried put yoy're phone in depurating mode?
I guess yo mean Debugging mode, as I couldn't found Depurating anywhere. Have selected it and the same effect
HI
I had the same problem after getting nowhere with it, for some reason and I don"t know why, I put it in download mode and then connected it to odin and my PC found it I then disconected it and its been fine eversince.
Jim
#Samsung Kies always makes problems on Windows x64 !
##I would recommend, if you got 32-Bit Computer, to use that ;-)
#If you Want just flash over Odin, then is this driver package enough
##[Link]--http://download2us.softpedia.com/dl/85b009d47a0940e89eee2297a531d100/4f577870/300141878/drivers/mobile/SAMSUNG_USB_Driver_for_Mobile_Phones_1.4.8.0.exe
#The Package is also enough for If you want just to connect to mass Storage (Phone's SD Card)
Don't Forget to Thanks, if it was useful for you!
_______________________________________________
Hi there.
By direct connection you mean the USB Mass Storage mode, right?
It might be some weird, random problem with the samsung system drivers. I used to have such problems about two years ago, back in the days of Froyo. Have you tried re-installing them? There was a link to proper drivers file in one ICS installation tutorial, and those drivers can be downloaded here. If you go about trying this method, lemme know if it worked.
Cheers.
PS: Unlike diklooc there suggested, do not never EVER go back to x86 OS. That's the worst advice. Kapisch?
Did you check your usb port in System ?
Sometimes it stuck with another lastest device
Hi,
have tried everything, and finally only in a WinXP32 could be abble to get the error shown on the file atached.
But nothing (warnings) come up in Device Manager
Unninstalled everything (kies) and tried to install only the driver and nothing happens.
Should I try to mount it on a linux?
or is it dead?
thanks
i have this problem too
wat chan I do???
my sgs can not connect to my PC
This may help...
Hi there - I don't have the same phone as you, but I did encounter the exact same problem. I've been searching around and it looks like the most common fix was to simply replace the cable. I don't know what kind of cable you have, but my phone (a Samsung Focus i917) uses a mini-usb connector. I found that my Amazon Kindle used the same connector.
When I was using the Samsung cable, I'd get intermittent connects and charge power. The OS would report unknown device. When I switched computer's = same result. I switched to my Kindle cable and the computer instantly recognized the device and installed the drivers. After 12 hours of troubleshooting, factory resetting my phone (blah - lost everything) it turned out to be the cable. I know that this isn't an easy troubleshooting step for most people, because who has an extra cable? I just got lucky that my Kindle uses the same connector. I'm now suspecting (due to the prevalence of this connectivity problem coming from people with Samsung phones - there are a LOT of reported issues) that there is probably a Samsung cable problem in general.
Good luck with your phone.
try
try select mass strong ...
Tips and unlock advice.
nasdriver said:
Hi,
I'm having a real though time trying to connect my galaxy s1 to a pc. Have tried everything, like kies, direct connection, reseted the device, and no joy.
When I plug the cable it makes that sound as it is connecting but it doesn't show in the PC anywhere, nor even in Device manager.
It can get pwr from the usb cable when is connected; already tried with another cable and same thing.
My final goal is to unlock it.
thanks for any help
Click to expand...
Click to collapse
Nasdriver, I currently have a similar problem but mine is related with Samsung Kies as I can't get either my older SGS1 or my newer Samsung Nexus to get recognized by Kies. I also suspected the cable thing and even read it could be a USB port issue but neither of them was my problem (I have 3 cables and 8 ports on 2 computers that result in the same thing). I can connect other devices with the same cables and they work, so I suspect my problem is focused around the Samsung device drivers.
My advice is if you can go in a systematic manner, first focus on the cable (easiest to replace), if you get the same results with a new cable, then focus on the USB physical port, clean it with some Isopropyl alcohol, if the port works for other devices (camera, other phones, etc..) on the same cable but not with the SGS, then try reinstalling the samsung device drivers.
Oh, and if you want to unlock your phone, the EASY way is to download the Galaxy S Unlock application from the Android market (no affiliation) it's free (but the developer does accept donations) and it WORKS. I won't bore you with my 3 week journey trying to unlock my Bell SGS phone here in Canada, had I found this app first I would have done it in less then 2 min saved myself a LOT of frustration.
Good luck
Let me start by stating that I have read through pages of various threads on here & haven't found an answer... Or at least I haven't found an answer in laymen's terms that I can understand. So, if/when offering help, please break it down for me a little. Thank you!!
I just purchased a Nexus 7. When I plug it in to my Windows 7 PC, nothing happens. It doesn't install any device drivers. It doesn't appear anywhere in my device manager. Nothing. After reading several posts, I downloaded drivers from Asus's site, but now I don't know how to install them. I came across this comment from "MrTrackZed" in another thread (one I can't yet post in):
"After you download the driver, unzip/extract its contents. Then you go to your device manager on your PC, and plug in your Nexus. You'll see it with a yellow exclamation point, right click it and select update driver. You can then select this driver manually. Also, if using Wug's root method, make sure you configure the fastboot driver as well. I don't have my PC with me, but I believe its step 6 in the driver install process. Its all very easy, sounds confusing, but its not. Good luck! "
I totally understand that, but what do I do if the device isn't even showing up in the device manager? I've plugged it in to 3 different computers (2 windows 7 & one Windows XP) and it does nothing on any of them. The device does show that it's charging, but nothing else. Please help. This is driving me nuts. Oh, and I've done all of this while having debugging on & off. Same results.
~Clint
U may just have a bad device! I have seen posts similar to this and after a device exchange they have no problems.
The fact that It doesn't register on three different computers means that or a bad cable.
Sent from my Nexus 7 using Tapatalk 2
When you plugin your phone, on your phone, you need to click USB Storage, did you do that?
Another thing to try is to enable Debuging on your phone, and install drivers, to check if device manager can detect it.
We have a package contains the right drivers for your device, you may want to download and try it. We have Nexus 7 users works fine.
http://www.vmlite.com/vaac/
This is for our vmlite vnc server, but it may help you, as it installs USB drivers.
huisinro said:
When you plugin your phone, on your phone, you need to click USB Storage, did you do that?
Another thing to try is to enable Debuging on your phone, and install drivers, to check if device manager can detect it.
We have a package contains the right drivers for your device, you may want to download and try it. We have Nexus 7 users works fine.
This is for our vmlite vnc server, but it may help you, as it installs USB drivers.
Click to expand...
Click to collapse
I did as you suggested & installed both the PC client & downloaded the app from google play. Still nothing... The device works perfectly except for this one issue. It's making me crazy!
can you run this command to debug? (open a command window on Windows)
"c:\program files\vmlite\AndroidAppController\adb.exe" devices
what is the output message?
It just occured to me that some USB cable is charging only, this morning, I got such a cable, there is no USB device showing up in device manager with that USB cable, once I switched to another data cable, it works.
You may want to change to another usb cable to test.
Problem Identified
Okay, so after much research, I think the problem has been identified. The one thing that I've found in common with all the threads that discuss this problem is that we've all, at one point or another, used a USB car charger to charge our N7. I've found that most cheap USB chargers only put out at about 1 amp. The N7 is trying to pull 2 amps. This is causing the USB cable to overheat & damage the USB connector on the N7. Unfortunately, once the damage is done, it's done. Fortunately for me, I purchased my N7 at a local retailer that had a 30 day return policy & they gave me a new N7. It works great & I've ordered a 2.1 amp USB car charger to prevent this from happening in the future.
huisinro said:
It just occured to me that some USB cable is charging only, this morning, I got such a cable, there is no USB device showing up in device manager with that USB cable, once I switched to another data cable, it works.
You may want to change to another usb cable to test.
Click to expand...
Click to collapse
Thank you for the reply, but I am using the OEM N7 USB cable. Plus, I used 3 other cables to no avail. See my previous comment though. I've identified the error.
Sorry for the bump, but are you saying that (under)charging at 1A essentially breaks the N7? Wow. You'd think it would break if you'd feed it 5A or so, not at less than 2!
I think I'm having the same issue now. I can charge, but no debugging for me since my computer doesn't even notice a USB device. Must have happened in my car once when I was trying to charge my phone and my N7 at the same time. (Since then I can't charge any phone at all in the car using that charger.) Let's see if I can find the warranty slip.
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 :|