Anyone w/S7 Active on Red Pocket? Mobile hotspot & tethering just broke - Samsung Galaxy S7 Active Questions & Answers

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?

Related

Can't get migrated xv6800 back onto Verizon network

What started out as an effort to get my migrated XV6800 to operate on Verizon's data network has taken a nasty turn for the worse... Here is the long, sordid story, and I would really appreciate help in getting this device back onto the Verizon network.
This was originally a Qwest phone. I unlocked it and flashed it with a Verizon ROM, the file name is _Verizon XV6800_RUU_TITAN_VZW_WWE_3.57.605.1_RS_TITAN_3.37. 75_OM_VZW_ShipFULL. After I did that the customization routines did not run. Frankly, I don't know if they were supposed to or not, but they didn't.
I couldn't get the phone to connect to the Verizon network, even on *228. Eventually I applied a PRL and then I was able to connect to *228, and option #3 got the phone onto the voice network. I used it as my cell phone for two weeks with no issues on the voice network. Still, I wasn't able to get data working.
These are the things I tried while troubleshooting the data issue:
* Loaded the carrier cab from DCD
* Forced a CDMA only connection to download new keys
* Loaded the newest Verizon ROMs I found while at their website (this is the first time I saw customization routines)
* Told Verizon to switch me from pay as you go data to unlimited data (though it looks like they never turned this on)
* Tried activating my PDA with a different Verizon number, and then re-activating it with my original Verizon number
* Did a hard reset
It's those last two steps that screwed me. After I swapped the number off the phone I wasn't able to get it back. I could get to option #3, but it wouldn't let me activate the phone. Their tech support is no help and they are shocked when they look back at my account history and see that I was able to use *228 to get this phone on their network two weeks ago.
I then did a hard reset and got myself all the way back to the point where I was before I manually put the PRL in place. When I dial *228 I get the following: "Your account is not authorized to make calls to this phone number. I you would like to have additional capabilities added to your account please call customer service. Message 4, swich 691". I'm guessing that installing a PRL on the phone will now let me use option #3, because that's what made it work last time. However, I'm looking for instructions since I messed up somewhere in the process last time.
I just tried the following, but I get a recording saying they are unable to activate my phone at this time and then it tried to connect me to a person.
1. Install PRL
2. Install carrier cab
3. Install MMS cab
4. Run *228, #3
I know the person is just going to tell me that they can't help because their system doesn't recognize the ESN.
So what's the verdict, can I expect to get this phone back onto the voice network, will it ever work on the data network? Any help that anyone can offer in resolving this would be greatly appreciated.
Wrong forum? Should this have gone into upgrades?
moved thread by request of OP as Q&A forum did not provide answers nor does the OP expect it to.
Best regards,
Flar
Since being able to dial *228, have you called customer service to pull a new key for your device? When I upgraded a xv6800 rom I was not able to dial *228 until I did that. It was a bit of work getting it to pull the new key, but they did it. They first walked me through a manual registration process, then I think they tried to push it through and that worked.
Is your phone a Verizon phone? The pickle I'm in is that mine is not. When they ask me for the ESN they say it's unrecognized and that's pretty much it. They say they can't help me get it on the network because it's not a Verizon phone.
mfreema said:
Since being able to dial *228, have you called customer service to pull a new key for your device? When I upgraded a xv6800 rom I was not able to dial *228 until I did that. It was a bit of work getting it to pull the new key, but they did it. They first walked me through a manual registration process, then I think they tried to push it through and that worked.
Click to expand...
Click to collapse
Yep mine is a verizon phone. I am wondering if this is a new implementation, because I have flashed several roms before and never had to call them to get my phone activated until about a month ago. When you dial *228 does it allow you to do a phone programing, I think it is option 1?
No. 1, 2, & 3 all fail. I just called tech support again, hoping getting a new A key would resolve this. He told me he couldn't give me an A key unless the phone's ESN was in the system and the only way to get it in there is through *228, #3... Kind of a Catch 22.
His last suggestion was that I activate a different PDA on my number and see if maybe the computer is choking because my current phone isn't a PDA, and this one is. Kind of sounds like clutching at straws, but he said at this point I've done all that can be done, short of that.
I find really odd, and extremely frustrating, that I can't find anyone else who has been through this with a non-Verizon phone.
mfreema said:
Yep mine is a verizon phone. I am wondering if this is a new implementation, because I have flashed several roms before and never had to call them to get my phone activated until about a month ago. When you dial *228 does it allow you to do a phone programing, I think it is option 1?
Click to expand...
Click to collapse

