Question S23 Ultra - CSC Change Questions - Samsung Galaxy S23 Ultra

Hi, I have an S23 Ultra (SM-S918B) and had a few questions about changing CSC.
1) I currently have XSG. I want to change to a CSC that:
- Has native call recording
- Is in the list of supported beta program regions (Check question 2)
- Is unlocked (Accepts any SIM)
- Won't cause any issues (For example some apps not working, device losing Google Play certification etc.)
- (Optional) Gets updates usually fast
Which CSC should I choose? I was thinking of INS, as it fits all the criteria, though please recommend a CSC to me.
2) On the topic of beta program, does changing CSC even allow for that? I couldn't find a solid answer online.
3) Will my warranty be voided? Again, couldn't find a solid answer.
4) Which tool should I use to change CSC? I've heard of a few but want to know which is recommended (without wiping my phone). I also have the June update (AWF1) and since updates usually tend to patch the use of stuff like this, please recommend a tool that'll work.
5) Can you guys send me a GOOD tutorial for the recommended CSC changing tool (video preferred) that has up-to-date info and has any info I might need?
6) After changing CSC, will I get OTA updates?
7) After the change, nothing will happen to my IMEI right?
8) Does this have any risks, such as the phone getting bricked? If so, how likely is it? If anyone has changed their CSC before, could you please share your experience?
9) I currently have AWF1, whilst some places like India (INS as I was thinking to change to) never got AWF1 and skipped to AWF3. Will different firmware version matter? Like will it cause issues? Or should I wait until we get the same firmware version?

Related

[Q] Possible to change Lumia 800 firmware to another region?

Hi guyz,
I have a Nokia Lumia 800 with me of UK region and I dont mean just software wise. The actual phone was shipped from UK and the product code is 059J3G0
Now I reside in India and due to this region differences many of the features dont work especially USSD which is proving problematic since its difficult to even check my balance.
So is it possible to change my firmware to Indian version?
Thanks.
Possible very much, infact I have updated to the latest UK firmware, but will flash it back to the original White Lumia 800 firmware
mohib.sheth said:
Hi guyz,
I have a Nokia Lumia 800 with me of UK region and I dont mean just software wise. The actual phone was shipped from UK and the product code is 059J3G0
Now I reside in India and due to this region differences many of the features dont work especially USSD which is proving problematic since its difficult to even check my balance.
So is it possible to change my firmware to Indian version?
Thanks.
Click to expand...
Click to collapse
Yes you can
1) goto seidea[dot]com and start off by downloading the Nokia Care Suit and Data Package Manager.
2) After installation of both also install the WinUSB driver from C:\Program Files\Nokia\Nokia Care Suite\Drivers or C:\Program Files(x86)\Nokia\Nokia Care Suite\Drivers
3) Connect your phone with the Nokia Support Tool for Store open, this programme will have a launcher in the main Nokia Care Suite, and should have detected your phone, disconnect cable, this might restart your phone, this is normal.
4) Next fire up the Data Package Manager and search for RM-801 in product type, this will return a bunch of different variations of the firmware. In the cell below Name type India and download any of the firmwares you want, possibly to match the colour of your phone as well.
5) After download fire up the Nokia Support Tool for Store, change it to offline mode at bottom right, or simply disconnect from the Internet,from the file menu, select Open Product and select product RM-801
6) From the bottom left pane, select Programming and then Recovery and select the new firmware you just finished downloading.
7) Flashing should take 5-7 minutes and leave the phone un-attended. Voila
Again I take no responsibility for any dammage to your phone, and you may download and flash any firmware from the entire list under RM-801 should not be a problem.
Additionally you may also want to take a backup from WP7 Easy Backup, google it or search the forums for it.
regards
Prateek
mohib.sheth,
no problems at all, i´m from Brazil and i updated to test Tango one from Mexico and another from UK, both worked like a charm.
U can follow this thread if u have any issues, like dead phone, errors or different Product Code
RM-819 Firmware on RM-801 thanks to thesmartguyy
or simple follow the original one Tango:
New update !! Rm801_059q201_1750.0805.8773.12220_002 thanks to surya467
Thank you so much lohiaprateek and xpc21 for the steps.
Another query is If I do flash to India firmware, will I get update from regular Zune or I will need to keep flashing to the latest firmware manually?
Zune should prompt the update ideally..
mohib.sheth said:
Now I reside in India and due to this region differences many of the features dont work especially USSD which is proving problematic since its difficult to even check my balance.
Click to expand...
Click to collapse
USSD is not supported (fully) in Windows Phone so as far as that goes changing to an Indian FW will not make any difference.
paulheu said:
USSD is not supported (fully) in Windows Phone so as far as that goes changing to an Indian FW will not make any difference.
Click to expand...
Click to collapse
Thanks for the information. Silly me, should have researched that before asking the question
Thanks for saving me the hassle.
Thanks a lot for the thread and all the members...thanks a lottttttttttttttttttttttttttttt

