[Q] CSC Query Since Debranding Phone - Galaxy S II Q&A, Help & Troubleshooting

Seeing as I`m still a relatively noobish poster I`m unable to ask this question in the relevant thread. I`ve just debranded the phone following the 8 step guide but I had issues following step 8 where you change the CSC code. I couldnt quite figure it out so step 8 never got followed. As a result, despite losing the Three branding on the phone I now have a phone that displays the CSC as "unknown" and may well explain why Kies cannot pick up the firmware version on the phone. If I follow step 8 and key in *#272*<your IMEI># on my phone it then shows me a screen headed "Preconfig" with "Sales Code" underneath and "H3G" in the box to the right. Underneath is a radio button thats deselected. if I press to highlight it then press "install" at the bottom of the screen I keep getting an error saying "Must be THREE chars".
Can anyone shed any light on this and give me any hope of rectifying?
Will I need to manually input the Three APN settings once I successfuly change the CSC code?
Thanks in advance. I have spent ages scouring the web but there`s not a great deal of info out there about the CSC part of the debranding process.

id like some more info on how important the csc is too, im got told it hold some carrier information but i dont know if that is true or not.
the reason you cant pick on is probably as since debranding you havent flashed the csc you need, you could find the one you need for your firmware over in the dev section.

Cheers for the reply, interestingly i`ve just re-flashed the phone and this time it is showing my CSC as XEU. Even so, I still cannot follow step 8. When I input that code including my IMEI in it shows XEU but when I press "install" it gives me the same old error of "Must be THREE chars". So not sure whether its worked or not and what diference it makes. At least Kies now shows something in the firmware field, even if it doesnt show what I was expecting. Hopefully someone can assist with this at some point later.

RedAl said:
Cheers for the reply, interestingly i`ve just re-flashed the phone and this time it is showing my CSC as XEU. Even so, I still cannot follow step 8. When I input that code including my IMEI in it shows XEU but when I press "install" it gives me the same old error of "Must be THREE chars". So not sure whether its worked or not and what diference it makes. At least Kies now shows something in the firmware field, even if it doesnt show what I was expecting. Hopefully someone can assist with this at some point later.
Click to expand...
Click to collapse
Hi there
If it says XEU after inputting the imei then it's working fine. You're not supposed to have to press install at this stage. Also to make sure it's working fine, I always boot into recovery mode. If you look down the code as recovery is loading, it will say which csc is being used/implemented (xue etc). Always reset data in recovery after rom flash from (especially from different csc.
I've had issues in the past when I flashed back to T-Mobile (after originally flashing ke7 stock) and then back again to T-Mobile. When I re-flashed back to stock after this, I couldn't get it to change from tmu (t-mobile) csc back to xeu, no matter how I flashed it. In the end the only way I could revert csc back to xeu was using the jig I had purchased. Apart from resetting the customer binery counter, it seemed to reset other settings, as once I had done this, I was able to install stock ke7 with xeu csc.

redbullman said:
Hi there
If it says XEU after inputting the imei then it's working fine. You're not supposed to have to press install at this stage. Also to make sure it's working fine, I always boot into recovery mode. If you look down the code as recovery is loading, it will say which csc is being used/implemented (xue etc). Always reset data in recovery after rom flash from (especially from different csc.
I've had issues in the past when I flashed back to T-Mobile (after originally flashing ke7 stock) and then back again to T-Mobile. When I re-flashed back to stock after this, I couldn't get it to change from tmu (t-mobile) csc back to xeu, no matter how I flashed it. In the end the only way I could revert csc back to xeu was using the jig I had purchased. Apart from resetting the customer binery counter, it seemed to reset other settings, as once I had done this, I was able to install stock ke7 with xeu csc.
Click to expand...
Click to collapse
Cheers for that. I just did a recovery as you suggested and saw it was done using the Multi-CSC so hopefully that means its all sorted.
Does this mean I should now be able to see the latest Firmware update available in Kies?

RedAl said:
Cheers for that. I just did a recovery as you suggested and saw it was done using the Multi-CSC so hopefully that means its all sorted.
Does this mean I should now be able to see the latest Firmware update available in Kies?
Click to expand...
Click to collapse
Yes you should be able to see the latest available update for your csc via kies. Although kies seems much slower to get the updates. It's much easier to use Odin. Most people update by this method. It's really easy and pretty safe.

redbullman said:
Yes you should be able to see the latest available update for your csc via kies. Although kies seems much slower to get the updates. It's much easier to use Odin. Most people update by this method. It's really easy and pretty safe.
Click to expand...
Click to collapse
The csc will be sorted now. Also if you plug your phone into kies, this will confirm what csc you are using.

