Related
Hi there,
Apologies if this is the wrong section or if it has already been posted.
I recently acquired an 8500 from Overseas (Middle East region) which doesn't seem to hold a stable 2G or 3G signal here in Australia (both before and after the update - see below).
I am normally an Android guy, and with Android you have the ability to flash different radios/modems/basebands btu I cant seem to find this anywhere. Is the radio automatically upgraded when flashing a new firmware?
I just (literally hours ago) upgraded to KL6 but it seems the radio hasnt changed.
WHen I type in *#5239870*# into the phone this is what I got both before KL6 and after.
Pre flash to KL6
S8500+JP+JH1
Modem:
SHP: VPP R5 2.1.1
CSC: S8500OJPJG1
Post flash to KL6
S8500+XX+KL6
Modem:
SHP: VPP R5 2.1.1
CSC: S8500OXAKL6
Note in both cases, there is nothing next to Modem
Is there a repository of radio files that is out there (for the life of me, no amount of google or xda searches have found anything)?
Any Australian users out there care to share what modem they have?
Hello sabaramo
About 3G signals in Australia
This was requested a while ago
you can see the solution right here : http://forum.xda-developers.com/showpost.php?p=20068355&postcount=26
And the result right here : http://forum.xda-developers.com/showpost.php?p=20071719&postcount=27
That was for bada 1.2
Nothing available for 2.0 yet
Best Regards
Thanks, I am getting 3G but its just seems unstable.
Can I flash that same amss.bin from the argentinian 1.2 with my KL6 bada 2.0 firmware?
Frankenware 1.2.0
you can try but honestly i doubt that it will work
Best Regards
Right, MyLove90. I just went through the same thing with Bada 2.0 flashed on a Bell Mobility Canada S8500M that I am trying to use in Thailand.
Step 1 - Try amss.bin from DXKE1 firmware with Bada 2.0. - No boot up - freezes on flashing SIM image.
Step 2 - Try to flash DXKE1 complete firmware. This is a downgrade from Bada 2.0 to Bada 1.2. Also set Preconfiguration to THL (Thailand) from default KOR.
Now the phone boots up, but it it cannot be used with the GSM network. Why is this? GSM is a world phone, right? People travel all over the world with their GSM phones and just buy local SIMs while travelling don't they? I had no trouble at all with this when I first brought my T-Mobile G1 phone from the US here. I just popped in the same AIS SIM and it worked fine with no fiddling with the phone at all.
By the way, my Thai carrier is AIS, and setting preconfig to THL makes this a fully AIS phone. AIS menu options and Mobile AP settings, etc that were not there before now appear all over the phone menus.
When trying to dial, I get the no network service error. If I try to select network manually, or access the SIM for a contact phone number or to set a PIN lock, the message changes to "Emergency Calls Only".
So I'm starting to think that I have a defective phone with bad radio, but I figure, well, I can dial 911 with no harm because here emergency is 191. So I dial 911 and the phone dials and starts ringing. Oops! So I hang up so I won't get in trouble, but at least the phone works!
So what's wrong? I went to AIS and after playing with the menus and trying one of their SIMs, they blame the phone not being from Thailand, but as far as I can see, after the Thai firmware flash, this phone is the same as what Samsung shipped to AIS themselves. There are no SIM locks or any reason the phone shouldn't work.
Any ideas? Am I missing something?
can you please mention full info about your very first firmware maybe i can get it for you from Check fus or Slyfer ??
S8500M model is not available at all on Slyfer ...I just heard about it today
You can see...i am from Egypt and here we don't have branding or network lock and such stuff
So all what i can do right now is getting your old firmware for your so your phone work again
Best Regards
Wow! I never even thought about that being a solution!
S8500MUGJF5/S8500MBMCJF5 (BMC)
Thanks!
I found this page : http://www.anysvc.mobi/categories.php?cat_id=2731&sessionid=4bqbt21kclnrg2m92fvo9qkhq6
I think you need to register to download
I am totally disappointed
Slyfer & Check fus don't have such product code !
Best Regards
mylove90 said:
I found this page : http://www.anysvc.mobi/categories.php?cat_id=2731&sessionid=4bqbt21kclnrg2m92fvo9qkhq6
I think you need to register to download
I am totally disappointed
Slyfer & Check fus don't have such product code !
Best Regards
Click to expand...
Click to collapse
You also have to pay upwards of €100 per download, not sure if the CSC is included for that price either. I know because I bought 2 firmwares several months ago.
sabaramo, it sounds to me like your phone is not a 8500T or a 8500M model. Thus unless you are with Telstra, using the Argentinan modem file wouldn't be recommended as you would be changing your broadband frequencies.
Who is your telco?
Let me have another try with SamMobile this time
Maybe our admin add support for Canadian Wave
Please don't pay for a firmware again
Best Regards
mylove90 said:
I found this page : (anysvc.mobi eGSM)
I think you need to register to download
I am totally disappointed Slyfer & Check fus don't have such product code !
Click to expand...
Click to collapse
You are so right mylove90! This experience is starting to bring back memories. I've been using my G1, so this phone has been put aside since I got it, but now I'm remembering how hard it was to find the original ROM. KrazyKong is right. It is 120 euros to download from that site. But with your help and suggestion, I started additional searching.
First I found this service tech offering to share it for a fee because he bought it too. I remember finding him last time I looked for the FW:
http://tinyurl.com/83w3q8k
He's actually on the second page of that thread, and I saw him around other forums last time I searched that firmware too. Other than the pay services, he's the only private party that comes up on that firmware search.
Still, I decided to search the FW name again to see if it crops up anywhere else for download. Actually, after a lot of practice with these searches, I'm starting to learn that Google isn't too useful, and that searching file servers like Megaupload directly are more useful, and those all panned out negative, as I expected since that firmware was non-existent last year too.
But searching that ROM number did find a fresh post from someone with the exact same phone as me and the exact same problem. It's really timely because he just posted the problem 5 days ago and found the answer 3 days ago.
http://tinyurl.com/7x25ags
In a nutshell, he recommends the Brazilian firmware because it has the same bands as our Bell Canada S8500M phones. I gave a try first just to flash the amss.bin file over my Thai firmware, but no luck. I am thinking it is because the Thai firmware I installed is Bada 1.2 and the Brazilian is 1.0.
So next I tried to flash the Open Brazil he recommended (but didn't work on his phone) because I didn't want to try the branded one first. That was unsuccessful because it's not a full firmware and I got error messages in downloading. I'm guessing again it's because I'm trying to load Bada 1.0 over 1.2.
Still, before going to the branded (Vivo Brazil) firmware, I took another look at samobile.com/firmware and found 2 similar Brazil ROMs misfiled under North America. But more hopefully, I found another "U" series ROM: S8500L UHJL1 (Bada 1.0)
I was hopeful for this because my Bell Canada phone is similar: S8500M UGJF5
Because of the common "U" prefix, or the close UH/UG combination, I had hopes that this might be a correct firmware belonging to my Canadian hardware, but for the other Canadian Wave provider/carrier, Rogers.
While I was flashing, I noticed the file name protocols for firmware files and saw that the Brazil file had "Open Brazil" embedded in the file name, so I checked the corresponding file name in this ROM and found CI Entel PCS, which is a provider in Claro, Chile. This corresponds well with the other firmware for S8500L, VCKH1, for Claro, Argentina.
So anyway, after finishing the flash, my phone is working again thanks to your tips and suggestions to point the way.
Thinking about the theory behind this, I have to ask why the regular telephony GSM bands didn't work regardless of firmware, or why flashing different amss.bin files didn't correct the problem.
The only thing I can conclude is that these S8500M phones have a different modem to accomodate Bell Mobility Canada and need firmware to support the oddball hardware. Fortunately this same hardware is available in other countries as well. This procedure also changed my phone to an S8500B.
my head is going to explode
WTH all these brands for
Why it isn't just a normal phone ?!
But still i have curioustiy to get that damn firmware for free
Thanks for explaning...maybe others can use this
Best Regards
I won't be paying for another firmware no. But the branded firmware I was after could not be located any other way than by paying and going through www.anysvc.mobi
mylove90 said:
my head is going to explode
WTH all these brands for
Why it isn't just a normal phone ?!
But still i have curioustiy to get that damn firmware for free
Thanks for explaning...maybe others can use this
Click to expand...
Click to collapse
Yeah, I understand the feeling mylove90. It had my head spinning too. This has been a big learning experience for me too. Like you, I just imagined all the phones were the same, and that having the right firmware would make it work anywhere in the world.
I can only guess, but I'm thinking a lot of non-standard telecommunications equipment is out there with the carriers, and Samsung just tries to accomodate their needs for hardware variations so they can make the sales.
A consequence of all this is that I have lost Badadroid. I used Rebellos' Bada 2.0 fota to install Badadroid the first time and everything worked fine. Now I need to set it up with Bada 1.0. Of course, this firmware isn't on the supported list in the tutorial, but I tried a couple of fixes posted in the thread.
First I installed the bootloaders that are supposed to enable you to run the regular TUT fota on any firmware version. I don't remember off hand what post I got them from, but they installed fine and did not disrupt my phone at all.
Next I tried to install the fota for Bada 2.0, but it doesn't work, giving a fota erase error. I suppose again this is a consequence of trying to mix Bada 2.0 files with Bada 1.0.
So, since I supposedly have the boot files that work with the TUT fota on any firmware, I went ahead and flashed the regular TUT fota. It will not start Android. It goes straight to Bada.
So then I got Rebellos new universal boot fota that is also supposed to run any firmware here:
http://forum.xda-developers.com/showthread.php?t=1020444&page=34
http://code.google.com/p/badadroid/downloads/detail?name=S8500_bl_univ_boot_v2.3.zip
It does not work either, booting straight to Bada.
Any ideas? I hate to lose Android on this phone.
Also, if you find that Canadian firmware for free, let me know. I would like a copy in case I ever need to restore the phone to original.
You are trying with bada 1.0 !!
Fota won't work for sure because it is not supported at all
Also bada 2.0 Fota may have a different address
Universal fota may have or may not have your bootloader address it use
Flash XXJEE bootloader because i am sure it is supported
I think it will work as normal bootloader
S8500XXJEE bootloader : http://code.google.com/p/badadroid/downloads/detail?name=S8500XXJEE_BL.zip&can=4&q=
Also you may need to patch apps_compressed.bin to make it support fota
About patching apps
You can use mijona's app : http://forum.xda-developers.com/showpost.php?p=15159642&postcount=309
You have to use it through windows cmd....place it with apps file you want to patch...go to that path from cmd and write command as following
App_ena.exe <inputfile> <outputfile>
Example : App_ena.exe apps_compressed.bin patched_apps_compressed.bin
or read my post and try to do it yourself : http://forum.xda-developers.com/showpost.php?p=15151700&postcount=300
I think mijoma did a good job already
Best Regards
mylove90 said:
You are trying with bada 1.0 !!
Fota won't work for sure because it is not supported at all
Also bada 2.0 Fota may have a different address
Universal fota may have or may not have your bootloader address it use
Click to expand...
Click to collapse
That's what I was thinking in my process of trial and error. I felt like the OS was protecting itself judging by the nature of the MultiLoarder error messages, so I wasn't worried about bricking the phone as I tried to see what the phone would and wouldn't tolerate.
Flash XXJEE bootloader because i am sure it is supported
I think it will work as normal bootloader
S8500XXJEE bootloader : (URL)
Click to expand...
Click to collapse
Okay. I put those in. The phone accepted them and continued to boot just fine, but there is still no Android boot, so on to the next step:
Also you may need to patch apps_compressed.bin to make it support fota
About patching apps
You can use mijona's app : (URL)
You have to use it through windows cmd....place it with apps file you want to patch...go to that path from cmd and write command as following
App_ena.exe <inputfile> <outputfile>
Example : App_ena.exe apps_compressed.bin patched_apps_compressed.bin
or read my post and try to do it yourself : (URL)
I think mijoma did a good job already
Click to expand...
Click to collapse
Okay, so true! It's been a long time since I have edited files in hexadecimal, so that's nice. I don't mind hex editing, but I haven't poked around with Wave Remaker to get a feel of how to operate in it, so I appreciate mijona's file.
Navigating in cmd is a nice time to do work in C:\ !!!
So that was fun, but flashing patched_apps.compressed.bin made the phone stop booting. So I went on to another route.
Somehow I still had a tab for this thread open from my amss.bin research. These guys are struggling with the same issue in Bada 1.2:
http://forum.xda-developers.com/showthread.php?t=1313675&page=3
Particularly this post gave me a lead on a solution:
http://forum.xda-developers.com/showpost.php?p=20068355&postcount=26
I didn't follow their approach of mixing firmware files though.
Since the CSC file is also a "U" series ROM from Latin America, and in fact closely related to the CI Entel PCS from Claro, Chile firmware that I had already used to successfully get my phone working, I decided to use the entire firmware to reflash my phone with the indicated firmware: S8500LVCKH1
This firmware has no bootfiles, so I used the ones you gave me above. This flash was successful as far as the phone booting okay and working with my carrier. I was surprised to see all my setup options and changes still preserved after the flash. I expected to lose everything on a Full Download flash. I only lost the numbers I store in Contacts for the service menus. This firmware changes my phone to an S8500L. I lose the cute Bada animation for a cheesy Claro animation, and get a stupid message everytime reminding me that data charges can be expensive. If you know how to change the animation back and get rid of the message, it would be nice!
Since this is a Bada 1.2 firmware, I was hoping for this solution to get BadaDroid running again. Unfortunately there is no Android first boot with the power+menu+vol up command. It goes directly and immediately to Bada first.
I tried this both with the Rebellos' Universal Boot 2.3 fota
http://code.google.com/p/badadroid/downloads/detail?name=S8500_bl_univ_boot_v2.3.zip
And I also tried it with the TUT fota, but neither one will boot Android.
Any more ideas?
Of course, all this progress is possible because of your help. Thanks.
This time i had to know what i am dealing with so i downloaded that firmware
and as i thought Apps_compressed.bin needs to be patched
flash the patched file from an old multiloader let's say 5.62 so you won't get errors
If after flashing the file your phone didn't restart please don't panic
Just turn it off then on and it will be fine
Don't use fota made for bada 2.0 please....use the one from the tutorial
About Power On/Off animation
We got a great thread made by adfree in which he explains everything : http://forum.xda-developers.com/showthread.php?t=944620
An advice : Use latest Wave Remaker because it is so cool in this part
You can even make your very own animation
Believe it or not
bada hacking is more cool than the whole Android thing to me and more fun but needs someone who really try to do it
Best Regards
Okay! Thank You MyLove90! You have really made a happy day for me today!
Patching this binary did fix my Android boot, and I spent the rest of the afternoon re-installing all my Android apps.
I miss Bada 2.0, but it wasn't completely functional, so I actually have a better phone now that I have gone back to Bada 1.2.
Even though the Android port isn't complete, it is more fun than my T-Mobile G1 because I haven't upgraded Android yet. Now that I have the Wave working right, I'll go ahead and update the G1 too.
I found this post from mijoma as to possibly why the patch didn't fix my Bada 1.0 install:
"It's also problematic with loading patched version using new bootloaders."
http://forum.xda-developers.com/showpost.php?p=15206739&postcount=1240
Of course, I used the same bootloaders you gave me for both the 1.0 and 1.2 installs, but maybe it was an issue of 1.0 compatibility.
I appreciate your appraisal of Bada. Before I got the Wave, I read rave reviews of Bada, so I didn't mind owning a Bada phone. I just need some Android apps when I'm out, so this phone is working great for me as is. It will be nice if the port is properly finished, but I'm glad I have what they have done.
Thanks also for the animation thread. I'll look into it and Wave Remaker more.
Bell wave firmware
Hi members. A couple days ago I found the S8500MUGJF5 firmware for free. Since I am new I can't post a link but I found it on hotfile website. Anyone that needs this firmware can go there for it.
---------- Post added at 12:59 PM ---------- Previous post was at 11:59 AM ----------
PJK2011 said:
Right, MyLove90. I just went through the same thing with Bada 2.0 flashed on a Bell Mobility Canada S8500M that I am trying to use in Thailand.
Step 1 - Try amss.bin from DXKE1 firmware with Bada 2.0. - No boot up - freezes on flashing SIM image.
Step 2 - Try to flash DXKE1 complete firmware. This is a downgrade from Bada 2.0 to Bada 1.2. Also set Preconfiguration to THL (Thailand) from default KOR.
Now the phone boots up, but it it cannot be used with the GSM network. Why is this? GSM is a world phone, right? People travel all over the world with their GSM phones and just buy local SIMs while travelling don't they? I had no trouble at all with this when I first brought my T-Mobile G1 phone from the US here. I just popped in the same AIS SIM and it worked fine with no fiddling with the phone at all.
By the way, my Thai carrier is AIS, and setting preconfig to THL makes this a fully AIS phone. AIS menu options and Mobile AP settings, etc that were not there before now appear all over the phone menus.
When trying to dial, I get the no network service error. If I try to select network manually, or access the SIM for a contact phone number or to set a PIN lock, the message changes to "Emergency Calls Only".
So I'm starting to think that I have a defective phone with bad radio, but I figure, well, I can dial 911 with no harm because here emergency is 191. So I dial 911 and the phone dials and starts ringing. Oops! So I hang up so I won't get in trouble, but at least the phone works!
So what's wrong? I went to AIS and after playing with the menus and trying one of their SIMs, they blame the phone not being from Thailand, but as far as I can see, after the Thai firmware flash, this phone is the same as what Samsung shipped to AIS themselves. There are no SIM locks or any reason the phone shouldn't work.
Any ideas? Am I missing something?
Click to expand...
Click to collapse
I have a problem similar to PKJ2011. I have an unlocked Bell Canadian wave with firmware S8500MUGJF5. I am using it in Barbados with that firmware on a 2G GSM900 network. I flashed it with S8500XXKL6 Euro firmware and now it is not getting signal on the 2G GSM900 band. When I do a network search it picks up the 2G GSM1900 band but it has a circle with a slash in it. Is there anything I can do to get it working with the Euro bada 2.0 firmware on the 2G GSM900 band since this phone is a quadband phone?
asmythy said:
Hi members. A couple days ago I found the S8500MUGJF5 firmware for free. Since I am new I can't post a link but I found it on hotfile website. Anyone that needs this firmware can go there for it.
Click to expand...
Click to collapse
Thanks for the tip. All three links go to usenet. They offer a free trial period, but you have to sign up for an account and give a payment method, so I'll pass for now. It's good to know the resource is there if needed.
I have a problem similar to PKJ2011. I have an unlocked Bell Canadian wave with firmware S8500MUGJF5. I am using it in Barbados with that firmware on a 2G GSM900 network. I flashed it with S8500XXKL6 Euro firmware and now it is not getting signal on the 2G GSM900 band. When I do a network search it picks up the 2G GSM1900 band but it has a circle with a slash in it. Is there anything I can do to get it working with the Euro bada 2.0 firmware on the 2G GSM900 band since this phone is a quadband phone?
Click to expand...
Click to collapse
You have to wait for Bada 2.0 to be released for one of the carriers that uses our same modem. This includes some carriers in Australia and South America like Brazil, Chile, and Argentina. So I had to downgrade to Bada 1.2 to keep my phone working. I used Claro in Argentina.
I currently have the US s20Ultra unlocked model on ATT (don't foresee changing carriers). Currently I am missing features like VoLTE and VVM. What other features would I be missing if I stay on the unlocked firmware? Can I flash the ATT firmware to get those missing features? Can I flash back to unlock?
Thank you
What's the CSC on your device?
varcor said:
What's the CSC on your device?
Click to expand...
Click to collapse
I am not sure what I am looking for. Its currently on ATT/ATT.
Open your dialer, enter *#1234#, press the Dial Icon. You'll see CSC: G98??, the next 3 letters will be your device's CSC Code. Your Service Provider's CSC is "ATT" which is different than the CSC in your device. Whether or not you can change the CSC depends on your device's CSC. Device firmware is always configured for the specific, original CSC or Multi CSC's.
This post may be the best workaround.
https://forum.xda-developers.com/showpost.php?p=82444733&postcount=8
varcor said:
Open your dialer, enter *#1234#, press the Dial Icon. You'll see CSC: G98??, the next 3 letters will be your device's CSC Code. Your Service Provider's CSC is "ATT" which is different than the CSC in your device. Whether or not you can change the CSC depends on your device's CSC. Device firmware is always configured for the specific, original CSC or Multi CSC's.
This post may be the best workaround.
https://forum.xda-developers.com/showpost.php?p=82444733&postcount=8
Click to expand...
Click to collapse
My CSC: G988U1OYM1ATE4
garyHal said:
My CSC: G988U1OYM1ATE4
Click to expand...
Click to collapse
Your device has Multiple CSC's which are included in OYM so you should be able to change your CSC to ATT, which is the CSC for AT&T.
Go to "Settings" then "About phone". Write down your IMEI Number. Open dialer and enter *#272*IMEInumber# (In the thread replace IMEInumber with your actual IMEI Number). Press the Dial Icon, you should see a screen with the list of available CSC codes for your device. Select ATT and tap the Install option.
Be aware your firmware isn't AT&T, it's unbranded so even if you change the CSC, full call functionality may not be available. You can obtain AT&T's firmware at SamMobile.
https://www.sammobile.com/samsung/galaxy-s20-ultra/firmware/SM-G988U1/ATT/
varcor said:
Your device has Multiple CSC's which are included in OYM so you should be able to change your CSC to ATT, which is the CSC for AT&T.
Go to "Settings" then "About phone". Write down your IMEI Number. Open dialer and enter *#272*IMEInumber# (In the thread replace IMEInumber with your actual IMEI Number). Press the Dial Icon, you should see a screen with the list of available CSC codes for your device. Select ATT and tap the Install option.
Be aware your firmware isn't AT&T, it's unbranded so even if you change the CSC, full call functionality may not be available. You can obtain AT&T's firmware at SamMobile.
https://www.sammobile.com/samsung/galaxy-s20-ultra/firmware/SM-G988U1/ATT/
Click to expand...
Click to collapse
Varcor, thank you so much for all the directions.
As it stands right now, it is already on ATT. Once I flash over to the ATT firmware, would I be able to flash back to an unbranded one in the future, for whatever reason? Additionally, do I have to stay on the ATT firmware to retain those features? Or could just having my phone communicate with ATT at least once with my "branded" phone and then flash back retain those features?
garyHal said:
Varcor, thank you so much for all the directions.
As it stands right now, it is already on ATT. Once I flash over to the ATT firmware, would I be able to flash back to an unbranded one in the future, for whatever reason? Additionally, do I have to stay on the ATT firmware to retain those features? Or could just having my phone communicate with ATT at least once with my "branded" phone and then flash back retain those features?
Click to expand...
Click to collapse
You're most welcome. Yes, flashing back to unbranded won't be a problem. I don't think you will be able to retain the features if you go back to the unbranded firmware, it's not configured to allow full call feature functionality. Also, after flashing to the AT&T firmware you may need to contact their CSR for external programing. Good luck!
S20+ AT&T
Hi Varcor,
I'm new in this firmware things. I'm from Singapore and has been using S20 Exynos, but due to the extreme heat, bad battery life,etc. I've decided to import S20+ Snapdragon from AT&T, according to the Service provider SW ver information, it's showing as SAOMC_SM-G986U-OYN_ATT_QQ_0023 (I believe this means the set are unlocked).
With that said, I noticed that the software is outdated and the security patch level is on February 1,2020. when I referring to the AT&T website, It's showing as the latest software is QP1A.190711.020.G986USQU1ATE6 (June update) and mine still on QP1A.190711.020..G986USQU1ATAW (February). My CSC is G986UOYN1ATAW.
My question now is, whenever I tried to hit the software update, it's keep telling me that my software is up to date. Is there's a reason why it's wont detect the update? If it's because I'm in Singapore not US, then there's no choice that I need to flash using the firmware from Sammobile. The problem is which one that I need to download as AT&T carrier is not listed there. There's only T-mobile, Sprint, Unknown, USA. Please help.
https://www.sammobile.com/samsung/galaxy-s20-plus/firmware/#SM-G986U
Raigar said:
Hi Varcor,
I'm new in this firmware things. I'm from Singapore and has been using S20 Exynos, but due to the extreme heat, bad battery life,etc. I've decided to import S20+ Snapdragon from AT&T, according to the Service provider SW ver information, it's showing as SAOMC_SM-G986U-OYN_ATT_QQ_0023 (I believe this means the set are unlocked).
With that said, I noticed that the software is outdated and the security patch level is on February 1,2020. when I referring to the AT&T website, It's showing as the latest software is QP1A.190711.020SAOMC_SM-G986U-OYN_ATT_QQ_0023 (June update) and mine still on QP1A.190711.020..G986USQU1ATAW (February). My CSC is G986UOYN1ATAW.
My question now is, whenever I tried to hit the software update, it's keep telling me that my software is up to date. Is there's a reason why it's wont detect the update? If it's because I'm in Singapore not US, then there's no choice that I need to flash using the firmware from Sammobile. The problem is which one that I need to download as AT&T carrier is not listed there. There's only T-mobile, Sprint, Unknown, USA. Please help.
https://www.sammobile.com/samsung/galaxy-s20-plus/firmware/#SM-G986U
Click to expand...
Click to collapse
I would reach out to SamMobile and inquire why they're not listing the AT&T Firmware Update. You state your CSC is G986UOYN1ATAW. That CSC is also associated with T-Mobile. You're not using an AT&T SIM Card, correct? On a Multi-CSC Device when you insert a different SIM, the device should update to the correct Service Provider. If you're using a SIM from a Service Provider other than AT&T you probably won't receive AT&T Software Updates, which are distributed by Samsung, not AT&T via OTA.
varcor said:
I would reach out to SamMobile and inquire why they're not listing the AT&T Firmware Update. You state your CSC is G986UOYN1ATAW. That CSC is also associated with T-Mobile. You're not using an AT&T SIM Card, correct? On a Multi-CSC Device when you insert a different SIM, the device should update to the correct Service Provider. If you're using a SIM from a Service Provider other than AT&T you probably won't receive AT&T Software Updates, which are distributed by Samsung, not AT&T via OTA.
Click to expand...
Click to collapse
I did try to reach them, but for some reason they are giving me some irrelevant answer. Something like "You probably don't get OTA-updates (otherwise you got them already from AT&T)". We are having a conversation breakdown there, I think they are not an english speaker (or my english is just bad). Really? that CSC is associated with T-Mobile? now I'm getting more confused because the box is stated AT&T and it's sealed.
I'm using Singapore SIM card (Singtel), so you were saying this set I'm using right now is a Multi-CSC device? If i were to flash to the other carrier firmware, will it create any problem?
Raigar said:
I did try to reach them, but for some reason they are giving me some irrelevant answer. Something like "You probably don't get OTA-updates (otherwise you got them already from AT&T)". We are having a conversation breakdown there, I think they are not an english speaker (or my english is just bad). Really? that CSC is associated with T-Mobile? now I'm getting more confused because the box is stated AT&T and it's sealed.
I'm using Singapore SIM card (Singtel), so you were saying this set I'm using right now is a Multi-CSC device? If i were to flash to the other carrier firmware, will it create any problem?
Click to expand...
Click to collapse
Flashing Singtel Firmware won't work since it's configured for the Exynos SoC. Multi-SIM Devices have only regional Service Providers available, you don't have Singtel as an option in an AT&T device. Based on your situation I would consider one of two options. The first would be insert an AT&T SIM just for OTA updates. Not sure if you received an AT&T SIM when you purchased the device, if you didn't they're not hard to find. The second and likely best option is sell the device and purchase a Global Variant with a Snapdragon SoC, you'll receive updates regardless of your Service Provider. If it makes you feel any better there's lots of users in the same predicament. They want the Snapdragon device in regions selling mainly Exynos devices. Workarounds are in many situations are challenging,
varcor said:
Your device has Multiple CSC's which are included in OYM so you should be able to change your CSC to ATT, which is the CSC for AT&T.
Go to "Settings" then "About phone". Write down your IMEI Number. Open dialer and enter *#272*IMEInumber# (In the thread replace IMEInumber with your actual IMEI Number). Press the Dial Icon, you should see a screen with the list of available CSC codes for your device. Select ATT and tap the Install option.
Be aware your firmware isn't AT&T, it's unbranded so even if you change the CSC, full call functionality may not be available. You can obtain AT&T's firmware at SamMobile.
https://www.sammobile.com/samsung/galaxy-s20-ultra/firmware/SM-G988U1/ATT/
Click to expand...
Click to collapse
Varcor
I have the exact same phone and using the same network as garyHal, unlocked 988U1/OYM/ATT.
I got my bootloader unlocked and decided to apply the ATT firmware (
G988U1UES1BTJ2). My CSC was already ATT so I didn't perform the csc install step.
After setting the phone up as new, it still seems like its running the unlocked mode. I don't see any kind of branding or extra ATT stuff that may have been downloaded. How do I verify that I have the right firmware and CSC set to ATT?
Thank you.
itchyUnder said:
Varcor
I have the exact same phone and using the same network as garyHal, unlocked 988U1/OYM/ATT.
I got my bootloader unlocked and decided to apply the ATT firmware (
G988U1UES1BTJ2). My CSC was already ATT so I didn't perform the csc install step.
After setting the phone up as new, it still seems like its running the unlocked mode. I don't see any kind of branding or extra ATT stuff that may have been downloaded. How do I verify that I have the right firmware and CSC set to ATT?
Thank you.
Click to expand...
Click to collapse
How did you manage to unlock your bootloader since US Snapdragon variants are locked down pretty tight? I don't think the firmware is dedicated to ATT, it's Multi CSC, designed to function with a number of US Carriers. You should be delighted you're not suffering with ATT bloatware! To check the Active CSC go to About Phone, Settings, Software Information, Service Provider SW ver. On the bottom string the first three letters are the Active CSC on your device. You can review this article for additional information on Firmware and CSC's.
CSC and Home_CSC | All You Need to Know About ODIN Samsung Flash
Here is all you need to know about the CSC and Home_CSC.What exactly is a Firmware?A firmware is nothing but a permanent software which is programme
www.getdroidtips.com
varcor said:
How did you manage to unlock your bootloader since US Snapdragon variants are locked down pretty tight? I don't think the firmware is dedicated to ATT, it's Multi CSC, designed to function with a number of US Carriers. You should be delighted you're not suffering with ATT bloatware! To check the Active CSC go to About Phone, Settings, Software Information, Service Provider SW ver. On the bottom string the first three letters are the Active CSC on your device. You can review this article for additional information on Firmware and CSC's.
CSC and Home_CSC | All You Need to Know About ODIN Samsung Flash
Here is all you need to know about the CSC and Home_CSC.What exactly is a Firmware?A firmware is nothing but a permanent software which is programme
www.getdroidtips.com
Click to expand...
Click to collapse
If I am reading it correctly, this is what I am seeing:
ATT/ATT/XAA
I am happy that I don't have the ATT bloatware but I also feel that ATT is locking me out of some of their features because I don't have a "branded" phone, such as wifi call or visual voicemail. Am I misunderstanding your post from above, #6, that flashing ATT firmware would give me the carrier features?
Additionally, does the firmware determine what frequency bands I am using and if I am taking full advantage of ATT's offerings?
itchyUnder said:
If I am reading it correctly, this is what I am seeing:
ATT/ATT/XAA
I am happy that I don't have the ATT bloatware but I also feel that ATT is locking me out of some of their features because I don't have a "branded" phone, such as wifi call or visual voicemail. Am I misunderstanding your post from above, #6, that flashing ATT firmware would give me the carrier features?
Additionally, does the firmware determine what frequency bands I am using and if I am taking full advantage of ATT's offerings?
Click to expand...
Click to collapse
Flashing ATT Dedicated Firmware would give you the best chance for additional call features ASSUMING your Ulocked Device is capable of incorporating those features. It should do the trick since the hardware is identical to an ATT device. I would head to an ATT Store to get a definitive answer. Samsung has made it more and more challenging to mix and match branded and unlocked devices with CSC or Firmware modifications. In many cases you won't know until you try. Users want their smartphones to be smart, to work perfectly in every situation but the major carriers use proprietary tools to hold clients hostage.
varcor said:
Open your dialer, enter *#1234#, press the Dial Icon. You'll see CSC: G98??, the next 3 letters will be your device's CSC Code. Your Service Provider's CSC is "ATT" which is different than the CSC in your device. Whether or not you can change the CSC depends on your device's CSC. Device firmware is always configured for the specific, original CSC or Multi CSC's.
This post may be the best workaround.
https://forum.xda-developers.com/showpost.php?p=82444733&postcount=8
Click to expand...
Click to collapse
Please bro i need a help
My note 20 ultra is ATT unlocked
Because I'm not in united state
But in section about phone
My model is N986U note U1
am searching sammobil to udate my phone to android 13
I found nothing at&t with my model number N986U
Only N986U1
What should I do to update to android 13
This should do the trick.
Download Samsung Galaxy Note 20 Ultra 5G SM-N986U USC USA (US Cellular) firmware
All Samsung firmwares for Galaxy Note 20 Ultra 5G in USA (US Cellular) with model code SM-N986U. We offer free and fast download options. Check them out now.
www.sammobile.com
romano_ezzat said:
Please bro i need a help
My note 20 ultra is ATT unlocked
Because I'm not in united state
But in section about phone
My model is N986U note U1
am searching sammobil to udate my phone to android 13
I found nothing at&t with my model number N986U
Only N986U1
What should I do to update to android 13
Click to expand...
Click to collapse
Download Samsung Galaxy Note 20 Ultra 5G SM-N986U USC USA (US Cellular) firmware
All Samsung firmwares for Galaxy Note 20 Ultra 5G in USA (US Cellular) with model code SM-N986U. We offer free and fast download options. Check them out now.
www.sammobile.com
varcor said:
This should do the trick.
Download Samsung Galaxy Note 20 Ultra 5G SM-N986U USC USA (US Cellular) firmware
All Samsung firmwares for Galaxy Note 20 Ultra 5G in USA (US Cellular) with model code SM-N986U. We offer free and fast download options. Check them out now.
www.sammobile.com
Click to expand...
Click to collapse
I misunderstanding
What a trick bro
It's a link for firmware updates
I need to know which one compatible with my note
And after flash will still unlocked?
Hi Everyone,
I'm from Australia and recently bought a SM-G781B off eBay...
Turns out it was a UAE variant and Samsung Pay is all messed up.
I've flashed the phone a few times now using ODIN, trying to get the right CSC correct for Australia (G781BXXU2CUB5) for either of the following CSC's;
XSA (Generic Australia), OPS (Optus), VAU (Vodafone), or TEL (Telstra).
The issue I have is all the Stock Firmware's I've download and flashed keeps registering my CSC as XME (Malaysia)...
Phone INFO app doesn't even detect any other CSC's in the package
I've tried downloading the correct Firmware packs from the following and none gives me the correct CSC for Australia;
https://samfrew.com/
https://www.sammobile.com/
https://samfw.com/
App: Frija Firmware
Does anyone know why this is happening, or can upload/direct me to correct firmware either XSA, OPS (Optus), VAU (Vodafone), or TEL (Telstra)?
I'm totally at a loss now...
Any help would be much appreciated, thanks heaps in advance.
from what I've read recently Samsung has stopped people being able to switch as of android 11.
maybe... I stress MAYBE according to your countryman Hugh Jefferys, if there's a lower version of firmware on the same binary number you might be able to downgrade and then that might mean you can switch CSC.
this is someone who's never even tried changing CSC telling you this so your own research is obviously the only thing to put some faith in.
good luck
XSG (UAE) firmware is part of the OJM multi CSC, whereas XSA/OPS/TEL are part of the OLM multi CSC. This means that it is not possible to simply flash XSA in Odin as the multi CSCs are different, you would first have to use the combination ROM to change from OJM to OLM and then you would be able to flash any OLM CSC firmware, whether that be Australia, Singapore, Malaysia, or Thailand. I'm an Aussie myself, I got my phone from JB Hi Fi but switched it to Thailand CSC since XSA updates are horrendously slow (Samsung Pay does still work on Thailand CSC as does VoLTE/VoWiFi). For your case though, I'm afraid you are out of luck in terms of changing the multi CSC with the combination ROM, if you are on One UI 3.1 then the bootloader version is U2 whereas the combination ROM bootloader version is U1, so you would not be able to flash it anyway. Also, I tried to flash the combination ROM while my bootloader was still on U1 because I wanted to change from OLM to OXM (Romania CSC) for fastest updates, but Odin was not allowing the flash first because of "please get the approval to flash factory images (pit)" which I fixed, then "please get the approval to flash factory images (abl)" at which point I gave up. So as I said before, sorry but I don't think there's a lot you can do Unless a U2 bootloader version combination ROM is leaked which may or may not happen and you can get around the Odin not allowing you to flash it issues, the phone will unfortunately be stuck on UAE firmware (unless there are other countries part of OJM which you could switch to for faster updates).
Hopefully this helps you.
I have the same model! I changed my CSC but for some reason chat features in messaging app doesn't work now..other than that, all's good..
Skhux said:
I have the same model! I changed my CSC but for some reason chat features in messaging app doesn't work now..other than that, all's good..
Click to expand...
Click to collapse
Your software version is was originally XSA, so you wouldn’t have any issues flashing it with XSA and defaulting to XSA instead of another region. The CSC will automatically default back to XSA.
Mine unfortunately defaults to Malaysia XME when flashed with XSA firmware.
FedoraMaster420 said:
XSG (UAE) firmware is part of the OJM multi CSC, whereas XSA/OPS/TEL are part of the OLM multi CSC. This means that it is not possible to simply flash XSA in Odin as the multi CSCs are different, you would first have to use the combination ROM to change from OJM to OLM and then you would be able to flash any OLM CSC firmware, whether that be Australia, Singapore, Malaysia, or Thailand. I'm an Aussie myself, I got my phone from JB Hi Fi but switched it to Thailand CSC since XSA updates are horrendously slow (Samsung Pay does still work on Thailand CSC as does VoLTE/VoWiFi). For your case though, I'm afraid you are out of luck in terms of changing the multi CSC with the combination ROM, if you are on One UI 3.1 then the bootloader version is U2 whereas the combination ROM bootloader version is U1, so you would not be able to flash it anyway. Also, I tried to flash the combination ROM while my bootloader was still on U1 because I wanted to change from OLM to OXM (Romania CSC) for fastest updates, but Odin was not allowing the flash first because of "please get the approval to flash factory images (pit)" which I fixed, then "please get the approval to flash factory images (abl)" at which point I gave up. So as I said before, sorry but I don't think there's a lot you can do Unless a U2 bootloader version combination ROM is leaked which may or may not happen and you can get around the Odin not allowing you to flash it issues, the phone will unfortunately be stuck on UAE firmware (unless there are other countries part of OJM which you could switch to for faster updates).
Hopefully this helps you.
Click to expand...
Click to collapse
Thanks for the detailed reply.
From what I’ve tested, I have no issues with flashing from XSG OJM Multi to XSA OLM Multi. You can do this provided the FIrmware security number is the same as your current revision. You can’t however flash to a lower security value. See image attached.
The current firmware security value at the moment is “2” running One UI 3.1, Android 11. We can’t downgrade to any security firmware version “1” types with Android 10. If we could, then you can use multiple methods to manually change the CSC .i.e through Google Dialer or IMEI trick.
All the Firmwares at the moment are still Muti regional, unfortunately there doesn’t seem to be a way to change the CSC manually even though they are Multi regional.
All XSA firmwares I’ve downloaded and flashed will keep defaulting to XME as that’s the default unless my original CSC was XSA to begin with for it to detect.
I think the only option at the moment is to use SAMKEY, unless someone comes with with a new Android 11 method...
The other option is to root the phone and ADB to change the CSC, however this would trigger and break KNOX securities.
I did check Samkeys update log and they state it’s supported now, this method wouldn’t trigger KNOX;
VERSION 3.63.9 (PLANET EARTH'S FIRST)
- Added support for G780F (Galaxy S20 FE) ALL BIT
- Added support for G781B (Galaxy S20 FE 5G) ALL BIT
- Fixed FAIL(16) on Slow PC's
- Fixed FAIL(20) on G780F
They’re actually up to VERSION 3.71.9 now.
Might be worth a try.
kuri_2k said:
I think the only option at the moment is to use SAMKEY, unless someone comes with with a new Android 11 method...
The other option is to root the phone and ADB to change the CSC, however this would trigger and break KNOX securities.
I did check Samkeys update log and they state it’s supported now, this method wouldn’t trigger KNOX;
VERSION 3.63.9 (PLANET EARTH'S FIRST)
- Added support for G780F (Galaxy S20 FE) ALL BIT
- Added support for G781B (Galaxy S20 FE 5G) ALL BIT
- Fixed FAIL(16) on Slow PC's
- Fixed FAIL(20) on G780F
They’re actually up to VERSION 3.71.9 now.
Might be worth a try.
Click to expand...
Click to collapse
I can confirm SamKEY works on One UI 3.1, unfortunately it is paid but it does work. You can get an account for cheap from eBay with 1 credit on it which is all you need to do the CSC change. Using it I was able to change from XSA to THL (with no data wipe at all which really surprised me).
kuri_2k said:
Your software version is was originally XSA, so you wouldn’t have any issues flashing it with XSA and defaulting to XSA instead of another region. The CSC will automatically default back to XSA.
Mine unfortunately defaults to Malaysia XME when flashed with XSA firmware.
Click to expand...
Click to collapse
Trust me you wouldn't want XSA firmware anyway, the updates are terribly slow for it for the S20 FE 5G (not sure about 4G), it tends to get security patches a month after they should've came out, for example it got the March security patch in April which is pretty awful imo. I think it's the slowest CSC in general for the G781B, if you're on OLM multi CSC you're much better off switching to THL where the updates are a lot faster.
kuri_2k said:
Thanks for the detailed reply.
From what I’ve tested, I have no issues with flashing from XSG OJM Multi to XSA OLM Multi. You can do this provided the FIrmware security number is the same as your current revision. You can’t however flash to a lower security value. See image attached.
The current firmware security value at the moment is “2” running One UI 3.1, Android 11. We can’t downgrade to any security firmware version “1” types with Android 10. If we could, then you can use multiple methods to manually change the CSC .i.e through Google Dialer or IMEI trick.
All the Firmwares at the moment are still Muti regional, unfortunately there doesn’t seem to be a way to change the CSC manually even though they are Multi regional.
All XSA firmwares I’ve downloaded and flashed will keep defaulting to XME as that’s the default unless my original CSC was XSA to begin with for it to detect.
Click to expand...
Click to collapse
That's interesting, I didn't think it was possible to change between multi CSCs like this without the combination ROM (how you were able to switch from OJM to OLM). If you try to switch to an OXM multi CSC such as DBT or ROM from OLM multi CSC, what happens? Does it work? I'll be honest I never tried it myself but didn't have the motivation to try it anyway as I heard it wouldn't work.
FedoraMaster420 said:
That's interesting, I didn't think it was possible to change between multi CSCs like this without the combination ROM (how you were able to switch from OJM to OLM). If you try to switch to an OXM multi CSC such as DBT or ROM from OLM multi CSC, what happens? Does it work? I'll be honest I never tried it myself but didn't have the motivation to try it anyway as I heard it wouldn't work.
Click to expand...
Click to collapse
Hi There,
Yes, im sure it works provided the security firmware version is the same as I mentioned above.
I also changed to BTU to test.
I can't test for you any longer as I've returned the device for a refund. Will go buy an AUS XSA Variant.
Attached are the images of my original and changed firmware for your reference.
kuri_2k said:
Hi There,
Yes, im sure it works provided the security firmware version is the same as I mentioned above.
I can't test for you any longer as I returned the device for a refund. Will buy an AUS XSA Variant.
Attached are the images of my original and changed firmware for your reference.
Click to expand...
Click to collapse
That's very interesting, when you get the XSA variant can you try and see if you are able to flash a CSC such as ROM or DBT on the phone successfully using Odin? I would love to know if it was possible for this to work or not, I'm on THL myself after changing from XSA and did not think it was possible to switch to a different multi CSC (from OLM to OXM).
FedoraMaster420 said:
I can confirm SamKEY works on One UI 3.1, unfortunately it is paid but it does work. You can get an account for cheap from eBay with 1 credit on it which is all you need to do the CSC change. Using it I was able to change from XSA to THL (with no data wipe at all which really surprised me).
Click to expand...
Click to collapse
Wish I tried it before returning the device. The Australian stock only has 6GB RAM and no dual-sim....
kuri_2k said:
Wish I tried it before returning the device. The Australian stock only has 6GB RAM and no dual-sim....
Click to expand...
Click to collapse
Yeah that's true no 8GB variant sold here as far as I know not even on the Samsung website and we don't even get eSIM support either
Is there an update/workaround on this issue?
are there any methods that work without samKey?
Noticed that the dialer app that was once able to record calls, is now recording only me talking, since the latest OTA updates on the stock firmware (updated to oneUI 3.1 and Android 11).
I'm also on XSG (OJM) firmware and want to change CSC to enable call recording on galaxy S20 FE 5G (model G781B).
Would love to know how can it be done.
*my software info is attached in the screenshot
thanks!
VM57 said:
Is there an update/workaround on this issue?
are there any methods that work without samKey?
Noticed that the dialer app that was once able to record calls, is now recording only me talking, since the latest OTA updates on the stock firmware (updated to oneUI 3.1 and Android 11).
I'm also on XSG (OJM) firmware and want to change CSC to enable call recording on galaxy S20 FE 5G (model G781B).
Would love to know how can it be done.
*my software info is attached in the screenshot
thanks!
Click to expand...
Click to collapse
I'm sure by now you've already sorted this, but this is for future people with a need to change CSC
The SamFW FRP Tool can tell you which CSCs are available on your phone already, and can automatically have the CarrierPreConfig service trigger a CSC update. Only need to enable USB Debugging. No root, no reinstall.
But if your phone doesn't have the CSC you need already, download Frija, or another firmware download tool, you'll be able to download and install an OXM Multi CSC firmware (such as XSA, OPS, TEL or VAU), and install it via ODIN tool.
Be sure to select HOME_CSC to keep your data, and backup first.
Peterepeat87 said:
I'm sure by now you've already sorted this, but this is for future people with a need to change CSC
The SamFW FRP Tool can tell you which CSCs are available on your phone already, and can automatically have the CarrierPreConfig service trigger a CSC update. Only need to enable USB Debugging. No root, no reinstall.
But if your phone doesn't have the CSC you need already, download Frija, or another firmware download tool, you'll be able to download and install an OXM Multi CSC firmware (such as XSA, OPS, TEL or VAU), and install it via ODIN tool.
Be sure to select HOME_CSC to keep your data, and backup first.
Click to expand...
Click to collapse
Thank you, mate! I have just registered here specifically to thank you You really were the last random post I found in the internet that helped me to solve this unflashable state of my S9. Thank you again! <O
Hi all,
I purchased an A52s 5G (SM-A528B/DS, snapdragon version) last week. I never had a Samsung before so I’m learning now about CSC and such.
I noticed that I don’t have the call recording function even though my country should support it (ILO). As it turns out the device has XSG CSC (I guess it’s a non-official parallel import).
I gathered information around the forums and I’m trying to understand if I can change the CSC by factory reseting and doing the device setup while my ILO SIM card is installed.
Apologies if my questions are stupid and the answer is obvious, but I couldn’t piece it together.
I’m trying to avoid tripping Knox to retain my warranty.
I read somewhere that ILO and XSG are part of the same multi-CSC group (OJM) and that it should work?
I read somewhere else that it no longer works on One UI 3.1/Android 11 versions?
I read somewhere else again that samkey may be a viable solution?
So should I try just by factory resetting the phone? Or try samkey? Or?
Is there any way to change CSC on the fly and avoid having to factory reset the device?
Thanks so much in advance,
Tal
I used to require a SIM to change the CSC but was able to do without it this time.
Doesn't trip Knox. There's a list of countries that details which have call recording built in.
talla1 said:
Hi all,
I purchased an A52s 5G (SM-A528B/DS, snapdragon version) last week. I never had a Samsung before so I’m learning now about CSC and such.
I noticed that I don’t have the call recording function even though my country should support it (ILO). As it turns out the device has XSG CSC (I guess it’s a non-official parallel import).
I gathered information around the forums and I’m trying to understand if I can change the CSC by factory reseting and doing the device setup while my ILO SIM card is installed.
Apologies if my questions are stupid and the answer is obvious, but I couldn’t piece it together.
I’m trying to avoid tripping Knox to retain my warranty.
I read somewhere that ILO and XSG are part of the same multi-CSC group (OJM) and that it should work?
I read somewhere else that it no longer works on One UI 3.1/Android 11 versions?
I read somewhere else again that samkey may be a viable solution?
So should I try just by factory resetting the phone? Or try samkey? Or?
Is there any way to change CSC on the fly and avoid having to factory reset the device?
Thanks so much in advance,
Tal
Click to expand...
Click to collapse
pacificator1048 said:
I used to require a SIM to change the CSC but was able to do without it this time.
Doesn't trip Knox. There's a list of countries that details which have call recording built in.
Click to expand...
Click to collapse
I have the exact same issue with the same XSG CSC, and I need to change to ILO.
Can you guys help me with that?
CosTuMe said:
I have the exact same issue with the same XSG CSC, and I need to change to ILO.
Can you guys help me with that?
Click to expand...
Click to collapse
To anyone who might encounter this in the future, My phone was bought trough GoMobile a parallel importer in Israel who didn't have call recordings available although the official one had.
I used SAMKEY in order to change the CSC into "ILO" the Israeli CSC and it worked getting me back the recordings and even had gotten OTA's after it.
I bought an A52s 5G on Amazon UK, and the model that arrived was a Romanian one. I find two things very odd: there is nothing outside the box to indicate that the device is not a UK one (product code would suffice), and when opening the box (which was untampered, as expected) it had a UK plug charger, adding to the fact that the device was destined for the UK market. The back of the device shows a sign for compliance with UK CA standards, and booting it first time, it greeted me in English. However, soon after I figured out the shortcomings and I found that CSC is set to ROM. Factory resetting the phone with a UK sim didn't make much difference however this time the phone greeted me in Romanian. While I've resolved the issue with.. the usual method, I find it dodgy and either the seller went to great lengths to hide the originating country or Samsung is creating these devices targetting Romania but actually making them look British, for.. reasons? Both possibilities are weird.
CosTuMe said:
To anyone who might encounter this in the future, My phone was bought trough GoMobile a parallel importer in Israel who didn't have call recordings available although the official one had.
I used SAMKEY in order to change the CSC into "ILO" the Israeli CSC and it worked getting me back the recordings and even had gotten OTA's after it.
Click to expand...
Click to collapse
Did you use it on Galaxy A52s 5G? Which firmware date version did you use to change the CSC?
I wanna go back to my original CSC.
gambit1091 said:
Did you use it on Galaxy A52s 5G? Which firmware date version did you use to change the CSC?
I wanna go back to my original CSC.
Click to expand...
Click to collapse
I think I was on the latest one
can someone help with it?
i am currently before buying from GOMOBILE parallel , and want to add call recording.
can someone help with it?
i am currently before buying from GOMOBILE parallel , and want to add call recording.
CosTuMe said:
To anyone who might encounter this in the future, My phone was bought trough GoMobile a parallel importer in Israel who didn't have call recordings available although the official one had.
I used SAMKEY in order to change the CSC into "ILO" the Israeli CSC and it worked getting me back the recordings and even had gotten OTA's after it.
Click to expand...
Click to collapse
mordydd91 said:
can someone help with it?
i am currently before buying from GOMOBILE parallel , and want to add call recording.
Click to expand...
Click to collapse
Thats exactly what I did, bought from GoMobile as well, change the csc trough SamKey to ILO
CosTuMe said:
Thats exactly what I did, bought from GoMobile as well, change the csc trough SamKey to ILO
Click to expand...
Click to collapse
P{ls help me throw this
talla1 said:
Hi all,
I purchased an A52s 5G (SM-A528B/DS, snapdragon version) last week. I never had a Samsung before so I’m learning now about CSC and such.
I noticed that I don’t have the call recording function even though my country should support it (ILO). As it turns out the device has XSG CSC (I guess it’s a non-official parallel import).
I gathered information around the forums and I’m trying to understand if I can change the CSC by factory reseting and doing the device setup while my ILO SIM card is installed.
Apologies if my questions are stupid and the answer is obvious, but I couldn’t piece it together.
I’m trying to avoid tripping Knox to retain my warranty.
I read somewhere that ILO and XSG are part of the same multi-CSC group (OJM) and that it should work?
I read somewhere else that it no longer works on One UI 3.1/Android 11 versions?
I read somewhere else again that samkey may be a viable solution?
So should I try just by factory resetting the phone? Or try samkey? Or?
Is there any way to change CSC on the fly and avoid having to factory reset the device?
Thanks so much in advance,
Tal
Click to expand...
Click to collapse
did you succeed? do you have call recording?
For some reason I've never been able to buy a Samsung that used a single sku CSC.
Even with ICCID locked devices they always shipped with the multi-csc/multi-csc2, so I've always been able to use a SIM Card to change out carriers unless the EFS/CSC partitions blocked it partially.
And even in those couple cases, I've always been able to cross-flash carrier firmware for that device to switch networks when need be.
This method even allowed me to use my AT&T locked Galaxy Note5 with T-Mobile Firmware. The only bug was the AT&T Modem's lack of hardware support for all of the TMO network bands.
Other than that. I even bested the Geek Squad at Best Buy...
This method worked on my A32x 5G.
As the title suggests, I was able to successfully change the CSC on my factory unlocked (unbranded) Fold 3 - F926B/DS bought in Germany with OXM firmware having Android 13 & one UI 5.0 from EUX to INU csc using SamFW Tool v3.31 in hardly 2-3 mins. Kindly note that I also looked into other options to do this like Samkey tool (paid service) and alliance shield app (which doesn't work anymore) etc before engaging with the SamFW Tool as none were simple/working with no complications whatsoever involved.
My main objective to change the CSC was to enable call recording and couple of other features (including some pleasant surprises listed in the end of the post) which were available in the INU csc with little to no hassle. The process was pretty simple, straight forward and most importantly, FREE . It DOESN'T require any factory reset, flashing of roms or wiping cache partition before or after the process.
The step by step guide process which worked for me is as follows:
STEP 1: Click here - SamFW Tool Download - to download the latest version of SamFW tool.
STEP 2: Remove the sim card and connect your phone to a computer and make sure the phone's drivers are installed.
STEP 3: Unzip the downloaded file. Right click on the file SamFwFRPTool.exe and 'Run as Administrator'.
STEP 4: After the software opens, make sure your phone is detected before proceeding. If its detected, click on ADB tab in the software.
STEP 5: In your phone, go to developer options and enable 'usb debugging'.
STEP 6: In your phone, open phone dialer and type *#0*# to get into test mode. Leave the phone unlocked and keep it aside now.
STEP 7: Click on 'Change CSC' button in the ADB tab of the tool. Now the tool will connect to your phone, check and list the available CSCs which your phone model supports as shown in the pic attached.
STEP 8: Choose a CSC which you wish to change to from the drop down menu in the pop-up window as shown in the pic attached.
NOTE: The tool also has the option to force the phone to accept a CSC not listed/supported as well by manually entering the same. However, I would not recommend doing it if you really wish to get OTA updates and also to evade any unforeseen issues. I must admit, I haven't frankly tried this and do not know what lies in the pandora box to be honest.
STEP 9: After choosing the CSC from the drop down, the tool quickly connects to the phone, changes the CSC and restarts the phone.
STEP 10: After the phone restarts, unlock the phone using your pin/password, insert your simcard, check the change of CSC in software information, disconnect the phone from the computer and also disable the 'usb debugging' in the developer options.
That's it! All done. Phone restarts with the new chosen CSC and the related features will now be active!
BONUS: There is also an option in the ADB tab in the SamFW Tool named 'Battery information' which gives the complete information of the battery status including the 'charge/discharge cycles' along with its temperature, voltage etc. like in the pic attached. Do note that the information shown in the 'Genuine battery' section isn't correct for some reason and always shows as 'NO' for any phone with/without genuine battery.
With my choice of INU csc the following major changes/surprises were noticed over the EUX:
1. Call recording and a couple of other INU specific features are now enabled (google for more info on what csc enables what features).
2. Not sure why but Battery backup has increased significantly after the csc change to INU. SOT (Screen On Time) which has fallen to 3-4 hrs after the OTA update to One Ui 5.0 & Android 13 is now back to 5-7hrs or more.
3. RAM management has definitely got better. With EUX csc it used be around 5-6GB during standby and now its always around 3-4GB when the phone is idle.
4. Instead of 4G or 4G+, now it shows LTE and LTE+.
5. Mobile data speed has increased both in 5G (Jio True5G network) and in LTE+ when compared to EUX CSC.
6. 5G signal strength has improved drastically. Signal loss or switching to 4G+/LTE+ is very low now.
7. 5G to 4G/LTE switching while calls (VoLTE/VoNR) is more seamless now. Latching back onto 5G network after a call is a breeze now unlike earlier with EUX csc.
8. Phone definitely got faster for some reason. Can very much feel the difference when switching between apps, multi-tasking, even opening/closing apps and other day-to-day tasks.
etc...
Haven't tested whether the OTA updates will still get pushed after the change in CSC yet, as my phone is already updated to the latest patch as I write this. Should absolutely work IMO as long as we choose a CSC which the phone supports but in any case will update the thread once the next update via OTA is available/pushed by Samsung.
Disclaimer: Please be informed that all the above information is purely based on experience of using the tool for changing CSC only which worked well for me with my Fold 3. Cannot take responsibility if it doesn't work for you.
Does it work for Fold 4. Want to change CSC from Korean Region to INU (India). Please guide
Sorry, haven't tried it on Fold 4. Logically it shud work, I guess. There is no harm in connecting n checking what CSCs does ur model supports using the tool IMO.
Tried out but it does not work. It shows only the Korean csc. Even that seems to be not changing
Oh k. I think the tool works, else u wudnt b seeing the CSC which ur phone supports.
I have checked sources in the web as well on this and looks like Fold 3 or 4 with Korean CSC supports only CSC from Korea.
I guess u can still force a CSC on to it replacing the Korean one but thats too risky as u will b missing OTA updates and im not aure wat all things it will mess up.
Awesome! It works and it doesn't wipe the device. I just switched from G975U VZW to CCT without any issues.
BlueTR said:
Awesome! It works and it doesn't wipe the device. I just switched from G975U VZW to CCT without any issues.
Click to expand...
Click to collapse
Happy to hear that. BTW I also got samsung pay/wallet to work as well by installing its apk file today after changing the system language to a local one specific to the changed CSC i.e., English (India) for INU CSC in my case.
I confirm that it is working on a stock android 13! Great tool!
(It worked on the second try though )
Has anyone tired it on a Fold 4, Mine is XAA and I want to convert it to INU. Haven't been abe to do it as yet.
Let me know if someone finds a way, mine is a US version and I want to convert it to the India CSU.
Thanks in advance
unexpected0ne said:
I confirm that it is working on a stock android 13! Great tool!
(It worked on the second try though )
Click to expand...
Click to collapse
Good to know! Just out of curiosity, u tried this on a Fold 3 or Fold 4?
srikanth.addala said:
Good to know! Just out of curiosity, u tried this on a Fold 3 or Fold 4?
Click to expand...
Click to collapse
Fold 3, latest official android 13
unexpected0ne said:
Fold 3, latest official android 13
Click to expand...
Click to collapse
Oh great. Getting otas after the change?
Does OTA work after change?
Hello, can somebody please briefly summerise the options for switching the CSC/Firmware?
I read other threads and this one and now am confused which method actually would work for me.
My situation: i have a Samsung A52s 5G purchased from Deutsche Telekom in Germany, sold separately, not bundled with a contract.
And i am having a contract with a different carrier on a different network, but a german SIM card.
My phone is configured all english, and i need to keep that.
Because of assumed network optimisations and the problem of delayed updates of "branded" phones, i would like to convert the phone from the current CSC of DTM to the DBT using fimrware (A528BXXS1DVL2/A528BOXM1DVK5/A528BXXU1DVK5/A528BXXS1DVL2), which i hope would link me to updates directly provided by Samsung.
I found "https://forum.xda-developers.com/t/...official-firmware-all-samsung-device.2697238/" and "https://forum.xda-developers.com/t/...-multi-csc-codes.4436853/page-5#post-87485577 ", but i am not sure whther the methods described there only apply for UPDATING (within the same CSC) the phone with non-OTA methods, or whether that also covers SWITCHING the CSC?
In the end i have two questions:
1) So far i believed that "simply" putting an official stock Samsung firmware (multi CSC in my case, containing the DBT, but apparently NOT containing the DTM) would bring me there.
But then i read that this might not be suffficient. Instead i also would have to switch the CSC in my Phone's config, which apparently would require purchasing a license for a Samkey unlock code.
Because otherwise i would not receive any OTA updates once i switched just the firmware.
Is that actually true?
I would prefer not to have to buy a Samkey...
And to make the confusion even bigger: now i read, SamFw Tool would also be an option?
But: is that trustworthy? And: from posts of some of you: this might even obsolete to switch the firmware, do i understand that right?
2) If switching firmware still is required: would using Odin/Heimdall be the only option to switch the firmware, or would adb sideloading do the same job as well? I am asking because i don't have access to a windows machine.
Would be so great if someone of you could untangle my confusion a bit, thank you.
MarkoParkovic said:
Does OTA work after change?
Click to expand...
Click to collapse
Did not automatically receive the OTA updates with the recent DVL9 update. However, tried a work around to change the CSC back to EUX via the same tool (which is a 2 min task) to check if I can get OTA again.
And yes it worked! immediately after changing the OTA to its home CSC, was able to see OTA in the updates section of the phone. So, I updated the phone to the latest version (DVL9) and then changed the CSC back to INU after the update . All is well and quick! .
very nice i changed sfr to tur but netflix and always on display app not shown google play so unsupported why idk
burc ugur said:
very nice i changed sfr to tur but netflix and always on display app not shown google play so unsupported why idk
Click to expand...
Click to collapse
May be TUR csc has restricted options/features. In my example after I changed to INU csc (India one) all the India related options got automatically activated like call recording, spam filter, samsung pay using cards etc etc. which weren't available with the EUX csc before the change.
srikanth.addala said:
May be TUR csc has restricted options/features. In my example after I changed to INU csc (India one) all the India related options got automatically activated like call recording, spam filter, samsung pay using cards etc etc. which weren't available with the EUX csc before the change.
Click to expand...
Click to collapse
Any potential issues using INU csc in the UK? I use Samsung pay already but native call recoding would be really useful for me
srikanth.addala said:
May be TUR csc has restricted options/features. In my example after I changed to INU csc (India one) all the India related options got automatically activated like call recording, spam filter, samsung pay using cards etc etc. which weren't available with the EUX csc before the change.
Click to expand...
Click to collapse
edit: excuse me you have play protect certificate? i changed csc samfw topl but now i don't have play protect certificate. Therefore not shown Netflix.
you have this? if you have how can i fix certificate.
burc ugur said:
edit: excuse me you have play protect certificate? i changed csc samfw topl but now i don't have play protect certificate. Therefore not shown Netflix.
you have this? if you have how can i fix certificate.
Click to expand...
Click to collapse
Might be worth clearing cache and data from Google play services see if that helps. Having the same device with 2 different cscs might have confused Google
Edit
Any reason your Google play store is out of date or is it connected to your original issue