[Q] Radio/Modem Files for Wave 8500 - Bada Software and Hacking General

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.

Related

[Q] FIRMWARE UPDATE(which is which)

Hi Guys,
I want to update my current firmware version(2.3.6-DLC1)(Stock) to the latest stock(DXLM3) firmware for my country(Philippines)but i was hesitant which firware to download.
I visited samobile.com and i was confused on what to download on the site. there where 4 stock firmware with same baseband(below).
GT-I8150 Philippines (Smart) 2012 April Android 2.3.6 I8150DXLM3 I8150OLBLD1
GT-I8150 Philippines 2012 April Android 2.3.6 I8150DXLM3 I8150OLBLD1 - for some reason no indicated subscriber
GT-I8150 Philippines (Globe) 2012 April Android 2.3.6 I8150DXLM3 I8150OLBLD1 and
GT-I8150 Philippines (Sun) 2012 April Android 2.3.6 I8150DXLM3 I8150OLBLD1
FYI, im a smart subscriber, but i also have a globe and sun sim which i usually both use, depending on my needs(sun=call)(globe=call and sms my friends)(smart=net,txt and call=1 option).
I have read that there where problems with regards to signal,etc when you have not set the right firmware specific for your country or subscriber, would it be possible to explain what is the difference between on all 4 firmwares?and also which should i choose base on my needs..
thnx in advance^^..
I'm not really sure, but here's my guess:
The firmwares where the operator is indicated, they are "branded" firmware, containing perhaps apps that the operator requested Samsung to include in the phone. This usually go into phones offered by the operator with a service/contract bundle.
The firmware without operater is most likely an "unbranded" firmware, i.e., the firmware used by phones purchased without contract, from a 'neutral' reseller.
The problem with signal is due to incompatible baseband; the baseband is the piece of firmware that communicates with the BTS and/or WiFi Access Points. The Telecommunication Authority of a country may specify a certain behavior (out of several) regarding the communication standard with the BTS / WiFi AP (for example: WiFi Channel Selection, which 'variant' of GSM signaling used, which GSM signaling 'options' are legal, etc etc etc).
From the list of firmwares you gave, I can see that they are all using the exact same baseband: DXLM3. So, there should be no problem using any of them within your country. (Of course, you really should choose the 'unbranded' one to save you from having to deal with annoying operator-specific bloatware)
pepoluan said:
I'm not really sure, but here's my guess:
The firmwares where the operator is indicated, they are "branded" firmware, containing perhaps apps that the operator requested Samsung to include in the phone. This usually go into phones offered by the operator with a service/contract bundle.
The firmware without operater is most likely an "unbranded" firmware, i.e., the firmware used by phones purchased without contract, from a 'neutral' reseller.
The problem with signal is due to incompatible baseband; the baseband is the piece of firmware that communicates with the BTS and/or WiFi Access Points. The Telecommunication Authority of a country may specify a certain behavior (out of several) regarding the communication standard with the BTS / WiFi AP (for example: WiFi Channel Selection, which 'variant' of GSM signaling used, which GSM signaling 'options' are legal, etc etc etc).
From the list of firmwares you gave, I can see that they are all using the exact same baseband: DXLM3. So, there should be no problem using any of them within your country. (Of course, you really should choose the 'unbranded' one to save you from having to deal with annoying operator-specific bloatware)
Click to expand...
Click to collapse
I see..thank you so much for clearing it out..this means that i dont have to reflash a whole firmware since they are using the exact baseband.
the main Reason i posted this, is beacuse im guessing this might be the cause of why my 3g signal is not appearing and i cannot use 3g services, im currently at CM-9(RC5) and 3g is not appering even if i am already registed on the service,already tried to reregister, on/off airplane mode, reset apn, even manually set it but still to no avail..
[iop]wah said:
I see..thank you so much for clearing it out..this means that i dont have to reflash a whole firmware since they are using the exact baseband.
the main Reason i posted this, is beacuse im guessing this might be the cause of why my 3g signal is not appearing and i cannot use 3g services, im currently at CM-9(RC5) and 3g is not appering even if i am already registed on the service,already tried to reregister, on/off airplane mode, reset apn, even manually set it but still to no avail..
Click to expand...
Click to collapse
CM9 does not contain a baseband; perhaps your baseband needs to be upgrade.
@sigprof has extracted and repackaged a whole gaggle of baseband images to allow easy flashing using CWM: http://forum.xda-developers.com/showthread.php?p=36690782
Get one, then flash the baseband right after flashing CM9.
Sent from my GT-I8150 using xda app-developers app

