Database Users

Can I flash SM-G900F firmware on an SM-G900I?

Hi,
I have an SM-G900I and was wondering if anyone knows if I can flash SM-G900F firmware on it? Will it change the model number as well?
Also, does anyone know the difference between the 2 models apart from one being an Asian model and one being European?

Nope. You can't flash different models firmware, because it'll brick your device...

Isn't it effectively the same phone though?

gyrex said:
I have an SM-G900I and was wondering if anyone knows if I can flash SM-G900F firmware on it? Will it change the model number as well?
Also, does anyone know the difference between the 2 models apart from one being an Asian model and one being European?
Click to expand...
Click to collapse
Sure you can flash the 900F firmware. It isn't recommended and may "brick" (damage) your phone, making it as useful as a brick. You'd already know this if you had read any of the existing threads on the subject. But you can try anyway if you really want to. If you do, at least make the effort to locate the proper 900F PIT file and flash it concurrently. Your phone still won't work properly afterwards, but using the PIT file will make it less likely that you brick it due to partition corruption.
If you just want to change the displayed model number, you can do that by editing the build.prop file. The main difference between the two models is that they are intended for use in different regions and with different carriers and have different firmware. Therefore each will support different frequency bands.
Unfortunately you didn't tell us why you want to do this. If you are trying to use your phone on a different carrier that uses different frequencies, then trying to flash a 900F firmware won't do that. If you are looking for some 900F specific apps or features, you can probably do that by installing a 900F based custom ROM instead.
.

gyrex said:
Hi,
I have an SM-G900I and was wondering if anyone knows if I can flash SM-G900F firmware on it? Will it change the model number as well?
Also, does anyone know the difference between the 2 models apart from one being an Asian model and one being European?
Click to expand...
Click to collapse
Yes flash another firmware will change the model number accordingly

fffft said:
Sure you can flash the 900F firmware. It isn't recommended and may "brick" (damage) your phone, making it as useful as a brick. You'd already know this if you had read any of the existing threads on the subject. But you can try anyway if you really want to. If you do, at least make the effort to locate the proper 900F PIT file and flash it concurrently. Your phone still won't work properly afterwards, but using the PIT file will make it less likely that you brick it due to partition corruption.
If you just want to change the displayed model number, you can do that by editing the build.prop file. The main difference between the two models is that they are intended for use in different regions and with different carriers and have different firmware. Therefore each will support different frequency bands.
Unfortunately you didn't tell us why you want to do this. If you are trying to use your phone on a different carrier that uses different frequencies, then trying to flash a 900F firmware won't do that. If you are looking for some 900F specific apps or features, you can probably do that by installing a 900F based custom ROM instead.
.
Click to expand...
Click to collapse
Thanks for your comprehensive response!
The main reason for wanting to flash the SM-G900F firmware is because it seems like a more mainline branch and DBT/BTU will probably get more OTA frequent updates than XSA and i think issues would get resolved quicker in that branch...

vndnguyen said:
Yes flash another firmware will change the model number accordingly
Click to expand...
Click to collapse
Are you absolutely sure of this? Do you know anyone who has done this successfully?

gyrex said:
The main reason for wanting to flash the SM-G900F firmware is because it seems like a more mainline branch and DBT/BTU will probably get more OTA frequent updates than XSA and i think issues would get resolved quicker in that branch...
Click to expand...
Click to collapse
You could do that.. but NFC and sundry other features will fail on you. And any update involving the bootloader won't work for you. And probably ditto for any radio (modem) updates.
Your best bet to do what you want in my opinion is to install a 900F based custom ROM e.g. the Alliance ROM. The active custom ROM developers are proactive in updates and supporting their ROMs and would see the best result by you.
This approach would leave you with your stock 900l bootloader and radio. And 900F ROM, with updates for the ROM maintained by the ROM developer.
.

gyrex said:
Are you absolutely sure of this? Do you know anyone who has done this successfully?
Click to expand...
Click to collapse
When you flash the new firmware, the build.prop is replaced by a new one and the model number will be changed accordingly.
You can also manually change the model number by editing the build.prop file (ro.product.model), as fffft already pointed out.

How can I change from single CSC to Multi-CSC

How can I change from a single CSC (TNZ) to a multi-CSC without root? It doesn't seem to be as easy as for my S8.

Any luck with this change. As i am also looking to change in my note 9

androidloveRs3104 said:
Any luck with this change. As i am also looking to change in my note 9
Click to expand...
Click to collapse
No luck at all:crying:

If its the F model you can flash the multi csc firmware with odin 3B.
Sent from my SM-G975U1 using XDA Labs

SeanX said:
How can I change from a single CSC (TNZ) to a multi-CSC without root? It doesn't seem to be as easy as for my S8.
Click to expand...
Click to collapse
what trouble are you running into? flashing a CSC doesnt require root as its done in download mode and every Galaxy S phone from the S8 on are capable of taking any firmware built for any US bootloader version S device youre on. It will very likely require the patched version of odin available here
for the most part, all the CSC does is tell the phone what carrier its on which tells it what LTE bands to use, what carrier bloat to install, config for voLTE and wifi calling etc etc

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.

Will it work if I Flash only the CSC file of SM-T560(KitKat) to SM-T560NU(Lollipop)?

I'm from Philippines sadly the only region available is from USA
SM-T560NU-T560NUBNN1AOK1 - Lollipop (Current OS)
SM-T560-T560OLB0APL1 - Kitkat

Yes, you can use Odin to downgrade, as long as your bootloader is unlocked.

V0latyle said:
Yes, you can use Odin to downgrade, as long as your bootloader is unlocked.
Click to expand...
Click to collapse
Thanks for the reply,
Just clarifying that the two models I stated on my thread are two different models, but only their processor is different.
SM-T560NU-Qualcomm (Model I'm Currently Using)
SM-T560-Spreadtrum
and only the CSC File I'm flashing, will it work?

deathnote08 said:
Thanks for the reply,
Just clarifying that the two models I stated on my thread are two different models, but only their processor is different.
SM-T560NU-Qualcomm (Model I'm Currently Using)
SM-T560-Spreadtrum
and only the CSC File I'm flashing, will it work?
Click to expand...
Click to collapse
If they are different hardware, I would not recommend flashing different firmware. Flashing a different CSC on a device that firmware is designed for is fine, but you can't take a CSC from one device and flash it on another device. This will cause issues and could permanently brick your device.