[GUIDE] Using Retail XT1607 With Verizon - Moto G4 Play Guides, News, & Discussion

UPDATE: Confirmed working on Squid's 11-08 build of Lineage 14.1 as well as various other Oreo/Pie ROMs
I've heard people making claims that the unlocked retail G4 Play (xt1607) doesn't actually work on Verizon's network--and this is true according to Verizon's own site even when you run the IMEI check. After a while I got everything to work just fine on mine, so I'll post here what I did and things I was told by the Verizon people. I apologize if it seems a bit unorganized, I just wanted to rush this out there ASAP since it seems like this is a known problem and I'd hate to see people returning their perfectly good G4 Plays for a supposed problem that got fixed
(Probably the most important thing here) They claim the activation process will take 5-10 minutes, but apparently this is a known problem with certain unlocked Motorola phones. Give it a few hours to see if it'll work eventually. This very well might be what eventually fixed it for me but I'll follow this up below with everything else we tried during this time anyway
Make sure you are running completely stock firmware so it can "provision" properly, at least initially. I remember with my friend's E4 Plus he had to be running on stock at first to get Verizon to recognize and accept his phone before he could flash Lineage on it and use it with that. Apparently this has something to do with outdated APNs that custom ROMs use, or perhaps Verizon just doesn't like custom ROMs at first and they detect/block it. Whatever the case may be, the TWRP Flashable Stock Nougat by Q9Nap will work just fine. What I did was a full wipe before flashing the stock firmware in TWRP. So not only did I do a factory reset, I wiped /system as well before flashing. To do this go to the Advanced Wipe menu in TWRP and check everything except Internal Storage and SD storage
When you're initially getting the SIM card for it, it seemed like they had to apparently tie it to an initial IMEI for it to work. Verizon's system of course said my G4 Play wasn't compatible but the rep said he'd put in another phone's IMEI that did work and then transfer it to my new phone once it was initialized initially. See if the Verizon rep can do this for you as well
If you give it a while running on stock firmware and it still doesn't fix the issue, proceed to the steps below
During the troubleshooting process the Verizon representative at the store took out my SIM card and put it in one of his Verizon phones to test as well. This was just to ensure the SIM itself is working properly which mine was. He made a couple of test calls and test texts with my SIM in his phone and it was all working fine. Obviously I'm no expert with Verizon's activation and provisioning process but perhaps this aided in the SIM being activated or whatever on their end. If you aren't at a Verizon store, find a friend or family member that has a Verizon smartphone and put your SIM in their device for a little while and do a test call or two
Go into the phone's hidden network menu (Dialer>*#*#4636#*#*>Phone Info) and set the Perferred Network Type to LTE/CDMA/UMTS Auto. Give it a minute or two and see if that changes anything
If none of the above is working, or if you're like me where you only had partial service (data/text is fine but cant make or receive calls because you're put in some weird restricted call mode on their network) go to TWRP and do another factory reset. Reboot afterwards and give it a few minutes to see if that fixed anything
If none of the above works or after factory resetting you lose ALL signal and its stuck in a Searching For Signal state (like mine was), go into fastboot and issue the following commands to wipe your phone's modem partitions/settings: "fastboot erase modemst1" and "fastboot erase modemst2". Reboot and give it a bit to see if that fixes it. This is what I believe finally fixed it for me
As of writing this I am running the TWRP flashable stock nougat and have full call/text/LTE capability on my G4 Play with the Preferred Network Type set to LTE/CDMA/UMTS auto. I couldn't get VoLTE working unfortunately, but the rest of the base functionality is all good (which is still better than others I've seen online that say their G4 Play flat out won't work at all)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Have you had VoLTE working? I can't remember if I had it working a couple of years ago when I got this phone. Moved the SIM from a Nokia 929, so already had a good SIM. But I've never had the original firmware back on the device - always some ROM or other.
jasonmerc said:
UPDATE: Confirmed working on Squid's 11-08 build of Lineage 14.1 as well as various other Oreo/Pie ROMs
I've heard people making claims that the unlocked retail G4 Play (xt1607) doesn't actually work on Verizon's network--and this is true according to Verizon's own site even when you run the IMEI check. After a while I got everything to work just fine on mine, so I'll post here what I did and things I was told by the Verizon people. I apologize if it seems a bit unorganized, I just wanted to rush this out there ASAP since it seems like this is a known problem and I'd hate to see people returning their perfectly good G4 Plays for a supposed problem that got fixed
(Probably the most important thing here) They claim the activation process will take 5-10 minutes, but apparently this is a known problem with certain unlocked Motorola phones. Give it a few hours to see if it'll work eventually. This very well might be what eventually fixed it for me but I'll follow this up below with everything else we tried during this time anyway
Make sure you are running completely stock firmware so it can "provision" properly, at least initially. I remember with my friend's E4 Plus he had to be running on stock at first to get Verizon to recognize and accept his phone before he could flash Lineage on it and use it with that. Apparently this has something to do with outdated APNs that custom ROMs use, or perhaps Verizon just doesn't like custom ROMs at first and they detect/block it. Whatever the case may be, the TWRP Flashable Stock Nougat by Q9Nap will work just fine. What I did was a full wipe before flashing the stock firmware in TWRP. So not only did I do a factory reset, I wiped /system as well before flashing. To do this go to the Advanced Wipe menu in TWRP and check everything except Internal Storage and SD storage
When you're initially getting the SIM card for it, it seemed like they had to apparently tie it to an initial IMEI for it to work. Verizon's system of course said my G4 Play wasn't compatible but the rep said he'd put in another phone's IMEI that did work and then transfer it to my new phone once it was initialized initially. See if the Verizon rep can do this for you as well
If you give it a while running on stock firmware and it still doesn't fix the issue, proceed to the steps below
During the troubleshooting process the Verizon representative at the store took out my SIM card and put it in one of his Verizon phones to test as well. This was just to ensure the SIM itself is working properly which mine was. He made a couple of test calls and test texts with my SIM in his phone and it was all working fine. Obviously I'm no expert with Verizon's activation and provisioning process but perhaps this aided in the SIM being activated or whatever on their end. If you aren't at a Verizon store, find a friend or family member that has a Verizon smartphone and put your SIM in their device for a little while and do a test call or two
Go into the phone's hidden network menu (Dialer>*#*#4636#*#*>Phone Info) and set the Perferred Network Type to LTE/CDMA/UMTS Auto. Give it a minute or two and see if that changes anything
If none of the above is working, or if you're like me where you only had partial service (data/text is fine but cant make or receive calls because you're put in some weird restricted call mode on their network) go to TWRP and do another factory reset. Reboot afterwards and give it a few minutes to see if that fixed anything
If none of the above works or after factory resetting you lose ALL signal and its stuck in a Searching For Signal state (like mine was), go into fastboot and issue the following commands to wipe your phone's modem partitions/settings: "fastboot erase modemst1" and "fastboot erase modemst2". Reboot and give it a bit to see if that fixes it. This is what I believe finally fixed it for me
As of writing this I am running the TWRP flashable stock nougat and have full call/text/LTE capability on my G4 Play with the Preferred Network Type set to LTE/CDMA/UMTS auto. Soon I will be flashing a Pie based custom ROM to see if it works on custom firmware too now that (hopefully) the initial provisioning is done. I will post back my results soon
Click to expand...
Click to collapse

