Related
Hello All,
Something changed in my phone and not really sure as to what has happened. All of a sudden my phone loses data connectivity and thinks that it is roaming. If I enable airplane mode and disable it, then the phone works for about 10-15 minutes and then loses connectivity again. Running the 12B baseband (been using it for months with no issue) and haven't changed the ROM in quite some time. This started happening on yesterday.
Any suggestions?
The 4G radio seems to have crapped out completely. Getting a replacement sent on tomorrow
Optimus124 said:
The 4G radio seems to have crapped out completely. Getting a replacement sent on tomorrow
Click to expand...
Click to collapse
Damnit. I am having the EXACT same problem, running CM11.
How did you come to that conclusion? I am thinking I'm going to have to restore to stock if I'm going to get Verizon to do anything about it.
EtherBoo said:
Damnit. I am having the EXACT same problem, running CM11.
How did you come to that conclusion? I am thinking I'm going to have to restore to stock if I'm going to get Verizon to do anything about it.
Click to expand...
Click to collapse
I reverted all the way back to 11A stock unrooted. The phone was in 4G for about 5 minutes (if that) and then remained in 3G mode.
Optimus124 said:
I reverted all the way back to 11A stock unrooted. The phone was in 4G for about 5 minutes (if that) and then remained in 3G mode.
Click to expand...
Click to collapse
I'm at the same point. Going to do an Asurion claim since I didn't buy my phone from VZW (Swappa).
I had this problem before when I tried other roms like cm rom and omni rom. I tried to do *228 to fix problem, but made it made it worse. I restored it back to stock and took it to the Verizon store. They put a new sim card in it for free and it fixed the problem. Now i am running stock with simple kernel.
Same exact problem here. I was on the phone with Verizon last night. I was running cloudy pro 2 (all his roms for that matter as they are international roms) and kept getting the roaming issue you speak of...with 3g. I went back to 11A completely bone stock. Just like you mentioned, I get 4g but then after like 10 minutes I get 3g with roaming. Of course this is after I spent 30 minutes on the phone with tech support. They 'zapped' my sim card and it appeared to work but no dice. Now before doing all this I downloaded build prop editor and changed the ro.build.target_country to US versus COM as everyone suggested in all the forums, still no dice. I've tried the toggle airplane mode trick...works for like 5 minutes and back to 3g roaming. I think maybe a new sim card and avoid international roms...bummer because cloudys roms are blistering fast. Interesting thing though, I installed xdabebbs rom and malladus' rom, after already running cloudys roms, and get 3g but no roaming. I also verified that Verizon wasn't throttling me or something like that. One more thing I tried is reflashing the basebands and 24A modem, no dice. If there is a build prop fix or some other fix I'd love to hear it.
Edit: One think I'd like to mention. When I had an S4 I switched between stock roms and AOSP roms and the network settings were responsible for causing the roaming because the stock rom was an older build than the AOSP. So when I had roaming, I'd reflashed the AOSP rom, changed the settings then flash the stock rom. It worked great.
Edit#2: Ok making a little progress. Just did this:
Get a build.prop editor from the play store, and change ro.carrier to VZW and ro.build.target_operator to VZW and ro.build.target_country to US.
Initially it worked but when I make calls it gives me Unfortunately, the process com.android.phone has stopped and I cant make calls. I went into Settings, Apps, reset app preferences...that didn't fix it either.
4G/LTE is pretty solid now but again, I cant make calls.
Edit#3: Nevermind...roaming again.
Alright, I'd be lying if this makes any sense to me, but the issue appears to be related strictly to the SIM card.
I had them swap the SIM, it fixed the issue, then it came back. I'm on a new phone now, and it appears to be working. The old SIM did not work on either phone, but the new one does. What makes no sense is the old SIM would work fine in my Galaxy Nexus, but would not work in the G2. Now the new SIM is working perfectly in the new G2 (haven't tried the old one).
I'm baffled.
I've never seen anything make so little sense. The guy at the store told me I would need to replace the SIM again in a few days. Whatever, if it happens again, I'll do just that.
I did the same with my gs3. What ROM are you running?
Sent from my VS980 4G using Tapatalk
The original phone was running CM 11 Nightlies.
I'm currently on stock - not sure if I'm going to stay with CM because the official thread indicates official development is DitW for the G2 .
That's actually strange... I'd expect roaming issues with an Intl ROM but not cm.
Sent from my Nexus 7 using Tapatalk
My phone out of nowhere started doing this really fun thing where it drops to roaming at random. From what I can tell, the phone is not making a handoff to the next tower to avoid the roaming. For example, if I'm sitting under a tower with full 4G, everything is fine. If I have 2 bars, it will work in 4G for a while before dropping to 3G roaming. I am able to force it back into 4G by dropping in and out of Airplane mode.
I'm running the official CM11 4/30 nightly (I was on the March Snapshot until this started happening).
First I used some Google-Fu and found it's most likely a bad SIM. I swapped SIMs with my wife, she was stuck in 3G roaming, awesome! Went to Verizon, the switched the SIM, all good, right? Nope, I didn't notice it right away, left the store and thought all was good until I needed to use internet at work.
Next, I thought it was software, so I created a backup, and dirty installed the newest CM11 nightly. No change, so I did a full wipe and install. No luck.
So next I thought maybe the radio was corrupted, so I tried to update the radio, which didn't go so well. I got stuck in a boot loop and had to sideload the old driver and reflash. So I'm back up but still having this problem. I'm thinking my only thing I can do at this point is to go to stock and see if the updated radios make a difference.
I saw another guy is had the same problem, but he had his phone replaced. I'm not sure if that will work for me since I purchased via Swappa (I do have Asurion insurance though).
So what help do I need?
1) Does anyone have any ideas on what I can do to fix this?
2) Are there any good instructions out there for how to flash to stock?*
3) Are there any good instructions on how to re-root and flash back to a custom ROM once taking the newest OTA?*
*Most of the instructions I've found have been pretty confusing and use a lot of acronyms without explaining them. I'd be willing to write some cleaner instructions for a sticky if someone would be willing to help me out with any questions I have.
Thanks everyone, I appreciate any help offered.
EtherBoo said:
My phone out of nowhere started doing this really fun thing where it drops to roaming at random. From what I can tell, the phone is not making a handoff to the next tower to avoid the roaming. For example, if I'm sitting under a tower with full 4G, everything is fine. If I have 2 bars, it will work in 4G for a while before dropping to 3G roaming. I am able to force it back into 4G by dropping in and out of Airplane mode.
I'm running the official CM11 4/30 nightly (I was on the March Snapshot until this started happening).
First I used some Google-Fu and found it's most likely a bad SIM. I swapped SIMs with my wife, she was stuck in 3G roaming, awesome! Went to Verizon, the switched the SIM, all good, right? Nope, I didn't notice it right away, left the store and thought all was good until I needed to use internet at work.
Next, I thought it was software, so I created a backup, and dirty installed the newest CM11 nightly. No change, so I did a full wipe and install. No luck.
So next I thought maybe the radio was corrupted, so I tried to update the radio, which didn't go so well. I got stuck in a boot loop and had to sideload the old driver and reflash. So I'm back up but still having this problem. I'm thinking my only thing I can do at this point is to go to stock and see if the updated radios make a difference.
I saw another guy is had the same problem, but he had his phone replaced. I'm not sure if that will work for me since I purchased via Swappa (I do have Asurion insurance though).
So what help do I need?
1) Does anyone have any ideas on what I can do to fix this?
2) Are there any good instructions out there for how to flash to stock?*
3) Are there any good instructions on how to re-root and flash back to a custom ROM once taking the newest OTA?*
*Most of the instructions I've found have been pretty confusing and use a lot of acronyms without explaining them. I'd be willing to write some cleaner instructions for a sticky if someone would be willing to help me out with any questions I have.
Thanks everyone, I appreciate any help offered.
Click to expand...
Click to collapse
Get anywhere? I'm experiencing the same. Roaming all the time. Going to revert back to stock 12b and see what happens.
dr_w said:
Get anywhere? I'm experiencing the same. Roaming all the time. Going to revert back to stock 12b and see what happens.
Click to expand...
Click to collapse
I'm fairly certain it's hardware. I spent a day using my Galaxy Nexus - full 4G the entire day.
I went back to stock, "bricked" my phone about 3 times doing it (quotes because it was salvageable, but I had a couple hours where I was googling like a madman worried I dun ****ed up). Stock and the new radios made no difference. In fact, with stock it would only go to 4G if I restarted it - airplane wouldn't even bring 4G back. Figure that one out.
I went to the VZW store and I'm basically screwed. I can call LG and see if they'll replace it or use Asurion. Since I got the device off Swappa, they cannot replace it. They tried to order me a new one, but the system wouldn't let them. I don't really have time to call LG, so I'm probably going to Asurion it. Their process is stupid simple to do and they'll have a phone to me the next day. Then I can spend all day tinkering with it and getting CM11 back on, which I feel like I'm an expert at right now.
Sorry, wish I had better news. If you got the device from VZW, go to the store after flashing to stock. They might want to try swapping your SIM first though, so make sure you go to a store that has decent 4G coverage in its surrounding area.
EtherBoo said:
I'm fairly certain it's hardware. I spent a day using my Galaxy Nexus - full 4G the entire day.
I went back to stock, "bricked" my phone about 3 times doing it (quotes because it was salvageable, but I had a couple hours where I was googling like a madman worried I dun ****ed up). Stock and the new radios made no difference. In fact, with stock it would only go to 4G if I restarted it - airplane wouldn't even bring 4G back. Figure that one out.
I went to the VZW store and I'm basically screwed. I can call LG and see if they'll replace it or use Asurion. Since I got the device off Swappa, they cannot replace it. They tried to order me a new one, but the system wouldn't let them. I don't really have time to call LG, so I'm probably going to Asurion it. Their process is stupid simple to do and they'll have a phone to me the next day. Then I can spend all day tinkering with it and getting CM11 back on, which I feel like I'm an expert at right now.
Sorry, wish I had better news. If you got the device from VZW, go to the store after flashing to stock. They might want to try swapping your SIM first though, so make sure you go to a store that has decent 4G coverage in its surrounding area.
Click to expand...
Click to collapse
Thanks dude. I think you are right, flash stock and get a new sim first. I have a hard time believing its a hardware problem. I just wrote this in the other post about roaming:
"Same exact problem here. I was on the phone with Verizon last night. I was running cloudy pro 2 (all his roms for that matter as they are international roms) and kept getting the roaming issue you speak of...with 3g. I went back to 11A completely bone stock. Just like you mentioned, I get 4g but then after like 10 minutes I get 3g with roaming. Of course this is after I spent 30 minutes on the phone with tech support. They 'zapped' my sim card and it appeared to work but no dice. Now before doing all this I downloaded build prop editor and changed the ro.build.target_country to US versus COM as everyone suggested in all the forums, still no dice. I've tried the toggle airplane mode trick...works for like 5 minutes and back to 3g roaming. I think maybe a new sim card and avoid international roms...bummer because cloudys roms are blistering fast. Interesting thing though, I installed xdabebbs rom and malladus' rom, after already running cloudys roms, and get 3g but no roaming. I also verified that Verizon wasn't throttling me or something like that. One more thing I tried is reflashing the basebands and 24A modem, no dice. If there is a build prop fix or some other fix I'd love to hear it.
Edit: One think I'd like to mention. When I had an S4 I switched between stock roms and AOSP roms and the network settings were responsible for causing the roaming because the stock rom was an older build than the AOSP. So when I had roaming, I'd reflashed the AOSP rom, changed the settings then flash the stock rom. It worked great. "
Edit#2: Ok making a little progress. Just did this:
Get a build.prop editor from the play store, and change ro.carrier to VZW and ro.build.target_operator to VZW and ro.build.target_country to US.
Initially it worked but when I make calls it gives me Unfortunately, the process com.android.phone has stopped and I cant make calls. I went into Settings, Apps, reset app preferences...that didn't fix it either.
4G/LTE is pretty solid now but again, I cant make calls.
Edit#3: Nevermind...roaming again.
dr_w said:
Thanks dude. I think you are right, flash stock and get a new sim first. I have a hard time believing its a hardware problem. I just wrote this in the other post about roaming:
"Same exact problem here. I was on the phone with Verizon last night. I was running cloudy pro 2 (all his roms for that matter as they are international roms) and kept getting the roaming issue you speak of...with 3g. I went back to 11A completely bone stock. Just like you mentioned, I get 4g but then after like 10 minutes I get 3g with roaming. Of course this is after I spent 30 minutes on the phone with tech support. They 'zapped' my sim card and it appeared to work but no dice. Now before doing all this I downloaded build prop editor and changed the ro.build.target_country to US versus COM as everyone suggested in all the forums, still no dice. I've tried the toggle airplane mode trick...works for like 5 minutes and back to 3g roaming. I think maybe a new sim card and avoid international roms...bummer because cloudys roms are blistering fast. Interesting thing though, I installed xdabebbs rom and malladus' rom, after already running cloudys roms, and get 3g but no roaming. I also verified that Verizon wasn't throttling me or something like that. One more thing I tried is reflashing the basebands and 24A modem, no dice. If there is a build prop fix or some other fix I'd love to hear it.
Edit: One think I'd like to mention. When I had an S4 I switched between stock roms and AOSP roms and the network settings were responsible for causing the roaming because the stock rom was an older build than the AOSP. So when I had roaming, I'd reflashed the AOSP rom, changed the settings then flash the stock rom. It worked great. "
Edit#2: Ok making a little progress. Just did this:
Get a build.prop editor from the play store, and change ro.carrier to VZW and ro.build.target_operator to VZW and ro.build.target_country to US.
Initially it worked but when I make calls it gives me Unfortunately, the process com.android.phone has stopped and I cant make calls. I went into Settings, Apps, reset app preferences...that didn't fix it either.
4G/LTE is pretty solid now but again, I cant make calls.
Edit#3: Nevermind...roaming again.
Click to expand...
Click to collapse
Alright, so, I have some interesting news.
I got a replacement device from Asurion - not just a replacement, a brand new device out of the box. I pulled it out of the box, swapped the SIM, same exact issue .
I went to Verizon and *****ed up a storm. They basically said "you bought it on eBay, not our problem" (I actually did Swappa - but they don't know Swappa and they do know eBay).
So I got the guy in the store to do some digging, and apparently Verizon has a point opened up with LG as they're seeing this on more and more devices - especially since KK came out. So I figured I could try an older radio. The device was on 12B when it arrived. I just flashed stock to 10B and it's the same issue. I don't know what's going on at this point - nothing makes sense but its apparently a known issue that's been appearing since the KK update.
I'm going to call Asurion and request a new device again since this one is doing the same thing, we'll see what happens. I'm still leaning towards hardware and thinking there was a slew of bad radios that went out.
Just for giggles - and I have no reason whatsoever to think this will work. I'm going to swap out the new SIM that came with the phone. Originally, I just put in my old SIM since the new one was taking too long to activate. I'm having the exact same issue I had previously. With that, I'm going to leave the new SIM in and see if it has the same dropping issue. The guy in the store had mentioned he could swap out the SIM but after a few days it will crap out again... which makes zero ****ing sense. Because of that, I might as well see what happens if I pop a new SIM in. While again, this makes 0 sense, I'm wondering if maybe the phone is frying the SIM somehow?
Again, it makes no sense at all, but I have nothing else left to try other than getting Asurion to repeatedly send me phones until I find one that works or they replace for another type of phone (which I REALLY don't want). I'll drop an edit in an hour or so if what I try makes a difference.
Quick Edit:
I COULD just keep going to the VZW store and have them repeatedly swap out SIMs since it will fix it for a few days .
EDIT:
Got the new SIM installed and it's working. The guy in the VZW store told me that we can keep swapping SIMs and the same issue will happen, which again, makes no sense to me. I'm at a bit of a loss to be honest. I wonder if it's possible that my old device was frying the SIMs (again, makes no sense) and that maybe the new SIM not going in my old device will fix the issue.
What ROMs are you running? A phone frying a Sim does not sound likely at all. I got my new sim card and have been running xdabebbs ROM with no network issues. I feel like my issues stemmed from the Intl ROMs.
Sent from my Nexus 7 using Tapatalk
dr_w said:
What ROMs are you running? A phone frying a Sim does not sound likely at all. I got my new sim card and have been running xdabebbs ROM with no network issues. I feel like my issues stemmed from the Intl ROMs.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
The only ROM I've ever run was CM11.
Same thing happened on stock though after flashing through the LG Flash Tool. Then, with the new phone from Asurion, used old SIM - 3G only. Used new SIM - 4G sticks.
Hello,
I just retired my venerable Samsung T699 Relay 4G (RIP QWERTY Keyboard) and, just picked up an unlocked, "refurbished" AT&T Note 3 for pretty cheap (it was sold as an "International" model, so I didn't know it was an AT&T version until I got it). I've had T-Mobile service for the last couple of years, and the big draw, for me, is WiFi calling/SMS; I've installed SafeStrap and been trying some T-Mobile ROMs, but can't seem to get WiFi calling to work. Obviously I've got a T-Mobile SIM card, and I've tried changing/adding APNs, and installing different builds of KitKat (some of which won't even boot - NB4 and NF9 seem to work best), but I still can't get it to work properly. I've been racking my brain and searching the Interspace for the last two weeks with no luck... what am I missing? Is it even possible?
Thanks in advance!
Hello,
As a fellow N900A user on Tmobile, I have been trying to get wifi calling as well.
I tried using a tmobile stock rom with wifi calling baked in (tweaked), but that did not work. I was told that I need to add an emergency 911 address, but even doing this did not do it.
I would think that wifi calling is doable, but something tells me that tmobile might be doing something similar to Verizon. Rumor was that Verizon had a list of IMEIs, and if your IMEI was not on their list, you couldn't bring the phone over to Verizon, even if it were CDMA capable (once again, this is rumor as I cannot confirm this is true).
The closest I have been to getting wifi calling through tmobile was having the settings show on the stock tmobile rom, but that was about it. Maybe someone in the forums has an answer/got it working, but I have yet to see one. I'll keep you posted if I somehow get it to work, but something tells me this won't happen for a while.
AresRising said:
Hello,
I just retired my venerable Samsung T699 Relay 4G (RIP QWERTY Keyboard) and, just picked up an unlocked, "refurbished" AT&T Note 3 for pretty cheap (it was sold as an "International" model, so I didn't know it was an AT&T version until I got it). I've had T-Mobile service for the last couple of years, and the big draw, for me, is WiFi calling/SMS; I've installed SafeStrap and been trying some T-Mobile ROMs, but can't seem to get WiFi calling to work. Obviously I've got a T-Mobile SIM card, and I've tried changing/adding APNs, and installing different builds of KitKat (some of which won't even boot - NB4 and NF9 seem to work best), but I still can't get it to work properly. I've been racking my brain and searching the Interspace for the last two weeks with no luck... what am I missing? Is it even possible?
Thanks in advance!
Click to expand...
Click to collapse
gangpe said:
Hello,
As a fellow N900A user on Tmobile, I have been trying to get wifi calling as well.
I tried using a tmobile stock rom with wifi calling baked in (tweaked), but that did not work. I was told that I need to add an emergency 911 address, but even doing this did not do it.
I would think that wifi calling is doable, but something tells me that tmobile might be doing something similar to Verizon. Rumor was that Verizon had a list of IMEIs, and if your IMEI was not on their list, you couldn't bring the phone over to Verizon, even if it were CDMA capable (once again, this is rumor as I cannot confirm this is true).
The closest I have been to getting wifi calling through tmobile was having the settings show on the stock tmobile rom, but that was about it. Maybe someone in the forums has an answer/got it working, but I have yet to see one. I'll keep you posted if I somehow get it to work, but something tells me this won't happen for a while.
Click to expand...
Click to collapse
Yeah, considering I have zero service with any provider where I live (but 4G LTE 100 yards down the street), WiFi services were the single reason I went with T-Mobile. Considering the Unlocking Bill, one wouldn't think a carrier could block IMEIs from being used on another carrier... but I have a hard time reading the fine print, so there is that.
I've tried several of the stock T-Mobile ROMs, and while WiFi calling was there, it simply wouldn't enable; it would try to enable, but never would. Have you contacted T-Mobile and asked if there are any potential fixes? I'm considering doing that, but am worried that they'll say "Oh, that's your IMEI, looks like you can't use it on our network SORRYABOUTYOURLUCK!"
I have contacted tmobile about this before.
Their response was that they did not know why it did not work. They helped me set up the emergency 911 address, but they said when it comes to other hardware they couldn't give me a reason why it wouldn't work.
I remember dwetherill (sp?) mention that some n900a users were able to get wifi calling on their phones. I don't know if the modem can/will affect wifi calling, but at this point it's the easier thing to test.
I'm on the NJ5 modem - I might try testing out NC2.
Have you tried carl's TMB version of the norma stable rom? Check it out if you haven't. Wifi calling is supposed to connect automatically. I haven't seen it work yet, but I'll keep you posted if somehow I get it to work.
AresRising said:
Yeah, considering I have zero service with any provider where I live (but 4G LTE 100 yards down the street), WiFi services were the single reason I went with T-Mobile. Considering the Unlocking Bill, one wouldn't think a carrier could block IMEIs from being used on another carrier... but I have a hard time reading the fine print, so there is that.
I've tried several of the stock T-Mobile ROMs, and while WiFi calling was there, it simply wouldn't enable; it would try to enable, but never would. Have you contacted T-Mobile and asked if there are any potential fixes? I'm considering doing that, but am worried that they'll say "Oh, that's your IMEI, looks like you can't use it on our network SORRYABOUTYOURLUCK!"
Click to expand...
Click to collapse
gangpe said:
I have contacted tmobile about this before.
Their response was that they did not know why it did not work. They helped me set up the emergency 911 address, but they said when it comes to other hardware they couldn't give me a reason why it wouldn't work.
I remember dwetherill (sp?) mention that some n900a users were able to get wifi calling on their phones. I don't know if the modem can/will affect wifi calling, but at this point it's the easier thing to test.
I'm on the NJ5 modem - I might try testing out NC2.
Have you tried carl's TMB version of the norma stable rom? Check it out if you haven't. Wifi calling is supposed to connect automatically. I haven't seen it work yet, but I'll keep you posted if somehow I get it to work.
Click to expand...
Click to collapse
I'm on NC2, and haven't gotten anything to work as of yet... I've been looking for modem threads, but I guess I need to look a little harder. I'll search that ROM out and give it a shot, and let you know if it works with NC2. Thanks for the heads-up! :good:
So I tried NC2 modem, and it is not allowing for wifi calling.
I went to tmobile yesterday to get another line added. Rumor on the tmobile side is that AT&T is working to get wifi calling setup for the n900a's by around April. Take it as a rumor at this point, seeing how it came from tmobile, but the rep made a good point - AT&T tends to follow what tmobile is doing, so who knows.
Here's to hoping they're right.
BTW, I went to the note 4 tmobile forums, and I grabbed a deodexed stock rom. I noticed that there were a few files related to wifi calling (had WFC in the name). I tried playing around with it last night, and I managed to get the settings. It will even go so far as to turn the phone GSM radio off when you select wifi only. It's doing what Tweaked was doing for me (which was keeping the wifi calling option grayed out (enabling). I think I'm still missing a few files to get it to work, but I'll keep playing around with it later and let you know if I have any success.
AresRising said:
I'm on NC2, and haven't gotten anything to work as of yet... I've been looking for modem threads, but I guess I need to look a little harder. I'll search that ROM out and give it a shot, and let you know if it works with NC2. Thanks for the heads-up! :good:
Click to expand...
Click to collapse
gangpe said:
So I tried NC2 modem, and it is not allowing for wifi calling.
I went to tmobile yesterday to get another line added. Rumor on the tmobile side is that AT&T is working to get wifi calling setup for the n900a's by around April. Take it as a rumor at this point, seeing how it came from tmobile, but the rep made a good point - AT&T tends to follow what tmobile is doing, so who knows.
Here's to hoping they're right.
BTW, I went to the note 4 tmobile forums, and I grabbed a deodexed stock rom. I noticed that there were a few files related to wifi calling (had WFC in the name). I tried playing around with it last night, and I managed to get the settings. It will even go so far as to turn the phone GSM radio off when you select wifi only. It's doing what Tweaked was doing for me (which was keeping the wifi calling option grayed out (enabling). I think I'm still missing a few files to get it to work, but I'll keep playing around with it later and let you know if I have any success.
Click to expand...
Click to collapse
I wonder how that would work regarding using a T-Mobile SIM in the AT&T phone, and if it could support cross-carrier features like that.
You're a braver soul than I, that's for sure. If I knew anything about what I was looking at/for, I'd be more than willing to help get this nut cracked... otherwise, I look forward to your findings!
Today my Nexus will only get 3G and says "000000" in the settings instead of Verizon. What could be the problem?
TIA
Xirix12 said:
Today my Nexus will only get 3G and says "000000" in the settings instead of Verizon. What could be the problem?
TIA
Click to expand...
Click to collapse
I had the same issue trying blisspop, got a roaming notification, and could only get 3g after turning on data roaming. The only way to get LTE back was to flash a stock based rom, I used cleanrom, then I was able to go back to liquidsmooth. I tried going straight from blisspop to liquid while having the issue and same issue.
I did manage to try bliss one more time, and it worked..until I rebooted and same issue again. So back to cleanrom then to liquid..ugh
Thanks for the reply. Same thing. I just did what you mentioned. I had LTE working and on Blisspop. I then rebooted to install some navbar mods and bam lost LTE and got the "000000" instead of VZW.
Xirix12 said:
Thanks for the reply. Same thing. I just did what you mentioned. I had LTE working and on Blisspop. I then rebooted to install some navbar mods and bam lost LTE and got the "000000" instead of VZW.
Click to expand...
Click to collapse
Having weird issues where I am suddenly only able to get LTE on stock (cleanrom) based roms as well. Never had an issue on any rom previously. Weird.
Ok, so I just went from CleanROM to MeanPop rebooted and lost LTE and was only on 3G. Then from CleanROM to Chroma rebooted and lost signal entirely. I am not on Liquidsmooth from CleanROM and I have rebooted and still have LTE signal.
akellar said:
Having weird issues where I am suddenly only able to get LTE on stock (cleanrom) based roms as well. Never had an issue on any rom previously. Weird.
Click to expand...
Click to collapse
I am also having issues with Verizon as well, It started happening yesterday around 10am. I was on Puritan ROM, I switched to Chroma, Temasek, Euphoria and having the same issues where it's either 3G or the bar with an exclamation point. I flash Clean Rom and Sinless and I am able to get LTE again. Has anyone found a solution cause I would like to go back to Euphoria or other ROMS? Thanks
Can't even get LTE with Clean ROM anymore. After further testing, I put the phone on airplane mode for like 10 seconds and was able to get back LTE. This whole thing is just so weird
Yeah it's very odd, tried a few more times myself, and both times when I got LTE on bliss, a reboot would instantly kill it and it would go back to the data roaming 000000 issue, and 3g only. Tried the fastboot oem config carrier vzw command, flashing the zip, nothing had any effect.
I always have to go back to cleanrom to get LTE back. A couple times, when cleanrom was installed, it didn't give LTE right away, but I changed from global to LTE, toggled airplane mode and LTE was back. I tried going directly from Bliss to Liquid again, but it's like LTE must be working before it will work on liquid, even from a nandroid backup.
braxync said:
Yeah it's very odd, tried a few more times myself, and both times when I got LTE on bliss, a reboot would instantly kill it and it would go back to the data roaming 000000 issue, and 3g only. Tried the fastboot oem config carrier vzw command, flashing the zip, nothing had any effect.
I always have to go back to cleanrom to get LTE back. A couple times, when cleanrom was installed, it didn't give LTE right away, but I changed from global to LTE, toggled airplane mode and LTE was back. I tried going directly from Bliss to Liquid again, but it's like LTE must be working before it will work on liquid, even from a nandroid backup.
Click to expand...
Click to collapse
yup I was desperate too and tried the fast boot oem config carrier VZW command, flashing the zip, to no effect as well. Since I am under no contract I might as well go to Tmobile. Have you tried Sinless?
I haven't tried sinless, but maybe I'll check it out and see what happens... Hope someone figures it out soon as I'd like to try other roms, but need to keep LTE.
braxync said:
I haven't tried sinless, but maybe I'll check it out and see what happens... Hope someone figures it out soon as I'd like to try other roms, but need to keep LTE.
Click to expand...
Click to collapse
Well, if anything changes please keep me posted. Thanks for your input
this is a known issue for just about all roms except stock based.
the_rooter said:
this is a known issue for just about all roms except stock based.
Click to expand...
Click to collapse
I know, but everything was going well. In the past I had flashed DU, Tamasek, Chroma and purity without an issue. The LTE bar and signal was always consistent, but starting yesterday things went sour. I even tried flashing old versions of my previous ROMS and I am still seeing no LTE. It's so weird that out of the blue a few people just lost LTE on verizon. Clean ROM still an awesome ROM so no issues for me but it was nice to try other builds.
Damon13 said:
I know, but everything was going well. In the past I had flashed DU, Tamasek, Chroma and purity without an issue. The LTE bar and signal was always consistent, but starting yesterday things went sour. I even tried flashing old versions of my previous ROMS and I am still seeing no LTE. It's so weird that out of the blue a few people just lost LTE on verizon. Clean ROM still an awesome ROM so no issues for me but it was nice to try other builds.
Click to expand...
Click to collapse
i am on pureandroid made by the same developer of cleanrom
Works great with xposed
the_rooter said:
i am on pureandroid made by the same developer of cleanrom
Works great with xposed
Click to expand...
Click to collapse
Great! Will give it a try!
I had to switch to MeanPop to get LTE back. Does anyone know the technical reasons this stopped working?
fucheeno said:
I had to switch to MeanPop to get LTE back. Does anyone know the technical reasons this stopped working?
Click to expand...
Click to collapse
From my understanding a few ROMS used a certain commit that dealt with Verizons APN's setting and It didn't play nice with VZ. Chroma is up and running.
Made a thread about this about a month ago. It was a PIA. Verizon does not recognize this phone as a compatible phone with their network. I went from a working phone for 2.5 months to not being able to get service. Was on the phone over a couple days trying to go through with tech on making it work. I had intermittent 3G, ! in navigation bar, and many other problems. I finally spoke to a guy in tech and he told me that the phone kept being registered in Verizon's network as incompatible and consequently being stolen. He finally got it rolling again and haven't had too many problems, but he said that it could easily happen again and to have a back-up Verizon phone to switch the sim card into when calling tech support. Since then it has been fine, but I did have 3G for a day. I did reboots and backup restore, etc...None of it was an immediate fix. I just waited till the next day and when I looked at my phone LTE was back. d
ame29 said:
Made a thread about this about a month ago. It was a PIA. Verizon does not recognize this phone as a compatible phone with their network. I went from a working phone for 2.5 months to not being able to get service. Was on the phone over a couple days trying to go through with tech on making it work. I had intermittent 3G, ! in navigation bar, and many other problems. I finally spoke to a guy in tech and he told me that the phone kept being registered in Verizon's network as incompatible and consequently being stolen. He finally got it rolling again and haven't had too many problems, but he said that it could easily happen again and to have a back-up Verizon phone to switch the sim card into when calling tech support. Since then it has been fine, but I did have 3G for a day. I did reboots and backup restore, etc...None of it was an immediate fix. I just waited till the next day and when I looked at my phone LTE was back. d
Click to expand...
Click to collapse
Has nothing to do with this issue
Sent from my Nexus 6 using XDA Free mobile app
I'm beginning to think that this may be on Verizon's end because I can't get LTE back on any ROM. Mabey because if the official release of nexus 6 on their network.
Just to update everyone. I just went from Liquidsmooth to Chroma without going to Stock based ROM and was able to get LTE. The first time I rebooted it took some time, but I have rebooted twice and have not lost LTE. Hoping it stays that way. This is using Chroma's latest update 3.2.15 r2
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. ?