Related
Hi, I got a S7 Edge SM-G935A from AT&T at the end of December.
That same night I tried to root my phone(i got a bootloop), and I didn't know the bootloader was locked.
So I re-flashed a SM-G935U rom, but I would like to go back to the basic one in order to get a new start(SM-G935A), without root and nothing.
Knowing that I have a problem connecting to the wifi, maybe because of the rom that doesn't match.
And also i dont have samsung updates, i'd like to have the latest one im currently on 7.0.
If someone could help me to get my phone with original firmware, I'd be grateful.
Ok, first off, you can run any US/Qualcomm variant software on your device. Unless you just have a hankering for AT&T firmware, the U firmware will work just fine. Either way, find a full copy of either A or U firmware and ODIN it down, and you will essentially factory reset your device in the process.
There are links to both in this forum. I personally prefer U because it is faster and less bogged down with carrier crap, but if you are an AT&T customer, there are decent enough reasons to stick with A.
NOTE: you may need to use Prince Comsy's ODIN tool if you get a mismatch error. Unfortunately, there is no universal ODIN tool, but as a general rule, if you are CHANGING variants you need Prince's. If you are writing over the same version, you need the official.
jshamlet said:
Ok, first off, you can run any US/Qualcomm variant software on your device. Unless you just have a hankering for AT&T firmware, the U firmware will work just fine. Either way, find a full copy of either A or U firmware and ODIN it down, and you will essentially factory reset your device in the process.
There are links to both in this forum. I personally prefer U because it is faster and less bogged down with carrier crap, but if you are an AT&T customer, there are decent enough reasons to stick with A.
NOTE: you may need to use Prince Comsy's ODIN tool if you get a mismatch error. Unfortunately, there is no universal ODIN tool, but as a general rule, if you are CHANGING variants you need Prince's. If you are writing over the same version, you need the official.
Click to expand...
Click to collapse
Im not living in the USA and AT&T doesnt exist where i live, but sometime i have a issue with my wifi "internet may not be available" is because of the rom?
Leqz said:
Im not living in the USA and AT&T doesnt exist where i live, but sometime i have a issue with my wifi "internet may not be available" is because of the rom?
Click to expand...
Click to collapse
Then this is easy. Go download the U firmware and use Prince's ODIN to convert it to a G935U. If you aren't on an AT&T network there is zero reason to keep your device on A firmware, starting with the fact that you will never get updates. (AT&T firmware will only update if you have an AT&T SIM installed.)
jshamlet said:
Then this is easy. Go download the U firmware and use Prince's ODIN to convert it to a G935U. If you aren't on an AT&T network there is zero reason to keep your device on A firmware, starting with the fact that you will never get updates. (AT&T firmware will only update if you have an AT&T SIM installed.)
Click to expand...
Click to collapse
Only add-on is to perform this from a Windows 7 pc and not 10. Prince kept crashing on 10 and worked fine on 7.
I know these are much tougher to find - can't be obtained from SamFirm or SamMobile. So I'll be uploading one for each bootloader version. Firmware is universal on U models so you can use the other 4 files from any other matching collection. Can probably even mix and match builds, if you can't find files for the exact same build. Can't mix and match bootloaders though, so the other 4 files have to at least be from the same bootloader.
USERDATAs for any other CSCs can be gotten from SamFirm - for the latest version. If you need an old USERDATA for a CSC that's not commonly found on SamMobile (ACG, LRA, TFN, etc), let me know and I can probably get it.
https://www.androidfilehost.com/?w=files&flid=283206
Can I use the userdata file for G55USQU5CRF5 with the other four files being from the build G55USQS5CRF5? I'm not sure what the difference between SQU and SQS is, and if it is significant. Thank you!
zeiguy17 said:
Can I use the userdata file for G55USQU5CRF5 with the other four files being from the build G55USQS5CRF5? I'm not sure what the difference between SQU and SQS is, and if it is significant. Thank you!
Click to expand...
Click to collapse
Yes, you can. There basically is no difference
I'm begging someone to help me. I flashed my AT&T S8+ to the G955U1 unlocked firmware, then got accepted into the beta and installed it via OTA update. I now want to go back to a AT&T rom so I can have stuff like Wi-fi calling and VOLTE back. I've tried so many different roms with ATT userdata and they all fail with ODIN. I'm guessing its something to do with bootloader version. Is there any way I can get back to a AT&T ROM from the G955U1 Pie beta firmware.
sean8102 said:
I'm begging someone to help me. I flashed my AT&T S8+ to the G955U1 unlocked firmware, then got accepted into the beta and installed it via OTA update. I now want to go back to a AT&T rom so I can have stuff like Wi-fi calling and VOLTE back. I've tried so many different roms with ATT userdata and they all fail with ODIN. I'm guessing its something to do with bootloader version. Is there any way I can get back to a AT&T ROM from the G955U1 Pie beta firmware.
Click to expand...
Click to collapse
Well the beta has to still be Bootloader 5, so just flash any 5 build
iBowToAndroid said:
Well the beta has to still be Bootloader 5, so just flash any 5 build
Click to expand...
Click to collapse
I finally managed to get Odin to flash a ROM. All of them I tried were bootloader 5. But now the problem is I cant get OTA updates. My phone is back to being a AT&T one with the AT&T boot screen and wi-fi calling etc etc. But everytime I check for updates it says its up to date even though I have CRL1 and the latest AT&T firmware is U5CSA4. I would update form SD card but that wipes the phone every time. I had to do that 4 or 5 times just to get to CRL1 because it kept saying my phone is up to date.
sean8102 said:
I finally managed to get Odin to flash a ROM. All of them I tried were bootloader 5. But now the problem is I cant get OTA updates. My phone is back to being a AT&T one with the AT&T boot screen and wi-fi calling etc etc. But everytime I check for updates it says its up to date even though I have CRL1 and the latest AT&T firmware is U5CSA4. I would update form SD card but that wipes the phone every time. I had to do that 4 or 5 times just to get to CRL1 because it kept saying my phone is up to date.
Click to expand...
Click to collapse
1. AT&T phones don't OTA if you're using a carrier other than AT&T - even their own MVNOs
2. If you are using AT&T, OTA rollouts are staged. It just came out less than a week ago, so your phone might not have been green-lit yet
3. Both 1 and 2 are really irrelevant anyways, because you can just Odin flash any update you want. Using HOME CSC will ensure data isn't wiped
iBowToAndroid said:
1. AT&T phones don't OTA if you're using a carrier other than AT&T - even their own MVNOs
2. If you are using AT&T, OTA rollouts are staged. It just came out less than a week ago, so your phone might not have been green-lit yet
3. Both 1 and 2 are really irrelevant anyways, because you can just Odin flash any update you want. Using HOME CSC will ensure data isn't wiped
Click to expand...
Click to collapse
I am using AT&T. I know rollouts are staged but I've never had it tell me my phone is up to date when it is 7 versions behind which it was because I had to start at CRF5 since that is the newest AT&T Userdata file I could find. I checked after doing the update from SD card method each time, making sure to put the date on my phone forward since AT&T only lets you manually check once a day. No matter what it said I was up to date despite being several versions behind.
I'm gonna try using Odin to flash one more time because not being able to do OTA update is a HUGE PIA. Dose it matter that the user data is called "ATT_G955USQU5CRF5" despite the firmware being USQS because I couldn't find a USQUCRF5 and besides AT&T's update history shows USQSCRF5 anyways. What I did was downloaded a verizon G955USQS5CRF5 ODIN file (because for some reason AT&T odin files are really hard to find) and replaced the Verizon user data with the AT&T one.
Also if I flash say CSA4 verizon with the verizon user data the put my AT&T sim card in it dose it not download all the the carrier bloatware and what not? dose that basically turn it back into a AT&T phone? or could I take that CSA4 and flash it with the CRF5 AT&T user data?
sean8102 said:
I am using AT&T. I know rollouts are staged but I've never had it tell me my phone is up to date when it is 7 versions behind which it was because I had to start at CRF5 since that is the newest AT&T Userdata file I could find. I checked after doing the update from SD card method each time, making sure to put the date on my phone forward since AT&T only lets you manually check once a day. No matter what it said I was up to date despite being several versions behind.
I'm gonna try using Odin to flash one more time because not being able to do OTA update is a HUGE PIA. Dose it matter that the user data is called "ATT_G955USQU5CRF5" despite the firmware being USQS because I couldn't find a USQSCRF5 and besides AT&T's update history shows USQSCRF5 anyways. What I did was downloaded a verizon G955USQS5CRF5 ODIN file and replaced the Verizon user data with the AT&T one.
Also if I flash say CSA4 verizon with the verizon user data the put my AT&T sim card in it dose it not download all the the carrier bloatware and what not? dose that basically turn it back into a AT&T phone? or could I take that CSA4 and flash it with the CRF5 AT&T user data?
Click to expand...
Click to collapse
1. I have no idea what the difference is between SQS and SQU. Even on the same network, it seems to be completely random as to which one gets assigned to each new update. I don't think it matters
2. Don't flash userdata if you're going to Odin flash a different carrier's version. Just do the normal 4 files
Sorry for the late reply. But just wanted to say that this method of getting from a G955U1 (US Unlocked) firmware back to AT&T branded firmware did end up working. I did eventually start getting OTA updates after using the method I mentioned (flashing Verizon USQS5CRF5 ROM files with AT&T G955USQS5CRF5 USERDATA file using ODIN Odin3 v3.13.1 3B Patched). Then updating to the then latest version using the update.zip method using files from the "Firmware Science" site (I think that's the name). Then about two days after AT&T released a new update I actually got it OTA. However after it installed successfully my chrome app became broken. Opening it and hitting the ... button in the top right would open the menu but all the options just said "chrome". Tried clearing the cache and files of Chrome but then it just crashed when launched. Had to do a reset (not a big deal since I had a Samsung SmartSwitch backup on my SD Card). Just hope that dose not happen every OTA, but guessing it was a weird fluke.
sean8102 said:
Sorry for the late reply. But just wanted to say that this method of getting from a G955U1 (US Unlocked) firmware back to AT&T branded firmware did end up working. I did eventually start getting OTA updates after using the method I mentioned (flashing Verizon USQS5CRF5 ROM files with AT&T G955USQS5CRF5 USERDATA file using ODIN Odin3 v3.13.1 3B Patched). Then updating to the then latest version using the update.zip method using files from the "Firmware Science" site (I think that's the name). Then about two days after AT&T released a new update I actually got it OTA. However after it installed successfully my chrome app became broken. Opening it and hitting the ... button in the top right would open the menu but all the options just said "chrome". Tried clearing the cache and files of Chrome but then it just crashed when launched. Had to do a reset (not a big deal since I had a Samsung SmartSwitch backup on my SD Card). Just hope that dose not happen every OTA, but guessing it was a weird fluke.
Click to expand...
Click to collapse
Hey I am in the same boat. Can you please help pointing to the files you used to ODIN to get back to ATT version.
SC1 USERDATA was added a few days ago, for anyone wanting to jump to Pie
USERDATA added for bootloader 6
USERDATA added for bootloader 7
Ive been researching and reading most of the day about returning to stock on an att 955u. The only download i can find that wont take 6 hours is from samfirm and is G955USQS7DSL2. Can i use this and the userdata from your link to return this back to stock?
jetracer said:
Ive been researching and reading most of the day about returning to stock on an att 955u. The only download i can find that wont take 6 hours is from samfirm and is G955USQS7DSL2. Can i use this and the userdata from your link to return this back to stock?
Click to expand...
Click to collapse
Since the USERDATA is TA5, I would recommend using a build that's closer to that one. You can get TA3 from SamFirm under regions/CSCs ACG, CCT, LRA, SPR, TFN, or VZW.
When you say "returning to stock", what firmware is currently on the device?
iBowToAndroid said:
Since the USERDATA is TA5, I would recommend using a build that's closer to that one. You can get TA3 from SamFirm under regions/CSCs ACG, CCT, LRA, SPR, TFN, or VZW.
When you say "returning to stock", what firmware is currently on the device?
Click to expand...
Click to collapse
I was on a verizon build. I ended up returning to stock with G955USQS6DSG4, got one update and now says no firmware. Currently shows G955USQU6DSH8.
SamMobile actually had pretty decent speed.
jetracer said:
I was on a verizon build. I ended up returning to stock with G955USQS6DSG4, got one update and now says no firmware. Currently shows G955USQU6DSH8.
SamMobile actually had pretty decent speed.
Click to expand...
Click to collapse
Do you have all of AT&T's apps and bloatware now? If so, it should be updating at least to SJ3, if not up to TA5. You would need an active AT&T SIM inserted in order to pull the update though
iBowToAndroid said:
Do you have all of AT&T's apps and bloatware now? If so, it should be updating at least to SJ3, if not up to TA5. You would need an active AT&T SIM inserted in order to pull the update though
Click to expand...
Click to collapse
Yea just uninstalled and disabled a bunch of att and samsung bloat. I am currently running an att sim. Should i possible download the v7 files and try again? Shouldn't matter that the firmware was from "tmobile" right its the userdata that counts iirc.
jetracer said:
Yea just uninstalled and disabled a bunch of att and samsung bloat. I am currently running an att sim. Should i possible download the v7 files and try again? Shouldn't matter that the firmware was from "tmobile" right its the userdata that counts iirc.
Click to expand...
Click to collapse
What do the 3 service provider codes show as, under Software Information?
When searching for a firmware for the phone I just bought on ebay none of the sites i have checked, including sammobile and updato.com, have the baseband version I have which is G975FXXAU1ASE5. I specifically bought this phone so that i could root it and when I checked all the bands that it has there are all except 1 for the tmobile network and I read that it should still work. I currently use metropcs so my question is which firmware can i use that is going to work with tmobile or metropcs and if i use one with a different baseband or csc will it affect if my phone works or not on the tmobile network. I am also in California in the US and all the firmwares are international so what should I use? My CSC is G975FOXM1ASE5 and I haven't seen any with the same CSC either
AlwaysPhresh said:
When searching for a firmware for the phone I just bought on ebay none of the sites i have checked, including sammobile and updato.com, have the baseband version I have which is G975FXXAU1ASE5. I specifically bought this phone so that i could root it and when I checked all the bands that it has there are all except 1 for the tmobile network and I read that it should still work. I currently use metropcs so my question is which firmware can i use that is going to work with tmobile or metropcs and if i use one with a different baseband or csc will it affect if my phone works or not on the tmobile network. I am also in California in the US and all the firmwares are international so what should I use? My CSC is G975FOXM1ASE5 and I haven't seen any with the same CSC either
Click to expand...
Click to collapse
You will be able to use on Tmobile. All of the carrier features are available excepted RCS messaging. You will also be missing some of the LTE bands, like 71. You can flash any of the 975F firmwares. OXM denotes multi csc firmware regions. Use Frida download tool instead of Sammobile or updato. It much faster - 4/5 minutes vs hours with those websites. AUT gets updates first, but you can choose the same one that is currently on your phone.
Cindysmith0994 said:
You will be able to use on Tmobile. All of the carrier features are available excepted RCS messaging. You will also be missing some of the LTE bands, like 71. You can flash any of the 975F firmwares. OXM denotes multi csc firmware regions. Use Frida download tool instead of Sammobile or updato. It much faster - 4/5 minutes vs hours with those websites. AUT gets updates first, but you can choose the same one that is currently on your phone.
Click to expand...
Click to collapse
I have Frija already and tried it last night with the auto setting and it didn't let me put OXM for a CSC. I tried to run it with MODEL- SM-975F and for the CSC I chose AUT with auto selected and it gives me an error that it cannot find a firmware. I read a comment from somebody with the same phone as I have on yt and somebody replied with a firmware from Nepal and it said OXM in the CSC would that have been compatible too?
AlwaysPhresh said:
I have Frija already and tried it last night with the auto setting and it didn't let me put OXM for a CSC. I tried to run it with MODEL- SM-975F and for the CSC I chose AUT with auto selected and it gives me an error that it cannot find a firmware. I read a comment from somebody with the same phone as I have on yt and somebody replied with a firmware from Nepal and it said OXM in the CSC would that have been compatible too?
Click to expand...
Click to collapse
You can't choose OXM. I just tried it with AUT, it works. The model needs to be SM-G975F.
Cindysmith0994 said:
You can't choose OXM. I just tried it with AUT, it works. The model needs to be SM-G975F.
Click to expand...
Click to collapse
I had SM-975F without the G before the 9 so it wasn't working thank you very much for replying and the help. The firmware that I am getting will work with Odin and rooting the phone with Magisk correct?
AlwaysPhresh said:
I had SM-975F without the G before the 9 so it wasn't working thank you very much for replying and the help. The firmware that I am getting will work with Odin and rooting the phone with Magisk correct?
Click to expand...
Click to collapse
Yes. Just follow the root instructions on the S10 forum.
Cindysmith0994 said:
Yes. Just follow the root instructions on the S10 forum.
Click to expand...
Click to collapse
I followed the instructions and now my phone won't boot and gives me a message saying the phone does not have samsung's official firmware and I used the firmware from Frija. It is not booting in any way.
AlwaysPhresh said:
I followed the instructions and now my phone won't boot and gives me a message saying the phone does not have samsung's official firmware and I used the firmware from Frija. It is not booting in any way.
Click to expand...
Click to collapse
Your bootloader is still locked. Reflash entire stock firmware [BL, AP, CP, CSC (not home_csc). It's much easier to follow the videos showing the process instead of following written posts if you're having issues.
Cindysmith0994 said:
Your bootloader is still locked. Reflash entire stock firmware [BL, AP, CP, CSC (not home_csc). It's much easier to follow the videos showing the process instead of following written posts if you're having issues.
Click to expand...
Click to collapse
My bootloader was unlocked fine already. I followed both of these videos https://www.youtube.com/watch?v=o3a8YnWT3yk&t=179s / https://www.youtube.com/watch?v=s2Xp-lQg1xs&t=612s
Both are pretty much the exact same all the way through. I flashed the patched tar from Magisk restarted the phone and held the vol up bixby power combo when it went black and then I went to wipe data factory reset then rebooted. After it booted i set up the phone the same and checked if magisk was there and it was not so i turned off the phone and when booting i did the vol up bixby and power and the screen stayed on the boot logo saying the this phone is not running samsung's official software and on the top a red line that said i can flash any official software and it stayed like that and after trying to just boot it with the power it gave the exact same message. Only difference from the video and what I did was the firmware I got was from frija while they got theirs from different methods like sammobile and samfirm
EDIT- I flashed the ap cp and csc not the bl file from the firmware i got off of frija and the phone booted up now. The phones bootloader is still unlocked and it boots up but there is no root.
AlwaysPhresh said:
My bootloader was unlocked fine already. I followed both of these videos https://www.youtube.com/watch?v=o3a8YnWT3yk&t=179s / https://www.youtube.com/watch?v=s2Xp-lQg1xs&t=612s
Both are pretty much the exact same all the way through. I flashed the patched tar from Magisk restarted the phone and held the vol up bixby power combo when it went black and then I went to wipe data factory reset then rebooted. After it booted i set up the phone the same and checked if magisk was there and it was not so i turned off the phone and when booting i did the vol up bixby and power and the screen stayed on the boot logo saying the this phone is not running samsung's official software and on the top a red line that said i can flash any official software and it stayed like that and after trying to just boot it with the power it gave the exact same message. Only difference from the video and what I did was the firmware I got was from frija while they got theirs from different methods like sammobile and samfirm
EDIT- I flashed the ap cp and csc not the bl file from the firmware i got off of frija and the phone booted up now. The phones bootloader is still unlocked and it boots up but there is no root.
Click to expand...
Click to collapse
If you flashed those files you should be back to stock. Start the process again. Try this video: https://m.youtube.com/watch?v=Mn4dTjxY89I
Also make sure your patched magisk file is not corrupted when transferred back to your PC.
If not, I'm out of suggestions...sorry.
For those who aren't already aware, G981U is the model number of all of the US carrier versions of the S20. The G981U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. A "U to U" or "U1 to U1" flash does not require a factory reset, but changing from one firmware to the other will require one. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.
Manual Odin flashing is designed for those who:
- want to manually update to a newer version of U firmware on their U device, either because they don't want to wait for their carrier's OTA or because OTAs aren't working on their device, or a different carrier got a new feature/patch before they did
- want to flash U1 firmware to their U device
- want to convert from U1 firmware to carrier U firmware
- want to convert from one carrier's U firmware (with all apps and bloatware) to a different carrier's U firmware (with all apps and bloatware)
For those who aren't already aware, anyone can now download firmware for almost any Samsung device any time that they want, via SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But they only provide whatever the latest/newest/current version is - nothing older. I pay for a subscription to a site that gets the official releases (usually) before they hit SamFirm/Frija, so that's where my files come from. However, I don't have unlimited bandwidth on the site, and it's also quite time consuming to download the files, zip them up, and upload them to AFH. And, I do threads like this for every single Sx and Note x model - so I won't be uploading every single version. The only full builds that I upload are ones where I get access to a new bootloader and/or Android version early, before they hit SamFirm/Frija.
This is not a "beginner's guide to Odin flashing" -type post/thread, so I won't list basic, step-by-step flashing instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware (or haven't done it in a long time), I recommend you consult one of those "beginner's" guides- there are tons of them here on XDA.
Happy flashing!
U firmware: https://www.androidfilehost.com/?w=files&flid=305577
U1 firmware: https://www.androidfilehost.com/?w=files&flid=305578
(Quebec tends to be the fastest download mirror, if it gives you that option)
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
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
So I flashed with Odin with my unlocked from Samsung U1 firmware to the T-Mobile U firmware because I wanted the advanced messaging. Only issue in the beginning was not using the patched Odin, but once I did, no problems.
Tools:
Downloaded from this previous thread, post #2, with Modified Odin and Samsung Drivers https://forum.xda-developers.com/s10-plus/how-to/sm-g975u-firmware-downloads-tmo-spr-att-t3908657
Since it's been awhile since I've done flashing or Odin, I followed this basic guide:
https://forum.xda-developers.com/s10-plus/how-to/guide-g975f-flashing-megathread-faqs-t3936704
Of note, only needed the files from the TAW folder only, did not need the T-Mobile specific U firmware as resetting the phone with a T-mobile sim automatically loaded it.
My quick rundown:
1)Extract the G981U_TAW firmware file you just downloaded. You should get 5 files:
AP (System & Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_OXM (OXM CSC file, will wipe your phone)
HOME_CSC_OXM (OXM CSC file, will NOT wipe your phone)
2.)In Modified Odin I added each file to it's respective slot EXCEPT for HOME_CSC as I wanted to do a clean factory reset
3) Put the S20 in Download/ Odin mode. 2 different ways as outlined here https://www.youtube.com/watch?v=ZPSWEL6-gWg&t=8s
4) Once the phone was detected in the COM port number in Odin, I clicked the start button and waited til Odin said "PASS". One thing I noticed was the phone didn't reboot all the way automatically, it actually went into recovery mode and I ended up having to do a factory reset through there because at first it would bootloop and take me back into recovery mode, but after doing a factory reset in recovery mode it restarted just fine with the T-mobile firmware along with the t-mobile apps and advanced messaging working as it should be.
I want to flash my unlocked samsung s20 so I can use the ATT Volte and wifi calling but will rom eventually get released
jameslee2 said:
I want to flash my unlocked samsung s20 so I can use the ATT Volte and wifi calling but will rom eventually get released
Click to expand...
Click to collapse
If you're saying that you want AT&T apps and bloatware and features, then all the files that you need are already linked in the OP
I'm worried that I already know the answer, but i'm asking it anyways. I'm currently on a SM-G981N (South Korean version), which is a Snapdragon865 phone. I'm wondering if I can change my firmware to the SM-G981U version to get rid of the bloatware on my phone. For what I read for other phone's this wouldn't work. Perhaps I should start looking for an unbloated SM-G981N rom? Thanks!
tijsva said:
I'm worried that I already know the answer, but i'm asking it anyways. I'm currently on a SM-G981N (South Korean version), which is a Snapdragon865 phone. I'm wondering if I can change my firmware to the SM-G981U version to get rid of the bloatware on my phone. For what I read for other phone's this wouldn't work. Perhaps I should start looking for an unbloated SM-G981N rom? Thanks!
Click to expand...
Click to collapse
I'm assuming the flash would fail. But there's only one way to know for sure
I'll first try an unbloated korean firmware, until I'll find out if crossflashing between different region phones is safe and working...
tijsva said:
I'll first try an unbloated korean firmware, until I'll find out if crossflashing between different region phones is safe and working...
Click to expand...
Click to collapse
Is the a recovery for sm-g981u?
Sent from my SM-G981U using Tapatalk
Bee101 said:
Is the a recovery for sm-g981u?
Sent from my SM-G981U using Tapatalk
Click to expand...
Click to collapse
I don't understand what you're asking
Tried to flash the unbloated (my assumption at least) of the Korean rom: KOO. Followed the correct steps, flashed without problems but bloatware was not removed, also bootlogo of the original carrier doesn't disappear.
@iBowToAndroid, have you tested this method yourself with the S20 series? Flashing from unlocked to carrier firmware should always work I would say, but the other way around, have you got confirmed results for the S20 series?
SM-G981U Carrier Aggregation for Europe
I have S20 SM-G981U1 that i flashed with SM-G981U with no problems but is there any way to make CA to work in Europe?
Any help will be greatly appreciated because i have way lower mobile data speed in EU with my US unlocked phone...
tijsva said:
Tried to flash the unbloated (my assumption at least) of the Korean rom: KOO. Followed the correct steps, flashed without problems but bloatware was not removed, also bootlogo of the original carrier doesn't disappear.
@iBowToAndroid, have you tested this method yourself with the S20 series? Flashing from unlocked to carrier firmware should always work I would say, but the other way around, have you got confirmed results for the S20 series?
Click to expand...
Click to collapse
For U and U1 firmware, yes. You'll have to look elsewhere for discussions on Korean firmware
So you have tested flashing from (US) carrier firmware to unlocked carrier on the S20 succesfully? All bloatware and carrier bootscreens removed?
Any firmware (compatible with U1) that has CSC feature enabled for native call recording?
tijsva said:
So you have tested flashing from (US) carrier firmware to unlocked carrier on the S20 succesfully? All bloatware and carrier bootscreens removed?
Click to expand...
Click to collapse
@iBowToAndroid. Have you got confirmed results that bloatware is indeed removed including boot animations when changing from a US carrier branded phone to the international firmware on the Galaxy S20? I'm starting to wonder if there have been new restrictions in the S20 series that won't allow the CSC to be modified and therefor bloatware/carrier logo's won't be removed.
tijsva said:
@iBowToAndroid. Have you got confirmed results that bloatware is indeed removed including boot animations when changing from a US carrier branded phone to the international firmware on the Galaxy S20? I'm starting to wonder if there have been new restrictions in the S20 series that won't allow the CSC to be modified and therefor bloatware/carrier logo's won't be removed.
Click to expand...
Click to collapse
International firmware can't be flashed to a US model - never have been able to, never will be able to. Just because it's bloatware free doesn't make it "international". But yes, flashing the U1 firmware package removes all of the bloatware - it's been that way ever since the S7
iBowToAndroid said:
International firmware can't be flashed to a US model - never have been able to, never will be able to. Just because it's bloatware free doesn't make it "international". But yes, flashing the U1 firmware package removes all of the bloatware - it's been that way ever since the S7
Click to expand...
Click to collapse
Sorry, typo, should have been "unlocked" firmware.
You still haven't answered my question though Have you got confirmed results? Proof? I see you had good results for the S10 series, but so far I can't seem to find similar results for the S20 series.
dtothesquare said:
So I flashed with Odin with my unlocked from Samsung U1 firmware to the T-Mobile U firmware because I wanted the advanced messaging. Only issue in the beginning was not using the patched Odin, but once I did, no problems.
Tools:
Downloaded from this previous thread, post #2, with Modified Odin and Samsung Drivers https://forum.xda-developers.com/s10-plus/how-to/sm-g975u-firmware-downloads-tmo-spr-att-t3908657
Since it's been awhile since I've done flashing or Odin, I followed this basic guide:
https://forum.xda-developers.com/s10-plus/how-to/guide-g975f-flashing-megathread-faqs-t3936704
Of note, only needed the files from the TAW folder only, did not need the T-Mobile specific U firmware as resetting the phone with a T-mobile sim automatically loaded it.
My quick rundown:
1)Extract the G981U_TAW firmware file you just downloaded. You should get 5 files:
AP (System & Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_OXM (OXM CSC file, will wipe your phone)
HOME_CSC_OXM (OXM CSC file, will NOT wipe your phone)
2.)In Modified Odin I added each file to it's respective slot EXCEPT for HOME_CSC as I wanted to do a clean factory reset
3) Put the S20 in Download/ Odin mode. 2 different ways as outlined here
&t=8s
4) Once the phone was detected in the COM port number in Odin, I clicked the start button and waited til Odin said "PASS". One thing I noticed was the phone didn't reboot all the way automatically, it actually went into recovery mode and I ended up having to do a factory reset through there because at first it would bootloop and take me back into recovery mode, but after doing a factory reset in recovery mode it restarted just fine with the T-mobile firmware along with the t-mobile apps and advanced messaging working as it should be.
Click to expand...
Click to collapse
i got advanced messaging by just inserting a T-Mobile SIM into my unlocked s20, it restarted the phone and i even have the wifi calling too
tijsva said:
Sorry, typo, should have been "unlocked" firmware.
You still haven't answered my question though Have you got confirmed results? Proof? I see you had good results for the S10 series, but so far I can't seem to find similar results for the S20 series.
Click to expand...
Click to collapse
The proof is already here in the thread. Many users have already done it
I have migrated to TMobile and am trying to reflash my unlocked S8 Active from Sprint to TMobile mainly for wifi calling functionality. The phone was already running Android 9.
I downloaded & flashed the latest TMB firmware from sammobile via Odin v3.14.4 per the instructions on sammobile.
I flashed all the files including CSC and Userdata to ensure a complete wipe and flash.
I even wiped the cache and performed a factory reset after the firmware flash. The phone has been rebooted multiple times now since the reprogramming.
Unfortunately when the phone starts up I still get the Sprint flash screen and I don't have the Wifi Calling option available. The phone shows the latest TMB software is loaded (G892USQS6CTB2) however it still shows software ownership as Sprint (SPR/SPR/SPR).
Any advice on what I should be doing differently? Thanks!
It's a bit old to bump, but I'm in the exact same boat. Anyone have a fix for this?
I also am in the same boat: I want to use my SM-G892A on T-Mobile with wifi calling enabled. Many rooting resources say rooting this phone is not possible, but apparently on Sammobile there's instructions. I could not find them though. Any pointers appreciated.