Database Users

XXJMF Modem / Baseband download

Here is the latest (at time of writing) XXJMF Modem / Baseband file (tested on my Euro Tab - flash with care). To be flashed via Odin / Heimdall.
XXJMF - DOWNLOAD (ROMraid Load Balancing) - MD5: cd4061a61e409c45a9e6ee6c8fcb0370
P

This version is in the JMG ROM that's been available for a few days so people who have updated to JMG already have the JMF baseband version and don't need to make any changes.

This works with your MoDaCo Beta ROM?
Which section do I put the file under in the Heimdal GUI (OSX)?

Does this have the same WCDMA capabilities as the Bell I9000 modem (I9000UGJK3) that has served AT&T Tab users well?
If so, is it better?
Edit: I did some research and it seems that the Bell I9000 modem is not the only one that will work for AT&T Tab users (giving 850MHz UMTS along with the rest).
See:
http://forum.xda-developers.com/showthread.php?t=869628
http://forum.cyanogenmod.com/topic/11247-gt-i9000-cm61-faq-user-discussion-thread/page__st__40
http://forum.xda-developers.com/showthread.php?t=906977
I loaded this radio--T959TLJL3, along with Roto-JMI-v1--and confirmed that it does work on 850MHz on an AT&T Tab.
Now my question is, what differentiates I9000UGJK3 from I9000UGJK4, T959TLJL3, and XXJMF? How can I tell what the differences are between these radio/baseband/modem versions for EDGE/3G/UMTS, WiFi, BT, GPS?

jeremysv said:
Now my question is, what differentiates I9000UGJK3 from I9000UGJK4, T959TLJL3, and XXJMF?
Click to expand...
Click to collapse
The i9000 and T959 radios are for other samsung galaxy s phones. The JM* is for samsung tabs. Since they have the same hardware they can be used on AT&T or T-mobile tabs respectively.

jeremysv said:
Does this have the same WCDMA capabilities as the Bell I9000 modem (I9000UGJK3) that has served AT&T Tab users well?
Now my question is, what differentiates I9000UGJK3 from I9000UGJK4, T959TLJL3, and XXJMF? How can I tell what the differences are between these radio/baseband/modem versions for EDGE/3G/UMTS, WiFi, BT, GPS?
Click to expand...
Click to collapse
This question bothers me as well. I tried quite a few modem firmwares on my US Tmobile Tab and was not able to get 3G with none of them except original stock version.
We have to consider another variable: hardware version of the Tab. It seems that they don't support frequencies of competitive carrier. I had success with Tmo Vibrant. It works on both Tmobile and ATT 3G with proper Sim, of course. Same modem file that worked on Vibrant did not provide 3G on ATT meaning that either software stack or hardware not compatible.
To my knowledge the source code of phone software is not available for public and thus not much we can do about it.

mmmm, there is something strange in the way this tar is compressed,
if you try to unzip it using 7zip (i know there is NO need to unzip it but i do it as usual to check files integrity)it gives an error...
so I think it's better to stay away even if it works it may got some broken bit.
this is the error it gives:
"There i no correct record at the end of archive"

I tried downloading several times and end up with a tar around 500kb in size NOT 12Mb
Hope no one else tries flashing if it happens to them

can anyone who was able to get the entire 12Mb file, pls host it somwhere, as some people have posted, i was only able to download 1Mb file, even if it is zipped thats not going to inflate to 12Mb..
pls post if you were able to download the original 12Mb file.

Worked fine when I downloaded from the Tab lol
MD5: cd4061a61e409c45a9e6ee6c8fcb0370
http://www.multiupload.com/V937VVSVWV

Guys anybody have the 12 mb file? Modaco link is now blocked here in Midddle East and the links provided above is dead, anyone kindly upload or send to my email please?! Thanks in advance!
Kiss my Tab!

Here's another: XXJMF.bin

jeremysv said:
Here's another: XXJMF.bin
Click to expand...
Click to collapse
Dude thank you so much! Clicked the Thanks button for you!!!

thank you, hopefully this will make my bars go up a little more @ home.. i always lose connection there and go into emergency call mode

Only getting H+!

Hi I have a note 3 N9005 with t-mobile. It does not get LTE even though LTE is checked in the settings. Does anyone have the same issue?
Sent from my SM-N9005 using XDA Premium 4 mobile app

Are you in an LTE area?
Currently only 4 cities have T-Mobile/Vodafone LTE, I don't even have an LTE option

