Database Info

[Q] USB Connection Issues

Some time in the last 2 or 3 ROM flashes, my usb port has quit communicating. It will charge the phone, but never so much as gives me the usb connected tone on the pc. have tried numerous pcs that have worked in the past, 3 different cables that all have worked before, reinstalled drivers, tried adb, kies, odin, and mass storage to no avail. I have checked and unchecked debugging. Currently running MIUI, but was on phidelt82's EC10 combo rom before that with the same result. Anything I may be missing? I have run out of ideas, and none of what I am finding by searching seems to be helping.

snowgod76 said:
Some time in the last 2 or 3 ROM flashes, my usb port has quit communicating. It will charge the phone, but never so much as gives me the usb connected tone on the pc. have tried numerous pcs that have worked in the past, 3 different cables that all have worked before, reinstalled drivers, tried adb, kies, odin, and mass storage to no avail. I have checked and unchecked debugging. Currently running MIUI, but was on phidelt82's EC10 combo rom before that with the same result. Anything I may be missing? I have run out of ideas, and none of what I am finding by searching seems to be helping.
Click to expand...
Click to collapse
I went to settings then USB settings and changed my option to ask everytime. Now when I plug phone to usb cable the phone screen comes up to select media or mass, I select mass and the computer sees it.

No dice. Not sure what else to try, can't go back to stock, acts as if my usb port is charge only.
Sent from my SCH-I500 using XDA Premium App

Anyone have a package to get me back close to stock with clockwork (cant use Odin obviously) so I can take the phone in for a replacement?.

This is why you should back up your phone before flashing.

Thanks so much for your kind and helpful words. As it stands, I did back it up in Clockwork, but the phone will not read the backup now. At what point did these forums change from a place of information sharing and learning to a troll haven full of "Noob bashers"?

I had those same problems and I could never get my phone to recognize but I found one computer and xp machine that odin saw and I got it to work but my USB still doesnt work on any other pc (Weird). So just keep trying diff computers maybe it my show up

Thanks for the tip, will see what I can come up with

snowgod76 said:
Thanks so much for your kind and helpful words. As it stands, I did back it up in Clockwork, but the phone will not read the backup now. At what point did these forums change from a place of information sharing and learning to a troll haven full of "Noob bashers"?
Click to expand...
Click to collapse
No one is bashing anybody. Maybe you need to change the way you interpret things. If you'd reread your original post, you'll see you never said you made a backup and couldn't restore it. I was making a legitimate point to make sure in the future you made backups. I had no way of knowing you had.
Point is, my comment was legitimate; I was not bashing you, so don't be so quick to interpret things people say in the most negative connotation as possible.

Sorry, add, I too fell victim to your "hard" tone in many of your replies around the forums. I apologize for being quick to the trigger, as I can see where you are coming from in the piles of questions daily from folks who have never even thought to back up before flashing. As it turns out, I gave it a quick bricking, and a replacement with working usb is on the way. Pretty sure it was a hardware issue, as it was working one minute and gone the next with no changes to the phone.

Any advice for an Android beginner?

I just got the Captivate about a month ago. Had a regular phone for about a year, touch screen went out, bought a replacement digitizer but knew it was a temporary fix anyway and wanted a new phone. Convinced the maternal unit to use her contract extension to get me a new phone, and snagged the Captivate for $30 from RadioShack. My first Android phone, and I have to say I'm horribly disappointed, but I guess I'm doing something wrong here.
First two or three weeks, my mom had the phone and got to play around with it for a while. Wasn't until the 29th that I got the phone, and I just played around with it for a week and got all the apps I deemed useful and worthwhile. Eventually realized I couldn't use Flash in the browser, nor Skype, etc., without upgrading to 2.2.
So, I went through the tutorial Samsung provided, watched videos on Youtube just to be sure, but followed everything Samsung's tutorial said word for word. ... only for my phone to end up completely screwed up. Gallery, Browser, Music Player, Video Player, and many other default applications were missing. Now I'm smart enough with technology to think, okay, something's wrong. I knew about the factory reset, so I went to go to settings to do that, and realized. ... oh wait, the Settings menu is also missing. Wonderful. There was no "Settings" button in the Applications list, and if I tried getting to it from the menu button, it simply did nothing at all.
Found Odin, flashed back to 2.1, and then factory reset and got rid of every application I had and etc., so that absolutely nothing was on it, basically a stock phone. Tried upgrading again fresh, still following the instructions very closely. Same problem occurred, and I was pissed. Gave up on 2.2, tried flashing back to 2.1 /again/ with Odin, only for my phone to decide it didn't want to enter download mode anymore. Forced it using 'adb reboot download', but alas, it locked up in the middle of flashing back to 2.1 and wouldn't do anything. I waited about 30 minutes to see if it'd resume the flashing process at all, but nothing, so I regrettably had to disconnect the USB cable and hard brick the phone (wouldn't turn on or anything).
Still under warranty, so I replaced it from RadioShack, and now have a new Captivate. Went ahead and installed all the applications I needed, used the Sideload Wonder Machine to install a few third-party applications, had no problem doing that for a while. Didn't bother attempting to upgrade. However, my computer got a trojan and deleted the MBR. Repaired using the XP boot disc, but it meant I was back on SP2. After installing every last one of the damn updates all over again, I decided to check up on some new applications to install via sideloading.
Hooked up my phone, it detected all the new hardware again since the drivers seemingly were also lost amongst everything else during the repair, only for it to encounter an error on the "Samsung Android Composite ADB Interface". So, I uninstalled the drivers, tried installing them manually. Hooked up the phone, but it still wanted to try to install that one driver and failed. I've restarted my computer, uninstalled the drivers, attempted manually installing them through device manager, you name it. Still can't get it to work -- it keeps having a fatal error every time. However, it's only when my phone has USB Debugging on. Installs every single driver perfectly fine when it's off, in MTP/Mass Storage/Kies mode. Just has a "fatal error" in USB Debugging on that one driver.
tl;dr, the drivers are broken on my computer and I can't fix them despite actually /not/ being computer illiterate. And, I kind of still want 2.2, but apparently the stock 2.2 update is a pain in the rear end and I no longer have a warranty through RadioShack now, so I can't risk bricking my phone due to a faulty update process. Any suggestions?

