[Q] S2 Rom supports OTA - Galaxy S II Q&A, Help & Troubleshooting

Hi all
I have been wondering how I can tell if the custom or claimed-to-be-official S2 ICS rom supports OTA upgrade?
I know it's perhaps impossible for those custom ones, but the ones I downloaded and flashed that claim 'official', how can I be sure if they supports OTA or not? I am a bit tired of keeping flashing the new versions after all.
Thank you!

it is strictly connected to your product code and region the ROM was released for - these two things have to match.
You will have OTA update if you're using ROM officially released for the region you have set in your phone. and you will get OTA updates only to other ROMs released for this region. few examples:
1. you have XEO product code and you use ROM officially released for XEO - you will get OTA updates but only to other ROMs released for XEO;
2. you have TWO product code but you have installed ROM released for XEO - you won't have OTA update at all (unless you change your PC according to you ROM release region - to XEO - and then, again, updates will be only to XEO ROMs)
3. you HAD XEO and ROM released for XEO, but for some reason you changed your PC to TWO - you won't have OTA update at all (unless you match your PC with region your ROM was released for again).
so, check your product code and the region your ROM was released for, match them however you want - change ROM or PC - and you will be having OTA updates. remember that changing PC is wiping all your data so do backup.
other thing is that you won't have OTA update if you use custom ROM, custom kernel or in some cases root (depending on the root method. rooting phone without making changes to kernel doesn't stop your device from getting OTA update until you make changes in your system).

gaeilge said:
it is strictly connected to your product code and region the ROM was released for - these two things have to match.
You will have OTA update if you're using ROM officially released for the region you have set in your phone. and you will get OTA updates only to other ROMs released for this region. few examples:
1. you have XEO product code and you use ROM officially released for XEO - you will get OTA updates but only to other ROMs released for XEO;
2. you have TWO product code but you have installed ROM released for XEO - you won't have OTA update at all (unless you change your PC according to you ROM release region - to XEO - and then, again, updates will be only to XEO ROMs)
3. you HAD XEO and ROM released for XEO, but for some reason you changed your PC to TWO - you won't have OTA update at all (unless you match your PC with region your ROM was released for again).
so, check your product code and the region your ROM was released for, match them however you want - change ROM or PC - and you will be having OTA updates. remember that changing PC is wiping all your data so do backup.
other thing is that you won't have OTA update if you use custom ROM, custom kernel or in some cases root (depending on the root method. rooting phone without making changes to kernel doesn't stop your device from getting OTA update until you make changes in your system).
Click to expand...
Click to collapse
Thanks for the detailed response. So I guess I need to get a stock rom for Australia then as I bought the phone and am using it in Australia.
Where I can find it? What's the code for Australia market? XEO is just for Euro, rite?
Thanks!!

Get the PC version of Checkfus (search for it on here/Google) & download I9100XWLP8/I9100XSALP4/I9100XXLPS/I9100XWLP8 which is an unbranded Australian ICS stock rom. Flash it following the instructions in this thread. You can also download carrier branded ICS stock roms with Checkfus if that's your preference.

MistahBungle said:
Get the PC version of Checkfus (search for it on here/Google) & download I9100XWLP8/I9100XSALP4/I9100XXLPS/I9100XWLP8 which is an unbranded Australian ICS stock rom. Flash it following the instructions in this thread. You can also download carrier branded ICS stock roms with Checkfus if that's your preference.
Click to expand...
Click to collapse
Thanks!
a few more questions:
1. How can I tell a ROM definitely supports OTA before I install it?
2. How can change my s2 region code to match the ROM's in order to get OTA working again?
3. what's the real difference between carrier branded rom and unbranded ones? e.g. is it better to use say telstra branded rom?

