SM-R805F, bought in Germany.
Changing CSC works flawlessly on this one, the usual method:
* Connect via SDB (wireless or wired connection)
* Run launch_app csc-manager.csc-pre-configuration
* Choose CSC, wait for the watch to reset, all done. SPay works as well now.
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", "");
Thanks Samsung.
Small update:
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.
Samsung pay does not work in Germany right now. The app is not available in the app store. Would your procedure allow me to use Samsung pay in Germany?
Gesendet von meinem SM-G965F mit Tapatalk
Samsung Pay works in Germany as a payment method. If you want to enroll your card, it must be supported, which means your bank must accept you to use the card they issued in SPay. I do not know of any German bank that accepts it ... I personally usr a foreign card with SPay (Swiss). It works on all NFC terminals.
It is more about the app not being available for my region (Germany). It is not officially released around here yet.
Gesendet von meinem SM-G965F mit Tapatalk
The app on the watch as well as the SPay companion app on the phone (not to be confused with the one that allows one to pay with the phone) will become available as soon as you change the CSC, say to Italy. If you find a card you can enroll, you can pay with the watch, but not with the phone. The SPay for the phone and the one for the watch are two different animals.
P.S. The original post instructions are just for changing the CSC and getting SPay to run on the watch. How to find a bank to provide a credit card that supports it is a long story that we do not really want to start discussing here.
Hi, I have a Korean SM-R810 and I am very interested in changing it to a US CSC for Samsung pay. You mention aboove that you used the "usual method" is there a thread you could recommend as a guide to the usual method? I searched and came up with this:
https://forum.xda-developers.com/gear-s3/how-to/succesfully-changed-csc-to-xar-to-t3718236
However, I am not sure where you got your mom files, and I can't seem to find any that would be applicable to my model either. My watch is an SM-R810NZDAKOO. The model I want to change it to is SM-R810NZDAXAR.
Thanks for any assistance.
Jenoin said:
Hi, I have a Korean SM-R810 and I am very interested in changing it to a US CSC for Samsung pay. You mention aboove that you used the "usual method" is there a thread you could recommend as a guide to the usual method? I searched and came up with this:
https://forum.xda-developers.com/gear-s3/how-to/succesfully-changed-csc-to-xar-to-t3718236
However, I am not sure where you got your mom files, and I can't seem to find any that would be applicable to my model either. My watch is an SM-R810NZDAKOO. The model I want to change it to is SM-R810NZDAXAR.
Thanks for any assistance.
Click to expand...
Click to collapse
What I did was far easier, but I don't know if the same will work on your model:
* Connect via SDB (wireless or wired connection) e.g. run sdb shell and you should be getting a shell prompt on the watch
* Run launch_app csc-manager.csc-pre-configuration - a list of the available CSC codes will be shown on the watch screen for you to choose from
That's all - no need to flash anything, the watch will either let you change the CSC or not - mine works.
Good luck, and please let me know if it worked out for you.
What's CSC?
Does that mean you can change the region of the watch, i.e. buying it in US or Korea and make it identical to one bought in Europe regarding Samsung Pay?
eloisant said:
What's CSC?
Does that mean you can change the region of the watch, i.e. buying it in US or Korea and make it identical to one bought in Europe regarding Samsung Pay?
Click to expand...
Click to collapse
Yes. You cannot change the model, e.g. SM-R805U to SM-R805F, but often the firmware contains the CSC for multiple countries / regions. In such cases you can switch between them - again, if the firmware allows it.
Run launch_app csc-manager.csc-pre?
Could you help explain what is Run launch_app csc-manager.csc-pre-configuration, is this a application or a command?
This is a command you run from SDB. SDB is a command line application for Samsung hardware:
https://forum.xda-developers.com/gear-s3/how-to/guide-how-to-change-gear-s3-r760-csc-t3784226
(That's a detailed explanation for the Gear S3, but it should be similar for Galaxy Watch)
ecoco1 said:
What I did was far easier, but I don't know if the same will work on your model:
* Connect via SDB (wireless or wired connection) e.g. run sdb shell and you should be getting a shell prompt on the watch
* Run launch_app csc-manager.csc-pre-configuration - a list of the available CSC codes will be shown on the watch screen for you to choose from
That's all - no need to flash anything, the watch will either let you change the CSC or not - mine works.
Good luck, and please let me know if it worked out for you.
Click to expand...
Click to collapse
I can't get it to work yet, after a lot of trouble I was unable to get it to connect directly to watch over WiFi. The rsa notification would never come up on the watch.
I then attempted to connect via USB through my phone (Essential PH-1) which worked ok. However, when I run "launch_app csc-manager.csc-pre-configuration" I get the response "/system/bin/sh: launch_app: not found"
Any advice? An ls of /system/bin does not show a launch_app command.
Thanks for any assistance!
---------- Post added at 12:56 PM ---------- Previous post was at 12:48 PM ----------
I connected my S3 up using the same process and it also didn't work, so I think the issue is that I am only connecting to the phone and not connecting to the watch at all. Not sure how to correct this issue.
I did get my S3 to connect using wifi, it appears that nothing I do will enable the SM-R810 to connect over wifi, I have even installed galaxy watch designer and it is unable to connect to the watch. The RSA authorization just never appears and GWD acts like it didn't detect anything.
---------- Post added at 03:19 PM ---------- Previous post was at 02:24 PM ----------
I finally got it working. I have no idea why I had so much trouble. Steps that I took in order:
* Using Windows 10
* I started by enabling debugging and developer mode and enabling wifi, connecting and getting IP address.
Tried using SDB 2.26 found here https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330
- This didn't work, I couldn't see my watch over wifi at all, tried it over and over, never saw the RSA authentication popup, got errors saying it couldn't find device or something (Not "connecting to 192.168.1.118:26101 ... device unauthorized. Please approve on your device.")
Installed Tizen Studio
Installed Galaxy Watch Designer
Tried to connect using Galaxy watch designer, basically same as above but now with a pretty GUI that gave no feedback on why it wasn't working.
Tried to connect over usb cable to phone through BT. SDBoverBT installed on phone but kept giving an error that it wouldn't work to check SPP or BT connection.
GWD did detect my phone just fine though.
I noticed that my S3 would also not connect through my phone at this point. I never figured out why I couldn't get a wired/BT connection to work. Does this maybe require a Samsung phone? Mine is a PH-1.
I did a factory reset on my watch around this point and tried again with GWD but no luck.
Tried using Tizen Studio version of SDB
When starting SDB from Tizen Studio package I would get "* The version of SDB client (3.1.7) and server (2.3.0) are different. This may cause version compatibility problems. It is recommended to use SDB server 3.1.7. *"
According to other forums this was fine. But it wasn't working for me so I decided to try and get rid of the message. I tried to kill the server and restart but it just kept saying the same message. Finally I closed GWD and then killed the server and got the message "info: Server is not running" Great!
Now with server 3.1.7 running I could see the watch finally. I repeatedly tried to connect and finally got the right message "connecting to 192.168.1.118:26101 ... device unauthorized. Please approve on your device."
But the notification didn't popup on the watch. I restarted the watch for about the 10th time and tried to connect again. this time it finally got the RSA popup!
Success!
My Korean SM-R810 (SM-R810NZDAKOO) is now a US model SM-R810 (SM-R810NZDAXAR) by changing CSC. This turned out to be a lot of work to save $40 (Ebay) but I did really want Samsung pay, and it wasn't really worth trying to send it back to Korea.
For those interested, there were about 40 different CSC options available. If useful I can provide a list.
Thanks to the OP for the guide.
Good stuff
Great stuff am happy you got it working, hopefully I get mine sorted soon as well. Having connection issues also
Good to see it works Jenoin!
Could you post a list of available CSC? I'm planning to buy a Korean watch too (really cheap in Seoul airport duty free) and I'd like to confirm I can set it to a French CSC.
eloisant said:
Good to see it works Jenoin!
Could you post a list of available CSC? I'm planning to buy a Korean watch too (really cheap in Seoul airport duty free) and I'd like to confirm I can set it to a French CSC.
Click to expand...
Click to collapse
After I posted that it was 40 before I was kind of second guessing myself, because it didn't seem like it could be so many.
I was way off, it was actually 70! Hope some people find this useful. I still had some trouble this time getting SDB connected. What seemed to work, is to make sure you have enabled developer mode, debugging, and wifi. Restart and wait a couple minutes for it to complete any startup routine that may be running in the background. Ensure the screen is ON but at the home screen/main watch face and then attempt to connect via IP.
XAR ACR AFR ARO ATO AUT BGL BRI BTU BVO
CAC CAM CHC CHO COO DBT ECT EGY EUR ILO
INU ITV KOO KSA LUX LYS MID MWD MXO MYM
NEE NPL PAK PEO PHE PHN ROM SEB SEE SEK
SER SKZ TGY THO THR TMC TPA TPH TTT TUN
TUR UPO UYO XAC XEF XEH XEO XEZ XFA XJP
XME XNZ XSA XSE XSG XSK XSP XTC XXV ZTO
Out of curiosity, what is the price at the duty free store in Korea?
Good luck!
Thank you!
The 46mm bluetooth is roughly 265USD duty free in Korea.
Samsung pay
I successfully changed my region from Korea to EUR and I have not received any prompt for Samsung pay. It's been over 6 hours now. Anyone know how long it should take?
Samsung pay
I successfully changed my region from Korea to EUR and I have not received any prompt for Samsung pay. It's been over 6 hours now. Anyone know how long it should take? I have a non Samsung android phone
I followed this and restarted, restarted and restarted.... still no RSA prompt, any hints to help please?
---------- Post added at 09:46 AM ---------- Previous post was at 09:45 AM ----------
Jenoin said:
After I posted that it was 40 before I was kind of second guessing myself, because it didn't seem like it could be so many.
I was way off, it was actually 70! Hope some people find this useful. I still had some trouble this time getting SDB connected. What seemed to work, is to make sure you have enabled developer mode, debugging, and wifi. Restart and wait a couple minutes for it to complete any startup routine that may be running in the background. Ensure the screen is ON but at the home screen/main watch face and then attempt to connect via IP.
XAR ACR AFR ARO ATO AUT BGL BRI BTU BVO
CAC CAM CHC CHO COO DBT ECT EGY EUR ILO
INU ITV KOO KSA LUX LYS MID MWD MXO MYM
NEE NPL PAK PEO PHE PHN ROM SEB SEE SEK
SER SKZ TGY THO THR TMC TPA TPH TTT TUN
TUR UPO UYO XAC XEF XEH XEO XEZ XFA XJP
XME XNZ XSA XSE XSG XSK XSP XTC XXV ZTO
Out of curiosity, what is the price at the duty free store in Korea?
Good luck!
Click to expand...
Click to collapse
I followed this and restarted, restarted and restarted.... still no RSA prompt, any hints to help please?
Related
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?
I've tried to debrand my phone by flashing open market firmware (XEO, Poland). I downloaded the newest version of Odin, flashed it but now my CSC under settings says OPV/OPV, OPV/EUX/OPV. OPV is my carrier's CSC, I'm wondering what that EUX is. I've looked it up on Google and it seems like I'm not alone, seems like Samsung changed something and older methods no longer work. The question is - will I still receive updates released for my carrier or I'm screwed for good? Phone INFO app says my active CSC is OPV. I'm running S20+ 5G (G986B) Exynos variant.
Same problem here, I've flashed it with XEO POLAND G986BXXU1ATBM firmware using Odin3 v3.14.1_3B_PatcheD, few minutes later it showed "PASS" and nothing changed. Same branded firmware after reboot..
It seems, that many more 'branded' CSCs are now part of Multi-CSC. For me, this is DTM (T-Mobile DE). It osed to not be part of multi-CSC but it is now part of OXM.
This means, that you can not force it anymore, as you already ARE having the exact same firmware with the 'branded' CSC. Just checked, OPV is in deed part of OXM now.
In the Ultra Section is a thread showing the CSCs belonging to OXM: https://forum.xda-developers.com/ga...galaxy-s20-ultra-g988b-firmwares-5g-t4060443/
I have not yet found out / gotten an answer from anybody how to change CSC. Samkey also is not supporting the S20 series ATM - dont know, if this will change.
Monnq said:
I've tried to debrand my phone by flashing open market firmware (XEO, Poland). I downloaded the newest version of Odin, flashed it but now my CSC under settings says OPV/OPV, OPV/EUX/OPV. OPV is my carrier's CSC, I'm wondering what that EUX is. I've looked it up on Google and it seems like I'm not alone, seems like Samsung changed something and older methods no longer work. The question is - will I still receive updates released for my carrier or I'm screwed for good? Phone INFO app says my active CSC is OPV. I'm running S20+ 5G (G986B) Exynos variant.
Click to expand...
Click to collapse
What I have worked out is that when you flash a multi-CSC firmware file you end running the CSC one letter earlier in the alphabet out of the. Available multi-CSC list
E.g. I had a VOD branded S105G and flashed BTU firmware, and ended up with TEL CSC
I also tried flashing BTU on an H3G branded A70 and ended up with EVF CSC
The original branded product CSC also never changes
---------- Post added at 11:32 AM ---------- Previous post was at 11:30 AM ----------
Andrino said:
Same problem here, I've flashed it with XEO POLAND G986BXXU1ATBM firmware using Odin3 v3.14.1_3B_PatcheD, few minutes later it showed "PASS" and nothing changed. Same branded firmware after reboot..
Click to expand...
Click to collapse
Enable Developer mode and set OEM Unlock to ON before trying to change CSC via ODIN Flash
This should not be necessary? Doesn't that trip Knox, despite original Samsung Firmware?
corwin_amber said:
It seems, that many more 'branded' CSCs are now part of Multi-CSC. For me, this is DTM (T-Mobile DE). It osed to not be part of multi-CSC but it is now part of OXM.
This means, that you can not force it anymore, as you already ARE having the exact same firmware with the 'branded' CSC. Just checked, OPV is in deed part of OXM now.
In the Ultra Section is a thread showing the CSCs belonging to OXM: https://forum.xda-developers.com/ga...galaxy-s20-ultra-g988b-firmwares-5g-t4060443/
I have not yet found out / gotten an answer from anybody how to change CSC. Samkey also is not supporting the S20 series ATM - dont know, if this will change.
Click to expand...
Click to collapse
Since now it's part of Multi CSC, does that mean I will receive updates faster? I can see other polish carrier's CSC are listed as single so I assume they are kind of separate firmware, am I right?
Honestly I do not know, if the respective CSC will be getting OTAs at the same time.
However, you can always flash manually with HOME_CSC, that is true.
corwin_amber said:
This should not be necessary? Doesn't that trip Knox, despite original Samsung Firmware?
Click to expand...
Click to collapse
Enable OEM unlock does not trip Knox. As long as you flash official Samsung firmware files in Odin Knox is never tripped
My own personal experience on S10 and above is you cannot flash a different CSC with OEM Unlock disabled
(Flash completes successfully but CSC doesn't change)
When changing from one e.g. branded csc to multi csc with the S10+, this worked fine without enabling oem unlock. Well, anyway. Flashing OXM multi CSC over OXM multi CSC will not change anything, right?
corwin_amber said:
When changing from one e.g. branded csc to multi csc with the S10+, this worked fine without enabling oem unlock. Well, anyway. Flashing OXM multi CSC over OXM multi CSC will not change anything, right?
Click to expand...
Click to collapse
I found that you have to be on a single CSC before flash to multi-CSC and also you don't always end up on the CSC you expected
e.g. Flash BTU on a VOD product and you end up on TEL CSC (one letter in alphabet below VOD) and not on BTU
did everyone succesed DEBRAND ?
i v got s20 ultra OPV(orange) and need XEO (official)
tak, poprzez samkey
Yes, with samkey
@0kti if you have any credits remain let me know please ( I will buy it )
I found link to our android com pl forum , thanks
Nope. Buy on ebay. It's cheap. 3 credits.
Tapatalk - SM-G986B
one credit please, somebody will share ?
raphaelx69 said:
one credit please, somebody will share ?
Click to expand...
Click to collapse
really lmao.. its literally a few bucks... chimera tool works great also but is a mpre expensive subscription but dont gotta kee0 buyin credits
Hello today i bought a Samsung Galaxy Watch Active 2 4G it is a France device, in France they use the frequences LTE 800 and LTE1800 in Germany too.
It is possible to get running a German E-Sim on it ? Or Flash a German ROM or anything ?
Kind regrads from Germany !
@Son.y
If you want write me a personal message ... then we can try it in German ...
If you want..
Wenn Du willst schreib mir eine Persönliche Nachricht... dann können wir es in dt. Sprache versuchen...
Wenn Du willst...
Best Regards
I'm kind of in the same boat. I have a German watch 46mm lte and live in Belgium. I want to activate orange esim (I already have a qr code) but the wearable app doesn't give me an option to scan a qr code. I have a proximus, telenet and orange simcard to try in my s10+ but none of them gives me the scan option in wearable app
And to answer OP question, the European lte watch models should all be compatible cross country, all lte bands are supported
@glenner05
Please give more details...
Enter this code like you would call someone...
Code:
*#1234#
And write visible result...
So we can see Firmware details...
Thanx.
Best Regards
I have the mobile option in the wearable app but I always get the error 'this operator is not supported on your watch ' and I don't get the qr option.
I'm sure if I could get a german simcard and put it in my phone I would get to the qr scanning option, then I would just scan my orange esim qr code and after that use my belgian sim again . Anybody have a spare german simcard by any chance
Code:
R805FXXU1FSL3/R805F[B]OXA[/B]1FSL3/R805FXXU1FSL3
According to your Photo... thanx... you are not exact in same boat...
Because your device is SM-R805F...
IMHO this simplify the problem with CSC change... if mandatory...
IMHO if CSC change is solution... then your way is to downgrade to older Firmware to use SDB Tool for easier CSC change like this method:
https://forum.xda-developers.com/showpost.php?p=76077212&postcount=1
Code:
launch_app csc-manager.csc-pre-configuration
Older Firmwares... Stock Firmware of SM-R805F for region OXA are here:
https://forum.xda-developers.com/smartwatch/galaxy-watch/update-sm-r805f-esd8-t3935832
Be carefully... you need OXA...
Summary..
You think you have MAYBE DBT CSC...
This idea could be wrong... anyway... it is possible to be sure which CSC is set as active...
Anyway...
You wish to use CSC from Belgium...
...and live in Belgium
Click to expand...
Click to collapse
Please use Google to identify CSC for Belgium...
I have NO idea yet... and I am too lazy to search with Google.
Best Regards
adfree said:
According to your Photo... thanx... you are not exact in same boat...
Because your device is SM-R805F...
IMHO this simplify the problem with CSC change... if mandatory...
IMHO if CSC change is solution... then your way is to downgrade to older Firmware to use SDB Tool for easier CSC change like this method:
https://forum.xda-developers.com/showpost.php?p=76077212&postcount=1
Older Firmwares... Stock Firmware of SM-R805F for region OXA are here:
https://forum.xda-developers.com/smartwatch/galaxy-watch/update-sm-r805f-esd8-t3935832
Be carefully... you need OXA...
Summary..
You think you have MAYBE DBT CSC...
This idea could be wrong... anyway... it is possible to be sure which CSC is set as active...
Anyway...
You wish to use CSC from Belgium...
Please use Google to identify CSC for Belgium...
I have NO idea yet... and I am too lazy to search with Google.
Best Regards
Click to expand...
Click to collapse
Csc for belgium is LUX
So you think if i manage (by downgrading) to change csc from DBT to LUX i might get the scanning option? Im a little afraid to try that because there are no lte watches sold in belgium, so normally there are no LUX lte watches. I could make the problem worse? And second i dont want to brick my device. I have experience with flashing before, i know odin and stuff but never flashed samsung watches before. I used to flash samsung phones a couple of years ago
So you think if i manage (by downgrading) to change csc from DBT to LUX i might get the scanning option?
Click to expand...
Click to collapse
I wrote you Private Message... to prevent Mod action... as I only found German hits... for search:
Code:
SM-R805F eSIM
Could be CSC change is not Holy Grail.. maybe... not tested not confirmed...
German Users fixed QR crap "adventure" ... by swap SIM card in Phone...
About LUX as CSC...
DBT German:
http://fota-cloud-dn.ospserver.net/firmware/DBT/SM-R805F/version.xml
LUX Belgium... but empty:
http://fota-cloud-dn.ospserver.net/firmware/LUX/SM-R805F/version.xml
https://doc.samsungmobile.com/SM-R805F/LUX/doc.html
I will check CSC of OXA package...
Yes it is inside OXA Firmware package...
But not sure if this fix your problem...
You have to try...
Best Regards
Edit 1.
Code:
<Country>[B][COLOR="Red"]Luxembourg[/COLOR][/B]</Country>
<CountryISO>LU</CountryISO>
<Region>EUR</Region>
<SalesCode>[COLOR="Green"][B]LUX[/B][/COLOR]</SalesCode>
<NbNetworkInfo>1</NbNetworkInfo>
<NetworkInfo>
<MCCMNC>20601</MCCMNC>
<NetworkName>[B]Proximus[/B]</NetworkName>
<NWID>NW01053</NWID>
Taken from Firmware file CSC.img.. extracted with 7Zip tool:
Code:
CSC_[B]OXA[/B]_R805F[B]OXA[/B]1ESD8_usr.tar
Hi Everyone,
I'm from Australia and recently bought a SM-G781B off eBay...
Turns out it was a UAE variant and Samsung Pay is all messed up.
I've flashed the phone a few times now using ODIN, trying to get the right CSC correct for Australia (G781BXXU2CUB5) for either of the following CSC's;
XSA (Generic Australia), OPS (Optus), VAU (Vodafone), or TEL (Telstra).
The issue I have is all the Stock Firmware's I've download and flashed keeps registering my CSC as XME (Malaysia)...
Phone INFO app doesn't even detect any other CSC's in the package
I've tried downloading the correct Firmware packs from the following and none gives me the correct CSC for Australia;
https://samfrew.com/
https://www.sammobile.com/
https://samfw.com/
App: Frija Firmware
Does anyone know why this is happening, or can upload/direct me to correct firmware either XSA, OPS (Optus), VAU (Vodafone), or TEL (Telstra)?
I'm totally at a loss now...
Any help would be much appreciated, thanks heaps in advance.
from what I've read recently Samsung has stopped people being able to switch as of android 11.
maybe... I stress MAYBE according to your countryman Hugh Jefferys, if there's a lower version of firmware on the same binary number you might be able to downgrade and then that might mean you can switch CSC.
this is someone who's never even tried changing CSC telling you this so your own research is obviously the only thing to put some faith in.
good luck
XSG (UAE) firmware is part of the OJM multi CSC, whereas XSA/OPS/TEL are part of the OLM multi CSC. This means that it is not possible to simply flash XSA in Odin as the multi CSCs are different, you would first have to use the combination ROM to change from OJM to OLM and then you would be able to flash any OLM CSC firmware, whether that be Australia, Singapore, Malaysia, or Thailand. I'm an Aussie myself, I got my phone from JB Hi Fi but switched it to Thailand CSC since XSA updates are horrendously slow (Samsung Pay does still work on Thailand CSC as does VoLTE/VoWiFi). For your case though, I'm afraid you are out of luck in terms of changing the multi CSC with the combination ROM, if you are on One UI 3.1 then the bootloader version is U2 whereas the combination ROM bootloader version is U1, so you would not be able to flash it anyway. Also, I tried to flash the combination ROM while my bootloader was still on U1 because I wanted to change from OLM to OXM (Romania CSC) for fastest updates, but Odin was not allowing the flash first because of "please get the approval to flash factory images (pit)" which I fixed, then "please get the approval to flash factory images (abl)" at which point I gave up. So as I said before, sorry but I don't think there's a lot you can do Unless a U2 bootloader version combination ROM is leaked which may or may not happen and you can get around the Odin not allowing you to flash it issues, the phone will unfortunately be stuck on UAE firmware (unless there are other countries part of OJM which you could switch to for faster updates).
Hopefully this helps you.
I have the same model! I changed my CSC but for some reason chat features in messaging app doesn't work now..other than that, all's good..
Skhux said:
I have the same model! I changed my CSC but for some reason chat features in messaging app doesn't work now..other than that, all's good..
Click to expand...
Click to collapse
Your software version is was originally XSA, so you wouldn’t have any issues flashing it with XSA and defaulting to XSA instead of another region. The CSC will automatically default back to XSA.
Mine unfortunately defaults to Malaysia XME when flashed with XSA firmware.
FedoraMaster420 said:
XSG (UAE) firmware is part of the OJM multi CSC, whereas XSA/OPS/TEL are part of the OLM multi CSC. This means that it is not possible to simply flash XSA in Odin as the multi CSCs are different, you would first have to use the combination ROM to change from OJM to OLM and then you would be able to flash any OLM CSC firmware, whether that be Australia, Singapore, Malaysia, or Thailand. I'm an Aussie myself, I got my phone from JB Hi Fi but switched it to Thailand CSC since XSA updates are horrendously slow (Samsung Pay does still work on Thailand CSC as does VoLTE/VoWiFi). For your case though, I'm afraid you are out of luck in terms of changing the multi CSC with the combination ROM, if you are on One UI 3.1 then the bootloader version is U2 whereas the combination ROM bootloader version is U1, so you would not be able to flash it anyway. Also, I tried to flash the combination ROM while my bootloader was still on U1 because I wanted to change from OLM to OXM (Romania CSC) for fastest updates, but Odin was not allowing the flash first because of "please get the approval to flash factory images (pit)" which I fixed, then "please get the approval to flash factory images (abl)" at which point I gave up. So as I said before, sorry but I don't think there's a lot you can do Unless a U2 bootloader version combination ROM is leaked which may or may not happen and you can get around the Odin not allowing you to flash it issues, the phone will unfortunately be stuck on UAE firmware (unless there are other countries part of OJM which you could switch to for faster updates).
Hopefully this helps you.
Click to expand...
Click to collapse
Thanks for the detailed reply.
From what I’ve tested, I have no issues with flashing from XSG OJM Multi to XSA OLM Multi. You can do this provided the FIrmware security number is the same as your current revision. You can’t however flash to a lower security value. See image attached.
The current firmware security value at the moment is “2” running One UI 3.1, Android 11. We can’t downgrade to any security firmware version “1” types with Android 10. If we could, then you can use multiple methods to manually change the CSC .i.e through Google Dialer or IMEI trick.
All the Firmwares at the moment are still Muti regional, unfortunately there doesn’t seem to be a way to change the CSC manually even though they are Multi regional.
All XSA firmwares I’ve downloaded and flashed will keep defaulting to XME as that’s the default unless my original CSC was XSA to begin with for it to detect.
I think the only option at the moment is to use SAMKEY, unless someone comes with with a new Android 11 method...
The other option is to root the phone and ADB to change the CSC, however this would trigger and break KNOX securities.
I did check Samkeys update log and they state it’s supported now, this method wouldn’t trigger KNOX;
VERSION 3.63.9 (PLANET EARTH'S FIRST)
- Added support for G780F (Galaxy S20 FE) ALL BIT
- Added support for G781B (Galaxy S20 FE 5G) ALL BIT
- Fixed FAIL(16) on Slow PC's
- Fixed FAIL(20) on G780F
They’re actually up to VERSION 3.71.9 now.
Might be worth a try.
kuri_2k said:
I think the only option at the moment is to use SAMKEY, unless someone comes with with a new Android 11 method...
The other option is to root the phone and ADB to change the CSC, however this would trigger and break KNOX securities.
I did check Samkeys update log and they state it’s supported now, this method wouldn’t trigger KNOX;
VERSION 3.63.9 (PLANET EARTH'S FIRST)
- Added support for G780F (Galaxy S20 FE) ALL BIT
- Added support for G781B (Galaxy S20 FE 5G) ALL BIT
- Fixed FAIL(16) on Slow PC's
- Fixed FAIL(20) on G780F
They’re actually up to VERSION 3.71.9 now.
Might be worth a try.
Click to expand...
Click to collapse
I can confirm SamKEY works on One UI 3.1, unfortunately it is paid but it does work. You can get an account for cheap from eBay with 1 credit on it which is all you need to do the CSC change. Using it I was able to change from XSA to THL (with no data wipe at all which really surprised me).
kuri_2k said:
Your software version is was originally XSA, so you wouldn’t have any issues flashing it with XSA and defaulting to XSA instead of another region. The CSC will automatically default back to XSA.
Mine unfortunately defaults to Malaysia XME when flashed with XSA firmware.
Click to expand...
Click to collapse
Trust me you wouldn't want XSA firmware anyway, the updates are terribly slow for it for the S20 FE 5G (not sure about 4G), it tends to get security patches a month after they should've came out, for example it got the March security patch in April which is pretty awful imo. I think it's the slowest CSC in general for the G781B, if you're on OLM multi CSC you're much better off switching to THL where the updates are a lot faster.
kuri_2k said:
Thanks for the detailed reply.
From what I’ve tested, I have no issues with flashing from XSG OJM Multi to XSA OLM Multi. You can do this provided the FIrmware security number is the same as your current revision. You can’t however flash to a lower security value. See image attached.
The current firmware security value at the moment is “2” running One UI 3.1, Android 11. We can’t downgrade to any security firmware version “1” types with Android 10. If we could, then you can use multiple methods to manually change the CSC .i.e through Google Dialer or IMEI trick.
All the Firmwares at the moment are still Muti regional, unfortunately there doesn’t seem to be a way to change the CSC manually even though they are Multi regional.
All XSA firmwares I’ve downloaded and flashed will keep defaulting to XME as that’s the default unless my original CSC was XSA to begin with for it to detect.
Click to expand...
Click to collapse
That's interesting, I didn't think it was possible to change between multi CSCs like this without the combination ROM (how you were able to switch from OJM to OLM). If you try to switch to an OXM multi CSC such as DBT or ROM from OLM multi CSC, what happens? Does it work? I'll be honest I never tried it myself but didn't have the motivation to try it anyway as I heard it wouldn't work.
FedoraMaster420 said:
That's interesting, I didn't think it was possible to change between multi CSCs like this without the combination ROM (how you were able to switch from OJM to OLM). If you try to switch to an OXM multi CSC such as DBT or ROM from OLM multi CSC, what happens? Does it work? I'll be honest I never tried it myself but didn't have the motivation to try it anyway as I heard it wouldn't work.
Click to expand...
Click to collapse
Hi There,
Yes, im sure it works provided the security firmware version is the same as I mentioned above.
I also changed to BTU to test.
I can't test for you any longer as I've returned the device for a refund. Will go buy an AUS XSA Variant.
Attached are the images of my original and changed firmware for your reference.
kuri_2k said:
Hi There,
Yes, im sure it works provided the security firmware version is the same as I mentioned above.
I can't test for you any longer as I returned the device for a refund. Will buy an AUS XSA Variant.
Attached are the images of my original and changed firmware for your reference.
Click to expand...
Click to collapse
That's very interesting, when you get the XSA variant can you try and see if you are able to flash a CSC such as ROM or DBT on the phone successfully using Odin? I would love to know if it was possible for this to work or not, I'm on THL myself after changing from XSA and did not think it was possible to switch to a different multi CSC (from OLM to OXM).
FedoraMaster420 said:
I can confirm SamKEY works on One UI 3.1, unfortunately it is paid but it does work. You can get an account for cheap from eBay with 1 credit on it which is all you need to do the CSC change. Using it I was able to change from XSA to THL (with no data wipe at all which really surprised me).
Click to expand...
Click to collapse
Wish I tried it before returning the device. The Australian stock only has 6GB RAM and no dual-sim....
kuri_2k said:
Wish I tried it before returning the device. The Australian stock only has 6GB RAM and no dual-sim....
Click to expand...
Click to collapse
Yeah that's true no 8GB variant sold here as far as I know not even on the Samsung website and we don't even get eSIM support either
Is there an update/workaround on this issue?
are there any methods that work without samKey?
Noticed that the dialer app that was once able to record calls, is now recording only me talking, since the latest OTA updates on the stock firmware (updated to oneUI 3.1 and Android 11).
I'm also on XSG (OJM) firmware and want to change CSC to enable call recording on galaxy S20 FE 5G (model G781B).
Would love to know how can it be done.
*my software info is attached in the screenshot
thanks!
VM57 said:
Is there an update/workaround on this issue?
are there any methods that work without samKey?
Noticed that the dialer app that was once able to record calls, is now recording only me talking, since the latest OTA updates on the stock firmware (updated to oneUI 3.1 and Android 11).
I'm also on XSG (OJM) firmware and want to change CSC to enable call recording on galaxy S20 FE 5G (model G781B).
Would love to know how can it be done.
*my software info is attached in the screenshot
thanks!
Click to expand...
Click to collapse
I'm sure by now you've already sorted this, but this is for future people with a need to change CSC
The SamFW FRP Tool can tell you which CSCs are available on your phone already, and can automatically have the CarrierPreConfig service trigger a CSC update. Only need to enable USB Debugging. No root, no reinstall.
But if your phone doesn't have the CSC you need already, download Frija, or another firmware download tool, you'll be able to download and install an OXM Multi CSC firmware (such as XSA, OPS, TEL or VAU), and install it via ODIN tool.
Be sure to select HOME_CSC to keep your data, and backup first.
Peterepeat87 said:
I'm sure by now you've already sorted this, but this is for future people with a need to change CSC
The SamFW FRP Tool can tell you which CSCs are available on your phone already, and can automatically have the CarrierPreConfig service trigger a CSC update. Only need to enable USB Debugging. No root, no reinstall.
But if your phone doesn't have the CSC you need already, download Frija, or another firmware download tool, you'll be able to download and install an OXM Multi CSC firmware (such as XSA, OPS, TEL or VAU), and install it via ODIN tool.
Be sure to select HOME_CSC to keep your data, and backup first.
Click to expand...
Click to collapse
Thank you, mate! I have just registered here specifically to thank you You really were the last random post I found in the internet that helped me to solve this unflashable state of my S9. Thank you again! <O
hi
G988B
under softwareinformation i have AUT/AUT,AUT/EUY/AUT all fine
the other G988B
i see AUT/AUT,AUT/EUY/SWC no native Videocalling
both have the same Provider AUT
Both of them are rooted
how can i change the swc to AUT?
Thanks for help me, i spend 4 days for this problem
If you live in Switzerland, using any SIM, reboot to recovery, and it should pick-up the AUT CSC automatically.
Samsung disabled CSC changing using dial pad codes since February, 2021. So it's either root, or official way. There's a hard trick to change CSC without tripping KNOX, if you want it I'll bring it.
i live in switzerland and my provider is sunrise both of them.
Basebandversion for both is G998BXXU8DUF9.
I Reboot to recovery but still SWC at the end.
the other 3 AUT , i change it self in the DAT files