[VK810.4G] [altev] [ViKtory810ROM] official 36B 5.0.2 & 24A 4.4.2 - updated 8/30/2016 - G Pad 8.3 Android Development

[VK810.4G] [altev] [ViKtory810ROM] official 36B 5.0.2 & 24A 4.4.2 - updated 8/30/2016
First, the thanks:
@AndroidFileHost for the Android File Host website and especially their changes allowing for the reorganization of already uploaded files.
@KyPbP for letting us know it's availability and giving the link to download the VK810 35A_08 KDZ.
@hsbadr for giving me permission to kang his Verizon G3 VS985 JasmineROM 7.0 update script for this use.
@rant for giving a link to the official Verizon PDF detailing this release.
@Chainfire for SuperSU!
@Hnk1 for continued support, advise and ideas, and for experimenting to find out how to root 35A_08 without downgrading. His two updated guides:[VK810][Altev][Guides][Information] Root Recovery Repair [4.4.2][5.02]
[VK810][ROOT][Lollipop][5.02] No downgrade required​Debloat scripts that you can flash in TWRP or CWM (ClockworkMod Recovery) after flashing the ROM and SuperSU.zip are located in the second post.
Donator's Thanks:
@middle_road
@k3ttle
@JBurch/cry
@habatchaNow
@b52apl
@Protonus
@Carolinaherps
@thvoicwethin
@random.mannix
@raghublr
 @megadrive007
Thank you!!!
Just a fair warning, not trying to sound like a you know what, but no Xposed-related comments in this thread. If anyone wishes to post a new thread in General for what Xposed experiences they have under Lollipop, that would be a good idea.
Disclaimer: The usual. I am not responsible for what you do with this nor what happens when you do whatever you do with it.
Instructions to flash:
0. If you haven't previously updated TWRP to the latest version (v2.8.7.0 still as of January 3rd, 2016), do so by:
0A. Download TWRP v2.8.7.0 from http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-7-0-t3150812
Credit and thanks @AndroidUser00110001 !
0B. (in TWRP v2.7.0.1) choosing "Install", navigating to where you downloaded the TWRP v2.8.7.0 zip (probably in internal storage in the Download folder), and choosing to flash the zip.​
1. Download my ROM from my section on Android File Host at https://www.androidfilehost.com/?w=files&flid=32160. I use ADM "Advanced Download Manager" from the Play Store at https://play.google.com/store/apps/details?id=com.dv.adm&hl=en, especially for downloading larger files like ROMs.
2. Check the MD5 Hash of the ROM zip:
2A. Copy (to the clipboard) the MD5 hash that I have in the filename of the ROM zip you downloaded in step 1 above.
2B. Install @scary alien 's "AFV File Verifier for Android" from the Play Store at https://play.google.com/store/apps/details?id=sa.afvx&hl=en.
2C. Run the AFV app.
2D. Choose "Input checksum for comparison".
2E. Paste the MD5 hash previously copied to the clipboard in step 2A above.
2F. Choose "Select File".
2G. Navigate to where you have the ROM zip.
2H. Long-press on the ROM zip and choose "Calc MD5 Checksum".
2I. When it's done calculating the MD5 hash of the ROM zip, it'll automatically compare it to the MD5 hash you pasted in step 2E above.
If the hashes match, the downloaded ROM zip is non-corrupt. If the hashes don't match, you have to re-download the ROM zip.​
3. Optionally download one or more of my debloat zip files in the third post below. If you don't flash my "no OTA" debloat zip, then don't take any OTAs you get offered if there are ever any more, or you might get soft bricked, which I won't go into recovering from here.
4. (Not needed for 24A KitKat 4.4.2 pre-rooted ROM) Download the latest non-beta SuperSU zip from http://download.chainfire.eu/supersu (XDA thread with this link at http://forum.xda-developers.com/showthread.php?t=1538053) or the latest Beta version from a link in @Chainfire 's thread at http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.
5. Copy/move anything you want to keep from internal storage like the files you downloaded in the previous sections.
6. I strongly suggest wiping everything from TWRP (Data, Cache, System, Dalvik and Internal Storage). Wiping all of these things, especially if you use my debloat zip(s) will clear up garbage/folders that were left behind by previous bloat.
7. Flash my ROM.
8. (Not needed for 24A KitKat 4.4.2 pre-rooted ROM) Flash SuperSU.zip (downloaded in step 4 above). This step is VERY IMPORTANT on 35A Lollipop 5.0.2 and above if you want to get back into custom recovery without having to re-flash a stock ROM and go through the whole process again.
9. Optionally flash one or more of my debloat zip files. If you don't flash my "no OTA" debloat zip, then don't take any OTAs you get offered if there are ever any more, or you might get soft bricked, which I won't go into recovering from here.
Flashing the debloat zip(s) before the first boot of the ROM will give the advantage of never having the data/cache entries or internal storage folders for the debloated apps created, the latter is why I recommend a wipe of internal storage.
In order to get back into TWRP/custom recovery from rooted Lollipop 35A 5.0.2 or above ROMs (not needed for 24A KitKat 4.4.2 pre-rooted ROM):
1. Download the corresponding "aboot only" (aboot is the bootloader) found in the same place to download as my ROM zip. Corresponding means if you installed the latest 36B VK810 stock ROM, then download the 36B VK810 aboot zip file.
2. Download the 4.2.2 aboot package from http://forum.xda-developers.com/showpost.php?p=54533937&postcount=2
Credit and thanks @paperWastage !
The download link is about three quarters down in that second post.
3. Move this aboot.4.2.2.img file into the top of the internal storage (meaning, not in a folder).
4. In Terminal Emulator type (make sure no typos, or can copy/paste to be sure):
Code:
su
dd if=/sdcard/aboot.4.2.2.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
5. You can now reboot into recovery via your preferred method.
6. Once you're finished in TWRP, you need to re-flash the newer aboot zip downloaded in step 1 above. If you forget, the ROM won't boot. You should be able to long-press the power button to force the device off, then use the manual method to get back into TWRP mentioned in step 22 in the previous section above. Re-flash the newer aboot zip, then reboot from TWRP and the ROM will boot.
You can alternatively dirty flash my ROM zip instead of just the aboot. You'd have to re-flash SuperSU.zip, any debloat zips and Xposed if you had before, too.

Reserved

