Develop Bugs

[Q] LG G3 McaFee issues big time

Hi everyone
This is my first post here and a sad one at present.
i restored my G3 back to stock last night and all seemed to go well but now my phone says McaFee mobile security your device is locked and is asking for a pin to unlock it.
i don't have this pin and i don't have a clue how to get it, i purchased the phone as a used mobile and it was all good until i did the root back to stock because lollipop was causing some serious lag issues.
can anyone please help me with a way around this if possible
big thanks in advance

Contact the person who sold you the phone. He entered the PIN. McAfee thinks the phone is stolen now.
You can try flashing stock firmware (kdz) file with CSE flash. It could help
http://forum.xda-developers.com/showthread.php?t=2785089

DelBoy said:
Contact the person who sold you the phone. He entered the PIN. McAfee thinks the phone is stolen now.
You can try flashing stock firmware (kdz) file with CSE flash. It could help
http://forum.xda-developers.com/showthread.php?t=2785089
Click to expand...
Click to collapse
Thanks for the reply
I contacted the seller and it seems the phone is infact 3rd hand if not more and basically he does not have the pin
i did the firmware flash and thats why I'm in the pickle now as the phone knows its been factory reset and MacaFee kicks in for security, the sellers not interested as he sold me the phone working which it was but lollipop was just killing the phone when i updated it and after trying to get back to kitkat I'm in brick land

If anyone else has a suggestion or can help then please do get in touch if possible
Thank you

In fact the previous owner set up an account here: McAffee Mobile Security.
Contact someone there and explain your situation.

I will contact McAfee for sure and see if they can help me but I do believe the answer I will receive will be can't help and I come to this conclusion through general security measure because I'm pretty sure anyone could steel a phone and call them up asking for the unlock code but let's see what they say.
If anyone has had this happen and have found a way around the issue please do send me a private message if you don't wish to publish it as I am stuck big time at present
Cheers

I have just got off the phone with McAfee customer support here in the UK and well to be blunt I'm up that creek without a paddle
Nothing they can do for me because even though the software licence is valid and I have the original owners email address that confirms this because I don't have a prof of purchase for the phone like a receipt or mobile number for the original owner they can not help me I'm anyway
All they said I can do is to keep emailing the owner with this email address and hope for a reply and if I get one enter the pin and it will unlock
So people be very careful if you don't have the pin for your phone as it looks like I have just lost £240 and now have a brick to look at
Again if any of you wonderfully cleaver people know of a fix please do help me out if possible
Thanks
Joe

talk2joe said:
I have just got off the phone with McAfee customer support here in the UK and well to be blunt I'm up that creek without a paddle
Nothing they can do for me because even though the software licence is valid and I have the original owners email address that confirms this because I don't have a prof of purchase for the phone like a receipt or mobile number for the original owner they can not help me I'm anyway
All they said I can do is to keep emailing the owner with this email address and hope for a reply and if I get one enter the pin and it will unlock
So people be very careful if you don't have the pin for your phone as it looks like I have just lost £240 and now have a brick to look at
Again if any of you wonderfully cleaver people know of a fix please do help me out if possible
Thanks
Joe
Click to expand...
Click to collapse
have you tried any diff roms or cyanogen mod? maybe a diff software wont have the mcafee on like cyanogen mod

No I haven't tried to put any other software on because I can no longer access download mode as the McAfee has a kill switch and won't let me do anything from what I can see.
All I can do it switch on my device I can't even get into setting properly because the McAfee block kicks in to quickly and I've tried probably 20 odd times
If anyone can explain a way for me to flash another operating system onto my handset please get in touch as I will try anything rather than have a dead phone and e out of pocket
Cheers

Take it some private repair shop. They will solve your issue.

DelBoy said:
Take it some private repair shop. They will solve your issue.
Click to expand...
Click to collapse
If i can not get around this fix i will defo take it to a shop as you mentioned and try my luck.
but i have some news
i have managed to get into the phone and it allows me to gain access without lock down but no sim installed yet.
i followed the steps from an earlier thread on how to get to buddy lock code and gain access to Macafee software but i do not see or can not figure out how to enter a buddy number as suggested in the last part of the solution
anyone know how to enter a buddy number please
cheers

Bump up just for those who might have missed this thread
Anyone know how I add buddy number please
Cheers

