Develop Bugs

How to flash a AT&T Galaxy S9 SM-G960U with a T-Mobile Stock Rom?

Hello,
I've been trying to find my answers on how to flash a AT&T GS9 SM-G960U with a T-Mobile S9 Stock Firmware\ROM.
I found this thread and although it's fairly close to what I am trying to do, I didn't want to post this there because they are talking about flashing U1 to U and I'm not sure if that is what I need to do exactly. https://forum.xda-developers.com/galaxy-s9/how-to/how-to-flash-u1-firmware-to-device-t3765200 from this thread, I've followed the initial steps and although Odin (Moded Odin v3.13.1 Raymonf ) tells me that the flash passed, upon reboot, the phone does not have the TMO firmware, it's still the original AT&T firmware. The only thing that it did do was add the TMO Visual VM icon\app.
I was informed of being able to download the TMO firmware from here: https://www.droiddosh.com/2018/04/samsung-galaxy-s9-sm-g960u-firmware-tmobile-usa-G960USQU1ARBG.html
Am I doing something wrong here? It seems that maybe these US models do not offer the OEM Bootloader unlocker option in developer settings unless you purchase the U1 version direct from Samsung that does not have a locked boot loader? I got this phone at no cost so that is also why I did not purchased from Samsung directly.
Any guidance and help would be appreciated.
Thank you

US carrier models have locked bootloaders, no way to root or install custom roms.
We should be able to flash between carrier versions/CSCs like we could with the S8, but the process is different and I've only read of a few people finding success in trying. The voicemail app you're seeing is due to flashing the T-Mobile userdata partition. This is the bloat partition - doesn't actually change device features, etc.

Any chance anybody has success doing this? It seems like a "Must Have" feature to switch carrier roms on the G960U between carriers, including Boot Screen/Logo, Firmware, Bloatware, etc.
All the goodies.
Any help?
Thank you,

I've done it!
dovid said:
Any chance anybody has success doing this? It seems like a "Must Have" feature to switch carrier roms on the G960U between carriers, including Boot Screen/Logo, Firmware, Bloatware, etc.
All the goodies.
Any help?
Thank you,
Click to expand...
Click to collapse
I've completed this task tonight thanks to some great help from a user that stepped me through it on a TMO Forum.
First an FYI, I first was able to flash my AT&T S9 version from SM-960U to a Stock SM-960U1. It worked great. After that, I was able to flash the TMO Rom and it's also working perfect. I'm not sure if it's required or not to flash the phone to a U1 first or if the TMO Rom can just be flashed. After I flashed the TMO firmware, I had no issues downloading and installing the latest TMO update. (My device is unlocked as well)
It's best to use Samsung switch first to backup your texts, pics, etc. first if you want to restore them to the device after completing the flash. The below instructions will start the phone up as if it was new out if the box.
Here is what I was provided with and the steps I followed.
To Flash the SM-G960U to a SM-G960U1
1. Allow\Enable USB Debugging in Developers settings.
2. Download the U1 Firmware here: https://androidfilehost.com/?w=files&flid=257063
(this is the U1 from Samsung, it's compressed but once extracted it will be around 4GB's of data.)
3. Download the ADB tools: https://devfiles.co/download/PDYvOWBg/platform-tools-latest-windows.zip. Create a folder on your desktop and name it ADB (for easy reference)
4. Download Odin: https://drive.google.com/file/d/10dSyPTuccP8Km9MnDrvbRdS-CAcgFZB3/view
5. From windows, run command prompt, in the command prompt type the following: cd C:\Users\XXX\Desktop\ADB
(XXX is your username)
6. Connect your phone to a USB port on your computer, your phone should prompt you to allow the connection to\from your computer. Allow the connection. Might be best to choose to "Always Allow"
7. Return to the command prompt and type in: adb devices You should see your device listed.
8. In the same command window, type in: adb reboot bootloader This will auto reboot your device into the "Download" mode.
9. Open and run Odin, add the corresponding tar files to the respective area's, in the "options tab" in Odin, make sure that only "Auto Reboot" and "F. Reset Time" is checked.
Click "Start" and the process will take a few minutes to complete.
Allow the device a few minutes to auto reboot and start up.
After you get through all the post boot setup screens, open a phone dial pad and type in, *#2263#. then make sure that all LTE bands are enabled.
Here you can find the SM-G960U T-Mobile Files: https://www.droiddosh.com/2018/04/samsung-galaxy-s9-sm-g960u-firmware-tmobile-usa-G960USQU1ARBG.html

Switching from U -> U1 -> U
B"H
Ok, thank you.
1. So stock G960U (Original Carrier) -> Flash to U1 -
2. Then, Go from G960U1 -> Stock G960U (Any Carrier)
Few questions:
1. Which CSC file are you using to flash -- CSC_HOME?
2. In moving from U1 -> U, do you need the final carrier SIM inside the phone?
I've tried this with a Verizon phone I'd like to convert to XFinity (CCT). I flashed the G960U VZW to G960U1 XXA. That worked fine. Then I flashed the G960U CCT rom, and the phone just boots up Verizon. When I check the CSC, it says "VZW/VZW/VZW", even though I flashed the CCT rom.
I don't have an XFinity sim card, so perhap that is the problem.
Any help would be great.

