Database Info

How to enable VoLTE on SM-G930F?

I was wondering if it's possible to enable VoLTE on an SM-G930F running BTU firmware on an AT&T carrier. Is there any way to get things like WiFi Calling and VoLTE on it, or am I just screwed since I'm using the international variant of the phone?
When I first got it brand new from Wal-Mart, it was running TTT firmware (from Trinidad and Tobago for some reason) and showed normal 3G, 4G, and LTE symbols on my status bar. Since I wanted to get the Nougat update early, I flashed BTU which switched the symbols to H, H+, and 4G. Does that have anything to do with it?
Thanks.

You're certain it's a G930F? And from Walmart of all places? Exynos isn't meant to be sold in the US.
If it's a G930F and you have TWRP you can flash the CSC tool in the development section which has the US carriers, and CSC is what enables VoLTE.
If it's a US snapdragon model you could flash the AT&T CSC via Odin without needing TWRP.

Beanvee7 said:
You're certain it's a G930F? And from Walmart of all places? Exynos isn't meant to be sold in the US.
If it's a G930F and you have TWRP you can flash the CSC tool in the development section which has the US carriers, and CSC is what enables VoLTE.
If it's a US snapdragon model you could flash the AT&T CSC via Odin without needing TWRP.
Click to expand...
Click to collapse
If OP successfully flashed BTU then it has to be a Exynos G930F, but I agree, most phones sold in the US claiming to be the G930F are modded Snapdragons faked to look like it, but they obviously won't allow a Exynos ROM to be flashed to them, so in this case OP has got a real Exynos
Could be the modem (CP) part of the firmware controlling which carrier services you can receive in your region, not sure I'd recommend flashing a US modem to a UK firmware though, unsure what would happen, although the G930F is pretty straight forward to unbrick as long as you can get back into download mode

Beanvee7 said:
If it's a G930F and you have TWRP you can flash the CSC tool in the development section which has the US carriers, and CSC is what enables VoLTE.
Click to expand...
Click to collapse
Where is this CSC tool? I'm not sure what you mean by "development section". I have an Oreo G930F and I'm trying to get VoLTE to work with AT&T.

Feenix0 said:
Where is this CSC tool? I'm not sure what you mean by "development section". I have an Oreo G930F and I'm trying to get VoLTE to work with AT&T.
Click to expand...
Click to collapse
It hasn't been updated with the newer versions of Android so it's not really a thing anymore.
Next best thing is to download the entire firmware package for your carrier from somewhere like updato then flash only the home_CSC file. Although iirc this might now work if mixing and matching models, which is why the CSC flash tool was a thing.

Beanvee7 said:
It hasn't been updated with the newer versions of Android so it's not really a thing anymore.
Next best thing is to download the entire firmware package for your carrier from somewhere like updato then flash only the home_CSC file. Although iirc this might now work if mixing and matching models, which is why the CSC flash tool was a thing.
Click to expand...
Click to collapse
The trouble is that the G930F was never officially released on US markets, so I can't find a US firmware. I'd gladly use another market's firmware if I knew it would support AT&T VoLTE and "LTE only" mode, but I have no idea how to figure that out!

So it turns out that I have the Canadian SM-G930W8 (as shown on the download mode screen), not the G930F (as shown everywhere else). Identical hardware, but I can only flash Canadian firmware.

General G996U and G996U1 Firmware Links and Flashing Discussion Here

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

Initial U firmware and AT&T USERDATA are posted, along with U1 firmware. U firmware is not yet accessible in the firmware download tools like SamFirm and Frija, but if anyone wants a different carrier's USERDATA (for flashing bloatware to a U1 device or for converting a U device from one carrier's bloatware to a different one), let me know and I'll get it for you

Are the firmware in OP compatible for the S21 (Non-plus)?

craznazn said:
Are the firmware in OP compatible for the S21 (Non-plus)?
Click to expand...
Click to collapse
This thread is in the S21+ forum, not the S21 forum.
This thread is for model numbers G996U and G996U1, not G991U or G991U1.
If you're looking for S21 firmware, that will be found in the S21 forum