RedCrane3 said:
Have you had VoLTE working? I can't remember if I had it working a couple of years ago when I got this phone. Moved the SIM from a Nokia 929, so already had a good SIM. But I've never had the original firmware back on the device - always some ROM or other.
Click to expand...
Click to collapse
That's something I shouldve mentioned, I did not get VoLTE working on this regardless of stock/custom firmware. So perhaps it's not FULLY working, but still much better than others I've seen online that say their G4 Play flat out doesn't work at all
Just updated the OP with that bit of info too

Interesting, ok. I guessed probably not... but you never know
I bought my 1607 from motorola, havan't had any issues with it on Verizon.
Thanks for the info!
jasonmerc said:
That's something I shouldve mentioned, I did not get VoLTE working on this regardless of stock/custom firmware. So perhaps it's not FULLY working, but still much better than others I've seen online that say their G4 Play flat out doesn't work at all
Just updated the OP with that bit of info too
Click to expand...
Click to collapse

RedCrane3 said:
Interesting, ok. I guessed probably not... but you never know
I bought my 1607 from motorola, havan't had any issues with it on Verizon.
Thanks for the info!
Click to expand...
Click to collapse
Funny thing is the G4 Play actually shows up as "not compatible" on Verizon's own IMEI checking tool. So if you go by what Verizon themselves say you're SOL. This strikes me as weird because Verizon themselves once sold their own G4 Play which is basically the same thing as the 1607 but minus an unlockable bootloader. According to the rep it has to do with Verizon "changing/upgrading their network" which for some apparent reason supposedly makes older phones like this mysteriously not work anymore. Regardless, the only reason I could even attempt at getting it to work was because I proved to the rep that Motorola themselves said this'll work with Verizon (which isn't simple to do since the G4 Play is no longer listed on their site) and I basically told the dude "Motorola says it works and I'm not gonna buy a new phone so do whatever you can to make it work" (and believe me, he sure as hell tried to sell me a new expensive phone during the process)
I figure this guide can also serve as a signal to onlookers that not only will this work with Verizon, it'll work even though they themselves want to assure you it wont

The real question is, has anyone ever figured out a way to get this phone to do VoLTE on Verizon/MVNOs? I'm testing it on Page Plus using AICP 16.1, and VoLTE is provisioned, but I only get 1xRTT for voice.

Related

[Q] Mobile Network Settings missing data

So I just got a new M7 swapped over and decided to let it update with Sprint to the newest revision prior to S-off, unlock, etc. Now, no matter what ROM I seem to flash, my Mobile Netowrk Settings simply show Four options -
4G Settings
Network Mode
Access Point Names (gray)
Available GSM networks (gray)
I have no option to changes to home network, roam only, automatic, etc. My wife's stock phone has all the other settings in there such as roaming, automatic connections, etc.
I'm thinking I need to RUU? Reprovision with sprint? (they screwed up the first time and my SIM wasn't linked to my account when I swapped phones so they had to do that - don't know if that has any bearing.) And the phone does work - so.....
Thoughts?
Also just to add,
HBoot 1.57
Radio 1.01.20.0515
Thanks!
Bump on this....
Would an RUU to an older version work? If so - do I have to downgrade the HBOOT and firmware to do this? If yes - if someone can point me at the right thread for the process, and recommend what version to revert to it would be most helpful. Been searching all day for this, and I've found multiple threads on how to do different things, but a specific "Do this followed by this" would be great rather than bricking the phone - which is possible considering I can only seem to run a single RUU on the device (the newest one) and if I break something, I'll have nothing.
It just seems that Roaming isn't there - everything else works just fine... I'm thinking maybe it's just the radio or a setting someplace....But I'm racking my brain.
Anyways, Thanks for letting me rant.
cubexg said:
Bump on this....
Would an RUU to an older version work? If so - do I have to downgrade the HBOOT and firmware to do this? If yes - if someone can point me at the right thread for the process, and recommend what version to revert to it would be most helpful. Been searching all day for this, and I've found multiple threads on how to do different things, but a specific "Do this followed by this" would be great rather than bricking the phone - which is possible considering I can only seem to run a single RUU on the device (the newest one) and if I break something, I'll have nothing.
It just seems that Roaming isn't there - everything else works just fine... I'm thinking maybe it's just the radio or a setting someplace....But I'm racking my brain.
Anyways, Thanks for letting me rant.
Click to expand...
Click to collapse
Do the options appear with stock?
No and that's what's making me think it might be carrier related. But not sure what I could tell sprint to do. The only change on my account was adding international roaming for an upcoming trip. Maybe it's the Sim card I transferred from the old phone?
cubexg said:
No and that's what's making me think it might be carrier related. But not sure what I could tell sprint to do. The only change on my account was adding international roaming for an upcoming trip. Maybe it's the Sim card I transferred from the old phone?
Click to expand...
Click to collapse
Probably. Try going stock and doing a PRL update and all that jazz. To go stock you need to RUU. But before that could you go into the HBOOT menu (by pressing VOL DOWN + POWER) and take a picture of the menu you see there (should be some text in multiple colors with a white background), and post it here?
I did that already - went stock with the newest RUU- that works but same result. PRL update and the like all resulted in the same.. Did it last night. Let me get you a sccreenshot of the bootloader screen..
Also running on ViperOne 5.8.0 right now with TWRP installed.. Tried BadBoyz Sense 6.0 - same result. Stock - same result.. (tried both last night)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also here's the actual screen itself in mobile network:
cubexg said:
I did that already - went stock with the newest RUU- that works but same result. PRL update and the like all resulted in the same.. Did it last night. Let me get you a sccreenshot of the bootloader screen..
Also running on ViperOne 5.8.0 right now with TWRP installed.. Tried BadBoyz Sense 6.0 - same result. Stock - same result.. (tried both last night)
Also here's the actual screen itself in mobile network:
Click to expand...
Click to collapse
You'll probably have to take it to Sprint then. RUU back to stock (if not already), and make sure that on the bootloader screen it says **LOCKED**.
StormyNight said:
You'll probably have to take it to Sprint then. RUU back to stock (if not already), and make sure that on the bootloader screen it says **LOCKED**.
Click to expand...
Click to collapse
Crap.. Ok - I can do that... Have to get it back to S-On and fix that.. Have to remember how to do it... I think I used RevOne to get S-Off... can you point me to the thread to relock?
cubexg said:
Crap.. Ok - I can do that... Have to get it back to S-On and fix that.. Have to remember how to do it... I think I used RevOne to get S-Off... can you point me to the thread to relock?
Click to expand...
Click to collapse
Never mind - figured out the relock - sure I can figure out S-On as well... Thanks for the help. Off to sprint tomorrow.. maybe they can fix.. /sigh/
Resolution
So, just wanted to update this post in case anyone else ever comes looking for this info like I did. Here's what happened:
Walked into a Sprint Corp store @ 10.00 when they opened with stock locked phone running newest version from an RUU I did last night. All my data restored from the cloud, etc.
Went right up to lead tech, explained the issue, showed it to him, and he was, admittedly, baffled. We compared the screen to an M8, an M7, etc. He took the phone in the tech area, and I hung out with him whilst he worked on it. After 50 minutes of playing with it, attempting to reactivate it, so on and so forth, he finally grabbed another refurbished that came in from the center. Powered it on, and low and behold the SAME issue. (That phone was not activated). At this point, I asked him to try swapping SIMs - maybe it's a problem with provisioning. He did this - same issue on my device. Finally, he suggested swapping me into a new device to see if that help. Of course, not going to turn down a new device, but this was after almost two hours of attempts to fix things.
We get the new device turned on and after the system provisions, believe it or not - the same issue.. The phone, factory new, doesn't have roaming options. We're both staring at each other is disbelief. We then see that the phone hadn't completed it's provisioning yet - and figured we should wait another few minutes for handsfree to finish. What I saw next I hadn't seen before.
The phone rebooted itself and did an update.. Don't exactly know what it did, but it wasn't a full blown Android Update - it was something else - which I can only guess unlocked whatever options needed to be unlocked on the phone to allow for roaming - because after the unit booted back up everything that was supposed to be available was.
In summary, it looks like there is something that the phone downloads via the network from Sprint at time of initial activation to unlock certain functions in that mobile data screen (specifically the roaming). I don't know what it is - don't know if anyone knows, but I would say that if anyone ever encounters this again - the best solution seems to be going to sprint and standing there for a few hours while insisting it's a Sprint provisioning issue - because it is.
If anyone wants any other details, I'll post what I know - but that's about it.
I've got the same problem
cubexg said:
So, just wanted to update this post in case anyone else ever comes looking for this info like I did. Here's what happened:
Walked into a Sprint Corp store @ 10.00 when they opened with stock locked phone running newest version from an RUU I did last night. All my data restored from the cloud, etc.
Went right up to lead tech, explained the issue, showed it to him, and he was, admittedly, baffled. We compared the screen to an M8, an M7, etc. He took the phone in the tech area, and I hung out with him whilst he worked on it. After 50 minutes of playing with it, attempting to reactivate it, so on and so forth, he finally grabbed another refurbished that came in from the center. Powered it on, and low and behold the SAME issue. (That phone was not activated). At this point, I asked him to try swapping SIMs - maybe it's a problem with provisioning. He did this - same issue on my device. Finally, he suggested swapping me into a new device to see if that help. Of course, not going to turn down a new device, but this was after almost two hours of attempts to fix things.
We get the new device turned on and after the system provisions, believe it or not - the same issue.. The phone, factory new, doesn't have roaming options. We're both staring at each other is disbelief. We then see that the phone hadn't completed it's provisioning yet - and figured we should wait another few minutes for handsfree to finish. What I saw next I hadn't seen before.
The phone rebooted itself and did an update.. Don't exactly know what it did, but it wasn't a full blown Android Update - it was something else - which I can only guess unlocked whatever options needed to be unlocked on the phone to allow for roaming - because after the unit booted back up everything that was supposed to be available was.
In summary, it looks like there is something that the phone downloads via the network from Sprint at time of initial activation to unlock certain functions in that mobile data screen (specifically the roaming). I don't know what it is - don't know if anyone knows, but I would say that if anyone ever encounters this again - the best solution seems to be going to sprint and standing there for a few hours while insisting it's a Sprint provisioning issue - because it is.
If anyone wants any other details, I'll post what I know - but that's about it.
Click to expand...
Click to collapse
I've taken my husband's M7 to the Sprint Store, and the technician tried, but couldn't do anything at all. I thought it lost the roaming options when I downloaded the latest operating system, back around June 1. I called HTC, and the technician checked their Sprint M7, and it had the same issue, too. I'm waiting for HTC to call me and agree to replace the phone, but it sounds like the new one will most likely be the same way.
I guess I'll call Sprint and try to have them reprovision it.

