Database Info

G955FD won't connect to Cricket Wireless in US

I just unboxed my G955FD and put my cricket SIM in and have no response from the network other than pushing an APN and my phone number. I tried manually selecting carrier networks and it listed 5 different "cricket" to attempt to connect to. At one point it showed signal bars in the status area, but no network connectivity. When I automatically connect to the network it responds saying I am registered but no signal bars in status and no activity. I appreciate the help.

Can anyone offer some tips before I call it a lost cause? The phone is out of its return period and probably broken since it will now receive a cricket badge and bars and LTE service but will not make calls or go online

Hey, are you on stock ROM. My 955F works just fine on Cricket, though compared to my daughters AT&T setup, her data is much faster. just discovered this today, and tomorrow will visit Cricket and AT&T to find out why...
Jan 9, 2108 update. I discovered Cricket is limited to about 5-6 Mps. I'm now on AT&T, for a few dollars more for two lines, and can get up to about 40-60 Mps in town.
What region CSC are you using?
---------- Post added at 07:59 AM ---------- Previous post was at 07:35 AM ----------
Here are my apn settings
Name: any but I input Internet or Cricket, I think it will work with whatever you like.
APN: ndo
MMSC: http://mmsc.aiowireless.net
MMSC proxy: proxy.aiowireless.net
multimedia message port: 80
mcc: 310
mnc: 150
apn type: default,mms,fota,hipri,supl
I know when I've setup APs on other phones there have been times that I will first do a 'reset' of my network settings on the phone, then reboot. Sometimes that will help. After that I will enter new APN settings and reboot.
On this 955F, with a viable CSC my phone just finds Cricket and works. With a bad CSC, it may list/show the cricket or AT&T networks, and will not register, no matter what I do, and for how long.
For example, my phone initially had a stock F ROM and a Panama region for the CSC. It worked with Cricket straight away. I changed the CSC to XAA using AT&T, and would find the towers, but would absolutely not register/work.
I ended up installing CarHDROM - a Note 8 OS ported for the 8+, and It took me a bit to find a CSC package that was meant for the ROM (Note 8) I was using, meaning I had to use a Note 8 CSC, even though my phone was an 8+ 955. Once that installed, Cricket started right away.
The CSC that came with CarHDROM I don't think worked straight out, but I can't recall for sure. I did end up using a XAA CSC, for the Note 8, non-AT&Tand that solved my connection issue after I had installed the CarHDROM.
CSC and phone wise, the ROM takes precedent, and the CSC must match the ROM (model). Seems that way to me, anyway.
Hope his helps.

There is another post about a FD phone that won't connect up, as well.
https://forum.xda-developers.com/galaxy-s8+/help/original-firmware-t3725472

I am on stock ROM. I guess I will root today and change CSC and hopefully that fixes whatever issue is going on. I have seen the cricket badge and LTE bars recently but no registration on network. If not, the eBay seller said they will take the phone back I'd it's indeed broken.

Ok so far no luck changing the CSC on stock ROM. I am going to try a couple different ROM and CSC combos tonight. Once again I am showing bars and cricket badge but not connecting data or voice on the phone, after root, and changing CSCs. I feel like Im so close and passed up my last day to return to eBay seller so I hope it truly is software and not hardware related. Im thinking of going by AT&T to act like a potential customer and see if its cricket messing up. Any other suggestions to try before I go crazy and use this phone for target practice?

Is it possible this is a region lock issue? My phone is a Tawain version and it was brand new out of the box. There is no sticker on it mentioning region lock. Does anyone have any insight into region locking for outside EU devices?

ChikhaiBardo said:
Is it possible this is a region lock issue? My phone is a Tawain version and it was brand new out of the box. There is no sticker on it mentioning region lock. Does anyone have any insight into region locking for outside EU devices?
Click to expand...
Click to collapse
Good question. I have a 930S Chinese region and it pulled in ATT/Cricket/TMobile just fine. I did have problems when I flashed a custom ROM, and flashed the CSC that came with the ROM. Later I flashed back the OEM CSC for the region (China) and it worked perfectly, again.
If you do flash a custom ROM, make sure you get a CSC package that is meant for that ROM (model). Not the exact model of your original phone. If you can find an XAA CSC that is meant for the new ROM, should be perfect.