redbullman said:
The csc will be sorted now. Also if you plug your phone into kies, this will confirm what csc you are using.
Click to expand...
Click to collapse
Cheers Redbullman. I can get into Kies now but on the firmware information section it says "Current Firmware Version : PDA:KDD / PHONE:KDH / CSC:KD1 (H3G)"
Its not telling me there`s a firmware update available so I have a horrible feeling something`s still not quite right but I`ve flashed it twice now and done 2 factory resets.
Would it be easier to find the stock KE7 kernel (forgive me if I`m using the wrong words) in Odin to flash it that way? If I can manually do it then I`d rather do it that way. Only problem is I`ve not yet found any tutorials on doing that, unless its the same (mostly) as the tutorial for debranding, except using a different .tar file (KE7).

Related

[Q] Changing Product Code?

Hey.
I was wondering, How do I change my product code from Spain FOP to UK Three H3G
Kies won't update my device because it's on FOP code on Three firmware Is there any way I can restore H3G or use Kies to do it? Would the Emergency Firmware Recovery work for me?
Thanks/ Jamie.
*shameless bump *
I'm not sure if the product code is the only thing Kies checks -perhaps it checks the IMEI as well like LG does.
As far as I can tell, once you've flashed some firmware via Odin you have no hope of ever getting a firmware update from Kies again.
davew said:
I'm not sure if the product code is the only thing Kies checks -perhaps it checks the IMEI as well like LG doe.
As far as I can tell, once you've flashed some firmware via Odin you have no hope of ever getting a firmware update from Kies again.
Click to expand...
Click to collapse
Thanks for replying
I've NEVER used Odin, and don't plan to :L.
I checked the CSC on my phone through the secret code and it clearly says H3G
So im going to install Kies on another computer and see
Because my product code in Registry is GT-S5830OKAFOP
Thanks anyway
I'm sorry, I'd assumed you'd flashed the spanish firmware yourself.
So your CSC and your Product Code don't match through no fault of your own?
davew said:
I'm sorry, I'd assumed you'd flashed the spanish firmware yourself.
So your CSC and your Product Code don't match through no fault of your own?
Click to expand...
Click to collapse
Partially haha, I flashed CM7 last weekend, Didn't like it, and tried to restore to Stock Firmware backup in CMW, which didn't work because of EXT4 FS, So I had to go to GingerReal, which is clearly where the FOP Product code came from, I then discovered how to revert to RFS, and did so, and back to Stock firmware. I haven't changed anything from then though, But yeah my Product Code is found as FOP but CSC is H3G, which is really confusing! :S can you provide any help haha, Not used to all the CSC, Odin and EFS, last phone was the GT540, Simplest phone ever to change rom on! no need to worry about IMEI etc
*#272*IMEI# - To change the salescodes and reset the user data (by blade2011)
If I do this, do you think it'll work? Quite scared of breaking my Ace, so going to make a backup now
I don't fully understand just yet what Kies checks to determine if your firmware is official or not. Flashing a firmware will change your CSC, but not your product code. I think if your Product Code, IMEI, CSC and firmware version don't agree, Kies will assume your firmware is unofficial.
If your firmware is multi-CSC you can change your CSC code with:-
*#272*???????????????#
where ??????????????? is your 15 digit IMEI
It will perform a hard reset though, you'll lose all your user data. The other big problem with this is working out, given a product code, your CSC should be. You could go through the whole process and still not be able to get updates from Kies.
There's a thread here for the galaxy, but how much of that will work on an Ace I don't really know. I haven't tried any of the stuff in the thread.
http://forum.xda-developers.com/showthread.php?t=787163
HTH
Dave
EDIT: I see you got this far already
Yeah, My CSC, Firmware and IMEI should all Agree, because I've flashed the Three rom back, and I checked on my PC which I used to sync my phone with before CM7, the codes are all the same APART from the Product code I'm trying what I posted and what you posted now
EDIT: My firmware is Stock, so will NOT be Multi-CSC, but because it's the Stock ROM, it should have my original Product Code etc right?
Okay. Tried entering the code, but Im given the screen to select Sales Code, but it's stuck on FOP and I CANNOT do anything with the code, Look at the attachment below
I guess (and this is only a guess) that when you restored your backup, your CSC and Product code didn't get changed back to what they should be.
I had no idea that flashing a ROM could change your product code. I knew it would change the CSC, which is why I've been careful only to flash firmwares that match my product code. Even then, I still can't (and have never been able to) get updates through Kies.
Yeah, I was thinking that somethings messed up here, because my CSC is definitely right, (I hope) but my product code is in Spain.. geez :L
So the executive summary is:-
1. Rooted and installed CWM, took a backup
2. Flashed CM7
3. Flashed GingerReal
4. Your product code and CSC were changed to FOP (spain) at some point along this process
5. You restored your backup, and the CSC changed back to H3G but (and this is the important bit) your Product Code is still reading as FOP
What's weird is when I flashed my Ace with Odin, although the CSC changed, the product code did not. I had no idea flashing a ROM could change your product code - that'd cause a problem if you need a warranty repair and its something people really need to be aware of.
My advice - see if the guy that wrote GingerReal has a clue why this might have happened. There could just be a simple file somewhere that holds the product code which you could get to with Root Explorer or ADB. I'm really just guessing though.
I was in your shoes but from no fault of my own - my new Ace wouldn't update from Kies no matter what, so I flashed S5830XWKPW (OXX/TPH) and haven't really looked back. Uninstalled Kies, forgot about it. I have every confidence that if a new stock firmware comes out, it'll make it out in Odin flashable format for everyone
Yeah, pretty much
I know from the Galaxy S forums that the product code is changeable .. I noticed that the guy who actually develops GingerReal comes from Spain and therefore where FOP has came from .. I think its the bootloader though.. because before flashing GingerReal or CM7 I NEVER had the green triangle in the top left when going into Recovery.. and now I do.. so thats tthe only thing left custom, recovery and possibly bootloader, although the kernel is stock as I remember it having Dell in it,
Swyped from my GT-S5830 using XDA App
I NEED someone on Three UK 2.3.3 KPN Stock to take a screenshot of a Kies registry key for me tomorrow to check if I definitely have H3G CSC, and if not.. how to get it back.. I rang Three and they want to send it to Samsung, which is a bad idea as they will see CMW recovery and charge me probably :/
Swyped from my GT-S5830 using XDA App
Jamielawther said:
Yeah, pretty much
I know from the Galaxy S forums that the product code is changeable .. I noticed that the guy who actually develops GingerReal comes from Spain and therefore where FOP has came from .. I think its the bootloader though.. because before flashing GingerReal or CM7 I NEVER had the green triangle in the top left when going into Recovery.. and now I do.. so thats tthe only thing left custom, recovery and possibly bootloader, although the kernel is stock as I remember it having Dell in it,
Swyped from my GT-S5830 using XDA App
Click to expand...
Click to collapse
The triangle you see at the corner is an indication that you're using CF-ROOT or an equivalent .
Forever living in my Galaxy Ace using XDA App
Yeah I know that, would that be the bootloader im using because CF-Root kernel is not installed, and kernel version shows this,
Swyped from my GT-S5830 using XDA App
You can flash 2.2 with multi CSC (i think that KB7 is right one). When phone boot's up, change CSC with *#272*IMEI...#. Phone will reboot, and after that KIES will report the right values and it will update your phone if there is an update.
You can flash 2.2 with multi CSC (i think that KB7 is right one). When phone boot's up, change CSC with *#272*IMEI...#. Phone will reboot, and after that KIES will report the right values and it will update your phone if there is an update.
Click to expand...
Click to collapse
Do you mean S5830XWKB7/MULTI-CSC-OXXKB6 (9th on the list at samfirmware)?
I tried that and still couldn't get Kies to get updates. When I checked my CSC it was what it should have been (TPH).
Yes that one. Did you change CSC with that FW? I tried and it worked. For example, I changed to XEN and after 2 restarts, KIES was able to recognize phone and offer a update.
And of course, are you sure that there is update in your country?

