Related
Tried and tried to get wifi calling enabled on my G900F but it would never work. I got a suitable pit file and resized the ext4 partition so it installed correctly, but icon would never appear even when wifi calling enabled in settings and enabled by EE.
Got a G930F Galaxy S7 yesterday. It didn't come from EE so should have come with BTU firmware (I didnt check - but it didn't come with EE EVR firmware). It's a carphone warehouse one. It's the non edge version.
EE firmware appeared today on sammobile so I downloaded it and just went for it, but I expected it to fail so I had the BTU version of the firmware downloaded ready to flash to recover my phone.
It installed without a hitch (no ext4 partition error) and so far wifi calling seems to work. The icon appears at the top of the screen and when I make a call I have a big icon on the call screen. I need EE signal to completely drop in the house before I'm sure though, and annoyingly their signal is stronger than usual tonight.
Congratulations, great to know that someone has this working.
I'm thinking of moving to EE when my current contract with Vodafone ends.
Meanwhile I tried the same procedure, but flashing the Vodafone UK firmware that's recently appeared on Sammobile. Flashing just the AP didn't seem to work as the CSC remained as BTU and no WiFi Calling. So I tried it again, this time flashing the CSC as well as AP in Odin. I ended up with what must have been the Vodafone Germany CSC (VD2) and still no WiFi Calling feature. Then tried flashing just the 'HOME...' CSC and soft bricked it. Managed to get back to the original BTU CSC using Kies3. So I'm not sure what's going on with the current Vodafone UK firmware from Sammobile. Either I messed up somehow or the version they currently have is not Voda UK. Not a very productive day.
I didn't even know vodafone had wifi calling.
I flashed the whole lot - AP, BL, CP and CSC. I think you more than likely need to, or at least I did it so I'd covered all the bases.
Vodafone wifi calling is available on the Galaxy S6 and the iPhone 6's. Via an online chat they confirmed S7 supplied from them (IE running Voda firmware) also has it.
After only just recovering from a soft brick I'll probably wait until updated Voda UK firmware appears on sammobile before having another go. Or until someone else confirms success.
Still, good to know that EE's wifi calling is working.
dosher said:
Vodafone wifi calling is available on the Galaxy S6 and the iPhone 6's. Via an online chat they confirmed S7 supplied from them (IE running Voda firmware) also has it.
After only just recovering from a soft brick I'll probably wait until updated Voda UK firmware appears on sammobile before having another go. Or until someone else confirms success.
Still, good to know that EE's wifi calling is working.
Click to expand...
Click to collapse
I'd wait a bit longer. S7/Edge aren't enabled for Vodafone wifi calling yet. Check their S7 forum for details but no announcements regarding S7 wifi calling have been made. I'm sure it will come eventually...
Good to see EE can do it from day 1 although the usefulness of Vodafone Wi-Fi calling for me took a huge drop when I learned it doesn't do text messages. Think I'll switch to EE (BT) come contact renewal time.
Sent from my Nexus 9 using Tapatalk
Thanks moonray. Just checked the Voda eforum - what a shambles. And I wasn't aware of the inability to send texts via Voda's wifi calling.
But I think you may have to go with EE direct to get their wifi calling feature as I've read that BT will not have access to it?
Only issue is BTU firmware drops well before carriers firmwares, so you mat be left behind
@buachaille did you flash the "HOME" file too?
No. How do you even flash that file? I couldn't see an option in odin that would allow me to do it.
What does the home file do anyway?
buachaille said:
No. How do you even flash that file? I couldn't see an option in odin that would allow me to do it.
What does the home file do anyway?
Click to expand...
Click to collapse
Strange, I flashed them all but it's still showing as on the XEU CSC
---------- Post added at 04:12 PM ---------- Previous post was at 04:04 PM ----------
FSOP said:
Strange, I flashed them all but it's still showing as on the XEU CSC
Click to expand...
Click to collapse
Nevermind, a second flash did it! Wifi calling now working
Don't know what the HOME file does but I made the mistake of experimenting with it, tried flashing it as csc and soft bricked my S7. Won't be touching it again.
FSOP said:
Strange, I flashed them all but it's still showing as on the XEU CSC
---------- Post added at 04:12 PM ---------- Previous post was at 04:04 PM ----------
Nevermind, a second flash did it! Wifi calling now working
Click to expand...
Click to collapse
Well if it worked for you and me, it looks like the ext4 partition problem that plagued everyone with the s5 and s6, is gone :good:
Looks like it!
Sent from my SM-G930F
FSOP said:
Looks like it!
Sent from my SM-G930F
Click to expand...
Click to collapse
Mucking Fagic
It's tempting. But, Slow updates...
It'll probably support volte when ee roll it out properly too
Sent from my SM-G930F
FSOP said:
It'll probably support volte when ee roll it out properly too
Sent from my SM-G930F
Click to expand...
Click to collapse
That shouldnt be EE FW Specific.
I've just bought one of these (via CPW) and on EE. Obvious question, but when my phone arrives tomorrow, I want the EE wifi calling service!
If I grab the fw & flash over odin as usual, I presume it won't invalidate the warranty/screw KNOX etc?
dosher said:
Vodafone wifi calling is available on the Galaxy S6 and the iPhone 6's. Via an online chat they confirmed S7 supplied from them (IE running Voda firmware) also has it.
After only just recovering from a soft brick I'll probably wait until updated Voda UK firmware appears on sammobile before having another go. Or until someone else confirms success.
Still, good to know that EE's wifi calling is working.
Click to expand...
Click to collapse
jonboyuk said:
I've just bought one of these (via CPW) and on EE. Obvious question, but when my phone arrives tomorrow, I want the EE wifi calling service!
If I grab the fw & flash over odin as usual, I presume it won't invalidate the warranty/screw KNOX etc?
Click to expand...
Click to collapse
I have no idea. I'm careless when it comes to warranties and because of this I've never cared about tripping Knox.
You are flashing a carrier branded stock unrooted rom so it's not like you are really messing with the phone, but warranties are provided by big business and we all know big business is run and populated by slime who will use any excuse to get out of paying up for stuff. I think they could use the fact that you are on different firmware from that which came on the phone to slide out of their warranty responsibilities.
buachaille said:
I think they could use the fact that you are on different firmware from that which came on the phone to slide out of their warranty responsibilities.
Click to expand...
Click to collapse
Agreed, I know what they can be like, even at the best of times! However, if KNOX isn't tripped they won't know! Is there anyway you can just check this in your bootloader to see if it's intact please? No rush!
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.
My wife works in a hospital and we used wifi calling because reception was poor.
It's still poor with Tmobile but no wifi calling. When we moved from At&t the wifi
option was greyed out. Tmobile states that it works fine on their network.
Is there any way to get a samsung s7 g930a and a samsung j7-j727a to use wifi calling
on the Tmobile network?
I'm sure it will probably involve something over my pay grade but I am willing to try
anything needed to get this feature to work
JohnAtlas said:
My wife works in a hospital and we used wifi calling because reception was poor.
It's still poor with Tmobile but no wifi calling. When we moved from At&t the wifi
option was greyed out. Tmobile states that it works fine on their network.
Is there any way to get a samsung s7 g930a and a samsung j7-j727a to use wifi calling
on the Tmobile network?
I'm sure it will probably involve something over my pay grade but I am willing to try
anything needed to get this feature to work
Click to expand...
Click to collapse
If your current firmware has WiFi calling (Volte) You can only use Volte if the network supports it. There are however many apps you can use for WiFi calling look on the play store.
Not sure what volte is, I have had some other issues with the
service that I thought might be resolved by installing a
different rom
Tell me if i'm wrong
Thanks
JohnAtlas said:
Not sure what volte is, I have had some other issues with the
service that I thought might be resolved by installing a
different rom
Tell me if i'm wrong
Thanks
Click to expand...
Click to collapse
Volte is wi fi calling over a network which the network operator supports without the need for a specific app.
Please tell me exactly what you are trying to do
What network are both phones using?
Which networks were the phones on initially?
Have you modified the phones in any way? Root? or TWRP?
What firmware are both phones currently using? Go to Settings>about phone>software information>baseband version G930A????
Sorry for not getting back sooner
Both phones are currently on Tmobile network
Both phones were originally on At&t network
No modification
Samsung s7 g930a baseband version G930AUCS8CRL1
Samsung j7-j727a baseband version J727AUCS4BRL1
Note: Wifi calling was available on original at&t network but is now greyed out on tmobile network
JohnAtlas said:
Sorry for not getting back sooner
Both phones are currently on Tmobile network
Both phones were originally on At&t network
No modification
Samsung s7 g930a baseband version G930AUCS8CRL1
Samsung j7-j727a baseband version J727AUCS4BRL1
Note: Wifi calling was available on original at&t network but is now greyed out on tmobile network
Click to expand...
Click to collapse
Ok since wi fi calling is network specific (some have it some don't) you either need to have unbranded firmware on your phone so it works no matter which network is providing it, or you need to now flash T Mobile firmware for it to work again on your phone.
US networks are a nightmare when it comes to this sort of thing and it's a right pain in the a** to solve it. So what you need to search for now on here is how to flash different firmware on AT&T S7. You should always try to flash unbranded firmware so everything works easily, if not it will have to be T Mobile Oreo.
cooltt said:
Ok since wi fi calling is network specific (some have it some don't) you either need to have unbranded firmware on your phone so it works no matter which network is providing it, or you need to now flash T Mobile firmware for it to work again on your phone.
US networks are a nightmare when it comes to this sort of thing and it's a right pain in the a** to solve it. So what you need to search for now on here is how to flash different firmware on AT&T S7. You should always try to flash unbranded firmware so everything works easily, if not it will have to be T Mobile Oreo.
Click to expand...
Click to collapse
Ok, If you think unbranded is the best way to go can you point me in the right direction
updato.com and sammobile.com both host firmware and have flash guides. SamFirmTool also is good for downloading firmware, but only lets you download the latest version and isn't as user friendly.
For unbranded you'll want to look for G930U firmware.
For best compatibility you flash all 4 files using (AP,BL,CP,CSC) this will wipe the phone clean. Otherwise you can try Home_CSC instead of CSC (So AP, BL, CP, Home_CSC) , which keeps your data but may not fully resolve your issues.
Beanvee7 said:
updato.com and sammobile.com both host firmware and have flash guides. SamFirmTool also is good for downloading firmware, but only lets you download the latest version and isn't as user friendly.
For unbranded you'll want to look for G930U firmware.
For best compatibility you flash all 4 files using (AP,BL,CP,CSC) this will wipe the phone clean. Otherwise you can try Home_CSC instead of CSC (So AP, BL, CP, Home_CSC) , which keeps your data but may not fully resolve your issues.
Click to expand...
Click to collapse
What beanvee has said but I think it's worth mentioning I find Sam Firm tool pretty straight forward to use and you'll always get the firmware in separate parts which can be useful.
I found a link for the G930A here
I'm not really understanding the differences in firmware. How is flashing with this firmware
any different than what's on the phone right now?
I am just trying to get the wifi calling to work, How is flashing it with at&t version firmware going
to help me on the tmobile network.
I guess I don't know what I need, stock, unbranded, official or custom rom.
I checked all sites listed and there is no firmware for the J727a, alternative?
I would rather someone more knowledgeable guess what I need to do, if that is what is
necessary because the phones are no good to me without that feature. Any suggestions
would be appreciated.
Each carrier deploys their own CSC file, which contains carrier specific configurations, and its this file that determines if VoLTE or VoWIFI is enabled and how it connects.
AT&T may have different VoWIFI settings to TMobile, which is why using AT&T firmware it doesn't work. Some carriers outright disable it since they don't offer it.
Your best bet would be G930T firmware https://updato.com/firmware-archive-select-model?q=SM-G930T&rpp=15&order=date&dir=desc&exact=1
However unbranded G930U should also work because the unbranded firmware is meant to work on all cariers. G930A would likely get you no where since it'll be AT&T specific
The phones in the USA are all identical hardware under the hood, the only difference is the carrier branding and firmware.
But that's only for the S7, I'm not familiar with the J7.
And it's not through lack of knowledge @JohnAtlas, US phones are a nightmare to do anything with. There are several options available but it's difficult to explain what to do and how to do if you are not familiar with how the software works.
There are many guides on how to unlock the software on all US networks, and depending on the network can include multiple steps to complete, you just have to search and read.
Ok, I was able to find the latest firmware for the G930 phone
I installed odin and have the files, BL, AP, CP, and CSC or Home CSC
My question is, Do I load all files and then start or do one file at a time in odin
I tried all files the first time and got failed error and dismatch
Thanks
JohnAtlas said:
Ok, I was able to find the latest firmware for the G930 phone
I installed odin and have the files, BL, AP, CP, and CSC or Home CSC
My question is, Do I load all files and then start or do one file at a time in odin
I tried all files the first time and got failed error and dismatch
Thanks
Click to expand...
Click to collapse
All files in correct slots and use this Odin https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Put all files in and used patched odin via link
Received fail and screen that said, "An error has occurred while updating the device software"
After reading more, tried to install twrp and received secure check fail : recovery
Rebooted phone and this is the screen right now, not sure what to do next
Thanks
https://drive.google.com/file/d/1QRvaTNb067u49lW1s4UZdRZivK936C2Y/view?usp=sharing
JohnAtlas said:
Put all files in and used patched odin via link
Received fail and screen that said, "An error has occurred while updating the device software"
After reading more, tried to install twrp and received secure check fail : recovery
Rebooted phone and this is the screen right now, not sure what to do next
Thanks
https://drive.google.com/file/d/1QRvaTNb067u49lW1s4UZdRZivK936C2Y/view?usp=sharing
Click to expand...
Click to collapse
That is the system recovery and when you flash with Odin you need to put your phone in download mode first press volume down+home+power. The phone should not go to that screen you have posted either before or after Odin, its a completely different recovery mode.
Get your firmware from updato. Com or sammobile
G930U, filter by USA and choose the latest XAA or USC and use the modified version of Odin. We know this works because thousands of people have used it to do what you are trying to do.
Thanks for info, I used G930U TMK version since we are on Tmobile carrier
It seems to be working fine and wifi calling is available
There is no TMK version for the J727U but will try the XAA for the other phone
The way I understand it is that the U means unlocked and the XAA is generic and not carrier specific
Please advise if I'm not on the right track
Thanks for your help
JohnAtlas said:
Thanks for info, I used G930U TMK version since we are on Tmobile carrier
It seems to be working fine and wifi calling is available
There is no TMK version for the J727U but will try the XAA for the other phone
The way I understand it is that the U means unlocked and the XAA is generic and not carrier specific
Please advise if I'm not on the right track
Thanks for your help
Click to expand...
Click to collapse
That's brilliant , glad your up and running.
So the letter "U"after the "G930" denotes the region of the world the device is build to operate in, the Americas just happens to be U. The unbranded firmware is the one that has a region but no network assigned to it, so a 3 letter code is used instead, in your case its USC, or XAA.
Europe is G930"F" or "FD" and the 3 letter code for unbranded is BTU & XEA.
Anyway if your phone is running great on T Mobile then don't update it anymore, turn auto update off. The advantage of keeping it T Mobile is you have the wifi calling, the unbranded firmware needs more fiddling around with the get the wifi calling working on the network your using, so best to stick with what works.
I will have a look for firmware for the J7 you have to see if i can recommend doing something with it to get the wifi calling working.
*update*
So it seems the J727 is the same as the J7 in terms of the internal components, everything is the same in both models so that's great news. I think the "27" bit is just a marketing thing.
In theory you should be able to flash the latest T Mobile Oreo to your device from this link https://www.sammobile.com/firmwares/galaxy-j7-pop/SM-J727T/TMB/download/J727TUVS4BRK1/249137/
Now before we start please check / do the following to avoid further problems.
1. Save everything you need from the phone to your pc.
2. Check that you have OEM unlocked in "developer settings" and "USB debug" enabled.
3. developer setting menu is, settings>about phone>software and information>build number>tap 7 or 8 times, developer menu should now appear. (Sometimes it's somewhere else but build number is what you want to find and tap on 7-8 times).
4. To avoid any issues with device FRP lock, delete your google account off the phone., settings>accounts>google. delete it. When successfully flashed you just add the account again when the phone starts for the first time by signing in.
5. Use the same version of Odin you used to flash your S7.
you can also use updato.com (i think it's slightly faster than sammobile.)
Let me know how you get on.
Remember J727T (TMB) is the firmware you want.
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.