I had problems with Kies recognizing my phone and its a Win 7 64-bit build, I was getting the same issues with my wifes Kies on a Win 7 32-bit build.
I installed drivers, multiple versions of Kies...and still nothing. Untill I found the answer, and its going to sound stupid but it worked for both our computers...
Ready?
All we had to do was use the USB ports on the back of the computer. The front ones were not recognizing our phones, switched to the back and BAM, working perfect. Just a tip to try but it worked for both my wife and I and our captivates/PC's.
I have no clue as to the reason behind this, as the ports on the front of the PC's recognize everything else. I learned this from another forum when I was having issues. Something to try for sure for others having issues.
him no worky sir. not on xp, not on 7x32 or 7x64. my cap must have the herp cuz she derp on every machine. personally. . .i blame kies.
gunstar3035 said:
I had problems with Kies recognizing my phone and its a Win 7 64-bit build, I was getting the same issues with my wifes Kies on a Win 7 32-bit build.
I installed drivers, multiple versions of Kies...and still nothing. Untill I found the answer, and its going to sound stupid but it worked for both our computers...
Ready?
All we had to do was use the USB ports on the back of the computer. The front ones were not recognizing our phones, switched to the back and BAM, working perfect. Just a tip to try but it worked for both my wife and I and our captivates/PC's.
I have no clue as to the reason behind this, as the ports on the front of the PC's recognize everything else. I learned this from another forum when I was having issues. Something to try for sure for others having issues.
Click to expand...
Click to collapse
This really does not make much difference as it can be similar to Odin not recognizing the phone. The USB has been issues for many people and switching to others can help. Kies is just junk really.
gunstar3035 said:
I had problems with Kies recognizing my phone and its a Win 7 64-bit build, I was getting the same issues with my wifes Kies on a Win 7 32-bit build.
I installed drivers, multiple versions of Kies...and still nothing. Untill I found the answer, and its going to sound stupid but it worked for both our computers...
Ready?
All we had to do was use the USB ports on the back of the computer. The front ones were not recognizing our phones, switched to the back and BAM, working perfect. Just a tip to try but it worked for both my wife and I and our captivates/PC's.
I have no clue as to the reason behind this, as the ports on the front of the PC's recognize everything else. I learned this from another forum when I was having issues. Something to try for sure for others having issues.
Click to expand...
Click to collapse
That's fine and dandy if you have a desktop box, I have two win7 x64 laptops and it works on neither, no matter if i amend the db or the connect method. Until they make a dedicated version for the US captivate there's going to be issues.
Related
After unrooting my phone to take to Verizon for some repairs, I can't connect my phone to a computer. I haven't connected my phone to a computer since I rooted back in March. And you don't need to connect to unroot.
I read somewhere that upgrading the radio will fix it but I'm not rooted so I can't. All I want to do is root again and I cannot. My mac doesn't see with osx or bootcamp, it and neither does my Windows 7 desktop. It's not that it's unrecognized, my computers just can't find it.
Is there some fix that I'm just not finding? Or is my USB port fried? I've tried another cable as well.
I can still charge so idk. I'm at a loss.
I had something similar happen to me the other day. I upgraded the hard drive on my netbook & then did a fresh install of Windows 7 Ultimate x64. upon getting it up & running, I plugged in my phone and it just said "USB device not recognized".
Seeing as how I ocassionally do wired tethering with PDAnet, I loaded PDAnet on to the netbook & then it specified to disconnect my phone & asked what manufacturer phone I have. I selected "HTC", it installed HTC drivers, then asked me to plugmy phone back in(with USB debugging on), then it said it was installing my phone and everything went smooth from there.
Right, but I don't even get "Unknown Device" or "Device not recognized". Absolutely nothing happens.
My phone will charge but neither device talks to each other.
you ate sure igs a USB 2.0/3.0 and not a 1.0 jack?
czn you trhy on someone elses pc?
normally wjen a USB jack goes out that's it.
sprryfor typos, lpud music and alcohol. id say what else but domt want some law enforcement type to see my post. weee
howephillip said:
After unrooting my phone to take to Verizon for some repairs, I can't connect my phone to a computer. I haven't connected my phone to a computer since I rooted back in March. And you don't need to connect to unroot.
I read somewhere that upgrading the radio will fix it but I'm not rooted so I can't. All I want to do is root again and I cannot. My mac doesn't see with osx or bootcamp, it and neither does my Windows 7 desktop. It's not that it's unrecognized, my computers just can't find it.
Is there some fix that I'm just not finding? Or is my USB port fried? I've tried another cable as well.
I can still charge so idk. I'm at a loss.
Click to expand...
Click to collapse
Have you tried loading hboot then connecting?
Sent from my Synergy driven Thunderbolt...
Have you tried uninstalling your USB drivers, I had this happen and after a reboot it worked once everything loaded back up, search for a tutorial or I'll post when I get home
Sent from my ADR6400L using xda premium
icesteve said:
Have you tried uninstalling your USB drivers, I had this happen and after a reboot it worked once everything loaded back up, search for a tutorial or I'll post when I get home
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
that *might* work.. if your PC is a store bought system, you'd just go to the manufacturers website and download the drivers from the 'downloads/support' page, then uninstall from device manager, reboot, re-install(and possibly reboot again).
if it's a custom PC, you'd goto the motherboard manufacturers page & do the same thing. if you don't know the make/model of the motherboard, it will also tell you in device manager(or just remove the side of the case and look at the motherboard itself, it'll be labelled somewhere near the cpu).
Stratejaket said:
Have you tried loading hboot then connecting?
Sent from my Synergy driven Thunderbolt...
Click to expand...
Click to collapse
If by loading Hboot you mean loading the bootloader and trying every single option (even Hboot USB), then yes.
voxigenboy said:
you ate sure igs a USB 2.0/3.0 and not a 1.0 jack?
czn you trhy on someone elses pc?
normally wjen a USB jack goes out that's it.
sprryfor typos, lpud music and alcohol. id say what else but domt want some law enforcement type to see my post. weee
Click to expand...
Click to collapse
I've tried two computers! And one is a mac which has 2.0
icesteve said:
Have you tried uninstalling your USB drivers, I had this happen and after a reboot it worked once everything loaded back up, search for a tutorial or I'll post when I get home
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
I can't even get the computers to recognize that I need a driver or that I have a device connected.
not sure if you've tried another USB cable or not, but if you have and it's still doing the same thing then it has to be a hardware related issue. possibly something wrong with the USB connection on your phone.
Awhile back, mine was doing something weird where when i'd plug it in to charge it and it kept showing that it was constantly charging, then not charging... I thought "what the hell!?".. I ended up trying canned air and it helped a little.. but started up again. I finally used some 'electrical parts cleaner' on it and ever since it's been functioning normally again.
not sure if you've tried another USB cable or not
Click to expand...
Click to collapse
Please read the op
It charges but doesn't connect
howephillip said:
Please read the op
It charges but doesn't connect
Click to expand...
Click to collapse
it helps to read the entire post apparently ;P
well, in the time I've had my TBolt, I've tried out every radio & countless rom/kernal variations. I have never had an issue connecting to PC on any radio so I doubt the radio has anything to do with your issue.
You have already attempted everything else though(a side from the cleaning) so i'd wonder if there's some sort of issue with the software on your phone.
I have had this exact problem.. have tried different PC's, different cords, different usb ports...I have tried to mount under CWM also. Computers don't give any indication that there is anything hooked into them....the phone does charge however. I have reinstalled the ROM (using CM7.1.1) I have intalled previous backups which had no problems linking to my PC. I have not tried to clean the charging port..will give that a go...I feel I will have to by a card reader for my pc to read the microSD. worked fine for 6 months, but then just quit. Posted this problem on android central...but no one could figure out a solution, thought someone here might have....last post on my AC thread from someone with same problem was told by verizon/htc to send it back for replacement...don't want to but might have to do this...love to have a brilliant idea before I do though! Can't post the link to the AC thread as I am a new registered user here..been trolling all year...but you can find it under the Thunderbolt Rooting. ROM's and Hacks area.....
I'm pretty sure no one has a solution to our problem. I've taken compressed air and cleaned everything and still no luck. It's just a question of how much they'll charge me for it.
So I got an incident with my phone, if you wanna now about it, its at my sig, but the thing is that I dunno why or how, sometimes my computer does recognizes my phone and display the Turn on USB storage option at the notification bar, but each time I try to turn it on it just wont work. Attached is a logcat whenI try to enable it, maybe someone could tell me why it wont work.
What rom are you running for those off that are on the xda application?
Sent from my LG-P999 using xda premium
Normally I got two nandroids a GB based one and an ICS based one, right now Im using both Eagle's Blood 2.3.7 v2.8 and ICS 4.0.3 Build 1. But I had this problem since... always. I'm a flashaholic so i have tested actually every rom from stock 2.2.2 to beta 4.0.3... I even have a nandroid of my original ROM (the one that came with it when y bought it and rooted it) and not even there works. The only clue i have right now is that only if I disable USB debugging it will randomly connect.
This may sound dumb but have you tried a different usb cable? I had the same problem and tried my girls and my phone was able to connect each and every time. another thing I noticed with my phone is that it sometimes won't connect using windows 7...xp no problem but 7 it plays hard to get.
Sent from my LG-P999 using XDA
No man, doesn't sounds dumb, actually if you read the "issue" background on my sig, you'll notice that I have made all those steps... its not a big deal, there are SDCard Readers and the bluetooth but... itw not the same.
Sent from my LG-P999
Ok but my bad I can't see your sig since I use the app most of the time. Yea its not the same
Sent from my LG-P999 using XDA
Holy Mother of God! I did it! In one of those "random" times my comptuter recognized my phone I just pulled out the batt unplug/plug again the cable, keeping both vol buttons pressed and it reconginzed the APX decive! Then all I had to do was NVFlash again, restore the stock 2.2.2 Nandroid i had somewhere and play a bit with the USB mount/debbug options, flashed both storages (using gparted for the microSD) and it works! Now have to restore everything to my SD and reflash latest cm7...
Nice!
Sent from my LG-P999 using XDA
Talked too early, if. I restore my nandroid the issue continues... -_____- Gonna try doing everything again...
Sent from my LG-P999
Did you ever figure this out? Sounds like your having the same problem that i am.
I've tried at least 6 different cables, home PC, work PC, laptop and a co-worker's PC that didn't have anything vmware installed (had a hunch that vmware usb drivers were the cause). Oh, all the computers were win7x64.
I've only rooted my phone and upgraded to 2.3.3 so nothing crazy going on there and it's worked for months since i did both of those.
I have a feeling that this may have been a recent windows update, but no clue when or which one because i haven't really cared that it didn't work. If i had to guess i'd say mine stopped working about 3 months ago... again, hard to remember.
CaptMorganz said:
Did you ever figure this out? Sounds like your having the same problem that i am.
I've tried at least 6 different cables, home PC, work PC, laptop and a co-worker's PC that didn't have anything vmware installed (had a hunch that vmware usb drivers were the cause). Oh, all the computers were win7x64.
I've only rooted my phone and upgraded to 2.3.3 so nothing crazy going on there and it's worked for months since i did both of those.
I have a feeling that this may have been a recent windows update, but no clue when or which one because i haven't really cared that it didn't work. If i had to guess i'd say mine stopped working about 3 months ago... again, hard to remember.
Click to expand...
Click to collapse
Make sure usb debugging is turned off.
Plug in the phone, enable usb storage.
Right click on the phone drives in the explorer and click on eject.
Turn off usb storage.
Unplug and plug in again.
Enable usb storage.
Drives should work now.
This did it for me. Since then if I remember to eject before unplug I haven't seen any issues.
Sent from my LG-P999 using XDA
Thanks for the reply, I'll give that a shot.
Curious though, when yours was having problems, did windows detect anything? For instance, when I plugged mine into my co-workers pc there are zero pop ups about new hardware detected.
Sent from my LG-P999 using XDA
I had the same problem. Dirt in the mini-USB port can cause that problem.
Take a can of compressed air and blow it into the mini-USB port (blowing with your mouth isn't enough). Also, take a close look at the port with a magnifying glass and look for any dirt or discoloration in there.
Do the same with your cable.
Not working after install RemICS 1.3.2
EEngineer said:
I had the same problem. Dirt in the mini-USB port can cause that problem.
Take a can of compressed air and blow it into the mini-USB port (blowing with your mouth isn't enough). Also, take a close look at the port with a magnifying glass and look for any dirt or discoloration in there.
Do the same with your cable.
Click to expand...
Click to collapse
Hi, this problem occur to me after I've installed RemICS 1.3.2 ROM (CM9 based), I did follow the installation steps from beginning, when the problem occur, I did re-flash the same ROM several times, but this problem still unsolved.
I did try all recommendations (blow out dirt, disable usb debugging etc) but still not success.
This ROM should able to detect USB when phone connected with PC, but somehow I don't know why. Any experts recommendation?
________________________________________________________________________________________________________________
Ok, I just found the problem. I can hear now the tone of PC detected USB when plugged-in, and I update the driver. then Voila!!
Thanks All..
Try wifi file explorer gives you the ability of seeing your sd card through your ip address you'll find it on the play store
sent on my Evil Evo running the so called developers kernel
Hey, just thought I'd register an account because I stumbled upon this thread because I had the same issue verbatim and I managed to get it working.
I ended up using the USB 3.0 ports on my desktop and suddenly it picks up my g2x without fail everytime. With that said, I'm lead to believe that perhaps its an issue of power. Maybe the USB 2.0 ports you're using simply aren't providing enough power. Not sure what its worth or if my issue was something unrelated but maybe that bit of information is something to work with. =)
Found another solution that fixed the problem for me.
If you are using Windows XP, log on as an Administrator and open Device Manager
Select View > Show Hidden Devices
Scroll down to Storage Volumes, and expand
Right-click on each entry and select Update Driver.
This fixed the problem for me!
So... I got a Tab 2 10.1 last week from amazon after 3 days of use the Tablet died, no power, no signal, tried charging and all troubleshooting I found through the internet in the ended decided to send it back and got a replacement Tablet from Amazon.
Yesterday I got the new one and let it charge all night, this morning I got to set it up, everything was working great until I decided it was time for me to root it and transfer some music to it. When I connected it to my pc i got an error message saying "USB Device is not recognized" error message said something like the device had malfunctioned. Funny thing is that the tablet charges perfectly, although I do know that the pins it uses to charge and data transfer are not the same.
Having hopes in my tablet and my luck decided to check if it was for some reason in USB Debugging, it was not.
*Removed Kies, and all Samsung related drivers, rebooted and reinstalled the drivers alone, nothing.
*Unistalled the drivers rebooted and installed latest kies...nothing...
*Tried using a friends cable to see if that was the issue, nothing. *
Tried cleaning the port, nothing.
*Tried both cables, mine and my friend's, on a different computer and still nothing!.
So I have ran out of options and ideas and I'm really frustrated as I can't believe I've so much bad luck as to get 2 damaged tablets in a row.
Is there anymore troubleshooting I can do before I ask for a refund? I'd really appriciate any help that you guys can provide me.
Just a hunch... Are you on win7 x64?
Posted from my Fascinate using XDA Premium
MultipleMonomials said:
Just a hunch... Are you on win7 x64?
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
Yes, I am. Does it have to do with that?
Samsung's drivers and ODIN don't play nice with win7 x64. It works for some but not others. Use someone else's 32-bit PC, or try Heimdall Suite.
Posted from my Fascinate using XDA Premium
I've never had a problem with win 7 x64 with my Tab 2 10.1. What I would recommend is use a different USB port or try several different USB ports.
If that doesn't work, you likely have a bad USB port on your tab. Samsung should honor their warranty and replace it.
Posted from my Fascinate using XDA Premium
Hello again! So I recently picked up a Galaxy S 4g for a good deal, and now for some reason, I can't connect it to my pc. I plug it in via usb, I've tried all the USB settings, and my pc won't recognize it at all. I've searched everywhere on the web, and on these forums, and still no dice. I found another similar thread from about a year ago, and nobody really gave a concrete answer there. I've tried in debug mode also. The phone charges when it is plugged in, but that is all. I installed the Kies Mini and the drivers on my work pc (Win7 x64) and it still won't recognize my phone. At home I'm running Win8 x64, and Kies Mini won't even download the drivers, it just sticks at 0%. If anyone has any ideas as to why it won't work, or options that I can try, it would be greatly appreciated. Also, it is not rooted. The point of this is to try to root it. I've rooted many other Android phones without issue. This one's being a tricky little bugger!
Thanks in advance.
You will need to install the drivers for your phone on the pc. Also check out your usb cable some give me problems
Sent from my SGH-T959V
Had a similar problem on my win7 laptop. Decided to start over on my winXP pc and Kies mini worked to install drivers.
Well I've tried multiple USB cables, and both of the ones I have work with my Windows phone so im pretty sure those aren't the issue.
I will set up a PC with XP today then and see what happens. Will post with results. Thanks in advance!
I'm using windows 7 with no issues
Sent from my SGH-T959V
Tunderpimp said:
I'm using windows 7 with no issues
Sent from my SGH-T959V
Click to expand...
Click to collapse
I got it to work! Here's how:
I tried installing XP on a pc that I was setting up for my grandma, and still had the same problem. Having been working on this for a few days, I got frusturated, and brought it to my Dad to have him give it a go (he's done tons of rooting/unlocking on tons of phones, and he is in the 360 modding scene) and lo and behold, he got it. It was just the USB cables I was using I guess. He hooked it up with the cable from his Kindle Fire, and it worked instantly. Looks like I just need to pick up a new cable, because all 3 of mine are ****ty >.>
Thanks for the help guys!
Make sure MTP is checked under storage -> press menu -> USB Computer connection
EDIT: sorry i didnt see you had it solved
I dl'd Beans 12, and wanted to flash it, but my home PC didn't recognize my phone this morning. I went to the office, dl'd it there as well, and still, no recognition.
That's:
two different computers
two cables
heck, two different buildings.
This all worked before. They are both Win7 64 bit.
Also, after finally flashing Beans 12 (via sd card, which I had to remove to get it on the phone), still, nothing. So, I don't think it's something I removed. It's highly unlikely to be a computer/cable/port thing, as stated above.
I have KT747 and checked fast charge, that's not set. I tried with usb debug on and off. My computer DOES recognize my Archos tablet.
Any ideas?
Were the two cables the Samsung OEM cables?
Did you try re-installing the drivers?
At home, OEM Samsung cable. At work, OEM from my old Droid X.
I'll try the drivers, but on two different computers? I know I didn't un-install them.
I have this issue from time to time. My solution which works for me is un install Samsung drivets from your pc, reboot pc, install drivers, and reboot one last time. Make sure you download new drivers from Samsung site or Verizon not sure where from it's been awhile for me, but that should do the trick.
Sent from my SCH-I535 using xda premium
ProfLonghair said:
I dl'd Beans 12, and wanted to flash it, but my home PC didn't recognize my phone this morning. I went to the office, dl'd it there as well, and still, no recognition.
That's:
two different computers
two cables
heck, two different buildings.
This all worked before. They are both Win7 64 bit.
Also, after finally flashing Beans 12 (via sd card, which I had to remove to get it on the phone), still, nothing. So, I don't think it's something I removed. It's highly unlikely to be a computer/cable/port thing, as stated above.
I have KT747 and checked fast charge, that's not set. I tried with usb debug on and off. My computer DOES recognize my Archos tablet.
Any ideas?
Click to expand...
Click to collapse
It sounds like it is a ROM issue.
mikeman45 said:
I have this issue from time to time. My solution which works for me is un install Samsung drivets from your pc, reboot pc, install drivers, and reboot one last time. Make sure you download new drivers from Samsung site or Verizon not sure where from it's been awhile for me, but that should do the trick.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
tried that. Didn't work
EAGLEEYE51 said:
It sounds like it is a ROM issue.
Click to expand...
Click to collapse
I wonder about that, but it was working on Beans 10 until that day I posted, and I was thinking/hoping it was something I had uninstalled, but even with a clean install, nothing.
I once had a bad download of a ROM and couldn't transfer it. That is a little different from your situation, but have you checked the md5?
Checked MD5 before installing.
After many gyrations of installing, uninstalling, cleaining, rebooting, etc. my home PC, I saw on some board a few people with this problem, and a battery pull fixed them. Worked for me last. Just got in to work, where I touched nothing on the laptop, and it works here, too. That must have been it.
Now that I seem to have a fix, I wonder what the problem was.