I agree with you

Does the firmware control the SIM lock? So, can you flash the U1-XAA firmware and use say a phone purchased from AT&T on another carrier? Or do you need to do the SIM unlock before flashing?

3BeersKen said:
Does the firmware control the SIM lock? So, can you flash the U1-XAA firmware and use say a phone purchased from AT&T on another carrier? Or do you need to do the SIM unlock before flashing?
Click to expand...
Click to collapse
SIM unlock always goes much deeper than firmware. Flashing U1 will never automatically unlock any model - the unlock has to be done separately. If desired, I can provide a recommendation for a professional 3rd party business to do the unlocking, for any interested users who may not meet the carrier's unlock requirement(s).

Thanks. That's what I figured, but wanted to make sure. I like to get off of the AT&T firmware as quickly as possible as you can't get their updates unless you have an active SIM in the phone.

3BeersKen said:
You can't get their updates unless you have an active SIM in the phone.
Click to expand...
Click to collapse
Correct. They're A-holes like that haha

iBowToAndroid said:
Correct. They're A-holes like that haha
Click to expand...
Click to collapse
I got TMobile s21+ and want flash to u1,do you know which odin should I use, thanks

yijinsa said:
I got TMobile s21+ and want flash to u1,do you know which odin should I use, thanks
Click to expand...
Click to collapse
3.14.1 patched

I don't have my S21+ yet but it will be here soon. I ordered from Samsung and selected the Verizon version as unlocked was considerably more expensive.
Does anyone know what Verizon specific bloatware the S21+ has?
Are there certain apps which can be uninstalled with the U1 version but not the Verizon U version?
Are there any potential speed benefits on the 5G network that would be lost using the U1 version, or features like tethering that won't work?
For updates in the future, would they arrive faster on the U1 version, slower, or the same?
My main purpose in flashing from U to U1 is to free up the maximum amount of space of the 128 GB while still retaining 100% of the speed and features I would have with the Verizon version.
Thank you for educating me! It's been a couple years since I flashed my Note 8.

I order a unlocked S21+ U1 version straight from Samsung and didn't have to put in any VZW info.
There is a buttload of Samsung bloatware but no VZW except fot MyVZX

Have anyone here with T-mobile version stuck on TMB/TMB/TMB after going to U1 firmware?
Someone over S21 Ultra have this problem, but I'm not sure if Android 11 tinker or T-mobile side. Used to be XAA/XAA/TMB

x1tymez said:
Have anyone here with T-mobile version stuck on TMB/TMB/TMB after going to U1 firmware?
Someone over S21 Ultra have this problem, but I'm not sure if Android 11 tinker or T-mobile side. Used to be XAA/XAA/TMB
Click to expand...
Click to collapse
Yes, that seems to be a common issue with T-Mobile S21s - all 3 models

iBowToAndroid said:
Yes, that seems to be a common issue with T-Mobile S21s - all 3 models
Click to expand...
Click to collapse
You think there will be a fix for this? It's weird that dialer codes also don't work.

x1tymez said:
Have anyone here with T-mobile version stuck on TMB/TMB/TMB after going to U1 firmware?
Someone over S21 Ultra have this problem, but I'm not sure if Android 11 tinker or T-mobile side. Used to be XAA/XAA/TMB
Click to expand...
Click to collapse
I've got a T-Mobile locked that I was able to get flashed over to U1 without much trouble. Shows mode number SM-G996U1 now, build number shows same.
edit: Nevermind, I see the TMB/TMB/TMB

krisology said:
You think there will be a fix for this? It's weird that dialer codes also don't work.
Click to expand...
Click to collapse
Dialer codes don't work? On which firmware?

