VS98024A - OTA manual install + Patched Stock Kernels

Search This thread

MicroMod777

Recognized Contributor
Has anyone tried making a flashable zip
Not yet. If i get time I'll try.
Sweet. I'll use that.
@MicroMod777

Glad to see you back in the G2 mix, I thought you had gotten rid of yours?

Sent from my Vs980 running Deviant Xone
Not yet. Using my G2 with Cricket Wireless. Its 1/4 the price and I get decent coverage.
 

MicroMod777

Recognized Contributor
I routed on 24 then took both the 25B and 26A OTA and maintained root.
How u get 24 installed?

---------- Post added at 09:08 PM ---------- Previous post was at 08:22 PM ----------

Got it working. Had to set write permissions to the recovery folder, command, and dlpkgfile! :)
 
Last edited:

HueyT

Senior Member
Apr 3, 2014
4,814
2,183
New Albany, IN
OnePlus 7T
I routed on 24 then took both the 25B and 26A OTA and maintained root.

So you started with nonrooted 24A, rooted it with IOROOT25, then took the OTA to 26A, and it kept root? Huh, very interesting !!!

Maybe where I went wrong was that I was already rooted on Liquid AOSP with TWRP 2.8.0.1, nandroided back 25B stock rooted with TWRP 2.8.0.1, and then took the 26A OTA which then made me stuck in TWRP 2.8.0.1. I had to be rescued by JackpotClavin when he pointed me towards 2 phone-saving dd commands that got me out of the TWRP bootloop and allowed me to KDZ back to nonroot 24A.

So we basically have 3 choices now:

1) Wait for XDABBEB to make 26A bootstack (I know he can't resists :D)
2) KDZ to 24A nonroot, IOROOTED, take the OTA to 26A which should keep root. Then AutoRec to get TWRP 2.7.0.0 after on 26A rooted?
3) Be happy with 25B as 26A is minor update

I think I'll wait for choice 1 as I thought I lost my 2 day old, refurbed G2 (warrantied after the black lines from PA 4.6 beta2) :D

I also think the key is NOT to take any OTA once you've AutoRec to TWRP recovery as it can cause TWRP bootloop. Root will let you OTA safely but not TWRP as it interupt stock recovery with TWRP recovery.
 
Last edited:

Lawlrus

Senior Member
Nov 20, 2013
10,687
6,599
Well that would explain it, you can't take an ota with a custom recovery.

Sent from my Vs980 running Deviant Xone
 
  • Like
Reactions: kbuck13

jonstrong

Senior Member
Jan 20, 2012
1,790
719
www.jonathanrstrong.com
Just for clarification, if I take the latest ota, ioroot25 will still root it? That would be awesome!

I'm still on the 24A from the front of this thread, and guessing I must have modified something that's causing the update to cough up the 0X1111004 error.

Phone is rooted, I uninstalled xposed framework, unfroze all the Verizon apps (ugh) -- except I believe I actually uninstalled one of them at some point (silly me - should have saved notes somewhere, or just frozen it). I uninstalled busybox -- no idea if that matters, but can always put it back. Only other change I can think of is the xdabbeb's 3.0 camera (never installed updates since then). I ran the apk again and ran a "restore" to get back the stock camera -- no errors, and hopefully I didn't overwrite my original backup with a copy of the modded files (how can I tell?) -- I'm guessing this may be causing the error though:

If I go into system\cache\fota\log I can see a file called, "FSUA_LOG_000.txt". Near the bottom of this (huge) file, I see:

FOTASF_Open/system/lib/hw/camera.msm8974.so, handle : 7
FOTA_GetFileSize : 7
[LGFOTA_GetFileSize : /system/lib/hw/camera.msm8974.so, 1913672

LGFOTA_CloseFile : /system/lib/hw/camera.msm8974.so

FOTAFS_Close 7

UpdateAPi_Update Restult - 1111004

There's more below this, but my interpretation of this is that the install checked the file size on this camera file, didn't like it, set the error return code to 1111004 and proceeded to exit the installation. This leads me to believe that this file is the culprit.

Can anyone share any intel on this? Also - if this is the issue, and anyone can share copies of the correct file(s) to restore the camera back to stock, that would be great. BTW: I'm looking at the camera file on the phone right now. The size is 1913672 bytes. The checksum info is:

File: System (Root)/system/lib/hw/camera.msm8974.so
MD5: d2:f8:9c:29:93:e7:c5:f4:49:4b:3c:79:7c:d4:cb:e5
SHA1: d6:ff:0f:76:30:cc:5a:e7:36:65:a6:3e:8b:75:b9:37:da:08:2f:fe​

thanks!
 

wilkster

Senior Member
Jul 30, 2011
306
129
I'm still on the 24A from the front of this thread, and guessing I must have modified something that's causing the update to cough up the 0X1111004 error.

Phone is rooted, I uninstalled xposed framework, unfroze all the Verizon apps (ugh) -- except I believe I actually uninstalled one of them at some point (silly me - should have saved notes somewhere, or just frozen it). I uninstalled busybox -- no idea if that matters, but can always put it back. Only other change I can think of is the xdabbeb's 3.0 camera (never installed updates since then). I ran the apk again and ran a "restore" to get back the stock camera -- no errors, and hopefully I didn't overwrite my original backup with a copy of the modded files (how can I tell?) -- I'm guessing this may be causing the error though:

If I go into system\cache\fota\log I can see a file called, "FSUA_LOG_000.txt". Near the bottom of this (huge) file, I see:

FOTASF_Open/system/lib/hw/camera.msm8974.so, handle : 7
FOTA_GetFileSize : 7
[LGFOTA_GetFileSize : /system/lib/hw/camera.msm8974.so, 1913672

LGFOTA_CloseFile : /system/lib/hw/camera.msm8974.so

FOTAFS_Close 7

UpdateAPi_Update Restult - 1111004

There's more below this, but my interpretation of this is that the install checked the file size on this camera file, didn't like it, set the error return code to 1111004 and proceeded to exit the installation. This leads me to believe that this file is the culprit.

Can anyone share any intel on this? Also - if this is the issue, and anyone can share copies of the correct file(s) to restore the camera back to stock, that would be great. BTW: I'm looking at the camera file on the phone right now. The size is 1913672 bytes. The checksum info is:

File: System (Root)/system/lib/hw/camera.msm8974.so
MD5: d2:f8:9c:29:93:e7:c5:f4:49:4b:3c:79:7c:d4:cb:e5
SHA1: d6:ff:0f:76:30:cc:5a:e7:36:65:a6:3e:8b:75:b9:37:da:08:2f:fe​

thanks!
Mine is stock camera on 24A and here is what I get for that library.
File: camera.msm8974.so
CRC-32: a699bf79
MD4: 2ef5d1e525285e9892eb1b4599a933e7
MD5: e1fe474415b101fc6944dc6d63722755
SHA-1: 979ff9be2197d5573af3a5eae70b0ee64a381a37

Zipped file for upload.
 

Attachments

  • camera.msm8974.zip
    877.3 KB · Views: 10

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