dovid said:
B"H
Ok, thank you.
1. So stock G960U (Original Carrier) -> Flash to U1 -
2. Then, Go from G960U1 -> Stock G960U (Any Carrier)
Few questions:
1. Which CSC file are you using to flash -- CSC_HOME?
2. In moving from U1 -> U, do you need the final carrier SIM inside the phone?
I've tried this with a Verizon phone I'd like to convert to XFinity (CCT). I flashed the G960U VZW to G960U1 XXA. That worked fine. Then I flashed the G960U CCT rom, and the phone just boots up Verizon. When I check the CSC, it says "VZW/VZW/VZW", even though I flashed the CCT rom.
I don't have an XFinity sim card, so perhap that is the problem.
Any help would be great.
Click to expand...
Click to collapse
You most likely will need a Xfinity Sim Card. I was able to convert my Xfinity Mobile S9 to AT&T by going to U1 firmware then inserting my AT&T sim card then flashing the AT&T U firmware.

ajairola said:
You most likely will need a Xfinity Sim Card. I was able to convert my Xfinity Mobile S9 to AT&T by going to U1 firmware then inserting my AT&T sim card then flashing the AT&T U firmware.
Click to expand...
Click to collapse
Where is the at&t u firmware? Currently on the unlocked firmware. Thanks

Savebig said:
Where is the at&t u firmware? Currently on the unlocked firmware. Thanks
Click to expand...
Click to collapse
Go to this thread (thanks @iBowToAndroid) and then look in the RB7 folder on Android File host.

Question
Does anyone know if you have to have the phone unlocked before changing over carriers? for example if i had a Galaxy S9 from Sprint and wanted to change the firmware to T-Mobile would it work or would it still be locked to Sprint? Thanks for your Help!

B AdamsHxC said:
Does anyone know if you have to have the phone unlocked before changing over carriers? for example if i had a Galaxy S9 from Sprint and wanted to change the firmware to T-Mobile would it work or would it still be locked to Sprint? Thanks for your Help!
Click to expand...
Click to collapse
Have the same question, but on my Verizon Note 8...

PieceofSlice said:
Have the same question, but on my Verizon Note 8...
Click to expand...
Click to collapse
I would check if your phone is already unlocked, Most Verizon phones come unlocked (unless you bought them from a Verizon Tent at Cosco or stores like that) Just put in another carriers sim card and check, if it is unlocked then you shouldnt have to flash anything, once you put in a different carrier sim it will tell you to restart your phone and once you do it will come up with the new carriers splash logo and apps

PieceofSlice said:
Have the same question, but on my Verizon Note 8...
Click to expand...
Click to collapse
In my experience all the carrier S9s are locked. You will need an unlock code from your carrier or an unlocking service.

Noob here: I’ve read that all US S9 models are the same in terms of hardware, is that true? Would that mean if I change the firmware from verizon to T-Mobile, it’ll be fully compatible?

Xamuyees said:
Noob here: I’ve read that all US S9 models are the same in terms of hardware, is that true? Would that mean if I change the firmware from verizon to T-Mobile, it’ll be fully compatible?
Click to expand...
Click to collapse
Yes! All 965U's, 965U1's, and 965W's are the exact same hardware, just different firmware.

For those of you that use TMO or U1 firmware on an unlocked ATT phone on TMO network, do you get a <Subject: NoSubject> before other people's texts in group texts? I've tried flashing U and U1 firmware several times as well as factory reset without being able to get rid of the subject line. Anyone have any insight or suggestions?

I was able to go from U1 to the att firmware. My question is why does samsung pass not work? I can see that the knox is not tripped and google play store is certified. Device status says official. Device is not rooted but Samsung pass thinks it is rooted. Why would this happen when all I did was install the carrier bundle?

(Newbie) doing what jrockz3000 did would allow root to be possible?

MFmvrdoc said:
(Newbie) doing what jrockz3000 did would allow root to be possible?
Click to expand...
Click to collapse
Unfortunately not. All North American S9s are not able to be rooted at this point.

ajairola said:
Unfortunately not. All North American S9s are not able to be rooted at this point.
Click to expand...
Click to collapse
Thank you man~

Odin link down
jrockz3000 said:
I've completed this task tonight thanks to some great help from a user that stepped me through it on a TMO Forum.
First an FYI, I first was able to flash my AT&T S9 version from SM-960U to a Stock SM-960U1. It worked great. After that, I was able to flash the TMO Rom and it's also working perfect. I'm not sure if it's required or not to flash the phone to a U1 first or if the TMO Rom can just be flashed. After I flashed the TMO firmware, I had no issues downloading and installing the latest TMO update. (My device is unlocked as well)
It's best to use Samsung switch first to backup your texts, pics, etc. first if you want to restore them to the device after completing the flash. The below instructions will start the phone up as if it was new out if the box.
Here is what I was provided with and the steps I followed.
To Flash the SM-G960U to a SM-G960U1
1. Allow\Enable USB Debugging in Developers settings.
2. Download the U1 Firmware here:
(this is the U1 from Samsung, it's compressed but once extracted it will be around 4GB's of data.)
3. Download the ADB tools: . Create a folder on your desktop and name it ADB (for easy reference)
4. Download Odin:
5. From windows, run command prompt, in the command prompt type the following: cd C:\Users\XXX\Desktop\ADB
(XXX is your username)
6. Connect your phone to a USB port on your computer, your phone should prompt you to allow the connection to\from your computer. Allow the connection. Might be best to choose to "Always Allow"
7. Return to the command prompt and type in: adb devices You should see your device listed.
8. In the same command window, type in: adb reboot bootloader This will auto reboot your device into the "Download" mode.
9. Open and run Odin, add the corresponding tar files to the respective area's, in the "options tab" in Odin, make sure that only "Auto Reboot" and "F. Reset Time" is checked.
Click "Start" and the process will take a few minutes to complete.
Allow the device a few minutes to auto reboot and start up.
After you get through all the post boot setup screens, open a phone dial pad and type in, *#2263#. then make sure that all LTE bands are enabled.
Here you can find the SM-G960U T-Mobile Files:]
Click to expand...
Click to collapse
Odin link down.

