6P stopped receiving network service with AT&T - Nexus 6P Q&A, Help & Troubleshooting

I've tried everything to get my phone to get network working again. I've re-flashed old and newer images, got a new sim, messed with the APN settings and I just can't get it to work since yesterday.
When it started, my phone was sitting on charge. It was working just fine before I had put it down for 30 minutes. Upon checking for any messages I saw it wasn't getting any service so I restarted the device and was greeted with the 7.1.2 july update installer. Waited for it to finish and once fully back onto the home screen for a few minutes service still never came back. Turned it off and on a few times and turned airplane mode on and off few times still never came back. Turned it off for the night till today when I started playing with it more, factory reset, flashed 6.0, 7.1.2 june, 7.1.2 july, O beta 3 and none of it was getting the network to work.
Went and got a new sim, guy at the store also tried a floor sim and none of them were working but both my old and new sim do work just fine in a backup phone. The 6P reads there is a sim in and it knows its AT&T, but it won't pick up signal at all.
Any help with this? There really isn't much on this topic, but I do see a sim card no installed issue which my phone knows there is a sim card in it.

that happened to a nexus 6p i bought from a guy off craigslist. at first it worked with tmobile and metro pcs then after a few weeks it stopped working but i had switched to cricket anyway and it worked on cricket but not on tmobile or metro, so then i checked imei and it was black listed,.... being that it was a BYOD it wasnt bound to any network so i was like why would it be blacklisted... didnt make sense but i stayed with cricket and to this day it works..

i42o said:
that happened to a nexus 6p i bought from a guy off craigslist. at first it worked with tmobile and metro pcs then after a few weeks it stopped working but i had switched to cricket anyway and it worked on cricket but not on tmobile or metro, so then i checked imei and it was black listed,.... being that it was a BYOD it wasnt bound to any network so i was like why would it be blacklisted... didnt make sense but i stayed with cricket and to this day it works..
Click to expand...
Click to collapse
I just checked to see if it was blacklisted and its good. Google & Huawei won't service it due to it being out of warranty so rn its pretty much a dead phone for me. Is there is any tests I can run to see if the network radios are working or even turned on?

I had this exact same problem a few months ago with my other 6P. Thankfully it was right before my warranty ran out so i was able to get a replacement, but as far as I know, there isn't much you can do with it network wise.

@MadBullBunny could it maybe be the antenna inside? If you've tried other carrier Sims and flashed different radios what else I wonder. Since it's not working maybe worth a peak if your comfortable opening her up.

Exodusche said:
@MadBullBunny could it maybe be the antenna inside? If you've tried other carrier Sims and flashed different radios what else I wonder. Since it's not working maybe worth a peak if your comfortable opening her up.
Click to expand...
Click to collapse
I really didn't want to go that far and I rather just dump it on craigslist for $250 if its just an issue with at&t. is there some sort of test to see if the antennas are working?

have you try resetting your network settings? this has happen to me right after a update and resetting the network settings fixed it for me. i'm on project fi.

boxcar8028 said:
have you try resetting your network settings? this has happen to me right after a update and resetting the network settings fixed it for me. i'm on project fi.
Click to expand...
Click to collapse
Dude... Not trying to be rude, but really?
Anyway I've been waiting for a response back from google. Huawei pretty much told me tough luck since I didn't have warranty left on it. Told google that I was pretty much shoved out by them and argued that a phone not even 2 years old can't get serviced by a multi billion dollar company is pretty embarrassing. Supposedly its being routed up but I was told that a couple days ago when it was going to take 24-48 hours to get back. Right now I'm trying last ditch effort to drain the battery completely and stick it in some rice to possibly suck any possible moisture out that maybe my butt sweat caused. If this doesn't work I'm going to go to other service's stores and ask to try their sims in the phone out.
Fun tip: My phone is been running in boot mode for almost an hour after it turning off from android os for battery being dead. I've been doing random stuff in boot mode trying to make it die completely and it doesn't want too.

So being back and fourth with google for almost a week I was pretty much told tough luck buddy. It fathoms me that a company who created the android OS doesn't even have a service center or require its manufacturers to provide a service center for phones that aren't even more than 2 years old.
My nexus 6p is posted on craigslist and I've bought myself a s8+. so word of warning to you all who buy any google product or from them, just don't. If you have any issues you'll just get a run around. I've had to tell my issue to google at least 20 times and they still didn't care and kept trying to push me to hauwei when neither of them wanted to help.