Changing CSC on A520F/DS -- a couple of questions

Hi guys and girls of XDA!
I have recently bought a used A5 2017 Dual SIM on eBay and I am in awe with its battery life even after the Oreo upgrade.
However, Samsung does not sell Dual SIM models here in Germany, my model comes from Iran (CSC: THR)
I have read the forum, but I haven't found answers to my questions.
I want to flash a DBT version onto my phone ans I have a couple of questions.
1) I have a DS model which were never available on a German market. Will Dual SIM work after I flash and will I get updates after I flash?
2) The german version of (mono-SIM) firmware, which is available on Sammobile still has A520FXXU7CRH9 baseband. I have already updated to the -I9 one. Does that mean that I cannot revert back o the H9 and will have to wait until german phones get I9?
3) My phone came with a sticker "Middle Eastern and African SIM only". Both slots work with German (and some other) SIMs as of now. Will this setting revert back and it will be locked to those SIMs, if I change CSC?
4) If I will apply the Combination CSC from Sammobile , will I get access to every region-locked option without tripping knox?
Thanks in advance!
Alex.
Anybody here? up!
I don't know the answers to your specific questions - but if the dual sim (Iran) phone you have works with your german sims why are you trying to reflash it?
Is there a problem or something that is not working?
I live in New Zealand and have an imported UAE (United Arab Emirates) 2017 A5 with dual SIM and it works just fine. I havent tried the second sim, but have heard of other people that have and it works as expected. The phone doesnt have any UAE junkware. You are right - the battery life on this phone is great. I did find the always on display uses more battery that I like though. Really wish they had an option that just turned the AOD on when you got a notification (new email/text/missed call etc) but Samsung don't seem to want to provide useful features like this. I came from a galaxy Note 2 and miss that little notification LED
If it helps, I see that the A520F and A520F/DS do not have different firmware - I have searched and there are plenty of posts on this forum where people have flashed Dual SIM hardware with the 'standard' A520F software and report that the dual SIM functionality works fine.
https://forum.xda-developers.com/samsung-a-series-2017/help/sm-a520f-to-sm-a520f-ds-t3704566
The DS model was never officially sold in new Zealand (the single SIM model was) but I have received the Oreo update and several security updates for my phone anyway since I bought it.
Hi, thanks for your reply!
Is there a problem or something that is not working?
Click to expand...
Click to collapse
VoLTE is not showing up in settings, for instance. I would need this option sometimes.
report that the dual SIM functionality works fine.
Click to expand...
Click to collapse
Thanks for the link.
the battery life on this phone is great.
Click to expand...
Click to collapse
I get 26-28 hours of norml usage.
However one thing that irritates me is why it loses up to 10% over the night? Everything is closed and AOD is off, too. Other than that I had to uninstall Chrome because it literally ate up trice as much battery as everything else added up, including screen.
Not sure about your overnight power loss - sounds a litle high...
I use my phone very little and usually only charge it every 4 or 5 days.
AOD uses more power than I like (I have seen 1% an hour mentioned and that is probably about right), so I switched that off.
Really annoyed that Samsung havent made an AOD setting that only enables the AOD on when there are notifications (Missed call, new messages). I would really find that useful.
Have searched all over but cant find any apps that will do this.
For those interested, here is what happened.
1) I have a DS model which were never available on a German market. Will Dual SIM work after I flash and will I get updates after I flash?
Basically, it is the same model and the same firmware. The "normal" firmware for a non-Dual-SIM market works perfectly with a DS model and gets updates via OTA.
2) The german version of (mono-SIM) firmware, which is available on Sammobile still has A520FXXU7CRH9 baseband. I have already updated to the -I9 one. Does that mean that I cannot revert back o the H9 and will have to wait until german phones get I9?
The main thing is that ninth digit ("7") because it represents the revision of the firmware. As long as it is the same, you can flash it. If not you will get a brick.
3) My phone came with a sticker "Middle Eastern and African SIM only". Both slots work with German (and some other) SIMs as of now. Will this setting revert back and it will be locked to those SIMs, if I change CSC?
It didn`t happen to me.
4) If I will apply the Combination CSC from Sammobile , will I get access to every region-locked option without tripping knox?
I did as follows.
I flashed the DBT firmware from SamMobile and got myself a british code because it is a standard one in this Multi-CSC.
Knox not tripped. But VoLTE and VoWiFi still not working
Then I found the Combination ROM (FACTORY BINARY) with the same revision as the firmware (See question 2 about the "7").
I flashed it, dialed some USSD code. Then menu appeared from which I could choose the product code.
I chose DBT, wiped the data and cache and voila, I had a DBT phone with working VoLTE and VoWiFi otb.
Knox not tripped 0x0 !
ioffer007 said:
For those interested, here is what happened.
1) I have a DS model which were never available on a German market. Will Dual SIM work after I flash and will I get updates after I flash?
Basically, it is the same model and the same firmware. The "normal" firmware for a non-Dual-SIM market works perfectly with a DS model and gets updates via OTA.
2) The german version of (mono-SIM) firmware, which is available on Sammobile still has A520FXXU7CRH9 baseband. I have already updated to the -I9 one. Does that mean that I cannot revert back o the H9 and will have to wait until german phones get I9?
The main thing is that ninth digit ("7") because it represents the revision of the firmware. As long as it is the same, you can flash it. If not you will get a brick.
3) My phone came with a sticker "Middle Eastern and African SIM only". Both slots work with German (and some other) SIMs as of now. Will this setting revert back and it will be locked to those SIMs, if I change CSC?
It didn`t happen to me.
4) If I will apply the Combination CSC from Sammobile , will I get access to every region-locked option without tripping knox?
I did as follows.
I flashed the DBT firmware from SamMobile and got myself a british code because it is a standard one in this Multi-CSC.
Knox not tripped. But VoLTE and VoWiFi still not working
Then I found the Combination ROM (FACTORY BINARY) with the same revision as the firmware (See question 2 about the "7").
I flashed it, dialed some USSD code. Then menu appeared from which I could choose the product code.
I chose DBT, wiped the data and cache and voila, I had a DBT phone with working VoLTE and VoWiFi otb.
Knox not tripped 0x0 !
Click to expand...
Click to collapse
Could you go into more detail, please? What USSD code did you dial?

