Has anyone else experienced the same problem? Is there any way to get them to reactivate it?
I had an an XT1955-5 that was fully functional on the AT&T network, including voice over LTE. I bought this phone because XT1955-5 was on their list of approved phones. I even checked the sim status to verify that it didn't kick down to 3g/H+ when I made a call, and it had the HD symbol on the call screen.
Despite this, AT&T disabled it because they were shutting down the 3g network. I got them to reactivate it and it worked again for several months. Then, when they sent me the cheap replacement phone and sim card, they deactivated my old phone and I couldn't get it to work again. I tried calling them and talking to their technical support to explain the situation that VoLTE was fully functional on it. They didn't seem to know much other than "the computer says this phone isn't compatible." They said they would try changing my provisions, but they ended up making it much worse so mobile data wouldn't even work anymore.
Do they just go by an IMEI whitelist that can't be overridden? My best guess is that they seem to be shutting down all phones that weren't AT&T branded, so this one gets the axe because it was unlocked from another carrier. This is very disappointing because I really liked this phone for a combination of several factors that I can't seem to find in any others.
Unless I'm misreading the list, this is a whitelisted device on the AT&T network.
Correct, the model number is on their whitelist. That's why I chose this phone and why it's so frustrating that it was deactivated. I guess there's a subset of whitelisted IMEIs within that list, but isn't published. This particular one must not have been on their whitelisted IMEI list because it was unlocked from a nother carrier. Do you know if there's any way to get ATT to add it of am I SOL?
They say nothing about IMEI number limitations.
As long as it's not blacklisted there shouldn't be an issue. This list was just revised so your phone may not have been previously whitelisted.
There's quit a bit of confusion is what I gathered.
Some of the AT&T features like vid calling won't work without the AT&T software maybe firmware. Guess we'll both find out on the 22nd.
Call AT&T advance tech support as this is the game that moves as you play it.
I have a development:
I flashed back to stock/RetUS ROM from LineageOS 18.1 to try to fix wifi calling on T-Mobile since I was trying to switch to them due to this hassle. While I was at it, I read a post on a forum for another phone, where the person said they reflashed stock to reprovision the sim. I figured it's worth a try, so I popped in my AT&T sim card while on stock ROM and to my surprise, it fixed it. The LTE network is fully functional, at least for now. I didn't think Lineage did anything to change the radio firmware or whatever it is that controls how it interacts with the cell carrier. I guess I was wrong.
Now, I wonder if I'm stuck with the stock ROM because AT&T will detect a change and shut it down, or if I can get away with switching back to Lineage. I'll try it soon.
MotoMan1955-5 said:
Now, I wonder if I'm stuck with the stock ROM because AT&T will detect a change and shut it down, or if I can get away with switching back to Lineage. I'll try it soon.
Click to expand...
Click to collapse
AT&T isn't witch hunting. As long as it's firmware is compatible with their protocols it will work.
I have no clue what those protocols are though.
(deleted, mistook carrier)
I've pretty much lost hope at this point but I might as well share some more of this madness I'm experiencing. Maybe you'll even get some amusement out of my struggles.
VoLTE continued to work with the stock ROM. I flashed LineageOS again last night and was pleased to see VoLTE still worked. It went fine all day until someone in person mentioned to me that they texted me yesterday but I didn't respond. I never received the text, and I tried sending them one and they had not received that either. Since I was on the stock ROM when that text had been sent, I figure it was something still incorrectly configured with the carrier. I tried messages to several other people. They would all say "sent" but only a couple actually made it to the recipient, and likewise I could not receive messages from most people.
When I got home, I switched the sims around in a couple of phones to narrow down whether it was my phone or my sim that was causing the issue. It turned out to be the sim, as evidenced by successful messaging with a different sim in my phone but not my sim in a different phone. I happened to have the SIM in the AT&T Callypso when I called ATT customer support to see if they could fix the problem. Ultimately they did. VoLTE worked. Messaging worked.
I switched the SIM back to the G7 (currently running LineageOS 18.1). I made a quick call to confirm VoLTE still worked. It did. Great success! Then right after that I got the dreaded message saying they're updating the network and the phone I was trying to activate will not work. Now, it drops from LTE to H+ any time I have an incoming/outgoing call again, and mobile data doesn't even work now. At least messaging works now.
To make things worse, now it isn't even automatically reprovisioning when I put the sim in a new phone so I can't automatically get those privileges back like I did before. To make it double-worse, the sim for my spare line got the same screwed up status from being inserted into the G7 that it now has the same troubles.
Blackhawk, I agree that they probably aren't witch hunting or intentionally making this difficult, but obviously its network is changing my privileges when I put the SIM card in this phone. It seems to be that switching a sim to a new phone sends that phone info to the carrier, and if they have it on their list they automatically adjust the types of services available to that line to fit the phone. I suspect that info it sends also includes some software info, considering how it worked as intended when I had the stock software but not with Lineage which it probably did not recognize. My best guess is that I got away with flashing Lineage yesterday because my line was already configured correctly from when I had the stock rom, and since the SIM didn't change with the Lineage flash, it kept that same configuration. Moving it to another phone and back made it see the G7 as a new phone again, and it sent the info but the software wasn't recognized so I didn't get the good privileges.
ffdm, unfortunately you seem to be correct about just getting the runaround if your issue isn't common. The tech support people don't seem interested in anything other than their pre-scripted instructions, and it doesn't help that the support has clearly been outsourced to another country so they are hard to understand.
I have one last hope which is to put the SIM into the G7 totally stock, call customer support and have them reset the provisions for this line, then flash Lineage again and hope it never triggers the automatic provisioning ever again.
I just want a phone with a long battery life and AOSP not bloated with spyware that sends all my information to third parties that profile me. It shouldn't be this hard.
MotoMan1955-5 said:
I've pretty much lost hope at this point but I might as well share some more of this madness I'm experiencing. Maybe you'll even get some amusement out of my struggles.
VoLTE continued to work with the stock ROM. I flashed LineageOS again last night and was pleased to see VoLTE still worked. It went fine all day until someone in person mentioned to me that they texted me yesterday but I didn't respond. I never received the text, and I tried sending them one and they had not received that either. Since I was on the stock ROM when that text had been sent, I figure it was something still incorrectly configured with the carrier. I tried messages to several other people. They would all say "sent" but only a couple actually made it to the recipient, and likewise I could not receive messages from most people.
When I got home, I switched the sims around in a couple of phones to narrow down whether it was my phone or my sim that was causing the issue. It turned out to be the sim, as evidenced by successful messaging with a different sim in my phone but not my sim in a different phone. I happened to have the SIM in the AT&T Callypso when I called ATT customer support to see if they could fix the problem. Ultimately they did. VoLTE worked. Messaging worked.
I switched the SIM back to the G7 (currently running LineageOS 18.1). I made a quick call to confirm VoLTE still worked. It did. Great success! Then right after that I got the dreaded message saying they're updating the network and the phone I was trying to activate will not work. Now, it drops from LTE to H+ any time I have an incoming/outgoing call again, and mobile data doesn't even work now. At least messaging works now.
To make things worse, now it isn't even automatically reprovisioning when I put the sim in a new phone so I can't automatically get those privileges back like I did before. To make it double-worse, the sim for my spare line got the same screwed up status from being inserted into the G7 that it now has the same troubles.
Blackhawk, I agree that they probably aren't witch hunting or intentionally making this difficult, but obviously its network is changing my privileges when I put the SIM card in this phone. It seems to be that switching a sim to a new phone sends that phone info to the carrier, and if they have it on their list they automatically adjust the types of services available to that line to fit the phone. I suspect that info it sends also includes some software info, considering how it worked as intended when I had the stock software but not with Lineage which it probably did not recognize. My best guess is that I got away with flashing Lineage yesterday because my line was already configured correctly from when I had the stock rom, and since the SIM didn't change with the Lineage flash, it kept that same configuration. Moving it to another phone and back made it see the G7 as a new phone again, and it sent the info but the software wasn't recognized so I didn't get the good privileges.
ffdm, unfortunately you seem to be correct about just getting the runaround if your issue isn't common. The tech support people don't seem interested in anything other than their pre-scripted instructions, and it doesn't help that the support has clearly been outsourced to another country so they are hard to understand.
I have one last hope which is to put the SIM into the G7 totally stock, call customer support and have them reset the provisions for this line, then flash Lineage again and hope it never triggers the automatic provisioning ever again.
I just want a phone with a long battery life and AOSP not bloated with spyware that sends all my information to third parties that profile me. It shouldn't be this hard.
Click to expand...
Click to collapse
If these apply to you try:
Clear system cache
Clear Sim Toolkit data
Reset network setting
Get a new sim card from AT&T, handle like a stick of ram as they can be damaged by ESD.
From what is described, it does sound like a provisioning issue, and calling to get it fixed would probably be the correct solution. But why is it flagged as incompatible? Why would that status be persistent for that line? It's weird.
FWIW, AT&T kicked me off for switching from a OnePlus 6 (not a 5g phone) to a OnePlus N10 (5G phone). They were nice enough to disable my account on a Friday night when I switched sims, and was without cell service all weekend since they apparently don't want to do customer service outside banker's hours. Couldn't use the old one either (on 4G), I was completely blacklisted.
T-Mobile happily accepted my porting on Monday .
I'll save my unkind thoughts past "maybe consider firing them" as I don't want to sound like a loonie.
Man, I wish I could switch. I actually tried switching to a T-Mobile MVNO. They provisioned my SIM correctly, but unfortunately their coverage was insufficient in my rural area. I considered sticking with them and using wifi calling at home if that would work, but that feature was broken on lineage and I thought I got this to work correctly with AT&T.
I did get it working by flashing stock again, calling ATT to have them correctly provision it, then flashing LineageOS again. It has been working properly for about a week so with any luck I'll get to continue using the phone.
The 22nd came and went. I'm noticing some vids pause occasionally. May be just a random glitch otherwise no change. I may eventually try a network reset and have AT&T do it on their end.
Long live 4G LTE
Related
Howdy,
About 3 weeks ago, I bought two refurbished SGH-M919 phones off eBay to replace mine and my wife's broken/old phones. Her phone was worse off, so the first one I set up was to be hers. Rooted, installed TWRP, and flashed Mokee with no issues. Put her SIM in, put her data back on, she's good to go.
I go to set the next one up for myself, do everything the exact same way, and came to realize after I put my SIM in that the phone is not connecting to LTE. Call/SMS/Wifi all work fine. I didn't notice whether or not it was doing this before rooting, recovery, and ROM.
It's giving me a "Sign-in to network" notification. I tap it, it takes me to a T-Mobile ConnectMe screen. It gives me a "Get Started" button, which I tap, and it says "We're sorry, you have switched your SIM card between different devices, so you will need to manage your account through My T-Mobile or the MyAccount app. Once you have replaced the original SIM card, you may resume managing your account through on-device account maintenance." I can only tap close. My wife's phone didn't give me this "error". I made sure the APN settings were identical between the phones, they were.
I called T-Mobile, they gave me a bit of runaround, said everything looked fine from their end, and "rebooted the connection" which didn't improve anything. They also had me verify my APN settings with them. They had me enter some different values, but it didn't change anything. They also advised me against purchasing phones from less than reputable sources. Great, thanks, that was helpful.
I switched the SIM cards between the two phones and this one is still not connecting to LTE, the other phone is. This led me to think maybe it was a hardware issue, and looked into the modem as a possibility. I found that T-Mobile updated the baseband last month on the stock 4.4.4 ROM, so I flashed that baseband and no change. Both phones were on NH7 when I received them.
I happened to notice on my T-Mobile account page that the device status is listed as "locked/unknown." So, I called T-Mobile twice today for an unlock code. The first guy was less than helpful but the second person did enter an unlock request for me, theoretically, I am currently waiting for that email to show up sometime in the next 24 hrs. But, the phone so far has not given me an unlock prompt so I'm not quite sure what I'm going to do with that unlock code once I get it. I'm also not 100% clear on whether the code is for a SIM unlock (which I shouldn't need) or what exactly. It is just the next in a series of ideas which I'm rapidly running out of. A check of the IMEI number revealed it was clean on all US carriers, with the exception of T-Mobile and Sprint which both come up as "unknown." Don't know if that means anything or not.
I'm getting ready to jam this eBay store up, but I'd really rather the phone just start working. I've been dinking with this for weeks and my frustration is mounting, especially since I can't seem to find anyone else who has had/posted about this problem before. I'm not a cell phone hobbyist or anything, and I'm just going off what I can find on Google and places like this. Any ideas/help would be appreciated.
Thanks,
Tony
I am not familiar with the issue, just some extra troubleshooting ideas...
Have you checked under the battery and confirmed the model number is SGH-M919 and the IMEI matches matches what is on the phone?
Have you checked your APN settings?
Have you tried flashing a complete full stock firmware -
http://forum.xda-developers.com/showthread.php?p=64431358
lumin30 said:
I am not familiar with the issue, just some extra troubleshooting ideas...
Have you checked under the battery and confirmed the model number is SGH-M919 and the IMEI matches matches what is on the phone?
Have you checked your APN settings?
Have you tried flashing a complete full stock firmware -
http://forum.xda-developers.com/showthread.php?p=64431358
Click to expand...
Click to collapse
IMEI under the battery matches what comes up with *#06#.
I did check on the APN settings, forgot to mention that. I edited it into the first post, added text in red:
dauntless89 said:
It's giving me a "Sign-in to network" notification. I tap it, it takes me to a T-Mobile ConnectMe screen. It gives me a "Get Started" button, which I tap, and it says "We're sorry, you have switched your SIM card between different devices, so you will need to manage your account through My T-Mobile or the MyAccount app. Once you have replaced the original SIM card, you may resume managing your account through on-device account maintenance." I can only tap close. My wife's phone didn't give me this "error". I made sure the APN settings were identical between the phones, they were.
I called T-Mobile, they gave me a bit of runaround, said everything looked fine from their end, and "rebooted the connection" which didn't improve anything. They also had me verify my APN settings with them. They had me enter some different values, but it didn't change anything. They also advised me against purchasing phones from less than reputable sources. Great, thanks, that was helpful.
Click to expand...
Click to collapse
I didn't flash a full stock firmware. I had issues flashing the non-hlos.bin to the phone, which as I understand it is the more important of the two files for my issue since it does the LTE. However, Wifi works perfect with transfer rates equal to the other phone. So, I don't know.
I'm downloading OK3 now. I read about a guy updating his modem by backing up his custom ROM, flashing a stock rom, and restoring his custom ROM. Will TWRP back up my current NH7 non-hlos.bin? If so, can I manually remove it from the recovery image without borking anything?
For your situation, just flash the full firmware. Don't remove anything from the tar. OK3 is the newest modem. Get your phone working and go from there.
Yeah, I think I'll do that when I get home, unless someone has a better idea. :fingers-crossed:
dauntless89 said:
Yeah, I think I'll do that when I get home, unless someone has a better idea. :fingers-crossed:
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3276231
Try to flash the latest stock... Before flashing reset your device (take data/photo etc backup).... Hope that should resolve the issue....
Also what is it showing in settings > network? Is it LTE or 2G or 3G???
Sent from my SGH-M919 using Tapatalk
Thanks, that's the one I'm downloading and I'll try flashing it when I get home. It looks like it will replace TWRP and everything, bringing the phone completely back to stock?
In the mobile network settings > mobile network menu, it shows the preferred network as LTE.
Yes. It will be completely stock. If it works, you can then root and put TWRP on and go from there.
Alright, flashed the afore-linked OH3 ROM and the LTE is still broken. The phone shows up as connected to LTE, but nothing works. Play Store times out, both stock internet browsers time out. I still get the same T-Mobile nag that I got before and it still doesn't let me do anything.
Also got the unlock email from T-Mobile:
[FONT="]Thank you for taking the time to contact T-Mobile. We have received your SIM Unlock Request. Unfortunately, we are unable to process your request at this time because we are only able to provide unlock codes for T-Mobile USA handsets. Please refer your unlock request for this equipment directly to the carrier that the handset was purchased from.[/FONT]
Click to expand...
Click to collapse
Is there anything left to troubleshoot, or do I return it as defective?
If data works for your sim card in your wife's phone and not for your sim card in your phone, it would have to be a phone issue. You can double check if data works with your wife's sim card in your phone.
If your APN settings match your wife's phone with her data working, the last thing I can think of to try is go to Settings, under Connections go to More networks > Mobile networks and check Data roaming just in case your phone is roaming for whatever reason.
If your phone was locked on a different carrier, I don't think you would have cell service. If your IMEI was blacklisted or borked, I don't think you would have cell service.
I'd return the phone.
lumin30 said:
If data works for your sim card in your wife's phone and not for your sim card in your phone, it would have to be a phone issue. You can double check if data works with your wife's sim card in your phone.
If your APN settings match your wife's phone with her data working, the last thing I can think of to try is go to Settings, under Connections go to More networks > Mobile networks and check Data roaming just in case your phone is roaming for whatever reason.
If your phone was locked on a different carrier, I don't think you would have cell service. If your IMEI was blacklisted or borked, I don't think you would have cell service.
I'd return the phone.
Click to expand...
Click to collapse
I will check on those two things when I get home, but my thought process was similar to yours. Both my wife's new phone and the LTE Wifi hotspot we use for our internet service have full signal on LTE everywhere in the house, so my best guess at this point is there's a hardware issue with the modem in the phone. I might look into replacing whatever board the modem is on. If it's relatively cheap, I'd rather just pay for the part instead of waiting 2-3 weeks for turnaround on the return/exchange, but I think that's probably what we're gonna end up doing.
Thanks for the help, fellas. I appreciate it.
Hello,
First, let me express my deepest thanks in advance for those of you who may be of assistance. I have visited this site many times over the years when I needed to find the answers to smartphone related issues (mostly rooting..etc). I have usually found the information that I needed via reading posts and trial and error; however, I am having a problem that I cannot find the answer to and it is frustrating the crap out of me.
So, here goes:
I bought a LG LS980 off of Ebay. It was locked to Sprint and I had a friend of mine root it (since I couldn't figure it out and it ended up being that the firmware had to be downgraded since a patch was bumped to it) and unlocked (or so i was told, but I do not know how to find out). It is currently running Cyanogenmod 12.1. I wanted to use my old phone's SIM and pop it into my new phone so that I could enjoy it (the old phone was a Nexus and ran hella slow). So, anyway.... I contacted NET10 customer support since that is my carrier and explained what I wanted to do. They let me know that as long as it is unlocked that I would be able to just swap the SIM into the new phone and should be good to go. They checked my IMEI and said that the phone was, indeed, compatible and as long as it is unlocked it should just be a matter of a simple ROM swap. Not the case. I put the SIM in and booted it up. It went from No Service to saying "Sprint" on the upper left hand corner. I try to make a call and it states that, "The code or number that I am dialing is incorrect, please try the code or number again". I looked this up on the internet and didn't find a focused answer. I talked to my friend and he stated that I may have to set up a new APN profile.
I have checked the APN settings on it and all of the APN profiles have the prefix "Verizon". I used this mini tutorial at http://forums.androidcentral.com/goo...-settings.html along with the NET10 settings to try and make a profile. Both of their workarounds don't seem to work. I can enter about half of the information and then either click BACK or SAVE and then the profile is gone. I am not sure this is the reason that my phone is not working, but I thought I would give it a try. I have also tried to use this tutorial: http://forum.xda-developers.com/showthread.php?t=2798566 as a loose guide, TWRP installed. Keep in mind that I believe that my firmware was rolled back to ZVE. and not ZVD. When I have tried to edit the build.prop values at the tutorial states it does not save. Also, there are two lines that are not even in my build.prop (ro.build.target_operator and persist.service.crash.enable). When I have tried to edit or add it adds them but does not save and definitely does not persist through reboot. I feel as if I am close to getting the phone to work, but I am unsure where to go from here. I really do NOT want to have to go back to a stock ROM and all of that because....well.... my friend did the rooting and installing of cyanogenmod and I don't want to risk undoing all of his work and having to pay $ to have it done all over again (I have rooted phones..etc, but this G2 was a MOFO because of the firmware patch for me). NET10 CS and TS was of no help and they gave me a ticket number (and to tell you the truth the are outsourced and I can't understand what their reps are saying). So, does anyone have any advice or threads that I can look at? Like I said, I feel as if it is close, but no matter what number I call it says that recording. I get no incoming calls (although it rings when listening to the incoming calling phone's speaker). I am also unable to send or receive SMS or MMS messages. Any help would be greatly appreciated. I am not the most technically savvy person, but I can answer your questions to the best of my ability and I am good at following directions. (I have about 5-6 phone root/ROMS under my belt and even 2-3 SPRINT to NET10 activations, but this one is just perplexing the crap out of me) . Could it be that the phone is not unlocked???? How do I check this??? Is there a way??? When I put in the NET10 SIM it never asked me for an unlock code so I am assuming that my friend unlocked it? I have also tried "Turn the phone ON and type 2945#801# If nothing happens, type 2945#802# or 2945#*803#" and no hidden menu appears asking for an unlock code.
Hello,
First, let me express my deepest thanks in advance for those of you who may be of assistance. I have visited this site many times over the years when I needed to find the answers to smartphone related issues (mostly rooting..etc). I have usually found the information that I needed via reading posts and trial and error; however, I am having a problem that I cannot find the answer to and it is frustrating the crap out of me.
So, here goes:
I bought a LG LS980 off of Ebay. It was locked to Sprint and I had a friend of mine root it (since I couldn't figure it out and it ended up being that the firmware had to be downgraded since a patch was bumped to it) and unlocked (or so i was told, but I do not know how to find out). It is currently running Cyanogenmod 12.1. I wanted to use my old phone's SIM and pop it into my new phone so that I could enjoy it (the old phone was a Nexus and ran hella slow). So, anyway.... I contacted NET10 customer support since that is my carrier and explained what I wanted to do. They let me know that as long as it is unlocked that I would be able to just swap the SIM into the new phone and should be good to go. They checked my IMEI and said that the phone was, indeed, compatible and as long as it is unlocked it should just be a matter of a simple ROM swap. Not the case. I put the SIM in and booted it up. It went from No Service to saying "Sprint" on the upper left hand corner. I try to make a call and it states that, "The code or number that I am dialing is incorrect, please try the code or number again". I looked this up on the internet and didn't find a focused answer. I talked to my friend and he stated that I may have to set up a new APN profile.
I have checked the APN settings on it and all of the APN profiles have the prefix "Verizon". I used this mini tutorial at http://forums.androidcentral.com/goo...-settings.html along with the NET10 settings to try and make a profile. Both of their workarounds don't seem to work. I can enter about half of the information and then either click BACK or SAVE and then the profile is gone. I am not sure this is the reason that my phone is not working, but I thought I would give it a try. I have also tried to use this tutorial: http://forum.xda-developers.com/show....php?t=2798566 as a loose guide, TWRP installed. Keep in mind that I believe that my firmware was rolled back to ZVE. and not ZVD. When I have tried to edit the build.prop values at the tutorial states it does not save. Also, there are two lines that are not even in my build.prop (ro.build.target_operator and persist.service.crash.enable). When I have tried to edit or add it adds them but does not save and definitely does not persist through reboot. I feel as if I am close to getting the phone to work, but I am unsure where to go from here. I really do NOT want to have to go back to a stock ROM and all of that because....well.... my friend did the rooting and installing of cyanogenmod and I don't want to risk undoing all of his work and having to pay $ to have it done all over again (I have rooted phones..etc, but this G2 was a MOFO because of the firmware patch for me). NET10 CS and TS was of no help and they gave me a ticket number (and to tell you the truth the are outsourced and I can't understand what their reps are saying). So, does anyone have any advice or threads that I can look at? Like I said, I feel as if it is close, but no matter what number I call it says that recording. I get no incoming calls (although it rings when listening to the incoming calling phone's speaker). I am also unable to send or receive SMS or MMS messages. Any help would be greatly appreciated. I am not the most technically savvy person, but I can answer your questions to the best of my ability and I am good at following directions. (I have about 5-6 phone root/ROMS under my belt and even 2-3 SPRINT to NET10 activations, but this one is just perplexing the crap out of me) . Could it be that the phone is not unlocked???? How do I check this??? Is there a way??? When I put in the NET10 SIM it never asked me for an unlock code so I am assuming that my friend unlocked it? I have also tried "Turn the phone ON and type 2945#801# If nothing happens, type 2945#802# or 2945#*803#" and no hidden menu appears asking for an unlock code.
You can unlock your Sprint phone for GSM but you can't activate it to Verizon or its MVNOs.
I had 4G before this update, but nothing I do, no matter how many different APN settings I try, no dice.
I'll tell you where I've been. Have had the phone at least a year and it came with Nougat.
As soon as I got it, I got a Total Wireless SIM (owned by Tracfone and running on Verizon's network) and activated it with no problems. Had full service. 4g, mms, etc. All was great.
Even when I got the 8.0 notification and I updated to Oreo, all worked fine.
A few months back, I got the 8.1 notification. I allowed it to install and when It booted back up, I had no service at all.
Found this thread, Android 8-1 - How to Edit Cellular APN, and one post in there got me with the phone setup and connected to my computer running ADB commands, which allowed me to at least add an APN.
Adding the standard TRACFONE.VZWENTP apn you can easily find via Google searching fixed the problem. (Had to add mms port of 80 but otherwise, all was perfect)
About a week back I get the 8.1 notification again, which i thought was weird since I was already running 8.1
Turns out it was the April Security Patch for 8.1 (i suppose as that's the only reasoning that makes sense to me right now).
After it installed and did it's thing, I only had 3G service, which around here is prone to many interruptions, aside from the slow speed.
I checked, and it's still using the APN I set up. Nothing has changed on that APN, nor anywhere else I can see.
I even added a new one with the same data, and same thing, 3G.
I've searched the threads here, tried some of the other suggestions but none have worked.
I've even went as far as to get Smail to unlock my bootloader (it's a verizon Pixel XL) and from there I've rooted installed twrp and rooted etc, all in hopes that I could try another method listed in that thread i linked above, using an adb shell with root permissions to view the "default" apn data, thinking maybe something in there is messing it all up.
I had no luck there because even though the phone is rooted now, there was something else I have to do to run an adb shell with root permission and seems the easiest way to get that done is just install a custom rom.
Still, what baffles me is, isn't this what the SIM card is partly for?
And why would software updates disable service, or parts of service?
Seems odd that a software upgrade would effect how the phone uses the service, especially when a custom apn is setup and unchanged.
I have scanned these forums for hours over the past few days and I would really love some direction on what to try next.
Any ideas are appreciated. Thanks!
Play around in the *#*#4636#*#* dialer menu just don't hit the update button beside the smsc input field
Sometimes, the best thing to do is to go to total wireless and ***** at them till they deal with it. I don't think its something you need to stress over. It's Verizon's and Total Wireless's responsibility to get your 4g LTE back. I just dealt with T-Mobile with the same issue. no 4G but call and texting worked. APN set right but they did something on their side and got me back on track after handing them my phone.(in store)
DR3W5K1 said:
Play around in the *#*#4636#*#* dialer menu just don't hit the update button beside the smsc input field
Click to expand...
Click to collapse
Oh wow, never knew about this. Brought up all kinds of options. Will mess around and see if I can find something useful.
acters said:
Sometimes, the best thing to do is to go to total wireless and ***** at them till they deal with it. I don't think its something you need to stress over. It's Verizon's and Total Wireless's responsibility to get your 4g LTE back. I just dealt with T-Mobile with the same issue. no 4G but call and texting worked. APN set right but they did something on their side and got me back on track after handing them my phone.(in store)
Click to expand...
Click to collapse
I would but Total Wireless doesn't have a store front or even a kiosk. They're kinda like Straight Talk, but just for Verizon phones. Verizon naturally won't have anything to do with it since I'm paying their competition to use their network.
I had thought about going through the activation again, but when i put my IMEI # on their website now, it says my phone is not compatible. A year ago it said it was, and it has been until this update.
I've considered flashing 8.0 and see if that lets it work again, but I don't like the thought of not being to update my phone or i'll lose parts of my service.
Thanks for the suggestions yall. Will repost if the dialer code leads me somewhere helpful.
kamikazeedriver said:
I had thought about going through the activation again, but when i put my IMEI # on their website now, it says my phone is not compatible. A year ago it said it was...
Click to expand...
Click to collapse
Oh my, can you confirm if your IMEI is the same one as the one as last year?
They are probably getting money hungry and want people to buy phones from them. There is a big chance that hidden menu could solve your problem though. Regarding the imei the only way that could be a problem is if yours was somehow stolen
DR3W5K1 said:
They are probably getting money hungry and want people to buy phones from them. There is a big chance that hidden menu could solve your problem though. Regarding the imei the only way that could be a problem is if yours was somehow stolen
Click to expand...
Click to collapse
I think it shows up as an issue because I'm currently using it. I just tried it again and it said "there was an error." When I tried it a few days ago it had said the same, "there was an error, contact customer support"
It's possible that time it showed up as incompatible i had punched a number in wrong.
Can't confirm if it's the same IMEI i had a year ago but it would be weird if that changed.
Couldn't find anything in the hidden menu except when I checked "Carrier Provisioning Info" showed up that it last attempted it yesterday and had failed.
Well as a last ditch .. just a thought here. Pull the sim power on your phone delete the apn. Perform a reboot insert sim and wait. Still nothing? Check apn add if necessary and reboot. Profit?
DR3W5K1 said:
Well as a last ditch .. just a thought here. Pull the sim power on your phone delete the apn. Perform a reboot insert sim and wait. Still nothing? Check apn add if necessary and reboot. Profit?
Click to expand...
Click to collapse
I did try that after the april update.
With no APN, I get no service, which first happened right after the first 8.1 update. That lead me to adding the APN.
I haven't tried it since I've unlocked the bootloader.
I will try again before flashing back to 8.0.
8.0 was the last time my phone worked just fine with no custom APNs or anything.
I thank y'all for the ideas.
I would like to know if I'm the only one with this specific problem.
Is anyone else experiencing this issue with the 8.1 updates using a Verizon MVNO?
For future reference that provisional menu will be populated with answers other than no. If you have the proper apn etc..
DR3W5K1 said:
For future reference that provisional menu will be populated with answers other than no. If you have the proper apn etc..
Click to expand...
Click to collapse
Want me to take a screenshot of the provisional menu? I don't know what I'm looking for in that menu.
As far as APN, it never needed to make one until the first 8.1 update but all worked fine afterwards. It's only since the April update that I have issues.
Will report back after trying to reset without the sim again
If a fresh image+apn doesn't fix it the only other thing that "you” could try would be replacing the Sim. Sometimes the Sim can fry. Could also be as easy as reseating it.
It's fixed
Here's what I had to do.
I did a wipe install (flash all.bat) of an 8.0 Oreo image as it was the last time I had LTE without even having to do anything (like setup a custom APN etc)
After that was successful, I did a no-wipe install of the 8.1 (April 2018) image, and afterwards, and once it was booted, all was well, I have LTE and everything with no custom APNs needed.
Thanks to everyone who offered help in getting me in the right direction.
In addition to what I previously mentioned that I had tried, I also tried:
-I did try a wipe install of 8.1 a few days ago but still with no success. Even with tweaking APN settings.
-I messed around with the carrier provisioning menu and could see I was not getting LTE and when I told the phone LTE only, then no service at all, so I set it back to LTE/CDMA/UMTS (that's what it was already on.)
-Tried dialer code *228 to "activate" my service, but that had no change.
I went back, this morning, to the thread I first looked at after the first 8.1 update I had which disrupted my service completely and ended up with me using an adb shell to do something that allowed me to add APNs and subsequently setup an APN that worked for me until the 8.1 April security update.
Noticed this post:
ThePhoneGeek said:
I have this same issue and the only solution I've found is to full wipe go back to 8.0 activate on Verizon's network (I too use a VZN MVNO) and then flash the full 8.1 package without wipe.
Click to expand...
Click to collapse
I can't say I understand why that worked when a completely fresh wiped install of 8.1 didn't, but it did so I'll take it.
The next thing I was going to try, if it hadn't worked, was changing the radio band in the provisioning menu as that seemed to work for another person.
Either way, all is well for now. Thanks for all the advice!
kamikazeedriver said:
Noticed this post:
I can't say I understand why that worked when a completely fresh wiped install of 8.1 didn't, but it did so I'll take it.
The next thing I was going to try, if it hadn't worked, was changing the radio band in the provisioning menu as that seemed to work for another person.
Either way, all is well for now. Thanks for all the advice!
Click to expand...
Click to collapse
The only thing I've come up with is that starting on 8.1 flashing full wipe for VZN users (or perhaps limited to VZN MVNO's) with unlocked bootloaders is not allowing the device to activate on the network. I suspect VZN hanky panky at work but I am generally a skeptic that way. Once you get it the way you want it you can update each month with the full firmware but remove the -w in the flash-all.bat file and you should be good.
ThePhoneGeek said:
The only thing I've come up with is that starting on 8.1 flashing full wipe for VZN users (or perhaps limited to VZN MVNO's) with unlocked bootloaders is not allowing the device to activate on the network. I suspect VZN hanky panky at work but I am generally a skeptic that way. Once you get it the way you want it you can update each month with the full firmware but remove the -w in the flash-all.bat file and you should be good.
Click to expand...
Click to collapse
My bootloader was still locked when these issues began with the first 8.1 update (which adding an APN fixed), and culminated in 3G only after the 8.1 April update.
I only unlocked it so I could hopefully find a solution, which thankfully was a success.
I'm just as skeptic as you are when it comes to VZN though. They have the best coverage in this area, and that's the only positive thing I have to say about them.
Hello all,
I was warned of an impending "update" a few nights ago. Since it hit, my mobile hotspot no longer works.
Does anyone else have an S7 Active on Red Pocket who has a working hotspot? If so, could you share the APN settings you are using, and the Android version you are on?
I think they rolled me back to January 2018. G891AUCU2BRB5
Would rather not factory reset or root, but getting very close to doing so. Neither RP or AT&T are helpful here.
Thank you,
Bob
Red Pocket Mobile Hotspot problem solved - stock Oreo 8.0 fixed it
Well, for anyone who might encounter this, I finally resolved it.
Pulled the SIM card and did a factory reset. Then it recognized the Oreo update over Wifi. Had to load an intermediate update first.
I put it Red Pocket's AP settings.
First time I tried Mobile Hotspot, it still didn't work.
Restarted the phone.
Still didn't work.
Then I remembered one rep saying to switch MVNO type to "IMSI".
3rd times a charm. Hotspot and USB tether now both working.
After ten hours of wading through poor advice, I'm back to where I was four days ago.
With one exception: I learned how to turn on Developer Mode (tap Build Number 7 times in Software Info)
AND SHUT OFF THE AUTOMATIC UPDATES UNDER DEVELOPER MODE SO IT WON'T HAPPEN AGAIN!!!
I have a stock S7 Active/G891A that I bought unlocked on eBay in March of 2018. It's currently running Oreo 8.0.0, build G891AUCS4CSA3. I just now disabled OTA updates thanks to you.
I've been trying to get Mobile Hotspot to work on this phone ever since I switched Consumer Cellular several months ago. Whenever I tried to enable hotspotting the phone screen would display a popup:
Please wait while verifying
Which was a normal message on the AT&T network, but now (using AT&T's network through Consumer Cellular), after 5-10 seconds a different window would appear:
Tethering/Mobile AP is unavailable.
A network issue may be preventing use of your Mobile Hotspot. Please call Customer Care at 611.
[excessive hard-coded line breaks omitted]
Over the course of several weeks in January I literally spent hours on the phone with several Consumer Cellular 1st and 2nd tier support techs trying to get past that error. Tier 2 support gave me new APN settings, had me do a network reset, and suggested that I do a factory reset. Which I did later, but that didn't work, either. Then CC tier 2 support gave up and bumped my ticket to tier 3. Tier 3 support then transmitted their version of an APN definition to my phone, but still no love. At the end of the 2nd week of phone tag, a Tier 2 tech told me that "it <Mobile Hotspot> just doesn't work with some phones not sold by us".
Maybe hotspotting won't work with my old Motorola Razor, but I was pretty sure that I'd eventually strike gold with my trusty G891A.
Because my S7 Active has version 4 of the boot loader (thank you, latest and final OTA), I haven't been able to find anything that resembles a working root. I even paid OneClickRoot to do it via remote desktop session, hoping that they had some good mojo that I hadn't yet discovered. But their support tech hit a wall, too, and ended up flashing my phone back to stock Oreo 8.0.0. They also refunded my purchase almost immediately which made me sort of happy but still sad that I had no Hotspot abilities.
While searching for possible workarounds (ROMS, root, mystical incantations) tonight I came across your posts:
bobcpdx said:
[snip]
Then I remembered one rep saying to switch MVNO type to "IMSI".
[snip]
Click to expand...
Click to collapse
So I followed your tip. I created a new APN definition and copied in all of the values from the CC Tier 3 definition . I then set Mobile virtual network operator type to imsi . This value was set to None in all in all of the other APN definitions on my phone.
I didn't even need to reboot the phone. I selected my new APN definition and enabled Mobile Hotspot. The first message about verifying came up. But then the phone didn't direct me to dial 611. Mobile Hotspot simply started working.
Thanks every so much for sharing this insight.
bobcpdx said:
Well, for anyone who might encounter this, I finally resolved it.
…..
Then I remembered one rep saying to switch MVNO type to "IMSI".
3rd times a charm. Hotspot and USB tether now both working.
….
Click to expand...
Click to collapse
WOW! Thanks so much for posting this. I've been struggling for a couple of months to find a way to hotspot my two unlocked LG's (G6 and a G7) on Cricket and Consumer Cellular. This trick enabled hotspot/tether quickly and easily.
My apologies to Cricket and CC, for my unflattering thoughts about them. I assumed it was their issue! Not sure why these unlocked LG's are fidgety like this. We got a Moto X4 (Android One flavor) in the family, and it can hotspot with no tweaking.
BTW - I have a similar issue with call forwarding on the LG's. Can't enable it, get an error. But the Moto X4 has no problem on either of these AT&T MVNO's. Anyone have an easy answer for that? Thanks.
This doesn't answer the call forwarding question. I'm not sure who pushes OTA updates, but soon after my last post I got a notification that an my phone needed to be rebooted for an update to finish. This was after I (at least thought that I had) disabled automatic updates. After the update the hotspot feature no longer worked. I checked APN settings and found that the update had reset the APN MVNO type to NONE . I manually changed it back to imsi and it's been working ever since. I also made sure (twice with reboot in between) that automatic OTA Updates are disabled.
Although enabling/disabling these features seems to be problematic with AT&T MVNOs, what I find more curious is that techs at Consumer Cellular claim not to know how to fix them. Maybe that's true, or maybe that's what they are told to say.
Was it coincidence that I received an OTA update within days of making this change, or is the Big Brother with the Blue Death Star logo watching us so closely?