S7 Active for use outside the US (WiFi Calling and Software Updates?)

Hey folks,
I bought an S7 Active from eBay and I'm using it in Ireland. Everything is working fine that I need, but my carrier recently introduced WiFi Calling and upon trying to set it up from the setting menu where it reads
"wifi calling lets you make and receive calls over wifi with your at&t accoumt. when you use wifi calling, information about the country where the wifi connection is made will be sent to your carrier. Learn more about wifi calling (link).
GET STARTED"
I get the following error:
"Wifi Calling activation not successful, try again later"
I rang support for my carrier and they think it's something to do with the handset. They support the S7 and the S7 Edge but as the S7 Active is an AT&T exclusive and appears to have custom AT&T software, it seems like it might be trying to connect to AT&T and it can't?
Also, when I check for software updates, it says AT&T Software Update at the top of the screen, now this doesn't give any errors and it says software up to date, so I'm not sure if this is correct or if there's new software out that it can't connect to update?
Is there any way around this? I know maybe it's possible to ROOT and install a new ROM, but I'd rather avoid that hassle..
Any feedback would be great
I am in the same situation. S7 Active unlocked from EBAY, and using it in Czech Republic with Vodafone sim. Is here chance to get OTA Nougat update?
I'm using one in Canada and flashed the updates described in another thread in this phone's forum. They will reset your phone to factory, but you will have 7.0 nougat and security patches into April, 2017. I doubt any kind of OTA will be forthcoming unless you have an ATT SIM, but I'm not an expert in this at all. I plan on keeping good backups and flashing the updates as they become available. Aside from that, it's a great phone. If they make the s8 active global, then I'll look into getting one some time down the road.
Thanks for the replies. Does the S8 have an active version? I hadn't heard anything on it yet?
so when you flash nougat 7, does it completely wipe and install a new ROM on your phone, or it just updates the AT&T rom, so even with the update, you're still bound to the AT&T settings for updates/wifi calling etc?
Yes, it wipes out the phone completely, you'll have to set it up again. Everything else is same, such as AT&T bloats, wifi calling etc.
Ok thanks for letting me know. So no point I guess if it doesn't solve the issue
I live in Czech Republic. In situation, when I will buy prepaid sim card from AT T, and I will use it in my unlocked S7 Active, it is possible to get OTA Nougat update?
That's not a bad idea, would possibly work for the OTA update, but maybe not if it's not actually connected to AT&T?
It wouldn't work for the wifi calling though I'm sure?
faronium said:
I'm using one in Canada and flashed the updates described in another thread in this phone's forum. They will reset your phone to factory, but you will have 7.0 nougat and security patches into April, 2017. I doubt any kind of OTA will be forthcoming unless you have an ATT SIM, but I'm not an expert in this at all. I plan on keeping good backups and flashing the updates as they become available. Aside from that, it's a great phone. If they make the s8 active global, then I'll look into getting one some time down the road.
Click to expand...
Click to collapse
I'm in Edmonton AB, Yes, there will be nothing for updates or WiFi calling if you are not on the ATT network with their SIM.
Which ROM did you update to, the QD4, or past it?
Keep it rolling
I'd love to know more about using the S7 Active internationally from anyone who has been down that road already. In the UK and considering getting one from Ebay but I would immediately want to update it to Nougat and I'm unsure if this will be possible? I have a Mac laptop in the house and would hope to use that to apply any upgrades. Really appreciate any info you guys have!
mmmbient said:
I'd love to know more about using the S7 Active internationally from anyone who has been down that road already. In the UK and considering getting one from Ebay but I would immediately want to update it to Nougat and I'm unsure if this will be possible? I have a Mac laptop in the house and would hope to use that to apply any upgrades. Really appreciate any info you guys have!
Click to expand...
Click to collapse
ODIN is only available for Windows (Vista/7/8/10). You will have to run Wine for just the Odin program or Boot Camp for the full Windows OS in a partition.
Wine is the easiest solution, start there and install the program, USB drivers.
UnableToResetOldProfile said:
ODIN is only available for Windows (Vista/7/8/10). You will have to run Wine for just the Odin program or Boot Camp for the full Windows OS in a partition.
Wine is the easiest solution, start there and install the program, USB drivers.
Click to expand...
Click to collapse
I to am in the UK and purchased a S7 Active from Ebay. The phone came in a sealed box and worked fine. No AT&T logo at startup or bloatware. However when I rebooted the phone after switching of, an integrity error came up which forced me to wipe/erase the phone. I thought maybe a first time glitch but it did it again and all was lost. Had my old S4 Active so persevered and read info on this post to reflash firmware to QB2 using ODIN. Now note this is the first time i have ever attempted anything like this so complete newbie. However all went well and I now have a phone on Nougat. It reboots without error now. But it is now back to AT&T with logo at Startup and US voice for google navigation etc... Google pay now does work though. I am pleased with my results but would love to have firmware that makes it non AT&T specific for use in the UK, any ideas would be greatly appreciated.