open the apk. on top , on the right there are like three dots. settings, scroll down to find device-buddy list.
under settings you can also see subscription info. there you can find the email of the person who set up the apk.

Well just wanted to say thanks to everyones help who replied or sent me a ptivate message
My phone is back and working well and i now have a new password for mcafee
Took some time and my device went through a few stalls n freezing trips but after being persistant i got around the issues.
Cheers to all

talk2joe said:
Well just wanted to say thanks to everyones help who replied or sent me a ptivate message
My phone is back and working well and i now have a new password for mcafee
Took some time and my device went through a few stalls n freezing trips but after being persistant i got around the issues.
Cheers to all
Click to expand...
Click to collapse
how were you able to enter the buddy code?

i have the same problem..i cant access my lg g3 because of mcafee.. i dont know the pincode.. im the 3rd owner of the phone and i dont know how to contact the first person who bought this.. im begging you guys please help me

cass10 said:
i have the same problem..i cant access my lg g3 because of mcafee.. i dont know the pincode.. im the 3rd owner of the phone and i dont know how to contact the first person who bought this.. im begging you guys please help me
Click to expand...
Click to collapse
Deleted

here is the method :https://forum.xda-developers.com/lg...are-method-t3534946/post70470494#post70470494

LG LS-980 Sprint to NET10 driving me crazy!!!!!