Related

[Q] Defy XT555 'couldn't connect to server'

:crying: I have looked at other threads before posting but don't have my answer. My new (this is 3rd day) Defy XT555 says it "cannot connect to server" or "webpage not available" or it just never goes anywhere- just like an image of a 'wheel' turning until I get sick of waiting. I've been on the phone with straight talk and nothing has worked so far. They finally told me to return it and I reluctantly brought it up to the Walmart. The people there were messing with it and it started working! I think it was on the wifi mode. I had internet in the store and until I was almost home and lost it. I have a wireless router for the computer that has a password that I don't remember, but I thought this was the problem. I turned off the wifi setting on phone and it still won't work, turned wifi back on and went to work today. I went to a much bigger town and halfway home lost all internet again. I have alternated between having the wifi on and off. Straight talk insists that the phone should be working in my area and they said there are no problems on their end. I really want this phone to work. I researched phones before buying and this had all the features that I really wanted. I just haven't wanted to give up. Not only because I had so much anticipation for this phone I couldn't hardly sleep waiting for it to get here, but I've also spent almost $60 on accessories for this phone from Amazon- all from differant sellers, and it's not worth sending back because a lot of the expense was in shipping.
I do live in a somewhat rural area, but really not that far out at all... I read that cdma was better in rural areas, plus I had a Sprint phone several years ago that used to work great here, and had a gsm At&t that didn't. My daughter used a straight talk phone here before and says it's the only one that works here now and now apparently that doesn't work either- or I just got a lemon? I'm getting tired of this and feeling pretty ripped off. I'm afraid to order another one just like it but I haven't wanted to give up on this phone. Any suggestions?

Galaxy Note 3 won't activate to my phone number??

