Hi all, i´m very confusing about CSC codes.
I´m pretending flash the new baltic LQ3 ICS Image available today , but i live in Chile (CHB CHE CHL & CHT codes).
Founded this information to know the CSC charged in phone:
Your phone's IMEI (International Mobile Equipment Identity) number is an international "Serial number" for your phone to properly identify it.
Your IMEI can be found using the following methods :
At the back of your phone behind the battery
Or by dialing *#06#* while your phone is powered on it is a 15 digit number.
NOTE: If your phone prints out more than 15 digits for your IMEI , please only supply us with the first 15 numeric digits the phone provides, no dashes or space. The remaining numbers are unimportant as they are just checksum numbers.
Once obtained IMEI, it can be used to know the CSC code charged on Phone:
check for CSC (*#272*IMEI#)
My question is:
¿ how can i switch from precharged CSC codes from LQ3 -baltic ICS Image to south america ones that can be usefull in Chile ?
¿ is only matter of change the CSC code on phone or there is neccesary download some CSC image and flash with Odin or any else program ?
Please i´ll really appreciate your comments.
regards in advance.
Related
Hi,
I have tried to look around for an answer to this Q, but none has given a technical answer, just a general "do it, don t worry , don t do it...".As anyone knows, every update Samsung releases is released by Countries or "areas". The CSC defines these areas and throu the correct code it is pushed via kies only to the given Countries.. Now, I wonder what happen if I flash thru Odin a new FW ( say the newest 2.2.1 JS3 that is made by a single tar file including a CSC XEU) to a NON XEU Samsung, my case being italian is ITV ...I know that I should have a working phone, 2.2.1 update , in italian language yet with a CSC XEU....so what? what are the tecnical implications or changes I have? different setting to radio? Swipe not working? Wrong APN...??? DIFFERENT IMEI??the typical known things are that I will not be probably be able to connect thru Kies, and lost my warranty . But ...what else? If these are the only things, If I have to worry about my warranty, then I can always reflash wth the original ITV FW....mmmh, anyone can explain me the associated risks/ pros and cons? thanx a lot
Essentially its the networks local to that CSC .
ITV csc is going to give you your local networks .
SER csc is giving Russian networks
XEU is UK and Ireland
You flash a CSC for your area .
jje
Thanx JJE....but, if I understand well, flashing a FW with a different CSC would NOT give me my local networks and therefore ( this is the point) I should not be able to find them...well, this it seems not to be true. Many users living in different countries have flashed the first 2.2.1 JPY XEU appeared on dec 2010 yet I think they have been able to connect to their networks...I mean, not sure about that biut I guess that if they could have not , they would have noticed....
Manual entrant of networks .
CSC gives
Sales code dat selling network branded O2UK
Others xml Vibrate on Off latin IME
Feature xml add in for operators to use
Customer xml a list of networks and network information
Contents db data base file
Loose in a rom not in CSC is
CSC Files text
/system/csc/customer.xml
/system/csc/others.xml
/system/csc/sales_code.dat
/system/csc/feature.xml
/system/csc/contents.db
/system/T9DB/qwerty_sv.kdb
/system/T9DB/phonepad_sl.kdb
/system/T9DB/phonepad_cs.kdb
/system/T9DB/qwerty_hu.kdb
/system/T9DB/Samsung_400_FRlsUN_xt9s.ldb
/system/T9DB/qwerty_sl.kdb
/system/T9DB/phonepad_nl.kdb
/system/T9DB/Samsung_400_ELlsUN_xt9.ldb
/system/T9DB/qwerty_nl.kdb
/system/T9DB/phonepad_sk.kdb
/system/T9DB/Samsung_400_PTlsUN_xt9.ldb
/system/T9DB/qwerty_sk.kdb
/system/T9DB/qwerty_el.kdb
/system/T9DB/Samsung_400_ENubUN_xt9.ldb
/system/T9DB/qwerty_it.kdb
/system/T9DB/qwerty_pt.kdb
/system/T9DB/qwerty_pl.kdb
/system/T9DB/Samsung_400_DEusUN_xt9.ldb
/system/T9DB/qwerty_es.kdb
/system/T9DB/Samsung_400_SVusUN_xt9.ldb
/system/T9DB/Samsung_400_ITlsUN_xt9.ldb
/system/T9DB/phonepad_hu.kdb
/system/T9DB/phonepad_fr.kdb
/system/T9DB/phonepad_hr.kdb
/system/T9DB/qwerty_ko.kdb
/system/T9DB/phonepad_es.kdb
/system/T9DB/Samsung_400_CSlsUN_xt9.ldb
/system/T9DB/qwerty_hr.kdb
/system/T9DB/phonepad_ro.kdb
/system/T9DB/phonepad_ko.kdb
/system/T9DB/phonepad_en.kdb
/system/T9DB/Samsung_400_NLlsUN_xt9.ldb
/system/T9DB/qwerty_fr.kdb
/system/T9DB/qwerty_de.kdb
/system/T9DB/Samsung_400_ROlsUN_xt9.ldb
/system/T9DB/qwerty_cs.kdb
/system/T9DB/phonepad_sv.kdb
/system/T9DB/Samsung_400_SKlsUN_xt9.ldb
/system/T9DB/qwerty_ro.kdb
/system/T9DB/phonepad_el.kdb
/system/T9DB/Samsung_400_HUlsUN_xt9.ldb
/system/T9DB/phonepad_pt.kdb
/system/T9DB/phonepad_de.kdb
/system/T9DB/Samsung_400_PLlsUN_xt9.ldb
/system/T9DB/Samsung_400_HRlsUN_xt9.ldb
/system/T9DB/qwerty_en.kdb
/system/T9DB/phonepad_pl.kdb
/system/T9DB/Samsung_400_ESlsUN_xt9.ldb
/system/T9DB/phonepad_it.kdb
/system/T9DB/Samsung_400_SLlsUN_xt9.ldb
/system/SW_Configuration.xml
/system/wallpaper/drawable/7858 The O2 Image 800x960px_small.jpg
/system/wallpaper/drawable/7858 The O2 Image 800x960px.jpg
/system/wallpaper/default_wallpaper/default_wallpaper.jpg
/system/CSCFiles.txt
CSC Version = product code
jje
All a CSC is, is a bunch of text files that tell Android what to set as default when there is no data partition.
It contains your default APN. As well as the default "home" bookmark in the browser, and any other bookmarks that may show up by default. It contains default settings for keyboards, like languages and if click sounds/vibrations are on or off.
Just extract one of the csc *.tar files and open all the files in WordPad or something similar. There's nothing there that can possibly hurt your phone if you go to another CSC. It's JUST settings that can be changed and saved when you're booted into android and have a data partition.
"I had this problem after uesing darkys rom this is how i fixed it i typed *#06# and wrote iemi number down 15 digits long now type *#272*your 15 digit iemi # this will bring up new menu now select apropiate country code ie (xeu) uk and press install will tottaly reset phone but after i did this my gps like new darkys had set my csc to korea.lol hope this works "
I seen this solution for a GPS fix (darkys)
I can get to this screen but I see:
Sales Code XEE
1) What's XEE? how do I change this to north america?
http://forum.xda-developers.com/showthread.php?t=787163
jje
You can also open "Fasterfix" which comes with Darkys.
You have a dropdown menu.
An other easy to use app is "GPS-AIDS"
I have a problem with my phone. I bought the phone through a carrier, so it had the CSC set to UFN, but then i decided to flash through odin the brandless version of the firmware, which has the CSC set to ARO. The thing is that while *#272*<IMEI># shows me that i have the ARO code, kies keeps showing me the UFN cose thus making me unable to update through it. What can i do to make kies update the CSC from UFN to ARO?
Regards
Well i have an update on this, apparently kies is reading the UFN through the PRODUCT CODE and not the CSC. The problem now is that apparently the PRODUCT CODE information, along with other things like IMEI, is stored in a file named .nv_data.bak in the efs folder. The thing is that i don't have that file on that folder, but somehow the phone and kies can still read the PRODUCT CODE and the IMEI so they must be getting the information from somewhere. My questions now are, where is the file from which the phone and kies are reading the product code? Can i change the PRODUCT CODE from there? Can i copy the .nv_data.bak from another I-9070 and work from there or the files are completely different?
Regards
file is called nv_data.bin.md5 - and it must be there - or else *#06# will give you 0000000000 or some kind of error.
IDK if copying this file from other phone will fix it for you but I would rather not give it away to anyone (in this case you) because of IMEI - so it might be hard for you to get one from anyone else.
You can try to flash ARO again - I had PLS ROM (branded by Plus in Poland) and I have flashed XEO (Poland - not branded) and my Kies shows me XEO and OTA update was detected and applied as XEO
I downloaded XEO from here: http://samfirmware.com/
EDIT:
One more thing comes to my mind: is it maybe carrier locked device (as in no other sim card will work on it)?
In such case it is probably that thing - sim locked to UFN and stays there no matter the ROM region code
th3cr0w said:
file is called nv_data.bin.md5 - and it must be there - or else *#06# will give you 0000000000 or some kind of error.
IDK if copying this file from other phone will fix it for you but I would rather not give it away to anyone (in this case you) because of IMEI - so it might be hard for you to get one from anyone else.
Click to expand...
Click to collapse
When i do *#06# i get my phones IMEI perfectly, but in the efs folder the only nv files i have are .nv_state, nv.log and nv_data.bin.md5 (this file with 0 bytes of info). That's why I'm puzzled, if the files are not there i shouldn't be able to retrieve my IMEI or PRODUCT CODE, but i can do that perfectly fine. Maybe the info is stored somewhere else?
Regards
Edit: i believe that flashing the stock ROM doesnt restore the efs folder, am i wrong?
all IMEI repairing guides are using nv_data.bin (no .md5) that is 2MB of size so at least this part must be there - thing is my phone gives me my IMEI with 8#06# and i do not have nv_data.bin - just .md5 as in your case - 0b in size.
IDK about product code location but I know that flashing non-branded ROM changed how Kies sees region of my device and I didn't mess with my device anymore - just applied root to XEO and flashed rooted one - I am sure that no root version would work the same way
th3cr0w said:
all IMEI repairing guides are using nv_data.bin (no .md5) that is 2MB of size so at least this part must be there - thing is my phone gives me my IMEI with 8#06# and i do not have nv_data.bin - just .md5 as in your case - 0b in size.
IDK about product code location but I know that flashing non-branded ROM changed how Kies sees region of my device and I didn't mess with my device anymore - just applied root to XEO and flashed rooted one - I am sure that no root version would work the same way
Click to expand...
Click to collapse
If I'm not mistaken the information actually comes from .nv_data.bak not .bin, and kies needs a match from the CSC and the PRODUCT CODE to allow updates. I can change the CSC freely, but lacking the files in the efs folder i cannot change the PRODUCT CODE, but as i already mentioned it is extremely weird because those files also contain the IMEI info and both my phone and kies can read the IMEI and PRODUCT CODE perfectly, which leads me to the conclusion that maybe the files are stored somewhere else?
Regards
Please, can i get some insight on then the matter? At least from the technical part, how can my phone and kies read the IMEI and PRODUCT CODE when the files that have that information (nv_data.bin, nv_data.bak) are missing? Where are they getting the info from, from which files?
Regards
Well, to give a helping hand to people who may encounter the same problem, here is the solution. When i was almost ready to give up i found this thread that explains how to back up the efs data in the Samsung Galaxy S III Mini, and there it said that this particular phone has the NovaThor chipset and that it doesn't posses the normal nv files in the efs folder. So i checked the specs of our phone and i realized that it also has a NovaThor chipset. Then after a little investigation i found that that the file that has the PRODUCT CODE information is in this location /ModemFS/Perm/prot/ and in this file NV.DAT. I changed the PRODUCT CODE there i now i can freely update with kies!
Regards
CSC question
hey guys! i need help.. when i dial *#272*IMEI# my csc/sales provider is O2i(United Kingdom-Ireland). i was wondering how i could change it (if possible, to SMA(philippines)). when i try to do so, i only get o2i and nothing else. no other choices (even when using csc changer from google play). the phone had been locked to o2i but had been unlocked here in the philippines ( phone was given as a gift). any suggestions?
Hello! My 9305(from Hong-Kong) can't register in SK Telecom - emergency only (911 works). I tried to put the sim card to sony xperia(from Russia) - worked fine in 3g mode(umts:3). May the problem be in my csc?
AP: I9305XXBLL5 (Ripper ROM v8) CP: I9305BVBMF1 CSC: I9305TTELALI3
Check here:
http://forum.xda-developers.com/showthread.php?t=2010116
Raistlin1158 said:
Check here:
http://forum.xda-developers.com/showthread.php?t=2010116
Click to expand...
Click to collapse
Thanx, I've tried native modem for my HK phone zhali2 - the same result.
Don't know wich to install to work in S. Korea(
Find the Korean users thread probably in General .
JJEgan said:
Find the Korean users thread probably in General .
Click to expand...
Click to collapse
Korean users don't use 9305(
If you cannot ask in the Korean thread then use Google .
Korean users don't use 9305( >>> in that case you are wasting your time .
You will require the correct hardware re networks likewise modem and CSC
Trouble with most firmware on sammobile is that they are multi-csc and distributed for a region together with the factory code (KOR) for Samsung Korea.
If you install firmware via Kies your Product Code remains intact, but installing with Odin, and at reboot, android defaults to KOR inmany cases.
Have you tried going to Recovery Mode and Clear cache and Clear Data ? (recommended after a new install, but may also set your CSC to BTU -but again may not)
The only way to change Product Code to a specific CSC code, is to root your phone and install a CSC changer app from the Play Store.
Is any modem patch for 9305 like Ariza for 9300? May be this will help... I also tried to change option sha256 to 0 in phone lock service menu despite the fact that my phone wasn't locked (worked in many countries) and no result but gps can't find sats now(( returned that option back - no effect...
Hi,
Info
I have a GT-I9305, Android 4.3, SentinelROM Version 5.00 with Build date of Oct 1st 2013.
Kernel 3.0.64-CM-gbc8f4c9, [email protected] #1 and
Baseband Version : I9305DXALI7
Background :
My Samsung S3 LTE was initially locked to Orange/EE, which I did a network unlock by downgrading to 4.1.1 and using that famous menu command *#19...Subsequently I upgraded to Android 4.3
Issue
I am using Virgin Network here in UK, but the phone always shows Orange/T-Mobile signal. Also, it stops sending SMS messages after a few days. If I put the SIM Card back in Nexus 4, it correctly shows Virgin Network on the phone. (I am aware that Virgin is a virtual network provider using Orange/T-Mobile).
Question
Is there a way I can show Virgin network on the phone? Currently it doesn't even detect Virgin network, if I do a search available networks. Is that due to an incorrect Baseband Version? If yes, could someone point me to the correct one? I did search on http://www.sammobile.com/firmwares/ but they all seemed to be for Android 4.1.1 and not 4.3 for I9305
I have tried flashing a few other basebands as well from this link : http://forum.xda-developers.com/showthread.php?t=2010116
But still not able to get Virgin network. Phone does seem to be working fine but I dont want to get suddenly caught out again whereby it stops sending SMS's again!
Thanks
Sam
You require a CSC that includes Virgin .
Try CPW carphone warehouse csc .
Or ask Virgin for the APN settup .
Android 4.3 is not released by Samsung so you will not find it .
JJEgan said:
You require a CSC that includes Virgin .
Try CPW carphone warehouse csc .
Or ask Virgin for the APN settup .
Android 4.3 is not released by Samsung so you will not find it .
Click to expand...
Click to collapse
Hi,
APN setup seems to be fine (goto.virginmobile.co.uk), SMSC shows as "+447958879890",145 ..How do I get CarPhoneWarehouse's CSC?
Sorry, don't know much about CSC so am a bit ignorant about CSC..
Cheers
Sam
sam_htc_touch said:
Hi,
APN setup seems to be fine (goto.virginmobile.co.uk), SMSC shows as "+447958879890",145 ..How do I get CarPhoneWarehouse's CSC?
Sorry, don't know much about CSC so am a bit ignorant about CSC..
Cheers
Sam
Click to expand...
Click to collapse
Modem CSC post or in a stock rom from sammobile.com .
BUK UK probably has CPW csc
Sorry i always delete CSC from roms otherwise i could post one .
All i say is that the CPW csc did have Virgin inside at one time .
JJEgan said:
Modem CSC post or in a stock rom from sammobile.com .
BUK UK probably has CPW csc
Sorry i always delete CSC from roms otherwise i could post one .
All i say is that the CPW csc did have Virgin inside at one time .
Click to expand...
Click to collapse
Hi JJEgan,
I am going to use the CSC Changer App, currently taking a backup of the phone. Is there anyway to quickly check the current CSC? (by checking some file in system directory etc or viewing build.prop etc to figure out the current CSC?) Asking this as USSD Codes don't seem to be running on my phone and I always get Connection Problem or Invalid MMI Code error message. So that means I am unable to run *#1234#
Cheers!
PS : Just tried to use CSC Changer App, but realized that either the phone should be on Android version lower than 4.2.2 or the ROM should be a Samsung Stock ROM! And in my case I am on a Custom ROM and on Android 4.3
http://ykkfive.blogspot.com/2011/11/samsung-csc-code-reference-3.html#.UmV5lPnBPeM
Got the list of CSC's above..What should I do next? And against UK is mentioned as : BTC, BTU, CPW, H3G, O2I, O2U, ORA, OXA*, TMU, TSC, VIR, VOD, XEU
So CarPhoneWarehouse is there in the above list and VIR (I assume VIR means Virgin Mobile) is also there..So how do I flash or what do I flash now?
Faqs and Guides .
http://forum.xda-developers.com/showthread.php?t=2198512
JJEgan said:
Faqs and Guides .
http://forum.xda-developers.com/showthread.php?t=2198512
Click to expand...
Click to collapse
Thanks JJEgan, I did look at the thread you mentioned and that's where I got the CSC Changer idea..but stayed back from actually doing it as I realized that the 2nd step mentioned about factory resetting the phone..The issue that I have currently is that to find out about my current CSC etc, I need to run a USSD Code which gives me an error message (about invalid MMI Code). So I would either probably leave it at that or better still get a new Orange contract SIM and port the number back from Virgin to Orange!