Home

Share this Story

LG G2 on Verizon Receiving Tiny Update to Build VS98011A

LG G2 update

The LG G2 on Verizon began receiving an update this morning to build VS98011A. No changelog is in sight, but with its minuscule size, we wouldn’t be surprised if it was a security patch for the current root exploit or bootloader bypass. Then again, that would be a record turn-around for Verizon’s software department. If you update, do so knowing that you could be patching up work previously performed by developers.

If you’d like to update right away, head into Settings>About phone>Software update.

lg g2 update

Cheers David, Jerrod, Becky, Monroe, and Kodi!

  • Buenos

    FYI form Verizon support:

    Chrissy: Issues Resolved

    Chrissy: Device may not ring on incoming calls. – FIXED

    Chrissy: App tray icon fonts are too small. – FIXED

    Chrissy: Read out of TN on incoming call is incorrect. – FIXED

    Chrissy: Can’t get out of Google setup with 2 step sign-in account. – FIXED

  • emplox

    This does NOT break root. You can’t update if you already have TWRP installed, else you will bootloop. You need to flash back to stock recovery, accept the update, and the flash back TWRP. This does not block anything related to root or recovery.

  • Droid 1967

    INFO:– 1) the update on verizon has no effect on root or loki. it is not a security patch that breaks this at least.
    2) if you installed the update with twrp installed and you are bootlooped.
    unplug the usb cable and hold down the power button for 2 minutes or so.
    3) never install a ota with custom recovery on an LG phone apparently it sits in memory and completes rathr than failing like most other phone manufacturers updates.

    This is from the guys that are doing all this great work.

  • startedfire

    This KILLED my battery life. Watch it take 2 months for the next update, too.

    • skubadoo

      Hows is your battery doing after a few hours? I’m debating on whether I should install the OTA then root, or just root it and not do the OTA

  • Mike Hilal

    If one were to buy this phone, it should be rommed and onto an AOSP rom immediately following the first boot.

    • BobButtons

      While I definitely get the appeal, I may be going for a custom version of the stock ROM. There’s some added functionality that wouldn’t be carried over that I’d like to hold onto.

      • flosserelli

        Scott Rosler has already hinted at CleanRom for LG G2

      • Mike Hilal

        Like? I’m not trying to be an ass…im genuinely curious. The camera .apk could be ported over…other than that, what’s there to keep that would enhance the experience?

        • BobButtons

          KnockOn. I know you can use an app to ‘knock off’ but would be interested to see someone incorporate knock on in a different ROM. With the buttons being on the back, it’s a great feature to have. Also, I really like the built in video app. It’s similar to MX or BS but when you seek it starts playing a miniature version of the video at that spot. Rather nifty. I also like the fading of the popped out video so you can see/work through it.

          • Mike Hilal

            Thank you for the explanation. I could live without most of that, but the knock-on feature would be something i’d want along with the camera.

      • KleenDroid

        I agree. My S4 is rooted and Loki’d but I run a version of the stock rom.

        But it’s nice to install the Google version once and awhile.

  • Andy Stetson

    Does not break root OR the exploit used to install TWRP. Verified by multiple people on XDA.

    http://forum.xda-developers.com/showthread.php?t=2450772

    Checked the script for the update, looks like some audio fixes, thermal engine configs and updates to Roboto.

    • http://techonblogger.ward.pro/ Stynkfysh

      Hopefully awesome! I was having calls cutting in and out that did not appear to be signal related.

  • IBT

    Would any rooted vzw user who’s accepted this update fire up root explorer and provide some info please? Goto /system/build.prop then long press and view as text. At line starting ro.build.fingerprint please advise on the 10 digit number directly before “user release keys” toward the end of the string. Thanks.

    • http://techonblogger.ward.pro/ Stynkfysh

      1378346052 – what does that tell you?

      • IBT

        Once we know that number we can edit the build.prop to get rid of the update nag.

    • kevin

      Not sure if this will help but my Verizon LG G2 has just been rooted and I have not accepted the OTA update yet, here is the 10 digit # in my scenario:

      1376449988

      If there was a way to stop the OTA update from appearing for a VZW LG G2(rooted, but haven’t implemented the OTA update), that would be awesome

  • Swoops212

    Just a baseband change?

  • Daniel Flores

    Oh well…no need to rush to go get it now…didn’t think Verizon would be that fast. I’d like confirmation that if you hadn’t rooted or installed TWRP, and you received the update, can you still root and flash TWRP. I’m gonna head to XDA and see what’s being said.

    • Daniel Flores

      Ok…FYI…you will not lose Root if you update. But, if you have TWRP installed, you will get stuck in a bootloop. I’ve read that you can flash stock recovery, apply update still keeping Root, then flash TWRP back…But do not flash if you have TWRP installed.

  • lars 46

    this minor update does not help me at all with the software issues i have….no fm radio, no capture plus, no stock browser (for qslide application) and no air conditioner feature for remote. :( ( these were all featured on lg’s launch of the g2…for every other carrier…)

  • RaptorOO7

    Just as I read the story, I immediately jumped to security patch without needing to read any further. FU Verizon, FU.

  • RepsolRider

    Damm you Verizon!! Can someone who took the update please verify if they still have customer recorvery.

    • KleenDroid

      Nobody that ever wanted to keep their custom recovery would take an ota update.

      But then again there were bunches of them on the S4 that did the same thing never to get it back again. And no the bootstrap effort just coming isnt the same.

      • RepsolRider

        Agree 100%. If you have a custom recovery and accept an OTA update you deserve what you are left with.
        Can’t get to a store till later tonight or maybe Friday to look and make my final decision on this phone. If this OTA locks it up tight not sure what I’m headed to next

        • KleenDroid

          Just dont let the salesperson activate it for you. Tell them you want to sign in google yourself. Google restores everything anyway.

          Then don’t accept the ota and go home and root and install Loki’d recovery and you will be good.

          Just don’t let them activate your phone.

        • Joe Gugelman

          To follow up what KleenDroid said, be FIRM with them if they try to act like they have to activate it. They do not, and they are lying to you. Once you let them know that you don’t want it activated, if they balk, tell them that if they hand you an activated phone, you’ll be handing it back to them and they won’t be making a sale. Get a manager involved if they still don’t relent.

          Had this issue when I bought my Gnex. I didn’t want them to do ANYTHING to it. I wanted it as if I ordered it online. Wanted to unbox it myself and everything. Had read enough to know this was possible, but really had to be forceful (not dickish, just firm) with them until they finally relented…

  • KleenDroid

    Don’t ever take an ota update if any of this is important to you.

    EVER

    We have been over this a thousand times people. Custom recovery is what you need to keep and will never get back again.

  • Skittlez

    can anyone tell if this breaks TWRP too?

    • BobButtons

      Multiple people on XDA are saying installing this update after having TWRP installs puts the phone into a loop only booting into TWRP.

      • KleenDroid

        Are people so dumb to want an ota update after going through the effort to get a custom recovery?

        Guess they didnt really want it. Or know what it was for.

      • Skittlez

        yea, but thats only if you already had TWRP installed, wich is a given. i did read somewhere that it doesn’t affect root or the ability to install TWRP

    • KleenDroid

      Dont ever take an update.

      if you do you will be very sorry.

      • Skittlez

        Apparently, this update doesn’t mess with anything.

        • KleenDroid

          Good. But don’t take chances because there is one coming that will.

          But I’m happy that people have more time.

          It didnt take too long for them to mess up the S4.

          • Skittlez

            yea, i wouldn’t install it until i knew it didn’t mess anything up

  • MacNificent

    Does volume+ help the low speaker volume at all?
    If not. what does besides rooting?

  • ITGuy11

    Funny how they can push out this update a week after the phone is released, but still hasn’t “certified” the LTE Nexus 7 since August…

    • Razma

      have they even updated the galaxy nexus to 4.3 yet? Im on Shiny Rom so i havent bothered to look into it. But funny how they cant seem to get a nexus updated with this speed

      • ToddAwesome

        Nope.

      • Kyle Miller

        They never will. They let that phone die and moved on. I did the exact same. I’m surprised you are still using it knowing that its not as fast nor battery efficient as it once was.

      • Jeff Sabin

        I am running my Vzw GNex on the latest 4.3 so up yours Verizon. With a different kernel this phone is as viable as it was when I first got it.

  • imHOWIE

    I was rooted and performed the update after installing and performing the necessary actions on OTA root keeper. I don’t know what the update did, but I was able to get root back no problem.

    • KleenDroid

      Never take an ota update. Root doesn’t matter. … check to see if you still have a custom recovery. If not you got screwed.

    • http://techonblogger.ward.pro/ Stynkfysh

      I took the update and did nothing to protect root and I still have root access.

    • Eric R.

      If I had this phone I’d be rooted and on a custom Rom. LGs status bar makes my eyes bleed.

      • Derrick Jefferson

        There are no custom roms for the G2 yet… we are all patiently waiting.

  • Gasaraki

    I still have my root after the update.

    • Brian Wolfman

      can you still get into TWRP? I doubt verizon has a 24hr turn around on closing root exploits.

    • KleenDroid

      Why would you take the update

      • http://techonblogger.ward.pro/ Stynkfysh

        I do know about anyone else, but I have been experiencing some sound/microphone cutting in and out with callers. I was going to exchange the phone, but will see if this update fixes it.

        • http://techonblogger.ward.pro/ Stynkfysh

          I got a down-vote for that???

          • lookatmyfunnyusername

            now you have two ONE FROM ME AHAHAHA

          • lookatmyfunnyusername

            no malice though just thought it would be funny to me

      • Gasaraki

        Mainly because of potential bug fixes etc.

  • http://twitter.com/geoff5093 Geoff Johnson

    Hopefully freezing the service “Software update MUC 6.4.1.2_B02-LG” will prevent it if you’re rooted.

    • skubadoo

      Does it stop the update prompt?

      • BobButtons

        I have it frozen and have yet to be prompted for an update, granted it might just not have gotten to me yet.

        • skubadoo

          Thanks for the heads up! I’ll be doing the same!

  • giri0n

    Glad I bought mine last night when I saw that root/TWRP were available. Turned my mobile data off til I can root/flash recovery tonight.

    • Greyhame

      I heard TWRP isn’t quite ready for prime time. Use caution.

      • KleenDroid

        2.5.0.2 version of twrp is golden. The newer ones have issues.

        Ive been through all this on my S4 over the past few months with Loki.

        Install it to get Loki to protect yourself. You can always install the 2.0.5.2 version later.

    • http://twitter.com/geoff5093 Geoff Johnson

      If you use it, don’t make a backup as that seems to be causing people to have to factory reset. Although the latest version is that ADB in TWRP now works.

    • Bigwavedave25

      Herd the same, a friend entered into boot loops after attempting to put TWRP on his G2 this morning. (may have it fixed by now)

      • giri0n

        what I read on XDA was that using the hardware buttons to access TWRP was causing the bootloop issue. There is a new TWRP VZW.img file with adb baked in, but reports are, if you use a softkey reboot into recovery, things are working just fine. Also – the Flashify solution was nixed, I presumed because it didn’t push the Loki thru first, but that’s pure speculation on my part.

      • KleenDroid

        Get version 2.0.5.2.

        On my Loki’d S4 it is the only one that doesn’t have issues.

        In the S4 rom section on xda there is an aroma recovery installer that makes it easy to install it. Just don’t install any of the Clockwork recoveries in it because they are not Loki’d.

        I could get you a link.

        None of twrp’s last 3 updates were even close to being as solid as 2.0.5.2

        trust me I’ve been through all this on my Loki’d S4

  • Ryan

    It really is a trap. The update forces users to have a verizon booting animation now after the LG screen making the device longer to boot up. There goes the awesome boot up time for the G2. Eff Verizon.

    • http://twitter.com/geoff5093 Geoff Johnson

      There has always been a Verizon boot animation on their G2, I bought it on release day and it had it.

      • Ryan

        I never had it, and I also bought it on release date? I don’t remember it anyways… hmmmmm

    • imHOWIE

      As Geoff said, that has always been there. I also got it on release day. The boot time is still pretty fast in spite of it, but I agree that it would be nice if it wasn’t there.

    • Raj Bhatt

      Had it on mine since launch day as well. The most annoying thing about it though is the 2002 era Verizon startup sound.

      • Jared Keplinger

        I thought the same thing. Its quite antiquated Lolol.

    • flosserelli

      Root G2, then add this to the build.prop:
      debug.sf.nobootanimation=1

      • Ryan

        Thanks for the tip.

  • Uncle Ruckus

    Don’t update!