samanbabah said:
Hi I have a note 3 N9005 with t-mobile. It does not get LTE even though LTE is checked in the settings. Does anyone have the same issue?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
T-Mobile only has LTE in specific areas. Even though it is selected in the network mode, if your area is not LTE ready then it will revert to the best possible speed for your area. I am with Telus and have LTE enabled on my device but it shows 4G in my home as I'm in a fringe area. When I leave my home and travel about 100 meters, I have LTE and it will display the icon.
It was my understanding that T-Mobile disabled the LTE band on their device. If you rooted, it's possible you enabled the LTE band partially in that it's shown but even though selected, the regional settings have not been updated to reflect the ROM you installed for LTE capability.
Have you rooted your device?

cellrama said:
T-Mobile only has LTE in specific areas. Even though it is selected in the network mode, if your area is not LTE ready then it will revert to the best possible speed for your area. I am with Telus and have LTE enabled on my device but it shows 4G in my home as I'm in a fringe area. When I leave my home and travel about 100 meters, I have LTE and it will display the icon.
It was my understanding that T-Mobile disabled the LTE band on their device. If you rooted, it's possible you enabled the LTE band partially in that it's shown but even though selected, the regional settings have not been updated to reflect the ROM you installed for LTE capability.
Have you rooted your device?
Click to expand...
Click to collapse
When I had my HTC One before getting my Note 3 I was getting LTE in my area. So I'm pretty sure that t-mobile does have coverage in my area! And yes I have rooted my device.
Sent from my SM-N9005 using XDA Premium 4 mobile app

samanbabah said:
When I had my HTC One before getting my Note 3 I was getting LTE in my area. So I'm pretty sure that t-mobile does have coverage in my area! And yes I have rooted my device.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK, if your device is rooted, have you installed the T-Mobile ROM onto the device? Have you confirmed this ROM installs an LTE capable modem? If so, follow step 6 at the bottom of my thread to ensure you've enabled the regional carrier settings thus essentially turning on the LTE modem: http://forum.xda-developers.com/showthread.php?t=2489766.
If you do not have a ROM installed with an LTE capable modem, flash a compatible ROM and follow step 6 and you should have LTE capability.
Hope this helps!

I'm only getting H+ aswell and on my old phone with the same sim card and plan I had LTE!

Payette1996 said:
I'm only getting H+ aswell and on my old phone with the same sim card and plan I had LTE!
Click to expand...
Click to collapse
Like mentioned, T-Mobile just recently rolled out LTE in specific areas. The problem here is not the network but the phones capability of communicating with the network. My device is from WIND Mobile (Canada). This company only supports 4G data. The phone is LTE capable but the modem has been crippled. I rooted my phone and installed the Telus ROM (which inadvertently installs the LTE modem). Once installed, LTE is no longer crippled and once I entered the correct APN settings for LTE, I had access under my network options to select: LTE/WCDMA/GSM (auto connect). Problem was when doing this, I would still only get 3G. The phone was displaying the capability but it had to be enabled by modifying the regional settings and selecting the provider ROM. At this point, everything was functional and LTE capable.
Hope this helps!

I can't install any firmware other than the n9005 model ones. I tried installing the T-Mobile ROM but it gave me an error.

samanbabah said:
I can't install any firmware other than the n9005 model ones. I tried installing the T-Mobile ROM but it gave me an error.
Click to expand...
Click to collapse
Like I've suggested to others, please follow the documentation from start to finish in the following link: http://forum.xda-developers.com/show....php?t=2489766. With regards to ROOTING in the first set of instructions, replace the downloadable file with that which corresponds to your model. With the second set of instructions, when downloading TWRP, from the linked site, go back one directory and download the hltetmo version of TWRP. When you get to the third stage of instructions, download the file which represents T-Mobile's version of the ROM.
This should work for you but if not, let me know and I can assist where possible. Another individual had a similar issue who was PM'ing me and with a bit of time and troubleshooting, they're now up and running.
Hope this helps!
---------- Post added at 10:16 AM ---------- Previous post was at 10:11 AM ----------
Just as an FYI, both your threads relate to the same question regarding a ROM for increased device productivity. You also posted similar information in another thread: http://forum.xda-developers.com/showthread.php?t=2491711
Please try to limit posts regarding the same issue and post all concerns within a single thread. Please follow the instructions as outlined in my link. This should hopefully fix all your issues and if you have trouble along the way, please post in this thread and I'll respond and help where I can. Thanks!

