• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Kies Mini doesnt detect captivate

I would think that you need to be on 2.1 to get 2.2. Also try some of the following.

-Uninstall/Reinstall Samsung drivers.
-Uninstall Kies mini and delete all traces of it (Folders, registry entries).
-Reinstall Kies mini
-Try another a USB port, preferably one in the back of your computer. Make sure Kies mini is running first before you connect your phone.

That's basically what I had to do to get Kies mini to recognize my phone. I hope you get it figured out.
 
OK. So Samsung L-III support sez that I must use the USB cable that came with the phone and not a third party cable. I will have to give that a try tonight as I do not have that cable with me at work. I was attempting to use a similar USB cable from by BB Torch. That cable charges my Captivate and allows me to connect to it in mass storage mode just fine, so I am not sure why it would work for an update...
 
I have tried Odin and everything. I got the leaked Froyo back in October and my phone refuses to flash back to 2.1. It'll say that it worked and be all completely reset, but checking the Firmware shows I still have 2.2 and with the leaked 2.2 also came Flash 10 and a Nook, which are also always still on my phone. I'm at a loss. Everyone else is talking about how easy it is flash back and I do everything exactly how the forums say, yet I'm still stuck with the leaked. It sucks because now I can't update my phone to the actual new official release of 2.2. Help? Thanks!

~Melanie~
 
I was having the same problem, Kies Mini was not detecting the phone. What I did to get it to work is I removed the SD memory card I had in the phone (so that its not constantly media scanning) then I went to Settings, and I forgot exactly where but you have to turn on USB debugging, after I did that it worked.
 
Djluminus89: I also had already tried all of that ages ago. I haven't put my SD card in since the first time I tried removing the fake 2.2 a couple of months ago. I have had it in both Debugging and not Debugging mode on more than a few occasions. I've kept it on Debugging mode lately though and every so often try it again. Still no results. I'm hoping my phone isn't defective and somehow I permanently engraved the fake 2.2 on it and from the hundreds, maybe even thousands of reviews and questions and comments other people have posted on their problems similar to mine and such, I still can't get mine fixed. (long run-on sentence I know) Thanks for your help though!
 
You must log in or register to reply here.
Back
Top Bottom