Related
Hello friends,
I'm from Brazil and I bought a LTE Galaxy Watch in Germany, exactly the same version (Sm-R805F) used in Brazil. However when I went to my mobile company to activate the e-sim it was not possible. When the system ask to read a QR code, in the mobile networks' activation process, a message of error appears ("It's not possible to conect this mobile"). Does anyone know why and how to fix it?
Can you check this Code...
Code:
*#1234#
Seems DIFFERENT Software crap exists... so different Profiles...
Code:
OXX
OXA
Check your CSC ...
OXA could be inside German Version... and OXX is maybe for Brazil...
Best Regards
adfree said:
Can you check this Code...
Code:
*#1234#
Seems DIFFERENT Software crap exists... so different Profiles...
Code:
OXX
OXA
Check your CSC ...
OXA could be inside German Version... and OXX is maybe for Brazil...
Best Regards
Click to expand...
Click to collapse
Thank you very much!
I did it and the CSC is OXA (German version).
How can I change it to OXX?
PS: I did as they recomended here (https://forum.xda-developers.com/smartwatch/gear-s3/guide-how-to-change-gear-s3-r760-csc-t3784226 ) but theres no Brazilian code nor OXX.
OXX and OXA are """group"""
OXA contains minimum DBT CSC... for Germany
You can NOT change from OXA to OXX... because the config files not inside...
Your Link shows only way to change existing CSC inside flashed CSC file...
Example...
I have Firmware files... from OXX region...
Code:
CSC_[B]OXX[/B]_R805FOXX1BRI4_usr.tar.md5
You can unpack and extract with 7Zip... csc.img file.
Folder preconfig have 8 folderS with 7 CSC... DEF means Default IMHO...
Code:
BRI
TGY
VAU
XNZ
XSA
XSG
XSP
XSP is Singapore...
For the others I am tooo lazy... forgotten... use Google...
I have NO idea if it is an good idea to try to flash with netOdin such CSC files... or complete Firmware of OXX region.
Samsungs funny Security...
Best Regards
Edit 1.
I have tried to identify Brzil via Google search...
For me it looks no CSC inside for Brazil...
I have NO idea if SM-R805F is for Brazil market...
Edit 2.
Okidoki... Google search leads to this:
https://www.samsung.com/br/support/model/SM-R805FZSAZVV/
So looks like exists for Brazil... and you can see Sales Code ZVV it is in Product Code...
Code:
SM-R805FZSA[B]ZVV[/B]
IMHO 3 region groups... OXX OXA and ?
Firmware for Brazil seems not leaked... with ZVV inside...
Edit 3.
Firmware for SM-R805F for Brazil looks like this:
Code:
R805FXXU1CRK7/R805F[B]OWO[/B]1CRK7/R805FXXU1CRK7
So OWO is Region Code... for Brazil...
IMHO OWO package have ZVV Sales Code/CSC inside... for Brazil.
Edit 4.
My fault...
Code:
R805FXXU1DSC7_Tizen_4File_Multi CSC ([B]OWO[/B]).rar
Leaked and available...
But still no idea if this helps you... because dangerous to flash... Sams..g Security could prevent success...
adfree said:
Edit 4.
My fault...
Code:
R805FXXU1DSC7_Tizen_4File_Multi CSC ([B]OWO[/B]).rar
Leaked and available...
But still no idea if this helps you... because dangerous to flash... Sams..g Security could prevent success...
Click to expand...
Click to collapse
Hi,
Can you list the available CSC's within the OWO version ?
I wasn't able to find it for download to check by myself..
@Nocturney
Region OWO Firmware contains these CSC:
Code:
COM
ZTA
ZTO
ZVV
Best Regards
I've been reading the post, but I'm a little lost. I do not know what to do. I have a R815 Vodafone Germany version, and I want to activate it for movistar Spain, but I receive the error "It's not possible to conect this mobile". The data of my watch are the following:
AP: R815FXXU1ARH5
CP: R815FXXU1ARH5
CSC: R815FOXA1ARH5
With the SDB utility I have accessed a hidden menu on the watch and I changed the original CSC VD2 to XEC, or at least I thought so ... I think VD2 is Vodafone Germany, and XEC is Movistar Spain (the company that I have on my mobile phone). Samsung Pay works, but LTE is impossible to configure ("It's not possible to conect this mobile")
It is possible to get a different firmware and flash it?... or how can I get to configure an esim (lte) from movistar españa?
adfree said:
@Nocturney
Region OWO Firmware contains these CSC:
Code:
COM
ZTA
ZTO
ZVV
Best Regards
Click to expand...
Click to collapse
Awesome, Thanks for the info
Hey guys, I was reading this post and I have a problem a little different of you.
I bought a Galaxy Watch from The USA, LTE version (R805U) but I live in Brazil, I went to the phone company (VIVO) to try able the LTE (eSim) function but they said to me that it is impossible because only the R805F works here. My question is. Can I change the firmeware from 805U to 805F and it will works LTE here ?
secawan said:
I've been reading the post, but I'm a little lost. I do not know what to do. I have a R815 Vodafone Germany version, and I want to activate it for movistar Spain, but I receive the error "It's not possible to conect this mobile". The data of my watch are the following:
AP: R815FXXU1ARH5
CP: R815FXXU1ARH5
CSC: R815FOXA1ARH5
With the SDB utility I have accessed a hidden menu on the watch and I changed the original CSC VD2 to XEC, or at least I thought so ... I think VD2 is Vodafone Germany, and XEC is Movistar Spain (the company that I have on my mobile phone). Samsung Pay works, but LTE is impossible to configure ("It's not possible to conect this mobile")
It is possible to get a different firmware and flash it?... or how can I get to configure an esim (lte) from movistar españa?
Click to expand...
Click to collapse
Is not to you to do'it...
You need to call the operatório, in this case, Movistar and subscribe for the service and they activate the eSim...
Sent from my Samsung SM-G975F using XDA Labs
Hi had same problem
Hello mate
I bought Samsung Galaxy watch when I was on holidays in Greece as in UK the LTE version was only with contract on EE. As I'm using Vodafone UK, I got the Qr Code for the esim but Samsung neither Vodafone could help me to make it work. Finally I make It work but my self, because my Samsung Galaxy watch is from Greek region I try to activate my Vodafone uk esim with a Greek sim network in my mobile device and it's worked perfectly, even when I put back my Vodafone uk sin on my mobile.
Hope that helps you.
MrNtrev said:
Hello mate
I bought Samsung Galaxy watch when I was on holidays in Greece as in UK the LTE version was only with contract on EE. As I'm using Vodafone UK, I got the Qr Code for the esim but Samsung neither Vodafone could help me to make it work. Finally I make It work but my self, because my Samsung Galaxy watch is from Greek region I try to activate my Vodafone uk esim with a Greek sim network in my mobile device and it's worked perfectly, even when I put back my Vodafone uk sin on my mobile.
Hope that helps you.
Click to expand...
Click to collapse
Hi, could you elaborate on how you did that? I want to buy the silver LTE version from Hong Kong because that colour is not sold in Singapore, and it would be great if I could get the LTE working.
Rbs_fael said:
Hey guys, I was reading this post and I have a problem a little different of you.
I bought a Galaxy Watch from The USA, LTE version (R805U) but I live in Brazil, I went to the phone company (VIVO) to try able the LTE (eSim) function but they said to me that it is impossible because only the R805F works here. My question is. Can I change the firmeware from 805U to 805F and it will works LTE here ?
Click to expand...
Click to collapse
Sou do Brasil tambem e estou com o mesmo problema e duvida. Vocë conseguiu resolver?
I've tried to debrand my phone by flashing open market firmware (XEO, Poland). I downloaded the newest version of Odin, flashed it but now my CSC under settings says OPV/OPV, OPV/EUX/OPV. OPV is my carrier's CSC, I'm wondering what that EUX is. I've looked it up on Google and it seems like I'm not alone, seems like Samsung changed something and older methods no longer work. The question is - will I still receive updates released for my carrier or I'm screwed for good? Phone INFO app says my active CSC is OPV. I'm running S20+ 5G (G986B) Exynos variant.
Same problem here, I've flashed it with XEO POLAND G986BXXU1ATBM firmware using Odin3 v3.14.1_3B_PatcheD, few minutes later it showed "PASS" and nothing changed. Same branded firmware after reboot..
It seems, that many more 'branded' CSCs are now part of Multi-CSC. For me, this is DTM (T-Mobile DE). It osed to not be part of multi-CSC but it is now part of OXM.
This means, that you can not force it anymore, as you already ARE having the exact same firmware with the 'branded' CSC. Just checked, OPV is in deed part of OXM now.
In the Ultra Section is a thread showing the CSCs belonging to OXM: https://forum.xda-developers.com/ga...galaxy-s20-ultra-g988b-firmwares-5g-t4060443/
I have not yet found out / gotten an answer from anybody how to change CSC. Samkey also is not supporting the S20 series ATM - dont know, if this will change.
Monnq said:
I've tried to debrand my phone by flashing open market firmware (XEO, Poland). I downloaded the newest version of Odin, flashed it but now my CSC under settings says OPV/OPV, OPV/EUX/OPV. OPV is my carrier's CSC, I'm wondering what that EUX is. I've looked it up on Google and it seems like I'm not alone, seems like Samsung changed something and older methods no longer work. The question is - will I still receive updates released for my carrier or I'm screwed for good? Phone INFO app says my active CSC is OPV. I'm running S20+ 5G (G986B) Exynos variant.
Click to expand...
Click to collapse
What I have worked out is that when you flash a multi-CSC firmware file you end running the CSC one letter earlier in the alphabet out of the. Available multi-CSC list
E.g. I had a VOD branded S105G and flashed BTU firmware, and ended up with TEL CSC
I also tried flashing BTU on an H3G branded A70 and ended up with EVF CSC
The original branded product CSC also never changes
---------- Post added at 11:32 AM ---------- Previous post was at 11:30 AM ----------
Andrino said:
Same problem here, I've flashed it with XEO POLAND G986BXXU1ATBM firmware using Odin3 v3.14.1_3B_PatcheD, few minutes later it showed "PASS" and nothing changed. Same branded firmware after reboot..
Click to expand...
Click to collapse
Enable Developer mode and set OEM Unlock to ON before trying to change CSC via ODIN Flash
This should not be necessary? Doesn't that trip Knox, despite original Samsung Firmware?
corwin_amber said:
It seems, that many more 'branded' CSCs are now part of Multi-CSC. For me, this is DTM (T-Mobile DE). It osed to not be part of multi-CSC but it is now part of OXM.
This means, that you can not force it anymore, as you already ARE having the exact same firmware with the 'branded' CSC. Just checked, OPV is in deed part of OXM now.
In the Ultra Section is a thread showing the CSCs belonging to OXM: https://forum.xda-developers.com/ga...galaxy-s20-ultra-g988b-firmwares-5g-t4060443/
I have not yet found out / gotten an answer from anybody how to change CSC. Samkey also is not supporting the S20 series ATM - dont know, if this will change.
Click to expand...
Click to collapse
Since now it's part of Multi CSC, does that mean I will receive updates faster? I can see other polish carrier's CSC are listed as single so I assume they are kind of separate firmware, am I right?
Honestly I do not know, if the respective CSC will be getting OTAs at the same time.
However, you can always flash manually with HOME_CSC, that is true.
corwin_amber said:
This should not be necessary? Doesn't that trip Knox, despite original Samsung Firmware?
Click to expand...
Click to collapse
Enable OEM unlock does not trip Knox. As long as you flash official Samsung firmware files in Odin Knox is never tripped
My own personal experience on S10 and above is you cannot flash a different CSC with OEM Unlock disabled
(Flash completes successfully but CSC doesn't change)
When changing from one e.g. branded csc to multi csc with the S10+, this worked fine without enabling oem unlock. Well, anyway. Flashing OXM multi CSC over OXM multi CSC will not change anything, right?
corwin_amber said:
When changing from one e.g. branded csc to multi csc with the S10+, this worked fine without enabling oem unlock. Well, anyway. Flashing OXM multi CSC over OXM multi CSC will not change anything, right?
Click to expand...
Click to collapse
I found that you have to be on a single CSC before flash to multi-CSC and also you don't always end up on the CSC you expected
e.g. Flash BTU on a VOD product and you end up on TEL CSC (one letter in alphabet below VOD) and not on BTU
did everyone succesed DEBRAND ?
i v got s20 ultra OPV(orange) and need XEO (official)
tak, poprzez samkey
Yes, with samkey
@0kti if you have any credits remain let me know please ( I will buy it )
I found link to our android com pl forum , thanks
Nope. Buy on ebay. It's cheap. 3 credits.
Tapatalk - SM-G986B
one credit please, somebody will share ?
raphaelx69 said:
one credit please, somebody will share ?
Click to expand...
Click to collapse
really lmao.. its literally a few bucks... chimera tool works great also but is a mpre expensive subscription but dont gotta kee0 buyin credits
I'm living in europe and I'm using S20 Ultra exynos variant, I'm planning to get S20 Ultra Korean variant to get the snapdragon 865 chip. But my questions are is it possible to debrand it? I read few articles that it has so many bloatwares, also is it possible to unlock BL and root it? My last concern is about the 5G, wonder if 5g work on my country with the Korean variant.
Thanks.
I'm owning a SM-G981N, carrier branded phone. Regarding bloatware, there are plenty of tutorials that can be found here to get rid of the majority of bloatware. The only way to be completely bloatware/carrier info free is to change CSC and flash the unlocked rom for your device. It seems possible to do with some third party software (samkey), but I haven't done so yet.
I have OCD when it comes to bloatware and or carrier info, I can't stand the fact that something is not original samsung. I have to say that after removing bloatware, except for the bootanimations, I really don't notice that I'm on a carrier branded phone anymore. If you dig deep enough, you will always find a handful of settings/options that shows you are on a carrier phone. Besides that, no problem at all.
I can't answer your questions regarding unlocking BL or rooting, but i assume in the near future this would be possible (if not already).
For 5G, you want to check your 5G provider's data protocol. If your phone supports it, then it should work no problem. Data for your phone can be found anywhere, example: http://phonedb.net/index.php?m=devi...ultra_5g_td-lte_kr_256gb__samsung_hubble_2_5g
Good luck!
That's possible my friend. I have successfully debranded over samkey from KTC (KorenTelecom) to KOO (OpenKorea) without loosing any of my data on my phone. I'm also from Europe!
Thanks again to @mishufac
Gesendet von meinem SM-G988N mit Tapatalk
nobrain3000 said:
That's possible my friend. I have successfully debranded over samkey from KTC (KorenTelecom) to KOO (OpenKorea) without loosing any of my data on my phone. I'm also from Europe!
Thanks again to @mishufac
Gesendet von meinem SM-G988N mit Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I wonder if we can flash it from KOO to BTU.
iampatricktan said:
Thanks for the reply. I wonder if we can flash it from KOO to BTU.
Click to expand...
Click to collapse
No mate. They are two different models. Using two different processor.
west2cool said:
No mate. They are two different models. Using two different processor.
Click to expand...
Click to collapse
So we can only flash the korean firmwares only? Alright.
iampatricktan said:
So we can only flash the korean firmwares only? Alright.
Click to expand...
Click to collapse
That's right!
Gesendet von meinem SM-G988N mit Tapatalk
Hi Mate,
After debranded, are you able to use Volte, wifi calling, 5G in Europe on the SD865 version.
Thanks
No 5g here at the moment. I think you need your home csc to use voip and wifi calling there but I'm not sure!
Gesendet von meinem SM-G988N mit Tapatalk
Yesterday I succesfully changed my CSC using Samkey. I've already flashed the KOO firmware of the rom prior to changing the CSC, but according to Samkey support, the firmware for these korean phones is the same. This would mean only changing CSC should debrand your phone. I managed to change CSC without any loss of data, it simply reboots afterwards and it's fully debranded!
tijsva said:
Yesterday I succesfully changed my CSC using Samkey. I've already flashed the KOO firmware of the rom prior to changing the CSC, but according to Samkey support, the firmware for these korean phones is the same. This would mean only changing CSC should debrand your phone. I managed to change CSC without any loss of data, it simply reboots afterwards and it's fully debranded!
Click to expand...
Click to collapse
chimera tool changes csc on my g988u no problem
can this be done using ODIN? I tried to flash the open korea KOO over my KTC branded S20Ultra but it still go back to KTC after. Any way to fix this?
tijsva said:
Yesterday I succesfully changed my CSC using Samkey. I've already flashed the KOO firmware of the rom prior to changing the CSC, but according to Samkey support, the firmware for these korean phones is the same. This would mean only changing CSC should debrand your phone. I managed to change CSC without any loss of data, it simply reboots afterwards and it's fully debranded!
Click to expand...
Click to collapse
I tried to see if the G988N (KT Korean version) but it says not supported at their samkey website. How did you do it? It only support G988B so far
Rithina said:
I tried to see if the G988N (KT Korean version) but it says not supported at their samkey website. How did you do it? It only support G988B so far
Click to expand...
Click to collapse
Correct, I received the same message, however changing CSC was still successful.
Rithina said:
can this be done using ODIN? I tried to flash the open korea KOO over my KTC branded S20Ultra but it still go back to KTC after. Any way to fix this?
Click to expand...
Click to collapse
I've already answered both of your questions in this topic, please read.
Can this be done using ODIN?
https://forum.xda-developers.com/showpost.php?p=82435697&postcount=2
I tried to flash the open korea KOO over my KTC branded S20Ultra but it still go back to KTC after. Any way to fix this?
https://forum.xda-developers.com/showpost.php?p=82565687&postcount=10
tijsva said:
Yesterday I succesfully changed my CSC using Samkey. I've already flashed the KOO firmware of the rom prior to changing the CSC, but according to Samkey support, the firmware for these korean phones is the same. This would mean only changing CSC should debrand your phone. I managed to change CSC without any loss of data, it simply reboots afterwards and it's fully debranded!
Click to expand...
Click to collapse
yes I have g988n and changed to KOO with samkey if ur 5g band in Europe in n78 5g will work but regarding VOLTE it may not work
Yesterday I debranded my SM-G988N, different logo when booting and lots of Korean bloatwares. First I flashed it via Odin (KOO firmware) then after that I used SamKey to change CSC.. Credit needed is just 1. So now my phone is debranded already, back to Samsung logo when booting and no korean bloatwares.
New firmware available with camera improvements, may security patch and system stability improvements!
Gesendet von meinem SM-G988N mit Tapatalk
Could some one grab a screen shot of your NFC settings, please.
I noticed on a Korean tech YouTube video, they have an extra option in the nfc settings.
I think it's related to nfc door locks etc.
try getting the hong kong version , that has the snapdragon as well and is over 100 cheaper than samsung prices
Hello community!
I recently bought a Samsung Galaxy S20+ (SM-G985F) which is carrier branded and sim locked. I am looking to remove the carrier branding by using a unbranded firmware. I am trying to find an unbranded firmware that will not affect the functionalities of the phone ( VoLTE, VoWiFi etc..) . Would this be done by finding a firmware with same PDA but different CSC?
Current Branded Firmware:
Version G985FXXU3ATG4 / G985FOWA3ATG4 / G985FXXU3ATG4
Product Code: PGU
Would this firmware work?
Product code LUX
PDA G985FXXU3ATG4
CSC G985FOXM3ATG9
Thanks in advance for your help!
@servenaya
if you have a sim card of Guatemala and you want to keep VoLTE, VoWiFi etc.. for this country
install Version PDA G985FXXU3ATG4-CSC G985FOXM3ATG9
and change your CSC to GTO ( with préconfiguration for TIGO_CGU , PCW_PA and Claro_DR )
LUX have only préconfiguration for Luxemburg ( Proximus , POST , Tango , Telenet , Orange B and LUX )
regards
yakapa40 said:
@servenaya
if you have a sim card of Guatemala and you want to keep VoLTE, VoWiFi etc.. for this country
install Version PDA G985FXXU3ATG4-CSC G985FOXM3ATG9
and change your CSC to GTO ( with préconfiguration for TIGO_CGU , PCW_PA and Claro_DR )
LUX have only préconfiguration for Luxemburg ( Proximus , POST , Tango , Telenet , Orange B and LUX )
regards
Click to expand...
Click to collapse
@yakapa40, thank you! This information is very helpful. I do have a Claro Guatemalan sim and even though the carrier does not support VoLTE, or VoWifi, I would like to keep this features in case they implement them in the future. I did find a firmware with the recommended PDA and CSC (Country South East Europe, Product code: SEE, PDA: G985FXXU3ATG4, CSS: G985FOXM3ATG9). Would this firmware work? From what understand, I would have to first flash this firmware, then change de CSC with Samkey to GTO and lastly, factory restore the phone. Is this correct?
Also, would you recommend using Samkey to perform a carrier unlock before changing the CSC or could I do it later on? I read that Samkey only works for phones that dont ask for unlock code. Mine does ask for a code when I insert another carrier's sim.
Thanks in advance for your help!
save all your data
install new firmware
you have a free apk here to change the CSC:
https://forum.xda-developers.com/showpost.php?p=82858645&postcount=37
yakapa40 said:
save all your data
install new firmware
you have a free apk here to change the CSC:
https://forum.xda-developers.com/showpost.php?p=82858645&postcount=37
Click to expand...
Click to collapse
@yakapa40, Thank you once again. Just want to make sure that the firmware mention before is the best one to use? I have attached the software information from my phone. Please let me know your opinion.
yes all is ok with your firmware
PGU:
GTO:
yakapa40 said:
yes all is ok with your firmware
PGU:
GTO:
Click to expand...
Click to collapse
@yakapa40 Thank you for your help. You are extremely knowledgeable on this topic! To be honest, I just realize how little I know about flashing even though I've been doing it since 2012. I feel like I understand firmware flashing less than I did before.
I just have a last question. If I flash the firmware with a CSC NEE, and than do the CSC change to GTO, which CSC will be used for future OTA updates? What I mean is, if there is a new NEE firmware will I get it, or will I have to wait for a new GTO update? Sorry, I am little confused with all of this.
G985F OXM is a multi CSC so if you flash the firmware with a CSC NEE , you will get XEF CSC by default
, and when you change to GTO you will get GTO OTA updates
https://forum.xda-developers.com/galaxy-s20/how-to/s20-g985f-firmwares-t4060279
yakapa40 said:
G985F OXM is a multi CSC so if you flash the firmware with a CSC NEE , you will get XEF CSC by default
, and when you change to GTO you will get GTO OTA updates
https://forum.xda-developers.com/galaxy-s20/how-to/s20-g985f-firmwares-t4060279
Click to expand...
Click to collapse
@yakapa40, I was finally able to flash the phone. I followed the steps and got the GTO CSC and the unbranded firmware working! Thank you for helping me throughout the whole process. The only down side was that I still lost the VoLTE and VoWifi options. When I look at the Sim Card Status menu, the IMS registration Status is "not registered". :crying:
Hi All,
I have a Samsung Z fold 4 ‐ SM-F936N model (Korea version). I want to use it in India. Can I flash BL, AP and CP from SM-F936N firmware and CSC and Home CSC from SM-F936B (india compatible version)'s firmware (CSC as OXM, and Home CSC as INS)?
Want to do this primarily for Samsung Pay and removing Korean telecom files which came installed by default.
Also, assuming it is possible, will it impact OTA update?
Pdash said:
Hi All,
I have a Samsung Z fold 4 ‐ SM-F936N model (Korea version). I want to use it in India. Can I flash BL, AP and CP from SM-F936N firmware and CSC and Home CSC from SM-F936B (india compatible version)'s firmware (CSC as OXM, and Home CSC as INS)?
Want to do this primarily for Samsung Pay and removing Korean telecom files which came installed by default.
Also, assuming it is possible, will it impact OTA update?
Click to expand...
Click to collapse
I Can´t speak without doubs, but, AFIK, you can´t mix firmware files nor use firmwares from different HW versions...
Pdash said:
Hi All,
I have a Samsung Z fold 4 ‐ SM-F936N model (Korea version). I want to use it in India. Can I flash BL, AP and CP from SM-F936N firmware and CSC and Home CSC from SM-F936B (india compatible version)'s firmware (CSC as OXM, and Home CSC as INS)?
Want to do this primarily for Samsung Pay and removing Korean telecom files which came installed by default.
Also, assuming it is possible, will it impact OTA update?
Click to expand...
Click to collapse
No different models You will end up with a bricked phone.
cooldude20000 said:
No different models You will end up with a bricked phone.
Click to expand...
Click to collapse
Thanks for your post. Saved me from attempting a disaster.
rafafischer said:
I Can´t speak without doubs, but, AFIK, you can´t mix firmware files nor use firmwares from different HW versions...
Click to expand...
Click to collapse
Thanks a tonne for your reply. Not gonna attempt it.
I have the same problem. I am unable to change the primary csc and it won't pay
luisvaljun said:
I have the same problem. I am unable to change the primary csc and it won't pay
Click to expand...
Click to collapse
Flashing firmware does not change csc u have to use something like samkey or samfw csc changer
Can you use 5G in India I have the same model and I can’t I want to use 5G
I successfully flashed my fold4 from US Verizon to US AT&T but video call doesn't work. Flashing from completely different region models might be more problematic.