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