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
Related
I have gotten this message 3 times in the last 5 days. Each time I need to do a reboot to restore cellular/sms service (toggling airplane, wifi, bluetooth, sync, and 4g do not restore cellular/sms). The phone has the same AT&T sim card since day 1 and I have never removed it.
Is this a faulty phone, sim card or both?
gtabfish said:
I have gotten this message 3 times in the last 5 days. Each time I need to do a reboot to restore cellular/sms service (toggling airplane, wifi, bluetooth, sync, and 4g do not restore cellular/sms). The phone has the same AT&T sim card since day 1 and I have never removed it.
Is this a faulty phone, sim card or both?
Click to expand...
Click to collapse
Did the sim come with the phone? ATRIX 2 needs newest of sim cards to function properly. If that's not the problem then I'm not to sure.
Sent from my MB865 using XDA App
Yes, same sim card that came with phone.
Could be a faulty Sim, i've had that happen before with other phones, just go to at &t and show them the problem, they should replace it for you!
Sent from my MZ617 using Tapatalk
(Hope you understand my english)
I wasn't able to solve this problem about an year. But did. And totally sure that it is Device's defect (in some cases it is a ROM deffect as in my case, in other - hardware. Smth like stack overflow issues at GSM controller or so). A year ago when I had face this "sim card does not allow connection... " problem, there are no google serch results on this keywords request. Any. To remove this message I was ought to reboot my device every time it appears. And I was thinking that it is normal behaviour for my device. But now there are lot of complainings at the web ( minimum 5 of Galaxy Tabs P1000, thousands of HTC Disire, few motorolla Deffy, 10 Galaxy Ace, few of Nexus S and so on), so I understand that I'm not alone, and problem is known. So I went to Samsungs Service and they confirmed that it is famous problem, have flashed my phone with some magic ROM (magic because it is official but does not available anywhere in the web, XDA or samsung sites! ) and now my phone works fine. Any other solutions like battery removing, *#*#4636#*#* sirvice menu, new sim-card, flashing variety of modems and roms, didn't helps me. This is not faulty sim. This is serious device's defect. Bring your phone to manufacturer and let them repair it or give your money back. This is their problem not your.
using old 3g prior sim card
With ATT---If you took your old 3g sim card out of old phone and used it. You will get this message. You need to activate the 4g card that came with phone
537magspc said:
With ATT---If you took your old 3g sim card out of old phone and used it. You will get this message. You need to activate the 4g card that came with phone
Click to expand...
Click to collapse
Not true.I'm using my old 3g sim with zero issues.
Sent from my MB865 using XDA
Same issue in Mumbai India
CS4 said:
(Hope you understand my english)
I wasn't able to solve this problem about an year. But did. And totally sure that it is Device's defect (in some cases it is a ROM deffect as in my case, in other - hardware. Smth like stack overflow issues at GSM controller or so). A year ago when I had face this "sim card does not allow connection... " problem, there are no google serch results on this keywords request. Any. To remove this message I was ought to reboot my device every time it appears. And I was thinking that it is normal behaviour for my device. But now there are lot of complainings at the web ( minimum 5 of Galaxy Tabs P1000, thousands of HTC Disire, few motorolla Deffy, 10 Galaxy Ace, few of Nexus S and so on), so I understand that I'm not alone, and problem is known. So I went to Samsungs Service and they confirmed that it is famous problem, have flashed my phone with some magic ROM (magic because it is official but does not available anywhere in the web, XDA or samsung sites! ) and now my phone works fine. Any other solutions like battery removing, *#*#4636#*#* sirvice menu, new sim-card, flashing variety of modems and roms, didn't helps me. This is not faulty sim. This is serious device's defect. Bring your phone to manufacturer and let them repair it or give your money back. This is their problem not your.
Click to expand...
Click to collapse
I have exactly the same issue randomly at times when I try to register on network manually (MTNL Dolphin 3G - Mumbai). Unrooted MB865 ver 2.3.6 & updated on 18th May 2012 to System Ver 55.28.37.MB865.AsiaRetail.en03. If I keep the setting as Automatic in Type of Network & Operator it functions fine fluctuating between Dolphin for local access & CellOne on roaming access in the same area based on cell tower connection the phone registers on alternating between "E" & "H" automatically based on cell mast direction proximity, however if I select 3G only and uncheck automatic for operator then the phone searches for signal for a very long time and fails to show any operator saying "no connection available" & sometimes when "Dolphin" network does appear and try to select manually get the error as "this sim card does not allow connection to this network". I did complain with the service provider and they were supposed to get back to me after checking in their switchboard exchange where I also provided them my SIM number in addition to my cellphone number(no response). Also as is case with poor service of all Indian cell network providers even in urban cities, also face random peculiar issue of call not being received inspite of signal available on the phone & network asking me to recheck the number I have dialled while placing outgoing calls though it is ok and signal is sufficient. Also "Network Speed Booster" app looks like a lot of bull (any other good apps??)
I needed to know using the secret Menu *#*#4636#*#* for 3G GSM service which kind of network I should ideally select for best results & does this setting override the regular menu network settings??
I get "G", "E", "H" randomly based on my locations but no "3G" or "H+" and further at times these icons are grey and sometimes blue and in either cases randomly at different locations sometimes data throughput is not there as only one of the arrow shows active blinking. Any advise on the status based on colors and the blinking of the arrows?? Thanks!
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.
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.
Hi folks,
This is my first post on here. I'm having a problem with my phone which I think is quite unique and I hope someone on here can help me fix it before I buy a new device.
I have a galaxy nexus (maguro) running cyaogenmod.
Previously I was running CM11 (cm-11-20141115-SNAPSHOT-M12-maguro) from the CM website and updated it to CM12.1 cm-12.1-20160719-SNAPSHOT-YOG7DAO8DL-maguro) a few weeks ago.
When I rebooted my phone it was running very slow (and getting very warm) so I did a factory reset and re-installed CM12.1.
It started working ok but I noticed that my phone was displaying 'emergency calls only' even though the network reception in the status bar was full, displaying 'H' (3g) and allowing me to connect to the internet using 3G.
Whenever I make a call it states 'Mobile network not available' and I cannot send text messages.
I tried phoning O2 and they gave me a new sim but the problem was still happening. I then tried putting my girlfriend's EE sim into the phone and I could make calls/send messages. I also went to France on holiday and could use my phone to phone/text using my O2 sim abroad. Whenever I put my O2 sim into another phone I can make calls and text.
So basically it is only when my O2 sim is specifically in the Galaxy Nexus that I cannot make calls/send texts but can still use 3g.
Oh yeah when I go to Settings>Mobile Network Settings>Network Operators the following available networks are shown:
O2-UK
T-Mobile UK
3 UK
vodafone UK
Orange
When I select O2-UK is states 'cannot connect at this time. Please try again later'
I've tried re-installing the older version of CM11 and today I tried wiping the entire phone (internal sd card etc) and it is still happening. Can anyone help? Is there something else I can wipe, or setting I can change?
Thanks in advance
The basic problem is as follows:
I've got a Nexus 6p on which I dirty flashed an 8.1 update (27 Feb 2018) of ABC Rom over an earlier 8.1 version (01 Jan 2018) of ABC Rom. After that, the issues began. At boot, I'd be on 3g and if I toggled airplane mode off and then on, I could get LTE for about 10 seconds. However, it would then drop back to 3g. It's probably worth noting that my cellular provider is Verizon.
I tried everything that I could think of and/or learn via the google. Such as:
Wipe system, data, cache, and dalvic
Revert to stock
Install different/older radio images
Changed SIM (although still Verizon)
... nothing worked. I've read about people manually configuring their APNs. However, I've got a Verizon SIM, so that option does not exist... as far as I can tell.
I've identified a crappy work-around that allows me to get a stable LTE connection as follows:
Open the Phone's Testing Settings by dialing: *#*#4636#*#*
Tap "Phone Information"
Scroll down and set the "VoLTE Provisioned" toggle to the "on" position.
Then, toggle airplane mode on and off.
However, the reason I've described this as crappy is that doing this results in my phone being unable to make or receive calls. Whenever I try to make a call with VoLTE Provisioned, the call fails and reports "Server Error". Consequently, I generally just deal with the phone working in 3G. On the up side, this work-around does demonstrate that LTE is still possible... with the right configuration. Although, it would be nice if I could get both LTE and phone working vs just one or the other.
I came across this post suggesting that a possible solution is to boot the phone up with a non-Verizon SIM, power it off, and then boot it up again with the Verizon SIM. I'm not sure how this fixes the issue. However, before I go buy a $30 SIM in the hopes that it will fix my issue, I figured I'd make this post and see if anyone has any other ideas how I might correct this.
Any ideas are appreciated.
[email protected]
So after a few months of using 3g, I got my hands on brand new AT&T SIM card. (For what it's worth, it hadn't even been provisioned yet). I went ahead and boot the phone with this new sim card. (I also reset the new APN settings to the default, although it probably didn't do much). After powering the phone down and putting the Verizon Sim back in, I've got my LTE back and all is good.