[GUIDE]: G975F - Flashing megathread + FAQs

Since the official firmware thread by @henklbr is flooded with posts asking how to flash rather than actual firmware update talk, this thread can be used for that instead.
Here's the Odin flashing guide at the beginning of the thread which nobody will read.
How to flash the stock Odin flashable firmware:
1) Download Odin v3.13.1 - Link
2) Extract the firmware file you just downloaded. You should get 5 files:
AP (System & Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_OXM (OXM CSC file, will wipe your phone)
HOME_CSC_OXM (OXM CSC file, will NOT wipe your phone)
3) Add each file to it's respective field in Odin v3.13.1. Use CSC_OXM if you want to do a clean flash and HOME_CSC OXM if you want to keep your apps and data.
4) Reboot your phone in Download / Odin mode:
-Power off your Galaxy S10/S10+
-Connect the cable to your PC, but do not plug it into your phone yet
-Hold Volume Down + Bixby button and plug the Type C cable into your phone while holding down those buttons
-You will get a warning on your screen, press 'Continue'
5) Once in download mode, Odin should detect your device and a blue box will show up with the COM port number.
6) Do NOT tick any extra boxes. The only options to be ticked are F.Reset Time and Auto-Reboot and they are enabled by default.
7) Click the start button, wait for Odin to say 'PASS'. Once the flash is complete, your phone will reboot automatically.
Flashing Tips:
1) Always try to use the OEM Samsung USB-C cable when flashing.
2) Install Samsung Smart Switch before flashing, it automatically installs the latest Samsung USB drivers. However, make sure Smart Switch is CLOSED when you are flashing your device with Odin.
3) Try not to have too many other applications running if you have a PC with low RAM as Odin can consume a lot of memory sometimes, and the last thing you need is for your PC to freeze in the middle of a flash.
This is what a successful flash log on Odin looks like for an S10+ ----> Pastebin Link
--------------------------------------------------------------------------------------------------------
Before asking a question below, read the FAQs, your question has most probably already been answered.
Q1) Will this trip KNOX, and will I lose my warranty?
Short answer: No
Detailed answer: KNOX counter will remain at 0x0 and warranty stays valid as well.
However, some service centers might note regional differences between builds based on the latest build available for your CSC, indicating that the phone has been flashed, so if you're sending your device in for a service/repair/replacement, then I'd suggest flashing to the latest build available for your home country's CSC. Usually not required though, so not a big deal.
--------------------------------------------------------------------------------------------------------
Q2) What if the firmware build number mentioned above is not available for my CSC, can I still flash it?
Short answer: Yes, but that is subject to your current active CSC. Read detailed answer below.
Detailed answer: See this list --- > LINK
--------------------------------------------------------------------------------------------------------
Q3) I flashed 'ASxx' build, but now I can't get OTAs for a newer build that's available on my CSC?
Short answer: The build you are currently running on your device was never released for your CSC, so no subsequent OTA file is available on the server.
Detailed answer: This is due to Samsung's stupid update rollout methods. Go to SamMobile, select SM-G975F and find your region in the list, and flash whatever the latest build is to regain the ability to receive OTAs.
--------------------------------------------------------------------------------------------------------
Q4) Can I flash the ROM in the main post without flashing the builds that came before it?
Short answer: Yes.
Detailed answer: The firmwares available for download using SamFirm or Frija are full firmware files. Flashing them will manually flash (and update, if necessary) every partition on your phone. So you could be on the oldest firmware ever released for the S10+, and flash directly to the latest one without having to flash any builds released in between.
--------------------------------------------------------------------------------------------------------
Q5) Can I flash without wiping my data?
Short answer: Yes.
Detailed answer: If you've gotten to this question, you clearly haven't read the Odin flashing instructions.
If you want to flash and retain all the data on your phone, you can choose to use the HOME_CSC file when flashing. This will only upgrade your phone to the newer firmware, but allow you to keep all your data.
--------------------------------------------------------------------------------------------------------
Q6) I am on a carrier firmware, can I flash this firmware?
Short answer: Yes, but all your data will be erased.
Detailed answer: If you are on a carrier firmware that is not part of the OXM multi-CSC list given in the answer for Q2, then you can still flash OXM firmwares, but you will not have the option of using the HOME_CSC file to retain your data. You must wipe your data when switching from a carrier firmware to an unbranded firmware. Once you are on the unbranded OXM firmware, you can use HOME_CSC to upgrade without wiping data.
--------------------------------------------------------------------------------------------------------
Q7) If I flash AUT region firmware on my DBT device, will it affect my ability to get OTA updates?
Short answer: Maybe, maybe not.
Detailed answer: Read the answer of Q3.
--------------------------------------------------------------------------------------------------------
Q8) Is there any risk of flashing?
Short answer:No, not really.
Detailed answer: If you are not experienced with flashing but would still like to flash your phone, make sure to be very very careful and don't miss any steps in the process. There is usually no risk, and it is very hard to permanently brick your device when flashing stock ROMs. There is a chance of data loss if the flash is interrupted.
--------------------------------------------------------------------------------------------------------
Q9) Why does the window says 'FAIL' instead of PASS?
Short answer: Could be for multiple reasons, see detailed answer.
Detailed answer: If a flash fails, always make sure to copy and paste your Odin log here so we can see where and why the flash failed.
The Odin flash log can be seen on the bottom left of the Odin window, see this screenshot ---> Odin 3.13.1 screenshot
--------------------------------------------------------------------------------------------------------
Q10) Why does the Odin log show that the flash failed at sboot.bin.lz4?
Short answer: The version of your Odin is not compatible with newer firmwares that use lz4 compression.
Detailed answer: Samsung started using .lz4 compression with Oreo firmwares, so older versions of Odin can't be used.
Use Odin v3.13.1 (Download link) for flashing on the S10+.
--------------------------------------------------------------------------------------------------------
Q11) Why does the Odin flash log show FAIL (XmitDataWrite)?
Short answer: There was an issue flashing the AP (System) file to your device. Read detailed answer on how to solve.
Detailed answer: This is usually due to an issue with the USB port or the cable being used to flash the device. If you are using a USB 3.0 port on your PC / laptop, try switching to a USB 2.0 port instead. If you don't have a USB 2.0 port available, change the cable. Some cables don't handle large file transfers well. Preferably use the OEM Samsung cable that you got in the box of your phone.
--------------------------------------------------------------------------------------------------------
Q12) Where can I download the latest S10+ (SM-G975F) firmwares?
Answer: You can use Frija which downloads the firmwares straight from Samsung servers - Link
--------------------------------------------------------------------------------------------------------
Q13) What do the CSCs in the settings menu mean?
Answer: See below.
Single SIM device:
If you have a Single SIM device, it will show 3 CSCs in the settings menu, in the following format:
DBT/DBT/DBT
1st CSC = active CSC (You will get OTAs for this CSC and any features like Samsung Pay, VoLTE, WiFi calling are dependent on the active CSC)
2nd CSC = CSC of your SIM card (In case your SIM card is from a different region than your active CSC, this will be different from the active CSC)
3rd CSC = Hardware CSC of your device (For example, you purchased the device in Germany, but are living in the Netherlands, it will show PHN/PHN/DBT)
It is not possible to change the hardware CSC, and it has 0 effect on the device's functionality or when it will get OTA updates. It is simply an indicator for what market the device was intended for sale in.
Dual SIM device:
If you have a Dual SIM device, it will show 4 CSCs in the settings menu, in the following format:
DBT/DBT,DBT/DBT
1st CSC = active CSC (You will get OTAs for this CSC and any features like Samsung Pay, VoLTE, WiFi calling are dependent on the active CSC)
2nd CSC = CSC of your SIM card (In case your SIM card is from a different region than your active CSC, this will be different from the active CSC)
3rd CSC = CSC of your SIM card in SIM slot 2
4th CSC = Hardware CSC of your device (For example, you purchased the device in Germany, but are living in the Netherlands, it will show PHN/PHN,PHN/DBT)
It is not possible to change the hardware CSC, and it has 0 effect on the device's functionality or when it will get OTA updates. It is simply an indicator for what market the device was intended for sale in.
--------------------------------------------------------------------------------------------------------
Q14) Why did my CSC change to XEF (France) after flashing from a carrier ROM to the unlocked ROM?
Answer: For OXM firmwares on the S10 series, when flashing from a non-OXM ROM (such as a carrier ROM) to an OXM multi-CSC ROM, the active CSC defaults to XEF.
Detailed answer: For devices that are region locked, once you flash from carrier to unlocked, it will stay on XEF. There is no way to change CSC yet without root.
For devices that are not region locked, it will change to XEF, but to switch to the unlocked CSC for your region, remove your SIM card, insert it again and do a factory reset from the settings menu.
--------------------------------------------------------------------------------------------------------
Q15) Can I downgrade to an older build?
Answer: It depends on your current build. Sometimes you can downgrade, sometimes you can not. Read detailed answer to check.
Detailed answer:
You have to see the bootloader version of your current build. Samsung tends to upgrade bootloader versions regularly so downgrading is not always possible.
For example if your current build is G975FXXU3ASG8, and you want to downgrade to G975FXXU2ASF3, it will not be possible.
Moving from 'XXU3' to 'XXU2' is not possible since XXU2 is an older bootloader version, and because of Samsung's downgrade protection, it will not allow the older version to be flashed.
When attempting to flash, Odin will show 'FAIL' in the flash window, and the bootloader screen on your device will display this error:
SW REV CHECK FAIL(BOOTLOADER) DEVICE: 3, BINARY: 2
This is showing that the device is currently on a v3 build, and the build being flashed is v2, so it will reject the file and abort the flash immediately.
If however you want to downgrade from G975FXXU3ASG8 to G975FXXU3ASG2, you are free to do so, since both builds are labeled 'XXU3' and are on the same bootloader version (i.e: v3).
Note: Some builds will be labeled 'XXS', and the same reasoning applies to those builds as well. If the bootloader version is different, you can not downgrade.
--------------------------------------------------------------------------------------------------------
Q16) Why are some builds labeled 'XXU', whereas some builds are labeled 'XXS'?
Answer:
XXU builds are usually larger updates, they usually include security patches, kernel changes and other under the hood fixes. When new features are added, they are also usually shipped with 'XXU' builds.
XXS builds are maintenance releases. They just include security patches and nothing more. OTA sizes for XXS builds are usually significantly smaller as well. In some cases, exceptions can be made and new kernels can be included with XXS builds as well.
These changes are usually discussed in the stock firmware thread for the device.
For newly released devices in the first 6-8 months, almost all builds are XXU since Samsung is actively working on improving the device.
For devices nearing EOL, Samsung is only fulfilling its obligation to provide security patches and no new features, so most builds are XXS.
--------------------------------------------------------------------------------------------------------

