Develop Bugs

Release: I9000XWJM6 - Multi CSC(s) Europe

I installed this version to my phone yesterday (see the attachment) and since I have nothing to complain about (has there ever been ), I decided to share this release with the community.
Few facts about this version:
INTERNAL release (not official, obviously)
It is 2.1 Eclair
Build time: 2010.08.06 23:20:57 KST
Changelog: Unknown
PDA version I9000XWJM6, MODEM version I9000XXJM3
All CSC versions are I9000???JM1 and unbranded, but CSC´s for specific operators (Vodafone for example) are included.
I have not modified the code in any way, although I have repacked the release to make CSC selection possible.
Usually Odin3 images are provided in a single integrated .tar package which contain all of the necessary files. This way the CSC cannot be selected separately.
That is why I splitted the release in three different parts (CODE, MODEM, CSC).
Since Odin3 has flashfile checksum support I also added md5 hash tail to the .tar files. This way is more secure because Odin will not allow flashing corrupted images. Flashing takes a bit longer thou because the checksums are checked in the beginning of the update process.
You need to download two files.
GT-I9000_I9000XWJM6_I9000XXJM3_CODE-MODEM.rar
CSC_I9000???JM1 (CSC of your selection)
I know this is not nearly all of the excisting variants, but repacking the softwares is quite a slow process for certain reasons. I have access to pretty much any Samsung firmware, so if you find a variant missing you can send me pm. I can have a look.
Here is the description of CSC´s (included country variants):
DBT (Germany specific)
OXA *Multi CSC* (for France, Germany, Italy, Poland, UK, UK & Ireland)
OXE *Multi CSC* (for Baltic, Kazakhstan, Russia, Ukraine)
OXX *Multi CSC* (for Austria, Baltic, Bulgaria, Croatia, Czech Republic, Greece, Hungary, Ireland, Macedonia, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, South Africa, Switzerland)
BMC *Multi CSC* Unbranded / Custom apps: (Canada)
HUI Branded: (Tre - H3G Italy)
OLB *Multi CSC* Unbranded / Branded: (Indonesia, Malaysia, Philippines, Singapore, Thailand, Vietnam)
OPS Unbranded / Custom apps: (Optus Australia)
XEE - Nordic: (Denmark, Finland, Iceland, Norway, Sweden).
TMN Branded: (TMN Portugal)
Download links:
GT-I9000_I9000XWJM6_I9000XXJM3_CODE-MODEM.rar
CSC_I9000DBTJM1.rar
CSC_I9000OXAJM1.rar
CSC_I9000OXEJM1.rar
CSC_I9000OXXJM1.rar
CSC_I9000BMCJH2.rar
CSC_I9000HUIHUI.rar
CSC_I9000OLBJG4.rar
CSC_I9000OPSJG1.rar
CSC_I9000XEEJM1.rar
CSC_I9000TMNJM1.rar
Special request:
I9000OXAJF6
Mock-up, check post #182 for further information.
Extract the downloaded .rar archives to the same folder.
The archives are contain .tar.md5 files. Do not open them with Winrar for example. They are compressed Odin images which do not need unpacking.
So how to proceed:
Put your phone to download mode (hold down: volume down, home key, power)
DO NOT plug in your phone yet, Odin / driver does not like it at this stage.
Start Odin3
Tick "Re-Partition", check that "Auto Reboot" and "F. Reset Time" have been ticked.
Click "PIT" button and select s1_odin_20100512.pit file.
Plug in the phone and wait until Odin finds it.
Click "Start" button... <Firmware update start...> <Get PIT for mapping...> appear. The phone will turn off and the screen indicates "Reset". Wait until Odin indicates "Pass".
Plug out your phone, remove the battery, put it back in and put phone to download mode again.
Click "Reset" button in Odin and untick "Re-Partition" box.
DO NOT select PIT file again.
Click "PDA" button and select "CODE_I9000XWJM6.tar.md5" file.
Click "MODEM" button and select "MODEM_I9000XXJM3.tar.md5" file.
Click "CSC" button and select the desired version "CSC_I9000???JM1.tar.md5".
Plug in the phone and wait until Odin finds it.
Click "Start" button and wait until phone reboots with the new software version.
When using *Multi CSC* you need to type *#272*????# after the flash (in dialer). ???? being the current time displayed by phone. For example if the time is currently 6.25pm you need to type *#272*0625#. Then select the desired CSC version from the list and press "Install".
Regards.
- Nottingham

Looks good, but mind if I ask where you're getting the FWs?

ShezUK said:
Looks good, but mind if I ask where you're getting the FWs?
Click to expand...
Click to collapse
I guess from the same place pretty much every release is.
Cannot go into the specifics, sorry.

anybody tried this one ??!! how does it compare to JM5 and samset 1.9f ??

Downloading.

Will you be providing regular FW releases? apparently the guy from samsung-firmwares isn't getting any so it'd be nice to have a regular source for newer versions

Spybreak said:
Will you be providing regular FW releases? apparently the guy from samsung-firmwares isn't getting any so it'd be nice to have a regular source for newer versions
Click to expand...
Click to collapse
Maybe.
One user requested a CSC for T-Mobile Hungary.
Here is the link.
CSC_I9000TMHJM2