How to check CSC? Why does Kies say KOR?

I installed CSC_XEU_I9100XEUKH2 after i noticed Kies said my CSC was KI3 (KOR) and not XEU. Kies still says this however.
Under phone settings I can see Baseband and kernel and build. They are all XXKI3.
Why does kies show my csc as KOR? Did the CSC file not install properly?
Look her for your csc code.
codes.docx
Hmmm.. that document doesn't even list KOR. I would have thought it was Korea. TBH I think my phone first showed KOR in Kies after I put nimphetamine kernel on it. I just don't understand why subsequent flashes leave it still saying KOR. I would have thought it would now be back XEU like it was at first.
I am trying to fix a bluetooth car problem (another thread) and don't want to be wasting my time flashing what I think is different software if it isn't flashing properly.
I really understood my HD2 but I'm still climbing a steep learning curve with this phone.
Also in another thread someone posted a screen capture and it was title version. It listed PDA, phone and CSC. I can't seem to find this screen. See 1st post here:
http://forum.xda-developers.com/showthread.php?t=1169338
You can change the CSC code to anything you want.
Just flashed clockwork mod. Now Kies shows CSC KH2 (KOR).
Where did KOR come from and how do you change it? Why does flashing an XEU CSC not return it?
Dexter_Morgan said:
Hmmm.. that document doesn't even list KOR. I would have thought it was Korea. TBH I think my phone first showed KOR in Kies after I put nimphetamine kernel on it. I just don't understand why subsequent flashes leave it still saying KOR. I would have thought it would now be back XEU like it was at first.
I am trying to fix a bluetooth car problem (another thread) and don't want to be wasting my time flashing what I think is different software if it isn't flashing properly.
I really understood my HD2 but I'm still climbing a steep learning curve with this phone.
Also in another thread someone posted a screen capture and it was title version. It listed PDA, phone and CSC. I can't seem to find this screen. See 1st post here:
http://forum.xda-developers.com/showthread.php?t=1169338
Click to expand...
Click to collapse
*#06# gives your IMEI number
*#272*IMEI# gives the CSC Code (!!!!!!!!!!!If you change the CSC code you'll get a factory reset !!!!!!!!!!!!)
*#1234# gives the CSC version
Nitrality from Market does this all for you.
Cheers. that 1234 gave me that version screen. under this csc is listed as xeu.
Can someone explain what flashing clockwork mod changes. is this another csc or does it just modify the one you have to give a new recovery menu. i also seem to still have root after flashing clockwork despite the saying it would be gone.
Dexter_Morgan said:
Cheers. that 1234 gave me that version screen. under this csc is listed as xeu.
Can someone explain what flashing clockwork mod changes. is this another csc or does it just modify the one you have to give a new recovery menu. i also seem to still have root after flashing clockwork despite the saying it would be gone.
Click to expand...
Click to collapse
Guide
http://forum.xda-developers.com/showthread.php?t=1125282
Clockworkmod is a 'custom recovery' made by xda member koush. Every phone had a recovery partition designed so that if the user messes up a ROM installation, they can recover their phone. CWM is a modified recovery installed into the recovery partition that allows advanced control over ROM recovery, installation and much more.
Features of CWM include:
- NANDroid Backup, This allows you to completely back up your existing ROM with all its files, data and apps
- Restore Backup, Restores a previous backup (obviously...)
- ROM installation, Allows you to install a ROM contained inside a flashable .zip file
- Wipe data/Factory reset, completely erases all of your data contacts, apps etc, leaving your phone 'as new'
Amongst others...
How to install CWM​
If you have already rooted your phone using the CF-root Kernel, then you already have CWM! If not, then just install the kernel linked to above in the 'how to root your phone' section
AP: I9505XXUAMDM
CP: I9505XXUAMDM
CSC: I9505OXXAMDB
Can somebody please tell me what my region is? I purchased it through handtec.co.uk sim free unlocked. wondering ever since why it isn't showing BTU
Or is it that this information itself is BTU??

