Related
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.
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.
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.
I've posted the question: "Can the Google Store Pixel 5 bootloader be unlocked?" in rooting threads and gotten no reply.
The model number is the GD1YQ
Yes, of course. However, the model number can belong to Verizon or AT&T as it's the N. American model.
GTT9Q - global
G5NZ6 - Japan
RBEmerson said:
I've posted the question: "Can the Google Store Pixel 5 bootloader be unlocked?" in rooting threads and gotten no reply.
The model number is the GD1YQ
Click to expand...
Click to collapse
Go to this website and enter your IMEI. It will tell you if it's a Verizon branded phone or not.
Check Your Device's IMEI | Bring Your Own Device to Verizon
Check your device's IMEI to see if it's compatible with Verizon's network. Need help finding your IMEI? We have instructions for your device type.
www.verizon.com
Nope - not a VZW phone, just one they like:
Awesome, your Pixel 5 is a perfect match for our network.Your device also requires a SIM card. We'd be happy to send you a new SIM card for free, or you can check if your current card already works with our network.
Click to expand...
Click to collapse
Yes, there's no SIM in the phone. No, there won't be until it's rooted. Or there's no way to unlock the bootloader.
This phone will replace an S7. I won't move stuff over until I know I won't be doing FDR's.
Have you tried it with a sim In it? Like you, I normally wait until it's set up to migrate the sim but I've run into this issue before and it's because it had been activated on another carrier prior. Give that a shot.
I did some checking on the IMEI and come back with unlocked, clean. I tried four checkers, and they agree. Except one site, for some odd reason, said I had a Samsung Pixel 5. Everybody else said Google Pixel 5.
Anyway, the phone's not tied any carrier - as expected.
I'm more than a little reluctant to move my S7's SIM to the P5. It's meaningless to the Pixel 5. I doubt it would ding the SIM to make it unusable in the (old) S7. Better safe than sorry.
I'm working through my WiFi net for what little setup I've done. To date, there've been no problems. I deliberately didn't finish setting up the P5, so I get complaints about that and no SIM- no surprise.
The sim has nothing to do with the ability to unlock the bootloader. If you buy a Verizon device I don't care what sim you put in or if you never put in a sim, you can't unlock the bootloader. I always buy Google devices and before I turn it on I put in my Verizon sim. OEM unlock is always active.. always! If you want flawless ability to unlock and root never buy a carrier branded device. Some make you wait until you pay off the device, some make you wait 30 or 60 days, and some like Verizon don't care what you do they'll never allow unlock.
So if you're worried then flip the OEM unlock switch and put in your sim and enjoy the device. I'm not sure what you're waiting for.
A) My P5 isn't tied to VZW, or anyone else. B) OEM unlock isn't active (greyed out) & no response to touches - USB Debugging is active, and set to ON. Whether OEM unlocking is active hinges on the bootloader being unlocked. Bootloader locked, no OEM unlocking, no rooting.
My current phone (Sammy S7) is rooted, and it's an ex-VZW device, with a locked bootloader. I don't remember how getting past the locked bootloader happened, but... SuperSU, RootChecker, FX, Titanium are alive and running as su. My hope is the same magic applies to the P5, but it doesn't look as though it does. Sigh...
RBEmerson said:
A) My P5 isn't tied to VZW, or anyone else. B) OEM unlock isn't active (greyed out) & no response to touches - USB Debugging is active, and set to ON. Whether OEM unlocking is active hinges on the bootloader being unlocked. Bootloader locked, no OEM unlocking, no rooting.
My current phone (Sammy S7) is rooted, and it's an ex-VZW device, with a locked bootloader. I don't remember how getting past the locked bootloader happened, but... SuperSU, RootChecker, FX, Titanium are alive and running as su. My hope is the same magic applies to the P5, but it doesn't look as though it does. Sigh...
Click to expand...
Click to collapse
Your P5 is tied to something whether you know it or not. If you didn't buy it from Google, Fi, or another company as unlocked then it's tied to a carrier. Whether OEM unlocking is active has absolutely nothing to do with the bootloader being unlocked other than allowing it to be so. You've got it backwards, you're basically putting the cart before the horse. You cannot unlock the bootloader if the OEM is grayed out. If the bootloader is unlocked at some point the switch was active and the bl unlocked in fastboot. Just curious, where did you get the device from? If you bought it 3rd party someone sold you a bill of goods. If you got it from Google and the switch is not active then return it for a replacement.
Sorry, I'm not familiar with the S7. I do believe there was/is a way to bypass the security and get into download mode or something of the sort but I just don't know.
See below for the reason why OEM Unlock has to be available before unlocking the bootloader.
Or...
Catch-22: Need an unlocked bootloader to get OEM unlock, need OEM Unlock to unlock the bootloader.
That the OEM Unlock option is greyed out means no OEM Unlock, period.
And that's what I'm trying to sort out.
[Guide] Root Pixel 5 XL Android 11 (R)
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
This will erase all user data from the device!
Backup your data
Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Notes: After unlocking your bootloader, you'll see a warning: You will see this warning until, you relock the bootloader.
Do not relock your bootloader until you have returned the device to Stock..
Click to expand...
Click to collapse
The same requirement appears in
[Tutorial] Unlock Bootloader, get root and valid Safetynet
RBEmerson said:
See below for the reason why OEM Unlock has to be available before unlocking the bootloader.
Or...
Catch-22: Need an unlocked bootloader to get OEM unlock, need OEM Unlock to unlock the bootloader.
That the OEM Unlock option is greyed out means no OEM Unlock, period.
And that's what I'm trying to sort out.
[Guide] Root Pixel 5 XL Android 11 (R)
The same requirement appears in
[Tutorial] Unlock Bootloader, get root and valid Safetynet
Click to expand...
Click to collapse
That's not a catch-22. The first part of your statement and the guide is correct. You need to be able to toggle the OEM switch in order to perform the bootloader unlock. As far as the bootloader being unlocked first, that's false. It needs to be unlockable. The OEM toggle is the gateway to unlocking the bootloader. The carriers block access to that gateway. Verizon is permanent. Other carriers I believe can be temporary after a period of time. I don't know because I've never bought a carrier phone.
@RBEmerson Where did you buy the device?
@ridobe Thanks for resolving the conflict.
Here's what I get about the bootloader. Additionally, the About info says nothing about Verizon, or any specific carrier. OEM Unlock is greyed out. How to change that, then?
@bobby janow Open box from an eBay seller in Florida. I'd ask them about any possible carrier connection but I had problems with shipping (I paid for FedEx, they used First Class). Messy details like carrier connects? Hah!
{
"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"
}
Not much useful for identifying the phone's "pedigree" - the only info not shown relates to the SIM (no SIM, no info, of course).
@RBEmerson Unfortunately, unless you can determine which carrier it is on you are out of luck. If it's TM you might be able to call them and get it released and perhaps other carriers too. If it's Verizon then there is absolutely no hope to bl unlock. Are you sure the device has been paid off or are they on a monthly plan for 2 years? The problem with buying on eBay is that people are deceptive. They probably sold it as carrier unlocked which it very well might be. That has nothing to do with bl unlockable. When I sell a device I show a picture of the OEM switch as active so there is no mistaking it. You would have needed to specifically ask for that screenie from the seller.
Also know that even a Verizon device can be called unlocked legitimately. Google even sells Verizon devices. But they are not bl unlockable and that is a mistake a lot of buyers (and some sellers) make. If you want to root and unlock the bootloader then you'll need to get the info from the seller or try to return it to them. Or you can always sell it and buy one you want. Sorry to be the bearer of bad news but there still is a little hope if it's not a Verizon device.
Understood regarding VZW. What I've posted is all I know about the phone. The seller had several (many?) of these phones. That is, this isn't a private, one-time seller.
By comparison, my Samsung S7's model number, SM-G930U, is a Verizon-only model number. (Which is correct)
The P5's model is GD1YQ which seems to be (albeit not conclusively) a Google Store device. AFAIK, Google Store phones can be unlocked.
All that I have to work with is in the two pictures I posted. FWIW, the bloatware doesn't include any of the usual VZW apps - another argument against being a VZW device. Likewise, there's nothing that shouts AT&T or TM or (used to be) Sprint, etc.
Hence the original question: "can I unlock this thing? If so, how?"
RBEmerson said:
Understood regarding VZW. What I've posted is all I know about the phone. The seller had several (many?) of these phones. That is, this isn't a private, one-time seller.
By comparison, my Samsung S7's model number, SM-G930U, is a Verizon-only model number. (Which is correct)
The P5's model is GD1YQ which seems to be (albeit not conclusively) a Google Store device. AFAIK, Google Store phones can be unlocked.
All that I have to work with is in the two pictures I posted. FWIW, the bloatware doesn't include any of the usual VZW apps - another argument against being a VZW device. Likewise, there's nothing that shouts AT&T or TM or (used to be) Sprint, etc.
Hence the original question: "can I unlock this thing? If so, how?"
Click to expand...
Click to collapse
The only way is to get that OEM switch active otherwise you are SOL. Just an FYI, I have 2 Pixel 5s. One I bought at the Google store and the other was bought at a Verizon store. They are both model GD1YQ. So your model ID means nothing in relation to where the device was bought or how it's branded. Check to see if you have a service called My Verizon Services under "settings-apps-all apps-show system" I just put in a Verizon sim and it shows up but I disable it since they can read my app activity with it active. But it might give you a clue, I'm not sure what that clue would be. ;-) You really need to contact the seller and find out where the phone was purchased. If you want PM me the eBay listing maybe I can root around (no pun intended) and even ask the seller about bl unlock as a prospective buyer. Also, what is the SKU on the box?
The box's SKU's GAO1955-US doesn't match what's listed on eBay (GAO1355-US). Google searches don't come up with a hint of an idea about the pedigree.
Sigh... there's a possibility this is a VZW phone, or maybe TM.
There's no sign of any branded apps, only Google apps. IIRC even an FDR doesn't make VZW apps disappear. At least not when I rooted the S7 (yea for Titanium doing the job!).
The immediate challenge is to run down whose phone this is. I suppose I can take it to T-Mobile in hopes a) it's a TM phone and b) they'll unlock the bootloader. AFAIK, short of taking someone hostage at gunpoint, VZW doesn't want to discuss the idea, let alone do it.
I still think there should be a way to positively identify if unlocking is a possibility.
About the eBay listing, look for item 284112075311
It doesn't take much thinking to find the seller's phone number. Which I called. Whoever answered the phone hasn't visited the clue store in many, many years.
RBEmerson said:
The box's SKU's GAO1955-US doesn't match what's listed on eBay (GAO1355-US). Google searches don't come up with a hint of an idea about the pedigree.
Sigh... there's a possibility this is a VZW phone, or maybe TM.
There's no sign of any branded apps, only Google apps. IIRC even an FDR doesn't make VZW apps disappear. At least not when I rooted the S7 (yea for Titanium doing the job!).
The immediate challenge is to run down whose phone this is. I suppose I can take it to T-Mobile in hopes a) it's a TM phone and b) they'll unlock the bootloader. AFAIK, short of taking someone hostage at gunpoint, VZW doesn't want to discuss the idea, let alone do it.
I still think there should be a way to positively identify if unlocking is a possibility.
About the eBay listing, look for item 284112075311
It doesn't take much thinking to find the seller's phone number. Which I called. Whoever answered the phone hasn't visited the clue store in many, many years.
Click to expand...
Click to collapse
The listing specifically says Verizon - TMobile. They also have a return policy if you bought it within 30 days. You might want to take advantage of that.
Unfortunately, I'm square up against the wall for time. I'm moving from the S7 to the P5 to take advantage of BT 5.0 and the ASHA protocol for use with hearing aids. Having significant hearing loss, HA's are a must. While many HA's function without streaming and control apps, the newer units pretty demand it (good thing, but there are times I leave the phone behind or what happens if the phone's battery is dead).
Anyway, I have to get the P5 up and running like it happened yesterday. Exchanging phones is, at this point, a non-starter. Grrr...
Beyond that, how can I be sure that a phone, from any source, has an unlockable bootloader?
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.