Hey all, I just got my GN3, still am using the GN2 though BC Verizon can't get the phone to activate to my phone number? Actually Verizon says it show the GN3 activated, but l have no service/phone/data/anything at all. They tried 5 different GN3's and 13 different SIM cards before they gave up trying to activate. My number works/activates just fine on my GN2. So they gave me a temporary number yesterday to see if it was a problem with my particular phone number and sure enough, my GN3 activated on the temp number. When I switched back to my reg # it wouldn't connect...again. Then I went to work which was about 10 miles away and the GN3 activated on my reg#. I called my wife, made a few texts, surfed the net, etc... for about 2 hours, when I got about 8 miles from home, I lost all connection again... What gives here? It's the weirdest problem I've ever seen. I'm home now, and tried activating it again with no luck. Any thoughts??
I'm sorry if this is the wrong forum for this thread, if so please move??
Mine wouldn't activate for the first 20-30 minutes or so. I removed the sim card, reinstalled then went on the website and updated the Note 3 in formation for my line. Had keep refreshing my lines info on the Web page about 2 more times and hit accept before it Finally activated. Took about 5 additional minutes after removing the sim. Not sure if that will help, but hope you get it working.
Sent from my SM-N900V using XDA Premium 4 mobile app
chino0131 said:
Mine wouldn't activate for the first 20-30 minutes or so. I removed the sim card, reinstalled then went on the website and updated the Note 3 in formation for my line. Had keep refreshing my lines info on the Web page about 2 more times and hit accept before it Finally activated. Took about 5 additional minutes after removing the sim. Not sure if that will help, but hope you get it working.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well seeing as how I got mine on 10OCT2013 at 10 am and it still hasn't activated, I think it's not going to at this point. I may sadly have to go back to my GN2 and return the GN3 altogehter. :crying:
Mine seemed stuck on activation, ended up using my old sim card, activated almost instantly.
Update: just got off phone with Big Red and they said that for some reason when I'm on my "home" towers, my activation has trouble letting go of the GN2?? Maybe it really is hard to say good-bye...
They are working on it now...
I've always had an issue activating my old number on a new phone with a new SIM.... I've always just switched my old SIM card in and it's worked perfectly lol
Make sure the SIM card has been linked correctly to your phone number. The easiest way is to look on the VZW paperwork that came with the phone and make sure it's your phone nbr and not another person's on your plan.
I am having more or less the same issue.
To make a long story short, whenever I leave the "home" cell tower that the phone was activated on, it will not connect to any kind of network whatsoever. It just shows a circle with a line through it, and at the same time it reboots itself, randomly and frequently, even when it isn't being touched. All of these problems go away as soon as I get back home to that cell tower. I wonder if the original poster activated his phone at work the first time, and that's why it only works when he returns to work?
I have tried 3 different SIMS to fix this: the one that came in the GN3, the one from my old Galaxy Nexus, and a brand new one from a Verizon store. I have done half a dozen factory data restores.
My next step is to try an in-store swap. A local store around here first refused to hold a phone for me to swap, then when I got there (or rather when a family member got there), we were told that there was a master ticket for this issue and there was a freeze on doing any exchanges until Samsung released a "fix". My subsequent conversations with Verizon tech support have confirmed that the whole story about a master ticket and not doing exchanges was a complete lie. The stores are actually required to uphold the 14 day worry free guarantee no matter what. Obviously this store didn't want to give up a phone to me that they could sell to someone else. They weren't just being unhelpful, they were running interference on resolving my problem for their own greed.
I had an activation problem in store yesterday when swapping my note 2 for note 3. The sales rep entered the sim card info that was on the sticker on the box for the sim card that comes with the phone.
It all ended up causing major activation / service connectivity issues because the sim card info on the box did Not match the actual sim card number for the sim pre-installed on the phone.
This is apparently an issues for some other people as well. If the sim card in the phone is not reconciled with the info on the box prior to entering the info into Verizon's system.... You will be in for a time consuming headache
Sent from my SM-N900V using xda app-developers app
urielsynthesis said:
I am having more or less the same issue.
To make a long story short, whenever I leave the "home" cell tower that the phone was activated on, it will not connect to any kind of network whatsoever. It just shows a circle with a line through it, and at the same time it reboots itself, randomly and frequently, even when it isn't being touched. All of these problems go away as soon as I get back home to that cell tower. I wonder if the original poster activated his phone at work the first time, and that's why it only works when he returns to work?
I have tried 3 different SIMS to fix this: the one that came in the GN3, the one from my old Galaxy Nexus, and a brand new one from a Verizon store. I have done half a dozen factory data restores.
My next step is to try an in-store swap. A local store around here first refused to hold a phone for me to swap, then when I got there (or rather when a family member got there), we were told that there was a master ticket for this issue and there was a freeze on doing any exchanges until Samsung released a "fix". My subsequent conversations with Verizon tech support have confirmed that the whole story about a master ticket and not doing exchanges was a complete lie. The stores are actually required to uphold the 14 day worry free guarantee no matter what. Obviously this store didn't want to give up a phone to me that they could sell to someone else. They weren't just being unhelpful, they were running interference on resolving my problem for their own greed.
Click to expand...
Click to collapse
Switching your device or SIM will not work. I have now gone through 6 GN3's and almost 20 different SIM cards. It's the towers/service from Verizon. They have noted that this is a problem and are working diligently to fix it...lol Meanwhile, I've returned my GN3 and will wait until they fix this disaster. This rollout is almost as bad as Obamacare...haha
dead batteries said:
Hey all, I just got my GN3, still am using the GN2 though BC Verizon can't get the phone to activate to my phone number? Actually Verizon says it show the GN3 activated, but l have no service/phone/data/anything at all. They tried 5 different GN3's and 13 different SIM cards before they gave up trying to activate. My number works/activates just fine on my GN2. So they gave me a temporary number yesterday to see if it was a problem with my particular phone number and sure enough, my GN3 activated on the temp number. When I switched back to my reg # it wouldn't connect...again. Then I went to work which was about 10 miles away and the GN3 activated on my reg#. I called my wife, made a few texts, surfed the net, etc... for about 2 hours, when I got about 8 miles from home, I lost all connection again... What gives here? It's the weirdest problem I've ever seen. I'm home now, and tried activating it again with no luck. Any thoughts??
I'm sorry if this is the wrong forum for this thread, if so please move??
Click to expand...
Click to collapse
Mine kept trying to activate on the phone and would continually fail.
I thought I had a faulty device and was going to go to the store. Something told me to login to MyVerizon online on my computer [since I kept my old phone off as directed via the on-screen instructions] and poke around and see if there was anything there that might be able to help me.
I clicked on my line, and the Manage My Device link on the left hand side of the screen and ended up being able to complete the activation via the website. Re-booted the phone, and then voila~! Activation complete.
FYI, I was migrating from an iPhone 5 to the GN3.
nimitch said:
Mine kept trying to activate on the phone and would continually fail.
I thought I had a faulty device and was going to go to the store. Something told me to login to MyVerizon online on my computer [since I kept my old phone off as directed via the on-screen instructions] and poke around and see if there was anything there that might be able to help me.
I clicked on my line, and the Manage My Device link on the left hand side of the screen and ended up being able to complete the activation via the website. Re-booted the phone, and then voila~! Activation complete.
FYI, I was migrating from an iPhone 5 to the GN3.
Click to expand...
Click to collapse
Yeah I tried that as well. I'm not sure there is anything I haven't tried. I've returned my device and decided to stick with my Note 2. Maybe when Verizon gets their heads on right and fixes this, I'll come back.