err, the only thing you should have needed to do was install the latest version of Kies, plugged the phone in, it would have prompted you to do the update. It's quite painless..

Edit: Sorry irrelevant

sw411 said:
err, the only thing you should have needed to do was install the latest version of Kies, plugged the phone in, it would have prompted you to do the update. It's quite painless..
Click to expand...
Click to collapse
At the time I tried, Kies itself didn't support the Captivate. Only Kies mini. And in order to do that upgrade, I had to install the drivers, then put the phone into download mode to install more drivers for some odd reason, restart the phone (taking out the battery and putting it back in), then hook it up. Kies mini wouldn't detect the phone for several tries at first, finally got it about the 10th time in. Then go to the "Upgrade phone" link, and yeah. I followed the instructions from Samsung's official SGH-i897 Froyo upgrade guide.
I did EXACTLY as the instructions say, down to the wire. Still ended up both times with all those applications missing and the settings panel missing, unable to do a factory reset without flashing back to 2.1 first.

Install z4root and root phone
Install rom manager
Flash clockwordmod recovery from rom manager
Choose a 2.2 rom from the forums
Download and copy to SD card
Install via rom manager
????????
Profit
Hope this helps. Btw I reccomend firefly or serendipity for the rom
Sent from my Captivate running CyanogenMod7 using XDA Premium App

brendanmurphy said:
Install z4root and root phone
Install rom manager
Flash clockwordmod recovery from rom manager
Choose a 2.2 rom from the forums
Download and copy to SD card
Install via rom manager
????????
Profit
Hope this helps. Btw I reccomend firefly or serendipity for the rom
Sent from my Captivate running CyanogenMod7 using XDA Premium App
Click to expand...
Click to collapse
Only downside to rooting the phone is the voided warranty. I don't entirely know what I'm doing there when it comes to flashing, and if I manage to do something wrong and brick the phone again, I'm completely wiped. I don't have the money to replace the phone at all. I have no job. ._. Only reason I got the phone was because I managed to get some spare money fixing up a friend's computer, and the maternal unit's contract extension was available. I'm not paying for the phone, still my parents. Damn economy in this state is so broken, and I'm screwed over worse since I have no diploma.
However, I was looking into info on the roms, and while I was tempted to try out CM7 for the fact it was 2.3, I actually considered getting Paragon RC6 from what I had read. Just decided not to because I can't replace the phone if I screwed up. In the slim chance I do opt to risk not having a phone at all if I do something wrong, would you say Paragon's worthwhile or would it be better to go with Serendipity? I do like TouchWiz, and Wifi access is a must (200 MB plan isn't going to cover it with how I use data; I'm frequently using Wifi in as many places as is possible), but I'm pretty sure both of those are fine there. Just not really sure which would be better overall, performance-wise.
I can't do either of them right now anyway until I figure out why the drivers aren't installing. So that's my first issue.

Don't worry about bricking I almost guarantee you will brick your phone once. But that is what Odin is for and it's almost impossible to hard brick a phone these days. Just install paragon with the instructions I gave its really fool proof these days to install rom. You will learn by trying if you mess up so be it that's what xda is here for to help.
Drop me a pm anytime if you need help
Sent from my Captivate running CyanogenMod7 using XDA Premium App