JeffDC said:
Good question. I have a 930S Chinese region and it pulled in ATT/Cricket/TMobile just fine. I did have problems when I flashed a custom ROM, and flashed the CSC that came with the ROM. Later I flashed back the OEM CSC for the region (China) and it worked perfectly, again.
If you do flash a custom ROM, make sure you get a CSC package that is meant for that ROM (model). Not the exact model of your original phone. If you can find an XAA CSC that is meant for the new ROM, should be perfect.
Click to expand...
Click to collapse
Ok I have been changing CSC through TWRP with the CSCSelection Utility. Is that what you are referring to with flashing CSC? Is there a more effective way to do this through Odin? I think tomorrow morning I am going to flash back to stock firmware and start over. Am I able to flash any stock firmware for the SM-G955FD through Odin or do I need the original firmware for my region, which is (BRI) I believe I remembered reading I can flash everything for that model, but not any North American firmware meant for the SM-g955U

ChikhaiBardo said:
Ok I have been changing CSC through TWRP with the CSCSelection Utility. Is that what you are referring to with flashing CSC?
Yes
Is there a more effective way to do this through Odin? I think tomorrow morning I am going to flash back to stock firmware and start over. Am I able to flash any stock firmware for the SM-G955FD through Odin or do I need the original firmware for my region, which is (BRI) I believe I remembered reading I can flash everything for that model, but not any North American firmware meant for the SM-g955U
Click to expand...
Click to collapse
Just flash the CSC that comes 'stock'/with the rest of the full, stock firmware set, Odin will work. Have the SIM in the phone before you reboot, as for me it seems to help.
I haven't found a difference, for me yet, just flashing the exact CSC through Odin or TWRP. As I'm now on a custom ROM, I'm usually flashing via TWRP with a CSC that is supplied by an Aroma setup. Aroma is very handy.
Yes, flash your full stock via Odin. If you have TWRP you will lose it. You can re-flash TWRP from Odin. I typically flash TWRP all by itself, but I don't think that is really necessary. Maybe someone will come along and let us know.
As an aside I always keep a copy of zips/installs of TWRP, re-verity and SU on my SD card.
So after the stock full flash, I reboot into download mode and Odin flash TWRP, and follow that by a direct 3 key reboot into recovery, and TWRP will load. If you are going to root then flash re-verity, then SU/Magisk. You could then flash your CSC, but with the issues you've been having, I'd then boot to system, do the initial setup of the phone, and then boot back to recovery/TWRP, backup the phone.
Then TWRP flash the CSC Aroma package, making sure you have the SIM in the phone and reboot to system. I've been using XAA as my CSC with my custom ROM, within that is AT&T, T-Mobile, etc for US phones. I select the main XAA CSC from Aroma. Next I select the unbranded XAA as my more specific/local package, instead of AT&T, for example.
My 955F, stock worked just fine on it's 'stock' CSC (China region). I only had to change the CSC when I flashed a custom ROM, and that ROM did not have the ROM's (model) of XAA, so I had to find a CSC, which had XAA, that 'matched' the ROM I had flashed. I had flashed a Note 8 ROM, CarHDROM,v8 initially. Again, that ROM was largely meant for Europe and Exynos phones, so I had to be pointed to a Note 8 CSC that was compatible with the Note 8 custom ROM.
Yes, Odin is where you would flash stock firmware/stock CSC (not in an Aroma package) for your SM-G955FD. It is my understanding that all non-US phones, eg the G955's, are mechanically the same, so flashing 'any' Exynos ROM, G955FD ROM should work via Odin. You can also flash CSC packages via Odin as well, but there is no Aroma process, to my knowledge/experience. So have the specific and correct CSC to flash via Odin, if you go that route. It sounds like you are aware your phone is Exynos? A non-US phone?
I specifically bought my G955 (8+) as non-US so it could take root smoothly/easily, and work great world wide, including working great here in the US. Sometimes the U.S. does not seem a part of the world.
As I've been messing about with S7's/8s, there have been times that the phone did not grab onto AT&T, for example, and i would then 'reset' the network and reboot, with the SIM in the phone, then do a search for phone networks/services. That usually solved it, but when it did not, and I know I have the right CSC, I would then input/create a new APN, with AT&T, Cricket, Sprint, or what-ever service I needed, then reboot.
The only times I've not gotten the phone/s to grab the networks after that is when I've had the incorrect CSC.
Again, on my stock what-ever country G955F, stock G930S, etc, all Exynos, with the same stock (non-US) CSC that come in the firmware package, the phones have grabbed AT&T/T-Mobile just fine. If it would not, I would have reset the network, rebooted and entered the APN, and then rebooted (with the SIM in the phone). Done a network search after that, if necessary.
Hope this helps.