Ah nice I'll give this a bash after work tomorrow in the name of science and fannying around!
Does anybody fancy sticking Quadrant benchmark results up in the mean time?

Installing now and doing 1 click lag fix 4.0+SU Access+89 apps so i can post in 30 min my quadrant results

Richthofen said:
Maybe.
Click to expand...
Click to collapse
I think everyone wants a froyo firmware, any chance of that happening?

Just flashed. Looks identical to JM2. I cannot try many things now (it's 2 AM here ).
You may want to add that spanish carrier Movistar is also supported. Detected the SIM and connected. Calls working. Wifi working. GPS unknown, I'm not going outside to try it now...

vcespon said:
You may want to add that spanish carrier Movistar is also supported. Detected the SIM and connected. Calls working.
Click to expand...
Click to collapse
Yes, CSC is not critical for the phone.
It just contains (possible) operator customizations, country specific operator infos (APN´s etc) and sets preferences like default language.
Identical to JM2?!
Turn off the phone and you´ll see a difference

There is any difference compared to JM5?
What about GPS and lag?

Wait, don't tell me this has a built-in lag fix?!

cba1986 said:
There is any difference compared to JM5?
What about GPS and lag?
Click to expand...
Click to collapse
Same Question

Improvments
I understand that some tweaks were put into one of the latest roms (forgotten the name) such as improved ram management and better battery life to name a few. Are this improvements also incoroprated into this rom? And would you be able to give a froyo release at the end of the month, i mean samsung should have deffinitly completed the rom by the last week of August if they want to test it and allow carries to mod it in time for end of september... right?

Quadrant says:
863
No lagfix

Just flashed and there's definitely an improvement in apploading speed(running 15 apps doesn't result in a black screen anymore when launching new ones). This is without any lagfix applied(was running jm5 + oneclick 2-3). Gonna try the gps now!

Numbers means anything. JH2 also gets that numbers and people reports that this FW it's much more fluid.

jim_panse said:
Quadrant says:
863
No lagfix
Click to expand...
Click to collapse
Quadrant scores mean zilch. Had 2358 before and the phone ran noticeably slower than my friend's desire.

BTU Firmware won't allow CSC Secret Code

Hello everyone, I just got my G960F/DS and it originally came with SIN CSC so being I am in Canada, I tried to load the UK firmware to try and get VoLTE and WiFi calling to work. I was able to on SIN CSC, to select BTU firmware from the phone app using the secret code, but stupid me didn't discover the one thread about to use XEU to get the WiFi calling option and now I am stuck on BTU CSC without the option to go to XEU. I read if you use ODIN to go on H3G and then use ODIN back to a OXM based ROM, that it will go by default to XEU, but for me it just kept the BTU CSC after the firmware was flashed.
Does anyone have any suggestions? As mentioned above, no secret codes on the phone app I read to access the CSC changer or the advanced phone info is currently working. I can't flash a custom ROM as I am on the 7 days wait so wondering if it would be best to wait the 7 days and just flash a custom TW ROM with the CSC I want?
Thanks.

You can't switch between XEU and BTU easily, if at all as they are MultiCSC and one contains the other, BTU contains XEU
Not sure why your phone would default to BTU if you were flashing XEU from a completely different CSC not included though unless your phone was originally BTU
Make sure you're using CSC and not HOME_CSC when you flash and remove the SIM for the flash
Flash back to SIN then to XEU using CSC in ODIN both times

*Detection* said:
You can't switch between XEU and BTU easily, if at all as they are MultiCSC and one contains the other, BTU contains XEU
Not sure why your phone would default to BTU if you were flashing XEU from a completely different CSC not included though unless your phone was originally BTU
Make sure you're using CSC and not HOME_CSC when you flash and remove the SIM for the flash
Flash back to SIN then to XEU using CSC in ODIN both times
Click to expand...
Click to collapse
Yeah the phone originally showed SIN as the product code for Singapore. When I got the phone, I did originally try flashing the G960FXXU1BRF8 BTU ROM with the CSC (not HOME_CSC) with ODIN, but after setting up the phone, the CSC stayed at SIN. The only way I was able to set it to BTU was using the phone secret code of '*#272*IMEI#*' which now being on BTU, that no longer works to switch to XEU. Is there any special steps I should be following to switch CSC's properly? I did the following so far to try and switch
- Flashed H3G BL, AP, CP, CSC using ODIN (kept default ODIN options with SIM card and SD Card removed)
- Let the ROM boot up and went back to Download mode to flash the OXM BL, AP, CP, CSC
- After the firmware was flashed in ODIN, booted into recovery mode to factory reset/wipe cache.
- Inserted SIM Card and SD Card and let the ROM boot which indicated BTU as active CSC and Product Code.
Hope these details help. Do you know if the SIN firmware is a non-OXM or is it part of the OXM-multi CSC?

