How To Guide OTA and Non-OTA Firmware for S22 Ultra SM-S908U and S22 Ultra SM-S908U1 Versions
- Thread starter kangi26
- Start date
Noticed mine stopped working this weekend. Tried everything and can't get it to work.
Kris_b1104
Senior Member
Hello, I have the problem of not getting OTA updates on my s22 ultra (SM-S908U/DS). In the software information page it says
and my phone's whole model code is SM-S908UZKATT
and the baseband version is S908USQS2AVHJ
I need the right firmware for my phone for the manual update.
Thanks in advance. Cheers.
and my phone's whole model code is SM-S908UZKATT
and the baseband version is S908USQS2AVHJ
I need the right firmware for my phone for the manual update.
Thanks in advance. Cheers.
You said your device is DS..dual Sim but model number is ATT? That's not possible as AT&t doesn't have a dual sim
as I live in Bangladesh I'm currently using local operators Teletalk (physical sim) and GrameenPhone (eSim)
I seriously have no idea about that. I used an app named Phone info which is showing my product code as: sm-s908uzkaatt.
Pardon the ignorant question, I haven't been involved with Samsung for years.
Is the S908U and U1 firmware interchangeable?
I assume flashing U1 firmware on a U won't carrier unlock or otherwise allow using the device on a different network?
Is the S908U and U1 firmware interchangeable?
I assume flashing U1 firmware on a U won't carrier unlock or otherwise allow using the device on a different network?
Maxninja
Senior Member
- Correct. You can swap U1 > U or U > U1 firmware. It will just load in the bloatware if you do the carrier firmware.
-- Negative, Ghost Rider. You're referring to sim unlock which is TOTALLY DIFFERENT than what's being discussed.
Copy, thanks.
Out of curiosity, what sort of unlock IS being discussed here?
Are carrier specific variants generally SIM/carrier unlockable upon request from the original lienholder?
Maxninja
Senior Member
- If you're asking what was being discussed prior to your comment, it was about a guy posting a model name that sounds like it's an ATT model but it isn't.
-- Uh.. of you want to be pedantic about it, sure. ATT (or insert your carrier here) is the lienholder if you're paying a balance to own the device. If you want it unlocked, ATT will give you the sim unlock but here's the criteria from ATT site:
"
- Is an AT&T phone or device and isn't active on another AT&T account.
- Has a paid-off installment plan:
- Paid through your monthly bill: Submit your unlock request at the start of your next bill period.
- Paid off early: The wireless number assigned to the device must be active for at least 60 days. Wait 48 hours after you make your final payment to submit your unlock request.
- Was paid in full when you bought it (it was not purchased on an installment plan). You must wait 60 days from your purchase date to submit an unlock request.
- Hasn't been reported as lost, stolen, or involved with fraud and doesn't have a past-due account balance. (Make a payment to bring your account current. It may take up to 24 hours to post.)
- Is an AT&T Prepaid® phone with a Prepaid SIM and six months of service on the AT&T network. You must submit your unlock request using the most recent version of the AT&T Device Unlock app."
I wasn't referring to previous discussion, my question is not in reference to anything prior. I wasn't sure what you meant by "what's being discussed"
Right, just confirming what I thought I already knew. Carrier/SIM unlock is at carrier's discretion, subject to their own requirements. Firmware won't change this, probably because of IMEI whitelist. If IMEI not blacklisted, only option to unlock outside of carrier unlock is via 3rd party service which may or may not work-- Uh.. of you want to be pedantic about it, sure. ATT (or insert your carrier here) is the lienholder if you're paying a balance to own the device. If you want it unlocked, ATT will give you the sim unlock but here's the criteria from ATT site:
"
If you don't have ATT, go to your carriers website and do your due diligence and research into your carrier's policies
- Is an AT&T phone or device and isn't active on another AT&T account.
- Has a paid-off installment plan:
- Paid through your monthly bill: Submit your unlock request at the start of your next bill period.
- Paid off early: The wireless number assigned to the device must be active for at least 60 days. Wait 48 hours after you make your final payment to submit your unlock request.
- Was paid in full when you bought it (it was not purchased on an installment plan). You must wait 60 days from your purchase date to submit an unlock request.
- Hasn't been reported as lost, stolen, or involved with fraud and doesn't have a past-due account balance. (Make a payment to bring your account current. It may take up to 24 hours to post.)
- Is an AT&T Prepaid® phone with a Prepaid SIM and six months of service on the AT&T network. You must submit your unlock request using the most recent version of the AT&T Device Unlock app."
Imagine my surprise when Youtube Vanced started working out of the blue yesterday... All I did was clear the cache when I had the issue last week which didn't really do anything so I had it just sitting there until I could get some time to look into ReVanced.
I'll take it for now
Top Liked Posts
-
There are no posts matching your filters.
-
2Alright Bois, GOT THE FIX. Works for all S22/+/Ultra
Had the same issue everyone else is experiencing after the latest Aug update:
I was able to get it working after performing the following: (noob friendly)
Files needed beforehand:
A. Odin3 v3.13.1_3b_Patched (only download version: Odin3_v3.13.1_3B_patched)
B. Open browser and go to https://samfw.com/, enter your SPECIFIC MODEL NUMBER
C. Pay attention to the U and U1 version as you will need both
4. Choose your current carrier and then select (Version) to the right to download the files
(verify build date is most current)
EXTRACT FILES AFTER DOWNLOADING THEM
Links for S22 Ultra
S22 Ultra U
S22 Ultra U1
Links for S22+
S22+ U
S22+ U1
Links for S22
S22 U
S22 U1
1. Make a backup of your phone if you haven't already as we will need to do a factory reset ( I used Samsung Smartswitch)
2. Factory reset your phone in settings and then turn off
3. Boot into Recovery menu (press and hold volume up + power button) and perform the following
a. wipe cache partitionb. wipe data/factory resetc. power off device4. Boot into download mode
a. Press and hold the two volume keys + power button at the same time, release once the screen is onb. Insert USB cable to your PC and to your phone and press the volume up buttonc. Download mode has started and we can start loading files into ODIN5. Open Odin and load corresponding U files
If you wish to stay with carrier locked Firmware (bloatware etc.) ONLY FLASH UAfter loading the AP file, it will take about 45 secs to complete, just wait until it finishes to load other files
For CSC: use the CSC_OYN file only
6. Select Start and wait until it finishes, phone will turn on and disconnect from PC
7. Go through the initial setup process until you are at the main screen (don't sign into anything)
8. Your phone should work now, test calling/internet/etc.
WAIT 10 MIN BEFORE FLASHING U1
Flashing U1
Repeat steps 2-5 with U1 files
Select Reset option on ODIN if you didn't close the application
Reload Fw files with U1
For CSC: use the CSC_OYN file only
Select Start and wait until it finishes, phone will turn on and disconnect from PC
Go through the initial setup process until you are at the main screen (don't sign into anything)
Your phone should work now, test calling/internet/etc.
Enjoy!!!111
Very strange. I used the dialer code trick to pull it this time, and have for the last several updates with no issues. I've also done the whole date change thing before to pull an update, and once I've gotten it and changed the date back all has been fine. Sucks that something as simple as that could hammer your phone. Hope you get it resolved as painlessly as possible.
1
This worked great!
I was trying to push (via ADB) the " -Galaxy S22 Ultra (SM-S908U1):
Beta 1 (XAA CSC): CHW3->ZWIA (Thanks to @Robert Smali)" from "https://forum.xda-developers.com/t/...2-ultra-beta-thread-update-zip-files.4615057/"
My phone is a S22 Ultra bought from Verizon and ADB would not complete the file transfer because of a Status 1 error (trying to push an older file? or possibly because my Verizon phone wasn't showing as U1). Regardless of the exact cause of my issue, I was able to follow @sincer 's Steps to reset and push the U version of CHW3; Waited ~10 minutes, and I pushed the U1 versions (without a USERDATA file, because they aren't present in Unlocked CSC folders [from my knowledge, USERDATA is a carrier specific file].
Once I had pushed the U1 of CHW3 using Odin, I was able to follow the other thread's means of updating via ADB and that got me all the way to One UI 6 Beta on my Verizon bought S22 Ultra.
After that: I simply had to use Samsung Smart-Switch to restore all of my apps/files/settings/etc; and since, I'm off to the races.
Thanks for the insight @sincer. -
22
See Post #2 and #3 for the Links to the Firmware
All of the firmware posted here can be flashed on any U or U1 Device. Each of the firmware's are NOT carrier dependent and only has carrier labels listed in order to have an idea if you might get OTA when you flash it.
The firmware packages house each of the carrier's information, features, bloat, splash screens etc. (That's why they roll in at over 7Gb). When you flash a firmware the installation package reads your SIM, determines what carrier you're using and then installs the "package" that's designed for your carrier
S908USQU1AVA7 (Totally fake Firmware. I just made it up for example purposes)
S=Galaxy S
908U or F etc, the model of device
SQ, FX etc = CPU and model specific
U,S,E = Update, Security, Engineering, respectively
1,2,3,4,5 etc = bootloader revision (This is important! You cannot go to a previous revision)
A, B, C etc = Android version
U, V = Year (U=2021, V=2022 etc)
A,B,C etc = month (January A - December L)
1 - 9 and then A - Z =build compilation. This basically means how many builds there are in a month. They start at 1 and go to Z
So S908USQU1DVAM would be
S908-U-SQ-U-1-A-V-A-7
S908U (S22 Ultra Carrier version), SQ (Snapdragon), U (Update), 1 (Bootloader version), A (Build 12), V (2022), A (January), 7 (7th build)
BL- Boot Loader
AP - Application Processor (also termed PDA), this is the system partitions, recovery etc,
CP - This is the Modem
CSC - Consumer Software Customization. This is all of the stuff that contains the different carrier features, wi-fi calling, APN stuff like that. You'll notice that this file is getting as big(If not bigger) than the AP file with the system information.
HOME_CSC - This is still the "Same" as the CSC, except it retains the CSC information that is flashed on the device. It wont wipe your device like the normal CSC will. This is part of the package in the OTA that doesn't wipe your phone
USERDATA - Carrier files, this "Brands" the device to your carrier
How to enter Download Mode:
Turn off the device.Connect USB cable to your PC (Leave it disconnected from the phone)Press and hold down the Volume Up and Volume Down buttons. While they are still pressed, plug in the USB cable into your phone.The phone will go into download mode press volume up. In Odin you will see that phone is added.
A decent writeup on how to use Odin:
From samsungfirmware.net How to Flash Samsung Phone Firmware Using Odin***You MUST use one of the Patched versions of Odin in post #2 or #3 when flashing***
Dirty Flash:
I would only do this if you are having to manually update to the newer firmware and would not do it if you are coming/going to U/U1 or from beta firmware or if you are on an old firmware. I'd also highly recommend doing a back up prior to the doing thisLoad these into OdinBLAPCPHOME_CSC
Do NOT flash CSC or USERDATA (If it's in the download package), either of these WILL wipe your device.This is a "dirty flash" and these can sometimes cause issues. Keep in mind if things start going sideways and stuff starts not working right, your first step to a solution will be to wipe the device.15S908U1 - Unlocked Versions
Bootloader 2 - If you are on a Bootloader 2 firmware you can NOT go back to a Bootloader 1 firmware, there is NO workaround. See Post 1 to determine which bootloader you're on13/OneUI 5.0 BETA -You MUST be on S908U1UEU2AVF7 in order to update to this beta.This is BL 2 so you can go back to stock, but if you do it's HIGHLY recommended to not dirty flash (It might not let you so be prepared to wipe)BETA1>BETA2 - S908U1UEU2ZVHK Thanks for the file @Venom0642You MUST be on S908U1UEU2ZVH4 in order to update to Beta 2 (ZVHK)Bootloader 1S908U1UEU1AVA6 - Thanks to 66880]@southern87 for the MIRROROdin3_v3.13.3b Patched: HEREOdin3_v3.14.4 Patched: HERE14S908U - Carrier Versions
Bootloader 2 - If you are on a Bootloader 2 firmware you can NOT go back to a Bootloader 1 firmware, there is NO workaround. See Post 1 to determine which bootloader you're onS908USQU2AVE4 - ATT/CHA/CCT/TMB/VZW thanks to @Venom0642 for the linkS908USQS2AVDC - ATT/TMB thanks for the link @hyeltonBootloader 1S908USQU1AVCK - TMBS908USQU1AVCJ - ATT/CCT/CHA/VZWS908USQU1AVC8 - ATT/CCT/CHA/TMB/VZWOdin3_v3.13.3b Patched: HEREOdin3_v3.14.4 Patched: HERE7
There's VERY little chance you'll brick (The only way that I know you can is pulling the USB cable when flashing), that aside, it'll just error before the flash could happen.
That being said, If you have a S908U or S908U1 device you can flash ANY of the firmware on this post. The firmware is not Carrier agnostic, the only reason there are carrier tags next to the posted firmware is to let people if they flash a specific one whether or not that is the current stock one and will get OTA in future releases.
Most of that info is in the OP (I think.......), and if you're not too familiar with the process, I highly advise taking the time to read thru the pages, almost everything you'll need to know has been posted.
If you can't find something ask, most everyone is super helpful
