Database Users

[UK] Unlocked S7 Edge - Enable EE features?

Hi folks,
So as in iPhone user, i've been following the latest Galaxy very closely and decided to take the plunge on Sunday!
Suffice to say, sat in front of me at the moment is my first Samsung (I went for the Edge).
I'm on EE, so i'd like to know how I go about enabling Wi-Fi calling (and VoLTE when it launches - although i'm aware it's testing in several areas at the moment) on my device. I bought it unlocked, direct from Samsung - which probably explains why I can't see the settings for it?
I've ready that I may have to flash the firmware with the EE version to get the features - my concern with that though is tripping Knox, as i'd like to use Samsung Pay when it launches.
Is there a method of enabling the features without flashing the firmware?
Any help on this would be greatly appreciated!

I've ready that I may have to flash the firmware with the EE version to get the features - my concern with that though is tripping Knox, as i'd like to use Samsung Pay when it launches.
Is there a method of enabling the features without flashing the firmware
Click to expand...
Click to collapse
'''
i wouldnt if i were you. i tried that with apple pay in australia and it didnt work. its region locked. wait for the official launch.
for me, my ban offers nfc payments through the phone so i can wait abit for samsung pay to arrive in australia and if im lucky, they will give out free stuff like in america.
i never tried volte calling. but you can always use whats app and stuff.

Its safe to do so,
I bought my S7 Edge from the Samsung store, and flashed the EE firmware, it doesn't trip knox, only custom changes will trip knox, So rooting/custom recoveries and such. its safe to flash the EE firmware. and WI-FI calling working for me, (How to enable WiFI calling). as we speak. But I did do a factory reset(delete everything) after flashing to make sure the CSC for EE was installing correctly.

kossiewossie said:
Its safe to do so,
I bought my S7 Edge from the Samsung store, and flashed the EE firmware, it doesn't trip knox, only custom changes will trip knox, So rooting/custom recoveries and such. its safe to flash the EE firmware. and WI-FI calling working for me as we speak. But I did do a factory reset after flashing to make sure the CSC for EE was installing correctly.
Click to expand...
Click to collapse
Ah - just what I wanted to hear
Can you tell me if the EE firmware comes with loads of bloat? Also, will OTA updates work, or will I have to manually flash them when released (I'm sure I read that auto-updates don't work if flashing a different firmware - although I could have misconstrued that).
Thanks

Captain.Slow said:
Ah - just what I wanted to hear
Can you tell me if the EE firmware comes with loads of bloat? Also, will OTA updates work, or will I have to manually flash them when released (I'm sure I read that auto-updates don't work if flashing a different firmware - although I could have misconstrued that).
Thanks
Click to expand...
Click to collapse
Auto-update will work, but you will have to wait for EE to push the updates out. so might be a delay until they release them, Only difference from buying the phone from EE or Samsung is the firmware, So if you flash the whole phone and factory reset in recovery, its pretty much a EE phone. be warned sometimes WiFi calling will not work until you call up EE and ask them to activate it on your handset, (and that can be a funny conversation, since you didn't buy the phone from them but I managed to talk my way around it on my S6 edge+), And on my S7 Edge it seems to already be enabled after I flashed the EE firmware and enabled in the phone settings.

It's a shame that we still have to install carrier specific firmware to access these things. I thought I heard samsung had overcome this?
Some articles suggested that the S7 could install carrier specific software upon detection of SIM accordingly. This doesn't appear to be the case. I have just had to flash H3G firmware. BTW op it didn't trip KNOX

sammyelrefee said:
It's a shame that we still have to install carrier specific firmware to access these things. I thought I heard samsung had overcome this?
Some articles suggested that the S7 could install carrier specific software upon detection of SIM accordingly. This doesn't appear to be the case. I have just had to flash H3G firmware. BTW op it didn't trip KNOX
Click to expand...
Click to collapse
It is a bit rubbish really - it's one good thing Apple has over android imho. I know Google are trying to go down the same route with Carrier Updates - but they're gonna have to grow a pair if they're going to get anywhere with it.
Anyway, thanks kossiewossie - just finished flashing mine. Hoping I haven't tripped Knox (not checked yet, it's restoring my Google Account backup).

To flash the firmware is it just a case of downloading the EE firmware from sammobile and using Odin to flash it? Because I know for the S6 there was an issue where the partitions were different between the EE version and the unlocked version meaning you had to get hold of a PIT file to flash the EE firmware. Is that still the case?

I'm also considering doing the same. I'm on EE but it came through a re-seller so I've got stock Samsung firmware.
Other than the delay in updates being released, is there any other reason why not to do this? Are you able to flash back the BTU version if you grow tired of waiting for carrier updates and don't end up making the use of wifi calling?

mmotti said:
I'm also considering doing the same. I'm on EE but it came through a re-seller so I've got stock Samsung firmware.
Other than the delay in updates being released, is there any other reason why not to do this? Are you able to flash back the BTU version if you grow tired of waiting for carrier updates and don't end up making the use of wifi calling?
Click to expand...
Click to collapse
The only benefit I see with the EE firmware is Wifi calling, but as I am in a fantastic reception area, I do not need it. Therefore I see no other reason to use the EE firmware and prefer updates as soon as they are released.
Yes, if you grow tired of waiting for carrier updates, you can flash back to BTE/XEU firmware.

I can't speak for EVR firmware. I used Samfirm to download 4 file H3G firmware and I was not asked for a PIT file.
Interesting there are PIT files included in the files if you unpack them so maybe this was used?

Having downloaded the EE firmware I'm a little confused with Odin.
I have:
AP...
BL...
CP...
CSC_EVR...
Home_CSC_EVR...
Do I need to select all of these within Odin? If so, which CSC as there seems to be two? Sorry if this is a stupid question....

mmotti said:
Having downloaded the EE firmware I'm a little confused with Odin.
I have:
AP...
BL...
CP...
CSC_EVR...
Home_CSC_EVR...
Do I need to select all of these within Odin? If so, which CSC as there seems to be two? Sorry if this is a stupid question....
Click to expand...
Click to collapse
When I did it last night, within Odin I selected files for AP, BL, CP and for CSC - CSC_EVR. I didn't use the Home_CSC_EVR file.
Knowing my luck, i've probably done it wrong - although my phone does seem to be running fine!!

I'm too cautious about flashing the wrong one lol. I'll wait until we know the difference I think!
Edit: Flashed it with the standard CSC. All seems well.

I flashed the standard csc myself and all seems well for over a day now. Would still like to know what the home csc file is for.
Edit. Just found out that home_csc doesn't contain the pit file so it doesn't wipe the phone. So would have to use the standard CSC when changing firmware.

Can I flash an SM-G950U1 ROM onto my SM-G950U?

Hi all, (I previously asked this here.)
I have a carrier unlocked SM-G950U that was previously on T Mobile that I now have on Verizon, (long story, see below.) However, my device isn't updating, as seems to be the case for a lot of migrated SM-G950U(s). Of course, I want Android 9, and I also wouldn't mind getting rid of some of Verizon's bloatware. I was also fortunate enough to have received a research grant for some work in Italy, and I'd like to bring my phone along, (I'm a student.) So really, 3 reasons:
I want Android 9.
I don't want Verizon's bloatware.
I want to be able to switch carriers without the painful process of a carrier unlocked phone. (Ie., with the unlocked firmware my understanding is that I only need to restart my phone, as opposed to resetting my device, to switch carriers/SIMs in the carrier unlocked (ie., non-U1) device, (I think.))
I want to flash an SM-G950U1 ROM, but I'm not sure if this is still possible, (though according to here and here it was possible about 2 years ago, on different firmware/bootloaders.)
My plan is to do this:
Download this G950U1UEU5DSC1_XAA from updato. (I believe XAA is the unlocked region code. My device is already carrier unlocked.)
Flash with ODIN (3.12.3, as far as I know only making sure repartitioning is UNchecked.)
I have a Snapdragon device.
Will this brick my phone?
Alternatively, here says I can download any carrier version of G950USQU5DSC1 (except Verizon and Sprint,) flash it, and it will work. I think this only accomplishes my getting Android 9, however, as it is still a carrier branded ROM. (So I'd still have to deal with bloatware and (possibly) resetting my device to switch networks.)
Phone INFO (the app) lists:
Original CSC Code: [blank]
Firmware's CSC Code: XAA
Active CSC Code: VZW
Avaialble CSC Codes: [a bunch]
Bootloader Version: G950USQU5CRG3
CSC Version: G950UOTN5CRG3
Baseband Version: G950USQU5CRG3
Build Number: R16NW.G950USQU5CRG3
Long story of how I got a carrier unlocked (SM-G950U) and not unlocked (SM-G950U1) device:
I purchased my "new" device on Amazon through a third party about 3 months ago. I checked the model number and found SM-G950U, but a couple places online said that this was indeed a regular, unlocked S8. However, my device wouldn't update, and I could see that I was stuck on a mid July/August build of Android 8, (CRG3.) Now that the summer's getting closer, I need(ed) to make sure my device is going to work while in Italy, so I called Samsung to update it/make sure it would work. They told me my device was previously activated on T Mobile, unlocked, apparently refurbished and sold to me. I rechecked the Amazon listing and it was in fact listed as new. (It was alongside Amazon's own listing for the S8.) Unfortunately, after spending the second half of my day on support calls, I won't be able to return my device because it's been just over 3 months. Looks like my next best option is to update/maintain it myself.

staMerrill said:
Hi all, (I previously asked this here.)
I have a carrier unlocked SM-G950U that was previously on T Mobile that I now have on Verizon, (long story, see below.) However, my device isn't updating, as seems to be the case for a lot of migrated SM-G950U(s). Of course, I want Android 9, and I also wouldn't mind getting rid of some of Verizon's bloatware. I was also fortunate enough to have received a research grant for some work in Italy, and I'd like to bring my phone along, (I'm a student.) So really, 3 reasons:
I want Android 9.
I don't want Verizon's bloatware.
I want to be able to switch carriers without the painful process of a carrier unlocked phone. (Ie., with the unlocked firmware my understanding is that I only need to restart my phone, as opposed to resetting my device, to switch carriers/SIMs in the carrier unlocked (ie., non-U1) device, (I think.))
I want to flash an SM-G950U1 ROM, but I'm not sure if this is still possible, (though according to here and here it was possible about 2 years ago, on different firmware/bootloaders.)
My plan is to do this:
Download this G950U1UEU5DSC1_XAA from updato. (I believe XAA is the unlocked region code. My device is already carrier unlocked.)
Flash with ODIN (3.12.3, as far as I know only making sure repartitioning is UNchecked.)
I have a Snapdragon device.
Will this brick my phone?
Alternatively, here says I can download any carrier version of G950USQU5DSC1 (except Verizon and Sprint,) flash it, and it will work. I think this only accomplishes my getting Android 9, however, as it is still a carrier branded ROM. (So I'd still have to deal with bloatware and (possibly) resetting my device to switch networks.)
Phone INFO (the app) lists:
Original CSC Code: [blank]
Firmware's CSC Code: XAA
Active CSC Code: VZW
Avaialble CSC Codes: [a bunch]
Bootloader Version: G950USQU5CRG3
CSC Version: G950UOTN5CRG3
Baseband Version: G950USQU5CRG3
Build Number: R16NW.G950USQU5CRG3
Long story of how I got a carrier unlocked (SM-G950U) and not unlocked (SM-G950U1) device:
I purchased my "new" device on Amazon through a third party about 3 months ago. I checked the model number and found SM-G950U, but a couple places online said that this was indeed a regular, unlocked S8. However, my device wouldn't update, and I could see that I was stuck on a mid July/August build of Android 8, (CRG3.) Now that the summer's getting closer, I need(ed) to make sure my device is going to work while in Italy, so I called Samsung to update it/make sure it would work. They told me my device was previously activated on T Mobile, unlocked, apparently refurbished and sold to me. I rechecked the Amazon listing and it was in fact listed as new. (It was alongside Amazon's own listing for the S8.) Unfortunately, after spending the second half of my day on support calls, I won't be able to return my device because it's been just over 3 months. Looks like my next best option is to update/maintain it myself.
Click to expand...
Click to collapse
Lss yes you can. I don't know the exact. But it is nearly impossible to truly brick a u model. But everything you show looks good. I think you need the modded odin for unbranded but you can Google carrier switching s8 and it should lead you right back to xda

TheMadScientist said:
Lss yes you can. I don't know the exact. But it is nearly impossible to truly brick a u model. But everything you show looks good. I think you need the modded odin for unbranded but you can Google carrier switching s8 and it should lead you right back to xda
Click to expand...
Click to collapse
Thanks for the quick reply!
I'll try later today with the G950U1 firmware. I've finished downloading the T Mobile firmware recommended by the second thread, (G950USQU5DSC1,) in case anything goes wrong, (in which case it looks like this firmware will positively work.)

staMerrill said:
Thanks for the quick reply!
I'll try later today with the G950U1 firmware. I've finished downloading the T Mobile firmware recommended by the second thread, (G950USQU5DSC1,) in case anything goes wrong, (in which case it looks like this firmware will positively work.)
Click to expand...
Click to collapse
See here: https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473
Just download the G950U1 firmware from Updato (or using SamFirm or Frija) and use that instead of the firmware referenced in the linked instructions.

Hai Karate said:
See here: https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473
Just download the G950U1 firmware from Updato (or using SamFirm or Frija) and use that instead of the firmware referenced in the linked instructions.
Click to expand...
Click to collapse
So as a surprise to no one, this worked successfully.
Thanks for all the help!
Ultimately, I did have to deviate from the guide here, (the same one you linked and that I had above.) I needed to download a new patched version of ODIN, which I got here.
The process was:
Download PatcheD Odin
Launch PatcheD Odin
Put phone in Download Mode
Connect Phone to PC
Extract the G950U1UEU5DSC1_XAA firmware from updato. (The same link/URL as I have above.)
Browse to/find files in Odin and put them in the right places.
Start...
Wait a reasonable amount of time for the files to be downloaded to the device, and forever for it to actually update.
Profit, (and finish setting up the device, wondering how you're going to signin without your 2FA codes...)
So again, thank you everyone. If anyone comes across this thread in the future you have my steps.

G977U models Retail Stock Firmware Links Here

So it seems like Samsung has really switched things up here, with the 5G model. I haven't seen any mention of a U1 model, so I would not expect that to be a thing here in the US - at least not yet. The Verizon and AT&T model are both G977U, G977T is T-Mobile, and G977P is the Sprint model. Firmware packages are comprised of the 4 base files plus a USERDATA.
It appears that even though AT&T and Verizon are both U models, they will each be getting their own distinct updates. For example, we have G977UUCU1ASEM for AT&T but G977UVRU1ASE8 for Verizon. The CSC file names also specifically have "ATT" and "VZW" in them. AT&T and Verizon firmwares have confirmed to be interchangeable (as long as you're not trying to downgrade the bootloader) but you cannot cross flash between anything with different model numbers.
This is not a "beginner's guide to Odin flashing" type post/thread, so I won't list basic, step-by-step instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware, I recommend you consult one of the "beginner's" posts/threads - there are tons of them here on XDA.
Happy flashing!
https://www.androidfilehost.com/?w=files&flid=292071
Notes:
- Don't quote the OP when you reply, kthx
- I compress 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
- I pay for a subscription to a site that gets beta builds and also sometimes gets the official releases before they hit SamFirm/Frija, so that's where my files come from. However, I don't have unlimited bandwidth on the site, and it's also quite time consuming to download the files, zip them up, and upload them to AFH. And, I do threads like this for every single Sx and Note x model. The latest versions of Verizon (manual entry required), Sprint, and T-Mobile firmware can always be downloaded at any time, using SamFirm/Frija. So I won't be adding any of those firmwares to my AFH folders, unless I get early access to them, before they hit SamFirm/Frija. I will be adding at least one version per bootloader increment for AT&T firmware, since their files are never available on SamFirm/Frija. If you want an AT&T version that's not already uploaded, or a Verizon/Sprint/T-Mobile version other than whatever the latest is, let me know and I'll see what I can do.
- HOME CSC file keeps data intact; using the other one will wipe data. Also, flashing the USERDATA file will wipe your data. USERDATA is only needing if converting between AT&T and Verizon firmwares. If you're just looking to manually update from an older version, then you can skip the USERDATA file (but I'd still recommend flashing it if you don't care if your phone gets wiped).
**it has been discovered that, like most of the rest of AT&T Samsung models (true U models excluded), the AT&T AP tars have a small "userdata" partition in them that will also initiate a wipe, during the flash. So for bootloader 2 AT&T firmwares and higher, I'll also include a "no-wipe" AP tar that has that partition removed, for those who are looking to manually update from an older AT&T version without losing their data. Flash that, along with BL, CP, and HOME CSC in order to retain your data and not have a factory reset performed.
- My naming method for AFH folders 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. And each folder will have a designation showing whether it's an AT&T or Verizon build, instead of having separate folders for all of each carrier's builds

Firmware is now listed on SamFirm. Like almost all Verizon phones, manual entry for the 3 fields is required in order to find/download it

Could I use this to flash a unlocked version per say. To get rid of the Verizon bloat and add back the stock Samsung system
Like how the U1 would be if it were made?

Darktorn said:
Could I use this to flash a unlocked version per say. To get rid of the Verizon bloat and add back the stock Samsung system
Like how the U1 would be if it were made?
Click to expand...
Click to collapse
Nope. Flashing it is just gonna give you the exact same thing that you have now

iBowToAndroid said:
Nope. Flashing it is just gonna give you the exact same thing that you have now
Click to expand...
Click to collapse
Ah damn. So I would have to wait for the elusive unlocked model. Thank you anyway .
I miss my Samsung caller ID and Samsung cloud from my unlocked s10+

can u please put the verizon USA version if available? s10plus5G

88santee said:
can u please put the verizon USA version if available? s10plus5G
Click to expand...
Click to collapse
It's already there, linked in the OP. You can also get it from SamFirm any time that you want

can i flash it on my G977N (korea version) ?

hoangtu2410 said:
can i flash it on my G977N (korea version) ?
Click to expand...
Click to collapse
I don't know. Try it and see what happens

iBowToAndroid said:
I don't know. Try it and see what happens
Click to expand...
Click to collapse
my device can be brick if it fail or not ?

hoangtu2410 said:
my device can be brick if it fail or not ?
Click to expand...
Click to collapse
I have no idea. Anything that you do, you do at your own risk

Is anyone have access to BTU or XEU for SM-G977B please?

Damian said:
Is anyone have access to BTU or XEU for SM-G977B please?
Click to expand...
Click to collapse
No, because those providers don't sell that model. EE is the only one that does, so EVR is the only region for which G977B files exist

Vodafone and UK Samsung is selling them already. I have my S10 5G from Vodafone UK.
Wysłane z mojego SM-G977B przy użyciu Tapatalka

Links for AT&T (U model) and Sprint (P model) firmware have been added

iBowToAndroid said:
No, because those providers don't sell that model. EE is the only one that does, so EVR is the only region for which G977B files exist
Click to expand...
Click to collapse
about G977B UK CSC
in G977BOBE : BTB BTE EVR - UK ( BT Mobile ) - United Kingdom (T-Mobile UK,Orange UK)
in G977BOVF : VOD - United Kingdom (vodafone)
in G977FOXM : CPW - United Kingdom (Carphone Warehouse)
regards

good news samsung whent back to old days firmware is cross-flashable like on the s7/edge.. i flashed my g977u vzw with att firmware and its all att now ATT/ATT/VZW

juvemex said:
good news samsung whent back to old days firmware is cross-flashable like on the s7/edge.. i flashed my g977u vzw with att firmware and its all att now ATT/ATT/VZW
Click to expand...
Click to collapse
Old days? Lol. It's always been that way, ever since that S7 - that was the first device that had that capability. And all flagships have been that way since. Good to know that it works though

Did you flash the att with Odin? Or how? They're all zip files packed in the main zip file

Mklubertanz said:
Did you flash the att with Odin? Or how? They're all zip files packed in the main zip file
Click to expand...
Click to collapse
No, they're not zip files packed within a zip. Odin files are in .tar format. So they're tar files, packed within a zip.

G988U and G988U1 Firmware Links and Flashing Discussion Here

For those who aren't already aware, G988U is the model number of all of the US carrier versions of the S20 Ultra. The G988U1 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. 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 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 pay for a subscription to a site that gets the official releases (usually) before they hit SamFirm/Frija, so that's where my files come from. However, I don't have unlimited bandwidth on the site, and it's also quite time consuming to download the files, zip them up, and upload them to AFH. And, I do threads like this for every single Sx and Note x 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 SamFirm/Frija.
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, 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=305574
U1 firmware: https://www.androidfilehost.com/?w=files&flid=305575
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 to an S20, 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
- 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 SamFirm/Frija:
ATT = AT&T (not available via SamFirm/Frija)
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
SPR = Sprint
TMB = T-Mobile
USC = US Cellular
VZW = Verizon (available via SamFirm/Frija, but Manual Entry is required - Auto will not work)
XAA = U1 firmware
- the correct procedure for switching from one carrier's firmware to another is:
1. Flash full U1 firmware package including non HOME CSC
2. Upon boot, insert a SIM of the carrier whose firmware you want
3. Watch for the popup that says "reboot to apply new carrier settings" etc, and do it
4. After that restart completes, reboot back to Download mode and flash the full U firmware package, with the USERDATA file of the carrier whose firmware you want

Pre-release notes:
1. I do not have one of these and do not plan to acquire one, so I have no idea if anything can actually be flashed at this moment - I'm just providing the firmware. Like all other models, I'm assuming patched Odin is needed for this, but it wouldn't surprise me if a new version is needed for this specific device. There's only one way to know though, so as soon as someone gets their hands on one and can try this, please let us know.
2. I don't know if using the HOME CSC will actually save data. I don't get access to that file straight from the source - I have to decompile the regular CSC, remove the parts that initiate the factory reset, and then re-compile it. Based on the S10 and Note 10, I've done what I think will avoid a factory reset. But the S20 has some new partitions, so we won't know for sure until someone tests it. So if you're willing to be that guinea pig, you're responsible for taking proper steps to avoid an FRP lock, make sure your data is backed up, etc

I will be the first to try. I ordered the unlocked. I will flash the TMO firmware. I have it downloaded already
Sent from my SM-G975U1 using Tapatalk

Thanks for posting these! I ordered the Verizon model but am planning on flashing the unlocked firmware once I get it in hand.
Sent from my SM-N975U using Tapatalk

at this point can we only flash the Userdata for the carrier without the actual firmware?

daraj said:
at this point can we only flash the Userdata for the carrier without the actual firmware?
Click to expand...
Click to collapse
I guess you could flash USERDATA by itself. There's really no point to doing that though

No the firmware is there. Its a separate file zipped up
Sent from my SM-G975U1 using Tapatalk

Is it possible to flash Canada firmware to the us variant or is that not advised ?

roadcabe14 said:
Is it possible to flash Canada firmware to the us variant or is that not advised ?
Click to expand...
Click to collapse
Canadian firmware has been able to be flashed to US Samsung flagship phones ever since the S7. So yes, I would assume that that trend will continue with the S20

Samfirm and Frija have TBN firmware available...I assume based on the naming that it's newer than the ones you have uploaded? I also saw on Sammobile that Verizon has already released a newer firmware which is odd considering they haven't even shipped them yet...lol

tlbland0426 said:
Samfirm and Frija have TBN firmware available...I assume based on the naming that it's newer than the ones you have uploaded? I also saw on Sammobile that Verizon has already released a newer firmware which is odd considering they haven't even shipped them yet...lol
Click to expand...
Click to collapse
1. SamFirm and Frija will always only give you whatever the newest/latest version is. So if it's not the same version that I have uploaded, then yes, it's a newer one.
2. Not odd at all. Most devices get an OTA before release to fix bugs, add features, etc. There was an OTA that came out shortly after I got access to the files, so TBN would be the 3rd release now for this model
3. Looks like firmware has now hit SamFirm and Frija for all S20 models, for anyone who wants to download it themselves

Tried flashing multiple times ATT FW with Odin 3.14.1. Odin reports no errors but it's definitely not taking. SW info still reports XAA and I have no "carrier bloat".

Its not as simple as that. There is a trick when going from unlocked to carrier fw. Look on s10 forums, the procedure is there I believe
Sent from my SM-G975U1 using Tapatalk

johnwayne27 said:
Its not as simple as that. There is a trick when going from unlocked to carrier fw. Look on s10 forums, the procedure is there I believe
Sent from my SM-G975U1 using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s10/help/samsung-s10-unlocked-phone-att-firmware-t3912973
this thread? pretty much the same process. if you don't mind linking me i'm working on trying to get this done proper and won't sleep until then lol

Ive been there done that. Timing is everything. Gotta reset dorectly after boot and flash and when i see carrier update prompt-you know its right. Trial and error.
Sent from my SM-G975U1 using Tapatalk

johnwayne27 said:
Ive been there done that. Timing is everything. Gotta reset dorectly after boot and flash and when i see carrier update prompt-you know its right. Trial and error.
Sent from my SM-G975U1 using Tapatalk
Click to expand...
Click to collapse
TY. Tried again this morning and got it. I assumed I did not need to flash U1 first since my phone was already unlocked. Doing that made all the difference. New to all of this but glad it's finally done!

johnwayne27 said:
Its not as simple as that. There is a trick when going from unlocked to carrier fw. Look on s10 forums, the procedure is there I believe
Sent from my SM-G975U1 using Tapatalk
Click to expand...
Click to collapse
Procedure is also given right here, in the OP

Will flashing the att firmware to an unlocked phone enable wifi calling?

Murph2k said:
Will flashing the att firmware to an unlocked phone enable wifi calling?
Click to expand...
Click to collapse
My other threads are chock full of discussions of this exact thing. Bottom line is, we don't know until someone tries it

I'm trying to download the Tmobile from the SamFirm tool for my S20 ultra SM-G988U1
I put in the model number above and TMB in the region.
But I also noticed that if I enter any other region, it's the same filename and size as well. Just want to make sure about downloading the right file.
I re-read the OP, and saw some youtube videos. It's my assumption now that I need to put SM-G988U in the MODEL and keep TMB as the region to download the correct firmware. Am I correct in assuming this is the correct way to go?
The reason I want to do this is because I want to have Tmobiles advance messaging feature back

Flashing AT&T updates

Question..I recently downloaded the DTD5 update from Sammobile. It's the USA version from 2020-05-18. There isn't any specific carrier tied to this download. I have the AT&T model, but haven't had any success since receiving the phone (purchased directly from Samsung) in getting any OTA's. My question is, there is a USERDATA_USC file within the download. Is that ok to use, even with the AT&T model? I'm not positive, but is USC = US Cellular?
I want to say that I recall reading it doesn't matter which firmware you download, if you have an AT&T sim card in the phone, it'll load all the AT&T software.
Just looking for clarification on the USERDATA thing, as I would prefer to not do a reset and start from scratch.
Thanks in advance

The user data is carrier specific. Userdata_ATT is out there, but you will have to pay for it. Userdata_vzw will give you verizon wireless user data while userdata_tmb will give you t mobile stuff.

StoneyJSG said:
The user data is carrier specific. Userdata_ATT is out there, but you will have to pay for it. Userdata_vzw will give you verizon wireless user data while userdata_tmb will give you t mobile stuff.
Click to expand...
Click to collapse
Can you use any AT&T User data file, or does it have to be the specific one for that build? I've got the AT&T User data file from TB3, but have also downloaded the full DTD5 update (USC). Can I just swap out the User Data files? Or worst case, just load the newest update without the user file and do a full wipe?

I am not sure on that, but I think it has to be for that build. I wouldn't try swapping out the files, though it may work or could cause issues. If you take the OTA to the latest update, then do a data reset you should be good. As for flashing in ODIN, I think you can leave off the user data file and flash. You might want to post in the G975U firmware thread on here. There you will find a user by the name iBowToAndroid, he can help more than I can.

StoneyJSG said:
I am not sure on that, but I think it has to be for that build. I wouldn't try swapping out the files, though it may work or could cause issues. If you take the OTA to the latest update, then do a data reset you should be good. As for flashing in ODIN, I think you can leave off the user data file and flash. You might want to post in the G975U firmware thread on here. There you will find a user by the name iBowToAndroid, he can help more than I can.
Click to expand...
Click to collapse
Thanks. I'm familiar with that thread as well. The reason for my post is because I've never had an OTA update on AT&T. Purchased the AT&T model directly from Samsung. Not a single OTA update. I'm not alone, this is a common problem.

I have heard that some phones won't OTA update for some reason. I got my phone directly from AT&T and only once did it not update by itself (I had to manually click on check for updates in settings then it updated). Watch out for the April and May updates, the April one gives you one UI 2.1 which to me seems to use more battery than One UI 2.0 did.