I've had a T-mobile Nexus 6 on Verizon network since Thanksgiving. I've had no problems at all UNTIL today. Woke up and my network symbol has an exclamation point next to it and when I try and make calls it sends me to Verizon's customer account services. Also, a dropdown bar with the words "sign into network" appear. After clicking on it it sends me to the Verizon's broadband page.
Anybody else have this problem and no what to do? Wanna run this by before I call and navigate customer service.
Edit: My account is fully paid and up to date
Try reinserting the sim card and reboot with WiFi off. Otherwise you might need a new activated nano sim.
Its weird that it'd suddenly become deactivated though. That would suggest they cut you off intentionally.
mordrukk said:
Try reinserting the sim card and reboot with WiFi off. Otherwise you might need a new activated nano sim.
Its weird that it'd suddenly become deactivated though. That would suggest they cut you off intentionally.
Click to expand...
Click to collapse
Yeeup. I've tried a factory reset and exchanging the sim. I put my wife's micro sim in and it deactivated her whole account. Verizon did this on purpose and I'm not happy. I've been using this phone for 3 months with NO problems
So any sim inserted to your N6 has the associated account deactivated? What did Verizon support say when you called them?
mordrukk said:
So any sim inserted to your N6 has the associated account deactivated? What did Verizon support say when you called them?
Click to expand...
Click to collapse
Okay, so I called Verizon and the tech could not get my phone activated. She said the phone number on that account wasn't working. While this was going on I randomly checked my EMEI number on Swappa and my phone was just reported Stolen/blacklisted! Although I bought on CL unopened in box with triple-checked clean ESN. I've used it for almost 3 months with no issues and a clean ESN. I even registered it through Motorola's website. I am beside myself. I didn't say anything to the tech because she was determined to get it working and I didn't want to be like "oh hey, yeah by the way I just realized this phone is reported stolen".
Well, it is still not working and tech pretty much gave up. So I'm gonna go down to Verizon and see if there is another workaround. I don't know if this is the reason it isn't working, but all evidence says so.
Anybody have any ideas on if this phone can be used again? Am I screwed?
That's sucks how that can happen. I to bought my nexus from someone and I sure hope he doesn't do the same thing. They should see one you activate it and use it for a period of time. Then all of a sudden reported stolen, that is a scam.
Sent from my Nexus 6 using Tapatalk
Haha! Figured it out.... Finally got to a tech who knew what was up. I'm on a family plan and unbeknownst to me my inlaw had an ipad stolen and reported it to Verizon, which in turn deactivated and reported device stolen. BUT, instead of reporting just the ipad, they reported the phone too. Doesn't make a whole lot of sense. But the tech fixed it.
I told him it up front it wasn't a verizon "branded" device, that I cut my micro sim card down to fit it and he said no problem he would get it working....AND he did.
Similar issue
I'm having exactly the same symptoms as you mentioned, but on Swappa my IMEI comes up clean. I've talked with Google, Motorola (source for my N6), and Verizon. This happened right after a *611 call related to a billing issue. The sim in the phone is a microsim cut from my S3. Worked for about a month, then boom. Finally talked to someone last night that "fixed" my issue, but it's flaky and temporary at best. The tech support person activated my phone as my old S3 somehow, but it does seem to work. One of the other Verizon techs put in a service request to add my IMEI to the Verizon database, but it was denied because of differences between the firmware/software on the Verizon N6's making mine "not safe" to be on their network. I'm looking for a long term solution. Every time I jump off WiFi I get the aforementioned network exclamation point and then it comes back. I'm wondering if the phone had Verizon's firmware version if they'd activate it? I think my IMEI is blacklisted?
I didn't want to start a new thread since this is similar.
Hoping I didn't break any other rules. Any help would be greatly appreciated.
My wife bought me the international version of the Samsung Gear S (SM-R750W). She said that she researched and from her understanding it should work on the T mobile network. From what I've found though the consensus seemed to be it would not work, or if it did it would be spotty at best depending on the specific towers/area you were in because Tmobile utilizes different network types in different areas.
I decide to give it a shot anyway and went to the T-Mobile store where I signed up for the wearable plan and got a new nano sim card. I was crossing my fingers but as soon as they put the sim card in the watch it came to life. It looked to be working fine but as I left the store I received a text from T-Mobile stating " the SIM for your wearable devices is in an ineligible device. Services to the SIM are locked until it returned to your eligible wearable device".
I pessimistically started thinking well great, there goes that idea. But as I got into my vehicle I shut my phone down and tried to see if the watch can work on its own as a phone when unencumbered from my Note 4 bluetooth/WiFi data connections. It worked perfectly-I started calling my friends and they couldn't believe I was talking on a watch phone. Several I actually felt the call sound quality was better on the watch speaker phone compared to normally speaking on the Note 4. I called customer service but they told me they couldn't see anything and if it was working fine not to worry about it.
For the next eight or 9 hours it worked perfectly and I was using it a lot. I drove around large swaths of town and neither data nor call experienced even the slightest issue - for once I was happy to be wrong.
Eventually, as I am oft to do, I fell asleep. When I awoke this morning the watch was no longer connected to the network. It gave me a message saying it was unable to connect and did I want to scan for additional networks. I selected yes and it was able to find the T-Mobile and ATT networks. T-Mobile was selected and a "registering" notification was displayed. It took awhile but eventually said it was unable to register with the network.
I call T-Mobile and they said pretty much exactly what I expected them to say -that because it was not a T mobile device they could not ensure proper operation. But he said (and he characterized this as "good news", "light at the end of a tunnel" and "viable solution” Seriously said all 3 things.) I could either forget all about the cellular connection and just use this as a companion device OR go and buy a new Gear S from T Mobile if I really wanted that feature.
I’m truly and utterly baffled that he believed his suggestions merited the positive sayings from above. Never in my lifetime has my head been closer to exploding.
After I was finally able to speak again, I explained that it seemed unlikely to be an issue with the watch. If my Gear S was working perfectly yesterday and can still detect Tmobile & ATT networks, then something on your end seems to be preventing registration. He agree to file a ticket with the engineering team and tomorrow I should hear from them hopefully. He also told me to go and try another nano-SIM, gratis, at the Tmobile store. So today I went and as soon as I put the new card in all systems were go. I assumed that I somehow had received a bad card because here again now, data and voice are connected.
This time I didn’t even make it out of the parking lot before it notified me that that it was again unable to register with the network. There is conflicting information regarding the radio frequencies and bands that the different Gear S models have and I didn’t have high hopes. But then it actually did work, WELL, so any ideas as to what is going wrong?
I don't know how I put this in the wrong forum, could one of the mods please delete it? It's already been reposted in the correct forum.
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
Try to unlock bootloader, install TWRP, root the stock rom, then install lastest bootloader (v72.03) and latest radio (v05.45):
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Use WUG Fresh NRT tool to accomplish above when hooked to Windows PC via microUSB in 2.0 USB port with correct Windows drivers installed (OK for ADB): https://forum.xda-developers.com/showthread.php?t=1766475
HueyT said:
Try to unlock bootloader, install TWRP, root the stock rom, then install lastest bootloader (v72.03) and latest radio (v05.45):
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Use WUG Fresh NRT tool to accomplish above when hooked to Windows PC via microUSB in 2.0 USB port with correct Windows drivers installed (OK for ADB): https://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
I'm already unlocked, rooted, TWRP'd and using the PureNexus that came out end of april (I haven't flashed the one in may yet). I believe I'm also currently using the latest radio and latest bootloader.
Edit - I actually was not on the most recent radio, but I did flash that, no change.
The volte provisioned flag turned on in the testing menu? I have a setting for enhanced 4g lte mode in my settings, wireless networks/more/cellular networks settings. Did they remove the advanced calling from your account? Just throwing some things out there.
Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
The tech may not be wrong as Verizon uses band 13 as their main LTE band and ATT uses band 17
http://www.phonearena.com/news/Chea...on-T-Mobile-and-Sprint-use-in-the-USA_id77933
Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
In others countries we don't get the same bands management, then I can't say anything about LTE.
But I'm on PureNexus 7.1.1 and I get the same "issue" about network droppin when calling. When the call starts, my phone turns into don't disturb-mode and recover the network only when the phone call ends.. It doesn't really cut my network connection, but it looks like. It may be rom settings.
However I don't care as long as everything works good, it's just an icon. (how a phone call can be done while network is shutted off ^^)
When I was on the stock ROM, this autumn, 7.1 version of Android did the same thing, loosing data connection while being still connected to the network (but at anytime not just phonecalls). Finding it back some minutes later. That was fixed with 7.1.1. Stock.
Hope that might help you (looks not ) if it's the same problem. May be give an eye to the Rom settings..
Have you tried if your device do the same thing with an another Rom ? (stock for example)
Larzzzz82 said:
The volte provisioned flag turned on in the testing menu? I have a setting for enhanced 4g lte mode in my settings, wireless networks/more/cellular networks settings. Did they remove the advanced calling from your account? Just throwing some things out there.
Click to expand...
Click to collapse
I knew something looked like it was missing. I don't have any enhanced 4g LTE settings in that section. Normally there's a tick box to turn it on there. It's missing. Is that due to them not having it turned on in my account?
Also for everyone else, this problem only started when I tried the whole at&t switch. I was on this rom when I switched and it worked fine before then. I didn't factory reset since then though, wondering if I need to try that.
zelendel said:
The tech may not be wrong as Verizon uses band 13 as their main LTE band and ATT uses band 17
http://www.phonearena.com/news/Chea...on-T-Mobile-and-Sprint-use-in-the-USA_id77933
Click to expand...
Click to collapse
The tech is definitely wrong; since it's a Nexus 6 (presumably XT1103) it has all the possible LTE bands used in the US. There should not have been any issue when switching. I had something similar happen to me, when I just switched to verizon and did the "reset network settings" button, it screwed up my phone so I couldn't use LTE period, I had to reflash the modem in order to fix it. I know you already said you reflashed the modem, but I'm not sure what to suggest. There is absolutely nothing physically wrong or incapable about your phone, just some config got screwed up somewhere along the way. I'd just try to flash as many things as you're comfortable with without losing your userdata. Like modem, bootloader, etc. until your data comes back. If nothing else, press the network settings reset button and flash the latest modem. Make sure your twrp is up to date as well.
BlockOfDynamite said:
The tech is definitely wrong; since it's a Nexus 6 (presumably XT1103) it has all the possible LTE bands used in the US. There should not have been any issue when switching. I had something similar happen to me, when I just switched to verizon and did the "reset network settings" button, it screwed up my phone so I couldn't use LTE period, I had to reflash the modem in order to fix it. I know you already said you reflashed the modem, but I'm not sure what to suggest. There is absolutely nothing physically wrong or incapable about your phone, just some config got screwed up somewhere along the way. I'd just try to flash as many things as you're comfortable with without losing your userdata. Like modem, bootloader, etc. until your data comes back. If nothing else, press the network settings reset button and flash the latest modem. Make sure your twrp is up to date as well.
Click to expand...
Click to collapse
I think i'm going to reflash my rom today. I did the modem, twrp is up to date, bootloader is fine. I did the reset network settings (I was sure that was going to fix it, no dice). So I'm going to reflash the rom today and see if that fixes it. After that I have no idea what is left to try other than reverting to stock, which I'd like to avoid.
Yes, it is a feature that needs to be added to your account. Go online and check their website or go into the hidden menu and activate it. If it sticks, it's on your account.
I tried the wifi and video calling flags and they didn't stick. Go figure... C'MON big red...
Larzzzz82 said:
Yes, it is a feature that needs to be added to your account. Go online and check their website or go into the hidden menu and activate it. If it sticks, it's on your account.
I tried the wifi and video calling flags and they didn't stick. Go figure... C'MON big red...
Click to expand...
Click to collapse
How do you enter the hidden menu on the n6? I thought I found it but it wasn't working.
.#.#4636#.#. select the phone info tab. In there, there will be either a drop down menu or buttons to tick and they'll change color
Larzzzz82 said:
.#.#4636#.#. select the phone info tab. In there, there will be either a drop down menu or buttons to tick and they'll change color
Click to expand...
Click to collapse
I got in, VoLTE was not ticked. I ticked it. I got the setting for it then in settings. But making a phone call gave me an error. I rebooted, and it's not ticked now. So does that mean I need to call Verizon to have them flag my account?
You need to add it in your account then. Easy enough to do online. You want to, "manage features."
Larzzzz82 said:
You need to add it in your account then. Easy enough to do online. You want to, "manage features."
Click to expand...
Click to collapse
That did the trick. All fixed. Thank you! That was driving me nuts. I never considered the idea that the setting would be turned off . But since I did leave and come back...
Thanks again!
Glad you're all set. ?
Hi all,
Have a question for you. Bought a used S8 off of a guy on the internet awhile back. Phone worked fine for a few weeks, but now has developed a problem where it claims no service and as such there is no data/calling/texting. Factory resets sometimes do or don't fix this issue. If it is fixed with a reset, it reoccurs within some hours. I have sent this in five times to Samsung. It has been out of my possession for weeks and weeks with the constant shipping back and forth. It is currently being shipped back to me. I assume in a not-fixed state. The service center people can't replicate the issue because it magically doesn't occur when they run their suite of tests on the device. As a result, they literally do nothing to the phone and also won't replace it. What is the chance I could go into a T-Mobile store and have it replaced? Thanks for your time.
Deepcoiler said:
Hi all,
Have a question for you. Bought a used S8 off of a guy on the internet awhile back. Phone worked fine for a few weeks, but now has developed a problem where it claims no service and as such there is no data/calling/texting. Factory resets sometimes do or don't fix this issue. If it is fixed with a reset, it reoccurs within some hours. I have sent this in five times to Samsung. It has been out of my possession for weeks and weeks with the constant shipping back and forth. It is currently being shipped back to me. I assume in a not-fixed state. The service center people can't replicate the issue because it magically doesn't occur when they run their suite of tests on the device. As a result, they literally do nothing to the phone and also won't replace it. What is the chance I could go into a T-Mobile store and have it replaced? Thanks for your time.
Click to expand...
Click to collapse
Normally in order for T-Mobile to exchange the unit, they would need to access the original buyer's account and see the warranty status. I first thought your phone's IMEI could have been blocked by T-Mobile, but you mention that after factory reset it works sometimes. Use T-Mobile's IMEI checker website and see what it shows you. https://www.t-mobile.com/verifyIMEI.aspx If you phone is unlocked, try another sim card, from another provider such as AT&T.
Charkatak said:
Normally in order for T-Mobile to exchange the unit, they would need to access the original buyer's account and see the warranty status. I first thought your phone's IMEI could have been blocked by T-Mobile, but you mention that after factory reset it works sometimes. Use T-Mobile's IMEI checker website and see what it shows you. [SNIP, can't even quote links, apparently] If you phone is unlocked, try another sim card, from another provider such as AT&T.
Click to expand...
Click to collapse
I was just assuming it wasn't blocked since it works on and off, but yeah, that site is telling me it is blocked on their network. Thanks. Guess this was a complete waste of money.
Deepcoiler said:
I was just assuming it wasn't blocked since it works on and off, but yeah, that site is telling me it is blocked on their network. Thanks. Guess this was a complete waste of money.
Click to expand...
Click to collapse
I believe there is a chance that T-Mobile might unblock it depending on why it was blocked in the first place.
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.