VS985K purchased new from Verizon, ships with 47A firmware,new variant? - Verizon LG G3

I have a new LG G3 from Verizon I bought to replace my aging Motorola Droid RAZR M. It seems this one is a model "vs985K" which I have never seen mentioned before. It shipped with 47A Marshmellow, and conventional tot flash methods (using 35B dll and such) do not work. States "no ks version."
So I dd'd in the relevant partitions from the 35B bootstack, and TWRP as needed. It bricked the phone. Black screen. Nothing.
Fortunately, I am not a noob at this. I shorted the testpoints to get into qualcomm 9008 mode, and to my absolute horror, even BoardDiag 3.99 would not talk to the board. It seems this may be a new part number. Swapping some files from a another tool got it to finally flash, and I'm still trying to recreate what I did, but however I did it now I know I have a tool that can debrick it via qualcomm 9008 mode and so I'm ready to try again.
After some messing, it seems the exploitable aboot is what makes it brick. Unless I am missing something. Anyhow that's not the point of this post. The point of this post is to discuss this potential new variant, and how the heck to get this on 10B. Any ideas? It really seems tough if I can't use the exploitable aboot.
PS: I would post how to debrick a vs985K, but because it uses tools and software that is of questionable copyright status, I can't. PM me if you are desperate and maybe I can help you, though.

The K is probably just referring to the color. Is it black?
Some people get bricked doing what you did, others it works fine including me when I tested that method several times. I have a thread in the General section about that method. The title includes "KS Error".
When some people do something that causes the black screen, they're still able to go through the motions of putting it in Download mode and you can see its in that mode in Device Manager, and then able to flash either the 10B TOT (with downgraded partitions, there's a chance you wouldn't get the KS Error any more) or the 10B KDZ, since the downgraded partitions would now let you flash any KDZ you want.
As far as I know, everyone who tried that method - those who didn't brick and those who did, were able to downgrade to 10B via TOT or KDZ after. Read the thread for more details.

Yeah, I was following your post. It led to a black screen. I know I got all the partitions but I had to short the test pins and use qualcomm 9008 mode to get back.
I'll try again and report back. Don't see what I could've possibly missed though. I'm trying to get back to 10B in the end.

