Related
I've recently run into a problem with my phone being recognized by my computer... basically it just doesn't work anymore. This happened after upgrading from Midnight ROM 5.3 to ACS Frozen 1.2. At this point, when I plug my phone into the computer, it only charges and does not enter into usb connected mode. On the computer I get a pop-up message saying that the USB Device is not recognized. After searching through these forums and others, I have tried uninstalling / reinstalling drivers, installing PDANet, switching USB ports, and Switching USB cables... All multiple times. The best I've gotten out of the process is immediately after certain tries, I am able to get the usb mode activated, but only once. When I try to boot the phone into download mode because I'm trying to upgrade to EF02, it is no longer recognized, and then when I do a regular boot, it is still no longer recognized.
Any help would be appreciated.
Thanks,
Greg
I've also toggled USB debugging multiple times...
Which OS is your PC running?
Sent from my SPH-D700 using XDA App
Try downloading the android sdk and updating all its files and repo's? I had to do that for my w7 x64 pc to see my epic
Posted by some phone named the Epic.
Your drivers crapped out or your cable is flaky. Try a different cable. Also turn on USB debugging and go into Device Manager in system in control panel. Go to the unknown USB device (may say Samsung Android) and hit update driver and let it search Windows update for drivers, will take a long time for all the drivers. Then reboot and should work.
Are you using the cable that came with your phone? Mine stopped working and I had to buy a new cord off amazon.
Sent from my SPH-D700 using XDA App
Win 7 x64 is the OS...
I've found a temporary workaround by pulling the battery, plugging the device into the usb, starting it into download mode, and then replacing the battery, but thats not really practical for storage purposes, only for the one time install of EF02. I have used 4 different cables and reinstalled the drivers multiple times. I am going to try reinstalling the sdk and see if that helps, as well as searching drivers using Win 7 Device Manager.
treblesum81 said:
I've recently run into a problem with my phone being recognized by my computer... basically it just doesn't work anymore. This happened after upgrading from Midnight ROM 5.3 to ACS Frozen 1.2. At this point, when I plug my phone into the computer, it only charges and does not enter into usb connected mode. On the computer I get a pop-up message saying that the USB Device is not recognized. After searching through these forums and others, I have tried uninstalling / reinstalling drivers, installing PDANet, switching USB ports, and Switching USB cables... All multiple times. The best I've gotten out of the process is immediately after certain tries, I am able to get the usb mode activated, but only once. When I try to boot the phone into download mode because I'm trying to upgrade to EF02, it is no longer recognized, and then when I do a regular boot, it is still no longer recognized.
Any help would be appreciated.
Thanks,
Greg
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1042746
Try this had the same problem this worked for me trust me it works
Sent from my SPH-D700 using XDA App
Hi All, I've got a USB connection problem with my Galaxy Nexus. When I connect it to a computer, it will start charging, but doesn't show that it's connected to a computer and the computer doesn't show that a device is connected. I've tried on a few different Windows machines and don't get any change in the device manager. There is no "unknown device" nor device with an error. I've been searching the Internet and this forum, but still can't find the problem after a couple of days. Here's some details and things I've done:
I did not install the "force fast charge" kernel mod.
I've tried a couple different cables and verified that the cables worked with my wife's Galaxy II.
I've tried several different computers.
I've tried MTP and PTP storage options.
I rebooted everything several times.
I drank heavily.
I tried a factory reset.
I updated Windows Media Player to get the latest MTP software.
I installed drivers packages even though it never gets to the point of installing drivers.
Does anyone have any other ideas before I smash this thing with a hammer?
Does anyone have any ideas? At this point, I'm thinking there is a hardware problem.
Go into Menu -> System Settings -> Developer Options -> Turn on USB Debugging.
Not a guarantee, but something to rule out.
I've got USB Debuging on. Thanks for the reply.
Can anyone help? I'm having the same exact problem. My phone charge but is not detected by my computer. I am having this problem right after flashing AOKP ROM B35. This is very important, one mistake and my phone will be bricked as a computer to phone is so important !! There is nothing detected at all under device manager. Tried it on several laptop to make sure it isn't just my computer.
someone?
Uninstall the drivers you have for the s2. Reboot and install the official drivers for the galaxy nexus. Reboot. Then try.
If that doesn't work... let the phone load a while and just keep trying other ports on the computer. I saw this with my other gnex that it would take a while to realize a USB to be connected. Also make sure the USB is in completely... don't jam it in but make sure you know its All the way in. ( no pun intended) What's funny is my gnex will detect it instantly... but the other one takes a few tries.
Sent From My Sprint Galaxy Nexus via Xda Premium
Thank you dude. It doesn't work. Prior to installing this rom, my nexus is detected instantly. There is something wrong with the process i root or something. Now i can't do anything as It is not detected by my computer. Someone please help.
Indeed is the rom that is causing the problem. I opened NEXUS toolkit and rebooted my phone into boot image. It will sense it and i can operate from there. I've restored to factory and now my phone is being detected. I hope the thread starter gained something out of it too
Okay, this is the second time this error has popped up and it's starting to get on my nerves. Anytime I plug my phone into ANY USB port, and this is counting both 2.0 and 3.0 ports, I get the error bubble: Hardware ID Missing. Windows cannot identify the device plugged into the SAMSUNG Mobile USB Composite Device." Honestly, this is beyond irritating.
For one, I am not going to reinstall Windows 7. That's too much hassle for this. Second, ever since someone plugged their Droid into my USB cable so they could charge up their phone, this message started appearing. I tried to reinstall drivers (Samsung driver exe said it couldn't install), uninstall, disable, etc etc, but finally managed to get the damn computer to read it when I stuck it in the 3.0 USB port. Now, just 10 minutes ago, I plug the phone in, I get that error, on a 3.0 USB port.
So, now I have no idea what is going on, nor how to fix it. I've tried searching, but there are no answers. Or, the possible "solutions" don't even work even remotely close.
I could really use some help on this. And, again, please do not mention "Reinstall Windows". That's just too much of a hassle and I'm not going to do that.
You may not want to try this either but try a system restore
Sent from my SPH-L710...if some one helps you press the thanks button
Volknochi said:
Okay, this is the second time this error has popped up and it's starting to get on my nerves. Anytime I plug my phone into ANY USB port, and this is counting both 2.0 and 3.0 ports, I get the error bubble: Hardware ID Missing. Windows cannot identify the device plugged into the SAMSUNG Mobile USB Composite Device." Honestly, this is beyond irritating.
For one, I am not going to reinstall Windows 7. That's too much hassle for this. Second, ever since someone plugged their Droid into my USB cable so they could charge up their phone, this message started appearing. I tried to reinstall drivers (Samsung driver exe said it couldn't install), uninstall, disable, etc etc, but finally managed to get the damn computer to read it when I stuck it in the 3.0 USB port. Now, just 10 minutes ago, I plug the phone in, I get that error, on a 3.0 USB port.
So, now I have no idea what is going on, nor how to fix it. I've tried searching, but there are no answers. Or, the possible "solutions" don't even work even remotely close.
I could really use some help on this. And, again, please do not mention "Reinstall Windows". That's just too much of a hassle and I'm not going to do that.
Click to expand...
Click to collapse
I had the same issue what ended up fixing it for me was watching when I plugged the phone in after a clean driver install and stopping Windows from downloading and installing an updated driver. Dont know if its the same for you but that fixed it for me. I was really frustrated by it and found no help either.
probably an easy fix
definitely don't need to reinstall windows or do a restore. But just to be sure, you don't have kies installed right? Seems to cause problems.if there's no kies installed, go into the device manager and find your phone whatever it's listed as right click and uninstall. Check the little box that says, "delete the driver software for this device". do this for any devices relating to yours. Including the stuff under modems,ports,USB controllers.and tick that box that delete driver software for this device every time you uninstall something. Now, not saying it's necessary but wouldnt hurt, reboot the pc. Then with your phone unplugged, reinstall the Samsung drivers for the phone. Now to make sure windows doesn't DL its own drivers,disconnect from the internet and plug the phone back in. Should be all good.
I won't do a system restore, that won't do anything. Not to mention it would erase some programs that were installed (not related to phone). So, not doing that. Also, my computer will not automatically update any drivers or any thing else, as I have it set to manual mode.
And, I do not have Kies installed. It never worked for me properly, when it came to driver installation. I've done the "go into device manager" bit many times before, it still likes to play the "Hardware ID doesn't match" card. Drivers won't install either. I don't know what it is, but damn this is the most stubborn thing I've ever encountered.
i've post this in other forums today. what i do to get it working is i toggle USB debugging and try it out, then start toggling the ptp and mtp until it works. the combo that works for me is turn on debug, plug in computer, unplug, turn off debug, plug in. if it doesnt work then i toggle back and forth MTP and PTP. 5 tries at most, for me. Also, i did a nandroid back to my oem ICS that was 2 weeks old and just rooted. the problem is worse there. i'm using freegsmr6 with trinity kernel on Tmo. hope it helps.
Ditto
Yeah that whole "Hardware ID missing" was an irritating situation. This is what I recommend as far as making it work.
1. Plug in.
2. When you get the error message, I think its because of a conflict with the ADB interface. Go to Settings, Developer Options, and check off USB Debugging.
3. Plug in once again and it should work. If not, try toggling between Camera and MTP.
I have Windows 7 Ultimate and it works fine for me
I always get that error as well with my SGS 3. I have to reinstall Kies everytime it does that which is annoying.. ANyone has a permanent solution about this?
Fix for me was...
1-plug in phone. Get the hardware ID message. Leave phone plugged in.
2- open device manager. Click on. Android Phone and Uninstall Samsung Android ADB Interface. Also check the "delete software driver" when the dialog box shows.
3-still in device manager. Scroll down to Universal Serial Bus Controllers. Uninstall Samsung Mobile USB Composite Device.
4-unplug phone.
5-reboot pc.
6-install SAMSUNG USB drivers from their site or from here
http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html?m=1
7-reboot or not. Plug in phone.
This worked for me and no issues for the last 6 days. YMMV..
this works!
stevounit said:
yeah that whole "hardware id missing" was an irritating situation. This is what i recommend as far as making it work.
1. Plug in.
2. When you get the error message, i think its because of a conflict with the adb interface. Go to settings, developer options, and check off usb debugging.
3. Plug in once again and it should work. If not, try toggling between camera and mtp.
I have windows 7 ultimate and it works fine for me :d
Click to expand...
Click to collapse
But why this problem now out of nowhere when everything worked fine before.
Sent from my SPH-L710 using xda app-developers app
Hardware ID missing - SOLVED!!
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
I've done just that, I've connected my S3 to the PC several times, I've also rebooted twice and I've never seen that stupid message again - while of course everything works as expected.
:good::good:4 days later, several times rebooted (phone and PC), several connections with Kies and I have NEVER seen that error again - it works!!
UPDATE!! (Oct.11.2012)
After a few Kies updates and going through various ROM's:
- the procedure listed above works 100% but a few steps are just not needed (redundant) - see bellow
- the problem is mostly caused by Windows "forcefully" trying to install its own drivers, rather than allowing Samsung's suggested.
- Samsung's fault is providing "updated" drivers that don't always work (hence, use the suggested 1.4.6.0 drivers)
- Following EVERY Kies update, DISCONNECT from internet before plugging your phone (otherwise you'll have to go through this, AGAIN).
Some suggested here that plugging the phone into a different USB port (without disconnecting from internet) would be the culprit - which happens to be true, but as a mere effect, not the cause: every time an unknown device is plugged into a different USB port, Windows is trying to download/install the appropriate drivers if it doesn't recognize the hardware - and there you are again.
So, the simplified procedure becomes:
1. Not needed - leave Kies installed, as is - no harm at all
2. N/A
3. YES
4. Not (always) required
5. MUST
6. MUST
7. MUST
8. Yes
Furthermore, if still interested in connecting your I747(M) as UMS (USB mass storage) the solution presented here works. I tested it myself - read my comment on this post for the very few existing hiccups.
- while installing the USB mass storage device drivers you don't have to disconnect from the internet
Install Drivers
Have you tried just installing the drivers directly from Samsung? That is all I did when I had problems and it worked.
tyler1037 said:
Have you tried just installing the drivers directly from Samsung? That is all I did when I had problems and it worked.
Click to expand...
Click to collapse
For someone experiencing the "hardware ID missing" error, just reinstalling the drivers won't do anything. Like many others, I've been banging my head trying to solve this for quite some time; the suggested steps are truly a compilation of successful ideas and trials mingled with tons of frustration, coming from my own experience as well as from many different people and forums.
If, on the other hand, you had a different type of connectivity issues - without this error, then, yes, reinstalling the drivers is Samsung's recommendation.
billard412 said:
definitely don't need to reinstall windows or do a restore. But just to be sure, you don't have kies installed right? Seems to cause problems.if there's no kies installed, go into the device manager and find your phone whatever it's listed as right click and uninstall. Check the little box that says, "delete the driver software for this device". do this for any devices relating to yours. Including the stuff under modems,ports,USB controllers.and tick that box that delete driver software for this device every time you uninstall something. Now, not saying it's necessary but wouldnt hurt, reboot the pc. Then with your phone unplugged, reinstall the Samsung drivers for the phone. Now to make sure windows doesn't DL its own drivers,disconnect from the internet and plug the phone back in. Should be all good.
Click to expand...
Click to collapse
Just wanted to say thank you. Did this and the last 2 days, works everytime. I made sure that after the first time I plugged the phone in after doing all this, and the screen pops up asking what I wanted to do, made sure to check the box for "do this everytime" and then choose the view folder option or whatever that is.
Thank you again,
Whiteice
One thing I have tried which might help others - I had the Android Developers toolkit installed on my machine, which I've removed and I also removed the HTC Sync software which was for my old desire.
Rebooted, installed the SG Toolkit (can't remember which post I found it in) and then chose option one after selecting firmware to install drivers.
I cancelled the "Windows Updates" bit of the driver detection and it found the first item, and had "item disconnected" for the remaining three.
Unplugged and plugged back in and voila it works.
This worked for approx 5 mins and then stopped, however I did all the above with debugging on, debugging is now off and all seems well (touch wood). However looking at putting on a different kernal to expose storage as mass storage and also get around cifs issues.
Hope this helps someone.
nacos said:
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
I've done just that, I've connected my S3 to the PC several times, I've also rebooted twice and I've never seen that stupid message again - while of course everything works as expected.
:good::good:4 days later, several times rebooted (phone and PC), several connections with Kies and I have NEVER seen that error again - it works!!
Click to expand...
Click to collapse
Thank you so much for this. This solution worked for me.
nacos said:
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
I've done just that, I've connected my S3 to the PC several times, I've also rebooted twice and I've never seen that stupid message again - while of course everything works as expected.
:good::good:4 days later, several times rebooted (phone and PC), several connections with Kies and I have NEVER seen that error again - it works!!
Click to expand...
Click to collapse
Thanks for this i will try it tomorrow as still new to these tabs.
For moment i change to camera PTP and it pops up, so at least i can use it for now.
Will let you know how i get on.
Best wishes :good:
adamspud said:
One thing I have tried which might help others - I had the Android Developers toolkit installed on my machine, which I've removed and I also removed the HTC Sync software which was for my old desire.
Rebooted, installed the SG Toolkit (can't remember which post I found it in) and then chose option one after selecting firmware to install drivers.
I cancelled the "Windows Updates" bit of the driver detection and it found the first item, and had "item disconnected" for the remaining three.
Unplugged and plugged back in and voila it works.
This worked for approx 5 mins and then stopped, however I did all the above with debugging on, debugging is now off and all seems well (touch wood). However looking at putting on a different kernal to expose storage as mass storage and also get around cifs issues.
Hope this helps someone.
Click to expand...
Click to collapse
The Android Developers toolkit DOES install the USB drivers 1.4.6.0 - which seems to be the ONLY one that works, BUT the rest of the steps suggested in my previous post are needed in order to get rid of the problem - otherwise the fix is just temporary.
Re-loading OS drivers corrected issue.
tyler1037 said:
Have you tried just installing the drivers directly from Samsung? That is all I did when I had problems and it worked.
Click to expand...
Click to collapse
I removed the updates to Kies on my Note and uninstalled the Kies update on the PC which is what started this issue of the OS not recognizing the device and then a fresh driver load for my phone from the Samsung site. Worked Perfectly, Thanks!
Cowoholy
The device acts as if it is being charged.
Steps I have taken so far:
-uninstalled T-mo Samsung mobile drivers and reinstalled
-deleted (uninstalled) ALL recognized USB devices via USB deview
-tried to connect without Samsung drivers installed and all USB devices uninstalled
-tried to connect with Samsung drivers installed and all USB devices uninstalled
-tried to connect without Samsung drivers and other devices installed
-tried to connect using safe mode, both with drivers installed and not
---**these are both trying with the current one provided on Samsung's site (1.5.14.0) and with the one found here on XDA from 25apr2013 (1.5.23.0)
-tried to connect using different USB ports
-tried to connect using a different USB port on a different USB controller altogether
The kicker:
Device is recognized instantly... on my laptop.
This means:
-It is not the USB cable I am using (even though I have tried 3 different cables altogether regardless, including the one that came with the phone)
-It is not the device itself
Possible: Windows issue? Last time this happened was long ago when I had gotten a MyTouch 3G Slide. I eventually just reinstalled Windows since I had been meaning to then. I don't want to do it now though because I have too many things installed on here to start a fresh install... but I suppose if nothing else works, that's what I'll have to do.
Before that though, I would love to hear any other suggestions from anyone here.
Some time the fault cud be the cable itself... I had same issue months ago my original samsung UsB cables didn't worked... It olwyz show the msg UsB not recognized... Then I tried with a different UsB cable (i had a Nokia UsB cable) and it worked...
Try it...
Cheers!!!
Sent from battery killer Jellybean GT-I9100 :-\
rjsmer said:
Some time the fault cud be the cable itself... I had same issue months ago my original samsung UsB cables didn't worked... It olwyz show the msg UsB not recognized... Then I tried with a different UsB cable (i had a Nokia UsB cable) and it worked...
Try it...
Cheers!!!
Sent from battery killer Jellybean GT-I9100 :-\
Click to expand...
Click to collapse
As stated, I have tried to use two other USB cables aside from just the one that came in the package.
Since all cables work on the laptop, but not this computer, I have pretty much singled it out to be a windows or a driver issue. :\
What are the specs of your desktop and the specs of your laptop? You claim it is a windows issue so I assume your laptop (that recognizes the phone) is not windows? Do you have Kies on the PC? If so, try to uninstall it completely and then install the individual drivers. Also, maybe just try updating Kies. You wouldn't need to install it, just download to your PC should work. As far as that goes, does Kies recognize the phone when plugged in at all? Does ODIN recognize the phone when plugged in? Maybe some of this will help you to find out if it is a driver issue or not. Good luck.
scott14719 said:
What are the specs of your desktop and the specs of your laptop? You claim it is a windows issue so I assume your laptop (that recognizes the phone) is not windows? Do you have Kies on the PC? If so, try to uninstall it completely and then install the individual drivers. Also, maybe just try updating Kies. You wouldn't need to install it, just download to your PC should work. As far as that goes, does Kies recognize the phone when plugged in at all? Does ODIN recognize the phone when plugged in? Maybe some of this will help you to find out if it is a driver issue or not. Good luck.
Click to expand...
Click to collapse
PC is i7 920, 12GB DDR3, Intel x58
Laptop is i5 2430M, 6GB DDR3, Sandy Bridge
Both are Win7 Pro, neither have Kies (I always just downloaded the drivers themselves) but I'm downloading it now to give it a try. As of now, nothing recognizes the phone on PC.
Kies method didn't work either
I did "Troubleshoot connection error", which I guess reinstalled the driver, but it still didn't work.
Getting ready to dig out that Win7 Pro CD at this point... :\
Shuurei said:
Kies method didn't work either
I did "Troubleshoot connection error", which I guess reinstalled the driver, but it still didn't work.
Getting ready to dig out that Win7 Pro CD at this point... :\
Click to expand...
Click to collapse
Samsung Kies isn't yet compatible with the sgh-m919. Samsung rep told me soon last night
Have you unlocked developer options yet and checked usb debugging? That might be your problem....
SBERG117 said:
Have you unlocked developer options yet and checked usb debugging? That might be your problem....
Click to expand...
Click to collapse
Enabling dev options and USB debugging was the first thing I did once I turned on the phone. Tried it both with and without, still not recognized either way. Still recognized on laptop.
I've also reinstalled windows altogether, since that fixed my issue last time around, but it's no good this time still. Clean install, formatted. No good. Previous steps from first post also taken, still no good. Tried the PDAnet method as well, no good.
At this point I am wondering if it might be an x58 issue, which would really suck, but it's the only thing I can think of given all the steps I have taken.
Okay... so what's the trick on getting Windows 7 x64 to recognize this device in Download Mode?
I have enabled USB Debugging. Tried several different ports on my Maximus V Extreme motherboard. I have tried using the PDANet drivers. Nothing works.Windows will prompt me with the "Device Driver software was not successfully installed" message. Anyone know a trick?
EDIT: FIGURED IT OUT. The last Android device I owned was the Galaxy S2. Now, back then it was understood that one should avoid Kies like the plague. However, in this case, it solved my problem. It installed all necessary drivers and I was able to communicate with ODIN. Cheers.
x58 issue
luckyduck69 said:
Okay... so what's the trick on getting Windows 7 x64 to recognize this device in Download Mode?
I have enabled USB Debugging. Tried several different ports on my Maximus V Extreme motherboard. I have tried using the PDANet drivers. Nothing works.Windows will prompt me with the "Device Driver software was not successfully installed" message. Anyone know a trick?
EDIT: FIGURED IT OUT. The last Android device I owned was the Galaxy S2. Now, back then it was understood that one should avoid Kies like the plague. However, in this case, it solved my problem. It installed all necessary drivers and I was able to communicate with ODIN. Cheers.
Click to expand...
Click to collapse
I might have pinpointed the issue!
I tried Kies again, uninstalled, reinstalled, updated. No go. I did Kies by air and got a connection! So It's gotta be something with the USB.
Although I thought it was weird, I think it might be an x58 issue, I decided to pursue that anyways.
I found out that USB issues are common with x58 (per this forum: http://www.evga.com/forums/tm.aspx?m=159610 ) and will be trying a fix located here: http://www.evga.com/forums/tm.aspx?m=442244&mpage=1
I'll report back once I try this out. Hopefully it fixes it.
If not, I just ordered another USB 3.0 controller (completely unrelated, it doesn't need to be USB 3.0, just a different controller altogether, but USB 3.0 is backwards compatible anyways. I just needed one for blackmagic) which was PCI-e x1 (still dependent on x58, so it wouldn't have mattered, check diagram on fix link), which I WAS going to install in my PCI-e x1 slot, but that would have not worked! Going to install in a PCI-e x16 and hope for the best.
I'll reply back once I test that out too.
Confirmed x58 and S4/general USB connectivity issues
Shuurei said:
I might have pinpointed the issue!
I tried Kies again, uninstalled, reinstalled, updated. No go. I did Kies by air and got a connection! So It's gotta be something with the USB.
Although I thought it was weird, I think it might be an x58 issue, I decided to pursue that anyways.
I found out that USB issues are common with x58 (per this forum: http://www.evga.com/forums/tm.aspx?m=159610 ) and will be trying a fix located here: http://www.evga.com/forums/tm.aspx?m=442244&mpage=1
I'll report back once I try this out. Hopefully it fixes it.
If not, I just ordered another USB 3.0 controller (completely unrelated, it doesn't need to be USB 3.0, just a different controller altogether, but USB 3.0 is backwards compatible anyways. I just needed one for blackmagic) which was PCI-e x1 (still dependent on x58, so it wouldn't have mattered, check diagram on fix link), which I WAS going to install in my PCI-e x1 slot, but that would have not worked! Going to install in a PCI-e x16 and hope for the best.
I'll reply back once I test that out too.
Click to expand...
Click to collapse
In case anyone was wondering or stumbles upon this later, I have a few updates.
I got the USB controller today and plugged it into the PCI-e x16 slot, plugged in the S4 and it worked completely fine.
I also contacted EVGA about the issue and will get an RMA, so perhaps it's just a faulty unit. However, this seems rather common (refer to previous linked threads) in x58 chips.
I imagine it has something to do with power distribution with the controller, which is why upping the ICH voltage fixes it for some people. The USB controller is powered via 4pin, not dependent on Southbridge. I guess the S4 has higher voltage(?) requirements for it to be recognized. It seems rather strange since my other devices are still recognized, but well, that's what I managed to come up with.
Cheers.
Shuurei said:
In case anyone was wondering or stumbles upon this later, I have a few updates.
I got the USB controller today and plugged it into the PCI-e x16 slot, plugged in the S4 and it worked completely fine.
I also contacted EVGA about the issue and will get an RMA, so perhaps it's just a faulty unit. However, this seems rather common (refer to previous linked threads) in x58 chips.
I imagine it has something to do with power distribution with the controller, which is why upping the ICH voltage fixes it for some people. The USB controller is powered via 4pin, not dependent on Southbridge. I guess the S4 has higher voltage(?) requirements for it to be recognized. It seems rather strange since my other devices are still recognized, but well, that's what I managed to come up with.
Cheers.
Click to expand...
Click to collapse
Here's my craziness.
USB connection was working yesterday. Today, it is not.
I have uninstalled/reinstalled the Samsung Windows drivers/Kies
I have even adjusted my southbridge voltage to 1.2V in my BIOS
Still, no joy.
Curiously, when I boot the phone into download/ODIN mode and connect it, ODIN recognizes the connection. Reboot back into normal mode, and no USB connection is recognized. It is not showing up in my Device Manager as an unrecognized device. It just doesn't know it is there (unless phone is in download mode).
UPDATE: Solved. I had installed this ROM (http://forum.xda-developers.com/showthread.php?t=2261013). Reading back over the thread, it provided instructions for re-enabling the USB recognition of the phone. Had to re-enable the developer options and reset USB debugging. Makes sense now.
HI
I'm facing this issue today, I've tried two different laptops, both have Windows 7 x64 installed. I've tried every USB port on the two machines, I've tried with three different cables, I've downloaded and installed every USB driver there is. no use!
I'm out of options here and I can't think where to look further.
any help please?
shuurei said:
the device acts as if it is being charged.
Steps i have taken so far:
-uninstalled t-mo samsung mobile drivers and reinstalled
-deleted (uninstalled) all recognized usb devices via usb deview
-tried to connect without samsung drivers installed and all usb devices uninstalled
-tried to connect with samsung drivers installed and all usb devices uninstalled
-tried to connect without samsung drivers and other devices installed
-tried to connect using safe mode, both with drivers installed and not
---**these are both trying with the current one provided on samsung's site (1.5.14.0) and with the one found here on xda from 25apr2013 (1.5.23.0)
-tried to connect using different usb ports
-tried to connect using a different usb port on a different usb controller altogether
the kicker:
Device is recognized instantly... On my laptop.
This means:
-it is not the usb cable i am using (even though i have tried 3 different cables altogether regardless, including the one that came with the phone)
-it is not the device itself
possible: Windows issue? Last time this happened was long ago when i had gotten a mytouch 3g slide. I eventually just reinstalled windows since i had been meaning to then. I don't want to do it now though because i have too many things installed on here to start a fresh install... But i suppose if nothing else works, that's what i'll have to do.
Before that though, i would love to hear any other suggestions from anyone here.
Click to expand...
Click to collapse
很想帮你啊 可是英文水平比较拙计
ok so now I'm guessing it is not windows, I tried on another machine with Windows Vista and got the same error.
any thoughts, anyone?
Did a factory reset for the phone
no it works!
don't know why
I just picked up this phone a couple days ago and last night tried to get the USB to work with no luck. I've tried everything I can think of. It does work in PTP mode but not MTP mode. I was able to use odin to on it though, so I was able to root it.
I've tried both in linux and on windows xp. I've never had an issue with any phone on linux and have installed/removed drivers numerous times on XP.
Tried 3 different cables, Factory reset with and without USB installed, tried pretty much everything I could find while googling similar problems (removing old registry entries, installed media player, etc)
I have adb installed on my linux box and even with debugging enabled I can't even get adb to connect to the phone.
Definitely something strange going on. Maybe I'll switch to cm10.1 to see if that makes a difference
I cant get my computer (windows 7) to connect with the phone when the phone is on, and was hoping some one might have found a fix.
This might fix it...
Shuurei said:
The device acts as if it is being charged.
Steps I have taken so far:
-uninstalled T-mo Samsung mobile drivers and reinstalled
-deleted (uninstalled) ALL recognized USB devices via USB deview
-tried to connect without Samsung drivers installed and all USB devices uninstalled
-tried to connect with Samsung drivers installed and all USB devices uninstalled
-tried to connect without Samsung drivers and other devices installed
-tried to connect using safe mode, both with drivers installed and not
---**these are both trying with the current one provided on Samsung's site (1.5.14.0) and with the one found here on XDA from 25apr2013 (1.5.23.0)
-tried to connect using different USB ports
-tried to connect using a different USB port on a different USB controller altogether
The kicker:
Device is recognized instantly... on my laptop.
This means:
-It is not the USB cable I am using (even though I have tried 3 different cables altogether regardless, including the one that came with the phone)
-It is not the device itself
Possible: Windows issue? Last time this happened was long ago when I had gotten a MyTouch 3G Slide. I eventually just reinstalled Windows since I had been meaning to then. I don't want to do it now though because I have too many things installed on here to start a fresh install... but I suppose if nothing else works, that's what I'll have to do.
Before that though, I would love to hear any other suggestions from anyone here.
Click to expand...
Click to collapse
Here's a link with a list of things to try what you may not have tried to fix your problems.
A small number of devices I have worked on have a weird thing, that the first time I plug the cable into the computer, it connects but won't show up on the screen. unplugging the USB cable from the machine for maybe 3 seconds, and reinserting makes the connection work... go figure! :>)
Aloha and Good Luck!
http://forum.xda-developers.com/showthread.php?p=32906335#post32906335
My sprint galaxy nexus is stuck on the phone to pc conection problem screen. I've tried all manner of button pushing to get to the Odin screen to no avail. Odin opens a com port to the phone but trying to flash anything causes Odin to stop working. ADB does not recognize the device. When I attach the phone the computer sees "Samsung USB Driver" in devices so it seems some communication is happening. I've tried all my different cables and usb ports including those that have worked before. Removing drivers via device manager and reinstalling different drivers did not work. Any ideas or links to appropriate threads would be greatly appreciated. Thanks.
Quick update - after a helpful email from one of the JTAG services from ebay (nice guy by the way) I got the phone flashed then up and running.
I manually updated the "Samsung USB Device" with new drivers, used a different tar with a Md5 and Odin 3.04. I have a feeling the manual driver install did the trick but I'm not going back through that again to find out.