So today I stopped by TMOBILE and the store clerk popped a SIM card in and it fired up 4G LTE immediately and made calls. I then decided to stop by AT&T and it showed bars but refused to register or do anything even with the APN settings being pushed through from AT&T and Cricket. I am finally happy to realize that my phone is not defective (which I had feared before) and that it must be this service area and the bands on the G955FD. I have wanted to switch to TMOBILE for awhile now anyway so this is my chance to have an excuse to do it. Any input on why it won't access AT&T through an AT&T or Cricket SIM? I'm curious now more than anything. It must be missing a band that this area uses correct? The phone is clearly unlocked and functioning correctly.

What local CSC r u using?
Did you have AT&T check the APN?
T-Mobile and AT&T work on S8+ just fine, but need appropriate APNs.
Head back to the AT&T, if you want AT&T, and see if they will reset and or reinstall AT&T CSC/OS on your phone. XAA/ATT will have the AT&T boot logo. XAA/XAA (generic US use, ATT/T-Mobile compatible) will not.
One ringy dingy, two ringy dingy's...

SM-G930P to SM-G930U

I have the SM-G930UP baseband version G930PVPS4BQE1
I am preparing to flash the universal firmware, but with the T-Mobile modem. The goal is a phone with the U firmware and the T-Mobile modem.
Download and install Samsung USB drivers: http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Odin utility: https://odindownload.com/SamsungOdin/
Latest SM-G930U firmware files for “USA (XAS)”:
G930UUEU4BRD1_G930OUYM4BRD1_XAS
All U variants have the same baseband etc. numbers , so I assume it doesn't matter which one I use.
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930U/
Latest T-Mobile SM-G930T firmware files:
G930TUVS4BRC1_G930TTMB4BRC1_TMB https://www.sammobile.com/firmwares/galaxy-s7/SM-G930T/
The plan is to back up all data first, extract the all the files (Odin, drivers, and both U and T archives). Install the Samsung USB drivers.
Next steps:
Connect phone to PC.
Shut down phone: Hold Home and Volume-Down buttons while pressing the power button. Press Volume-Up when prompted to place phone in download mode (whatever it’s called).
Open Odin. Wait for Com connected prompt.
Click BL button. Select the SM-G930U BL file.
Click AP button. Select the SM-G930U AP file.
Click CP button. Select the SM-G930T CP file.
Click CSC button. Select the SM-G930U CSC (NOT HOME_CSC) file to wipe and factory reset the phone.
Click Start and wait for Odin to say “Complete.”
Any feedback? Suggestions? Anything I missed?

what baseband are you currently on?

why would you want T-mobile modem? anything wrong with U-version?

turbozapekanka said:
why would you want T-mobile modem? anything wrong with U-version?
Click to expand...
Click to collapse
In some of the reading I have done it appears advantageous to have the carrier modem of the service provider you use; I'm assuming because the carriers tweak the modem for use with their particular infrastructure.
I don't know if that's true, but I have seen a number of posts to that effect. It sounds logical and I figure it can't hurt as long as it works.

InsanePostman said:
what baseband are you currently on?
Click to expand...
Click to collapse
Mr. _Happy said:
I have the SM-G930P baseband version G930PVPS4BQE1
Click to expand...
Click to collapse
Software version is the same. G930PVPS4BQE1 it's from May 2017.

Mr._Happy said:
In some of the reading I have done it appears advantageous to have the carrier modem of the service provider you use; I'm assuming because the carriers tweak the modem for use with their particular infrastructure.
I don't know if that's true, but I have seen a number of posts to that effect. It sounds logical and I figure it can't hurt as long as it works.
Click to expand...
Click to collapse
I doubt it.
I've been using U-version (converted from SM-G930P) on T-mobile for a year and found no issues whatsoever.
I was reading the opposite, something like U-version has more LTE bands unlocked (which makes sense as it should work with all carriers)
Also someone here claimed it has extra bands for Europe. like band 7, 20