cellrama said:
Like I've suggested to others, please follow the documentation from start to finish in the following link: http://forum.xda-developers.com/show....php?t=2489766. With regards to ROOTING in the first set of instructions, replace the downloadable file with that which corresponds to your model. With the second set of instructions, when downloading TWRP, from the linked site, go back one directory and download the hltetmo version of TWRP. When you get to the third stage of instructions, download the file which represents T-Mobile's version of the ROM.
This should work for you but if not, let me know and I can assist where possible. Another individual had a similar issue who was PM'ing me and with a bit of time and troubleshooting, they're now up and running.
Hope this helps!
---------- Post added at 10:16 AM ---------- Previous post was at 10:11 AM ----------
Just as an FYI, both your threads relate to the same question regarding a ROM for increased device productivity. You also posted similar information in another thread: http://forum.xda-developers.com/showthread.php?t=2491711
Please try to limit posts regarding the same issue and post all concerns within a single thread. Please follow the instructions as outlined in my link. This should hopefully fix all your issues and if you have trouble along the way, please post in this thread and I'll respond and help where I can. Thanks!
Click to expand...
Click to collapse
I did root my phone. I did successfully install TWRP. but for the 3rd step I don't know what firmware to download! I downloaded a few t-mobil ones and N9005 roms but when I try to flash them using Odin, it just fails. can you post the link to the correct Rom for my phone please? I have the N9005 model.

samanbabah said:
I did root my phone. I did successfully install TWRP. but for the 3rd step I don't know what firmware to download! I downloaded a few t-mobil ones and N9005 roms but when I try to flash them using Odin, it just fails. can you post the link to the correct Rom for my phone please? I have the N9005 model.
Click to expand...
Click to collapse
Well, in my 3rd step, I've listed ROMS for the SM-N900W8 model and you required ROMS for the International 9005 model. I would first load into TWRP by powering off your device and then once powered off, power on again using: Volume Up + Home Button + Power Button (all at once). When you see the Note 3 logo, let go and you will be in TWRP. Ensure you do a full wipe/format through TWRP and now you will be ready to install another fresh ROM rather than overwriting an existing ROM which can cause problems within itself. Once at this state, download an appropriate ROM from this link:
http://www.samsungis.com/Firmwares/SM-N9005-Galaxy-Note3-Snapdragon.html
The ROM I would go with is:
Galaxy Note 3 (Snapdragon) SM-N9005 TPLPoland (t-mobile) N9005XXUBMI7 4.3 11.09.2013 1628120 Download
This one I think has LTE but if not, you're safe with downloading any one of these variants. If the above does not enable LTE, you must research the carrier to ensure they have LTE. Please ensure you follow the last steps of the instructions to enter into the regional carrier settings and select the 3 digit code for the carrier ROM you installed.
Hope this helps!
---------- Post added at 11:17 AM ---------- Previous post was at 10:58 AM ----------
FYI....
Here is a list of carriers world-wide who support LTE and the frequency they support:
http://en.wikipedia.org/wiki/List_of_LTE_networks
If the ROM I suggested does not support LTE, this is what I would recommend:
Look at the different carriers provided in the original link I gave you for 9005 ROMS. Match one of these to this link showing supported LTE carriers. Make sure the frequency of this LTE carrier is supported by your phone then download the ROM. Once the ROM is installed, go to your regional carrier settings as I've listed in my rooting instructions and change the 3 letter code to match the ROM you just installed. Once the device resets and reboots, you should have the capabilities your device originally crippled.
Hope this helps!

cellrama said:
Well, in my 3rd step, I've listed ROMS for the SM-N900W8 model and you required ROMS for the International 9005 model. I would first load into TWRP by powering off your device and then once powered off, power on again using: Volume Up + Home Button + Power Button (all at once). When you see the Note 3 logo, let go and you will be in TWRP. Ensure you do a full wipe/format through TWRP and now you will be ready to install another fresh ROM rather than overwriting an existing ROM which can cause problems within itself. Once at this state, download an appropriate ROM from this link:
http://www.samsungis.com/Firmwares/SM-N9005-Galaxy-Note3-Snapdragon.html
The ROM I would go with is:
Galaxy Note 3 (Snapdragon) SM-N9005 TPLPoland (t-mobile) N9005XXUBMI7 4.3 11.09.2013 1628120 Download
This one I think has LTE but if not, you're safe with downloading any one of these variants. If the above does not enable LTE, you must research the carrier to ensure they have LTE. Please ensure you follow the last steps of the instructions to enter into the regional carrier settings and select the 3 digit code for the carrier ROM you installed.
Hope this helps!
---------- Post added at 11:17 AM ---------- Previous post was at 10:58 AM ----------
FYI....
Here is a list of carriers world-wide who support LTE and the frequency they support:
http://en.wikipedia.org/wiki/List_of_LTE_networks
If the ROM I suggested does not support LTE, this is what I would recommend:
Look at the different carriers provided in the original link I gave you for 9005 ROMS. Match one of these to this link showing supported LTE carriers. Make sure the frequency of this LTE carrier is supported by your phone then download the ROM. Once the ROM is installed, go to your regional carrier settings as I've listed in my rooting instructions and change the 3 letter code to match the ROM you just installed. Once the device resets and reboots, you should have the capabilities your device originally crippled.
Hope this helps!
Click to expand...
Click to collapse
I really appreciate your help but I couldn't install the Polish Rom you suggested either. Odin keeps failing! it gives me this error message: SW Rev Check Fail : [aboot] Fused 2 > Binary 1

