Database Info

still on android 7.0

ive had my s8plus from at&t (refubished) for a while now and i never got the one ui update like most people get. any ideas? also i live in australia but i purchased it in the US then moved here. i used a vpn and clicked check for updated and it did nothing.

samfirm + odin3.13
moshesmith said:
ive had my s8plus from at&t (refubished) for a while now and i never got the one ui update like most people get. any ideas? also i live in australia but i purchased it in the US then moved here. i used a vpn and clicked check for updated and it did nothing.
Click to expand...
Click to collapse
You can use samfirm for download the newest firmware & update from your pc manually with odin.
if you s8+ is from at&t the region is USC, fot T-Mobile is TMB, Sprint is SPR, Verizon VZW

luisale201 said:
You can use samfirm for download the newest firmware & update from your pc manually with odin.
if you s8+ is from at&t the region is USC, fot T-Mobile is TMB, Sprint is SPR, Verizon VZW
Click to expand...
Click to collapse
I'm kind of in the same boat as the person you're replying to. I have decided to flash 9.0 Pie. However, the links in the youtube tutorials are sort of dead. And I'm not sure if I can flash my 7.0 S8+ straight to 9.0 Pie or do I need to first flash it to Android 8.0 and then 9.0?

HaplessK said:
I'm kind of in the same boat as the person you're replying to. I have decided to flash 9.0 Pie. However, the links in the youtube tutorials are sort of dead. And I'm not sure if I can flash my 7.0 S8+ straight to 9.0 Pie or do I need to first flash it to Android 8.0 and then 9.0?
Click to expand...
Click to collapse
Flash 9.0 right off. Frija or samfrew

TheMadScientist said:
Flash 9.0 right off. Frija or samfrew
Click to expand...
Click to collapse
Those did not work. Frija says "CSC code not supported". SamFirm doesn't load "USA" option in region.
I have an ATT branded s8+.
EDIT: Nevermind that, I realize now that Samfrew is not Samfirm. I'm trying that now...
EDIT#2: Can I flash unbranded 'XAA' Pie instead of an ATT branded one? I see one guys tutorial on youtube but said to only use a 'modded' Odin, but his video is from three years ago. How do I know if that modded Odin is still compatible with recently released Pie firmware from just a few months back?
Final Edit: I took the risk and flashed the latest XAA firmware I could find (which I downloaded using Frija, I searched for XAA CSC code, not ATT) using the patched odin 3.14.1_3B. I used the slow port on my laptop (I was warned not to use the fast one a year ago by someone who rant into some issues) and I had also removed sim and micro sd card just to be on the safe side. It worked. Phone is now running the latest Pie release I believe (SM-G955U1 20210304173908).

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?

How To Guide F711U and F711U1 Firmware Links and Flashing Discussion Here

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