G975U and G975U1 Firmware Links and Flashing Discussion Here

For those who aren't already aware, G975U is the model number of all of the US carrier versions of the S10+. The G975U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. A "U to U" or "U1 to U1" flash does not require a factory reset, but changing from one firmware to the other will require one. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.
Manual Odin flashing is designed for those who:
- want to manually update to a newer version of U firmware on their U device, either because they don't want to wait for their carrier's OTA or because OTAs aren't working on their device, or a different carrier got a new feature/patch before they did
- want to flash U1 firmware to their U device
- want to convert from U1 firmware to carrier U firmware
- want to convert from one carrier's U firmware (with all apps and bloatware) to a different carrier's U firmware (with all apps and bloatware)
For those who aren't already aware, anyone can now download firmware for almost any Samsung device any time that they want, via the various firmware download tools posted here on XDA like SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But they only provide whatever the latest/newest/current version is - nothing older. I pay for a subscription to a site that gets the official releases (usually) before they hit the firmware download tools, so that's where my files come from.
This is not a "beginner's guide to Odin flashing" -type post/thread, so I won't list basic, step-by-step flashing instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware (or haven't done it in a long time), I recommend you consult one of those "beginner's" guides- there are tons of them here on XDA.
Happy flashing!
U firmware: https://www.androidfilehost.com/?w=files&flid=290649
U1 firmware: https://www.androidfilehost.com/?w=files&flid=290650
Notes:
- I compress extra small for space and bandwith savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- I remove the .md5 from each file solely for faster flashing (Odin won't check the file integrity without it). Rest assured, the files are perfectly fine and safe - Odin has a million safechecks built in.
- My naming method for folders is: build - bootloader - Android version
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- HOME CSC file keeps data intact; using the other CSC will wipe data. Any zips with "wipe" in the title do not have a HOME CSC included.
- I have identical threads for the S10e and S10 as well
- the correct procedure for switching from one carrier's firmware to another is given in post #25
- You can get USERDATAs from SamFirm for everything but AT&T and Cricket- those files will never be on SamFirm. So in addition to the 5 piece firmware, I'll try to always upload one USERDATA per bootloader increment for those carriers.
- For identifying USERDATAS, and to know what region/CSC to use in the firmware download tools if you're downloading yourself:
AIO = Cricket (not available via firmware download tools)
ATT = AT&T (not available via firmware download tools)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
SPR = Sprint
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon
XAA = U1 firmware
This is looking great, was about to pre-order the T Mobile variant, when I remembered that they disable the (Data) Quick Toggle and I have to fiddle around to turn it off, Well, Not the case with the Unlocked version, at least on my Note 9. Anyways, this will come in handy, thanks!
Willy318is said:
This is looking great, was about to pre-order the T Mobile variant, when I remembered that they disable the (Data) Quick Toggle and I have to fiddle around to turn it off, Well, Not the case with the Unlocked version, at least on my Note 9. Anyways, this will come in handy, thanks!
Click to expand...
Click to collapse
Hopefully One UI stays the same. You're welcome
Good to see and will be a good place to hangout! ?
Loved your dedication to uploads on the 9+! Glad to see you here as well! I preodered my ATT 10+ yesterday. Got my mom and two daughters the 10+ / 10e also. Happy to see you'll be providing firmware for the "E" also!
Build SBA added.
Only CCT, VZW, and SPR USERDTAs (for now), but it can be flashed to any S10+
So I flashed this on my new U1 and went to U firmware. My Wifi didn't work after this. I can't connect to any Wifi network... I will try going back to U1 and see if the issue is fixed. Maybe I have a defective phone?
rocket31337 said:
So I flashed this on my new U1 and went to U firmware. My Wifi didn't work after this. I can't connect to any Wifi network... I will try going back to U1 and see if the issue is fixed. Maybe I have a defective phone?
Click to expand...
Click to collapse
Hmmm that's weird. I'm assuming you wiped?
G975U and G975U1 firmware is now live and downloadable in SamFirm. Getting U1 requires manual entry - Auto will not work. U firmware is up for these carriers:
Xfinity Mobile
Spectrum Mobile
Sprint
T-Mobile
US Cellular
Verizon (have to use Manual entry - Auto will not work)
So going forward, I'll only be adding full builds if I can get them before they hit SamFirm, and only if there isn't build for that month already (eg. I won't add any more February builds since SBA is already up.). I will try to stay up to date on USERDATAs for AT&T and Cricket, since AT&T won't let their firmware be put on SamFirm.
Thank you for this. Just flashed my U1 to TMB SBA for video calling feature.
iBowToAndroid said:
G975U and G975U1 firmware is now live and downloadable in SamFirm. U firmware is up for these carriers:
Xfinity Mobile
Spectrum Mobile
Sprint
T-Mobile
US Cellular
Verizon (have to use Manual entry - Auto will not work)
So going forward, I'll only be adding full builds if I can get them before they hit SamFirm, and only if there isn't build for that month already (eg. I won't add any more February builds since SBA is already up.). I will try to stay up to date on USERDATAs for AT&T and Cricket, since AT&T won't let their firmware be put on SamFirm.
Click to expand...
Click to collapse
Is it? I'm not seeing anything.
http://fota-cloud-dn.ospserver.net/firmware/XAA/SM-G975U1/version.xml
YandereSan said:
Is it? I'm not seeing anything.
http://fota-cloud-dn.ospserver.net/firmware/XAA/SM-G975U1/version.xml
Click to expand...
Click to collapse
Not sure what that link is, but U1 is available via the SamFirm tool. I did forget to mention that you have to use Manual input, so i'll edit that part
iBowToAndroid said:
Not sure what that link is, but U1 is available via the SamFirm tool. I did forget to mention that you have to use Manual input, so i'll edit that part
Click to expand...
Click to collapse
That's for auto download. How'd you get the PDA/CSC/Phone?
YandereSan said:
That's for auto download. How'd you get the PDA/CSC/Phone?
Click to expand...
Click to collapse
Manual input, like I said. You have to type in the builds manually
iBowToAndroid said:
Manual input, like I said. You have to type in the builds manually
Click to expand...
Click to collapse
Yes, I realize that. G975U1UEU1ASAU/G975U1OYM1ASAU/G975U1UEU1ASAU
Where are you pulling the values from? Do you have the physical device?
YandereSan said:
Yes, I realize that. G975U1UEU1ASAU/G975U1OYM1ASAU/G975U1UEU1ASAU
Where are you pulling the values from? Do you have the physical device?
Click to expand...
Click to collapse
No. I'm getting them from the place where I get my firmware files from
I have a question and I hope someone can help me. I just purchased a s10 not the plus. And its unlocked which is great but has three UK branding on boot up ect..,
Is it possible to remove this maybe install another rom via oden? And it wouldn't void warranty or enable a security problem on the phone? Any help would be much appreciated
Guessing ATT is late to the party as usual with no ASAB userdata yet? Doesn't appear they've pushed it yet ?
vimto25 said:
I have a question and I hope someone can help me. I just purchased a s10 not the plus. And its unlocked which is great but has three UK branding on boot up ect..,
Is it possible to remove this maybe install another rom via oden? And it wouldn't void warranty or enable a security problem on the phone? Any help would be much appreciated
Click to expand...
Click to collapse
This thread is for U models (Qualcomm). You need to find a thread about the F models (Exynos).
todd3835 said:
Guessing ATT is late to the party as usual with no ASAB userdata yet? Doesn't appear they've pushed it yet ?
Click to expand...
Click to collapse
Anyone can flash any update - USERDATA isn't required unless you're changing from U1 to U, or from one carrier to another.
iBowToAndroid said:
This thread is for U models (Qualcomm). You need to find a thread about the F models (Exynos).
Anyone can flash any update - USERDATA isn't required unless you're changing from U1 to U, or from one carrier to another.
Click to expand...
Click to collapse
Ah ok. On my S9+ I did some Odin flashing and even though I was on the att release, I wasn't getting OTA's. It was odd. Only way to restore OTA updates was flashing with ATT userdata.
On a side note, ATT has pushed the ASAB update for both the S10+ and the S10E.

Question Flashing ROM on Fold 3 - chinese to australian

One of our Chineese suppliers has gifted me a New Fold 3. The issue is the stock Chinese Rom, or rather the restrictions that come with it (nerfing most google based services, and apps i use all the time.). The device is great but restrictions applied give you a feeling of a second class android user, with core sevices absent: Play store, youtube, gmail, maps, chrome, android auto., can't even apporve family link download requests from kids. etc. etc.
I have made the choice i would rather go back to my S21 if i can't resovle this issue, as phone is useless like this.
Advice required on Loading Australian Rom via odin.
The phone model is: SM-F9260 which only seems to have overseas Rom available for download. Can i successfully load a ROM made for model SM-F926B (Australian) on a SM-F9260?
All the how to guides specifically say jou must select the same model number, and i don't want a brick it. Will have mud on my face next time i see the supplier if i have bricked their gift to me.
Any feedback/advice from users with more experience with odin and flashing would be appreciated.
Both are on Snapdragon CPU so shouldn't be any problem to flash it with PIT over the Odin.
But I never done it so I can't give you 100% answer.
streinhardt said:
One of our Chineese suppliers has gifted me a New Fold 3. The issue is the stock Chinese Rom, or rather the restrictions that come with it (nerfing most google based services, and apps i use all the time.). The device is great but restrictions applied give you a feeling of a second class android user, with core sevices absent: Play store, youtube, gmail, maps, chrome, android auto., can't even apporve family link download requests from kids. etc. etc.
I have made the choice i would rather go back to my S21 if i can't resovle this issue, as phone is useless like this.
Advice required on Loading Australian Rom via odin.
The phone model is: SM-F9260 which only seems to have overseas Rom available for download. Can i successfully load a ROM made for model SM-F926B (Australian) on a SM-F9260?
All the how to guides specifically say jou must select the same model number, and i don't want a brick it. Will have mud on my face next time i see the supplier if i have bricked their gift to me.
Any feedback/advice from users with more experience with odin and flashing would be appreciated.
Click to expand...
Click to collapse
Update: The AU version gave me an Auth Failed in Odin. Chances i could have resovled by unlocking the Bootloader which i didn't want to risk tripping the e-fuse. I ended up just using the Taiwan version which had the identical model number, and falls in the same region as China. Odin flashed without complaint. The taiwan version has no restrictions on google services, and once you set the language its hard to tell it from a regular AU one; unless you know what you are looking for that is.
streinhardt said:
Update: The AU version gave me an Auth Failed in Odin. Chances i could have resovled by unlocking the Bootloader which i didn't want to risk tripping the e-fuse. I ended up just using the Taiwan version which had the identical model number, and falls in the same region as China. Odin falshed without complaint. The taiwan version has no restritions on google services, and once you set the language its hard to tell it from a regular AU one; unless you know what you are looking for that is.
Click to expand...
Click to collapse
it's unfortunate currently there is no solution to flash variant
jemfalor said:
it's unfortunate currently there is no solution to flash variant
Click to expand...
Click to collapse
Technically there are ways, just it is very grey as to when/how you trip the e-fuse. Some say if you simply unlock the bootloader and restart, others say when you load a bootloader that doesn't match model numbers, or is older than your current, or isn't offical samsung one. I personally don't know exactly. I do however know that i didn't trip the e-fuse when i loaded the taiwan version, and i didn't have to unlock the bootloader in developer options to achevie this.
streinhardt said:
Technically there are ways, just it is very grey as to when/how you trip the e-fuse. Some say if you simply unlock the bootloader and restart, others say when you load a bootloader that doesn't match model numbers, or is older than your current, or isn't offical samsung one. I personally don't know exactly. I do however know that i didn't trip the e-fuse when i loaded the taiwan version, and i didn't have to unlock the bootloader in developer options to achevie this.
Click to expand...
Click to collapse
nope. I've tried. unlocked bootloader still won't allow you to flash variant
jemfalor said:
nope. I've tried. unlocked bootloader still won't allow you to flash variant
Click to expand...
Click to collapse
oh. Good to know. Just wondering..Did you trip your e-fuse? If so when did it happen? Did you try extracting the PIT file from the CSC and using the PIT tab in odin? with the re-parition option selected?
streinhardt said:
oh. Good to know. Just wondering..Did you trip your e-fuse? If so when did it happen? Did you try extracting the PIT file from the CSC and using the PIT tab in odin? with the re-parition option selected?
Click to expand...
Click to collapse
you won't have the chance to trip. there is some check before the boot image is integrated. so it failed showing some error, auth or secure check failed etc etc.
if you flash variant home csc you will trip
TBH, I consider the Chinese version is the best version above all other region. The dual sim is enable on Chinese version, 512GB is the only available option.
As for google service. You don't need to change the Chinese firmware to Australian to enable it, the GMS is pre-installed. All you need to do is to find a way to install the google series apps as apk by yourself, it would work just fine.
tony_peng said:
TBH, I consider the Chinese version is the best version above all other region. The dual sim is enable on Chinese version, 512GB is the only available option.
As for google service. You don't need to change the Chinese firmware to Australian to enable it, the GMS is pre-installed. All you need to do is to find a way to install the google series apps as apk by yourself, it would work just fine.
Click to expand...
Click to collapse
BTW, the only version that Chinese region Fold 3 can change is the HongKong firmware, all other regions are not available. If you use Chinese region Fold 3 in Australia, the only thing you need to concern is the Samsung Pay, but Samsung Pay is fixed by the region and cannot be changed by switching the regional firmware.
tony_peng said:
TBH, I consider the Chinese version is the best version above all other region. The dual sim is enable on Chinese version, 512GB is the only available option.
As for google service. You don't need to change the Chinese firmware to Australian to enable it, the GMS is pre-installed. All you need to do is to find a way to install the google series apps as apk by yourself, it would work just fine.
Click to expand...
Click to collapse
Each to their own, if you like the chinese version great. I hated it, restrictions in every aspect of the firmware. I personally am unsure how you rate the chinese version better, when it is loaded with restrictions and hard coded settings that can't be changed, or if they can it is really a sub par workaround. Settings that are not present in standard android builds. What exactly does it have extra that makes it better? If you like it thou that is all that matters.
I loaded the taiwan version which yes is really just the hong kong version. No restrictions, no issues. Now it works just like any other standard samsung android build, you get in AU. Yes samsung pay that use the firmware version doesn't work great, but i prefer google pay anyway. No need to stuff around with downloading apk files from third party sites, for core functions. No need to even enable developer tools.
The chinese version sounds like driving a ferrari on a go karting track.....
Can you flash the Chinese or any international dual sim version to work in the US ?

Question Changing CSC for free using SamFW Tool | No Root required! - A brief guide!

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

Categories

Resources