iBowToAndroid said:
Dialer codes don't work? On which firmware?
Click to expand...
Click to collapse
XAA U1, VZW U1, stock TMB U, and I've tried the TLI U1 above and couldn't get it to work. Using google dialer, I input the codes like *#*#27262826#*#* and as soon as I type the last star it just disappears and nothing pops up. I tried with T-Mobile and Verizon sim.

krisology said:
XAA U1, VZW U1, stock TMB U, and I've tried the TLI U1 above and couldn't get it to work. Using google dialer, I input the codes like *#*#27262826#*#* and as soon as I type the last star it just disappears and nothing pops up. I tried with T-Mobile and Verizon sim.
Click to expand...
Click to collapse
Dialer codes usually don't work on VZW firmware, whether U or U1. But they almost always work on TMB and all others.
Have you tried *#06# ?

Question The current state of this device in the community

I'm not too familiar with this community or android rooting in general but I still want to see what I can do. I want to know more than just the state of rooting, is there a way to unlock the boot loader, is there a way I can remove some (if not all) of the preinstalled spyware and replace it, what can I do to better protect my privacy? I figured I'd check out this community as this is where I was lead when I wanted to root my old Kindle Fire and since this community doesn't just direct to sketchy proprietary tools like kingroot (or maybe you all do, IDK I haven't been here very long). If I could remove alot of the spyware/bloatware I wouldn't be as concerned with rooting or flashing a custom rom as those would be just nice to have if I could get the preinstalled OS to be more privacy focused. I know I can't really escape google since they're embedded right into android but what can I do about Samsung? If I can't do anything on the device I would still like to know if there is a list of domains I could block using a pi-hole. Thanks if anyone has any info, also my phone is from the T-Mobile distribution, I feel like that probably matters.

How to disable any pre-installed system app bloatware on Android without root
If you hate the bloatware or pre-installed apps on your Android smartphone, here's how to disable them even if Android doesn't normally let you.
www.xda-developers.com

LR7875 said:
How to disable any pre-installed system app bloatware on Android without root
If you hate the bloatware or pre-installed apps on your Android smartphone, here's how to disable them even if Android doesn't normally let you.
www.xda-developers.com
Click to expand...
Click to collapse
The reason I specified replace is that I already tried this and it broke nearly everything, for example:
despite the fact I have a different keyboard, all keyboards broke, I couldn't get the keyboard to show up.
The entire OS became very unstable

TheXGS said:
The reason I specified replace is that I already tried this and it broke nearly everything, for example:
despite the fact I have a different keyboard, all keyboards broke, I couldn't get the keyboard to show up.
The entire OS became very unstable
Click to expand...
Click to collapse
(Sentence removed for stopping confusion)
Without TWRP, replacing the OS will be impossible.
Maybe downgrade to a older phone that has greater custom ROM support.

LR7875 said:
Too bad, Samsung is bricking every debloated device, which is quite horrible.
Without TWRP, replacing the OS will be impossible.
Maybe downgrade to a older phone that has greater custom ROM support.
Click to expand...
Click to collapse
Wait, de bloating can get the device bricked?
I was able to fix it by just reinstalling everything from pm

TheXGS said:
Wait, de bloating can get the device bricked?
I was able to fix it by just reinstalling everything from pm
Click to expand...
Click to collapse
Not fully bricked, but it can be semibricked, i.e. not completely working as a mobile phone.
Xiaomi boot loops when certain apps are disabled, which is nasty and needs a factory reset to 'unbrick' it. Not sure about Samsung.

TheXGS said:
The reason I specified replace is that I already tried this and it broke nearly everything, for example:
despite the fact I have a different keyboard, all keyboards broke, I couldn't get the keyboard to show up.
The entire OS became very unstable
Click to expand...
Click to collapse
I think you removed things that shouldn't have been, or you didn't have the alternate app (e.g. keyboard) set as default. If you look at my post history, you can find the debloat list that I posted, which is 100% safe to remove without affecting the usage in any way whatsoever.
More aggressive debloating is possible, sure, but you risk breaking some things. You can always reinstall whatever you removed with "pm install-existing" as long as you used -k when you removed.