Investigating repair of Emergency Only issue on Galaxy S6 Edge

Hi all!
I bought an S6 Edge second hand and after flashing a stock ROM, I had the "emergency only" calls issue, I tried everything I could find in the forums to no avail and I ended up taking it to a repair service. I did not think they could fix it but they did and I would like to know what they did to it in order to prevent it from happening again and to know if I can leave it as default (not custom OS) so that it can upgrade.
State of phone when bought:
So, the phone was working well with all carriers (from Colombia). The only thing I was able to notice after I bought it was that it was still on Marshmallow (6.0.1) with carrier branded stuff. It was in perfect shape otherwise.
So I downloaded a stock ROM and installed it using Odin. After this the phone would not let me make calls as it was not registering on the network. It did not even let me make emergency calls despite getting full bars of signal and being able to recognise the list of carriers when attempting to manually connect to them.
Important: The ROM downloaded was for the right version of the phone which was the G925i and the IMEI, serial number and baseband were not altered from the original. Also, I checked the phone to see if it was reported as lost/stolen and it was not (of this I'm sure because in Colombia you can consult a centralised database on any carrier's webpage). Also.. Here in Colombia it is illegal for carriers to lock phones.
Steps I took to fix it:
Downloaded ROMs for all carriers, branded and unbranded, I even installed one from Trinidad and Tobago and a LATAM one.
I performed all the tricks to disable and enable flight mode, location services, try con connect manually to the networks, changing to GSM only, GMS/CDMA, international roaming, etc.
I also extracted modem.bin from an earlier version and flashed the modem.bin with Odin (6.0.1 moden on 7.0, 5.1.1 moden on 6.0.1 and 5.1.1 moden on 7.0). All modems flashed correctly and the issue remained exactly the same.
So I finally gave up.. I installed the latest stock ROM which was an unbranded Nougat (7.0) version and took it to a repair service and they fixed it in a couple hours.
What I noticed after the phone was "repaired":
- The phone was rooted, SuperSu was installed, no other root app was installed.
- On SuperSu, there are entries for ADB shell (they all say Superuser command contents have not been logged for this entry) in a two minute timespan.
- The android version was downgraded to 6.0.1, I was told not to try to update it.
- Developer options was enabled with USB debugging turned on.
- The boot option (the one where you can wipe data and cache partition) was left as original (not the TWRP one).
- The ROM used to downgrade was the same I had before but only downgraded the version.
I suspect this same procedure was performed before on the phone but it had the original ROM carrier branded so it seems as if they installed a custom ROM, rooted it, connected with pc and performed some command line stuff to fix it, then cleaned the bootloader to a stock one.
The questions:
Any ideas what did the repairman do to fix the phone? Also, would it be safe to make a full backup with TWRP and flash again a stock ROM upgraded to 7.0 and then flash the backed up modem to get it working? Or would that possibly screw up the repair?
Thank you all in advance for any help. I'm sure there are lots of people out there experiencing the same "emergency only" issue I had but there does not seem to be a fix around, but clearly there is one! So I hope this sheds some light into what could possibly happen.

Piggybacking VoLTE and Wifi calling from XZ1 Compact USA firmware?

