Google Fi, Android Pie, and Invalid SIM - Moto X4 Questions & Answers

Been experiencing "invalid SIM" error messages on Google Fi after the Pie update. It seems to happen when trying to connect to Sprint. I've tried removing the SIM, reactivating, factory reset. Nothing works.
Anyone else having this problem? It's happening on both my X4 A-1 and my wife's X4 A-1.

Happened to me. Thought I scratched my SIM when adding an sd card to the phone after upgrading to Pie. I contacted Fi and was sent a new SIM which hasn't fixed the issue. Factory reset and reflashing the upgrade didn't do anything.

Same here, my normal use is sprint...startup of sim is configuration of sprit dm... Get sim icon then searching in cell triangle. Signal info App data shows correct sim data for Sprint tower. After twice would access cell site but never got data connection or cell phone even though signal info app would show connected. Then fail, tried to access us cellular but complete sim failure. Removed sim returned to my "daily" Pixel working normally. I guess a push update in the future for us Fi base...have read this happening on first devices that went to Pie way back in August..... Our great android ONE .....

Different waters, same boat
I'm having the exact same issue. Wish I would have waited to take the update.

Same problem here. Restart doesn't help...tried all suggestions on the web using repair codes...only thing left to try is factory reset but have read that doesn't fix it(anybody here tried?).
Sent from my SM-T350 using Tapatalk

Google is aware of this problem and said they're working on a fix.

dgt02 said:
Google is aware of this problem and said they're working on a fix.
Click to expand...
Click to collapse
In troubleshooting I am now getting the same error using my Moto X4 Amazon prime version on 8.1. I was playing around with the various repair codes to understand how they would react compared to my wifes Moto X4 Android One 9.0. I started to get invalid sim error after repairing on Sprint. Now I get the same errors on both 8.1 and 9.0 (invalid sim switching to Sprint). Looks like the problem is a little deeper and more complex than just the Pie upgrade.
At least both still work on Tmobile (the strongest carrier locally). Anxiously awaiting a fix.

A friend at work told me today he saw the invalid sim message and he is a regular Sprint customer so I agree this seems to be a Sprint issue.

It's not just X4A1 models. Regular X4 also. However, my X4A1 was purchased from Google. Quite a disappointing intro to Fi.

I bought 3 Moto X4s for my wife & kids directly from Google Fi. Kids are on Oreo & the wife is on Pie. All 3 phones get the dreaded Invalid SIM error when switching to Sprint. Now, every now and then, I can force connect to an "Unknown Carrier" with Mobile Network Code (MNC) 310-000 (Sprint is 310-120 & T-Mobile is 310-260). When connected to MNC 310-000, I got speeds of up to 74Mbps (I triple checked that wifi was off!). I believe that Sprint is doing network upgrades & for some reason the Moto X4 phones can connect to their test network but not their live network. Anyone else have any insights?

My Fi Moto X4 is Pie same thing. I also have US Cellular in this area and I can if Forced, connect to US Cell but oddly will always revert to T-Mobile. T-Mobile is zero most of the time but will never just try the other two in my coverage area. On Sprint will sim lock, which in the end is which of course locks it up.
I have 2 Pixels (first) Nov, Dec google factory images when were released I found same thing, but a 50-50 to get Sprint to show sprint dm services and complete....registering to specific tower coverage+sim + imei? When working on Sprint would always switch to T-Mobile. Now in the good old days would never go to T-Mobile, Sprint was preferred, then US Cellular, then if found any signal T-Mobile. Jan Images work so far with NO SIM LOCK. I can on my Pixel use a radio.img from Oct 18 and will work like the past on Dec images. So........waiting for "monthly" two months later updates, I guess.

Related

Verizon Moto X Sim card from unknown source

So I sold my Moto X on swappa and had some issues with the buyer activating the phone. They kept getting a message that said "Sim card from unknown source" with a Verizon sim. I know this happens with sims from other carriers but not from Verizon sims. The phone has a clear IMEI and the account is paid and clear. I recently switched to tmo and thought the porting process was initially the problem. Could it be there is some other hold up on Verizon's end that is preventing the phone from being activated with another account? The phone was working perfectly prior to sending it off and I switched about a day ahead of mailing it out. I don't have access to a verizon nano sim (or account) anymore to test the phone either.
Currently running 4.4 rooted with WP disabled using jcase's method for root and WPNOMORE. Its factory other than that though. I didn't add any user data prior to mailing out and it remains that way. The whole situation has me stumped on what's going on. Do you guys think using RSDlite to go back to a stock 4.4 or 4.2.2 to reroot will fix the issue? I do have access to an ATT nano sim (buddy has a motox) but I don't know anyone with a nano sim from verizon to test the phone. Any help would be great because I'm basically sitting on this phone and have zero use for it.
A new buyer will need to take it to Verizon to get a new SIM. Verizon will do this for free. Even though it seems trivial, they won't put the new SIM onto another account.
Based on my experience with buying a Moto X via Swappa.
Buyer said they tried several new sims and it still had the error. I'm going to see if I can test with my friends iphone5 sim and see if there are any issues. Otherwise I guess no choice but to rsd back to stock or something. Maybe reflash radios.