December 26 2017 update LS992ZVE

I just received a new update on G5 sprint to upgrade to LS992ZVE_5. Will it relock my sim card
kleinkel said:
I just received a new update on G5 sprint to upgrade to LS992ZVE_5. Will it relock my sim card
Click to expand...
Click to collapse
i want to know the same, if somebody update please tell us..
Stay safe and don't try.
i take the risk... and the result its... My phone still unlocked ... u can upgrade guys
PD: i unlock my phone with optopus box in past version
Did the update add any new feature
still unlocked!
NinjarD said:
i want to know the same, if somebody update please tell us..
Click to expand...
Click to collapse
I have updated to zve... my phone is still unlocked! :good:
Phone remains unlocked. Unfortunately, it wipes APN data and now I can't go in and edit APN. Anybody have any work arounds? I can't add an APN (no option) in the settings menu (settings - more - mobile networks - access point names) nor in the ##3282# menu with the MSL. It's been a huge pain and I'm currently trying to use this phone in Peru. It can make and receive calls/texts but will not access the internet without being able to add/edit APN's.
Hi, I just want to know can I downgrade ZVE update
Mortal Eternity said:
I have updated to zve... my phone is still unlocked! :good:
Click to expand...
Click to collapse
I have a problem.... I upgraded to zvc ..my phone got unlocked remotely but my facebook..twitter.instagram and whatsapp won't work well with mobile data.. How can I solve
didospike said:
Hi, I just want to know can I downgrade ZVE update
Click to expand...
Click to collapse
No
kleinkel said:
Did the update add any new feature
Click to expand...
Click to collapse
It's a security update, so no. If you guys want to keep your unlock, DON'T UPDATE.
dont update.. As i unlocked my phone from the hidden menu app but as i updated it got locked (and i can't seem to find any solution whosoever).. You cant go back and downgrade and you cant unlock it again with the hidden menu app..
But if anyone knows how to do it please i beg you i need help as it was my gift to my father and i fu..ed it up :crying:
Why,LG, why?
Gah this is so frustrating. I had my phone unlocked by sprint and am currently abroad, but had the wonderful combination of ideas to both update to ZVE and reset network settings. I've already been using this international sim for five months and everything was fine and dandy, but now I can't add an APN so I can't connect to the internet (the apn settings are greyed out) - I even spoke to Sprint for 3 hours and they concluded there's nothing they can do. I'm thinking there's one of three things to be done: change the APN by some "hack" like a dialer code or ADB, revert to previous firmware, or connect to the internet somehow without an APN.
Does anyone know how to do either of three things? Please help.
Update: I called LG and Sprint for a combined total of about 5 hours. LG confirmed that indeed with ZVE they disabled manual changing of APNs (due to "security") and they don't even have a special code or anything to fix that. They said I should ask Sprint to maybe push an ota apn for the international carrier but they said they can't do that. The LG guy said that he would add a ticket (they can't even talk to anyone higher up) to tell the dev team to add an option again to change APNs but I don't know how likely that'll be. It's just super frustrating that LG pushed an update to break international data and now says they can't do anything about it. Reminds me of my bootlooped Nexus 5x that they said they couldn't do anything about. Smh lg, smh.
BuntzenB said:
Gah this is so frustrating. I had my phone unlocked by sprint and am currently abroad, but had the wonderful combination of ideas to both update to ZVE and reset network settings. I've already been using this international sim for five months and everything was fine and dandy, but now I can't add an APN so I can't connect to the internet (the apn settings are greyed out) - I even spoke to Sprint for 3 hours and they concluded there's nothing they can do. I'm thinking there's one of three things to be done: change the APN by some "hack" like a dialer code or ADB, revert to previous firmware, or connect to the internet somehow without an APN.
Does anyone know how to do either of three things? Please help.
Update: I called LG and Sprint for a combined total of about 5 hours. LG confirmed that indeed with ZVE they disabled manual changing of APNs (due to "security") and they don't even have a special code or anything to fix that. They said I should ask Sprint to maybe push an ota apn for the international carrier but they said they can't do that. The LG guy said that he would add a ticket (they can't even talk to anyone higher up) to tell the dev team to add an option again to change APNs but I don't know how likely that'll be. It's just super frustrating that LG pushed an update to break international data and now says they can't do anything about it. Reminds me of my bootlooped Nexus 5x that they said they couldn't do anything about. Smh lg, smh.
Click to expand...
Click to collapse
Welcome to my hell. I tried to warn the community in my comment about this exact issue. I spent weeks talking to Sprint and LG's useless "technical support." LG reps kept insisting that LG has nothing to do with software updates which is completely wrong and extremely ignorant of them to think that. Sprint advanced tech support even conferenced LG in on a call once that lasted about 45 minutes and the LG rep kept saying they don't have anything to do with the updates. Finally, we got him to agree that they did make the updates. But, even that was a waste of time. It wasn't until I wrote to LG through their website that I got several responses (mostly the same as before - walking you through how to change APN settings) but, finally in those conversations, I was able to get LG support to admit that they had a problem with ZVE and that they are the ones that broke it. The last response I got was that their developers are aware of the problem and are working to fix it. It probably won't be fixed until the next software update and they won't give me any timeline as to when that will be. It's been a couple of weeks since I last talked to LG. My advice is to do the same and file a bug error on their website. Calling in is a complete waste of time. They need more reports on this so that they know this is a big issue. You can't even go in with your MSL and change APN's. If they were really worried about security, they would at least allow the carriers to give you permission to modify the APN. Seems completely nonsensical to me.
Never update if you have an unlock. I've said this a hundred times... Maybe you can get on eBay and get a remote unlock.
somy body plz can you post this upgrade ?
kleinkel said:
I just received a new update on G5 sprint to upgrade to LS992ZVE_5. Will it relock my sim card
Click to expand...
Click to collapse
somebody plz can you post this upgrade ? mb it will help to recover some phones who has updated allready.
i think it stores on ota directory on your ls992
acidlenin said:
somebody plz can you post this upgrade ? mb it will help to recover some phones who has updated allready.
i think it stores on ota directory on your ls992
Click to expand...
Click to collapse
It stores in /cache which you can't get to without root. I didn't see how it would help anybody either.
Sympathy, empathy
kephaisrock said:
Welcome to my hell. I tried to warn the community in my comment about this exact issue. I spent weeks talking to Sprint and LG's useless "technical support." LG reps kept insisting that LG has nothing to do with software updates which is completely wrong and extremely ignorant of them to think that. Sprint advanced tech support even conferenced LG in on a call once that lasted about 45 minutes and the LG rep kept saying they don't have anything to do with the updates. Finally, we got him to agree that they did make the updates. But, even that was a waste of time. It wasn't until I wrote to LG through their website that I got several responses (mostly the same as before - walking you through how to change APN settings) but, finally in those conversations, I was able to get LG support to admit that they had a problem with ZVE and that they are the ones that broke it. The last response I got was that their developers are aware of the problem and are working to fix it. It probably won't be fixed until the next software update and they won't give me any timeline as to when that will be. It's been a couple of weeks since I last talked to LG. My advice is to do the same and file a bug error on their website. Calling in is a complete waste of time. They need more reports on this so that they know this is a big issue. You can't even go in with your MSL and change APN's. If they were really worried about security, they would at least allow the carriers to give you permission to modify the APN. Seems completely nonsensical to me.
Click to expand...
Click to collapse
How does one file a bug report? I looked and couldn't find it.
As to the reason I updated my phone, I'm very involved in security and need the newest security patches I can get. Also, I don't know/don't think a remote unlock will help, I think it is actually fully impossible to add an APN at this point... I even had sprint lock and unlock my phone...
BuntzenB said:
How does one file a bug report? I looked and couldn't find it.
As to the reason I updated my phone, I'm very involved in security and need the newest security patches I can get. Also, I don't know/don't think a remote unlock will help, I think it is actually fully impossible to add an APN at this point... I even had sprint lock and unlock my phone...
Click to expand...
Click to collapse
Sometimes you can't have your cake and eat it too. A bug report will get you nowhere. I've filed legitimate bug reports with solutions and didn't even get a reply. They did this on purpose and don't care if it effects you. They don't want you to use your device the way you want, they want you to use it the way they want.
I read this in other post
Idk this work
HiddenMenuCall
Google, download and install HiddenMenuCall_1.7.apk
Go to LTE Settings
Go to APN Settings
Set APN there and use "default,dun,fota" as APN Type
Restart phone
Done!

Pixel XL on Verizon MVNO - April Security patch has disabled my 4G.

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.

G7 Power (XT1955-5) kicked off AT&T network despite being VoLTE compatible?

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

Categories

Resources