[Q] DO I need to change my CSC

Hi
Ok so I was with o2 on KF3, I've now flashed stock samsung firmware from here http://forum.xda-developers.com/showthread.php?t=1075278
I'm using the most up to date XEU one which is
XWKI4
Firmware info
PDA:XWKI4
PHONE: XXKI1
Date: 14/09/2011
Android 2.3.4
All o2 stuff has disapeared. I've read through the forums on changing the CSC and am confused.
Do I need to change it to XEU now to be able to update through kies? currently it comes up as 02U.
The firmware flash didn't reset my phone everything was as before. Which was nice, however I want the option to get the updates through kies or by flash.
Am i right in thinking I would have to change my CSC for this?
I see views but no replies - anyone no the answer or is it a smarties job?
Tried to change it anyway but phone wont let me dont even get a keyboard. Stuck it on clipboard selected all on 02U then pasted XEU ontop all i got was an error to say it had to be 3 characters any clues?
Sent from my GT-I9100 using Tapatalk
So after some more internet scouring and no help here it appears i need to flash a multi csc fw then change csc then reflash the one i have now......... Can anybody verify if this is correct or not?
Sent from my GT-I9100 using Tapatalk
To use kies again you will have to flash back to the original firmware,in your case carrier firmware,that came with you phone.If your firmware is not official or doesnt match your product code then kies will say that "this firmware cannot be updated" although your phone will still connect.The CSC firmware you have is a mono-csc package.If you try to change it or install a custom ROM on top it will say "CSC-UNKNOWN" because for custom ROMs and other changes to be done there needs to be at leats 3 CSCs in the firmware.The best thing you can do if you want to stay on this firmware is stay with XEU for your region or if you want flash the OXA multi CSC pack.It has varios CSCs to choose but i cant remember if it has XEU.You could always flash a custom ROM that has a multi CSC package built in to it like Omega ROM which im using but this of course means you cant use Kies.So the choice is yours.Stay with XEU if you want to keep to stock or OXA-multi CSC if you want to flash a custom ROM or back to your original carrier firmware to keep using Kies.
EDIT: Theres nothing Kies can do for you that XDA cant.Im in Spain on XXKI4 (Poland 2.3.5.) running Omega XT v3.0 ROM which has a EUR CSC for Europe built in to the ROM itself.So Ive got a Europe CSC thats works fantastic with a version of android that isnt even released in my country and a ROM thats fast and stable that gives me 2 days battery life with 3G on all day with moderate use.
thanks
Hi
Thanks for that, I guess I just wanted the best of both worlds, to be able to flash official roms from XDA as they come out for XEU but also have the ability to do the same through kies - ODIN was painless enough so as u say there's nothing kies can do for me that xda can't in that respect
Eureaka
So I factory re-set my phone from the recovery menu.......bang csc now reads xeu so it would seem to be that flashing the firmware as above won't sort csc on it's own unless a multi csc, but it doesn't matter which route u pick multi/single csc fw package you have to factory re-set to change it.
At least I know if I ever need to send the phone back to 02 I reflash, factory re-set and everything is as should be, although will the binary counter hint i've been flashing?
kpsmithuk said:
So I factory re-set my phone from the recovery menu.......bang csc now reads xeu so it would seem to be that flashing the firmware as above won't sort csc on it's own unless a multi csc, but it doesn't matter which route u pick multi/single csc fw package you have to factory re-set to change it.
At least I know if I ever need to send the phone back to 02 I reflash, factory re-set and everything is as should be, although will the binary counter hint i've been flashing?
Click to expand...
Click to collapse
For the counter just buy a jig on ebay or maybe from a store if you can find one that sells them.Ebay always has them.It wipes the counter clean so Samsung dont know that yourve been playing around cos if the counter isnt at 0 then your warranty is void.Cost 2 bucks.The latest 2.3.5 official firmwares,also available here on XDA,have a new bootloader which is un-wipeable but there is an odin flashable old bootloader which allows you to flash the latest version and still wipe the counter.you can read about it here at the bottom of the Frankenstein section bellow XXKI3
http://forum.xda-developers.com/showthread.php?t=1075278
I also wanted the best of both worlds but at the end of the day all official kies firmwares you can find here from the link i just gave you anyway and flashing custom ROMs and back to stock and custom and stock again could also put your IMEI in danger of being corrupt.
EDIT: Heres a good IMEI backup method http://forum.xda-developers.com/showthread.php?t=1308546
Wasn't aware of that risk! Will have to get a jig as if phone busts it will have to go back via my insurance company and I'm sure they will check!
Also I've got Odin 4.42 now not odin 3 1.85 does anyone know how to use it to flash the GS2 as it's options are slightly different e.g one tarball support - dedicated option rather than just pointing the pda field at the single tar.
also the reset time has a value of 300 rather than just being a tick box. Other than that it's pretty much the same
kpsmithuk said:
Wasn't aware of that risk! Will have to get a jig as if phone busts it will have to go back via my insurance company and I'm sure they will check!
Also I've got Odin 4.42 now not odin 3 1.85 does anyone know how to use it to flash the GS2 as it's options are slightly different e.g one tarball support - dedicated option rather than just pointing the pda field at the single tar.
also the reset time has a value of 300 rather than just being a tick box. Other than that it's pretty much the same
Click to expand...
Click to collapse
About the new Odin im not sure.If your not sure then its probably a fail-safe bet to stick to v1.85,at least you know it works and messing around with things that your not sure about could end up with a bricked phone.Ive been flashing for donkeys and im happy with v1.85.If it aint broken....so ill stick with it.A jigs good to have just incase.If something happens you need to wipe the counter before sending it back.An IMEI backup is a MUST HAVE.Not really if your only flashing original firmwares but if you want to flash custom ROMs then YES its possible that something could go wrong.Happens not to often,to some people never,but if you dont have a backup then there is no way you can get your original IMEI back without sending it back to the service centre and that will cost you.No IMEI means on conection at all.No 3G,HSPDA or even signal.Not good at all
Cheers for the advice will stick to 1.85 it works lol yeah i stick to official fw interested to know how imei can get fried though
Sent from my GT-I9100 using Tapatalk