First! Just installed ASE7 (AUT) over ASE6 (BTU) using HOME_CSC (I was already on BTU). Very nice it is like real OTA because bloatware wasn't installed. Phone working...
additional info: My S10 (not +) was branded in Czech T-Mobile TMZ/TMZ,TMZ/TMZ now is BTU/BTU,BTU/TMZ and all is good. Still obserwing stuff around Samsung

Flashing for dummies guide is very useful. Thanks

To keep root when flashing new firmware, you patch the AP file in Magisk then use that patched .tar file in the AP slot in odin, right?

vibrantliker said:
To keep root when flashing new firmware, you patch the AP file in Magisk then use that patched .tar file in the AP slot in odin, right?
Click to expand...
Click to collapse
I haven't rooted my phone, but have read about it, and yes that seems to be the way to go about it.
Lots of people complaining that they have to patch the entire 5 GB AP file.

The list of CSCs included in the OXM multi-CSC has now been updated for the Galaxy S10/S10+.
Link is in the main post, and here as well:
https://drive.google.com/open?id=1PPPo1DhdVAIJDha6kEmIDE4UxyxtEsBHqONlE81QvEc

Hi there,
My OPS (OPTUS) Is a multi CSC carrier but since I do not longer use it in Australia but rather in South America,I would like to change my CSC to perhaps DBT so I can get the latest OTA updates.
Is it possible to change my CSC?
I use the Claro SIM here and I have successfully updated the AS7 firmware.
Thanks.

