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.

Need Specific Firmare CSC combination

Hi All
Im looking for a specific CSC file if any of you have it plz could you upload it for me so i could DL it from somewhere
The CSC file i need is for the XFV region
From what i could tell in version histories there are only a few of them out but i would like to see if there is a easier way to fix the you cannot update the firmware issue so we could probably document it properly.
The firmware dont really matter as i have most of them from samfirmware but i would like to replace the CSC to see if that would fix the problem.
This is for experimental purposes only and in no way will i or have a need to downgrade to a official firmware but seeing as i live in SA its hard to get the local CSC if everything is in the XEU region
Please check if you have one and let me know. I have a treory in terms of assisting ppl to get back on track with official firmware if they want to upgrade that way seeing as Bada 2.0 is close and a lot of ppl will want to go to the official release.

Have you tried the new Kies 2 hack found in the galaxy forum? it works well with bada due to there are all on the same server. I dont know yet how to find it, the forum is to huge.

larioteo said:
Have you tried the new Kies 2 hack found in the galaxy forum? it works well with bada due to there are all on the same server. I dont know yet how to find it, the forum is to huge.
Click to expand...
Click to collapse
No idea. I was looking around but the CSC file still reffers in registry to the Kies software. The problem with that is that your geographical location gets picked up by the Kies software and if that dont match your CSC you wont be able to trick it in updating your FW over Kies.
I want to test that and see if that makes a difference because your productcode can also still be changed in the registry but you need the correct CSC
If it works everyone that want to manually flash has a 5 step fix to revert to original. Im just testing a theory
Please see if you can find that and share it Thanks

That with geographical is not true, i am using german firmwares and i can update through kies in austria, already flashed korean versions and everything works.
Manually you cannot change the settings, maybe your firmware configuration is mismatched.

larioteo said:
That with geographical is not true, i am using german firmwares and i can update through kies in austria, already flashed korean versions and everything works.
Manually you cannot change the settings, maybe your firmware configuration is mismatched.
Click to expand...
Click to collapse
Last night i tested this and flashed back to XXJEG witch was one of the 1st firmwares out and knowing there is a update after that it still stated the same that the FW cant be updated. I have also tested multiple CSC FW combinations and cant get it to simulate my region to be able to update from Kies
Currently my Config looks like this
FW: S8500XXJL2
CSC: S8500OXDJL1
I installed JID and updated to JL2 witch atm is the most stable build i could find.

I can give you my xxji5 multi which contains every csc for open europe.
It is one combilation that i have made, in this time slyfer (my firmware downloader) have given me access to every samsung firmware.
It should solve your problems A bada 1.2 firmware with all csc i don't have, after the JL2 the downloader stopped to work, sorry.
You can choose what you want.

larioteo said:
I can give you my xxji5 multi which contains every csc for open europe.
It is one combilation that i have made, in this time slyfer (my firmware downloader) have given me access to every samsung firmware.
It should solve your problems A bada 1.2 firmware with all csc i don't have, after the JL2 the downloader stopped to work, sorry.
You can choose what you want.
Click to expand...
Click to collapse
OMG dude you are a legend
Add me on skype: bubblethe1
I need the last 3 on that list as they are all to my country area
The XFA, XFE and XFM of you could just upload them somewhere so i could DL them if you dont mind

Here is the list i could use in terms of CSC
South Africa.
XFA = SOUTH AFRICA
XFC = SOUTH AFRICA
XFM = SOUTH AFRICA
XFV = SOUTH ARFICA
XFE = SOUTH AFRICA