I have T-Mobile in the US, and they recently got rid of one of the bands my phone was relying heavily on, so I want to be able to do calls over wi-fi and VoLTE which is not currently a feature with the international firmware I have. Since the Z5 Compact hardware technically has the capability to do this with other carriers using the EE firmware, and the XZ1 Compact is specifically able to do this with T-Mobile with the US firmware, is there a way to either flash just the bits I need or root and install the whole XZ1 Compact ROM on my Z5 Compact?
Sorry if this is a dumb question, I've been reading about how folks buying the XZ1 Compact are flashing bits and pieces to get wi-fi calling and VoLTE working with the fingerprint reader (normally disabled in the US version), and thought if there's a trick I can do with my existing phone it might save me $500.
Z5 Compact stock rom already have VoLTE and VoWiFi function, but the option only appear if the network supports it, but probably not on the us firmware?
gspbeetle said:
Z5 Compact stock rom already have VoLTE and VoWiFi function, but the option only appear if the network supports it, but probably not on the us firmware?
Click to expand...
Click to collapse
I have Hong Kong firmware that came with the phone. T-Mobile doesn't support the phone here in the US, but I did notice that there are firmware versions (Czech, Austrian, a couple others) that are T-Mobile branded. Is it worth a try to flash one of those (assuming it does include VoLTE), or for this purpose, would T-Mobile in another country be considered another carrier?
T-Mobile here in the US seems to be heading toward 100% VoLTE with only one 2G band left in my area. However, at least in the US, T-Mobile has not certified the Z5 Compact for VoLTE. I think the only Sony phone they've certified is the new XZ1 Compact. Does that mean I'm out of luck, or is there some kind of work-around?
I also have this issue, but I'm more of a noob to this than most people here, including the OP. I have a few fundamental (probably stupid) questions:
bokononisidore said:
I have T-Mobile in the US, and they recently got rid of one of the bands my phone was relying heavily on, so I want to be able to do calls over wi-fi and VoLTE which is not currently a feature with the international firmware I have.
Click to expand...
Click to collapse
1.) How do you know this? How do you track what band(s) your phone is using?
bokononisidore said:
T-Mobile here in the US seems to be heading toward 100% VoLTE with only one 2G band left in my area. ?
Click to expand...
Click to collapse
1.a.) Again, how do you know that there's only that one band left?
bokononisidore said:
I have Hong Kong firmware that came with the phone.
Click to expand...
Click to collapse
2.) How can I check exactly what firmware I have? I got an international version when I ordered it from Amazon, so I didn't even have to flash anything to enable the fingerprint sensor. I also know it was from a Spanish country because everything was in Spanish when I booted it for the first time. But how do I know verify which version it is exactly?
Also, OP, did you ever resolve this?
I don't use forums too much, so I have a feeling I'm going to be commenting here within the quote. Sorry about that. I hope this is helpful.
fr0zensphere said:
I also have this issue, but I'm more of a noob to this than most people here, including the OP. I have a few fundamental (probably stupid) questions:
1.) How do you know this?
I called T-mobile, and this is what they told me. In fact, it was so bad for their customers in my area that they were offering a special deal on new phones just to people in my service area.
How do you track what band(s) your phone is using?
I can't remember the code I used, but google "hidden codes xz1 compact" and you'll find a service code to see the settings. Be careful not to use one that will reset the phone.
1.a.) Again, how do you know that there's only that one band left?
Both through speaking with their tech support and reading their press releases online.
2.) How can I check exactly what firmware I have? I got an international version when I ordered it from Amazon, so I didn't even have to flash anything to enable the fingerprint sensor. I also know it was from a Spanish country because everything was in Spanish when I booted it for the first time. But how do I know verify which version it is exactly?
This is going to be in one of those service codes.
Also, OP, did you ever resolve this?
Click to expand...
Click to collapse
I ended up buying an XZ1 Compact and flashed the firmware for the international version with one portion using the US firmware. What I originally wanted to do couldn't be done with the old phone.
I made myself a file of notes back the first time I was taking care of all of this. These are not my words, but direct quotes from various forums, but I didn't keep all the sources so I'm afraid I'm unable to cite them properly. However, before embarking on this process, I should tell you that I haven't had any push updates since I did this over a year ago, and I haven't figured out how to repeat the process to update with new firmware. Good luck!
You can probably try googling some phrases from these in quotes to find the original sources:
I tried just those two files and didn't have any luck.
ETA - man, am I dumb! I accidentally was flashing the system_X-FLASH-ALL-C93B.sin and vendor_X-FLASH-ALL-C93B.sin files from the US firmware instead of the CE firmware! Once I used the correct files, it worked perfectly.
So to summarize (and definitely do at your own risk!)
0) I backed everything up.
1) I didn't load drivers because I had them.
2) I followed the directions at the link below to get xperifirm and newflasher, then used xperifirm to download the Xperia XZ1 poplar roms for G8432 Central Europe 1
3) I copied the two files listed above to my newflasher directory.
4) I shut down the phone, waited 5 seconds, then held down the volume down key and plugged it into my PC using a USB A to C cord.
5) I ran newflasher as administrator, and chose N when it asked if I wanted to load a driver
6) When newflasher told me I was done, I unplugged the phone and started it up.
The fingerprint scanner works, group texting works, and my system is showing the same signal strength!
See my screens in the prior 2 posts. It's really much easier than what you are describing. Download the Customized UK firmware from Xperifirm. Download the Customized US firmware from Xperifirm. Copy the system sin file and vendor sin file from UK firmware and replace the files in US firmware with the copied files. Flash the modified US firmware using newflasher tool. Bingo!
So I decided to take the plunge on this with the XZ1 Compact at least. Not only do I have the fingerprint sensor working, but also WiFi Calling and VoLTE on T-Mobile US.
I took the oem_X-FLASH-ALL-C93B.sin from the US Customized version, and overwrote the one included with the UK (Device is UK Model) version, and then proceeded to flash with Newflasher.
Everything seems to be working without issue. I couldn't possibly enjoy this phone more now.
I am being a bit lazy and will refer you to XZ1 Compact thread. pbarrette has done amazing job with figuring out all the bits and writing out how stuff works
Start reading from this post https://forum.xda-developers.com/sho...9&postcount=35
Most informative post is here https://forum.xda-developers.com/sho...&postcount=105
In summary, oem.sin from XZ1 Compact "Customized US" should be used to flash XZ1. All other *.sin etc files should be from XZ1 firmware (can use other region for fingerprint reader support).
Create folder caled 'partition', extract partition.zip into that folder and it will get flashed.
To put the phone in flash mode, you need to:
1] Power the phone off.
2] Press and hold the Volume Down Button.
3] While doing #2, plug the phone into your computer.
Device Manager should show an Unknown or Other device. Quite possibly the one above what you think is the right one.
It will have a device descriptor like this USB\VID_0FCE&PID_B00B in the "Details" tab.
Run newflasher and answer Y to the GordonGate driver.
It will exit after having dumped a zip file into the newflasher directory.
Unzip and install that driver for the device described above.
---
I know userdata.sin and fota-reset.ta is responsible for wiping userdata so its safe to delete these two files in case you need to keep userdata, but cust-reset.ta and master-reset.ta somebody need to try and let us know if these two files is also responsible for wiping userdata. The rest of ta files is ALWAYS recommended for flashing, don't skip it! Simlock.ta is by default skipped so you no need to delete it.
http://www.xperiablog.net/2018/01/2...-firmware-for-xperia-xz-premium-xz1-and-more/
https://forum.xda-developers.com/xperia-xz1/help/flashing-international-firmware-model-t3683552
maybe best description
A quick update since my last reply:
I mentioned not being able to repeat the process. Turns out, it's because I didn't have the driver installed, which is basically step one. So user error, not related to any risk or issue with having flashed the custom rom to the phone.

