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.7zOTA: 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.7zOTA: 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.imgOTA: 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.7zOTA: 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.7zOTA: 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!
Related
Updated 2/3/16 Master Download Link Added at Bottom of This Post For All Old and Current KDZ's
This method is confirmed working 100% for devices running 10b/11c/12b/23abc regardless of root/unlock state. While the .tot method is also working on Windows 7, users with Windows 8.1 are having difficulty using that method. Myself and @autoprime obtained a 10b KDZ file that has solved the issue for +10b updaters that couldn't flash back to 10b, so please send him some love for his help and for hosting the file on Team Codefire's servers for all to download. A big shout out to @quangnhut123 for creating the super sweet modified LG KDZ Flash Tool 2014 that makes KDZ flashing an absolute breeze!! He deserves some love as the previous KDZ flashing methods were anything but fun - especially on Windows 8. And another shout out to @deathsquad737 for initially testing the method for our device.
-Please this post and second post FULLY before asking questions!
-First remove any of the .tot flashing tools/programs that you may have already installed as they will conflict with the KDZ flashing tool.
-Download and install the latest LG drivers for your phone here (FYI I am linking the LG site directly instead of the file to ensure that you download the current up-to-date drivers): http://www.lg.com/us/support-mobile/lg-VS985-Metallic-Black
-Download the VS985 10b KDZ: Downloads Located Below
-Download the LG Flash Tool 2014 from this thread here: http://forum.xda-developers.com/showthread.php?t=2797190 and be sure to thank @quangnhut123 for his efforts. Also read that thread a bit so you understand how to fully use the tool exactly, but I will outline the process below.
-Extract the .zip folder to wherever you wish to keep it (desktop, downloads, etc).
-Copy the 10b KDZ file (or whatever KDZ your flashing) into the LG Flash Tool folder
-Power off your phone completely, hold volume up, plug in the usb cable, wait for any drivers to load, and you should then be in Download Mode
-Run LGFlashTool2014.exe (you may need to run as administer as its not an installed program, rather an executed one from wherever you saved the folder).
-You may need to install Visual C++ Runtime Library. If so, refer to the LG Flash Tool thread for more info on obtaining that.
-Select CDMA as your type
-Select Diag as your phone mode
-Select your KDZ file that you copied or pasted into the folder
-Choose the option of CSE Flash (this is a full wipe, you will lose your data). Do not choose Normal Flash when performing a downgrade, nothing good will come from doing that!! Another screen will open, just leave everything the way it is.
-Click the Start button and yet another window will appear showing a language selection screen. Just leave everything the way it is as Korean and hit OK. Don't worry, the tool is already set to flash in English.
-Wait until the Flash is done 100% and unplug/reboot... and that's it - now enjoy your corrected mistake and stop taking OTA's!!!
KDZ files rock, and are nice and easy to flash. No separate DLL files or changing ports either with the tool linked. If any other KDZ files become available in the future I will add them to this post along with any tool or flashing method changes. This thread will be solely kept for KDZ flashing for the VS985. I will also help as much as I can if you run into trouble, though I am not a Windows expert and actually only boot into it when I have to run programs like this....Linux MInt FTW!!
~KDZ Downloads~
-VS98510b_01.kdz: http://downloads.codefi.re/autoprime/LG/LG_G3/VS985 -Thanks to @autoprime
-Mirror for VS98510b_01.kdz (10b): https://mega.co.nz/#!7ERgXJbI!2KxATJt7q-HWvAPbTfVrT3wGuwPjWCw70N65MVlgfWg md5: d228ba692ef0c4704cba0b00fad8b8c
-VS98512b_00.kdz: https://www.androidfilehost.com/?fid=95916177934537134 -Thanks to @hokiealumnus for the AFH hosting
-Mirror for VS98512b_00.kdz (12b): https://mega.co.nz/#!7AwylQiZ!vK6rumjP0r1eP7lN37oeJ_cWLwal1DnriGDPUZGW1-0 md5: e8280b279d327b96689579a9eca22a3e
New download link to all KDZ files thanks to @roirraW "edor" ehT https://www.androidfilehost.com/?w=files&flid=35484
-For reference, here's @ins5736 thread for restoring using the .tot method: http://forum.xda-developers.com/verizon-lg-g3/general/restore-verizon-to-stock-t2827878 .
-Also there are reports of the tool deleting the KDZ you copied to the Flash Tool folder after the flash. I cannot confirm this, as it did not happen to me, but to be safe make sure you copy the file to the folder instead of pasting it so that you don't have to re-download the file for future use.
-Please note that the KDZ file we have is build # 10B.01, while the .tot file available is build # 10b.03. The only difference between the 2 files is that the .03 build is the actual released build that shipped with the phone, while the .01 kdz build was obviously a pre-released build. Its most likely some minor last minute changes/bloat added. We can't find any noticeable differences between the 2 builds.
-OTA's WILL FAIL USING THE 10b KDZ FILE WE HAVE due to a signing error with it being a pre-release. The purpose here is to downgrade, unlock, and flash whatever you want. This is NOT to return to an official stock state. You'll need to use the .tot file or the official LG Flash Tool that downloads the current build automatically in order to be in an official "stock" state. The 12b kdz is official and will allow OTA's
*Error Update* So with this leaked LP image, I've been playing with kdz'ing quite a bit and with a new Windows install I got to experience a few of the issues being reported by others that I have never seen, along with trying to troubleshoot some others. Did I manage to fix them easily you ask?? Hell yeah!
USB Disconnected Issue: This is a driver issue. Very easy fix, just download the latest Verizon drivers from the link I posted above and install them without phone plugged in. Power off phone, hold up, plug into usb and WAIT for download mode drivers to install (as stated several times in this thread). Click the balloon to watch the progress, this took about 10min on an i5/ssd machine - be patient. This is the predominant issue I think people are having. The drivers while in download mode are:
-USB Composite Device
-LGE Android phone or LGE AndroidNet for VZW USB Serial Port COM5 (this is the important one)
-CDC Serial or LGE AndroidNet for VZW USB Modem (this will fail if you are on a rom with certain VZW items removed - not a problem, its not needed)
-CDC ECM LGE AndroidNet for VZW NDIS Ethernet Adapter
If driver install fails, manually update them by pointing windows to the driver file you downloaded. I am not going any further here, use Google.
??????'s In The Field: easy, don't change region or language from Korean as stated in the OP. Leave it alone, it will flash in English I promise you. Result = all fields readable in English while running
Connection To Server Failed: Simple, ignore the window. Just drag it away, but don't close it. This is an offline hack originally indented to run online, deal with the window!
Progress Bar: The tool will initially analyze the phone, then when flashing starts, pay attention to the phone screen which will now say COM5. The blue progress bar on the phone is the important one. At around 80% on the tool screen, the phone will reboot. The flash is over and the bar will continue to progress into the 99% while rebooting - then the program will crash. You can disconnect now, you've been successful.
Thanks for the help and the new guide
WHATSAMATTA U ALUMNI
I'm getting a message saying "Path is too long or file problem" when adding the kdz. Any ideas?
droidiac13 said:
I'm getting a message saying "Path is too long or file problem" when adding the kdz. Any ideas?
Click to expand...
Click to collapse
Sounds like your linking the file path instead of directly copying the file right into the folder. Also try checking the file md5 with this one for the 10b kdz file: d228ba692ef0c4704cba0b00fad8b8ce
Don't Forget To Remove Previous LG FlashTool
When I first tried the method I was receiving a message "Path is too long or file problem". So I read through the instructions again. I failed to remove the previous LG FlashTool I was using. Once I uninstalled that program, everything went through without a problem. Thanks annoyingduck!!
I keep getting this and I installed all drivers. Any ideas? Thanks
Sent from my VS985 4G using XDA Free mobile app
kreep22 said:
I keep getting this and I installed all drivers. Any ideas? Thanks
Sent from my VS985 4G using XDA Free mobile app
Click to expand...
Click to collapse
Some basics to check first:
-Were you in download mode before executing the program?
-When you initialized download mode, did you wait to allow the download mode drivers to load before hitting start?
-Were all steps followed?
-Check cable, and try another one (this is very often the cause)
-Change usb port
-Don't use a 3.0 port, use a 2.0
Thanks for this excellent guide, Duck. Very simple to follow, well laid out, etc. I haven't actually done it yet, but I've got everything in place to do so (the flash tool, the KDZ file in the folder, etc.)
I assume once the downgrade is successful, just reroot with Stump, etc and wait for updates via the community?
Will future updates be available via this flash tool, or will they have to be flashed via TWRP? Sorry, I'm just now getting used to the LG G3 dev community, coming from an old GNEX.
Thanks!
continued error when trying ota
I have a problem. I was originally rooted without a custom recovery. I decided to try the ota and got the error message when trying to install. I then flashed this method (kdz) and got back to stock. I rerooted via stump and tried the ota again, failure. I then rewiped and kdz again, this time I did not root. Tried the ota again, no dice.
Any thought? I can flash the kdz fine and get phone to factory 10b but once I try to install the ota I still get the error.
killian1212 said:
I have a problem. I was originally rooted without a custom recovery. I decided to try the ota and got the error message when trying to install. I then flashed this method (kdz) and got back to stock. I rerooted via stump and tried the ota again, failure. I then rewiped and kdz again, this time I did not root. Tried the ota again, no dice.
Any thought? I can flash the kdz fine and get phone to factory 10b but once I try to install the ota I still get the error.
Click to expand...
Click to collapse
That's odd... You chose cse flash, not normal correct? Normal would not wipe your device and could definitely be the culprit for the ota failing. While cse mode is a complete wipe prior to flashing.
Correct. I did cse, full wipe. I dont know what's going on. I tried atleast 10 times from scratch. I still cant get the ota to install.
killian1212 said:
I have a problem. I was originally rooted without a custom recovery. I decided to try the ota and got the error message when trying to install. I then flashed this method (kdz) and got back to stock. I rerooted via stump and tried the ota again, failure. I then rewiped and kdz again, this time I did not root. Tried the ota again, no dice.
Any thought? I can flash the kdz fine and get phone to factory 10b but once I try to install the ota I still get the error.
Click to expand...
Click to collapse
annoyingduck said:
That's odd... You chose cse flash, not normal correct? Normal would not wipe your device and could definitely be the culprit for the ota failing. While cse mode is a complete wipe prior to flashing.
Click to expand...
Click to collapse
After using the method here to downgrade back to 10b and root. I too wasn't able to then S/W update to 11c using survival mode in SuperSU. I perform the OP procedures again and this time didn't root and still wasn't able to S/W update, kept getting error. So I used ---> [GUIDE][HOW TO][VS985] Restore Verizon to Stock to go all the way back. I'm now able to S/W update to 11c and keep root with survival mode set in SuperSU. I most humbly say that there may be a very slight issue with maybe the files here. I truly do appreciate the ability to return to 10b using this method after updating in the first place!
Thanks, ill try the other method and report back. wish me luck. Either way, a huge thanks to duck for the easy way to rerturn. I just wish kdz worked for future ota. It may be a file issue allowing us to revert to 10b but not then allowing future updates.
Use the kdz method then factory reset the device and see if that works.
I tried that. No dice.
annoyingduck said:
Use the kdz method then factory reset the device and see if that works.
Click to expand...
Click to collapse
I tried that as well.
gatorstew said:
Thanks for this excellent guide, Duck. Very simple to follow, well laid out, etc. I haven't actually done it yet, but I've got everything in place to do so (the flash tool, the KDZ file in the folder, etc.)
I assume once the downgrade is successful, just reroot with Stump, etc and wait for updates via the community?
Will future updates be available via this flash tool, or will they have to be flashed via TWRP? Sorry, I'm just now getting used to the LG G3 dev community, coming from an old GNEX.
Thanks!
Click to expand...
Click to collapse
Sorry, I missed this question. Yes, any future kdz's that become available will be updated here, along with any changes in flashing methods. Though it's pretty hard to beat the current tool that's available.
And yes, the idea here is to downgrade to 10b and be able to root, unlock, and flash anything you want. Still unclear as to why some want to take the 11c ota, but that's for another thread. The kdz method here is working where the tot was failing for some, and I personally think it's faster and easier to do than the tot method.
The third step might be clarified. Do you mean something like, "Power off your phone completely, then turn power on while also holding the volume up button..."?
markfm said:
The third step might be clarified. Do you mean something like, "Power off your phone completely, then turn power on while also holding the volume up button..."?
Click to expand...
Click to collapse
You should probably try it before trying to correct it.....
Nope, power off phone completely, hold volume up ONLY, plug in usb cable...it will auto power on into download mode
*WARNING* - There have been at least two known hard bricks using this method. It has worked successfully for many people, including myself three times. However, with two hard bricks, this isn't something to go into without at least considering the possibility. The standard warning has always been in this thread (second paragraph), but consider yourself doubly warned. Now that we have root and TWRP on 5.0 stock, this method is all but obsolete. We're just waiting on the good devs to bring us superb Lollipop stock ROMs like SkyDragon by @HolyAngel and Jasmine by @hsbadr. Once those are out, this method should really only be used if you need "official" software on your phone. Or you can just wait for Verizon to push the actual OTA, which is probably technically safer than any custom flashing methods there are.
--------------------------------------------------------------------
**NOTE** - There are two stellar custom-stock ROMs here in the form of Jasmine v.5.0 and SkyDragon 3.0.0. There is no longer any need to use this method to upgrade to stock LP unless you just really need the software status to say "official". Download link & instructions at the following links:
SkyDragon G3 VS985 Edition Version 3.0.0
JasmineROM v5.0 Release [LP] [Stock] [Rooted] [Unmodified]
--------------------------------------------------------------------
Are you still here after reading that warning and looking at the great custom options? Read post # 148, then, if you really insist on being so daring as to try an obsolete method, I guess proceed on. Best of luck to you.
--------------------------------------------------------------------
For starters, this thread may be deemed unnecessary and/or redundant. If so, please accept my apologies and mods feel free to close the thread. This is an extension of this thread started by @annoyingduck. It's a start-to-finish way to flash 23A and keep all your apps. Rather than linking threads here, there and everywhere, I've compiled everything and put it all in one place, to try and keep down the number of questions in that thread (which is really supposed to be for devs to assist them in getting the info they need to make the wonderful stock ROMs we've all come to know and love). NONE of this information is original to me. I'm not that smart. All credit goes to the respective posters listed below.
Now, the usual disclaimer - I am not responsible if you brick your device by using any or all methods outlined below. They worked for me. They may or may not work for you. If you go down this path, you do so at your own risk and/or peril. Don't come crying to me in the unlikely event you can't figure it out or kill your phone!
Also, please take note right here right now, as this question will never be answered again by me in this thread. There is currently NO ROOT on 23A. Root will NOT be retained when you upgrade (in fact, it will be lost at the 12B KDZ step). Further, we do NOT know how to root stock Lollipop on Verizon at this point. So to answer your questions: NO, you will not have root on 23A at all, period, no matter what, until some smart dev is able to come up with a way to root it.
The good news is that you can downgrade back to 10B (the only root-able version) at any time and get back to rooted goodness and flashing rooted stock-KK or AOSP-Lollipop. I'm hopeful we'll get root eventually for stock Lollipop, but it's too soon for that.
First, you need to download several files. The first several have to do with KDZ'ing back to 10B, followed by 12B (you WILL LOSE DATA going back to 10B...back up everything!).
Things you will need:
Drivers from LG for the G3.
Two files from this download page - the 10B KDZ file (VS98510B_01.kdz) and the 23A update file (LG_VS985_12B-23A.dlpkgfile).
NEW 3/6/15 - The 23B (should be an OFFICIAL LP build) update is available here. Same as before, rename to .up and put it in the Software Update folder. Update from 12B stock.
The 12B KDZ file. (Alternate mirror.)
The LG Flash Tool 2014 (originally from this thread).
Now that you have those, we can move on to the directions. To KDZ back to 10B (followed by 12B after a few interim steps), you need to follow the procedure outlined here by annoyingduck. I'm quoting everything so it's all in one post, but linking back so those who made it get all the credit.
When flashing the 10B KDZ, you must use the "CSE Flash" option, because you're downgrading and getting rid of everything on your phone. You will lose ALL data, so copy your TiBu folder, your photos, files, etc. elsewhere first.
annoyingduck said:
-First remove any of the .tot flashing tools/programs that you may have already installed as they will conflict with the KDZ flashing tool.
-Download and install the latest LG drivers for your phone here (FYI I am linking the LG site directly instead of the file to ensure that you download the current up-to-date drivers): http://www.lg.com/us/support-mobile/lg-VS985-Metallic-Black
-Download the VS985 10b KDZ file from here: http://downloads.codefi.re/autoprime/LG/LG_G3/VS985 and thank @autoprime in whatever manner you deem fit.
-*New* Mirror for 10b.01 KDZ: https://mega.co.nz/#!7ERgXJbI!2KxATJt7q-HWvAPbTfVrT3wGuwPjWCw70N65MVlgfWg md5: d228ba692ef0c4704cba0b00fad8b8ce
-Download the LG Flash Tool 2014 from this thread here: http://forum.xda-developers.com/showthread.php?t=2797190 and be sure to thank @quangnhut123 for his efforts. Also read that thread a bit so you understand how to fully use the tool exactly, but I will outline the process below.
-Extract the .zip folder to wherever you wish to keep it (desktop, downloads, etc).
-Copy the 10b KDZ file (or whatever KDZ your flashing) into the LG Flash Tool folder
-Power off your phone completely, hold volume up, plug in the usb cable, wait for any drivers to load, and you should then be in Download Mode
-Run LGFlashTool2014.exe (you may need to run as administer as its not an installed program, rather an executed one from wherever you saved the folder).
-You may need to install Visual C++ Runtime Library. If so, refer to the LG Flash Tool thread for more info on obtaining that.
-Select CDMA as your type
-Select Diag as your phone mode
-Select your KDZ file that you copied or pasted into the folder
-Choose the option of CSE Flash (this is a full wipe, you will lose your data). Do not choose Normal Flash when performing a downgrade, nothing good will come from doing that!! Another screen will open, just leave everything the way it is.
-Click the Start button and yet another window will appear showing a language selection screen. Just leave everything the way it is as Korean and hit OK. Don't worry, the tool is already set to flash in English.
-Wait until the Flash is done 100% and unplug/reboot... and that's it
Click to expand...
Click to collapse
Ok, now that you're back to 10B, it's time to do some work there. You need to root your phone, install Titanium Backup and restore your backed up apps & their data. I prefer to use the IOroot method. So root, then install all your apps. After that, it's time to update to 12B. You're doing the same thing you did with 10B, except this time you are choosing "Normal Flash", not CSE flash, because you're upgrading. Once you've done that, you will be upgraded to 12B and will have lost root. Here is more from annoyingduck:
annoyingduck said:
-Restore apps, and select system data items you want restored (aka: call log, sms/mms messages, wifi access points, bluetooth pairings) via Titanium
-KDZ to 12b, but this time choose NORMAL flash. No bootloops because it's an upgrade
-Root is now lost, but atleast all your apps and data are already there
Click to expand...
Click to collapse
Now we're going to update to 23A using a method described here by justiz33.
justiz33 said:
Do not attempt unless you are sure of yourself and have a high percentage of battery left.
if you are on 12B and NONROOT, you can put the update on /storage/external_SD/SoftwareUpdate/23A.up (**hokie note - FYI, I had to put mine on the internal SD in a SoftwareUpdate folder for this to work; it wouldn't flash when on the external SD card. Don't forget to rename your update downloaded above to "23A.up")
then download and install Activity Launcher (**hokie note - Here's a play store link.)
then in Activity Launcher use the drop down to switch between ALL ACTIVITY.
scroll down to the bottom area and look for either 'Software Update' or com.lge.permission (**hokie note - Mine was titled a little differently, something like com.lge.fotaupdate.permission.)
click the dropdown and expand the list.
look for DmcEzUpdateStart and click it.
You should be on a black screen with FOTA UPDATE written, just sit on that screen and wait 3 min and it will then say 'Shutting Down'
It should reboot and start the update.
Click to expand...
Click to collapse
Now we'll let annoyingduck take us home.
annoyingduck said:
-Be prepared to wait a while while all that bloat and user apps optimize in ART!!
-Put your internal sd card data you pulled earlier back on your phone
-Cry now, because its a nice build and your stuck without root. No more saving your app data with Titanium or removing the load of ****e Verizon has put into it...... unless a root method is found.
-You can KDZ or TOT back to stock, re-root, bump recovery, flash 12b radio, and restore your backup if you can't live without root....which I will be doing again shortly because my OCD won't allow me to function with apps like NFL mobile embedded in my phone!! Just wanted to outline a method for you guys.
Click to expand...
Click to collapse
So there you have it, you're on Verizon official stock Lollipop (23A) for the G3! Now, there's a lot of bloat on there, which you can disable at will. This is a list of apps that are safe to disable, courtesy roirraW "edor" ehT and typed up by yours truly.
Can Be Uninstalled said:
Farmville
iHeartRadio
Click to expand...
Click to collapse
Can Be Disabled said:
Amazon
Amazon app suite
Amazon Kindle
Amazon MP3
Appstore
Audible
Cloud
DT Ignite
FamilyBase Companion
Favorite Contacts Widget
FIle Manager
Google Play Books
Google Play Games
Google Play Movies & TV
Google Play Music
Google Play Newsstand
Google+
LG TTS+
Message+
Music
Music
My InfoZone
My Verizon Mobile
NFL Mobile
SLacker
Support & Protection
Verizion Location Agent
VZ Navigator
Click to expand...
Click to collapse
After disabling most of that (I think I left one or two I use on, like G+, Google Books, etc), my G3 is happily up & running without issue. Some have discovered issues with their installs.
The only issue I've had is gmail not syncing on WiFi. I've tried everything I (and the community) can think of and am unable to fix the no-notifications-on-WiFi bug. Unfortunately I'm not alone, but it doesn't affect everyone. So, be forewarned, this is a semi-widespread bug. Everything else I experienced about this build is absolutely wonderful, save for that one bug.
Once you're done, you should be greeted by some notifications similar to these...and a software info screen that looks like this. With the bloat disabled, Antutu treated me well with a score over 41K. That's without any tweaking at all obviously since there is no root yet. I only miss two things about root - Titanium Backup and the ability to change DPI (to my preferred 600). Aside from that and the bloat (which is disabled), I'm quite happy as it is.
There you have it folks...if you want to be an early stock Lollipop adopter on the Verizon G3, this is how to do it! To answer the other inevitable question, yes you can downgrade back to 10B, root and install bumped TWRP without issue.
Special thanks to @annoyingduck for most everything how-to above, @justiz33 for the easy 12B-to-23A path, @roirraW "edor" ehT for the safe-to-disable list, Team Codefire for the files, @autoprime for IOroot & @quangnhut123 for the LG Flash Tool. If any one of you takes issue with how your posts are represented, please don't hesitate to PM me and I'll do what it takes to fix it.
Last, but not least, please do not quote this entire ginormous post in responses. It's unnecessary and insane. Thanks in advance. :fingers-crossed:
Do you have the MD5 for LG_VS985_12B-23A.dlpkgfile? (The update 12B to 23A MD5sum) i cant seem to find it but mine is
478a14b37b34e353722022e547fb2894
KShion619 said:
Do you have the MD5 for LG_VS985_12B-23A.dlpkgfile? (The update 12B to 23A MD5sum) i cant seem to find it but mine is
478a14b37b34e353722022e547fb2894
Click to expand...
Click to collapse
I just downloaded it again on my PC and checked the one on my phone. Both match: 85f01bfdefb4615328a29300a3625b64
Well this is new, and nifty.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, fyi, disabling and re-enabling account sync did NOT fix my Wi-Fi gmail sync problem. Deleting and re-adding my Google account didn't either. Hate it, but I might have to try a factory reset. Perish the thought.
EDIT - Battery life is looking pretty darn good to me too.
I have the world's worst Windows machine and I'm having problems with the LG flash tool working. It just freezes every time I try and use it. I'm currently on the 11c build and with root and TWRP. Could I just restore the stock recovery, take the OTA to 12b, unroot within superuser, and then use the above method to get to lollipop?
jlvlawrence said:
I have the world's worst Windows machine and I'm having problems with the LG flash tool working. It just freezes every time I try and use it. I'm currently on the 11c build and with root and TWRP. Could I just restore the stock recovery, take the OTA to 12b, unroot within superuser, and then use the above method to get to lollipop?
Click to expand...
Click to collapse
If you're able to do that, I don't see why it wouldn't work; but I don't think it has been tried, at least that I've seen, so you'd be the guinea pig.
As far as flash tool, do you have any TOT flashing tools/programs installed? Are you sure the driver is properly installed? Try seeing if you can see your device with adb. It comes with the ioroot package linked in the OP. Enable USB debugging, plug it in and set it to internet/ethernet mode. Then launch a command prompt in the adb folder and see if you can see your device by typing "adb devices".
hokiealumnus said:
If you're able to do that, I don't see why it wouldn't work; but I don't think it has been tried, at least that I've seen, so you'd be the guinea pig.
As far as flash tool, do you have any TOT flashing tools/programs installed? Are you sure the driver is properly installed? Try seeing if you can see your device with adb. It comes with the ioroot package linked in the OP. Enable USB debugging, plug it in and set it to internet/ethernet mode. Then launch a command prompt in the adb folder and see if you can see your device by typing "adb devices".
Click to expand...
Click to collapse
Well, I wasn't able to OTA from 11c to 12b. I keep getting an error. My issue with the flash tool is it freezes before the flash process. It freezes at around 7 percent after plugging the phone in. Im pretty sure the drivers are correctly installed.
jlvlawrence said:
Well, I wasn't able to OTA from 11c to 12b. I keep getting an error. My issue with the flash tool is it freezes before the flash process. It freezes at around 7 percent after plugging the phone in. Im pretty sure the drivers are correctly installed.
Click to expand...
Click to collapse
Hmm. Sorry; without being at your computer to play with it, there isn't a whole lot I can think of other than the drivers. Did you check whether you can access the phone via adb?
hokiealumnus said:
Hmm. Sorry; without being at your computer to play with it, there isn't a whole lot I can think of other than the drivers. Did you check whether you can access the phone via adb?
Click to expand...
Click to collapse
I'll check when I get home and see if adb is working. Thanks for your help.
hokiealumnus said:
The only issue I've had is gmail not syncing on WiFi. I turned off, then re-enabled account syncing. I'll report back if that doesn't fix it when I'm back on WiFi.
Click to expand...
Click to collapse
A resolution has been had! Deleting my google account didn't work, nor did toggling sync. What worked was a kind suggestion by @Crsdr37 from the bug thread.
Crsdr37 said:
Use the built in LG backup app. Do a factory reset through settings and your sync issues should be resolved was for me anyways.
Click to expand...
Click to collapse
hokiealumnus said:
I'll give that a try, thanks! I honestly just ignored the built-in backup and didn't realize it would do downloaded apps. That's quite handy. Thanks for the tip, I'll report back whether it works. :fingers-crossed:
Click to expand...
Click to collapse
hokiealumnus said:
Wow, that worked incredibly well; pretty much equally as good as TiBu. Seems it fixed my gmail-on-wifi issue too. Thanks for the tip!
Click to expand...
Click to collapse
Like I said there, that thing is just as good as TiBu. Now the only real reason I miss root is the inability to change DPI. Sure, I'd rather have it de-bloated than have to disable a bunch of stuff, but disabled is nearly as good. I'm very pleased with this build.
Now @hsbadr & @HolyAngel are working diligently to try and get a custom stock ROM going for us, but in the mean time I'm happy to stick it out on unrooted stock. For now.
Thanks - this worked great. Software status says modified, is there a way to change that back since we're stock again?
hokiealumnus said:
Hmm. Sorry; without being at your computer to play with it, there isn't a whole lot I can think of other than the drivers. Did you check whether you can access the phone via adb?
Click to expand...
Click to collapse
So this is where I get stuck within the flash tool.
Ignite023 said:
Thanks - this worked great. Software status says modified, is there a way to change that back since we're stock again?
Click to expand...
Click to collapse
Huh...good question. Following the path above, mine says Official. Screenshot is here. You're not the first to report that though, so I'm not really sure what makes the difference, sorry.
hokiealumnus said:
Huh...good question. Following the path above, mine says Official. Screenshot is here. You're not the first to report that though, so I'm not really sure what makes the difference, sorry.
Click to expand...
Click to collapse
I don't know if this is the case here, but I think I've noticed even someone's rooted and they successfully unroot and restore stock everything, something is left behind and the status is modified, whereas if going straight from completely stock to 23A results in Official.
Sent from my VK810 4G
roirraW "edor" ehT said:
I don't know if this is the case here, but I think I've noticed even someone's rooted and they successfully unroot and restore stock everything, something is left behind and the status is modified, whereas if going straight from completely stock to 23A results in Official.
Sent from my VK810 4G
Click to expand...
Click to collapse
Very interesting. Using the method in the OP I was indeed rooted on 10B to install my apps with TiBu, then the upgrade to 12B took root away (leaving the apps). I wonder if it has to do with the method for root? Could stump root be different than ioroot maybe?
@jlvlawrence, what method did you use to root on 10B?
hokiealumnus said:
Very interesting. Using the method in the OP I was indeed rooted on 10B to install my apps with TiBu, then the upgrade to 12B took root away (leaving the apps). I wonder if it has to do with the method for root? Could stump root be different than ioroot maybe?
@jlvlawrence, what method did you use to root on 10B?
Click to expand...
Click to collapse
Mine's on official. I wasn't sure until I checked. I had my apps installed with Titanium Backup under 12B before I flashed the OTA. After trying it out I found my WIFI was constantly trying to turn on, so I did a factory reset and it was good after that.
I used Stump under 10B, for the record.
My phone overall seems snappier from the factory reset. It's probably a good idea for folks to so, period.
KDZ to 10B, root & restore apps, KDZ to 12B, initiate OTA to 23A, backup with LG utility, factory reset, login and restore from LG backup.
Sounds like a lot, but it is worth it, at least IMHO.
hokiealumnus said:
My phone overall seems snappier from the factory reset. It's probably a good idea for folks to so, period.
KDZ to 10B, root & restore apps, KDZ to 12B, initiate OTA to 23A, backup with LG utility, factory reset, login and restore from LG backup.
Sounds like a lot, but it is worth it, at least IMHO.
Click to expand...
Click to collapse
Doesn't 12B have the LG Backup too? Save restoring with TB if so. Might have to play with this.
Huh, not sure.
...and darnit, not getting notifications again. There must be something in the backup. I'll try it again and only back up my apps with nothing else and see if that fixes it.
I know it successfully got an email before restoring the backup. Hmm. Might have to just download the apps fresh the lollipop way. Hate to lose that data though.
hokiealumnus said:
Huh, not sure.
...and darnit, not getting notifications again. There must be something in the backup. I'll try it again and only back up my apps with nothing else and see if that fixes it.
I know it successfully got an email before restoring the backup. Hmm. Might have to just download the apps fresh the lollipop way. Hate to lose that data though.
Click to expand...
Click to collapse
Keep us posted if you make any progress on eliminating the quirks.
[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 requiredDebloat 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...
Hey all, ran into a (probably rookie) mistake yesterday.
I was running my phone on Cyan13 with 35B and decided, after seeing how popular it was, to check out JasmineROM 9.1. I downloaded the ROM files, 9.0 and 9.1 as well as some of the ancillary files, copied them to my phone and started the install process. I flashed 9.0, then 9.1 and then rebooted...my phone went blank.
You could see that the phone was still "working" but the screen was completely blank. I could take screenshots with power + vol down like normal, and hear the sound. Plus I could type on the screen (i could hear the touch tones), but the screen itself was completely black. Even during reboots you couldn't see the LG logo and since it was a new ROM I didn't have usb debugging on so I couldn't (assumed anyways) get into adb from my computer either.
After some digging, I ended up doing the following...as much of a PITA it was, it worked and I'm extremely thankful for the posts here on XDA and all of the contributors...so follow along if you're having this issue and you should be good to go.
Run the process found here with BoardDiag and TOT (I used the 10B.03 file found here --- http://forum.xda-developers.com/verizon-lg-g3/development/tot-vs985-10b-share-t2832488) (also yes the site says for Sprint, it works on Verizon as well) --- http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Then use the LG Flash Tool found here to flash the 12B KDZ firmware (make sure you download the 12B file) --- http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
Go into the app store after your phone boots and install King Root --- http://www.kingroot.net/
Install TWRP from here --- http://forum.xda-developers.com/ver...recovery-twrp-touch-recovery-2-8-2-0-t2966014
Start doing your own thing again
Remember that you're on 12B at this point. The All in One tool found here --- http://forum.xda-developers.com/verizon-lg-g3/general/verizon-lg-g3-one-toolkit-vs985-root-t3124846 --- did NOT work for me for some reason, probably the various drivers that are required. That's why I used King Root.
Hope this helps someone.
The problem was that you had the 35B bootstack flashed before JasmineROM. JasmineROM (and SkyDragon) contain some older partitions. If you flash the 35B bootstack after its fine, even if you already had the 35B bootstack flashed before the ROM.
You didn't have to use BoardDiag. Even though the screen didn't show anything it still gets in Download mode.
Edit: my info regarding Download mode is not applicable in these users' case - they confirmed they couldn't get into Download mode no matter what. Sorry for the confusion.
For some reason mine wasn't entering download mode. Even without the screen showing I could see the LED flashing and then if you tapped the screen you'd hear the touchstone sounds. It was strange but it's fixed now.
roirraW "edor" ehT said:
The problem was that you had the 35B bootstack flashed before JasmineROM. JasmineROM (and SkyDragon) contain some older partitions. If you flash the 35B bootstack after its fine, even if you already had the 35B bootstack flashed before the ROM.
You didn't have to use BoardDiag. Even though the screen didn't show anything it still gets in Download mode.
Click to expand...
Click to collapse
Are you sure? Mine would not go into dl mode and I tried both TOT and KDZ methods.
CaptainElwood said:
Are you sure? Mine would not go into dl mode and I tried both TOT and KDZ methods.
Click to expand...
Click to collapse
You tried the board diag method? Make sure you're getting a good ground on the board and hold it for a few seconds...basically while holding the wire and attaching the USB cable to the computer watch device manager, specifically under the COM port section. Once you see the phone show up you can remove the wire, being careful not to touch any of the other pins. If you're running Vista or newer you must use the bcdedit commands from that post AND reboot into F8 and select disable driver signing (can't remember the exact verbiage).
Once you're done, I'd reverse those bcdedit commands BTW. Just a thought for the cleanup process.
malhovic said:
For some reason mine wasn't entering download mode. Even without the screen showing I could see the LED flashing and then if you tapped the screen you'd hear the touchstone sounds. It was strange but it's fixed now.
Click to expand...
Click to collapse
CaptainElwood said:
Are you sure? Mine would not go into dl mode and I tried both TOT and KDZ methods.
Click to expand...
Click to collapse
My mistake, sorry!
roirraW "edor" ehT said:
My mistake, sorry!
Click to expand...
Click to collapse
No need to be sorry, sometimes things act differently all depending on the steps people took with their devices. I was really hoping it would pop into download mode so I didn't have to run BoardDiag as I didn't feel like taking things apart (save for the back off so I could get to the battery).
Either way, hopefully the idea works for someone else so they don't have to go through all the extra steps that I (and others) have. :laugh:
malhovic said:
No need to be sorry, sometimes things act differently all depending on the steps people took with their devices. I was really hoping it would pop into download mode so I didn't have to run BoardDiag as I didn't feel like taking things apart (save for the back off so I could get to the battery).
Either way, hopefully the idea works for someone else so they don't have to go through all the extra steps that I (and others) have. :laugh:
Click to expand...
Click to collapse
Yes, it's funny the different behavior on theoretically the same hardware. It's probably still applicable that flashing the bootstack before and not after the ROM was the cause.
I had the 35b bootstack when I installed JasmineROM and so far I am unable to get into download mode, when I take out the battery the screen actually turns on for a second. I am installing a VM for Windows 8 to see if that will help with my issues of not detecting the device.
I wish I'd seen this before trying to go back Jasmine after flashing 35b, thanks so much for the guide! My screen wouldn't come on, but was actually still going into download mode (keep volume up button depressed for about 10 seconds after it vibrates and it entered DL mode.) I used this method http://forum.xda-developers.com/showthread.php?t=2475045 to get back to KK stock. Here is the DL link to the TOT http://www.mediafire.com/download/6i..._Stock_TOT.zip. Also needed the LGUP8974.dll to complete the operation (don't have the link for that one, sorry.) Hope this helps a few and thanks again!
I'm getting a new g3 this week. I know the first thing the phone will do when I activate it is to do the OTAs. I want to root my phone. I want to know at which point do I stop the OTAs so I don't get stuck with unroot able version. I know the latest version, 6.0 is not root able. I do want to accidentally go to far.
Thanks
Don't take any OTAs at all if you can help it. It could come with 47A already, some other user's have recently.
Usually you can downgrade to 10B via the TOT method using the .DLL that's extracted from the 35B KDZ (both available from my Android File Host link at the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section, or in my signature below.
Root is easiest with the Stump app on XDA with its brute force option and that only works on 10B, then use TWRP Manager to install TWRP, and that part is only that easy on 12B and below
@R-T-B has found evidence that if under your battery the model number has a K at the end like VS985WK, then you might not be able to downgrade at all, so no permanent root.
Kingroot works even on 47A but it's highly suspicious and deeply ingrains itself into your system even more than is necessary for root, and with it you have to reroot after every reboot, rooting requires Internet every time, and it might be sharing your private information in the background.
If you do try to downgrade and brick, especially if you have the "K" model number, @R-T-B has a new debrick thread in the General section with modifications to previously available methods to at least get the phone working back on 47A.
This my first lg phone so I'm not a noob when it comes to rooting, I'm unfamiliar with some of lg terms. I've had moto and Samsung in the past.
So when the phone arrives I am going to post the current versions of everything and see if someone can guide me through the bes way to root, get twrp and flash a rom if I had to.
And yes, I have two threads on here. I have a thread to try and figure out out to unbrick a somewhat bricked g3 and this thread to make sure I don't do the same thing to the new phone.
Thanks
simpson1190 said:
So when the phone arrives I am going to post the current versions of everything and see if someone can guide me through the bes way to root, get twrp and flash a rom if I had to.
Click to expand...
Click to collapse
The best way is the same (what I replied previous) no matter what version.
roirraW "edor" ehT said:
The best way is the same (what I replied previous) no matter what version.
Click to expand...
Click to collapse
So if I am on 10b, I can root with stump, flash twrp with twrp manager and I'm good to go? I can flash rooms even if they are based on new versions like MM?
So the only hard thing is if I'm past 10b and/or the device is already on MM.
simpson1190 said:
So if I am on 10b, I can root with stump, flash twrp with twrp manager and I'm good to go? I can flash rooms even if they are based on new versions like MM?
Click to expand...
Click to collapse
Yes to both. Highly unlikely it'll come with 10B, and very likely it'll come with 47A or at least 35B.
roirraW "edor" ehT said:
The best way is the same (what I replied previous) no matter what version.
Click to expand...
Click to collapse
so my new g3 had 35b on it.
i've followed the guide to flash down to 10 b, i get an error in the lg tool that says upgrade stopped due to an error. then it gives instructions on trying again..
simpson1190 said:
so my new g3 had 35b on it.
i've followed the guide to flash down to 10 b, i get an error in the lg tool that says upgrade stopped due to an error. then it gives instructions on trying again..
Click to expand...
Click to collapse
You're using the new .DLL I directed you to? If you downloaded the TOT and .DLL from my Android File Host link, did you use 7-Zip to extract the files out of .7z archives you downloaded? Are you using the original USB cable (hopefully it came with the OEM one)? Installed the latest drivers from LG's website for the VS985 and then rebooted with the phone disconnected from the PC? Connected the phone in Download mode to a USB 2.0 port that comes directly off the motherboard on the PC (not USB 3.x and not through a USB hub)?
You changed the port # of the correct device - the one in the Port section, not the one in the Modem section, right?
Once the TOT flashing software gets to certain point where you think it's just going to "continue" on it's own but it doesn't, did you try unplugging the cable from the phone, wait five seconds, and then plug it back in, and wait up to a minute or more while the software should then start the flash in earnest?
Lastly, sometimes trying a different PC does the trick.
roirraW "edor" ehT said:
You're using the new .DLL I directed you to? If you downloaded the TOT and .DLL from my Android File Host link, did you use 7-Zip to extract the files out of .7z archives you downloaded? Are you using the original USB cable (hopefully it came with the OEM one)? Installed the latest drivers from LG's website for the VS985 and then rebooted with the phone disconnected from the PC? Connected the phone in Download mode to a USB 2.0 port that comes directly off the motherboard on the PC (not USB 3.x and not through a USB hub)?
You changed the port # of the correct device - the one in the Port section, not the one in the Modem section, right?
Once the TOT flashing software gets to certain point where you think it's just going to "continue" on it's own but it doesn't, did you try unplugging the cable from the phone, wait five seconds, and then plug it back in, and wait up to a minute or more while the software should then start the flash in earnest?
Lastly, sometimes trying a different PC does the trick.
Click to expand...
Click to collapse
the post you pointed me to has the KDZ file not the TOT file. It does reference a thread to downgrade via TOT file but that thread doesn't have the download links on it anymore. http://forum.xda-developers.com/verizon-lg-g3/general/restore-verizon-to-stock-t2827878
simpson1190 said:
the post you pointed me to has the KDZ file not the TOT file. It does reference a thread to downgrade via TOT file but that thread doesn't have the download links on it anymore. [/QUOTE]
My Android File Host link...d has all the KDZs, and the TOT and the .DLL.
Click to expand...
Click to collapse
roirraW "edor" ehT said:
My Android File Host link at the bottom of the first post of that thread has all the KDZs, and the TOT and the .DLL.
Click to expand...
Click to collapse
ok i found your files and I"m downloading them now. I have downloaded the flash tool and it wants a username and password. found a work around that involves turning off the internet and resetting the date on the computer. Is this the best way to flash a tot or did i not download the correct tool?
i give up....i get an error when using the tot that it didn't load. i even looked into the LGup tool and it says i have an unknown model. maybe this tool is not for the g3
f it. i'm doing the ota to MM, i like the phone with stock unrooted. so it's not worth this headache. Maybe the problem is I am on windows 10. But it is the only computer I have. If I every have a chance to use a win 7 computer, maybe I will try. With what I read, I should be able to downgrade to 10b from MM using the same methods.
simpson1190 said:
i give up....i get an error when using the tot that it didn't load. i even looked into the LGup tool and it says i have an unknown model. maybe this tool is not for the g3
Click to expand...
Click to collapse
simpson1190 said:
f it. i'm doing the ota to MM, i like the phone with stock unrooted. so it's not worth this headache. Maybe the problem is I am on windows 10. But it is the only computer I have. If I every have a chance to use a win 7 computer, maybe I will try. With what I read, I should be able to downgrade to 10b from MM using the same methods.
Click to expand...
Click to collapse
LGUp doesn't work with the VS985. The second post of the LGUp thread details what to use for Verizon G3s.
Windows 10 works fine. As long as your PCB (printed circuit board) in your particular phone isn't v2 (you'd have to look in @R-T-B 's thread in the General section as far as where to look on the board to find the "2" or "1", etc), then yes the downgrade method is the same from 47A. If you happen to have a newer revision of the VS985 then putting Marshmallow on will keep it from being downgraded any longer. This is a fairly recent development (last week or two) that this has been noticed in such detail.
If it is revision 2 of the PCB, then you won't be able to downgrade from 47A at all.
What you mean with "unrooteable" ?
If we like rooteable devices, why still people stay paying these "unrooteable" devices?
Its time to IMPOSE for CHITTY GOGLE INC to create REAL LINUX ADM ROOTED devices or STOP BUYING THESE DAMN CHITS!
Sent from my XT687 using xda premium
Dethfull said:
What you mean with "unrooteable" ?
If we like rooteable devices, why still people stay paying these "unrooteable" devices?
Its time to IMPOSE for CHITTY GOGLE INC to create REAL LINUX ADM ROOTED devices or STOP BUYING THESE DAMN CHITS!
Sent from my XT687 using xda premium
Click to expand...
Click to collapse
Personally, I love my G3, but I'm with you. I won't buy another LG product until they lose their root/custom firmware unfriendly stance.
The Google in says "Google is your friend"
so, A friendly acceptable device, is being distributable by them?
We have years Forcing, imposing, root on all SIMPLY ALL these "friendly" devices.
How we believe on their phrase?
I only believe, the UNIX AND LINUX GPL ARE BEING PAID FOR THEIR "FRIENDISM".
Sent from my XT687 using xda premium