Can I flash stock firmware via odin form diffrent country?
I have bought tablet in US. Now i want to gift this tablet to my brother, but he only speak in polish language
So I have SM-T800 with T800XXU1BOE2 firmware. XAR region.
I want to flash T800XXU1ANEB_T800XEO1ANE2_XEO via odin.
The reason for this change is lack of polish language in my current firmware.
Thanks in advance
Yes as long as the bootloader isn't locked and the roms use the same platform, ie exynos or Qualcomm.
However there may be issues with mobile data.
This is Wi-FI version, so this problem doesnt concern me. i think bootloader will not be a problem to unlock.
How can i check platform in firmware i have downloaded? (from sammobile.com for sm-t800 model, there was 3 diffrent i have picked the one with kies icon enabled).
mj_weed said:
This is Wi-FI version, so this problem doesnt concern me. i think bootloader will not be a problem to unlock.
How can i check platform in firmware i have downloaded? (from sammobile.com for sm-t800 model, there was 3 diffrent i have picked the one with kies icon enabled).
Click to expand...
Click to collapse
You wont be able to unlock the bootloader, but no worries you have the exynos wifi version so you dont have a locked bootloader anyway.
No Point
Just flash the U.S. one and change the language to Polish
Hello to everybody,
I have a Galaxy S9, model SM-G960N and finally the Korean Update to Android 10 arrived, downloaded it from SamMobile (The unbranded version KOO) Flashed it without problems and the phone works as intended. Only it doesn't have KOO as CSC, it has SKC, which has bloatware and it isn't the one I flashed. What gives? Why does it do that, are there any workarounds? Here's what I've tried until now:
Downloaded, and flash numerous times, no result, I don't live in Korea, I don't have a Korean SIM, phone still reports SKC.
Flashing with or without sim card inserted gives the same result.
Can't flash any other CSC, other than Korean ones, Odin spits out an error and it does not even start the flashing process.
Mix and matching different CSC with different firmware's obviously not successful.
Any idea if something can be done about this?
Thank you in advance.
You need to root it and change CSC with phone info app to KOO
numpea said:
You need to root it and change CSC with phone info app to KOO
Click to expand...
Click to collapse
I guess that's the only remaining way, but do you know why it picks SKC instead of KOO, even if the firmware that I'm downloading is KOO.
Korean CSC is a multiCSC even if you download KOO firmware you phone will use SKC that's included in the CSC so there is no different korean csc there's only one that includes the 4 csc codes
i have rooted device but i need multilanguage. ho i can debrand or add orginal languages?
tejanaqkilica said:
Hello to everybody,
I have a Galaxy S9, model SM-G960N and finally the Korean Update to Android 10 arrived, downloaded it from SamMobile (The unbranded version KOO) Flashed it without problems and the phone works as intended. Only it doesn't have KOO as CSC, it has SKC, which has bloatware and it isn't the one I flashed. What gives? Why does it do that, are there any workarounds? Here's what I've tried until now:
Downloaded, and flash numerous times, no result, I don't live in Korea, I don't have a Korean SIM, phone still reports SKC.
Flashing with or without sim card inserted gives the same result.
Can't flash any other CSC, other than Korean ones, Odin spits out an error and it does not even start the flashing process.
Mix and matching different CSC with different firmware's obviously not successful.
Any idea if something can be done about this?
Thank you in advance.
Click to expand...
Click to collapse
i've to face the same thing mine is KTC but it shows SKC. idk what to do after did that always my device is getting overheat
...because I use the phone in Europe. Given the firmware is North America I was wondering whether I need to change the modem in ODIN to get better reception/ 5g in Europe. The last Samsung I owned was the S4 where updating the modem to your region was ubiquitary. Not sure if this is still necessary and doable., so hoping for some advice.
Second question: I have a US S20 locked to AT&T. Will flashing the U1 firmware (incl. factory reset) also unlock the phone?
Cheers!
tpunkttpunkt said:
...because I use the phone in Europe. Given the firmware is North America I was wondering whether I need to change the modem in ODIN to get better reception/ 5g in Europe. The last Samsung I owned was the S4 where updating the modem to your region was ubiquitary. Not sure if this is still necessary and doable., so hoping for some advice.
Second question: I have a US S20 locked to AT&T. Will flashing the U1 firmware (incl. factory reset) also unlock the phone?
Cheers!
Click to expand...
Click to collapse
You can't mix exynos firmware and Snapdragon. I doubt you can use just the modem portion of a European exynos code. You can flash U1 code freely, but that does not unlock the bootloader. Do you mean you can't put any sim other than AT&T?
I didn't mean to unlock the bootloader (since that's not possible for US phones) but the sim so I can use my German sim card in Europe in this phone.
tpunkttpunkt said:
I didn't mean to unlock the bootloader (since that's not possible for US phones) but the sim so I can use my German sim card in Europe in this phone.
Click to expand...
Click to collapse
Do you know if I run the risk to brick my device if I tried to combine the exynos modem with a snapdragon rom? Cause otherwise I might just try it.
For those who aren't already aware, F926U is the model number of all of the US carrier versions of the Z Fold3. The F926U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. A "U to U" or "U1 to U1" flash does not require a factory reset, but changing from one firmware to the other will require one. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.
Manual Odin flashing is designed for those who:
- want to manually update to a newer version of U firmware on their U device, either because they don't want to wait for their carrier's OTA or because OTAs aren't working on their device, or a different carrier got a new feature/patch before they did
- want to flash U1 firmware to their U device
- want to convert from U1 firmware to carrier U firmware
- want to convert from one carrier's U firmware (with all apps and bloatware) to a different carrier's U firmware (with all apps and bloatware)
For those who aren't already aware, anyone can now download firmware for almost any Samsung device any time that they want, via the various firmware download tools posted here on XDA like SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But they only provide whatever the latest/newest/current version is - nothing older. I have access to an internal Samsung firmware download tool that usually gets new versions before they hit the public firmware download tools, so that's where my files come from.
This is not a "beginner's guide to Odin flashing" -type post/thread, so I won't list basic, step-by-step flashing instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware (or haven't done it in a long time), I recommend you consult one of those "beginner's" guides- there are tons of them here on XDA.
Happy flashing!
U firmware: https://www.androidfilehost.com/?w=files&flid=327754
U1 firmware: https://www.androidfilehost.com/?w=files&flid=327755
Notes:
- DON'T QUOTE THE OP WHEN YOU REPLY, kthx
- I have lots of threads just like this one for other Samsung flagships, if it interests you. For those who have already made use of my previous threads for a different device and are upgrading, welcome back
- My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- it's quite time consuming to download the files, zip them up, and upload them to AFH. And, I do threads like this for every single flagship model, so I won't be uploading every single version. The only full builds that I upload are ones where I get access to a new bootloader and/or Android version early, before they hit the firmware download tools.
- My naming method for folders on AFH is: build - bootloader - Android version
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- HOME CSC file keeps data intact; using the other CSC will wipe data. Flashing USERDATA will also wipe data.
- Since AT&T doesn't allow their firmware to be publicly available (for any of their devices), I'll try to always upload at least one USERDATA per bootloader increment for AT&T (and Cricket, if they get this model). I'll also upload any full builds if AT&T is the only carrier to get that specific build, because you won't be able to find the files anywhere else.
- For identifying USERDATAS, and to know what region/CSC to use in the firmware download tools if you're downloading yourself:
AIO = Cricket (not available via firmware download tools)
ATT = AT&T (not available via firmware download tools)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
DSH = Dish Network
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via firmware download tools, but Manual Entry is required - Auto will not work)
XAA = U1 firmware
Is there a T-Mobile version available yet?
ruthlessnature said:
Is there a T-Mobile version available yet?
Click to expand...
Click to collapse
Yep, firmware has been on Samsung's servers since last week
iBowToAndroid said:
Yep, firmware has been on Samsung's servers since last week
Click to expand...
Click to collapse
I downloaded the file from samefirm, and frija but did not get the carrier bloat or T-Mobile boot screen from either one. I have an unlocked version.
ruthlessnature said:
I downloaded the file from samefirm, and frija but did not get the carrier bloat or T-Mobile boot screen from either one. I have an unlocked version.
Click to expand...
Click to collapse
You need to make sure your CSC shows as TMB, and need to make sure you're flashing USERDATA too
iBowToAndroid said:
You need to make sure your CSC shows as TMB, and need to make sure you're flashing USERDATA too
Click to expand...
Click to collapse
That's strange, neither one I downloaded has TMB in the csc, do you have a link ?
ruthlessnature said:
That's strange, neither one I downloaded has TMB in the csc, do you have a link ?
Click to expand...
Click to collapse
I'm not talking about the firmware. I'm talking about the phone itself, in the Settings
Oh, I see, it doesn't change, shows xaa/xaa/xaa I downloaded the ATT userdata to flash and see if it changes it.
ruthlessnature said:
Oh, I see, it doesn't change, shows xaa/xaa/xaa I downloaded the ATT userdata to flash and see if it changes it.
Click to expand...
Click to collapse
If you want T-Mobile bloatware, you need to insert a T-Mobile SIM so that the CSC changes to TMB. And then you need to flash a U firmware with T-Mobile USERDATA
iBowToAndroid said:
If you want T-Mobile bloatware, you need to insert a T-Mobile SIM so that the CSC changes to TMB. And then you need to flash a U firmware with T-Mobile USERDATA
Click to expand...
Click to collapse
Thanks for the info, I couldn't get it to flash back to the u1 firmware until I downloaded the patched Odin. Then I was able to I put my Sim, the csc showed TMB and then I was able to flash the u firmware with the TMB userdata. Thanks again for your help.
ruthlessnature said:
Thanks for the info, I couldn't get it to flash back to the u1 firmware until I downloaded the patched Odin. Then I was able to I put my Sim, the csc showed TMB and then I was able to flash the u firmware with the TMB userdata. Thanks again for your help.
Click to expand...
Click to collapse
You're welcome!
ruthlessnature said:
Thanks for the info, I couldn't get it to flash back to the u1 firmware until I downloaded the patched Odin. Then I was able to I put my Sim, the csc showed TMB and then I was able to flash the u firmware with the TMB userdata. Thanks again for your help.
Click to expand...
Click to collapse
For anyone looking for that it's here: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
I'm getting a weird Complete(Write) Operation Failed error when flashing any tips?
NVM gotta have USB Debugging on
wschamps42 said:
I'm getting a weird Complete(Write) Operation Failed error when flashing any tips?
NVM gotta have USB Debugging on
Click to expand...
Click to collapse
Uhhhh what? Flashing is done in Download mode, not Normal mode
can we flash a different region firmWARE (UK / EUROPE) to the U1? Given the phones are all Qualcomm SD now
Drnms said:
can we flash a different region firmWARE (UK / EUROPE) to the U1? Given the phones are all Qualcomm SD now
Click to expand...
Click to collapse
Nope
I appologize for being the super noob. A couple questions.
Does using this process disable the cameras as mentioned in https://forum.xda-developers.com/t/unlocking-bootloader-will-disable-the-camera.4321957/page-.
You stated that there are tons of beginners guides. In doing searches I find multiple different guides with different completely different processes. Is there one that you recommend or works best?
My goal is to make my unlocked fold3 more usable on ATT/firstnet. There are multiple features I cannot use and I don't receive same call quality service as my wife's locked att fold3.
sllong said:
I appologize for being the super noob. A couple questions.
Does using this process disable the cameras as mentioned in https://forum.xda-developers.com/t/unlocking-bootloader-will-disable-the-camera.4321957/page-.
You stated that there are tons of beginners guides. In doing searches I find multiple different guides with different completely different processes. Is there one that you recommend or works best?
My goal is to make my unlocked fold3 more usable on ATT/firstnet. There are multiple features I cannot use and I don't receive same call quality service as my wife's locked att fold3.
Click to expand...
Click to collapse
You will not lose the cameras as you are flashing firmware not unlocking the bootloader.
sllong said:
My goal is to make my unlocked fold3 more usable on ATT/firstnet. There are multiple features I cannot use and I don't receive same call quality service as my wife's locked att fold3.
Click to expand...
Click to collapse
Under Settings-->About-->Software Information, what's the last line of your "Service provider SW ver" item?
iBowToAndroid said:
Under Settings-->About-->Software Information, what's the last line of your "Service provider SW ver" item
Click to expand...
Click to collapse
iBowToAndroid said:
/xaa/xaa/xaa
Click to expand...
Click to collapse
I've been messing around with few firmwares out there but none are unbranded, so I'm here asking for a solution to get rid of annoying unnecesary bloatware, no rooting if it's possible. Maybe someone already have found a good unbranded firmware that I can use to flash my A52s? Thanks.
Samsung nowadays uses multi CSC packs (OMC), so it's most likely you've been flashing the same firmware over and over. You need to de-brand your phone by changing your CSC, you can use SamFw since it doesn't requires root and will not blow your warranty bit
BlackMesa123 said:
Samsung nowadays uses multi CSC packs (OMC), so it's most likely you've been flashing the same firmware over and over. You need to de-brand your phone by changing your CSC, you can use SamFw since it doesn't requires root and will not blow your warranty bit
Click to expand...
Click to collapse
Stuck in Latinamerica, and my CSC code is OWO, I believe that ain't multi, tried the UUSD code on Samsung and Google phone apps but not working. I checked every CSC so I don't end up flashing unnecesarily. I'm gonna flash some nordic firm that I read is unbranded, wish me luck, hope I don't end up with a brick.
ekam95 said:
Stuck in Latinamerica, and my CSC code is OWO, I believe that ain't multi, tried the UUSD code on Samsung and Google phone apps but not working. I checked every CSC so I don't end up flashing unnecesarily. I'm gonna flash some nordic firm that I read is unbranded, wish me luck, hope I don't end up with a brick.
Click to expand...
Click to collapse
Flashing the firmware for your country's CSC alone is not enough, as I said you need a tool like SamFw to change the sales code set in the efs partition of your phone (without it, root would be required to modify those files).
BlackMesa123 said:
Flashing the firmware for your country's CSC alone is not enough, as I said you need a tool like SamFw to change the sales code set in the efs partition of your phone (without it, root would be required to modify those files).
Click to expand...
Click to collapse
How come I didn't notice the CSC change function on SamFW tool? I just change it with it and now is all clean as expected (debranded), thank you! So grateful!