Database Users

Nexus S total network loss.

So my girlfriend's Nexus S has been losing the entire voice and data network and going into no service mode, no biggie at first, just cycle airplane mode, then it went on to rebooting because you would select airplane mode from the power off menu but it would not check the box in the wireless settings menu.
After the reboot the box would show checked and airplane mode could be disabled and the service would resume. The the phone started getting stuck in airplane mode and not even rebooting it would bring it out the first few times, then it got to the point of resetting the phone, a wipe cache/data reset didn't fixed it. So off to T-Mobile for a new sim card. Rebooted the network immediately. And as of last night its back in full force and now not even a new sim will resurrect the network.
Have tried wiping, reflashing stock 2.3.3, new sim again, multiple resets, had to get an toggle widget to get it out of airplane mode and still a dead network, all this time the network in the *#*#4636#*#* menu showing unknown and is not able to be changed and reverts back to unknown immediately, OEM specifics settings button is greyed out and you are not able to disable the radio either.
While I'm going to call Samsung on Monday and I guess send the phone off, I worry about mine because it too does it but only once a month or so, but I do constantly have issues resurrecting the phone from airplane mode at times because the box will not be checked in the wireless settings menu but I can see the airplane instead of network bars, problem persists with reboots sometimes.
I also would like to add that even when the box is not checked in the wireless settings menu for airplane mode, if you click it it just hangs forever and will try to select but never will and stays grey like its turning everything off, but if the scren goes off its like you never tried.
Has anyone else seen this? I have seen a lot of people with data network issues or having to reboot to get voice network back but nothing as bad as I'm experiencing.
Both our phones are and have been completely stock and unmodified.
Thankfully we still have her Vibrant and in case I need to send mine in my Nexus One.
Sent from my Xoom using XDA App

Have you tried restoring from another persons' pre-made nandroid backup?
This over-writes the radio firmware, you should give it a go!
I also found that I had problems on 2.3.3, however reverting to 2.3.2 gave me no problems!
Just contact me if you need any help restoring from a nandroid backup or finding the 2.3.2 backup files

cdaly985 said:
Have you tried restoring from another persons' pre-made nandroid backup?
This over-writes the radio firmware, you should give it a go!
I also found that I had problems on 2.3.3, however reverting to 2.3.2 gave me no problems!
Just contact me if you need any help restoring from a nandroid backup or finding the 2.3.2 backup files
Click to expand...
Click to collapse
Is that true? I am just on the verge of calling samsung. My phone won't connect to or display any available networks, and is pretty much now dumbed down to a small tablet. I've tried everything except another persons nandroid backup. I've been told to stay away from flashing another persons... but I'm really desperate.
If you could provide me with a backup, that would be awesome.

I'm having identical problem.
It was working fine yesterday, look back to it and now it's got no mobile network, nothing. Just the no bars and cross symbol. I've tried wiping dalvik cache, reflashing the radio, wiping data/factory reset, reflashing the rom, restoring with a backup (Backup of when I first rooted the phone) and still no signal. Nothing has worked..
Anyone got ideas on how to fix this issue?

Gawthorne said:
I'm having identical problem.
It was working fine yesterday, look back to it and now it's got no mobile network, nothing. Just the no bars and cross symbol. I've tried wiping dalvik cache, reflashing the radio, wiping data/factory reset, reflashing the rom, restoring with a backup (Backup of when I first rooted the phone) and still no signal. Nothing has worked..
Anyone got ideas on how to fix this issue?
Click to expand...
Click to collapse
Can you search for and view available networks?

This sounds like the CM7 powerwidget problem (3g/2g) I used it and I loss all network, phone process will crash every second, however if your phones are stock I can't think in anything causing it.
For CM7 you'll have to reflash and delete userdata or edit the sql database for the providers and change a value to 0, but you need root.
When I went to *#*4636.... my preferred service was "unknown" too, but now it is OK.

Try to dail:
*#*#4636#*#*
and find your network information.

