Related
I'm currently running a T-Mobile Samsung Galaxy S7 with an AT&T sim card.
Model# SM-G930T.
Android Version 8.0.
Baseband Version G930TUVU4CRI2.
Build Numer R16NW.G930TUVU4CRI2.
I'm wanting to hopefully flash the AT&T firmware to this phone, but I'm not exactly sure how to go about doing it. I've spent about 2-3 hours searching back & forth between the AT&T forums & T-Mo forums but can't seem to find a definitive answer, or definitive guidance.
I think it's fairly simple via Odin once I have the appropriate firmware. But I just wanted to make sure since I'm flashing another carriers firmware on top of an existing carriers firmware.
Everything aside from video calling & WiFi calling is working. I would love to be able to use those 2 features & receive future OTA updates. Any info/guidance is greatly appreciated. Thanks!
No love?
I'd settle for an insulting reply guiding me in the right direction. I just don't want to brick my phone throwing AT&T firmware right over top of T-Mobile firmware.
The rom you are looking for is here: https://forum.xda-developers.com/att-galaxy-s7/development/rom-t3804287
I am using it now and love it. Several options for the install. Can root if desired.
ff-racer said:
The rom you are looking for is here: https://forum.xda-developers.com/att-galaxy-s7/development/rom-t3804287
I am using it now and love it. Several options for the install. Can root if desired.
Click to expand...
Click to collapse
Thanks for the response racer! I'm gonna bookmark that page and definitely save it. Right now I'm looking to stay 100% stock. But I'll definitely go that route if I can't get any guidance on going stock AT&T.
Drewbalicious said:
Thanks for the response racer! I'm gonna bookmark that page and definitely save it. Right now I'm looking to stay 100% stock. But I'll definitely go that route if I can't get any guidance on going stock AT&T.
Click to expand...
Click to collapse
Going stock AT&T is no harder than going stock for any carrier - here is the skinny, using SamFirm 0.3.6, the latest version of ODIN and a S7 of the Snapdragon sort (along with variations for the S7 Edge):
1. Automatic search using SamFirm - the easiest method - SM-G930A (for the S7 edge - SM-G935A) with a country/carrier code of ATT (both phones)
2. Once the firmware shows up, select where you want it stored on your PC, then select Download Automatically/Decrypt Automatically (this performs all the scutwork for you, such as checking for CRC32 errors, as well as separating the firmware itself so you can simply plus the parts into ODIN.).
3.. Once you have the firmware downloaded and decrypted, it's time to put ODIN to work; but before you can do that, you have to do two things; physically connect the phone to the PC, and get your phone itself ready to receive the files via ODIN. The ODIN part is easy - your newly-downloaded firmware is in multiple parts; each part fits in a specific block in ODIN. For the CSC part, you have a choice between CSC and HOME-CSC. Because I tend to make sure nothing is left over from the previous firmware, I choose CSC; this forces the new firmware to start from scratch. Lastly, before sending those files to the phone, you must enable the phone to be able to get them - you have to put the phone into Download Mode. (for all Snapdragon S7s - including the S7 Edge, it is Volume-up, Power, and Fingerprint-sensor (all at the same time)); a sky-blue screen will show, indicating you are in Download mode; this is what you want. Make sure your cable is properly connected, then hit the Start button in ODIN - that's it. (As long as the transfer is successful (which ODIN itself will tell you with a green PASS message) you're done the hard part; the phone will auto-reboot and start the Setup process for the new firmware.
Have at it.
Hello,
I bought an S7 from eBay, it was marked as a "new" and "UK" phone. I factory reset the device on receipt and apparently worked fine to start with. However, there have been a few problems (poor signal, battery life, echoes in video calls) and I noticed the device was still on Android 6, so wondered if an update to Android 8 might help (?).
There is no menu option available to update Android so I started looking into flashing firmware. On further digging, the device seemed an official SM-G930F but "United Arab Emirates" appears in the "About Phone" section.
I downloaded some stock firmware (Android 8, UK Vodafone which is the network I expect to run it on) and tried flashing with Odin 3.13 and it failed with error "unsupport dev_type" on the phone screen. Any suggestions?
I also noticed that in "Download mode" the phone said it was a "SM-G930V". I wondered if this was why the flash had failed. For the SM-G930V I only seem to be able to get USA/Verizon stock firmware. Might this work or would I have trouble using this in the UK?
Any help would be much appreciated. I'm a newbie in this area so apologies if any of these questions are answered elsewhere.
Many thanks,
Edwin
ecc25 said:
Hello,
I bought an S7 from eBay, it was marked as a "new" and "UK" phone. I factory reset the device on receipt and apparently worked fine to start with. However, there have been a few problems (poor signal, battery life, echoes in video calls) and I noticed the device was still on Android 6, so wondered if an update to Android 8 might help (?).
There is no menu option available to update Android so I started looking into flashing firmware. On further digging, the device seemed an official SM-G930F but "United Arab Emirates" appears in the "About Phone" section.
I downloaded some stock firmware (Android 8, UK Vodafone which is the network I expect to run it on) and tried flashing with Odin 3.13 and it failed with error "unsupport dev_type" on the phone screen. Any suggestions?
I also noticed that in "Download mode" the phone said it was a "SM-G930V". I wondered if this was why the flash had failed. For the SM-G930V I only seem to be able to get USA/Verizon stock firmware. Might this work or would I have trouble using this in the UK?
Any help would be much appreciated. I'm a newbie in this area so apologies if any of these questions are answered elsewhere.
Many thanks,
Edwin
Click to expand...
Click to collapse
Go to the play store and install Sam phone info, then look at what chipset it lists, you don't want it to be Qualcomm Snapdragon, Eyxnos is what you want to see.
G930V is US Verizon firmware
Report back please.
cooltt said:
Go to the play store and install Sam phone info, then look at what chipset it lists, you don't want it to be Qualcomm Snapdragon, Eyxnos is what you want to see.
G930V is US Verizon firmware
Report back please.
Click to expand...
Click to collapse
Thanks for your reply! The "hardware/board" is "qcom/msm8996". Where does that leave me?
I noticed that the Bootloader & Baseband Versions begin G930VVRU but the PDA and CSC versions begin G930FXXU. Not sure if that means anything.
Thank you!
ecc25 said:
Thanks for your reply! The "hardware/board" is "qcom/msm8996". Where does that leave me?
I noticed that the Bootloader & Baseband Versions begin G930VVRU but the PDA and CSC versions begin G930FXXU. Not sure if that means anything.
Thank you!
Click to expand...
Click to collapse
Well the person who sold it to you is a liar for starters, it's not a "brand new UK device", it's a US S7 (G930V) Originally bought for the Verizon Network in the states. They are difficult to do anything with as the Qualcomm boot loader is locked down.
So your first option is to update the firmware to the latest Verizon Oreo, probably not worth it since that firmware is designed to work on a couple of frequencies only.
Next option is to flash unbranded US firmware with a modified version of Odin that ignores mismatch devices etc and just installs the firmware. You will need to use this version of Odin from this thread >>> here Odin 13 PatchD.zip is the one you want.
Unzip, run Odin, place phone into download mode flash firmware. You will need to download G930U from Sammobile or undato.com The 3 letter code should either be USC or XAA.
Any questions please ask.
Also before flashing please remove you google account off the phone.
cooltt said:
Well the person who sold it to you is a liar for starters, it's not a "brand new UK device", it's a US S7 (G930V) Originally bought for the Verizon Network in the states. They are difficult to do anything with as the Qualcomm boot loader is locked down.
So your first option is to update the firmware to the latest Verizon Oreo, probably not worth it since that firmware is designed to work on a couple of frequencies only.
Next option is to flash unbranded US firmware with a modified version of Odin that ignores mismatch devices etc and just installs the firmware. You will need to use this version of Odin from this thread >>> here Odin 13 PatchD.zip is the one you want.
Unzip, run Odin, place phone into download mode flash firmware. You will need to download G930U from Sammobile or undato.com The 3 letter code should either be USC or XAA.
Any questions please ask.
Also before flashing please remove you google account off the phone.
Click to expand...
Click to collapse
Thank you for these detailed instructions -- much appreciated!
Presumably using this version of Odin carries a high risk of bricking the phone if I get anything wrong?
Out of interest, what's the reason for removing the Google account?
Cheers,
Edwin
ecc25 said:
Thank you for these detailed instructions -- much appreciated!
Presumably using this version of Odin carries a high risk of bricking the phone if I get anything wrong?
Out of interest, what's the reason for removing the Google account?
Cheers,
Edwin
Click to expand...
Click to collapse
Because it's a further complication with FRP lock you just don't need after flashing. Just add the google account after flashing and your good to go.
With regards to flashing yes there's always a risk that something can go wrong, that's why you take your time and follow the steps exactly. In your case it's pretty straight forward and remember nothing changes on the external SD card, so anything you want to keep can be moved there before flash.
I would also mention that theoretically you could flash UK unbranded (BTU) but it's for G930F Exynos devices so best at this stage just get the device on unbranded Qualcomm and working on UK networks.
let me know how it goes.
cooltt said:
Because it's a further complication with FRP lock you just don't need after flashing. Just add the google account after flashing and your good to go.
With regards to flashing yes there's always a risk that something can go wrong, that's why you take your time and follow the steps exactly. In your case it's pretty straight forward and remember nothing changes on the external SD card, so anything you want to keep can be moved there before flash.
I would also mention that theoretically you could flash UK unbranded (BTU) but it's for G930F Exynos devices so best at this stage just get the device on unbranded Qualcomm and working on UK networks.
let me know how it goes.
Click to expand...
Click to collapse
Hello,
I've just tried doing what you suggested (I think!) and I got a failure. Odin said "FAIL! (Auth)" and the phone said "Secure check fail: apnhlos". I tried rebooting and got a security error. So I tried Odin again and it passed.
However, now the phone won't boot, it alternates between "Samsung Galaxy S7" and a blank screen. In recovery I get:
"#fail to open recovery_cause(No such file or directory)#"
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
dm-verity verification failed..."
Any ideas?
Thanks a lot,
Edwin
ecc25 said:
Hello,
I've just tried doing what you suggested (I think!) and I got a failure. Odin said "FAIL! (Auth)" and the phone said "Secure check fail: apnhlos". I tried rebooting and got a security error. So I tried Odin again and it passed.
However, now the phone won't boot, it alternates between "Samsung Galaxy S7" and a blank screen. In recovery I get:
"#fail to open recovery_cause(No such file or directory)#"
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
dm-verity verification failed..."
Any ideas?
Thanks a lot,
Edwin
Click to expand...
Click to collapse
Ok, so try an earlier G930V firmware and please make sure you are placing the file in the right places with Odin. The US carriers have all updated their firmware and often closes the loophole which allows the patched Odin to work. Then it's just a question of waiting until someone develops a workaround again.
Also you can pick up an S7 from ebay for about £100 now, your always going to have problems with a qualcomm device on UK networks. Where about are you in the UK?
cooltt said:
Ok, so try an earlier G930V firmware and please make sure you are placing the file in the right places with Odin. The US carriers have all updated their firmware and often closes the loophole which allows the patched Odin to work. Then it's just a question of waiting until someone develops a workaround again.
Also you can pick up an S7 from ebay for about £100 now, your always going to have problems with a qualcomm device on UK networks. Where about are you in the UK?
Click to expand...
Click to collapse
Thanks! Actually shortly after posting I found a suggesting of using CSC not HOME_CSC, which enabled the flash to work (at the expense of phone data, as expected).
The device still does have a few issues though, as you predicted. Is the radio hardware different for Qualcomm? Might need to buy another then. Any advice to avoid being scammed on eBay again?!
Thanks so much!
ecc25 said:
Thanks! Actually shortly after posting I found a suggesting of using CSC not HOME_CSC, which enabled the flash to work (at the expense of phone data, as expected).
The device still does have a few issues though, as you predicted. Is the radio hardware different for Qualcomm? Might need to buy another then. Any advice to avoid being scammed on eBay again?!
Thanks so much!
Click to expand...
Click to collapse
Well you could flash G930U which opens up all of the radios for the US and you may have less issues but US and European devices have different chips so your never going to be able to flash any EU generic firmware. I'm addition the US and Europe are different cellular regions with different operating frequencies. You can get by with what you have but never get full functionality.
I think you were just unlucky with this phone on ebay, there are plenty which are genuine EU region devices.
I have the T-Mobile version A71 5g, model # SM-A716U. I can't stand the T-Mobile branding, especially the jingle on startup.I am trying to flash the generic firmware XAS-A716USQU1ATFB-20200713085932 with odin and it fails every time with a message on the phone.
Odin on the computer does not show any error. Once that process is complete the phone reboots to the bootloader and shows an error message: failed the resizing-data
Is there any way to do this without wiping the phone? I read some things that say you have to log out of google and samsung accounts, would that really make this process fail?
digitalcandy said:
I have the T-Mobile version A71 5g, model # SM-A716U. I can't stand the T-Mobile branding, especially the jingle on startup.I am trying to flash the generic firmware XAS-A716USQU1ATFB-20200713085932 with odin and it fails every time with a message on the phone.
Odin on the computer does not show any error. Once that process is complete the phone reboots to the bootloader and shows an error message: failed the resizing-data
Is there any way to do this without wiping the phone? I read some things that say you have to log out of google and samsung accounts, would that really make this process fail?
Click to expand...
Click to collapse
I doubt Odin cares what accounts you do or don't use. Shouldn't have any effect.
I'm not a fan of the T-Mo branding either. The all-pink screen splash is obnoxious.
Sounds like the problem is the internal memory partitions are slightly different between the generic image and the T-Mo image and it doesn't lime that.
So you think for this I will need to factory reset. Do I just select re-partition in odin and then select CSC file instead of HOME_CSC file?
And is there any risk of tripping the efuse or setting the warranty void status to 1?
In the meantime I tried the *#272*IMEI# and this is just such a mess. When I set it to XAS the phone thinks it is Sprint phone and tries and fails to activate. When I set it to XAA then that doesn't happen but it refuses to make VoLTE call and calls over CDMA do not connect for some reason. I am using Verizon SIM card BTW. Also in XAA T-Mobile 5G does not work.
But now it is stuck on XAA *#272*IMEI# does not bring up the menu!
digitalcandy said:
I have the T-Mobile version A71 5g, model # SM-A716U. I can't stand the T-Mobile branding, especially the jingle on startup.I am trying to flash the generic firmware XAS-A716USQU1ATFB-20200713085932 with odin and it fails every time with a message on the phone.
Click to expand...
Click to collapse
Where are you finding generic (unlocked) firmware?
I've looked on SamMobile & couldn't find anything for the SM-A716U.
As best I can tell, there is no unlocked version of this firmware nor does Samsung even offer an unlocked version of the phone itself.
I don't know, this is all very confusing. Some random websites say XAS is generic firmware, other random site say XAS is Sprint. And then they show a BST firmware too but nobody tries to guess what carrier that is for.
In any case if I used the *#272*IMEI# menu to switch it to XAA and now Verizon VoLTE doesn't work and T-Mobile 5G doesn't work what can I do to revert back to stock since the *#272*IMEI# menu will no longer show up?
digitalcandy said:
I don't know, this is all very confusing. Some random websites say XAS is generic firmware, other random site say XAS is Sprint. And then they show a BST firmware too but nobody tries to guess what carrier that is for.
In any case if I used the *#272*IMEI# menu to switch it to XAA and now Verizon VoLTE doesn't work and T-Mobile 5G doesn't work what can I do to revert back to stock since the *#272*IMEI# menu will no longer show up?
Click to expand...
Click to collapse
Have you tried using Samsung's Smart Switch desktop tool to restore your phone back to stock?
https://www.samsung.com/us/support/owners/app/smart-switch/
Smart switch doesn't give me any option. The old version says this phone is not supported for recovery.
And now I can't even get the phone back to download mode
I am also looking for a way to update my A71 5g to Android 11 and OneUI 3.
I have the model number SM-A716U, the AT&T variant that is network unlocked and on Metro-by-Tmobile.
I have been looking for a way to update the phone but I only found the firmware for model SM-A716U1 which is the unlocked variant.
I don't want to take the chance of bricking the phone.
But the firmware is from AT&T but the model number is different.
There is an update for the right model number but it can't be downloaded anywhere.
Smart Switch also doesn't recognize that there is an update.
I guess I am just stuck with Android 10 and OneUI 2.5
(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
See Post #2 and #3 for the Links to the FirmwareAll 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
Spoiler: Understanding Firmware naming
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)
Spoiler: What are the Files in the Firmware Package:
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.
S908U - 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/VZWS908USQU1AVA6 - ATT/CCT/CHA/TMB/USC/VZW - Thanks to @hyelton for the MirrorOdin3_v3.13.3b Patched: HEREOdin3_v3.14.4 Patched: HERE
S908U1 - Unlocked VersionsBootloader 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 onS908U1UES2AVI5S908U1UEU2AVE4S908U1UEU2AVDC13/OneUI 5.0 BETA -BETA1 S908U1UEU2ZVH4 (AFH) and a MIRROR (Faster) Thanks @lexcynYou 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 1S908U1UEU1AVCKS908U1UEU1AVC8S908U1UEU1AVA6 - Thanks to 66880]@southern87 for the MIRROROdin3_v3.13.3b Patched: HEREOdin3_v3.14.4 Patched: HERE
Thank you. I purchased the unlocked 1TB version, and I'm sure I'll need this to get it working correctly on the AT&T network. (...more specifically - I need wifi calling to work on this unlocked unit)
kangi26 said:
Adding a thread for the S22 Ultra SM-S908U and S22 Ultra SM-S908U1 versions Firmware with links as they start to roll out
Click to expand...
Click to collapse
On board
baddison said:
Thank you. I purchased the unlocked 1TB version, and I'm sure I'll need this to get it working correctly on the AT&T network. (...more specifically - I need wifi calling to work on this unlocked unit)
Click to expand...
Click to collapse
My ATT Note 20Ultra is on U1 firmware and has Wi-Fi calling, I'm going to do the bad thing and assume this one will behave the same
kangi26 said:
My ATT Note 20Ultra is on U1 firmware and has Wi-Fi calling, I'm going to do the bad thing and assume this one will behave the same
Click to expand...
Click to collapse
Yup! Mine too. Maybe we'll have to do the same thing with the 22 Ultra...
Anyone know if eSim will be available on launch? It took more than a year for Note 20 Ultra to get the update.
I don't know. I think we'll all find out together
I can confirm Esim is available along with Sim Manager on all 3 US S22 versions
I'm thinking ahead and trying to picture how easily my t-mobile e-sim account will transfer from my N20 Ultra to the S22 Ultra. I figure since they're both t-mobile U variants they should easily make the transition between each other..... Right?
Well well well...here we are again. I'm not starting off by beating up on Venom..he has been good to me over the years. I knew Kangi would be at it again. Good to see the usual peeps here. Just dropping in to say whats up.
butchieboy said:
Well well well...here we are again. I'm not starting off by beating up on Venom..he has been good to me over the years. I knew Kangi would be at it again. Good to see the usual peeps here. Just dropping in to say whats up.
Click to expand...
Click to collapse
My goodness don't say anything about ship dates..lol...the sensitive people on XDA do not like it.
butchieboy said:
My goodness don't say anything about ship dates..lol...the sensitive people on XDA do not like it.
Click to expand...
Click to collapse
That's rule number 1, never talk about shipping. Rule number 2 is never talk about shipping
What i mean is i said something about people making a shipping thread everytime a new device drops. Then said we all know when they will ship so why make a thread. You would think that I just punched a kitten..lol
I forget most don't understand my humor like you Kangi..and Venom
butchieboy said:
What i mean is i said something about people making a shipping thread everytime a new device drops. Then said we all know when they will ship so why make a thread. You would think that I just punched a kitten..lol
Click to expand...
Click to collapse
Hmmm, sounds like a new Olympic event......
Ohhhh crap...don't say that. Someone will see it and be like..DAMN! THEY PUNCHING P**** over there
Kittens man kittens