Hello toxicdust, you can use the Kies Registry Patcher as suggested by larioteo to install any firmware of your choice from kies.
It works and it's very simple to use. Like larioteo, I have also installed several firmwares from different regions from kies without problems.
I will give you a short tutorial on how to do this. You can also save the firmware that kies uses when upgrading your phone by extracting the files.
Now here is the tutorial. A screenshot is also attached.
HOW TO USE KIES PATCHER TO UPGRADE WAVE
1. Launch Samsung Kies.
2. Connect phone in kies mode (make sure phone is detected by kies).
3. With phone connected to kies, launch Kies Registry Patcher as Administrator
(Note: If you have previously connected more than one phone in kies,
you will be prompted that you need to cleanup regustry.
Accept/say yes, and then continue from nº 3 above, that is, start over again).
In kies Registry patcher,
- Click on the menu "Basic"
- In the option, "Enable Spoof" select "True"
- In the option, "Spoof Product Code as" Select "XFC" (e.g South Africa).
- In the option, "Spoof Software Revision as" enter any previous firmware version/csc for South Africa
example with Europe OXC previous firmware, "S8500XXJF7/S8500OXCJF3" (without the quotes).
- In the option, "Kies Version" enter the installed kies version. (By default, displays automatically).
4. After entering above information, now click on the button "Write Registry" to enter the data to registry.
5. Finally, go to kies and click on "Upgrade Firmware" and "Accept".
6. Kies will display that there is a new firmware version (e.g. S8500XXJL2/S8500OXCJL1).
7. Just click on accept and the upgrade process in kies will begin. That's all.
CAUTION:
Make sure you return kies patcher back to "False" after using, otherwise the app will be active at the background.
- In the option, "Enable Spoof" select "False"
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Download kies2.0 Registry Patcher from here: http://www.megaupload.com/?d=Q3ZWSE0O

Thanks a lot. Will try that tonight quick to see what the results are. Will let you know

OK then i wait, i am currently developing if you need the files i will post it for you or send you via skype.

Ok just checked now on this list for the release referances
http://www.scribd.com/doc/47859691/Samsung-Firmware-Langpacks-Descriptions-09-2010
The last official update combination was
PHONE: S8500JBJI2 CSC: S8500XFVJI2 - Bada 1.0
and
PHONE: S8500XXJF1 CSC: S8500XFVJF1 - Bada 1.0
Using both the combinations it says that there is no firmware update and this is the latest version.
Should i update to one of them to find out what the latest combination is because both cant be right right ?

Cross Version Updates can go in a bad way, you need first a full open firmware that is also available in your firmware revision.
Firmware Version Example: S8500XXJI5 (The base)
Config Version Example: S8500OXAJI5
The configs are not important if a other is available for your country, if not, then it it also important,
Litte differences can cause also a reboot loop.

toxicdust said:
The last official update combination was
PHONE: S8500JBJI2 CSC: S8500XFVJI2 - Bada 1.0
and
PHONE: S8500XXJF1 CSC: S8500XFVJF1 - Bada 1.0
Using both the combinations it says that there is no firmware update and this is the latest version.
Should i update to one of them to find out what the latest combination is because both cant be right right ?
Click to expand...
Click to collapse
Yes, wrong combination of firmware(PDA) and CSC can lead to an endless booting of phone.
Please use a correct combination of the firmware files for South Africa. If possible, install an earlier version of kies
[say, Kies_1.5.3.10103_102_1 (19 Nov 2010) or Kies_2.0.0.11011_16_5 (05 Jan 2011)].
This is because most recent versions of kies read firmware versions direct from the phone.
I have personally used the above versions with Kies Patcher and they worked successfully.
But when I tried with the latest kies version [Kies_2.0.1.11053_66_6 (15 June 2011)],
hoping to trick kies by entering an old firmware version (S8500XXJF4/S8500XENJF3) into Kies Patcher,
kies deteted that there is a firmware upgrade for my phone. When I clicked to upgrade, kies stopped half-way,
displaying that the latest firmware XXJL2 is already installed on my phone.
So to avoid this happening in your case, install an earlier kies version, and use kies patcher to upgrade your phone.
I include below some firmware combinations for South Africa. Try the combinations one by one (starting from the unbranded firmwares).
Hopefully one of them will work for you. Best of luck.
1. NOT BRANDED FIRMWARE
CODE * COUNTRY * FIRMWARE * CSC
==========================================
XFM (SOUTH AFRICA) S8500XXJL2/S8500XFMJL1
XFM (SOUTH AFRICA) S8500XXJL4/S8500XFMJL3
XFA (SOUTH AFRICA) S8500XXJL2/S8500XFAJL1
XFA (SOUTH AFRICA) S8500XXJL4/S8500XFAJL3
XFE (SOUTH AFRICA) S8500XXJL3/S8500XFEJL2
XFE (SOUTH AFRICA) S8500XXJL2/S8500XFEJL1
XFE (SOUTH AFRICA) S8500XXJI5/S8500XFEJH1
XFC (SOUTH AFRICA) S8500XXJF1/S8500OXXJEG
XFC (SOUTH AFRICA) S8500XXJH3/S8500XFAJH1
XFM (SOUTH AFRICA) S8500XXJH3/S8500XFMJH1
XFE (SOUTH AFRICA) S8500XXJH3/S8500XFEJH1
XFA (SOUTH AFRICA) S8500XXJF1/S8500OXXJEG
XFA (SOUTH AFRICA) S8500XXJH3/S8500XFAJH1
2. BRANDED FIRMWARE
CODE * COUNTRY * FIRMWARE * CSC
==========================================
XFV (SOUTH AFRICA) S8500JBJL2/S8500XFVJL2
XFV (SOUTH AFRICA) S8500JBJL1/S8500XFVJL1

