GSM / Network Signal grey out - Samsung Galaxy S8+ Questions & Answers

Hey all, thanks in advance for any advice offered.
For some reason my GS8+ has a greyed out GSM signal bar with an 'x' next to it. As far as I remember the only thing I did was put it to charge overnight. I've tried removing the SIM, still grey, inserting another carrier's SIM (known to be working), still grey, my original SIM also works fine in another phone. Everything else not related to cell service works fine (wifi, bluetooth etc.). I can see the IMEI number in settings as usual.
I've tried resetting the network settings, factory resetting the phone, I've even reloaded the ROM via Odin. No joy.
The phone is pretty much stock, except for the fact that I changed the carrier software from AT&T to Verizon in order to use a particular LTE band. Since I did that, the phone worked fine for several months.
I've only noticed two things odd thus far. After reloading the ROM and downloading a few updates, a game (Empire) appeared from nowhere installed in my app drawer. Also, the Airplane mode icon in the notification shade is light blue, similar to when it's transitioning from off to on. Airplane mode seems to work though, because I can toggle it, and the wifi reacts as such.
I can't search network operators manually (says: Error while searching for networks), changing the network mode does nothing, and none of the secret dialing codes work either. They all say "Mobile network not available". With a SIM inserted, my SIM status menu says, Network: unknown, Signal strength: -113dBm 0 asu, Service state: Radio off.
Sorry if I'm long-winded, but I'd appreciate any assistance at all. Thanks again for taking the time to read.

Hey, I'm having the same problem. Did you find a fix?

Nope.

I had a same issue after I update girlfriend's s7 . The ROM (custom one) was based on newer version but the firmware and BL were old.
I know and I understand that you just put it to charge overnight but you can give a try to flash latest firmware CRED one.
Allso is mandatory to chose the correct country and carrier. Chose the country where you are and Verzion carrier

I have same issue tried flashing other roms. All didn't work

Related

Nexus S roaming problem with ICS