Cancerbero04 said:
Hi there,
My OPS (OPTUS) Is a multi CSC carrier but since I do not longer use it in Australia but rather in South America,I would like to change my CSC to perhaps DBT so I can get the latest OTA updates.
Is it possible to change my CSC?
I use the Claro SIM here and I have successfully updated the AS7 firmware.
Thanks.
Click to expand...
Click to collapse
Your device seems to be region locked to OPS which is why it isn't offering automatic CSC change.
I need to experiment with the complicated CSC change method on my own S10+ first and then I'll post it here.

My S10+ has the active CSC code as TTT, the device doesn't receive OTA software updates and I notice your listing has TTT as N/A, would this be why I haven't received the OTA updates? I've flashed the latest ones manually. I've tried to change the CSC by flashing XEF, BTU, SKR, TPA and EON as I'm from Trinidad, but nothing has changed the CSC, all my other Samsung devices, including my other S10+ has the active CSC as TPA and they receive updates. All are unlocked and have sims from the same carrier. Any ideas as to how to change it to get OTA updates?

Gdefreitas said:
My S10+ has the active CSC code as TTT, the device doesn't receive OTA software updates and I notice your listing has TTT as N/A, would this be why I haven't received the OTA updates? I've flashed the latest ones manually. I've tried to change the CSC by flashing XEF, BTU, SKR, TPA and EON as I'm from Trinidad, but nothing has changed the CSC, all my other Samsung devices, including my other S10+ has the active CSC as TPA and they receive updates. All are unlocked and have sims from the same carrier. Any ideas as to how to change it to get OTA updates?
Click to expand...
Click to collapse
Did you buy the device from a carrier, or unlocked?
I've got TTT listed as N/A since I wasn't aware which country / carrier it belonged to.

MeltdownSpectre said:
Did you buy the device from a carrier, or unlocked?
I've got TTT listed as N/A since I wasn't aware which country / carrier it belonged to.
Click to expand...
Click to collapse
It's an unlocked device that's purchased from a retailer, I'm not sure where their supplier is located, my guess would be Panama. TTT is Trinidad and Tobago, I'm from Trinidad, but instead of my device CSC being TPA like the other devices that gets the update, mine is TTT/TTT, TTT/TPA. I just would like to change it to TPA to be able to get updates, or even EON which is the CSC for firmwares for Trinidad.

Gdefreitas said:
It's an unlocked device that's purchased from a retailer, I'm not sure where their supplier is located, my guess would be Panama. TTT is Trinidad and Tobago, I'm from Trinidad, but instead of my device CSC being TPA like the other devices that gets the update, mine is TTT/TTT, TTT/TPA. I just would like to change it to TPA to be able to get updates, or even EON which is the CSC for firmwares for Trinidad.
Click to expand...
Click to collapse
What carrier are you using in Trinidad?
Maybe TTT is for a specific carrier, and since that's part of OXM, your phone automatically selects that CSC.
Although it is very weird that the FOTA server doesn't list any OTAs for TTT, which means you'll have to flash every update manually.

MeltdownSpectre said:
What carrier are you using in Trinidad?
Maybe TTT is for a specific carrier, and since that's part of OXM, your phone automatically selects that CSC.
Although it is very weird that the FOTA server doesn't list any OTAs for TTT, which means you'll have to flash every update manually.
Click to expand...
Click to collapse
I'm using Bmobile, which is the carrier all my other devices use as well, and they show the CSC as TPA, so they receive the updates. Their is no TTT firmware for the S10+, but there is for the S10. I assumed that would mean no firmware updates, and I only received one, but that was when I now purchased the phone, after that I had to factory reset the phone and since then, I haven't gotten any OTAs. Is there anyway to change the CSC to TPA? I've tried flashing the other firmwares, the BTU, XEF, SKR, but none of them changed the CSC from TTT. Any suggestions?

Gdefreitas said:
I'm using Bmobile, which is the carrier all my other devices use as well, and they show the CSC as TPA, so they receive the updates. Their is no TTT firmware for the S10+, but there is for the S10. I assumed that would mean no firmware updates, and I only received one, but that was when I now purchased the phone, after that I had to factory reset the phone and since then, I haven't gotten any OTAs. Is there anyway to change the CSC to TPA? I've tried flashing the other firmwares, the BTU, XEF, SKR, but none of them changed the CSC from TTT. Any suggestions?
Click to expand...
Click to collapse
Can you try swapping the SIM card from another phone of yours to the S10+?
After inserting the SIM card, restart the phone and check what it shows under settings > about > software information > service provider SW Ver.