1. Be sure that ROM was released for the region/carrier which fits product code set in your phone - it's always written in ROM info on any download page I know. you may also adapt product code in your phone later, to fit the ROM you wish to use (in case you insist on FOTA/Kies updates).
2. *#272*IMEI# changes your product code. Remember that it wipes all your data.
3. Branded FW may include additional apps but also lot of operator's useless trash. Personally I never use branded ROMs and always suggest debranding. Check thread about chosen ROM for more info.
Sent from my GT-I9100 using Tapatalk 2

gaeilge said:
1. Be sure that ROM was released for the region/carrier which fits product code set in your phone - it's always written in ROM info on any download page I know. you may also adapt product code in your phone later, to fit the ROM you wish to use (in case you insist on FOTA/Kies updates).
2. *#272*IMEI# changes your product code. Remember that it wipes all your data.
3. Branded FW may include additional apps but also lot of operator's useless trash. Personally I never use branded ROMs and always suggest debranding. Check thread about chosen ROM for more info.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, Re #2, it seems strange that although I never used that command to change my code, only flashed a stock rom issued for another region a while ago, now the checkfus says my handset's the regional code that fits this new rom, other than the supposed-to-be australian one.
Is this normal? So the flashing process can actually alter the phone prod. region code without warning me?

Theoretically it shouldn't but s... happens. If you were flashing ROMs in which your product code wasn't available then it could adjust itself. Mostly I've seen situations when after such an ROM update, PC just wasn't available for change but it stayed the same as it was. On the second hand I've also heard about few cases like yours. Anyway, are you sure about your original PC if you never used this code option? Maybe originally it was different than you think it ought to be?
Sent from my GT-I9100 using Tapatalk 2

You can also try www.sammobile.com for stock firmware. Just make sure that you input your device and region correctly
Edit : and you'll have to flash through odin
Sent from my GT-I9100 using xda premium

gaeilge said:
Theoretically it shouldn't but s... happens. If you were flashing ROMs in which your product code wasn't available then it could adjust itself. Mostly I've seen situations when after such an ROM update, PC just wasn't available for change but it stayed the same as it was. On the second hand I've also heard about few cases like yours. Anyway, are you sure about your original PC if you never used this code option? Maybe originally it was different than you think it ought to be?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Strange!
1. I use *#1234# command and found my rom info is I9100ZSLPG, which is for the region Hongkong - TGY
2. then I use *#272*imei#* (Product code) to check my phone's current CSC, which is shown already 'TGY'.
Now my question is, why my phone still can't get any OTA update?
Any other bit not matched? How to check if any?
Thanks.

Related

A Question

Hey guys,
I recently rooted my S2 and installed a custom ROM because i was sick of waiting for Samsung to release ICS in my region ( Also i love stock ICS ).
Recently they released ICS in my region so i went to sammobiles to download the firmware.
My Question is that do PDA and CSC change for each new version of android released or am i supposed to wait for the firmware with the same PDA and CSC as the version i was using.
Also I wanted to know if I could flash firmware of different region on the phone without it having any errors
Thank you.
Mysterious99 said:
Hey guys,
I recently rooted my S2 and installed a custom ROM because i was sick of waiting for Samsung to release ICS in my region ( Also i love stock ICS ).
Recently they released ICS in my region so i went to sammobiles to download the firmware.
My Question is that do PDA and CSC change for each new version of android released or am i supposed to wait for the firmware with the same PDA and CSC as the version i was using.
Also I wanted to know if I could flash firmware of different region on the phone without it having any errors
Thank you.
Click to expand...
Click to collapse
u can flash any stock rom ...
The only small issue you might face if you flash stock firmware for a different region is you may not be able to get OTA updates for your region when they're released. But it's easy enough to flash them via Odin so this isn't a massive problem.
MistahBungle said:
The only small issue you might face if you flash stock firmware for a different region is you may not be able to get OTA updates for your region when they're released. But it's easy enough to flash them via Odin so this isn't a massive problem.
Click to expand...
Click to collapse
What if i flash a firmware for a region i will be going to.
Will I get OTA updates if i access the update list from that region ?

