Related
Hey guys. I have had my Captivate since the beginning of September. I downloaded Samsung KIES and was able to download the update back in Sept. I have checked periodicially for any updates, was able to sync contacts, and all that. Yesterday, I went to check for an update, and there was one available. After downloading the update, KIES could no longer recognize my phone. I shut down my computer and the phone. When I reconnected, KIES told me that the "device was not supported." I have redownloaded it several times, but to no avail. I am trying it again, using advice I found on another forum service, hoping it will work. However, has anyone else had this issue, or is this an issue that seems to be plaguing the new update? I thought I was downloading a new firmware update for the phone, however, It may have been a KIES update...
What update did you install on your phone? Post your firmware, baseband, and kernel versions, along with the build number.
Also, this probably doesn't belong in the development section. You should post this in the general board.
[Update] I downloaded KIES again (the newest version) and it still says my device is not supported. My computer recognizes the phone, just not KIES...Is it still possible to download an older version of KIES, because the issue seems to be the version of KIES, and not my phone...?
kegobeer said:
What update did you install on your phone? Post your firmware, baseband, and kernel versions, along with the build number.
Also, this probably doesn't belong in the development section. You should post this in the general board.
Click to expand...
Click to collapse
This info would really help...
I didn't actually update my phone. KIES was downloading the update, and once the update was downloaded, my phone was not recognizable. I will move the forum to the general discussion and post the info there... Thanks!
Sent from my SAMSUNG-SGH-I897 using XDA App
i have the same problem on my i897. i m running latest cognition rom on mine that could be the issue?
I have the same issue with Kies. I downloaded an update for Kies and now Kies no longer sees my Captivate. My computer sees the Captivate no problem. I have been looking for an older version of Kies to go back to.
Kies update issue
I had the same problem once my version of Kies updated last week. I tired everything, cleared user setting and cache, formated the INT SD card.
Did a ODIN one click restore to the original firmware and tried the above steps again... Nothing...
I had to uninstall the full version of Kies and go back to the MINI version of Kies, then all was fine...
I'm suspecting that they updated the full version of Kies to exclude certain versions of the Galaxy S (Captivate in my case)...
I had the same thing happen after I let Kies update, tried everything I could think of, it would not link to the phone. I uninstalled the new version and reinstalled the older version I first had, all is good again. I suspect it was a deliberate move, as Samsung now says the Captivate can only be updated with Kies mini.
Sent from my SAMSUNG-SGH-I897 using XDA App
jth747 said:
I suspect it was a deliberate move, as Samsung now says the Captivate can only be updated with Kies mini.
Click to expand...
Click to collapse
I concur, since AT&T has removed all native tethering and WiFi AP ability from the captivate, I think they pushed Samsung to remove captivate support from Kies. I don't have time to look around, but perhaps Kies has a config file that can be updated/changed to re-add captivate support.
Same here. I just updated Kies to 1.5.3.10103_100 just now before doing research on the adverse affects (Who'da thunk it that I would need to). Turns out that after Kies installed the update, it can no longer recognize my Samsung Captivate. I am running Cognition 2.1.6 ROM but that shouldnt matter. Just last week I was able to connect to Kies and back up my calendars and messages. Now....I am getting the "connecting the device..." message. That message has been up for the past 40 minutes. I have not reflashed my phone for at least 2 weeks now.
Seems like the Kies update to 1.5.3.10103_100 did something bad.
Same Problem
Its the Kies new version bug !
need a solution
I went back to the older version kies (1.5.3.10075_17)
and it works very well now .. i think new version kies have some bug or problem
djdk80 said:
I went back to the older version kies (1.5.3.10075_17)
and it works very well now .. i think new version kies have some bug or problem
Click to expand...
Click to collapse
Have you read this thread? It's not looking like a bug - more like Samsung doesn't want the full Kies to work with US Captivates. Kies mini still works, and that's what Samsung wants people to use.
In case anyone is looking for an older version of kies, I found one at turbobit.net/i8v2c4oixldz.html
Thread moved to Q&A.
chernomorez said:
Have you read this thread? It's not looking like a bug - more like Samsung doesn't want the full Kies to work with US Captivates. Kies mini still works, and that's what Samsung wants people to use.
actually mind is samsung vibrant , anyhow still same problem
Click to expand...
Click to collapse
Remember you have to be in TWLauncher for Kies to work.
Also if you search for Kies you will find many prior versions.
I happened to have 1.5.3.10093_82 and reverted from the update.
Everything works fine.
I installed a previous version of Kies and it works just fine. If anyone needs a older version you can find it at samfirmware.com
They list all the versions that Samsung has made under the Samsung Kies link
encountered same issue.
here's another alternative link to older version 1.5.3.10092_2_1 that seems to work.
http;//org.downloadcenter.samsung.com/downloadfile/ContentsFile.aspx?CDSite=DE&CttFileID=3203268&CDCttType=SW&ModelType=N&ModelName=GT-S5250&VPath=SW/201009/20100914110209343/Kies_1.5.3.10092_2_1.exe
Hi all,
I've purchased a samsung captivate from United States and bring it to italy where I'm using with Wind operator.
I'm starting thinking that it was the worst purchase that i've never made.
First of all, I've unlocked at&t sim restriction and it was the only think went fine.
In italy I had time to test the phone and I've noticed the full unworking gps feature: position was never catched and just 1 or 2 satellites was found with low signal.
I'm trying to use samsung kies to upgrade the firmware before install a custom rom but samsung kies doesn't found the phone! (on win 7 or xp the fault is the same.. Mtp driver not installed correctly or kies says that phone is not supported!)
Moreover, updates by OTA don't work because the updated tool fails to connect to at&t server!
I'm really sick for all of that.. The last think I can do is to root the phone and install a custom ROM but I'm afraid that gps still doesn't work.
What do you think about this?
You don't need to update to install a custom rom. So I wouldn't stress too much about it. Make sure you back up the folder which contains the unlock information!! I made that mistake.
Many roms out there try to fix gps issues. For now, many of us (including me) have awful gps capabilities.
Edit, I should say that many roms vastly improve the GPS, so after you've read up on flashing and want to give it a try, it's probably your best bet.
Sent from Captivate, sorry for the brevity.
I don't know if your experience with the original firmware is the same that i have but my gps is not working at all. I can't understand how they can sell a phone with this buggy behaviour.
However, if it does not work also with the new firmware may I flash back original firmware for at&t / samsung assistance? I don't think so but maybe you are more informed than me.
Have you tried installing the gpsjm9 files with clockwork? Makes even stock gps better.
Sent from a phone somewhere in the universe
cappysw10 said:
Have you tried installing the gpsjm9 files with clockwork? Makes even stock gps better.
Sent from a phone somewhere in the universe
Click to expand...
Click to collapse
i see its from/for an i9000. will it be fine with the captivate?
chasesavestheday said:
i see its from/for an i9000. will it be fine with the captivate?
Click to expand...
Click to collapse
yes...and you can flash from stock to a custom.
you can flash back to stock via odin 1-click.
my best gps performance (build 1007)
have been with
Doc's, Chronus, and Assonance.
From what I have gathered... this seems to be a problem that only I have encountered, or at the very least something that I have deemed annoying enough that now I have to solve it... but I recently threw Gingerbread onto my i9000, quite successfully I might add, but I decided I wanted to go back to Froyo until the official release of 2.3 comes out of Samsung, since I am a big fan of "stock".
Problem is, every single ROM (I am at ten and counting) always results in Kies telling me that there is no update available. I have been loading only stock ROMs onto my device, so I am a little confused by this, since even the 2.1 firmwares have given me the same message. I know that, when I had Froyo loaded on stock, the message read that everything was up to date or something along those lines. Having that knowledge just means I won't be able to stop trying to put things back to stock until I see that same message again.
Anyone able to shed some light on what is happening here and how to fix it? Ideally I would love to load up 2.1 Eclair, update to Froyo using Kies and then just call it a day.
(PS. on Gingerbread I am getting some weird "static" screen popping up every time I restart... is that normal? I will take a picture and post it into the Gingerbread review forum if I can capture it.)
i was in a similar boat as you, loading 2.3 was no problem but going back is a pain in the ass.
BE WARNED! I spent nearly a day and i know a fair amount about what im doing, i even had to make the USB jig to force download mode at one point (testing different ideas) so be prepared for some issues.
what i did was use odin to flash stock JL2 (9000M bell version here), with 512 pit and a CSC file from another build (sorry i forget), bootloader update repartition clear efs checked. Thats the ONLY thing i could find to get me back to stock without any internal SD error messages.
IF YOU FLASH THE WRONG THING OR THE FLASHING PROCESS SCREWS UP YOU CAN BRICK YOUR PHONE. Read twice, do once.
See if you can find a stock rom for your area, what your phone came with, with the proper pit file and csc file.
Best of luck, you are not alone. I will definately be waiting for a less buggy leak before i switch back to gingerbread.
Kies reads and looks for the correct software for your product code and firmware tied to the supplying network .Once you install different roms you may change those details and Kies cannot find the correct details on your phone to recognise and match it to a firmware .
Spoof product keys and Kies registry patcher posts may help .
jje
Thanks for the quick answers guys... I shall plug-and-chug a bit more tonight and see if I cannot get something to work... then I will be back to post of my success (or failure).
You can use SpoofFw to trick Kies think you are on an official fw, the let Kies do the stock upgrade for you.
Having quite a bit of trouble getting Busybox installed properly, apparently... SpoofFW always starts up with "BusyBox not found. Spoof not possible." I have installed BusyBox a couple of different times from different sources and different versions... nothing seems to work. Am I missing something?
Also, when loading certain ROMs... the phone doesn't seem to register the modem anymore. There is a 2.2 ROM (forgot which) and the 2.3.3 ROM (without Bootloader) which, unusually enough, are the only ones WITH a working modem. Just tried loading up the 2.3.3 ROM w/Bootloader but the modem file from the non-bootloader version, and that seems to work... weirdly enough.
Since I am betting that there will be a "official" update through Kies to 2.3.x at some point, perhaps I will stick with this... since I am using an official ROM, will Kies recognize my phone properly and offer me an update, or has my product code become screwed up?
Wirebrook. I already replied to one of these today. Same happened to me. flashed back to jpu with a view to using kies to upgrade me to jpy but it wouldn't. So flashed eclair jm1 and kies upgraded me to jpy so I suggest that. You'll have to flash bootloader afterwards though as you'll lose 3 button reboot. But don't panic
Sent from my GTI9000 using XDA App, gingerbread 2.2.3 rooted, ADW launcher + gingerbread theme
I am using an official ROM, will Kies recognize my phone properly and offer me an update, or has my product code become screwed up?
Its not an official rom its a Samsung stock rom not the rom that was supplied with your phone . Kies might update it or might not .
You have firmware provided by the original phone seller and product codes hardware id firmware id for that . Kies will see that and update .
But its going to show not the firmware supplied by the original phone seller and tied to product code etc . Then requires you to Spoof Kies for an update .
jje
@Mossy1963
I'll give it a shot this evening... I have the JM1 firmware glaring at me in the face on my desktop right now, though... not sure that worked right the first time.
@JJEgan
As long as it is all "stock" I am pretty much fine with it at the moment. Not too bothered with having it tied to it's specific product code so much, although that would be nice.
wirebook said:
Having quite a bit of trouble getting Busybox installed properly, apparently... SpoofFW always starts up with "BusyBox not found. Spoof not possible." I have installed BusyBox a couple of different times from different sources and different versions... nothing seems to work. Am I missing something?
Also, when loading certain ROMs... the phone doesn't seem to register the modem anymore. There is a 2.2 ROM (forgot which) and the 2.3.3 ROM (without Bootloader) which, unusually enough, are the only ones WITH a working modem. Just tried loading up the 2.3.3 ROM w/Bootloader but the modem file from the non-bootloader version, and that seems to work... weirdly enough.
Since I am betting that there will be a "official" update through Kies to 2.3.x at some point, perhaps I will stick with this... since I am using an official ROM, will Kies recognize my phone properly and offer me an update, or has mys product code become screwed up?
Click to expand...
Click to collapse
That error message its actually wrong, you get it because nv_data.bin could not be found in /efs folder.
This could be due to a faulty flash where Csc was not applied correctly in recovery on the first boot.
Reflash with Odin is the solution.
Sent from my GT-I9000 using XDA Premium App
@Mossy1963
No cigar whatsoever... Kies simply stated there was no update to be done. Oh well.
@LuffarJoh
Tried reflashing... didn't work either.
Aaaaand to make things weird, that sometimes-working Antenna suddenly started working with an Eclair ROM that it hadn't worked before. Then after a reboot... nothing anymore. And now I have flashed the thing back to Gingerbread and what do you know... no more antenna. I would much rather have a working phone as opposed to a "perfect-stock" phone, so it looks like I might have to get an exchange... and perhaps acquire what I was after in the first place at the beginning of this thread anyways.
Hi, I was wondering exactly the same thing after flashing 2.3.3 today. I just like the idea of being able to plug the phone into kies to get a proper release although, I've no doubt the exact same version will be available for download. Has anyone got any useful info ?
so i flashed back to stock to see if it would work.. i dont know curiosity killed the cat right. anyway i then checked to see if mini kies would work and upgrade to 2.2 again just to see if it would not like i need it, many custom roms for cappy that are way better than stock 2.2. i was only checking to see.
so like i said it says unregistered device and wont let me upgrade dont know if the 2 are related or not.
anyone have a guess? also there was a mini kies update may have done something to also i checked and my IMEI is still the same number it matches the # on the box it came in.
Which version of GB did you have loaded?
You can always try the regular Kies version as GB is for I9000, see if that registers.
ok so update to anyone interested.
i relfashed back to 2.1 aka jf6. few days later.
tried mini kies again and worked just fine. must have been server connection problem on samsungs part, big suprise there. lol
so now fone is 2.2 samsung stock firmware.
i know it sucks i was only curious to make sure my fone could still odin 1click since my fone 1010 build. i never had problems using one click before so i hoped it would be no problems. never needed to add 3button combo fix my fone always had it, it is a refurb and always have had good refurbs, i think they need to be judged at a higher passing than brand new anyway, i digress.
after flashing and reflashing many GB roms, flashing back to stock jf6, absolutley no flaws or errors in fone can still use mini kies if want to, fone is as stock as the day i got it. so GB flash your asses off, just be smart and dont forget your steps. have fun and read reread your GB install steps very carefully.
I know this was resolved, but I had a similar issue and it never corrected itself. I found the problem to be that my product code was changed by one of the roms I had previously installed. I followed the instructions in the link below and it allowed me to set my product code to what it was from the factory. I can now update through Kies Mini without getting the "unregistered device" error.
http://forum.xda-developers.com/showthread.php?t=880223
Hi guys, I know I need to make this short but I want it to be clear anyway. This is crazy I wanted nothing to do with smartphones 3-4 days ago because all the carriers rip us off with huge bills to get them. But low and behold when my cheap flip phone died after 3 years of loyal daily work a friend of mine offered me his Galaxy S i9000m for a good price. Started playing with the device and having a strong software/computer background started having a lot of fun with all the applications and was amazed with the possibilities (Networking, ipcam whatever) that just kept multiplying until I fell upon applications that needed something called gingerbread... Anyways I can tell you I learned a ****load in 48hours...
So I installed Samsung Kies, it found me the update and put it on for me.. (2.3.3 Gingerbread) then the nightmare started. The phone would boot, and would randomly reboot a random number of times until it could finally stay on and this could last from 2-30 minutes. So I thought, I'll just do a factory reset, to realise that its "STUCK" in 2.3.3 once its updated no going back to 2.1 or 2.2 easily.
Started looking around for ways to downgrade, and EVERY SINGLE LINK redirects to these 'mass download' sites that end up saying the firmwares were taken down for copyright issues. So desperate to find something, I fell upon a multiple CSC FROYO 2.2 firmware for the i9000 and was able to flash that in download mode the phone worked fine, except for me being very curious about the fact that I lost the "M" in my model description...
So started reading this thread(Mostly because I had already realised that with this non i9000m rom I had lost the 3 button DOWNLOAD MODE which i Had before) **** : http://androidforums.com/galaxy-s-a...flashing-darky-v9-gt-i9000m-minimal-risk.html
Got it rooted, got clockwork on, never managed to get the voodoo kernel working had errors in CWM.. so I was ready to give up until my eyes caught the
"*#*#2663#*#*
Then click Touch key FW update"
Which I thought would be neat to try.
NIGHTMARE, now BACK and MENU are dead, I understand that this is because I am running a non i9000m ROM and that updating the firmware rendered them unusable.
I came accross a post : http://forum.xda-developers.com/showthread.php?t=869492
Where this problem is adressed, I pretty much understand everything that should be done to get this back on its feet (right now the phone is still working I can use it at least 75% of its functions work except no back and menu)
Where I need your help : I'm not too sure how to attack this the right way, since I can't get into download mode I understand flashing is now more complicated to accomplish and now that I know that I need a i9000m firmware how can I find that...
Sorry for the long post I know I'm a noob here but I wanted to prove I had done all my homework to get where I'm at now seeking help from you guys!
Thanks a lot
Mat
By the way : Galaxy S GT i9000m currently on a 2.2 i9000 rom, my carrier is BELL. (Canada)
So there's no way of updating to 2.3.3 using Kies?
The only thing I can think of is getting a USB jig from ebay, which makes the i9000 go to download mode instantly. Good luck!
Alright, so I used CHECK FUS, and was able to get the i9000m stock BELL firmware YAY
now the help I need is to flash it correctly and find a way to get past the no download mode problem, would be very appreciated,
thanks guys
No, similar minds Sepharite, I also thought of redoing the Kies method, and then going back again if I needed to but now Samsung Kies says "Your device does not support firmware updates through Kies" Wow.. useful app, a samsung native app can't even detect it's own fricking hardware.
Thanks
UPdate : Was able to restore the 3 button "DOWNLOAD MODE" with a little tutorial online. Now I tried flashing my i9000m with ODIN, it flashed all the way and I get a i9000M logo now but it gets to the splash S logo and keeps rebooting never gets into the actual android setup is there something I did wrong?
In Odin all I put was the "BELL i19000m stock ROM" under PDA and wrote it. The device rebooted after flash but there still seems to be something I haven't done right.
Thanks guys
Please help guys, I know some of you out there have got this stuff nailed down!
Did you flash with a 1 file ROM or a 3 file ROM?
Using the UGKG3 ROM that you can fine here:
http://forum.xda-developers.com/showthread.php?t=1102881
Place the 3 files in their respective places (PDA, PHONE, CSC), for the PIT file, select the 512 pit file that should have come with ODIN, connect the phone, wait for ID:COM to turn yellow, and press Start.
That should get you going again. You may get apps that force close, so you'll need to delete the apps data and then reinstall them.
Hey thanks a lot man ya my flash was a SINGLE FILE, I bricked it yesterday trying to flash a different ROM since I had nothing to lose, I just got it working again on the old 9000 ****ty version that my back and menu keys don't work...
Now for some reason the USB JIG doesn'T work anymore after a couple of uses... could something have been damaged by doing it many times?
And your original roms section they are all unavailable due to copyright did you check the links before sending them?
When you say get the stock roms, I was able to get the UGKG3 file, but what about the versions? When I look at the north american section of the 2.2 version
UGKC1/UGKC1/BMCKC1/Sbl
UGJL2/UGJL2/BMCJL2/Sbl
UGJK3/UGJK3/BMCJK3
which one of the three suits me?
Thanks for your help, and if I get this running and go back and update my touch key firmwares with the right "Vibrant / 9000M" roms I should get them working again?
PS : I'm also very preoccupied by the fact that the USB JIG fix doesn'T seem to pop download mode anymore because this version of the ROM that I have has Download mode not working with the 3 button method. :S I wonder whats going on, but basically if I get your ROMS working the first time It'll fix everything but if it crashes then I lose the galaxy haha
Not sure why the USB jig doesn't work anymore. I have a couple and have only tested them on my phone to make sure they work, but they did not work on a Galaxy S II that I tried it on.
I just checked and the download link for the UGKG3 ROM at multiupload (downloading from multiupload), still works (you need to enter the captcha phrase).
The site megaupload was shut down by the US gov't, so that one won't work.
EDIT: UGKC1/UGKC1/BMCKC1/Sbl is the latest Froyo release from Bell. That's what mine and my wife's gt-i9000m phones came with.
She's still running it on hers.
Ok sorry for all these posts, basically when you said UGKG3 you want me to get the 2.3.3 ROM on ? Is that right? What if I Want to put on 2.2 to be sure I have no trouble with it since I'm in all this mess because the Kies update to Gingerbread had my phone in a bad state.
Thanks a lot by the way!
Sorry your post refreshed right after I did mine. Alright cool so I'll try the one you say your wife is running, I had made myself a JIG with a stock Samsung wire, it was working fine with a 300K resistor and I decided to solder it on and then it stopped working after that.... maybe the actual "usb plug" is damaged from the soldering heat I guess I'd have to try another wire, but anyway I'll try to download the 2.2 I just got the UGKG3 3 FILE rom downloaded one of the links did work!
But I'm a little worried about 2.3.3
I'll try to see if i can download the 2.2 first.
I mean basically... these roms shouldn't jam during transfer i Guess
One other thing I see different confusing information, is it important for me to click 'update bootloader" with these stock roms since these files contain an 'SBL' ? Because both times I bricked it was with an "update bootloader checked" firmware update trying to put the ARIES 3 button method fix as a boot.bin and sbl.bin
Fanks..
Files with SBL in the name already have the bootloader included in the PDA file, so "update bootloader" should NOT be checked.
That reassures me, because the only times it did jammed was when the bootloader was checked! THanks a lot blackrose i'll go out and buy another usb cable because I destroyed mine making my JIG. And I'll try yours out. I was reading a lot on another thread and found this one guy who flashed the JL2 one to save his keys instead of the C1 you said your wife was running, whats the main difference between those two and which one should I start with?
Update : I got a new wire, flashed the KC1 version of the firmware, everything goes fine, I did a repartition with the 512 PIT, it reboots the phone, loads all files in a prompt in yellow and there are no errors that appear, the phone reboots after writing 'successful update' and then goes to the galaxy logo and jams there and does the ONE vibrate, PAUSE, 2 vibrate on a black screen forever. The advantage of having successfully flashed a 9000M ROM allows me to have access to my DOWNLOAD MODE 3 button method, but ever since I flashed that 2.2 i9000 XXJP2 (seems its a euro version) off a torrent I found on the web (When I was desperate to find a functioning 2.2 working version) it seems as though it doesn'T want to boot with any other rom than that one, because all the 9000M roms that I've tried so far flash correctly, and the logo actually changed from i9000 to i9000M on the startup, but they just don't boot.. what could be missing it doesn't seem to be much???
Thanks Mat
If any of this can help, the device was rooted, I was following the darky's mod i9000M guide so I had previously installed the CLOCKWORK MOD and that's as far as I got because my eyes caught the FIRMWARE TOUCH KEY UPDATE which ruined my keys.
Could any of this have screwed something that stops my other roms from booting?
Thanks guys I really want to get this phone up and working again as I don't have much money and am afraid I'll have to cancel with my phone company if I just can'T get this running. I am also willing to make a significant donation to whoever can help me.
You in Canada right? Where abouts?
Sent from my GT-I9000 using xda premium
Quebec province
Alright, if this can help anybody my whole problme is solved.
I flashed the ****JL2**** the KC1 did not boot, the JL2 did.
Once inside JL2, I was able to update my TOUCH KEY FIRMWARE *#*#2663#*#* and everything went back to normal
I have no idea why the KC1 does not work, bugs me out.