turbozapekanka said:
I doubt it.
I've been using U-version (converted from SM-G930P) on T-mobile for a year and found no issues whatsoever.
I was reading the opposite, something like U-version has more LTE bands unlocked (which makes sense as it should work with all carriers)
Also someone here claimed it has extra bands for Europe. like band 7, 20
Click to expand...
Click to collapse
Interesting. That seems logical too.
Unfortunately I may not be flashing anything as every time I have downloaded firmware from SAMOBILE and extracted it I have got an error message that the AP portion has a problem. If I "retry" it gives me the same error. If I "skip" it unpacks everything except the AP file. I have tried several times with multiple downloads. Each one took the full two hours to download, so it's been a lengthy process with no results.
When you flashed the G930U which variant did you use?

Mr._Happy said:
Interesting. That seems logical too.
Unfortunately I may not be flashing anything as every time I have downloaded firmware from SAMOBILE and extracted it I have got an error message that the AP portion has a problem. If I "retry" it gives me the same error. If I "skip" it unpacks everything except the AP file. I have tried several times with multiple downloads. Each one took the full two hours to download, so it's been a lengthy process with no results.
When you flashed the G930U which variant did you use?
Click to expand...
Click to collapse
I flashed version G930UUEU4APL2 with odin 3.12.3
It was back in January 2017. Note the number 4 in the version. This indicates bootloader version.
I believe you can no longer flash this version if your current version has 5 (or any greater number) in place of 4 because you're not allowed to downgrade the bootloader version.
Sprint is known to bump the bootloader version from 4 to 5 for (supposedly) blocking this type of conversions of their branded phones.

turbozapekanka said:
I flashed version G930UUEU4APL2 with odin 3.12.3
It was back in January 2017. Note the number 4 in the version. This indicates bootloader version.
I believe you can no longer flash this version if your current version has 5 (or any greater number) in place of 4 because you're not allowed to downgrade the bootloader version.
Sprint is known to bump the bootloader version from 4 to 5 for (supposedly) blocking this type of conversions of their branded phones.
Click to expand...
Click to collapse
Mr._Happy said:
I have the SM-G930P baseband version G930PVPS4BQE1
Click to expand...
Click to collapse
Sprint is currently on bootloader 6, actually. Crappy obstructionist commercialism specifically to block people converting.
I have been denying and rejecting the software updates since May of 2017 which is when I got that software version, so your G930UUEU4APL2 firmware from January would not work on this phone as my Sprint firmware is more recent.
I should be able to flash the most recent version of G930U, however. I just can't seem to download one that will extract the AP portion. It's really frustrating.

Try this https://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-g930uueu4apl2-sm-g930u-t3535230
You should be able to flash any firmware as long as the bootloader version is the same
For newer firmwares you may need to use the latest Odin version (3.13.x)
---------- Post added at 12:15 PM ---------- Previous post was at 12:07 PM ----------
I wonder why did you choose XAS version.
I also remember back in time I downloaded two versions of U-firmware (SPR and XAA) and compared the files they appeared identical.

turbozapekanka said:
I doubt it.
I've been using U-version (converted from SM-G930P) on T-mobile for a year and found no issues whatsoever.
I was reading the opposite, something like U-version has more LTE bands unlocked (which makes sense as it should work with all carriers)
Also someone here claimed it has extra bands for Europe. like band 7, 20
Click to expand...
Click to collapse
What ROM have you been running?
Looks like slim pickins for the snapdragon chipset.
I assume all Exynos ROMs would obviously not work .
I have a SM-G930VL that I flash the G930U firmware . Much better

Stock