[Q] Flashing a different Product Code

Hey peeps,
I flashed a firmware with a different product code to my Lumia 920, and everything works fine. It came with CV-HK but I flashed CV_AU (Australian unbranded).
Just wondering if I will receive OTA updates since the firmware uses a different product code?
I am worried that when Nokia stops allowing users to access NCS, that I will be forever stuck on the current build of the Aussie firmware and wont receive updates (if a future update process checks the product code and blocks the install).
Should I leave it, or should I flash the CV-HK back to the phone just incase?
So I guess that no one has any idea? I've asked everywhere and haven't been able to find an answer.
i think the product code is stored in permanent memory, so likely what will happen is that it will check for OTAs/updates based on your actual product code, basically if you update it will likely just reflash the branded software
Emba4 said:
i think the product code is stored in permanent memory, so likely what will happen is that it will check for OTAs/updates based on your actual product code, basically if you update it will likely just reflash the branded software
Click to expand...
Click to collapse
I cant imagine an OTA update being 1.2 to 1.4GB. That is what it would take to re-flash a different firmware over the existing one.
I thought that it would notice an incorrect Product Code and not update, or hopefully it would just detect the ROM your using and flash the updated version of that.
Wish someone from Nokia/Microsoft could clarify. Time to hit twitter.
Simmo3D said:
I cant imagine an OTA update being 1.2 to 1.4GB. That is what it would take to re-flash a different firmware over the existing one.
I thought that it would notice an incorrect Product Code and not update, or hopefully it would just detect the ROM your using and flash the updated version of that.
Wish someone from Nokia/Microsoft could clarify. Time to hit twitter.
Click to expand...
Click to collapse
Would also like to know. Can't find a South Africa Portico update so want to update to a EU variant atm but don't want to lose the South Africa Portico OTA when it is released.

Hong Kong SGS II Firmware Update?

Hi Guys
I have a SGSII, which I got in Hong Kong a couple of years ago. It came pre-installed with Stock Samsung Firmware ICS 4.0.3. I currently living in the UK and was wondering if I did a Firmware update using Kites, would it install you UK version of the firmware instead of the HK version?
If it's got the HK firmware/CSC on it, it will update to the latest for that region; where you are now is irrelevant, it reads the CSC info off the phone to determine what firmware to upgrade to, assuming there is a later firmware for that region.
But it's a moot point. Why would you use Kies for anything ? Flash whatever stock rom for whatever region you want with Odin.
MistahBungle said:
If it's got the HK firmware/CSC on it, it will update to the latest for that region; where you are now is irrelevant, it reads the CSC info off the phone to determine what firmware to upgrade to, assuming there is a later firmware for that region.
But it's a moot point. Why would you use Kies for anything ? Flash whatever stock rom for whatever region you want with Odin.
Click to expand...
Click to collapse
To be honest, I am a noobie when it comes to the advanced aspects of android devices. So I've always followed the mantra of always following the manufacturer's instructions to the letter. Also I don't want to loose all my user data for my game of Asphalt g

F900U and F900U1 Firmware Links Here