brendanmurphy said:
Don't worry about bricking I almost guarantee you will brick your phone once. But that is what Odin is for and it's almost impossible to hard brick a phone these days. Just install paragon with the instructions I gave its really fool proof these days to install rom. You will learn by trying if you mess up so be it that's what xda is here for to help.
Drop me a pm anytime if you need help
Sent from my Captivate running CyanogenMod7 using XDA Premium App
Click to expand...
Click to collapse
Well. Despite it being almost impossible, I've managed it once already within the first month of having one. Kind of why I'm a bit skittish about actually going through with it. I'm definitely all about modding and customizing things to your liking, but not having the funds to fall back on if I /do/ screw up bigtime again, yeeeeah.
After looking at Firefly and Serendipity thoroughly, though, I'm impressed. It's a tough choice between the three (Paragon, Serendipity, and Firefly). I'm leaning towards Serendipity now though after watching a video just to see the interface. Kinda not a huge fan of the GB launcher -- I liked the side-scrolling app launcher more, honestly -- but that's not a big deal.
So, let's see if I've got the details down right before I try anything. Search z4root in Market, install. Subsequently get Rom Manager, install it. Flash ClockworkMod (via Rom Manager). Pick a 2.2 rom (which will be a tough choice), and download it to my microSD card to put in the phone. Install said rom (via Rom Manager). And then, voila, it's done.
Did I miss anything, or am I actually following instructions right here?
Edit: Nope, can't find z4root in the Market anyways. Means I'd have to Sideload it, and until I get this driver issue solved, that's not gonna work either. That's gonna be the first thing necessary to fix since it also means I can't use Odin if I do anything wrong... Downloading Serendipity now though, so if I can get that fixed, I may go ahead and try this out after I get some sleep. But since I'm nocturnal, time for some rest. Hoping for some tips or pointers when I get back on. Definitely looking forward to good experiences with XDA and my Android phone.

Yea those are the exact steps its really simple. http://forum.xda-developers.com/showthread.php?t=944418 try this it will install drivers for you ans sideload apps. This is a useful tool
Sent from my Captivate running CyanogenMod7 using XDA Premium App

The.Se7enth said:
Only downside to rooting the phone is the voided warranty.
Click to expand...
Click to collapse
Quick question. Did you purchase the insurance through AT&T for the phone? If so, you will most likely always be able to get it replaced even if it's been rooted. It's just as simple as calling the help line, and saying that you have no idea what happened, and it won't work now. Of course that is worst case scenario
From my experience, the Captivate is a pretty difficult phone to hard brick compared to some others. For a beginner, all of this can be somewhat overwhelming, we've all been there. But once you get the hang of the whole process, you'll be good to go!

Yeah I've done that once already. Just called in and told them that it seems like a software problem and they replaced it no charge.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

Beginner help....
AT&T warranty is for 1 year on new phones, 90 days on phones you purchase as refurbished. (30 day "I just don't like THIS phone" replacement/return in both cases.) If Radio Shack will not replace the phone, AT&T should swap. If neither is willing to help, Samsung will honor their 1 year warranty, but it requires shipping back to Samsung.
Your situation sounds like your Windows PC is the problem. A complete reinstall of Windows & apps (not just a quick MBR repair / install over top of existing stuff) may be your best bet if you can't use a different machine.
Kies Mini should upgrade your phone to 2.2 painlessly - without you having to do anything but plug it in and click the on screen button.

Also if you root and need to return it just flash back to stock which will take away root and at$t is none the wiser, most likely