LG G Pad 8.3 & Verizon LG G3 DEBLOAT SCRIPTS - updated 4-6-2016
These will work with both the VK810 Verizon LG G Pad 8.3 35A through 36B, and VS985 Verizon LG G3 23C up through 47A. They will NOT work on KitKat for debloating apps yet, they will work for various other non-app files I debloat. I'm working on updating them.
Again, thanks to @hsbadr for giving me permission to kang "anything I want" for this use.
Thanks to @abced123 for figuring out the root/sbin/lge_fota file is what was still allowing OTAs even after LGFOTA.apk was removed.
Thanks to @alfadon for making me aware of the two additional files that needed removed (at least on the VS985) in order to stop OTAs.
Thanks to @xdabbeb for his VS985 v2.0 ROM, with which I made a comparison to find things I could still debloat that I hadn't yet. If he didn't already figure out what we could lose without loss of functionality, this wouldn't have been possible.
INSTRUCTIONS: Backup in TWRP or read list of files deleted and make sure you don't mind, first. Debloat scripts that you can flash in TWRP after flashing the ROM and SuperSU.zip are located in my debloat script section on Android File Host.
@joshua70448 was kind enough to make an online tool to automate making custom debloat zips according to what a user selects to debloat:
joshua70448 said:
I put together an online tool that lets you pick exactly which files to remove in a debloat script and builds the flashable ZIP and MD5 files for you (as well as a full list of deleted files). Check it out at LG G3 VS985 (Verizon) and G Pad 8.3 VK810 (Verizon) debloat generator.
Click to expand...
Click to collapse
Please thank him at his original post here and take note of his other Android tools in his signature: http://forum.xda-developers.com/showpost.php?p=66192766&postcount=238.
Note that these are most effective if flashed before booting the ROM for the first time, or after a data/cache/Dalvik/internal storage wipe since the data, etc for them are built on first boot but if you flash the debloat script(s) before booting the ROM, then it never gets a chance to create the data and cache for them.
That said, it's completely fine to flash them any time.
Which package removes what (additionally there is a "all" zip that removes all of these EXCEPT it still has OTA and doesn't remove the apps affected by Xposed - you'll need to flash the "no OTA" zip separately). I remove all except for OTA, so I'm aware when OTAs arrive if I don't see notice about it here first, and so I can capture the OTA files. ):
Amazon
delete_recursive("/system/app/AmazonIMDb");
delete_recursive("/system/app/AmazonKindle");
delete_recursive("/system/app/AmazonMobile");
delete_recursive("/system/app/AmazonWidget");
delete_recursive("/system/priv-app/AmazonAppstore");
delete_recursive("/system/priv-app/AmazonAudible");
delete_recursive("/system/priv-app/AmazonKindle");
delete_recursive("/system/priv-app/AmazonMobile");
delete_recursive("/system/priv-app/AmazonMP3");
Google
delete_recursive("/system/app/Books");
delete_recursive("/system/app/Chrome");
delete_recursive("/system/app/CloudPrint");
delete_recursive("/system/app/Drive");
delete_recursive("/system/app/Gmail2");
delete_recursive("/system/app/Hangouts");
delete_recursive("/system/app/Maps");
delete_recursive("/system/app/Music2");
delete_recursive("/system/app/Newsstand");
delete_recursive("/system/app/NewsstandStub");
delete_recursive("/system/app/PlayGames");
delete_recursive("/system/app/PlusOne");
delete_recursive("/system/app/Street");
delete_recursive("/system/app/talkback");
delete_recursive("/system/app/Videos");
delete_recursive("/system/app/YouTube");
delete_recursive("/system/priv-app/Velvet");
delete_recursive("/system/tts/google/es-es-x-ana-phone-hmm");
delete_recursive("/system/tts/google/es-us-x-sfb-phone-hmm");
LG Apps
delete_recursive("/system/app/elt_test");
delete_recursive("/system/app/GnssAirTest");
delete_recursive("/system/app/GnssLogCat");
delete_recursive("/system/app/GnssPosTest");
delete_recursive("/system/app/GnssTest");
delete_recursive("/system/app/LGHome_Theme_Marshmallow");
delete_recursive("/system/app/LGLW_Feather");
delete_recursive("/system/app/LGLW_PolarBear");
delete_recursive("/system/app/LGLW_Prince");
delete_recursive("/system/app/LGNotebook");
delete_recursive("/system/app/LGSearchWidgetProvider");
delete_recursive("/system/app/LGSpringCleaning");
delete_recursive("/system/app/LGVZWHelp");
delete_recursive("/system/app/LGWernickeManager");
delete_recursive("/system/app/OBDM_Permissions");
delete_recursive("/system/app/WfdService");
delete_recursive("/system/media/shutdownanimation.zip");
delete_recursive("/system/priv-app/BioITPlatform_SDService");
delete_recursive("/system/priv-app/LGActionManager");
delete_recursive("/system/priv-app/LGConciergeBoard");
delete_recursive("/system/priv-app/LGCover");
delete_recursive("/system/priv-app/LGEasyHome");
delete_recursive("/system/priv-app/LGFavoriteContactsWidget");
delete_recursive("/system/priv-app/LGFormManager");
delete_recursive("/system/priv-app/LGLIA");
delete_recursive("/system/priv-app/LGLW_MultiPhoto");
delete_recursive("/system/priv-app/LGMemo");
delete_recursive("/system/priv-app/LGMusicWidget");
delete_recursive("/system/priv-app/LGMyGuide");
delete_recursive("/system/priv-app/LGMyWellness");
delete_recursive("/system/priv-app/LGNLPService");
delete_recursive("/system/priv-app/LGPCSuite");
delete_recursive("/system/priv-app/LGPolarisOffice");
delete_recursive("/system/priv-app/LGQMemoplus");
delete_recursive("/system/priv-app/LGQVoiceplus");
delete_recursive("/system/priv-app/LGThinkFreeViewer");
delete_recursive("/system/priv-app/LGTTS");
delete_recursive("/system/priv-app/LGVoiceCommand");
delete_recursive("/system/priv-app/LGVZWHelp");
delete_recursive("/system/priv-app/LIAInformant");
delete_recursive("/system/priv-app/LIAS4URecommender");
delete_recursive("/system/priv-app/LocationAgent");
delete_recursive("/system/priv-app/Maluuba_QVoice");
delete_recursive("/system/priv-app/SSO_P3");
LG Audio
delete_recursive("/system/media/audio/effects/KeypressDelete.ogg");
delete_recursive("/system/media/audio/effects/KeypressReturn.ogg");
delete_recursive("/system/media/audio/effects/KeypressSpacebar.ogg");
delete_recursive("/system/media/audio/effects/KeypressStandard.ogg");
delete_recursive("/system/media/audio/effects/VideoRecord.ogg");
delete_recursive("/system/media/audio/ui/af_failure.ogg");
delete_recursive("/system/media/audio/ui/af_success.ogg");
delete_recursive("/system/media/audio/ui/Audible_Selection.ogg");
delete_recursive("/system/media/audio/ui/camera_click.ogg");
delete_recursive("/system/media/audio/ui/camstart.ogg");
delete_recursive("/system/media/audio/ui/camstop.ogg");
delete_recursive("/system/media/audio/ui/circle_lock.ogg");
delete_recursive("/system/media/audio/ui/circle_unlock1.ogg");
delete_recursive("/system/media/audio/ui/circle_unlock2.ogg");
delete_recursive("/system/media/audio/ui/circle_unlock3.ogg");
delete_recursive("/system/media/audio/ui/circle_unlock4.ogg");
delete_recursive("/system/media/audio/ui/circlemosaic_lock.ogg");
delete_recursive("/system/media/audio/ui/circlemosaic_touchdown.ogg");
delete_recursive("/system/media/audio/ui/circlemosaic_unlock.ogg");
delete_recursive("/system/media/audio/ui/clear_ram.ogg");
delete_recursive("/system/media/audio/ui/continuous_shot.ogg");
delete_recursive("/system/media/audio/ui/crystal_lock.ogg");
delete_recursive("/system/media/audio/ui/crystal_unlock.ogg");
delete_recursive("/system/media/audio/ui/dewdrop_lock.ogg");
delete_recursive("/system/media/audio/ui/dewdrop_touchdown.ogg");
delete_recursive("/system/media/audio/ui/dewdrop_touchrelease.ogg");
delete_recursive("/system/media/audio/ui/dewdrop_unlock.ogg");
delete_recursive("/system/media/audio/ui/Effect_Tick.ogg");
delete_recursive("/system/media/audio/ui/Email_Sent.ogg");
delete_recursive("/system/media/audio/ui/FullBattery.ogg");
delete_recursive("/system/media/audio/ui/Homescreen_Remove.ogg");
delete_recursive("/system/media/audio/ui/Homescreen_Uninstall.ogg");
delete_recursive("/system/media/audio/ui/hulahoops_lock.ogg");
delete_recursive("/system/media/audio/ui/hulahoops_touchdown.ogg");
delete_recursive("/system/media/audio/ui/hulahoops_unlock.ogg");
delete_recursive("/system/media/audio/ui/ink_lock.ogg");
delete_recursive("/system/media/audio/ui/ink_touchdown.ogg");
delete_recursive("/system/media/audio/ui/ink_unlock.ogg");
delete_recursive("/system/media/audio/ui/KeypressDelete.ogg");
delete_recursive("/system/media/audio/ui/KeypressReturn.ogg");
delete_recursive("/system/media/audio/ui/KeypressSpacebar.ogg");
delete_recursive("/system/media/audio/ui/KeypressStandard.ogg");
delete_recursive("/system/media/audio/ui/LG_Cable_Connect.ogg");
delete_recursive("/system/media/audio/ui/LG_Media_volume.ogg");
delete_recursive("/system/media/audio/ui/light_lock.ogg");
delete_recursive("/system/media/audio/ui/light_touchdown.ogg");
delete_recursive("/system/media/audio/ui/light_unlock.ogg");
delete_recursive("/system/media/audio/ui/Lock_Cover.ogg");
delete_recursive("/system/media/audio/ui/Lock.ogg");
delete_recursive("/system/media/audio/ui/LowBattery.ogg");
delete_recursive("/system/media/audio/ui/mosaic_lock.ogg");
delete_recursive("/system/media/audio/ui/mosaic_touchdown.ogg");
delete_recursive("/system/media/audio/ui/mosaic_unlock.ogg");
delete_recursive("/system/media/audio/ui/particle_lock.ogg");
delete_recursive("/system/media/audio/ui/particle_unlock.ogg");
delete_recursive("/system/media/audio/ui/ripple_lock.ogg");
delete_recursive("/system/media/audio/ui/ripple_touchdown1.ogg");
delete_recursive("/system/media/audio/ui/ripple_touchdown2.ogg");
delete_recursive("/system/media/audio/ui/ripple_touchdown3.ogg");
delete_recursive("/system/media/audio/ui/ripple_touchrelease1.ogg");
delete_recursive("/system/media/audio/ui/ripple_touchrelease2.ogg");
delete_recursive("/system/media/audio/ui/ripple_touchrelease3.ogg");
delete_recursive("/system/media/audio/ui/ripple_unlock.ogg");
delete_recursive("/system/media/audio/ui/shot_snap.ogg");
delete_recursive("/system/media/audio/ui/soda_lock.ogg");
delete_recursive("/system/media/audio/ui/soda_touchdown.ogg");
delete_recursive("/system/media/audio/ui/soda_unlock.ogg");
delete_recursive("/system/media/audio/ui/switchoff.ogg");
delete_recursive("/system/media/audio/ui/switchon.ogg");
delete_recursive("/system/media/audio/ui/Unlock.ogg");
delete_recursive("/system/media/audio/ui/vector_lock.ogg");
delete_recursive("/system/media/audio/ui/vector_touchdown.ogg");
delete_recursive("/system/media/audio/ui/vector_unlock.ogg");
delete_recursive("/system/media/audio/ui/VideoRecord.ogg");
delete_recursive("/system/media/audio/ui/volume_key.ogg");
delete_recursive("/system/media/audio/ui/whitehole_lock.ogg");
delete_recursive("/system/media/audio/ui/whitehole_unlock.ogg");
No OTA
delete_recursive("/sbin/lge_fota_launcher");
delete_recursive("/sbin/lge_fota");
delete_recursive("/sbin/lge_gota_launcher");
delete_recursive("/system/app/LGDMWebViewer");
delete_recursive("/system/app/LGFOTA");
delete_recursive("/system/priv-app/LGDMSClient");
Verizon
delete_recursive("/data/app/air.com.sgn.cookiejam.gp-1");
delete_recursive("/data/app/air.com.sgn.juicejam.gp-1");
delete_recursive("/data/app/com.mapquest.android.ace-1");
delete_recursive("/data/app/com.sgn.geniesandgems.gp-1");
delete_recursive("/data/app/com.verizonmedia.go90.enterprise-2");
delete_recursive("/system/app/LGVZWHelp");
delete_recursive("/system/media/bootanimation.zip");
delete_recursive("/system/priv-app/com.gotv.nflgamecenter.us.lite");
delete_recursive("/system/priv-app/com.verizon.mips.adpt");
delete_recursive("/system/priv-app/ECID");
delete_recursive("/system/priv-app/iHeartRadio");
delete_recursive("/system/priv-app/LGVZWHelp");
delete_recursive("/system/priv-app/MyInfozone");
delete_recursive("/system/priv-app/MyVerizon");
delete_recursive("/system/priv-app/SlackerRadio");
delete_recursive("/system/priv-app/VerizonIgnite");
delete_recursive("/system/priv-app/VerizonMessage");
delete_recursive("/system/priv-app/VVM");
delete_recursive("/system/priv-app/VZCloud");
delete_recursive("/system/priv-app/VZMessages");
delete_recursive("/system/priv-app/VZMobileSecurity");
delete_recursive("/system/priv-app/VZNavigator");
Apps affected by Xposed
delete_recursive("/system/app/LGWeather");
delete_recursive("/system/app/LGWeatherService");
delete_recursive("/system/app/LGWeatherTheme");
For the VK810 only, there are also 7-Zip archives of the apps and files that are removed in case any user needs them located in the "35A_08 debloated apps-files" or "36B_00 debloated apps-files" subfolders of my section on Android File Host. They are virtually identical to the separate packages listed above for which debloat script removes what, with the only two exceptions being self-explanatory.
Enjoy!

Claimed again.

Ok....now I'm excited. Any more info?

