Strange Mini Kies problems trying to update to Froyo - Captivate General

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

Related

How to: Samsung Kies program

It works, though not made for the Captivate. Here's how to get it:
First, you will need to get .NET 4 Framework from Microsoft and install that. You will need to restart your computer after installing, so be prepared.
Go to samsungapps.com or it should be the first search link when searching for Samsung Kies using Google.
It will tell you that it's not available for the US.
Click the "Applications" tab in the upper right part of the screen.
Click "See all Countries"
Click on "Europe" then select "United Kingdom" (I did this just to make sure that whatever follows would be in English, but it may not matter)
At the bottom-center there will be a link "Download Kies" Save or Run the .exe
During installation, it will ask you what language you want. You can choose US at that point.
Phone wouldn't connect at first. I closed the program, disconnected the USB cable, then reconnected the USB cable and Windows started installing drivers. After that, I reopened Kies, selected Samsung Kies on the phone when prompted for USB connection type, and it started establishing connection with the phone. It will then show the phone's model number and your wireless phone number.
If you're having trouble after the drivers are installed, just make sure that the "MTP Application" with USB connector symbol is displayed on the phones screen. It Kies should recognize the phone and connect automatically after that.
It has a few useful features, but isn't the best phone assisting software I've used.
Thanks for this. I just wish I had it before I spent so much time getting my Outlook contacts on my phone.
I installed and ran the program before connecting my phone. When I did connect, it recognized it right away.
What kind of system did you do this on? I tried it a couple of days ago, but my 64 bit Win 7 system had no love for the Samsung MTP USB drivers.
XP, sp3
Someone posted on another topic that they had to update the .NET framework and some other stuff to get it to work on 7.
Sent from my SAMSUNG-SGH-I897 using XDA App
I tried doing it on xp sp3 as well and it always says connecting device and it won't ever connect. Tried to re-install and all that updated everything and still wont work
Why do I need Kies? (innocent tone) All I've needed is mass storage option..
After installing Kies I kept having problems with Win7 64 bit until I plugged the USB cable directly into one of the motherboard ports. Once I did that things started working correctly.
I'm using Windows 7 Starter on my netbook. It's true, you have to get .NET 4 Framework, and I'll add that to the original post.
No one NEEDS Kies, but it is nice to have if you want to back up your contacts and convert videos to play on the phone.
Dave
I've found this only connects if you're using the TouchWiz launcher.
phrebh said:
XP, sp3
Someone posted on another topic that they had to update the .NET framework and some other stuff to get it to work on 7.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Tried that too. The Kies Recovery Mode attempts to install the drivers and the Samsung Android USB Composite Device does install but the CDC Abstract Control Model (ACM) driver fails.
Any idea what that "other stuff" is that might be needed?
Tnx
this is great... but for whatever reason, when transfering music, i can't get playlists to transfer, nor some album art...
oh and i'm using it on win 7 pro x64... you do need the .net 4 framework and it will only connect while using TouchWiz :-\
Truceda said:
It works, though not made for the Captivate. Here's how to get it:
First, you will need to get .NET 4 Framework from Microsoft and install that. You will need to restart your computer after installing, so be prepared.
Go to samsungapps.com or it should be the first search link when searching for Samsung Kies using Google.
It will tell you that it's not available for the US.
Click the "Applications" tab in the upper right part of the screen.
Click "See all Countries"
Click on "Europe" then select "United Kingdom" (I did this just to make sure that whatever follows would be in English, but it may not matter)
At the bottom-center there will be a link "Download Kies" Save or Run the .exe
During installation, it will ask you what language you want. You can choose US at that point.
Phone wouldn't connect at first. I closed the program, disconnected the USB cable, then reconnected the USB cable and Windows started installing drivers. After that, I reopened Kies, selected Samsung Kies on the phone when prompted for USB connection type, and it started establishing connection with the phone. It will then show the phone's model number and your wireless phone number.
If you're having trouble after the drivers are installed, just make sure that the "MTP Application" with USB connector symbol is displayed on the phones screen. It Kies should recognize the phone and connect automatically after that.
It has a few useful features, but isn't the best phone assisting software I've used.
Click to expand...
Click to collapse
I'm on Win 7 64 bit , amazing guy , you're the best
Wow thnx a lot! finally its working for me and i have a windows 7 x64.
Can't connect.
My phone is rooted and all drivers installed fine except the MTP driver won't install.
I can choose mass storage and mount but when I choose Kies option on the phone it just goes crazy and keeps flashing MTP on the phone.
Someone posted somewhere that you need to do a factory reset but I really don't want to do that cause it will wipe all my apps and stuff.
Any other ideas?
You need to connect the usb cable with it already set to the Kies option.
My phone connects to Win7 x86 when it is in development mode and Kies registers that fact but complains that it cannot be in that mode. So I switch the mode off in the phone but now when I plug the phone in it does not even get recognized. Nothing, not even trying to install driver or a new USB device found.
What am I doing wrong?
Net 4 is installed and so are the Sammy usb drivers.
What's the point of Kies?
Hi,
I have HTC Tilt 2 and I have contacts with photos on that. Also all the photos are in sync with outlook. When I used Kies to sync my contacts it did not bring any photo? What should I do? I have more than 300 contacts..
Samsung, this is pathetic!
Wasted 2 hours of my life dealing with your stupidity.
heres the solution (problem was launcher pro):
1. grab the homeswitcher from market
2. set touchwiz crap as default.
3. reboot phone.
from then on, kies acts normally, phone gets detected normally etc etc etc.
thanks for wasting my time samsung.
edit: even after this i had probs, seems i need to reboot phone everytime i need to connect it. on first connect after fresh reboot it seems to work. goodluck. (very very very poor software as expected from samsung)
edit2: this is a bug fest! who coded this samsung? some student? jesus this soft is so bad it kills all the experience. what a piece of junk. barely works. flaky. buggy. samsung, fire your software team asap. they suck. only a true amateur can output this kind of garbage. this is below badly coded visualbasic garbage.
Seems to me you need to take your unhappy self and learn how to code. Then apply for a Job at Samsung claiming you can put their programmers to shame. IF you aren't gonna do anything about it, other than complain, you need to just STFU or get another phone.
kodea said:
Samsung, this is pathetic!
Wasted 2 hours of my life dealing with your stupidity.
heres the solution (problem was launcher pro):
1. grab the homeswitcher from market
2. set touchwiz crap as default.
3. reboot phone.
from then on, kies acts normally, phone gets detected normally etc etc etc.
thanks for wasting my time samsung.
edit: even after this i had probs, seems i need to reboot phone everytime i need to connect it. on first connect after fresh reboot it seems to work. goodluck. (very very very poor software as expected from samsung)
edit2: this is a bug fest! who coded this samsung? some student? jesus this soft is so bad it kills all the experience. what a piece of junk. barely works. flaky. buggy. samsung, fire your software team asap. they suck. only a true amateur can output this kind of garbage. this is below badly coded visualbasic garbage.
Click to expand...
Click to collapse

