Database Develop

Network not registering

Every once in a while I would notice, when I unlocked my phone, it would say "Emergency Calls Only" as if I didn't have a SIM card in.
Everything would still work after that such as text messages and calls, so I just figured it was a weird issue with Cyanogen 6 RC1.
Starting today, I was getting that message every single time, and also a notification that I couldn't register on T-Mobile's network.
I got on T-Mobile's live chat help, and they said there's nothing wrong with the service in my area. The person also had me tell him the SIM card number to ensure they had the right one in their system, which they did.
After this, I figured it might still be because I'm running CM RC1 so I upgraded to RC3 and I"m still having the same issue.
T-Mobile's "my account" program is no longer set up, so I don't get the notification, but I still get the emergency calls message on the lock screen.
Also, I AM connected to the T-Mobile network, but it just won't recognize my phone.
I was wondering if anyone else had any insight...

Which radio are you using? Has it done this since upgrading from stock rom?

Yes I just had this similar issue yesterday and I'm on at&t. Also, everything on my N1 is stock.
Sent from my Nexus One using Tapatalk

I had the froyo radio but then I flashed the new Korean radio and it didn't help.
I did, however, pull out the old trusty G1 to have a working phone again. But when I started it up, it reported not having a sim card. Im going to go to tombile tomorrow to get them to test it. I'll report back in case someone else has the same issue.
Sent from my Nexus One using XDA App

You might try cleaning the SIM card contacts, they might be the culprit.

I went to T-Mobile and he confirmed it was the sim card. Actually he said it was fairly common for them to go bad. No charge and I'm working 100% now. Thanks!
Sent from my Nexus One using XDA App

I have not in my life seen a dead SIM card, it was a month ago that somebody was asking around the forums what and why. I was shocked
And T-Mobile says it's common.. lol wut?

Maybe the Nexus One eats them lol
Sent from my Nexus One using XDA App

[Q] No 3G after 902 update

I had been fairly lucky with the 4G/3G switching issue with my bionic. It happened occasionally but wasn't a big deal.
Got the 902 update yesterday afternoon. Almost immediately I lost all data. Tried airplane mode, reboot, pull the battery, take the sim out, boot without sim. Sometimes one or the other of these would bring back 4 G briefly. Today I lost all data at home and did all those things plus a factory reset and still did not have data. (I live in an area that is definitely in 4G)
So I drove to the Verizon store and tech support did all the things I told them I had already done and then he discovered I had no 3G. He tried all sorts of things to get 3G to turn on but it would not. 4G would turn on when he switched from cdma only to cdma/lte. I know I used to have 3G because when I would drop 4G i would see 3G in the notifications. So I have a new bionic on the way.
Has anyone else lost 3G after the 902 update? Anyway to get it back without getting a new phone?

Just a thought, but it seems something went wrong with the radio flash. I'd try reinstalling the .902 update (download it on the web).

I noticed the radio issues as well. Apearently not all handsets are affected. Motorola received feed back on this and say their looking into this...
Thier is something wrong with the idle settings affecting 3g/4g after the update.
If your push notifications are on then you probably won't have this issue.
At least that's what I've seen.
Sent from my DROID BIONIC using xda premium

Yeah this happened to me. I lost all data. I thought I fried my Sim but after 4 hours at Verizon store and 3 Sims obviously that was not it.
I ended up flashing 893 system image, rooted and flashed a 902 update. It's finally back.
Sent from my DROID BIONIC using Tapatalk

"Mobile network not available" Trouble ... ?do I need a new phone?!

I am totaly lost as to how to proceed;
I was on Moto X 2013 stock Android 4.4 for over 10 months on a rooted (not a recent root) phone when one day, I suddenly started to get a message saying "Mobile Network not available" on attempt to make a call.
Data is working fine!
The same sim works on another phone. No other sim works on my Moto X 2013... same issue (the phone was sim unlocked)
I have tried literally everything I can think of:
1. Reinstalled stock 4.4.
2. Upgraded to 5.1 OTA
3. Set network type to WCDMA only & GSM only (as well as working through the entire list of network types)
4. Selecting my network operator + setting the network operator selection to "choose automatically"
What is going on?
Why should the problem suddenly start?
And Do I Need a New Phone??

