Hi all, (I previously asked this here.)
I have a carrier unlocked SM-G950U that was previously on T Mobile that I now have on Verizon, (long story, see below.) However, my device isn't updating, as seems to be the case for a lot of migrated SM-G950U(s). Of course, I want Android 9, and I also wouldn't mind getting rid of some of Verizon's bloatware. I was also fortunate enough to have received a research grant for some work in Italy, and I'd like to bring my phone along, (I'm a student.) So really, 3 reasons:
I want Android 9.
I don't want Verizon's bloatware.
I want to be able to switch carriers without the painful process of a carrier unlocked phone. (Ie., with the unlocked firmware my understanding is that I only need to restart my phone, as opposed to resetting my device, to switch carriers/SIMs in the carrier unlocked (ie., non-U1) device, (I think.))
I want to flash an SM-G950U1 ROM, but I'm not sure if this is still possible, (though according to here and here it was possible about 2 years ago, on different firmware/bootloaders.)
My plan is to do this:
Download this G950U1UEU5DSC1_XAA from updato. (I believe XAA is the unlocked region code. My device is already carrier unlocked.)
Flash with ODIN (3.12.3, as far as I know only making sure repartitioning is UNchecked.)
I have a Snapdragon device.
Will this brick my phone?
Alternatively, here says I can download any carrier version of G950USQU5DSC1 (except Verizon and Sprint,) flash it, and it will work. I think this only accomplishes my getting Android 9, however, as it is still a carrier branded ROM. (So I'd still have to deal with bloatware and (possibly) resetting my device to switch networks.)
Phone INFO (the app) lists:
Original CSC Code: [blank]
Firmware's CSC Code: XAA
Active CSC Code: VZW
Avaialble CSC Codes: [a bunch]
Bootloader Version: G950USQU5CRG3
CSC Version: G950UOTN5CRG3
Baseband Version: G950USQU5CRG3
Build Number: R16NW.G950USQU5CRG3
Long story of how I got a carrier unlocked (SM-G950U) and not unlocked (SM-G950U1) device:
I purchased my "new" device on Amazon through a third party about 3 months ago. I checked the model number and found SM-G950U, but a couple places online said that this was indeed a regular, unlocked S8. However, my device wouldn't update, and I could see that I was stuck on a mid July/August build of Android 8, (CRG3.) Now that the summer's getting closer, I need(ed) to make sure my device is going to work while in Italy, so I called Samsung to update it/make sure it would work. They told me my device was previously activated on T Mobile, unlocked, apparently refurbished and sold to me. I rechecked the Amazon listing and it was in fact listed as new. (It was alongside Amazon's own listing for the S8.) Unfortunately, after spending the second half of my day on support calls, I won't be able to return my device because it's been just over 3 months. Looks like my next best option is to update/maintain it myself.
staMerrill said:
Hi all, (I previously asked this here.)
I have a carrier unlocked SM-G950U that was previously on T Mobile that I now have on Verizon, (long story, see below.) However, my device isn't updating, as seems to be the case for a lot of migrated SM-G950U(s). Of course, I want Android 9, and I also wouldn't mind getting rid of some of Verizon's bloatware. I was also fortunate enough to have received a research grant for some work in Italy, and I'd like to bring my phone along, (I'm a student.) So really, 3 reasons:
I want Android 9.
I don't want Verizon's bloatware.
I want to be able to switch carriers without the painful process of a carrier unlocked phone. (Ie., with the unlocked firmware my understanding is that I only need to restart my phone, as opposed to resetting my device, to switch carriers/SIMs in the carrier unlocked (ie., non-U1) device, (I think.))
I want to flash an SM-G950U1 ROM, but I'm not sure if this is still possible, (though according to here and here it was possible about 2 years ago, on different firmware/bootloaders.)
My plan is to do this:
Download this G950U1UEU5DSC1_XAA from updato. (I believe XAA is the unlocked region code. My device is already carrier unlocked.)
Flash with ODIN (3.12.3, as far as I know only making sure repartitioning is UNchecked.)
I have a Snapdragon device.
Will this brick my phone?
Alternatively, here says I can download any carrier version of G950USQU5DSC1 (except Verizon and Sprint,) flash it, and it will work. I think this only accomplishes my getting Android 9, however, as it is still a carrier branded ROM. (So I'd still have to deal with bloatware and (possibly) resetting my device to switch networks.)
Phone INFO (the app) lists:
Original CSC Code: [blank]
Firmware's CSC Code: XAA
Active CSC Code: VZW
Avaialble CSC Codes: [a bunch]
Bootloader Version: G950USQU5CRG3
CSC Version: G950UOTN5CRG3
Baseband Version: G950USQU5CRG3
Build Number: R16NW.G950USQU5CRG3
Long story of how I got a carrier unlocked (SM-G950U) and not unlocked (SM-G950U1) device:
I purchased my "new" device on Amazon through a third party about 3 months ago. I checked the model number and found SM-G950U, but a couple places online said that this was indeed a regular, unlocked S8. However, my device wouldn't update, and I could see that I was stuck on a mid July/August build of Android 8, (CRG3.) Now that the summer's getting closer, I need(ed) to make sure my device is going to work while in Italy, so I called Samsung to update it/make sure it would work. They told me my device was previously activated on T Mobile, unlocked, apparently refurbished and sold to me. I rechecked the Amazon listing and it was in fact listed as new. (It was alongside Amazon's own listing for the S8.) Unfortunately, after spending the second half of my day on support calls, I won't be able to return my device because it's been just over 3 months. Looks like my next best option is to update/maintain it myself.
Click to expand...
Click to collapse
Lss yes you can. I don't know the exact. But it is nearly impossible to truly brick a u model. But everything you show looks good. I think you need the modded odin for unbranded but you can Google carrier switching s8 and it should lead you right back to xda
TheMadScientist said:
Lss yes you can. I don't know the exact. But it is nearly impossible to truly brick a u model. But everything you show looks good. I think you need the modded odin for unbranded but you can Google carrier switching s8 and it should lead you right back to xda
Click to expand...
Click to collapse
Thanks for the quick reply!
I'll try later today with the G950U1 firmware. I've finished downloading the T Mobile firmware recommended by the second thread, (G950USQU5DSC1,) in case anything goes wrong, (in which case it looks like this firmware will positively work.)
staMerrill said:
Thanks for the quick reply!
I'll try later today with the G950U1 firmware. I've finished downloading the T Mobile firmware recommended by the second thread, (G950USQU5DSC1,) in case anything goes wrong, (in which case it looks like this firmware will positively work.)
Click to expand...
Click to collapse
See here: https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473
Just download the G950U1 firmware from Updato (or using SamFirm or Frija) and use that instead of the firmware referenced in the linked instructions.
Hai Karate said:
See here: https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473
Just download the G950U1 firmware from Updato (or using SamFirm or Frija) and use that instead of the firmware referenced in the linked instructions.
Click to expand...
Click to collapse
So as a surprise to no one, this worked successfully.
Thanks for all the help!
Ultimately, I did have to deviate from the guide here, (the same one you linked and that I had above.) I needed to download a new patched version of ODIN, which I got here.
The process was:
Download PatcheD Odin
Launch PatcheD Odin
Put phone in Download Mode
Connect Phone to PC
Extract the G950U1UEU5DSC1_XAA firmware from updato. (The same link/URL as I have above.)
Browse to/find files in Odin and put them in the right places.
Start...
Wait a reasonable amount of time for the files to be downloaded to the device, and forever for it to actually update.
Profit, (and finish setting up the device, wondering how you're going to signin without your 2FA codes...)
So again, thank you everyone. If anyone comes across this thread in the future you have my steps.
Related
Hi folks,
So as in iPhone user, i've been following the latest Galaxy very closely and decided to take the plunge on Sunday!
Suffice to say, sat in front of me at the moment is my first Samsung (I went for the Edge).
I'm on EE, so i'd like to know how I go about enabling Wi-Fi calling (and VoLTE when it launches - although i'm aware it's testing in several areas at the moment) on my device. I bought it unlocked, direct from Samsung - which probably explains why I can't see the settings for it?
I've ready that I may have to flash the firmware with the EE version to get the features - my concern with that though is tripping Knox, as i'd like to use Samsung Pay when it launches.
Is there a method of enabling the features without flashing the firmware?
Any help on this would be greatly appreciated!
I've ready that I may have to flash the firmware with the EE version to get the features - my concern with that though is tripping Knox, as i'd like to use Samsung Pay when it launches.
Is there a method of enabling the features without flashing the firmware
Click to expand...
Click to collapse
'''
i wouldnt if i were you. i tried that with apple pay in australia and it didnt work. its region locked. wait for the official launch.
for me, my ban offers nfc payments through the phone so i can wait abit for samsung pay to arrive in australia and if im lucky, they will give out free stuff like in america.
i never tried volte calling. but you can always use whats app and stuff.
Its safe to do so,
I bought my S7 Edge from the Samsung store, and flashed the EE firmware, it doesn't trip knox, only custom changes will trip knox, So rooting/custom recoveries and such. its safe to flash the EE firmware. and WI-FI calling working for me, (How to enable WiFI calling). as we speak. But I did do a factory reset(delete everything) after flashing to make sure the CSC for EE was installing correctly.
kossiewossie said:
Its safe to do so,
I bought my S7 Edge from the Samsung store, and flashed the EE firmware, it doesn't trip knox, only custom changes will trip knox, So rooting/custom recoveries and such. its safe to flash the EE firmware. and WI-FI calling working for me as we speak. But I did do a factory reset after flashing to make sure the CSC for EE was installing correctly.
Click to expand...
Click to collapse
Ah - just what I wanted to hear
Can you tell me if the EE firmware comes with loads of bloat? Also, will OTA updates work, or will I have to manually flash them when released (I'm sure I read that auto-updates don't work if flashing a different firmware - although I could have misconstrued that).
Thanks
Captain.Slow said:
Ah - just what I wanted to hear
Can you tell me if the EE firmware comes with loads of bloat? Also, will OTA updates work, or will I have to manually flash them when released (I'm sure I read that auto-updates don't work if flashing a different firmware - although I could have misconstrued that).
Thanks
Click to expand...
Click to collapse
Auto-update will work, but you will have to wait for EE to push the updates out. so might be a delay until they release them, Only difference from buying the phone from EE or Samsung is the firmware, So if you flash the whole phone and factory reset in recovery, its pretty much a EE phone. be warned sometimes WiFi calling will not work until you call up EE and ask them to activate it on your handset, (and that can be a funny conversation, since you didn't buy the phone from them but I managed to talk my way around it on my S6 edge+), And on my S7 Edge it seems to already be enabled after I flashed the EE firmware and enabled in the phone settings.
It's a shame that we still have to install carrier specific firmware to access these things. I thought I heard samsung had overcome this?
Some articles suggested that the S7 could install carrier specific software upon detection of SIM accordingly. This doesn't appear to be the case. I have just had to flash H3G firmware. BTW op it didn't trip KNOX
sammyelrefee said:
It's a shame that we still have to install carrier specific firmware to access these things. I thought I heard samsung had overcome this?
Some articles suggested that the S7 could install carrier specific software upon detection of SIM accordingly. This doesn't appear to be the case. I have just had to flash H3G firmware. BTW op it didn't trip KNOX
Click to expand...
Click to collapse
It is a bit rubbish really - it's one good thing Apple has over android imho. I know Google are trying to go down the same route with Carrier Updates - but they're gonna have to grow a pair if they're going to get anywhere with it.
Anyway, thanks kossiewossie - just finished flashing mine. Hoping I haven't tripped Knox (not checked yet, it's restoring my Google Account backup).
To flash the firmware is it just a case of downloading the EE firmware from sammobile and using Odin to flash it? Because I know for the S6 there was an issue where the partitions were different between the EE version and the unlocked version meaning you had to get hold of a PIT file to flash the EE firmware. Is that still the case?
I'm also considering doing the same. I'm on EE but it came through a re-seller so I've got stock Samsung firmware.
Other than the delay in updates being released, is there any other reason why not to do this? Are you able to flash back the BTU version if you grow tired of waiting for carrier updates and don't end up making the use of wifi calling?
mmotti said:
I'm also considering doing the same. I'm on EE but it came through a re-seller so I've got stock Samsung firmware.
Other than the delay in updates being released, is there any other reason why not to do this? Are you able to flash back the BTU version if you grow tired of waiting for carrier updates and don't end up making the use of wifi calling?
Click to expand...
Click to collapse
The only benefit I see with the EE firmware is Wifi calling, but as I am in a fantastic reception area, I do not need it. Therefore I see no other reason to use the EE firmware and prefer updates as soon as they are released.
Yes, if you grow tired of waiting for carrier updates, you can flash back to BTE/XEU firmware.
I can't speak for EVR firmware. I used Samfirm to download 4 file H3G firmware and I was not asked for a PIT file.
Interesting there are PIT files included in the files if you unpack them so maybe this was used?
Having downloaded the EE firmware I'm a little confused with Odin.
I have:
AP...
BL...
CP...
CSC_EVR...
Home_CSC_EVR...
Do I need to select all of these within Odin? If so, which CSC as there seems to be two? Sorry if this is a stupid question....
mmotti said:
Having downloaded the EE firmware I'm a little confused with Odin.
I have:
AP...
BL...
CP...
CSC_EVR...
Home_CSC_EVR...
Do I need to select all of these within Odin? If so, which CSC as there seems to be two? Sorry if this is a stupid question....
Click to expand...
Click to collapse
When I did it last night, within Odin I selected files for AP, BL, CP and for CSC - CSC_EVR. I didn't use the Home_CSC_EVR file.
Knowing my luck, i've probably done it wrong - although my phone does seem to be running fine!!
I'm too cautious about flashing the wrong one lol. I'll wait until we know the difference I think!
Edit: Flashed it with the standard CSC. All seems well.
I flashed the standard csc myself and all seems well for over a day now. Would still like to know what the home csc file is for.
Edit. Just found out that home_csc doesn't contain the pit file so it doesn't wipe the phone. So would have to use the standard CSC when changing firmware.
Hey there, hope y'all are doing well.
I recently purchased a Samsung Galaxy S7 SM-G930V, Nougat 7.0 (note: I live in europe, and it's an unlocked phone). I want to get rid of Verizon logo while booting and all the unnecessary apps connected with Verizon. Plus, as you know Verizon locks some functions like the device maintenance, turning off the backlight of the capacitive buttons, etc, etc.
So, I'd like to have a clean/untouched samsung firmware without any useless apps.
Is androidfilehost.com trustworthy? what about updato.com? (the latter had slow dl speed, and I stumbled upon the first alternative)
PS. by the way, mine reads G930VVRS4BQI1, so one thing that confused me was while loking up for files to download; should I get the G930VVRS4BQI1 which may be the only compatible file for my phone, or do I already have G930VVRS4BQI1, so downloading it would be useless?
Since I wouldn't like to tinker often with the phone system, what do you suggest, flashing or rooting?
Is there any guide for my case for flashing?
I noticed these two on the front page:
---[Rom] [Ufirm_QD2_Hybrid_Nougat_Rom_FlashFire_Install][Status Official For VZW S7FLAT]Last edited by CVertigo1; 25th September 2017
---[Rom] [Verizon_TMO_Hybrid_Nougat_Rom_FlashFire_Install][Status Official] [S7flat]Last edited by CVertigo1; 26th May 2017 at 03:13 PM.
which should I pick?
and since the posts were last edited in may and september, where can I find the latest firmware?
and after doing all this, will everything work well, will I get OTA updates?
I would really appreciate someone helping me out, whenever you're free.
Thanks in advance
You can actually cross flash any Qualcomm s7 firmware between all carrier handsets. With your case being in Europe I would recommend the sm-G930U firmware. Which is the carrier unlocked variant of the S7 stateside that has all bands unlocked that the modem is capable of. You will recieve OTA's. It's Odin files are on Updato and SamMobile. AndroidHost is trustworthy.
In your case of not wanting to tinker or have a "need to have" rooted feature on the new device, I would flash the the 930U firmware and enjoy your new non branded system.
JediDru said:
You can actually cross flash any Qualcomm s7 firmware between all carrier handsets. With your case being in Europe I would recommend the sm-G930U firmware. Which is the carrier unlocked variant of the S7 stateside that has all bands unlocked that the modem is capable of. You will recieve OTA's. It's Odin files are on Updato and SamMobile. AndroidHost is trustworthy.
In your case of not wanting to tinker or have a "need to have" rooted feature on the new device, I would flash the the 930U firmware and enjoy your new non branded system.
Click to expand...
Click to collapse
Hey JediDru,
I also just bought the S7 Verizon variant, and am planning on using it on MetroPCS. Would you recommend the 930U firmware for me as well? I wouldn't mind getting rid of the Verizon bloat before I hand it over to my wife...
jbjcurly said:
Hey JediDru,
I also just bought the S7 Verizon variant, and am planning on using it on MetroPCS. Would you recommend the 930U firmware for me as well? I wouldn't mind getting rid of the Verizon bloat before I hand it over to my wife...
Click to expand...
Click to collapse
You very well could. I think there is a thread around here specifically about metropcs setup somewhere between the verizon s7 and tmobile s7 forums. I use my 930v flashed to 930U on tmobile.
JediDru said:
You can actually cross flash any Qualcomm s7 firmware between all carrier handsets. With your case being in Europe I would recommend the sm-G930U firmware. Which is the carrier unlocked variant of the S7 stateside that has all bands unlocked that the modem is capable of. You will recieve OTA's. It's Odin files are on Updato and SamMobile. AndroidHost is trustworthy.
In your case of not wanting to tinker or have a "need to have" rooted feature on the new device, I would flash the the 930U firmware and enjoy your new non branded system.
Click to expand...
Click to collapse
hey there, thanks for your advice! I downloaded the latest file from here. sammobile"dot"com/firmwares/galaxy-s7/SM-G930U/VZW/
In a moment I was clueless at the "pick country" since there were more than one USA options. so I went with verizon, since my phone comes from verizon.
In the link I mentioned above it reads this This is for SM-G930U from USA (Verizon) which makes no sense to me, how it can be both "U"-unlocked and verizon at the same time... but, oh well, I flashed it 4 days ago and I've encountered no problem, which is all that matters! Hope I made no mistake at picking that file.
Recently purchased galaxy S7 SMG-930V (Best buy version) from a private owner.
I am on cricket and on APN setup LTE and MMS works without issues. Only issue is that upon dialing USSD code i get 'Connection problem or Invalid MMI code' . I tried all options available mentioned in this forum still doesn't work. Which version of SM-G930U should i flash? Main reason i purchased the phone is for Samusing Pay. Don't want to brick or lose Samusing Pay option after flash.
Inputs are appreciated.
thricegreat said:
hey there, thanks for your advice! I downloaded the latest file from here. sammobile"dot"com/firmwares/galaxy-s7/SM-G930U/VZW/
In a moment I was clueless at the "pick country" since there were more than one USA options. so I went with verizon, since my phone comes from verizon.
In the link I mentioned above it reads this This is for SM-G930U from USA (Verizon) which makes no sense to me, how it can be both "U"-unlocked and verizon at the same time... but, oh well, I flashed it 4 days ago and I've encountered no problem, which is all that matters! Hope I made no mistake at picking that file.
Click to expand...
Click to collapse
Did it remove all the bloatware from Verizon?
Does Samsung pay works?
matrixddl said:
Did it remove all the bloatware from Verizon?
Does Samsung pay works?
Click to expand...
Click to collapse
Yes Flashing the G930U firmware removes all carrier bloat.
Samsung pay comes with the U firmware.
The last time I was on the U I had bad standby drain. I read somewhere else it has to do with the U not dozing correctly. They may very well have fixed it now, I'm on the latest tmobile 4BRA firmware and it sleeps like a baby right now.
JediDru said:
Yes Flashing the G930U firmware removes all carrier bloat.
Samsung pay comes with the U firmware.
The last time I was on the U I had bad standby drain. I read somewhere else it has to do with the U not dozing correctly. They may very well have fixed it now, I'm on the latest tmobile 4BRA firmware and it sleeps like a baby right now.
Click to expand...
Click to collapse
Flashed the verizon U firmware and it did remove all the bloatware. Still need to check on battery drain with Samsung Pay. All other apps are in "Always Sleeping Apps" for better battery performance.
For future reference make sure before flashing new firmware google accounts and lock screen securities are removed/disabled.
Is there a way to back up apps with user data and home screen and reuse instead of installing all over again when a new firmaware is flashed. Spoiled by the root and titanium full back. That was so easy.
matrixddl said:
Flashed the verizon U firmware and it did remove all the bloatware. Still need to check on battery drain with Samsung Pay. All other apps are in "Always Sleeping Apps" for better battery performance.
For future reference make sure before flashing new firmware google accounts and lock screen securities are removed/disabled.
Is there a way to back up apps with user data and home screen and reuse instead of installing all over again when a new firmaware is flashed. Spoiled by the root and titanium full back. That was so easy.
Click to expand...
Click to collapse
As far as I know, no. It's not so bad. I had gotten into the habit of taking screen shots of my app drawer and redownloading. To think now I can just redownload the configuration of apps I had before is as good as it gets. I still just redownload. I like to re-set everything back up just so I know its done.
I haven't tried this method but to backup and restore all installed apps check this Link.
matrixddl said:
I haven't tried this method but to backup and restore all installed apps check this Link.
Click to expand...
Click to collapse
Actually, if all you want to do is switch carriers (same GMail address), then a firmware swap will work.
I have an ex-Verizon (blacklisted IMEI - previous owner)S7 that I was moving to Tracfone (which uses both VZW and T-Mobile towers) - naturally, VZW was a non-starter; however, the UnCarrier was fine, so I used a T-Mobile nanoSIM (Tracfone triple-punch SIM kit includes SIMs from all except Sprint) and replaced the VZW firmware with T-M firmware (Prince Comsy ODIN does the track rather neatly). As long as your IMEI is not blacklisted from the TARGET, such a swap will always work.
Hi all,
I have an S10+ that refuses to acknowledge that its software is out of date.
I bought a US Cellular Galaxy S10+ from the Samsung website when the phones launched in March 2019. In late August 2019, I decided to switch to AT&T (had previously been on my parents' plan, wanted to start my own). I transferred the phone and my number over to AT&T.
Recently, I noticed that I have not received a software update or security update since before I switched. My Android version is still 9, my kernel is dated Aug 7, 2019, and my security patch level is Aug 1, 2019.
No matter what I do, my phone says its software is up to date.
I took the following actions:
Called AT&T to have them update the phone in their servers or whatever it is they do.
Changed the date in the phone, restarted and searched for updates.
Cleared the cache data in the phone's BIOS.
Tried using Smart Switch, it said it was up to date.
Did a factory reset of my phone.
Contacted Samsung, was told to talk to my carrier.
Called AT&T again, was told they could not push the updates because the IMEI number is for a US Cellular phone, not an AT&T phone.
Today, I took it to a Samsung representative at a local Best Buy. He plugged the phone in to whatever PC tool he has, it prompted him to download the latest AT&T firmware. He did so and tried flashing the phone. I looked and saw the blue BIOS screen where the phone said it was downloading the firmware. However, when it finished and he started the phone up again, the phone's software information was unchanged. He tried it a second time, and still no change. He told me he had never seen a phone refuse the firmware like this, and he said there was nothing he else he could think of to try. He said even if I could flash the firmware, it might still refuse to receive updates and I'd have to keep flashing it to get all the updates. His suggestion was to just wait and try to see if I could get a deal on an S20.
This phone is paid off, and still in great condition. I'd really rather not have to replace it less than a year after I got it. I've thought about trying to flash the phone myself with Odin, but I'm not sure whether I need to try it with AT&T firmware or US Cellular firmware. Furthermore, I can't find AT&T firmware for the SM-G975U, only the SM-G975U1, and I'm not even sure if it's up to date. What are your suggestions?
You could try updating using the Frija & Odin method found in News & Discussion board, then see if next month you receive OTA?
RuthlessNate said:
Hi all,
I have an S10+ that refuses to acknowledge that its software is out of date.
I bought a US Cellular Galaxy S10+ from the Samsung website when the phones launched in March 2019. In late August 2019, I decided to switch to AT&T (had previously been on my parents' plan, wanted to start my own). I transferred the phone and my number over to AT&T.
Recently, I noticed that I have not received a software update or security update since before I switched. My Android version is still 9, my kernel is dated Aug 7, 2019, and my security patch level is Aug 1, 2019.
No matter what I do, my phone says its software is up to date.
I took the following actions:
Called AT&T to have them update the phone in their servers or whatever it is they do.
Changed the date in the phone, restarted and searched for updates.
Cleared the cache data in the phone's BIOS.
Tried using Smart Switch, it said it was up to date.
Did a factory reset of my phone.
Contacted Samsung, was told to talk to my carrier.
Called AT&T again, was told they could not push the updates because the IMEI number is for a US Cellular phone, not an AT&T phone.
Today, I took it to a Samsung representative at a local Best Buy. He plugged the phone in to whatever PC tool he has, it prompted him to download the latest AT&T firmware. He did so and tried flashing the phone. I looked and saw the blue BIOS screen where the phone said it was downloading the firmware. However, when it finished and he started the phone up again, the phone's software information was unchanged. He tried it a second time, and still no change. He told me he had never seen a phone refuse the firmware like this, and he said there was nothing he else he could think of to try. He said even if I could flash the firmware, it might still refuse to receive updates and I'd have to keep flashing it to get all the updates. His suggestion was to just wait and try to see if I could get a deal on an S20.
This phone is paid off, and still in great condition. I'd really rather not have to replace it less than a year after I got it. I've thought about trying to flash the phone myself with Odin, but I'm not sure whether I need to try it with AT&T firmware or US Cellular firmware. Furthermore, I can't find AT&T firmware for the SM-G975U, only the SM-G975U1, and I'm not even sure if it's up to date. What are your suggestions?
Click to expand...
Click to collapse
Settings > About > Software Information > Service Provider SW Ver
What does it show for you over there?
Your phone is probably still on the US Cellular CSC.
I'd recommend flashing the G975U1 ATT firmware if you want ATT features, or the XAA firmware, to convert your device to a completely unbranded variant with no carrier apps.
You can use SamFirm or Frija to get the firmwares.
Use 'SM-G975U1' as the model and for the CSC, use 'ATT' if you want the AT&T firmware, or 'XAA' if you want the unbranded firmware.
Flash it with patched Odin here:
https://androidfilehost.com/?fid=6006931924117912211
You will have to wipe/reset the entire phone with this process, so make sure to use Smart Switch to backup your data.
MeltdownSpectre said:
Settings > About > Software Information > Service Provider SW Ver
What does it show for you over there?
Your phone is probably still on the US Cellular CSC.
I'd recommend flashing the G975U1 ATT firmware if you want ATT features, or the XAA firmware, to convert your device to a completely unbranded variant with no carrier apps.
You can use SamFirm or Frija to get the firmwares.
Use 'SM-G975U1' as the model and for the CSC, use 'ATT' if you want the AT&T firmware, or 'XAA' if you want the unbranded firmware.
Flash it with patched Odin here:
https://androidfilehost.com/?fid=6006931924117912211
You will have to wipe/reset the entire phone with this process, so make sure to use Smart Switch to backup your data.
Click to expand...
Click to collapse
Hey, thanks for the advice.
My service provider software information version is:
SAOMC_SM-G975U_OYN_ATT_PP_0039
R58M20FYAKW
ATT/ATT/USC
I've looked at both Frija and SamFirm/Updato. Frija doesn't seem to recognize ATT or OYN as a CSC for me when I try using it in the auto search for either SM-G975U or SM-G975U1. Updato has an AT&T firmware, but it's from Nov 2019 and is still Android 9. SamMobile claims to have more up to date firmware, but their download links always send me to the registration page, even after I already registered (I'm guessing they're not as free as they claim to be).
RuthlessNate said:
Hey, thanks for the advice.
My service provider software information version is:
SAOMC_SM-G975U_OYN_ATT_PP_0039
R58M20FYAKW
ATT/ATT/USC
I've looked at both Frija and SamFirm/Updato. Frija doesn't seem to recognize ATT or OYN as a CSC for me when I try using it in the auto search for either SM-G975U or SM-G975U1. Updato has an AT&T firmware, but it's from Nov 2019 and is still Android 9. SamMobile claims to have more up to date firmware, but their download links always send me to the registration page, even after I already registered (I'm guessing they're not as free as they claim to be).
Click to expand...
Click to collapse
Ah, it seems like your device has switched to the ATT CSC but remained on a US cellular build, resulting in there being no available update file on the ATT server.
Download the XAA unbranded G975U1 firmware with Frija.
I completely forgot that ATT doesn't host their firmware files on Samsung servers, instead it uses its own servers for updates.
Updato and SamMobile are both greedy and want you to pay for uncapped download speeds so I wouldn't recommend using them.
With patched Odin can change the csc? I have G977B and cannot change the csc.
DeXTeRrR said:
With patched Odin can change the csc? I have G977B and cannot change the csc.
Click to expand...
Click to collapse
Only applies to US variants when switching from G975U to G975U1.
It's 'patched' as it bypasses the model number check.
MeltdownSpectre said:
Only applies to US variants when switching from G975U to G975U1.
It's 'patched' as it bypasses the model number check.
Click to expand...
Click to collapse
Thank you.
It took me forever to find someone with this problem / solution.
I switched from Verizon to Xfinity Mobile and had not received a security patch since Oct '21 and was still on Android 11.
You'd think that this problem occurs often enough that support would know the solution.
Xfinity Mobile told me Samsung was responsible.
Samsung (Best Buy Geek Squad who is certified Samsung Service Center) said Xfinity Mobile is responsible but gave me the idea that the phone might be 'stuck' on Verizon so it can't pull the updates from Xfinity Mobile.
The build was from Verizon.
I installed the latest build from Xfinity Mobile (CHA) for this model phone (SM-G973U) so it now has Android 12 with Dec '22 security patch.
I'm guessing that the updates will work now but I won't find out for 3 months since the S10 is now on quarterly releases.
Thanks 2x.
Scott
For those who aren't already aware, G988U is the model number of all of the US carrier versions of the S20 Ultra. The G988U1 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. 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, 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=305574
U1 firmware: https://www.androidfilehost.com/?w=files&flid=305575
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 S20, 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, 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 SamFirm/Frija:
ATT = AT&T (not available via SamFirm/Frija)
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
SPR = Sprint
TMB = T-Mobile
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
Pre-release notes:
1. I do not have one of these and do not plan to acquire one, so I have no idea if anything can actually be flashed at this moment - I'm just providing the firmware. Like all other models, I'm assuming patched Odin is needed for this, but it wouldn't surprise me if a new version is needed for this specific device. There's only one way to know though, so as soon as someone gets their hands on one and can try this, please let us know.
2. I don't know if using the HOME CSC will actually save data. I don't get access to that file straight from the source - I have to decompile the regular CSC, remove the parts that initiate the factory reset, and then re-compile it. Based on the S10 and Note 10, I've done what I think will avoid a factory reset. But the S20 has some new partitions, so we won't know for sure until someone tests it. So if you're willing to be that guinea pig, you're responsible for taking proper steps to avoid an FRP lock, make sure your data is backed up, etc
I will be the first to try. I ordered the unlocked. I will flash the TMO firmware. I have it downloaded already
Sent from my SM-G975U1 using Tapatalk
Thanks for posting these! I ordered the Verizon model but am planning on flashing the unlocked firmware once I get it in hand.
Sent from my SM-N975U using Tapatalk
at this point can we only flash the Userdata for the carrier without the actual firmware?
daraj said:
at this point can we only flash the Userdata for the carrier without the actual firmware?
Click to expand...
Click to collapse
I guess you could flash USERDATA by itself. There's really no point to doing that though
No the firmware is there. Its a separate file zipped up
Sent from my SM-G975U1 using Tapatalk
Is it possible to flash Canada firmware to the us variant or is that not advised ?
roadcabe14 said:
Is it possible to flash Canada firmware to the us variant or is that not advised ?
Click to expand...
Click to collapse
Canadian firmware has been able to be flashed to US Samsung flagship phones ever since the S7. So yes, I would assume that that trend will continue with the S20
Samfirm and Frija have TBN firmware available...I assume based on the naming that it's newer than the ones you have uploaded? I also saw on Sammobile that Verizon has already released a newer firmware which is odd considering they haven't even shipped them yet...lol
tlbland0426 said:
Samfirm and Frija have TBN firmware available...I assume based on the naming that it's newer than the ones you have uploaded? I also saw on Sammobile that Verizon has already released a newer firmware which is odd considering they haven't even shipped them yet...lol
Click to expand...
Click to collapse
1. SamFirm and Frija will always only give you whatever the newest/latest version is. So if it's not the same version that I have uploaded, then yes, it's a newer one.
2. Not odd at all. Most devices get an OTA before release to fix bugs, add features, etc. There was an OTA that came out shortly after I got access to the files, so TBN would be the 3rd release now for this model
3. Looks like firmware has now hit SamFirm and Frija for all S20 models, for anyone who wants to download it themselves
Tried flashing multiple times ATT FW with Odin 3.14.1. Odin reports no errors but it's definitely not taking. SW info still reports XAA and I have no "carrier bloat".
Its not as simple as that. There is a trick when going from unlocked to carrier fw. Look on s10 forums, the procedure is there I believe
Sent from my SM-G975U1 using Tapatalk
johnwayne27 said:
Its not as simple as that. There is a trick when going from unlocked to carrier fw. Look on s10 forums, the procedure is there I believe
Sent from my SM-G975U1 using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s10/help/samsung-s10-unlocked-phone-att-firmware-t3912973
this thread? pretty much the same process. if you don't mind linking me i'm working on trying to get this done proper and won't sleep until then lol
Ive been there done that. Timing is everything. Gotta reset dorectly after boot and flash and when i see carrier update prompt-you know its right. Trial and error.
Sent from my SM-G975U1 using Tapatalk
johnwayne27 said:
Ive been there done that. Timing is everything. Gotta reset dorectly after boot and flash and when i see carrier update prompt-you know its right. Trial and error.
Sent from my SM-G975U1 using Tapatalk
Click to expand...
Click to collapse
TY. Tried again this morning and got it. I assumed I did not need to flash U1 first since my phone was already unlocked. Doing that made all the difference. New to all of this but glad it's finally done!
johnwayne27 said:
Its not as simple as that. There is a trick when going from unlocked to carrier fw. Look on s10 forums, the procedure is there I believe
Sent from my SM-G975U1 using Tapatalk
Click to expand...
Click to collapse
Procedure is also given right here, in the OP
Will flashing the att firmware to an unlocked phone enable wifi calling?
Murph2k said:
Will flashing the att firmware to an unlocked phone enable wifi calling?
Click to expand...
Click to collapse
My other threads are chock full of discussions of this exact thing. Bottom line is, we don't know until someone tries it
I'm trying to download the Tmobile from the SamFirm tool for my S20 ultra SM-G988U1
I put in the model number above and TMB in the region.
But I also noticed that if I enter any other region, it's the same filename and size as well. Just want to make sure about downloading the right file.
I re-read the OP, and saw some youtube videos. It's my assumption now that I need to put SM-G988U in the MODEL and keep TMB as the region to download the correct firmware. Am I correct in assuming this is the correct way to go?
The reason I want to do this is because I want to have Tmobiles advance messaging feature back
For those who aren't already aware, G986U is the model number of all of the US carrier versions of the S20+. The G986U1 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. 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.
Happy flashing!
U firmware: https://www.androidfilehost.com/?w=files&flid=305579
U1 firmware: https://www.androidfilehost.com/?w=files&flid=305580
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 S20, 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, 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 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
Notes:
1. I do not have one of these and do not plan to acquire one, so I have no idea if anything can actually be flashed at this moment - I'm just providing the firmware. Like all other models, I'm assuming patched Odin is needed for this, but it wouldn't surprise me if a new version is needed for this specific device. There's only one way to know though, so as soon as someone gets their hands on one and can try this, please let us know
It's been confirmed that Odin 3.14.1 Patched is needed for flashing S20s - https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
H/T @clabern
2. I don't know if using the HOME CSC will actually save data. I don't get access to that file straight from the source - I have to decompile the regular CSC, remove the parts that initiate the factory reset, and then re-compile it. Based on the S10 and Note 10, I've done what I think will avoid a factory reset. But the S20 has some new partitions, so we won't know for sure until someone tests it. So if you're willing to be that guinea pig, you're responsible for taking proper steps to avoid an FRP lock, make sure your data is backed up, etc
What are TAW and TAY
Vats12 said:
What are TAW and TAY
Click to expand...
Click to collapse
That's explained in the OP
Odin fail
Couldn't get odin to work, probably needs an update, tried 3.14.4 and custom. either freezes at setupconnection, or says write failed.
iBowToAndroid said:
That's explained in the OP
Click to expand...
Click to collapse
I want to know who is TAW/TAY? like SPR is Sprint, VZW is Verizon...
I didn't find this information on the internet or maybe I am not searching with the right keyword.
luminaire117 said:
Couldn't get odin to work, probably needs an update, tried 3.14.4 and custom. either freezes at setupconnection, or says write failed.
Click to expand...
Click to collapse
Freezing at SetupConnection can be a USB issue. Try again with a different port, different cable, or different PC
Vats12 said:
I want to know who is TAW/TAY? like SPR is Sprint, VZW is Verizon...
I didn't find this information on the internet or maybe I am not searching with the right keyword.
Click to expand...
Click to collapse
TAW/TAY are not carrier CSC codes. As I already stated, the explanation for what TAW/TAY is is given in the OP
Just wanted to let folks know I had to use this patched Odin (3.14.1_3B) in order to flash unlocked (U1) firmware on my Verizon S20+. Pulled the most recent firmware from Sammobile and flashed it successfully.
clabern said:
Just wanted to let folks know I had to use this patched Odin (3.14.1_3B) in order to flash unlocked (U1) firmware on my Verizon S20+. Pulled the most recent firmware from Sammobile and flashed it successfully.
Click to expand...
Click to collapse
Sweet, good to know - thanks!
maybe i am misreading the OP but can the stock firmware be used to go from t-mobile to stock?
danon.brown said:
maybe i am misreading the OP but can the stock firmware be used to go from t-mobile to stock?
Click to expand...
Click to collapse
Yes, if by "stock" you mean "factory unlocked" aka U1.
clabern said:
Just wanted to let folks know I had to use this patched Odin (3.14.1_3B) in order to flash unlocked (U1) firmware on my Verizon S20+. Pulled the most recent firmware from Sammobile and flashed it successfully.
Click to expand...
Click to collapse
It has been a while since i looked into flashing. I want to do the same (have an s20+ verizon) I want factory unlocked software . On sam mobile , everything looks like it has a carrier attached even looking up U1 model. Which did you pick?
iHTC said:
It has been a while since i looked into flashing. I want to do the same (have an s20+ verizon) I want factory unlocked software . On sam mobile , everything looks like it has a carrier attached even looking up U1 model. Which did you pick?
Click to expand...
Click to collapse
You want product code "XAA". So it should be this one.
clabern said:
You want product code "XAA". So it should be this one.
Click to expand...
Click to collapse
that's what I figured. Any difference going to sam mobile vs the one in the original post here, I assume both are current this early on in the game. Thanks for your help!
iHTC said:
that's what I figured. Any difference going to sam mobile vs the one in the original post here, I assume both are current this early on in the game. Thanks for your help!
Click to expand...
Click to collapse
The one from Sammobile is more current, there was an update soon after launch. You can compare the build number to that of the software on your phone.
Anybody else flash the VZW userdata and still end up with Tmo branding, bloat, and boot animation?
finshan said:
Anybody else flash the VZW userdata and still end up with Tmo branding, bloat, and boot animation?
Click to expand...
Click to collapse
If you didn't follow the steps in the OP correctly, then yes, you can very possibly end up with the same bloat as before
Ok. So I guess the one place I'm struggling, from a not implemented, but understanding standpoint is that the instructions show how to go to carrier branded versions, but if I just want the U1 firmware, do I need to follow through with the other portion, the second flashing that happens, or can I just run the unbranded one?
halcyon77 said:
Ok. So I guess the one place I'm struggling, from a not implemented, but understanding standpoint is that the instructions show how to go to carrier branded versions, but if I just want the U1 firmware, do I need to follow through with the other portion, the second flashing that happens, or can I just run the unbranded one?
Click to expand...
Click to collapse
Just flash U1 - nothing else
Thank you for this. I was able to flash from Tmobile to the U1 firmware with a virtual machine.