[Q] Voice: Out of service / Data: In service HELP!

I have lurked so much around XDA and still I have no solution
I own a Moto X XT1053 on Movistar (Mexico)
Everything was working fine until I got my SIM card replaced. Now Voice and SMS don't seem to function but Data from my carrier works fine.
When I try to dial I get a "Mobile network not available"
I have done "fastboot oem config carrier (all possible options) No luck.
I have switched from 4G to Edge since that seems to be the solution for many but that didn't work for me.
Yes I have searched for networks and selected "Choose Automatically" No luck.
I have flashed back to stock firmware using T-Mobile's firmware (which has always been my solution and everything worked flawlessly) but now that doesn't work. I've actually not a fan of custom roms I only do stock and xposed the [email protected]#$! out of it but even a clean stock doesn't seem to fix it.
I even went to Movistar and they believe its my phone since they tested my sim on another phone and voice worked on theirs.
Any thoughts on what could be the solution? Please Help!
Check the APNs?
Alecegonce101 said:
Everything was working fine until I got my SIM card replaced....
....they tested my sim on another phone and voice worked on theirs.
Click to expand...
Click to collapse
I think your first statement supersedes your latter statement and everything in between. Just because your new SIM worked properly in another phone doesn't mean it's guaranteed to work in your moto x. Maybe for some reason your moto x is reading the sim as a data only Sim, or maybe it's registering on the network as a data only Sim.
did you cut the Sim to nano or did it come as nano?
Did you try a different SIM in your Moto X?
dtg7 said:
I think your first statement supersedes your latter statement and everything in between. Just because your new SIM worked properly in another phone doesn't mean it's guaranteed to work in your moto x. Maybe for some reason your moto x is reading the sim as a data only Sim, or maybe it's registering on the network as a data only Sim.
did you cut the Sim to nano or did it come as nano?
Did you try a different SIM in your Moto X?
Click to expand...
Click to collapse
They did try another Sim on my phone and same, no good. Voice seemed to work on other phones. I personally believe my phone was blacklisted. When I went to get my Sim changed I forgot to mention the account was under my moms name. Now my new Sim is under my name but with the number of another owner (my mom). Which could explain why I get no voice or SMS but data works fine. I am actually on my way to customer service right now.
Well just returned from customer service. No good. Its the phone itself. :/
Well just returned from customer service. No good. Its the phone itself. :/
Problem solved?
Alecegonce101 said:
Well just returned from customer service. No good. Its the phone itself. :/
Click to expand...
Click to collapse
Have you solved the problem? I'm using Samsung Galaxy S5 and has similar problem... After couple of times of change rom the problem occur... I'm not genius and I have struggle with this problem for more than 2 weeks... See whether we can work this out...
My situation is:
1. Voice: out of service, data: inservice;
2. IMEI: seems normal
3. I tried two SIM card with different ISP, neither work;
4. I also try that two SIM card on my iphone4, both work well.
5. Since my phone is G900F HK version, and I'm currently in UK, so I tried latest UK stock firmware and latest HK stock firmware. Same...
I had do some searching and said that there are few reason that might lead to this problem:
1. IMEI error. Flash rom may damage your partition, if your IMEI is 0046*** or 0000*** something then this is the case;
2. Baseband related. Just flash some wired rom that no capable with your local bands?
3. still looking...
Good luck then...
Same thing
Did you ever solve this? I am having the same problem on my Moto x Pure 2015.

Help with Project Fi back to Sprint

