VS98024A - OTA manual install + Patched Stock Kernels

Search This thread
By:
Advanced…
jonstrong

jonstrong

Senior Member
Jan 20, 2012
1,790
719
www.jonathanrstrong.com
wilkster said:
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.
Click to expand...
Click to collapse
I think we're onto something! I used your file, and it passed. Now the Log file shows "libcameraservice.so" as the problem. Must be next in the validation list. I hate to ask, as I suspect there will be more after this. But if you could post your copy of that one, I think I'll be one step closer. Thx in advance!
 
W

wilkster

Senior Member
Jul 30, 2011
306
129
jonstrong said:
I think we're onto something! I used your file, and it passed. Now the Log file shows "libcameraservice.so" as the problem. Must be next in the validation list. I hate to ask, as I suspect there will be more after this. But if you could post your copy of that one, I think I'll be one step closer. Thx in advance!
Click to expand...
Click to collapse
Attached are three libcamera*.so files.
 

Attachments

  • camera.zip
    246 KB · Views: 5
jonstrong

jonstrong

Senior Member
Jan 20, 2012
1,790
719
www.jonathanrstrong.com
wilkster said:
Attached are three libcamera*.so files.
Click to expand...
Click to collapse
Thanks again! This is still moving forward. Wish I had a list of all files in advance that might need replacing instead of discovering them piecemeal. The libcamera*.* files all passed. Now it's complaining about libmedia.so.

Without knowing the whole list I can't say if it's worth going down this path or if I should bite the bullet and revert to stock. If you don't mind, I'll keep trying these replacement files to see if I can get past the ones the update doesn't like (that libmedia.so file next).

On a side note: now that I have partially replaced camera files, the camera app no longer functions. Hoping that's resolved too after I've gotten all the needed files replaced.

Thx again...and just let me know if this is too much of a bother.
 
HueyT

HueyT

Senior Member
Apr 3, 2014
4,814
2,183
New Albany, IN
OnePlus 7T
jonstrong said:
Thanks again! This is still moving forward. Wish I had a list of all files in advance that might need replacing instead of discovering them piecemeal. The libcamera*.* files all passed. Now it's complaining about libmedia.so.

Without knowing the whole list I can't say if it's worth going down this path or if I should bite the bullet and revert to stock. If you don't mind, I'll keep trying these replacement files to see if I can get past the ones the update doesn't like (that libmedia.so file next).

On a side note: now that I have partially replaced camera files, the camera app no longer functions. Hoping that's resolved too after I've gotten all the needed files replaced.

Thx again...and just let me know if this is too much of a bother.
Click to expand...
Click to collapse

MicroMod has 26A, debloated, rooted, flashable in TWRP, stock rom out now. Even KDZ back to 24A may be easier than trying to reinvent the wheel?
 
T

TheUnladenSwallow

Senior Member
Aug 3, 2013
341
147
Hey guys, I'm going to tell you how to do this with 0 errors. 1. Put all your photos/app data/anything from your phone onto your desktop or wherever you want to back it up. You're gonna lose everything. 2. Kdz flash to 24a 3. Ioroot on 24a (you MUST do this on 24a, from 24a it will ota you straight to 26a, no 25x in-between) 4. Take the update to 26a. You will now have preserved root and be on 26a. Note supersu may go away (or ioroot doesn't install it anymore, I'm not sure), just install it on the play store and now you have fully rooted 26a. 5. Once you have supersu use autorec. 6. Flash the thermally governed twrp 2.8.0.1. here http://forum.xda-developers.com/showpost.php?p=55278189&postcount=2 And you're done! I have confirmed aosp ROM s work, I'm on 777's PA.

Edit: Also micromod's ROM doesn't use the 26a kernel cus it's not booting with that one for some reason. This is the only way to get full 26a.
 
J

jkjambo

Senior Member
Mar 26, 2011
563
34
what problems you have guys?


