• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

General G996U and G996U1 Firmware Links and Flashing Discussion Here

Search This thread

akrasna

Member
Jun 14, 2012
15
1
So here is where I am confused (even before the 120hz 60hz bug) -

How come there were Android 12 g996u versions available, but not g996u1?
Shouldn't the "unlocked" non-carrier always be available before or at least at the same time as the first carrier (verizon) - as of this moment there are 4 carrier android 12s available on sammobile -
PDAG996USQU4BUK7
CSCG996UOYN4BUK7

But there are no g996u1 (and I have been checking every day so I don't think it was there and then removed)

would love
1. An explanation of why
2. A link to the unlocked firmware if I was just too stupid to understand where it is .

Thanks
 

iBowToAndroid

Senior Member
Nov 9, 2010
4,895
1
1,560
Twin Cities MN
How come there were Android 12 g996u versions available, but not g996u1?
Shouldn't the "unlocked" non-carrier always be available before or at least at the same time as the first carrier?
Nope. Carriers obviously sell way more devices than Samsung themselves do, so there are way more U devices than U1 out there. So Samsung tends to push out updates to the carrier models first, in order to get it to as many people as possible
 

akrasna

Member
Jun 14, 2012
15
1
Nope. Carriers obviously sell way more devices than Samsung themselves do, so there are way more U devices than U1 out there. So Samsung tends to push out updates to the carrier models first, in order to get it to as many people as possible
Thanks

I just assumed that since the files are the same it would be easy to drop the unlocked ...
guess I will wait
 

iBowToAndroid

Senior Member
Nov 9, 2010
4,895
1
1,560
Twin Cities MN
ATT USERDATA has been added for Android 12 - build UK7. All other carriers got this same version so the rest of the files are readily available elsewhere if needed
 

geeyow30

Member
Jan 2, 2020
15
4
Hello guys! I just need some clarification on some stuff.

So I got my girlfriend, who is outside the US, an unlocked Samsung S21+ through an online seller. The phone arrived, and her sim works properly. Our only problem is that her phone doesn't get any updates. I have looked around here, and found out that her phone was actually an ATT unlocked phone. Hers is SM-G996U (ATT). I've come across this thread, so please, can anyone confirm if what we're going to do is correct or not:

1. Download SM-G996U1 (XAA) firmware from Frija
2. Load BL, AP, CP, CSC on Odin 14 (patched)
3. Put phone on DL mode, and start the process.
4. Wait for phone to boot.

Is that the whole process?
She is still stuck on the February update. I tried the process of going from U to U1 using a spare phone, which is a T-Mobile A32 5G. I got the XAA unlocked firmware for the A32, but it seems to just fail as soon as I start flashing. Maybe because the U1 firmware's bootloader is a lower version compared to the one that the latest T-Mobile firmware has? Thanks to anyone who will answer. :D
 

iBowToAndroid

Senior Member
Nov 9, 2010
4,895
1
1,560
Twin Cities MN
Hello guys! I just need some clarification on some stuff.

So I got my girlfriend, who is outside the US, an unlocked Samsung S21+ through an online seller. The phone arrived, and her sim works properly. Our only problem is that her phone doesn't get any updates. I have looked around here, and found out that her phone was actually an ATT unlocked phone. Hers is SM-G996U (ATT). I've come across this thread, so please, can anyone confirm if what we're going to do is correct or not:

1. Download SM-G996U1 (XAA) firmware from Frija
2. Load BL, AP, CP, CSC on Odin 14 (patched)
3. Put phone on DL mode, and start the process.
4. Wait for phone to boot.

Is that the whole process?
She is still stuck on the February update. I tried the process of going from U to U1 using a spare phone, which is a T-Mobile A32 5G. I got the XAA unlocked firmware for the A32, but it seems to just fail as soon as I start flashing. Maybe because the U1 firmware's bootloader is a lower version compared to the one that the latest T-Mobile firmware has? Thanks to anyone who will answer. :D
1. Yes, that's correct. Make sure she backs up her stuff ahead of time, and it's best to remove screen lock and Google account, to prevent an FRP lock

2. If your A32 is on bootloader 6, then yes, that would explain it. Bootloader 6 hasn't been released for U1 firmware for that model yet
 

geeyow30

Member
Jan 2, 2020
15
4
1. Yes, that's correct. Make sure she backs up her stuff ahead of time, and it's best to remove screen lock and Google account, to prevent an FRP lock

2. If your A32 is on bootloader 6, then yes, that would explain it. Bootloader 6 hasn't been released for U1 firmware for that model yet
Thanks for the confirmation! The phone doesn't have that much stuff yet, since it's pretty new. I caught the OTA update issue right away.

By the way, looking at the file names of the firmwares, how can you tell which bootloader version that firmware has? Is there a certain number that you need to be looking at? What I did with the A32 was more of a hit and miss thing, where I didn't really know about the bootloader version stuff.
 

iBowToAndroid

Senior Member
Nov 9, 2010
4,895
1
1,560
Twin Cities MN
Bootloader version is the 5th character from the end, in either the Build Number or Baseband Version.

There are posts here on XDA and also articles across the web that explain how to read Samsung's software version naming scheme
 

geeyow30

Member
Jan 2, 2020
15
4
Bootloader version is the 5th character from the end, in either the Build Number or Baseband Version.

There are posts here on XDA and also articles across the web that explain how to read Samsung's software version naming scheme
Thanks!! Knowing the bootloader version really helps a lot. We'll do the flashing this weekend. Let you know how it goes. Cheers!
 

sr2021

Member
Nov 28, 2021
6
3
Hello guys! I just need some clarification on some stuff.

So I got my girlfriend, who is outside the US, an unlocked Samsung S21+ through an online seller. The phone arrived, and her sim works properly. Our only problem is that her phone doesn't get any updates. I have looked around here, and found out that her phone was actually an ATT unlocked phone. Hers is SM-G996U (ATT). I've come across this thread, so please, can anyone confirm if what we're going to do is correct or not:

1. Download SM-G996U1 (XAA) firmware from Frija
2. Load BL, AP, CP, CSC on Odin 14 (patched)
3. Put phone on DL mode, and start the process.
4. Wait for phone to boot.

Is that the whole process?
She is still stuck on the February update. I tried the process of going from U to U1 using a spare phone, which is a T-Mobile A32 5G. I got the XAA unlocked firmware for the A32, but it seems to just fail as soon as I start flashing. Maybe because the U1 firmware's bootloader is a lower version compared to the one that the latest T-Mobile firmware has? Thanks to anyone who will answer. :D

You know I have a Samsung S21+ Factory unlocked US version, when I traveled to India and used local SIM, VoLTE was WIFI calling disabled and I could not use the phone. As soon as I insert the US SIM the VoLTE/WIFI calling will be enabled. my phone has XAA firmware because it is factory unlocked.

When asked about this Samsung said it is by design and till now we found NO workaround.



so be very careful about the
 
  • Like
Reactions: baazigarg

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    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
    1
    Yep that one works in stock dialer. I've read that the csc dialer code doesn't work anymore for Android 11?

    *#1234# should too right? I can't get that one to work, error.
    I have no idea about "csc dialer code". When you said dialer codes weren't working, I assumed that you meant any/all of them.

    Yes,*#1234# should work also. At least, I haven't heard of them removing/discontinuing that one
    1
    I try and flash the AT&T USERDATA but it is not flashing as I think my phone has a newer version and can't downgrade does anyone have the newer ATT userdata? I switched from Verizon to ATT and the phone is not connecting to data correctly as it only shows H+ not LTE or 5G.
    Bootloader 2 USERDATA was added 3 weeks ago
    1
    Only issues i have had not able to set phone number for voicemail and no call recording not sure what update i will get next and in developer mode no option for OEM unlocker.
    Any help would be appreciated.
    OEM unlock is never present on any U or U1 firmware.

    For the rest, you'll need to ask your carrier for assistance. I don't think there's much that any of us can do about that
    1
    I have a G996U AT&T device. If I install U1 firmware, will knox be triggered?
    It's impossible to trip knox on a U or U1 device, since they have locked bootloaders. So they won't allow you to flash something that would trip Knox