Official ICS failed to install after 12%

I went to software update and there is a 197mb update on my phone then i started to download and it downloaded just fine but after rebooting it is failed always at 12% and meesage comes up " update through kies or contact samsung"... on kies there is no update.
My phone is not rooted.S II I9100 from KSA.
anyone?
This is what exactly going on
http://www.youtube.com/watch?v=gHkU_57zmlM&feature=player_embedded
Assuming you're running stock & have never messed with (rooted/run non stock firmware) the phone, try a factory reset/wipe in the first instance (boot into recovery), then try the update again.
You could flash a stock ICS rom manually with Odin, but be aware if you bork it in the process (very unlikely/small risk, but still a risk nonetheless), you'll likely not get it fixed under warranty. Get the PC version of Checkfus if you want to go down this route (search for it on here/Google), this will enable you to download the update manually, then flash it following the instructions here.
Ton need at least 40% to install an update.
MistahBungle said:
Assuming you're running stock & have never messed with (rooted/run non stock firmware) the phone, try a factory reset/wipe in the first instance (boot into recovery), then try the update again.
Click to expand...
Click to collapse
actually i have rooted my phone before 2 months but now it is not rooted... i just want to install official ICS using kies or through OTA ...don't want to root again.
Then take your pick. Do the reset & try it again (make sure you've got at least 40% battery; I think that's what JT meant), or do it manually with Odin. Or try the first option, then the 2nd one.
Up to you.
Also, if you can't find the firmware you need with Checkfus, search Samfirmware or here
Edit after your edit - In that case definitely the first option. If it doesn't work & you don't want to do it manually, take it to a Samsung service centre & ask them to put the latest firmware on it for you.
MistahBungle said:
Then take your pick. Do the reset & try it again (make sure you've got at least 40% battery; I think that's what JT meant), or do it manually with Odin. Or try the first option, then the 2nd one.
Up to you.
Also, if you can't find the firmware you need with Checkfus, search Samfirmware or here
Edit after your edit - In that case definitely the first option. If it doesn't work & you don't want to do it manually, take it to a Samsung service centre & ask them to put the latest firmware on it for you.
Click to expand...
Click to collapse
Ok, after reseting there is no update available on my phone when i try to update using phone.
OK. Have you ever flashed any other stock firmware on the phone ? I have two theories about this 'upgrade' - one; if you've flashed stock firmware for other regions on your phone, there's may be some issue with the CSC (even if you're currently running correct firmware for your region) preventing you from getting OTA updates successfully. Also, the update you saw may have been not for your region, because your CSC is messed up , it may have tried to pull an update for the region whose firmware you had on the phone previously. And when you did a reset it might have somehow fixed the issue with the CSC, and there is no update for your region. Conjecture, but hard to know exactly without knowing the history of the phone & exactly what you've done it.
Two; the size of the update sounds a bit strange. I would have thought it would be bigger than 197MB. Even zipped, I have a carrier branded ICS firmware and it's huge (>700MB). That you were able to download it, yet there was nothing on Kies is really strange.
Go into settings/about phone & tell me all the details you have in there. Also tell me everything you've done with the phone since you got it so far as rooting/flashing other firmware goes (details of kernels, roms, etc). And we'll see if we can shed a bit more light on things.
And one other thing, in your last post you say there's no update on the phone, have you checked Kies again. If not, have a look.
MistahBungle said:
it may have tried to pull an update for the region whose firmware you had on the phone previously. And when you did a reset it might have somehow fixed the issue with the CSC, and there is no update for your region. Conjecture
Click to expand...
Click to collapse
This might be true
Go into settings/about phone & tell me all the details you have in there
Click to expand...
Click to collapse
.
I bought S2 from Saudi Arabia.
baseband version: I9100XXKI4
Kernal Version: 2.6.35.7-I9100JPKJ2-CL655700 [email protected] #2
GBuild Number: GINGERBREAD.JPKJ2
]Also tell me everything you've done with the phone since you got it so far as rooting/flashing other firmware goes (details of kernels, roms, etc). And we'll see if we can shed a bit more light on things.
Click to expand...
Click to collapse
I have used this guide for rooting http://androidforums.com/galaxy-s2-...t/482994-rooting-galaxy-s2-dummies-guide.html
but after trying 5 or 6 custom ROMS i just unroot my phone.
And one other thing, in your last post you say there's no update on the phone, have you checked Kies again. If not, have a look.
Click to expand...
Click to collapse
no update on kies either.
I have also used this method toinstall official stock firmware http://www.technetinfo.in/mobile/mobile-software/stock-gingerbread.html
let me quote my own message while i was having problem with CSC.
k i did factory reset and wipe all data now it doesn't show "that device doest not support software upgrading via KIES" but firmware info is totally different now, it is suppose to be (KSA) not (XSG).
Click to expand...
Click to collapse
one thing more i would like to mention here is that before rooting....KIES showing
PDA:KJ2 / PHONE:KI4: / CSC KJ1 (KSA)
now it's showing
PDA:KJ2 / PHONE:KI4: / CSC KJ1 (XSG)
Click to expand...
Click to collapse
FIXED BY CHANGING CSC CODE
OK. Given all that, then it's obviously a CSC issue. Which means either it showed an update was available for the wrong region, and now that CSC issue has been resolved. Or there is an update for your region but your CSC is messed up so it can't get the update.
I've had a look at Checkfus, and the stock rom you're currently running is the latest for Saudi Arabia (GT-I9100LKAKSA -I9100JPKJ2/I9100OJPKJ1/I9100XXKI4/I9100JPKJ2) which was released on 25/10/2011.
So I'd say that update you saw was for another region, and the factory reset you did fixed whatever issue there was. There are no updates for your region, put it that way.
Edit - Unless it's some kind of minor carrier specific update ? That could explain the relatively small size of the one you saw. I guess you could find this out by contacting your carrier.
Thanks a lot MistahBungle, i really appreciate your help.
Now i have changed my CSC code from (KSA) to (JED) and now i'm getting official update from kies. Just curious about changing CSC, is there any negative effect on my phone in future by just changing CSC code?
Given you're getting OTA updates OK, probably not. Normally if you change your CSC to a different region, you often have problems getting OTA firmware updates. If it's working for you, it's obviously fine.
MistahBungle said:
Given you're getting OTA updates OK, probably not. Normally if you change your CSC to a different region, you often have problems getting OTA firmware updates. If it's working for you, it's obviously fine.
Click to expand...
Click to collapse
not sure about OTA but on KIES it is showing my firmware info correctly, i mean i can get updates through KIES without any issues.
suppose if i want to change my CSC back to original one (KSA) then what will happen?
As long as you can get it via Kies you're set. And even if you couldn't, it's simple to download the firmware with Checkfus & flash it via Odin. That's what I'd do if I were on rooted stock, for example (but I probably wouldn't be in any event).
I don't know. Try it & find out. Yes, I'm serious. I hate stock firmware, it's rubbish, and haven't run it since the first week I got my phone. So I honestly don't know.

