So I'm ready to return this phone and switch to Verizon and a Droid X
Problem 1: No matter what I try I cannot get this phone to connect to my laptop or PC I have probably spent almost 6-10 Hours trying to do this.
Problem 2: This is no where near the concern of problem one but it's annoying as hell, following many of the users advice in order to sync my contacts I used a gmail account and it synced 750 of my "contacts" while most of those 750 are worthless to me I have about 210 or so I actually need. So in order to fix this I created a new gmail account and only copied the contacts I needed as a .csv and synced now I can't get rid of the contacts from the original sync without restoring the phone or so it says.
Setup 1: Laptop Dell Lattitude D630 with Windows XP 32bit SP3 and .net frame work 4. I have tried almost everything. Tried using Kies, Updating Kies, Reinstalling Kies, Reinstalling Drivers, Tried ever driver out there, backdating and redoing it all over again etc. tried different USB Cables the closest I ever got was where it would say Connecting ( displayed in KIES ) and would eventually time out.
Setup 2: Desktop Windows XP SP3 32 Bit .net frame work 4 basically ran down the same thing on the desktop as well except for trying the original USB cable going to try that tomorrow
With both setups I can't get either to connect or even mount the drive in debug mode so I can;t even root this piece of garbage.
IS it me? Am I doing something wrong? If so call me an idiot and tell me how to fix it. I'm open to try anything at this point as this is more frustrating then using that piece of garbage Tilt 2 I had before this.
Please oh geniuses of XDA HALP!
If you have any questions please ask or if you think I left something Important out as well
This may or may not help you; however I had to get the official drivers from Samsung and not the ones that people were using - the Galaxy S drivers caused more problems for me. Uninstall, reinstall the proper drivers, reboot. Then reconnect, expand the drivers installation "balloon" and make sure the four drivers necessary install correctly. I kept having a problem with the USB Mass Storage Driver - but the second time got it.
On the phone, switching from Samsung Kies to USB Mass Storage then enabling USB Debugging and connecting directly to my machine(s) solved most of my probs. I'm using the original USB cable; but to be honest not too sure that would make a difference - just don't go too cheap - I'm also using the Nokia N810 microUSB cable without issues.
Not 100% sure that will help you, but I also had some troubles initially. Don't fret. And good luck.
I just went through exactly the same ordeal you describe with a Win XP machine.
I eventually got it to work, here's what I did:
1. I Downloaded and installed in the following order:
A. Windows Installer 4.5 ... reboot
B. .NET Compact Framework 3.5 redistributable ... reboot
C. .NET Framework 4.0 redistibutable ... reboot
D. Windows XP sp3 ... reboot
After that I downloaded the drivers from the Samsung site, installed them and prepped my phone by putting it in mass storage mode, and turning debugging on.
After another reboot, I connected my phone, waited and prayed ... and it worked. It was a rather long wait as I watched it install the drivers ... be patient.
I think the prayer is what eventually worked ...
ekasey said:
So I'm ready to return this phone and switch to Verizon and a Droid X
Problem 1: No matter what I try I cannot get this phone to connect to my laptop or PC I have probably spent almost 6-10 Hours trying to do this.
Problem 2: This is no where near the concern of problem one but it's annoying as hell, following many of the users advice in order to sync my contacts I used a gmail account and it synced 750 of my "contacts" while most of those 750 are worthless to me I have about 210 or so I actually need. So in order to fix this I created a new gmail account and only copied the contacts I needed as a .csv and synced now I can't get rid of the contacts from the original sync without restoring the phone or so it says.
Setup 1: Laptop Dell Lattitude D630 with Windows XP 32bit SP3 and .net frame work 4. I have tried almost everything. Tried using Kies, Updating Kies, Reinstalling Kies, Reinstalling Drivers, Tried ever driver out there, backdating and redoing it all over again etc. tried different USB Cables the closest I ever got was where it would say Connecting ( displayed in KIES ) and would eventually time out.
Setup 2: Desktop Windows XP SP3 32 Bit .net frame work 4 basically ran down the same thing on the desktop as well except for trying the original USB cable going to try that tomorrow
With both setups I can't get either to connect or even mount the drive in debug mode so I can;t even root this piece of garbage.
IS it me? Am I doing something wrong? If so call me an idiot and tell me how to fix it. I'm open to try anything at this point as this is more frustrating then using that piece of garbage Tilt 2 I had before this.
Please oh geniuses of XDA HALP!
If you have any questions please ask or if you think I left something Important out as well
Click to expand...
Click to collapse
You're better off with an iPhone iOS4. Getting the Droid X is just as complicated, it's just how a Android is. You got to learn to use it before it gets powerful.
On a side note, if you do what the above posters are telling you to do, then I hope you love your Captivate as much as I love mine.
Best damn phone I have ever had. Have not had one real problem with it.
But please, read through the android development stickies, there are so many tutorials you just need to follow.
Download the Drivers you need, 32 or 64 bit what ever you need.
gerbick said:
This may or may not help you; however I had to get the official drivers from Samsung and not the ones that people were using - the Galaxy S drivers caused more problems for me. Uninstall, reinstall the proper drivers, reboot. Then reconnect, expand the drivers installation "balloon" and make sure the four drivers necessary install correctly. I kept having a problem with the USB Mass Storage Driver - but the second time got it.
On the phone, switching from Samsung Kies to USB Mass Storage then enabling USB Debugging and connecting directly to my machine(s) solved most of my probs. I'm using the original USB cable; but to be honest not too sure that would make a difference - just don't go too cheap - I'm also using the Nokia N810 microUSB cable without issues.
Not 100% sure that will help you, but I also had some troubles initially. Don't fret. And good luck.
Click to expand...
Click to collapse
Can you link me to the Driver set you used? I have tried the captivate drivers, the T mobile Versions as well, along with a the generic Galaxy S drivers
Battlehymn said:
I just went through exactly the same ordeal you describe with a Win XP machine.
I eventually got it to work, here's what I did:
1. I Downloaded and installed in the following order:
A. Windows Installer 4.5 ... reboot
B. .NET Compact Framework 3.5 redistributable ... reboot
C. .NET Framework 4.0 redistibutable ... reboot
D. Windows XP sp3 ... reboot
After that I downloaded the drivers from the Samsung site, installed them and prepped my phone by putting it in mass storage mode, and turning debugging on.
After another reboot, I connected my phone, waited and prayed ... and it worked. It was a rather long wait as I watched it install the drivers ... be patient.
I think the prayer is what eventually worked ...
Click to expand...
Click to collapse
Will Give it a Try
SlimJ87D said:
You're better off with an iPhone iOS4. Getting the Droid X is just as complicated, it's just how a Android is. You got to learn to use it before it gets powerful.
On a side note, if you do what the above posters are telling you to do, then I hope you love your Captivate as much as I love mine.
Best damn phone I have ever had. Have not had one real problem with it.
But please, read through the android development stickies, there are so many tutorials you just need to follow.
Download the Drivers you need, 32 or 64 bit what ever you need.
Click to expand...
Click to collapse
I don't use Apple products, but thanks.
It's not that the Software or procedures are beyond my scope of intellect. It seems that every stickied thread I have read on here has 11 different ways of doing the same thing, and not one process works the same for everyone.
Like I said I'm not opposed to trying anything at this point or starting from scratch I just figured it would be a little bit less confusing.
I guess I assumed it would be
DL Software > Install Drivers and Software > plug in phone and magic it works haha.
So far I love the phone besides the fact that it had an SMS error the other day and Deleted all of my texts, the audio jack has become flakey, and the gmail app has consistent errors. OH and I'm missing text messages from people
Drivers are here: http://www.samsung.com/us/consumer/...ATT/index.idx?pagetype=prd_detail&tab=support
Battlehymn said:
Drivers are here: http://www.samsung.com/us/consumer/...ATT/index.idx?pagetype=prd_detail&tab=support
Click to expand...
Click to collapse
Thanks wanted to be sure, I had tried those on the laptop, I will try them tomorrow along with the other suggestions. Wish I had an office job like I used to then I would screw with it at work.
To fix the contacts, turn off the contact syncing, dowload Contact Remover from Market, run Contact Remover and select all contacts then delete. Now you can turn contact sync back on and you should be all set.
Sent from my SAMSUNG-SGH-I897 using XDA App
you could try simpler first - try to connect without Kies;
1. Phone ->settings->applications->usb settings -> ask on connection
2. Install drivers - I installed the AT&T captivate drivers, then the Samsung Drivers
3. Connect phone - if the screen is unlocked, you should see an option for which USB setting you want
4. Pick Mass storage
5. You should see one or two new drive letters on your machine (internal and SD card if you have one)
6. Pull down notification bar on phone, click USB, use for files, Mount drive
This will validate that you have the drivers installed without doing everything else that is involved with .Net stuff
You really only need the Captivate AT&T drivers for this part to work.
I have 2 XP machines and I have full functionality without installing Kies.
I probably tried everything as well..... if not more, but kept trying on my Win 7 64bit.
Don't know of which step finally worked but in using the updated version of Kies (Kies_1.5.1.10074_2_6), Samsung cable (non-motherboard port?), Samsung official 64bit USB drivers, unmounting External SD, setting Captivate to "ask preference for USB", and a final deep breath.
I ended up copying the Samsung USB driver folder to an easy to find location (desktop) and while in Kies(probably not necess.) I opened Windows device manager and asked each device error message to search that folder for correct driver one by one. It finally worked. I used Kies for Outlook Contacts, selected and used Media Center for music(had to remount SD before it would be recognized). Haven't used, but tried mass storage, modem(tether) and they were correctly recognized. Good luck!
What finally did it for me, after getting all the drivers to install with the phone in debug mode, was to set it to always ask on connection. It refused to install the mtp driver if I just set it to mass storage and left it there. I have no idea why, as mass storage is what I click when it connects, but it seems happier this way.
Sent from my SAMSUNG-SGH-I897 using XDA App
I had problems with kies and launcher pro. Had to switch back to original launcher for kies to work. Haven't tried in awhile.with both programs getting updates, it may be fixed now. My .02.
Sent from my SAMSUNG-SGH-I897 using XDA App
I had the same problem. .. actually I still have the same problem, however, there are ways to root and enable sideloading without ever hooking up to the computer. Try that out. If you can't find out how to do it, let me know and I'll do a write up.
Rooted Capivate Galaxy S
naplesbill said:
To fix the contacts, turn off the contact syncing, dowload Contact Remover from Market, run Contact Remover and select all contacts then delete. Now you can turn contact sync back on and you should be all set.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Thanks Will do this today.
everything else I will try tonight and let you guys know how it goes I will do it on both my laptop and on my PC at the same time.
Thanks so much for all the suggestions guys
I had the same problem with launcher pro, no matter how I tried to connect, unless I was in debug. Switching to the always prompt or whatever took care of that for me.
Sent from my SAMSUNG-SGH-I897 using XDA App
i knw this isnt really helpful but dont throw it out the window send it to me hehehe
I just tried the older cable that was party to all the unsuccessful Kies attempts and got the same error. Tried Samsung cable.....no issues. Odd because that same cable worked fine for EVO 4G and a Motorola device and Moto Phone Tools.
Could be fluke?
Well first off I want to thank everyone for the words of encouragement. I was able to finally get the phone rooted. not 110% sure how I did it but it's now done.
My second issue is now getting Kies to work, all it does is sit there and say connecting device
Thanks again everyone
My Kies Mini used to crash whenever I connected my phone. I found this advice somewhere on the internet and it worked for me:
Consulting the crash report he came up with the following:
1. Uninstall Kies Mini
2. Uninstall Internet Explorer 9 (beta or RC1).
3. Install Kies Mini
You don't have to uninstall Kies Mini - just install IE9 Beta and reboot. That's how I fixed my problem.
It still didn't work for me. Oh well, back to Supernova
Holy crap it worked. haven't been able to get Kies to work at all on Win 7 x64. Uninstalled IE9 and it worked first try. Sweet. Now I'm REALLY ready for 2.2 lol.
Worked
After spending several hours trying my own fixes as to the crashing problem i came across this post and realized that this must be the problem. with IE 9 not completely stable the Kies program isn't designed for anything like that and will freak out. This did work for me and solved one of the problems that i was having with trying to update my Samsung Galaxy S (AT&T) to 2.2, the other problem was the the phone was not connecting to the computer when it was in Kies mode. I found (once again on these forums) that there was an issue with have file names that had mode then 16 symbols. once i had both of those problems fixed and with a factory restore just for good measure i was able to update to 2.2 with out any further problem.
Something that i spent hours on the phone with samsung tech support on both level 1 and 3 and they could not figure it out, a great forum community helped me figure it out.
I had tons of problems trying to update via Kies Mini while using Windows 7 64-bit. It was VERY frustrating. You can read my full story here:
http://androidforums.com/2336420-post20.html
Some of you may have more success than others and myself, but if you're having issues, READ ON!
That said, I found another solution on AT&T's Facebook page from a "Spike Falana".
1. Basically, go here: http://dls.scione-music.de/KIES/ (click link)
2. Download an older version of Kies (non-Mini). Spike used Kies_1.5.3.10083_66.exe, and so I did too.
3. Install Kies, run it. DO NOT let it update.
4. Plug in your phone, Kies will recognize it.
5. Update your firmware.
I have no idea why the US has been stuck with Kies Mini, but this solution works so well it's mind-boggling. The update took less time than it took to write this post to complete.
My phone was successfully updated to Froyo (official) 2.2, I897UCKB1 in less than 20 minutes if you include the download time.
Crazy. Just crazy. NO IDEA why Kies Mini won't work when the full version of Kies works so perfectly.
Before you jump through to many hoops uninstall IE9 if you have it installed. That worked for me.
KewlRobD said:
Before you jump through to many hoops uninstall IE9 if you have it installed. That worked for me.
Click to expand...
Click to collapse
now that's an interesting thought.... I wish I had heard of such an idea for a solution before I tried what I did, but at least I found something that worked, haha.
thanks for the pointer though!
For what it is worth, I have a 64 bit Windows 7 system and I was able to install with Kies Mini without issue. I do not have IE9 mind you, but just in case anyone else is having issues I used the following method which differs from what I have seen some post:
Obviously install Kies Mini and the Captivate drivers from the Samsung website if you haven't already (make sure you have uninstalled any previous version of Kies you might have).
Turn off debugging if you have this selected.
Set the phone to ask what to do when it is connected via USB.
Plug the phone into your computer USB connection.
Wait while it loads the drivers etc. The phone should eventually say connected, but do not start Kies Mini yet.
For me, after up to around 10 seconds after the phone says it is connected, the Windows autoplay selection box will pop asking what you want do (view files, play media, etc.)
Once that box pops up, then start Kies Mini.
You should be good to go - at least that is the most reliable way I have found. If I try and launch Kies as soon as the phone says 'Connected' though and don't wait for the autoplay box to pop up then Kies won't see the phone.
Hopefully this may help someone.
Hello!
I have been facing a peculiar problem since last week.
When I plug in my Core, it starts charging instead of connecting as a media device/ camera, before which it used to work fine. But If i plug in my Core before booting my PC, it recognises it as a media device or camera and i can use it in the usual way. Ditto for my External hard drive.
I know it's a PC problem coz it gets detected straightaway in other PCs but this is the only PC I have and it is causing me problems as any virus that comes with it will have a free hand if i connect it during boot. or won't it? any help will be appreciated!
Core UserRob said:
Hello!
I have been facing a peculiar problem since last week.
When I plug in my Core, it starts charging instead of connecting as a media device/ camera, before which it used to work fine. But If i plug in my Core before booting my PC, it recognises it as a media device or camera and i can use it in the usual way. Ditto for my External hard drive.
I know it's a PC problem coz it gets detected straightaway in other PCs but this is the only PC I have and it is causing me problems as any virus that comes with it will have a free hand if i connect it during boot. or won't it? any help will be appreciated!
Click to expand...
Click to collapse
Try to re-install your window, and again install samsung drivers i.e, ''kies'' keep any antivirus ,in future
hope that ll work..
anup34 said:
Try to re-install your window, and again install samsung drivers i.e, ''kies'' keep any antivirus ,in future
hope that ll work..
Click to expand...
Click to collapse
Hey!
Thanks for replying but if you noticed I have mentioned its not a problem specific to Core, but is happening with my external hard drive/ flash drives too, so reinstalling kies wont help.
Nevertheless, I did update the driver for core as soon as this problem cropped up (about 3 weeks) and that didn't help
Also reinstalling windows would be the last resort. I was hoping to find something other than that.
oh btw, it's not a virus/malware/rootkit problem 'coz I DO have a licensed Anti virus up and running since I first bought this PC which should be 2 yeas now. I asked about the virus coz if i connect my core during boot, and 'suppose' my mobile has got infected by a virus since the last time i scanned it, wont the virus have a free hand till my pc boots as the anti virus will essentially scan it only after windows starts?
I have done system file check but no problem there.
I got a couple of things I 'll try before formatting my c drive like updating BIOS and running memtest for RAM. if these don't work then I 'll have no other option left
people please feel free to pitch in with any ideas which could detect the problem
had the same issue
Core UserRob said:
Hey!
Thanks for replying but if you noticed I have mentioned its not a problem specific to Core, but is happening with my external hard drive/ flash drives too, so reinstalling kies wont help.
Nevertheless, I did update the driver for core as soon as this problem cropped up (about 3 weeks) and that didn't help
Also reinstalling windows would be the last resort. I was hoping to find something other than that.
oh btw, it's not a virus/malware/rootkit problem 'coz I DO have a licensed Anti virus up and running since I first bought this PC which should be 2 yeas now. I asked about the virus coz if i connect my core during boot, and 'suppose' my mobile has got infected by a virus since the last time i scanned it, wont the virus have a free hand till my pc boots as the anti virus will essentially scan it only after windows starts?
I have done system file check but no problem there.
I got a couple of things I 'll try before formatting my c drive like updating BIOS and running memtest for RAM. if these don't work then I 'll have no other option left
people please feel free to pitch in with any ideas which could detect the problem
Click to expand...
Click to collapse
hi buddy
i had the same issue few months ago. it was frustrating. i tried everything and it failed. im using avast antivirus .i suspected that it was the cause but it wasn't. as far as i remember the problem occurred while i plugged in the core to kies and it suddenly showed the phone unrecognizable since i think its running on omkars Monster$ rom.i suspect kies sort of deleted the reg files or something of the core and it became unrecognizable. fortunately for me my windows 8 was giving some other issues so i reinstaled it completely. aaaand the problem is gone. i kept away from KIES ever since and so far no issues at all.
hope i helped.
cheers..