MeltdownSpectre said:
Can you try swapping the SIM card from another phone of yours to the S10+?
After inserting the SIM card, restart the phone and check what it shows under settings > about > software information > service provider SW Ver.
Click to expand...
Click to collapse
I've tried that, even tried from the other carrier available in my country, but it still doesn't change. It remains as TTT. It's the dual sim version, although I've never even inserted a second sim into it, that slot shows TTT as well.

MeltdownSpectre said:
Can you try swapping the SIM card from another phone of yours to the S10+?
After inserting the SIM card, restart the phone and check what it shows under settings > about > software information > service provider SW Ver.
Click to expand...
Click to collapse
I saw another one of your posts where it mentioned using RealTerm to change the CSC, can this be used with my device, and if so, how do I go about doing it? Thanks for any assistance you may be able to render.

Gdefreitas said:
I saw another one of your posts where it mentioned using RealTerm to change the CSC, can this be used with my device, and if so, how do I go about doing it? Thanks for any assistance you may be able to render.
Click to expand...
Click to collapse
In theory the RealTerm method should work just fine. All you'll need is a combination / factory binary file for the G975F. The rest of the tutorial should work the same way.
I think I have the file, I'll check and upload it later today.

MeltdownSpectre said:
In theory the RealTerm method should work just fine. All you'll need is a combination / factory binary file for the G975F. The rest of the tutorial should work the same way.
I think I have the file, I'll check and upload it later today.
Click to expand...
Click to collapse
OK, thanks a lot, I'll give it a try. Just for the sake of knowing, could you explain what exactly the combination file is, and does it work on any software version of the device, or is it firmware specific? In other words, will it work on the ASE7 build that I'm presently on? Also, will I continue to get OTA updates after switching the CSC this way?

Gdefreitas said:
OK, thanks a lot, I'll give it a try. Just for the sake of knowing, could you explain what exactly the combination file is, and does it work on any software version of the device, or is it firmware specific? In other words, will it work on the ASE7 build that I'm presently on? Also, will I continue to get OTA updates after switching the CSC this way?
Click to expand...
Click to collapse
Combination or factory binary is the file used in Samsung factories and service centers to program phones before sale or return to the customer.
It does work as long as the Bootloader revision is the same. If you are on the May update or older, it will work just fine.
You flash it with Odin like you would a normal ROM, and it will boot up with very limited functionality. Then follow the RealTerm tutorial and set the CSC to whatever you'd like.
If it's TPA, then once you're done changing the CSC, flash your device to the ASE7 May build and let it boot up, go through the setup wizard and it should say TPA/TPA,TPA/TPA.
Once you've confirmed that TPA is the active CSC, then you're good to go. Everything will work normally and you will get OTA updates as well.
I'm uploading the factory binary now, but since I don't recommend publicly posting the link, I'll PM it to you once it's done.

Hey guys, sorry if this has been asked and answered a thousand times but I'm a bit paranoid after doing the research and as this is a my new phone I don't want to do anything wrong.
I bought a carrier locked S10+ with MOB CSC, A1 carrier in Austria. The phone is now carrier unlocked and on latest MOB firmware which is May 1. sec. lvl. I want to flash the lastest released MULTI-CSC G975FXXU2ASF3 firmware from the firmware thread. As the phone is new and I didn't even set it up I planned to flash with CSC_OXM. From my understanding the phone will change to the SIMs CSC after the flash. Am I correct?
Am I able to do this as planned or is it not possible to flash MULTI-CSC over my MOB-CSC? Will I be able to receive OTA updates or do I need to flash everytime with ODIN after CSC change? Thanks in advance!

ATT -> Unlocked firmware help?

Have a carrier unlocked ATT device, and want to flash unlocked firmware.
Can someone explain in detail the steps to do this?

Randomtandem said:
Have a carrier unlocked ATT device, and want to flash unlocked firmware.
Can someone explain in detail the steps to do this?
Click to expand...
Click to collapse
I would also like to know that Bought note 10+ few days ago and didn't checked if it's debranded version. I have downloaded the newest Odin and newest firmware
Product code XEO
PDA N975FXXS1BSLD
CSC N975FOXM1BSL7
Is there anything important i should know before i proceed?
THX

Randomtandem said:
Have a carrier unlocked ATT device, and want to flash unlocked firmware.
Can someone explain in detail the steps to do this?
Click to expand...
Click to collapse
I'M NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOU DEVICE!
THIS IS THE PATH I TOOK.
I'll pass on to you what I did. I flashed over SPR unlocked.
1. Download frija, you can Google this. It's a neat tool to quickly download firmware.
Type in the model number of your phone, and add a 1 at the end... Example... I own the N975U, from Sprint. Add the 1 at the end for unlocked... N975U1. And in the CSC slot, type XAA.
XAA is unlocked CSC code for US.
Firmware should show last digits BSLD for January security patch and Android 10.
Unzip the downloaded firmware somewhere close. I did mine on the desktop.
2. Download Samsung Drivers and install.
3. Download Odin V3 V 3.13.1_3B Patched.
Add the files into Odin.
On the CSC, do NOT use Home CSC. Use the regular.
You absolutely have to factory reset your device when switching to Unlocked or vice versa. So you might want to backup using Samsung smart switch or Google. Which ever you prefer.
Do not add any user data when switching from carrier to unlocked.
4. Place phone into Download mode BEFOR plugging into computer.
5. At this point... Phone should be in download mode. 4 files should be added into Odin. No other changes in Odin should be made. And CSC should be regular and not Home CSC.
6. Plug phone into computer and see if you see the device in Odin.
If you see it, great. Proceed to flash.
Odin likes to verify for awhile so don't mind this. Leave it be. If it gets stuck more than 10 minutes saying verifying, you may need to Google the issue.
Once Odin says passed... You should be good to go.
Phone will reboot, phone will factory reset.
At this point, you should be done.
I'M NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOU DEVICE!
THIS IS THE PATH I TOOK.