[Q] JB Update query Samsung galaxy S3

Hi all....
I am an infrequent user of this site, the last time I pored over the information housed in here was a couple of years ago when I found the site and various threads invaluable for me when rooting my old and trusty HTC Desire.
I am now the owner of a fab and groovy galaxy S3 which I aquired in the UK from carphone warehouse.
I am using Vodafone as a carrier, but my understanding is that the stock phone was not tied in any way to a carrier.
It didn't take me long to root the phone, I only rooted the device because I wanted to get rid of various bits of samsung/bloatware, not in order to Flash a new rom to the phone.
I was more than happy with this until I received a notification that there was an OTA update, this I deemed to be the JB OS, which of course would not install due to the fact the phone was rooted and was using cwm etc.
After a week of cancelling the update and being reminded of it every three hours I decided that it was maybe time to update, I discovered that in order to do this I needed in effect to put the phone back to its factory state, soo I completed a factory reset on the phone and in no time at all I was up and running again with an unrooted S3....however, despite this in the last three weeks I have seen hide nor hair of the update that seemed to be banging at my door for so long!
My question therefore is:
is there something I am unaware of that is now stopping my phone from receiving the OTA update via settings/about device/software update/update(check for updates)?
To help those of you that know about this stuff here are the details from the phone that may help you to help me...and anyone else not in the know enough!
Device Status = Normal (while rooted this obviously showed as being modified)
Model Number GT-19300
Android version 4.0.4
baseband version - 19300XXLG8
kernel version - 3.0.15-928452-user [email protected] #1 SMP PREEMPT Thu Jul 26 12:06:08 KST 2012
Build Number IMM76D.19300XXBLGB
In addition prior to unrooting the phone the foillowing info was parsed and returned :
AP: 19300XXBLG8
CP: 19300XXLH1
CSC: 19300OXABLG8
Following unrooting and completing a factory reset.....the same process returns this information.....
AP: 19300XXBLG8
CP: 19300XXLG8
CSC: Unknown.
My apologies for the length of the post for what is probably a trivial matter, but as a Phone noob (but a systems pro) you can never have too much info!
many thanks in anticipation!
It's because your CSC was lost when you unrooted and hence OTA won't work. You would have been better off using the toolkit (see original development forum) to simply download and flash the JB ROM yourself, then no need to unroot etc.
You can still do this and you'll also get updates usually faster than OTA.
Regarding your bust CSC, try:
http://forum.xda-developers.com/showthread.php?t=1845103
Hmmm...well...
many thanks for the info re the cause of the issue, however, having looked at the following I still am having no joy.
1) downloaded a correct csc file and using odin flashed it to my phone, however, it is still showing the same information as before.
2) Found a stock Rom. the exact same Rom as that which is installed, that has been flashed using Odin and once again, upon reboot the information is exactly the same.
I'm not quite sure why you want to fix it, flashing jb yourself is much quicker, but a quick search found:
Q. I have flashed XXXX ROM and now my CSC is unknown?
A. Generally Speaking CSC does not make much of a difference. If you are really facing a problem which is related to CSC such as some specific apps not working, some language not there etc. Either:
Use
Type *#272*Device IMEI# at Phone dial pad.
Select the CSC that you want.
Click Install.
or Install CSC changer app from the Market and change the CSC
Both ways yopur device will be factory resetted.
Good luck.
I can....
...find all of that myself, It doesn't really help much if the person searching amongst the huge amount of disarticulated information liberally strewn around this forum is faced constantly with broken links or unhelpful replies and threads that vanish up their own orifice.
In order to decorticate that information it helps if some form of standardisation or common language is employed.
I have my reasons for asking the original question.
I am facing a problem and asking for advice and help in order to rectify the issue.
I have tried to flash the JB ROm myself, I am despite what you may consider not stupid, however, I am receiving errors when flashing the rom from the 'update' menu from the recovery menu within the phone.
Elsewhere on this forum I discover that it may be an issue with the csc being in an unknown state, hence my post in the first place, If I was able to follow the instructions and all was working as it should I would not bother anyone here or indeed waste my time doing so.
by querying the csc by using the dial pad it shows me that the correct one is still there, so installing it seems pointless, however, as stated at the very beginning of the question, when parsing the phone for detail info it tells me that the csc is 'UNKNOWN'
Greywolf907 said:
many thanks for the info re the cause of the issue, however, having looked at the following I still am having no joy.
1) downloaded a correct csc file and using odin flashed it to my phone, however, it is still showing the same information as before.
2) Found a stock Rom. the exact same Rom as that which is installed, that has been flashed using Odin and once again, upon reboot the information is exactly the same.
Click to expand...
Click to collapse
Try installing this from the Android Market
https://play.google.com/store/apps/details?id=com.manniakk.cscselector&
Run it and update your CSC to your correct one
EDIT :- Just looked at your phone info in post 1 again, this relates to UK unbranded version so your CSC should be BTU
You shouldn't normally have a problem updating a rooted phone to newer versions provided the base rom is still stock I have never had a problem with mine but everyone is different I guess, I did mine via Kies then just re-rooted afterwards.
...well...
ag4751 said:
Try installing this from the Android Market
Run it and update your CSC to your correct one
Click to expand...
Click to collapse
Hi and thank you also...however, I have checked the sales code and it is properly installed and shown as being BTU, which is correct, this is shown of course by typing into the dial pad...et al ad nausea....whatever, it is correctly displayed, the issue is that when typing into the dial pad *#1234# in order to retrieve the information contained there, it is returning CSC UNKNOWN.
Greywolf907 said:
Hi and thank you also...however, I have checked the sales code and it is properly installed and shown as being BTU, which is correct, this is shown of course by typing into the dial pad...et al ad nausea....whatever, it is correctly displayed, the issue is that when typing into the dial pad *#1234# in order to retrieve the information contained there, it is returning CSC UNKNOWN.
Click to expand...
Click to collapse
OK you wrote this while I was writing my edit in the previous post.
Have you tried just installing the latest 4.1.1 BTU version using Odin you can get it from the Sammobile web site its the PDA version I9300XXDLJ4
http://www.sammobile.com/firmware/?page=3&model=GT-I9300&pcode=BTU&os=1&type=1#firmware
......not
ag4751 said:
OK you wrote this while I was writing my edit in the previous post.
Have you tried just installing the latest 4.1.1 BTU version using Odin you can get it from the Sammobile web site its the PDA version I9300XXDLJ4
....that version no........I did d/l and try this version
United Kingdom 8 Sep 2012 4.1.1 I9300XXBLG8 I9300XXDLI4 283.2 MB Download
which seemed to be relevant to my original build, this is the one that I have been having issues with.
I am also somewhat confused as to how to install the zip file via Odin, I more or less think that the pda file needs to be a single tar/md5 file and of course these things are coming as zips...well..at least the last one I d/l'd did.....
I am as I type sucking the file you suggest down and as soon as hotfile finishes dribbling it into my machine I'll give it a bash and let you know what happens.....many many thanks for taking the time to help me and do it with such good grace and civility, it's refreshing.
Cheers for now!
PS: I tried Kies, on three different machines, two running XP and one running Seven, each time it just doesnt want to know that the phone is even connected...ie. it knows its there, but just doesnt want to actually connect to it...just whirrs and clicks until I get fed up and unplug it....hence the grief I am having one way or another trying to update the O/S...so I can root it again!
Click to expand...
Click to collapse
I am also somewhat confused as to how to install the zip file via Odin, I more or less think that the pda file needs to be a single tar/md5 file and of course these things are coming as zips...well..at least the last one I d/l'd did.....
Click to expand...
Click to collapse
You need to extract the file located inside the zip file, then start Odin, click the PDA button and find the extracted file, put your phone in download mode, connect to your PC, wait for Odin to connect then start the update.
mucho...
ag4751 said:
You need to extract the file located inside the zip file, then start Odin, click the PDA button and find the extracted file, put your phone in download mode, connect to your PC, wait for Odin to connect then start the update.
Click to expand...
Click to collapse
yes I understand all that bit, I didn't make myself clear maybe....The problem I had was that the file I had downloaded seemed to be a zip file containing the whole system, i.e a cloned image, it didn't work...however, the link you so very helpfully provided was just waht i was looking for and couldn't find myself, a single tar/md5 file which has been downloaded, installed and is up and running....I now have JB, but still the csc is classified as unknown...anyhow, that doesn't matter much until the next time I need to update.
My very best regards to you and huge thanks.
have a good 'un
:good:
Got there eventually, strange abut the CSC
If you want to root your phone use this thread, 3rd post if you don't already have it
http://forum.xda-developers.com/showthread.php?t=1957273
Then install this for easy access to recovery
http://forum.xda-developers.com/showthread.php?t=1768142

Categories

Resources