Thanks a lot for the most recent combinations... I'll have a look at these. Seeing as i have JL2 installed i will see if i cant trinck it in updating to JL4

How to Create your country CSC File for bada 2.0 firmware

1. First, dump the csc file of your choice from XXJL2 firmware. Save these dumped files at desktop.
You will need to use some files/folders here to replace some in the bada 2.0 OXA csc file.
2. Now use Trix to dump and edit the "CSC_S8500_Open_Europe_Common_OXA_KG5" csc file
3. With Trix still open, go to the dumped files and edit as follows:
a. Delete folder "CSC" and replace it with the "CSC" folder from XXJL2 (the one you saved at desktop in nº 1 above).
b. After replacing, Open the new CSC folder and edit the "SW_Configuration" xml file:
<CustomerDataSet>
<CSCName>S8500OXC</CSCName> *
<CSCVersion>KG5</CSCVersion> **
* make sure the CSCName displays your own csc, e.g OXC, OXD, etc (should be by default)
** change the CSCVersion to KG5 (not JL2), and SAVE FILE.
4. Now open folder "SystemFS" ==> open folder "Settings" ==> open folder "PreConfiguration" ==>
...In folder "PreConfiguration", delete all folders and files therein except the folder "Default".
...copy in (to replace) from your XXJL2 dumped files (nº 1 above),
all folders and files from the "PreConfiguration" folder except the folder "Default".
5. Finally, upload the files in Trix and name it, e.g. CSC_S8500_Open_Europe_Common_OXCKG5.csc
6. That's all. You now can flash bada 2.0 firmware with your own csc file.
NB: I have uploaded the OXC csc file (Greece, Spain and Portugal),
CSC_S8500_Open_Europe_Common_OXCKG5 for those who may need it.
Download from: http://www.megaupload.com/?d=036VSJHI

That way is not applicable for other regions to get more languages (just Europe)
Correct me if i am wrong
Best Regards

mylove90 said:
That way is not applicable for other regions to get more languages (just Europe)
Correct me if i am wrong
Best Regards
Click to expand...
Click to collapse
Yes, this method is based on the Europe XX firmware.
Works 100% for Europe as the files and settings are almost similiar.
For other regions, I don't know if the process may work or not.
Firmwares from different regions differ in so many aspects;
so I am afraid this process may likely not work.
But anyone from other region can try it and give us feedbacks.

Can I make a CSC file for bada 2.0 to Nordic countries?
What happens? Will I get Norwegian if I want? =)