Hi,
I have a Nexus S I9023 with baseband I9023XXKI1
Provider is Telenet in Belgium, which is a full MVNO with its own MNC
When running any Gingerbread version, the phone works fine when going out of the country, and returning.
But with any ICS rom (stock or CyanogenMod) the phone will not be able to connect to any international providers, when my providers SIM is installed. But when I stick my providers SIM into another phone the SIM will switch over, after which I can put it back into my Nexus S and I can roam to any other international provider without problems, but the phone will not switch back to my own provider when I get back into the country. At this point I again have to put the Telenet SIM into another phone to force it out of roaming mode after which I can put it back into my Nexus S and it works again on my own provider.
I also tried with another Telenet SIM and had the exact same problem, so it is not a problem with the specific SIM itself. But when I stick in a non-Telenet SIM it does switch to roaming and non-roaming without problems. So it clearly is a combination of the ICS ROM with the Telenet SIM.
The only other thing I found is that the MNC code in apns-conf.xml is wrong for Telenet. It is listed as MNC=10 which used to be correct until sometime last year when everyone was issued a new SIM with MNC=05. But with a custom APN setup mobile data works fine.
If anyone has any idea how I could solve this issue, I would love to hear about it!
Cant Activate/Deactivate International Call Roaming on Nexus S.
Hi,
Same issue here, mine is Nexus S, running ICS 4.0.4, baseband version I9020XXKI1. I am not able to make calls in roaming. I spoke to my provider (O2 Germany) and they say that, I have to deactivate the lock (Lock to activate roaming). I haven't found any way to unlock this service. I have not tried what the OP has mentioned in his post (i.e., to put the sim into another phone and then try back in Nexus S). But I would like to know, how can I Activate or Deactivate the roaming lock ??
Thanks,
Cheers!!
esunny said:
Hi,
Same issue here, mine is Nexus S, running ICS 4.0.4, baseband version I9020XXKI1. I am not able to make calls in roaming. I spoke to my provider (O2 Germany) and they say that, I have to deactivate the lock (Lock to activate roaming). I haven't found any way to unlock this service. I have not tried what the OP has mentioned in his post (i.e., to put the sim into another phone and then try back in Nexus S). But I would like to know, how can I Activate or Deactivate the roaming lock ??
Thanks,
Cheers!!
Click to expand...
Click to collapse
The only roaming feature you can enable is for Data. This has no effect on roaming for normal phone usage.
You can change this setting under "System Settings" -> "More..." (under Wireless & Networks) -> "Mobile Networks"
Here you will find a "Data roaming" option, and possibly a "National data roaming" option
I have a Desire Z with Android 4.0.4 and Telenet for the cellphone also. I noticed I have to activate the romaing in Belgium to have the data connection which is strange as I'm in Belgium. Now I hear that they can be issues calling/sending sms abroad... I'll see when I'll be in Croatia.
I activated for the moment all the option (data roaming, national roaming) for the moment, nothing more strange than having the romaing activated and the 'R' in the network signal.
National Roaming seems to be needed on some phones, since the Telenet SIM swap last year to get a data connection in Belgium. On my own Nexus S phone I don't have the problem. But on my wife's SE Xperia Mini Pro (2011 model) with stock Android 2.3.4 it does have this issue.
The old sim used MNC=10, while the new SIM uses MNC=05 and it seems that some phones have some kind of issue with that.
MNC is the Mobile Network Code, which together with the MCC (Mobile Country Code) forms a identifier per provider.
http://en.wikipedia.org/wiki/Mobile_Network_Code
I narrowed down the issue somewhat.
Basically my prior workaround that the SIM needed to be swapped to another phone to force the network to connect was false.
What actually needs to happen to force the phone to enter or exit roaming is to pull the battery.
Rebooting the phone, or shutting it down and rebooting (cold boot) does not make a difference, the battery needs to be pulled and then the phone will switch networks.
I found this by accident, because I was out of the country and it was as normal refusing to switch to roaming mode. Then the battery died and I connected power to the phone and booted it, and it suddenly connected to a foreign provider in roaming mode.
Getting back to Belgium, it again refused to switch back, so I verified it by just pulling out the battery and putting it back and the phone successfully was able to connect to Telenet again.
In other words, some component needs to be reset for it to successfully switch to roaming and back. This component does not get turned off when the phone is turned off, so the battery needs to be pulled.

Help request: LTE Data works,"no service" otherwise. IMEI/number, but no texts/calls.

