Hope this doesnt sound like a really stupid question, but considering you put the .img files at the end of this do we need them at all? Or just the Bin?
VS98024A - OTA manual install + Patched Stock Kernels
- Thread starter xdabbeb
- Start date
-
- Tags
- development
Hope this doesnt sound like a really stupid question, but considering you put the .img files at the end of this do we need them at all? Or just the Bin?
I sent OptimusRs this thread. Prepare for a G Pro 2 ROM!
Sent from my VS980 4G using Tapatalk
Sent from my VS980 4G using Tapatalk
I'd be happy with a stock rom. Is anyone working on one?
Sent from my VS980 4G using Tapatalk
I can't get it past step one. Says fail. Can't figure out what I'm doing wrong.
VZW LG G2 VS980
Can't you all just zip it and upload it for flashing?
Edited it because it looked assertive lol
Sent from my VS980 4G using Tapatalk
Edited it because it looked assertive lol
Sent from my VS980 4G using Tapatalk
Last edited:
Hmmm...I can't afford to jam up my phone right now, so I suspect I'll be watching this thread for a bit to see how you make out. Glad you're willing to jump in and try this right away. Considering how active you've been with ROMs, flashing (Sourcery on the GNex - beta, etc) - and your track record of success, the fact that you're running into something blocking the install suggests there are some variables that it would be good to know about before attempting this.
BTW: any more detail re: error messages, or is a log file created on your device that might have messages in it?
This please and thank you. I wonder how many are attempting this method that probably shouldn't.
I pm'ed savoca to see if he could get in on the action. If we get a modified kk kernel to work with older boot image we can have our cake and eat it too
Sent from my VS980 4G using XDA Premium 4 mobile app
Thanks @jonstrong, I'm retarded today. Didn't bother to actually READ the error log, lol. I had forgotten I changed the sound file in system/etc, so I replaced it with the original, changed perm, rebooted. All is working now. I'm at 31% in step two and counting...:fingers-crossed:
---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------
One thing I had to do that's not in the OP was create a folder in /cache called "recovery" because it didn't work otherwise. I used root explorer.
I'm now at 39% on step 2.
Sure. Give me a few and I'll get it. I take it the released kernel source is enough?
My guess is some system file mod that you've forgotten. Even a build.prop edit could cause problems. It's just like any other OTA in that sense
Last edited:
I couldn't get the file to push, I just added the file into the download section and then used Root Explorer to place it in the right cache location. I then followed the command to force update and it worked 100%. I hope that helps.
savoca
Inactive Recognized Developer
Well, it worked, I'm on 4.4.2 but I lost root ?
Would I have to go back to JB to get root back?
VZW LG G2 VS980
Would I have to go back to JB to get root back?
VZW LG G2 VS980
So I am on step four and its saying the system cannot find the path specified.. Any ideas?
---------- Post added at 02:15 PM ---------- Previous post was at 02:10 PM ----------
Nevermind, had to run ADB shell. I am a noob. Updating software step 1.
---------- Post added at 02:15 PM ---------- Previous post was at 02:10 PM ----------
Nevermind, had to run ADB shell. I am a noob. Updating software step 1.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
85After 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:
- 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.
- Download the bin file from here and verify that the md5 is ebb9750e33574c7738a8256fb01a9e00
- Rename the file to dlpkgfile and push it to /cache/fota/
- From an adb shell run the following command:
** Note: If the recovery directory does not exist on your phone...create itCode:echo "--update_package=/cache/fota/dlpkgfile" > /cache/recovery/command
- From adb shell run the following command:
Code:am start -n com.lge.lgfota.permission/com.lge.lgfota.permission.DmcEzUpdateStart - 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.23Here 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.20I'd like to aplogize in advance but the OP clearly states....
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
