Related
Hey guys
Just received a new Galaxy A3 SM-A320FL as a work phone. The phone is a German (DE) Vodafone device with CSC of VD2. I'm trying to get it on VOD (UK) so I can get VoWIFI etc.
As the CSC is a multi CSC file it's not as simple as flashing the full latest set of files from VOD (via SamFirm) via Odin as it picks up VD2 again.
I've just tried downloading and flashing XEU firmware and that worked fine, CSC changed in Phone Info etc.
When I've reflashed the VOD multi CSC file it's put VD2 back on again?
How do I get to VOD? Any ideas?? My Note8 was far easier than this!!!
Thanks
Hi, can anyone confirm if the combination file method as described here https://www.sammobile.com/forum/showthread.php?t=39155 works on the A3?
The combination file is for the A5?
Thanks
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
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
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,
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