Help request: LTE Data works,"no service" otherwise. IMEI/number, but no texts/calls.
Software: Android 5.0.1 Skydragon M8 v2.0 Sense 7
Many people have posted issues with LTE where their cellular signal was fine for "2G" functions like calls and texts.
I'm having the opposite problem. After leaving airplane mode (landing at an airport today), I have a "No Service" message in the status bar drop down (notification tray), and the Settings>Network information page shows "Not Registered." However, I do have an IMEI (see details below). However, LTE data works perfectly fine.
I've obviously tried changing the settings in Settings>Mobile Data (preferred network to Global / LTE / LTE/legacy 3GPP mode) connection type global/auto/LTE/etc), to no avail. If LTE is connected it works flawlessly, but I cannot make calls or texts, and show not registered on the network. Data roaming is set to deny, but even allowing roaming does not change the situation.
Before this happened, I HAD gone through all the XTended Settings, and even 'looked' at (but did NOT change) some advanced settings pages, including the 'hidden' HTC network info page ( *#*#4636#*#* ). Again, however, I didn't change anything -- unless by accident?!
Does this sound familiar to anyone? Anyone know if I may have inadvertently changed something and can change it back (a setting that would persist in the hardware through NANDROID restores and factory resets...). Or, any other advice to restore the cellular service connection to normal?
I've tried a full NANDROID restore (multiple times) to a working copy, and a factory reset. I have limited access to a PC since I'm traveling, so re-flashing the VZW firmware or stock recovery or lollipop/verizon RUU would be challenging.
I did spend a good 45 minutes (at a library, my only PC access!) searching the forums and web, but to no avail.
Settings information:
OPperator Name: Verizon
Signal Strength -114 (I've had better but still have the same issues)
Mobile Network type: LTE
Service state: In service
IMS service state: Not Registered
Roaming: Not Roaming
Phone Identity page:
IMEI shows up (15-digit number...how can I verify I didn't mess this up?)
Phone Number is correct
IP Address: 100.66..... (looks good)
Any help is GREATLY appreciated!
Same here
I'm having the same issue. When i try to make a call my LTE bars drop to nothing and it says call failed no network available. Any ideas or help would be nice. I was using venom rom as well. I'm currently trying to flash the newest RRU to see if that resets things. I'm wondering if it somehow my sim card. I took it from my droid turbo. I've made sure to turn off advanced calling on my VZW account though.
Drhoot said:
I'm having the same issue. When i try to make a call my LTE bars drop to nothing and it says call failed no network available. Any ideas or help would be nice. I was using venom rom as well. I'm currently trying to flash the newest RRU to see if that resets things. I'm wondering if it somehow my sim card. I took it from my droid turbo. I've made sure to turn off advanced calling on my VZW account though.
Click to expand...
Click to collapse
I had this same issue, running from ruu then rooted. I didn't noticed until I started seeing voice mail notifications but never heard the phone ring. When I tried to dial out I got the immediate call lost message. I couldn't figure what was causing it so I just did a reset. I made sure not to restore any systems data from prior to the Lollipop upgrade. At this point everything is working, the only thing I haven't installed yet is the xposed framework and sense 6 toolbox.
mc_365 said:
I had this same issue, running from ruu then rooted. I didn't noticed until I started seeing voice mail notifications but never heard the phone ring. When I tried to dial out I got the immediate call lost message. I couldn't figure what was causing it so I just did a reset. I made sure not to restore any systems data from prior to the Lollipop upgrade. At this point everything is working, the only thing I haven't installed yet is the xposed framework and sense 6 toolbox.
Click to expand...
Click to collapse
What kind of reset did you do? I know my issue is slightly different, but I did a full RUU-flash yesterday (latest lollipop version) and still no luck. Unfortunately I'm out of the country now and access to a computer is limited, and I don't even have a SIM card yet to check if cellular service would work anyway.
I do intend to do a flash of the stock recovery and radios once I have the time and access, but that may be a while...
Still, I'll keep checking this thread to see if anyone posts any other options
lifebringer123 said:
What kind of reset did you do? I know my issue is slightly different, but I did a full RUU-flash yesterday (latest lollipop version) and still no luck. Unfortunately I'm out of the country now and access to a computer is limited, and I don't even have a SIM card yet to check if cellular service would work anyway.
I do intend to do a flash of the stock recovery and radios once I have the time and access, but that may be a while...
Still, I'll keep checking this thread to see if anyone posts any other options
Click to expand...
Click to collapse
Just go into settings and to Backup & Reset , this will return your phone to a fresh install and remove all non bundled apps.
Before doing the reset try going into Settings then Call then change Preferred Network to Global, or toggle from LTE then back to Global.

[Q] LG Nexus 5 fails to recognize celullar network

Hello,
I have a Nexus 5 phone that came with Kitkat a few months back. The phone worked without issues until I decided to update to Lollipop 5.0 (OTA update) at the end of November. Initially the phone started to have troubles to detect the network at certain times - typically "playing" with the settings "Preferred network type" by changing from 4G to 2G, restarting, letting the phone detect the network on 2G mode and change back to 3G or 4G would fix the problem. The issue became more and more frequent until a point where i can not change the "Preferred network type" from 4G to any other type (as if it is "glued" on that setting). At this point my phone does not recognize at all the cellular network but It does seem to recognize the SIM card since i need to enter the 4 digit code to unlock SIM and it displays the network name, just no service.
I've researched the internet and I've tried several things but nothing seems to fix it such as restart mobile, change to airplane mode and back, take out and re-insert SIM card, request new SIM card from operator. The APN settings seem to be OK.
I've noticed that a new 5.1 version just came out and although I was not fully familiar with the process i decided to give it a try (after reading several instructions) and update manually (using factory images posted) and see if that would fix it. The phone is now with version 5.1 and still can't recognize the cellular network - no service. Everything else works fine, including Wi-Fi.
Has anyone experienced such issue after OTA update? The only odd thing I can think of is that I did the initial OTA update to 5.0 in US while i was on travel from Europe, but I can't say if this would in some way contribute to the issue. The mobile is D821 model.
Since I was stuck and mobile is within warranty period, I have sent it to service repair. I would be interested to know ideas of what could be the issue cause.
Sorry for long message, any help would be very much appreciated.
Pedro

sim tray and network not working properly

a few days ago I switched from cm to AEX 7.1.2 on my moto g. Whether that has anything to do with it I don't know.
Anyway last night the phone was working fine then this morning I see that the cell network is disconnected and the phone doesn't see the simcard. However when I put in another simcard from a different network it works normally. I switch back to my sim and it works for about 20 seconds where I can make a call or text then it shuts down again and dowsn't recognize the sim then does again once I have switched the sims but only for 20 seconds. I don't understand what is happening to the phone and why it is doing this. I need help. I have tried picking different network modes from the list after inserting this code #*#*4636#*#* nothing has worked so far. I haven't systematically gone through each one at a time yet and the list is quite long. I haven't seen a list of modes that long before there are over 10 of them from auto prl to scdma etc... Some of them I have never heard of like the scdma one. wif and bluetooth are working ok if that means anything. Thanks for any help
Also when I go into settings the network section is greyed out and under prefered network type it says Invalid Network Mode (-1) Ignore. I only tried changing the modes when this problem arose my changing these modes was not the cause
i've had similar issues, when i skipped using mobile data for a long time, my non-data SIM would dropout intermittently. i changed SIM slots didn't solve it either. other SIM was fine in either slot. just before replacing what i thought was a faulty SIM, without turning mobile data on, i just set the problematic SIM for data. that solved mys issue. however, running mobile data on back on the original setting didnt cause any more issues either.

GSM / Network Signal bars grey / unavailable

Hey all, thanks in advance for any advice offered.
For some reason my Galaxy S8+ has a greyed out GSM signal bar with an 'x' next to it. As far as I remember the only thing I did was put it to charge overnight. I've tried removing the SIM, still grey, inserting another carrier's SIM (known to be working), still grey, my original SIM also works fine in another phone. Everything else not related to cell service works fine (wifi, bluetooth etc.). I can see the IMEI number in settings as usual.
I've tried resetting the network settings, factory resetting the phone, I've even reloaded the ROM via Odin. No joy.
The phone is pretty much stock, except for the fact that I changed the carrier software from AT&T to Verizon in order to use a particular LTE band. Since I did that, the phone worked fine for several months.
I've only noticed two things odd thus far. After reloading the ROM and downloading a few updates, a game (Empire) appeared from nowhere installed in my app drawer. Also, the Airplane mode icon in the notification shade is light blue, similar to when it's transitioning from off to on. Airplane mode seems to work though, because I can toggle it, and the wifi reacts as such.
I can't search network operators manually (says: Error while searching for networks), changing the network mode does nothing, and none of the secret dialing codes work either. They all say "Mobile network not available". With a SIM inserted, my SIM status menu says, Network: unknown, Signal strength: -113dBm 0 asu, Service state: Radio off.
Sorry if I'm long-winded, but I'd appreciate any assistance at all. Thanks again for taking the time to read.
I had the same issue and I replaced the daughterboard and antennas

Categories

Resources