Interesting. Check and make sure that the IMEI isn't blacklisted.
When you say that data isn't working I can't help but think that you're talking about Wi-Fi because it doesn't use a cellular network just to verify what data is working?
Sent from my XT1060 using Tapatalk

SR3TLAW said:
When you say that data isn't working I can't help but think that you're talking about Wi-Fi because it doesn't use a cellular network just to verify what data is working?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
By data, I do mean mobile data. Not WiFi. Which makes it more odd.
Also, imei is Not blacklisted.

I have the same issue and tried the same troubleshooting as you. I activated a different phone for now. Another user on the xda forum solved his issue:
Solved mine by going into the settings menu, about phone i think, and updating PRL, profile, manually activating.
Click to expand...
Click to collapse
I had a stock xt1056 running 4.4.4. I receive 'no service' and all the Sprint reps tell me the moto x uses Wimax 4g which has been rolled over to 4g LTE. Still not sure why I can't receive 3g or lower service in my area .

reso newt said:
I have the same issue and tried the same troubleshooting as you. I activated a different phone for now. Another user on the xda forum solved his issue:
I had a stock xt1056 running 4.4.4. I receive 'no service' and all the Sprint reps tell me the moto x uses Wimax 4g which has been rolled over to 4g LTE. Still not sure why I can't receive 3g or lower service in my area .
Click to expand...
Click to collapse
I am in the UK so I am not aware of the issue you highlighted on Sprint (as we do not have it here) ... my issue seems nothing to do with network - I have tried multiple sims from various network and still no luck.
Also, I do not see any setting to update PRL...

I was wondering if you made any progress with the "No mobile network available". I tried a multitude of options with no success regarding the mobile error on my phone.
I think an OTA update at the beginning of November bugged my antennae firmware....best guess I can come up with. I only made OTA updates (no OS altercations) prior to the bugged antennae update. Looks like I have to get a new phone.
Edit: I forgot to mention that the repair technician that I spoke to in early November that told me that my phone cannot connect to 4G LTE admitted he was wrong today.
nirpaudyal said:
I am in the UK so I am not aware of the issue you highlighted on Sprint (as we do not have it here) ... my issue seems nothing to do with network - I have tried multiple sims from various network and still no luck.
Also, I do not see any setting to update PRL...
Click to expand...
Click to collapse

reso newt said:
I was wondering if you made any progress with the "No mobile network available". I tried a multitude of options with no success regarding the mobile error on my phone.
I think an OTA update at the beginning of November bugged my antennae firmware....best guess I can come up with. I only made OTA updates (no OS altercations) prior to the bugged antennae update. Looks like I have to get a new phone.
Edit: I forgot to mention that the repair technician that I spoke to in early November that told me that my phone cannot connect to 4G LTE admitted he was wrong today.
Click to expand...
Click to collapse
I am not sure if you have gotten any further with this issue - I doubt it tbh.
I have actually tried a number of things and been through 100s of forums - I have learnt that this issue is not uncommon, and there is no solution at all that exists. I have given up and settled on a new phone. I use my Moto X for testing apps/wifi/music. Such wastage, but I have got to the point where investing effort of finding a solution was more costly than getting a new phone. I do not say this lightly and it is said with a lot of frustration.
If anyone if future sees this thread and has solution, I would be more than interested in hearing it - I wouldnt mind reviving this phone.
Thanks