For those who don't know, F900U is the model number of all of the US carrier versions of the Galaxy Fold. The F900U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. A "U to U" or "U1 to U1" flash does not require a factory reset, but changing from one firmware to the other will require one. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.
Manual Odin flashing is designed for those who:
- want to manually update to a newer version of U firmware on their U device, either because they don't want to wait for their carrier's OTA or because OTAs aren't working on their device, or a different carrier got a new feature/patch before they did
- want to flash U1 firmware to their U device
- want to convert from U1 firmware to carrier U firmware
- want to convert from one carrier's U firmware (with all apps and bloatware) to a different carrier's U firmware (with all apps and bloatware)
For those who aren't already aware, anyone can now download firmware for almost any Samsung device any time that they want, via SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But AT&T doesn't allow their firmware to be publicly available (for any of their devices). I pay for a subscription to a site that gets the official releases (usually) before they hit SamFirm/Frija, and also gets me access to AT&T firmware, 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. I'll definitely do at least one build per bootloader level though.
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.
U firmware: https://www.androidfilehost.com/?w=files&flid=293117
U1 firmware: https://www.androidfilehost.com/?w=files&flid=293118
Happy flashing!
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
- My naming method for Android File Host 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 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.
- I pay for a subscription to a site that gets beta builds and also sometimes gets the official releases before they hit SamFirm, so that's where any of my files come from. I will only be posting versions that I get early access to, and USERDATAs that aren't available on SamFirm or Frija (AT&T). The newest/latest firmware files for all carriers other than AT&T can always be obtained via SamFirm and Frija.
- For USERDATAs (all the others are self explanatory):
AIO = Cricket
CCT = Xfinity Mobile (Comcast)
CHA - Spectrum Mobile (Charter)
TMK = Metro PCS
- 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
Interesting development, as we approach the release date for the now-redesigned Fold: U1 firmware has appeared!
I have no idea if they were planning for a U1 model all along, but that firmware never showed up earlier this year. I still haven't seen any new U firmware, but assuming that I get access to at least the launch version before the actual release, I'll post it when I get it
Build SH9 has appeared for the U model, along with an AT&T USERDATA. Files have been uploaded to the OP link
Will SHA get OTA to SH9?
mastibeta said:
Will SHA get OTA to SH9?
Click to expand...
Click to collapse
I don't understand your question.
First of all, numbers come before letters. 9 is older than A. If SH9 and SHA were both released for the same model, then SH9 would come first, and then there would be an OTA to SHA.
But SH9 is U firmware and SHA is U1. You can't OTA to a different model's firmware.
iBowToAndroid said:
I don't understand your question.
First of all, numbers come before letters. 9 is older than A. If SH9 and SHA were both released for the same model, then SH9 would come first, and then there would be an OTA to SHA.
But SH9 is U firmware and SHA is U1. You can't OTA to a different model's firmware.
Click to expand...
Click to collapse
Gotcha, didnt realize the u1 was newer. Do you know what CSC frija would have the u1 firmware under?
mastibeta said:
Gotcha, didnt realize the u1 was newer. Do you know what CSC frija would have the u1 firmware under?
Click to expand...
Click to collapse
XAA is always used for U1 firmware. Manual input is required in order to get it, as of right now. They'll probably change that once the device actually releases
Morning. I cant get these files to download. It's been about 30 min and the download says 6 days.
NEVER MIND. After about an hour it went form six days to finished. Lol.
harsaphes said:
Morning. I cant get these files to download. It's been about 30 min and the download says 6 days.
NEVER MIND. After about an hour it went form six days to finished. Lol.
Click to expand...
Click to collapse
AFH's servers are crap, half of the time. If you ever get a slow download, just reload the link and try a different mirror
Really want to do this but have never flashed any type of Samsung software before. Was checking guides but none of them seemed exact. Don't want to Brick my fold and even though I have AT&T I don't want to be behind on updates and have bloatware.
alexrotondo said:
Really want to do this but have never flashed any type of Samsung software before. Was checking guides but none of them seemed exact. Don't want to Brick my fold and even though I have AT&T I don't want to be behind on updates and have bloatware.
Click to expand...
Click to collapse
It's impossible to brick it. And yes, there are tons of very precise and exact Odin flashing guides here on XDA. Odin flashing is always pretty much the same process, no matter the model. Put the phone in Download, make sure you have the right Odin version, extract the zip, load all the files, plug the phone in, and click Start
What is the site you pay a subscription for?
I have a small question... will I brick the Fold, if I flash this to the Korean Version of the Fold (SM-F907N)?
The only version I could buy in where I live is the Korean version, which is a 5G model, but I really want to use my credit cards from USA. I guess I have to have a Fold with USA firmware to use Samsung Pay with credit card from USA, but I don't know what would happen if I flash this firmware... I am okay with losing the 5G, I just want the Samsung Pay works with my credit cards...
STEVEcKONG said:
I have a small question... will I brick the Fold, if I flash this to the Korean Version of the Fold (SM-F907N)?
The only version I could buy in where I live is the Korean version, which is a 5G model, but I really want to use my credit cards from USA. I guess I have to have a Fold with USA firmware to use Samsung Pay with credit card from USA, but I don't know what would happen if I flash this firmware... I am okay with losing the 5G, I just want the Samsung Pay works with my credit cards...
Click to expand...
Click to collapse
You can't flash it. Odin won't allow you to, because those models are not cross compatible. If you want a Fold that does US Samsung Pay, buy one from the US and have it shipped to you
iBowToAndroid said:
You can't flash it. Odin won't allow you to, because those models are not cross compatible. If you want a Fold that does US Samsung Pay, buy one from the US and have it shipped to you
Click to expand...
Click to collapse
Thanks a lot!
Hmm....after I download the F900U1 file the folder says 'empty'.
On the download link the U1 folder says no files. Am I looking in the wrong place?
Trying this again.
OK GOT IT. THANKS
harsaphes said:
On the download link the U1 folder says no files. Am I looking in the wrong place?
Click to expand...
Click to collapse
You must be. I can see it perfectly clear, when I click the U1 link in the OP
Any update on successfully flashed u1 firmware on att fold? Wanting to pick up unlocked one but only the att version is available
I just did mine . If you need help let me know
svickory said:
I just did mine . If you need help let me know
Click to expand...
Click to collapse
sent you a message, have a question or two.