i had 24A rooted and following instruction updated to 25b , then 26a without any problem , still have root and everything and yes knock on works also

just don't forget to give dlpkgfile file permissions rwx rwx rwx
 
W

wilkster

Senior Member
Jul 30, 2011
306
129
jonstrong said:
Thanks again! This is still moving forward. Wish I had a list of all files in advance that might need replacing instead of discovering them piecemeal. The libcamera*.* files all passed. Now it's complaining about libmedia.so.

Without knowing the whole list I can't say if it's worth going down this path or if I should bite the bullet and revert to stock. If you don't mind, I'll keep trying these replacement files to see if I can get past the ones the update doesn't like (that libmedia.so file next).

On a side note: now that I have partially replaced camera files, the camera app no longer functions. Hoping that's resolved too after I've gotten all the needed files replaced.

Thx again...and just let me know if this is too much of a bother.
Click to expand...
Click to collapse

Bummer. I fear the list of modified files may be large then. Take a look at the binary files from the URL below. I suspect you may have flashed these at some point. There are dozens of changed files in the camera mod flash and I am not sure how to extract all of those files easily fro stock 24a. Maybe someone has a way to extract them from a kdz or tot file.

http://forum.xda-developers.com/showthread.php?p=54549364


Sent from my Transformer TF101 using Tapatalk
 
HueyT

HueyT

Senior Member
Apr 3, 2014
4,814
2,183
New Albany, IN
OnePlus 7T
jkjambo said:
what problems you have guys?


i had 24A rooted and following instruction updated to 25b , then 26a without any problem , still have root and everything and yes knock on works also

just don't forget to give dlpkgfile file permissions rwx rwx rwx
Click to expand...
Click to collapse

Oh, mostly my own stupidity of taking OTA with TWRP 2.8.0.1 which gave me TWRP bootloop requiring JackpotClavin to the rescue with 2 "dd" commands in TWRP terminal emulator to fix. Otherwise no real problems.
 
J

jkjambo

Senior Member
Mar 26, 2011
563
34
HueyT said:
Oh, mostly my own stupidity of taking OTA with TWRP 2.8.0.1 which gave me TWRP bootloop requiring JackpotClavin to the rescue with 2 "dd" commands in TWRP terminal emulator to fix. Otherwise no real problems.
Click to expand...
Click to collapse