samanbabah said:
I really appreciate your help but I couldn't install the Polish Rom you suggested either. Odin keeps failing! it gives me this error message: SW Rev Check Fail : [aboot] Fused 2 > Binary 1
Click to expand...
Click to collapse
Go into Settings | General | About Device
Within this menu, let me know what your Model number and Baseband version are. From here, I can further look into things for you. Thanks!

cellrama said:
Go into Settings | General | About Device
Within this menu, let me know what your Model number and Baseband version are. From here, I can further look into things for you. Thanks!
Click to expand...
Click to collapse
model number is SM-N9005
Baseband Version is N9005XXUBMJ2
I can install the official N9005 roms alright but not the ones that are associated with t-mobile.

samanbabah said:
model number is SM-N9005
Baseband Version is N9005XXUBMJ2
I can install the official N9005 roms alright but not the ones that are associated with t-mobile.
Click to expand...
Click to collapse
This is what I have gathered from you Baseband...
The model of device you have is a Samsung Galaxy Note 3 (International - Snapdragon). It was manufactured October 2013 and was the second batch or build released for public purchase. The Countries/regions your phone recognizes are as follows:
Austria
Belgium
France
Germany
Hungary
Italy
Nordic
Spain
United Kingdom
This means that you must install an International ROM supported by one of these Countries for the device to successfully load it and boot up. You currently have the device unlocked and are using T-Mobile. This does not mean you must have the T-Mobile ROM loaded on the device to enable features which have been crippled. All you must do is research 3 letter CSC code for the ROM you download and ensure that carrier supports the features which are currently being crippled at the moment with T-Mobile. Once the ROM has been downloaded and installed through ODIN, as previously stated, enter the CSC menu on your device and select the 3 letter code which represents the ROM you just downloaded. The link to obtain a ROM (as previously provided) is:
http://www.samsungis.com/Firmwares/SM-N9005-Galaxy-Note3-Snapdragon.html
Please make sure the ROM you download supports all the features you wish to enable and that it also supports one of the locations listed above. At this point, a ROM should successfully load and you should be operational.
Hope this helps!

G977U models Retail Stock Firmware Links Here

