I've been searching for days now, yet can't find what I'm looking for. I have the S7 Edge International vatient SM-G935F and have recently upgraded it to Oreo on the Superman Rom. I'm loving my phone again, yet I have yet to find a solution to enable WIFi calling and VOLTE for the S7 International on TMB. Can anyone assist? I'm sure there are a ton of other folks in my situation, yet everything I've found only works on Nougat or is only for newer model phones.
I'd greatly appreciate any guidance to get this final piece of the puzzle solved.
Thanks in advance!
Flash Home_CSC for your carrier over top of the ROM, CSC is what controls your carrier specific features like VoWiFi and VoLTE
Edit: Although since you're using T-Mobile, isn't that US based? Make sure you only flash the firmware appropriate to your device. US model S7's use a different SoC so you can't flash it over an international phone
It's the international version that I'm using on a US carrier. There is no firmware from the carrier directly due to the difference in SoC on the phones that were sold in the US.
This being said I was able to use the CSC selection tool with Nougat, yet the tool hasn't been updated for the S7 running Oreo.
My hope is someone has created a compatible tool or flashable fix. I've found several for the s8, yet nothing for my S7.
You could do a full TWRP backup, try the Nougat CSC tool or the S8 one and see how it runs, and if any issues you can restore the backup or dirty flash the ROM
You can try this: https://forum.xda-developers.com/showpost.php?p=69864872&postcount=5484
using this: https://forum.xda-developers.com/s7-edge/development/utility-flashable-csc-selection-30-t3392957
which is a recommended step when doing this: https://forum.xda-developers.com/galaxy-s7/development/rom-s7-rom-v1-0-t3356197
So, it might just work for you.
Edited after re-reading your initial post:
Also, I've not done this yet, but I am possibly about to install the Superman Oreo ROM too (I have the sm-g930f), and you mentioned you find only tools for Nougat. The second link I provided is the 2.5.0 CSC selection tool for MM or Nougat, and no version listed for Oreo, yet that CSC selection 2.5.0 version is linked to from the Superman Oreo developer in one of the steps, for flashing CSC after flashing the ROM......
So, my question to you is: have you tried that CSC selection tool for Nougat already just after flashing Superman Oreo, and it doesn't work? One of my main reasons for going with the Superman ROM is to have the proper CSC installed for my international (exynos) variant on US T-Mobile, and I'm not even gonna start if the CSC won't install.
Thx!
Yes, I've tried the Nougat 2.5.0 version as well as the s8 version, neither of which seem to work for my phone on Oreo.
Beanvee7 said:
You could do a full TWRP backup, try the Nougat CSC tool or the S8 one and see how it runs, and if any issues you can restore the backup or dirty flash the ROM
Click to expand...
Click to collapse
Tried both of the tools already (csc select 2.5.0 for Nougat and the Oreo version for the s8). S8 version says, nope, this is an S7 and won't install, the S7 version installs yet ends up in a boot loop. So, no dice as of yet.
I've asked for info from the dev on his forums with no response as of yet. Crossing my finger that he releases a new version or someone else can work some magic.
sirebral123 said:
Tried both of the tools already (csc select 2.5.0 for Nougat and the Oreo version for the s8). S8 version says, nope, this is an S7 and won't install, the S7 version installs yet ends up in a boot loop. So, no dice as of yet.
I've asked for info from the dev on his forums with no response as of yet. Crossing my finger that he releases a new version or someone else can work some magic.
Click to expand...
Click to collapse
I just installed Superman Oreo last night then installed csc from the Nougat 2.5.0 csc selection tool immediately afterward. I got it all working, including volte. What boot loop issue did you have? How far did it boot and what did you see before the reboot?
gruuvin said:
I just installed Superman Oreo last night then installed csc from the Nougat 2.5.0 csc selection tool immediately afterward. I got it all working, including volte. What boot loop issue did you have? How far did it boot and what did you see before the reboot?
Click to expand...
Click to collapse
After android booted the system said it was rebooting to complete the configuration for new SIM functionality. It then rebooted itself to TWRP. From TWRP I selected boot system and then it would start the same process over. I had no control while the message displayed. I also noted random crashes at the same time while Android was booted.
I cleared cache and tried again with no change. Really happy you got it working, can you detail your progress?
Thanks!
sirebral123 said:
After android booted the system said it was rebooting to complete the configuration for new SIM functionality. It then rebooted itself to TWRP. From TWRP I selected boot system and then it would start the same process over. I had no control while the message displayed. I also noted random crashes at the same time while Android was booted.
I cleared cache and tried again with no change. Really happy you got it working, can you detail your progress?
Thanks!
Click to expand...
Click to collapse
Ya, that's the same issue I had.
I just typed it up in another response on the Superman Rom for g930f thread:
https://forum.xda-developers.com/showpost.php?p=77640954&postcount=13063
basically, when at the point you were at, you could pull the sim card (you won't get the error when you have no sim in the device) and keep on going with the setup, until you have the device rooted (recommend magisk) and then connect to your device and disable the package that's giving you a problem, using the adb shell and "su; pm disable com.sec.android.AutoPreconfig"
I was able to get the phone to stop rebooting with the sim installed by disabling the preconfig service, yet I'm still left with weirdness. I am getting two crashes that appear to be associated with Samsung Messages (SMS program). Copy code and messages are continually crashing.
Also, I am able to see the wifi calling in the pulldown, yet it doesn't appear in the actual configuration menu. Things are still very wonky with the Nougat CSC.
Any ideas?
I was able to get past the sim card issue, yet then experienced several FCs from "Messages", "Floating text" and "Copy text".
I tried clearing cache, a dirty install of Superman, clearing messages data, no dice, same errors. Also, as mentioned the wifi calling still doesn't show up in the other network settings, although volte does show up and the icon for wifi calling shows in the pulldown config, yet I can't open details.
Note, I also saw a note from the developer of CSC Selection that said nougat CSCs had the potential to causes FCs, not sure where I saw it, yet probably on these forums or on his website.
I haven't tried a clean install yet, but that's my last option as it entails a day of work.
Still hoping someone has the answers.
sirebral123 said:
I was able to get the phone to stop rebooting with the sim installed by disabling the preconfig service, yet I'm still left with weirdness. I am getting two crashes that appear to be associated with Samsung Messages (SMS program). Copy code and messages are continually crashing.
Also, I am able to see the wifi calling in the pulldown, yet it doesn't appear in the actual configuration menu. Things are still very wonky with the Nougat CSC.
Any ideas?
Click to expand...
Click to collapse
Not really, except that my approach, when encountering issues like this, is often to start at the beginning and fully work through it again. When I had this issue, I was not satisfied to have let the system boot multiple times, so I actually shut down, uninstalled the sim, reformatted /data, fully wiped, installed SuperStock kernel with the ROM, did not ever let it install bootloader and modem (stayed with what samsung pushed with the initial Oreo update, ERG2), i DID let the aroma installer install the default btu csc, then when rom install completed, I installed the tzo csc, booted once to the spanish "Hola" screen, immediately rebooted to recovery, installed tmb csc, rebooted again, did the initial android wifi and google setup, rebooted, installed magisk, rebooted and adb shell disable that package, shut down, install sim, reboot and went to steps 7,8,9 from here https://forum.xda-developers.com/showpost.php?p=69864872&postcount=5484 I honestly have NO IDEA why that link had me install the brazilian csc right after rom install, boot then install the tmobile US csc... that seems weird, but I did it, and it worked (?) At any rate, since I had fought with it for a few hours prior to that, I kinda knew how I should properly sequence the setup for best chance at success, starting from the beginning. I have a g930f.... is yours a g935f? not sure that would make a difference, but if you have the same hardware, then you must be able to reproduce the successful results.
I should also add that wifi calling is not something that I've actually done... I haven't needed it yet. But I do have the selection in Connections > Mobile Networks > VoLTE calls, and I use LTE Discovery app to show me that my phone connects to LTE band 12 now. I also now have a working "Wi-Fi Calling" toggle in my toggles pulldown menu, and while it is on, I made a phone call while connected to my home wifi. I haven't yet figured out how to verify it's working. I suppose if I really want to test this, I could tin-foil the house so I can't get cell signal, then see if I can make a phone call while I'm on wifi!
---------- Post added at 08:42 PM ---------- Previous post was at 08:05 PM ----------
sirebral123 said:
I was able to get past the sim card issue, yet then experienced several FCs from "Messages", "Floating text" and "Copy text".
I tried clearing cache, a dirty install of Superman, clearing messages data, no dice, same errors. Also, as mentioned the wifi calling still doesn't show up in the other network settings, although volte does show up and the icon for wifi calling shows in the pulldown config, yet I can't open details.
Note, I also saw a note from the developer of CSC Selection that said nougat CSCs had the potential to causes FCs, not sure where I saw it, yet probably on these forums or on his website.
I haven't tried a clean install yet, but that's my last option as it entails a day of work.
Still hoping someone has the answers.
Click to expand...
Click to collapse
What kernel did you install?
Yeah, I dug a little deeper, and I may not have wifi calling working, as it is not something that shows up in Settings, and if there is a toggle, I should be able to find it in settings. .... same as you, I have the wifi calling toggle, and VoLTE in settings, but not wifi calling in settings. weird that my toggle doesn't seem to have an issue turning on and off... I'll need to figure out how to test this.
No force closing though. It all seems quite stable, actually. But, yeah, it takes forever to setup all the apps..... about 50 of em!
Good luck!
Thanks for your diligence, I'll continue to hack away at it as well and perhaps we can put this to rest together. I did find one other CSC that does seem to work until it tries to register the WIFI calling. Perhaps this will help us. I'll attach it in the next message. (Need to post it from my phone).
Here's the TMO version that I was able to install without issues. I think it's Europian, yet it does show VoLTE and WIFI calling enabled. The issue is when it tries to register on the TMB servers (probably pointing to Germany). My hope with posting this is that someone with more skill than I can assist with the setting(s) that need to be changed to have it register on the TMB servers.
https://mega.nz/#!LeAVxQ6T!6WnCmQ0N5kFbGW83AAf_qyLmhM5g-3UNCnS6wIl5boc
sirebral123 said:
Here's the TMO version that I was able to install without issues. I think it's Europian, yet it does show VoLTE and WIFI calling enabled. The issue is when it tries to register on the TMB servers (probably pointing to Germany). My hope with posting this is that someone with more skill than I can assist with the setting(s) that need to be changed to have it register on the TMB servers.
https://mega.nz/#!LeAVxQ6T!6WnCmQ0N5kFbGW83AAf_qyLmhM5g-3UNCnS6wIl5boc
Click to expand...
Click to collapse
I read this morning, the suggestions from the selection tool thread, to install the tekhd csc from here that's for the S8, so I wouldn't take the chance, but since you did, kudos!
I downloaded and opened the package you linked, and I'm looking at the xml to see if there is a european server.... and looking also at the tmb csc from tkkg's package in source here: https://github.com/GrifoDev/CSC/blob/Nougat/aroma/csc/XAA/system/csc/TMB/system/csc/customer.xml
In that customer.xml file there is the closest thing I found to a tmobile url with respect to wifi, which is "wlan.mnc260.mcc310.3gppnetwork.org" and that url is the same url found in tekhd tmb crc
btw, in your csc package there is others.xml, and in there is: "<CscFeature_Setting_SupportWifiCall>TRUE</CscFeature_Setting_SupportWifiCall>"
I am very tempted to add that line in the tmb csc inside Tkkg's 2.5.0 selection tool, and flash it to my phone to see if that exposes the wifi call setting with my setup..... My pessimism tells me that things are never that easy!
Also, Tkkg announced this morning in one of his SupermanRom threads that he will be updating the csc selection tool for Oreo soon.... keeping fingers crossed that will be sooner rather than later.
Edited:
The csc you linked to is T-Mobile US.... check out the customers.xml file <CustomerData> <GeneralInfo> <Country> USA
The csc you linked to is T-Mobile US.... check out the customers.xml file <CustomerData> <GeneralInfo> <Country> USA[/QUOTE]
So.. it seems the one I uploaded is for the s8 as well. It does seem to work until wifi calling enabled, then it fails to register.
sirebral123 said:
The csc you linked to is T-Mobile US.... check out the customers.xml file <CustomerData> <GeneralInfo> <Country> USA
Click to expand...
Click to collapse
So.. it seems the one I uploaded is for the s8 as well. It does seem to work until wifi calling enabled, then it fails to register.[/QUOTE]
Have you had any luck? I've been able to recreate everything so far in this thread and taking some advice from this one: https://forum.xda-developers.com/s7-edge/development/utility-flashable-csc-selection-30-t3392957. WiFi calling is still a no go for TMB.
Nope, nothing as of yet. ?
Tkkg locked that thread as soon as he posted the updated CSCs for Oreo. The tmb csc in that update doesn't work for me at all. Phone just crashes. Nothing tested and no way to discuss what does and doesn't work. 3.0.0 csc tool can not be taken seriously, unfortunately.
Related
Here is the link to the tmobile original thread
[ODIN] Stock Nougat Firmware [SM-G935T] S7 Edge
Instuctions provided by jrkruse (original post)
1. You need to be on Verizon Beta Nougat 2
2. In developer options turn on OEM unlock
3. Reboot to download mode
4. Load the files you downloaded in the corresponding slots in odin BL,AP CP, CSC the files are labeled this way
you dont use the G935TUVU4BQB1_Boot_Recovery_Image.tar.md5 until later
5. Install with odin the phone will reboot to recovery to finish the csc install
6. If the csc install in recovery fails reboot to bootloader in stock recovery
7. In odin reflash the CSC file in the CSC slot in odin. The phone will reboot to recovery again and install the csc files
8. Once the phone is done installing and wiping in recovery try and catch the phone as it reboots and reboot back to
download mode (PWR+Home+Vol Down )
9. Use odin Install G935TUVU4BQB1_Boot_Recovery_Image.tar.md5 in the AP slot
10. Let phone reboot and go through setup
11. During Setup you may have trouble typing info in the setup boxes the keyboard has some bugs in setup. I recommend skipping
adding any accounts and do it after your through setup. Or use the alternative method to find your google account
12. Once through setup download 4G LTE Switch and use to Change Network to LTE/CDMA auto (PRL)
13. I recommend downloading Package Disabler Pro (It Works now) and disable all Tmobile Apps
I found samsung pay wasnt working I found that the tmb bootloaders and persist.img needed to also be flashed I made a new odin flashable package and install instructions. All seems to work now except of course volte and wifi calling.
Explanation why you need to be on nougat beta 2
Download:
TMOBILE_NOUGAT_VZW.ZIP
ODIN v3.12.3.zip
Possible Issues and solutions :
Q: after flashing the bootloaders and persist.img, it broke all data and calls and texts again.
A: they need to be all flashed at same time. Maybe Wipe data and it might work
Q: The Google "email or phone" text input box still only accepts one letter and any extra letters overwrite the previous letter typed.
A: The samsung keyboard will work fine if you just goto settings on the keyboard to language and types and change to US english.
Q: So the question is..... this worth flashing or wait for vzw?
A: Other than no volte this definitely the best running Rom so far. It is much better than beta
Q: 13. I recommend downloading Package Disabler Pro (It Works now) and disable all Tmobile Apps
Care to share your list?
A: List of Tmo apps to disable
Q: Except MMS isn't working, for me anyways. VoLTE isn`t working.
A: I got volte working and video calling maybe this will help mms for you
Download App shortcut maker from playstore
Select all activities find IMS Settings and create shortcut
Open the ims settings from the created shortcut
Choose Ims service switch
Click on MMTEL switch
Click on RCS switch
Under MMTEL section I enabled all the options
Q: Cant get this thing to flash CSC...just keep getting the dm-verity error 0x02.
A: 1:Flash all 4 files in zip.
2:let reboot and see if you get dm verity error.
3:if you get the error than reboot to bootloader and reflash all 4 again.
4:after it reboots again it will say error.
5:reboot to bootloader and flash the csc again.
Q: in 4g lte switch, i dont see the option for lte/cdma auto. could this stuff be because csc didnt flash correctly?
A: if you have the verizon data icons you know the 4g lte then it flashed correctly. If you see data icons that ate not verizon then it didnt flash correctly.
When every one is starting over are you flashing a pit file when going pack to ph1. If not you need too.
P.S. All credits goes to jrkruze. :good:
You mentioned to install Nougat beta first before installing t mobile firmware. Is that necessary? Also, any link for Verizon apn?
Sent from my SM-G935V using Tapatalk
junear said:
You mentioned to install Nougat beta first before installing t mobile firmware. Is that necessary? Also, any link for Verizon apn?
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Look at you apn settings and just copy it. I didn't mention about to install nougat beta, I mentioned that it was installed successfully on nougat beta and that you must be on latest bootloader.
Okay so I have T-Mobile Nougat installed on my device, and I've changed my VPN over to VZWINTERNET, and I can't seem to get anything working (calls or data).
I'll continue to toy around with things though.
FoxyDrew said:
Okay so I have T-Mobile Nougat installed on my device, and I've changed my VPN over to VZWINTERNET, and I can't seem to get anything working (calls or data).
I'll continue to toy around with things though.
Click to expand...
Click to collapse
Same here
is there maybe a need to change to verizon csc?
j3ffm1ll said:
is there maybe a need to change to verizon csc?
Click to expand...
Click to collapse
are you meaning swap the pi3 csc to odin vice the csc that came with the firmware. I guess we can try that. worst thing no load, flash back stock.
justinsch03 said:
are you meaning swap the pi3 csc to odin vice the csc that came with the firmware. I guess we can try that. worst thing no load, flash back stock.
Click to expand...
Click to collapse
just a thought I would try it but I am at work and have to have use of my phone while I am here lol
FoxyDrew, radelon from what firmware did you flashed ?
spiderkr said:
FoxyDrew, radelon from what firmware did you flashed ?
Click to expand...
Click to collapse
The T-Mo one you posted. Odin with ap,bl,cp and csc selected.
After toying with tons of things on the Tmo firmware, I tried booting into Odin, and flashing the Verizon pi3 CSC. That gave me a bootloop. I then tried reflashing the entire Tmo Nougat with Odin, but replacing the CSC again with Verizons, same bootloop. So now my phone is being flashed back to the trusty U MM.
I can only assume now that running the Tmo firmware on VZW will require root to make CSC edits. But Verizon will release our own Nougat before we get root.
Now I guess it's just a race between Verizon releasing 7.0, and the G935U getting it.
$50 on Verizon.
Edit: After flashing the G935U firmware again, after the first boot I was greeted with a message saying "your device must update to use new features from your SIM card." And I booted to a weird all blue screen with a big SIM card on it. I've never seen anything like that. I'm not sure if the Tmo firmware messed with stuff, so I'm going to fully flash the G935V firmware, THEN reflash the G935U firmware, just in case the G935T firmware messed something up.
they also did something to disable all package disabler apps even if you go back to MM they dont work. They screwed us goood on this
so @spiderkr were you able to get it working or just going off of other reports?
radelon said:
The T-Mo one you posted. Odin with ap,bl,cp and csc selected.
Click to expand...
Click to collapse
i mean at what firmware where you before you flash t-mo nougat?
spiderkr said:
i mean at what firmware where you before you flash t-mo nougat?
Click to expand...
Click to collapse
Beta 2 Verizon Nougat
Unable to select network
Under "Network Operators" I selected Verizon Wireless, waited 5 minutes, and now got Unable to select network. Then, maybe a minute or so later, it says "Unable to connect. Try again later." Is there a way around this?
jrkruse said:
they also did something to disable all package disabler apps even if you go back to MM they dont work. They screwed us goood on this
Click to expand...
Click to collapse
I noticed this too, thought I was going crazy lol. That was the only think keeping me from rooting, and considering how horrible root is on this phone, I'm going to Verizon tomorrow to get a Pixel.
Im messing with it I got lte can make and receive phone call receive text but cant send
jrkruse said:
Im messing with it I got lte can make and receive phone call receive text but cant send
Click to expand...
Click to collapse
awesome!! getting closer...
jrkruse said:
Im messing with it I got lte can make and receive phone call receive text but cant send
Click to expand...
Click to collapse
How'd you manage to do that? Still can't get anything to work on my end...
Has anyone successfully (or have any info regarding) converted from a SM-G930U (7.0) to a SM-G930T (8.0)?
I have a completely stock, working S7 SM-G930U (that I previously converted from SM-G930V), updated to the latest Unlocked 7.0 version. I was eager to get Oreo, but didn't want to wait for 930U firmware so decided to just switch to the T-mobile version because I'm on a T-mobile MVNO. However, when I tried just flashing the G930T files with Odin it fails right after the "emmc_appsboot.mbn.lz4" step (whatever that is). This made the phone unbootable and would just boot loop.
I was able to successfully recover the phone by re-flashing the G930U files again after downloading from Updato. So the phone is working again, but I'm right back where I started.
So, my question is: Is there something different that I should be doing, or some other secret to go from U -> T, with the intent of getting Oreo? Would it work if I flashed the 7.0 version of 930T, then taken the OTA update?
Edit: As indicated in the responses below, the solution is the latest Odin version (3.13.1), and I successfully converted. Good luck!
quasihellfish said:
Has anyone successfully (or have any info regarding) converted from a SM-G930U (7.0) to a SM-G930T (8.0)?
I have a completely stock, working S7 SM-G930U (that I previously converted from SM-G930V), updated to the latest Unlocked 7.0 version. I was eager to get Oreo, but didn't want to wait for 930U firmware so decided to just switch to the T-mobile version because I'm on a T-mobile MVNO. However, when I tried just flashing the G930T files with Odin it fails right after the "emmc_appsboot.mbn.lz4" step (whatever that is). This made the phone unbootable and would just boot loop.
I was able to successfully recover the phone by re-flashing the G930U files again after downloading from Updato. So the phone is working again, but I'm right back where I started.
So, my question is: Is there something different that I should be doing, or some other secret to go from U -> T, with the intent of getting Oreo? Would it work if I flashed the 7.0 version of 930T, then taken the OTA update?
Click to expand...
Click to collapse
You need to update your Odin. Oreo ROMs use a new compression format that your old Odin can't handle.
Ultima99 said:
You need to update your Odin. Oreo ROMs use a new compression format that your old Odin can't handle.
Click to expand...
Click to collapse
Update to what? I was using 3.12.7.
Edit: OK, looks like I found it. 3.13.1 is for Oreo, etc. Thanks for the heads-up.
Hi. I have the same Verizon s7 and have also got a 930u rom on it but I am desperate for Oreo. Have you managed to successfully flash the 930t oreo rom? And if so where did you download it from?
updated URL
james909 said:
Hi. I have the same Verizon s7 and have also got a 930u rom on it but I am desperate for Oreo. Have you managed to successfully flash the 930t oreo rom? And if so where did you download it from?
Click to expand...
Click to collapse
Yes, I was successful. You can get the firmware from Updato here: https://updato.com/firmware-archive-select-model?q=SM-G930T&exact=1&r=&v=Oreo(Android+8.0.0)&rpp=15
But ignore their update instructions, as they are outdated and meant for Nougat and below. You need Odin 3.13.1, from here: https://forum.xda-developers.com/galaxy-s8+/how-to/guide-flash-oreo-g955fxxu1crb7-using-t3755789.
If you try with an older Odin version it will soft-brick your device (as I found). Otherwise flashing instructions are simple and the same as when you switched to 930U.
Great thanks. I will try it!
I can't get it to start. I've loaded up the firmware into odin, connected the phone in download mode and it won't start flashing. What could I be doing wrong and is it worth doing anyway?
james909 said:
I can't get it to start. I've loaded up the firmware into odin, connected the phone in download mode and it won't start flashing. What could I be doing wrong and is it worth doing anyway?
Click to expand...
Click to collapse
I can't tell you if it's worth it (I think it is). But you also need the Samsung USB drivers installed on your PC, and you need USB debugging turned on, etc. Make sure you have a working connection before flashing.
It worked. Thanks!
Does it has the whole bloatware thing???
I'm still gonna flash it, but I wanna know, cuz I'm not in my house right now, and also is it laggy???
Whicho_castillo said:
Does it has the whole bloatware thing???
I'm still gonna flash it, but I wanna know, cuz I'm not in my house right now, and also is it laggy???
Click to expand...
Click to collapse
Define "bloatware thing". There's like half a dozen T-mobile apps, plus a small handful of other "pre-installed" things like Whatsapp, etc. Virtually all of them can be disabled. The only one I've found that can't is the official T-mobile account app. But I just cleared the apps data, and never use it. I'm not logged in or anything, so it sits there idle.
Regarding "laggy", I can't really say. It works as well as Nougat did. And I think I can say the battery life is definitively better.
quasihellfish said:
Define "bloatware thing". There's like half a dozen T-mobile apps, plus a small handful of other "pre-installed" things like Whatsapp, etc. Virtually all of them can be disabled. The only one I've found that can't is the official T-mobile account app. But I just cleared the apps data, and never use it. I'm not logged in or anything, so it sits there idle.
Regarding "laggy", I can't really say. It works as well as Nougat did. And I think I can say the battery life is definitively better.
Click to expand...
Click to collapse
Thank for your response, at least I'll be using GoodLock
I have all the files over in the TMobile forum
Use the latest Odin
https://forum.xda-developers.com/tm.../sm-g930t-official-stock-oreo-update-t3810449
---------- Post added at 05:21 AM ---------- Previous post was at 05:18 AM ----------
quasihellfish said:
Has anyone successfully (or have any info regarding) converted from a SM-G930U (7.0) to a SM-G930T (8.0)?
I have a completely stock, working S7 SM-G930U (that I previously converted from SM-G930V), updated to the latest Unlocked 7.0 version. I was eager to get Oreo, but didn't want to wait for 930U firmware so decided to just switch to the T-mobile version because I'm on a T-mobile MVNO. However, when I tried just flashing the G930T files with Odin it fails right after the "emmc_appsboot.mbn.lz4" step (whatever that is). This made the phone unbootable and would just boot loop.
I was able to successfully recover the phone by re-flashing the G930U files again after downloading from Updato. So the phone is working again, but I'm right back where I started.
So, my question is: Is there something different that I should be doing, or some other secret to go from U -> T, with the intent of getting Oreo? Would it work if I flashed the 7.0 version of 930T, then taken the OTA update?
Click to expand...
Click to collapse
U firmware is just firmware without carrier bloat. You can flash any carrier on an unlocked phone. I provided the link to my thread with the official TMobile Oreo stock files just get Odin. https://forum.xda-developers.com/tm.../sm-g930t-official-stock-oreo-update-t3810449
hello. I had flashed my smg930a with smg930U firmware. after that everytime I restarted my mobile, it showed error " no network connection " sometimes it picked up network after a restart and sometimes it picked up network after weeks. Tried flashing smg930a firmware again but the error remains same. Now i flashed it with smg930t firmware hoping the error will end but it shows "searching" and I've no network connection.
any help will be great.
Hi, there's bloatware and it's mildly annoying as is the t-mobile splash screen and sound effect. I'll switch bach to 930u when Oreo is available. You'll also have no data toggle swith in the shortcuts when you pull the screen down. However, I added mine using adb. You can also uninstall programs uing adb but I haven't. If anyone has the adb script for removing t-mobile apps I'd be greatful if they'd post it.
UmerBaig said:
hello. I had flashed my smg930a with smg930U firmware. after that everytime I restarted my mobile, it showed error " no network connection " sometimes it picked up network after a restart and sometimes it picked up network after weeks. Tried flashing smg930a firmware again but the error remains same. Now i flashed it with smg930t firmware hoping the error will end but it shows "searching" and I've no network connection.
any help will be great.
Click to expand...
Click to collapse
Call your network provider or carrier and see if they can change the settings or to make sure your data settings are set up right. Things like apn settings, network, etc.
---------- Post added at 03:18 PM ---------- Previous post was at 03:17 PM ----------
james909 said:
Hi, there's bloatware and it's mildly annoying as is the t-mobile splash screen and sound effect. I'll switch bach to 930u when Oreo is available. You'll also have no data toggle swith in the shortcuts when you pull the screen down. However, I added mine using adb. You can also uninstall programs uing adb but I haven't. If anyone has the adb script for removing t-mobile apps I'd be greatful if they'd post it.
Click to expand...
Click to collapse
Once official Oreo is out for 930u I'm switching back also
UmerBaig said:
hello. I had flashed my smg930a with smg930U firmware. after that everytime I restarted my mobile, it showed error " no network connection " sometimes it picked up network after a restart and sometimes it picked up network after weeks. Tried flashing smg930a firmware again but the error remains same. Now i flashed it with smg930t firmware hoping the error will end but it shows "searching" and I've no network connection.
any help will be great.
Click to expand...
Click to collapse
What network SIM are you using? You kind of need to match the firmware with the carrier you are using, as it enable certain radios. That being said, the 930U should work universally. If it doesn't, then you probably didn't update or use the right APN settings to enable LTE. You'll have to do some online searching to look for the appropriate APN settings for your carrier, especially if you are using a firmware version that doesn't match your carrier.
I have Tmobile G930t.
Can i install G930FD indian rom in it?
Indian roms are for exynos processors i guess..
Pls advice
atin_garg said:
I have Tmobile G930t.
Can i install G930FD indian rom in it?
Click to expand...
Click to collapse
NO!
atin_garg said:
Indian roms are for exynos processors i guess.
Click to expand...
Click to collapse
Yes.
Can i Install this on My 930U its nougat and this to go on OREO ? is it possible ?
Thanks
I managed to get VoLTE working on the xz2cd (H8324) with T-Mobile USA using the xz3 (H8416) USA firmware oem-*.sin files.
Thank you to all the others that figured out the process details so all I had to do was try every combination - see the other VoLTE threads in this forum to guide you on the actual steps. Also thanks to Androxyde and Igoreisberg for the flash & download tools!
I have this working with the H8324_Customized NOBA_1313-6167_52.0.A.8.25_R5B firmware, I happen to choose, replacing only the oem-*.sin files from the XZ3 H8416_Customized US_1316-4522_52.0.A.8.25_R10B firmware. When you set both lines to "LTE (preferred)" and you'll be able to make LTE calls on both lines, however it may only show [HD] calling on the line you configured last I think but it'll be VoLTE on both.
Enjoy and thanks again to all the other threads that guided me through this long but worthwhile trial process. I wish the carriers didn't make LTE VoLTE provisioning difficult, why didn't they just make it universal like 3G.
Note: I was able to separately get Wifi-Calling to appear using the H8276_Freedom CA_1313-8876_52.0.A.8.25_R3B oem-*.sin files but it wasn't functional on T-Mobile USA - I think someone with a little bit more knowledge might be able to get this to work, unless you can point me in the right direction.
Someone please make an open firmware thin/light/compact dual SIM phone with Wifi-Calling/VoLTE (removable battery a bonus)!
Do you think the files would be the same on the H8314 US edition? i'm assuming you need to be rooted for this to work?
Hey Mike, Can you please share(download link) OEM*.sin files of USA firmware for Volte Settings
Im wondering if we can flash the OEM files from the US XZ1 Compact to get T-Mobile VOLTE and Wifi calling? I would try it myself but I cant find one of these phones at a reasonable price. If I do I will try and report back if anyone cares. I am glad at least VOLTE seems to work with this workaround.
VoLTE provisioned on XZ2 but calls are still made over 3G
I’ve done the same for my XZ2 (not compact, H8266). The VoLTE button is now active, but calls are still making over 3G. Any suggestion?
I just talked to a T-mobile specialist, and he confirmed that my phone should work and no need to register or do anything if it supports all bands!!! As he told me "only check for compatibility" and mine is compatible! ?
Were you ever able to get this working? New XZ2 owner and of course I bought this within a week is the announcement about all non VoLTE devices being kicked off in January..
Is there anyway to get volte working for tmobile on the h8314?
XZ2C H8314 VoLTE working on T-Mobile USA
colonelcack said:
Is there anyway to get volte working for tmobile on the h8314?
Click to expand...
Click to collapse
Yes VoLTE works but no VoWIFI with the following method:
Download USA Customized for XZ2C (H8314) and use only the two oem...sin files from XZ3 (H8416) USA Customized. (overwrite the two files in the XZ2C stack)
Use newflasher tool. (I deleted all .ta files and userdata file to avoid losing existing data)
To put the phone into flash mode, power off, hold the vol down button and plug in your usb cable while holding the button until you get a dim green light.
The device will show up in device manager under USB and you can run newflasher as administrator. Please search for a tutorial - there are many that are very good with screenshots of the files you want to move into the newflasher folder.
Some hangups I ran into when setting up and flashing -
Installing flashtool drivers required disabling driver signature enforcement on win10 (Flash device did not show up in usb in device manager until this was done)
For safety, after the flashtool driver install, I performed a repair on xperia companion app in case of any driver conflicts.
Running newflasher again, I got an error: Unable to open ./boot/Apollo_XBootConfig_MiscTA.ta! after multiple system files had been flashed.
But not to worry, the command window said the phone exited flash mode, but got error 933 - unable to sync. - No worries though, just make sure the command window states the phone is out of flash mode somewhere, disconnect your cable and power up your phone.
Then you will get an android message saying your carrier settings will update after reboot and the phone may reboot.
Once rebooted, enter *#*#4636#*#* in your phone dialer app (Takes 30 seconds after fresh boot for the menu to come up) , select phone information, and select LTE only (Note: VoLTE Provisioned will have the slider set to the right, but grayed out - Before the re-flash, the slider was set to the left and grayed out), reboot again. (If you click the 3 dots and look at IMS Status, you will see IMS status Registered, VoLTE Available and UT interface Available - Before the re-flash status was not registered and not available)
Now when you make a call, it will say "HD" in your dialer while on a call and your signal indicator will no longer say 3G when calling.
VoWIFI does not work, but you can use whatapp or something else like googleFi if its a must have, but in my case, I did not want to have to buy a new phone in January when they turn off 3G - Phones are too darn big now anyways and I love the display on this phone.
Notices will go out starting AUG 4th if your phone is marked as not supported using T-Mobile IMEI BYOD online tool - Their tool said my phone does not support VoLTE (Not fully true - It just does not have Band 71 for Long Range VoLTE but will use Band 4(66) just fine, I cannot confirm band 12 even though the phone spec supports it. It appears only Short range VoLTE is working on the phone unless someone else can confirm with this method, My Band 12 tower is behind a hill and i am 20 miles from it) T-mobile currently does not have a whitelist like AT&T, so If the UE (User Equipment - ie. phone) is configured properly, the network will handle the rest. I hope this practice does not change.
The advantage to using this method, is you are using completely stock USA files - My bootloader is locked and i am not rooted BTW. My XZ2C is only carrier unlocked.
The build number of both Roms I used was the same 52.1.A.3.49 XXX - Good Luck.
BTW - Some people were asking what modem config is working with VoLTE on T-mobile USA - to get the modem setting type *#*#7378423#*#* and in the service menu select software info, under Current modem config the value reads:
row/tmobile/vl/us
XZ1 oem files on XZ2 for VOLTE and VOWIFI calls.
nicogu said:
Im wondering if we can flash the OEM files from the US XZ1 Compact to get T-Mobile VOLTE and Wifi calling? I would try it myself but I cant find one of these phones at a reasonable price. If I do I will try and report back if anyone cares. I am glad at least VOLTE seems to work with this workaround.
Click to expand...
Click to collapse
You will need to try this. I was not so brave. The reason is the difference in the build IDs and oem.sin file names between the XZ1 (Old) and XZ2 (Current as of July USA Customized builds).
Mixing and matching files is easier when you are doing so off the same build ID. Thats why V0LTE worked on my XZ2 using XZ3 oem.sin files, they were from the same build ID and had the same names even though the sizes were slightly different.
It may work if the format of the oem.sin file did not change between the XZ1 builds and XZ2 Builds. The more different the builds, the higher the risk of something going wrong.
---------- Post added at 01:31 AM ---------- Previous post was at 01:28 AM ----------
gigili said:
I’ve done the same for my XZ2 (not compact, H8266). The VoLTE button is now active, but calls are still making over 3G. Any suggestion?
Click to expand...
Click to collapse
Enter *#*#4636#*#* in your phone dialer app, select phone information, and select LTE only - Reboot, if you cant make calls after that something else is wrong.
---------- Post added at 01:33 AM ---------- Previous post was at 01:31 AM ----------
hitemup92 said:
Were you ever able to get this working? New XZ2 owner and of course I bought this within a week is the announcement about all non VoLTE devices being kicked off in January..
Click to expand...
Click to collapse
Got this to work, no VoWIFI though - look further down the thread.
depsilon said:
Yes VoLTE works but no VoWIFI with the following method:
Download USA Customized for XZ2C (H8314) and use only the two oem...sin files from XZ3 (H8416) USA Customized. (overwrite the two files in the XZ2C stack)
Use newflasher tool. (I deleted all .ta files and userdata file to avoid losing existing data)
To put the phone into flash mode, power off, hold the vol down button and plug in your usb cable while holding the button until you get a dim green light.
The device will show up in device manager under USB and you can run newflasher as administrator. Please search for a tutorial - there are many that are very good with screenshots of the files you want to move into the newflasher folder.
Some hangups I ran into when setting up and flashing -
Installing flashtool drivers required disabling driver signature enforcement on win10 (Flash device did not show up in usb in device manager until this was done)
For safety, after the flashtool driver install, I performed a repair on xperia companion app in case of any driver conflicts.
Running newflasher again, I got an error: Unable to open ./boot/Apollo_XBootConfig_MiscTA.ta! after multiple system files had been flashed.
But not to worry, the command window said the phone exited flash mode, but got error 933 - unable to sync. - No worries though, just make sure the command window states the phone is out of flash mode somewhere, disconnect your cable and power up your phone.
Then you will get an android message saying your carrier settings will update after reboot and the phone may reboot.
Once rebooted, enter *#*#4636#*#* in your phone dialer app (Takes 30 seconds after fresh boot for the menu to come up) , select phone information, and select LTE only (Note: VoLTE Provisioned will have the slider set to the right, but grayed out - Before the re-flash, the slider was set to the left and grayed out), reboot again. (If you click the 3 dots and look at IMS Status, you will see IMS status Registered, VoLTE Available and UT interface Available - Before the re-flash status was not registered and not available)
Now when you make a call, it will say "HD" in your dialer while on a call and your signal indicator will no longer say 3G when calling.
VoWIFI does not work, but you can use whatapp or something else like googleFi if its a must have, but in my case, I did not want to have to buy a new phone in January when they turn off 3G - Phones are too darn big now anyways and I love the display on this phone.
Notices will go out starting AUG 4th if your phone is marked as not supported using T-Mobile IMEI BYOD online tool - Their tool said my phone does not support VoLTE (Not fully true - It just does not have Band 71 for Long Range VoLTE but will use Band 12 just fine) T-mobile currently does not have a whitelist like AT&T, so If the UE (User Equipment - ie. phone) is configured properly, the network will handle the rest. I hope this practice does not change.
I made the mistake of calling sony and t-mobile for support and they both kept blaming each other, the reason they don't know why VoLTE does not work on some phones is they really don't know enough about their network or the basebands in the phone or the software build process and details about android sin files - as they should not either cause if the network engineers, device manufacturers and software developers all do their job and stick to industry standard practices, it will just work anyway.
The advantage to using this method, is you are using completely stock USA files - My bootloader is locked and i am not rooted BTW. My XZ2C is only carrier unlocked.
The build number of both Roms I used was the same 52.1.A.3.49 XXX - Good Luck.
BTW - Some people were asking what modem config is working with VoLTE on T-mobile USA - to get the modem setting type *#*#7378423#*#* and in the service menu select software info, under Current modem config the value reads:
row/tmobile/vl/us
Click to expand...
Click to collapse
Thank you so much for the detailed instructions! Only one question... Where do I download these files from? And the tool? Can you link me...
Sorry it's been a long time since I've done any xda stuff
H8314 Flash tools
colonelcack said:
Thank you so much for the detailed instructions! Only one question... Where do I download these files from? And the tool? Can you link me...
Sorry it's been a long time since I've done any xda stuff
Click to expand...
Click to collapse
I dont have direct links, but here is an excellent walkthrough that calls out all the tools -
https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/
Search for flashtool on XDA there should be links for that, but you only install the drivers from it, not the tool.
You also need the xperia companion software download from sony website for any missing drivers from flashtool.
Search XDA for newflasher, thats what you will actually flash with - https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
the firmware download utility is xperifirm software - https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
depsilon said:
H8314 Flash tools
I dont have direct links, but here is an excellent walkthrough that calls out all the tools -
https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/
Search for flashtool on XDA there should be links for that, but you only install the drivers from it, not the tool.
You also need the xperia companion software download from sony website for any missing drivers from flashtool.
Search XDA for newflasher, thats what you will actually flash with - https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
the firmware download utility is xperifirm software - https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Click to expand...
Click to collapse
It's been a while but wanted to thank you for taking the time to write out these steps. I finally took a shot with the incoming shutdown of 3g for my XZ2, but unfortunately it did not work. Similar to what gigili said, while VoLTE appears to be provisioned the calls are dropping to 3g/HSPA like they originally were. After setting to "LTE Preferred" and rebooting, calls would not be made at all. I also saw "Unknown" under the Modem Config, and from what you said it should reference T-Mobile after flashing the OEM sin files.
I tried this using the latest firmware available on XperiFirm for the XZ2 (Customized US H8266 - my device is H8276) and the XZ3, which I used to grab the two OEM sin files. The firmware is 52.1.A.3.137.
Using UnSin, I unpacked both "oem_X-FLASH-CUST-B6B5.sin" files in both firmwares, and under modem-config there are a bunch of folders, and each one seems to have a conf files pointing to "mcfg_sw/generic/row/tmobile/vl/us/mcfg_sw.mbn."
I read in another thread that T-Mobile maybe has some way of blocking this workaround now, but I'm not entirely sure if that is true? Totally understand if you've moved on from the device as it's been a while, but am admittedly curious if there's a specific firmware version that this works on I could try to salvage the device.
Volte xz2/xz2 p/xz3 solved
Samir solanki said:
Volte xz2/xz2 p/xz3 solved
Click to expand...
Click to collapse
Details on exactly how?
I will create complete guide thread for the same
Samir solanki said:
I will create complete guide thread for the same
Click to expand...
Click to collapse
Thanks I'll watch for it
I am working to bring support for T-Mobile VoLTE on the xz2c to LineageOS 18.1. As of this writing, official LineageOS builds for this device do not support VoLTE unless it was already enabled and working in the stock firmware.
I have submitted some patches which may resolve the issue for TMO and probably other carriers as well. They work for me, but testing has been limited. If you are interested in using LineageOS instead of the stock ROM, and you are willing and able to build LOS yourself on linux, consider giving my patchset a try. Please read the patch description fully before attempting a build: you will need to obtain and mount some additional files first. The LineageOS wiki has additional instructions for creating a build environment.
EDIT: My patch is part of official LOS 18.1 starting with nightly 20220401. There is no need to build it yourself.
cbs228 said:
---
Click to expand...
Click to collapse
You are a saint for working on this. I bought a H8324 XZ2c recently and was super disappointed it didn't work, so I am back to my XZ1c. Super frustrated. If you ever get a pre-compiled ROM, I would love to try. In the meantime I will try to compile it myself in the coming days despite my technical illiteracy.
If that doesn't end up working, what stock firmware is available with T-Mobile VoLTE enabled and working, so I could step up from that to Lineage? Considering how old the other solutions for trying to get VoLTE working, I am hesitant to try any especially funny business of switching old firmware files from other phones around.
xperiaperson42069 said:
If that doesn't end up working, what stock firmware is available with T-Mobile VoLTE enabled and working, so I could step up from that to Lineage?
Click to expand...
Click to collapse
As far as I am aware there isn't any stock firmware that works "out of the box." The xz2c is listed as "unsupported" by t-mobile, which probably means there isn't any sort of stock ROM out there that works. Sometimes carriers do release "branded" ROMs, but there's nothing like that for this device AFAIK.
LinageOS is designed to be installed "on top" of an existing stock ROM. If you attempt to install it after you have flashed another distro (like an AOSP build), you will likely just make a brick. If you do end up bricking your device, do not despair. You can use Emma to restore your device to factory condition. Emma is available on the Sony Developer World website, and there are many guides available for it.
I have an SM-G930S unlocked. It came with Korean firmware. I am using Mint as my carrier which uses the T-Mobile network. I want to use wifi calling. I am doing so with my three SM-G930U phones on the same carrier.
I have seen two posts where people got SM-G930F or SM-G930FD to work with wifi calling. I have never seen one claiming to do it with an S model.
I installed Superman ROM and followed the instructions to get wifi to work. This was only my second custom ROM installation. I was unsuccessful getting Resurrection Remix to work (it installed, I had BeansGapps, but the play store would not install anything). I unsuccessfully installed Superman ROM once (it hung at 65%, did start anyway, but was REALLY slow). I went to the factory ROM, still no wifi calling. I reinstalled Superman without Magisk. The instructions said install without a CSC, but I could not figure out how (it was not an option), so I used default BTU. I then did CSC Selections to ZTO (Brazil), then CSC Selections XAA sub select TMB. When I restarted, it rebooted to change settings as per my SIM card, but would not restart. I tried it again (ZTO, then XAA sub TMB) without a SIM card, then installing QuickShortcutMaker and opening the wifi calling. The instructions said to turn it on (which I could not find out how to do), but I did hit create (it did not seem to do anything). Still, no wifi calling option.
Did I miss a step in the Superman ROM thing? I could not use v1.8, as I was on Oreo (not Marshmallow).
Thank you in advance for your help.
josephgrab said:
I have an SM-G930S unlocked. It came with Korean firmware. I am using Mint as my carrier which uses the T-Mobile network. I want to use wifi calling. I am doing so with my three SM-G930U phones on the same carrier.
I have seen two posts where people got SM-G930F or SM-G930FD to work with wifi calling. I have never seen one claiming to do it with an S model.
I installed Superman ROM and followed the instructions to get wifi to work. This was only my second custom ROM installation. I was unsuccessful getting Resurrection Remix to work (it installed, I had BeansGapps, but the play store would not install anything). I unsuccessfully installed Superman ROM once (it hung at 65%, did start anyway, but was REALLY slow). I went to the factory ROM, still no wifi calling. I reinstalled Superman without Magisk. The instructions said install without a CSC, but I could not figure out how (it was not an option), so I used default BTU. I then did CSC Selections to ZTO (Brazil), then CSC Selections XAA sub select TMB. When I restarted, it rebooted to change settings as per my SIM card, but would not restart. I tried it again (ZTO, then XAA sub TMB) without a SIM card, then installing QuickShortcutMaker and opening the wifi calling. The instructions said to turn it on (which I could not find out how to do), but I did hit create (it did not seem to do anything). Still, no wifi calling option.
Did I miss a step in the Superman ROM thing? I could not use v1.8, as I was on Oreo (not Marshmallow).
Thank you in advance for your help.
Click to expand...
Click to collapse
The firmware must be unbranded stock for wifi calling to work. Sometimes custom Roms get it working most of the time it just doesn't.
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.