yeah, you MUST HAVE stock recovery to get ota . (offcourse if you don't know that working dd commands)

i had twrp also , but first i installed 24a via kdz method, even i already was on 24a (that's because of recovery)
 
HueyT

HueyT

Senior Member
Apr 3, 2014
4,814
2,183
New Albany, IN
OnePlus 7T
jkjambo said:
yeah, you MUST HAVE stock recovery to get ota . (offcourse if you don't know that working dd commands)

i had twrp also , but first i installed 24a via kdz method, even i already was on 24a (that's because of recovery)
Click to expand...
Click to collapse

I just got a 24a bootstack made by CloudyFA and Bender007 (thanks to the generosity and kindness of Bender007) that I am about to try to revert to stock recovery from rooted, TWRP-recovery 24A that I nandroided, so I may take the 26A OTA. I'll share the file once I know it works :D :good: (too lazy to KDZ as I've KDZ a lot lately ;) )
 
  • Like
Reactions: jesssiii
jonstrong

jonstrong

Senior Member
Jan 20, 2012
1,790
719
www.jonathanrstrong.com
wilkster said:
Bummer. I fear the list of modified files may be large then. Take a look at the binary files from the URL below. I suspect you may have flashed these at some point. There are dozens of changed files in the camera mod flash and I am not sure how to extract all of those files easily fro stock 24a. Maybe someone has a way to extract them from a kdz or tot file.

http://forum.xda-developers.com/showthread.php?p=54549364
Click to expand...
Click to collapse

ah well... this really is sort of unrealistic I guess. At this point, I'm getting a "can't connect to camera" error when I try to open any of my camera apps. I can try to roll back the file replacements I did over the last 24 hours, to just go ahead and revert to stock and start fresh. Might be easiest at this point...
 
T

TheUnladenSwallow

Senior Member
Aug 3, 2013
341
147
jonstrong said:
ah well... this really is sort of unrealistic I guess. At this point, I'm getting a "can't connect to camera" error when I try to open any of my camera apps. I can try to roll back the file replacements I did over the last 24 hours, to just go ahead and revert to stock and start fresh. Might be easiest at this point...
Click to expand...
Click to collapse

Backup your picks and do a clean kdz flash. That'll fix everything related to do with various customizations and edits over time. If other than pictures you also need your app data titanium backup the apps (just user apps, titanium backup of system apps will just bring back a bunch of errors) and you're good to go.
 
P

PJroast

Member
Dec 21, 2013
29
0
I was only able to flash to 11A, couldn't find 12b from the guide I used.

Will 11A still work in flashing to 24a?
 
HueyT

HueyT

Senior Member
Apr 3, 2014
4,814
2,183
New Albany, IN
OnePlus 7T
PJroast said:
I was only able to flash to 11A, couldn't find 12b from the guide I used.

Will 11A still work in flashing to 24a?
Click to expand...
Click to collapse

Use 24A KDZ, root with IOROOT25, update to 26A through OTA which will retain root, and then AutoRec to get TWRP 2.7.0.0 custom recovery (then you can flash DrGravy's 2.8.0.1, thermal controlled, custom recovery which is the latest).

http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW678695432109876543213/VS98024A_11.kdz

You could do OTA update from 11A to 26A but then you'll lose ability to root using IOROOT25
 
jesssiii

jesssiii

Senior Member
Aug 19, 2010
4,942
1,656
Southern CA
You couldn't root with IOROOT 25 while on 11A, then use SuperSU's retain root with OTA setting before OTA to 26A?

Sent from my VS980 4G using Tapatalk
 
simon_lefisch

simon_lefisch

Senior Member
Dec 8, 2010
1,459
396
not balanced said:
I tot'ed back to 11A, rooted with IORoot, took the 12B OTA, the 24A OTA, and finally the 26A OTA.
I then used MicroMods KitKat Freedom24A to install TWRP and then loaded DR. Gravy's thermally protected TWRP 2.8.0.1
Click to expand...
Click to collapse

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 must log in or register to reply here.

Similar threads

xdabbeb
XDABBEB's VS980 v3.1.2
Replies
6K
Views
869K
G
gonna.act.right
O
[ROM] Malladus 2.0.3 - 6/28/2014 [Android L 5/4.4.2] [stock based]
Replies
8K
Views
846K
T
Tom Barrister
JackpotClavin
CM12 based on 5.0.2 (Lollipop) OTA
Replies
4K
Views
412K
Zimeron
Zimeron
D
[ROM][DEV] CM 11.0 Nightlies for VZW VS980
Replies
3K
Views
330K
gorm
gorm
xdabbeb
  • Sticky
VS980 Resources - Bootstacks/Modems/Manual OTA/etc
Replies
187
Views
88K
darkharbinger81
darkharbinger81

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 85
    xdabbeb
    xdabbeb
    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.
    View
    23
    Cloudyfa
    Cloudyfa
    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.
    View
    20
    Cloudyfa
    Cloudyfa
    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.
    View
    20
    EvilDobe
    EvilDobe
    I'd like to aplogize in advance but the OP clearly states....
    xdabbeb said:
    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.
    Click to expand...
    Click to collapse

    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.
    View
    20
    xdabbeb
    xdabbeb
    55Pegasus said:
    Now it's gone, hope you got it.

    Sent from my VS980 4G using Tapatalk
    Click to expand...
    Click to collapse

    No worries, I got it
    View

New posts