You mention the CSC should be XAA, when it comes to ODIN you mention regular?
Can you clarify that part?
Add the files into Odin.
On the CSC, do NOT use Home CSC. Use the regular.
You absolutely have to factory reset your device when switching to Unlocked or vice versa. So you might want to backup using Samsung smart switch or Google. Which ever you prefer.
Click to expand...
Click to collapse
In addition, do I have to backup the contents (no user data on it currently)?

Randomtandem said:
You mention the CSC should be XAA, when it comes to ODIN you mention regular?
Can you clarify that part?
In addition, do I have to backup the contents (no user data on it currently)?
Click to expand...
Click to collapse
It's two different things that's being referred too. When you download the firmware there isn't just one and they are identified by CSC. TMB is for T-Mobile, CHA is Spectrum Mobile, SPR is Sprint.. to name a few.
In your particular case when you download the unlocked firmware you would search for the CSC "XAA" (without quotes) as this is the firmware from the unlocked note 10+
Second when you flash the firmware you need to place different files into the appropriate and applicable locations within Odin. One of those spots you place a file into is called "CSC".
Also no you don't need to backup anything if you don't have anything installed (or no userdata on it).
If you have further questions I would suggest you search this forum and/or Google. The question on flashing the N975U1 firmware onto the N975U has been asked before and covered in detail already more then once... So those other threads will be of help for you.

How To Guide F926U and F926U1 Firmware Links and Flashing Discussion Here

For those who aren't already aware, F926U is the model number of all of the US carrier versions of the Z Fold3. The F926U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. A "U to U" or "U1 to U1" flash does not require a factory reset, but changing from one firmware to the other will require one. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.
Manual Odin flashing is designed for those who:
- want to manually update to a newer version of U firmware on their U device, either because they don't want to wait for their carrier's OTA or because OTAs aren't working on their device, or a different carrier got a new feature/patch before they did
- want to flash U1 firmware to their U device
- want to convert from U1 firmware to carrier U firmware
- want to convert from one carrier's U firmware (with all apps and bloatware) to a different carrier's U firmware (with all apps and bloatware)
For those who aren't already aware, anyone can now download firmware for almost any Samsung device any time that they want, via the various firmware download tools posted here on XDA like SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But they only provide whatever the latest/newest/current version is - nothing older. I have access to an internal Samsung firmware download tool that usually gets new versions before they hit the public firmware download tools, so that's where my files come from.
This is not a "beginner's guide to Odin flashing" -type post/thread, so I won't list basic, step-by-step flashing instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware (or haven't done it in a long time), I recommend you consult one of those "beginner's" guides- there are tons of them here on XDA.
Happy flashing!
U firmware: https://www.androidfilehost.com/?w=files&flid=327754
U1 firmware: https://www.androidfilehost.com/?w=files&flid=327755
Notes:
- DON'T QUOTE THE OP WHEN YOU REPLY, kthx
- I have lots of threads just like this one for other Samsung flagships, if it interests you. For those who have already made use of my previous threads for a different device and are upgrading, welcome back
- My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- it's quite time consuming to download the files, zip them up, and upload them to AFH. And, I do threads like this for every single flagship model, so I won't be uploading every single version. The only full builds that I upload are ones where I get access to a new bootloader and/or Android version early, before they hit the firmware download tools.
- My naming method for folders on AFH is: build - bootloader - Android version
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- HOME CSC file keeps data intact; using the other CSC will wipe data. Flashing USERDATA will also wipe data.
- Since AT&T doesn't allow their firmware to be publicly available (for any of their devices), I'll try to always upload at least one USERDATA per bootloader increment for AT&T (and Cricket, if they get this model). I'll also upload any full builds if AT&T is the only carrier to get that specific build, because you won't be able to find the files anywhere else.
- For identifying USERDATAS, and to know what region/CSC to use in the firmware download tools if you're downloading yourself:
AIO = Cricket (not available via firmware download tools)
ATT = AT&T (not available via firmware download tools)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
DSH = Dish Network
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via firmware download tools, but Manual Entry is required - Auto will not work)
XAA = U1 firmware

Is there a T-Mobile version available yet?

ruthlessnature said:
Is there a T-Mobile version available yet?
Click to expand...
Click to collapse
Yep, firmware has been on Samsung's servers since last week

iBowToAndroid said:
Yep, firmware has been on Samsung's servers since last week
Click to expand...
Click to collapse
I downloaded the file from samefirm, and frija but did not get the carrier bloat or T-Mobile boot screen from either one. I have an unlocked version.

ruthlessnature said:
I downloaded the file from samefirm, and frija but did not get the carrier bloat or T-Mobile boot screen from either one. I have an unlocked version.
Click to expand...
Click to collapse
You need to make sure your CSC shows as TMB, and need to make sure you're flashing USERDATA too

iBowToAndroid said:
You need to make sure your CSC shows as TMB, and need to make sure you're flashing USERDATA too
Click to expand...
Click to collapse
That's strange, neither one I downloaded has TMB in the csc, do you have a link ?

ruthlessnature said:
That's strange, neither one I downloaded has TMB in the csc, do you have a link ?
Click to expand...
Click to collapse
I'm not talking about the firmware. I'm talking about the phone itself, in the Settings

Oh, I see, it doesn't change, shows xaa/xaa/xaa I downloaded the ATT userdata to flash and see if it changes it.

ruthlessnature said:
Oh, I see, it doesn't change, shows xaa/xaa/xaa I downloaded the ATT userdata to flash and see if it changes it.
Click to expand...
Click to collapse
If you want T-Mobile bloatware, you need to insert a T-Mobile SIM so that the CSC changes to TMB. And then you need to flash a U firmware with T-Mobile USERDATA