nirpaudyal said:
I am not sure if you have gotten any further with this issue - I doubt it tbh.
I have actually tried a number of things and been through 100s of forums - I have learnt that this issue is not uncommon, and there is no solution at all that exists. I have given up and settled on a new phone. I use my Moto X for testing apps/wifi/music. Such wastage, but I have got to the point where investing effort of finding a solution was more costly than getting a new phone. I do not say this lightly and it is said with a lot of frustration.
If anyone if future sees this thread and has solution, I would be more than interested in hearing it - I wouldnt mind reviving this phone.
Thanks
Click to expand...
Click to collapse
Best of luck. Sorry to see a fallen soldier, I know how it feels!
Sent from my XT1575 using Tapatalk

SR3TLAW said:
Best of luck. Sorry to see a fallen soldier, I know how it feels!
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Thank you - I like the way you said that. Makes me feel like one of the community members ... I can see I will be supported in times of need.

Lose all service after making or receiving a call

So pretty simple I have a nexus 6 and it was originally from t mobile. It worked fine then it started saying emergency calls only it seems occur immediately after trying to make a call. Texts don't affect it but as soon as I receive a call or make one all service is lost. I'm using straight talk tmo sim and it has happened on pure nexus, 6 ROM and cr droid also du.. Straight talk shows I'm connected and only thing that fixes it is luck and wipes with reflashing a ROM. I assume its something on my device that doesn't get wiped but I'm not sure. Any tips or advice would be appreciated.

Ry4n83 said:
So pretty simple I have a nexus 6 and it was originally from t mobile. It worked fine then it started saying emergency calls only it seems occur immediately after trying to make a call. Texts don't affect it but as soon as I receive a call or make one all service is lost. I'm using straight talk tmo sim and it has happened on pure nexus, 6 ROM and cr droid also du.. Straight talk shows I'm connected and only thing that fixes it is luck and wipes with reflashing a ROM. I assume its something on my device that doesn't get wiped but I'm not sure. Any tips or advice would be appreciated.
Click to expand...
Click to collapse
Does it happen on stock?
How old is the device?
Do you have the simcard ejection tool? Have you tried reseating the simcard?
What radio are you running?

I've had it
rignfool said:
Does it happen on stock?
How old is the device?
Do you have the simcard ejection tool? Have you tried reseating the simcard?
What radio are you running?
Click to expand...
Click to collapse
I've had it two years. It was from T-Mobile site and yes and I believe its 44r I updated it back when I jumped to nougat. It does it on stock as well. I reflashed stock and it fixed it and then flashed a new ROM and it worked until I received a call. I played around a bit got it back and as soon as I called my voicemail and hung up I lost all service. I can't get it back again so I'm not sure what fixes it but I can say 100% a phone call in or out is what kills it.

Ry4n83 said:
I've had it two years. It was from T-Mobile site and yes and I believe its 44r I updated it back when I jumped to nougat. It does it on stock as well. I reflashed stock and it fixed it and then flashed a new ROM and it worked until I received a call. I played around a bit got it back and as soon as I called my voicemail and hung up I lost all service. I can't get it back again so I'm not sure what fixes it but I can say 100% a phone call in or out is what kills it.
Click to expand...
Click to collapse
In the development section there is a thread about radios...
Grab the baseband cache eraser... Or reflash your radio... I bet you have junk causing your issue in there...
And format your cache partition for poop and giggles when you do the radio thing

rignfool said:
In the development section there is a thread about radios...
Grab the baseband cache eraser... Or reflash your radio... I bet you have junk causing your issue in there...
And format your cache partition for poop and giggles when you do the radio thing
Click to expand...
Click to collapse
Just tried to no avail. If you have another theory maybe how straight talk switches from 4g to 2g or 3g for voice differently maybe its a build prop or some conflict. Otherwise I will just request a new sim maybe its an issue on there end.

Just wanted to update in case others struggle, I had a pack of 3 straight talk sims so I went online and transfered the number and service to my att sim and it fixed the problem either it was a sim issue or straight talk tmo problem or flashing a ROM or weekly jacks up something but either way I'd like to know because the Verizon sim never worked right it was the first one I tried hoping for more coverage in dead tmo spots. I will keep a look out in case someone has experienced this or has another idea. For now its working well with att sim

