General G996U and G996U1 Firmware Links and Flashing Discussion Here
- Thread starter iBowToAndroid
- Start date
Hey Yall
Sorry for the question but I am a longtime lurker here and have learned a lot but I think I am still in the noob zone so don't hate on me please, also if this is in the wrong spot please direct me and I will post it in the correct area. I have used Odin in the past several times but this time it has me stumped. I have a T-Mobile Samsung Galaxy 21+, I am attempting to flash it to a U1 Firmware that is available on this thread on the first post. However I have attempted to do this several times and I keep getting the Fail! (Auth) Error. I am including the Odin screen and the phone screen. Any and all help would be appreciated!!!!!
Sorry for the question but I am a longtime lurker here and have learned a lot but I think I am still in the noob zone so don't hate on me please, also if this is in the wrong spot please direct me and I will post it in the correct area. I have used Odin in the past several times but this time it has me stumped. I have a T-Mobile Samsung Galaxy 21+, I am attempting to flash it to a U1 Firmware that is available on this thread on the first post. However I have attempted to do this several times and I keep getting the Fail! (Auth) Error. I am including the Odin screen and the phone screen. Any and all help would be appreciated!!!!!
Attachments
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
Hi. I want to Flash Firmware updates for Android 12 on my G996U. Problem is, I am not sure on my CSC.
"SM-G996U_OYN_XAA_RR_/0003XAA/XAA/ATT" is my CSC AT&T or XAA? On Smart Switch it is XAA. but on download mode carrier ID is ATT. Please help. So I can get correct firmware. I cannot get OTA here in the Philippines. Thank you
You can flash any G996U firmware - it doesn't matter which one you choose
"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" is this for the firmware you uploaded only? or I can get latest firmware of G996U on Sammobile.?
Oh. Okay. So my CSC is ATT then? I will flash G996U1 ATT for Android 12. Thanks.
BTW. If I'm to to flash firmware to Android 12. SHould I first flash the pre requisite updates beyond Security Patch Level May 1, 2021? (that was the last update my phone had) or I can go straight to the latest update on Android 12 say Jan 2022. Thank you
You can go straight to whatever version you want to be running
Thanks. But I can't seem to find firmware for G996U w/ CSC of ATT. Can I flash Firmware for G996U1 w/ ATT or XAA to a G996U phone? I download firmware from Sammobile and Frija for Android 12. BTW if Im outside USA should I opt for XAA rather than ATT since my network is not ATT here in my country?
I completed the flash on ODIN (Flash is correct IMO because it was "PASS" and there were no error on the logs of ODIN).
BUT there is this error on my phone "partition abl Reason avb_slot_verify.c:256: ERROR: abl: Hash of data does not match digest of decriptor. (2nd)"
I used G996U1 XAA. PLEASE HELP. PHONE JUST STUCK ON BLUE SCREEN CANT EVEN REBOOT
NMV it worked now. had to download another firmware from frija then flash it again it's all good now. THANKS A LOT! (Initial file is from Sammobile)
Last edited:
I have ones that are stuck to VZW/VZW/VZW with U1 package flashed. Any resolution?
Hi, I am from New Zealand and my better half has purchased a like new S21+. It has verizon branding and the update download speeds are very slow. The phone is currently on the october 21 patch. Am I correct in thinking I can just odin flash the newest U1 XAA firmware to remove the carrier branding? Is it alright to flash straight to the newest CVC4 XAA firmware?
You could flash a U1 package that will remove the carrier bloat. It is best to match the same bit when flashing, you can flash up, but not down.
I assume it is unlocked as her NZ sim is working perfectly. We do not have locked phones in NZ is there an easy way to check this? Appreciate the help.
It doesn't matter what the policy is for NZ phones, as this is not an NZ phone.
If her SIM is working perfectly, then the phone is already SIM unlocked
Top Liked Posts
-
There are no posts matching your filters.
-
5For 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 want2Switched from AT&T firmware (Jan '21 build) to U1 via Odin, all thanks to this thread! Just wanted to give a thanks to the op for leaving it out there for us!!
P.S I was on OneUI 3.0 before and was only showing Single Sim and wasn't getting any update notifications either. Flashed U1, instantly was prompted for available updates. Couple of downloads and installs later, I got OneUI 4, and eSIM also showed up. Leaving this here to help anyone in a similar situation!1
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 one11
I have a 996U and am using dual-SIM: an AT&T "live" SIM and Verizon eSIM. In my software info page I have VZW/XAA,VZW/TMB. I have activated all of the 5G bands on the S21+ using the part C, Method 1 referenced in this link, which was written for the S22, not for the S21+. Nonetheless, it worked fine for me, giving me 13 5G bands: 2, 5, 12 ,25, 30, 41, 48, 66, 71, 77, 78, 260 and 261, which is all the phone has I believe. If the 5G band(s) you need is in that group, It may be of some use for you. It is a bit involved. If you decide to pursue it, I'd recommend reading as much of the thread as you can stomach (it's a bit long) to get a sense of what's involved.
New posts
-
[Request] FTF Xperia 1 "Service Exchange Unit"
- Latest: Sadeeqarham
-
-
Optimized LineageOS19.1 v8.3 [28Feb/2023]- Latest: Androiddude222