ddodge68 said:
Ok....now I'm excited. Any more info?
Click to expand...
Click to collapse
Hi! I added some preliminary info in the OP. Thanks for asking!

Looking forward to it, thank so much for taking this on. My poor G Pad had been feeling neglected for far too long since my Nexus 6 gets all the ROM love

rant said:
Looking forward to it, thank so much for taking this on. My poor G Pad had been feeling neglected for far too long since my Nexus 6 gets all the ROM love
Click to expand...
Click to collapse
Will this be something we can flash right from TWRP ?

rant said:
Looking forward to it, thank so much for taking this on. My poor G Pad had been feeling neglected for far too long since my Nexus 6 gets all the ROM love
Click to expand...
Click to collapse
You're welcome! I was doing some preliminary work before CleanROM was released to release something like this for 24A but I didn't want to bother duplicating the effort once it was released. There's others who are trying quietly to give our tablet more love than I can give it.
Anthony-m said:
Will this be something we can flash right from TWRP ?
Click to expand...
Click to collapse
Yes.

ROM's done uploading for anyone interested. I'll work on a debloat zip, but that'll take longer than a day.

roirraW "edor" ehT said:
ROM's done uploading for anyone interested. I'll work on a debloat zip, but that'll take longer than a day.
Click to expand...
Click to collapse
Sorry for the questions and thanks a lot for making this rom happen for us. I am using the clean rom right now and the TWRP you mention above, do I just flash the rom and then Supersu and I will have rooted stock lollipop correct? Then I would need to follow the directions in your 4.22 aboot image (which I am pretty sure I already did when I installed TWRP the first time)..again thanks for your hard work..

Anthony-m said:
Sorry for the questions and thanks a lot for making this rom happen for us. I am using the clean rom right now and the TWRP you mention above, do I just flash the rom and then Supersu and I will have rooted stock lollipop correct? Then I would need to follow the directions in your 4.22 aboot image (which I am pretty sure I already did when I installed TWRP the first time)..again thanks for your hard work..
Click to expand...
Click to collapse
No problem. Just flash the ROM and SuperSU, and yes you'll have rooted stock lollipop.
You don't need to follow the directions regarding the 4.2.2 aboot image unless you want to get back into TWRP. But if flash the 4.2.2 aboot.img, you won't be able to boot the ROM, only TWRP. You can do it, to make a backup, to flash something else like Xposed Alpha for Lollipop, etc (unsupported by me), then you'll have to flash the 35A_08 aboot.img zip file I also provide from TWRP so that you can boot the ROM again.
I'll try to figure out a way to make this all clearer.

Thanks for the fast replies, you are so damn helpful I really appreciate it. Crap should I do a factory reset from TWRP before flashing this lol..you knew one more question was coming lol

Anthony-m said:
Thanks for the fast replies, you are so damn helpful I really appreciate it. Crap should I do a factory reset from TWRP before flashing this lol..you knew one more question was coming lol
Click to expand...
Click to collapse
Well thank you back! I appreciate it.
Yes wipe system, data, cache and Dalvik before flashing. Just remember to flash the SuperSU.zip after.

Do i have to wipe/factory reset or wiil this update from cleanrom

4218kris said:
Do i have to wipe/factory reset or wiil this update from cleanrom
Click to expand...
Click to collapse
Hello!
Answered a few posts above yours.

roirraW "edor" ehT said:
Hello!
Answered a few posts above yours.
Click to expand...
Click to collapse
Android is upgrading

Damn I installed the rom and it was working perfectly than I did the aboot update and restarted the tablet and it says secure booting error cause boot certification verify and it stays on the LG screen...FML lol...

Anthony-m said:
Damn I installed the rom and it was working perfectly than I did the aboot update and restarted the tablet and it says secure booting error cause boot certification verify and it stays on the LG screen...FML lol...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=60879291&postcount=11
You need to flash the 35A_08 aboot zip file I provided in the same place as the ROM download on AFH in order to boot the ROM. The 4.2.2 aboot is only for getting into custom recovery. Once you flash the ROM, the *only* reason for re-flashing the 4.2.2 aboot is to get into custom recovery. But then you need to reflash the 35A_08 5.0.2 aboot in order to boot back into the ROM.

Never mind *****es, did a factory reset and it went to TWRP and I did the update exactly like roirraW "edor" ehT instructed in his OP and I am all set with the new rooted Lollipop rom and TWRP Nice work brother....
---------- Post added at 05:22 PM ---------- Previous post was at 05:20 PM ----------
Yup I just didn't realize I wasn't going to automatically go into TWRP after flashing the 4.2.2 aboot image, once I got in I applied the 35A_08 aboot zip and all is well...

Related

