Related
For those who don't know, G960U is the model number of all of the US carrier versions of the Galaxy S9. The G960U1 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 SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But they only provide whatever the latest/newest/current version is - nothing older. I pay for a subscription to a site that gets the official releases (usually) before they hit SamFirm/Frija, so that's where my files come from. However, I don't have unlimited bandwidth on the site, and it's also quite time consuming to download the files, zip them up, and upload them to AFH. And, I do threads like this for every single Sx and Note x model - so I won't be uploading every single version. The only full builds that I upload are ones where I get access to a new bootloader and/or Android version early, before they hit SamFirm/Frija.
This is not a "beginner's guide to Odin flashing" -type post/thread, so I won't list basic, step-by-step flashing instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware (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.
Odin 3.13.1 3B Patched is required for flashing these.
Happy flashing!
U firmware: https://www.androidfilehost.com/?w=files&flid=257018
U1 firmware: https://www.androidfilehost.com/?w=files&flid=257047
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 S9+, welcome back
- My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- My naming method for folders on AFH is: build - bootloader - Android version
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- HOME CSC file keeps data intact; using the other CSC will wipe data. Flashing USERDATA will also wipe data.
- Since AT&T doesn't allow their firmware to be publicly available (for any of their devices), I'll try to always upload at least one USERDATA per bootloader increment for AT&T and Cricket. I'll also upload any full builds if AT&T is the only carrier to get that specific build, because you won't be able to find the files anywhere else.
- For identifying USERDATAS, and to know what region/CSC to use in SamFirm/Frija:
AIO = Cricket (not available via SamFirm/Frija)
ATT = AT&T (not available via SamFirm/Frija)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
SPR = Sprint
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via SamFirm/Frija, but Manual Entry is required - Auto will not work)
XAA = U1 firmware
- the correct procedure for switching from one carrier's firmware to another is:
1. Flash full U1 firmware package including non HOME CSC
2. Upon boot, insert a SIM of the carrier whose firmware you want
3. Watch for the popup that says "reboot to apply new carrier settings" etc, and do it
4. After that restart completes, reboot back to Download mode and flash the full U firmware package, with the USERDATA file of the carrier whose firmware you want
want
Is this unlocked or a carrier?
Cozmo85 said:
Is this unlocked or a carrier?
Click to expand...
Click to collapse
I don't understand what you're asking
iBowToAndroid said:
I don't understand what you're asking
Click to expand...
Click to collapse
The firmware posted. Is it carrier specific, like AT&T version or Verizon version.
Anyone else try Odin on the S9? It just crashes for me but never had any issues on the S8. 3.2.13
Faulting application name: Odin3.exe, version: 2016.1.21.1, time stamp: 0x56a0c21a
Faulting module name: Odin3.exe, version: 2016.1.21.1, time stamp: 0x56a0c21a
Exception code: 0xc0000094
Fault offset: 0x0002ebd4
Faulting process id: 0x38b4
Faulting application start time: 0x01d3bc0249b0ff88
Faulting application path: C:\Users\Paul\Downloads\Odin3_v3.12.3\Odin3.exe
Faulting module path: C:\Users\User\Downloads\Odin3_v3.12.3\Odin3.exe
Report Id: b49e6a33-3057-4066-81c2-08dd29e7f55f
Faulting package full name:
Faulting package-relative application ID:
Never mind, grabbed the latest Odin.
Cozmo85 said:
The firmware posted. Is it carrier specific, like AT&T version or Verizon version.
Click to expand...
Click to collapse
Starting with the S8, firmware is universal. Bloatware and carrier customization is determined by the USERDATA file that you flash
GrandMstrBud said:
Anyone else try Odin on the S9? It just crashes for me but never had any issues on the S8. 3.2.13
Edit: Never mind, grabbed the latest Odin.
Click to expand...
Click to collapse
So these files do flash fine with latest Odin?
iBowToAndroid said:
Starting with the S8, firmware is universal. Bloatware and carrier customization is determined by the USERDATA file that you flash
So these files do flash fine with latest Odin?
Click to expand...
Click to collapse
So all I need to do is flash the userdata file in Odin?
GrandMstrBud said:
So all I need to do is flash the userdata file in Odin?
Click to expand...
Click to collapse
I don't know if you can *only* flash USERDATA by itself. I suppose if the Build is the same, you can try.
iBowToAndroid said:
I don't know if you can *only* flash USERDATA by itself. I suppose if the Build is the same, you can try.
Click to expand...
Click to collapse
I tried with the entire build with the userdata and it's still the stock firmware with no sprint customization's.
GrandMstrBud said:
I tried with the entire build with the userdata and it's still the stock firmware with no sprint customization's.
Click to expand...
Click to collapse
Which carrier is yours from and/or where did you get it?
iBowToAndroid said:
Which carrier is yours from and/or where did you get it?
Click to expand...
Click to collapse
I'm on sprint and I used the Samfirm app to download the sprint firmware. Model SM-G960U and Region SPR.
I found some other sites with more files but not sure which would be proper ones to use nor do I have a way to get them as seem to require payments or premium download services.
They seem to be much larger in size so probably the full files we'd want?
http://samsung-updates.com/details/122078//SM-G960U1/SPR/G960U1UEU1ARBG.html - This one seems to indicate the unlocked model (U1) number but yet is SPR firmware somehow??
http://samsung-updates.com/details/121907/Galaxy_S9_SM-G960U/SM-G960U/SPR/G960USQU1ARB7.html - this one seems like it maybe the actual sprint one for the sprint model?
https://firmware.gem-flash.com/index.php?a=browse&b=category&id=14757 - This site seems to have other files with different names too. Maybe this is one without the security patch, IE the very first FW?
I like others purchased unlocked but want to load the bloat version to gain the extra features but want it to be able to auto update and be just like the branded ones.
On my old S7E people just had simple instructions with a single file or two to flip between unlocked and locked. This file the OP posted seems too small...
GrandMstrBud said:
I'm on sprint and I used the Samfirm app to download the sprint firmware. Model SM-G960U and Region SPR.
Click to expand...
Click to collapse
If you're on Sprint, then you should already have Sprint customizations
bryanu said:
This file the OP posted seems too small...
Click to expand...
Click to collapse
Ever heard of compression? I promise you, all the files you need are right there
I bought the unlocked one not the sprint version
GrandMstrBud said:
I bought the unlocked one not the sprint version
Click to expand...
Click to collapse
There's no guarantee you can convert. I convert from U to U1 every day for my customers. I don't think I've ever gone the other way though.
But if it's possible, you'd need to flash the full firmware with wipe CSC and SPR userdata, and then afterwards insert a Sprint SIM until you get the prompt to reboot to apply the CSC features
I’ve done it on the S8 I had the S8U and flashed to the sprint version and it worked just fine. Not sure what I’m doing wrong do I need he U1 firmware? It’s been a long time so I can’t remember
GrandMstrBud said:
I’ve done it on the S8 I had the S8U and flashed to the sprint version and it worked just fine. Not sure what I’m doing wrong do I need he U1 firmware? It’s been a long time so I can’t remember
Click to expand...
Click to collapse
No, U1 *is* what you purchased, if you got the unlocked model. Did you do everything I said, including inserting a Sprint SIM and watching for the reboot prompt?
Yes I flashed all 5 files and left the sprint SIM in there. The boot loader didn’t change to the sprint logo either like it did on the S8. Maybe the files from the samfirm app are not for sprint I don’t know but for region I put in SPR just like I did with the S8 or maybe I got them from uodato I can’t remember honestly
---------- Post added at 11:31 PM ---------- Previous post was at 11:28 PM ----------
SamFirm v0.3.6.0
Checking firmware for SM-G960U1/SPR/G960U1UEU1ARBG/G960U1OYM1ARBG/G960U1UEU1ARBG/G960U1UEU1ARBG
Model: SM-G960U1
Version: G960U1UEU1ARBG/G960U1OYM1ARBG/G960U1UEU1ARBG/G960U1UEU1ARBG
OS: Oreo(Android 8.0.0)
Filename: SM-G960U1_1_20180228143240_rjycp5j0hq_fac.zip.enc4
Size: 3701765232 bytes
LogicValue: 1d0ttjz7md60l2p1
Checking firmware for SM-G960U/SPR/G960USQU1ARBG/G960UOYN1ARBG/G960USQU1ARBG/G960USQU1ARBG
Error: Could not send BinaryInform. Status code 200/400
Request was invalid. Are you sure the input data is correct?
Checking firmware for SM-G960U/SPR/G960USQU1ARB7/G960UOYN1ARB7/G960USQU1ARB7/G960USQU1ARB7
Model: SM-G960U
Version: G960USQU1ARB7/G960UOYN1ARB7/G960USQU1ARB7/G960USQU1ARB7
OS: Oreo(Android 8.0.0)
Filename: SM-G960U_1_20180212190313_ut86u59ymj_fac.zip.enc4
Size: 4130493888 bytes
LogicValue: d9mn8e5rcebun1km
GrandMstrBud said:
Yes I flashed all 5 files and left the sprint SIM in there. The boot loader didn’t change to the sprint logo either like it did on the S8. Maybe the files from the samfirm app are not for sprint I don’t know but for region I put in SPR just like I did with the S8 or maybe I got them from uodato I can’t remember honestly
Click to expand...
Click to collapse
As long as you flashed USERDATA_SPR, that's what contains the carrier customizations. If that alone didn't do it, and if you didn't get the reboot prompt afterwards, then it might not be possible
I think the problem are these files are wrong/not the full conversion.
In my post with the links I put above I found the following.
http://samsung-updates.com/details/122078//SM-G960U1/SPR/G960U1UEU1ARBG.html - This one has U1 in name but states SPR, this seems to match these exactly.
Problem with this is that means it is U1 firmware with SPR user data. This means your bootup logo would NOT change to sprint because it's not the full sprint package which means other FW tweaks carrier specific would not be included, only userdata which would require a factory reset to possibly see by itself.
The one the OP found seems to be just the normal U1 firmwares with the data part different only, thus your boot logo etc. would not change because it's the same one and not actually the sprint one.
We actually would need this one:
http://samsung-updates.com/details/121907/Galaxy_S9_SM-G960U/SM-G960U/SPR/G960USQU1ARB7.html
Oddly they both say Feb security patch yet are different FW version, BUT the model in this one is NOT the U1.
I could be wrong but I think this is the issue but no way to confirm since I can't get these other files...
There's too many people claiming this.
It is untrue. There is no global fastboot firmware, no global OTA.
If you've flashed this so called "global" firmware on a device it was not designed for, you WILL HAVE TO WAIT until the official fastboot firmware for your region has been released and re-flash. Maybe that will fix it, possibly not.
Why is there no global firmware?
Because each region has different carriers, different government regulations about services, bands, carriers, etc. Even different laws about wifi channels. Flashing RETIN firmware on a RETUS device can cause all sorts of problems including loss of cell service, loss of emergency service, issues with wifi, Bluetooth, and other wireless technologies.
Along with that, there are the issues of you never getting another OTA until you get back to the stock firmware for the region your phone was designed for. An xt1806 running retin firmware will NEVER get an OTA. This is known.
I don't know who started saying there is global firmware, but it's wrong. I don't want to see more phones bricked. Please think and use common sense.
Yes, I agree with but there's same version number for Oreo in different world regions. It may differ with OEM partition.
Sent from Moto G (5S) Plus via Tapatalk
QkiZMR said:
Yes, I agree with but there's same version number for Oreo in different world regions. It may differ with OEM partition.
Click to expand...
Click to collapse
Indeed, I unpacked the three OPS28.65-36 full zips that are available at mirrors.lolinet .com for sanders
As seen in the flashfile and servicefile XMLs, only "oem.img" is different across
XT1802 retin
XT1805 retid
XT1805 play .pl
"NON-HLOS.bin" (modem) and "fsg.mbn" (fsg) are the same.
After expanding the oem sparseimage with simg2img and using imgextractor.exe (because bash on windows doesn't support loop mounting apparently) to extract the filesystem:
their contents differ in preinstalled APKs, resources such as wallpapers, etc.
I suppose someone with an unlocked BL could dump their Oreo oem partition to have a look, but it shouldn't break if you flash an Oreo firmware from another region for g5s+.
Previously I had playpl version (PLAY is cellular network in Poland). They always add a lot of bloatware to their oem partitions. After unblocking bootloader I flashed retail version (RETEU). It contains some apps like Outlook or Linkend in but it was disabled.
where to get the a full reteu image?
I can only find one for us
pizzaboy192 said:
There's too many people claiming this.
It is untrue. There is no global fastboot firmware, no global OTA.
If you've flashed this so called "global" firmware on a device it was not designed for, you WILL HAVE TO WAIT until the official fastboot firmware for your region has been released and re-flash. Maybe that will fix it, possibly not.
Why is there no global firmware?
Because each region has different carriers, different government regulations about services, bands, carriers, etc. Even different laws about wifi channels. Flashing RETIN firmware on a RETUS device can cause all sorts of problems including loss of cell service, loss of emergency service, issues with wifi, Bluetooth, and other wireless technologies.
Along with that, there are the issues of you never getting another OTA until you get back to the stock firmware for the region your phone was designed for. An xt1806 running retin firmware will NEVER get an OTA. This is known.
I don't know who started saying there is global firmware, but it's wrong. I don't want to see more phones bricked. Please think and use common sense.
Click to expand...
Click to collapse
Thank you so much. Is there a place we can check for our version? My phone is down and I wish it wasn't. It'll teach me to play with fire.
For those who aren't already aware, G998U is the model number of all of the US carrier versions of the S21 Ultra. The G998U1 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=322089
U1 firmware: https://www.androidfilehost.com/?w=files&flid=322090
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 carrier's firmware 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
Flashing the U1 right away when my Devices arrives
Polishow said:
Flashing the U1 right away when my Devices arrives
Click to expand...
Click to collapse
That's why I post it
That, and so that anyone interested can dig through the firmware for anything interesting.
I'm uploading in order of model number, so Ultra is last unfortunately - and my upload speed is only 10 Mbps. Should be up in the next few hours though
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 anyone know if Is the version SM-998U or SM-998U1 have or not dual SIM?
Thanks for doing this ! My phone arrives Wed and of course I wanna flash the U Home CSC to my unlocked U1 device so I can get the AT&T calling features. Are the ones you've uploaded the latest firmwares?
And thanks again for always taking time to do this!!!
Sorry for the possible silly question, but I am coming back to the Galaxy after 4 years on the Pixel and haven't been flashing for a while.
I am getting an Ultra from T-Mobile. If I flash the U1 (to remove the bloat) and then follow the instructions above, it says it will put the carrier files on there. Will that just put the bloat back on? I guess I was wondering if it would make it "stock" going forward. I just wanted to figure that out before I set the phone up since it requires a factory reset. Thanks!
crowax said:
Sorry for the possible silly question, but I am coming back to the Galaxy after 4 years on the Pixel and haven't been flashing for a while.
I am getting an Ultra from T-Mobile. If I flash the U1 (to remove the bloat) and then follow the instructions above, it says it will put the carrier files on there. Will that just put the bloat back on? I guess I was wondering if it would make it "stock" going forward. I just wanted to figure that out before I set the phone up since it requires a factory reset. Thanks!
Click to expand...
Click to collapse
No, that's not what it says - I think you're mis-reading. Flashing U1 removes bloat, period. If you want the bloat gone, you have no need to do anything else other than simply flashing U1 firmware
iBowToAndroid said:
No, that's not what it says - I think you're mis-reading. Flashing U1 removes bloat, period. If you want the bloat gone, you have no need to do anything else other than simply flashing U1 firmware
Click to expand...
Click to collapse
Oh perfect. I checked again after your post and my confusion was at
"the correct procedure for switching from one carrier's firmware to another is". I was thinking it was the procedure to switch from a carrier firmware to any other firmware including U1. So the re-adding of the carrier files didn't make sense.
Thank you very much for your quick answer!
OP Requested my linked deleted
bANONYMOUS said:
Here are links to both Canadian and US official samsung firmwares without bloat
Samsung Official Unlocked Firmware:
Canada = XAC
United States = XAA
Click to expand...
Click to collapse
Go create your own thread if you're going to post links other than the ones in my OP
I do have my own thread about these firmwares, I was just including the Canadian bloat free firmware because you only have the US firmwares. The links are to samfw because they update them regularly so people can get the latest releases where as your links are the current version you linked so if you don't update them then they'll be out of date versions. Do you get paid from your Android File Host links or something? What's the issue? No need to be hostile, just trying to help provide information
EDIT:
Also, when you're flashing between different carrier firmware's, you should only use CSC and not HOME_CSC because keeping the user data sometimes includes the bloat apps preinstalled.
The rule of thumb is if you're CHANGING anything, start fresh with CSC
If you're UPDATING from the same carrier firmware to a newer version, use HOME_CSC.
So for anyone using this guide, it's not recommended to use HOME_CSC when converting over to the bloat free firmware as it's a different carrier release. Not saying it won't work, it's just not recommended, almost like a dirty flash so it could cause stability issues down the road after a few OTA's or something.
bANONYMOUS said:
I do have my own thread about these firmwares, I was just including the Canadian bloat free firmware because you only have the US firmwares.
Click to expand...
Click to collapse
XAC is for model G998W. The title of this thread makes it clear that this is only for models G998U and G998U1. So kindly delete your posts, and keep them in your own thread
Okay, post deleted, but it's probably worth noting that you don't know what the G998W is. Because it's the same phone as the U and U1. During the One UI 3.0 Beta on the S20 Ultra, I flashed G988U on my G988W, and when the beta continued onto the U1, I flashed those firmware files as well. The Canadian S20/S21 is just a non branded T-Mobile with more supported radio bands in the firmware.
If you actually look at the carrier info for the S20 Unlocked U/U1/W firmware, they all say XAC and XAA at the bottom no matter whether it's U/U1/W. They are all the same phone and Samsung even uses the same firmware merged, just different radio bands, and because Canadian radio bands support ALL bands, it makes the W firmware the a merge of both U and U1, so it's actually the better choice from what you have posted because it supports every U/U1/W the best. So your post is relevant to the W models whether you want to accept it or not.
That's why I included a link to the firmware, because it's the same device, same flashing process, completely same procedure, so this thread IS relevant to the W models even if you said U and U1 only, the W is also included in that even if you didn't say it was, doesn't make it true.
Also the only difference between U and U1 is U is unlocked but INCLUDES carrier bloat, U1 is unlocked and has NO carrier bloat.
So, closing info here.
U1 is unlocked, no carrier bloat, US radio bands
U is unlocked, HAS carrier bloat, US radio bands
W is unlocked, no carrier bloat, ALL radio bands
You just need to make sure it's the SM-G998W for AXC and it's the best choice with no bloat.
Just because you clearly didn't know this about the W phones, doesn't mean you gotta get all snappy, I'm just trying to help the community.
bANONYMOUS said:
Okay, post deleted, but it's probably worth noting that you don't know what the G998W is.
Click to expand...
Click to collapse
I'm absolutely very well aware of what W models are. Thanks.
Then why are you mad I included it when it's the same device? I don't get why you're being salty about it. I'm just trying to help out.
bANONYMOUS said:
Then why are you mad I included it when it's the same device? I don't get why you're being salty about it. I'm just trying to help out.
Click to expand...
Click to collapse
1. Not mad at all
2. It's the same device internally, yes. But this thread is about software - not hardware. And the software being discussed is the USA firmware, not the Canadian firmware.
sorry I've also been out of the firmware game for a while too. I have a U1 from Samsung unlocked S21 Ultra and need to put the ATT carrier firmware on it. If I'm reading this right, I'm using Odin and flashing the XAA U1 firmware without a sim, when it reboots and reads updated SIM carrier setting at reboot then I am shutting it down and immediately attempting to install the ATT U1 firmware (all BL, AP, CP, CSC (non HOME CSC)? I don't see where I would select USERDATA but I need the ATT options (was going to exchange it but I got all the incentives)
alfredtv said:
sorry I've also been out of the firmware game for a while too. I have a U1 from Samsung unlocked S21 Ultra and need to put the ATT carrier firmware on it. If I'm reading this right, I'm using Odin and flashing the XAA U1 firmware without a sim, when it reboots and reads updated SIM carrier setting at reboot then I am shutting it down and immediately attempting to install the ATT U1 firmware (all BL, AP, CP, CSC (non HOME CSC)? I don't see where I would select USERDATA but I need the ATT options (was going to exchange it but I got all the incentives)
Click to expand...
Click to collapse
1. If your phone is already running U1 firmware, there's no need to flash it again
2. If you don't see the USERDATA slot, you have a very old version of Odin
It is running U1 but I need the ATT bloatware.....I'm on FirstNet and the only way it will connect correctly is if it's running the ATT built in config files. So I'm trying to go from clean to dirty!!
Hello,
I am trying to root my S21 Ultra and have tried following multiple tutorials with no success. Looking for assistance to see if anyone knows what I am doing wrong.
Model: SM-G998U1
CSC: XAA
I have downloaded the latest firmware via Frija flashed it onto my device via Odin. I then put the AP file onto my device downloaded Magisk and patched the file to create the Tar file. I then tried to flash the device again with the same files except I swapped the AP file with the Tar file Magisk generated. It gets almost all the way to the end but then fails on "vbmeta_system.img" and my Device shows "secure check fail: vbmeta(1)". Does anyone know what this error means. I tried googling it with no success. Sorry I am a total noob when it comes to this stuff. Any assitance is greatly appriciatede.
Thank you.
@Puffnstuf
You have the Galaxy S21 Ultra's US carrier unlocked variant (U1).
Unfortunately, Samsung doesn't allow unlocking the bootloader of US and Canadian Galaxy devices. There exists an unofficial bootloader unlock method, but you can only use it if your Galaxy S21 is on the v1 bootloader.
Without an unlocked bootloader, you can't flash third-party binaries (such as the Magisk-patched boot image).
@SkandaH
How do I tell if my device is on the v1 bootloader? I am guessing its not if I have updated the device. If its not is there anyway to downgrade to the v1 bootloader?
If I am unable to unlock the bootloader should I avoid updating my device incase a new way to unlock the bootloader is released in the furture?
@Puffnstuf
The fifth character from the right end of the build number is the bootloader version. For example, the latest available firmware for the SM-G998U1 model is G998U1UES5CVF5. Its bootloader version is v5.
There is no known way to downgrade the bootloader version.
You may start deferring updates, but it's really difficult to predict the future. If you want to tinker with your device, it's always better to get one that comes with an unlockable bootloader.
I haven't been in the phone flashing game for a while. I'm not seeing many topics regarding my Xperia 1ii (Docomo version) Because there are locked bootloaders nowadays or something? Would like to flash a global ROM on it but I don't see official TWRP support for it either.
Not receiving the Android 12 updates either even though I should by now. I'm in South East Asia, is my location causing the update not to get pushed over?
using Japaneses model doesn't mean it always locked, i have AU version of xz1 that unlocked and have xz3 global that locked.. but yeah. most Japaneses model are locked. if you are locked. or only want to flash global. there no need to unlock it. or use twrp or other recovery. in fact flashing official rom doesn't even use recovery mode at all. it use download mode(if im not mistaking it)and with tool like xperia Firmware downloader and newflasher. you can flash any official rom to your docomo one.
BUT. REMEMBER!!
1.Japaneses smartphone use special nfc hardware that different than global. your nfc will go bye bye if you flash global rom in there.
2.careful. do research before flashing. xperia devices is not as easy as samsung or xiaomi. 1 mistake can be fatal. if lucky it only bootloop. but if unluck, from software/feature glitch, locked(sim/ubl) or just refuse to detected(A.k.a permanent dead)
i been use xperia devices since z4 era. and trust me it more scare to change official rom on locked devices than swap custom rom or install mod like magisk,etc on unlocked devices even manually modified system file are better than change to global on locked devices,