VS98024A - OTA manual install + Patched Stock Kernels

Search This thread

jesssiii

Senior Member
Aug 19, 2010
4,942
1,656
Southern CA
Why go all the way back to 11A? You could've kdz'd back to 24A, root with ioroot and take the 26A OTA. Would've saved yourself a lot of time.
You weren't asking me, but personally the 11A tot is set up on my computer and takes 3 minutes tops. KDZ's I never tried and the instructions make it seem like a real pain. So, I'd probably go that tot way myself.

Sent from my VS980 4G using Tapatalk
 

simon_lefisch

Senior Member
Dec 8, 2010
1,459
396
You weren't asking me, but personally the 11A tot is set up on my computer and takes 3 minutes tops. KDZ's I never tried and the instructions make it seem like a real pain. So, I'd probably go that tot way myself.

Sent from my VS980 4G using Tapatalk

Actually, using the new flash tool (2014) is just as fast. Did it twice a few weeks ago. No probs. To each his (or her) own ?
 
  • Like
Reactions: jesssiii

TabletConnect

Senior Member
Aug 8, 2010
292
26
tabletconnect.blogspot.com
I'm on 24A rooted with TRWP. My phone automatically downloaded the OTA but I postponed installing until tonight 11:59pm. I know if I don't make some changes it will bootloop. I believe I can take ota if I have stock recovery. How do I deleted TRWP? Also I froze some apps and used Xposed to modify some things. Will this cause an issue taking the OTA? Any help is greatly appreciated.
 

bouchigo

Senior Member
Jan 17, 2008
1,240
850
Stockton
Nexus 7 (2013)
Google Pixel 6 Pro
I'm on 24A rooted with TRWP. My phone automatically downloaded the OTA but I postponed installing until tonight 11:59pm. I know if I don't make some changes it will bootloop. I believe I can take ota if I have stock recovery. How do I deleted TRWP? Also I froze some apps and used Xposed to modify some things. Will this cause an issue taking the OTA? Any help is greatly appreciated.

I recommend doing the 24A KDZ using the new Flash Tool 2014. First, wipe data, cache, dalvik, cache, and system using twrp. After that, power off your phone and go into download mode. Choose the "Normal Flash" in the tool so you don't erase your "sdcard" data. After the KDZ file is done flashing, you should boot up into the OS and continue from there; I think you may have to download the update again though.
 
Last edited:

mrdunn

Senior Member
Jan 6, 2010
457
155
portland, or
I recommend doing the 24A KDZ using the new Flash Tool 2014. First, wipe data, cache, dalvik, cache, and system using twrp. After that, power off your phone and go into download mode. Choose the "Normal Flash" in the tool so you don't erase your "sdcard" data. After the KDZ file is done flashing, you should boot up into the OS and continue from there; I think you may have to download the update again though.
How do you go to downloader mode if twrp is installed? Is it the same as bootloader?
 

jesssiii

Senior Member
Aug 19, 2010
4,942
1,656
Southern CA
It is frozen but my phone downloaded it anyway. I don't know if it will automatically install tonight as I postponed it when it finished downloading.
No, the updater thingy. If it's really frozen, it shouldn't auto update. You can delete it instead. Also, move the update file itself out of the fota folder in system so it won't install itself, just in case.

Sent from my LG-VS980 using Tapatalk

---------- Post added at 04:32 PM ---------- Previous post was at 04:30 PM ----------

I'm on Liquid ATM, so I don't know what that updater is called, sorry. But it has update in the name and it's a system app, so look in titanium for it and freeze or delete it.

Sent from my LG-VS980 using Tapatalk
 

MosesTheTool

Senior Member
Dec 24, 2011
248
25
www.pelefix.com
For the noobs (like me!), need to clarify:

When the OP said "Rename the file to dlpkgfile and push it to /cache/fota/", he means:
Start ADB window, Type this command:
Code:
Adb push dlpkgfile /cache/fota/

this process will take alot of time, because it's pushing a very large file to the device, and there is no status bar, so just wait patiently for a few minutes until it says it is done.

Then you need to execute the commands the OP said, in "ADB SHELL", so before the commands you need to do:
Code:
Adb shell

Hope i helped :p
 

lotero

Member
Aug 13, 2013
27
2
Hello. "echo" step didn't work. I created manually a command file with "--update_package=/cache/fota/dlpkgfile" inside and run the next step, by my phone didn´t rebooted.

Do you know where could be the problem?

Thanks
 

andresrodolfo