iBowToAndroid said:
If you want T-Mobile bloatware, you need to insert a T-Mobile SIM so that the CSC changes to TMB. And then you need to flash a U firmware with T-Mobile USERDATA
Click to expand...
Click to collapse
Thanks for the info, I couldn't get it to flash back to the u1 firmware until I downloaded the patched Odin. Then I was able to I put my Sim, the csc showed TMB and then I was able to flash the u firmware with the TMB userdata. Thanks again for your help.

ruthlessnature said:
Thanks for the info, I couldn't get it to flash back to the u1 firmware until I downloaded the patched Odin. Then I was able to I put my Sim, the csc showed TMB and then I was able to flash the u firmware with the TMB userdata. Thanks again for your help.
Click to expand...
Click to collapse
You're welcome!

ruthlessnature said:
Thanks for the info, I couldn't get it to flash back to the u1 firmware until I downloaded the patched Odin. Then I was able to I put my Sim, the csc showed TMB and then I was able to flash the u firmware with the TMB userdata. Thanks again for your help.
Click to expand...
Click to collapse
For anyone looking for that it's here: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/

I'm getting a weird Complete(Write) Operation Failed error when flashing any tips?
NVM gotta have USB Debugging on

wschamps42 said:
I'm getting a weird Complete(Write) Operation Failed error when flashing any tips?
NVM gotta have USB Debugging on
Click to expand...
Click to collapse
Uhhhh what? Flashing is done in Download mode, not Normal mode

can we flash a different region firmWARE (UK / EUROPE) to the U1? Given the phones are all Qualcomm SD now

Drnms said:
can we flash a different region firmWARE (UK / EUROPE) to the U1? Given the phones are all Qualcomm SD now
Click to expand...
Click to collapse
Nope

I appologize for being the super noob. A couple questions.
Does using this process disable the cameras as mentioned in https://forum.xda-developers.com/t/unlocking-bootloader-will-disable-the-camera.4321957/page-.
You stated that there are tons of beginners guides. In doing searches I find multiple different guides with different completely different processes. Is there one that you recommend or works best?
My goal is to make my unlocked fold3 more usable on ATT/firstnet. There are multiple features I cannot use and I don't receive same call quality service as my wife's locked att fold3.

sllong said:
I appologize for being the super noob. A couple questions.
Does using this process disable the cameras as mentioned in https://forum.xda-developers.com/t/unlocking-bootloader-will-disable-the-camera.4321957/page-.
You stated that there are tons of beginners guides. In doing searches I find multiple different guides with different completely different processes. Is there one that you recommend or works best?
My goal is to make my unlocked fold3 more usable on ATT/firstnet. There are multiple features I cannot use and I don't receive same call quality service as my wife's locked att fold3.
Click to expand...
Click to collapse
You will not lose the cameras as you are flashing firmware not unlocking the bootloader.

sllong said:
My goal is to make my unlocked fold3 more usable on ATT/firstnet. There are multiple features I cannot use and I don't receive same call quality service as my wife's locked att fold3.
Click to expand...
Click to collapse
Under Settings-->About-->Software Information, what's the last line of your "Service provider SW ver" item?

iBowToAndroid said:
Under Settings-->About-->Software Information, what's the last line of your "Service provider SW ver" item
Click to expand...
Click to collapse
iBowToAndroid said:
/xaa/xaa/xaa
Click to expand...
Click to collapse

Change Active CSC Code to Firmware CSC Code

I just got a galaxy s10+ from a friend who was on Tmoblie so it has the Tmoblie loading screen and apps. I would like to revert it back to the firmware CSC code XAA so I dont have to have the Tmoblie boot screen and apps. He didn't buy it from tmoblie its from an insurance company so I am pretty sure its unlocked. The app "Phone Info" says that Firmware's CSC code is XAA and the active one is TMB. I have tried to put in the *#272*IMEI# code into the phone but it just gives me an error code.
Is there anyway to revert it back to XAA without flashing the phone? Will I void the warranty if i flash the phone with official firmware? Also if I have to flash the phone where do I find XAA firmware as I only saw carrier firmware on SamMoblie.
Thanks for any help and very sorry if this has been posted a thousand times!
Also the phone model is SM-N975U / Galaxy Note10+
Device Type: d2q
Product Name: d2qsq
Bootloader Version: N975USQS6FUF1
CSC Version: N975UOYN6FUF1
Phone is on Android 11

I just flashed the phone and it all worked out. I used these threads to figure out the solution if anyone else is ever interested in how I solved this problem.
Note 10+ N975U carrier universal and unlocked models firmware.
Yep. I'm going to download the files just in case ,but wait a few days to see if anything happens.I'm curious if that was your issue all this time .
forums.androidcentral.com
Odin Files/Guides For S21
Flashing S21 Ultra t-mobile branded to unlocked? Hi Everyone, I am a new samsung owner. I recently got s21 ultra t-mobile branded. It is now network unlocked. But i wanted to have a clean bloat free phone so wanted to have unlocked firmware. As i understand it, i need XAA G998-UA firmware...
forums.androidcentral.com
And I used this very kind user on Androidcentrals help. The context of my question is not needed but I basically asked if I was choosing the correct files.
"Yes use the firmware from frija , you will also need prince comsey patched Odin which download from XDA website, this will factory reset your device for first time , choose XAA as region with model number from unlocked version. (He is refering to the model number SM-N975U1) Put the device in download mode and make sure using a good cable and try 7zip to extract the firmware,odin,frija ...then after extract the the firmware you going take for files Cp/CSC,Bl,Ap and put in corresponding slots in odin and flash"