Related
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
Kies mini is constantly crashing on me, both on my laptop (win7 x86) and desktop (win7 amd64). I've seen people giving random suggestions on things like trying different USB ports, formating internal SD, etc. None of them worked for me. So I took out windbg...
Turns out Samsung is making a stupid mistake in their AMiniFusCtrl.dll, when calling HttpOpenRequest. The lplpszAcceptTypes they pass in is not NULL terminated! So a random data past the end of the array could trigger an AV, that is, a crash. In fact I'm really surprised that majority of people have no issues.
Anyway, I took the work to patch AMiniFusCtrl.dll to load my hand-crafted ApiHook.dll, which hijacks the call to HttpOpenRequest to provide a safeguard there. Ok I'm not gonna dig into how it works here... The result is I finally upgraded my phone through an official means! (well, sort of )
And here I'm attaching the patch. You need to extract and put the two files AMiniFusCtrl.dll, ApiHook.dll in your Kies mini install folder, which by default is "C:\Program Files\Samsung\KiesMini" or "C:\Program Files (X86)\Samsung\KiesMini" on 64bit Windows. Remember to backup your original AMiniFusCtrl.dll.
P.S. I kinda suspect the "unregistered device" error is also due to the same bug, since during my test, it gave the same error when my hijacked HttpOpenRequest fails.
You are the man. This finally allowed me to update my Captivate to JF7. Could never get past 50% with the OTA and Mini always crashed on Win7 64-bit.
This did the trick. Thanks!
I'm have a Vibrant. Before Kies mini was giving me the error "minilauncher application has stopped working". I tried these files and now I get Unregistered Device. Ideas?
Good work, hope the Samsung developers that troll these forums take notice. I use to try to debug stuff that would crash on NT but not on 95/98 way back when in a similar manner and report it to mostly deaf software companies -- luckily all that knowledge is long gone having been at a unix shop for so long.
I tried installing the Kies Mini App. on two different computers (one Vista 32bit and one Win7 64bit). Both computers gave me the same crash/error with Kies Mini as soon as I plugged my phone in. I tried the patches above, and they had absolutely no effect on either computer. I'm on Samsung Vibrant from Tmo, and using the Tmo specific version of Kies but I don't see why this would matter for the patches.
Any Suggestions????
I tried this and it still says my device is unregistered how do i fix this samsung doesn't know crap
Worked perfect for me man! Thanks mucho!
Win 7 64-bit
jasonxh said:
Kies mini is constantly crashing on me, both on my laptop (win7 x86) and desktop (win7 amd64). I've seen people giving random suggestions on things like trying different USB ports, formating internal SD, etc. None of them worked for me. So I took out windbg...
Turns out Samsung is making a stupid mistake in their AMiniFusCtrl.dll, when calling HttpOpenRequest. The lplpszAcceptTypes they pass in is not NULL terminated! So a random data past the end of the array could trigger an AV, that is, a crash. In fact I'm really surprised that majority of people have no issues.
Anyway, I took the work to patch AMiniFusCtrl.dll to load my hand-crafted ApiHook.dll, which hijacks the call to HttpOpenRequest to provide a safeguard there. Ok I'm not gonna dig into how it works here... The result is I finally upgraded my phone through an official means! (well, sort of )
And here I'm attaching the patch. You need to extract and put the two files AMiniFusCtrl.dll, ApiHook.dll in your Kies mini install folder, which by default is "C:\Program Files\Samsung\KiesMini" or "C:\Program Files (X86)\Samsung\KiesMini" on 64bit Windows. Remember to backup your original AMiniFusCtrl.dll.
P.S. I kinda suspect the "unregistered device" error is also due to the same bug, since during my test, it gave the same error when my hijacked HttpOpenRequest fails.
Click to expand...
Click to collapse
Problems File is invalid....unknown format or damaged when opening with WinRar..
Explorer says file is invalid
i have updated two dlls but it says device unregistered.
any suggestions on how to overcome this?
ok kies mini right now is working only for the captivate so vibrant users are gonna have to wait for a while
This worked for me! My problem started when my attempts at OTA failed leaving me with a pseudo JH7 update (baseband was showing JH7 but no signs I actually got any part of the update).
Having tired of trying OTA, I downloaded Kies Mini and got the "unregistered device" error.
I then ran across this today and it worked perfectly. I have a full-on JH7 - no problems. THANK YOU!
Thanks
Worked like a champ, thanks for taking the time to fix Samsung's mistake.
Anybody find a way to update the vibrant?
Awesome!! That worked great! Thanks for sharing this with us!
That's a Developer 101 mistake. Can you imagine the garbage code in our phones? It's no wonder they can't fix the gps and froyo is taking so long.
Sent from my SAMSUNG-SGH-I897 using XDA App
Kies Mini would crash as soon as I connected my T-mo Vibrant (before acknowledging the connection), giving me the "MiniApplication Launcher has stopped working" error. Now with this patch, it acknowledges the connection, but crashes while trying to determine the firmware. Anyone have any ideas? I'm running Win7 64bit.
Edit: I ended up trying Kies v1.5.3.10093_82 as posted on the Samsung Galaxy S Series page on xda. It works like a charm! Wish I could post a link, but I'm under n00b restrictions.
Thank's so much for this. I've spend the last few days trying to figure out why my Captivate would cause the application to crash. You are a lifesaver!
Thank You!
I just got my captivate yesterday and have been trying update it with kies mini but to no avail.....that is until i came across this! Works like a charm, thank you!!!
Nice work! Perfect. Thanks.
Still not working
I followed the steps listed but kies still crashes on me once I connect my phone. I'm going to have to contact AT&T I guess. Also I'm not able to run kies mini with usb debugging enabled, and for some reason my kies keeps switching to Korean.
Update: Was able to get mini kies to stop crashing thanks to your fix but it now states "Failed to Connect Model Information Server". Also not sure why mini kies defaults to Korean on me but discovered that only happens when it's not run as an administrator.
I used designgears' jh7_ota.zip to update my phone to JH7. It worked fine. The one reason why I used it was because the OTA update had gone through to 100% and then crashed. In the "About phone" menu it had the right kernel version and the right baseband version, but the Build number was stuck on ECLAIR and not showing ECLAIR.UCJH7 like it should. So after using the JH7_OTA.zip it showed the right build number and the PC Internet option was gone from USB options like it should have been. Also, the GPS started working pretty well.
The one thing that sucked was it completely wiped my phone. So after reloading all my apps and redoing all the customizations I finally got it back to how I like it. Then I happened to notice that the "Build number" had somehow reverted back to just "ECLAIR". I also noticed that "PC Internet" was back as an option when USB was plugged in. I have no idea how it reverted back after I had successfully installed JH7. I never used ROM Manager or Titanium Backup to restore anything, I just went and redownloaded everything and reinstalled everything.
Has anyone else seen or had this happen to them? I had to reinstall JH7_OTA.zip again. And again it wiped my phone out completely. Having to go back through and reinstall everything all over again. How annoying.
You could always master clear, flash stock JF6 and then use Mini Kies to get the update. That way you know you have a fresh install.
I just did that coming of Cognition, loved it but didn't use any of the useful features (mobile AP, tethering) to make it worthwhile. I still bought DG a beer, dude works hard.
That was what I did to get the JH7 update. Although, I did use designgears' zip file rather than mini kies. Mini Kies wasnt out at that time. I used odin one click to revert to stock JF6, then the first thing I did was install clockwork recovery, then I installed designgears' zip file. Everything worked great for weeks. Cant see how or why it reverted back to build number "ECLAIR" from "ECLAIR.UCJH7".
I reinstalled JH7 with DG's zip file again since I still had it on my sdcard. Its back to the right version, build number says the right thing and pc internet is not an option and gps seems to work good and battery life seems to be better again. If it monks up again I will flash back to JF6, then use mini kies to get the JH7 update and try that.
I dont know whether its android or its just this galaxy S, but I've never had such a glitchy phone before. Random software crashes, random shutdowns, half-baked gps, updates that dont work and even brick phones. Just seems like I cant go more than a day or two without something on this phone F'ing up. Is this how it is with android all the time? This feels like the microsoft windows world a la 1995-2000. I thought we moved past all these crashes and glitches with plug and play and with Windows XP.
May or may not be the same thing ... but ... my wife updated to the current release OTA and said it worked. However I noticed the other day that she still has the PC Internet option that shouldn't be there.
jahfry said:
May or may not be the same thing ... but ... my wife updated to the current release OTA and said it worked. However I noticed the other day that she still has the PC Internet option that shouldn't be there.
Click to expand...
Click to collapse
Go to About Phone and look at the build number on her phone. If it really took the full update it will say "ECLAIR.UCJH7". If it didnt it will still say "ECLAIR".
The very first time I tried to get the update OTA, it downloaded, then installed and it went to 100% on the install screen, but once it reached 100%, it then said "Update is failed". And when I rebooted it, the build number was still at "ECLAIR". and I still had PC Internet option and Quick Office wasnt installed and it acted kind of "glitchy".
When I downloaded and installed the zip file from Designgears, I could tell right away the the update was truly installed. Build number was "ECLAIR.UCJH7". PC Internet option was removed from usb options. Quick Office was installed. It ran a little smoother. GPS performance was somewhat better, and I did notice improved battery life.
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.
This looks fairly weird.
I'm running the latest Mini Kies (11014_6) on a Windows XP system. My IE is version 8, I never installed IE 9.
I start the Mini Kies up, it asks me to connect my phone. I connect my Captivate (stock ROM, rooted) in the USB debugging mode. The Mini Kies recognizes it, displays the model name (SGH-I897) and the phone number, thinks for a sec, and tells me there's a firmware upgrade available. Helpfully it displays a big "Phone Upgrade" button in the bottom left corner. So far so good.
Now, when I click on that button, the Kies Mini window disappears for a second and then returns, exactly the same. I don't get the next screen (where I'm supposed to consent to the upgrade), instead I'm again looking at the same "Phone upgrade" button. Rinse and repeat.
I've reinstalled Kies Mini (with the manual purging of its keys from registry), tried running an _4 version without letting it upgrade to _6, tried connecting the phone in the Kies mode.
Same result everywhere -- the Kies Mini sees my phone, offers to upgrade it, and then doesn't do anything. It does not crash -- just returns to the same phone upgrade screen.
Anyone had problems like this? Any ideas?
KaaX
I have the same problem with two Captivates.
No ideas from me.
Update: I sidestepped the problem by installing Kies Mini on my netbook (which hasn't seen any Kies or Captivate drivers before) and updating the phone from it. The whole thing worked without a hitch.
This makes me suspect that the issue is somehow connected with the Samsung phone drivers on Windows, though now that I've updated my phone I can't be arsed to fix the Kies on my desktop machine.
KaaX