Well, tried out Project Fi and didn't go well. My Nexus 6 was purchased from Sprint and when activated on Project Fi would never connect to Sprint. Called Sprint to see if it was locked somehow and they did an unlock request. Found out later this was a bad idea. Phone would still not connect to Sprint on Fi so cancelled and tried to go back to Sprint. Now they are saying phone is incompatible and they can not re add my MEID back to the system. Anyone else went through this? Been calling every day for a week and ready to say FU to this incompetent company.
Broken said:
Well, tried out Project Fi and didn't go well. My Nexus 6 was purchased from Sprint and when activated on Project Fi would never connect to Sprint. Called Sprint to see if it was locked somehow and they did an unlock request. Found out later this was a bad idea. Phone would still not connect to Sprint on Fi so cancelled and tried to go back to Sprint. Now they are saying phone is incompatible and they can not re add my MEID back to the system. Anyone else went through this? Been calling every day for a week and ready to say FU to this incompetent company.
Click to expand...
Click to collapse
i would try flashing yoour stock build. i saw somewhere that fi can change some things that need a stock flash to fix.
just curious, why were you unhappy the fi wouldnt connect to sprint? was tmo not as good as the sprint you had?
my thought is its going to connect to the best network (theoretically), and for a large portion of the country, thats not sprint.
Well, where I live they are both about the same, except where I work. Barely any reception on T-mo and when I do it is Edge...
Broken said:
Well, where I live they are both about the same, except where I work. Barely any reception on T-mo and when I do it is Edge...
Click to expand...
Click to collapse
i read some post about bad activation on sprint, possibly tmo too, i dont recall the specifics.
unfortunately, i believe the fix was to wipe the phone and let it activate again on both networks.
once they had good activation's, the connection problems went away.
bweN diorD said:
i read some post about bad activation on sprint, possibly tmo too, i dont recall the specifics.
unfortunately, i believe the fix was to wipe the phone and let it activate again on both networks.
once they had good activation's, the connection problems went away.
Click to expand...
Click to collapse
Sounds like a plan. Go stock and see what the hell works. If they can't make it work it an RMA and get new IEMI.
Broken said:
Well, tried out Project Fi and didn't go well. My Nexus 6 was purchased from Sprint and when activated on Project Fi would never connect to Sprint. Called Sprint to see if it was locked somehow and they did an unlock request. Found out later this was a bad idea. Phone would still not connect to Sprint on Fi so cancelled and tried to go back to Sprint. Now they are saying phone is incompatible and they can not re add my MEID back to the system. Anyone else went through this? Been calling every day for a week and ready to say FU to this incompetent company.
Click to expand...
Click to collapse
On Google's fi website it says to do the following when activating the service:
Is your Nexus 6 ready for Project Fi?
Only the North America model (XT1103) is supported.
If your phone is on Sprint, deactivate your Sprint service before you insert your Project Fi SIM card. This step doesn't apply if you're transferring your Sprint number to us.
https://fi.google.com/signup#signup/device
Could this be the issue you are having with Sprint? Did you deactivate your service first?
quailallstar said:
On Google's fi website it says to do the following when activating the service:
Is your Nexus 6 ready for Project Fi?
Only the North America model (XT1103) is supported.
If your phone is on Sprint, deactivate your Sprint service before you insert your Project Fi SIM card. This step doesn't apply if you're transferring your Sprint number to us.
https://fi.google.com/signup#signup/device
Could this be the issue you are having with Sprint? Did you deactivate your service first?
Click to expand...
Click to collapse
the phone is not activated without a sim in it, so you should be able to remove the sim, then factory reset, and any trace of the sprint activation will be gone.
may be a better option for those who want to test fi, and arent ready to cancel their current service.
Broken said:
Well, tried out Project Fi and didn't go well. My Nexus 6 was purchased from Sprint and when activated on Project Fi would never connect to Sprint. Called Sprint to see if it was locked somehow and they did an unlock request. Found out later this was a bad idea. Phone would still not connect to Sprint on Fi so cancelled and tried to go back to Sprint. Now they are saying phone is incompatible and they can not re add my MEID back to the system. Anyone else went through this? Been calling every day for a week and ready to say FU to this incompetent company.
Click to expand...
Click to collapse
I did the same thing. I was going to just pay a month on Fi and use my google # and sim swap it to try it out. It got really hairy. T-Mo worked fine but wouldn't connect to Sprint. I called both Google and Sprint and they said it wouldn't ever work unless I cancelled the original line with Sprint. From what they said, you can't register the same IMEI twice on network. The service issue was fixed by doing this, manually reflash LMY48M in fastboot (fastboot flash radio radio.img) etc. There's a tutorial a google search away. Then boot, activate, dialer #*#*4636*#*#, change to LTE/GSM/CDMA AUTO PRL, and switch to band 7 mode.

Nexus 6 unable to make calls

I have a weird issue popping up and both Google and my tech savvy friends are having no luck in solving it.
My Nexus 6 was originally purchased through AT&T. When I got Project Fi, I worked with a Google rep to flash the Fi firmware onto it so it would be unlocked and work with the Fi network. That was all back in early August. I kept using the phone switching my AT&T and Fi sims in and out whenever needed (AT&T still remains my primary carrier, Fi was more for when I traveled internationally) and it worked fine.
For the last three weeks, I was using my AT&T sim in a Galaxy S6 Edge I was borrowing and was using nothing in my Nexus 6. At the end of last week, I put my AT&T sim back into the N6 but could not make any calls. I can receive calls but I can't make them from my end. Whenever I try (with Wi-Fi on or off), I get the message "We could not complete your call. Please try again" and it hangs up.
Can anyone think of any reason this is happening or how to fix it? Thanks!

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.

Categories

Resources