TheXGS said:
Wait, de bloating can get the device bricked?
I was able to fix it by just reinstalling everything from pm
Click to expand...
Click to collapse
No , unless your rooted. whatever you debloat while unrooted can be fixed doing Factory Reset

TheXGS said:
I'm not too familiar with this community or android rooting in general but I still want to see what I can do. I want to know more than just the state of rooting, is there a way to unlock the boot loader, is there a way I can remove some (if not all) of the preinstalled spyware and replace it, what can I do to better protect my privacy? I figured I'd check out this community as this is where I was lead when I wanted to root my old Kindle Fire and since this community doesn't just direct to sketchy proprietary tools like kingroot (or maybe you all do, IDK I haven't been here very long). If I could remove alot of the spyware/bloatware I wouldn't be as concerned with rooting or flashing a custom rom as those would be just nice to have if I could get the preinstalled OS to be more privacy focused. I know I can't really escape google since they're embedded right into android but what can I do about Samsung? If I can't do anything on the device I would still like to know if there is a list of domains I could block using a pi-hole. Thanks if anyone has any info, also my phone is from the T-Mobile distribution, I feel like that probably matters.
Click to expand...
Click to collapse
It can be rooted with Magisk V23.0 but you need to unlock the bootloader first.
The bootloader is unlockable up to V3 but this is a paid service.
To get rid of this bloatware i would suggest you flash an unlocked firmware.