peypey008 said:
Quick question. Did you purchase the insurance through AT&T for the phone? If so, you will most likely always be able to get it replaced even if it's been rooted. It's just as simple as calling the help line, and saying that you have no idea what happened, and it won't work now. Of course that is worst case scenario
From my experience, the Captivate is a pretty difficult phone to hard brick compared to some others. For a beginner, all of this can be somewhat overwhelming, we've all been there. But once you get the hang of the whole process, you'll be good to go!
Click to expand...
Click to collapse
Nope. Don't feel their insurance policies are worth it. You spend more money on the insurance policy in total, even if it's month-to-month, than you would on a brand new contractless phone. Besides, I had only made $120 from fixing up three ancient computers (so ancient they actually had ISA slots and DIMM SD-RAM memory -- one was even a Pentium II), and only had $50 by the time I bought the phone which was a couple months later. My $50 went towards the phone and a pack of screen protectors, while my mom covered the upgrade fee. Couldn't afford the insurance policy even if we wanted to.
But I do greatly appreciate the encouragement. I'll give it a go in a bit, and try out flashing Serendipity. I'll follow the official instructions from their own website though, because I read this on their FAQ:
"Never use ROM Manager. EVER, EVER, EVER, EVER, EVER!"
pouelle said:
AT&T warranty is for 1 year on new phones, 90 days on phones you purchase as refurbished. (30 day "I just don't like THIS phone" replacement/return in both cases.) If Radio Shack will not replace the phone, AT&T should swap. If neither is willing to help, Samsung will honor their 1 year warranty, but it requires shipping back to Samsung.
Your situation sounds like your Windows PC is the problem. A complete reinstall of Windows & apps (not just a quick MBR repair / install over top of existing stuff) may be your best bet if you can't use a different machine.
Kies Mini should upgrade your phone to 2.2 painlessly - without you having to do anything but plug it in and click the on screen button.
Click to expand...
Click to collapse
RadioShack replaced the phone the first time, but the manager there said after replacing it once, the warranty was thus void. I'm not sure if profanity is allowed here, but you can figure out which word I wanted to reply to him. It's eight letters long, starts with bull.
I've read posts on AT&T forums saying if the phone's bricked or can't be repaired by user methods though, especially if it's rooted, that they won't honor the warranty at all and will consider it user error and that you're out of luck. Even people who tried to upgrade to 2.2 stock had issues with that. But I dunno.
Anyways, my machine works perfectly for everything else. Before the repair, when I tried to upgrade? It was a fresh install. I had just reformatted it because it was performing sluggish before and I decided I wanted a single-boot installation instead of having my old dual-boot of Windows 7 and XP. It's now just XP for the time being, seeing as how the hardware's limited and I want to get the best out of it for gaming (I can run 7 with ease, but it uses more resources than XP, thus games don't run as well).
I realize earlier I may have come off as implying the upgrade to 2.2 process was difficult. I don't mean it was "difficult" by any means necessary. It was simply a plug the phone in, let all the drivers install, unhook and put in download mode, hook up again for more drivers. Restart phone, start up kies, hook up phone, and click "Upgrade phone" button. Accept the terms of service or whatever, and wait. Upgrade starts, phone flips into download mode on it's own, restarts a couple times, and voila, you're on 2.2. I thought it was a piece of cake. My issue is that regardless of how easy it was, it still ended up rather broken because all those applications were missing, on top of the fact the Settings panel was also gone, leaving me unable to perform a factory reset.
I have one last question. If I do somehow manage to get these drivers to work again (without reformatting, which I don't have the time to do), should I have the SIM card out while flashing the ROM? I'm wondering, subconsciously, if somehow that may have had something to do with the upgrade to 2.2 screwing up so bad. I had the SIM card in, with all my applications installed at first. Second time, no apps or anything were installed, but the SIM card was still in.
Edit: Well aware of most forums having a "do not double post" rule, as much as I want to bump this thread with an update on the issue. But, I've restarted my computer, tried a different USB cable, uninstalled and reinstalled the drivers from numerous different sources, and still the same "fatal error" issue on "Samsung Android ADB Composite Interface". I simply cannot get that to install whatsoever, and without it, the phone isn't detected as being hooked up even by SWM, much less anything else. Seriously, what do I do? I'm not reformatting my computer, because I simply see no reason for it, but I have no other computer I can use. How do I get these drivers to install properly like they did before?

The.Se7enth said:
At the time I tried, Kies itself didn't support the Captivate. Only Kies mini. And in order to do that upgrade, I had to install the drivers, then put the phone into download mode to install more drivers for some odd reason, restart the phone (taking out the battery and putting it back in), then hook it up. Kies mini wouldn't detect the phone for several tries at first, finally got it about the 10th time in. Then go to the "Upgrade phone" link, and yeah. I followed the instructions from Samsung's official SGH-i897 Froyo upgrade guide.
I did EXACTLY as the instructions say, down to the wire. Still ended up both times with all those applications missing and the settings panel missing, unable to do a factory reset without flashing back to 2.1 first.
Click to expand...
Click to collapse
Fail, Kies Mini works from Kies mode on the phone. It puts the phone into download mode when you start the upgrade from Kies Mini.
Just saying...

The.Se7enth said:
Nope. Don't feel their insurance policies are worth it. You spend more money on the insurance policy in total, even if it's month-to-month, than you would on a brand new contractless phone. Besides, I had only made $120 from fixing up three ancient computers (so ancient they actually had ISA slots and DIMM SD-RAM memory -- one was even a Pentium II), and only had $50 by the time I bought the phone which was a couple months later. My $50 went towards the phone and a pack of screen protectors, while my mom covered the upgrade fee. Couldn't afford the insurance policy even if we wanted to.
But I do greatly appreciate the encouragement. I'll give it a go in a bit, and try out flashing Serendipity. I'll follow the official instructions from their own website though, because I read this on their FAQ:
"Never use ROM Manager. EVER, EVER, EVER, EVER, EVER!"
RadioShack replaced the phone the first time, but the manager there said after replacing it once, the warranty was thus void. I'm not sure if profanity is allowed here, but you can figure out which word I wanted to reply to him. It's eight letters long, starts with bull.
I've read posts on AT&T forums saying if the phone's bricked or can't be repaired by user methods though, especially if it's rooted, that they won't honor the warranty at all and will consider it user error and that you're out of luck. Even people who tried to upgrade to 2.2 stock had issues with that. But I dunno.
Anyways, my machine works perfectly for everything else. Before the repair, when I tried to upgrade? It was a fresh install. I had just reformatted it because it was performing sluggish before and I decided I wanted a single-boot installation instead of having my old dual-boot of Windows 7 and XP. It's now just XP for the time being, seeing as how the hardware's limited and I want to get the best out of it for gaming (I can run 7 with ease, but it uses more resources than XP, thus games don't run as well).
I realize earlier I may have come off as implying the upgrade to 2.2 process was difficult. I don't mean it was "difficult" by any means necessary. It was simply a plug the phone in, let all the drivers install, unhook and put in download mode, hook up again for more drivers. Restart phone, start up kies, hook up phone, and click "Upgrade phone" button. Accept the terms of service or whatever, and wait. Upgrade starts, phone flips into download mode on it's own, restarts a couple times, and voila, you're on 2.2. I thought it was a piece of cake. My issue is that regardless of how easy it was, it still ended up rather broken because all those applications were missing, on top of the fact the Settings panel was also gone, leaving me unable to perform a factory reset.
I have one last question. If I do somehow manage to get these drivers to work again (without reformatting, which I don't have the time to do), should I have the SIM card out while flashing the ROM? I'm wondering, subconsciously, if somehow that may have had something to do with the upgrade to 2.2 screwing up so bad. I had the SIM card in, with all my applications installed at first. Second time, no apps or anything were installed, but the SIM card was still in.
Edit: Well aware of most forums having a "do not double post" rule, as much as I want to bump this thread with an update on the issue. But, I've restarted my computer, tried a different USB cable, uninstalled and reinstalled the drivers from numerous different sources, and still the same "fatal error" issue on "Samsung Android ADB Composite Interface". I simply cannot get that to install whatsoever, and without it, the phone isn't detected as being hooked up even by SWM, much less anything else. Seriously, what do I do? I'm not reformatting my computer, because I simply see no reason for it, but I have no other computer I can use. How do I get these drivers to install properly like they did before?
Click to expand...
Click to collapse
Yea once you have serendipity installed don't use rom manager but for initial install your fine
Sent from my Captivate running CyanogenMod7 using XDA Premium App

cappysw10 said:
Fail, Kies Mini works from Kies mode on the phone. It puts the phone into download mode when you start the upgrade from Kies Mini.
Just saying...
Click to expand...
Click to collapse
You can "say" all you want, my good sir, but google the instructions. They tell you clearly to put the phone into download mode TO FINISH INSTALLING DRIVERS. You don't start up Kies mini until after all the drivers are installed, at which point you hook up the phone with USB Debugging, not Kies mode. I appreciate your willingness to help, but be sure to read everything I say before you correct me. I'm not that slow. I read instructions thoroughly and I've read quite a lot of posts on these forums. I work with computers regularly -- just not Android. The issue had nothing to do with that anyway, so that doesn't even matter.
brendanmurphy said:
Yea once you have serendipity installed don't use rom manager but for initial install your fine
Sent from my Captivate running CyanogenMod7 using XDA Premium App
Click to expand...
Click to collapse
I'm sure it's possible, and I don't mean to come off disrespectful, but I'm just gonna go with the instructions on their website. Just seems a safer route to install a ROM by the creator's instructions, you know? Only thing I'm not sure about is what they mean by "Flash it in 2e recovery (twice)." on ClockworkMod.
The.Se7enth said:
I have one last question. If I do somehow manage to get these drivers to work again (without reformatting, which I don't have the time to do), should I have the SIM card out while flashing the ROM? I'm wondering, subconsciously, if somehow that may have had something to do with the upgrade to 2.2 screwing up so bad. I had the SIM card in, with all my applications installed at first. Second time, no apps or anything were installed, but the SIM card was still in.
Edit: Well aware of most forums having a "do not double post" rule, as much as I want to bump this thread with an update on the issue. But, I've restarted my computer, tried a different USB cable, uninstalled and reinstalled the drivers from numerous different sources, and still the same "fatal error" issue on "Samsung Android ADB Composite Interface". I simply cannot get that to install whatsoever, and without it, the phone isn't detected as being hooked up even by SWM, much less anything else. Seriously, what do I do? I'm not reformatting my computer, because I simply see no reason for it, but I have no other computer I can use. How do I get these drivers to install properly like they did before?
Click to expand...
Click to collapse
These two are still my top questions now. Is it a good idea to have the SIM card out during the upgrade process, and not put it back in until after the update is 100% complete?
Also, I'm really frustrated about this whole driver thing. I know the drivers aren't broken because I used them on this very computer before, and the repair shouldn't have damaged anything because absolutely everything else is working flawlessly. But every time I've uninstalled the drivers completely, and hook up the phone, it keeps getting a fatal error on that. Apparently "S3C6410 Android ADB" is the name of the device that can't install drivers.

[Q] Impressed with my new Infuse 4G but can't get USB connection to work

After plugging away for a few hours now, I am still unable to get my Windows 7 PC to recognize the Infuse 4G as a USB device. Upon plugging in the cable, I continue to get "USB device not recognized". I have installed the latest KIES package + drivers, tried a drivers-only install package from ATT, tried mini-KIES, tried all the USB ports and tried the whole thing over again on another Win7 PC. On the phone, I have tried the USB settings at Mass Storage, Media Player and Samsung EZUpdate and under Applications/Development, I have turned on and off USB debugging. The only thing I have not tried is another USB to mini cable, as I don't readily have one available (using the one that came with the phone).
The Infuse is a great smartphone, and I hope to make it a little smarter by sync'ing up to my PC. Any suggestions are appreciated. Jonathan

They may have included a charging only cable now. Is it telling you it is failing the install?
EDIT: Just read it said not recognizing. Try the Captivate Drivers. It's been a while but I think that's what I had to do.
Sent from Steve Jobs' iPhone

Uninstall kies completely! There is some problem with kies in windows 7 64 bit, search within this forum for the USB driver only.
I am so clever that sometimes I don't understand a single word of what I am saying.

Jonathan65 said:
After plugging away for a few hours now, I am still unable to get my Windows 7 PC to recognize the Infuse 4G as a USB device. Upon plugging in the cable, I continue to get "USB device not recognized". I have installed the latest KIES package + drivers, tried a drivers-only install package from ATT, tried mini-KIES, tried all the USB ports and tried the whole thing over again on another Win7 PC. On the phone, I have tried the USB settings at Mass Storage, Media Player and Samsung EZUpdate and under Applications/Development, I have turned on and off USB debugging. The only thing I have not tried is another USB to mini cable, as I don't readily have one available (using the one that came with the phone).
The Infuse is a great smartphone, and I hope to make it a little smarter by sync'ing up to my PC. Any suggestions are appreciated. Jonathan
Click to expand...
Click to collapse
Ok, so no joke, a day or two afterm I got my Infuse I had this exact issue. I was freakin out for at least two hours. Power cycled my phone, and I kid you not, it suddenly worked. Bizzare, but true.
Sent from my SAMSUNG-SGH-I997 using XDA App

Kevinr678 said:
Ok, so no joke, a day or two afterm I got my Infuse I had this exact issue. I was freakin out for at least two hours. Power cycled my phone, and I kid you not, it suddenly worked. Bizzare, but true.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Same, but i like disabled usb debugging and I think that did the trick.

I'm using Kies on 64bit windows 7 and it works fine.
You can try a different computer? Different USB port? I'm willing to bet the problem is not the phone at all.

Bandit_Kaine said:
I'm using Kies on 64bit windows 7 and it works fine.
You can try a different computer? Different USB port? I'm willing to bet the problem is not the phone at all.
Click to expand...
Click to collapse
Im on W7 64 bit running Kies with no problem, I don't think that the issue..

Problem persists... arrgh
Good tips, thank you, tried most of them, no go.
Using my cleanest, most reliable Dell, I uninstalled all of the KIES software, plus all of the Samsung drivers listed, plus the Samsung EZUpdate software. Rebooted, then installed only the drivers downloaded directly from Samsung (SGH-i997_Infuse4G_USB_Drivers_5_2_0_2.zip). Tried all the USB ports on the Dell, same issue - "USB device not recognized".
Just for fun, I then installed the new Samsung Galaxy 64bit drivers. Same issue.
As I am seeing exactly the same issue on two different PCs with no known USB port issues, I am beginning to suspect the cable that came with the phone might be the problem. Or is that too simplistic? Jonathan

The drivers are on the Samsung website. That would be the first logical place to look anyhow.
Also could be a bad cable but I think win 7 64 bit has issues with Samsung devices. Try to manually install the drivers and try a different cable.

At this point it is most likely the cable with a small chance of the phone itself being the issue. Try a different cable next, but if you have a linux live CD (Ubuntu, whatever you have) start a computer off of that, it won't require any drivers, and if it still isn't recognized that will prove you aren't having driver issues

Jonathan65 said:
Good tips, thank you, tried most of them, no go.
Using my cleanest, most reliable Dell, I uninstalled all of the KIES software, plus all of the Samsung drivers listed, plus the Samsung EZUpdate software. Rebooted, then installed only the drivers downloaded directly from Samsung (SGH-i997_Infuse4G_USB_Drivers_5_2_0_2.zip). Tried all the USB ports on the Dell, same issue - "USB device not recognized".
Just for fun, I then installed the new Samsung Galaxy 64bit drivers. Same issue.
As I am seeing exactly the same issue on two different PCs with no known USB port issues, I am beginning to suspect the cable that came with the phone might be the problem. Or is that too simplistic? Jonathan
Click to expand...
Click to collapse
I am currently running Windows 7 64-bit at home using the drivers you included above. I'm not having any issues connecting with my PC, so I would guess it's not drivers. The fact that it's happening with more than one computer would suggest that it's either your phone or your cable, and not the PC. I would start by shutting down your phone and pulling the battery. Let it drain for a few seconds, and then power it up with the battery back in. Then attempt a connection to your PC. It couldn't hurt to reboot your PC at the same time. Good luck!

ok so 1: sorry for reviving a semi-dead thread
2: first post so be easy on me?
but i might have a solution to the usb problem(kinda sorta) although its mainly for file management(like non os type.. unless u got a rooted phone)
but try installing "FTPDroid" from the market its a good free app, what you can do then is just get "FileZilla" (also free) on your computer.
just go to settigns of ftpdroid then add a user account ( so u can edit directorys and move/deleat files, instead of jsut transfers from computer) and sign on to the ftp server from your computer useing the account settings. and your good to go ^^.
but if u are needing the usb for say changing the os or rooting... this wont really work i dont think unless u can figureout how to do that threw other means.. then u can use the ftp to change os files(maby?)
hope i helped. atleast just a little bit.

[Q] USB drivers ?

Hi,
At home, on a Win7 64, I downloaded the T-Mobile drivers for the SGS2 and installed them. If I connect my Captivate it works fine, but when I connect my Skyrocket it says "not recognized".
At work I installed the same drivers on a Win7 32 bits and it works fine.
Any idea or links for a win 64 drivers?
Thanks

I had the same issue and after much searching, the end result was for me to install the latest Samsung Kies software. In the "%programfiles(x86)%\Samsung\USB Drivers folder" you can update device manager to recognize your phone.
I would post that directory, but it is >40MB. Everything worked after I did this.

IT Rider said:
I had the same issue and after much searching, the end result was for me to install the latest Samsung Kies software. In the "%programfiles(x86)%\Samsung\USB Drivers folder" you can update device manager to recognize your phone.
I would post that directory, but it is >40MB. Everything worked after I did this.
Click to expand...
Click to collapse
are you talking about this version of kies http://www.samsung.com/ca/support/mobilesoftwaremanual/mobilesoftwaremanual.do?page=MOBILE.SOFTWARE.MANUAL

That build appears to be newer than the one I used. I used build 2.0.3.11085_152_4
I got this from the i777 (SG2) since the download was not available for the i727
http://www.samsung.com/us/support/downloads/at-t/SGH-I777ZKAATT
I would assume that the version you posted would also work

IT Rider said:
That build appears to be newer than the one I used. I used build 2.0.3.11085_152_4
I got this from the i777 (SG2) since the download was not available for the i727
http://www.samsung.com/us/support/downloads/at-t/SGH-I777ZKAATT
I would assume that the version you posted would also work
Click to expand...
Click to collapse
unfortunately it didn't work. I did multiple "re-install drivers" with Kies phone connected and not connected but same problem. I guess I will have to edit the registry to force the right driver.
Thanks for your help

I know this sounds odd but I've had this issue and it wasn't a driver issue - it was the USB port itself. Do you have another one you can try by chance? If you're using one on the front of a desktop, is there one in the back that you can try instead?

Kadin said:
I know this sounds odd but I've had this issue and it wasn't a driver issue - it was the USB port itself. Do you have another one you can try by chance? If you're using one on the front of a desktop, is there one in the back that you can try instead?
Click to expand...
Click to collapse
Thanks for the idea, unfortunately yes, I tried that too yesterday without luck.
But thanks for your help

I had the drivers previously installed for the sgs2 and got the skyrocket which workd no problem on a win 7 64 bit machine. Id suggest uninstall your drivers reboot reinstall shutdown after install reboot. If still no dice use a different usb cable preferably one from another android device that is shorter and thicker. Like the moto ones. The one that comes with the droid pro and the moto atrix is short and very thick . Or better yet radio shack sells gold.tippd usb cables very high quality ibelieve they are about 30 bones

silver03wrx said:
I had the drivers previously installed for the sgs2 and got the skyrocket which workd no problem on a win 7 64 bit machine. Id suggest uninstall your drivers reboot reinstall shutdown after install reboot. If still no dice use a different usb cable preferably one from another android device that is shorter and thicker. Like the moto ones. The one that comes with the droid pro and the moto atrix is short and very thick . Or better yet radio shack sells gold.tippd usb cables very high quality ibelieve they are about 30 bones
Click to expand...
Click to collapse
I tried to uninstall and reinstall my drivers but same problem. It's really wierd because if I plug my captivate it is recognized right away, but if , with the same cable, I plug the Skyrocket then my Sky is not recognized.
I will try with a another cable tonight and let you know. Thanks for your help

Yes let me know. That is weird. Also maby your usb ports are underpowerd . Turn off power management and try the usb port thats connected to the hub. Although it ahould.work if the other phone did. Mabye a problem with the usb port on your phone. My samsung epic i had was very picky i tried like 6 different cables and finally bought a gold tipd one from radio shack and it worked and did u folow thia thread and use the drivers in it http://forum.xda-developers.com/show....php?t=1340710

silver03wrx said:
Yes let me know. That is weird. Also maby your usb ports are underpowerd . Turn off power management and try the usb port thats connected to the hub. Although it ahould.work if the other phone did. Mabye a problem with the usb port on your phone. My samsung epic i had was very picky i tried like 6 different cables and finally bought a gold tipd one from radio shack and it worked and did u folow thia thread and use the drivers in it http://forum.xda-developers.com/show....php?t=1340710
Click to expand...
Click to collapse
Yes, for the driver I did everything right
I connected my phone to two computers at my work without problem, I'm leaning forward a cable issue. Maybe the Skyrocket needs more power than my Captivate and that's why it is not recognized?
I will try another cable tonight
Thanks

Worth a try go to radio ahack get the gold tipd usb data transfer cable. Always worked for me when other cables didnt. Then try it

Thank you so much all for your help.
Finally it was the cable. Even if I used the same cable I used with my captivate, my skyrocket didn't want to be recognized.
I changed the cable and Tada..... It worked.
My guess is that the skyrocket need more power than the Captivate.
Anyway, thanks again for your help

good deal glad that worked out for you

[Q] Need help fixing my Infuse, more info inside

Alright, so, to get started, I am actually decently tech savvy, and I wish i had rooted my phone before I even tried following the crap that samsung put up, but heres how it went.
I have a Samsung Infuse 4G on the ATT network
I finally found out how to update to Gingerbread through Kies. I spent all night charging my phone, went to Kies, and started the upgrade. About 6% through the upgrade, it said it needed an emergency recovery. I was worried, and I followed all instructions. I let the emergency recovery page sit for a day, and all it did was sit at 6% the whole time, so I resorted to my next best option, rooting it.
I have tried Ultimate Unbrick, One Click Unbrick, and Hiemdall, though I didn't get extensive with Hiemdall.
One Click said it was successful, but my phone doesn't turn on, so I tried the emergency recovery again, and still sat at 6%, then it switched to that it couldn't fix it.
Ultimate Unbrick starts off well, seeming as it is doing soemthing, but then freezes at factoryfs.rfs. Mind you I am running it in compatability mode for XP SP2 as an administrator, and I have run it on Win7 as an admin as well.
Hiemdall I got a little confused, so Im going to try that again.
Im gonna have to say, Im done with Samsung after this phone. Ive had samsung phones for 10 years (not by choice, im 19 and my mom pays for it), and every time something stupid happens, its like they kill themselves on purpose.
Is anyone possibly able to help me get my phone back to working condition? I wont be able to get a new phone for about a month, and thats only if I can find a job, which is hard when I have no phone.
Thank you to anyone who can help.

Does your phone display anything on its screen at all? If so, there's still hope.
Have you installed drivers properly?
Make sure that anything related to Kies is killed on your computer's task manager.
Try using different USB ports.
As much as possible, use a Windows XP. I had the same "stuck at factoryfs.rfs" problem and I tried it at an XP and it worked.
If nothing works, try buying a jig off of e-bay. They're about a dollar or two. Invest in some.
If it's completely borked, time to go buy an S3.
Sent from my SAMSUNG-SGH-I997 using xda premium

I can get into download mode where it shows the android shoveling in a caution sign
I installed the drivers
I havent checked that kies thing yet, Ill do that now
Ill try another USB port and get back to ya on that part
I don't own any computers with windows XP. Only a Win7 and a crappy laptop with Ubuntu on it (the laptop is crappy, not ubuntu)
Im so broke a candybar looks like rich food
And Im done with Samsung after this, Ill prob go windows phone and hack the Android market onto it.

LMAO Idk I still like Samsung over HTC and Apple. It can get really complicated --yes -- but it's worth.
Also, make sure to restart computer and then do the things I suggested you to do.
Sent from my SAMSUNG-SGH-I997 using xda premium

Im aiming for Nokia.
So, I disabled kies
Restarted my computer
Tried a different USB port
restarted Odin
Reran everything
and now, it wont even get to factoryfs.rfs
Do you possibly have a link to Hiemdall thats the newest version?

You should restart before disabling Kies. This is because of the fact that when you restart, your computer re-runs Kies.
Sent from my SAMSUNG-SGH-I997 using xda premium

I disabled after I restarted as well. Sorry, my steps were out of order.

Hmmm that's odd. Try it on a different computer tomorrow. Possibly a friend's?
Sent from my SAMSUNG-SGH-I997 using xda premium

Im gonna try heimdall first and see if I can contact a friend tomorrow. I just moved and my friends out here are more busy than the other ones I used to live by.

Heimdall Link.
Try fresh installation remove drivers from Driver Manger, run the drivers again and use Heimdall package. you need to have latest java and it need to be run as application not in any of the zip/jar file opener like 7zip etc., right click and you will see run using java<your version >
http://forum.xda-developers.com/showthread.php?t=1524081
it is clearly explained on the link what to do,
If you found difficult you can read the thread to see some probable answers as well.
Hope it will solve your query.