Having trouble updating to Froyo (official) with a 64-bit OS? Try this...

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.

[Q] Problem with communication during GB update

Alrighty,
So I keep trying to update my g2x through LG but I continuously get an error message that says, "Problem with communication between cell phone and PC", and then it never goes past 4%. Yes, I've downloaded the proper drivers, and have followed the prompts of disconnecting the phone, removing the battery, powering back and pressing restart (countless times). None of it works though. And no, my phone isn't bricking up on the SW update, so that thread doesn't really help me.
I've been doing some research and it seems that it just doesn't work for some phones, but I'm wondering if anyone here has been able to successfully troubleshoot this.
Yeah, I'm one of the unfortunate ones that got a bad phone a while ago, so I'm hoping I can find a way to make it work...
Thanks in advance!!
I have had the same problem. I have a G2x that I got off ebay. It was un-moded, running stock Froyo 2.2.2. I went to the T-Mobile / LG update site and followed the steps. The program actually worked the first time, it went through the whole update procedure and said it was complete. The phone restarted, but when it restarted it no longer recognizes the SIM card and there is a question mark for the battery symbol. When I go into the settings, it does not show a baseband version. I have tried to re-install using the update program, but it stops after 36% saying "Problem with communication between cell phone and PC". Any ideas?
npo123 said:
Alrighty,
So I keep trying to update my g2x through LG but I continuously get an error message that says, "Problem with communication between cell phone and PC", and then it never goes past 4%. Yes, I've downloaded the proper drivers, and have followed the prompts of disconnecting the phone, removing the battery, powering back and pressing restart (countless times). None of it works though. And no, my phone isn't bricking up on the SW update, so that thread doesn't really help me.
I've been doing some research and it seems that it just doesn't work for some phones, but I'm wondering if anyone here has been able to successfully troubleshoot this.
Yeah, I'm one of the unfortunate ones that got a bad phone a while ago, so I'm hoping I can find a way to make it work...
Thanks in advance!!
Click to expand...
Click to collapse
Mine did this the first time. This is where the phone is never commanded to boot into S/W update mode so at least this is not a step where it can be bricked, as no update has actually occurred yet.
This is how I fixed it and got mine to update. Use a different USB port on your computer. Yes there are different as some are on internal hubs. The update must have a direct USB port with no hubs in between. I also reinstalled the drivers through the LG Update program and not from the LG website. When I did this and plugged in my phone about eight new devices were detected and installed as opposed to about two the first time around. Also, make sure your phone is in debug mode in Android application settings.
Then make sure you disable any anti-virus programs and turn off the Windows firewall. Then use ctrl-alt-delete and close down any programs running. Also go to the taskbar and click on the up arror (if Windows 7) and right click on each icon and see if you can close it down. Also, unplug all other USB devices (even a mouse if you don't need it) as they can interfere with communications between the updater program and your phone. The only USB device I left connected to my computer was the keyboard.
The LG Updater must be run in Admin mode. If when you run it you get a Windows warning asking you if it is ok for this program to make changes to your computer then it is launching in Admin mode. If not right click the LG Updater icon by clicking Start>All Program>LGMobile Support Tool>LGMobile update. Right click the last item and run it in admin mode. Again this is assuming you are running Windows 7. Admin mode is not necessary for Windows XP.
If all the drivers get loaded properly and you are not on a flakey USB port then at 4% the updater instructs the phone to reboot into S/W Update mode and that is where the real magic happens if you are lucky.
coreycollins3066 said:
I have had the same problem. I have a G2x that I got off ebay. It was un-moded, running stock Froyo 2.2.2. I went to the T-Mobile / LG update site and followed the steps. The program actually worked the first time, it went through the whole update procedure and said it was complete. The phone restarted, but when it restarted it no longer recognizes the SIM card and there is a question mark for the battery symbol. When I go into the settings, it does not show a baseband version. I have tried to re-install using the update program, but it stops after 36% saying "Problem with communication between cell phone and PC". Any ideas?
Click to expand...
Click to collapse
Use another USB port and try again. At various points in the update the updater resets the phones usb port and it has to reconnect. If it doesn't connect don't do a battery pull. Just try removing the USB cable and reinserting it. If you hear the computer beep wait a bit and then click restart on the updater. Hopefully it should see the device this time and continue the update.

[Q] Bricked worse than I thought? Help! (long)

Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,
JaimeZX said:
Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,
Click to expand...
Click to collapse
Interesting problem. I have bricked my phone a bunch of times and have always been able to get back to at least "download Mode". The method I use to go to "Download Mode" is With the usb cable plugged into the computer only, power off the phone. If phone wont power off, or stay powered off, pull battery, then put battery back in. Now hold vol down and vol up buttons only, keep holding these buttons as you plug the usb cable into the phone. In 3 seconds the download screen should appear. I hope this helps you get your phone back.
JaimeZX said:
Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,
Click to expand...
Click to collapse
This sounds like a time where a jig would be helpful. Any chance you can have your wife order one, and send to you? http://www.youtube.com/watch?v=D7I4dFX_iJ4
This should put you straight into download mode, and you can then flash.
Thanks, guys. I continued fiddling and got the phone into DL mode.
I also noted that when plugging and unplugging the phone, it would show up in zadig as "unknown device."
I tried to load the drivers on that, but (a) it still shows up as "unknown device" and (b) when I run HOC it doesn't see the phone under the list of compatible devices.
So.... still kind of stuck.
Any more ideas?
Oop. duplicate post
It's been awhile since I've played with the one clicks, but, "serial gadget" is what I remember seeing when I used them.
Right. MORE messing around later and "Serial Gadget" is it.
That said, I still think I have a driver issue. I have tried uninstalling and reinstalling the zadig-recommended drivers for Serial Gadget several times. I also tried manually installing the drivers from Super One Click.
Anyway, now when I load up HOC I get the green <<connected>> at bottom; but then sometimes it wants me to install the drivers (again) and sometimes it gets past that part, but then goes to
Flashing Kernel: 0%
...hangs there for about 10 seconds and then
Failed!
So... driver thing you think?
Thanks again,
If you reboot the phone after the 0% hanging for 10 seconds, does it go to the yellow exclamation mark screen? If so, just reflash again and you should be back to working... both my and my wife's phone always did that when I had to flash a kernel.
That's just another download screen that theraze is describing.
Exacatly. But the alternate download screen always came up after restarting the phone after a 'failed' flash where it stayed at 0% where it was successfully communicating through the cable. That just meant to not break the drivers or unplug anything... just reboot fast and finish up quickly.
Okay - I can definitely try that! It had not occurred to me to try and reboot the phone right then.
Question, though - when I get the "Failed!" Then HOC essentially hangs, when it says something along the lines of "ending session..." and never progresses from there. So how do you "restart quickly?" Because I have to like, close and reopen HOC. I guess I will see if it succeeds at ending the session when I reboot.
I will try it again. Strange though, sometimes HOC accepts the existing driver (I managed to DL the Samsung driver installer) and sometimes it wants to reinstall "WinUSB." does that make sense? Is the WinUSB an acceptable one?
The winusb is the right driver for heimdall, it doesn't like the Samsung driver.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Samsung drivers and the one click drivers clash. Yes, uninstall Samsung completely if you want to use the one click.
Hm. Thanks for that - might be part of the problem.
Dunno what I did differently, if anything, but last night I tried flashing again and this time it went through! I was very glad to see the whole HOC process completed successfully!
So anyway - thanks so much for the help, guys.

[Q] Non-powering up infuse

Hi,
I have a Samsung Infuse and yesterday when I left it to charge everything was fine, but after I took it out, nothing was working. I mean nothing at all, no Samsung logo, No download mode, no recovery mode, nothing. The LCD or the phone won't start up. I did the basic troubleshooting and the battery and all are fine. I showed it to a mobile hardware repair shop and they said that the hardware is fine and it's a software problem.
Now, since the phone won't even start up, I cannot connect it to windows and hence can't use Odin as well (phone doesn't even go to download mode).
Moreover, I am unable to install the driver on windows since Kies requires the phone to be connected and detected by windows and that isn't happening.
Any suggestions on what could be the problem and how I can fix it ?
Thanks

Categories

Resources