Flashed a physical T-Mobile F711U to a F711U1 XAA firmware using Odin(Can't stand the bright pink boot up animations).
Flash worked perfectly. But, when I tried to test doing an update from Google settings it failed every time with "Registration Failed". I flashed the device back to the T-Mobile F711U firmware and was able to update without issue.
Not sure if you ran into this issue, but it's worth noting you might not be able to update the phone if the carriers are checking the Firmware.
Edit: Also forgot to mention, had to use the patched Odin due to the Firmware Model mismatch. Phone does work properly though.

nwb_sam said:
Flashed a physical T-Mobile F711U to a F711U1 XAA firmware using Odin(Can't stand the bright pink boot up animations).
Flash worked perfectly. But, when I tried to test doing an update from Google settings it failed every time with "Registration Failed". I flashed the device back to the T-Mobile F711U firmware and was able to update without issue.
Not sure if you ran into this issue, but it's worth noting you might not be able to update the phone if the carriers are checking the Firmware.
Edit: Also forgot to mention, had to use the patched Odin due to the Firmware Model mismatch. Phone does work properly though.
Click to expand...
Click to collapse
What do you mean by "doing an update from Google settings"?
What type of update? What "Google settings" exactly?

iBowToAndroid said:
What do you mean by "doing an update from Google settings"?
What type of update? What "Google settings" exactly?
Click to expand...
Click to collapse
From "Settings" App > "Software Update" > "Download and Install" and pressing the "Download and Installing.
I get "Connecting to server" and then immediately "Registration Failed" I've attempted over Wi-Fi and with that option toggled off.
This could also be the phone is new and T-Mobile doesn't have the F711U1 XAA firmware at their carrier level, but the registration failed annoys me. On F711U (official T-Mobile firmware) I simply get a notification that the device is up to date.

nwb_sam said:
From "Settings" App > "Software Update" > "Download and Install" and pressing the "Download and Installing.
I get "Connecting to server" and then immediately "Registration Failed" I've attempted over Wi-Fi and with that option toggled off.
This could also be the phone is new and T-Mobile doesn't have the F711U1 XAA firmware at their carrier level, but the registration failed annoys me. On F711U (official T-Mobile firmware) I simply get a notification that the device is up to date.
Click to expand...
Click to collapse
Which F711U1 version did you flash?

iBowToAndroid said:
Which F711U1 version did you flash?
Click to expand...
Click to collapse
I flashed my phone using the F711U1OYM1AUG7 (F711U1 XAA) firmware from sammobile.
I flashed it back to the T-Mobile firmware, (F711UOYN1AUGB (F711U TMB) and the issue went away.
I did flash it again to the XAA to confirm the problem this evening. Never retained data during the process. Factory reset and removed my account information (Google and Samsung) before updating the firmware each time.
I've done this on a few phones in the past. If I'm making a blunder in the process causing this then I'm truly sorry for wasting anyone's time.
Edit: Typo

nwb_sam said:
I flashed my phone using the F711U1OYM1AUG7 (F711U1 XAA) firmware from sammobile.
I flashed it back to the T-Mobile firmware, (F711UOYN1AUGB (F711U TMB) and the issue went away.
I did flash it again to the XAA to confirm the problem this evening. Never retained data during the process. Factory reset and removed my account information (Google and Samsung) before updating the firmware each time.
I've done this on a few phones in the past. If I'm making a blunder in the process causing this then I'm truly sorry for wasting anyone's time.
Edit: Typo
Click to expand...
Click to collapse
Well UG7 is the latest that's available. So yes, I would expect you to get an error.
Once an update is available, if the phone is still giving the same error, then you can worry about it

Hello, well from my understanding Xfinity is bootloader unlockable after 60days and fully played for. I am wondering if anyone is planning on making a thread for Xfinity specifically. Or want too work with me on One. Sorry too spam or thread. But if u are familiar with how rom building, and flashing was with any other recent samsung model/Xfinity/bootloader unlock. It would be highly appreciated too know your experience.

jokono421 said:
Hello, well from my understanding Xfinity is bootloader unlockable
Click to expand...
Click to collapse
Incorrect. No US models of any Samsung device have been user-unlockable for years now, dating back to the S7

iBowToAndroid said:
Incorrect. No US models of any Samsung device have been user-unlockable for years now, dating back to the S7
Click to expand...
Click to collapse
I think network unlock got mixed up with bootloader unlock. You can unlock the phones for use with another carrier after X days and completed payment.

twistedumbrella said:
I think network unlock got mixed up with bootloader unlock. You can unlock the phones for use with another carrier after X days and completed payment.
Click to expand...
Click to collapse
Probably so

Can someone locate the thom browne fimware please?

blkghost22 said:
Can someone locate the thom browne fimware please?
Click to expand...
Click to collapse
Well normally I would say that you can get it yourself from the various firmware download tools like SamFirm or Frija. But it looks like Samsung changed something over the weekend, as the current versions of the tools are failing to pull any firmware
So I can grab it for you

iBowToAndroid said:
Well normally I would say that you can get it yourself from the various firmware download tools like SamFirm or Frija. But it looks like Samsung changed something over the weekend, as the current versions of the tools are failing to pull any firmware
So I can grab it for you
Click to expand...
Click to collapse
Thank you and always the best.

blkghost22 said:
Thank you and always the best.
Click to expand...
Click to collapse
Added, UGC build

iBowToAndroid said:
Added, UGC build
Click to expand...
Click to collapse
Guess its taking time to upload? Dont see the files just yet..
Edit:
Nvm i see the files now... again thank you so much

I know long time ago it didnt work but just wanted to throw it out there... if i flash the u1 or thom browne am i able to flash the att userdata to get the advance msging and video calls?

blkghost22 said:
I know long time ago it didnt work but just wanted to throw it out there... if i flash the u1 or thom browne am i able to flash the att userdata to get the advance msging and video calls?
Click to expand...
Click to collapse
1. Thom Browne *is* U1 firmware
2. USERDATA belongs to U firmware, not U1. So I have absolutely no idea. You'll have to try it and see what happens

Have successfully flashed F711U1 to F711W. Everything working fine. Used Odin 3.14, CSC_OMC_OYV, and working on Telus with all available features working.
Please note that AFTER the flash, you will be prompted to reset the device to stock. Reason being is that it needs to install the appropriate CSC linked to the inserted SIM card.

Can anyone confirm if cross flashing different build firmwares that it will unlock the unlock bootloader option?
Currently on carrier firmware for TMobile and I'm wondering if this is possible or if the u1 firmware has the unlock bootloader option available

Stuck on Android 9 and One UI 1.0

Greetings,
I am a new user here. I just bought Galaxy S10e and I really like the phone, but the problem is that I ordered it from USA (I live in the Republic of Georgia). Originally the phone was from AT&T, but the seller had it unlocked for any GSM carriers and it works fine with my Georgian sim card. The only problem is that I do not receive any software updates. It is stuck on Android 9 and One UI 1.0. When I try to check for updates, it says that my software is up to date. The same happens with Smart Switch.
I tried Frija and Odin. My CSC is G970UOYN1ASD9 and PDA is G970USQS1ASD9. There is no way to download firmware for my own country's CSC, because there is no firmware for SM-G970U (Snapdragon chipset), in Georgia they only sell Exynos ones officially. So, I tried to find updates with CSC ATT in Frija and it does not give me anything. I tried XAA and XAS (which is for unlocked phones) and still nothing. I tried TMK (I think it is for MetroPCS) and USC (This one is for US Cellular) and also TMB (T-Mobile) and they do have Android 11 firmware. But now I am afraid I will break something if I install above mentioned firmware to my device. Or maybe I will not break anything by changing the CSC, but maybe there is also a chance that if I install the above mentioned ones, the phone will get locked on these carriers and I won't be able to use my sim card. Is logical, or am I just overthinking it?
Any help would be really appreciated.
Thanks in advance.

don't flash your nations CSC- that shouldn't matter. Snapdragons LTE bands should be good enough to work internationally
go and reflash a USC or XAA rom with patched ODIN... I had to do this for my phone and OTA started working once it was on the correct CSC
you could even flash it to the latest firmware if you wanted too.

supertac said:
don't flash your nations CSC- that shouldn't matter. Snapdragons LTE bands should be good enough to work internationally
go and reflash a USC or XAA rom with patched ODIN... I had to do this for my phone and OTA started working once it was on the correct CSC
you could even flash it to the latest firmware if you wanted too.
Click to expand...
Click to collapse
Thank you for your answer.
What do you mean by correct CSC? I believe, my phone is on correct CSC now. I have already pasted it and in about phone > Software information > Service Provider it says ATT/ATT/ATT. But it seems that ATT doesn't receive updates outside US.
I cannot seem to find firmware for XAA/XAS, there is one for USC but I have already downloaded TMK. Is there any difference if I install USC or TMK? (TMK is MetroPCS).

GSamkh said:
Thank you for your answer.
What do you mean by correct CSC? I believe, my phone is on correct CSC now. I have already pasted it and in about phone > Software information > Service Provider it says ATT/ATT/ATT. But it seems that ATT doesn't receive updates outside US.
I cannot seem to find firmware for XAA/XAS, there is one for USC but I have already downloaded TMK. Is there any difference if I install USC or TMK? (TMK is MetroPCS).
Click to expand...
Click to collapse
Hi GSamkh... Did you upgraded to 11? Im trying to do the oposite, downgrade from Android 11 to 9. If you didnt the upgrade, can you check if the secure startup (or secure boot) its avaliable? Since in Android 10 and 11 isnt...
Seams that secure startup works on Galaxy S9 with Android 10 upgraded from 9.

dvaguirre said:
Hi GSamkh... Did you upgraded to 11? Im trying to do the oposite, downgrade from Android 11 to 9. If you didnt the upgrade, can you check if the secure startup (or secure boot) its avaliable? Since in Android 10 and 11 isnt...
Seams that secure startup works on Galaxy S9 with Android 10 upgraded from 9.
Click to expand...
Click to collapse
Greetings,
I have already updated to Android 11 using U1 XAA firmware and it works great. I used Frija and then Odin if anyone wants do to do this. Weird thing happened though - when I flashed the firmware and when Odin did it's job, the laptop suddenly shut down and I couldn't turn it back on. I had to disassemble it and unplug the integrated battery, plug it back on and fortunately it turned on again.
As far as your question goes, I am sorry but I cannot check it since I am already on Android 11.

Hi
GSamkh said:
Greetings,
I have already updated to Android 11 using U1 XAA firmware and it works great. I used Frija and then Odin if anyone wants do to do this. Weird thing happened though - when I flashed the firmware and when Odin did it's job, the laptop suddenly shut down and I couldn't turn it back on. I had to disassemble it and unplug the integrated battery, plug it back on and fortunately it turned on again.
As far as your question goes, I am sorry but I cannot check it since I am already on Android 11.
Click to expand...
Click to collapse
Hi GSamkh,
I am experiencing the same issue as you, purchased an AT&T branded SM-G970U for use in Australia. After you flashed to Android 11 using U1 XAA firmware, do you now receive OTA updates? cheers