Andrw0830 said:
Yeah the phone originally showed SIN as the product code for Singapore. When I got the phone, I did originally try flashing the G960FXXU1BRF8 BTU ROM with the CSC (not HOME_CSC) with ODIN, but after setting up the phone, the CSC stayed at SIN. The only way I was able to set it to BTU was using the phone secret code of '*#272*IMEI#*' which now being on BTU, that no longer works to switch to XEU. Is there any special steps I should be following to switch CSC's properly? I did the following so far to try and switch
- Flashed H3G BL, AP, CP, CSC using ODIN (kept default ODIN options with SIM card and SD Card removed)
- Let the ROM boot up and went back to Download mode to flash the OXM BL, AP, CP, CSC
- After the firmware was flashed in ODIN, booted into recovery mode to factory reset/wipe cache.
- Inserted SIM Card and SD Card and let the ROM boot which indicated BTU as active CSC and Product Code.
Hope these details help. Do you know if the SIN firmware is a non-OXM or is it part of the OXM-multi CSC?
Click to expand...
Click to collapse
You can check which CSCs are included in the one you are currently running using this app
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
OXM-multi CSC includes SIN so yea that'll be why it didn't change
OXM-multi CSC includes
ACR AFG AFR ARO ATO AUT BGL BNG BRI BTC BTU CAC CAM CHO COO DBT DKR ECT EGY EON ETL EUR GLB ILO INS ITV KSA LAO LUX LYS MID MM1 MWD MYM NEE NPL ORX PAK PHE PHN ROM SEB SEE SEK SER SIN SKZ SLK SMA STH THL THR TMC TPA TPH TTT TUN TUR WTL XEF XEH XEO XEU XFE XME XSG XSP XTC XXV ZTO
You'd have to flash to one not included first
(But make sure the bootloader version matches and is not higher than the one you want to flash back to or you'll be stuck)
Download mode > BL:x (x = version number)
Firmware BL version is here (G960FXXU1BRF8) << Version 1

*Detection* said:
You can check which CSCs are included in the one you are currently running using this app
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
OXM-multi CSC includes SIN so yea that'll be why it didn't change
OXM-multi CSC includes
ACR AFG AFR ARO ATO AUT BGL BNG BRI BTC BTU CAC CAM CHO COO DBT DKR ECT EGY EON ETL EUR GLB ILO INS ITV KSA LAO LUX LYS MID MM1 MWD MYM NEE NPL ORX PAK PHE PHN ROM SEB SEE SEK SER SIN SKZ SLK SMA STH THL THR TMC TPA TPH TTT TUN TUR WTL XEF XEH XEO XEU XFE XME XSG XSP XTC XXV ZTO
You'd have to flash to one not included first
(But make sure the bootloader version matches and is not higher than the one you want to flash back to or you'll be stuck)
Download mode > BL:x (x = version number)
Firmware BL version is here (G960FXXU1BRF8) << Version 1
Click to expand...
Click to collapse
Thanks for providing this. Do you know why when I flashed the H3G firmware which is a non-OXM CSC, why flashing to a OXM after, caused the Sales and Product Code to stay BTU? As described in my last post, I flashed the BL, AP, CP and CSC for H3G and it did boot, but I immediately shut off the phone and installed the OXM firmware after it did. Does my SIM Card have to be inserted during your steps? Lastly not sure if it's true but I read that whatever your product code is, the OXM CSC will apply that CSC during the first boot. So I have to find a way to change the Product Code without using the phone secret code since that no longer works on BTU firmware.
I usually do my research before doing anything like this to prevent issues and have installed custom ROMs, changed CSC since the S2 days, but this has me stumped.

Andrw0830 said:
Thanks for providing this. Do you know why when I flashed the H3G firmware which is a non-OXM CSC, why flashing to a OXM after, caused the Sales and Product Code to stay BTU? As described in my last post, I flashed the BL, AP, CP and CSC for H3G and it did boot, but I immediately shut off the phone and installed the OXM firmware after it did. Does my SIM Card have to be inserted during your steps? Lastly not sure if it's true but I read that whatever your product code is, the OXM CSC will apply that CSC during the first boot. So I have to find a way to change the Product Code without using the phone secret code since that no longer works on BTU firmware.
I usually do my research before doing anything like this to prevent issues and have installed custom ROMs, changed CSC since the S2 days, but this has me stumped.
Click to expand...
Click to collapse
If I had to guess, (if your phone is 2nd hand) then the original CSC was actually BTU and not SIN, SIN was flashed before it was sold
If that's not the case, then I'd guess that BTU always defaults from OXA Multi unless your CSC is included, which would mean you do not know your original CSC and SIN was still flashed before sale
Otherwise I have no idea, I haven't tried changing my CSC on the S9, I know with the S7 I had before this, the same problem occurred trying to switch between XEU and BTU, my S7 was XEU and refused to switch to BTU
SIM only needs to be removed for the initial flash and first boot from what I know, otherwise it can use the SIM to work out the original CSC

*Detection* said:
If I had to guess, (if your phone is 2nd hand) then the original CSC was actually BTU and not SIN, SIN was flashed before it was sold
If that's not the case, then I'd guess that BTU always defaults from OXA Multi unless your CSC is included, which would mean you do not know your original CSC and SIN was still flashed before sale
Otherwise I have no idea, I haven't tried changing my CSC on the S9, I know with the S7 I had before this, the same problem occurred trying to switch between XEU and BTU, my S7 was XEU and refused to switch to BTU
SIM only needs to be removed for the initial flash and first boot from what I know, otherwise it can use the SIM to work out the original CSC
Click to expand...
Click to collapse
Yeah I kind of figured. Phone was brand new and the Samsung seal wasn't broken but when I did boot it up for the first time, I didn't get the setup screen. I know with my S5 my product code was switched and even when flashing Canada's CSC, with my SIM installed, it would default to a different CSC then what I needed. The only way to change it was using the Phone's Secret code. It's a shame that it's not easier to change the product code so that the proper CSC is applied.
Does anyone who has the BTU product code have the same issue with the secret code not working? I am on the same version of ROM that I was on before my CSC got changed to BTU so I know it's not the ROM version. Every guide I found regarding flashing CSC has been to get to BTU not to get to XEU so anyone who can shed light on this? In the meantime, I will wait the 7 days for OEM Unlock to appear.

So I got the OEM unlock last night after 154 hours uptime but it was 7 days since signed into Samsung account and I did try XEU and INS CSC but no voLTE. Was wondering if anyone on Rogers or any of the Canadian carriers have gotten voLTE or wifi calling to work? In the past I know INS CSC did have voLTE for the s7 when it was a S8 port but so far trying INS, SIN, BTU, or XEU CSC hasn't worked. I am happy with RR AOSP right now, but wanted any suggestions as there must be one CSC that works.

Andrw0830 said:
So I got the OEM unlock last night after 154 hours uptime but it was 7 days since signed into Samsung account and I did try XEU and INS CSC but no voLTE. Was wondering if anyone on Rogers or any of the Canadian carriers have gotten voLTE or wifi calling to work? In the past I know INS CSC did have voLTE for the s7 when it was a S8 port but so far trying INS, SIN, BTU, or XEU CSC hasn't worked. I am happy with RR AOSP right now, but wanted any suggestions as there must be one CSC that works.
Click to expand...
Click to collapse
Hi Andrw0830,
Can you please advise how you did manage to change the CSC back as required to XEU? I also by mistake changed my CSC from STH to BTU via secret code and now the secret code is not working and I am stuck with BTU CSC. Does the OEM unlock has to do anything with it ? Appreciate your feedback ? Thanks

ksantoshh said:
Hi Andrw0830,
Can you please advise how you did manage to change the CSC back as required to XEU? I also by mistake changed my CSC from STH to BTU via secret code and now the secret code is not working and I am stuck with BTU CSC. Does the OEM unlock has to do anything with it ? Appreciate your feedback ? Thanks
Click to expand...
Click to collapse
I waited the 7 days to enable OEM unlock. Then I installed TWRP and installed the devbase ROM which has the choice to change the CSC. You do have to copy the options.prop that's included in the ROMs zip to your SD card before flashing the ROM. Then open up the file and there is a line for CSC, change it from KCSC to XEU. Save the file and install the ROM which will install the CSC you chose and the first boot will have it enabled.

Andrw0830 said:
I waited the 7 days to enable OEM unlock. Then I installed TWRP and installed the devbase ROM which has the choice to change the CSC. You do have to copy the options.prop that's included in the ROMs zip to your SD card before flashing the ROM. Then open up the file and there is a line for CSC, change it from KCSC to XEU. Save the file and install the ROM which will install the CSC you chose and the first boot will have it enabled.
Click to expand...
Click to collapse
Thanks a lot for your quick response and guidance. I was looking at options where I do not have to necessarily flash a custom ROM and somehow change the CSC. Nonetheless, can you please advise further if the KNOX count/warranty is void after you performed this flashing and is there a way to reset these counters ? Thanks again.

ksantoshh said:
Thanks a lot for your quick response and guidance. I was looking at options where I do not have to necessarily flash a custom ROM and somehow change the CSC. Nonetheless, can you please advise further if the KNOX count/warranty is void after you performed this flashing and is there a way to reset these counters ? Thanks again.
Click to expand...
Click to collapse
Unfortunately, once you flash a custom recovery, the KNOX is tripped and there is no way to reset.

ok thanks for your feedback. I will go and check with Samsung Service center

Problems in LTE activation (different regions)

Hello friends,
I'm from Brazil and I bought a LTE Galaxy Watch in Germany, exactly the same version (Sm-R805F) used in Brazil. However when I went to my mobile company to activate the e-sim it was not possible. When the system ask to read a QR code, in the mobile networks' activation process, a message of error appears ("It's not possible to conect this mobile"). Does anyone know why and how to fix it?

Can you check this Code...
Code:
*#1234#
Seems DIFFERENT Software crap exists... so different Profiles...
Code:
OXX
OXA
Check your CSC ...
OXA could be inside German Version... and OXX is maybe for Brazil...
Best Regards

adfree said:
Can you check this Code...
Code:
*#1234#
Seems DIFFERENT Software crap exists... so different Profiles...
Code:
OXX
OXA
Check your CSC ...
OXA could be inside German Version... and OXX is maybe for Brazil...
Best Regards
Click to expand...
Click to collapse
Thank you very much!
I did it and the CSC is OXA (German version).
How can I change it to OXX?
PS: I did as they recomended here (https://forum.xda-developers.com/smartwatch/gear-s3/guide-how-to-change-gear-s3-r760-csc-t3784226 ) but theres no Brazilian code nor OXX.

OXX and OXA are """group"""
OXA contains minimum DBT CSC... for Germany
You can NOT change from OXA to OXX... because the config files not inside...
Your Link shows only way to change existing CSC inside flashed CSC file...
Example...
I have Firmware files... from OXX region...
Code:
CSC_[B]OXX[/B]_R805FOXX1BRI4_usr.tar.md5
You can unpack and extract with 7Zip... csc.img file.
Folder preconfig have 8 folderS with 7 CSC... DEF means Default IMHO...
Code:
BRI
TGY
VAU
XNZ
XSA
XSG
XSP
XSP is Singapore...
For the others I am tooo lazy... forgotten... use Google...
I have NO idea if it is an good idea to try to flash with netOdin such CSC files... or complete Firmware of OXX region.
Samsungs funny Security...
Best Regards
Edit 1.
I have tried to identify Brzil via Google search...
For me it looks no CSC inside for Brazil...
I have NO idea if SM-R805F is for Brazil market...
Edit 2.
Okidoki... Google search leads to this:
https://www.samsung.com/br/support/model/SM-R805FZSAZVV/
So looks like exists for Brazil... and you can see Sales Code ZVV it is in Product Code...
Code:
SM-R805FZSA[B]ZVV[/B]
IMHO 3 region groups... OXX OXA and ?
Firmware for Brazil seems not leaked... with ZVV inside...
Edit 3.
Firmware for SM-R805F for Brazil looks like this:
Code:
R805FXXU1CRK7/R805F[B]OWO[/B]1CRK7/R805FXXU1CRK7
So OWO is Region Code... for Brazil...
IMHO OWO package have ZVV Sales Code/CSC inside... for Brazil.
Edit 4.
My fault...
Code:
R805FXXU1DSC7_Tizen_4File_Multi CSC ([B]OWO[/B]).rar
Leaked and available...
But still no idea if this helps you... because dangerous to flash... Sams..g Security could prevent success...

adfree said:
Edit 4.
My fault...
Code:
R805FXXU1DSC7_Tizen_4File_Multi CSC ([B]OWO[/B]).rar
Leaked and available...
But still no idea if this helps you... because dangerous to flash... Sams..g Security could prevent success...
Click to expand...
Click to collapse
Hi,
Can you list the available CSC's within the OWO version ?
I wasn't able to find it for download to check by myself..

@Nocturney
Region OWO Firmware contains these CSC:
Code:
COM
ZTA
ZTO
ZVV
Best Regards

I've been reading the post, but I'm a little lost. I do not know what to do. I have a R815 Vodafone Germany version, and I want to activate it for movistar Spain, but I receive the error "It's not possible to conect this mobile". The data of my watch are the following:
AP: R815FXXU1ARH5
CP: R815FXXU1ARH5
CSC: R815FOXA1ARH5
With the SDB utility I have accessed a hidden menu on the watch and I changed the original CSC VD2 to XEC, or at least I thought so ... I think VD2 is Vodafone Germany, and XEC is Movistar Spain (the company that I have on my mobile phone). Samsung Pay works, but LTE is impossible to configure ("It's not possible to conect this mobile")
It is possible to get a different firmware and flash it?... or how can I get to configure an esim (lte) from movistar españa?

adfree said:
@Nocturney
Region OWO Firmware contains these CSC:
Code:
COM
ZTA
ZTO
ZVV
Best Regards
Click to expand...
Click to collapse
Awesome, Thanks for the info

Hey guys, I was reading this post and I have a problem a little different of you.
I bought a Galaxy Watch from The USA, LTE version (R805U) but I live in Brazil, I went to the phone company (VIVO) to try able the LTE (eSim) function but they said to me that it is impossible because only the R805F works here. My question is. Can I change the firmeware from 805U to 805F and it will works LTE here ?

secawan said:
I've been reading the post, but I'm a little lost. I do not know what to do. I have a R815 Vodafone Germany version, and I want to activate it for movistar Spain, but I receive the error "It's not possible to conect this mobile". The data of my watch are the following:
AP: R815FXXU1ARH5
CP: R815FXXU1ARH5
CSC: R815FOXA1ARH5
With the SDB utility I have accessed a hidden menu on the watch and I changed the original CSC VD2 to XEC, or at least I thought so ... I think VD2 is Vodafone Germany, and XEC is Movistar Spain (the company that I have on my mobile phone). Samsung Pay works, but LTE is impossible to configure ("It's not possible to conect this mobile")
It is possible to get a different firmware and flash it?... or how can I get to configure an esim (lte) from movistar españa?
Click to expand...
Click to collapse
Is not to you to do'it...
You need to call the operatório, in this case, Movistar and subscribe for the service and they activate the eSim...
Sent from my Samsung SM-G975F using XDA Labs

Hi had same problem
Hello mate
I bought Samsung Galaxy watch when I was on holidays in Greece as in UK the LTE version was only with contract on EE. As I'm using Vodafone UK, I got the Qr Code for the esim but Samsung neither Vodafone could help me to make it work. Finally I make It work but my self, because my Samsung Galaxy watch is from Greek region I try to activate my Vodafone uk esim with a Greek sim network in my mobile device and it's worked perfectly, even when I put back my Vodafone uk sin on my mobile.
Hope that helps you.

MrNtrev said:
Hello mate
I bought Samsung Galaxy watch when I was on holidays in Greece as in UK the LTE version was only with contract on EE. As I'm using Vodafone UK, I got the Qr Code for the esim but Samsung neither Vodafone could help me to make it work. Finally I make It work but my self, because my Samsung Galaxy watch is from Greek region I try to activate my Vodafone uk esim with a Greek sim network in my mobile device and it's worked perfectly, even when I put back my Vodafone uk sin on my mobile.
Hope that helps you.
Click to expand...
Click to collapse
Hi, could you elaborate on how you did that? I want to buy the silver LTE version from Hong Kong because that colour is not sold in Singapore, and it would be great if I could get the LTE working.

Rbs_fael said:
Hey guys, I was reading this post and I have a problem a little different of you.
I bought a Galaxy Watch from The USA, LTE version (R805U) but I live in Brazil, I went to the phone company (VIVO) to try able the LTE (eSim) function but they said to me that it is impossible because only the R805F works here. My question is. Can I change the firmeware from 805U to 805F and it will works LTE here ?
Click to expand...
Click to collapse
Sou do Brasil tambem e estou com o mesmo problema e duvida. Vocë conseguiu resolver?

Recommended Firmware for Unbranding a Samsung Galaxy S20+ (SM-G985F)

Hello community!
I recently bought a Samsung Galaxy S20+ (SM-G985F) which is carrier branded and sim locked. I am looking to remove the carrier branding by using a unbranded firmware. I am trying to find an unbranded firmware that will not affect the functionalities of the phone ( VoLTE, VoWiFi etc..) . Would this be done by finding a firmware with same PDA but different CSC?
Current Branded Firmware:
Version G985FXXU3ATG4 / G985FOWA3ATG4 / G985FXXU3ATG4
Product Code: PGU
Would this firmware work?
Product code LUX
PDA G985FXXU3ATG4
CSC G985FOXM3ATG9
Thanks in advance for your help!

@servenaya
if you have a sim card of Guatemala and you want to keep VoLTE, VoWiFi etc.. for this country
install Version PDA G985FXXU3ATG4-CSC G985FOXM3ATG9
and change your CSC to GTO ( with préconfiguration for TIGO_CGU , PCW_PA and Claro_DR )
LUX have only préconfiguration for Luxemburg ( Proximus , POST , Tango , Telenet , Orange B and LUX )
regards

yakapa40 said:
@servenaya
if you have a sim card of Guatemala and you want to keep VoLTE, VoWiFi etc.. for this country
install Version PDA G985FXXU3ATG4-CSC G985FOXM3ATG9
and change your CSC to GTO ( with préconfiguration for TIGO_CGU , PCW_PA and Claro_DR )
LUX have only préconfiguration for Luxemburg ( Proximus , POST , Tango , Telenet , Orange B and LUX )
regards
Click to expand...
Click to collapse
@yakapa40, thank you! This information is very helpful. I do have a Claro Guatemalan sim and even though the carrier does not support VoLTE, or VoWifi, I would like to keep this features in case they implement them in the future. I did find a firmware with the recommended PDA and CSC (Country South East Europe, Product code: SEE, PDA: G985FXXU3ATG4, CSS: G985FOXM3ATG9). Would this firmware work? From what understand, I would have to first flash this firmware, then change de CSC with Samkey to GTO and lastly, factory restore the phone. Is this correct?
Also, would you recommend using Samkey to perform a carrier unlock before changing the CSC or could I do it later on? I read that Samkey only works for phones that dont ask for unlock code. Mine does ask for a code when I insert another carrier's sim.
Thanks in advance for your help!

save all your data
install new firmware
you have a free apk here to change the CSC:
https://forum.xda-developers.com/showpost.php?p=82858645&postcount=37

yakapa40 said:
save all your data
install new firmware
you have a free apk here to change the CSC:
https://forum.xda-developers.com/showpost.php?p=82858645&postcount=37
Click to expand...
Click to collapse
@yakapa40, Thank you once again. Just want to make sure that the firmware mention before is the best one to use? I have attached the software information from my phone. Please let me know your opinion.

yes all is ok with your firmware
PGU:
GTO:

yakapa40 said:
yes all is ok with your firmware
PGU:
GTO:
Click to expand...
Click to collapse
@yakapa40 Thank you for your help. You are extremely knowledgeable on this topic! To be honest, I just realize how little I know about flashing even though I've been doing it since 2012. I feel like I understand firmware flashing less than I did before.
I just have a last question. If I flash the firmware with a CSC NEE, and than do the CSC change to GTO, which CSC will be used for future OTA updates? What I mean is, if there is a new NEE firmware will I get it, or will I have to wait for a new GTO update? Sorry, I am little confused with all of this.

G985F OXM is a multi CSC so if you flash the firmware with a CSC NEE , you will get XEF CSC by default
, and when you change to GTO you will get GTO OTA updates
https://forum.xda-developers.com/galaxy-s20/how-to/s20-g985f-firmwares-t4060279

yakapa40 said:
G985F OXM is a multi CSC so if you flash the firmware with a CSC NEE , you will get XEF CSC by default
, and when you change to GTO you will get GTO OTA updates
https://forum.xda-developers.com/galaxy-s20/how-to/s20-g985f-firmwares-t4060279
Click to expand...
Click to collapse
@yakapa40, I was finally able to flash the phone. I followed the steps and got the GTO CSC and the unbranded firmware working! Thank you for helping me throughout the whole process. The only down side was that I still lost the VoLTE and VoWifi options. When I look at the Sim Card Status menu, the IMS registration Status is "not registered". :crying:

CSC mess... why has it become so difficult?

Hello Community,
I have always bought factory unlock international versions of Samsung galaxy S phones from Amazon and used it outside the US (in Central America). The last time I flashed a phone was in the Samsung S4 period where a few friends had carrier branded phones, which I helped them unbranded by flashing the TTT (Trinidad and Tobago) firmware, since the PDA and CSC was the same as mine. It never gave me any issues and therefore, I never really messed with CSC before. It was easy and simple!
I recently returned to Samsung ecosystem but this time I bought a S20+ (SM-G985F) carrier branded and locked phone (Claro Guatemala). It's clear that things have gotten way complicated now.
Version: G985FXXU3ATG4 / G985FOWA3ATG4 / G985FXXU3ATG4
CSC: PGU
Thanks to another post, I was instructed to able to flash a different firmware to unbrand it. I was also instructed to change CSC to GTO, so I would not loose VoWIFI and VoLTE. Apparently now just flashing the firmware does not change the CSC, there is another process for that. I performed the change but still lost the options (although my carrier still doesn't support it).
version: G985FXXU3ATG4 / G985FOXM3ATG9 / G985FXXU3ATG4
CSC: GTO
I've been trying to understand how CSC works but I've been reading several contradictions. Some say that if CSCs don't match you might not get OTAs. Other say that that doesn't matter. Why couldn't I just flash the TTT as I've done before? Why did I have to change my CSC to GTO? What if I change my CSC to TPA but use it in Guatemala, would I still get OTA updates? If my device is single sim, why does my CSC GTO/GTO,GTO/PGU as a dual sim?
Who can give me a definite explanation on how to choose a correct CSC firmware? HELP!

I'm going through the same nightmare...

servenaya said:
Hello Community,
I have always bought factory unlock international versions of Samsung galaxy S phones from Amazon and used it outside the US (in Central America). The last time I flashed a phone was in the Samsung S4 period where a few friends had carrier branded phones, which I helped them unbranded by flashing the TTT (Trinidad and Tobago) firmware, since the PDA and CSC was the same as mine. It never gave me any issues and therefore, I never really messed with CSC before. It was easy and simple!
I recently returned to Samsung ecosystem but this time I bought a S20+ (SM-G985F) carrier branded and locked phone (Claro Guatemala). It's clear that things have gotten way complicated now.
Version: G985FXXU3ATG4 / G985FOWA3ATG4 / G985FXXU3ATG4
CSC: PGU
Thanks to another post, I was instructed to able to flash a different firmware to unbrand it. I was also instructed to change CSC to GTO, so I would not loose VoWIFI and VoLTE. Apparently now just flashing the firmware does not change the CSC, there is another process for that. I performed the change but still lost the options (although my carrier still doesn't support it).
version: G985FXXU3ATG4 / G985FOXM3ATG9 / G985FXXU3ATG4
CSC: GTO
I've been trying to understand how CSC works but I've been reading several contradictions. Some say that if CSCs don't match you might not get OTAs. Other say that that doesn't matter. Why couldn't I just flash the TTT as I've done before? Why did I have to change my CSC to GTO? What if I change my CSC to TPA but use it in Guatemala, would I still get OTA updates? If my device is single sim, why does my CSC GTO/GTO,GTO/PGU as a dual sim?
Who can give me a definite explanation on how to choose a correct CSC firmware? HELP!
Click to expand...
Click to collapse
Isn't the SM-G985F a Multi CSC device? Try this, go to "Settings" then "About phone". Write down your IMEI Number. Open dialer and enter *#272*IMEInumber# (In the thread replace IMEInumber with your actual IMEI Number). Press dial, you should see a screen with the list of available CSC codes for your device. Select the CSC that you want and tap the Install option.

servenaya said:
Hello Community,
I've been trying to understand how CSC works but I've been reading several contradictions. Some say that if CSCs don't match you might not get OTAs. Other say that that doesn't matter. Why couldn't I just flash the TTT as I've done before? Why did I have to change my CSC to GTO? What if I change my CSC to TPA but use it in Guatemala, would I still get OTA updates? If my device is single sim, why does my CSC GTO/GTO,GTO/PGU as a dual sim?
Who can give me a definite explanation on how to choose a correct CSC firmware? HELP!
Click to expand...
Click to collapse
I'm also new to the CSC concept, and have been looking into its function. I would recommend checking out these links for a good overview.
(I'm a new user and cannot post external links, you'll have to use a search engine to find these. If a MOD wants to change these to links, feel free!)
1 - Droid Views dot com- "Difference Between CSC and HOME_CSC (Samsung Firmware)"
2 - Droid Views dot com - "Change CSC on Samsung Devices – Samsung CSC Codes"
3 - Samsung dot com - Tech Talk - "What’s CSC on Samsung?"
4 - Android dot stackexchange dot com - "How to find my device's CSC (Country Specific Code)"
5 - https://forum.xda-developers.com/showpost.php?p=72198850&postcount=21
6 - https://forum.xda-developers.com/showpost.php?p=72321531&postcount=28
7 - technastic dot com - "CSC or HOME CSC? Which File You Should Flash in Odin"
8 - https://forum.xda-developers.com/showthread.php?t=1988202
9 - https://forum.xda-developers.com/showthread.php?t=2033894
10 - https://forum.xda-developers.com/showthread.php?t=1356325
11 - Android dot stackexchange dot com - "What do the numbers and letters in the Samsung Firmware mean?"
12 - https://forum.xda-developers.com/galaxy-s3/general/csc-codes-t2090739
What follows are my findings and my attempt to 'put it all together'.
Samsung Firmware Naming Convention
See [10] and [11]
What is a CSC?
Samsung CSC refers to the Country Specific (Product) Code. This identifies the region and carrier for which the device is configured [1,3].
This includes [7]:
Carrier branding: A CSC may be country or carrier-specific. Samsung releases the same model of a smartphone to Tab with different CSCs. For instance, if you use an unlocked or unbranded Samsung Galaxy phone in the UK, its CSC would be BTU. However, if your device is locked to a network operator, it could be VOD (Vodafone), TMU (T-Mobile), ORA (Orange), XEU (EE & Three), etc.
System Languages: These include the availability of the popular languages used in a geographical area. For example, if you own a Samsung phone in Mexico and flash the firmware meant for India with INS as CSC, you won’t be able to set Spanish, Nahuatl, or Mixtec as your phone’s system language and keyboard.
Localizations: Samsung ships its devices with geo-specific or bloat apps relevant to a country or region. Localization also determines the calendar settings and local festivals.
APN Settings: Access Point Name settings include all configurations to make a mobile device work with the network carriers of a region or country. Without these configurations, you may not be able to enjoy seamless GSM, GPRS, 3G or 4G mobile networks.
Samsung FUS: CSC also contains key info to help Samsung’s Firmware Update Server to connect to the correct update channel and roll out the proper software update to your Galaxy device via OTA.
Deep dive:
Historically, Samsung had one CSC folder on the device [8], located at /system/csc. This folder contained different XML files used to configure the device.
Code:
/system/csc
features.xml
language.xml
others.xml
customer.xml
The supported configuration options for these files have been extensively documented by other users [9].
Presently, there are two flavors of CSC files CSC and HOME_CSC. Flashing CSC performs a factory reset of the device; wiping all third-party apps, data and settings [7]. HOME_CSC is used to reinstall the firmware or updating the system, retaining apps, data, and settings.
Examining the current contents of a HOME_CSC file shows the structure has changed.
Code:
HOME_CSC_OMC_OXM_G985FOXM3ATG9_CL18862671_QB33041563_REV01_user_low_ship_MULTI_CERT/
meta-data
cache.img.lz4
optics.img.lz4
prism.img.lz4
The three image files correspond to directories found on the device root (using adb).
Code:
/cache/
backup
backup_stage
lost+found
lsb
magisk
magisk.log
magisk.log.bak
recovery
/optics/
configs
/prism/
HWRDB
app
etc
lost+found
media
priv-app
sipdb
Buried within the optics folder, we find XML files similar to the original design.
Code:
/optics/configs/carriers/single/TPA/conf
cscfeature.xml
cscfeature_network.xml
customer.xml
omc.info
How do I find and interpret my CSC?
You check your CSC by going to Settings > About Phone > Software Information > Service Provider SW Version. According to [1] you should see the following, depending on your phone's SIM capacity.
CSC Format:
AAA/BBB/CCC (Single SIM Models)
AAA/BBB,BBB/CCC (Dual SIM Models)
Click to expand...
Click to collapse
Where, according to [5]
AAA is the current CSC
BBB is the recommed CSC for your SIM (if this CSC is inside your current Multi-CSC)
CCC is the factory CSC of your phone and can´t be changed
Click to expand...
Click to collapse
Some phone info applications call these the original (CCC), firmware (AAA), and active (BBB) CSCs. For example, my SM-G985F shows
Code:
SAOMC_SM-G980F_OXM_TPA_QQ_0006
...
TPA/TPA,TPA/TPA
Which tells me that the phone was manufactured for Panama, has the Panama firmware and the recommended SIM CSCs are both for Panama. I know this because the list of CSC country codes is well documented [12].
NOTE: I came across multiple sources online that say the SIM CSC will change depending on the SIM card you have inserted. For example, [1] states
When you switch to a SIM card from a different country, your device will attempt to modify the SIM CSC. If the operation is successful, you’ll receive a popup asking to align the new information with the active CSC. This will effectively modify the configuration region, but the process requires a factory reset.
Click to expand...
Click to collapse
But this may not be true. I am in the USA using a local provider and was never prompted as described.
What does each CSC do?
So we have the three different CSCs, each of which could be responsible for configuring different parts of the phone.
Firmware
SIM
Original (factory)
I would think that the original CSC is only there to identify the original factory firmware, and is not configuring anything on the phone. The firmware CSC should tell me the current firmware loaded and the SIM CSC does ???
I will continue to look into this over the next few days. If anyone can contribute more information it would be very helpful.