Related
I've read that the Galaxy S9 hardware is identical for all carriers in the USA.
If I bought a factory unlocked Galaxy S9 can I flash it to the carrier I am using (Verizon, Sprint, T-Mobile, AT&T) to enable carrier specific software and features? Can I flash it back to the unlocked firmware?
I already see a thread about flashing the unlocked firmware to carrier models so I am assuming there are no issues there.
Can one carrier model be flashed to another carrier model?
No, bootloaders are different, with the S7 there was an unbranded U firmware that was compatible with most of them, unlocked firmware will be that one for the S9, but no you cannot just flash different device firmwares to the wrong model
I was able to flash the ATT rom onto my Verizon S9. I got a VZ s9 from work but I'm on ATT. For the most part it's worked great, I had done the same thing previously with a Galaxy S7. I say for the most part b/c I am on here tonight to post a question myself about the fact that I'm getting a delay with MMS messages. I imagine it has something to do with the APNs I have setup, but I can't seem to figure it out.
toronado13 said:
I was able to flash the ATT rom onto my Verizon S9. I got a VZ s9 from work but I'm on ATT. For the most part it's worked great, I had done the same thing previously with a Galaxy S7. I say for the most part b/c I am on here tonight to post a question myself about the fact that I'm getting a delay with MMS messages. I imagine it has something to do with the APNs I have setup, but I can't seem to figure it out.
Click to expand...
Click to collapse
Did you have to flash to the U1 software first?
I do think that is what I ended up doing... tried to go directly first and it kept failing. Got fed up and decided to just try and put the bone stock rom on it, and that went on really easily.... so after using it like that a few days I tried to drop the ATT rom on it and it worked without issue.
SEALBoy said:
I've read that the Galaxy S9 hardware is identical for all carriers in the USA.
If I bought a factory unlocked Galaxy S9 can I flash it to the carrier I am using (Verizon, Sprint, T-Mobile, AT&T) to enable carrier specific software and features? Can I flash it back to the unlocked firmware?
I already see a thread about flashing the unlocked firmware to carrier models so I am assuming there are no issues there.
Can one carrier model be flashed to another carrier model?
Click to expand...
Click to collapse
Yes, but you need to go to the u1 firmware 1st then to the other carrier firmware. Also make sure you avoid the newer firmwares with the new bootloader, as the unlocked model and certain carrier models don't have the new bootloader.
*Detection* said:
No, bootloaders are different, with the S7 there was an unbranded U firmware that was compatible with most of them, unlocked firmware will be that one for the S9, but no you cannot just flash different device firmwares to the wrong model
Click to expand...
Click to collapse
lolol
yes u can.. u can flash between U and U1 firmwares no problem..
normally ud b correct tho but since s8/s8+ it has been ok.. just cant flash 9600 or 9650 to a U or U1 device
elliwigy said:
lolol
yes u can.. u can flash between U and U1 firmwares no problem..
normally ud b correct tho but since s8/s8+ it has been ok.. just cant flash 9600 or 9650 to a U or U1 device
Click to expand...
Click to collapse
That'll be why I still thought that then, coming straight from the S7 > S9
Had many members flashing the wrong firmwares thinking they could do that and bricking their S7s / wondering why ODIN failed
*Detection* said:
That'll be why I still thought that then, coming straight from the S7 > S9
Had many members flashing the wrong firmwares thinking they could do that and bricking their S7s / wondering why ODIN failed
Click to expand...
Click to collapse
I tried downloading vzw firmware G960USQS3ARI6 to my unlocked sprint s9 and still not vzw flashed. want to do this so can have voice over LTE. Any other steps im missing? flash went through but still sprint
As soon as Firmware ver. 3 came out for the G960U1, I was able to flash it to my Sprint G960U and finally have VoLTE, WiFi calling and stable LTE for MetroPCS. Used samkey to unlock it from Sprint. My phone is actually performing much faster without all of Sprint's bloatware hogging my RAM and storage space. I can confirm that OTA updates still work the same...I received September's security patch (current) with no problems. Device is still official status and Knox hasn't been tripped.
A lot of people think you can just flash the carrier firmware of your choice and boom, it works...I had the same thought process....that's not the case. You have to make sure that there is a matching firmware version for the carrier you want to flash to, as well as make sure the G960U1 firmware version (the unlocked version of the S9's software you have to flash first before even carrier flashing) is the same version of what is installed on your phone now. It's easy ya'll......just READ lol.
I'm in love with my phone again thanks to XDA. ?
HAPPY FLASHING!
nickosarus2008 said:
As soon as Firmware ver. 3 came out for the G960U1, I was able to flash it to my Sprint G960U and finally have VoLTE, WiFi calling and stable LTE for MetroPCS. Used samkey to unlock it from Sprint. My phone is actually performing much faster without all of Sprint's bloatware hogging my RAM and storage space. I can confirm that OTA updates still work the same...I received September's security patch (current) with no problems. Device is still official status and Knox hasn't been tripped.
A lot of people think you can just flash the carrier firmware of your choice and boom, it works...I had the same thought process....that's not the case. You have to make sure that there is a matching firmware version for the carrier you want to flash to, as well as make sure the G960U1 firmware version (the unlocked version of the S9's software you have to flash first before even carrier flashing) is the same version of what is installed on your phone now. It's easy ya'll......just READ lol.
I'm in love with my phone again thanks to XDA.
HAPPY FLASHING!
Click to expand...
Click to collapse
Hi, I got one unlocked G960U1(G960U1UES3ARI1) and downloaded new fireware(G960U1UES3ARI1-SPR) from sammobile, but after flashed SPR ROM successfully, the info on the phone still shows XAA, anything I missed here? Thanks!
Curtis2018 said:
Hi, I got one unlocked G960U1(G960U1UES3ARI1) and downloaded new fireware(G960U1UES3ARI1-SPR) from sammobile, but after flashed SPR ROM successfully, the info on the phone still shows XAA, anything I missed here? Thanks!
Click to expand...
Click to collapse
Well first off, you have the unlocked phone. I don't. My G960U is originally from Sprint, so I'm not sure about carrier flashing regarding the G960U1. I thought it was supposed to provision itself after you put the sim in, and the associated carrier apps will download since it's the unlocked model...but I may be wrong...
SEALBoy said:
I've read that the Galaxy S9 hardware is identical for all carriers in the USA.
If I bought a factory unlocked Galaxy S9 can I flash it to the carrier I am using (Verizon, Sprint, T-Mobile, AT&T) to enable carrier specific software and features? Can I flash it back to the unlocked firmware?
I already see a thread about flashing the unlocked firmware to carrier models so I am assuming there are no issues there.
Can one carrier model be flashed to another carrier model?
Click to expand...
Click to collapse
I know so many people have already answered your question from some saying No to others saying Yes but you need to Install U1 first and Bla Bla Bla.
I want to give you one specific answer: With S9 you can any Carriers firmware you wish or even Unlocked phone's firmware. You will never have any issue. And you don't ever need to flash U1 or something else before changing carrier firmware you can Flash from ATT S9 firmware to VZW S9 firmware without any issue. You can also flash from U to U1 which is from Carrier specific to Unbranded/Unlocked but only hiccup is original Odin will give you SHA-256 error, which is normal because you are flashing U1 firm to U device or vice versa. This error can easily be resolved by used Patched odin that disabled SHA-256 check. And trust me you will never have any issue.
You will never want to do this but I have gone as far as mix-matching U and U1 firmware together as well. Like flashing AP, BL and CP of U device but flashing CSC of U1 device. and it still works.
hey there, a little late to the party, having trouble with going from a Verizon to a Sprint, even by way of U1. I can't get any of them to work. And I've been told I have to go from VZW to U1 before I went to Sprint. Is that not the case? I'm having a hell of a time getting anything to flash, everything fails.
---------- Post added at 03:08 AM ---------- Previous post was at 02:57 AM ----------
ret4425 said:
hey there, a little late to the party, having trouble with going from a Verizon to a Sprint, even by way of U1. I can't get any of them to work. And I've been told I have to go from VZW to U1 before I went to Sprint. Is that not the case? I'm having a hell of a time getting anything to flash, everything fails.
Click to expand...
Click to collapse
well, I tried to load the Sprint image from the VZW, no dice. It said it passed, but upon reboot loaded up the old Big Red (even with the Sprint SIM in it).
Anyone have any ideas? This is driving me insane....
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!
Hi All,
I have Samsung S9 Unlocked T-mobile from US and currently in India. Currently i have Oreo Version.
As all know, it doesnt have VOLTE option enabled which is needed for my sim network for voice calls to go through.
Somewhere i read Pie update will have VOLTE option and hence i am trying to update to Pie update.
I downloaded G960USQS6CSGB firmware for T-mobile, but before upating firmware using Odin, i got doubt if it will stick to T Mobile after update. This will make my phone not usable in India.
I tried to check online, but couldnt get direct answer and hence posting in new thread.
Can someone help clarify if it will lock the mobile to T-Mobile or will the phone be still in unlocked state?
Also i see two CSC files in the firmware folder. CSC and HOME_CSC. Which one to use?
If I should update with some other firmware for being unlocked and yet to get PIE update, please point to required firmware name or links.
Also will updating to PIE update will have VOLTE option ? Kindly confirm.
Thanks in Advance.
abalanag said:
Hi All,
I have Samsung S9 Unlocked T-mobile from US and currently in India. Currently i have Oreo Version.
As all know, it doesnt have VOLTE option enabled which is needed for my sim network for voice calls to go through.
Somewhere i read Pie update will have VOLTE option and hence i am trying to update to Pie update.
I downloaded G960USQS6CSGB firmware for T-mobile, but before upating firmware using Odin, i got doubt if it will stick to T Mobile after update. This will make my phone not usable in India.
I tried to check online, but couldnt get direct answer and hence posting in new thread.
Can someone help clarify if it will lock the mobile to T-Mobile or will the phone be still in unlocked state?
Also i see two CSC files in the firmware folder. CSC and HOME_CSC. Which one to use?
If I should update with some other firmware for being unlocked and yet to get PIE update, please point to required firmware name or links.
Also will updating to PIE update will have VOLTE option ? Kindly confirm.
Thanks in Advance.
Click to expand...
Click to collapse
csc will factory reset your phone, home_csc wont
volte wasnt removed from pie, so that shouldnt be an issue
the firmware version you posted has the 6th bootloader revision, im betting here is a 7th available for your phone, but the 6th version should be fine as well
as far as the unlocked state of the phone goes, it shouldnt re-lock, but im paranoid lol. Have you looked into the U1 versions of the phones firmware? Theyre inherently unlocked firmwares and dont have any of that irritating bloatware **** in them
youdoofus said:
csc will factory reset your phone, home_csc wont
volte wasnt removed from pie, so that shouldnt be an issue
the firmware version you posted has the 6th bootloader revision, im betting here is a 7th available for your phone, but the 6th version should be fine as well
as far as the unlocked state of the phone goes, it shouldnt re-lock, but im paranoid lol. Have you looked into the U1 versions of the phones firmware? Theyre inherently unlocked firmwares and dont have any of that irritating bloatware **** in them
Click to expand...
Click to collapse
Thanks youdoofus the inputs. Say by chance if it gets locked, is there a way to unlock the phone again from here?
may be then i will try to load U1 versions otherwise. Thanks alot.
abalanag said:
Thanks youdoofus the inputs. Say by chance if it gets locked, is there a way to unlock the phone again from here?
may be then i will try to load U1 versions otherwise. Thanks alot.
Click to expand...
Click to collapse
if it has no financial obligation to any carrier and the phone locks to that carrier, then the carrier it locked to would be required to release it. I cant imagine how it would lock to t-mob tho
Factory unlocked phones stay unlocked, no matter what firmware you flash.
Carrier locked phones that were properly unlocked by the carrier (they provide the code to SIM unlock the phone) will stay unlocked, again, no matter what firmware you flash to it - as long as it's compatible. Flashing the wrong firmware may just brick the phone. But, at least it's still SIM unlocked.
Phones that had some kind of software hack installed to trick the phone into thinking it's unlocked will lose the unlock status when you flash a firmware that also wipes the phone. Then it will come back as carrier locked again, because the hack is gone.
That last case is the only case I know of that will "re-lock" a phone. I've never heard of a carrier unlocked phone spontaneously re-locking under any circumstance.
Hi,
Thanks for the details. I tried to flash G960U1UES6CSG4_G960U1OYM6CSG4_XAA firmware. But while loading AP file in ODIN, it gave some error. Couldnt understand what is the error as its in chinese.
Then i loaded G960USQS6CSGB_G960UOYN6CSGB_TMB firmware which i downloaded previously. This got loaded in ODIN without any issues. And i am able to flash to phone. On rebooting, saw that phone moved to Pie version.
But i couldnt find VOLTE option (Enhanced calling) option. Does anyone know which version will enable that option?
Or anyother way to enable that please.
Thanks in advance.
joeldf said:
Factory unlocked phones stay unlocked, no matter what firmware you flash.
Carrier locked phones that were properly unlocked by the carrier (they provide the code to SIM unlock the phone) will stay unlocked, again, no matter what firmware you flash to it - as long as it's compatible. Flashing the wrong firmware may just brick the phone. But, at least it's still SIM unlocked.
Phones that had some kind of software hack installed to trick the phone into thinking it's unlocked will lose the unlock status when you flash a firmware that also wipes the phone. Then it will come back as carrier locked again, because the hack is gone.
That last case is the only case I know of that will "re-lock" a phone. I've never heard of a carrier unlocked phone spontaneously re-locking under any circumstance.
Click to expand...
Click to collapse
another user just posted up in another thread that they had a factory cricket phone that got unlocked, he put an at&t sim in it and it installed at&t apps and locked the phone to at&t FWIW
---------- Post added at 02:42 PM ---------- Previous post was at 02:36 PM ----------
abalanag said:
Hi,
Thanks for the details. I tried to flash G960U1UES6CSG4_G960U1OYM6CSG4_XAA firmware. But while loading AP file in ODIN, it gave some error. Couldnt understand what is the error as its in chinese.
Then i loaded G960USQS6CSGB_G960UOYN6CSGB_TMB firmware which i downloaded previously. This got loaded in ODIN without any issues. And i am able to flash to phone. On rebooting, saw that phone moved to Pie version.
But i couldnt find VOLTE option (Enhanced calling) option. Does anyone know which version will enable that option?
Or anyother way to enable that please.
Thanks in advance.
Click to expand...
Click to collapse
if your Odin error messages are in Chinese, youve obtained a modified version. Itll probably work, but youll get that Chinese stuff whenever it needs to tell you anything. I dont know which versions have volte tbh. Sorry man.
youdoofus said:
another user just posted up in another thread that they had a factory cricket phone that got unlocked, he put an at&t sim in it and it installed at&t apps and locked the phone to at&t FWIW
---------- Post added at 02:42 PM ---------- Previous post was at 02:36 PM ----------
if your Odin error messages are in Chinese, youve obtained a modified version. Itll probably work, but youll get that Chinese stuff whenever it needs to tell you anything. I dont know which versions have volte tbh. Sorry man.
Click to expand...
Click to collapse
Thanks youdoofus for trying to help. For me atleast it didnt get locked when i moved to Pie. I will try other methods.
I will try to root the phone for enabling volte, but the methods that i tried didnt work.
youdoofus said:
another user just posted up in another thread that they had a factory cricket phone that got unlocked, he put an at&t sim in it and it installed at&t apps and locked the phone to at&t FWIW
Click to expand...
Click to collapse
That's just weird.
joeldf said:
That's just weird.
Click to expand...
Click to collapse
yeah, sort of. The CSC's on these things are weird. Im starting to believe that these new versions of android are just like windows ISOs where they have all the versions compressed into one file and it uses a directory file to tell the firmware which version to install. Im sure a code writing dev can confirm or deny this thought, but at this point its merely a weak theory
2019-10-08_21:17:56 Device Info:
MAC : 44:91:60:6F8:11
MACs : 44:91:60:6F8:11 46:91:60:6F8:11
Root : false
VirtualMachine : false
build.characteristics : nosdcard
build.display.id : PPR1.180610.011.G960USQS6CSGB
build.fingerprint : samsung/starqltesq/starqltesq:9/PPR1.180610.011/G960USQS6CSGB:user/release-keys
build.host : SWDH7918
build.id : PPR1.180610.011
build.incremental : G960USQS6CSGB
build.release : 9
build.sdk : 28
build.tags : release-keys
build.time : 1563280950
build.type : user
build.user : dpi
clientidbase : android-samsung-ss android-tmus-us-revc
cpu.abi : arm64-v8a
cpu.abilist : arm64-v8a,armeabi-v7a,armeabi
cpu.abilist32 : armeabi-v7a,armeabi
cpu.abilist64 : arm64-v8a
hardware : qcom
iso-country : us
maps :
/data/app/air.com.vudu.air.DownloaderTablet-t5mbVjvM1FFl0QEUPwzQyw==/base.apk
/data/app/app.greyshirts.firewall-d39DVNDNC1T-3kBvPh9atA==/base.apk
/data/app/cn.trinea.android.developertools-i-YQ40tKZG_8h1XUaPXnNw==/base.apk
/data/app/com.bigsing.changer-vw1KB9QxofVWzkNA5AIQqg==/base.apk
/data/app/com.bigsing.changer-vw1KB9QxofVWzkNA5AIQqg==/lib/arm64/libdeviceid.so
/data/app/com.bigsing.changer-vw1KB9QxofVWzkNA5AIQqg==/oat/arm64/base.art
/data/app/com.bigsing.changer-vw1KB9QxofVWzkNA5AIQqg==/oat/arm64/base.odex
/data/app/com.bigsing.changer-vw1KB9QxofVWzkNA5AIQqg==/oat/arm64/base.vdex
/data/app/com.bluedf.secretcodes-HV9rnYLpul4wQolux9pzwA==/base.apk
/data/app/com.bluedf.secretcodesroot-hGA1tSj9Tvim8s_10D9gsQ==/base.apk
/data/app/com.cleanerapp.supermanager-WePEX1NMFy_p1AuwuQ-8rw==/base.apk
/data/app/com.cleanerapp.supermanager-WePEX1NMFy_p1AuwuQ-8rw==/split_config.arm64_v8a.apk
/data/app/com.cleanerapp.supermanager-WePEX1NMFy_p1AuwuQ-8rw==/split_config.en.apk
/data/app/com.cleanerapp.supermanager-WePEX1NMFy_p1AuwuQ-8rw==/split_config.xxhdpi.apk
/data/app/com.contextis.android.BLEScanner-_JPbA8nJK6dFNifXOStWBw==/base.apk
/data/app/com.cpu82.roottoolcase-LS9phULHU4si2JZypZu18g==/base.apk
/data/app/com.cradlepoint.netcloud.manager-QNZJb2X6rbWHPj0nzT26SQ==/base.apk
/data/app/com.cradlepoint.netcloud.manager-QNZJb2X6rbWHPj0nzT26SQ==/split_config.en.apk
/data/app/com.cradlepoint.netcloud.manager-QNZJb2X6rbWHPj0nzT26SQ==/split_config.xxhdpi.apk
/data/app/com.derevenetz.oleg.magicphotos-dORDc6h1twxKI0IxBcyHAw==/base.apk
/data/app/com.diamond.apps.filemanager-Zt29zbvNjupsE3yzke4RHA==/base.apk
/data/app/com.enflick.android.TextNow-2ZsLoogNdPWqIwmaQGJb2g==/base.apk
/data/app/com.eypcnn.wifipasswordshow-2cIzlBAsm7GP4BuTC9feYw==/base.apk
/data/app/com.facebook.katana-WloRDUS_s087OTw-SlM3kg==/base.apk
/data/app/com.facebook.katana-WloRDUS_s087OTw-SlM3kg==/split_arservicesoptional.apk
/data/app/com.facebook.katana-WloRDUS_s087OTw-SlM3kg==/split_rtc.apk
/data/app/com.facebook.katana-WloRDUS_s087OTw-SlM3kg==/split_streamingsdk.apk
/data/app/com.facebook.orca-tsPK3nLBiCqKSuZzFyTgeg==/base.apk
/data/app/com.facebook.orca-tsPK3nLBiCqKSuZzFyTgeg==/split_cardio.apk
/data/app/com.freeit.java-znqdl0s04I9N-fbGWtOW_A==/base.apk
/data/app/com.freeit.java-znqdl0s04I9N-fbGWtOW_A==/split_config.arm64_v8a.apk
/data/app/com.freeit.java-znqdl0s04I9N-fbGWtOW_A==/split_config.xxhdpi.apk
/data/app/com.google.android.apps.access.wifi.consumer-eQa-41SblsmvYiy0lVSy7Q==/base.apk
/data/app/com.google.android.apps.books-jjrUo5E6vP0zhGP19Fch2A==/base.apk
/data/app/com.google.android.apps.docs-Up5ehHhl3wsTfpiLF95Z4A==/base.apk
/data/app/com.google.android.apps.photos--0tzlNaW_wuwWUDJMigTww==/base.apk
/data/app/com.google.android.apps.photos--0tzlNaW_wuwWUDJMigTww==/split_config.en.apk
/data/app/com.google.android.apps.photos--0tzlNaW_wuwWUDJMigTww==/split_config.xxhdpi.apk
/data/app/com.google.android.apps.translate-nkvNQXFkcbpp1zglp84UUw==/base.apk
/data/app/com.google.android.music-a7QiK-jqDGc_rE9Fw5XOzw==/base.apk
/data/app/com.google.earth-5XZzMY1I3fKcWGaJhJ1iyg==/base.apk
/data/app/com.indeed.android.jobsearch-5ciyVRNfrci-EXuXkANUcw==/base.apk
/data/app/com.inspiredandroid.linuxcommandbibliotheca-bb3ZTfwlOfOPylFFNy0fGQ==/base.apk
/data/app/com.inspiredandroid.linuxcommandbibliotheca-bb3ZTfwlOfOPylFFNy0fGQ==/split_config.arm64_v8a.apk
/data/app/com.inspiredandroid.linuxcommandbibliotheca-bb3ZTfwlOfOPylFFNy0fGQ==/split_config.xxhdpi.apk
/data/app/com.inspiredandroid.linuxcontrolcenter-Kqp5BsR5cSkjdffSe6TuEA==/base.apk
/data/app/com.instagram.android-y85BBsblTUYo1is0WluBZA==/base.apk
/data/app/com.jao.wifi.map.hotspot.connection.wifianalyzer.password.anywhere.wifimanager-lTiKRkBr35XPsQ-_RiB_oQ==/base.apk
/data/app/com.jumobile.manager.systemapp-16NybbvDbjY_D5agiVtsGw==/base.apk
/data/app/com.kasitskyi.hiddensettings-a-osLmMm5ePEz1y3VJ7RuA==/base.apk
/data/app/com.kpstv.youtube-5fN6D5m5G0FISRCSFBWMeg==/base.apk
/data/app/com.lonelycatgames.Xplore-h8Vemfk9AJcGgO6TlEcEog==/base.apk
/data/app/com.lookout.net-PEfkrK56N9hOzHDBXAW9KA==/base.apk
/data/app/com.magdalm.usbsettings-KCF_d3UQ4pXNZJekMlYO8Q==/base.apk
/data/app/com.magdalm.usbsettings-KCF_d3UQ4pXNZJekMlYO8Q==/split_config.en.apk
/data/app/com.magdalm.usbsettings-KCF_d3UQ4pXNZJekMlYO8Q==/split_config.xxhdpi.apk
/data/app/com.mobile.antivirus.security.virus.cleaner-torftuRqVy9ycIJqODc-Lw==/base.apk
/data/app/com.movietube.fullest.inwebsite-EEkAQ5GNuzQJvizkFk2Diw==/base.apk
/data/app/com.pandora.android-lQA_FIeHZhK1xUFFO2Svyw==/base.apk
/data/app/com.paprbit.dcoder-xDi_9MfJVQAwHkehs4caTg==/base.apk
/data/app/com.propel.ebenefits--ftv6kBm2X8SHhJRyzj-IQ==/base.apk
/data/app/com.samsung.android.app.notes-XcN2lg0cZZ0I-ZK86oSPlg==/base.apk
/data/app/com.samsung.android.videolist-VwfMDYlOcOgRJj7CTx4fxQ==/base.apk
/data/app/com.sec.android.app.ocrservice-Vx7pGxQhVb9Ct_EkebxUzg==/base.apk
/data/app/com.sec.android.app.popupcalculator-uHV2SpAqv4fNWhv_wlBCTA==/base.apk
/data/app/com.sec.android.app.voicenote-mJUISc5gQ2yx9gYhJC49Tg==/base.apk
/data/app/com.sharpened.androidfileviewer-s9Z0CE2pWNr-XyeCUfIrfQ==/base.apk
/data/app/com.sharpened.androidfileviewer-s9Z0CE2pWNr-XyeCUfIrfQ==/split_config.arm64_v8a.apk
/data/app/com.sharpened.androidfileviewer-s9Z0CE2pWNr-XyeCUfIrfQ==/split_config.en.apk
/data/app/com.sharpened.androidfileviewer-s9Z0CE2pWNr-XyeCUfIrfQ==/split_config.xxhdpi.apk
/data/app/com.snapchat.android-cqgv7rBP2rPoPNuiNtwTGg==/base.apk
/data/app/com.snapchat.android-cqgv7rBP2rPoPNuiNtwTGg==/split_config.arm64_v8a.apk
/data/app/com.snapchat.android-cqgv7rBP2rPoPNuiNtwTGg==/split_config.en.apk
/data/app/com.snapchat.android-cqgv7rBP2rPoPNuiNtwTGg==/split_config.xxhdpi.apk
/data/app/com.soomapps.screenmirroring-u0awU7-A205YfaTfw3t8bw==/base.apk
/data/app/com.spatialnetworks.fulcrum-tTNdrKTK5n5g8HapjAcvXA==/base.apk
/data/app/com.spatialnetworks.fulcrum-tTNdrKTK5n5g8HapjAcvXA==/split_config.arm64_v8a.apk
/data/app/com.spatialnetworks.fulcrum-tTNdrKTK5n5g8HapjAcvXA==/split_config.en.apk
/data/app/com.spatialnetworks.fulcrum-tTNdrKTK5n5g8HapjAcvXA==/split_config.xxhdpi.apk
/data/app/com.thirtydegreesray.openhub-m-X5STyX1NiOqdIWsjHHKw==/base.apk
/data/app/com.twitter.android-CCrLl-3tWEVBih_z7Vjo7A==/base.apk
/data/app/com.twitter.android-CCrLl-3tWEVBih_z7Vjo7A==/split_config.arm64_v8a.apk
/data/app/com.twitter.android-CCrLl-3tWEVBih_z7Vjo7A==/split_config.en.apk
/data/app/com.twitter.android-CCrLl-3tWEVBih_z7Vjo7A==/split_config.xxhdpi.apk
/data/app/com.ubnt.unifihome-dWJY-qLGK6YuYRn8GBV1BQ==/base.apk
/data/app/com.xda.labs-mj8AI7PMA4ykJLKmGx6F1A==/base.apk
/data/app/duy.com.text_converter-i71QdR_GutTm06Qk_IhnxA==/base.apk
/data/app/eu.faircode.netguard-xjF0xDra31VKBHL8Nnk0OA==/base.apk
/data/app/info.valky.decryptor-QNpaSsdyNK0O06DvqskOrA==/base.apk
/data/app/mtk.engineering.mode.app.apk-cj5K8glcKnDDeaKlfy1wSw==/base.apk
/data/app/net.techet.netanalyzerlite.an-A1UGqlffdlQSxA2FMePInw==/base.apk
/data/app/options.developer.com.developeroptions-0zTXrjNvoYe-hKYjU1gouQ==/base.apk
/data/app/org.malwarebytes.antimalware-0u7tRaOtS69f-f-uAr6vnQ==/base.apk
/data/app/org.mozilla.fennec_aurora-n1jo0bDX8Jh7pYm3koDuLQ==/base.apk
/data/app/org.mozilla.firefox--wE0cOpC-5dw9t0zdv-Cyw==/base.apk
/data/app/org.pocketworkstation.pckeyboard-1y0BnUC9lJpmMo24g65nzA==/base.apk
/data/app/ru.gavrikov.mocklocations-1KKeGOBK6SYV1zwIgMaQvg==/base.apk
/data/app/scd.atools-ugyYuEQfYtLTOV4NY433Ow==/base.apk
/data/app/screenmirroring.abdelm.com.screenmirroring-DSxowgttK15MH2GEt6-lrg==/base.apk
/data/misc/zoneinfo/current/icu/icu_tzdata.dat
/dev/ashmem/dalvik-/data/app/com.bigsing.changer-vw1KB9QxofVWzkNA5AIQqg==/oat/arm64/base.art_14890_14890 (deleted)
/mnt/asec/com.effinitytech.networkexplorer-1/base.apk
product.board : sdm845
product.brand : samsung
product.device : starqltesq
product.manufacturer : samsung
product.model : SM-G960U
product.name : starqltesq
Time Used: 2.00 s
My sm-N975U AT&T note 10+ has never ever received any updates.
It's currently at Android 9, N975USQU1AS12, security patch: September 1, 2019. Since I got it in 2019.
I see that the unlocked version SM-975U1 AT&T receives updates frequently and I can easily get the firmware online.
I've not even seen any Android 10 firmware for SM-975U AT&T.
So is it possible to flash SM-975U1 AT&T unlocked over SM-975U AT&T.
Or even just to make it US unlocked with no carrier so I can receive updates from Samsung?
You can flash the N975U1 firmware onto the N975U (and vice versa) so long as the bootloader is the same version (or higher) then what is currently installed on the phone.
Three things to keep in mind:
No way exists to downgrade the bootloader... So if you flash firmware with a newer bootloader and you decide you want to go back you will not be able too.
Bootloader version can be found by doing the following. Looking at your About Phone > Software Version look at the baseband version info.. Start at the far right and count 5 characters to the left (with the first character being the far right one). The number that is the 5th character in will be the bootloader version that is currently on the phone.
The USERDATA isn't always included with the U1 firmware should you desire the AT&T version of it. You should be able to find that in this thread,
For an example the red number is the bootloader version:
N975U1OYM3CTE7
For anything else this question has been discussed here a lot so you won't have any issues finding information about it.
So this will unlock the phone? Does the same go for the Sprint version?
Nickdroid86 said:
So this will unlock the phone? Does the same go for the Sprint version?
Click to expand...
Click to collapse
You can flash the firmware from the N975U1 to the N975U (and vice versa). It doesn't matter the carrier, only the model number matters.
Just be sure to be mindful of the bootloader version.
Flashing the firmware from the N975U1 does not have any relation to the network/sim lock. For network/sim unlocking you will have to ask your provider to do this for you
The term (or name) "unlocked firmware" is derived from the phone it comes from.. The N975U1 is the carrier/network unlocked variant sold by Samsung.
so if i put the, U1 firmware to n975u and i'm out USA. now I will receive all the new updates automatically via OTA?
Excuse me, I am new to the forum, I have a question for you, I have an at & t SM-N975U, this at & t firmware does not update outside the USA, I am in Mexico, which firmware should I use, I want it to update automatically via OTA here in Mexico? t-mobile firmware or U1 firmware, I really appreciate your answer,
hello, my question is similar but regarding the carrier. My Note 10 Plus is AT&T locked, if I flash the SM-N975U1 over the SM-N975U, will that unlock the carrier so i can use anyone outside USA?
No. It won't. You'll have to have AT&T unlock it.
scottusa2008 said:
You can flash the N975U1 firmware onto the N975U (and vice versa) so long as the bootloader is the same version (or higher) then what is currently installed on the phone.
Three things to keep in mind:
No way exists to downgrade the bootloader... So if you flash firmware with a newer bootloader and you decide you want to go back you will not be able too.
Bootloader version can be found by doing the following. Looking at your About Phone > Software Version look at the baseband version info.. Start at the far right and count 5 characters to the left (with the first character being the far right one). The number that is the 5th character in will be the bootloader version that is currently on the phone.
The USERDATA isn't always included with the U1 firmware should you desire the AT&T version of it. You should be able to find that in this thread,
For an example the red number is the bootloader version:
N975U1OYM3CTE7
For anything else this question has been discussed here a lot so you won't have any issues finding information about it.
Click to expand...
Click to collapse
Hello can you please help me too
I'm super new here
So i have the N975U and i live in Europe and i don't get any updates cuz my Note 10+ is the AT&T version and now i want to change it to N975U1 so i can get updates from Samsung themselves.. from Sammobile i downloaded The N975U1OYM7GULD-(XAA) model and also N975U1OYM7GULD-AT&T model while the current one i have is N975USQS7FUI7 so both of them i think should work because they have the same bootloader so my question is since i want to get updates to which one should i flash my phone with? I heard the XAA is better because u get updates directly from Samsung themselves ( even when I'm in Europe ) and the AT&T version is also N975U1 but I'm not sure if i will be getting updates because now I already have the N975U ( probably AT&T model that's why I'm not getting anything ) So what do you think i should do?
I'd appreciate ur help
And sorry for my broken ass English hope you understood..
scottusa2008 said:
You can flash the N975U1 firmware onto the N975U (and vice versa) so long as the bootloader is the same version (or higher) then what is currently installed on the phone.
Three things to keep in mind:
No way exists to downgrade the bootloader... So if you flash firmware with a newer bootloader and you decide you want to go back you will not be able too.
Bootloader version can be found by doing the following. Looking at your About Phone > Software Version look at the baseband version info.. Start at the far right and count 5 characters to the left (with the first character being the far right one). The number that is the 5th character in will be the bootloader version that is currently on the phone.
The USERDATA isn't always included with the U1 firmware should you desire the AT&T version of it. You should be able to find that in this thread,
For an example the red number is the bootloader version:
N975U1OYM3CTE7
For anything else this question has been discussed here a lot so you won't have any issues finding information about it.
Click to expand...
Click to collapse
And should i use Odin patch or just the normal odin? I actually wanted to flash my phone with the Germany version but i don't know if it will work!!? ( You'd use odin patch you want to change region! ) so idk if it would work if i change it from N975U to N975F which is Germany model !!?
sm-g975u unlocked att phone wanting to change to tmobile. I have a tmobile sim and had originally plugged this in. The phone works fine but I recently noticed it has no Ota updates occurring. I would like to load tmobile firmware on it to enable some of the tmobile features as well but primary concern is ota updates.
the service provider sw ver.
SAOMC_SM-G975U-OYN-AT-PP-0033
ATT/ATT/ATT
BUILD NUMBER
PPR1.180610.011.G975USQS1ASD9
Ap/CP:G975USQS1ASD9
Csc:G975UOYN1ASD9
Last update may 2019
When I try says fully updated when I put it on samsung switch it says fully updated
Can this be done?
What firmware do you suggest?
Csc *#272imei#(may have that wrong) but is recognized and does work not sure when and what to use here, many options.
Also, not sure of the answer here, but if I run an update or csc change (the phone is unlocked) would it require me to unlock it again for any reason?
I am trying to get the phone close to a tmobile if that is possible
Thank you in advance if i need to give more info please let me know.
Download the firmware of your current network and flash you will begin to receive updates. However you can also flash the unbranded one which is G975U1 and you will still receive updates too
Can you give directions on how to get the firmware for the current network and how to flash the phone? I have an SM-G975U that is on SPR that I need to get to ATT so it will get updates from cricket. I have found a lot of materials on the internet and not a single one shows all of the steps clear enough for me to risk blowing up my phone. I have found the SPR files and TMK, and USA, and TMB, but no ATT.