Related
I have a MAC. I'm using VM Fusion on with Windows XP for the virtual machine.
I want to go I9000 (sick of app limitations and ATT in general).
I cannot for the life of me get the Samsung USB drivers to work on my Windows side of the MAC. I've tried install, re-install over and over. I've tried, and have, both versions of the Samsung drivers that are out there.
I have the ODIN program and all the stuff needed to get the i9000 on my phone.
My phone goes to down load mode.
I've been at this 8 HOURS and am about to break a 32" lcd monitor!!!!
Please.... I will take any suggestions on how to get my phone to connect on Windows XP.
i'm not sure what the compatability is for emulating windows but i did have problems installing my drivers on my pc (win XP) and my solution was kies from samsung. it automatically installed the drivers for me. it can be found at samsung.com.
Sorry..... a little anxious, frustrated, and well.... you get the point.
Thanks.... I am getting KIES right now....
talking like that won't get you help any faster...
edit: yeppers, trust me, i get you.
....
Yes I know.... thx again..
Breath, drink, don't break the monitor, keep trying..... the now 9 hours will pay off!!!
lol, did it work for you?
Downloading now...
Of course the download is taking forever. Normally I can download around 200 MB in a minute or two... this 136 MB file is going at the rate of about 39 KB/sec..
Grin and bear it right? Man I hope this works!
Will update this with results.....
40k a sec...wow, i'm sorry man...that makes me want a drink now.
chaosjh said:
40k a sec...wow, i'm sorry man...that makes me want a drink now.
Click to expand...
Click to collapse
Just the kind of day it's been.... I no sooner type the speed of download and hit post.... sure as sh*t the thing has downloaded already.
The Kies installer will open, and the progress bar is indicating the files are extracting and then it just dead ends me....
Gotta play around with it I guess..
ever think about dual boot instead of emulating? or maybe in addition to. or can mac's do that? kies installed fine for me, sorry man, idk...
hey i was also thinking about this, how does your setup send the fact that your phone is connected to the emulated xp instead of just iOS? maybe stupid question, but i thought i'd ask
pdxrealtor said:
I have a MAC. I'm using VM Fusion on with Windows XP for the virtual machine.
I want to go I9000 (sick of app limitations and ATT in general).
I cannot for the life of me get the Samsung USB drivers to work on my Windows side of the MAC. I've tried install, re-install over and over. I've tried, and have, both versions of the Samsung drivers that are out there.
I have the ODIN program and all the stuff needed to get the i9000 on my phone.
My phone goes to down load mode.
I've been at this 8 HOURS and am about to break a 32" lcd monitor!!!!
Please.... I will take any suggestions on how to get my phone to connect on Windows XP.
Click to expand...
Click to collapse
im in the same page yesterday when I got my captivate.. im just wondering why go with the I9000 stock firmware(too much hassle) if you can just use the unleash the beast
chaosjh said:
ever think about dual boot instead of emulating? or maybe in addition to. or can mac's do that? kies installed fine for me, sorry man, idk...
hey i was also thinking about this, how does your setup send the fact that your phone is connected to the emulated xp instead of just iOS? maybe stupid question, but i thought i'd ask
Click to expand...
Click to collapse
Hey that is a great idea, the booting up just the windows side... I've never done it but I think there is a native Mac app called boot camp.
As of now, it seems like the first kies file I downloaded was corrupt. I downloaded again and now it is actually installing the software.
My virtual machine sees the Android phone, and then Windows picks it up but errors it out as an unknown USB device. No matter where I point the XP device to for driver files it won't pick them up.
On the Mac side... it just shows up in Finder once mounted.
Hey OP, I had the same problem as you and I just ended up going the Bootcamp route. For whatever reason VMware Fusion with Win7 does not want to recognize the Captivate. I know its not much help and having to go with bootcamp instead of a VM does kinda suck but the bright side is that you can always open up your bootcamp partition with VMware Fusion while in OSX if you need quick access to Windows.
Kind of topic, but how do you access boot camp with VM Fusion from the Mac OS?
I only use windows for IE, as I visit websites that only work with that browser.
Anyways... sure as sh*t this morning I wake up and get the old xp laptop out, download the Samsung Capitave drivers and instantly hook my phone up.
So.... an entire day wasted on trying to connect my phone to XP virtual machine. Gotta laugh .... right?
So I lent my brother my nexus s that had cm7 on it. He got into the clockworkmod, went to mounts/storage, and proceeded to format everything (bootloader, boot data, etc. everything in there) he said he thought that would fix the force closes, I figured no biggie, but now I can't even get the phone into download mode and I have no idea what to do, the phone will simply not turn on
wow.... dont even know why he would do that.
rule 1: dont lend people your phone.
and i dont know why you would try and get into download mode, Odin isn't the first thing you want to go to.
1. turn the phone off (if it isnt already)
2. hold volume up + power
... what happens? does bootloader mode pop up?
- plug your phone in your computer's USB
- does the sound for USB plugged in occur?
- does computer detect it?
Can't access fastboot.
Phone sometimes recognizes it and says this device is not recognized and it couldn't install the usb driver, sometimes when i plug it in it does nothing.
Didn't want to lend it to him, had no choice. I told him he should have just fixed the permissions on the phone, but then again he's not exactly android literate.
thats just dumb on his part.. i dont know why he would try and mess with your device. if it has problems, just ask you first.
its probably bricked if you cant access download or bootloader... definitely bricked if the computer is unable to detect it
your only way out of it is to get a replacement
In Device/Drivers of windows under Unspecified there's this:
SEC S5PC110 Test/BD
says drivers are not installed
Anybody out there with a solution?
I think there is more than one driver you can try, though I've never flashed anything in Windows (Linux already comes with the driver ), so I don't know for sure. I think I've seen people mentioned a few drivers before, try search for all the "brick" threads here.
Easiest solution might be to download a Linux live distribution (f.e. ubuntu) and run fastboot from there. No need to install any drivers.
Kicking him in the nuts will probably make you feel better... I don't know if it'll fix your phone though.
jruweaver said:
Kicking him in the nuts will probably make you feel better... I don't know if it'll fix your phone though.
Click to expand...
Click to collapse
lmao!!!!!!!!!!
KryPTiCk0d3 said:
lmao!!!!!!!!!!
Click to expand...
Click to collapse
While funny, it doesn't help one bit.
I would try the various methods to get into download mode and use Odin to fix it ...you might be screwed tho
Sent from my Nexus S using XDA App
SphericalPuma said:
While funny, it doesn't help one bit.
Click to expand...
Click to collapse
Unfortunately with the state your phone is in it is probably going to be the best advice you get.
Sent from my Nexus S using XDA App
http://forum.xda-developers.com/showthread.php?t=1000175
any chance that this could help you?
Ddi you ever get your phone sorted ? I'm now in the same situation !
Yes, hit up http://www.mobiletechvideos.com/blog/?page_id=970 For 50 bucks they'll fix your phone and ship it back to you in no time. They got my phone on a Friday, I got it back on either Monday or Tuesday. Of course they're based in Texas and I'm in STL so it could differ for you, but the point is, they're fast, reliable, and professional.
Thanks for that - I'm based in Ireland but I'll give them a shout and see if we can do business......
Thanks a million for the reference PUMA. Please contact me when you are in need of a brick fix. I fix hundreds of Galaxy S / Samsung / HTC variants and several others in a brick of nearly any scenario. I've devoted a lot of time to providing and almost unseen service to people in need versus parting the phone out or trashing it.
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.
Yes, I have read other threads prior to posting this. My Samsung infuse WILL NOT connect to my PC to attempt to use GTG's unbrick to revert back to stock. I have tried the following:
1. Multiple USB cables
2. Install Kies
3. Install Kies Mini
4. Uninstall both versions of Kies
5. Install just sole Infuse drivers
6. Attempted multiple computers (2 Windows 64-bit machines, 1 Windows XP SP3)
7. Attempted to use in VMWARE
8. Performed factory reset
9. Used USBdeview to delete any association of the device with the computer
10. Select mass storage mode when prompted to connect to the PC. Also set it to automatically select this setting.
I have tried everything I can find on this form and on the internet, still no luck. My phone makes the noise that it is going to connect and does nothing. Doesn't show that the device is installing, doesn't ever show up under my computer, just sits there. When I pick mass storage on the ROM it goes back to the main screen. I am running GTG's infused ROM, attempting to take back to stock. I have tried Heimdall, I have tried GTG's back to stock methods, phone NEVER is picked up by the computer even in download mode. To say the least, I have tried this OVER AND OVER on multiple machines, within the past week, and I would like to just go out and run my infuse over with my car at this point. I do not believe I will ever be buying a Samsung device again. Can someone please help me before I go insane? Any recommendations would be greatly appreciate on attempting to get this POS to connect to the computer. I am on Windows 7 64-bit edition.
Since you are attempting to unbrick... Have you tried to do a factory reset from the ROM settings?
Just my 2¢
http://forum.xda-developers.com/forumdisplay.php?f=1237
omnimanx1 said:
Since you are attempting to unbrick... Have you tried to do a factory reset from the ROM settings?
Just my 2¢
Click to expand...
Click to collapse
Several times. I have also tried reflashing the ROM through CWM as well.
drivel2787 said:
Several times. I have also tried reflashing the ROM through CWM as well.
Click to expand...
Click to collapse
1. You might have a bad usb data CORD or one meant only for charging, not DATA. Edit..nvm..saw the first line.
2. Your phone's UBS port may be bad.
3. Are you able to connect via kies air?
Thank you for doing your research. The only thing that I can see that you're missing is that you didn't say you ran the program with admin access. And comon Cheezy.. be nice. This guy knows his stuff man..
Erik_T said:
Thank you for doing your research. The only thing that I can see that you're missing is that you didn't say you ran the program with admin access. And comon Cheezy.. be nice. This guy knows his stuff man..
Click to expand...
Click to collapse
Apologize for not posting, I ran Odin as Administrator, even tried XP Compatibility mode on both Windows 7 64-bit boxes. I installed Ubuntu, but doesn't appear that GTG's Back to stock is compatible with Wine, so couldn't resort to that option. I didn't recall if I had tried installing Kies mini with administrative rights or XP compatibility mode so I'm trying that now. Will report back. I'm thinking I could have a bad data cable that's just used for charging. Thing is, it worked when I originally rooted the phone from Stock, so I was wondering if it had something to do with the firmware for GTG's infused and Windows 7 64-bit. But, I see plenty of people able to get Odin to work on his build, so doesn't make sense to me. I did flash back to GTG's Infused 2.2.1, seems to have fixed some of the issues I was having with 2.2.3 (random freezing of the phone, system volume freezing and crashing when opening through Settings menu), random WIFI turning on/off. That seems to be all good now. Just wanted to figure this issue out.
No luck... But, Kies Air does work. Still doesn't fix the fact that I can't connect via USB to store back to factory. But, I think that both USB cables I have may be bad for data connection. They are the ones that came with the phone, and BOTH cables attempt to just charge the phone and not attempt to mount the external storage in Windows 7 64-bit. Debating whether or not I want to order another cable, thinking about upgrading devices since I'm eligible at this time. Any recommendations on a good upgrade from the Infuse??
drivel2787 said:
No luck... But, Kies Air does work. Still doesn't fix the fact that I can't connect via USB to store back to factory. But, I think that both USB cables I have may be bad for data connection. They are the ones that came with the phone, and BOTH cables attempt to just charge the phone and not attempt to mount the external storage in Windows 7 64-bit. Debating whether or not I want to order another cable, thinking about upgrading devices since I'm eligible at this time. Any recommendations on a good upgrade from the Infuse??
Click to expand...
Click to collapse
If you're looking for a data cable, i got 2 off Ebay for $1 each. They worked. Search for mini usb DATA cable.
I've seen them go bad midcharge. If you had it plugged in, wiggle it, push slightly in each different direction gently. sew if you can get a brief response.
Re: new phone, galaxy note seems to be the hot device.
Sgs2 seems to be the fav by devs
I know you've said you've tried different cables, I had the same problem and it did turn out to be a cable issue. I tried 3 different types, and I ended up having to use one that I got directly from the local AT&T corporate store.
drivel2787 said:
No luck... But, Kies Air does work. Still doesn't fix the fact that I can't connect via USB to store back to factory. But, I think that both USB cables I have may be bad for data connection. They are the ones that came with the phone, and BOTH cables attempt to just charge the phone and not attempt to mount the external storage in Windows 7 64-bit. Debating whether or not I want to order another cable, thinking about upgrading devices since I'm eligible at this time. Any recommendations on a good upgrade from the Infuse??
Click to expand...
Click to collapse
If you have an old Blackberry USB it will work. I use one for my Infuse . Or maybe a friend of yours has one you can try before you decide to buy one...
Just my 2¢
Thanks guys, will definitely give that a shot and buy a new cable. I'm pretty sure that's gotta be what the issue is. I wouldn't think that 3 different computers are bad with two different OS's. I will probably get one here in a few days. I plan on upgrading the device here soon. I bought it out of pocket retail about six or so months ago so I didn't have to renew my contract. I'm waiting to see what they release at the end of next month's conference before upgrading. Probably give a quad core a shot to see how they are
Well, new USB cable NOPE, Still no connection to the phone via USB.
Did you try the ports on the back of the comp?
Sent from my SAMSUNG-SGH-I997 using xda premium
Try PUtting the phone in MTP mode
drivel2787 said:
Well, new USB cable NOPE, Still no connection to the phone via USB.
Click to expand...
Click to collapse
Drivel,
While you are plugged in, try pushing the connection around a bit. See if there is any recognition. If there isn't, i think you may have a hardware issue.
If it was a hardware issue, the trick it's to get att to honor their warranty.
if you're running infused, the trick is how to get out back to stock or to brick it
The closet thing i can think of is to download download dman uckl2 rooted package via kies air or by phone. Dl the stock kernal. Flash the ROM, disable lagfix, then flash the stock kernel.
That's as close to stock as I can think off for you to take to the att store and have them check the usb hardware port
edti: no prob GoSooner.
thanks qkster^ Thanks button failed on me
Take this with a little tolerance from a noob.
I am trying to get my G friends In fuse to upgrade and can't get past the unregistered device.
Shes uses it for prime business and is going out for 2 days so I can't wipe the internal till she gets back but I'm up to the last 2 steps. After pulling the sd card it wanted to but still hung. Will wait till she gets back to wipe the memory clean.
Following long trails of solutions it looks to me for some steps for you to try.
Do a search on your comp and find all kies. Remove all.
Pull usb from comp and phone.
Hard reboot of phone,reboot comp.
Reload Kies mini
Open above, file drop down,load drivers.
plug in usb to comp.
phone usb to kies.
plug in usb. Go/no go?
No go pull phone sd card. Repeat all above. Go/no go.
No go? wipe internal memory.
Repeat /Go/nogo.
No go /Sledge Hammer cure.
Pu
Appreciate the help guys. It's weird because when I first had the phone it worked for me to root the phone. I think I'll just stick to Kies air if I need to back up or anything. I don't feel like going through the trouble of flashing/exchanging and then re-rooting the new phone. I'll just deal with it. With the new USB cord I did trying a Windows 7 64-bit and Windows XP.
I do want to say that I appreciate everyone's help.
Had to remove the site address cause I'm a noob and this info wouldn't post. But the below is the issue for me.
[14] On February 3, 2012, the update went live on Kies Mini.
Samsung Infuses with "Kernel 2.6.32.9" blocks Kies Mini from being able to update to Android 2.3.6 "Gingerbread". An over the air patch should be released by 2/8/2012 to fix this issue.[citation needed]-
I'm not new to android whatsoever.. I've just returned from an Iphone 4s cause i was missing the openess of android. Now.. i've pulled out my old Nexus S 4g, Updated it to 4.0.4 and i cant get it to connect to my computer for the life of me! tried 4 different cables, 5 different computers, every driver i could find and nothing. I've come to believe this is a software failure... All i need is root and i will be able to sleep at night. Could someone package up .zip to give root and twrp recovery that i could flash through stock recovery? I dont know else i could do to get root... but this problem is becoming quite annoying.
1. There is no way to package a zip to flash through stock recovery since it would have to be signed.
2.For someone who is "not new to android whatsoever" making 2 threads about the same topic 2 minutes apart isn't exactly acting the part.
Try this guide.
Actually you're wrong, On the Epic 4G someone did in fact manage to do so. And yeah since i'm not new to these forums i understand that stuff like this gets overlooked so i made two posts. Cry me a river.
BTW Thanks harb... but that would involve being able to connect to my PC. Which just is not possible right now.
Thats the Android Karma... it happens but a little advice.
If you can't connect to the computer then it might a hardware issue not software.
If getting root was that easy that you just had to flash a zip on stock then everyone would be doing it. And good luck getting root without unlocking your bootloader first. Not to be rude but the problem could possibly be between the computer and the chair.
robogoflow said:
Thats the Android Karma... it happens but a little advice.
If you can't connect to the computer then it might a hardware issue not software.
If getting root was that easy that you just had to flash a zip on stock then everyone would be doing it. And good luck getting root without unlocking your bootloader first. Not to be rude but the problem could possibly be between the computer and the chair.
Click to expand...
Click to collapse
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?
grumpySasquatch said:
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?
Click to expand...
Click to collapse
Bro... Chill... They're just trying to help you out. There is NO way to to root your NS without a computer (currently. We are not Epic 4G owners here). You said you didn't use your NS since GB, SO during the time in between something could have happened to the hardware. Don't rule that out just yet. Your drivers might also be bad. Is this what migrating to iOS does to people? Makes them snobby and demand fixes to problems they can't figure out on their own? Don't hate on the XDA forums. If we're not helping you "hit the thanks button anyways, you ungrateful bastard" (XDA into video ). Anywho. Chill. Keep trying.
Nexus S (GSM i9020a)
Paranoid (14.a Hybrid - 4.0.4)
Matrix Kernel (CFS - 20.0)
Intellidemmand (800/100)
Live OC (105 - 800/1000)
Deep Idle (On - Noop)
BLX - 96 (Inverted Apps)
I am chill, i am just trying to describe what I've already done so maybe someone could suggest something else. And no what i meant is i downloaded the OTA on my computer than transferred it onto my Nexus through USB mount a couple of days ago so i know its not a hardware issue. Im not demanding fixes, just trying to see if anyone has done been able to figure this out yet as i know im not the only one with this issue. And there is a big problem w/ people on the XDA forums as a whole.. i am a little frustrated and just dont like when someone is telling me is a User issue when i have tried everything conceivable and know what i am doing.. Sorry if this offended you. and IOS is a good device.. its just like.. NWO they want to control everything haha. I'd rather be part of the rebel faction. even though i love my ipad XD
There is currently no way to root 4.0.4 without an unlocked bootloader (and no custom recovery), and the only way to get an unlocked bootloader is to either have root or plug it into the PC and unlock via fastboot. As such, you are stuck with sorting out drivers - despite how annoying they are.
The video i linked to above describes in detail (and through video) exactly how to sort out NS drivers on Windows machines as well as the required fastboot commands to get a custom recovery.
Harbb said:
The video i linked to above describes in detail (and through video) exactly how to sort out NS drivers on Windows machines as well as the required fastboot commands to get a custom recovery.
Click to expand...
Click to collapse
Yes that is a good video, and does a job well done in describing on how to install drivers. My main issue is that my Computer(s) are'nt recognized my device at all... It doesn't show up as android device, or nexus s... but Unknown device. If i could figure this out i believe i could handle the rest.
grumpySasquatch said:
Yes that is a good video, and does a job well done in describing on how to install drivers. My main issue is that my Computer(s) are'nt recognized my device at all... It doesn't show up as android device, or nexus s... but Unknown device. If i could figure this out i believe i could handle the rest.
Click to expand...
Click to collapse
Pretty sure that video describes that. You need to open up device manager, double click unknown device (while device is in fastboot), hit update driver and navigate to the provided drivers on the site. Watch it a few times, you'll figure it out.
Have you tried to install PDANet? I've read numerous times about it working wonders for users who have trouble with drivers. It has all of the necessary drivers built in.
Sent from my Nexus S using xda premium
d_phekt said:
Have you tried to install PDANet? I've read numerous times about it working wonders for users who have trouble with drivers. It has all of the necessary drivers built in.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
yes i second that,PDANet Drivers usually work across all devices you should try them.
Like ppl said before, try PdaNet drivers it might help.
thanks everyone, , but like i said i tried pretty much every driver you can find online. they will not install as my device comes up as "Unknown", i've literally tried every piece of literature on the web relating to this issue... at this point i'm just going to wait for the JB update and see what happens.
grumpySasquatch said:
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?
Click to expand...
Click to collapse
So the ICS update makes you unable to boot to fastboot and makes your device unable to be recognized by your computer from there?
That's a new one. As far as I know, "Unknown device" is actually your device being recognized, just the driver doesn't get installed correctly.
Have you tried manually specifying which driver to install and selecting the PDA Net driver? Look at Harbb's last post.
Have you went as far as editing the drivers inf to match your hardware ID? I know I had to do that way back when the PDA net drivers weren't even available.
'til then, user error.
polobunny said:
Have you tried manually specifying which driver to install and selecting the PDA Net driver? Look at Harbb's last post.
Have you went as far as editing the drivers inf to match your hardware ID? I know I had to do that way back when the PDA net drivers weren't even available.
'til then, user error.
Click to expand...
Click to collapse
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?
Epic 4G could do this in FROYO... It was patched by google in 2.3+. Do you want an app to secretly root you and install malware?
Sent from my Samsung Epic 4G using Tapatalk 2
grumpySasquatch said:
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?
Click to expand...
Click to collapse
Well it is going to be basically one of two things.
1. Is user error of some sort. That is what people have been trying to help with.
2. Is hardware issue that no one can help you with of course. Or some software issue causing it to not show up for who knows what reason. Neither of which folks can help with since a computer is not seeing it. So they revert back to what they can. Point 1
When you asked a question like is there a zip that you can flash in stock recovery to give you root or custom recovery that also doesn't help your cause for people assuming user error.
The one other thing you can try is download mode and Odin.
grumpySasquatch said:
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?
Click to expand...
Click to collapse
Cool. Trash your Nexus S, clearly broken.
Edit: That's nice of you albundy, but Mr grumpySasquatch (fitting name eh?) has tried everything, including modding the drivers inf. His Nexus S is broken beyond repair, also the first one we've ever seen that won't adb but works fine for USB mounting. *chuckle*