Roaming Data keeps switching to Verizon

I was running tx_dbs_tx Hybrid X 3.0 up until this morning when my phone suddenly kept popping up the Data Roaming Guard. Whenever I would attempt to make a call, it would alert me to a Verizon error to reboot my phone -I am on Sprint. I flashed with Odin the stock OK1 software, and besides having Knox and ItsOn back on my phone and battery life being horrible once again, I am still receiving the Data Roaming Guard splash screen and still receiving the Verizon error when making calls. I was able to make a single call after using the Activate Device self-service, but it didn't even last 20 minutes.
Again, back on stock OK1 ROM from Sammobile, re-rooted with Freeza's OK1 stock kernel, SuperSU Beta 2.52, any help would be greatly appreciated.
BGray210 said:
I was running tx_dbs_tx Hybrid X 3.0 up until this morning when my phone suddenly kept popping up the Data Roaming Guard. Whenever I would attempt to make a call, it would alert me to a Verizon error to reboot my phone -I am on Sprint. I flashed with Odin the stock OK1 software, and besides having Knox and ItsOn back on my phone and battery life being horrible once again, I am still receiving the Data Roaming Guard splash screen and still receiving the Verizon error when making calls. I was able to make a single call after using the Activate Device self-service, but it didn't even last 20 minutes.
Again, back on stock OK1 ROM from Sammobile, re-rooted with Freeza's OK1 stock kernel, SuperSU Beta 2.52, any help would be greatly appreciated.
Click to expand...
Click to collapse
Do you live in a 4G Sprint area? If not this EXACT same thing happened to me and my wife right before they started 4G in our area. Even service calls went to Verizon first. Evidently even the Sprint reps had no idea that 4G was getting turned on in my area, they had me do all the #* dialer codes and both our phones said we were in roaming for like a day or two.
ianmb said:
Do you live in a 4G Sprint area? If not this EXACT same thing happened to me and my wife right before they started 4G in our area. Even service calls went to Verizon first. Evidently even the Sprint reps had no idea that 4G was getting turned on in my area, they had me do all the #* dialer codes and both our phones said we were in roaming for like a day or two.
Click to expand...
Click to collapse
Yes, San Antonio was one of the first markets with Sprint to have 4G WiMax and then 4G LTE. It had been running just fine for months, but suddenly stopped working. Even after flashing stock back on without root or any added apps besides Sprint's auto-downloads, it still had the problem. Took it to the store yesterday and baffled them all for 2 hours before they ordered me a replacement. They even tried a new sim card because I told them that I've had problems intermittently in the past with the Roaming Guard popping up and forums stated it could be a bad sim card. The Sprint # codes wouldn't even work. Anyways, they ordered me a replacement- won't have it until Tuesday but thanks for the response. I had never heard of anything like this happening before and it struck me as odd. I even checked the settings for the network and they all checked out fine, Sprint store reps did the same and were just as perplexed as I was.
Mine was doing almost the same. Seemed like it had to go to verizon when it would go between towers. Then back to sprint. So I did the ##72786# that is suppose to launch the hands free activation. Although it didnt launch it(due to custom rom), it did run the provisioning stuff and fixed mine. Hasn't went to roaming yet.
No promise it will work. But hopfully it will fix yours. Assuming you are on a note 4.
Txdaredvl said:
Mine was doing almost the same. Seemed like it had to go to verizon when it would go between towers. Then back to sprint. So I did the ##72786# that is suppose to launch the hands free activation. Although it didnt launch it(due to custom rom), it did run the provisioning stuff and fixed mine. Hasn't went to roaming yet.
No promise it will work. But hopfully it will fix yours. Assuming you are on a note 4.
Click to expand...
Click to collapse
Yes, I am on Sprint Note 4, but the pound codes wouldn't even work. As soon as I put in the last # sign it just cleared out the dialer. I found a complete list of # codes on sammobile or samfirmware site, can't remember which, and even Sprint attempted them. I had flashed back to stock available on Sammobile prior to going to Sprint, but it still didn't work. You don't think different flashes or ROMs or kernels could have caused this do you?
Anyways, I have the insurance through Sprint and have a new one on the way Tuesday. I just hate not being able to figure out a software related problem. I was also trying to find a way to do it manually while rooted, but couldn't find the right edits because I cannot even remember how to get into the correct settings at the moment-mind cluttered with too many projects.
I appreciate all of the responses though and really enjoy learning about my device on xda and hope to either create my own apps or even cook a ROM in the near future.