turbozapekanka said:
You should be able to flash any firmware as long as the bootloader version is the same
Click to expand...
Click to collapse
This is what I was saying. The last Sprint update I did on the phone was May 2017. I have been dismissing the update nag since then. Which means I could flash any G930U firmware with a date later than May 2017 with the same bootloader number.
Sprint has been trying to block this: their bootloader number is currently on 6, all the other carriers are on 4.
turbozapekanka said:
For newer firmwares you may need to use the latest Odin version (3.13.x)
Click to expand...
Click to collapse
Yep. The link I used to download the latest version was in the first post of this thread. 3.13 worked just fine.
The problems I was having had to do with the my computer, but I solved them and was able to to flash the latest version of G930U.
The phone is snappy and without the annoying lag.
Call quality improved immediately. With the Sprint firmware on the T-Mobile network there was a glitch with using the voicemail icon on the dial screen - it would fail to call the voicemail and give an incomplete call error; the workaround was to call myself from contacts and enter my pin to get to my voicemail. Now the voicemail icon on the dialer takes me to voicemail without a hitch. When calling it doesn't have a 15 - 20 second wait before ringing the number (the top left of the status bar would read "Attempting"). Internet reception is also better especially in the NYC subway.
Also as soon as my phone went from Sprint to T-Mobile I could no longer send or receive pictures via text. Apparently Sprint firmware wasn't interested in sending MMS messages anymore, but with the U firmware they work just fine and regular texts go through more quickly as well.
So far battery life is about the same as far as I can tell, maybe a marginal improvement. Nothing to call home about.
But mostly I seem to get the overall desired reception improvement: it stopped dropping calls, and the call quality is solid and the undersea world that had been happening with the Sprint firmware is gone.
Also the fingerprint scanner is working better.
It's much improved.
I REALLY like how it seemlessly goes from voice on network to voice on WiFi.
Question: will this get OTA updates? Is it fantasy to think the G930U will get Oreo?
I am interested in testing the various towers, most frequent LTE bands, signal strength, and handset radios. Is there a thread for that or any apps you know of?

Mr._Happy said:
Question: will this get OTA updates? Is it fantasy to think the G930U will get Oreo?
Click to expand...
Click to collapse
Yes it will get OTA updates including Oreo. U-version lags behind branded versions in this regard though.

i'm just got the oreo update - installing right now (us cellular)

i have tmobile g930t
if i shift to U , will volte work?
because i am unable to use volte in india now

Hey guys so I am brand-new to all this but need to convert my g930p to g930u. I just want to clear this up: because my software version is Q930PVPU6CRE7, I won't be able to flash the version OP used but must find a version with a 6 in it?

I'm in the same boat with my wife's phone. Limited bands available meaning it's on 3G more often than not, and MMS won't work if connected to WiFi. Not to mention the sprint junkware... is there any way to change from G930P to a G930U firmware if the phone is currently on bootloader version 6? I don't mind rooting...

I flashed G930U on G930P but network still not working. It shows unknown network and Radio Off. Mobile can read SIM menu and Contacts but no signal. Any help please?
EDIT: Now I know that changing ROM or rooting does not network unlock.

Mr._Happy said:
I have the SM-G930UP baseband version G930PVPS4BQE1
I am preparing to flash the universal firmware, but with the T-Mobile modem. The goal is a phone with the U firmware and the T-Mobile modem.
Download and install Samsung USB drivers: http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Odin utility: https://odindownload.com/SamsungOdin/
Latest SM-G930U firmware files for “USA (XAS)”:
G930UUEU4BRD1_G930OUYM4BRD1_XAS
All U variants have the same baseband etc. numbers , so I assume it doesn't matter which one I use.
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930U/
Latest T-Mobile SM-G930T firmware files:
G930TUVS4BRC1_G930TTMB4BRC1_TMB https://www.sammobile.com/firmwares/galaxy-s7/SM-G930T/
The plan is to back up all data first, extract the all the files (Odin, drivers, and both U and T archives). Install the Samsung USB drivers.
Next steps:
Connect phone to PC.
Shut down phone: Hold Home and Volume-Down buttons while pressing the power button. Press Volume-Up when prompted to place phone in download mode (whatever it’s called).
Open Odin. Wait for Com connected prompt.
Click BL button. Select the SM-G930U BL file.
Click AP button. Select the SM-G930U AP file.
Click CP button. Select the SM-G930T CP file.
Click CSC button. Select the SM-G930U CSC (NOT HOME_CSC) file to wipe and factory reset the phone.
Click Start and wait for Odin to say “Complete.”
Any feedback? Suggestions? Anything I missed?
Click to expand...
Click to collapse
if i try this method to convert smg930u to smg930f will it work cuz meh need root ?

S7 International Oreo CSC for T-Mobile

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.

At&t branded phones on Tmobile network

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.

SM-G930S wifi calling?

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.