I didn't realize you had made a separate thread about this, as you mentioned your issues in the Pure Nexus thread. But now that I saw this thread I can utter those four immortal words no one likes to hear.
"I told you so."
In all seriousness, it's good to know that you got the issue resolved.

Nexus 6, T-Mobile and MMS problem

This has been a frustrating issue. My wife and I both have Nexus 6 phones. She has the 32gb & I have the 64gb version. Hers recently started not receiving MMS messages. Anything with a large picture would simply never show up. Anything with a very small graphic or group text would show up as "Non-text content". Here are the steps we've taken to solve this:
1. TMO started by insisting it was an APN issue. So she edited her APN. Didn't help.
2. We then swapped SIMs. Hmmmm. My phone then behaved like hers while hers could then send/receive MMS.
3. TMO said ok maybe it's the SIM. They sent us a new one. SAME result. Her phone wouldn't receive MMS.
4. Out of frustration, I factory reset her phone and reset the APN info. Didn't help. (Cleaned up her phone of some trash programs though. :laugh
5. TMO engineering says they still can't find anything on their end. Elevate to tech supervisor. She tells us to go a TMO store (right near us) to try a THIRD SIM. OK, we do. SAME RESULT. We tried swapping SIMs around again and the same thing happens. My SIM in her phone, everything works. Her SIM in mine, I can't receive MMS.
6. TMO store guy suggests MAYBE (but unlikely) that there is something her account has that's stored on the SIM when its activated that causes the phone to freak. Also says it's above his pay grade .
So now we are again waiting on TMO to poke around further on their end. My question for all you smart types here is:
Has anyone ever heard of this issue? Is there anything you know of that could be causing it? I think it's a bad provisioning somewhere in the dark recesses of TMO. The ONLY change we made to our plans (which seems just coincidental) is that we moved from the 2 lines Unlimited for $100 plan to the over-55 Unlimited plan. We did this maybe 3 weeks ago. But the features are all the same on both plans.
We are both on the same Android 7.0 final OTA firmware updates from Google. NBD92G
Would there be ANY chance that a sideload firmware update would make any difference? We're getting desperate here. Any & all suggestions welcome.

I wonder if her SIM is configured for wifi calling. There has been a conflict between wifi calling and mms for awhile. I've seen it reported several times where this T-Mobile forum post helps in that case

Don't use old firmware... I had issues on certain custom ROMs and old firmware where MMS wouldn't work over WiFi. Never as bad as you were getting.
If you wanna stay stock, sideload the latest OTA to go to NGI55D. Anything older than that is vulnerable to Blueborne exploit, which is a HUGE security concern IMO. I can confirm MMS is working correctly (even with WiFi enabled) on bone stock NGI55D as well as custom ROM Dirty Unicorns v11.7.1 which includes September security patch.

ktmom said:
I wonder if her SIM is configured for wifi calling. There has been a conflict between wifi calling and mms for awhile. I've seen it reported several times where this T-Mobile forum post helps in that case
Click to expand...
Click to collapse
I've had this issue on most LOS roms. i ended up making a custom APN i flash when i try a rom built on LOS.

Yeah, it sure sounds like a problem with account partitioning, or something else with the account that gets associated with the SIM on initial use. What if you try the problem SIM in a phone that is not a Nexus 6? I wonder if you could get a new sim and set it up in a different phone, then transfer it to the problem phone?

OK all, finally got a TMO engineer who agreed with my assessment -- that it was a hidden provisioning problem. She nuked my wife's line and recreated it from scratch. Everything works great now. Frustrating that we had to go through about 15 phone calls and over 3 hours of phone time to get it resolved.

RealSkier said:
OK all, finally got a TMO engineer who agreed with my assessment -- that it was a hidden provisioning problem. She nuked my wife's line and recreated it from scratch. Everything works great now. Frustrating that we had to go through about 15 phone calls and over 3 hours of phone time to get it resolved.
Click to expand...
Click to collapse
Glad they figured this out.