Member
Jan 31, 2015
19
1
The adb commands don't work to update in Lollipop. I hope somebody finds out why the commands work in Kitkat, but not in Lollipop.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 85
    After interrupting the 11A to 12B OTA to see what was happening and decompiling certain framework bits along with the LGFOTA.apk I was able to figure out how to force the 24A OTA KitKat build to install. Thanks to @JackpotClavin for finding the bin file.

    It looks like an official release is near, so if you aren't VERY comfortable with adb, etc. then this isn't for you, and please don't attempt it. As with any procedures of this sort you risk getting your phone in an unusable state and potentially worse. If you are comfortable with this and don't want to wait for the OTA, here's what I did to make it work. Hopefully this will also help others force future OTAs as the procedure should be transferable.


    Manual OTA Install:
    1. Restore to 100% stock VS98012B via one of the available tot/kdz methods, then get root using the latest ioroot from autoprime (or do it manually). Don't install a recovery. Don't modify anything.
    2. Download the bin file from here and verify that the md5 is ebb9750e33574c7738a8256fb01a9e00
    3. Rename the file to dlpkgfile and push it to /cache/fota/
    4. From an adb shell run the following command:
      Code:
      echo "--update_package=/cache/fota/dlpkgfile" > /cache/recovery/command
      ** Note: If the recovery directory does not exist on your phone...create it :)
    5. From adb shell run the following command:
      Code:
      am start -n com.lge.lgfota.permission/com.lge.lgfota.permission.DmcEzUpdateStart
    6. The phone will restart on its own and go through the software update procedure.

    Optional:

    If you want a custom recovery, then you have a few more steps. JackpotClavin has already written up an excellent guide on how to do so HERE. Follow his steps 5-8 (as you've theoretically already followed this guide to get to 24A), and substitute one of the .lok files included in this archive for the file named "boot.emmc.win" in step 7. If you have already gone through that procedure and have a custom recovery, you can simply flash either of the following two zips:

    xdabbeb_vs98024a_kernel_google_gcc

    xdabbeb_vs98024a_kernel_linaro_gcc

    Q: What's the difference between the two?
    A: One is built with the standard 4.6 gcc toolchain (same as stock LG) and the other is built with a linaro 4.7.4 optimized gcc toolchain.

    Note: In order to have a custom recovery you need to be use an older (12b, 4.2.2) aboot/bootloader. At the same time, your laf partition (which is the one responsible for download mode) is now based on the new 24A OTA and won't work with the older aboot. All you need to do to get a working download mode again is dd the laf partition from 12b. You can find it right here. Since the only way you got to this point is by using dd to install an older aboot, I'll assume you can do the same thing for laf.


    Devs: Feel free to use the kernels in your roms. Just give credit in your OP.
    23
    Here the flashable zip file to test, make sure you did a full wipe before flashing:
    http://www.androidfilehost.com/?fid=23329332407582762
    (MD5: 0c0f55f64c5be1a287e2ddec4bcde272)

    Remember to keep a copy of your working ROM so you can flash it if anything wrong happend. This one already included the system, kernel and modules needed for KitKat.

    If you can boot into the system (patched kernel works), you should enter recovery and flash VS980 KitKat Baseband and SuperSU

    If you stuck at boot logo, then flash your previous ROM and wait for a new patch from Savoca. (Then you will need to flash this ROM, and his later patch version)


    Please test it and give us feedback.

    Thanks @xdabbeb, @Savoca and @JackpotClavin for their hard work.
    20
    Well, something very weird happend. We cant flash this system.img directly (for some reason it always make the file over 2.2Gb and all recovery cant read it) like other variants. I'll dump it and repack in folders format so you guys can flash it. Be patient.
    20
    I'd like to aplogize in advance but the OP clearly states....
    This really is for devs and more advanced users, so I apologize, but I'm not going to be able to help people that run into problems. I've been through the procedure twice now so I know it works. I've also attached some of the system images below.

    Call me what you will for this but if the OPs instructions don't work for you then you're not following them exactly as posted. You're not reading. You're not following the instructions EXACTLY. If this doesn't work for you on the first try - you're doing it wrong. I'm not really sure what the confusion regarding "100% stock" is with people. If you can't figure out what "100% stock" means then you probably shouldn't be trying to follow this procedure. If you can't properly rename a file then you probably shouldn't be trying to follow this procedure. If you can't figure out how to get back to 100% stock then you probably shouldn't be trying to follow this procedure. If you're not sure how to backup the files on your sdcard then you probably shouldn't be trying to follow this procedure.

    If this process doesn't work for you on the first, or even second, try then you should probably stop & wait for someone to package up the contents into a flashable zip that you're comfortable with. It's better to wait & do something you're comfortable with than to bork your phone. Once again I apologize but if this doesn't work for you on the first or second try... you're flat out doing it wrong & not following the instructions in the OP & you need to give up before you make things worse for your device.
    20
    Now it's gone, hope you got it.

    Sent from my VS980 4G using Tapatalk

    No worries, I got it