[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my (and one 22B TOT too) updated 4-6-2016

Thanks to everyone over the past almost six years who helped me get to the point where I am so far. Glad to help others in what ways I can.
Thanks to @bweN diorD for his Verizon LG G3 VS985 repository. Inspired me to do this for the VK810.4G, although it took me six months of considering doing it before I was motivated enough to.
Thanks to @Papay346 for purchasing and testing the 22B_00 TOT file from a Chinese website, and for sharing it with us! His original post here http://forum.xda-developers.com/showpost.php?p=66089535&postcount=6.
I intend this as a repository for all OTA, .img, KDZ and TOT files relating to each official (and leaks if we ever find any, which will be indicated as unofficial/leak/whatever) LG release. If not noted otherwise, all files are official (unaltered from the official stock release).
The latest files will always be at the top with the oldest always at the bottom.
All downloads are available in my VK810.4G section on Android File Host in the OTA, IMG or KDZ and TOT subfolder. Below is merely a list of what's available there. If you don't know what to do with these, you don't need them.
36B_00 - Lollipop v5.0.2
KDZ: VK81036B_00-Lollipop_5.0.2_KDZ.7z
IMGs:VK81036B_00_5.0.2_system.img.7z
VK81036B_00_5.0.2_all_but_system.img.7z​OTA: VK810.4G_altev_35A_08to36B_00_5.0.2_OTA.7z
35A_08 - Lollipop v5.0.2
KDZ: VK81035A_08 - Lollipop 5.0.2.KDZ - MD5 hash inside.7z
IMGs:VK81035A_08 5.0.2 system.img.7z
VK81035A_08 5.0.2 all but system.img.7z​OTA: VK810.4G_altev_24A_00to35A_08_5.0.2_OTA.7z
24A_00 - KitKat 4.4.2
KDZ: VK81024A_00.KDZ - KitKat 4.4.2.7z
IMGs:Verizon LG G Pad 8.3 VK810.4G 24A system.img.7z
boot.img
modem.img​OTA: Not captured yet.
23A_04 - KitKat 4.4.2
KDZ: VK81023A_04.KDZ file with MD5 hash inside - NON-FLASHABLE - KitKat 4.4.2.zip
IMGs:VK810.4G Verizon LG G Pad 8.3 23A_04 system.img partition file.7z
VK810.4G Verizon LG G Pad 8.3 23A_04 other partition img files.7z
VK810.4G Verizon LG G Pad 8.3 23A_04 extracted from KDZ Web8064.dll - don't know if it's useful.7z​OTA: Not captured yet.
22B_00 - KitKat 4.4.2 (TOT available)
TOT: VK81022B_00.TOT file with MD5 hash inside - KitKat 4.4.2.7z
DLL for TOT method: VK81022B_00-KitKat_4.4.2-Web8064.DLL_for_TOT_method.7z
KDZ: VK81022B_00.KDZ file with MD5 hash inside - KitKat 4.4.2.7z
IMGs:VK81022B_00_4.4.2_all_but_system.img_and_userdata.img.7z
VK81022B_00_4.4.2_system.img_only.7z
VK81022B_00_4.4.2_userdata.img_only-extracts_to_10.7GB.7z​OTA: Not captured yet.
11A_01 - Jellybean 4.2.2
KDZ: VK81011A_01 - Jellybean 4.2.2.KDZ - MD5 hash inside.7z
IMGs:VK81011A_01_4.2.2_all_but_system.img.7z
VK81011A_01_4.2.2_system.img_only.7z​
I confirm that this works.
How is this tool used to flash VK81023A_04.kdz?
D0M1N!X said:
I confirm that this works.
Click to expand...
Click to collapse
Every time I go to thank your post I happen to not be on TapaTalk and over my 8 Thanks limit. Thanks for confirming.
gehx said:
How is this tool used to flash VK81023A_04.kdz?
Click to expand...
Click to collapse
Hi! The page I linked to for [URL=" Flash Tool 2014 - Tools Offline KDZ Flash Rom for LG[/URL] has the directions and screenshots. I know the language is in Vietnamese. Google Chrome (at least on the PC, but I believe on Android too) will translate the word directions closely enough, and for what doesn't get translated because it's text in a picture won't matter because the screenshots make it pretty clear what to do. It's pretty easy, I've done it a couple of times.
I'm not seeing the link for the KDZ file on the page. I used the translate option but maybe I'm blind. I looked around and found this:
https://www.androidfilehost.com/?fid=95864024717073362
Is this the right file?
sefirosu0522 said:
I'm not seeing the link for the KDZ file on the page. I used the translate option but maybe I'm blind. I looked around and found this:
Is this the right file?
Click to expand...
Click to collapse
Yep, that's my file as you can tell by the MD5 hashes matching those in my post. My link is at the end of the line:
Any current and future files for this and other devices will be available in my section on Android File Host.
Click to expand...
Click to collapse
I'll try to make it stand out more. Thanks!
roirraW "edor" ehT said:
Yep, that's my file as you can tell by the MD5 hashes matching those in my post. My link is at the end of the line:
I'll try to make it stand out more. Thanks!
Click to expand...
Click to collapse
Thanks. So basically just to dumb it out. What I should be doing is:
Install the LGUnitedMobileDriver_S50MAN311AP22_ML_WHQL_Ver_3.11.3.exe file.
Download and install the LG Flash Tool 2014.zip file.
Which files get copied into the KDZ 2014 LG Flash Tool folder?
Connect the phone to the computer. (Are we supposed to use ethernet mode ?)
LGFlashTool2014.exe
Does that sound right? Sorry for the dumb questions. I've set my G2 back a ton of times using the Verizon only method. I've never done it with the tablet and it seems like it's done differently.
Any help would be very appreciated.
sefirosu0522 said:
Thanks. So basically just to dumb it out. What I should be doing is:
Install the LGUnitedMobileDriver_S50MAN311AP22_ML_WHQL_Ver_3.11.3.exe file.
Download and install the LG Flash Tool 2014.zip file.
Which files get copied into the KDZ 2014 LG Flash Tool folder?
Connect the phone to the computer. (Are we supposed to use ethernet mode ?)
LGFlashTool2014.exe
Does that sound right? Sorry for the dumb questions. I've set my G2 back a ton of times using the Verizon only method. I've never done it with the tablet and it seems like it's done differently.
Any help would be very appreciated.
Click to expand...
Click to collapse
Just going by memory at the moment - I'm at work so I have to hurry. Yes, it all sounds right except the driver. If I remember correctly, the Verizon variant of the G3 uses a different set of drivers, I think it's mentioned on that LGFlashTool2014 page, right after it mentions the one you said. They're probably saying to copy the KDZ to the flash tool folder, but I think you can just browse to wherever you have it on the same PC from the tool anyway.
Yes, ethernet mode.
sefirosu0522 said:
Thanks. So basically just to dumb it out. What I should be doing is:
Click to expand...
Click to collapse
How'd it go?
Sent from my LG-VS985
roirraW "edor" ehT said:
How'd it go?
Sent from my LG-VS985
Click to expand...
Click to collapse
It was flawless. The only thing is that I did the CSE flash and I was able to root but I'm not sure how to get TWRP back. I tried following the thread but ran into issues. I can't remember what it was. So basically I did it twice and now I am fully stock unrooted.
sefirosu0522 said:
It was flawless. The only thing is that I did the CSE flash and I was able to root but I'm not sure how to get TWRP back. I tried following the thread but ran into issues. I can't remember what it was. So basically I did it twice and now I am fully stock unrooted.
Click to expand...
Click to collapse
That's good to hear!
To confirm that your steps of trying to root and put TWRP back on are the same as what I think:
1. Turn BOTH USB Debugging and (install from) Unknown Sources on.
2. Install and run Stump.apk (turn volume all the way down) and choose to brute force. Might take 10-20 minutes.
3. When Stump reports success, reboot when prompted, install SuperSU from the Play store, run SuperSU, install binaries and reboot again.
4. If it is or ever will be your intention for USB Debugging to stay on (for use with Titanium Backup, etc) between reboots, Stump creates a quirk where it doesn't stay selected between reboots. A known fix is to (if I remember correctly) plug the tablet into your PC, select Camera (PTP) mode, then re-select Media sync (MTP) mode. You might or might not have to already have USB Debugging re-checked during this - *shrug*.
5. While on the subject of Titanium Backup, I find that on recent versions of SuperSU (since it's been made Lollipop compatible and includes the "Mount namespace separation" option and it's checked by default), that I have to de-select "Mount namespace separation" in SuperSU's settings in order for Titanium Backup to work for restoring - perhaps backing up or other things as well. Reboot after changing that option in SuperSU.
6. Follow the directions at http://forum.xda-developers.com/showthread.php?t=2726707 to the letter, using the extracted zip of TWRP v2.7.0.1, then flashing 2.7.0.2 from 2.7.0.1 once booted into it.
Note that by "terminal", if I remember right, they mean the Terminal app on the rooted tablet - not Terminal under Linux or Command/PowerShell under Windows. Or it's the other way around, I really haven't done it quite enough times but I think I recall that it wasn't as convenient since I couldn't as easily copy and paste the necessary commands. Sorry for vagueness! Make sure USB Debugging is turned on for this, too.
roirraW "edor" ehT said:
That's good to hear!
To confirm that your steps of trying to root and put TWRP back on are the same as what I think:
6. Follow the directions at http://forum.xda-developers.com/showthread.php?t=2726707 to the letter, using the extracted zip of TWRP v2.7.0.1, then flashing 2.7.0.2 from 2.7.0.1 once booted into it.
Note that by "terminal", if I remember right, they mean the Terminal app on the rooted tablet - not Terminal under Linux or Command/PowerShell under Windows. Or it's the other way around, I really haven't done it quite enough times but I think I recall that it wasn't as convenient since I couldn't as easily copy and paste the necessary commands. Sorry for vagueness! Make sure USB Debugging is turned on for this, too.
Click to expand...
Click to collapse
Thank you. You've been extremely helpful with this. For step 6, are you talking about the instructions over at this thread?
http://forum.xda-developers.com/showthread.php?t=2726707
I thought that was only for 4.2.2.
sefirosu0522 said:
Thank you. You've been extremely helpful with this. For step 6, are you talking about the instructions over at this thread?
I thought that was only for 4.2.2.
Click to expand...
Click to collapse
You're welcome and thank you!
It's what I've used to put TWRP on, with 4.4.2 loaded, and make backups and restores.
roirraW "edor" ehT said:
You're welcome and thank you!
It's what I've used to put TWRP on, with 4.4.2 loaded, and make backups and restores.
Click to expand...
Click to collapse
Thanks again. I haven't tried this yet but I will soon.
I can confirm that the trick worked as noted in the VIET website. Thanks again.
joeminati said:
I can confirm that the trick worked as noted in the VIET website. Thanks again.
Click to expand...
Click to collapse
You're welcome!
I must be the only person who cannot understand the Vietnamese website....even when translated. I've attached images of what I get from Google, once translated. Yes, it's English, but it makes no sense. Any help would be appreciated.
ddodge68 said:
I must be the only person who cannot understand the Vietnamese website....even when translated. I've attached images of what I get from Google, once translated. Yes, it's English, but it makes no sense. Any help would be appreciated.
Click to expand...
Click to collapse
You can have the phone already in Download mode and attached when you start the LG Mobile 2014 tool. Personally (if the Android system is working), I leave the phone fully on and plug it into the PC. After all drivers load, I make sure the USB connection is set to MTP, or on 10B set it to Internet.
When you start the flash process in the tool, it'll reboot the phone into Download mode itself. Saves me some finger-wrangling plus coming from the Samsung Galaxy S2 & S3, I like to keep my presses of the power button to a minimum (because they would go bad on the Galaxy S2 & S3).
Leave all the settings exactly as pictured. CSE flash is what you want almost all the time. It's a complete wipe. Normal is like a dirty flash. If you're ever downgrading from a newer version to older version, you DEFINITELY want CSE, but you almost always want CSE anyway. Make a copy of the KDZ file and put it in the folder you extracted LG Mobile 2014 into. Use the button to the right on the first dialog to direct it to the KDZ file you just put in there.
On the screen with the language. Don't believe any instructions that say to leave it to Korean and that it'll still come out English. It doesn't. That doesn't affect actually flashing the phone but it's nice to understand the status messages, so change them appropriately. The rest is just as pictured.
If you have any specific questions beyond that, please ask.
VK810.4G altev Verizon LG G Pad 8.3 Stock 4.4.2 24A (4/5/2015) KDZ file
Added news that the build 24A KDZ file is available at my AFH link for posterity or at one of the two sources I downloaded it from, listed in the OP.
Thanks for always posting about the VK810. I feel like it gets no love!

[ROM] [Base] [LP] [Stock] ROM Base for LP Upgrade + Working Bump!

This is a ROM Base of the latest LP VS985 23C & 23B for all devs who work on Stock LG system. It was a part of JasmineROM, but since it's Unmodified Stock/Rooted ROM, it should be just a ROM base. It makes it easy to upgrade to LP without the OTA hassle & to prepare partitions for future updates. It also keeps Bump-signed images (TWRP recovery & custom kernels) working without affecting any of the current ROMs/Kernels. You might need to just flash modem & kernel (check this post for official firmware) if you'd like to downgrade or switch ROMs (only if they're not already included in that ROM).
I went the image route (the new method) because I had some issues with some firmware. It run perfectly on my device, but failed to boot (or stuck in a bootloop) for some testers. The reason for Data/WiFi & other issues I've experienced during testing was due Symlinks, Permissions, & SELinux context. They should be identical to stock system. So, to avoid any other unforeseen issues, I decided to write stock images (so it works as expected) & updates will automatically follow the correct symlinks/permissions/context. I can make a working updater-script, but this way is much easier & straightforward.
23C Installation Instructions: - Official
BACKUP your apps via TitaniumBackup
REBOOT to TWRP recovery (the latest TWRP v2.8.6.0 can be found here)
WIPE everything (system/data/cache/dalvic)
FLASH JasmineROM_v7.0.zip - BE PATIENT !
FLASH SuperSU for ROOT access
RESET factory from within ROM (in Settings) is required.
If you run into WiFi/Sync issues, flash CRONTAB_DisableIPv6.zip
Click to expand...
Click to collapse
23C Installation Instructions: - Leak
BACKUP your apps via TitaniumBackup
REBOOT to TWRP recovery (the latest TWRP v2.8.6.0 can be found here)
WIPE everything (system/data/cache/dalvic)
FLASH JasmineROM_v6.0_Unmodified.zip - BE PATIENT !
RESET factory from within ROM (in Settings) is required.
If you run into WiFi/Sync issues, flash CRONTAB_DisableIPv6.zip
Click to expand...
Click to collapse
23B Installation Instructions: - Leak
The installation of 23B is quite simple (much less complicated than it sounds): you just need to run installROM.sh script; the other steps are just for preparation/clarification. This method just works in all situations (coming from Stock KK 10B/11C/12B or AOSP LP) we tested to update all relevant partitions. The future updates will be in the form of a regular flashable .ZIP file.
1. Make Nandroid backup of your ROM via TWRP recovery
2. Download & extract JasmineROM_v5.0.zip (use Zarchiver)
3. Make sure you don't have any partition images in internal storage (/sdcard)
4. Copy all files in JasmineROM_v5.0 directory to internal storage (/sdcard)
5. (Re)boot into TWRP recovery
6. Use Terminal Command (in TWRP) OR ADB (from PC/Mac/Linux via adb shell) to run the following 3 commands:
Code:
cp /sdcard/installROM.sh /sbin/
chmod 0755 /sbin/installROM.sh
sh /sbin/installROM.sh
The first two commands shouldn't print anything.
The 1st command copies the script to /sbin & the 2nd sets its permissions.
The 3rd command runs the script only if it's in /sbin (1st command) & has executable permissions (2nd command).
If you've messed up with your partitions layout or filesystem (e.g., formatting f2fs), revert to factory setup (e.g., ext4 filesystem - since stock kernel doesn't support f2fs).
The last command will take some time (~10 minutes). BE PATIENT !.
Some entries will appear to hang, do not interrupt or disconnect cable!
The "No space left on device" warning is NORMAL
You should see command prompt & ROM info/release date at the end !
Click to expand...
Click to collapse
7. Flash Download Mode Fix + Debuggable Kernel & Reboot
If you run into issues, it's because you've conflicting data from KK.
Do a factory reset in Settings to restore default LP databases!
You may use TitaniumBackup instead of factory reset > Tap batch actions on the top right > Scroll down to "Manipulate data" > Run "Wipe data for user & system apps"
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads:
Please read carefully the instructions above before proceeding at you own risk!
JasmineROM v7.0 Release: JasmineROM_v7.0.zip
md5: 7ac04a41e1f6bb26f51e50760023395d
JasmineROM v6.0 Unmodified: JasmineROM_v6.0_Unmodified.zip
md5: 18887557219ccbf428a4fe99733698da
CRONTAB + Disable IPv6: CRONTAB_DisableIPv6.zip
md5: c6487922357b330cbb6257d91076ca7d
JasmineROM v5.0 Unmodified: JasmineROM_v5.0.zip
md5: 4e6aec50ab9763c4396dcb5e45408a95
Click to expand...
Click to collapse
Thanks to:
All devs/testers/users contributed to it
@HolyAngel for collaboration on Stock-based ROMs
@bweN diorD & @autoprime for the images!
@annoyingduck & @krazy_smokezalot for final tests
Click to expand...
Click to collapse
You guys are the best! I know everyone has been looking forward to this day. If you wanted to flash KK back, would it work to just flash the modems/KK ROM over this?
guitarbedlam said:
You guys are the best! I know everyone has been looking forward to this day. If you wanted to flash KK back, would it work to just flash the modems/KK ROM over this?
Click to expand...
Click to collapse
Yep, just flash the KK ROM + proper kernel & modem
Will this method work for 23a stock? I can't get any method to work for kdz, tot, or root. I lost root when I used active launcher to push 23 a.
jthompson0019 said:
Will this method work for 23a stock? I can't get any method to work for kdz, tot, or root. I lost root when I used active launcher to push 23 a.
Click to expand...
Click to collapse
This method is for those coming from Stock KK 10B/11C/12B or AOSP LP with KK firmware.
hsbadr said:
This method is for those coming from Stock KK 10B/11C/12B or AOSP LP with KK firmware.
Click to expand...
Click to collapse
Is there a method you would recommend? I can't seem to get anything to work.
jthompson0019 said:
Is there a method you would recommend? I can't seem to get anything to work.
Click to expand...
Click to collapse
You may try this at your own risk. It may work, but not tested.
hsbadr said:
This is a ROM Base of the latest LP VS985 23B for all devs who work on Stock LG system. It was a part of JasmineROM, but since it's Unmodified Stock/Rooted ROM, it should be just a ROM base. It makes it easy to upgrade to LP without the OTA hassle & to prepare partitions for future updates. It also keeps Bump-signed images (TWRP recovery & custom kernels) working without affecting any of the current ROMs/Kernels. You might need to just flash modem & kernel (check this post for official firmware) if you'd like to downgrade or switch ROMs (only if they're not already included in that ROM).
I went the image route (the new method) because I had some issues with some firmware. It run perfectly on my device, but failed to boot (or stuck in a bootloop) for some testers. The reason for Data/WiFi & other issues I've experienced during testing was due Symlinks, Permissions, & SELinux context. They should be identical to stock system. So, to avoid any other unforeseen issues, I decided to write stock images (so it works as expected) & updates will automatically follow the correct symlinks/permissions/context. I can make a working installer-script, but this way is much easier & straitforward.
The installation is quite simple (much less complicated than it sounds): you just need to run installROM.sh script; the other steps are just for preparation/clarification. This method just works in all situations (coming from Stock KK 10B/11C/12B or AOSP LP) we tested to update all relevant partitions. The future updates will be in the form of a regular flashable .ZIP file.
Installation Instructions:
Did you know that... You are the best? ?????
Click to expand...
Click to collapse
Thanks a lot. Worked great. Is anyone having trouble with ADB after updating? My ADB worked fine before. I'm trying to find new drivers to install but can't seem to get it.
Coming from the stock KK running AOSP based LP ROMs right now should I install this to get my modem updated to the LP one? Or can I just flash the LP modem to get that updated?
AngryManMLS said:
Coming from the stock KK running AOSP based LP ROMs right now should I install this to get my modem updated to the LP one? Or can I just flash the LP modem to get that updated?
Click to expand...
Click to collapse
You can just flash the modem, but I have no idea if the 23B modem works with AOSP/CM 12.
Sent from my VK810 4G
I'm having trouble installing the original jasmine from page 200. I go through all the steps to run the install script, and everything goes fine and it installs correctly. When I boot it up, however, it won't load and it gives me the stock verizon boot animation and it hangs there. I didn't flash the download mode fix, was going to do that after I booted up for the first time
EDIT: I reinstalled the script, again, everything goes fine and it shows the release data at the end. Then, I flash the last zip, goes fine, and I reboot just like in the instructions and it gives me a blue and green light from the notification light and it's hanging at the stock verizon boot animation and it doesn't look like it's going anywhere. Anyone can help??
cap1tal1sm said:
I'm having trouble installing the original jasmine from page 200.
Click to expand...
Click to collapse
You shouldn't post the same thing in multiple threads.
Sent from my VK810 4G
cap1tal1sm said:
I'm having trouble installing the original jasmine from page 200. I go through all the steps to run the install script, and everything goes fine and it installs correctly. When I boot it up, however, it won't load and it gives me the stock verizon boot animation and it hangs there. I didn't flash the download mode fix, was going to do that after I booted up for the first time
EDIT: I reinstalled the script, again, everything goes fine and it shows the release data at the end. Then, I flash the last zip, goes fine, and I reboot just like in the instructions and it gives me a blue and green light from the notification light and it's hanging at the stock verizon boot animation and it doesn't look like it's going anywhere. Anyone can help??
Click to expand...
Click to collapse
Hey, friendly advice. Don't cross post. Especially 3 different threads.
From my VS985 - Jasmine 5.0.11
whatever gets the fastest response
cap1tal1sm said:
whatever gets the fastest response
Click to expand...
Click to collapse
Lol. Ok, not really the best justification. This isn't an IT help desk.
Sent from my Nexus 7 2013
True that, and let me give you a counter point: How does one extra marginal post in a different forum deteriorate your life in any way possible or imaginable? What is the cost of one more forum post, which by mathematical truth can only lead to one extra page at most?
Is it the opportunity cost of reading my post, and realizing you read the same text somewhere else? Is my ire at my cross post really just anger at re-posts in general? The concept of copying content and under valuing originality? If this is the case, I concede you have a point. I too am an effervescent searcher for good, funny, original and insightful content. My jimmies become quite rustled when I see something I've already seen before.
But here's the irony: just now, you've taken more time to read this post, than the last one!!! Isn't that funny? And it's interesting to think about, for the following reason: What is a post's ultimate value? It's a + b , where a is the value I gain from my post being answered, and b is the value you gain from reading it. Let's think about this post again; this post is literal poop. It is worthless, it's a waste of my time and yours. So really, this post is valueless for everyone involved. Yet, according to the logic of this website's forum, this post is completely fine since it's an original, non-cross post.
Yet my cross posts, which are bad as you suggest, give me immense value! Because my question is answered nearly (but not perfectly) twice as fast, so I get 2a + b return on the post. Do you see how illogical your conception of what is good posts/content, and what is bad?
Eh, but what do I know: I just go to the number 1 school in the US.
cap1tal1sm said:
True that, and let me give you a counter point: How does one extra marginal post in a different forum deteriorate your life in any way possible or imaginable? What is the cost of one more forum post, which by mathematical truth can only lead to one extra page at most?
Is it the opportunity cost of reading my post, and realizing you read the same text somewhere else? Is my ire at my cross post really just anger at re-posts in general? The concept of copying content and under valuing originality? If this is the case, I concede you have a point. I too am an effervescent searcher for good, funny, original and insightful content. My jimmies become quite rustled when I see something I've already seen before.
But here's the irony: just now, you've taken more time to read this post, than the last one!!! Isn't that funny? And it's interesting to think about, for the following reason: What is a post's ultimate value? It's a + b , where a is the value I gain from my post being answered, and b is the value you gain from reading it. Let's think about this post again; this post is literal poop. It is worthless, it's a waste of my time and yours. So really, this post is valueless for everyone involved. Yet, according to the logic of this website's forum, this post is completely fine since it's an original, non-cross post.
Yet my cross posts, which are bad as you suggest, give me immense value! Because my question is answered nearly (but not perfectly) twice as fast, so I get 2a + b return on the post. Do you see how illogical your conception of what is good posts/content, and what is bad?
Eh, but what do I know: I just go to the number 1 school in the US.
Click to expand...
Click to collapse
we got us a arrogant lill fellow here...haha thinks he's the only smart person in the world all that schooling and can't even correct a minor android problem kinda ironic having that attitude will not get u any help '
update:
have u ever changed ur file system from ext4 to f2fs? mind the same but it was bc i had changed my filesystem to f2fs...i reformatted it to ext4 and it booted no problem...initial boot takes quite a bit...5 mins or so
I never bothered doing Bump to get a custom recovery installed. I simply got root on 10B and then disabled automatic updates. As such, I figure this method won't work for me as it involves steps within TWRP. Would my best bet for getting stock rooted Lollipop be to enact Bump to get a custom recovery, and then follow these steps? The Bump stuff didn't make sense to me so I didn't dare venture down that road, and am hoping I can still avoid it...
crazy4android said:
we got us a arrogant lill fellow here...haha thinks he's the only smart person in the world all that schooling and can't even correct a minor android problem kinda ironic having that attitude will not get u any help '
update:
have u ever changed ur file system from ext4 to f2fs? mind the same but it was bc i had changed my filesystem to f2fs...i reformatted it to ext4 and it booted no problem...initial boot takes quite a bit...5 mins or so
Click to expand...
Click to collapse
It's called trolling son. Back in my day, it was an art. Now I just do it for the thrill.
I have no idea how to change file systems. The whole boot partition thing is what weirded me out, I have no idea about that stuff. I ended up flashing back to my kit kat recovery (which had a date of like january 5, lol. So I had been off stock rooted xposed for almost 4 months) and running the commands. Then instead of hanging at the verizon screen at boot, it went into the android is upgrading thing fine.
So I guess it's a directional thing, where you can go forwards in time but not backwards. Which was where I was coming from on Illusion 6.0.

[Q] G3 update but have root and custom recovery

A friend of mibe wanted me to update my phone so i could have advanced calling. But its an update and do notwont to risk losing root and recovery or worst face brick. I would love to have this update so im hoping is there a work around. Is there a way to root the phone again if it does wipe it out. Is there a way to download it and have my custom recovery install it. Please and thank you
If you're already on 12b, you already have advanced calling. Otherwise, go here
http://forum.xda-developers.com/showthread.php?p=57360121
It's like the second sticky down in the general section. Read, read, and read again before attempting to update your G3. Although it's pretty easy to fix if you mess something up, it's also pretty easy to softbrick.
Sent from my VS985 4G using Tapatalk 2
Johneedoe said:
If you're already on 12b, you already have advanced calling. Otherwise, go here
http://forum.xda-developers.com/showthread.php?p=57360121
It's like the second sticky down in the general section. Read, read, and read again before attempting to update your G3. Although it's pretty easy to fix if you mess something up, it's also pretty easy to softbrick.
Sent from my VS985 4G using Tapatalk 2
Click to expand...
Click to collapse
I hope i did the quote right. I got more info to what i have this is whati have
Hope u see the pic
LASERWOLF452 said:
I hope i did the quote right. I got more info to what i have this is whati have
Hope u see the pic
Click to expand...
Click to collapse
The number at the end of the build number is 10B. You need to be on 12B or higher in order to use Advanced Calling. Also would have to enable it on your Verizon account. MIght be under "HD Calling".
roirraW "edor" ehT said:
The number at the end of the build number is 10B. You need to be on 12B or higher in order to use Advanced Calling. Also would have to enable it on your Verizon account. MIght be under "HD Calling".
Click to expand...
Click to collapse
Thanks but one thing. I hate to sound like a noob but doing this ive never done before. Is there a guide that can walk me threw it to get to 12b
LASERWOLF452 said:
Thanks but one thing. I hate to sound like a noob but doing this ive never done before. Is there a guide that can walk me threw it to get to 12b
Click to expand...
Click to collapse
If you're wanting to be rooted and update to 12B...
1. Root using Stump apk brute force method. Reboot.
2. Install SuperSU from Play Store, reboot, launch SuperSU, update binary, reboot again.
3. Install TWRP Manager from the Play Store, launch it and grant it root permissions.
4. Use TWRP Manager's option in the upper right corner to download and install the latest TWRP custom recovery for the VS985. It's already bump'd, I've verified.
5. Use the link @Johneedoe provided, download the 12B boot, modem and system.img files. Extract system.img from the system.zip.
6. There's a link in that first post, after all the download links to @autoprime 's Flash2 method. Use that through TWRP with the 12B img files you downloaded.
Sent from my VK810 4G
You can just take the OTA to 11c and then 12b. You won't lose root on the way.
siriusgamer said:
You can just take the OTA to 11c and then 12b. You won't lose root on the way.
Click to expand...
Click to collapse
he has custom recovery installed. do not take ota's or it will not boot until you flush the fota folder, and the ota wont install.
bweN diorD said:
he has custom recovery installed. do not take ota's or it will not boot until you flush the fota folder, and the ota wont install.
Click to expand...
Click to collapse
Thanks for letting them know. I was already told not to update with custom recovery by a friend. I have not done the update a friend is going to help me threw it cause i dont wont to take a chance and mess it up if i cone access sonthing i dont u derstand. Im more in learning stages of rooting. And new with ota updates as im new to that lol
update failed. need help to 12b
Me and my friend was working on my phone but we had an issue.
I'm running twrp latest version, and we followed this post as is
http://forum.xda-developers.com/showpost.php?p=56100153&postcount=1
And I,ended up with an error . all,passes and succeeds but I get
E: Unable to mount ' /system'
just wanted to put this but i found my error, i had no computer at the time and was using on my cellphone to extract the files, i got my laptop fixed and was able to get 12b installed thanks for the help
bweN diorD said:
he has custom recovery installed. do not take ota's or it will not boot until you flush the fota folder, and the ota wont install.
Click to expand...
Click to collapse
so.. i've made this mistake. where can i find info on flushing the fota folder? and the steps to take after that..? plz and thank you in advance
killerskincanoe said:
so.. i've made this mistake. where can i find info on flushing the fota folder? and the steps to take after that..? plz and thank you in advance
Click to expand...
Click to collapse
I'm not in a position to grab the link right now. Check my Reference post in general, or look for the original post by autoprime. It's a twrp flashable zip.
Sent from my N6
Ok, ive bricked and started fresh all over again, the problems with the file rhat im suppose to rename and take out the number, well when i down loaded that file it reads system 12B rar. If i change the name i brick, if i leave it as is i get error on system dwnload??, 1st two times was an error, 3rd time i changed the name and bricked it. Took me 3 hrs to get back to 19b,little help here!!!
Sent from my VS985 4G using XDA-Developers mobile app
jlb1959.01 said:
Ok, ive bricked and started fresh all over again, the problems with the file rhat im suppose to rename and take out the number, well when i down loaded that file it reads system 12B rar. If i change the name i brick, if i leave it as is i get error on system dwnload??, 1st two times was an error, 3rd time i changed the name and bricked it. Took me 3 hrs to get back to 19b,little help here!!!
Click to expand...
Click to collapse
I'm not positive what you want your end result to be, but if you want root and TWRP on any version of the stock ROM, the easiest method is to use the built in LG Backup to backup your user apps, user data and limited system data to your MicroSD card, move anything else you want to keep from your internal storage, flash the 10B TOT using the .DLL that's extracted from the 35B KDZ, root using the Stump app on XDA, put TWRP on with TWRP Manager from the Play Store, reboot to TWRP, wipe Cache, Dalvik/ART and Data, flash whatever ROM you want and appropriate Bootstack. Bootstacks are in @xdabbeb 's VS985 v2.0 ROM thread in the Development (non-original) section. 12B Bootstack for KitKat, 24B for Lollipop 5.0.x and 35B for Lollipop 5.1.x and Marshmallow 6.0.
If you flashed a stock-based ROM, then you can use the built-in LG Backup to restore your backup from previously. Not much, if any (depending on what version of the stock ROM you come from, and what you flash) system data will be restored.
Sorry road warrior, you helped me a ton, don't know if you remember me, I had 5.1 but did an Ota to 6.0, I wanted to start fresh do I followed you and laser wolf, I downgraded to 10b,now when trying to follow laser wolf a
---------- Post added at 05:08 PM ---------- Previous post was at 05:02 PM ----------
Sorry got cut off on the above, so when I downloaded the files and made flash folder for the files, on flash it came up error on system imaging, that's file read system 12B rar now when I changed the name by removing the number, as directed, I bricked on flashing. So it has to do with that file.??im at a loss. I thank you a ton for the downgrade to 10b tho.
---------- Post added at 05:09 PM ---------- Previous post was at 05:08 PM ----------
And yes I'm rooted etc as direct with your downgrade.
---------- Post added at 05:13 PM ---------- Previous post was at 05:09 PM ----------
I have since unbridled by returning to stock, which is 10b again. Just don't want to mess up again, so trying to figure out why that system file(System12B rar) cannot or will not work. If left alone, that files flashes as an error, if I change the name, by taking out the number(12B) it bricks.
Correct spell is killing me, after I bricked trying to flash I dug around xda and managed to replace to 10b exactly like laser wolf has in this post(his picture matches my phone exactly), my problem now is not the zipped files, the other files are the problem, there all suppose to go into a file named flash, however on the download the system file had system12b. rar... According to the direction it should read system12b I'm, and directions say rename to system.img,,thats what I changed the name of the file to and it bricked, if I leave it as downloaded it flashes error on system img, I don't want to trial and error as I'm new to flashing files etc. Was wandering if anyone else downloads those files and gets a file named system12b. rar instead of system12b. img , and if so what am I suppose to do. Again sorry roadway warrior for not posting in the proper place, however this was where people were trying to go from 10b to 12b...ang help is appreciated!!!!
I didn't read all that. Sorry. I guess I don't understand what the purpose of a 12B rar is. If you want to be on 12B, root and put TWRP on 10B, then wipe and flash a 12B-based ROM like JasmineROM I think v2 or v3, or SkyDragon - probably the same, v2 or so.
By your description it sounds like this is some more difficult method.
Ok, thanks mate, been driving me crazy because that particular file means changing the name etc, but I will try your way.... Greatly appreciated my friend... Thanx
---------- Post added at 12:28 AM ---------- Previous post was at 12:27 AM ----------
Dang it, where will I find those rooms?, under your work??
Update, [email protected] guided thru the process step by step, much thanks to [email protected] and a special thanks to roadwarrior, used your method and guidance from laserwolf452, thanks guys I'm now on 12b and rooted

can i flash a 23b or 23c rom over stock 12b?

Hey guys, I i see that JasmineROM has some instructions on updated using an Installrom.sh file or something, when I updated to 23B (SkyDragon 3.0.0 to be exact) I just KDZ'd back to 10c, rooted and flashed a bump'd TWRP and than flashed the SkyDragon 3.0.0 full on top and everything seems to work. I have since tried a few different roms and am now on SlimLP, but I want to know if this is an ok way to upgrade? Is there any reason to use the JasmineROM's creator (I forget his name, sorry) update method with the installrom.sh over this method?
The InstallROM.sh method was for JasmineROM v5.0. 6.0 is just a normal flashable zip. Just flash it from TWRP, doesn't matter what you're on currently.
roirraW "edor" ehT said:
The InstallROM.sh method was for JasmineROM v5.0. 6.0 is just a normal flashable zip. Just flash it from TWRP, doesn't matter what you're on currently.
Click to expand...
Click to collapse
Okay, just to be sure, if I'm on stock 10c but rooted and twrp'd than I can just flash the jasmine ROM 6.0 and everything is good?
r3xx3r said:
Okay, just to be sure, if I'm on stock 10c but rooted and twrp'd than I can just flash the jasmine ROM 6.0 and everything is good?
Click to expand...
Click to collapse
i havent been following this closely, but i didnt think you would be able to flash up ever without installing the base first.
unless something changed, you would need to install the 5.0 base first, then you could flash 6.0, but you should verify, there may have been new developments i wasnt privy to.
r3xx3r said:
Okay, just to be sure, if I'm on stock 10c but rooted and twrp'd than I can just flash the jasmine ROM 6.0 and everything is good?
Click to expand...
Click to collapse
Yes. Honest. Triply sure. @hsbadr is additionally very complete and accurate in his instructions for flashing his ROMs, along with caveats if there were any, which there are none for 6.0.
bweN diorD said:
i havent been following this closely, but i didnt think you would be able to flash up ever without installing the base first.
unless something changed, you would need to install the 5.0 base first, then you could flash 6.0, but you should verify, there may have been new developments i wasnt privy to.
Click to expand...
Click to collapse
6.0 is the new base (of 23C). 5.0 of course, was 23B. 6.0 includes every single .img file from 100% complete stock 23C except it also has the 12B aboot.img and bump'd 23C kernel instead of the originals (for 23C) of those. The 6.0 zip includes all of said .img files and then additionally includes the file/folder structure necessary to modify them to mold them into what becomes debloated and tweaked JasmineROM 6.0.
This is why I was able to simply take the .img files out of his 6.0 zip and use them with his installROM.sh script from 5.0 in order to install complete 100% stock (system) 23C in an all-in-one working manner through TWRP's Terminal Command option in the Advanced menu since I like to debloat and tweak my own way. I manually flashed SuperSU.zip since obviously the stock .img files don't include root, and since I don't use anything from the 6.0 zip except the .img files, and it's the additional files in his 6.0 zip which do all the debloating and tweaking.
Sorry for repeating myself.
It's really great the way he's done it since anyone can (assuming having a reasonably up to date TWRP) get 23C installed.
Personally, I think Verizon is just having fun with us at this point.
roirraW "edor" ehT said:
Yes. Honest. Triply sure. @hsbadr is additionally very complete and accurate in his instructions for flashing his ROMs, along with caveats if there were any, which there are none for 6.0.
6.0 is the new base (of 23C). 5.0 of course, was 23B. 6.0 includes every single .img file from 100% complete stock 23C except it also has the 12B aboot.img and bump'd 23C kernel instead of the originals (for 23C) of those. The 6.0 zip includes all of said .img files and then additionally includes the file/folder structure necessary to modify them to mold them into what becomes debloated and tweaked JasmineROM 6.0.
This is why I was able to simply take the .img files out of his 6.0 zip and use them with his installROM.sh script from 5.0 in order to install complete 100% stock (system) 23C in an all-in-one working manner through TWRP's Terminal Command option in the Advanced menu since I like to debloat and tweak my own way. I manually flashed SuperSU.zip since obviously the stock .img files don't include root, and since I don't use anything from the 6.0 zip except the .img files, and it's the additional files in his 6.0 zip which do all the debloating and tweaking.
Sorry for repeating myself.
It's really great the way he's done it since anyone can (assuming having a reasonably up to date TWRP) get 23C installed.
Personally, I think Verizon is just having fun with us at this point.
Click to expand...
Click to collapse
thanks for explaining.
one question though, where did the unrooted system file come from?
root is required to pull the system, therefore its rooted by default.
just curious,
thanks
Thank you guys for the great explanations. I am still getting used to the G3. My old Galaxy S4 from T-mo was very different. I have another question now. If I want to run an AOSP rom, like SlimLP, would anything be different if I flashed JasmineROM 6.0 than SlimLP?? Do the basebands or anything like that change from 23b to 23c and would they stick between roms??
bweN diorD said:
thanks for explaining.
one question though, where did the unrooted system file come from?
root is required to pull the system, therefore its rooted by default.
just curious,
thanks
Click to expand...
Click to collapse
Anytime! I've wondered the same thing. I definitely didn't have SuperSU in my app drawer before I rebooted to TWRP and flashed SuperSU.zip. I meant to do that anyway but it's just as well I find out for sure that SuperSU wasn't installed. Perhaps the system.img is technically rooted but the SuperSU app was moved from system to data before pulling the image. So binaries, etc are still in the system.img but without the SuperSU app it's effectively not rooted.
But if that were the case, I could've merely installed SuperSU from the Play Store. I didn't try that so I won't know if that's the case until I have time to play with the phone more.
@HolyAngel, can you confirm if this is how the system.img by itself for 23A/B/C doesn't "appear" rooted?
If we had the KDZ, of course, then it would be a different story since we can extract the totally pure system.img as of course you already know (just saying for other reader's benefit).
r3xx3r said:
Thank you guys for the great explanations. I am still getting used to the G3. My old Galaxy S4 from T-mo was very different. I have another question now. If I want to run an AOSP rom, like SlimLP, would anything be different if I flashed JasmineROM 6.0 than SlimLP?? Do the basebands or anything like that change from 23b to 23c and would they stick between roms??
Click to expand...
Click to collapse
You're welcome! I understand. Came from the S3 and S2 before this myself. At least KDZ is reminiscent of Odin, although it sure was easier to get custom recovery and root installed with being able to flash custom recovery from Odin. I've wondered about building KDZ packages of custom recoveries, although it'd have to flash the 12B aboot.img and a bump'd kernel, too. Since we can extract KDZs, hopefully we can create them, too. Don't know how hard it is to get LG Mobile Tool 2014 to flash custom KDZs, though, or for the phone to accept them.
Sorry I digressed. So far, AOSP/CM ROMs need 12B's modem, they won't work with 23A/B/C's modems. You can get the 12B modem from @bweN diorD 's sticky thread in the General section.
So far all 23A/B/C ROMs flash the appropriate modem. Just backup the modem when you do nandroid backups.
Sent from my VK810 4G
roirraW "edor" ehT said:
Anytime! I've wondered the same thing. I definitely didn't have SuperSU in my app drawer before I rebooted to TWRP and flashed SuperSU.zip. I meant to do that anyway but it's just as well I find out for sure that SuperSU wasn't installed. Perhaps the system.img is technically rooted but the SuperSU app was moved from system to data before pulling the image. So binaries, etc are still in the system.img but without the SuperSU app it's effectively not rooted.
But if that were the case, I could've merely installed SuperSU from the Play Store. I didn't try that so I won't know if that's the case until I have time to play with the phone more.
@HolyAngel, can you confirm if this is how the system.img by itself for 23A/B/C doesn't "appear" rooted?
If we had the KDZ, of course, then it would be a different story since we can extract the totally pure system.img as of course you already know (just saying for other reader's benefit).
You're welcome! I understand. Came from the S3 and S2 before this myself. At least KDZ is reminiscent of Odin, although it sure was easier to get custom recovery and root installed with being able to flash custom recovery from Odin. I've wondered about building KDZ packages of custom recoveries, although it'd have to flash the 12B aboot.img and a bump'd kernel, too. Since we can extract KDZs, hopefully we can create them, too. Don't know how hard it is to get LG Mobile Tool 2014 to flash custom KDZs, though, or for the phone to accept them.
Sorry I digressed. So far, AOSP/CM ROMs need 12B's modem, they won't work with 23A/B/C's modems. You can get the 12B modem from @bweN diorD 's sticky thread in the General section.
So far all 23A/B/C ROMs flash the appropriate modem. Just backup the modem when you do nandroid backups.
Sent from my VK810 4G
Click to expand...
Click to collapse
Yea, most likely the su app wasn't system, and you just need to re-install it.

XDABBEB's VS985 - 3.1.1

!!! PLEASE READ THIS ENTIRE POST BEFORE PROCEEDING !!!
!!! I AM NOT RESPONSIBLE FOR ANY PROBLEMS THAT OCCUR WHILE INSTALLING/USING THIS !!!
Please follow the XDA rules. This is a development thread, not a Q & A or opinion thread. If your post isn't related directly to development (within reason), it will be ignored and/or reported to the moderators. Speculation/flaming/attacks/rants will not be tolerated.
This is a heavily modified/gutted stock LG fw based on their 48a release. My goal was to get as close to an AOSP weight as an OEM LG fw distro can get while still having everything work. I have also added functionality that wasn't present in the stock fw. Due to my schedule I won't have time to add different options for other people, etc. As the name implies, this is just how I run my phone.
Features:
Xdabbeb Kernel 3.0.0 w/kcal (thanks @savoca) and adrenoidler (thanks @arter97) support
Removed ALL unnecessary Verizon apps, checks, services
Removed most unnecessary LG apps
Removed/disabled/modified many system services, receivers/listeners, loggers, etc in framework and elsewhere
QuickButton hotkey customization (longpress Vol + from lockscreen and Capture+ navbar button)
EPM Reboot to recovery (longpress "Power off and restart")
Hotspost Provision mod for VZW UDP
Mini view
Multi-User
Call record
Call reject
Flashlight QuickSetting
Increased volume steps (30-music, 15-others)
Added photo/video resolutions to stock camera
Torch Toggle app (Set as quickbutton hotkey app to activate flashlight via Vol+ longpress from lock screen. More settings inside app)
Access to all VZW/LG Hidden menus, LTE band selection, network/carrier configs, etc (dial *#LGMENU#*985#, ##PROGRAM985, ##DEBUG, ##FEATURE, ##AATEST)
Extra fonts (including proper/full Roboto)
Remove mobile data type icon while Wi-Fi is active
More I can't remember
Click to expand...
Click to collapse
How to Install:
Peform a full nandroid backup.
Flash the 35B bootstack zip found below. I have provided 12b and 24b bootstack zips for use with other firmware.
Wipe data/cache within twrp. You should leave internal storage alone. If you fail perform this step and have any issues while running the firmware, start this whole install process again and follow this step before posting.
Flash the latest firmware version below after verifying the md5.
Kernel/Firmware options:
This is a trimmed down kernel built for speed/stability/efficiency.
Tune CAF touchboost by creating /sdcard/touchboost file and rebooting. If the file is empty, boost freq is 1036800 Hz. If you want a different one, just put the value inside the text file (no spaces). Valid options are (0, 422400, 652800, 729600, 883200, 960000, 1036800, 1190400, 1267200, 1497600, 1574400, 1728000, 1958400, 2265600, 2457600). ***NOTE: 0 = off
Tune LG's interactive gov more for battery life vs performance by creating /sdcard/battery file and rebooting.
Disable LG oversharpening (thanks to @savoca) by creating /sdcard/sharpfix file and rebooting.
Enable adreno idler by creating /sdcard/adrenoidler file and rebooting.
Enable SEAndroid permissive mode by creating /sdcard/permissive file and rebooting.
Toggle MultiUser on/off by creating /sdcard/multiuser file and rebooting TWICE
Toggle autorun popup with USB connection on/off by creating /sdcard/autorun file and rebooting TWICE
Toggle miracast on/off by creating /sdcard/miracast file and rebooting (by default this is OFF)
Disable even more apps (after initial setup ONLY) by creating /sdcard/disableapps and rebooting (revert by creating /sdcard/enableapps and rebooting) *NOTE: Among the apps disabled are LG's Home and Keyboard, so make sure you have 3rd-party ones installed first. View the full list and add your own by checking the contents of /system/etc/init.d/98xdabbeb
If you wish to restore data using Titanium Backup or some other app, you are welcome to do so, but if you encounter problems, you must follow these steps again WITHOUT restoring data before posting.
Click to expand...
Click to collapse
Changelog:
Version 3.1.1:
Fixed hotspot provision
Allow stock camera app UI to display properly @ BOTH 560/640 dpi
Version 3.1.0:
Updated bundled SuperSU to 2.78-SR1 to fix vulnerability
Added photo/video resolutions to stock camera app
Fixed stock camera app UI to display properly @ 560 dpi
Version 3.0.0:
Initial MM Release
Version 2.0.0:
Initial LP Release - KK release (1.0.0) was/is only for my testing
Click to expand...
Click to collapse
Downloads:
NOTE: AFH provides md5 checksums of all downloads on their site. Please verify them before installing.
Bootstacks:
35B
24B
12B
Firmware/Patches:
XDABBEB's VS985 3.1.1
XDABBEB's VS985 2.0.0
2.0.0 Add-ons/Mods:
35B VVM
35B File Manager
3Minit battery mod + remove Lockscreen circle - courtesy of @netookska05
Click to expand...
Click to collapse
Thanks:
Brut.all & iBotPeaches - apktool
JesusFreke - smali/baksmali
Team Codefire - bump
Team Win - TWRP
Click to expand...
Click to collapse
Before posting about any issues, make sure that you have followed the install directions explicitly (including wiping data and NOT restoring backed-up data). If you are using a 3rd-party kernel, you must revert to the included kernel first. You must provide DETAILED steps to reproduce the issue along with a log if appropriate or your post will be ignored/moved/deleted/etc. If you don't know how to get a log, HERE is a good tutorial. There is also an excellent app available on the Play Store called SysLog that you can use on your phone.
Devs: I will provide flashable zips or tutorials for any included apps/modifications that I intend to share. I do not authorize anything else to be shared, used or uploaded elsewhere.
XDA:DevDB Information
XDABBEB's VS985, ROM for the Verizon LG G3
Contributors
xdabbeb
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: VS98535B Bootstack
Based On: Stock LG fw
Version Information
Status: Stable
Current Stable Version: 3.1.1
Stable Release Date: 2016-09-20
Created 2015-10-22
Last Updated 2016-09-20
Reserved
FAQ:
What's a bootstack?
Our devices have a number of partitions that all work together to give us a functioning smartphone. Every time LG releases a new firmware there are certain partitions that get updated (aboot, dbi, factory, laf, modem, rpm, sbl1, tz). This subset of partitions was given the arbitrary label "bootstack" at one point and the term stuck. They have been grouped together here in flashable zips and are referenced by their corresponding official LG version code (12b, 24b, 35b).
NOTE: Though the "modem" and "aboot" (bootloader) partitions are included, these terms are NOT synonymous with bootstack.
Which bootstack do I need?
You want the one that your firmware (in particular the kernel and certain binaries) is made to work with. This firmware is made to work with the 35b set of partitions. Other kernels/roms may want to see a 24b set of partitions. A KitKat 12b-based rom will want the 12b set, etc etc. It's up to the dev to declare which one is appropriate.
What are all of these partitions?
An in-depth analysis of them is beyond the scope of this thread, so if you're really interested I suggest doing your own research. VERY briefly, however: aboot = bootloader, dbi = qcom data bus inversion/signaling, factory = bootable/haven't looked into it much, laf = bootable/download mode, modem = self-explanatory, persist = ext4/store persistent info across updates (rooted flags, etc), rct = more root check, rpm = elf binary/power management, sbl1 = secondary boot loader/QCom secure boot, tz = elf binary/QCom trustzone secure exec
Will I lose root or ability to get into recovery if I flash one of the bootstack zips?
No. Each of the zips I have posted still has the exploitable 12b aboot (bootloader) so you're fine. If you overthink it and muck something up, that's beyond my control, however.
I really liked "X" LG/Verizon feature/app. Can you add it back for me?
Sorry, but I won't. In addition to the fact that I have limited time for this sort of thing, that's not the point of this fw. Though I have added a number of features that aren't in LG's stock distro, I spent even more time removing what I felt was unecessary/gimmicky. Though you're welcome to tailor it after the fact to your liking, I would caution that it often isn't simply a matter of putting an apk back in place. I have made changes throughout the framework, kernel, etc to reduce the overhead and increase the performance/multitasking of this fw. It's much closer to AOSP in terms of weight, while still maintaining the reliability of stock fw. If you wish to create a patch/zip (and test it thoroughly yourself first) to add certain things back in I would be happy to add it to the OP as an add-on.
Click to expand...
Click to collapse
Reserved
Great to see ya here! I was a loyal follower on the G2!
Awesome, thanks xdabbeb. Did you modify the 35b bootstack so we can use the 35b modem and custom recovery? Cause that would be hot.
bigdwg71 said:
Awesome, thanks xdabbeb. Did you modify the 35b bootstack so we can use the 35b modem and custom recovery? Cause that would be hot.
Click to expand...
Click to collapse
A fellow Bostonian! Nice.
Yes, it's the full 35b bootstack (obviously minus the 12b bump-friendly bootloader). Your existing recovery will work just fine with it. I've been on it for a week and everything works properly (including HD Voice/Video).
Ha! Go Pats!
So what do we lose them without the bump'd boatloader? I thought that was pretty crucial to custom roms with LGs.
I'm incredibly intrigued. I might just have to flash this later..
Does this flash like an ordinary ROM? Will I be able to revert to a different ROM easily?
Ha. Yes, indeed #pinkstripes
I think you may have a misunderstanding of what bump is/does. The BL is not ever what is "bumped"...it's the bootable partitions (boot, recovery, etc). The reason you need to stick with the older/KK 12b bootloader is that LG patched the exploit starting with their LP fw releases on both G2 and G3. I just took a quick look around and it doesn't seem that anyone really put together the appropriate sets of partitions (bootstacks) for the VS985 users, so you can use the three above for everything you need. If you want to have a better understanding of what a bootstack is, etc, read the sticky resources thread I have the top of the VS980 dev section.
tl;dr You aren't losing anything.
robrabbitman said:
Does this flash like an ordinary ROM? Will I be able to revert to a different ROM easily?
Click to expand...
Click to collapse
yes x2
Yay! Xdabbeb is on the lg g3 now! ?
xdabbeb said:
Ha. Yes, indeed #pinkstripes
I think you may have a misunderstanding of what bump is/does. The BL is not ever what is "bumped"...it's the bootable partitions (boot, recovery, etc). The reason you need to stick with the older/KK 12b bootloader is that LG patched the exploit starting with their LP fw releases on both G2 and G3. I just took a quick look around and it doesn't seem that anyone really put together the appropriate sets of partitions (bootstacks) for the VS985 users, so you can use the three above for everything you need. If you want to have a better understanding of what a bootstack is, etc, read the sticky resources thread I have the top of the VS980 dev section.
tl;dr You aren't losing anything.
yes x2
Click to expand...
Click to collapse
Thanks xdabbeb! I'll check it out.
xdabbeb said:
Ha. Yes, indeed #pinkstripes
I think you may have a misunderstanding of what bump is/does. The BL is not ever what is "bumped"...it's the bootable partitions (boot, recovery, etc). The reason you need to stick with the older/KK 12b bootloader is that LG patched the exploit starting with their LP fw releases on both G2 and G3. I just took a quick look around and it doesn't seem that anyone really put together the appropriate sets of partitions (bootstacks) for the VS985 users, so you can use the three above for everything you need. If you want to have a better understanding of what a bootstack is, etc, read the sticky resources thread I have the top of the VS980 dev section.
tl;dr You aren't losing anything.
yes x2
Click to expand...
Click to collapse
So if I'm on a 12b bootloader I can just flash the Rom?
@xdabbeb Flashed per your instructions and set up ok. Restored a nandroid of SD and had no data. Do we need to flash the 24B modem with the restore or the 35B bootstack with the restore? Restored your nandroid and have data again. Been running since last nite all i good so far. Thanks
Just for clarity If I restored my stock rom. My phone would be on 10b. Would I have to upgrade to 12b prior to flashing 35 bootstack, in order to revert back with the 12b bootstack? I like to have a back up plan in place in case of mishaps. Thanks
mopartonyg said:
Flashed per your instructions and set up ok. Restored a nandroid of SD and had no data. Do we need to flash the 24B modem with the restore? Restored your nandroid and have data again.
Click to expand...
Click to collapse
I believe you'll need to flash the appropriate Bootstack for the ROM. ie 12b or 24b
ok dumb question, where do you create the files for the options? Sorry
mopartonyg said:
ok dumb question, where do you create the files for the options? Sorry
Click to expand...
Click to collapse
In the root of your internal storage.
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
Droid1177 said:
Just for clarity If I restored my stock rom. My phone would be on 10b. Would I have to upgrade to 12b prior to flashing 35 bootstack, in order to revert back with the 12b bootstack? I like to have a back up plan in place in case of mishaps. Thanks
Click to expand...
Click to collapse
No, you don't need to. You can just flash the appropriate bootstack for the firmware you're looking to use. Flashing the zip provides you with the full set of partitions while keeping your aboot/laf pair on the exploitable 12b version.
I highly recommend that people who still aren't quite clear on any of this please look up the resources thread I mentioned earlier and read it all carefully.
Thanks for the rom! Especially happy to see intelligent agent and lia informant and that other LG garbage gone. And to see the smaller navbar.
Hey so if I want f2fs formatted partitions, will it wipe my internal sd too if I try and format data as f2fs?

Categories

Resources