Back at the black screen. LG FlashTool for TOT method seems to not want to flash it even though I can "kinda" get it into download mode (it just doesn't show anything on screen, but registers in device manager)
See attachment.
KDZ Methods similarly fail with "upgrade stopped due to an error"
Currently sitting at qualcomm 9008 mode with boarddiag, so if you have any ideas of what to flash, I can do basically anything, lol.

It seems flashing aboot is the culprit. I can flash just about any other part of the bootstack without issue. Is it possible 47A is blowing a qfuse or something to prevent aboot downgrades?

I really couldn't speculate, I refrain from guessing. There's guesses out there covering at least a few possibilities, but the only circumstancial evidence is the "KS error" and the fact that some get the black screen, but it's weak evidence since I'm pretty sure that some who got the KS error were successful downgrading without a hitch, and I know for sure others who bricked were definitely able to recover.
I'd try a different PC. Using the original USB cable? Using a USB 2.0 port that comes directly off your PC's motherboard, and not a USB 3.0 port or a USB hub?
Do you have the right special drivers to use with BoardDiag?
As far as I know, I've never come across anyone who couldn't downgrade eventually, and all our VS985s have a letter after the model number signifying the color.

roirraW "edor" ehT said:
I really couldn't speculate, I refrain from guessing. There's guesses out there covering at least a few possibilities, but the only circumstancial evidence is the "KS error" and the fact that some get the black screen, but it's weak evidence since I'm pretty sure that some who got the KS error were successful downgrading without a hitch, and I know for sure others who bricked were definitely able to recover.
I'd try a different PC. Using the original USB cable? Using a USB 2.0 port that comes directly off your PC's motherboard, and not a USB 3.0 port or a USB hub?
Do you have the right special drivers to use with BoardDiag?
As far as I know, I've never come across anyone who couldn't downgrade eventually, and all our VS985s have a letter after the model number signifying the color.
Click to expand...
Click to collapse
Thanks. I didn't know about the extra letter, and mine is indeed black.
You've given me some leads to chase, if nothing else.
I'm not afraid to mess as I can debrick just about anything. First up on my list of things to try is a different USB port (I was using a USB 3.0 port).

Weird, after experimenting a lot, I find that the KDZ tool (from a fresh 47A install) let's me downgrade to 35B, but it ALSO gives me a black screen with similar behavior.
No idea what that means, but for whatever reason, it seems this device will not accept pre-marshmellow boot loaders.

http://forum.xda-developers.com/showpost.php?p=66096623&postcount=965
This does suggest a qfuse is blown by 47A. Unfortunately, it seems newer production phones like mine DO obey the qfuse, and I would furthermore speculate that LG/Verizon did this intentionally to cover these new phones.
The fact that mine can't flash (or rather can, but dies) a 35B KDZ, and was purchased fairly recently directly from Verizon (preflashed with 47A) all support this.
It looks like we may need to find an exploit for the marshmellow bootstack (or an outright bootloader unlock) if we want to unlock newer production phones. Unfortunately, I doubt this platform is new enough to attract devs with that kind of skill. However, I'm still here and willing to test any and all exploits, being if there's one thing I CAN do, it is unbrick a phone.

R-T-B said:
http://forum.xda-developers.com/showpost.php?p=66096623&postcount=965
This does suggest a qfuse is blown by 47A. Unfortunately, it seems newer production phones like mine DO obey the qfuse, and I would furthermore speculate that LG/Verizon did this intentionally to cover these new phones.
The fact that mine can't flash (or rather can, but dies) a 35B KDZ, and was purchased fairly recently directly from Verizon (preflashed with 47A) all support this.
It looks like we may need to find an exploit for the marshmellow bootstack (or an outright bootloader unlock) if we want to unlock newer production phones. Unfortunately, I doubt this platform is new enough to attract devs with that kind of skill. However, I'm still here and willing to test any and all exploits, being if there's one thing I CAN do, it is unbrick a phone.
Click to expand...
Click to collapse
@R-T-B For the sake of discussion and trying to add more content I will add to this post. What you experienced was similar to what I had...well sorta. I have 4 LG G3's in my family. The first of which was mine from over a year ago. I was able to use KDZ and TOT methods to do what was necessary in rooting and then taking advantage of the aboot exploit for the first 2. However, I want to say that the 3rd and 4th version of the VS985 gave me a few fits. It was the 3rd handset that I had received that my wheels were spinning with trying to downgrade using the TOT and KDZ methods. Eventually, TOT worked for me, but similar to you I had gotten into an issue where the black screen of death was upon me. It felt like the grim reaper had come to take my new handset... I swapped USB ports, cables, DLL's and through much hair pulling finally was able to recognize the phone properly with the TOT method and downgraded. I never really got the phone display to work... I went into download mode blind by using another phone as a guide. Regardless of all the trouble I finally achieved success. By the time my fourth handset came from VZW, VS985K, I was running into the LAF/KS ERROR. Used the same cables, ports, dll's, etc etc. NEVER was able to downgrade... The only method that worked as a last ditch effort was the afore mentioned. Speculation is certainly dangerous, but I would surmise that VZW maybe made some slight hardware changes. Perhaps a slight change in manufacturing of the IC of the motherboard...who knows. But certainly everything done here is at our own risk. I was willing to flash mine immediately, as falling back on the 30 day satisfaction guarantee was there from me.

b00ster23 said:
@R-T-B For the sake of discussion and trying to add more content I will add to this post. What you experienced was similar to what I had...well sorta. I have 4 LG G3's in my family. The first of which was mine from over a year ago. I was able to use KDZ and TOT methods to do what was necessary in rooting and then taking advantage of the aboot exploit for the first 2. However, I want to say that the 3rd and 4th version of the VS985 gave me a few fits. It was the 3rd handset that I had received that my wheels were spinning with trying to downgrade using the TOT and KDZ methods. Eventually, TOT worked for me, but similar to you I had gotten into an issue where the black screen of death was upon me. It felt like the grim reaper had come to take my new handset... I swapped USB ports, cables, DLL's and through much hair pulling finally was able to recognize the phone properly with the TOT method and downgraded. I never really got the phone display to work... I went into download mode blind by using another phone as a guide. Regardless of all the trouble I finally achieved success. By the time my fourth handset came from VZW, VS985K, I was running into the LAF/KS ERROR. Used the same cables, ports, dll's, etc etc. NEVER was able to downgrade... The only method that worked as a last ditch effort was the afore mentioned. Speculation is certainly dangerous, but I would surmise that VZW maybe made some slight hardware changes. Perhaps a slight change in manufacturing of the IC of the motherboard...who knows. But certainly everything done here is at our own risk. I was willing to flash mine immediately, as falling back on the 30 day satisfaction guarantee was there from me.
Click to expand...
Click to collapse
Yeah, examination of my PCB shows it is version "2" as well, suggesting maybe this isn't the first revision. Maybe they are getting smarter.
I tried to go through the prcoess of accessing download mode with the black screen but the phone was completely dead to all input and would not respond to LG flash commands anymore.
Don't get me wrong, I am not complaining I still have a phone afterall and I know this is all at my own risk. This may be speculation but I'd like to think it is educated speculation that a new hardware revision exists.
Is anyone else willing to open their phone to see if the top of their PCB (The part near the camera) has similar markings to mine? It is inscribed (in gold) "VS985 HW V1.0 (2)". Note the "(2)" that makes me think they revised it a second time.

I'm going to try to use boarddiag to flash the entirety of the TOT. Any reason why this would be a bad idea? Seems as good as any at this point to see if it truly can't run 10B.
This may take a very long time, but heck, why not try?

Did not work. I think we can safely say whatever variant I have, a pre marshmellow bootloader will never load.

R-T-B said:
Is anyone else willing to open their phone to see if the top of their PCB (The part near the camera) has similar markings to mine? It is inscribed (in gold) "VS985 HW V1.0 (2)". Note the "(2)" that makes me think they revised it a second time.
Click to expand...
Click to collapse
Is it necessary to disassemble the phone to expose that part of the pcb? Received my factory refurb vs985 two days ago, and am interested in rooting it. Just removed the back and don't see any part of the pcb.
Sent from my LG-D801 using Tapatalk
---------- Post added at 01:01 PM ---------- Previous post was at 12:57 PM ----------
SofaSpud said:
Is it necessary to disassemble the phone to expose that part of the pcb? Received my factory refurb vs985 two days ago, and am interested in rooting it. Just removed the back and don't see any part of the pcb.
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
My device shows a mfr date of 10/26/15. Settings/about identifies as Rev 1.0, don't see any model reference numbers with "ks" suffix.
Sent from my LG-D801 using Tapatalk

I wouldn't advise disassembly to check for the markings unless you've already voided your warranty for some reason, but thank you for thinking of me and looking around your phone.
My advice to you would be to start by poking around the forums and looking up how to do a 10B TOT revert. You'll need the TOT file, and a .dll to go with it most likely. This is the safest way (if it works) to revert to firmware where you can get (and keep) root.

R-T-B said:
I tried to go through the prcoess of accessing download mode with the black screen but the phone was completely dead to all input and would not respond to LG flash commands anymore.
Click to expand...
Click to collapse
Could you clarify something? Have you been able to recover from the black screen issue? I was under the impression you have but now I'm not sure.

roirraW "edor" ehT said:
Could you clarify something? Have you been able to recover from the black screen issue? I was under the impression you have but now I'm not sure.
Click to expand...
Click to collapse
Yes, I recovered, but it was complicated.
First off, I had to use a modified version of BoardDiag (I can upload this if anyone needs it, but I'm unsure as to it's legal status) with the qualcomm drivers and testpoint shorted. Second, I had to reflash the 47A files via that method, anything lower than 46A will brick it again.
All in all, it's pretty messy to recover from what I did, but I was confident enough that I've probably done it 4 times now... unfortunately all without success reaching anything below 46A. Even a 35B flash bricks it.

I have a vs985wk, just recently purchased. I believe that the 'W' is for the color, which is white.

SofaSpud said:
I have a vs985wk, just recently purchased. I believe that the 'W' is for the color, which is white.
Click to expand...
Click to collapse
Interesting. What's the "K" mean then?

R-T-B said:
Interesting. What's the "K" mean then?
Click to expand...
Click to collapse
Good question! After reading your posts I looked around a bit for info re the 'k' but didn't find much.
I have yet to root (or even carrier activate) mine. I just received the Totalwireless similar today, but am thinking that perhaps I shouldn't activate until after rooting and disabling OTA, in hopes of avoiding further lock down against rollback. Device is rollback level 2, FW 47A.
Sent from my LG-D801 using Tapatalk

Related

Strange brick situation with D620r

I tried to unlock bootloader in my D620r running V10g EUR firmware. It is unbranded G2 Mini bought in polish electronic store.
I used this instruction: http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
After all described actions, I'm left with some nice black brick :/
It does not power on, enter to download mode, hard reset, not even battery charging during phone is off - no animated battery screen.
The only reaction is when the battery is removed from the phone - then plugging in the USB cable results in screen, that battery was removed and question mark. That's all.
Phone is not recognized as any USB device, like it was not connected at all.
I tried to revive it with this instruction: http://forum.xda-developers.com/showthread.php?t=2582142 , but it didn't help. Linux does not see it - USB subsystem is not even triggered that something was plugged in.
Can anyone confirm this behaviour of D620r? What is your advice? Is any chance to revive my phone? Is flasing NAND at phone shack could help?
Try this (with G2 Mini files!):
http://forum.xda-developers.com/showthread.php?t=2582142
Vagelis1608 said:
Try this (with G2 Mini files!):
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
I already tried, but as I wrote phone is not seen in Linux. Devices sdX<numbers> are not populating, there is nothing in the system logs,
USB driver does not see phone - there is no USB communication at all No LG logo, screen still OFF.
The same thing that happen to you, has happen to me as well.
Check my signature. I don't think there is any other way:/
Vagelis1608 said:
The same thing that happen to you, has happen to me as well.
Check my signature. I don't think there is any other way:/
Click to expand...
Click to collapse
Oh, I expected it. I'm about to send it to service like you. It's my first phone which I bricked that hard
Is your phone still at service now, or they repaired it for you some time ago? I think they will use some
kind of hardware box/flasher to flash firmware directly to EEPROM/NAND/NVM whatever sits there,
am I right?
twinsen.net said:
Oh, I expected it. I'm about to send it to service like you. It's my first phone which I bricked that hard
Is your phone still at service now, or they repaired it for you some time ago? I think they will use some
king of hardware box/flasher to flash firmware directly to EEPROM/NAND/NVM whatever sits there,
am I right?
Click to expand...
Click to collapse
It's been 2 weeks now.
Personally, I believe that they will simply sent a new phone. (They won't have to pay an employee to fix it and they will use the working parts as replacement parts for other phones - with them, nothing goes to waste )
BTW, don't tell them you did it. Tell them you don't know what happen
BTW, does anyone knows why there is a possibility to hard brick LG's that easy? What is wrong with some software mess? Is this some LG's mechanism to prevent phone modification? Some claims that only motherboard exchange in some hard brick cases is needed. Why? Can't service specialist just flash directly to chip?
twinsen.net said:
BTW, does anyone knows why there is a possibility to hard brick LG's that easy? What is wrong with some software mess? Is this some LG's mechanism to prevent phone modification? Some claims that only motherboard exchange in some hard brick cases is needed. Why? Can't service specialist just flash directly to chip?
Click to expand...
Click to collapse
If the aboot is broken, then the bootloader can get messed up.
You mean like JTAG? They don't seem to do that.
Sent from my GT-I5500 [CM11]
@twinsen.net I have d620r and I have used same instructions as you did. It worked like a charm.I now have unlocked bootloader, custom recovery and cm11. My phone is also locked on network.. Maybe you did something wrong?
Vagelis1608 said:
Personally, I believe that they will simply sent a new phone. (They won't have to pay an employee to fix it and they will use the working parts as replacement parts for other phones - with them, nothing goes to waste )
Click to expand...
Click to collapse
2 more weeks later...
I was right. LG sent a new phone as "they couldn't fix it" (as per their words).
So, they kept the battery, screen and etc, aka the parts people will pay to fix

Has anybody here had their phone repaired via Verizon's Asurion insurance?

I'd paid $180 in Asurion phone insurance as part of my Verizon plan over the last 18 months I've had my G3, and I think it may be time to finally use it.
Some time within the past several days, it appears I must have pressed too hard on my screen at some point because now, when the screen is dark/black, there is a reasonably noticeable 'smudge' (for complete lack of a better word) inside my screen that is a lighter color than the rest of everything else. I can't really seem to think of the correct words right now to describe it, but it's basically what you'd imagine would happen when you press a screen too hard. The fortunate thing is, it's really only noticeable when the screen is dark, but it's still enough to drive me nuts.
I had a few questions about Asurion. ~3 years ago, I paid my $100 deposit and sent my old Galaxy S3 in because I broke the screen. They sent me back a brand new phone. It was sealed in the original stock box and it came with everything a new phone does (headphones, cable, charger, all the paperwork.) Plus the phone was very clearly not a refurb; it was flawless. I was under the impression I was meant to either have the screen repaired on my phone or get a refurb, but I absolutely got a brand new phone. Maybe I was lucky.
But I understand that my experience likely wasn't typical. So I want to know, from people who have sent their faulty/broken phones in to Asurion:
- Did they fix your problem and send your old phone back? Or,
- Did you get a refurb? Or,
- Did you get a new phone?
Normally, I wouldn't care, but my serious concern is that I might get a new or refurb phone that has an updated OS. This brings me to my next question(s).
- If I get a new/refurb phone back from Asurion that is running 47A or something else relatively new, will I still be able to unlock my bootloader, install TWRP, root, and just generally get everything back to the way I have it now, loaded with customization and modifications? Or do the newer G3 updates keep the phone locked down permanently, in which case I'll be SOL? What's the most recent software update to which I'll be able to make all of my modifications to?
Sorry for the wall of text, but I just want to make sure I get everything cleared up. I would really like to get this screen issue repaired ASAP, but if there's any chance at all that I'll be stuck on stock un-rooted forever when I get the phone back, I'm not going to take that chance. But if it's trivial to unlock the bootloader, install TWRP, and root the newer updates like 47A, I'll be sending my phone in ASAP.
Thanks.
I haven't used Asurion since about 2009 so can't say much.
I can say that it doesn't matter what stock ROM a replacement would come with, including up to the latest which is 47A, you won't be stuck. Just flash the 10B TOT using the .DLL that was extracted from the 35B KDZ, root with the Stump app, install TWRP with TWRP Manager from the Play Store and flash whatever you want.
This might be a little late for you but had to replace my verizon vs985 lg g3 back in December. I paid my $100 copay, and Asurion sent me refurb. Even when it looks like a retail phone it's usually a refurb unless the phone is brand new and they haven't gotten any bad ones back to fix up. Asurion doesn't have a repair department. This is the first smartphone I've gotten through asurion, back in the days of flip phones I got a bunch of replacements and often I had to get 2-3 before I got a refurb that actually worked. This g3 worked ok on the first try, although I do have one weird rebooting issue, that started a week after I got it, and recently got way worse may or may not be hardware related, theoretically they should send me another refurb if it is hardware under their warranty(without another copay), but I have a feeling getting them to honor it will be a battle.
It came with Lollipop at the time, i forget if it was 5.0.1. or 5.1.1.
madmax988 said:
This g3 worked ok on the first try, although I do have one weird rebooting issue, that started a week after I got it, and recently got way worse may or may not be hardware related, theoretically they should send me another refurb if it is hardware under their warranty(without another copay), but I have a feeling getting them to honor it will be a battle.
Click to expand...
Click to collapse
If I were you, before bothering try anything else I would restore to stock using the 10B TOT, because TOTs flash more partitions than KDZs and can fix weird issues that flashing KDZs and other ROMs can't.
roirraW "edor" ehT said:
If I were you, before bothering try anything else I would restore to stock using the 10B TOT, because TOTs flash more partitions than KDZs and can fix weird issues that flashing KDZs and other ROMs can't.
Click to expand...
Click to collapse
My refurbished phone is stock never rooted never flashed verizon vs985 currently on 5.1.1. It reboots only during phone calls. Do you think rooting it and doing all that stuff you suggested, would be of any use to me?
madmax988 said:
My refurbished phone is stock never rooted never flashed verizon vs985 currently on 5.1.1. It reboots only during phone calls. Do you think rooting it and doing all that stuff you suggested, would be of any use to me?
Click to expand...
Click to collapse
I understand that. You don't have to root it - rooting isn't involved in what I'm suggesting; it's using official LG ROM files and the Windows software necessary to flash them. I'd flash the 10B TOT using the .DLL that's extracted from the 35B KDZ. Then I'd test the situation you describe while still on 10B and see if it reboots. If it doesn't, I'd flash the 47A KDZ and test it again.
Edit: unless you don't have the original USB cable. Always use the original USB cable that comes with a device when new to flash a phone from a PC.
Click to expand...
Click to collapse
There's no way of knowing if whoever actually refurbed the phone did what they should in order to return the software to a pristine condition. They obviously didn't QC their effort very well. It's possible they didn't even do anything to the phone. There's also no way of knowing if the person who owned the phone before it was refurbished ever rooted it. Even if they had (for example) flashed the 35B KDZ before they refurbished it (it's common to return to stock unrooted before turning a phone in under warranty), flashing KDZs doesn't solve as much as flashing TOTs does.
A couple of months ago I was having consistent weird issues that wouldn't go away no matter what ROM I flashed while rooted, or what KDZ I flashed. It wasn't until I flashed the 10B TOT that the issue went away - from there I was able to do again whatever I wanted (flashing ROMs, KDZs) without the issue returning.
Or you can exchange for another refurb and take a chance that you might get yet another different or worse half-effort fixed phone.

G3 Automatically Boots into DL mode. Can't use LG Flash Tool, IMEI all 0's

I was having sms issues on cm13, and it was suggested that I flash the TOT again.
Not sure what happened the first time I tried to flash the TOT, but I was following directions as always and just assumed it would work flawlessly as it has done in the past. It failed somewhere along the line but I wasn't paying too much attention .
Now the phone automatically boots into DL mode (after LG screen, unusual), and anytime I try to flash a TOT now the flash tool goes from "Waiting for Connection" to showing a PID and showing my IMEI as null (all 0's). After some googling around I realize that this is not good in the slightest. The flash tool will timeout after ~20s and try again, but just keeps timing out endlessy after 20s.
This looks to me like a brick but I don't have enough experience or knowledge to say for sure. If anyone has suggestions I would greatly appreciate it.
Try the 10B KDZ just for the hell of it. I'm sorry to hear you're having so much trouble. Don't do anything rash, we'll see what we can do.
I hope you have a TWRP backup of the EFS (IMEI) in a safe place or once you get the phone working you'll have to use QPST or some such to manually type in your IMEI.
roirraW "edor" ehT said:
Try the 10B KDZ just for the hell of it. I'm sorry to hear you're having so much trouble. Don't do anything rash, we'll see what we can do.
I hope you have a TWRP backup of the EFS (IMEI) in a safe place or once you get the phone working you'll have to use QPST or some such to manually type in your IMEI.
Click to expand...
Click to collapse
I tried flashing that kdz already, as well as the 47a. Both get up to that 4% like I had problems with before. Now the phone doesn't seem to want to boot into dl mode : ^) I can get into the system recovery but any of the options just take me to the LG boot screen.
And nope, no backups. I got this phone 4 days ago as a refurb to last me until the (supposedly) htc nexus phones in the fall. Never really got anywhere so didn't think to back anything up, especially not the imei. Never had a device be this finicky in my years rooting android devices.
Thanks for all your help man, but I may just have to chalk this one up as sunken costs and go back to my m7
Go with what roirraW "edor" ehT tells you first and foremost. What I'm posting is another option at last resort. If you dont have a backup of your imei, you will need an IMEI editor and use the IMEI that is printed inside your phone or on the box it came with.
I had the same problem. It's nerve racking but can be easily fixed. I'll look for the program I used and post it once I find it. Just so it's said, changing your IMEI is highly illegal. Make sure you restore your original that came with the device and not someone elses.
inexplicability said:
I tried flashing that kdz already, as well as the 47a. Both get up to that 4% like I had problems with before. Now the phone doesn't seem to want to boot into dl mode : ^) I can get into the system recovery but any of the options just take me to the LG boot screen.
And nope, no backups. I got this phone 4 days ago as a refurb to last me until the (supposedly) htc nexus phones in the fall. Never really got anywhere so didn't think to back anything up, especially not the imei. Never had a device be this finicky in my years rooting android devices.
Thanks for all your help man, but I may just have to chalk this one up as sunken costs and go back to my m7
Click to expand...
Click to collapse
I know it may seem useless, but take the battery out and leave it out for an hour or more, then try to put it into Download mode again. When you try to put it in Download mode now, what happens exactly? Are you checking in Windows' Device Manager to see if the phone shows up in the Modem and Port sections? Does it ever show up?
Was it a warranty (LG or Verizon) refurb and do you have the option to try to exchange it for another?
Sure - I just wish I could do more.
What @thebigindian said reminded me - you may have to restore the IMEI before you can flash the TOT (assuming you can get into Download mode or at least QHSUSB_BULK 9008 mode). I have no idea how to go about that, though, as I've never had to - I just know there are threads in these sections on how to do it.
thebigindian said:
Go with what roirraW "edor" ehT tells you first and foremost. What I'm posting is another option at last resort. If you dont have a backup of your imei, you will need an IMEI editor and use the IMEI that is printed inside your phone or on the box it came with.
I had the same problem. It's nerve racking but can be easily fixed. I'll look for the program I used and post it once I find it. Just so it's said, changing your IMEI is highly illegal. Make sure you restore your original that came with the device and not someone elses.
Click to expand...
Click to collapse
I've looked into restoring the imei, and have found that some users had success using a method for the lg g2, but most of these methods require some sort of booting. I am unable to boot to anything but the lg screen. I'll try why Rode says about leaving the battery out and see what happens from there.
roirraW "edor" ehT said:
I know it may seem useless, but take the battery out and leave it out for an hour or more, then try to put it into Download mode again. When you try to put it in Download mode now, what happens exactly? Are you checking in Windows' Device Manager to see if the phone shows up in the Modem and Port sections? Does it ever show up?
Was it a warranty (LG or Verizon) refurb and do you have the option to try to exchange it for another?
Sure - I just wish I could do more.
What @thebigindian said reminded me - you may have to restore the IMEI before you can flash the TOT (assuming you can get into Download mode or at least QHSUSB_BULK 9008 mode). I have no idea how to go about that, though, as I've never had to - I just know there are threads in these sections on how to do it.
Click to expand...
Click to collapse
I'll get back to you in a bit after the battery has been out for awhile.
I picked this up off of amazon as a refurb device. The first 2 devices I received were defective out of the box (first one had bent pins in usb port, second would bootloop and i didnt know as much about dl/recovery as i do now, it was probably fixable looking back) so that should have kept me away lol. I know I could probably get away with sending it back saying the device is defective or something, but it really is my fault (I believe) and wouldn't exactly feel good about doing that. Then again I don't exactly feel good about having a $120 brick lol.
inexplicability said:
I've looked into restoring the imei, and have found that some users had success using a method for the lg g2, but most of these methods require some sort of booting. I am unable to boot to anything but the lg screen. I'll try why Rode says about leaving the battery out and see what happens from there.
I'll get back to you in a bit after the battery has been out for awhile.
I picked this up off of amazon as a refurb device. The first 2 devices I received were defective out of the box (first one had bent pins in usb port, second would bootloop and i didnt know as much about dl/recovery as i do now, it was probably fixable looking back) so that should have kept me away lol. I know I could probably get away with sending it back saying the device is defective or something, but it really is my fault (I believe) and wouldn't exactly feel good about doing that. Then again I don't exactly feel good about having a $120 brick lol.
Click to expand...
Click to collapse
I was afraid of that (can't put the IMEI back in without booting). I understand what you're saying but I honestly wouldn't be surprised if there was something wrong with the device anyway and that is the cause of why it bricked so easily. I don't trust refurbs.
I had a good experience selling on Swappa once but I haven't bought any through there so no idea if the experience would be better. I wouldn't buy any refurbed one. There's a black one on there that says Mint condition for $150. It's funny, some of them say 16 GB - as far as I'm aware there's no 16 GB version of the VS985.
roirraW "edor" ehT said:
I was afraid of that (can't put the IMEI back in without booting). I understand what you're saying but I honestly wouldn't be surprised if there was something wrong with the device anyway and that is the cause of why it bricked so easily. I don't trust refurbs.
I had a good experience selling on Swappa once but I haven't bought any through there so no idea if the experience would be better. I wouldn't buy any refurbed one. There's a black one on there that says Mint condition for $150. It's funny, some of them say 16 GB - as far as I'm aware there's no 16 GB version of the VS985.
Click to expand...
Click to collapse
Yeah now I don't trust refurbs either haha. It was worth a shot though. But yeah I noticed that about the 16gb device too when I was looking for a device to purchase.
I only picked up the g3 because a friend of mine asked about rooting his g3, wondering if he could get some more life out of it as his was becoming sluggish with all the bloat and whatnot. Figured I need a new phone now anyway and I would be able to get a g3, figure it out, then help him. That worked out great, didn't it?
UPDATE:
@roirraW "edor" ehT just thought I'd give you an update. I plugged in the device to power and it stayed at the charging screen with the loading icon for awhile, then I came back and it was in download mode!! Plugged into my pc and let windows install the drivers (took like 20 min, unusually long time) and was able to flash the 10b tot. IMEI is still 0, but at least there are ways to change that. Thanks again for your advice!
UPDATE 2:
Restored IMEI using this method: http://forum.xda-developers.com/showthread.php?t=2701861
Confirmed that mobile data / sms / mms are in working order... Going to try flashing cm13 again if that doesn't work I'll go back to stock and debloat as recommended
inexplicability said:
UPDATE:
@roirraW "edor" ehT just thought I'd give you an update. I plugged in the device to power and it stayed at the charging screen with the loading icon for awhile, then I came back and it was in download mode!! Plugged into my pc and let windows install the drivers (took like 20 min, unusually long time) and was able to flash the 10b tot. IMEI is still 0, but at least there are ways to change that. Thanks again for your advice!
UPDATE 2:
Restored IMEI using this method: http://forum.xda-developers.com/showthread.php?t=2701861
Confirmed that mobile data / sms / mms are in working order... Going to try flashing cm13 again if that doesn't work I'll go back to stock and debloat as recommended
Click to expand...
Click to collapse
Wow. I'm always surprised when things actually turn around so well.
Do that IMEI (EFS) backup in TWRP although it must not have been too tough after all. You're welcome! It's helped me on various phones including this one from time to time.
roirraW "edor" ehT said:
Wow. I'm always surprised when things actually turn around so well.
Do that IMEI (EFS) backup in TWRP although it must not have been too tough after all. You're welcome! It's helped me on various phones including this one from time to time.
Click to expand...
Click to collapse
I'll do an imei and nandroid backup once i get everything up and running. Tried using dirty unicorn, but google play services was failing. Tried cm13 but ran into sms issues again. Reluctantly installed stock 47a w/ debloat and it seems to be working ok.
Going to go off of your recommendations and use the xposed modules mentioned in the 47a thread until a more stable aosp based rom is available.
You may have actually helped me with my thread/issue, unwittingly.
Your symptoms are similar to what happened when I flashed anything lower than 46A bootloader wise... it would get a black screen (this is different than yours but keep reading), register as a device in download mode without any keypresses, and then refuse to flash the same way with all 0's IMEI.
It never occured to me to pull the battery for an hour. Maybe I should try that?
EDIT: ...And nope, that did not work either. I guess I just have to wait until marshmellow bootloader is exploited somehow...

Rear Camera stopped working and front camera is now in wonky mode

So the other day I went to use Snapchat to take a photo of something and noticed it wouldn't switch to my rear camera. After some investigation I discovered that the rear camera wasn't working. I went further and tried using a flashlight app, a few different camera apps from the Play Store and some other ideas that I thought might work. None of them did. Not only that but the front "selfie" camera was now taking very elongated and flipped upside down pictures in the standard camera app. Snapchat they're just fine, reversed like in a mirror, but fine aside from that.
For the next step I did a complete wipe, data and cache as well as a factory reset. Again, this didn't resolve my issue. So I started looking into hardware fixes and decided I would order a new rear camera. They weren't expensive and I felt comfortable enough to install it.
While waiting for the camera to come in from Amazon I went about using my phone as normal, no big deal to not have a camera. One day I left my camera in the car on a fairly warm day and when I came back it said the phone had shut off due to overheating. No biggy, I restarted the phone and for whatever reason decided to check the camera for s&g's and voila! The rear camera was working just fine...until I replied to a message and went to use the camera again. Back to not working. Damn.
Replacement camera arrives and I install it, easy peasy. I restart my phone and....nothing. Still doesn't work. I thought maybe it could be a software thing so I was going to root it and try a Rom, but I have a revision (2) PCB, so I guess that's completely out of the question.
Does anyone have any ideas? Anything I could try? I love this phone and would hate to have to get a new one before the new Nexus arrives. Thanks for any help
Revision 2 only affects things if under your battery there's a K at the end of the VS985 model # such as VS985WK.
I've had a revision 2 PCB all this time this last year and a half, and it doesn't affect me since I don't have a K submodel.
Do if you don't either, definitely flash the 10B TOT and if the camera doesn't work on 10B then it's definitely not a software issue.
http://forum.xda-developers.com/showthread.php?p=67945841
http://forum.xda-developers.com/showthread.php?p=68040923
http://forum.xda-developers.com/showpost.php?p=68098895&postcount=1470
roirraW "edor" ehT said:
Revision 2 only affects things if under your battery there's a K at the end of the VS985 model # such as VS985WK.
I've had a revision 2 PCB all this time this last year and a half, and it doesn't affect me since I don't have a K submodel.
Do if you don't either, definitely flash the 10B TOT and if the camera doesn't work on 10B then it's definitely not a software issue.
http://forum.xda-developers.com/showthread.php?p=67945841
http://forum.xda-developers.com/showthread.php?p=68040923
http://forum.xda-developers.com/showpost.php?p=68098895&postcount=1470
Click to expand...
Click to collapse
Well, wish I would've saw this post before I updated my phone this morning. Latest OTA update change the rooting?
There is no K after the model, but the pcb does have a (2). So just the standard rooting procedure that you linked? And the latest Verizon OTA?
premedicated said:
Well, wish I would've saw this post before I updated my phone this morning. Latest OTA update change the rooting?
There is no K after the model, but the pcb does have a (2). So just the standard rooting procedure that you linked? And the latest Verizon OTA?
Click to expand...
Click to collapse
See my thread about the 48A OTA in the General section regarding downgrading. You can't take OTAs once you're rooted. It'll download but fail to apply. Once you're rooted and on @xdabbeb 's stock 47A firmware in the Development section - also in my signature below, flash any of my debloat zips in the third post of that thread including the No OTA debloat zip. I only leave OTAs non-debloated on all the other debloat zips by default because I want to be aware when an OTA is available, although someone usually reports it on here before I get the notice.
roirraW "edor" ehT said:
See my thread about the 48A OTA in the General section regarding downgrading. You can't take OTAs once you're rooted. It'll download but fail to apply. Once you're rooted and on @xdabbeb 's stock 47A firmware in the Development section - also in my signature below, flash any of my debloat zips in the third post of that thread including the No OTA debloat zip. I only leave OTAs non-debloated on all the other debloat zips by default because I want to be aware when an OTA is available, although someone usually reports it on here before I get the notice.
Click to expand...
Click to collapse
I've always rooted my phones previously, but my last g3 I dropped and shattered the screen. This is the replacement which was already updated.
I'll poke through there and get it rooted tonight and hopefully that'll solve the camera problem. However at this point I'm worried that it might be another piece of hardware related to the camera. Maybe the laser focus or flash, not sure. That's the only other thing I think it'll be if it isn't software related.. (obviously)
premedicated said:
I've always rooted my phones previously, but my last g3 I dropped and shattered the screen. This is the replacement which was already updated.
I'll poke through there and get it rooted tonight and hopefully that'll solve the camera problem. However at this point I'm worried that it might be another piece of hardware related to the camera. Maybe the laser focus or flash, not sure. That's the only other thing I think it'll be if it isn't software related.. (obviously)
Click to expand...
Click to collapse
Understood. I doubt if it's software but it's still worth a try. Rooting itself won't be the solution, but flashing the 10B TOT might. If the camera doesn't work after flashing the stock 10B TOT, then it won't work no matter what you'll do software-wise (rooting, etc). If you got this replacement through a warranty, I'd act fast as they might have a time limit under which you can re-exchange this faulty replacement without considering it a new claim.
roirraW "edor" ehT said:
Understood. I doubt if it's software but it's still worth a try. Rooting itself won't be the solution, but flashing the 10B TOT might. If the camera doesn't work after flashing the stock 10B TOT, then it won't work no matter what you'll do software-wise (rooting, etc). If you got this replacement through a warranty, I'd act fast as they might have a time limit under which you can re-exchange this faulty replacement without considering it a new claim.
Click to expand...
Click to collapse
Yeah, that's kinda what I gathered. I just figure it'll be my last ditch effort to try before giving up and saving for the new nexus.
premedicated said:
Yeah, that's kinda what I gathered. I just figure it'll be my last ditch effort to try before giving up and saving for the new nexus.
Click to expand...
Click to collapse
Good luck! Let us know how it goes.
Well, didn't work. I tried different camera apps and none of them will work on the rear camera.
At this point I'm not really sure what else to do since I've already replaced the camera. It might be the laser not working and causing the camera to in turn not work...or maybe the flash (?) but regardless, not sure what it is. I guess I'll just abandon it and wait for late October to pick up a new nexus and go back to paying Verizon more $$$... womp womp wooommmmppppp....
Thanks for all your help roirraW "edor" ehT
Sorry to hear that! You're welcome, hope we all find decent solutions when its time for us all to upgrade.
I'm having the exact same issue. Only front camera works, back camera doesn't. I do think it's a hardware issue related to overheating. My phone got hot one day and the camera started acting weird (not focusing correctly, glitchy pictures). Then a few days later it gave me the same error as yours. I flashed a stock ROM to no avail. I even tried safe mode which also didn't work. I'm going to try to mess with the insides next and see if that works.
benthe1 said:
I'm having the exact same issue. Only front camera works, back camera doesn't. I do think it's a hardware issue related to overheating. My phone got hot one day and the camera started acting weird (not focusing correctly, glitchy pictures). Then a few days later it gave me the same error as yours. I flashed a stock ROM to no avail. I even tried safe mode which also didn't work. I'm going to try to mess with the insides next and see if that works.
Click to expand...
Click to collapse
My camera is working again! I ended up not opening up my phone. Instead I flashed the camera mod that is supposed to allow 1080 recording at 60 fps. That ended up soft bricking my phone so I had to re-flash the stock ROM I originally flashed which ended up making the camera working again. I'm not sure if it was the camera mod that set something straight or just re-flashing the stock ROM that fixed it. Either way, I hope that helps someone.
My lg v10 was having same problem i installed evry camera app from playstore and wipe cache of gallery any camera app also .. But nothing helping .my problem is actually flashlight says camera app is running .. And camera app unfortunately stoping..... So here us what i have done to solve this
1.in power menu. Long press shutdown /poweroff to prompt safe mode menu .
2. It will ask .. Press ok

Any Questions!!!! (Ask me) you'll get a response within 24 hours

Ready, set, ask me anything!
I have a couple questions..
1. Is there any kind of ETA? I'm as patient as the next guy, but it's always nice to know! No worries if you don't have one though : )
2. Is there any proof of the K10 root working on the V10?
(not really a question but)
3. I know it's a very long time off, but in October of this year I will no longer be with Verizon and I'm willing to test anything around that time.
supermansbrother said:
I have a couple questions..
1. Is there any kind of ETA? I'm as patient as the next guy, but it's always nice to know! No worries if you don't have one though : )
2. Is there any proof of the K10 root working on the V10?
(not really a question but)
3. I know it's a very long time off, but in October of this year I will no longer be with Verizon and I'm willing to test anything around that time.
Click to expand...
Click to collapse
1. Sadly I have no ETA, right now I have an init and a new sepolicy. I'm able to dirtycow the sepolicy but I can't find any way to get the init across without the phone rebooting before it finishes. I need a way to like freeze the init in a way to make it available for transfer. So there's that and the other guy we are working with is gone right now and idk yet when he'll be back and ready.
2. Well, he is helping me out but he had the same issue with the init sadly. So stuck again
3. I have a question for you.. what version of Android are you on currently?
Currently running a V10 from Verizon, Android version is 6.0.
After recent updates (a few months ago) from Verizon, I noticed my call blocking software was no longer working. I had the software set to block any numbers not in my contacts.
I poked around in the phone app settings and the Android settings, all settings allowing me to block callers from mt phone had been removed.
Verizon's "solution" to be able to block up to 5 numbers free for 90 days (then you have to reblock them) simply does not meet my needs. Paying extra for their service to block numbers is just rude to me. I'd go to another carrier first.
Is there any way to get those settings back on my phone so I can block numbers from my phone again?
artcarney said:
Currently running a V10 from Verizon, Android version is 6.0.
After recent updates (a few months ago) from Verizon, I noticed my call blocking software was no longer working. I had the software set to block any numbers not in my contacts.
I poked around in the phone app settings and the Android settings, all settings allowing me to block callers from mt phone had been removed.
Verizon's "solution" to be able to block up to 5 numbers free for 90 days (then you have to reblock them) simply does not meet my needs. Paying extra for their service to block numbers is just rude to me. I'd go to another carrier first.
Is there any way to get those settings back on my phone so I can block numbers from my phone again?
Click to expand...
Click to collapse
All those settings to block calls from verizon are a verizon thing, once it's changed it's changed. Verizon's contract with us says they technically own the phone and we are just borrowing it. So my first guess would be no you can't get that software back. I could look, depends on what you were using. My suggestion though would check out an app on the play store to see what you get. Once we get root you can probably find a good software for it.
Do you expect roms to be available including nougat roms if/when root is achieved?
snapz54 said:
Do you expect roms to be available including nougat roms if/when root is achieved?
Click to expand...
Click to collapse
Maybe I'll start a project for one but it's a big maybe, I'm going to try to also push out the updates to be flashed over twrp.
artcarney said:
Currently running a V10 from Verizon, Android version is 6.0.
After recent updates (a few months ago) from Verizon, I noticed my call blocking software was no longer working. I had the software set to block any numbers not in my contacts.
I poked around in the phone app settings and the Android settings, all settings allowing me to block callers from mt phone had been removed.
Verizon's "solution" to be able to block up to 5 numbers free for 90 days (then you have to reblock them) simply does not meet my needs. Paying extra for their service to block numbers is just rude to me. I'd go to another carrier first.
Is there any way to get those settings back on my phone so I can block numbers from my phone again?
Click to expand...
Click to collapse
Actually, I've been using contacts+ and dialer+ from the play store on my last several phones and I no longer have to back up my contacts , call log, or texts! And, it has call blocking that does have the block everything not in your contacts. It has made rooting and breaking phones hurt a little less and/or be less of a pain in the @$$. I swear I have nothing to do with them, lol. I'm just a guy who likes to fiddle with this stuff who stumbled on this app purely by trial and error. If I can make one complaint, it's different than other dialers/contacts, and I don't think it's the prettiest app, but once you fiddle with it a while, it gets better. I wish I could skin it though, lol. Sorry for rambling, I just stumbled here and had to comment.
Root for LG V10 VS990 with MM
abine45 said:
Ready, set, ask me anything!
Click to expand...
Click to collapse
I was wondering if you could point me in the right direction?
I need to find a reliable, safe, proven way to root a LG V10 VS990 running MM.
Please, please, please help quickly.
Thank you so much!
~CM
cmccrar said:
I was wondering if you could point me in the right direction?
I need to find a reliable, safe, proven way to root a LG V10 VS990 running MM.
Please, please, please help quickly.
Thank you so much!
~CM
Click to expand...
Click to collapse
Sorry, I personally can't help. Be advised if you root an Android device now, Netflix won't work.
See: https://www.engadget.com/2017/05/14/netflix-no-longer-available-for-rooted-android-phones/
Not worried a/b Netflix, thanks though
artcarney said:
Sorry, I personally can't help. Be advised if you root an Android device now, Netflix won't work.
Not worried a/b Netflix, thanks though!
Click to expand...
Click to collapse
need help here. just bought my V10 refurb unit. they said its H900 at&t unit. its on lollipop with root out of the box so i cannot use any banking app. so i try to diry flash latest H900 firmware via LGUP. phone bootup but i cannot use due to force closed app. so i clean reflash it. now it booting as normal. but i cannot setup any fingerprint as it will force closed. so i came out a solution trying to clear cache and data . phone bootup still same. then suddenly its blank. only black screen with backlit on. so pull out the battery, now phone cannot turn on. only qdloader9008. so its hardbrick. try dismantle mainboard and its turn out im getting verizon vs990 mainboard with at&t firmware in it. now had no idea how to fix it. try those SDCARD using h901 system dumb as i cannot find any vs990 system dumb to work with. no luck, cannot enter download [email protected] fastboot mode. any help will be appreciated.
p/s : now im still not sleeping since yesterday trying to figure it out and my head feel like to exploded.
My parents both have the VS990 and recently their Wi-Fi calling has stopped receiving calls- calls can still be made (outgoing) but they go straight to VM incoming. My Verizon s7e on the same plan works just fine, leading me to rule out Network and Verizon. What is left is LG and Android (since I'm on N and they're still on MM). It seems that it occurred after the recent vzm upgrade from 27a to 28a. Nobody on Reddit responded to my thread, Verizon has been 0 help (they told my parents it was a SIM issue, swapped their SIM, "tested them" without putting the phones on airplane mode and sent them on the way telling them it was fixed..... thanks guys). I can't find any documentation or bug reports of this happening to anyone else- but, I'm not sure how many ppl depend on wireless calling like we do (satellite is our only method of telecom out here- no phone lines run, no dsl, no cell service.. we're in the middle of nowhere). I've tried resetting the Advanced Calling features. I've restarted the phones. I haven't done a factory reset.
A) Anything I've missed?
B) I found an img for 27a on here, is LGUP a feasible means still of downgrading/rolling-back?
Nothing going on
So my v10 wont charge, wont turn on, there's no charging notification light or anything. the only thing that gives me hope is that when I plug it into my laptop, my computer detects it because I can hear the sound. I cant get it into any of the modes, download..recovery..ect. any suggestions?
Hey could you please help me figure out something. I have an LG V10 H901 (purchased from China) its supposedly the T-Mobile version but was manufactured in Korea. Its WIFI and bluetooth weren't working so I tried to update its firmware using LGUP. However, after the update it was hardbricked. I have managed to get to the LG logo using H90021w Unbrick Qfil files. Afterwards I tried to flash stock firmware H90130d_00_0611 using lgup. However, I got a message about partition changes and hardbrick once again. I have also tried KDZ files related to F600L, h90021w and many others. Can you please suggest based on my details:
-Correct QFIL files
-Correct Firmware or KDZ
Phone Details:
IMEI:354017070602111
Model:LGH901BK
Suffix:ATMOOP
Buyer:TMO
Software Verison:H90130D_00
OS Version:N
File Name:H90130d_00_0611.kdz
KDZ File size:1975399272
No Luck
abine45 said:
Ready, set, ask me anything!
Click to expand...
Click to collapse
So my Lgv10. Doesn't show that its charging, doesn't turn on, doesn't do anything at all. It does however connect to the computer in the whole qualcomm hs-usb qdloader9008 mode thing. ive been doing the qfil thing because that seems to be the only thing that detects my phone but nothing is working. are there any other options? oh it says its the lgh900. but the motherboard is the vs990. does that make a difference? I have files for both
Been a while since I've touched a LG device but i'll respond to everyone tonight.
Shiah said:
So my v10 wont charge, wont turn on, there's no charging notification light or anything. the only thing that gives me hope is that when I plug it into my laptop, my computer detects it because I can hear the sound. I cant get it into any of the modes, download..recovery..ect. any suggestions?
Click to expand...
Click to collapse
Uh, check in device manager, see if you are in a qualcomm mode
nabilsp said:
Hey could you please help me figure out something. I have an LG V10 H901 (purchased from China) its supposedly the T-Mobile version but was manufactured in Korea. Its WIFI and bluetooth weren't working so I tried to update its firmware using LGUP. However, after the update it was hardbricked. I have managed to get to the LG logo using H90021w Unbrick Qfil files. Afterwards I tried to flash stock firmware H90130d_00_0611 using lgup. However, I got a message about partition changes and hardbrick once again. I have also tried KDZ files related to F600L, h90021w and many others. Can you please suggest based on my details:
-Correct QFIL files
-Correct Firmware or KDZ
Phone Details:
IMEI:354017070602111
Model:LGH901BK
Suffix:ATMOOP
Buyer:TMO
Software Verison:H90130D_00
OS Version:N
File Name:H90130d_00_0611.kdz
KDZ File size:1975399272
Click to expand...
Click to collapse
In device manager what is your phone coming up as?
thetestis said:
My parents both have the VS990 and recently their Wi-Fi calling has stopped receiving calls- calls can still be made (outgoing) but they go straight to VM incoming. My Verizon s7e on the same plan works just fine, leading me to rule out Network and Verizon. What is left is LG and Android (since I'm on N and they're still on MM). It seems that it occurred after the recent vzm upgrade from 27a to 28a. Nobody on Reddit responded to my thread, Verizon has been 0 help (they told my parents it was a SIM issue, swapped their SIM, "tested them" without putting the phones on airplane mode and sent them on the way telling them it was fixed..... thanks guys). I can't find any documentation or bug reports of this happening to anyone else- but, I'm not sure how many ppl depend on wireless calling like we do (satellite is our only method of telecom out here- no phone lines run, no dsl, no cell service.. we're in the middle of nowhere). I've tried resetting the Advanced Calling features. I've restarted the phones. I haven't done a factory reset.
A) Anything I've missed?
B) I found an img for 27a on here, is LGUP a feasible means still of downgrading/rolling-back?
Click to expand...
Click to collapse
I would update to the latest version. and I would factory data reset. I would also say that wifi calling is brutal and something that I wouldn't use all that much personally. any more questions you can ask

Categories

Resources