Related
First of all, sorry if this has been answered here, I simply can't find a definitive answer for our S6, let me explain better.
As you may know, I'm not a newbie here or in other forums, I've rooted most of my phones (Not this one) and have installed custom roms dozens of times to all of them, BUT, I'm definitely a newbie about what I need here, I'm trying to see if I can change my SM-G920i region from XSA (Australia) to any other one, India in this case. I have read tons of threads and posts and that's what is confusing me, in some threads there are people saying that they did it and is working great, in that same threads there are people saying that they did it but Knox got tripped, there are others that say that the device is soft bricked and others are saying that they have read somewhere that changing the CSC from it's original one may brake future Samsung pay.
So, this phone is paid by my office, they allow me to do what I want to it while I'm able to just put it back as it came from factory, so that means that I can root it if it doesn't trip Knox, that I can install anything while I can simply go back anytime they need me to, and obviously, Samsung pay works when it finally comes. With this in mind, can somebody answer me a couple of questions?
1-) I know it's possible to do it, but is it true that by doing this I'll have Samsung pay issues? I doubt that knox will be tripped if I do it with odin, but besides knox, is there any possibility that Samsung Pay will not work in certain regions (India in this case) and that's why some are saying that it will break it?
2-) If I download the firmware and flash it via Odin, I'm reading that it won't brick the phone is done via Odin, but in worst case scenario I assume that I can always go back to original one and it gets factory reset, am I right?
3-) If I flash it correctly as I expect an it doesn't brick, does this means that it will change PDA and CSC versions all together, that it will basically become a device from the new flashed region? So if I flash the India one to my XSA (Australia) now it will work completely as an India device and should get future OTA like the rest?
Again, sorry if this has been asked and answered but going back a lot of pages here can't give me definitive answer, thanks in advance for those of you kind enough to answer to this.
Flash a G920i ROM via odin other than your own region/country:
http://www.sammobile.com/firmwares/database/SM-G920I/
roydok said:
Flash a G920i ROM via odin other than your own region/country:
http://www.sammobile.com/firmwares/database/SM-G920I/
Click to expand...
Click to collapse
Thanks.
In another thread that I have posted (Brazilian one) I was replied to, so because of that I decided to do it, so far everything is working great as expected. Mine was an Australian baseband (XSA), only thing you I noticed is that when I connect it to Smart Switch app for PC or MAC it will still detects the Original CSC, I was curious about it and installed Phone info apk and it shows correctly the information, both PDA and CSC are now from India but it shows that the Original CSC was XSA (In my case), Firmware's CSC code is INU (India) and Active CSC code it says XSA/INU, so I'm assuming that it's showing multiple CSC.
Does somebody know if having the Active CSC showing XSA/INU causes future OTA issues?
After flashing a ROM its good practice to go to recovery mode and do a full wipe of cache and full reset to change CSC to the default of the ROM you flashed.
roydok said:
After flashing a ROM its good practice to go to recovery mode and do a full wipe of cache and full reset to change CSC to the default of the ROM you flashed.
Click to expand...
Click to collapse
Well, in that case I think I will pass for now, as I did a Full wipe cache and Full reset before the Flash but just did a Wipe cache after I flashed it.
The issue is that I basically just finish setting everything back as it was before (about 3 hours and I still haven't set my Contacts Ringtones and Accounts links) so begin again it's a PITA. Once I finish this I'll do a full nandroid backup to have everything as I want, but if I do the Wipe Data/Full Reset and then restore from the Full backup, does this put everything as it was including CSC again? I've been always confused about how deep this restore goes in the system files. Do you know about it?
Thanks.
Try restoring from your backup after the full wipe from recovery. If everything works then you should be ok. Otherwise start from scratch and reinstall everything one by one.
Will try that later today, thanks.
Goodluck.
roydok said:
Goodluck.
Click to expand...
Click to collapse
I tried that and nothing, still the same, then I decided to remove the Re-activation Lock in Find My Mobile settings, and after that and enter to recovery mode, it changed the CSC to India, so for those of you with same issues, remember about Re-activation lock.
Thanks for your help.
Did you have a SIM card inserted when you flashed your ROM with removed reactivation lock?
I had the SIM card on the phone today all the time as I forgot to bring with me the SIM removal tool and didn't have anything to open the Sim card tray, but last night I didn't have the Sim card installed when I flashed the ROM.
So today after I did the Wipe cache Partition and Data and saw that it still had the same issue, I flashed a UK ROM into a SM-G925f that had some African country ROM (have never heard of it before in my life but for the name it sounded like an African country), anyways I did that and everything went great, so that's when I thought what was different between the devices and then I remember that I had turned on the Reactivation lock in my S6 and not in the S6 Edge, so I turned it off, then went to Recovery mode and for my surprise the CSC was already changed without any other reset or anything.
erasat said:
I had the SIM card on the phone today all the time as I forgot to bring with me the SIM removal tool and didn't have anything to open the Sim card tray, but last night I didn't have the Sim card installed when I flashed the ROM.
So today after I did the Wipe cache Partition and Data and saw that it still had the same issue, I flashed a UK ROM into a SM-G925f that had some African country ROM (have never heard of it before in my life but for the name it sounded like an African country), anyways I did that and everything went great, so that's when I thought what was different between the devices and then I remember that I had turned on the Reactivation lock in my S6 and not in the S6 Edge, so I turned it off, then went to Recovery mode and for my surprise the CSC was already changed without any other reset or anything.
Click to expand...
Click to collapse
can you post a screen of CSC page of Phone ** info ** just for reference?
I see you said that CSC changed to India, but Active CSC or also Original CSC?
What I mean is that, now I have a S6 which has Original, Active CSC as MRU...I'd like to put a European fw on it since I'm based in Europe (got this Middle East / Africa phone just because Dual sim it's not available in europe) but I'm in doubt if putting an european fw will still show that CSC has changed from original one and maybe OTA updates won't work.
thanks
Changing csc!!!
I succesfully installed a G920I indian INU rom in my device which had a XSA rom but when i go to recovery it still shows as XSA ....How do i change that to INU?
Hi i am using a galaxy s6edge+ and i am really struggling with the region lock. I have tried a few options of the factory full reset changing the Apn's to the ones needed and using different sim cards.when it used to go into emergency mode "h+" now it won't connect to any internet at all. Can i possibly have any basic assistance with the rom and resetting options to change the csc when i do a hard reset the csc says it's 'multi'. what does that mean? Any region unlocking help would be appreciated so much!
Thanks guys
I just unboxed my G955FD and put my cricket SIM in and have no response from the network other than pushing an APN and my phone number. I tried manually selecting carrier networks and it listed 5 different "cricket" to attempt to connect to. At one point it showed signal bars in the status area, but no network connectivity. When I automatically connect to the network it responds saying I am registered but no signal bars in status and no activity. I appreciate the help.
Can anyone offer some tips before I call it a lost cause? The phone is out of its return period and probably broken since it will now receive a cricket badge and bars and LTE service but will not make calls or go online
Hey, are you on stock ROM. My 955F works just fine on Cricket, though compared to my daughters AT&T setup, her data is much faster. just discovered this today, and tomorrow will visit Cricket and AT&T to find out why...
Jan 9, 2108 update. I discovered Cricket is limited to about 5-6 Mps. I'm now on AT&T, for a few dollars more for two lines, and can get up to about 40-60 Mps in town.
What region CSC are you using?
---------- Post added at 07:59 AM ---------- Previous post was at 07:35 AM ----------
Here are my apn settings
Name: any but I input Internet or Cricket, I think it will work with whatever you like.
APN: ndo
MMSC: http://mmsc.aiowireless.net
MMSC proxy: proxy.aiowireless.net
multimedia message port: 80
mcc: 310
mnc: 150
apn type: default,mms,fota,hipri,supl
I know when I've setup APs on other phones there have been times that I will first do a 'reset' of my network settings on the phone, then reboot. Sometimes that will help. After that I will enter new APN settings and reboot.
On this 955F, with a viable CSC my phone just finds Cricket and works. With a bad CSC, it may list/show the cricket or AT&T networks, and will not register, no matter what I do, and for how long.
For example, my phone initially had a stock F ROM and a Panama region for the CSC. It worked with Cricket straight away. I changed the CSC to XAA using AT&T, and would find the towers, but would absolutely not register/work.
I ended up installing CarHDROM - a Note 8 OS ported for the 8+, and It took me a bit to find a CSC package that was meant for the ROM (Note 8) I was using, meaning I had to use a Note 8 CSC, even though my phone was an 8+ 955. Once that installed, Cricket started right away.
The CSC that came with CarHDROM I don't think worked straight out, but I can't recall for sure. I did end up using a XAA CSC, for the Note 8, non-AT&Tand that solved my connection issue after I had installed the CarHDROM.
CSC and phone wise, the ROM takes precedent, and the CSC must match the ROM (model). Seems that way to me, anyway.
Hope his helps.
There is another post about a FD phone that won't connect up, as well.
https://forum.xda-developers.com/galaxy-s8+/help/original-firmware-t3725472
I am on stock ROM. I guess I will root today and change CSC and hopefully that fixes whatever issue is going on. I have seen the cricket badge and LTE bars recently but no registration on network. If not, the eBay seller said they will take the phone back I'd it's indeed broken.
Ok so far no luck changing the CSC on stock ROM. I am going to try a couple different ROM and CSC combos tonight. Once again I am showing bars and cricket badge but not connecting data or voice on the phone, after root, and changing CSCs. I feel like Im so close and passed up my last day to return to eBay seller so I hope it truly is software and not hardware related. Im thinking of going by AT&T to act like a potential customer and see if its cricket messing up. Any other suggestions to try before I go crazy and use this phone for target practice?
Is it possible this is a region lock issue? My phone is a Tawain version and it was brand new out of the box. There is no sticker on it mentioning region lock. Does anyone have any insight into region locking for outside EU devices?
ChikhaiBardo said:
Is it possible this is a region lock issue? My phone is a Tawain version and it was brand new out of the box. There is no sticker on it mentioning region lock. Does anyone have any insight into region locking for outside EU devices?
Click to expand...
Click to collapse
Good question. I have a 930S Chinese region and it pulled in ATT/Cricket/TMobile just fine. I did have problems when I flashed a custom ROM, and flashed the CSC that came with the ROM. Later I flashed back the OEM CSC for the region (China) and it worked perfectly, again.
If you do flash a custom ROM, make sure you get a CSC package that is meant for that ROM (model). Not the exact model of your original phone. If you can find an XAA CSC that is meant for the new ROM, should be perfect.
JeffDC said:
Good question. I have a 930S Chinese region and it pulled in ATT/Cricket/TMobile just fine. I did have problems when I flashed a custom ROM, and flashed the CSC that came with the ROM. Later I flashed back the OEM CSC for the region (China) and it worked perfectly, again.
If you do flash a custom ROM, make sure you get a CSC package that is meant for that ROM (model). Not the exact model of your original phone. If you can find an XAA CSC that is meant for the new ROM, should be perfect.
Click to expand...
Click to collapse
Ok I have been changing CSC through TWRP with the CSCSelection Utility. Is that what you are referring to with flashing CSC? Is there a more effective way to do this through Odin? I think tomorrow morning I am going to flash back to stock firmware and start over. Am I able to flash any stock firmware for the SM-G955FD through Odin or do I need the original firmware for my region, which is (BRI) I believe I remembered reading I can flash everything for that model, but not any North American firmware meant for the SM-g955U
ChikhaiBardo said:
Ok I have been changing CSC through TWRP with the CSCSelection Utility. Is that what you are referring to with flashing CSC?
Yes
Is there a more effective way to do this through Odin? I think tomorrow morning I am going to flash back to stock firmware and start over. Am I able to flash any stock firmware for the SM-G955FD through Odin or do I need the original firmware for my region, which is (BRI) I believe I remembered reading I can flash everything for that model, but not any North American firmware meant for the SM-g955U
Click to expand...
Click to collapse
Just flash the CSC that comes 'stock'/with the rest of the full, stock firmware set, Odin will work. Have the SIM in the phone before you reboot, as for me it seems to help.
I haven't found a difference, for me yet, just flashing the exact CSC through Odin or TWRP. As I'm now on a custom ROM, I'm usually flashing via TWRP with a CSC that is supplied by an Aroma setup. Aroma is very handy.
Yes, flash your full stock via Odin. If you have TWRP you will lose it. You can re-flash TWRP from Odin. I typically flash TWRP all by itself, but I don't think that is really necessary. Maybe someone will come along and let us know.
As an aside I always keep a copy of zips/installs of TWRP, re-verity and SU on my SD card.
So after the stock full flash, I reboot into download mode and Odin flash TWRP, and follow that by a direct 3 key reboot into recovery, and TWRP will load. If you are going to root then flash re-verity, then SU/Magisk. You could then flash your CSC, but with the issues you've been having, I'd then boot to system, do the initial setup of the phone, and then boot back to recovery/TWRP, backup the phone.
Then TWRP flash the CSC Aroma package, making sure you have the SIM in the phone and reboot to system. I've been using XAA as my CSC with my custom ROM, within that is AT&T, T-Mobile, etc for US phones. I select the main XAA CSC from Aroma. Next I select the unbranded XAA as my more specific/local package, instead of AT&T, for example.
My 955F, stock worked just fine on it's 'stock' CSC (China region). I only had to change the CSC when I flashed a custom ROM, and that ROM did not have the ROM's (model) of XAA, so I had to find a CSC, which had XAA, that 'matched' the ROM I had flashed. I had flashed a Note 8 ROM, CarHDROM,v8 initially. Again, that ROM was largely meant for Europe and Exynos phones, so I had to be pointed to a Note 8 CSC that was compatible with the Note 8 custom ROM.
Yes, Odin is where you would flash stock firmware/stock CSC (not in an Aroma package) for your SM-G955FD. It is my understanding that all non-US phones, eg the G955's, are mechanically the same, so flashing 'any' Exynos ROM, G955FD ROM should work via Odin. You can also flash CSC packages via Odin as well, but there is no Aroma process, to my knowledge/experience. So have the specific and correct CSC to flash via Odin, if you go that route. It sounds like you are aware your phone is Exynos? A non-US phone?
I specifically bought my G955 (8+) as non-US so it could take root smoothly/easily, and work great world wide, including working great here in the US. Sometimes the U.S. does not seem a part of the world.
As I've been messing about with S7's/8s, there have been times that the phone did not grab onto AT&T, for example, and i would then 'reset' the network and reboot, with the SIM in the phone, then do a search for phone networks/services. That usually solved it, but when it did not, and I know I have the right CSC, I would then input/create a new APN, with AT&T, Cricket, Sprint, or what-ever service I needed, then reboot.
The only times I've not gotten the phone/s to grab the networks after that is when I've had the incorrect CSC.
Again, on my stock what-ever country G955F, stock G930S, etc, all Exynos, with the same stock (non-US) CSC that come in the firmware package, the phones have grabbed AT&T/T-Mobile just fine. If it would not, I would have reset the network, rebooted and entered the APN, and then rebooted (with the SIM in the phone). Done a network search after that, if necessary.
Hope this helps.
So today I stopped by TMOBILE and the store clerk popped a SIM card in and it fired up 4G LTE immediately and made calls. I then decided to stop by AT&T and it showed bars but refused to register or do anything even with the APN settings being pushed through from AT&T and Cricket. I am finally happy to realize that my phone is not defective (which I had feared before) and that it must be this service area and the bands on the G955FD. I have wanted to switch to TMOBILE for awhile now anyway so this is my chance to have an excuse to do it. Any input on why it won't access AT&T through an AT&T or Cricket SIM? I'm curious now more than anything. It must be missing a band that this area uses correct? The phone is clearly unlocked and functioning correctly.
What local CSC r u using?
Did you have AT&T check the APN?
T-Mobile and AT&T work on S8+ just fine, but need appropriate APNs.
Head back to the AT&T, if you want AT&T, and see if they will reset and or reinstall AT&T CSC/OS on your phone. XAA/ATT will have the AT&T boot logo. XAA/XAA (generic US use, ATT/T-Mobile compatible) will not.
One ringy dingy, two ringy dingy's...
Hello.
(backstory, boring) I have an SM-955F from Claro that I've been trying to unlock completely from the carrier. I've had lots of trouble with them and am pending a case with FCC to get out of their claws. In the meantime, I've been trying (without success, hence my posts) to get it working 100% with T-Mobile. I've had T-Mobile for years under a friend's name and couldn't get a device -so I took one from Claro when Puerto Rico was hit with the Hurricane (T-Mobile had no signal for months).
(Little-lot- of info) So, I had the phone updated to Sammobile's PCT 8.0 firmware -G955FXXU1CRC7_G955FOWA1CRC2_PCT-. But it didn't have the OEM unlock. At one point I remember installing TWRP but something happened to the phone and it wouldn't boot up. So, my act of magic (*coughs*, XDA) I found a way to get it back to official firmware (I think at first it was a Germany's 8.0 firmware*can't find the file name*). Anyways, I want to get the phone to have Wi-Fi calling, VoLTE, etc from T-Mobile and, for what I've interpreted, that comes from the CSC files.
Now, I found a thread that uses TWRP+AROMA to get a list of CSC files on the phone and I can just install the one I want. (I don't know if there's an easier way directly from ODIN but I've not found that compatible TMB CSC file for my phone to get the features working, if any).
In any case I still want my phone rooted (I think I triggered Knox, but the phone updated through the Samsung Updater just fine after installing a PCT 7.0 firmware -G955FXXU1AQCC_G955FOWA1AQCC_PCT-. Clearly I'm out of my depth)
(to the point) The phone doesn't want to install my TWRP file. Says "custom binary(RECOVERY) blocked due to remaining installment balance". Obviously it's Claro's side blocking it, I think?. But I can't get them to unlock it (since it's still "theirs", until I get my case resolved or pay their stupid balance. Long story short, Claro's service is **** and I regret not waiting to get my credit approved my T-Mobile)
So, how do I go about it? I read that its RMM blocked. But my state says normal. The OEM unlock only appears on the 7.0 -G955FXXU1AQCC_G955FOWA1AQCC_PCT- firmware (even then it won't let me install TWRP through ODIN). I honestly don't know. I'll appreciate all the help I can get to reach my goal of getting 100% on T-Mobile's features (mainly VoLTE, if possible-the feature is greyed out so I assume it can be activated). Can't even change the radio band on the thing. I read something about using Nova Launcher and having the widgets activate it through "Enhanced LTE" (I think) but that option doesn't appear on the list. I'd also like to delete all remnants from Claro on the phone, bloatware, booting logo and such. Since it's a 955F, I assume one can make it as if international?
Also, please check my previous post, I just realized I forgot to detail something. I did hit that "your phone has been modified, restart to undo process" and I forgot. Maybe that's the root of it all?
Any questions, please do ask. I'd like to get this moving. For now I'll use my Nexus 6 (God I love that phone a lot)
Maybe there's some compensation on this, maybe, if I get it done.
I've included the picture of the error and the info on Download mode, links for files I refer to also at the bottom.
https://www.sammobile.com/firmwares/galaxy-s8-plus/SM-G955F/PCT/download/G955FXXU1CRC7/216223/
https://www.sammobile.com/firmwares/galaxy-s8-plus/SM-G955F/PCT/download/G955FXXU1AQCC/129048/
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
Bump.
I have the same problem "custom binary (RECOVERY) blocked due to remaining installment balance", when trying to install TWRP, in my case I want to install Custom Rom and I could not, I have not found any solution to this problem, I do not have OEM on 8.0, and the RMM status is normal, I could unlock unlock SIM thanks to a friend with Z3X tool, do not charge for it but thankfully I made a donation for the hard work and also that the Z3X is not cheap at all, if you need to talk to him, you inform me to give you his contact.
SM-G955F Claro Puerto Rico.
I'm using a G930F with stock ROM, on Tmobile, and the January '21 update.
I'm using the UK BTU CSC. Been using this phone since 2018,; the first two years it worked fine, didn't get this error. Tmobile says my SIM card isn't the issue, and their tech support just has me do standard stuff like wiping data etc. Same issue even if I do a full factory reset.
I've noticed sometime nearly a year ago, my G930F started giving me a "Not registered on network" error msg when I tried to make a call, and SMS texts wouldn't go through, but internet was fine.
Toggling airplane mode on/off temporarily fixes this. (the phone will eventually log off so that I have to redo the airplane mode toggle or reboot.
Does anyone know what the issue is?
Is it just only certain G930F users that experience this on tmobile in the US, or is it all users?
Thanks.
I'm having a similar problem on AT&T. I also use a G930F (exynos) S7. Mine is rooted and flashed with LightROM, which is based on stock firmware. CSC is OXM/XEU. As you may know, AT&T is phasing out 3G, and my phone can't make calls in LTE only mode. I've been on chat with their customer service for an hour, and they have no idea why it isn't working. Can someone explain what I need to do to get this phone working?
It's an international version phone, so I wonder if the CSC is incompatible with AT&T. I understand that it is possible (in some cases) to change the CSC code, but I don't know how. The only methods I've found required me to install a stock USA firmware, but I haven't been able to find one. I think I'd need the ATT, XAA, or XAS firmware, but I'm not even sure that the CSC is the problem. But I'd expect the phone's VoLTE/HD voice capabilities to work because it has the stock drivers from Samsung in this ROM.
Ritor said:
I'm using a G930F with stock ROM, on Tmobile, and the January '21 update.
I'm using the UK BTU CSC. Been using this phone since 2018,; the first two years it worked fine, didn't get this error. Tmobile says my SIM card isn't the issue, and their tech support just has me do standard stuff like wiping data etc. Same issue even if I do a full factory reset.
I've noticed sometime nearly a year ago, my G930F started giving me a "Not registered on network" error msg when I tried to make a call, and SMS texts wouldn't go through, but internet was fine.
Toggling airplane mode on/off temporarily fixes this. (the phone will eventually log off so that I have to redo the airplane mode toggle or reboot.
Does anyone know what the issue is?
Is it just only certain G930F users that experience this on tmobile in the US, or is it all users?
Thanks.
Click to expand...
Click to collapse
Your problem is a consequence of the T-Mo acquisition of Sprint, and the resulting network reconfiguration which occurred in early 2021. The legacy Sprint bands (25, 26 and 41) do not support voice calls when connected to LTE; when connected to one of these bands, you must use VoLTE (which is different from LTE-Voice). And, therefore, when connected to one of the these bands, you will see "Not registered on network", although data will still work.
You can verify which bands you are connecting to by using the apps LTE Discovery or Signal Spy.
The solution is to enable the SM-G930F to use VoLTE.
-- Backup the data on your phone (you will lose it)
-- Download the Windows software "Samfirm", and then use it to download the official Samsung ROM for "EVR", and install it using Odin.
-- Install TWRP (I use twrp-3.5.2_9-MoRo-1.6-herolte)
-- I suggest following that by immediately installing the Alexndr ROM: https://forum.xda-developers.com/t/...vbase-v7-4-encryption-support-jul-10.3592914/ This is a debloated version of the official ROM, so everything works properly. Be sure to follow the instructions for keeping your CSC (in this case, EVR). Root the phone using Magisk.
-- I suggest using the ThundeRStormS kernel, which is MUCH more stable than the kernel in the Alexndr ROM (the stock kernel reboots randomly; the TS kernel does not).
-- Reinstall your data; reconfigure phone.
-- Download the app IMS Settings to enable VoLTE (you will need to re-implement these settings whenever you reboot).
You will find after doing this that VoLTE (and T-Mo or, in my case, Mint) works perfectly, and you will be able to connect to all of the bands now supported by T-Mo and the SM-G930F without issue.
Droiderat said:
Your problem is a consequence of the T-Mo acquisition of Sprint, and the resulting network reconfiguration which occurred in early 2021. The legacy Sprint bands (25, 26 and 41) do not support voice calls when connected to LTE;; when connected to one of these bands, you must use VoLTE (which is different from LTE-Voice). And, therefore, when connected to one of the these bands, you will see "Not registered on network", although data will still work.
You can verify which bands you are connecting to by using the apps LTE Discovery or Signal Spy.
The solution is to enable the SM-G930F to use VoLTE.
-- Backup the data on your phone (you will lose it)
-- Download the Windows software "Sanfirm", and then use it download the official Samsung ROM for "EVR", and install it using Odin.
-- Install TWRP (I use twrp-3.5.2_9-MoRo-1.6-herolte)
-- I suggest following that by immediately installing the Alexndr ROM: https://forum.xda-developers.com/t/...vbase-v7-4-encryption-support-jul-10.3592914/ This is a debloated version of the official ROM, so everything works properly. Be sure to follow the instructions for keeping your CSC (in this case, EVR). Root the phone using Magisk.
-- I suggest using the ThuneRStorM kernel, which is MUCH more stable than the kernel in the Alexndr ROM (the stock kernel reboots randomly; the TS kernel does not).
-- Reinstall your data; reconfigure phone.
-- Download the app IMS Settings to enable VoLTE (you will need to re-implement these settings whenever you reboot).
You will find after doing this that VoLTE (and T-Mo or, in my case, Mint) works perfectly, and you will be able to connect to all of the bands now supported by T-Mo and the SM-G930F without issue.
Click to expand...
Click to collapse
Will these instructions work for AT&T also? What is the correct site for downloading SamFirm?
Feenix0 said:
Will these instructions work for AT&T also? What is the correct site for downloading SamFirm?
Click to expand...
Click to collapse
They likely will (but I don't use AT&T, so I can't confirm).
Droiderat said:
They likely will (but I don't use AT&T, so I can't confirm). It is SanFirm, not SamFirm. Google is your friend.
Click to expand...
Click to collapse
Thanks! Actually, duckduckgo is my friend , but I only saw results for SamFirm, but there were several different ones and I don't want to use a copycat site that may have tampered with something. I think I'm safer trusting info I get on xda.
Feenix0 said:
Thanks! Actually, duckduckgo is my friend , but I only saw results for SamFirm, but there were several different ones and I don't want to use a copycat site that may have tampered with something. I think I'm safer trusting info I get on xda.
Click to expand...
Click to collapse
DuckDuckGo uses the Microsoft Bing search engine. My version of SamFirm is 0.3.7.1. I don't know which site I got it from.
When I open my SamFirm app, there is now a notice which tells me there is a newer version of the software, called SamUpdate.. See https://kfhost.net/firmware/samupdate I haven't yet tried the new download method, as the SamFirm tool still works.
Droiderat said:
Your problem is a consequence of the T-Mo acquisition of Sprint, and the resulting network reconfiguration which occurred in early 2021. The legacy Sprint bands (25, 26 and 41) do not support voice calls when connected to LTE;; when connected to one of these bands, you must use VoLTE (which is different from LTE-Voice). And, therefore, when connected to one of the these bands, you will see "Not registered on network", although data will still work.
You can verify which bands you are connecting to by using the apps LTE Discovery or Signal Spy.
The solution is to enable the SM-G930F to use VoLTE.
-- Backup the data on your phone (you will lose it)
-- Download the Windows software "Sanfirm", and then use it download the official Samsung ROM for "EVR", and install it using Odin.
-- Install TWRP (I use twrp-3.5.2_9-MoRo-1.6-herolte)
-- I suggest following that by immediately installing the Alexndr ROM: https://forum.xda-developers.com/t/...vbase-v7-4-encryption-support-jul-10.3592914/ This is a debloated version of the official ROM, so everything works properly. Be sure to follow the instructions for keeping your CSC (in this case, EVR). Root the phone using Magisk.
-- I suggest using the ThuneRStorM kernel, which is MUCH more stable than the kernel in the Alexndr ROM (the stock kernel reboots randomly; the TS kernel does not).
-- Reinstall your data; reconfigure phone.
-- Download the app IMS Settings to enable VoLTE (you will need to re-implement these settings whenever you reboot).
You will find after doing this that VoLTE (and T-Mo or, in my case, Mint) works perfectly, and you will be able to connect to all of the bands now supported by T-Mo and the SM-G930F without issue.
Click to expand...
Click to collapse
Thanks for the thorough response! I actually used to use the EVR csc in years prior, but switched to BTU due to the EVR bloatware. Does it really make a difference ?
Ritor said:
Thanks for the thorough response! I actually used to use the EVR csc in years prior, but switched to BTU due to the EVR bloatware. Does it really make a difference ?
Click to expand...
Click to collapse
I don't actually know. I researched VoLTE, and the suggestion I found was to use EVR. I didn't try using the IMS Settings app with BTU (my original CSC). I am not aware of any bloatware in EVR, but I immediately overwrote EVR with the Alexndr ROM, retaining only the EVR CSC. So, if EVR had bloatware, I wouldn't know.
I recorded the steps I followed, and I can attest that it works. There may be other solutions.
Droiderat said:
I don't actually know. I researched VoLTE, and the suggestion I found was to use EVR. I didn't try using the IMS Settings app with BTU (my original CSC). I am not aware of any bloatware in EVR, but I immediately overwrote EVR with the Alexndr ROM, retaining only the EVR CSC. So, if EVR had bloatware, I wouldn't know.
I recorded the steps I followed, and I can attest that it works. There may be other solutions.
Click to expand...
Click to collapse
I understand. When I originally bought my G930F, it had a latin american CSC. I first tried EVR from SamMobile, and it came with a bunch of uk carrier specific bloatware. I later installed BTU after reading it was the generic UK csc for non carrier branded phones.
[deleted]
Finally digging into this process now that I have a temp phone.
After Odin failing to flash with either the BTU and EVR, I started writing this post and took a picture of the download mode screen. Contrary to everything I saw in my phone's status and information apps, the download screen showed:
PRODUCT NAME: SM-G930W8
I guess it's no wonder it didn't work!!!!! I'm just glad the flashing TWRP and LightROM for the wrong model didn't ruin my device.
Edit: Turns out that the hardware in these two models is the same, so no surprise it didn't cause trouble.
A question from a noob here. I have a T-Mobile S22 Ultra phone which is network unlocked. As I recently I switched from T-Mobile to Verizon, I'm missing some of the features that are Verizon specific, while not needing anything that is T-Mobile specific anymore. From what I understand, Samsung installs multi SCS firmware on most of the phones these days, which can be changed by a dialer code. That however did not work at all.
Another option I've come across is by flashing provider specific (in my case Verizon) firmware as long as firmware version is the same (S908USQU2AVDC). There are a number of articles on how to do it by using Odin. The issues is no matter what I do and what files I select (like by using CSC file instead of HOME_CSC with or without flashing USERDATA file as well) the result is the same. It shows success and reboots and then reports an error and does the full factory reset which ends up back on T-Mobile version.
The question I have if it's even possible? And if so what I'm doing wrong here. Unlocking a bootloader is not really an option for me...
samirski said:
A question from a noob here. I have a T-Mobile S22 Ultra phone which is network unlocked. As I recently I switched from T-Mobile to Verizon, I'm missing some of the features that are Verizon specific, while not needing anything that is T-Mobile specific anymore. From what I understand, Samsung installs multi SCS firmware on most of the phones these days, which can be changed by a dialer code. That however did not work at all.
Another option I've come across is by flashing provider specific (in my case Verizon) firmware as long as firmware version is the same (S908USQU2AVDC). There are a number of articles on how to do it by using Odin. The issues is no matter what I do and what files I select (like by using CSC file instead of HOME_CSC with or without flashing USERDATA file as well) the result is the same. It shows success and reboots and then reports an error and does the full factory reset which ends up back on T-Mobile version.
The question I have if it's even possible? And if so what I'm doing wrong here. Unlocking a bootloader is not really an option for me...
Click to expand...
Click to collapse
In theory, flashing the correct firmware (VERIZON) should work. I would honestly first wipe the device, then flash (clean, not dirty) the Verizon firmware and setup accordingly. I had a similar case with a TMBILE unit (I had changed carriers) and I had managed to use XAA CSC and then when I reverted to TMOBILE SIM it would not "restart and install carrier updates". I had to basically switch the unit to U1 and then revert to U and it finally pulled all the TMO crap.
I may be mistaken since I haven't done this type stuff since S10, but I think you need to first reset the device and flash the unlocked version then when you put the verizon sim in it should provision it. Then you can flash the verizon package if you want the bloat apps. The features may be hit or miss. You may need to activate the features on the verizon website. Some features may never work as the carrier wont push them to IMEI not in their database of branded phones. There may be things you can do in hidden settings with "Activity Launcher" or other methods.
I'm here trying to figure out the same things for Tmobile and a factory Unlocked phone, before I buy.
Thanks a lot for your suggestions guys! I managed to do what I wanted. This is what I ended up doing, first flashed the unbranded U1 version on my phone and on the first boot Verizon sim was provisioned. Then I flashed Verizon firmware and it worked!