How to find CSC on brick phone

Just bought a samsung SM-N690F/DS. Newbie with rooting. I tried root but got stuck on SAMSUNG screen logo. I playing with TWRP and end clean whole the phone. I can only booty TWRP and get to DOWNLOAD MODE. I'M looking for the stock rom but i need csc code not sure which region my phone is? is way to find out...I find download mode...but not seeing anything look like csc code. Thanks for any help
Your phone can have any of the supported CSC codes, you just have to flash it.
For start just flash the latest and everything should go back to stock, use this link (https://www.sammobile.com/samsung/galaxy-note9/firmware/SM-N960F/DBT/download/N960FXXS8FUC4/1511407/) or use frija for faster download speeds. It will show as Germany but it is universal(for exynos - N960F - make sure the F is exactly your letter, there are more linke N or U).
After that you should find your country csc code, you can go to this link and select your country(https://www.sammobile.com/samsung/galaxy-note9/firmware/#SM-N960F).
CSC codes are dependent of region(like country) and carrier(SIM network provider). You can choose a specific carrier or use your country(this should have all your country carriers included and no carrier bloat apps included)

Question A528B/DS - CSC Change to BTU Won't work

I have an A528B/DS with the CSC XEO, however I want it to be changed to BTU.
I've tried using SamKEY and Chimera ands both said that the phones weren't supported even though they are on the supported models list. I spoke to a member of customer service from each of them and I was told the security firmware if too advanced but they are working on a method to resolve this.
I have also used ODIN with multiple flash files but none were able to change the CSC.
I have seen these phones being CSC changed multiple times with he latest firmware on them so I am fully aware there is a way to do it, I just cannot work out how. I keep sending my phones to someone to do it but for obvious reasons they won't tell me how to do it.
I don't want to root the phone as I don't want to void the KNOX and other than that I haven't been able to find a way online to resolve it.
I also have this problem with G780G and G781, N986B and some A other series Samsung's.
If anyone can help or has any ideas on what I can do, please could you reply to this and point me in the right direction as I am at a dead end.
Any news?? I have the same phone, A528B, and want to change CSC.
JohnStocktrolley said:
I have an A528B/DS with the CSC XEO, however I want it to be changed to BTU.
I've tried using SamKEY and Chimera ands both said that the phones weren't supported even though they are on the supported models list. I spoke to a member of customer service from each of them and I was told the security firmware if too advanced but they are working on a method to resolve this.
I have also used ODIN with multiple flash files but none were able to change the CSC.
I have seen these phones being CSC changed multiple times with he latest firmware on them so I am fully aware there is a way to do it, I just cannot work out how. I keep sending my phones to someone to do it but for obvious reasons they won't tell me how to do it.
I don't want to root the phone as I don't want to void the KNOX and other than that I haven't been able to find a way online to resolve it.
I also have this problem with G780G and G781, N986B and some A other series Samsung's.
If anyone can help or has any ideas on what I can do, please could you reply to this and point me in the right direction as I am at a dead end.
Click to expand...
Click to collapse
i assume the ones u saw it done on multiple times is likely due to them having root
Tried SamKEY and it worked, my phone is now on DBT.
I change it to btu .. I used a tool ..i think from the Sam mobile site ...all good without root ..samkey

Categories

Resources