christer12 said:
Can I make a CSC file for bada 2.0 to Nordic countries?
What happens? Will I get Norwegian if I want? =)
Click to expand...
Click to collapse
Yes, you can.
Just follow the steps as described above.
You will get Norwegian (it's under the same csc for Nordic)

I have tried now, but It was not in Norwegian. Can not get Norwegian keyboard, but the settings are correct. They have not added Norwegian language and keyboard. Whether If I have changed the CSC file.

spacks said:
1. First, dump the csc file of your choice from XXJL2 firmware. etc...
Click to expand...
Click to collapse
Hi spacks!
I followed your steps and created a CSC_S8500_Open_Europe_Common_OXD_KG5.csc (with XEH because I'm hungarian) but when I flash it and do a preconfig to XEH it bootloops... What could be the problem??? I used this : CSC_S8500_Open_Europe_Common_OXDJL1.csc for the "transplantation"

sorry for my English... Trix this is the program? if yes, where can I download it? and this method will work for Ukraine? (this is also Europe)

Hello anghelyi,
For all XX region firmwares, this process works ok.
I have not tested the XE region. Though XE is Europe, but the XE firmware is quite distinct from that of XX.
If you can upload the csc file from the last bada 1.2 of your region, maybe I can test it myself and give you feedback.
Thanks.

Slayerqq said:
sorry for my English... Trix this is the program? if yes, where can I download it? and this method will work for Ukraine? (this is also Europe)
Click to expand...
Click to collapse
You can download Trix from here: http://www.mediafire.com/?twu1ixb6ei211qb
or directly from TriX home page
As this is your first time to use Trix, I will advise you wait and let someone else who is experienced do the check first if this same process works for Ukraine.
I have only tested it for XX region which does not include Ukraine.
I think Ukraine belongs to the XE region.

spacks said:
Hello anghelyi,
For all XX region firmwares, this process works ok.
I have not tested the XE region. Though XE is Europe, but the XE firmware is quite distinct from that of XX.
If you can upload the csc file from the last bada 1.2 of your region, maybe I can test it myself and give you feedback.
Thanks.
Click to expand...
Click to collapse
Hi spacks!
Many thanks for the info. I uploaded the csc here: http://www.multiupload.com/O24UCOXPM7
Most certainly I made some stupid mistake...
TIA!

spacks said:
Hello anghelyi,
For all XX region firmwares, this process works ok.
I have not tested the XE region. Though XE is Europe, but the XE firmware is quite distinct from that of XX.
If you can upload the csc file from the last bada 1.2 of your region, maybe I can test it myself and give you feedback.
Thanks.
Click to expand...
Click to collapse
posted to file Russia (SER), please try to change it to BADA 2
but I can not put a link. How can I send it to you?

anghelyi said:
Hi spacks!
I followed your steps and created a CSC_S8500_Open_Europe_Common_OXD_KG5.csc (with XEH because I'm hungarian) but when I flash it and do a preconfig to XEH it bootloops... What could be the problem??? I used this : CSC_S8500_Open_Europe_Common_OXDJL1.csc for the "transplantation"
Click to expand...
Click to collapse
Hello anghelyi,
I have tried with the OXDJL1 CSC file you uploaded.
Same like your experience, as soon as you set pre-configuration to XEH,
the phone goes into endless rebooting process.
CONCLUSION: As this new bada 2.0 firmware is for the XX Europe region,
the process described here for creating each country CSC file
only applies to the XX Europe region.
Other Europe region like XE (Hungary, Russia, etc) will not work.
Thanks for your understanding.

spacks said:
Hello anghelyi,
I have tried with the OXDJL1 CSC file you uploaded.
Same like your experience, as soon as you set pre-configuration to XEH,
the phone goes into endless rebooting process.
Click to expand...
Click to collapse
Thank you anyway! As the SDK has hungarian language I think the final 2.0 will come with hungarian CSC, so it's more like interesting than a real problem Thanks again for your time!

hi ! . I have one ask I find it amusing to stop that one for it none app develop can!!! Why one cannot develop one app for bada where one the language which one needs in the mobile phone add can that would be super a geile app. Thus is that possible upper not young? and if not why?? You cannot do Androide oversize wave portieren however one spoke to add goes??!!! thanks

mylove90 said:
That way is not applicable for other regions to get more languages (just Europe)
Correct me if i am wrong
Best Regards
Click to expand...
Click to collapse
I have one ask I find it amusing to stop that one for it none app develop can!!! Why one cannot develop one app for bada where one the language which one needs in the mobile phone add can that would be super a geile app. Thus is that possible upper not young? and if not why?? You cannot do Androide oversize wave portieren however one spoke to add goes??!!!

Can i change the CSC for getting the firmware in hebrew (Israel)?
And if yes to what setting to change the CSC i didn't anderstand on Samfirmware what is my CSC

gilkzxc said:
Can i change the CSC for getting the firmware in hebrew (Israel)?
And if yes to what setting to change the CSC i didn't anderstand on Samfirmware what is my CSC
Click to expand...
Click to collapse
You need to know first, what csc Israel uses. If the csc falls under the XX Europe firmware group, then the process of changing csc will work for you. Otherwise, I am afraid not.
To check your CSC version, enter in your phone keypad the following: *#1234#

spacks said:
You need to know first, what csc Israel uses. If the csc falls under the XX Europe firmware group, then the process of changing csc will work for you. Otherwise, I am afraid not.
To check your CSC version, enter in your phone keypad the following: *#1234#
Click to expand...
Click to collapse
but it isn't from the XX Europe firmware group it's has it's own diffrent
and it's won't recongniz at Samfit
this is my firmware try to help find the right group
(in the picture)
what understand is that is bada 1.0.2 August 2010
and PTR is for Orange Israel but i don't know what is this S8500JHJH3
and i check it isn't the israel offical group for every cellolar compeny in Israel on the CSC diffrent
like this:
PTR = Orange Israel
PCL = Pellephone Israel
CEL = Cellcom Israel

for india can u make it and uplaod it?

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?

CSC change on SM-R815U, convert SM-R815U to be able to use LTE in Canada

Let's start out that i've been at this for about 12 hours now with no luck. Maybe i'm missing something or doing something wrong. People seem to be able to change the CSC on their watch active without issue but the Galaxy Watch may be a different story. I've tried following the guide made by @Mithos11 https://forum.xda-developers.com/smartwatch/galaxy-watch/sm-r825f-csc-change-tutorial-t4061905 and this one: https://forum.xda-developers.com/sm...r805f-csc-change-howto-esim-rsp-v2-x-t3848292 . I've even tried this one: https://forum.xda-developers.com/smartwatch/galaxy-watch/changing-region-galaxy-active-2-t3983895 with no luck. I've even tried the not un-ticking Auto reboot in Netodin to see if that would help.
Throughout the steps I tried flashing the latest combination firmware for the 815U, then flashing the CSC file from the latest 815U regular firmware, pull the 2 files, edit them, push them back and then flashed the 4 firmware files for 815U. I even tried leaving out the CSC from the last step since i did edit it just before. That didn't work either.
I am a bit confused by this: eSIM: The Gear S3 LTE models have eSIM RSP v1.x, in case anybody was wondering why LTE/3G connections were not possible in many countries (where operators are probably a bit concerned or regulated WRT security).
Galaxy Watch (well, at least my SM-R805F) supports ONLY RSP v2.x, which means it will work on most European carriers, including Telekom.de. From esim-server, in IDA:
Gear S3: std::string::string(&v8, "/gsma/rsp1/es9plus/initiateAuthentication", &v7);
Galaxy Watch: sub_64FD4(&v14, "/gsma/rsp2/es9plus/initiateAuthentication", "");
The activation of the eSIM should be done on the same CSC as the eSIM network and the mobile phone paired. Once the eSIM is provisioned and the watch has GSM connectivity, the CSC can be changed again, the eSIM profile will stay. Well i'm assuming my CSC on my bell phone is XAC which is what everyone is telling me. could it be different? Or is it saying i need to activate it on a AT&T network first before Bell in Canada?
I'll post screenshots of certain screens i have come across trying all of this. Hopefully someone else can help me figure this out.
Also, if you are going to be tinkering, i HIGHLY suggest getting a Gear S usb charger and take it apart. Those 5 pogo pins fit perfectly in there to use in download mode (not wireless) It can be finicky keeping it in there, but it works.

I have for US SM-R815U these files:
Code:
COMBINATION-FT40_R815USQU1ASE1.tar.md5
COMBINATION-FT40_R815USQU1ASK1.tar.md5
And few Stock Firmwares...
Meanwhile we know... sboot.bin from SM-R815W is not written... not accepted by Bootloader inside SM-R815U...
So sboot.bin inside device is ever:
Code:
SM-R815[B]U[/B]
From W I have only this Stock Firmware:
Code:
BL_R815WVLU1ASA5_usr.tar.md5
AP_R815WVLU1ASA5_usr.tar.md5
CP_R815WVLU1ASA5_CL1020541_QB11794236_SIGNED.tar.md5
[B]CSC_OYV_R815WOYV1ASA5_usr.tar.md5[/B]
I have NO R815USQU1BSA7...
@equlizer
A
Please flash all 4 files from R815USQU1BSA7...
B
Second round:
Code:
CSC_OYV_R815[COLOR="Red"][B]W[/B][/COLOR]OYV1ASA5_usr.tar.md5
C
Check in Reboot menu if you can select recovery...
If not work...
No idea where...
Then we can """modify""" CSC file... by removing partition.pit... so only TAR with csc.img inside...
Best Regards
Edit 1.
Added CSC from SM-R815W without partition.pit... ASA5

I am away from home ATM but the last time i tried flashing the CSC W version, the watch went into odin mode and needed the JTAG to start over.
What does taking out the PIT from the CSC file do?
I was able to find SM-R815F multi CSC firmware, but what ive read is the F lte bands are not supported on this side of the globe. Only like china, korea, etc.
https://easy-firmware.com/index.php?a=downloads&b=folder&id=35897
EDIT AGAIN: I think i may have found the problem (hopefully) All this time I was replacing the XAR (usa) with XAC (a few people told me this was canada) I believe the 2 pulled files need to be changed to OYV (all W firmwares show that) I will try this and report back (or if someone else wants to)

I thought we learn together...
About CSC aka Sales Code
1.
Look at your Photos...
Under Software Version also Product Code visible...
No idea if also in Stock Firmware...
You see something like SM-R815UblablaXAR
XAR is CSC from USA
I have this feature never seen on my SM-R760...
2.
How FOTA work... your device look on this Server:
XAR is bad example ... because empty...
http://fota-cloud-dn.ospserver.net/firmware/XAR/SM-R815U/version.xml
ATT for ATT better...
http://fota-cloud-dn.ospserver.net/firmware/ATT/SM-R815U/version.xml
You can also create these Notify Links with your knowledge about CSC / Sales Code
XAR
https://doc.samsungmobile.com/SM-R815U/XAR/doc.html
ATT
https://doc.samsungmobile.com/SM-R815U/ATT/doc.html
SM-R815W Cannadian Tornado...
https://doc.samsungmobile.com/SM-R815W/XAC/doc.html
Summary... Model Name + CSC / Sales Code
3.
Please use Tool 7zip to understand the magic of CSC / Sales Code Change...
You can use this csc.img...
https://forum.xda-developers.com/showpost.php?p=81970361&postcount=2
Seach for this File:
Code:
SW_Configuration.xml
Look with open eyes:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<SW-Configuration>
<MobileData>
<PublicName>SM-R815[COLOR="Red"][B]W[/B][/COLOR]</PublicName>
<NickName />
</MobileData>
<CustomerDataSet>
<CSCName>R815WOYV</CSCName>
<CSCVersion>1ASA5</CSCVersion>
<NbCustomer>1</NbCustomer>
<CustomerData src="/Customer/[B][COLOR="SeaGreen"]XAC[/COLOR][/B]/customer.xml" />
</CustomerDataSet>
</SW-Configuration>
4
OYN is Region Code... btw. same used for SM-R815U...
So your idea is simple wrong.
5
I can show you examples... so you can learn more about Watch... and CSC....
But need first complete result of my request...
A
Full SM-R815U BSA7... working condition
Second round:
Code:
CSC_OYV_R815WOYV1ASA5_usr.tar.md5
B
Full SM-R815U BSA7... working condition
Second round:
Code:
cscONLY_smR815W_ASA5.tar
Need full description of Errors...
netOdin shows Error?
Reboot menu.. recovery?
Reason for 2 Versions are to eliminate that RSA 2048 Signature is checked from partition.pit... because AUTOMATIC written to device...
Inside CSC package...
C
We could also increase Proffffesssssinanalitity
If Upload visible in Reboot menu... we can take Log files via Tool RDX:
https://forum.xda-developers.com/showpost.php?p=77375046&postcount=57
Click through this Thread... to see some Screenshots...
Later more...
Next lesson... i would show you how CSC change work via Codes... in Combination Firmware...
Best Regards

https://forum.xda-developers.com/showpost.php?p=81989145&postcount=3
As tiny exercise you could change from XAR to something else... to fix this stupid no FOTA...
I have NO idea why XAR not get updates...
You have have exact 6 CSC / Sales Codes inside your OYN region package:
Code:
ATT for ATT USA
TMB for T-Mobile USA
SPR for Sprint USA
USC for no idea because I am from Germany
VZW is Verizon USA
XAR is USA... but seems funny placeholder
You can check these CSC / Sales Codes by extracting files from csc.img of SM-R815U Firmware... with 7Zip Tool:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<SW-Configuration>
<MobileData>
<PublicName>SM-R815U</PublicName>
<NickName />
</MobileData>
<CustomerDataSet>
<CSCName>R815UOYN</CSCName>
<CSCVersion>[B][COLOR="Green"]1BSE3[/COLOR][/B]</CSCVersion>
<NbCustomer>6</NbCustomer>
[COLOR="Green"][B] <CustomerData src="/Customer/XAR/customer.xml" />
<CustomerData src="/Customer/ATT/customer.xml" />
<CustomerData src="/Customer/SPR/customer.xml" />
<CustomerData src="/Customer/TMB/customer.xml" />
<CustomerData src="/Customer/USC/customer.xml" />
<CustomerData src="/Customer/VZW/customer.xml" />[/B][/COLOR]
</CustomerDataSet>
</SW-Configuration>
BSE3 should also possible to use the old method... with SDB Tool and Command:
Code:
launch_app csc-manager.csc-pre-configuration
Described for instance here:
https://forum.xda-developers.com/sm...nging-region-samsung-gear-sport-r600-t3771324
Best Regards

Should i try your method before your last post or try the BSE3 firmware? The BSE3 is the update before SL2. should i try the oldest one (ARH8)?

If you want use BSE3 Firmware...
Good I have BSE3 on my HDD.
Here I can show you what and how CSC change work...
SDB Tool is here:
https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330
Code:
sdb connect ........ your IP address
Code:
sdb shell
Code:
launch_app csc-manager.csc-pre-configuration
Now you should see 6 CSC / Sales Codes
You can choose 1...
Before you can type (Copy and Paste) other Command:
Code:
launch_app csc-manager.csc-[B]verifier[/B]
You should see something with XAR...
Best Regards
Edit 1.
Ah, found my old Video captures...
https://forum.xda-developers.com/showpost.php?p=75846867&postcount=469

I just sold the damn thing. It was taking too much of my time. Thank you for all of your help though I ended up selling it for $250 and managed to get a 46mm canadian version for $250 so it worked out.

Hi, tell me if my idea is correct. After checking the firmware from sm-r8050, sm-r805f, sm-r805u and sm-r805w in the csc part, the pin in all the firmware is identical except for the signature at the end of the file, the signatures in all the firmware files for example always start in the same longwords linked to a specific model. I so understand from for this signature under firmware csc from another model not accepted. The idea is to unpack CSC. tar. md5 and add a folder with the region I need from another model to CSC. img native firmware by editing it SW_Configuration.xml. After that, flash the native COMBINATION-FT40 with a modified csc file and then fill in the native firmware forgetting about updates in the future but getting a working esim and samsung pay. The question is if I do all the above, will I get Knox 0x1? Sorry for my English.