8.0 Upgrade Now Lost LTE, Roaming Intermittently & Android Pay Does Not Work

Is anyone having this issue.
I upgraded to android 8.0 and no longer able to get any Verizon LTE service no matter what location I am in. I get frequent notifications stating I am Roaming and my phone is not rooted and the bootloader was locked, yet Android Pay Pop ups stating it cannot work on my 6p because my phone is either rooted or the bootloader is unlocked.
I flashed several different images to no avail.
Advice?
locolbd said:
Is anyone having this issue.
I upgraded to android 8.0 and no longer able to get any Verizon LTE service no matter what location I am in. I get frequent notifications stating I am Roaming and my phone is not rooted and the bootloader was locked, yet Android Pay Pop ups stating it cannot work on my 6p because my phone is either rooted or the bootloader is unlocked. I flashed several different images to no avail. Advice?
Click to expand...
Click to collapse
Reset Network settings reset, wipe cache partition. When you say you flashed images, do you mean sideloading OTAs.... or are you unlocked and using full images? Your post led me to believe you were getting erroneous messages about being rooted/unlocked (meaning you were not).
v12xke said:
Reset Network settings reset, wipe cache partition. When you say you flashed images, do you mean sideloading OTAs.... or are you unlocked and using full images? Your post led me to believe you were getting erroneous messages about being rooted/unlocked (meaning you were not).
Click to expand...
Click to collapse
Tried it all.
I installed several full factory image versions, locked the boot-loader and then started up the phone. With the boot-loader locked and phone not rooted Android Pay still gave me the error that my phone is running a custom ROM, the boot-loader is unlocked or the phone is rooted.
I have also installed several OTA images and none of the problems I mentioned in my earlier post went away. The only way for me to get Android pay to work is to unlock the boot-loader and root the phone with magisk. However, I still get intermittent Roaming notifications, intermittent signal lost and no LTE whatsoever.
Today:
I called Google and and did 45mins of troubleshooting, the final thing we did was reset my phone and then the agent acted helpless when nothing resolved the issue.
I called Verizon did 30 minutes of troubleshooting with them, reset network setting about 100 times, turned off my phone so that they could re-provision on their end. Turned the phone on and got LTE signal for approximately 60seconds. Then it went back to 3G, then no signal and then the dreadful roaming notification every few minutes.
Are you using the stock recovery or TWRP? And when you installed factory image did you do it through your computer using flash all? Or did you just install the factory image? Personally what I would do if wipe everything out and use your computer to install the latest factory image using the flash all script. So you are completely stock then relock the bootloader. Then you should be completely up to date with modem bootloader recovery vendor and rom. Your lte issue sounds like a modem problem possibly. And the September security patch broke safety net check and therefore Android pay. That build ended in.017. there is a new one up that fixes those issues and I think also the issue with the phone choosing mobile data over WiFi when it should be choosing wifi over mobile. That build ends in.019. try installing that build like I said above. Good luck
mojorisin7178 said:
Are you using the stock recovery or TWRP? And when you installed factory image did you do it through your computer using flash all? Or did you just install the factory image? Personally what I would do if wipe everything out and use your computer to install the latest factory image using the flash all script. So you are completely stock then relock the bootloader. Then you should be completely up to date with modem bootloader recovery vendor and rom. Your lte issue sounds like a modem problem possibly. And the September security patch broke safety net check and therefore Android pay. That build ended in.017. there is a new one up that fixes those issues and I think also the issue with the phone choosing mobile data over WiFi when it should be choosing wifi over mobile. That build ends in.019. try installing that build like I said above. Good luck
Click to expand...
Click to collapse
I wiped DATA so there were no files on my phone.
Downloaded july,august,september factory images and flashed, locked bootloader and tested each image to no avail. I saw the build on the google forum for 019 so i flashed that as well and same sh:silly:t different day.
Last thing I did was to flash 7.1.1 and that did not resolved my problems. Got the OTA notification to install 8.0 hoping all my problems might disappear but they did not.
It has been an hour and LTE seems to be working again
I have a 5X on Project Fi and my 6P is on Verizon(the phone that is having problems).
As a last resort tonight I swapped SIM Cards and after a few minutes the Fi SIM in the 6P showed LTE service. (Maybe proof it was not the phone....??? who knows)
It took alot longer but my Verizon sim then showed LTE service on my 5X which is running Oreo btw. (Baffled at this point)
I placed the SIM cards back in their original phones and LTE is functional on both. On my 6P I enabled WIFI, downloaded data, toggled WIFI, rebooted, ran several speed test and the 6P still shows LTE and I haven't seen the dreadful roaming notification as of this message.
I guess problem solved. Now to install Magisk to get AP working.
Wow that is odd. The one thing I have noticed with 8.0 on my 6p on fi is sometimes I lose data when I'm out and the phone loses wifi and switches back to lte. I have to reset the phone to get lte back.
Thank you so much for posting this issue. My Nexus 6P was doing the same thing after 8.01 October security update. Tried everything, same as you listed. I found your post and recalled that during my initial setup I had to put my wife's Verizon SIM into the 6P due to the same issue occurring. I tried it again this time but it failed, issue persisted. So, based on your post, I got a Project Fi SIM for $30 (1 month) and just tried it again. Powered down, put in Fi SIM, power on, activated Fi (with new phone # for new line... will be cancelled if needed...), and got LTE without issues over Project Fi. Then, I did Network Settings reset, reboot, and powered back up. No issues with Fi.
So, to the point now. I put the Verizon SIM back in the 6P and BAM, full LTE, no issues. Whatever the non-Verizon SIM does to the phone internal settings I have no idea, but I can tell you that it was not a fluke that your process worked. The exact same thing worked for me.
Hope this helps anyone else with the same issue - you need to install a non-Verizon SIM, get LTE going, and then put the Verizon SIM back in.
Thanks again.
JT
Just my 2 centers here for anyone else in this quagmire...
I had same issue. I've got a Nexus 6p on which I dirty flashed an 8.1 update of ABC Rom over an earlier 8.1 version 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. I tried everything, as is stated above: revert to stock, older radio images, different SIM... nothing worked. I read about people manually configuring their APNs. However, I've got a Verizon SIM, so that option was gone.
Anyway, after reading this post, I got the idea that I might be able to mimic the solution without buying a Project Fi SIM that I don't want.
Here's what I did:
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.
Profit!
I'm not sure if this solution has any parallels to the solution that uses a project Fi SIM for a brief moment. However, I speculate that it may.
At any rate, I hope this helps someone else with this issue.
UPDATE:
It turns out this method is more of a work around at best. At first I noticed that I had to toggle airplane mode once after a reboot. That didn't seem too difficult. However, I then discovered that I could no longer make calls. Switching the VoLTE Provisioned toggle back off fixes the calling issue, but puts me back on 3G.
Uggg.
locolbd said:
I have a 5X on Project Fi and my 6P is on Verizon(the phone that is having problems).
As a last resort tonight I swapped SIM Cards and after a few minutes the Fi SIM in the 6P showed LTE service. (Maybe proof it was not the phone....??? who knows)
It took alot longer but my Verizon sim then showed LTE service on my 5X which is running Oreo btw. (Baffled at this point)
I placed the SIM cards back in their original phones and LTE is functional on both. On my 6P I enabled WIFI, downloaded data, toggled WIFI, rebooted, ran several speed test and the 6P still shows LTE and I haven't seen the dreadful roaming notification as of this message.
I guess problem solved. Now to install Magisk to get AP working.
Click to expand...
Click to collapse
Hey is ur 6p still running well with LTE? I did that with a att SIM card and my 6p read as a att SIM so I then put my Verizon Sim back in and it read Verizon LTE but then after like half an hour it changed back to roaming and 3g. I went to Verizon to get a new sim card but that didn't do any help at all. I would like ur feedback if possible. Thank you
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 02:08 AM ---------- Previous post was at 02:06 AM ----------
j2t0621 said:
Thank you so much for posting this issue. My Nexus 6P was doing the same thing after 8.01 October security update. Tried everything, same as you listed. I found your post and recalled that during my initial setup I had to put my wife's Verizon SIM into the 6P due to the same issue occurring. I tried it again this time but it failed, issue persisted. So, based on your post, I got a Project Fi SIM for $30 (1 month) and just tried it again. Powered down, put in Fi SIM, power on, activated Fi (with new phone # for new line... will be cancelled if needed...), and got LTE without issues over Project Fi. Then, I did Network Settings reset, reboot, and powered back up. No issues with Fi.
So, to the point now. I put the Verizon SIM back in the 6P and BAM, full LTE, no issues. Whatever the non-Verizon SIM does to the phone internal settings I have no idea, but I can tell you that it was not a fluke that your process worked. The exact same thing worked for me.
Hope this helps anyone else with the same issue - you need to install a non-Verizon SIM, get LTE going, and then put the Verizon SIM back in.
Thanks again.
JT
Click to expand...
Click to collapse
Hey is the 6p still working well for you? LTE? I been following ur steps but I don't have project fi and I used my friends att SIM to kinda reset the network and I also reset the network too but it went back to 3g and roaming. Any help would be awesome. I don't want to have to get a new phone
Sent from my [device_name] using XDA-Developers Legacy app
reply to divineazn716 (won't let me quote for some reason)
Hello. I have not had any issues with the 6P since posting this. I honestly can't explain why the method posted earlier works, there does not seem to be a visible change in the user accessible settings.... so i don't know if i can help you any further from a technical standpoint. I'm not sure why the Verizon SIM didn't fix it the 2nd time, in my case. Something to do with the internal calibration of the LTE antenna (i'm guessing).
If you're willing to go this far, a factory reset of the phone, then ATT SIM might be an option. I HAVE NO IDEA IF THIS WILL WORK, so take that advice with 'a grain of salt'. Something to consider if you don't mind resetting the phone but don't/can't get a Fi account.
I can say that it was worth the $30 to me for a Fi account since it fixed it, but maybe more importantly the knowledge that if it happens AGAIN I should be able to fix it.
I know that wasn't super helpful but that's been my experience since the post.
(unrelated, but since you're a 6P user you may find helpful, I had the dreaded early battery shut down and it got so bad it almost bricked my phone. I got a new battery by sending it to Huawei customer service and it works like a champ now. Better than when it was brand new, from a battery standpoint.)
j2t0621 said:
reply to divineazn716 (won't let me quote for some reason)
Hello. I have not had any issues with the 6P since posting this. I honestly can't explain why the method posted earlier works, there does not seem to be a visible change in the user accessible settings.... so i don't know if i can help you any further from a technical standpoint. I'm not sure why the Verizon SIM didn't fix it the 2nd time, in my case. Something to do with the internal calibration of the LTE antenna (i'm guessing).
If you're willing to go this far, a factory reset of the phone, then ATT SIM might be an option. I HAVE NO IDEA IF THIS WILL WORK, so take that advice with 'a grain of salt'. Something to consider if you don't mind resetting the phone but don't/can't get a Fi account.
I can say that it was worth the $30 to me for a Fi account since it fixed it, but maybe more importantly the knowledge that if it happens AGAIN I should be able to fix it.
I know that wasn't super helpful but that's been my experience since the post.
(unrelated, but since you're a 6P user you may find helpful, I had the dreaded early battery shut down and it got so bad it almost bricked my phone. I got a new battery by sending it to Huawei customer service and it works like a champ now. Better than when it was brand new, from a battery standpoint.)
Click to expand...
Click to collapse
Tea I bought a new battery on eBay for 10 and got it replaced and it's running awesome. Are you on a custom rom? Just wondering what else I can try to fix this. It's weird while on the att it worked fine with LTE. I'm thinking about getting a fi acct thought
Sent from my [device_name] using XDA-Developers Legacy app
I had this same exact issue... I'm on Verizon and I was running FireHound ROM, which I loved btw, but every time I restarted the phone/toggled airplane LTE would pop up for 30 seconds and I would be stuck on 3G. Huge bummer but I found this to be an issue on every current custom ROM. Defeated and abused I ended up returning to 100% stock, unrooted and locked bootloader, full LTE capabilities now. I did end up buying a new SIM which helped with some of the connectivity issues I was having before granted my original sim was cut twice and I had it for many many years. Try going 100% back to stock, replace your SIM(most places cost about $10) and you should be good to go. I can only chalk this up to be an issue with source provided to developers but I'm not sure where the discrepancy lies for DEVS that isn't consistent with a stock instal...
Tried all these ROMs:
FireHound
ABC
Resurrection Remix
DARK ROM
Cortex - Uneffected by the LTE issue but is a dead ROM as of now and is on a different vendor.
k1ll3ry0 said:
I had this same exact issue... I'm on Verizon and I was running FireHound ROM, which I loved btw, but every time I restarted the phone/toggled airplane LTE would pop up for 30 seconds and I would be stuck on 3G. Huge bummer but I found this to be an issue on every current custom ROM. Defeated and abused I ended up returning to 100% stock, unrooted and locked bootloader, full LTE capabilities now. I did end up buying a new SIM which helped with some of the connectivity issues I was having before granted my original sim was cut twice and I had it for many many years. Try going 100% back to stock, replace your SIM(most places cost about $10) and you should be good to go. I can only chalk this up to be an issue with source provided to developers but I'm not sure where the discrepancy lies for DEVS that isn't consistent with a stock instal...
Tried all these ROMs:
FireHound
ABC
Resurrection Remix
DARK ROM
Cortex - Uneffected by the LTE issue but is a dead ROM as of now and is on a different vendor.
Click to expand...
Click to collapse
I will give this a try this evening
Sent from my [device_name] using XDA-Developers Legacy app
bleh im back to stock unrooted and locked and my signal is still crap. i guess i have to buy a new phone.... =*( i loved this 6P
Sorry to hear that. I'm just running stock android.

Very Strange Sim Card Carrier Issues [Completely Lost On Whats Goin On]

So ive had sprint as a carrier and my same number and plan for goin on like 15 years almost. i had the oneplus 7 5g pro on sprint for a good while. Some dum things occurred and i ended up losing that phone. So a buddy gave my an sprint iphone 6 to use til i figured out what i was going to do next. [i cant stand iphone lol] well i surfed around and found the essential ph-1 on sale for less than a $100 from multiple sources. So i go ahead and purchase one. Phone gets here and i take my sim out of my iphone and put it into this essential phone and thats where stuff gets wierd for me. if i can even make it to the menu to try to do an profile update or anything the phone will start like flashing a few times crash to the homescreen and then restart. it loads up cannot load android system your data may be currupt. try again or factory data reset. if i press try again the phone boots up fine get to the homescreen and it starts it all again. crash, restart. when i have gotten to the menu i notice my sim is saying boost mobile. but that cant be right cus when i use it in my iphone or any other sprint phone for that matter sprint locks in fine and good service and all. also if i dp a factory data reset and have the sim in it will show that its trying to register the carrier and it will just crash sayung somethign about a sprint app force closing. and then states the sim card has locked
so i have no idea what is happening. ive tried downgrading and taking all the otas and everything and im still having no luck
let me kno what you all think
update.
i went into sprint thinking maybe it was because im on an iphone or something and the sim didnt want to play nice transferring to and android. but they tell me that my new essential is a boost mobile phone and they cant activate my sprint account on it. asked them could they just relock it to sprint n they said id have to call the hotline.
so if its just because the phone has been unlocked to work on boost mobile. what would i have to do to lock it back to sprint.]
any help would be awesome
thx

Categories

Resources