Regarding not receiving OTA updates

It's my first time here, and much of this is new to me.
Anyways, I have an S21 (Snapdragon) with Multi-CSC? OYN, XAA/XAA/XAA that I use in Singapore. (SM-G991U)
I just learnt that apparently OTA updates are only given after the location of where the device is being used corresponds with the CSC.
What would my options be now, to update my phone? (Being able to have OTA updates would be preferable)
I know of (just learnt):
• Changing CSC via the phone app (using IMEI number). Never tried and I don't know if I'll get an error code. My main concern is that I'll not be able to update if I get firmware for Exynos instead (S21s in Singapore are Exynos), if I even get a Singaporean CSC on there.
• Flashing/ updating using Odin? (Heard it doesn't work anymore for changing CSC? I have One UI 3.1)
• Updating using ADB?
I'd love to learn something about this whole CSC mess too so I can understand what's happening and how everything works. And if it's not possible to get OTA updates, the best way to update my phone then. Thanks
mavcyh said:
It's my first time here, and much of this is new to me.
Anyways, I have an S21 (Snapdragon) with Multi-CSC? OYN, XAA/XAA/XAA that I use in Singapore. (SM-G991U)
I just learnt that apparently OTA updates are only given after the location of where the device is being used corresponds with the CSC.
What would my options be now, to update my phone? (Being able to have OTA updates would be preferable)
I know of (just learnt):
• Changing CSC via the phone app (using IMEI number). Never tried and I don't know if I'll get an error code. My main concern is that I'll not be able to update if I get firmware for Exynos instead (S21s in Singapore are Exynos), if I even get a Singaporean CSC on there.
• Flashing/ updating using Odin? (Heard it doesn't work anymore for changing CSC? I have One UI 3.1)
• Updating using ADB?
I'd love to learn something about this whole CSC mess too so I can understand what's happening and how everything works. And if it's not possible to get OTA updates, the best way to update my phone then. Thanks
Click to expand...
Click to collapse
Hi Mate
OTA are strictly Active CSC related , independent of the country you are using the phone. I have Spanish active CSC and i get the OTA in Panama
So you will get a new OTA as soon as available , the latest for you CSC (XAA) firmware is:
Date
Version
2021-06-27
11
PDA
CSC
G991U1UEU4AUF5
G991U1OYM4AUF5
https://www.sammobile.com/samsung/galaxy-s21/firmware/SM-G991U1/XAA/download/G991U1UEU4AUF5/1557396/
https://www.sammobile.com/samsung/galaxy-s21/firmware/SM-G991U1/XAA/download/G991U1UEU4AUF5/1557396/
You can change the CSC but it will depend in what firmware you have and what CSC available that firmware has.
To your questions
1 You will not get an Exynos firmware in your phone as you can not force an exynos CSC into an Snapdragon , Singapore does not have Snapdragon firmware , so you can not force a Singapore CSC into your phone
2 Flashing new firmware does not change the CSC anymore ( in my case did not)
3 Update with ADB ? not sure what you mean but if you mean firmware , no is not possible
MAX 404 said:
Hi Mate
OTA are strictly Active CSC related , independent of the country you are using the phone. I have Spanish active CSC and i get the OTA in Panama
So you will get a new OTA as soon as available , the latest for you CSC (XAA) firmware is:
Date
Version
2021-06-27
11
PDA
CSC
G991U1UEU4AUF5
G991U1OYM4AUF5
https://www.sammobile.com/samsung/galaxy-s21/firmware/SM-G991U1/XAA/download/G991U1UEU4AUF5/1557396/
https://www.sammobile.com/samsung/galaxy-s21/firmware/SM-G991U1/XAA/download/G991U1UEU4AUF5/1557396/
You can change the CSC but it will depend in what firmware you have and what CSC available that firmware has.
To your questions
1 You will not get an Exynos firmware in your phone as you can not force an exynos CSC into an Snapdragon , Singapore does not have Snapdragon firmware , so you can not force a Singapore CSC into your phone
2 Flashing new firmware does not change the CSC anymore ( in my case did not)
3 Update with ADB ? not sure what you mean but if you mean firmware , no is not possible
Click to expand...
Click to collapse
Thanks for the reply. Problem is, I've constantly checked for updates but I'm still stuck on the February patch which should actually have even came preinstalled on the phone. (basically, I've not received a single OTA update). This has led me to believe that the country you use your phone in affects receiving OTA updates.
I doubt there's other reasons why I wouldn't receive the updates (since other people have said that location/ connecting to the telco network? affects OTA updates).
Anyways, so to clarify, my only options to update then would be to use:
• Smart Switch (holding off because it is disabled from an app having device ownership)
• ADB (sideloading OTA update)
• Odin (unfamiliar with its uses)
I'm just looking for the path of least resistance to get my phone updated right now. And just to confirm, updating/ flashing (are they the same?) software will not wipe my phone?
Thanks.
mavcyh said:
Thanks for the reply. Problem is, I've constantly checked for updates but I'm still stuck on the February patch which should actually have even came preinstalled on the phone. (basically, I've not received a single OTA update). This has led me to believe that the country you use your phone in affects receiving OTA updates.
I doubt there's other reasons why I wouldn't receive the updates (since other people have said that location/ connecting to the telco network? affects OTA updates).
Anyways, so to clarify, my only options to update then would be to use:
• Smart Switch (holding off because it is disabled from an app having device ownership)
• ADB (sideloading OTA update)
• Odin (unfamiliar with its uses)
I'm just looking for the path of least resistance to get my phone updated right now. And just to confirm, updating/ flashing (are they the same?) software will not wipe my phone?
Thanks.
Click to expand...
Click to collapse
Hi
Is hard to say what really going on , as i said I have an active CSC from one country and live in another and get the OTA with no problem ( lot of people do)
Easiest option for me would be doing updates manually with odin , download the correct firmware and flash using the home-csc file , that way the phone will not be wipe , will be like a regular OTA
Check this threads , here and here even if the thread talks about an exynos the procedure is still valid for a snapdragon
I still dont get OTAs. I flahed BTU, PHE and OXD but nothing. anyone else facing this?
I flahed with odin.

Categories

Resources