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
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
Hey guys,
trying to root this beauty and Im running into problems. Been testing around for about 4 hours now, no solution.
Im Running Windows 8.1 and had a few other devices installed before. Cleaned up the drivers with the device manager and USBDeview.
At first I tried the Nexus Root Toolkit, simply followed the instructions until the final checkup. Device is connected in ADB mode but not authorized. (Authorization does not popup on N5x)
Also tried all different driver versions.
Then I cleaned all that stuff again and tried to go the manual way through the SDK. Same Problem, device is recognized but no authorization and no pop-up.
Im using a tronsmart Micro-USB to USB-C adapter and already tried two different cables and many different ports.
Also tried switching through the USB connection modes and toggling debugging on / off.
Im at my wits end here, anyone got a solution?
i have the same issue on n5x,
cant get recognized on adb at all or usb debug
Rooted without problems from my gf's Laptop. So I guess it's an issue with the PC / drivers.
I have latest SDK updates. And USB debug on. OEM unlock on many options on and off. Nothing works