Related
I noticed that my galaxy was sluggish & decided to preform the solution here: hemorrdroids.net, speed up your Samsung galaxy S
now in the process, i got it wrong several times whiles flashing with the odin. when I finally got it right and reinstalled the firmware, the phone displays a no service notification, but show the name of the network chip in it. no signal bars as if it were locked. I bought it as unlocked phone. now I cant even search for a single network in my country. when u do a manual search, it returns nothing. if u try the dialer it says not registered to network..
does anyone know how to get my signal a GPS working?? please!!!!!!!!!!!!!
Hmm... I've got the same problem as you... Flashed docs to my Galaxy S Yesterday and now it show no service notification.... Anyone who have a got an idea?
I am also facing the same problem. Any one who has solved it ?
Got the same problem, from 1 day i have notification (no service)
Got the same problem plz plz some one helpp
Not sure if it's the same problem you folks are having, but there's a thread on here entitled "Problem with Airplane Mode on Epic after installing midNight ROM" that describes a problem with no signal after a ROM flash, and a solution via using Odin to update just the modem.
I would post a link, but the forum here won't let me because I don't have enough posts. Your mileage may vary, but the symptoms sound similar so it might give you a place to start even if the fix doesn't fix you.
I too am having the same problem. It seems that my Phone (Galaxy SC-02b) does not recognize the modem/internal antena.
I installed the Darky's Rom on it, and it runs great. Except the signal part. I can flash it back to the original, but I want to see if I can make it work.
I think it's just a matter of picking out the correct modem tar, but I can't find the right one. My phone is a little bit odd, It's a Japanese Galaxy, so not sure if I can find it here. Unfortunately my Japanese is not good enough to go scouring the japanese forums.
Thanks for any help.
Hey Yefimenko what 3G bands are used in Japan 1900/850 or maybe 900/2100 or 1700/2100 ? Can you find that out ? then you need to flash modem that supports that , Europe support 900/2100 US/Canada/Australia 850/1900 and AWS 1700/2100 Tmobile US /Wind? mobilicity Canada
Hitec
We've been through all of this before the Japanese phones will only work with the Japanese kernel. Symptoms are usually sin not recognized and no radio signal. QUOTE=yefymenko;11612862]I too am having the same problem. It seems that my Phone (Galaxy SC-02b) does not recognize the modem/internal antena.
I installed the Darky's Rom on it, and it runs great. Except the signal part. I can flash it back to the original, but I want to see if I can make it work.
I think it's just a matter of picking out the correct modem tar, but I can't find the right one. My phone is a little bit odd, It's a Japanese Galaxy, so not sure if I can find it here. Unfortunately my Japanese is not good enough to go scouring the japanese forums.
Thanks for any help.[/QUOTE]
Sent from my SC-02B using XDA Premium App
Either the phone.apk is bad or the modem is incompatible.
You could try the http://romkitchen.org/ and make an update with different modem only.
If your Samsung Galaxy S displays no network/no signal, or emergency calls only, try the following things:
1. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site too)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you on Galaxy S.
For this, you’ll need root. If you have a root-enabled kernel, like the Voodoo lagfix kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC (to XEO for Europe): enter *#272*imei# on the phone tab. Note: this will reset your phone to factory settings, so make sure you did a clockworkmod backup before this. Incorrect CSC setting may cause MMS not working also.
4. check if you inserted the SIM card correctly
Thanks
MertBaBaaa
first check imei no
hello for all members,
i have solution for this problem "not network or not signal" Samsng Galaxy SC-02B Docomo
later write my solution phone work all World
__________
XcachorroX
galaksy s no signal
3. you can try changing the CSC (to XEO for Europe): enter *#272*imei# on the phone tab. Note: this will reset your phone to factory settings, so make sure you did a clockworkmod backup before this. Incorrect CSC setting may cause MMS not working also.
this solution works for me and thanks alot many many thanks
maybe i've got a solution for the no service probleme. i tried this code *2767*3855# and my phone works normal now
i hope it works for you guys
No Network after change of CSC - is there a recovery strategy?
SOLVED
======
Asked around and it goes like this: 2.1 + market = no signal, (2.2 or 2.3) + market = no problem
Solution is UPGRADE from 2.1. to 2.2 or better - I hope this will help anyone else with the same problem.
If you can't do it yourself, any mobile shop will for a small fee.
Symptoms
========
Changed CSC from KSA to XSG with code *#272*HHMM# for 2.1 (no Market in KSA mode)
Galaxy S GT-I9000 now shows blue circle with diagonal in notification area at top of screen.
Settings > Wireless and network > Mobile networks Network mode > Network operators > Search Networks or Select Automatically produces no response - finds no networks.
Dialpad dial a number => "Not registered on network"
Coincidental hardware failure seems very unlikely but not impossible I suppose.
What I would like to know is if there is a recovery strategy from here?
Even if it includes installing a complete new firmware? (and possibility to revert to original if required for warranty)
Device does not respond to "3-finger salute" (volume-home-power).
I am not confident that a warranty is worth all that much in this part of the world. It may be quicker and more effective to do it myself.
Further details of history and phone info below.
I will be very grateful if anyone can help me out
History
=======
Phone purchased in Saudi Arabia (KSA). Worked fine with pre-paid SIM (mobily) voice, data, sms, wifi.
Phone also worked fine with a pre-paid sim (cosmote whatsup) in Greece - voice, data, sms, wifi.
However, since phone was purchased in KSA, Android Market was not installed. Found a Market.apk and installed that. Installs but doesn't actually work.
Found code for changing CSC (*#272*HHMM# for 2.1, *#272*[IMEI No]# for 2.2) 2 colleagues had success and no problems with this with a Tab and 2 Ss, albeit with 2.2. The code looks worth a try on 2.1 so I gave it a go.
Had to remove the side-loaded Market before the code would run and changed the CSC from KSA to XSG.
Market pops up on the screen and works fine.
BUT no network. Network name shows in the Notifications though. The GR SIM shows "(No Service)"
Factory reset, returning CSC to KSA do not help.
The mobily SIM works fine in other phones but no known good SIM works in this phone.
Mobily tech support (in store visit, usually commpetent guy who knows me) is completely flummoxed and asks me if I have a warranty.
So now I have a very compact WiFi only tablet
Phone Info
==========
Model number: GT-I9000
Firmware version: 2.1-update1
Baseband version: I9000JXJG2
Kernel version: 2.6.29 [email protected] #2
Build number: ECLAIR.JPJG8
Personalisatiob(sic) Status
Network Lock
[OFF]
Network Subset Lock
[OFF]
SP Lock
[OFF]
CP Lock
[OFF]
Settings > Wireless and network > Mobile networks Network mode > GSM/WCDMA (auto mode)
Solution to your problem
Hi All,
This happened to me before and I was as frustrated as you and when I was about to give up, I tried one last restoration, but only this time I did it correctly. After that, I restored 5 different versions of Samsung Galaxy S stock ROM back to my Samsung Galaxy S. One of these versions were Chinese, and everything was in Chinese.
Samsung Galaxy S had no signal was because the modem file was missing while you were performing the restoration.
Now, all you have to do is go to this page and follow the instructions to restore the Stock ROM back to your Samsung Galaxy S.
same problems
Hi guys, I have same problem. But a litle diffirent.
When I use 2.3.6 firmware version it's work well no problem. But when I use 4.x.x Rom it says no network and no imei. If I use 4.x.x om pluged the charge my device ,I see gsm company and imei number. It's very interesting. I think , electricty not enough for my device. Maybe Its hardware problems. I 'dont any idea.
How can I solve this problem?
Thanks.
I managed to get VoLTE working on the xz2cd (H8324) with T-Mobile USA using the xz3 (H8416) USA firmware oem-*.sin files.
Thank you to all the others that figured out the process details so all I had to do was try every combination - see the other VoLTE threads in this forum to guide you on the actual steps. Also thanks to Androxyde and Igoreisberg for the flash & download tools!
I have this working with the H8324_Customized NOBA_1313-6167_52.0.A.8.25_R5B firmware, I happen to choose, replacing only the oem-*.sin files from the XZ3 H8416_Customized US_1316-4522_52.0.A.8.25_R10B firmware. When you set both lines to "LTE (preferred)" and you'll be able to make LTE calls on both lines, however it may only show [HD] calling on the line you configured last I think but it'll be VoLTE on both.
Enjoy and thanks again to all the other threads that guided me through this long but worthwhile trial process. I wish the carriers didn't make LTE VoLTE provisioning difficult, why didn't they just make it universal like 3G.
Note: I was able to separately get Wifi-Calling to appear using the H8276_Freedom CA_1313-8876_52.0.A.8.25_R3B oem-*.sin files but it wasn't functional on T-Mobile USA - I think someone with a little bit more knowledge might be able to get this to work, unless you can point me in the right direction.
Someone please make an open firmware thin/light/compact dual SIM phone with Wifi-Calling/VoLTE (removable battery a bonus)!
Do you think the files would be the same on the H8314 US edition? i'm assuming you need to be rooted for this to work?
Hey Mike, Can you please share(download link) OEM*.sin files of USA firmware for Volte Settings
Im wondering if we can flash the OEM files from the US XZ1 Compact to get T-Mobile VOLTE and Wifi calling? I would try it myself but I cant find one of these phones at a reasonable price. If I do I will try and report back if anyone cares. I am glad at least VOLTE seems to work with this workaround.
VoLTE provisioned on XZ2 but calls are still made over 3G
I’ve done the same for my XZ2 (not compact, H8266). The VoLTE button is now active, but calls are still making over 3G. Any suggestion?
I just talked to a T-mobile specialist, and he confirmed that my phone should work and no need to register or do anything if it supports all bands!!! As he told me "only check for compatibility" and mine is compatible! ?
Were you ever able to get this working? New XZ2 owner and of course I bought this within a week is the announcement about all non VoLTE devices being kicked off in January..
Is there anyway to get volte working for tmobile on the h8314?
XZ2C H8314 VoLTE working on T-Mobile USA
colonelcack said:
Is there anyway to get volte working for tmobile on the h8314?
Click to expand...
Click to collapse
Yes VoLTE works but no VoWIFI with the following method:
Download USA Customized for XZ2C (H8314) and use only the two oem...sin files from XZ3 (H8416) USA Customized. (overwrite the two files in the XZ2C stack)
Use newflasher tool. (I deleted all .ta files and userdata file to avoid losing existing data)
To put the phone into flash mode, power off, hold the vol down button and plug in your usb cable while holding the button until you get a dim green light.
The device will show up in device manager under USB and you can run newflasher as administrator. Please search for a tutorial - there are many that are very good with screenshots of the files you want to move into the newflasher folder.
Some hangups I ran into when setting up and flashing -
Installing flashtool drivers required disabling driver signature enforcement on win10 (Flash device did not show up in usb in device manager until this was done)
For safety, after the flashtool driver install, I performed a repair on xperia companion app in case of any driver conflicts.
Running newflasher again, I got an error: Unable to open ./boot/Apollo_XBootConfig_MiscTA.ta! after multiple system files had been flashed.
But not to worry, the command window said the phone exited flash mode, but got error 933 - unable to sync. - No worries though, just make sure the command window states the phone is out of flash mode somewhere, disconnect your cable and power up your phone.
Then you will get an android message saying your carrier settings will update after reboot and the phone may reboot.
Once rebooted, enter *#*#4636#*#* in your phone dialer app (Takes 30 seconds after fresh boot for the menu to come up) , select phone information, and select LTE only (Note: VoLTE Provisioned will have the slider set to the right, but grayed out - Before the re-flash, the slider was set to the left and grayed out), reboot again. (If you click the 3 dots and look at IMS Status, you will see IMS status Registered, VoLTE Available and UT interface Available - Before the re-flash status was not registered and not available)
Now when you make a call, it will say "HD" in your dialer while on a call and your signal indicator will no longer say 3G when calling.
VoWIFI does not work, but you can use whatapp or something else like googleFi if its a must have, but in my case, I did not want to have to buy a new phone in January when they turn off 3G - Phones are too darn big now anyways and I love the display on this phone.
Notices will go out starting AUG 4th if your phone is marked as not supported using T-Mobile IMEI BYOD online tool - Their tool said my phone does not support VoLTE (Not fully true - It just does not have Band 71 for Long Range VoLTE but will use Band 4(66) just fine, I cannot confirm band 12 even though the phone spec supports it. It appears only Short range VoLTE is working on the phone unless someone else can confirm with this method, My Band 12 tower is behind a hill and i am 20 miles from it) T-mobile currently does not have a whitelist like AT&T, so If the UE (User Equipment - ie. phone) is configured properly, the network will handle the rest. I hope this practice does not change.
The advantage to using this method, is you are using completely stock USA files - My bootloader is locked and i am not rooted BTW. My XZ2C is only carrier unlocked.
The build number of both Roms I used was the same 52.1.A.3.49 XXX - Good Luck.
BTW - Some people were asking what modem config is working with VoLTE on T-mobile USA - to get the modem setting type *#*#7378423#*#* and in the service menu select software info, under Current modem config the value reads:
row/tmobile/vl/us
XZ1 oem files on XZ2 for VOLTE and VOWIFI calls.
nicogu said:
Im wondering if we can flash the OEM files from the US XZ1 Compact to get T-Mobile VOLTE and Wifi calling? I would try it myself but I cant find one of these phones at a reasonable price. If I do I will try and report back if anyone cares. I am glad at least VOLTE seems to work with this workaround.
Click to expand...
Click to collapse
You will need to try this. I was not so brave. The reason is the difference in the build IDs and oem.sin file names between the XZ1 (Old) and XZ2 (Current as of July USA Customized builds).
Mixing and matching files is easier when you are doing so off the same build ID. Thats why V0LTE worked on my XZ2 using XZ3 oem.sin files, they were from the same build ID and had the same names even though the sizes were slightly different.
It may work if the format of the oem.sin file did not change between the XZ1 builds and XZ2 Builds. The more different the builds, the higher the risk of something going wrong.
---------- Post added at 01:31 AM ---------- Previous post was at 01:28 AM ----------
gigili said:
I’ve done the same for my XZ2 (not compact, H8266). The VoLTE button is now active, but calls are still making over 3G. Any suggestion?
Click to expand...
Click to collapse
Enter *#*#4636#*#* in your phone dialer app, select phone information, and select LTE only - Reboot, if you cant make calls after that something else is wrong.
---------- Post added at 01:33 AM ---------- Previous post was at 01:31 AM ----------
hitemup92 said:
Were you ever able to get this working? New XZ2 owner and of course I bought this within a week is the announcement about all non VoLTE devices being kicked off in January..
Click to expand...
Click to collapse
Got this to work, no VoWIFI though - look further down the thread.
depsilon said:
Yes VoLTE works but no VoWIFI with the following method:
Download USA Customized for XZ2C (H8314) and use only the two oem...sin files from XZ3 (H8416) USA Customized. (overwrite the two files in the XZ2C stack)
Use newflasher tool. (I deleted all .ta files and userdata file to avoid losing existing data)
To put the phone into flash mode, power off, hold the vol down button and plug in your usb cable while holding the button until you get a dim green light.
The device will show up in device manager under USB and you can run newflasher as administrator. Please search for a tutorial - there are many that are very good with screenshots of the files you want to move into the newflasher folder.
Some hangups I ran into when setting up and flashing -
Installing flashtool drivers required disabling driver signature enforcement on win10 (Flash device did not show up in usb in device manager until this was done)
For safety, after the flashtool driver install, I performed a repair on xperia companion app in case of any driver conflicts.
Running newflasher again, I got an error: Unable to open ./boot/Apollo_XBootConfig_MiscTA.ta! after multiple system files had been flashed.
But not to worry, the command window said the phone exited flash mode, but got error 933 - unable to sync. - No worries though, just make sure the command window states the phone is out of flash mode somewhere, disconnect your cable and power up your phone.
Then you will get an android message saying your carrier settings will update after reboot and the phone may reboot.
Once rebooted, enter *#*#4636#*#* in your phone dialer app (Takes 30 seconds after fresh boot for the menu to come up) , select phone information, and select LTE only (Note: VoLTE Provisioned will have the slider set to the right, but grayed out - Before the re-flash, the slider was set to the left and grayed out), reboot again. (If you click the 3 dots and look at IMS Status, you will see IMS status Registered, VoLTE Available and UT interface Available - Before the re-flash status was not registered and not available)
Now when you make a call, it will say "HD" in your dialer while on a call and your signal indicator will no longer say 3G when calling.
VoWIFI does not work, but you can use whatapp or something else like googleFi if its a must have, but in my case, I did not want to have to buy a new phone in January when they turn off 3G - Phones are too darn big now anyways and I love the display on this phone.
Notices will go out starting AUG 4th if your phone is marked as not supported using T-Mobile IMEI BYOD online tool - Their tool said my phone does not support VoLTE (Not fully true - It just does not have Band 71 for Long Range VoLTE but will use Band 12 just fine) T-mobile currently does not have a whitelist like AT&T, so If the UE (User Equipment - ie. phone) is configured properly, the network will handle the rest. I hope this practice does not change.
I made the mistake of calling sony and t-mobile for support and they both kept blaming each other, the reason they don't know why VoLTE does not work on some phones is they really don't know enough about their network or the basebands in the phone or the software build process and details about android sin files - as they should not either cause if the network engineers, device manufacturers and software developers all do their job and stick to industry standard practices, it will just work anyway.
The advantage to using this method, is you are using completely stock USA files - My bootloader is locked and i am not rooted BTW. My XZ2C is only carrier unlocked.
The build number of both Roms I used was the same 52.1.A.3.49 XXX - Good Luck.
BTW - Some people were asking what modem config is working with VoLTE on T-mobile USA - to get the modem setting type *#*#7378423#*#* and in the service menu select software info, under Current modem config the value reads:
row/tmobile/vl/us
Click to expand...
Click to collapse
Thank you so much for the detailed instructions! Only one question... Where do I download these files from? And the tool? Can you link me...
Sorry it's been a long time since I've done any xda stuff
H8314 Flash tools
colonelcack said:
Thank you so much for the detailed instructions! Only one question... Where do I download these files from? And the tool? Can you link me...
Sorry it's been a long time since I've done any xda stuff
Click to expand...
Click to collapse
I dont have direct links, but here is an excellent walkthrough that calls out all the tools -
https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/
Search for flashtool on XDA there should be links for that, but you only install the drivers from it, not the tool.
You also need the xperia companion software download from sony website for any missing drivers from flashtool.
Search XDA for newflasher, thats what you will actually flash with - https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
the firmware download utility is xperifirm software - https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
depsilon said:
H8314 Flash tools
I dont have direct links, but here is an excellent walkthrough that calls out all the tools -
https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/
Search for flashtool on XDA there should be links for that, but you only install the drivers from it, not the tool.
You also need the xperia companion software download from sony website for any missing drivers from flashtool.
Search XDA for newflasher, thats what you will actually flash with - https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
the firmware download utility is xperifirm software - https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Click to expand...
Click to collapse
It's been a while but wanted to thank you for taking the time to write out these steps. I finally took a shot with the incoming shutdown of 3g for my XZ2, but unfortunately it did not work. Similar to what gigili said, while VoLTE appears to be provisioned the calls are dropping to 3g/HSPA like they originally were. After setting to "LTE Preferred" and rebooting, calls would not be made at all. I also saw "Unknown" under the Modem Config, and from what you said it should reference T-Mobile after flashing the OEM sin files.
I tried this using the latest firmware available on XperiFirm for the XZ2 (Customized US H8266 - my device is H8276) and the XZ3, which I used to grab the two OEM sin files. The firmware is 52.1.A.3.137.
Using UnSin, I unpacked both "oem_X-FLASH-CUST-B6B5.sin" files in both firmwares, and under modem-config there are a bunch of folders, and each one seems to have a conf files pointing to "mcfg_sw/generic/row/tmobile/vl/us/mcfg_sw.mbn."
I read in another thread that T-Mobile maybe has some way of blocking this workaround now, but I'm not entirely sure if that is true? Totally understand if you've moved on from the device as it's been a while, but am admittedly curious if there's a specific firmware version that this works on I could try to salvage the device.
Volte xz2/xz2 p/xz3 solved
Samir solanki said:
Volte xz2/xz2 p/xz3 solved
Click to expand...
Click to collapse
Details on exactly how?
I will create complete guide thread for the same
Samir solanki said:
I will create complete guide thread for the same
Click to expand...
Click to collapse
Thanks I'll watch for it
I am working to bring support for T-Mobile VoLTE on the xz2c to LineageOS 18.1. As of this writing, official LineageOS builds for this device do not support VoLTE unless it was already enabled and working in the stock firmware.
I have submitted some patches which may resolve the issue for TMO and probably other carriers as well. They work for me, but testing has been limited. If you are interested in using LineageOS instead of the stock ROM, and you are willing and able to build LOS yourself on linux, consider giving my patchset a try. Please read the patch description fully before attempting a build: you will need to obtain and mount some additional files first. The LineageOS wiki has additional instructions for creating a build environment.
EDIT: My patch is part of official LOS 18.1 starting with nightly 20220401. There is no need to build it yourself.
cbs228 said:
---
Click to expand...
Click to collapse
You are a saint for working on this. I bought a H8324 XZ2c recently and was super disappointed it didn't work, so I am back to my XZ1c. Super frustrated. If you ever get a pre-compiled ROM, I would love to try. In the meantime I will try to compile it myself in the coming days despite my technical illiteracy.
If that doesn't end up working, what stock firmware is available with T-Mobile VoLTE enabled and working, so I could step up from that to Lineage? Considering how old the other solutions for trying to get VoLTE working, I am hesitant to try any especially funny business of switching old firmware files from other phones around.
xperiaperson42069 said:
If that doesn't end up working, what stock firmware is available with T-Mobile VoLTE enabled and working, so I could step up from that to Lineage?
Click to expand...
Click to collapse
As far as I am aware there isn't any stock firmware that works "out of the box." The xz2c is listed as "unsupported" by t-mobile, which probably means there isn't any sort of stock ROM out there that works. Sometimes carriers do release "branded" ROMs, but there's nothing like that for this device AFAIK.
LinageOS is designed to be installed "on top" of an existing stock ROM. If you attempt to install it after you have flashed another distro (like an AOSP build), you will likely just make a brick. If you do end up bricking your device, do not despair. You can use Emma to restore your device to factory condition. Emma is available on the Sony Developer World website, and there are many guides available for it.
Hello my operator started volte only on s9 so i extracted home csc from s9 and copied customer.xml pasted to csc folder but still not working. Or we need to flash modem too? Which files are related for volte to working i want to have early before they release.for s7 Or is device related
Thanks
Bump
Don't mess with the files unless you know what you are doing ! (you obviously not).
If your operator haven't enabled VoLTE for SM-G930, there is nothing you can do, only change operator, or phone.
mooms said:
Don't mess with the files unless you know what you are doing ! (you obviously not).
If your operator haven't enabled VoLTE for SM-G930, there is nothing you can do, only change operator, or phone.
Click to expand...
Click to collapse
Lol i know what im doing im not new, and im sure is related to csc or modem but im not gona flash s9 modem lol. I just playing around with csc. Than if somsthing go wrong i restore i have HOS in acces point but not IMS
bleros said:
Lol i know what im doing im not new, and im sure is related to csc or modem but im not gona flash s9 modem lol. I just playing around with csc. Than if somsthing go wrong i restore i have HOS in acces point but not IMS
Click to expand...
Click to collapse
If i could jump in here.
Volte isn't anything to do with csc, it's dependant on the operater enabling on the network and the firmware your device is running.
If your firmware is branded by the network this is how it can be enabled for specific devices and not yours , if your firmware isn't branded then the network operator cannot disable on your device. Unbranded firmware has all call functions enabled by default including Volte.
Some network operators even link functions to IMEI, if this is the case the only option is to change the phone.
cooltt said:
If i could jump in here.
Volte isn't anything to do with csc, it's dependant on the operater enabling on the network and the firmware your device is running.
If your firmware is branded by the network this is how it can be enabled for specific devices and not yours , if your firmware isn't branded then the network operator cannot disable on your device. Unbranded firmware has all call functions enabled by default including Volte.
Some network operators even link functions to IMEI, if this is the case the only option is to change the phone.
Click to expand...
Click to collapse
I have custom rom, if volte work for s9 should work for s7 too, so how they fix it? Volte on other devices , by updating firmware of course. Is firmware related not phone . They dont have compatibility to disable for some devices the tower is for all so they cant disable band.
But i will try to fix it i wont give up :good:
Working on SM-G930FD with Mint Mobile USA
Hi there,
I thought that I would share my findings. I got volte working on G930FD. The setting comes up under Connections --> Mobile Networks --> VoLTE calls. I have tested it with calls and LTE Discovery app to make sure that I am not dropping back down to 3g/H+/etc... The calls are so much better for me. I am hard of hearing, so it really helped me. I will list how I did it below.
1. Download this firmware. https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930F/ROM/download/G930FXXS8ETC3/327944/
2. Use Odin v3.14.4 to flash BL, AP, CP, CSC ( I used CSC not HOME CSC)
3. Boot phone and enable developer mode (not sure if necessary, but this is the way I did it)
4. Reboot to download mode and flash TWRP (uncheck auto reboot)
5. Immediately after flash, reboot to recovery (Power, Volume down, Home to reboot, then Power, Volume up, Home to enter TWRP)
6. Swipe to allow modifications
7. Wipe--> Advanced Wipe --> Select Data --> Repair or Change File System --> Change File System --> EXT2 --> go back --> and then EXT 4 --> back all the way to main screen.
8. Install --> latest version of Magisk
9. Install --> CSCSelection_V3.0.0.zip https://forum.xda-developers.com/s7-edge/development/utility-flashable-csc-selection-30-t3392957
10. Aroma --> Select XXA (Multi USA) --> Select XAA (Unbranded)
11. Reboot and wait to boot (Takes a few minutes)
12. Check in Connections --> Mobile Networks --> VoLTE Calls
That's it. Good luck!!
Oh yeah, Wifi calling is in the dialer app under settings, but I have had no luck with it, even though Mint Mobile supports it.
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.
Hi,
I have SM-N986B/DS, untouched KNOX, no root, bootloader locked, OTA updates were installing automatically. CSC version was "COS" (Greece/Cosmote). I had an eSim support and it was working fine, as I was using it without any trouble simultaneously with other physical different sim cards. Suddenly I realized that I can't add credit card to Google Wallet and use it with NFC - message from Google Wallet keeps telling me that I can't add a card because my device doesn't meet the security requirements. I'm located in Poland, so I thought it can be related somehow to CSC. I decided to flash "XEO" stock ROM (Poland/not branded), I downloded it from samfw.com/firmware/SM-N986B/XEO (version N986BXXS5GWA7). I thought it wouldn't harm, as I mention, I was receiving OTA updates. After successfuly flashing rom through Odin v3.14.4, phone info shows CSC: "EUX/EUX,EUX/EUX/COS", I was able to use Google Wallet with my credit card. Next, when I was configuring my phone as usual, I realized that I can't add eSim anymore. Nor through my service provider app (Orange), nor through scanning QR code. Each time it was giving me the error message that eSim feature is not supported on this device. I went to Android Settings > Network & Internet, but I couldn't find eSim settings where they were before flashing! Settings dissapeared from my phone. Next I spent whole bunch of hours trying to figure out what kind of crap is this. I flashed COS rom succesfuly, because I was trying to revert to previous installation. Still no eSim settings. I tried all other Poland located stock roms (branded), but eSim settings still not showing. I tried UK unbranded stock rom, but still no go. Then I tried to flash stock rom from different group of roms (Brasil/ZTO) as I read somwhere that all stock roms I was trying were EU located, so the CSC may not be updating as expected. After flashing "ZTO" finally eSim settings were accessible in my phone settings and I could add an eSim and it was working, however again I can't add my credit card to Google Wallet, as it keeps saying that my phone doesn't meet the security requirements. I flashed again XEO, because if I must choose, I want to use NFC with my credit card and eSim feauture isn't that much importat for me, because phone has two nano sim slots I can use. I can tell for 100% that my phone still has untoched KNOX, no root and locked bootloader and while in download mode it shows "0" at warranty line, so as I understand, the warranty is still fine.
The questions are:
1) Can any one explain me what happened? Why there's no support for eSim in all EU located stock roms for my phone, even in the COS one?! What I did wrong?
2) Is there any chance to flash some subpackage or is there any other method that will allow me to use eSim feauture with XEO stock rom?
I can't stand how it pisses me off. Thank you in advance for any help.
Kind regards