This post is to spread the knowledge about the recent software beta update android pie / one ui for the s9+ us( snapdragon variant ).
A lot of people including me faced a problem of not being able to use volte and wifi calling on us phones specially with Indian networks like JIO.
The update was manually installed using this link ,
https://www.theandroidsoul.com/galaxy-s9-plus-android-9-pie-download-one-ui/
There is no need to flash anything or change any csc , my csc status is still XAA but jio works just fine.
Volte automatically with the first boot itself was turned on.
Wifi calling keeps disabling but people update if your work !
Shoutout to all the people stuck with unlocked ( actually locked xD ) phones to use volte features.
Your post brings new hopes for me. I have a Unlocked T Mobile Galaxy S9 with TMB CSC on it. I have a few questions
1) Is your original device 965U1 or you flashed 965U1 firmware to your 965U device ?
2) What was the CSC on your phone prior to Android Pie update you made ?
3) With Jio did you have a challenge where you couldn't make calls from direct phone dialler and had to use Jio voice ? But now Jio voice is no longer needed after android Pie Update ?
4) Did you have Jio SIM inside phone while doing update or removed it ? I see posts saying that SIM inside phone influences CSC Config
5) I assume Samsung Pay is still a no go in India with XAA CSC. Please confirm.
rythym05392 said:
Your post brings new hopes for me. I have a Unlocked T Mobile Galaxy S9 with TMB CSC on it. I have a few questions
1) Is your original device 965U1 or you flashed 965U1 firmware to your 965U device ?
2) What was the CSC on your phone prior to Android Pie update you made ?
3) With Jio did you have a challenge where you couldn't make calls from direct phone dialler and had to use Jio voice ? But now Jio voice is no longer needed after android Pie Update ?
4) Did you have Jio SIM inside phone while doing update or removed it ? I see posts saying that SIM inside phone influences CSC Config
5) I assume Samsung Pay is still a no go in India with XAA CSC. Please confirm.
Click to expand...
Click to collapse
1. Original device - 965u1
2. Csc prior to update was XAA and still is the same.
3. Yes , i couldn't make calls before the update without the jio voice app. But after the update , normal dialer works just fine.
4. That really doesn't make a difference . Mine was in the phone during the update. The csc is still XAA , flashing pie didn't change the csc , only due to the beta nature or the update , samsung might have made some changes and a mistake served us as a boon.
5. Samsung pay works just fine for me , using in India.
There's a reason why wifi calling doesn't work on this beta is because the csc is only loaded with config supporting sim cards from US. Preloaded config are from companies like sprint , tmobile, etc. Hence , no change in csc means no change on config and thus wifi calling on jio doesn't work.
Another update , only update to beta 1 and stay on it , in beta 2 , they fixed this mistake making any volte carrier non working again .
melonhead7007 said:
1. Original device - 965u1
2. Csc prior to update was XAA and still is the same.
3. Yes , i couldn't make calls before the update without the jio voice app. But after the update , normal dialer works just fine.
4. That really doesn't make a difference . Mine was in the phone during the update. The csc is still XAA , flashing pie didn't change the csc , only due to the beta nature or the update , samsung might have made some changes and a mistake served us as a boon.
5. Samsung pay works just fine for me , using in India.
There's a reason why wifi calling doesn't work on this beta is because the csc is only loaded with config supporting sim cards from US. Preloaded config are from companies like sprint , tmobile, etc. Hence , no change in csc means no change on config and thus wifi calling on jio doesn't work.
Another update , only update to beta 1 and stay on it , in beta 2 , they fixed this mistake making any volte carrier non working again .
Click to expand...
Click to collapse
It is bad news that XAA CSC no longer supports JIO volte. I thought Android Pie brought in a fix for this issue.
I have the S9, and not sure if the same bug in Beta 1 as in S9+ that you saw is true for the S9.
melonhead7007 said:
1. Original device - 965u1
2. Csc prior to update was XAA and still is the same.
3. Yes , i couldn't make calls before the update without the jio voice app. But after the update , normal dialer works just fine.
4. That really doesn't make a difference . Mine was in the phone during the update. The csc is still XAA , flashing pie didn't change the csc , only due to the beta nature or the update , samsung might have made some changes and a mistake served us as a boon.
5. Samsung pay works just fine for me , using in India.
There's a reason why wifi calling doesn't work on this beta is because the csc is only loaded with config supporting sim cards from US. Preloaded config are from companies like sprint , tmobile, etc. Hence , no change in csc means no change on config and thus wifi calling on jio doesn't work.
Another update , only update to beta 1 and stay on it , in beta 2 , they fixed this mistake making any volte carrier non working again .
Click to expand...
Click to collapse
can you send please send beta1 or beta2 link or the build number of the beta firmware
Related
I don't see the option anywhere.
Should I flash Indian firmware (I found one from sammobile) or continue with the UAE firmware without VoLTE?
Also, please let me know the additional things you did for your foreign country device to make it work in India
prajithkv082 said:
I don't see the option anywhere.
Should I flash Indian firmware (I found one from sammobile) or continue with the UAE firmware without VoLTE?
Also, please let me know the additional things you did for your foreign country device to make it work in India
Click to expand...
Click to collapse
Just insert Indian sim and reset your phone. Hope you know how to reset your phone.
Flash indian firmware, inserting indian SIM and "resetting" your phone won't do you ****.
If you have a SM-G955FD, you can flash G955F firmware on it just fine.
Im also having uae s8 plus. Just insert any of the Indian sim and switch on. After few minutes you will be notified to restart the phone and factory reset. Do that and volte will work.
I have the G955FD on the BRI (Taiwan) firmware. I live in Australia, and really want to use Samsung pay. How should I change my CSC from BRI to XSA? I've seen varying information here and on other sites. I want to keep my Google Play as Certified, still have OTAs and without tripping KNOX. Essentially like a standard phone from this region. I don't particularly care about Dual-SIM, but it'd be nice to still have.
Here is my current software information: imgur(dot)com/a/197z5 <-- I can't post links yet, remove this if not allowed.
Thanks for helping
jAyKEbAb said:
I have the G955FD on the BRI (Taiwan) firmware. I live in Australia, and really want to use Samsung pay. How should I change my CSC from BRI to XSA? I've seen varying information here and on other sites. I want to keep my Google Play as Certified, still have OTAs and without tripping KNOX. Essentially like a standard phone from this region. I don't particularly care about Dual-SIM, but it'd be nice to still have.
Here is my current software information: imgur(dot)com/a/197z5 <-- I can't post links yet, remove this if not allowed.
Thanks for helping
Click to expand...
Click to collapse
Hi mate
Without root there are not many options ..
First F and FD firmwares are compatibles ( same device!! exynos to exynos) , you can flash an F firmware into an FD or vice versa
you could try to change your CSC to your SIM card CSC first
Check here
On the thread it shows how to add your SIM CSC to your current CSC config , if it work you may end up with a configuration like BRI/BRI/XSA , in my case I got TPA/TPA/PCW , TPA was the software default and PCW sims CSC. I do not have Samsung pay so i do not know if that change will be enough to make it work. Back up you need to factory reset for this.
The other option is to flash a full XSA firmware ( use a G955F firmware) , read here how to do it
BACK UP before you do anything
MAX 404 said:
Hi mate
Without root there are not many options ..
First F and FD firmwares are compatibles ( same device!! exynos to exynos) , you can flash an F firmware into an FD or vice versa
you could try to change your CSC to your SIM card CSC first
Check here
On the thread it shows how to add your SIM CSC to your current CSC config , if it work you may end up with a configuration like BRI/BRI/XSA , in my case I got TPA/TPA/PCW , TPA was the software default and PCW sims CSC. I do not have Samsung pay so i do not know if that change will be enough to make it work. Back up you need to factory reset for this.
The other option is to flash a full XSA firmware ( use a G955F firmware) , read here how to do it
BACK UP before you do anything
Click to expand...
Click to collapse
Thank you very much! I'm now running XSA/XSA/XSA with a flash. Dual-SIM support is still there which surprised me. There were some issues with Odin, but I fixed them up after a while.
jAyKEbAb said:
Thank you very much! I'm now running XSA/XSA/XSA with a flash. Dual-SIM support is still there which surprised me. There were some issues with Odin, but I fixed them up after a while.
Click to expand...
Click to collapse
Great news mate!!
Firmware is 100% same for F and FD so you should not see any difference at all , I asume also you got Samsung Pay working.
Good job!
I did the same when I had s8+. flashed TEL (Telstra) SM-G955F firmware which I got off Sammobile and worked like a treat. Samsung pay, VoLTE, Wifi Calling, Spam detection in calls worked as well.
I upgraded to S9+ and tried to do the same. The flash process works fine but CSC doesn't change. I am stuck on AFG CSC. Apparently it cant be done on S9 as Samsung is imposing multi CSC format.
Well, you are lucky one to have S8+. Enjoy
maximus81 said:
I did the same when I had s8+. flashed TEL (Telstra) SM-G955F firmware which I got off Sammobile and worked like a treat. Samsung pay, VoLTE, Wifi Calling, Spam detection in calls worked as well.
I upgraded to S9+ and tried to do the same. The flash process works fine but CSC doesn't change. I am stuck on AFG CSC. Apparently it cant be done on S9 as Samsung is imposing multi CSC format.
Well, you are lucky one to have S8+. Enjoy
Click to expand...
Click to collapse
That's unfortunate
I'm curious why you flashed TEL instead of XSA, XSA is the unlocked version and it still has WiFi calling, VoLTE etc. I have an ALDImobile SIM (which uses Telstra) but I installed the unlocked version to have minimal bloatware and the stock boot logo.
jAyKEbAb said:
That's unfortunate
I'm curious why you flashed TEL instead of XSA, XSA is the unlocked version and it still has WiFi calling, VoLTE etc. I have an ALDImobile SIM (which uses Telstra) but I installed the unlocked version to have minimal bloatware and the stock boot logo.
Click to expand...
Click to collapse
I tried both. First preference is always XSA but I tried TEL in anticipation that it may work
Sent from my SM-G965F using Tapatalk
Im in US , i have s7 G930T (Tmobile), carrier unlocked. At some point i needed Polish cell number so i came up with idea to have Orange sim card (its Polish cell carrier) shipped to me and install on my cell so i can make calls to Poland over wifi calling. When sim came and was inserted into my s7 it displays ATT carrier and wifi calling is no longer there, but i kind of expected it , tmobile kind of sucks when you try to use phones from different carriers on their network or vice versa. So using odin i flushed it with xaa rom (it should be stock us rom), then with att rom, both times wifi calling was not there just like with tmobile rom. Then i tried to flash it with Polish stock s7 rom and then with Orange s7 rom, both unsuccessful flashes (partition fail).
Does anyone have some idea what i should try next ?
PS s7 is my old phone , currently have galaxy s10e (G970U version), funny thing is when i put new Orange sim into S10e everything works fine, wifi calling showed up without a problem.
Any help greatly appreciated. Thank you.
If I recall correctly VoLTE and VoWifi config is part of the CSC device firmware on the S7, which means you'd need to flash the polish firmware.
But the US model is a different SoC (Snapdragon instead of Exynos) which is why the flashing fails as it's not the right firmware for the hardware. I'm not sure there's any way around it.
Beanvee7 said:
If I recall correctly VoLTE and VoWifi config is part of the CSC device firmware on the S7, which means you'd need to flash the polish firmware.
But the US model is a different SoC (Snapdragon instead of Exynos) which is why the flashing fails as it's not the right firmware for the hardware. I'm not sure there's any way around it.
Click to expand...
Click to collapse
Beanvee7, thank you for response, i kind of figure that much, I just had some hope there is a way around it somehow, especially since with my s10e i have same scenario ( us tmobile phone and Polish sim) and everything is working fine. Thank you again.
Looks like the S10 still has the CSC firmware, so I can only guess it no longer relies on carrier config in the CSC for VoLTE and VoWifi. But it's always been how the S7 has worked and commonly asked.
HI all,
With CSC change not possible using codes with latest UI 3.1 update what are options to change CSC?
For ex. I have SM-N986U unlocked Tmobile device but i changed CSC to ATT as im currently using ATT Prepaid and I'm on latest Apr update for ATT
How can i revert back to Tmobile CSC?
Do i need to flash Tmobile firmware using ODIN by first flashing to U1 firmware then Tmobile firmware or can i directly flash Tmobile latest firmware with Apr update using ODIN?
Will i be able to retain my app and data if I flash Tmobile firmware?
Any help will be appreciated.
Thanks
So you state csc change not possible then ask how to change it? lol.. and if it were as easy to just flash firmware in odin tgen that wouldve been the way to do it to begin with I would think lol
Update:
I was able to change CSC(ATT/ATT/TMB) to TMB/TMB/TMB but it was long and winded way. Just flashing firmware was not enough , need Tmobile sim to install carrier service and change CSC.
I followed the steps below:-
1) Did backup of my device using Smart Switch and removed my ATT sim.
2) Flashed latest T-Mobile firmware( N986USQU2DUC8 ) using instructions from post - https://forum.xda-developers.com/t/ota-and-non-ota-firmware-for-n986u-and-n986u1.4143833/ . Also, downloaded the ODIN (patched version) and T-Mobile firmware from links in the post. Flashed HOME_CSC too.
3) After rebooting phone with new firmware , the boot up screen was still ATT and CSC was still ATT/ATT/TMB.
4)Shut down phone and inserted Tmobile SIM i had lying around.
5) On reboot, i was asked to install Tmobile carrier services and on restart , Tmobile logo came on boot up with CSC changed to TMB/TMB/TMB.
6) Now, i have esim enabled and SIM manager showing up too.
mindseye0803 said:
Update:
I was able to change CSC(ATT/ATT/TMB) to TMB/TMB/TMB but it was long and winded way. Just flashing firmware was not enough , need Tmobile sim to install carrier service and change CSC.
I followed the steps below:-
1) Did backup of my device using Smart Switch and removed my ATT sim.
2) Flashed latest T-Mobile firmware( N986USQU2DUC8 ) using instructions from post - https://forum.xda-developers.com/t/ota-and-non-ota-firmware-for-n986u-and-n986u1.4143833/ . Also, downloaded the ODIN (patched version) and T-Mobile firmware from links in the post. Flashed HOME_CSC too.
3) After rebooting phone with new firmware , the boot up screen was still ATT and CSC was still ATT/ATT/TMB.
4)Shut down phone and inserted Tmobile SIM i had lying around.
5) On reboot, i was asked to install Tmobile carrier services and on restart , Tmobile logo came on boot up with CSC changed to TMB/TMB/TMB.
6) Now, i have esim enabled and SIM manager showing up too.
Click to expand...
Click to collapse
thats the normal process.. that firmware is same for each carrier.. firmware is multi csc which changes based on sim inserted.. shouldnt have to go through all of that really.. i think most ppl who have issues are trying to change csc without a active sim card or on carrier locked devices etc.
glad u figured it out tho!
elliwigy said:
thats the normal process.. that firmware is same for each carrier.. firmware is multi csc which changes based on sim inserted.. shouldnt have to go through all of that really.. i think most ppl who have issues are trying to change csc without a active sim card or on carrier locked devices etc.
glad u figured it out tho!
Click to expand...
Click to collapse
Well, the confusion for most ppl who are new to Samsung and CSC, like me , is that we could change CSC with code earlier and now cannot. Didn't have these issues with pixel and iPhone.
mindseye0803 said:
Well, the confusion for most ppl who are new to Samsung and CSC, like me , is that we could change CSC with code earlier and now cannot. Didn't have these issues with pixel and iPhone.
Click to expand...
Click to collapse
pixel and iphone dont have multi csc like samsung does.. just curious, when were u able to change csc with code earlier if ur new to samsung? lol
elliwigy said:
pixel and iphone dont have multi csc like samsung does.. just curious, when were u able to change csc with code earlier if ur new to samsung? lol
Click to expand...
Click to collapse
Yes, I was able to change CSC to ATT from TMobile, enable all LTE/5G bands before One UI update.Not, sure what u find so funny .
Yes, I'm aware that there is no CSC concept in pixel or iPhone or any other other manufacturer that I'm aware nor they are crippled in terms of hardware capability from carrier software like Samsung. LTE/5G bands not being enabled , esim not being enabled etc.
mindseye0803 said:
Yes, I was able to change CSC to ATT from TMobile, enable all LTE/5G bands before One UI update.Not, sure what u find so funny .
Yes, I'm aware that there is no CSC concept in pixel or iPhone or any other other manufacturer that I'm aware nor they are crippled in terms of hardware capability from carrier software like Samsung. LTE/5G bands not being enabled , esim not being enabled etc.
Click to expand...
Click to collapse
actually other devices are crippled in some cased disabled entirely.. for example u cant get a tmb oneplus 9 pro 5g and use it on verizon to get 5g bcuz vzw 5g bands are disabled in tmb variant..
its really the carriers to be honest..
and I say LOL all the time even in normal convo so not actually laughing sometimes, just say it out of habit
elliwigy said:
actually other devices are crippled in some cased disabled entirely.. for example u cant get a tmb oneplus 9 pro 5g and use it on verizon to get 5g bcuz vzw 5g bands are disabled in tmb variant..
its really the carriers to be honest..
and I say LOL all the time even in normal convo so not actually laughing sometimes, just say it out of habit
Click to expand...
Click to collapse
I have phones such as Z Flip3 5G and other models that do not change CSC like older models when following the flash procedure starting with U1, but the phones never prompt a restart. I have noticed it seems to be with TMB or VZW units. Any suggestion on how to actually get the CSC to change properly or is this something they are doing with new phones to avoid being able to use them fully on other carriers?
yygemmi770 said:
I have phones such as Z Flip3 5G and other models that do not change CSC like older models when following the flash procedure starting with U1, but the phones never prompt a restart. I have noticed it seems to be with TMB or VZW units. Any suggestion on how to actually get the CSC to change properly or is this something they are doing with new phones to avoid being able to use them fully on other carriers?
Click to expand...
Click to collapse
SamKey.org
Go to the page, download theirs Samkey app, buy few credits on Ebay and you can change the CSC as you wish in a minute, the phone will reboot without loosing your data, it's the easiest way as far as I know
Hi, I have yhe following issue and I need your thoughts please.
I have a Telus plan, canadian with US roaming option.
I am traveling in US alot. I have a Note 20 Ultra U1 from Samsung USA. When in US I can only register on Tmobile and I can get 5G icon too. Won't let me on ATT or Verizon.
With same sim card in Note20 Ultra "W" variant, canadian one, it wil register on all 3 major networks in US. No issues with the sim, I guess.
Also in Canada won't get 5G ever.
My provider said nothing to do with them, Samsung told me the same.
I reseted all network setings my APN is ok. VOLTE on. Only getting acces to Tmobile.
Any ideea how I can fix this ? Is it related to CSC ? Mine is XAA.
mindseye0803 said:
Update:
I was able to change CSC(ATT/ATT/TMB) to TMB/TMB/TMB but it was long and winded way. Just flashing firmware was not enough , need Tmobile sim to install carrier service and change CSC.
I followed the steps below:-
1) Did backup of my device using Smart Switch and removed my ATT sim.
2) Flashed latest T-Mobile firmware( N986USQU2DUC8 ) using instructions from post - https://forum.xda-developers.com/t/ota-and-non-ota-firmware-for-n986u-and-n986u1.4143833/ . Also, downloaded the ODIN (patched version) and T-Mobile firmware from links in the post. Flashed HOME_CSC too.
3) After rebooting phone with new firmware , the boot up screen was still ATT and CSC was still ATT/ATT/TMB.
4)Shut down phone and inserted Tmobile SIM i had lying around.
5) On reboot, i was asked to install Tmobile carrier services and on restart , Tmobile logo came on boot up with CSC changed to TMB/TMB/TMB.
6) Now, i have esim enabled and SIM manager showing up too.
Click to expand...
Click to collapse
So I have a Verizon phone and I switched to t-mobile. If I use this method to switch my csc would that lock my phone or would it stay unlocked?
Stevieboy02008 said:
So I have a Verizon phone and I switched to t-mobile. If I use this method to switch my csc would that lock my phone or would it stay unlocked?
Click to expand...
Click to collapse
Unlocked. Phone once unlocked will not lock to any carrier.
dadmi said:
Unlocked. Phone once unlocked will not lock to any carrier.
Click to expand...
Click to collapse
Thank you
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.