Phone must reboot

Hello everyone,
I've noticed starting last week my G4 will have a old android style pop-up stating "Device must restart to allow service to continue. Device will restart in ## seconds." It has reboot and later as the options, and will continue to pop-up if i hit later and will even do this when the screen is locked randomly. It is starting to become more often.
I have:
Rebooted phone
checked for apps at cause
Wiped phone with factory reset
updated PRL and other update options (no updates available)
Seems some people here had the same issue on their S5's but with no answer to what was causing it fully
http://forum.xda-developers.com/gal...service-to-t3049657/post60225538#post60225538
Thanks!
Government monitoring you?
I had one pop-up yesterday, we'll see what happens today. If it does I'll post back here. Thanks for the reply back!
Just had one pop-up, requiring me to restart or click later. I'm starting to get frustrated at this. My wife and my co-worker have the same phones, and they have not received this message at all before.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
in-case the link above does not work here direct: http://imgur.com/xGjDQdU
Does it happen on both WIFI and Cell Network?
Are you using WIFI Calling?
mswlogo said:
Does it happen on both WIFI and Cell Network?
Are you using WIFI Calling?
Click to expand...
Click to collapse
It can happen on both WiFi and Cell network. I do use WiFi calling as my work area is prone to dead signal areas for any carrier. It is completely random as I can be at home on WiFi calling or at the mall on Cellular and it reboot itself due to that message.
Jessooca said:
Did you get your issue fixed? PM me if you need help still.
Click to expand...
Click to collapse
Hi Jessooca, I sent you a PM
I am having this issue now o.k. two phones.
Our problem started after rooting. I followed @rirozizo's video guide on the cubes post. I installed "root checker" that was mentioned on that video as well.
Now every few hours I have the pop up. One time, I was able to press the square key to bring up the multi window/tab view and the name of the tan with the restart message was called Network System Provider.
The window appears, as described in the OP, and states Device must restart. Device will restart in XX seconds.
I did just try clearing the cache for Network System Provider. Hopefully that helps....
Any and all help anyone can offer will be appreciated.
Thank you
Im a troll said:
Hi Jessooca, I sent you a PM
I am having this issue now o.k. two phones.
Our problem started after rooting. I followed @rirozizo's video guide on the cubes post. I installed "root checker" that was mentioned on that video as well.
Now every few hours I have the pop up. One time, I was able to press the square key to bring up the multi window/tab view and the name of the tan with the restart message was called Network System Provider.
Any and all help anyone can offer will be appreciated.
Thank you
Click to expand...
Click to collapse
I bet this is because of a bad SIM card or the pins are disconnecting then reconnecting to the SIM card resulting this reboot popup.
Check the tray, clean it up, and maybe even try a different SIM Card and see if that works.
BTW yes i got mentioned here so i want to help
Sent from my LG-H815 using Tapatalk
rirozizo said:
I bet this is because of a bad SIM card or the pins are disconnecting then reconnecting to the SIM card resulting this reboot popup.
Check the tray, clean it up, and maybe even try a different SIM Card and see if that works.
BTW yes i got mentioned here so i want to help
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Thank you so much.
I will check the SIM, although, I feel pretty confident that it's something else. My reasoning is that it's happening to both our phones and started within hours of being rooted ( I rooted them within minutes of eachother). The only new app installed after rooting on either phone was root checker. The months prior had no issue at all, and Now both are having the same issue at once...unless both SIM card trays got dirty at the same time which would be very coincidental.
I well try your suggestion though. Thank you.
Im a troll said:
Thank you so much.
I will check the SIM, although, I feel pretty confident that it's something else. My reasoning is that it's happening to both our phones and started within hours of being rooted ( I rooted them within minutes of eachother). The only new app installed after rooting on either phone was root checker. The months prior had no issue at all, and Now both are having the same issue at once...unless both SIM card trays got dirty at the same time which would be very coincidental.
I well try your suggestion though. Thank you.
Click to expand...
Click to collapse
Now i don't know anything about Sprint and "american services" but did you flash the right system image specifically for your device? maybe some Sprint service is lost and it's just bugging out? just a blind guess here
rirozizo said:
I bet this is because of a bad SIM card or the pins are disconnecting then reconnecting to the SIM card resulting this reboot popup.
Check the tray, clean it up, and maybe even try a different SIM Card and see if that works.
BTW yes i got mentioned here so i want to help
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
rirozizo said:
Now i don't know anything about Sprint and "american services" but did you flash the right system image specifically for your device? maybe some Sprint service is lost and it's just bugging out? just a blind guess here
Click to expand...
Click to collapse
I appreciate your guesses! I am stumped myself so I will gladly accept any and all help.
I double checked to be sure, and yes I did use the correct files and commands.
The problem presents itself every few hours, so I will see if it continues now that I have cleared the cache I mentioned before.
Thank you again and thank you much for the wonderful videos
I see so many posts in this forum with odd issues and later find they are running unlocked in another country.
Are you in USA on a Sprint Network and getting this error?
I doubt it's the SIM card too.
If on Sprint network you might try ##72768# Hands Free Activate.
Be sure you are near a solid Sprint Signal and WIFI for backup.
Also I find adblocking software gives Sprint phones fits now.
OP Chiming in here, my phone has never been rooted, and is experiencing this issue still. I have flashed the TOT file and also done a recovery factory restore with no luck.
I can clean the sim card real quick and see how it goes today, I am however heading to a Sprint repair tech this weekend to have a new sim card placed in to see if it works.
Get your service code and do an RTN reset. It will wipe your internal storage so just click and drag from your G4 to a place on your desktop. If an RTN doesn't fix it, call Sprint.
Jessooca said:
I replied to your PM hopefully if you go through all those steps, it will fix your issues.... For whatever reason the issues seem to arise if you have factory reset your device, after you have rooted it; theres no proof that's the cause but in most cases, not all, this seems to be a perpetrator. ROOT that is, this issue has happened on various other devices, from 4.4.2 all the way up to a friends Nexus 6 running Android 6.0....
If it fixes your issues; I will share the steps here for anyone else.
Click to expand...
Click to collapse
Hi Jessooca,
I just sent you a PM as well.
Just so everyone is clear, Jessooca is amazing!
Having said that, I am both happy and sad to report that the problem may be solved ( I am not sure and will wait and see). I noticed that twice in the multi-window view brought up by pressing square (forgive me for not knowing the correct term) that the window with the restart message was titled Network System Provider.. so I googled...and then I went through my apps looking for the matching icons. I then found that the error was part of an app by "Its on." Specifically two apps matched the icon; NetworkSystemProvider with an install date of 8/1/2008 (weird?) and NetworkSystemProvider UID with a install date of 5/7/15 ( the day I took the Sprint ZV5 OTA and then rooted).
What I then did was clear the cache of both apps and then of the phone via storage. I have not noticed nay pop-ups since then so I hope that my problem is fixed.
I am also unsure what those two apps are, if they were always there, and if I can safely delete them.
Best of luck OP. I will post again right away if my problem is not resolved, and clearing the cache did nothing more than fill me with false hope!
Im a troll said:
Hi Jessooca,
I just sent you a PM as well.
Just so everyone is clear, Jessooca is amazing!
Having said that, I am both happy and sad to report that the problem may be solved ( I am not sure and will wait and see). I noticed that twice in the multi-window view brought up by pressing square (forgive me for not knowing the correct term) that the window with the restart message was titled Network System Provider.. so I googled...and then I went through my apps looking for the matching icons. I then found that the error was part of an app by "Its on." Specifically two apps matched the icon; NetworkSystemProvider with an install date of 8/1/2008 (weird?) and NetworkSystemProvider UID with a install date of 5/7/15 ( the day I took the Sprint ZV5 OTA and then rooted).
What I then did was clear the cache of both apps and then of the phone via storage. I have not noticed nay pop-ups since then so I hope that my problem is fixed.
I am also unsure what those two apps are, if they were always there, and if I can safely delete them.
Best of luck OP. I will post again right away if my problem is not resolved, and clearing the cache did nothing more than fill me with false hope!
Click to expand...
Click to collapse
i dont have these two apps (i'm on international version, so no carrier stuff here)
I updated to ZV6 this morning and got this message for the first time this afternoon.
"Device must restart to allow service to continue"
After doing some reading, the problem seems to be related to ItsOn.
http://forum.xda-developers.com/spr...nt/zip-remove-itson-sprint-of7-based-t3154181
ItsOn is difficult to remove as it has service running even when the apk files are frozen or removed.

Can't receive calls and SMS using LTE (LineageOS)

I have OnePlus 3T A3010.
The problem is that device randomly stops receiving calls or SMS. It happens on latest Resurrection Remix that is LineageOS based.
For example:
1. I reboot it.
2. It shows 4G icon after reboot, data is working, I can make calls.
3. I open ##4636## menu, it says that it's using LTE for both voice and data.
4. I call myself (from another device of course), my phone switches from LTE to UMTS and receives call.
5. I make some calls again, everything is working.
6. I leave my phone for a while so it goes to sleep.
7. After some time I try to call myself again and my phone doesn't even switch to 3G, no reaction to call at all and caller gets a message that destination is unavailable. I can fix it by turning WiFi on/off (so LTE data goes off/on too, I dunno why it works to be honest) or by switch airplane mode.
Any ideas about that? I clean flashed OxygenOS 4.1.0 and managed to get this behavior once only. Also it seems that on RR it starts to act like that short time after I connect to WiFi.
HTML:
persist.dbg.ims_volte_enable=0
persist.dbg.volte_avail_ovr=0
in build.prop solves the problem.
LineageOS has these set to 1, OOS has these set to 0. I guess 0 is right because now it switches to 3G correctly.
Problem solved.
AT&T Community Forums​
Messages
Plans & Features
8GB high-speed data $25/mo.
Shop now
techquestions​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
New Member
•
3 Messages
Mar 7, 2022
ATT cell phone service not working with Lineage OS 17 or 18​Hello,
The cell phone I've been using here
in the USA is a Motorola G7 Plus,
with the Lineage 17.1 OS.
Lineage OS is a fork of Android
The reason to use Lineage is that it is DeGoogled
More info on Lineage here.
5 De-Googled Android-based Operating Systems to Free Your Smartphone from Google and other Big Tech
5 De-Googled Android-based Operating Systems
Concerned about your privacy or want to give another life to your smartphone? You could consider these Android distributions and custom ROMs.
itsfoss.com
This Lineage 17.1 phone has worked fine with ATT since early 2021.
But March 2, 2022, I suddenly couldn't make a phone call.
Immediately, the call would end, and a message displayed:
"Call ended".
I'm assuming that this has to do with ATT's 5G upgrade.
ATT docs says that the Moto G7 Plus will work after the 5G upgrade
https://www.att.com/idpassets/images/support/wireless/Devices-Working-on-ATT-Network.pdf
So I did some tests with some other phones I have.
Here are the results after swapping the
same SIM card with the various phones:
...
Motorola G7 Plus, Lineage 17.1
- call ended
Motorola G7 Plus, Lineage 18.1
- call ended
Samsung Galaxy A32, out of the box Android
- calls work fine
Motorola G7, out of the box Android
- calls work fine
...
So, the SIM card is working on factory Android
But the same ATT SIM card is NOT working with Lineage OS.
...
q1:
Is there a setting that I need to tweak to
make Lineage work with ATT 5G?
q2:
What is ATT's roadmap to get Lineage OS
cell phones to work on their network?
If Lineage won't work with ATT, I will be
looking for a carrier that does work with Lineage.
Thanks a lot
Questions
•
Updated
an hour ago
180
7
1
7
Like
Comment
Follow
Share
Responses
https://forums.att.com/users/5defae6ff6e8ee15674daa0d
formerlyknownas​
+76 more
ACE - Sage
•
94.8K Messages
a month ago
My guess is you should be on your way to another carrier
I don’t work for AT&T or any carrier. Never have, never will. My replies are based on experience and reading content available on the website. If you posted personal information, please edit and remove.
Award for Community Excellence 2021 Achiever*
*I am not an AT&T employee, and the views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.
Like
0
0
https://forums.att.com/users/5defa677fd08351cbe19f0c7
GLIMMERMAN76​
+65 more
ACE - Expert
•
23.1K Messages
a month ago
You should look for another carrier as in T-Mobile. Verizon has problems supporting phones running non conforming OS. I would say there is problem in the modem stack on that phone.
Award for Community Excellence 2021 Achiever*
*I am not an AT&T employee, and the views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.
Like
0
1
https://forums.att.com/users/622638a846992233368d5763
techquestions​
New Member
•
3 Messages
a month ago
First of all, I want to thank all the
ATT staff for their help in solving
this tough tech problem
Note: this is sarcarm
ATT staff, so far, have had a 100% failure ratio
in even responding to my post
Perhaps no one from ATT even read it
"Take off, figure it out yourselves"
Like
0
1
https://forums.att.com/users/622638a846992233368d5763
techquestions​
New Member
•
3 Messages
a month ago
Hello all,
More on the Lineage / ATT drama
So, I tried calling ATT's 611 today.
Did not get a person, just a IVR server asking stupid questions.
I kept asking for "agent".
Because, Lineage OS will NOT be in their
pre-programmed set of recorded responses.
IVR kept asking the same questions.
And I kept saying "agent".
So it said, "good bye"
So rude
(What I call the management by middle finger
"Don't bug us, take off, figure it out yourself!" )
...
Went to the ATT store to give an update, and
ask for more info.
The customer disservice agent just kept
saying "I don't know" when I told him my
hardware was certified for ATT.
Note: I wasn't asking him. I was telling him.
When I showed him the ATT print out,
he refused to look at it, and refused
to recognize the fact.
He kept interrupting, giving me contradiction functions.
Later when he saw the Samsung A32 on my printout of results,
he interrupted again, and said that only A32 5G
would work on ATT.
Completely ignoring the fact that I'd just told him
my A32 is working fine with ATT.
Lots of attitude problems on his part.
Toward the end, he asked, "what is the problem?".
I said, "well I've told you three times now"
But even though I'd told him three times,
he still didn't know what the issue was!
Do you think there's a correlation between the fact
that he kept interrupting, wasn't listening,
refused to recognize facts, or even look, and
he still didn't know what the issue was?
What a useless, black hole, waste of my time!
Why does ATT hire narcissistic people,
who can't communicate, and then put them into
customer interfacing positions?
Do they also put the same people in financial department?
One good info I got was that they did say that
as an ATT store, they have managed to speak to 611.
When I asked how long it took to get through, the usual
knee (Edited per community guidelines) reaction was, "it depends". (Yes, we know.)
"In your experience, how long does it normally take to get through?"
Eventually two of them concluded, after 10 to 15 minutes of waiting!
As least they got through to 611.
Are the 611 phone systems programmed to
only answer the ATT store call IDs?
Also, not even the stores can contact engineering.
Seems engineering is in their glass tower.
Saying, "don't bug us!"
And that engineering doesn't care to hear that there are
real problems on their network, and
that dozens of hours of just one customer's time (me)
is being wasted, over days and weeks.
...
Also went to the T Mobile store.
The rep inserted a T Mobile SIM in my Lineage 17.1, and the
phone lit up with text messages, and we could make a call.
(Do you see the multiple contrasts with the ATT rep?)
So, at least for the moment,
TMobile seems to work with
Moto G7 Plus, Lineage 17.1
Guess which carrier I'm inclined to go with?
Guess which carrier is better,
from a customer service standpoint?
(edited)
Like
0
0
coshman​
New Member
•
1 Message
a month ago
Same with my Moto G7. ATT stopped working for call functions. Tried a T-Mobile SIM and it works perfectly. Nothing wrong with my phone, just an attempt by ATT to force you into buying a new one they control.
Like
0
0
Confused2much​
New Member
•
1 Message
5 days ago
Hello,
I, too, have a Moto G7 Plus that stopped making/receiving calls on March 2, 2022. I have even tried a T-Mobile SIM - same result, I can text and access mobile data, but can't make/receive calls. Tried for hours to get this resolved with their reps with no luck. Anybody have any ideas? I love this phone and paid good money to have it deGoogled (using LineageOS 18.1).
Like
0
0
Potatoalien​
New Member
•
1 Message
an hour ago
I don't know why (maybe a LOS issue), but when you switch to another carrier, in order for a smartphone to work with text and calls you have (at least works for me) to reinstall the stock Android ROM, ensure that calls and texts work, then install Lineage OS over top of the stock ROM. Then calls and text work. I used TWRP (.IMG, then WIPE all except external SD card, then install twrp.zip, then RESTORE backup (SYSTEM IMAGE), then reboot phone and test calls & text, then go back into twrp and INSTALL Lineage OS (no WIPE is done), then test calls & text (should work now). According to my method, you'll need a twrp backup of your SYSTEM IMAGE (stock ROM of Android). If you don't have, maybe you can find on internet, or buy a backup identical phone from eBay and unlock the bootloader and install twrp and do BACKUP of SYSTEM IMAGE onto external SD card. You will need to rename the serial number of the backup to your phone's serial number. You can find out your phone's serial number by doing a BACKUP of any option in twrp.
Also people sometimes get an error 225 code when doing a BACKUP or a RESTORE in twrp. If so, try only doing a BACKUP/RESTORE if SYSTEM IMAGE only, not a separate BACKUP/RESTORE of Data, System, Boot.
I think Lineage OS is at fault here with why you have trouble with calls, text. I think there is code removed from the Android stock ROM when Lineage is created; this code is necessary to be left in, but isn't. I write that Lineage OS must be at fault because Android OS stock ROM works with calls, text. When Lineage is INSTALLED over top of Android stock ROM, there must be settings on phone (somewhere......) that were placed there by Android OS, and these remain there if you INSTALL Lineage over top of Android OS.
I discovered thus problem a number if years ago with my Moto E 2nd Gen phone, and this problem still exists with my Moto G7 phone. So I have to reinstall stock ROM, then Lineage over top of it. To add to the fun you might have difficulty with installing the stock ROM onto the phone. If so, can try this: using twrp, install Lineage and do a factory reset. Then go back and try installing the stock ROM using steps I wrote. Also, when you install it and it starts booting up, it might fully boot, so you need to restart phone again to get stock ROM to fully boot up.
And if you hardbrick (no response from it) your phone, you should use a blankflash (that matches your phone model or is possibly similar to it) to unbrick it. Run in adb fastboot, then plug your phone in and it should unbrick.
Another thing: if your USB cable is faulty, you need to get another one that works. A good cable is edl cable, that's what I use.
There is a lot I don't know, there are things I know - hopefully this helps.
Like
0
0
Paragraph
Comment on this post here...
CancelPost
Need help?
Ask a question
Related Conversations​
No conversations found!
Top FAQs​
The latest Samsung devices!
The freedom of AT&T PREPAID
All About the 3G shutdown
Protect Yourself From Scams
Check Your Order or Trade-in Status
Need Help With Your Bill?
Answers to our Top FAQs
Did this help you?​NoYes
Tags​wireless
at&t
Fix, replace or check device delivery
Learn more
New to the AT&T Community?
Visit the Community How-To.
Find a store
Make a store appointment
Coverage maps
Learn about 5G
Contact us
Help & Support
About AT&T
TechBuzz blog
Community forums
Site map
Terms of use
Accessibility
Broadband details
Legal policy center
Advertising choices
Privacy center
Do Not Sell My Personal Information
©2022 AT&T Intellectual Property. All rights reserved.

so-called GSM unlocked Sprint LG V40 from ebay loops in network activation forever

I got a so-called "GSM-unlocked Sprint LG V40" from ebay, and I received it a week ago. when I powered up the phone the first time without a SIM card, it went directly with an "Activate your device Please wait while we activate your device for network service." message on the screen, and I had to wait for about 10 minutes for it to finish before I could do anything with the phone. I thought that was OK, since it did not have a SIM crad, and probably it's just some initialization thing. I then put a SIM card in the phone and did some tests, it appeared to be fine. A few days later, I had to restart the phone, and with a SIM card in the phone, the "Activate your device Please wait..." thing after the phone was powered up would take almost forever to finish. And when that "Network Activation" thing is on, the phone is pretty much locked and I could not do anything with it. What's worse is the "Network Activation" process is not only run immediately after powering up, it would come up every 1-2 hour, and each time it would take a few hours to finally give up with a message saying "Activation incomplete." I've seen it just went to the "Activation" loop indefinitely in the last few days. I've tried with WIFI ON or OFF, 4G LTE data On or Off, but nothing helps and the "Activation" loop just continues forever. As an example, I restarted the phone at 11:10am this morning, the "Activation" thing took 2.5 hours to complete (see attached picture). It started again in a little over an hour before I went out for a walk, and when I came back an hour later, the "Activation" thing was still on.
I contacted the seller, and he claimed that the "unlocked" Sprint V40 "unfortunately" has this problem--good for him to acknowledge that after I found it the hard way...he did not disclose this nasty problem at all on ebay. I can return the phone, but then I'll end up losing more than $50 for shipping+import tax.
Does anyone know if there's anyway to stop that "Network Activation" from running? Will paying someone to have the bootloader unlocked and change the ROM help?
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have also a sprint unlocked V40 and i have the same message each time I reboot my phone but it disappears just after 1 or 2 minutes
maybe there is a way to unistall this checking thing by ADB I would be interested too if someone can help with is
Package Disabler Pro
Install Package Disabler Pro and disable all Sprint stuff. I'm not sure, but I think it's the Carrier Setup Wizard (com.sprint.psdg.sw) that you experience right now...
nyttliv7 said:
Install Package Disabler Pro and disable all Sprint stuff. I'm not sure, but I think it's the Carrier Setup Wizard (com.sprint.psdg.sw) that you experience right now...
Click to expand...
Click to collapse
That would be my guess too
bought mine sprint gsm unlocked as well from ebay. That screen only comes up after every reboot and only took 2 minutes at most to go away.I found there's no way to disable it.I used package disable to shut down anything sprint related and even the carrier wizard/set packages.Nothing worked.So i just converted it to US open FW and now it's gone as well as sprint's other garbage plus you get pie
nyttliv7 said:
Install Package Disabler Pro and disable all Sprint stuff. I'm not sure, but I think it's the Carrier Setup Wizard (com.sprint.psdg.sw) that you experience right now...
Click to expand...
Click to collapse
Thanks for the tip. Unfortunately, it doesn't work, but it does help in shortening the annoying activation time in a great deal: Before trying your suggestion, I did a factory reset first, and that dramatically cut down the bootup activation time from a few hours to a little over 5min. I then followed your suggestion and installed the latest version v1.6 Package Disabler Pro for LG. At first, I just disabled Carrier Setup Wizard, but that did not help. So, I disabled all sprint crap except the one that could not be disabled via Package Disabler Pro but still no luck. However, with most Sprint crap disabled, I finally managed to have the annoying bootup activation time shortened to about 1min45sec. For those of you saying the bootup activation only took 1 to 2 minutes, I guess whoever sold you the phone might have already disabled those Sprint crap before you bought the phone.
So, it looks like this annoying "Activation" thing may not be from the Sprint crap, or perhaps it's caused by that one sprint package which could not be disabled (see pic). No matter what, I think whatever program behind it is pretty buggy.
jass65 said:
bought mine sprint gsm unlocked as well from ebay. That screen only comes up after every reboot and only took 2 minutes at most to go away.I found there's no way to disable it.I used package disable to shut down anything sprint related and even the carrier wizard/set packages.Nothing worked.So i just converted it to US open FW and now it's gone as well as sprint's other garbage plus you get pie
Click to expand...
Click to collapse
As I originally thought, that annoying activation screen could only be removed by replacing the sprint ROM. Did you pay someone to replace the FW, or did you do it yourself? I appreciate if you can point me to a DIY instruction. I prefer doing this myself. Thanks.
shng said:
So, it looks like this annoying "Activation" thing may not be from the Sprint crap, or perhaps it's caused by that one sprint package which could not be disabled (see pic).
Click to expand...
Click to collapse
Sure enough that one package/service Sprint Android Requirements which could not be disabled by Package Disabler Pro is the one responsible for the after-boot activation screen. I've found a few posts about bloatware on some very old LG devices such as G2 all point to Sprint Android Requirements as responsible for the Activation thing:
Sprint Android Requirements - Removing prevents Activation app from working, Can be removed if you removed SSA activation app
Click to expand...
Click to collapse
But Sprint Android Requirements cannot be disabled via Package Disabler Pro, I guess one other way is to root and then remove Sprint Android Requirements altogether.
ADB
What about uninstall Sprint Android Requirements with adb?
nyttliv7 said:
What about uninstall Sprint Android Requirements with adb?
Click to expand...
Click to collapse
I don't know. Package Disabler Pro runs on the device, and Sprint Android Requirements is probably installed on the system partition, so without ROOT it could not be disabled. Using adb should do it.
I have ADB environment on my old NB for my old mobile phones, but the NB's mother board is dead. I'll need to set up the environment on the current NB I'm using. I'll give adb a try and report back.
adb doesn't recognize V40
I'm not able to get adb to work with V40. At first I just grabbed an adb installation someone posted here on xda, but that did not work. I figured it's probably too old, so I downloaded from Android developer site the latest Android SDK Platform Tools v.29 and installed adb&fastboot etc. from there. That still didn't work--adb&fastboot just couldn't recognize V40. I've tried with two non-LG older phones and they all connected to adb swiftly. So I did a factory reset again to V40, but there's still no luck with adb after that. I've tried both File transfer and Photo transfer on V40 USB connection, but neither worked. I'm stuck for now.
【update】Just found out that in order to have LG devices make USB connections to PC painlessly, it's necessary to install LG USB driver on PC for the particular LG device.
adb disabled all sprint crap but still no luck
I finally managed to make V40 connect with adb and use adb shell command to disable all sprint packages/services, but that annoying boot activation still comes up on every reboot. It's driving me nuts.
While you're on it
shng said:
I finally managed to make V40 connect with adb and use adb shell command to disable all sprint packages/services, but that annoying boot activation still comes up on every reboot. It's driving me nuts.
Click to expand...
Click to collapse
Uninstall "com.sprint.psdg.sw" too...
Worth trying
nyttliv7 said:
Uninstall "com.sprint.psdg.sw" too...
Worth trying
Click to expand...
Click to collapse
Yeah that's something I was going to try next anyway. So I tried, and guess what--not only there was no luck still, but also now the bootup activation reverts back to seemingly forever. Waited for almost half an hour until it finished and then factory reset. I guess I'll just try disabling some of the non-sprint services.
Octoplus
shng said:
Yeah that's something I was going to try next anyway. So I tried, and guess what--not only there was no luck still, but also now the bootup activation reverts back to seemingly forever. Waited for almost half an hour until it finished and then factory reset. I guess I'll just try disabling some of the non-sprint services.
Click to expand...
Click to collapse
If nothing else works, you can always unlock bootloader, root and flash pie... It will cost you a few $, but definitely worth it
Octoplus or Vlad? I'm confused
nyttliv7 said:
If nothing else works, you can always unlock bootloader, root and flash pie... It will cost you a few $, but definitely worth it
Click to expand...
Click to collapse
Did you have octoplus or someone else (Vlad?) unlock your v40's bootloader & flash PIE? I saw on another thread you talked to Android4Lif back and forth on waiting for the service and paying for it etc. You recommend octoplus, but Android4Lif uses Vlad, and he's now complaining Vlad bricked his phone. So I'm confused--which one did you go for the service?
I'd really prefer doing this sort of things myself unless there is no other way but paying someone else to do it. Back in the old days, HTC devices have tons of free information&guides available for unlocking bootloader/falshing ROMs. And I've always done unlocking/ROOT/falshing myself on my old phones. I guess the landscape has changed in the last couple of years since I bought my last mobile phone before the recent purchase of a V40--those who have knowledge on unlocking are unwilling to share now.
shng said:
Did you have octoplus or someone else (Vlad?) unlock your v40's bootloader & flash PIE? I saw on another thread you talked to Android4Lif back and forth on waiting for the service and paying for it etc. You recommend octoplus, but Android4Lif uses Vlad, and he's now complaining Vlad bricked his phone. So I'm confused--which one did you go for the service?
I'd really prefer doing this sort of things myself unless there is no other way but paying someone else to do it. Back in the old days, HTC devices have tons of free information&guides available for unlocking bootloader/falshing ROMs. And I've always done unlocking/ROOT/falshing myself on my old phones. I guess the landscape has changed in the last couple of years since I bought my last mobile phone before the recent purchase of a V40--those who have knowledge on unlocking are unwilling to share now.
Click to expand...
Click to collapse
Hey guys, I can flash the firmware from V405QA instead of the sprint and it will be clean, without sprint applications, and this is 9 android.
Flashing 9 does not have to unload the bootloader, but I can do it.
The firmware will take 20-25 minutes.
And I will not make your device a brick, I have already flashed a lot of these phones and I know all the nuances
motogvasyag said:
Hey guys, I can flash the firmware from V405QA instead of the sprint and it will be clean, without sprint applications, and this is 9 android.
Flashing 9 does not have to unload the bootloader, but I can do it.
The firmware will take 20-25 minutes.
And I will not make your device a brick, I have already flashed a lot of these phones and I know all the nuances
Click to expand...
Click to collapse
Hello motogvasyag, How do you flash 9, and how much you charge?
motogvasyag said:
Hey guys, I can flash the firmware from V405QA instead of the sprint and it will be clean, without sprint applications, and this is 9 android.
Flashing 9 does not have to unload the bootloader, but I can do it.
The firmware will take 20-25 minutes.
And I will not make your device a brick, I have already flashed a lot of these phones and I know all the nuances
Click to expand...
Click to collapse
hi bro V405QA is a version unlock sim because have a sprint version locked
Try this:
When the "activacion mode" appears press emergency call - Turn off Wifi - Go Settings - Network and Internet - Mobile networks - Network mode - and here change automatic to LTE/CDMA.
Sometimes works.

LG G8 AT&T got Android 12 update, but be careful!

I just updated my G8 AT&T unlocked phone from A10 to A12 today. Initially, I was excited when AT&T pushed the updates. Later on, I found that I cannot make/receive calls (text and data are still working). Then I dialed *#*#4636#*#* and found that the volte is not provisioned. But in A10, it was provisioned. So frustrated now...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does anyone know how to solve this issue? Thanks!
UPDATES:
I finally solved the problem by cross flashing my LG G8 to US OPEN firmware. Now with H2O, or RP GSMT/GSMA, everything works perfect so far. I believe ATT intentionally disables volte, making the phone virtually 'locked' to ATT only sim card (I have tried FreedomPop, redpocket GSMA and GSMT, Boost, H2O sim cards, none of them worked before flashing).
I currently have the same issue and you are the only person I can find asking about it. So have you had any luck?
FadeOut2006 said:
I currently have the same issue and you are the only person I can find asking about it. So have you had any luck?
Click to expand...
Click to collapse
Changing the sim card could be a solution. I have tried sim cards from several mvnos, seems that only the ATT prepaid card works. Others reported the Boost sim card also works.
Hmm. So, I should definitely hold off on upgrading to Android 12? Because everything is working perfectly with Android 11 right now. Have you tried US Mobile?
Gurren Lagann said:
Hmm. So, I should definitely hold off on upgrading to Android 12? Because everything is working perfectly with Android 11 right now. Have you tried US Mobile?
Click to expand...
Click to collapse
But if your sim card works with Android 11, it may work with Android 12. Anyway, I just found It worked perfectly with my H2O sim card on Android 10, not working on android 12. I tried H2O, red pocket, tracfone, att, mint.
rrhhuutt said:
But if your sim card works with Android 11, it may work with Android 12. Anyway, I just found It worked perfectly with my H2O sim card on Android 10, not working on android 12. I tried H2O, red pocket, tracfone, att, mint.
Click to expand...
Click to collapse
Have you tried US Mobile? That's what I have but I am afraid to upgrade to Android 12 when it comes out. I am hearing things like people are unable to make or receive calls. Or the Wi-Fi Calling feature is greyed out. I don't want to risk it.
Shawn R said:
Have you tried US Mobile? That's what I have but I am afraid to upgrade to Android 12 when it comes out. I am hearing things like people are unable to make or receive calls. Or the Wi-Fi Calling feature is greyed out. I don't want to risk it.
Click to expand...
Click to collapse
OK---I just did the update. No WiFi calling & no calling period..... I had an ATT sim card laying around--put it in & ---you guessed it....WiFi calling came up--couldn't try a call (no network available--old sim)--but I tried my sim (Consumer Cellular--ATT reseller) & NOTHING. I'm looking for a 10 image so I can roll the phone back.....
The Consumer Cellular sim worked with 10...no WiFi calling with 11 & nothing with 12.
debianmain1 said:
OK---I just did the update. No WiFi calling & no calling period..... I had an ATT sim card laying around--put it in & ---you guessed it....WiFi calling came up--couldn't try a call (no network available--old sim)--but I tried my sim (Consumer Cellular--ATT reseller) & NOTHING. I'm looking for a 10 image so I can roll the phone back.....
The Consumer Cellular sim worked with 10...no WiFi calling with 11 & nothing with 12.
Click to expand...
Click to collapse
I believe this site has what you're looking for: https://lg-firmwares.com/
Now I am definitely not going to upgrade.
Shawn R said:
I believe this site has what you're looking for: https://lg-firmwares.com/
Now I am definitely not going to upgrade.
Click to expand...
Click to collapse
Yes---I have that one bookmarked......no ATT ROMs, but you can get the US_OPEN ROMs...If I don't resolve this in a week or so, I'm going to cross-flash to 20H using the no root guide...It works pretty well. I'm on my backup G7 now, so I have time to experiment.
You wouldn't want to image your phone & post it---would you?
rrhhuutt said:
I just updated my G8 AT&T unlocked phone from A10 to A12 today. Initially, I was excited when AT&T pushed the updates. Later on, I found that I cannot make/receive calls (text and data are still working). Then I dialed *#*#4636#*#* and found that the volte is not provisioned. But in A10, it was provisioned. So frustrated now...
View attachment 5713227
View attachment 5713225
Does anyone know how to solve this issue? Thanks!
UPDATES:
I finally solved the problem by cross flashing my LG G8 to US OPEN firmware. Now with H2O, or RP GSMT/GSMA, everything works perfect so far. I believe ATT intentionally disables volte, making the phone virtually 'locked' to ATT only sim card (I have tried FreedomPop, redpocket GSMA and GSMT, Boost, H2O sim cards, none of them worked before flashing).
Click to expand...
Click to collapse
Are you saying that WiFi Calling works for US_OPEN? As I understand it--that is a Verizon ROM?
debianmain1 said:
Yes---I have that one bookmarked......no ATT ROMs, but you can get the US_OPEN ROMs...If I don't resolve this in a week or so, I'm going to cross-flash to 20H using the no root guide...It works pretty well. I'm on my backup G7 now, so I have time to experiment.
You wouldn't want to image your phone & post it---would you?
Click to expand...
Click to collapse
I have the LG G8 ThinQ G820TM (T-Mobile Unlocked) running Android 11. Is this compatible with yours?
debianmain1 said:
Are you saying that WiFi Calling works for US_OPEN? As I understand it--that is a Verizon ROM?
Click to expand...
Click to collapse
Wifi-calling depends also on sim cards, my RP GSMT and ATT sim cards have wifi-calling enabled, but not H2O's.
The rom is: G820QM30c_00_NAO_US_OP_0103.kdz
Shawn R said:
I have the LG G8 ThinQ G820TM (T-Mobile Unlocked) running Android 11. Is this compatible with yours?
Click to expand...
Click to collapse
Well---I was hoping for an ATT Image....The T-Mo0bile will work, but I would have to cross-flash it anyway....THANK YOU. I'll most likely use the cross-flash guide posted here---it works very well.
rrhhuutt said:
Wifi-calling depends also on sim cards, my RP GSMT and ATT sim cards have wifi-calling enabled, but not H2O's.
The rom is: G820QM30c_00_NAO_US_OP_0103.kdz
Click to expand...
Click to collapse
I know that my sim was using WiFi Calling with 10---so I'm going to either do a downgrade with an ATT image if I can find one or cross flash to either T-Mo or Verizon ROM.
debianmain1 said:
I know that my sim was using WiFi Calling with 10---so I'm going to either do a downgrade with an ATT image if I can find one or cross flash to either T-Mo or Verizon ROM.
Click to expand...
Click to collapse
So, how does someone extract the image from their phone? I had a LG G3, G4, and G6 a few years ago. And I put TWRP on all three. I know that with TWRP I can backup the image but I'm kinda scared to put it on my G8 because it could cause all kinds of problems. Wouldn't I have to unlock the bootloader and erase everything off my phone?
Big big issues in Android 12 with reception and connectivity, please refer to my other topics, they REMOVED THE CARRIER AGGREGATION TOGGLE completely rendering the phone utterly slow on networks outside of Korea for my N version and the same can be said for others.
It's really sad and trust me, i've been trying for a solution.
For more info refer to my topic: https://forum.xda-developers.com/t/...-kt-please-help-me-lol.4506203/#post-87580253
And this post: https://forum.xda-developers.com/t/...s-opid-mismatched-error.4345963/post-87590409
The issue is in that the devs just took out so much code I think when it comes to the snapdragon modem, it's really dumb.
There needs to be a solution, I want to email LG but yeah... they are dead... maybe there are like 3 devs still there doing some work but realistically they don't care, they're probably just like : just buy a p7 or 14 pro man...
FRUSTRATING!
This phone would be so much better if I could get CA to work ffs..
Shawn R said:
So, how does someone extract the image from their phone? I had a LG G3, G4, and G6 a few years ago. And I put TWRP on all three. I know that with TWRP I can backup the image but I'm kinda scared to put it on my G8 because it could cause all kinds of problems. Wouldn't I have to unlock the bootloader and erase everything off my phone?
Click to expand...
Click to collapse
Well--if you look at the cross-flash thread....you can just pull the information from the partitions without erasing them---you get to copy them as they are at the time you do it (I found you need to rename the files--the software used creates rather cryptic file names).....I have looked at & used this method--it works, but you need to be VERY CAREFUL during this or you could do real damage to the phone. I pulled all the partition information from another phone--deleted the information that prevents a cross-flash & installed a different ROM on the phone...so I can say that it works VERY well--I even restored one partition from the old ROM to maintain the serial# of the phone.
debianmain1 said:
Well--if you look at the cross-flash thread....you can just pull the information from the partitions without erasing them---you get to copy them as they are at the time you do it (I found you need to rename the files--the software used creates rather cryptic file names).....I have looked at & used this method--it works, but you need to be VERY CAREFUL during this or you could do real damage to the phone. I pulled all the partition information from another phone--deleted the information that prevents a cross-flash & installed a different ROM on the phone...so I can say that it works VERY well--I even restored one partition from the old ROM to maintain the serial# of the phone.
Click to expand...
Click to collapse
What partition do you need to restore from the old ROM to maintain the serial number? I had issues last time I tried cross flashing, and I think I missed this step.
nortnil said:
What partition do you need to restore from the old ROM to maintain the serial number? I had issues last time I tried cross flashing, and I think I missed this step.
Click to expand...
Click to collapse
The info is in the thread--I don't remember right now....
Hello, I never used WiFi calls and VOLTE never worked on this phone. In july, I both updated to A12 and switched to a new carrier. problem is phone calls have poor quality voice as there is no VoLTE and 4G/LTE bandwith is terrible since I switched. I wanted to follow your instructions and go to the enginnering menu BUT dialing *#*#4636#*#* just makes the number disappear and nothing happens.. Do you have any clue of how to access it ?
Also, I went to *#546368#*820# --> SVC Menu --> VoWiFi --> switched Wi-Fi Calling Toggle form 0 to but.... nothing changed. Not options int the 3dots phone options and no new shortcut to add in the slide menu. Do you have any clue ?
I just found that you can change the "VoLTE quality" in the " dots phone menu section with "automatic/suppress/blur" options. I will try suppress to see if it's better.

Categories

Resources