Hello,
First, let me express my deepest thanks in advance for those of you who may be of assistance. I have visited this site many times over the years when I needed to find the answers to smartphone related issues (mostly rooting..etc). I have usually found the information that I needed via reading posts and trial and error; however, I am having a problem that I cannot find the answer to and it is frustrating the crap out of me.
So, here goes:
I bought a LG LS980 off of Ebay. It was locked to Sprint and I had a friend of mine root it (since I couldn't figure it out and it ended up being that the firmware had to be downgraded since a patch was bumped to it) and unlocked (or so i was told, but I do not know how to find out). It is currently running Cyanogenmod 12.1. I wanted to use my old phone's SIM and pop it into my new phone so that I could enjoy it (the old phone was a Nexus and ran hella slow). So, anyway.... I contacted NET10 customer support since that is my carrier and explained what I wanted to do. They let me know that as long as it is unlocked that I would be able to just swap the SIM into the new phone and should be good to go. They checked my IMEI and said that the phone was, indeed, compatible and as long as it is unlocked it should just be a matter of a simple ROM swap. Not the case. I put the SIM in and booted it up. It went from No Service to saying "Sprint" on the upper left hand corner. I try to make a call and it states that, "The code or number that I am dialing is incorrect, please try the code or number again". I looked this up on the internet and didn't find a focused answer. I talked to my friend and he stated that I may have to set up a new APN profile.
I have checked the APN settings on it and all of the APN profiles have the prefix "Verizon". I used this mini tutorial at http://forums.androidcentral.com/goo...-settings.html along with the NET10 settings to try and make a profile. Both of their workarounds don't seem to work. I can enter about half of the information and then either click BACK or SAVE and then the profile is gone. I am not sure this is the reason that my phone is not working, but I thought I would give it a try. I have also tried to use this tutorial: http://forum.xda-developers.com/showthread.php?t=2798566 as a loose guide, TWRP installed. Keep in mind that I believe that my firmware was rolled back to ZVE. and not ZVD. When I have tried to edit the build.prop values at the tutorial states it does not save. Also, there are two lines that are not even in my build.prop (ro.build.target_operator and persist.service.crash.enable). When I have tried to edit or add it adds them but does not save and definitely does not persist through reboot. I feel as if I am close to getting the phone to work, but I am unsure where to go from here. I really do NOT want to have to go back to a stock ROM and all of that because....well.... my friend did the rooting and installing of cyanogenmod and I don't want to risk undoing all of his work and having to pay $ to have it done all over again (I have rooted phones..etc, but this G2 was a MOFO because of the firmware patch for me). NET10 CS and TS was of no help and they gave me a ticket number (and to tell you the truth the are outsourced and I can't understand what their reps are saying). So, does anyone have any advice or threads that I can look at? Like I said, I feel as if it is close, but no matter what number I call it says that recording. I get no incoming calls (although it rings when listening to the incoming calling phone's speaker). I am also unable to send or receive SMS or MMS messages. Any help would be greatly appreciated. I am not the most technically savvy person, but I can answer your questions to the best of my ability and I am good at following directions. (I have about 5-6 phone root/ROMS under my belt and even 2-3 SPRINT to NET10 activations, but this one is just perplexing the crap out of me) . Could it be that the phone is not unlocked???? How do I check this??? Is there a way??? When I put in the NET10 SIM it never asked me for an unlock code so I am assuming that my friend unlocked it? I have also tried "Turn the phone ON and type 2945#801# If nothing happens, type 2945#802# or 2945#*803#" and no hidden menu appears asking for an unlock code.

LG G2 Sprint to Net 10 not working.... almost there...what am I missing????

Hello,
First, let me express my deepest thanks in advance for those of you who may be of assistance. I have visited this site many times over the years when I needed to find the answers to smartphone related issues (mostly rooting..etc). I have usually found the information that I needed via reading posts and trial and error; however, I am having a problem that I cannot find the answer to and it is frustrating the crap out of me.
So, here goes:
I bought a LG LS980 off of Ebay. It was locked to Sprint and I had a friend of mine root it (since I couldn't figure it out and it ended up being that the firmware had to be downgraded since a patch was bumped to it) and unlocked (or so i was told, but I do not know how to find out). It is currently running Cyanogenmod 12.1. I wanted to use my old phone's SIM and pop it into my new phone so that I could enjoy it (the old phone was a Nexus and ran hella slow). So, anyway.... I contacted NET10 customer support since that is my carrier and explained what I wanted to do. They let me know that as long as it is unlocked that I would be able to just swap the SIM into the new phone and should be good to go. They checked my IMEI and said that the phone was, indeed, compatible and as long as it is unlocked it should just be a matter of a simple ROM swap. Not the case. I put the SIM in and booted it up. It went from No Service to saying "Sprint" on the upper left hand corner. I try to make a call and it states that, "The code or number that I am dialing is incorrect, please try the code or number again". I looked this up on the internet and didn't find a focused answer. I talked to my friend and he stated that I may have to set up a new APN profile.
I have checked the APN settings on it and all of the APN profiles have the prefix "Verizon". I used this mini tutorial at http://forums.androidcentral.com/goo...-settings.html along with the NET10 settings to try and make a profile. Both of their workarounds don't seem to work. I can enter about half of the information and then either click BACK or SAVE and then the profile is gone. I am not sure this is the reason that my phone is not working, but I thought I would give it a try. I have also tried to use this tutorial: http://forum.xda-developers.com/show....php?t=2798566 as a loose guide, TWRP installed. Keep in mind that I believe that my firmware was rolled back to ZVE. and not ZVD. When I have tried to edit the build.prop values at the tutorial states it does not save. Also, there are two lines that are not even in my build.prop (ro.build.target_operator and persist.service.crash.enable). When I have tried to edit or add it adds them but does not save and definitely does not persist through reboot. I feel as if I am close to getting the phone to work, but I am unsure where to go from here. I really do NOT want to have to go back to a stock ROM and all of that because....well.... my friend did the rooting and installing of cyanogenmod and I don't want to risk undoing all of his work and having to pay $ to have it done all over again (I have rooted phones..etc, but this G2 was a MOFO because of the firmware patch for me). NET10 CS and TS was of no help and they gave me a ticket number (and to tell you the truth the are outsourced and I can't understand what their reps are saying). So, does anyone have any advice or threads that I can look at? Like I said, I feel as if it is close, but no matter what number I call it says that recording. I get no incoming calls (although it rings when listening to the incoming calling phone's speaker). I am also unable to send or receive SMS or MMS messages. Any help would be greatly appreciated. I am not the most technically savvy person, but I can answer your questions to the best of my ability and I am good at following directions. (I have about 5-6 phone root/ROMS under my belt and even 2-3 SPRINT to NET10 activations, but this one is just perplexing the crap out of me) . Could it be that the phone is not unlocked???? How do I check this??? Is there a way??? When I put in the NET10 SIM it never asked me for an unlock code so I am assuming that my friend unlocked it? I have also tried "Turn the phone ON and type 2945#801# If nothing happens, type 2945#802# or 2945#*803#" and no hidden menu appears asking for an unlock code.

You can unlock your Sprint phone for GSM but you can't activate it to Verizon or its MVNOs.

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?