ketchup539 said:
Can you search for and view available networks?
Click to expand...
Click to collapse
Nope. Sits their 'searching' but nothing shows up.
In, *#*#4636#*#*, it gives little to no information. Just says nothing for current network and for GSM disconnects it has,
Sate: DvInactiveState
disconnected with last try
at 9:59AM
fail because No Error
And that time never changes, stays at 9:59AM.
As my above post suggested, I've tried doing a factory reset and reflashing. I don't think I use CM.. I flashed with Oxygen 2.1.6 (using it's kernel) but I restored to Oxygen rom and trinity kernel after it didn't work.

Gawthorne said:
Nope. Sits their 'searching' but nothing shows up.
In, *#*#4636#*#*, it gives little to no information. Just says nothing for current network and for GSM disconnects it has,
Sate: DvInactiveState
disconnected with last try
at 9:59AM
fail because No Error
And that time never changes, stays at 9:59AM.
As my above post suggested, I've tried doing a factory reset and reflashing. I don't think I use CM.. I flashed with Oxygen 2.1.6 (using it's kernel) but I restored to Oxygen rom and trinity kernel after it didn't work.
Click to expand...
Click to collapse
That is the EXACT same problem I have. I too was using Oxygen 2.1.6 and lost all connectivity. I've just locked my bootloader and flashed back to stock ready to send for repairs. That rom must be doing something >.>

Oh no
I didn't want to send it back D:
Anyone got some suggestions that I haven't tried?

Gawthorne said:
Oh no
I didn't want to send it back D:
Anyone got some suggestions that I haven't tried?
Click to expand...
Click to collapse
I've been trying *everything* for last past few days. Nothing is working. That shouldn't stop you from trying though. Just stay well away from ODIN and those i9023 files, I've seen bad things.

ketchup539 said:
I've been trying *everything* for last past few days. Nothing is working. That shouldn't stop you from trying though. Just stay well away from ODIN and those i9023 files, I've seen bad things.
Click to expand...
Click to collapse
Cheers, going to a mates place soon to see if he has anything up his sleeves to try and fix this annoying issue..
If we somehow fix it, I'll be sure to post how we did here.

Gawthorne said:
Cheers, going to a mates place soon to see if he has anything up his sleeves to try and fix this annoying issue..
If we somehow fix it, I'll be sure to post how we did here.
Click to expand...
Click to collapse
Ok, it'd be great if you worked something out. I'm so glad i'm not the only person with this issue!

Anyone had any breakthroughs? *hopeful*

I wouldn't call it a breakthrough but I got somewhere!
Ended up putting a extremely thin piece of wire into the external antenna port at the back of the phone. Wasn't too keen on doing this, but my phone now has reception isn't stuck at the dreaded -113dbm.
The reception isn't good, but it's enough to send texts and have calls.
Although the area needs quite good reception for me to receive anything, and it's extremely sensitive. To get 3 bars in a place where I usually get full bars, I have to be outside. While inside it's reduced to none or 1 bar, which is enough to send/receive texts and a sort of lagging phone call (did a few tests). As mentioned before extremely sensitive. The phone seems to like it better when it's up-right. In the middle of the CBD at Brisbane I get full reception and 3G, which is fine but in the places where you usually get 2 bars, you get no signal at all, unless you're outside.
So this is hardly a fix. I will most likely be sending it to Samsung to get it actually fixed. Either that or get it fixed the same day and pay probably close to $100 so I don't have to wait 2 months waiting for Samsung to twiddle their thumbs.

Thats awesome! But I'm going to post mine off to Samsung USA tomorrow, which will take forever considering international shipping. Where could you get it fixed same-day? I'm going to try this wire thing

So it can't be a software issue, but maybe the rom overloaded the antenna and fried it or something? I'm glad we've got that far.

I've seen that nexus s has a problem like the iphone, the antenna gate. Try take the phone with the left hand looking to no touch the rear of the softkeys
Inviato dal mio Nexus S usando Tapatalk

RcrdBrt said:
I've seen that nexus s has a problem like the iphone, the antenna gate. Try take the phone with the left hand looking to no touch the rear of the softkeys
Inviato dal mio Nexus S usando Tapatalk
Click to expand...
Click to collapse
Its more serious than that my friend! Thanks anyway

I got a quote from a place in Brissy called "FixMyMobile" and they said if they can fix it, it will cost $99. Although I'll get quotes from different places (if I find them) and see what they charge however I don't think I will be able to get cheaper, most likely around the same price..
So I may do that to not wait the ridiculous time it will take to get it back from Samsung.. Not sure on places in NZ though.
Yeah it seems like a hardware issue definitely. I eventually reverted the phone back to stock everything and it still happened, so that there shouts hardware issue.

[Q] 4.2.2 update-can't make calls

Hi All,
I'm currently using Straight Talk with ATT SIM. Everything was working fine. I updated the software to 4.2.2 on Sunday. It didn't come OTA so I updated by going to Google Services Framework, clear data, then force stop. After a reboot, the OTA 4.2.2. showed up and I updated then.
Now, I am realizing that I cannot make or receive calls at all. Phone shows signal strength at 100% (4 bars) but when dialing, it does not go through, just silence, then a beep, then ends call.
I have tried rebooting phones, pulling SIM card out and replacing (twice) all with no luck.
HELP!!
Edit: I just realized I don't have internet connection either.

Larry216 said:
Hi All,
I'm currently using Straight Talk with ATT SIM. Everything was working fine. I updated the software to 4.2.2 on Sunday. It didn't come OTA so I updated by going to Google Services Framework, clear data, then force stop. After a reboot, the OTA 4.2.2. showed up and I updated then.
Now, I am realizing that I cannot make or receive calls at all. Phone shows signal strength at 100% (4 bars) but when dialing, it does not go through, just silence, then a beep, then ends call.
I have tried rebooting phones, pulling SIM card out and replacing (twice) all with no luck.
HELP!!
Edit: I just realized I don't have internet connection either.
Click to expand...
Click to collapse
Did you forget to pay the bill?
Sent from my Nexus 4 using xda app-developers app

What radio are you on?
Sent from my iPad 4

BigDig said:
Did you forget to pay the bill?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Haha. I wish it was that easy. No...account is current

mitchdickson said:
What radio are you on?
Sent from my iPad 4
Click to expand...
Click to collapse
Sorry for the newbie response but how can I find out what radio I am on?

Ah...found it.
Radio: 2.0.1700.48

I was on the same situation a couple days ago. after flashing 4.2.2, I can still make a call, people can still call me, but no sound from either me or them. The micros work fine (you can check by Voice Search).
At that time, after I ended messing everything up, I restocked the phone to 4.2.1. Everything worked fine after then. I dont know why this happens. You may wait for another solution. Just let you know that a restock can fix it, so dont worry. However I dont encounrage it becuase it wipes your phone completly.

opticaldh said:
I was on the same situation a couple days ago. after flashing 4.2.2, I can still make a call, people can still call me, but no sound from either me or them. The micros work fine (you can check by Voice Search).
At that time, after I ended messing everything up, I restocked the phone to 4.2.1. Everything worked fine after then. I dont know why this happens. You may wait for another solution. Just let you know that a restock can fix it, so dont worry. However I dont encounrage it becuase it wipes your phone completly.
Click to expand...
Click to collapse
Thanks for your reply. Yeah, I would like a solution that doesn't require complete wipe of phone.
So frustrating...been unable to use phone all day. Who knows how many calls I've missed.

Larry216 said:
Thanks for your reply. Yeah, I would like a solution that doesn't require complete wipe of phone.
So frustrating...been unable to use phone all day. Who knows how many calls I've missed.
Click to expand...
Click to collapse
In case you have no choice, back up your phone by Titanium backup. That saves everything you have at the moment

Same issue after 4.2.2 update
I'm having the exact same issue with my Nexus 4. Let me elaborate. I've had my Nexus 4 since the initial sale, today I got the OTA update sent via Tmobile. My phone seemed to work fine afterwards until I tried to answer a call. Upon attempting to answer or make a call (even with full service) the bars instantly drop to zero (hollow triangle) and an out-of-area tone & message display.
Restarted, pulled sim, sim worked fine in other phone, checked & rechecked APN/other settings, had Tmobile "reset" my device on network, finally wiped my device. I still can not make or receive phone calls. The radio seems to just disconnect when attempting to.
Spoke with Tmobile customer support (worthless), Tech Care (Very helpful & knowledgeable but no fix), Google Nexus support (Offered to replace device! However can't have any cosmetic damage). LG also contacted but zero assistance given.
I'm stumped, it seems to me that this issue might be related to the update disabling the LTE radio, because data & everything else works except for making calls. Like I said, Google offered to replace the device however I did (in good faith) advise them of a hairline crack on the back of the device, like many other N4 owners have had, not from a drop. Upon hearing of cosmetic damage they said that it's no longer their liability. I'm very disappointed but I understand.
Since the warranty is void from the crack, I'm going to root & play around.
Any questions or advice?
---------- Post added at 08:10 PM ---------- Previous post was at 07:44 PM ----------
Also, I'm on the same radio (Baseband?) as OP.
Radio: 2.0.1700.48

I'm curious to see if rooting will solve this issue. If yes, I will go this route.
Keep me posted. So frustrated.
Thanks johnmedic.

[Q] S4 - disconnecting from network and not reconnecting again

Hi all,
Regular reader but hardly ever post!
I have a Galaxy S4 (GT-I9505) - with Android 4.4.2. Unrooted.
Purchased and used in Singapore on the Starhub network since around October 2013. Everything was working fine until approx Feb or March when the latest Android version, 4.4.2 got rolled out.
Ever since then I am experiencing regular disconnections from the network. But the phone does not re-connect back to the network again, the only fix is to restart the phone.
These disconnections are often once or twice a day, and are very frustrating because if I don't notice it, I may be off the network for hours before noticing it - and are therefore missing out on calls emails etc etc.
This only happened after the Android 4.4.2 got rolled out, so I am pretty confident this is the cause of the problem.
What I tried myself to fix:
- restore APN's back to default state
- Factory reset (both via settings, and via boot screen)
What I have been able to narrow down troubleshooting, is:
- Disconnects seem to only happen when Network Mode is "LTE/WCDMA/GSM (auto connect)"
- If I use network mode "WCDMA/GSM (auto connect)" the disconnections have not happened (yet!)
- When the disconnection does happen in the first mode, I cannot manually change the network mode. The radio buttons are greyed out, and if I try to select "WCDMA/GSM auto connect" the request times out (I forget the exact message - it does respond to the tap but then nothing happens)
So it seems to me this is some sort of software bug/fault introduced with Android 4.4.2 that affects 4G connections.
After that, I have taken it to Samsung for warranty service. I have now had 4 visits to them and they have not been able to fix it yet. This is what they have done so far:
- First visit - factory reset (despite telling them I already did that) - did not fix
- Second visit - checked hardware and replaced mainboard. Did not fix.
- Third visit - checked hardware again and factory reset again. Did not fix.
- Fourth visit - who knows. I think same as visit three but done via a Service Manager instead of staff, Did not fix.
When I first called them back in Feb or March, they said it was a "known Issue' and sugegsted to "wait for a patch". However since visiting them, they said the known issue was only with Note 3's (not with S4's) and replacing the mainboard on the Note 3's fixed the problem. In my case replacing the mainboard - twice - has not fixed it.
I'm getting very annoyed with Samsung who seem to just be trying the same thing each time and are not fixing it. Staying in 3G only mode is a workaround but not an acceptable solution.
Now they've asked me to take if back again - for a 5th time.
Beginning to wish I had never bought the S4, or at least never got Android 4.4.2.
So I thought I would turn to here for help instead, I think you guys and gals probably know more than the Samsung service staff!
Any suggestions?
By the way, I don't run any memory/battery saver apps. I do run one data usage monitoring app that I thought perhaps was conflicting, so I tried not installing it after one of the resets, but the problem continued.

Chikara71 said:
Any suggestions?
Click to expand...
Click to collapse
you CAN try other modem flash, but be careful with your warranty.
I do not know about the warranty conditions in your country, but in EU normally 3 unsuccessful repairs = phone refund or replacement.

I would try reflashing stock file or just flash a different modem

Hello, just like you i have been reading the post but never posting because i just came here to learn, nothing to share from this side...sorry.
But i am having the same problem as you. I bought my phone in Switzerland on march 2013 but i live in Uruguay. I was just thrilled with my s4 until the 4.4.2 update came out. My connection keeps on crashing and it doesnt matter if its on 4g or 3g just make me miserable all day. Only the two of us is having this type of problem??
I believe is some kind of issue with the new bootloader i just updated with a patched rom that came for Germany last week (the one with kids mode) the phone work fine for a hours and then crashes, so this update didnt work. I have also flashed very differents official roms and modems but nothin seem to affect the problem.
I have another problem even though my s4 is 4g i cant connect to 4g network, every configuration is fine i just cant connect, any thougths??
Thank you very much.
Sorry for my english.

Dial *#1234# and paste here what appears.

Joku1981 said:
Dial *#1234# and paste here what appears.
Click to expand...
Click to collapse
AP: I9505XXUFNBE
CP: I9505XXUFNBE
CSC: I9505OLBFNB3
I should add, I took it in *again* to Samsung, to the Service Manager. Said they would replace the antenna and try that, which they did.
Still have the same problem though.
Not sure who to believe, Samsung are starting to run out of ideas and starting to say it may be a network issue. But if the network is down, then the phone should automatically reconnect once the network is back available again. And it doesn't.
I'm convinced it's a bug introduced with KitKat, as the problem only started then, but of course I cannot prove it...

felgrab said:
Hello, just like you i have been reading the post but never posting because i just came here to learn, nothing to share from this side...sorry.
But i am having the same problem as you. I bought my phone in Switzerland on march 2013 but i live in Uruguay. I was just thrilled with my s4 until the 4.4.2 update came out. My connection keeps on crashing and it doesnt matter if its on 4g or 3g just make me miserable all day. Only the two of us is having this type of problem??
I believe is some kind of issue with the new bootloader i just updated with a patched rom that came for Germany last week (the one with kids mode) the phone work fine for a hours and then crashes, so this update didnt work. I have also flashed very differents official roms and modems but nothin seem to affect the problem.
I have another problem even though my s4 is 4g i cant connect to 4g network, every configuration is fine i just cant connect, any thougths??
Thank you very much.
Sorry for my english.
Click to expand...
Click to collapse
Sounds very similar to my problem, that it just started with Kitkat only. I'm sure it can't be just us two having this problem! I don't have anything special or different installed on my phone, and it's too suspicious that it was working fine, 100% perfectly until the KitKat software came out...

Joku1981 said:
Dial *#1234# and paste here what appears.
Click to expand...
Click to collapse
AP: I9505XXUGNE5
CP: I9505XXUGNE5
CSC: I9505OXAGNE5
Thank you so much for giving us a hand!!
Chikara71:
I know it just cant be the two of us from such diferent places in the world but, i just cant find any similar in any post or google. It has been almost 3 months from the update an me using another phone...

Well I thought I would post again to close the loop.
After Samsung tried 5 times to fix my phone, checking hardware and trying to reinstall the OS with no luck, they suggested I try replacing my SIM card.
Surprise surprise, it has fixed the problem with no recurrence yet after a week so far.
I still don't understand how the sim card could be the problem, especially as my phone was working perfectly right up to the Kitkat software update. All I can assume is somehow KitKat either had an incompatibility with my simcard (maybe the new sim is technically slightly different?) or maybe KitKat somehow changed something on the simcard, if that's even possible.
Interestingly, I did contact my telco first, and they told me to contact Samsung. As it turned out, the fix was in the control of the telcom right from day one.
Anyway, so far the problem is resolved, so I thought I would post this here to help anyone that may have this problem.

Factory t-mobile S7e losing mobile network connectivity

so this is the second S7e and second SIM that I have been having this issue with. The phone will lose connection to the mobile network and the ONLY way to recover is to reboot phone. Reset Network Settings doesn't do anything. Toggle airplane mode doesn't do anything. Search for Network Operators doesn't do anything. I have a third phone on the way - but has anyone around here heard of or experienced similar? Am I missing something that I should be doing to correct this?
Thanks in advance

I too have this problem. Got a replacement refurbished phone under warranty and the phone has this problem

krishelnino said:
I too have this problem. Got a replacement refurbished phone under warranty and the phone has this problem
Click to expand...
Click to collapse
Did you pay the $20? I didnt want to pay the 20 so i sent the device to samsung. Should get it back friday or monday. The issue is definitely phone related. Im using a verizon s7 now and no issues like that arose. I even tried new sim.. My father is having same issue t-mobile s7 edge

Yes i had to pay 20. And it's disappointing I am having this issue with the replacement phone. I am having this problem on the U firmware as well.
Sent from my SM-G935U using Tapatalk

I've suffered the same issue from time-to-time and just do a restart....annoying as hell to be honest

Are you guys always in the same location when this is happening or is it just whenever and wherever? Or is it happening a one certain place where cell signal isn't that great? I had this same issue BUT only in my house so I had to get a network range extender from t-mobile to use at home.

This happens to me all the time. It's so annoying. At work, in the car, at home--it doesn't matter where I am. Have reset firmware multiple times and even rolled back once too. I think it has to do with the latest software because I never had this issue before the Fall/Winter. Hopefully Nougat fixes this!

Quickvic30 said:
Are you guys always in the same location when this is happening or is it just whenever and wherever? Or is it happening a one certain place where cell signal isn't that great? I had this same issue BUT only in my house so I had to get a network range extender from t-mobile to use at home.
Click to expand...
Click to collapse
I happens randomly in different places. For me i lose complete signal, and then only get back signal without data. I have to restart when this happens to get back data. Annoying as hell !

frappe33 said:
so this is the second S7e and second SIM that I have been having this issue with. The phone will lose connection to the mobile network and the ONLY way to recover is to reboot phone. Reset Network Settings doesn't do anything. Toggle airplane mode doesn't do anything. Search for Network Operators doesn't do anything. I have a third phone on the way - but has anyone around here heard of or experienced similar? Am I missing something that I should be doing to correct this?
Thanks in advance
Click to expand...
Click to collapse
I am having the same problem, this will be my 3rd phone 4th sim. I wish I knew how to fix it

I would try flashing different radios/modems, its worth a shot. Maybe try flashing the "U" firmware radios.

Nougat will fix it
My wife and I had the same issue on our tmobile s7 edge ... we got the 7.0 beta and now the issue is gone .... I bet it's radio and software related ... 7.0 will be out by the end of the month hope that helps...

I had this issue with my phone, and it was a huge pain. The biggest concern: I didn't know when my phone was off network (voice, data, etc.). The fix, for me, was simple: a new SIM card.

You may have an issue from a rejected permission on an app.
Had the same issue before but I did a hard reset and realised that I changed permissions on an app that wasn't written for 6.1.

ronstopable12 said:
My wife and I had the same issue on our tmobile s7 edge ... we got the 7.0 beta and now the issue is gone .... I bet it's radio and software related ... 7.0 will be out by the end of the month hope that helps...
Click to expand...
Click to collapse
I hope so! Been waiting for that before I try anything drastic, even though this issue is a huge pain in the ass. I'm glad others have come out of hiding to express their concerns with it as well. I thought I was the only one for the longest time having this issue.
---------- Post added at 02:20 PM ---------- Previous post was at 02:19 PM ----------
jimfun said:
I had this issue with my phone, and it was a huge pain. The biggest concern: I didn't know when my phone was off network (voice, data, etc.). The fix, for me, was simple: a new SIM card.
Click to expand...
Click to collapse
Many of us have tried new SIM cards, but it's worth a shot if it's still not working consistently after Nougat is released.
---------- Post added at 02:22 PM ---------- Previous post was at 02:20 PM ----------
geeserver said:
You may have an issue from a rejected permission on an app.
Had the same issue before but I did a hard reset and realised that I changed permissions on an app that wasn't written for 6.1.
Click to expand...
Click to collapse
My and my friend's phones are both running pure 100% OEM Tmo stock without any apps disabled or touched at all and we have this issue and have done multiple resets. Pretty sure it's an actual hardware defect, or hopefully just a software one with the modem/radio.

krishelnino said:
Yes i had to pay 20. And it's disappointing I am having this issue with the replacement phone. I am having this problem on the U firmware as well.
Sent from my SM-G935U using Tapatalk
Click to expand...
Click to collapse
I was thinking about going that route. But I wasnt sure what condition the phone would be. How was you condition?
I sent mine to samsung and the things they replaced is the Coaxle cable "antenna" replaced 3 of them. I have been using the s7 from verizon on the U firmware so havent seen if it is fixed.

4ringsa6 said:
I was thinking about going that route. But I wasnt sure what condition the phone would be. How was you condition?
I sent mine to samsung and the things they replaced is the Coaxle cable "antenna" replaced 3 of them. I have been using the s7 from verizon on the U firmware so havent seen if it is fixed.
Click to expand...
Click to collapse
I received a refurb. Other than this problem, the phone is alright. I noticed this problem on receiving the phone it was running on T firmware. Then I switched to U firmware and radio but no difference. I called customer support yesterday, they said to go to a retail store to get the phone replaced. My worry is going through this process again and if I receive a bad device again what to do? After all refurb phones are like playing Russian roulette!
Sent from my SM-G935U using Tapatalk

I just had this start happening on mine... I really wish they would release nougat already. It is ridiculous they won't post an Odin flashable version of the release candidate if it does indeed fix the issue.
I also think its a specific tower configuration that is causing the issue that the radio can not understand. (Maybe 3xCA). Its happening in the same areas every time.

I just started having this problem in the past month. All at once I've been getting BT sometimes turning off, mobile networks failing to reconnect after I visit a no/low signal area (such as after a plane trip when the phone was in airplane mode). I've also seen wifi mode fight my attempts to turn it back on sometimes - toggling itself on and off a couple of times per second until I poke at enough settings to stop it. When BT turns itself off I have trouble turning it back on, sometimes it just goes back on, sometimes it refuses after a number of tries and if I wait an hour it goes back on just fine.
The folks at a BB Samsung kiosk said they could reflash it if I wanted to go that route, but that the nougat release would be out soon so it might be better to just wait for that. Has anyone had a Samsung rep re-image their phone to try to solve this?

flarbear said:
I just started having this problem in the past month. All at once I've been getting BT sometimes turning off, mobile networks failing to reconnect after I visit a no/low signal area (such as after a plane trip when the phone was in airplane mode). I've also seen wifi mode fight my attempts to turn it back on sometimes - toggling itself on and off a couple of times per second until I poke at enough settings to stop it. When BT turns itself off I have trouble turning it back on, sometimes it just goes back on, sometimes it refuses after a number of tries and if I wait an hour it goes back on just fine.
The folks at a BB Samsung kiosk said they could reflash it if I wanted to go that route, but that the nougat release would be out soon so it might be better to just wait for that. Has anyone had a Samsung rep re-image their phone to try to solve this?
Click to expand...
Click to collapse
If you were able to fix without a reboot you didn't have the same issue as this.

rocket31337 said:
If you were able to fix without a reboot you didn't have the same issue as this.
Click to expand...
Click to collapse
I guess I wasn't clear about that as I have several problems that are probably related, but behave a little differently.
BT dropping - can usually turn it back on, but sometimes it refuses. Usually don't need to reboot to fix this.
Wifi dropping - often have trouble turning it back on and have seen the widget toggle off and on repeatedly by itself. Sometimes have to reboot to fix that.
Mobile Network data (and voice sometimes) dropping - usually have to reboot. I think I may have recovered that once without a reboot, but the other few times it's happened in the past month since it started I have rebooted and that fixed it in all but one of the reboots - one time I rebooted and still had to fiddle with it a bit after the reboot before it came back. That may have been because I played too much with the network settings before the reboot and so had to undo that damage after the reboot. But, definitely rebooting is a fairly reliable step in fixing this problem.
All 3 started happening around the same time which is why I thought it was a software issue (I remember a small update a little over a month ago, but forget the details of it). It's nice to hear that others also have the mobile network problem, but if that is isolated in those cases then maybe I'm not seeing exactly the same problem. But, it is clear that rebooting is almost always required to get my mobile network data back so that again suggests that at least that part is the same as what this thread is discussing.
In looking at the T-Mobile updates page for the S7 Edge I see that the version I have (G935TUVU4APK1) was updated in early November - which tracks when I started having problems, and it includes a fix for "Domestic data roaming improvements", which definitely sounds like they may have played with the radios.
I am so ready for the Nougat update...

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.