You can always flash a SM-A326U1 XXA ROM (https://www.sammobile.com/samsung/g...M-A326U1/XAA/download/A326U1UEU3AUF2/1558540/) by using a patched version of ODIN 3.13.1 or later. I was able to do this using ODIN 3.1.4 3B
I now have a TMO SM-A326U without any preinstalled TMO bloat. The XAA rom did not install any TMO software that I noticed at a high level and seems like a plan stock A32 5G.
Just make sure the SM-A326U1 baseband is the same version or high than the installed SM-A326U. The base band number will be the 5th to last number in on the About page under baseband.
Edit * I was checking my computer and noticed I had the SM-A326U1 roms for XAA and TMK. I can’t recall if XAA gave me an issue during the flash and I needed to use TMK, but the end result is, my A32 5G has no TMO bloatware installed.
I hope this helps someone.

tavella said:
You can always flash a SM-A326U1 XXA ROM (https://www.sammobile.com/samsung/g...M-A326U1/XAA/download/A326U1UEU3AUF2/1558540/) by using a patched version of ODIN 3.13.1 or later. I was able to do this using ODIN 3.1.3 B3
I now have a TMO SM-A326U without any preinstalled TMO bloat. The XAA rom did not install any TMO software that I noticed at a high level and seems like a plan stock A32 5G.
Just make sure the SM-A326U1 baseband is the same version or high than the installed SM-A-326U. The base band number will be the 5th to last number in on the About page under baseband.
Click to expand...
Click to collapse
Ill try this out i been using the USC FW no bloatware whatsoever

tavella said:
You can always flash a SM-A326U1 XXA ROM (https://www.sammobile.com/samsung/g...M-A326U1/XAA/download/A326U1UEU3AUF2/1558540/) by using a patched version of ODIN 3.13.1 or later. I was able to do this using ODIN 3.1.4 3B
I now have a TMO SM-A326U without any preinstalled TMO bloat. The XAA rom did not install any TMO software that I noticed at a high level and seems like a plan stock A32 5G.
Just make sure the SM-A326U1 baseband is the same version or high than the installed SM-A326U. The base band number will be the 5th to last number in on the About page under baseband.
Edit * I was checking my computer and noticed I had the SM-A326U1 roms for XAA and TMK. I can’t recall if XAA gave me an issue during the flash and I needed to use TMK, but the end result is, my A32 5G has no TMO bloatware installed.
I hope this helps someone.
Click to expand...
Click to collapse
I...
Don't understand this lingo
can someone explain

tavella said:
You can always flash a SM-A326U1 XXA ROM (https://www.sammobile.com/samsung/g...M-A326U1/XAA/download/A326U1UEU3AUF2/1558540/) by using a patched version of ODIN 3.13.1 or later. I was able to do this using ODIN 3.1.4 3B
I now have a TMO SM-A326U without any preinstalled TMO bloat. The XAA rom did not install any TMO software that I noticed at a high level and seems like a plan stock A32 5G.
Just make sure the SM-A326U1 baseband is the same version or high than the installed SM-A326U. The base band number will be the 5th to last number in on the About page under baseband.
Edit * I was checking my computer and noticed I had the SM-A326U1 roms for XAA and TMK. I can’t recall if XAA gave me an issue during the flash and I needed to use TMK, but the end result is, my A32 5G has no TMO bloatware installed.
I hope this helps someone.
Click to expand...
Click to collapse
So I can flash a de-bloated version of the version of the OS?

TheXGS said:
So I can flash a de-bloated version of the version of the OS?
Click to expand...
Click to collapse
Yes i just flashed the XAA version and it gives the same bloat ( google bloatware ew ) as the USC version

TheXGS said:
So I can flash a de-bloated version of the version of the OS?
Click to expand...
Click to collapse
Example if the current version your on is A326USQU1AUCF then you can only flash the A326U1UEU1AUF2

TheXGS said:
I...
Don't understand this lingo
can someone explain
Click to expand...
Click to collapse
The XAA and TMB are what are referrred to as CSC codes. Each carrier has their own:
ACG – Nextech/C Spire
ATT – AT&T
CCT – Comcast
LRA – Bluegrass Cellular
SPR – Sprint (CDMA)
TFN – Tracfone
TMB – T-Mobile
USC – US Cellular
VMU – Virgin Mobile USA
VZW – Verizon
XAA – USA (unbranded/unlocked/default)
XAS – USA (unbranded/unlocked)
ODIN is software used to flash firmware on to Samsung devices while in Download mode. I believe you need to use a patched version of ODIN to cross flash devices. Regular ODIN will most likely error out during the flashing process.
The SM-A326U is a carrier branded device which is why you will probably not find a ROM with a CSC code of XAA for these devies.
The SM-A326U1 I believe is the carrier unlocked version of the device. Regardless of the CSC you flash, don’t expect to get SM-A326U TMB flashed with the SM-A326U1 XAA firmware to enable OEM Unlock in the Developer Settings. It hasn’t appeared for me and I wouldn’t expect it to.
Please feel free to correct any of my assumptions above. I’m an iPhone guy using this phone with my ASUS router as a failover if my ISP goes down. Just tinkering with it from time to time.

tavella said:
The XAA and TMB are what are referrred to as CSC codes. Each carrier has their own:
ACG – Nextech/C Spire
ATT – AT&T
CCT – Comcast
LRA – Bluegrass Cellular
SPR – Sprint (CDMA)
TFN – Tracfone
TMB – T-Mobile
USC – US Cellular
VMU – Virgin Mobile USA
VZW – Verizon
XAA – USA (unbranded/unlocked/default)
XAS – USA (unbranded/unlocked)
ODIN is software used to flash firmware on to Samsung devices while in Download mode. I believe you need to use a patched version of ODIN to cross flash devices. Regular ODIN will most likely error out during the flashing process.
The SM-A326U is a carrier branded device which is why you will probably not find a ROM with a CSC code of XAA for these devies.
The SM-A326U1 I believe is the carrier unlocked version of the device. Regardless of the CSC you flash, don’t expect to get SM-A326U TMB flashed with the SM-A326U1 XAA firmware to enable OEM Unlock in the Developer Settings. It hasn’t appeared for me and I wouldn’t expect it to.
Please feel free to correct any of my assumptions above. I’m an iPhone guy using this phone with my ASUS router as a failover if my ISP goes down. Just tinkering with it from time to time.
Click to expand...
Click to collapse
OEM unlock wont appear on the A326U.
The SM-A326U1 XAA & SM-A326U1 USC should be the debranded versions.
The XAA FW causes CSC to revert Whilst the USC doesnt.
Theres is NO XAS FW for this device.

tavella said:
The XAA and TMB are what are referrred to as CSC codes. Each carrier has their own:
ACG – Nextech/C Spire
ATT – AT&T
CCT – Comcast
LRA – Bluegrass Cellular
SPR – Sprint (CDMA)
TFN – Tracfone
TMB – T-Mobile
USC – US Cellular
VMU – Virgin Mobile USA
VZW – Verizon
XAA – USA (unbranded/unlocked/default)
XAS – USA (unbranded/unlocked)
ODIN is software used to flash firmware on to Samsung devices while in Download mode. I believe you need to use a patched version of ODIN to cross flash devices. Regular ODIN will most likely error out during the flashing process.
The SM-A326U is a carrier branded device which is why you will probably not find a ROM with a CSC code of XAA for these devies.
The SM-A326U1 I believe is the carrier unlocked version of the device. Regardless of the CSC you flash, don’t expect to get SM-A326U TMB flashed with the SM-A326U1 XAA firmware to enable OEM Unlock in the Developer Settings. It hasn’t appeared for me and I wouldn’t expect it to.
Please feel free to correct any of my assumptions above. I’m an iPhone guy using this phone with my ASUS router as a failover if my ISP goes down. Just tinkering with it from time to time.
Click to expand...
Click to collapse
So from my understanding:
There is a tool known as ODIN, this can be used to flash new roms
and from what I seem to know
I am most likely running a TMB version of the ROM as it was the default for my phone as it is a TMobile OEM version
So my question is now this:
How can I get a working version of ODIN
Where can I find a safe XAS rom to flash
I don't know if my phone is unlocked, if my phone is still locked to TMobile, could this mess with anything?
I am using SM-A326U not SM-A326U1, I assume the 1 version is unlocked?

TheXGS said:
So from my understanding:
There is a tool known as ODIN, this can be used to flash new roms
and from what I seem to know
I am most likely running a TMB version of the ROM as it was the default for my phone as it is a TMobile OEM version
So my question is now this:
How can I get a working version of ODIN
Where can I find a safe XAS rom to flash
I don't know if my phone is unlocked, if my phone is still locked to TMobile, could this mess with anything?
I am using SM-A326U not SM-A326U1, I assume the 1 version is unlocked?
Click to expand...
Click to collapse
ODIN is the software used to flash ROMS on to Samsung devices. You will want to look for ODIN 3.1.4 3B Patched On the forums or a search engine. The patched version of ODIN will allow you to flash ROMS with different CSC codes. It removes this restriction.
You are correct that the CSC code for your device is TMB. The CSC codes I listed above are some examples, not a complete list. There are no XAS CSC ROMs for this device that I am aware of, just as financeledger stated.
Your Samsung A32 5G is actually the SM-A326U model, but the SM-A326U1 roms also work on these phones, provided you use the patched ODIN. Only the SM-A326U1 has a XAA CSC rom which is bloat free. I have not tried the USC variant but I switched between the SM-A326U TMB and SM-326U1 XAA ROMs and back last night without any issues. You can find the ROMS at Sammobile.com SM-326U1 Roms it will be the third one in the list with the carrier name of Unknown https://www.sammobile.com/samsung/g...M-A326U1/XAA/download/A326U1UEU3AUF2/1558540/
VersionAndroid 11Changelist21672463Build dateThu, 03 Jun 2021 06:20:56 +0000Security Patch Level2021-05-01Product codeXAAPDAA326U1UEU3AUF2CSCA326U1OYM3AUF2
Doing this will not unlock the phone in any way, shape, or form. All this does is provides you with an A32 5G without any carrier bloat. The boot loader still cannot be unlocked and the sim will remain locked until you’ve met T-Mobile’s conditions for unlocking.
I’d recommend on reading up on how to use ODIN properly as you can brick your device if it is not used correctly. Feel free to reply back if you still have questions. I’m not knowledgable enough to understand what financeledger meant when they said the CSC gets reset using the XAA vs USC rom. Hopefully they can provide some additional details regarding that.

Ok
to be sure I get it right:
Here is what I shal do:
1: Download https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
2: Download the XAA ROM for the SM-A326U
3: Flash the ROM with ODIN
4: Hope I don't brick my phone
Is this right?

Samsung Smart Call which firmware has this? USA only.

Hello, which firmware has Samsung Smart call enabled. I have N986U1 and it is disabled. I don't want to try every firmware to know does it work or not? Please USA only.

Nettwerk said:
Hello, which firmware has Samsung Smart call enabled. I have N986U1 and it is disabled. I don't want to try every firmware to know does it work or not? Please USA only.
Click to expand...
Click to collapse
U1 (XAA) device has it. This is my 986U ATT converted to a U1 XAA device.

So looks like it doesn't work with non-USA or different SIM card.

Nettwerk said:
So looks like it doesn't work with non-USA or different SIM card.
Click to expand...
Click to collapse
Unfortunately it's the CSC code that determines what features are available.
I did a CSC change on mine back when dialer code/IMEI still worked.
My phone was a stock 986U ATT device. I changed CSC to XAA and loaded U1 firmware.
My phone didn't retain the XAA CSC, after a 3rd reboot, but all the stock features remained.
Call and text on other devices works (normally blocked by AT&T), and Smart Call works as well.
Still can't get eSIM working, but that is only available for T-Mobile CSC.

rjohnstone said:
Unfortunately it's the CSC code that determines what features are available.
I did a CSC change on mine back when dialer code/IMEI still worked.
My phone was a stock 986U ATT device. I changed CSC to XAA and loaded U1 firmware.
My phone didn't retain the XAA CSC, after a 3rd reboot, but all the stock features remained.
Call and text on other devices works (normally blocked by AT&T), and Smart Call works as well.
Still can't get eSIM working, but that is only available for T-Mobile CSC.
Click to expand...
Click to collapse
I have converted from ATT to XAA. About phone it shows XAA/XAA/ATT and updates comes XAA. Or I haven't changed CSC?

Nettwerk said:
I have converted from ATT to XAA. About phone it shows XAA/XAA/ATT and updates comes XAA. Or I haven't changed CSC?
Click to expand...
Click to collapse
It's changed... All AT&T U devices will retain ATT in the 3rd set (???/???/ATT) as that is the original sales code for the device.
Having XAA/XAA/ATT with U1 firmware should let you have access to some XAA features.

Question [SM-S908U] Flashed Samsung DSH firmware over ATT firmware

Hello! i flashed with full wipe the SM-S908U DSH unknown firmware over my ATT branded S22 Ultra, thinking that it was the unbranded version. I still have all the ATT branding everywhere and also the ATT software update option in settings.
My question is: will i still be able to get OTA updates with this firmware?

Unbranded firmware is U1 firmware. DSH is Dish network/Boost Mobile

hyelton said:
Unbranded firmware is U1 firmware. DSH is Dish network/Boost Mobile
Click to expand...
Click to collapse
The weird thing is that even though I flash dtbe full firmware, when I booted up, I still had the ATT customizations, but in settings it shows the firmware is updated to the DSH that I flashed? Very weird.

The reason is that DSH firmware is still U firmware with a CSC that adapts the firmware to the SIM installed, therefore it reverted back to AT&T. As previously stated, you need U1 firmware, unlocked defaults to XAA in the US.

So what will happen if I dirty flash with the Home CSC the new DSH U over my SM-S908U1 that has been already flashed from U1 to carrier U Xfinity Mobile hard sim and a T-Mobile eSim ?
Will I still keep my same Xfinity Mobile T-Mobile carrier data ?
​​