So it seems like Samsung has really switched things up here, with the 5G model. I haven't seen any mention of a U1 model, so I would not expect that to be a thing here in the US - at least not yet. The Verizon and AT&T model are both G977U, G977T is T-Mobile, and G977P is the Sprint model. Firmware packages are comprised of the 4 base files plus a USERDATA.
It appears that even though AT&T and Verizon are both U models, they will each be getting their own distinct updates. For example, we have G977UUCU1ASEM for AT&T but G977UVRU1ASE8 for Verizon. The CSC file names also specifically have "ATT" and "VZW" in them. AT&T and Verizon firmwares have confirmed to be interchangeable (as long as you're not trying to downgrade the bootloader) but you cannot cross flash between anything with different model numbers.
This is not a "beginner's guide to Odin flashing" type post/thread, so I won't list basic, step-by-step 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 the "beginner's" posts/threads - there are tons of them here on XDA.
Happy flashing!
https://www.androidfilehost.com/?w=files&flid=292071
Notes:
- Don't quote the OP when you reply, kthx
- I compress 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
- I pay for a subscription to a site that gets beta builds and also sometimes gets the official releases 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. The latest versions of Verizon (manual entry required), Sprint, and T-Mobile firmware can always be downloaded at any time, using SamFirm/Frija. So I won't be adding any of those firmwares to my AFH folders, unless I get early access to them, before they hit SamFirm/Frija. I will be adding at least one version per bootloader increment for AT&T firmware, since their files are never available on SamFirm/Frija. If you want an AT&T version that's not already uploaded, or a Verizon/Sprint/T-Mobile version other than whatever the latest is, let me know and I'll see what I can do.
- HOME CSC file keeps data intact; using the other one will wipe data. Also, flashing the USERDATA file will wipe your data. USERDATA is only needing if converting between AT&T and Verizon firmwares. If you're just looking to manually update from an older version, then you can skip the USERDATA file (but I'd still recommend flashing it if you don't care if your phone gets wiped).
**it has been discovered that, like most of the rest of AT&T Samsung models (true U models excluded), the AT&T AP tars have a small "userdata" partition in them that will also initiate a wipe, during the flash. So for bootloader 2 AT&T firmwares and higher, I'll also include a "no-wipe" AP tar that has that partition removed, for those who are looking to manually update from an older AT&T version without losing their data. Flash that, along with BL, CP, and HOME CSC in order to retain your data and not have a factory reset performed.
- My naming method for AFH folders 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. And each folder will have a designation showing whether it's an AT&T or Verizon build, instead of having separate folders for all of each carrier's builds

Firmware is now listed on SamFirm. Like almost all Verizon phones, manual entry for the 3 fields is required in order to find/download it

Could I use this to flash a unlocked version per say. To get rid of the Verizon bloat and add back the stock Samsung system
Like how the U1 would be if it were made?

Darktorn said:
Could I use this to flash a unlocked version per say. To get rid of the Verizon bloat and add back the stock Samsung system
Like how the U1 would be if it were made?
Click to expand...
Click to collapse
Nope. Flashing it is just gonna give you the exact same thing that you have now

iBowToAndroid said:
Nope. Flashing it is just gonna give you the exact same thing that you have now
Click to expand...
Click to collapse
Ah damn. So I would have to wait for the elusive unlocked model. Thank you anyway .
I miss my Samsung caller ID and Samsung cloud from my unlocked s10+

can u please put the verizon USA version if available? s10plus5G

88santee said:
can u please put the verizon USA version if available? s10plus5G
Click to expand...
Click to collapse
It's already there, linked in the OP. You can also get it from SamFirm any time that you want

can i flash it on my G977N (korea version) ?

hoangtu2410 said:
can i flash it on my G977N (korea version) ?
Click to expand...
Click to collapse
I don't know. Try it and see what happens

iBowToAndroid said:
I don't know. Try it and see what happens
Click to expand...
Click to collapse
my device can be brick if it fail or not ?

hoangtu2410 said:
my device can be brick if it fail or not ?
Click to expand...
Click to collapse
I have no idea. Anything that you do, you do at your own risk

Is anyone have access to BTU or XEU for SM-G977B please?

Damian said:
Is anyone have access to BTU or XEU for SM-G977B please?
Click to expand...
Click to collapse
No, because those providers don't sell that model. EE is the only one that does, so EVR is the only region for which G977B files exist

Vodafone and UK Samsung is selling them already. I have my S10 5G from Vodafone UK.
Wysłane z mojego SM-G977B przy użyciu Tapatalka

Links for AT&T (U model) and Sprint (P model) firmware have been added

iBowToAndroid said:
No, because those providers don't sell that model. EE is the only one that does, so EVR is the only region for which G977B files exist
Click to expand...
Click to collapse
about G977B UK CSC
in G977BOBE : BTB BTE EVR - UK ( BT Mobile ) - United Kingdom (T-Mobile UK,Orange UK)
in G977BOVF : VOD - United Kingdom (vodafone)
in G977FOXM : CPW - United Kingdom (Carphone Warehouse)
regards

good news samsung whent back to old days firmware is cross-flashable like on the s7/edge.. i flashed my g977u vzw with att firmware and its all att now ATT/ATT/VZW

juvemex said:
good news samsung whent back to old days firmware is cross-flashable like on the s7/edge.. i flashed my g977u vzw with att firmware and its all att now ATT/ATT/VZW
Click to expand...
Click to collapse
Old days? Lol. It's always been that way, ever since that S7 - that was the first device that had that capability. And all flagships have been that way since. Good to know that it works though

Did you flash the att with Odin? Or how? They're all zip files packed in the main zip file

Mklubertanz said:
Did you flash the att with Odin? Or how? They're all zip files packed in the main zip file
Click to expand...
Click to collapse
No, they're not zip files packed within a zip. Odin files are in .tar format. So they're tar files, packed within a zip.

G988U and G988U1 Firmware Links and Flashing Discussion Here

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

G986U and G986U1 Firmware Links and Flashing Discussion Here

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.