Develop Bugs

Where's My Update - Community Edition

Microsoft has announced they will no longer document update releases by carriers, but this is still useful information, so now we must keep track ourselves to know which carriers are lagging behind.
Feel free to edit this spreadsheet when you have received an update notice on your carrier (no login required):
https://docs.google.com/spreadsheet/ccc?key=0AuPW6_Ouc0FidG53dGQ1al9JbGtQWnQ2TTR2Q1pGaGc
Cheers

Looks Great. Although I would suggest that they are completly sorted by Country, then Carrier and then device I guess this is fine for a first version.
Maybe someone can add these changes later with the help of this forum.
Anyway, today I received 8107 but only after using the cable/network disconnect trick on my PC. Should I still mark it as delivering update?

As long as you haven't changed your branding or your ROM to a different carrier, then you can add that your carrier is delivering the update.

slimshady322 said:
Looks Great. Although I would suggest that they are completly sorted by Country, then Carrier and then device I guess this is fine for a first version.
Maybe someone can add these changes later with the help of this forum.
Anyway, today I received 8107 but only after using the cable/network disconnect trick on my PC. Should I still mark it as delivering update?
Click to expand...
Click to collapse
hi, what phone model ? Branded or unbrander ?
I have a titan unbranded, I have try the disconnect trick but it does not work :-(

iosub said:
hi, what phone model ? Branded or unbrander ?
I have a titan unbranded, I have try the disconnect trick but it does not work :-(
Click to expand...
Click to collapse
Unbranded probably wont get the update as there is no one to request it for you! I think that is how it is. I've forced the update on my Titan and worked perfectly fine. Very simple steps. There is link etc in the Titan forum as well as here somewhere.

drupad2drupad said:
Unbranded probably wont get the update as there is no one to request it for you! I think that is how it is. I've forced the update on my Titan and worked perfectly fine. Very simple steps. There is link etc in the Titan forum as well as here somewhere.
Click to expand...
Click to collapse
hi the trick is to disconnect the WiFi (1-2 sec) on the PC after click update,right?
btw, do you have the wifi or 3g on, in the phone?
thanks

iosub said:
hi, what phone model ? Branded or unbrander ?
I have a titan unbranded, I have try the disconnect trick but it does not work :-(
Click to expand...
Click to collapse
I have a Vodafone Germany branded LG E900.
iosub said:
hi the trick is to disconnect the WiFi (1-2 sec) on the PC after click update,right?
btw, do you have the wifi or 3g on, in the phone?
thanks
Click to expand...
Click to collapse
You disconnect your PC from the Internet (in my case via network cable) shortly after you start searching for updates via Zune. I actually disconnected about 5 seconds after searching started, but you can try out what works for you.
I had WiFi enabled and cellular data connection disabled (no 3G and no EDGE), although I only disabled cellular data due to my prepaid flat expiring.

can confirm that unbranded/open market phones not get the 8107 update
omnia 7 -> no update availible in germany, even with cable trick, no chance.
dell venue pro -> no update avaible in germany, even with cable trick, no chance
both no carrier brandings.
I am pissed a lot about microsofts way to schedule udpates to the people, nobody knows where and why any update will arive and there are everywhere anoyiing bugs in wp (keyboard) -> user experience is an F

What does it mean, open phones no update??? no update now, or no update never ever?? Anyway, we pay more for a open phone, to get more updates and even sooner, and at the end, we are the last.

0711 said:
can confirm that unbranded/open market phones not get the 8107 update
omnia 7 -> no update availible in germany, even with cable trick, no chance.
dell venue pro -> no update avaible in germany, even with cable trick, no chance
both no carrier brandings.
I am pissed a lot about microsofts way to schedule udpates to the people, nobody knows where and why any update will arive and there are everywhere anoyiing bugs in wp (keyboard) -> user experience is an F
Click to expand...
Click to collapse
XxAndrexX said:
What does it mean, open phones no update??? no update now, or no update never ever?? Anyway, we pay more for a open phone, to get more updates and even sooner, and at the end, we are the last.
Click to expand...
Click to collapse
I think open phones now get the updates much easily! We only need one carrier to release update and then using cab sender it updates right away! I did that with my unbranded Titan and it only took 8-9 minutes from point A to point B!

there is currectly no update delivery, maybe in the future but if you see microsoft community manager any carrier has to request the update ... but theres no carrier for open market phones, whats the obvious? Open market phones dont receive this update ever and get it maybe with the next (tango?) update.

send a tweet to
Lets send a tweet to @joebelfiore
@joebelfiore my HTC titan is unbranded #wp7 how can I get the 8107 update If is carried depended ?
Iosu
---------- Post added at 10:25 PM ---------- Previous post was at 10:22 PM ----------
drupad2drupad said:
I think open phones now get the updates much easily! We only need one carrier to release update and then using cab sender it updates right away! I did that with my unbranded Titan and it only took 8-9 minutes from point A to point B!
Click to expand...
Click to collapse
I think that is a dangerous method.. If you don't update all the language cabs..
You may not get next HTC update..

So open phones users, we are screwed or what? i got the 7740 update right away. but until now no theethering for example.

yes this is the actual situation, some unbranded phones may not become wlan tethering because it depends on carrier request and dont get the 8107 update (on the official way...with hacks you can have both but this is not the point why i choose windows phone)
sad to see microsoft destroys its own system and screw away their fans

I've got a Samsung Focus (originally a Rogers phone) unlocked and using on Bell Canada network.
I did the wifi disconnect trick and got the 7740 update...doesn't this mean Roger is delivering it?

0711 said:
yes this is the actual situation, some unbranded phones may not become wlan tethering because it depends on carrier request and dont get the 8107 update (on the official way...with hacks you can have both but this is not the point why i choose windows phone)
sad to see microsoft destroys its own system and screw away their fans
Click to expand...
Click to collapse
for tethering you need OEM driver update it's not only OS depended
Iosu

Samsung had the driver ready even before Mango started rolling out. In the official rollout drivers update was already softap implemented and working . I got some ROM that had older OEM drivers date than the Mango rollout and it was there too.
On the other hand, HTC was playing bad and didn't include it. No idea how LG and Dell...

iosub said:
for tethering you need OEM driver update it's not only OS depended
Click to expand...
Click to collapse
i know...but if i use hack i can use internet sharing...if i dont, i am not able to use it
even on german telekom the omnia 7 users got internet sharing
i have german telekom sim but unbranded omnia 7 and dont got it
i know that the dell venue pro is not capable for this feature but omnia 7 was before mango!
When i look at 2 friends, one with branded telekom and one unbranded, both got internet sharing and no one can tell why my friend with unbranded got the update and i am not.
its not the lack of the feature, because i dont care about wlan tethering but who pushs the updates? Microsoft and they hold it back, a total inconsistents in the update process...like with 7740 as os update or even more worse the 8107 update
-> tested the cab sender and all seems to be fine for me but restored my backup because i want it on the official way and not this. I paid not only for the device, for the os, too! The update experience is just bull**** with wp, android doin it better because i can choose nexus phone (never thought i say this) and get every update immediatelly and apple do it the best way since now.
Looks like my next phone will be no windows phone, regardless that i like the system but i dont get what was promised and what i get.

The big issue here is how to confirm all this data.
Maybe some of the information is wrong.

I guess I'll try to keep the Sasktel (Canada) section current. I'm guessing there aren't too many Sasktel people on here with windows phones but I could be surprised.
Also +1 on being annoyed with this whole carrier requested updates.
At least we'll be able to come here to see what's officially available.

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.

Anyone w/S7 Active on Red Pocket? Mobile hotspot & tethering just broke

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?

ATT Port to Verizon S20 G981V Questions

I switched jobs and my work let me keep the S20 5G G981V that was assigned to me. I got it SIM unlocked and ported over to my family's Verizon account. At my new job, the entire warehouse is a cell deadzone but wifi is amazing. I have noticed that wifi calling is not even available for me to use. From what I gather, that's because I'm using the ATT image on the Verizon network. Is flashing the Verizon firmware through ODIN my best bet to getting wifi calling back, or should I go the root and custom ROM route? I've been rooting phones for over 10 years so I'm not new to the process. I went to the Verizon store and they told me I was ****e out of luck. Thanks!!!

pogibry said:
I switched jobs and my work let me keep the S20 5G G981V that was assigned to me. I got it SIM unlocked and ported over to my family's Verizon account. At my new job, the entire warehouse is a cell deadzone but wifi is amazing. I have noticed that wifi calling is not even available for me to use. From what I gather, that's because I'm using the ATT image on the Verizon network. Is flashing the Verizon firmware through ODIN my best bet to getting wifi calling back, or should I go the root and custom ROM route? I've been rooting phones for over 10 years so I'm not new to the process. I went to the Verizon store and they told me I was ****e out of luck. Thanks!!!
Click to expand...
Click to collapse
I have a similar situation: I'm trying to get VZW Wi-Fi calling to work on an unlocked international S20+ (SM-G986B). Verizon told me they allow WI-Fi calling on BYOD equipment and that my account is properly provisioned. However:
There is no evidence of any Wi-Fi calling settings anywhere in the phone's UI.
System logs (e.g., logcat | grep -e UNWFC -e EPDG) show lots of info about not being registered for Wi-Fi calling.
IMS Settings show that VoLTE is provisioned, but not HD Voice. VoLTE clearly works.
Samsung's Wi-Fi calling stack is supposed to be pretty universal these days, and to a large extent, it delivers: when I put in a T-Mobile SIM, Wi-Fi calling comes up right away. So it seems that the Wi-Fi calling stack on my phone isn't completely out to lunch. But Verizon's Wi-Fi calling implementation appears to not be so cut and dry.
Last night I popped open a SM-G986U (supposedly universal carrier-unlocked US Snapdragon S20+) firmware image in an attempt to understand what Verizon is doing for their Wi-Fi calling, and it appears I opened a can of worms.. I found a whole lot of Verizon-specific content in there that I don't have.
Spoiler: system.img find output
Code:
{tuxomatic /mnt/G986USQS1BTJ2_OYN1BTJ2/AP} # find system -type f | grep -iP 'vz|verizon'
system/etc/permissions/com.verizon.os.xml
system/etc/permissions/com.verizon.phone.xml
system/etc/permissions/com.verizon.provider.xml
system/etc/permissions/privapp-permissions-com.customermobile.preload.vzw.xml
system/etc/permissions/privapp-permissions-com.securityandprivacy.android.verizon.vms.xml
system/etc/permissions/privapp-permissions-com.verizon.llkagent.xml
system/etc/permissions/privapp-permissions-com.verizon.loginengine.unbranded.xml
system/etc/permissions/privapp-permissions-com.vzw.apnservice.xml
system/etc/permissions/privapp-permissions-com.vzw.ecid.xml
system/etc/permissions/verizon_net_sip_library.xml
system/etc/permissions/vzwapnlib.xml
system/etc/init/vzsysprop.rc
system/carrier/VZW/permissions/ecid-hiddenapi-package-whitelist.xml
system/carrier/VZW/permissions/snp-hiddenapi-package-whitelist.xml
system/carrier/VZW/permissions/mvm-hiddenapi-package-whitelist.xml
system/carrier/VZW/permissions/privapp-permissions-com.verizon.obdm.xml
system/carrier/VZW/permissions/privapp-permissions-com.verizon.mips.services.xml
system/carrier/VZW/permissions/vzcloud-hiddenapi-package-whitelist.xml
system/carrier/VZW/permissions/privapp-permissions-com.verizon.onetalk.dialer.xml
system/carrier/VZW/permissions/privapp-permissions-com.samsung.advancedcalling.xml
system/carrier/VZW/permissions/whitelist_com.LogiaGroup.LogiaDeck.xml
system/carrier/VZW/permissions/vla-hiddenapi-package-whitelist.xml
system/carrier/VZW/permissions/privapp-permissions-com.vzw.hss.myverizon.xml
system/carrier/VZW/permissions/mvs-hiddenapi-package-whitelist.xml
system/carrier/VZW/permissions/privapp-permissions-com.telecomsys.directedsms.android.SCG.xml
system/carrier/VZW/dummy.txt
system/carrier/VZW/priv-app/HuxExtension/HuxExtension.apk
system/carrier/VZW/priv-app/com.customermobile.preload.vzw/com.customermobile.preload.vzw.apk
system/carrier/VZW/priv-app/MyVerizonService/MyVerizonService.apk
system/carrier/VZW/priv-app/IgniteVerizon/IgniteVerizon.apk
system/carrier/VZW/priv-app/MyVerizonMobile/MyVerizonMobile.apk
system/carrier/VZW/priv-app/LocationAgent/LocationAgent.apk
system/carrier/VZW/priv-app/AdvancedCalling/AdvancedCalling.apk
system/carrier/VZW/priv-app/SNP_stub/SNP_stub.apk
system/carrier/VZW/priv-app/OneTalkDialer/OneTalkDialer.apk
system/carrier/VZW/priv-app/VzwImsApiService/VzwImsApiService.apk
system/carrier/VZW/priv-app/canid_stub/canid_stub.apk
system/carrier/VZW/priv-app/LLKAgent/LLKAgent.apk
system/bin/vzsysprop
system/priv-app/VZWAPNService_sku/VZWAPNService_sku.apk
system/priv-app/VzCloud/VzCloud.apk
system/framework/VZWAPNLib_VZW.apk
system/framework/com.verizon.os.jar
system/framework/com.verizon.phone.jar
system/framework/com.verizon.provider.jar
system/framework/oat/arm/com.verizon.os.odex
system/framework/oat/arm/com.verizon.os.vdex
system/framework/oat/arm/com.verizon.phone.odex
system/framework/oat/arm/com.verizon.phone.vdex
system/framework/oat/arm/verizon.net.sip.odex
system/framework/oat/arm/verizon.net.sip.vdex
system/framework/oat/arm64/com.verizon.os.odex
system/framework/oat/arm64/com.verizon.os.vdex
system/framework/oat/arm64/com.verizon.phone.odex
system/framework/oat/arm64/com.verizon.phone.vdex
system/framework/oat/arm64/verizon.net.sip.odex
system/framework/oat/arm64/verizon.net.sip.vdex
system/framework/verizon.net.sip.jar
Spoiler: optics.img find output
Code:
{tuxomatic /mnt/G986USQS1BTJ2_OYN1BTJ2/CSC } # find optics/configs/carriers/single/VZW -type f
optics/configs/carriers/single/VZW/conf/cscfeature.xml
optics/configs/carriers/single/VZW/conf/cscfeature_network.xml
optics/configs/carriers/single/VZW/conf/customer.xml
optics/configs/carriers/single/VZW/conf/omc.info
Spoiler: prism.img find output
Code:
{tuxomatic /mnt/G986USQS1BTJ2_OYN1BTJ2/CSC # find prism/etc/carriers/single/VZW -type f
etc/carriers/single/VZW/userdatacfg.xml
etc/carriers/single/VZW/enforcedeletepackage.txt
etc/carriers/single/VZW/oathpartnerid.conf
etc/carriers/single/VZW/contents.db
etc/carriers/single/VZW/sales_code.dat
etc/carriers/single/VZW/VZW_keystrings.dat
etc/carriers/single/VZW/csc_ringtones_list.txt
etc/carriers/single/VZW/imsupdate.json
etc/carriers/single/VZW/default_workspace_easy.xml
etc/carriers/single/VZW/default_apps.xml
etc/carriers/single/VZW/default_apps_upsm.xml
etc/carriers/single/VZW/enforceskippingpackages.txt
etc/carriers/single/VZW/default_workspace.xml
etc/carriers/single/VZW/unique_text.xml
etc/carriers/single/VZW/hidden_apks_list.txt
etc/carriers/single/VZW/default_application_order.xml
Just based on their names, a quick glance at the packages baked into system.img suggests the following are reasonably likely to be associated with Wi-Fi calling:
VZWAPNLib_VZW.apk
VZWAPNService_sku.ap
VzwImsApiService.apk
AdvancedCalling.apk
The big question is AdvancedCalling.apk?! Is this some sort of proprietary implementation of Wi-Fi calling and VoLTE?! Is it possible that Wi-Fi calling on Verizon isn't possible using the Samsung Unified Wi-Fi Calling app? And is there special APN config that needs to get pushed to my phone to enable EPDG connectivity required for Wi-Fi calling?
There's a whole lot in the CSC images (optics.img and prism.img) too. Of particular note, prism.img's imsupdate.json seems to define some sort of E911 IMS configuration. I wouldn't be suprised if that was a prerequiste for WI-Fi calling.
I also find interesting the declaration of packages allowed during power saving and emergency modes (suggesting these packages are necessary for core functionality like calling):
Spoiler: packages allowed during power saving mode
Code:
{tuxomatic /mnt/G986USQS1BTJ2_OYN1BTJ2/CSC } # grep -Po '<.*?PowerSaving.*>\K.*?(?=<.*?>)' optics/configs/carriers/single/VZW/conf/cscfeature.xml.out | tr ',' '\n'
com.sec.android.app.cmas
com.sec.imsservice
com.samsung.sdm
com.samsung.syncmlservice
com.samsung.syncmlphonedataservice
com.samsung.sdm.sdmviewer
com.vcast.mediamanager
com.vzw.apnservice
com.verizon.vzwavs
com.motricity.verizon.ssodownloadable
com.vzw.hss.myverizon
com.verizon.mips.services
com.cequint.ecid
com.samsung.vvm
com.LogiaGroup.LogiaDeck
com.vzw.hss.myverizontabletlte
com.vzw.ecid
com.telecomsys.directedsms.android.SCG
com.asurion.android.verizon.vms
com.samsung.unifiedsettingsservice
com.samsung.unifiedtp
com.verizon.messaging.vzmsgs
com.sec.android.app.setupwizard
com.samsung.advancedcalling
com.securityandprivacy.android.verizon.vms
com.samsung.usbyod
com.verizon.onetalk.dialer
Spoiler: packages allowed during emergency mode
Code:
{tuxomatic /mnt/G986USQS1BTJ2_OYN1BTJ2/CSC } # grep -Po '<.*?EmergencyMode.*>\K.*?(?=<.*?>)' optics/configs/carriers/single/VZW/conf/cscfeature.xml.out | tr ',' '\n'
com.sec.android.app.cmas
com.samsung.sdm
com.samsung.syncmlservice
com.ipsec.service
com.sec.android.providers.iwlansettings
com.sec.android.providers.mapcon
com.sec.providers.assisteddialing
com.sec.vowifispg
com.vzw.apnservice
com.motricity.verizon.ssodownloadable
com.vzw.hss.myverizon
com.verizon.mips.services
com.sec.unifiedwfc
com.samsung.vzwapiservice
com.samsung.advancedcalling
Interestingly, I see references to the packages I called out above. The also are likely involved too:
com.ipsec.service
com.sec.vowifispg
Even the Samsung Unified WiFI calling app made the list.
Ideally, we need some input here from someone that has VZW Wi-Fi calling up and running on a rooted device (and who is willing to do a bit of experimentation!) that can help us understand what components are involved/required. I don't know if there is anything to block you from installing the universal or VZW-specific firmware on your device, though based on what I remember from past reading on the topic it seems likely to be a large step in the right direction; please confirm for yourslef. I'm in a bit tougher spot than you because flashing the VZW firmware simply isn't an option on my Exynos device. I also don't want any unneeded extra VZW bloat on my system, but based on what I've seen it looks like I'll have to merge at least part of the VZW CSC into my ROM image.
Speaking of rooting and custom ROMs, have you managed to get the bootloader unlocked? As I understand, this is a nontrivial effort for US-based Snapdragon models and currently only available as a commercial unlocking service. The feedback seems pretty good but it appears that the service is limited to a handful of models running particular bootloader revisions.

Wow that's a lot of info! Thank you for that I tried installing the U firmware but it kept failing in Odin; I'm going to try the V tonight and see if it will work.
For unlocking the bootloader, I haven't done that yet. If I do, I will go all the way and load a custom ROM; I'm trying to avoid that for now UNLESS we know that wifi calling works on those custom ROMs, like Lineage or AOSP, etc...

pogibry said:
Wow that's a lot of info! Thank you for that I tried installing the U firmware but it kept failing in Odin; I'm going to try the V tonight and see if it will work.
For unlocking the bootloader, I haven't done that yet. If I do, I will go all the way and load a custom ROM; I'm trying to avoid that for now UNLESS we know that wifi calling works on those custom ROMs, like Lineage or AOSP, etc...
Click to expand...
Click to collapse
I guess it's not surprising they block installation of the universal firmware on a carrier locked model. Though that being the case, flashing Verizon firmware on an AT&T branded phone doesn't sound much more promising. How did that go?
My expectation is that going towards the likes of Lineage or even AOSP are going to take you further from a working Wi-Fi calling setup on a network with a non-standard implementation like Verizon.
BTW, do you by chance know what package is used to make the ipsec connection to the EPDG? I'm getting the impression that com.ipsec.service is an obsolete component that no longer exists on our phones. Interestingly though, my phone has /system/bin/charon and a handful of supporting libraries; these are components of the excellent, industrial-strength package strongSwan and could be responsible for that connection, though if that's the case, I still don't understand how it gets configured.

I wasn't able to get the link for the other firmware to work last night; I'm going to try again today.
For the EPDG, that part is over my head. I like rooting phones but I've never developed and made my own ROM's before.

Just got it downloaded, tried through ODIN and it failed. Is it because my bootloader isn't locked? I've never used ODIN with a phone that wasn't already unlocked.

pogibry said:
I wasn't able to get the link for the other firmware to work last night; I'm going to try again today.
For the EPDG, that part is over my head. I like rooting phones but I've never developed and made my own ROM's before.
Click to expand...
Click to collapse
In LTE, voice communication is carried over IP using trusted transport formed over the carrier's LTE network. Wi-Fi calling uses an analogous scheme, but since you are using a direct internet connection rather than the carrier's own trusted network connection, an IPsec VPN tunnel is instead used to create the trusted transport. The ePDG (evolved packet data gateway) is the device that terminates that VPN connection on the carrier end, and acts as the entry point into the carrier network for Wi-Fi calling; here is a nice little primer on ePDGs and IPsec. If your phone is unable to establish the requisite VPN tunnel, for example because the VPN software is not installed on your phone, there is precisely zero chance of Wi-Fi calling working. That's why I'm so interested in understanding what package is used to form the VPN connection. It's not clear to me what all the strongSwan instance I found in the ROM image is used for: it could be used for one or more of (a) the built in VPN client available on the Connections page, (b) the KNOX VPN client, or (c) Wi-Fi calling.
This is my first attempt at making a ROM. The quality and selection of custom ROMs seems to have been steadily decreasing in recent years, and I've never been able to find exactly what I was looking for out of the box anyway. Moreover, most ROM developers aggressively upgrade the base image of their ROMs which is exactly the opposite of the approach I'm looking for: I'd much rather stay on Android 10 for the foreseeable future rather than deal with 11 or (very soon) 12 and deal with compatibility issues with Magisk and all my favorite modules.
Overall, it's been a painful experience. Between the low quality of the tools and Samsung's countless security measures, it has resulted in a lot of hair pulling; I even ended up rolling my own kitchen. And now there's this Wi-Fi calling problem. I see plenty of posts complaining about difficulties with the feature on Verizon, but no one explaining how they solved it.
pogibry said:
Just got it downloaded, tried through ODIN and it failed. Is it because my bootloader isn't locked? I've never used ODIN with a phone that wasn't already unlocked.
Click to expand...
Click to collapse
I have pretty much no experience with the locked bootloader phones, but it sure wouldn't surprise me if carrier issued devices are keyed in such a way so that they won't accept the universal firmware or firmware of another carrier.

Bumping this thread. Verizon can't flash their software for me. They referred me to Geek Squad and they said they can't. From what I've read online about ODIN, it can work, but you legit need to crack the combination of things to get it to work. Since my bootloader is locked, I'm pretty sure I need the patched version of ODIN (?). I tried the bootloader version that matches mine but with the Verizon firmware and it fails, giving an error message of a modem mismatch. I grabbed the CP file from the ATT version and used that with instead of the Verizon CP file and this time I got a re-partition error message, which I don't get because I don't have the "ReParition" box selected within ODIN. There has got to be a way to get the Verizon firmware on this phone without having to unlock my bootloader (I did try and apparently my phone isn't able to be unlocked yet).

Did you ever get Wi-Fi calling working or at least get your bootloader unlocked? I finally got Wi-Fi calling working on my unlocked SM-G986B, and if you're able to bootloader unlock/root, I'd imagine you could do something similar.