G988B softwareinformation - Samsung Galaxy S20 / S20+ / S20 Ultra Questions &

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

Related

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

SM-R805F: CSC Change Howto, eSIM RSP v2.x Support

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?

S9 with an active PRT play CSC ( branded )

Hey Samsung Experts ! :laugh:
I'm a newbie to this CSC stuff But I'm used to flashing via odin and firmwares switching.
My question is like this : I live in Morocco and I have a Samsung S9 Exynos Sm-G960f ( dual Sim ) with an active PRT csc ( poland and I guess it is branded ) when I first got the phone a month ago I got october security patch OTA and installed it. Now my phone says it is up to date ; yet , it is stuck at october security patch. Is it a CSC related problem or poland users hadn't received any OTA ever since october ?
I want to update my phone to Pie but I don't know which firmware to use.
I downloaded the newer ISREALI one with january security patch and ILO csc.
I'm intending to flash it. And if I flash csc instead of Home_csc will my phone work normally ? I mean no IMEI or network related problems ? and will My PRT CSC be replaced with ILO ?
I have read about combination files method but it is way complicated.
thank you.
Could somebody here possibly help me out with this ?
I will be thankful , buds.

Vendor Change?

Hye guys, not sure if this has been answered before - I did try and search all around for answers.
I have a note 10 + purchased in Australia - due to the delay in carrier updates I flashed a UK firmware (though the same SM-N975 firmware) for quicker updates.
However now that I have flashed back to my AU firmware - it seems the vendor file has been overridden and is locked possibly. As everytime I install a new firmware the set up screen shows in French until I switch the language to English AU. Once set up everything works fine apart from Samsung Members app - it shows in French which I now believe is due to the vendor file being locked?
Ive tried to odin flash Userdata with the Home CSC and CSC but no luck.
Any insight would help
thank you
Change CSC with Samkey.
Sent from my SM-N976B using Tapatalk
When i switched csc from ITL (italian) to THL (Thailand) samsung members changed from italian to Thailand even though i have english(uk) as the only language installed, even samsung pay and some others

Question Multi-CSC does not aligns with SIM

Hi,
I bought a new A72 in EU with A725FOXM4AUH2 CSC on it. The problem is that it should align with Italian (ITV) or French (XER) CSC when I first boot with the french or italian SIM inside but this does not happen. I try to flash with Odin stock firmwares to reset the first boot procedure but nothing.
I tried to change it to THL CSC in order to force some kind of change. It worked but stay obviously with the default CSC of the multi CSC OLM (that's correct).
Back with Odin to OXM, it comes back to SER (Russia) CSC. Why it is not taking the SIM operator to switch to the right CSC (ITV or XER) ?
It seems like it just take a default CSC of the Multi-CSC without aligning with the SIM.
I also tried Samkey but, it says it's ok but then the CSC stay the same.
Many thanks for your help, I am really sad...
Can you state what is listed for you under service provider software version

Categories

Resources