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
Has anyone been able to install TWRP on a 35b rooted phone... I rerooted with kingroot and then replaced it with SuperSU Me with no issues this time... I did install twrp with twrp manager but it did not work.... Now my regulare recovery doean't work either.... I can do a kdz flash again if I have to. the phone itself still works no problem..
I think I mentioned before but this is applicable to this problem - you can use the root terminal DD commands as given at the bottom of @bweN diorD 's stickied thread in General to reflash just the stock 35B recovery.img, which he also has linked among all the other partitions for all of the LG builds. Otherwise, using the 35B KDZ is the only alternative since you haven't been able to downgrade.
It's known and expected that flashing TWRP through TWRP Manager on anything Lollipop and newer won't work as intended.
If you do the DD command method, I'd be tempted to first (instead) downgrade your bootloader (aboot.img) to the 12B one, and also the Download mode partition (laf.img) to the 24B one. Downgrading the bootloader might enable you to use/get into the TWRP you flashed. If that doesn't work, downgrading the laf.img should enable you to be able to use LG Flash Tool 2014 to downgrade to 10B so that you can root using the Stump app easily, and then be able to use TWRP Manager to flash TWRP and then be able to flash whatever ROM you want.
For performing DD commands, I'd copy/paste on the phone itself from his stickied thread so that you don't get a command wrong and brick your device.
Thanks I will give it a try tonight.
Sent from my VS985 4G using Tapatalk
My only question is I know I have to type in laf.img in one spot, but at the end of the command what name do I put.... I can use command line on a pc, but phone is new to me... It would be nice if you could just flash the dam thing LOL
dd if=/sdcard/**.img of=/dev/block/platform/msm_sdcc.1/by-name/*
doubledragon5 said:
My only question is I know I have to type in laf.img in one spot, but at the end of the command what name do I put.... I can use command line on a pc, but phone is new to me... It would be nice if you could just flash the dam thing LOL
dd if=/sdcard/**.img of=/dev/block/platform/msm_sdcc.1/by-name/*
Click to expand...
Click to collapse
laf
roirraW "edor" ehT said:
laf
Click to expand...
Click to collapse
I quess it worked. my phone boots but I do not have download mode anymore... Now to figure how how to correct it, so I can have a working phone...
Got it fixed, Boy nothing seems to work with getting rid of theis 35B B.S.
doubledragon5 said:
Got it fixed, Boy nothing seems to work with getting rid of theis 35B B.S.
Click to expand...
Click to collapse
Had you also flashed the downgraded (12B) aboot.img (bootloader)? Not to try to confuse you, to throw one more item into the mix, but @xdabbeb 's 35B bootstack zip contains all of the same 35B partitions extracted from the KDZ except it has the 12B bootloader and 24B Download partition. Since you already flashed the 35B KDZ (I think?) we know you're running the exact same software, so I'm starting to think there's actually a slight difference with your phone hardware. That's the only thing that makes sense to me, and would apply to those others who got the "ks error" with trying the TOT method.
Anyway, back to the bootloader. Had you tried downgrading that to see if you can get into TWRP that you tried flashing? Again, though, I'm not responsible if this bricks your device, so no pressure from me to actually try this. Just wondering if you did. It's possible that the 24B Download partition wouldn't work with anything but the 12B bootloader.
Did you just flash the 35B laf.img to fix your Download mode?
And when you thought you didn't have Download mode anymore, did you just have a black screen? If so, did you try connecting it to your PC and see if in it's listed in Device Manager under modem, which would confirm it actually was in Download mode despite the black screen? That's common when there's a weird mis-mash of partitions although the 24B Download mode does come up fine with everything else 35B except for the 12B bootloader.
roirraW "edor" ehT said:
Had you also flashed the downgraded (12B) aboot.img (bootloader)? Not to try to confuse you, to throw one more item into the mix, but @xdabbeb 's 35B bootstack zip contains all of the same 35B partitions extracted from the KDZ except it has the 12B bootloader and 24B Download partition. Since you already flashed the 35B KDZ (I think?) we know you're running the exact same software, so I'm starting to think there's actually a slight difference with your phone hardware. That's the only thing that makes sense to me, and would apply to those others who got the "ks error" with trying the TOT method.
Anyway, back to the bootloader. Had you tried downgrading that to see if you can get into TWRP that you tried flashing? Again, though, I'm not responsible if this bricks your device, so no pressure from me to actually try this. Just wondering if you did. It's possible that the 24B Download partition wouldn't work with anything but the 12B bootloader.
Did you just flash the 35B laf.img to fix your Download mode?
And when you thought you didn't have Download mode anymore, did you just have a black screen? If so, did you try connecting it to your PC and see if in it's listed in Device Manager under modem, which would confirm it actually was in Download mode despite the black screen? That's common when there's a weird mis-mash of partitions although the 24B Download mode does come up fine with everything else 35B except for the 12B bootloader.
Click to expand...
Click to collapse
Yup I had downgraded both, with no luck with getting twrp to boot.... When I went into download mode, I did get the download screen, but then it would go blank and the light in the corner would flash blue, then red none stop... So I ended up getting back to the main screen (yes it would boot, and boot then dd command stock partitions back on the phone, and the phone would once again boot into download mode and stay there... I'm not sure what different hardware I would have... I do know according to the sticker on the box, this phone was made 10/2015.. Is there a program that will list the phone exact hardware info? That was I can post it here if possible..
doubledragon5 said:
Yup I had downgraded both, with no luck with getting twrp to boot.... When I went into download mode, I did get the download screen, but then it would go blank and the light in the corner would flash blue, then red none stop... So I ended up getting back to the main screen (yes it would boot, and boot then dd command stock partitions back on the phone, and the phone would once again boot into download mode and stay there... I'm not sure what different hardware I would have... I do know according to the sticker on the box, this phone was made 10/2015.. Is there a program that will list the phone exact hardware info? That was I can post it here if possible..
Click to expand...
Click to collapse
I doubt if the difference would be anything any user program could distinguish. It would have to be not much different since it's compatible with the same KDZ. Just some small tweak they did on phones manufactured late last year is my guess.
I'd be tempted to make a thread asking others with the ks error when their phones were manufactured. Just a guess though.
I got an LG G3 that came packaged with 35B (5.1.1), and nothing seemed to be working to get TWRP installed. I couldn't use LG Flash Tools to downgrade using the "TOT" method, because it'd stop with an "no ks version" error. I finally found something that works, and I'm now running AICP (nice ROM) with TWRP installed!
The trick is to follow these instructions (make sure you use VS985 components for our Verizon LG G3s, not D855):
http://forum.xda-developers.com/lg-g3/help/help-secure-boot-error-trying-to-boot-t3054977
Overwrite aboot.img (12B version) & recovery (TWRP image) using dd commands via an adb shell, after rooting with KingRoot, while Android is running. I then used adb commands to reboot into recovery, and volia! I was in! I had AICP on my internal card, and the 12b bootstack, which I flashed in that order.
After seeing AICP successfully boot, I went back and flashed the 35B bootstack. Success!
Stock images (aboot 12B etc.): http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
Bootstacks: http://forum.xda-developers.com/verizon-lg-g3/development/xdabbeb-s-vs980-2-0-0-t3231279
KingRoot: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Great news for you and others. Thanks for sharing!
Well, i tried to follow this step by step and I ended up with a black screen after reboot. My G3 would power up, blue and green led's would flash like normal, I could hear the sounds being made by pressing the power button and touching the screen just like everything went as planned except for a black screen. My PC still recognized my device when Android was running and it was still detected when I entered download mode. I could see the device driver installation window popup on my PC and I could see my G3 in my Device Manager as well. I am a little unsure about what went wrong but I am doing my research to see if I can solve this problem. The good thing about the whole situation, I was able to use LG FLashTools 2014 to KDZ back to 35B which is what I was running at the beginning of this process. The software flash just finished and so did "Android is starting" so I will set this thing back up and try again once I find out what went wrong and why I received the black screen afterwards. If anyone can provide any input as to what my have happened or if there was something I missed I would appreciate it.
fast69mopar said:
Well, i tried to follow this step by step and I ended up with a black screen after reboot. My G3 would power up, blue and green led's would flash like normal, I could hear the sounds being made by pressing the power button and touching the screen just like everything went as planned except for a black screen. My PC still recognized my device when Android was running and it was still detected when I entered download mode. I could see the device driver installation window popup on my PC and I could see my G3 in my Device Manager as well. I am a little unsure about what went wrong but I am doing my research to see if I can solve this problem. The good thing about the whole situation, I was able to use LG FLashTools 2014 to KDZ back to 35B which is what I was running at the beginning of this process. The software flash just finished and so did "Android is starting" so I will set this thing back up and try again once I find out what went wrong and why I received the black screen afterwards. If anyone can provide any input as to what my have happened or if there was something I missed I would appreciate it.
Click to expand...
Click to collapse
Weird... this is what I did (nothing more):
1) Pick a ROM I wanted to use. I went with AICP nightly for VS985 (MM 6.0.1). Put that ROM zip to be flashed by TWRP on your internal memory.
2) Put the 12B bootstack on internal memory.
3) Put the 12B aboot.img & latest TWRP img on internal memory.
4) Root with KingRoot
5) Open up an "adb shell" and use "su" to get a root shell.
6) Use dd commands (like in the original post's link) to zero, flash aboot & the recovery image to their proper partitions.
7) Use "adb reboot recovery" to boot into TWRP
8) Factory reset
9) Flash ROM (AICP etc.)
10) Flash 12B bootstack (not 100% sure needed, but whatever)
11) Wipe cache/dalvik (not 100% sure needed, but whatever)
12) Reboot & profit!
After seeing successful boot, I did go back into TWRP & flash the 35B bootstack, just to have the latest stuff that still does work.
I *did* have one oddity where my screen went black, but NOTHING was responsive (not even the LED). Phone just appeared completely dead -- no response to anything. I pulled the battery, and it booted up fine. Hasn't happened again...
It was weird indeed. I flashed the 35B KDZ to return to stock after the screen went black. I was already on the stock 35B OTA that I received back in October. I was already rooted with Kingroot and had already removed Kingroot with SuperUser in its place. Was that something that was different between us maybe? Were you on the stock 35B, unrooted, before you started the process? Like I said, I was already rooted. Don't know if it makes a difference or not. Since I was able to flash back to stock after the mishap I will be trying it again here shortly when I get back in from of my Laptop. I am fully stock right now and my software status is official. I will do the process over again starting with a fresh template. I'll edit my post with an update after I'm finished. Thanks for the response and for the guide.
fast69mopar said:
It was weird indeed. I flashed the 35B KDZ to return to stock after the screen went black. I was already on the stock 35B OTA that I received back in October. I was already rooted with Kingroot and had already removed Kingroot with SuperUser in its place. Was that something that was different between us maybe? Were you on the stock 35B, unrooted, before you started the process? Like I said, I was already rooted. Don't know if it makes a difference or not. Since I was able to flash back to stock after the mishap I will be trying it again here shortly when I get back in from of my Laptop. I am fully stock right now and my software status is official. I will do the process over again starting with a fresh template. I'll edit my post with an update after I'm finished. Thanks for the response and for the guide.
Click to expand...
Click to collapse
I was on a "fresh", unrooted flash of the 35B KDZ after some previous failed attempts to get TWRP installed. Then, I started my steps listed above. I didn't swap out KingRoot to SuperSU (since I knew it'd just be overwritten when AICP gets installed). Just needed root to flash aboot & recovery.
What command did you run to flash the twrp img, in the other link with the commands of says he used flashify but you used terminal to flash yours. Thanks.
It works.
New here, also with VS985 35b. LG Flash tool kept giving me failed previous flash on every attempt to downgrade to 10b. Saw this and using the same aboot.img and bootstack.zip that you used, I used terminal emulator to update and it worked first time. I just had to remember to use VS985 components including twrp. Everything is now running, and am so thankful. My first G3, previously rooting and playing with Samsung S4. Again, thank you for your incredible work.
jimtom1948 said:
New here, also with VS985 35b. LG Flash tool kept giving me failed previous flash on every attempt to downgrade to 10b. Saw this and using the same aboot.img and bootstack.zip that you used, I used terminal emulator to update and it worked first time. I just had to remember to use VS985 components including twrp. Everything is now running, and am so thankful. My first G3, previously rooting and playing with Samsung S4. Again, thank you for your incredible work.
Click to expand...
Click to collapse
You mind giving m the exact commands you used and the order you did everything in? Got a little confused going from thread to thread to get everything downloaded. Think I read too much.lol confused myself
Evohog
1) Started on this site and downloaded:
Stock image (aboot.img 12b)
bootstack (12b) down the page in downloads.
This is important because the instruction page is for D855 and you need VS985 aboot and bootstack. This was what initially confused me.
2) I then went to the page that says follow these instructions.
Here I downloaded oversharpening fix flashable zip and a twrp recovery for VS985.
You will want to substitute VS985 aboot and bootstack for the D855 in his writeup.
3) I followed the rest of his tutorial, very carefully typing the commands into terminal emulator. (I haven't got my linux machine ready for adb yet.
4. Shut down the phone. rebooted into recovery (You can use flashify settings to reboot into recovery, or the buttons on back of the phone after shutdown.
5. It worked, I was in twrp. Flashed the oversharpening and the 12b bootstack.
Hope this helps.
jimtom1948 said:
1) Started on this site and downloaded:
Stock image (aboot.img 12b)
bootstack (12b) down the page in downloads.
This is important because the instruction page is for D855 and you need VS985 aboot and bootstack. This was what initially confused me.
2) I then went to the page that says follow these instructions.
Here I downloaded oversharpening fix flashable zip and a twrp recovery for VS985.
You will want to substitute VS985 aboot and bootstack for the D855 in his writeup.
3) I followed the rest of his tutorial, very carefully typing the commands into terminal emulator. (I haven't got my linux machine ready for adb yet.
4. Shut down the phone. rebooted into recovery (You can use flashify settings to reboot into recovery, or the buttons on back of the phone after shutdown.
5. It worked, I was in twrp. Flashed the oversharpening and the 12b bootstack.
Hope this helps.
Click to expand...
Click to collapse
One last question, where in the commands it says "block/name/a boot" so I enter vs985 where it says name or do I enter name. I'm so rusty,it's been a couple years since I've even rooted anything. Thanks again for the hand holding.
Evohog
If you are talking about the commands that you type into the terminal emulator, you enter them just as they are written, except for what is in quotes. Don't change them. Good Luck.
Hey guys, Tried this and now im hard bricked. Could anyone give me a hand? I have everything posted here.
http://forum.xda-developers.com/verizon-lg-g3/help/kdz-restore-t3315170/post65328929#post65328929
johnny567
I was successful twice with this method. The third time, it bricked so hard I couldn't even get into download mode. After a ton of reading, I found a recommendation in
verizon-lg-g3/general/restore-verizon-to-stock-t2827878/page24 no. 236 by jhtrades 1 at the bottom of his recommendation (ALT METHOD #2).
http://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928. I followed along starting with step 6, no wire, and somehow got the phone back to a version of verizon with a problem in the bootloader. At least, I was able to get into download mode and did a KDZ to 10b. After that everything was back on track.
I am not absolutely sure if this will work for you, or exactly sure what I did, but it's the best I can come up with. All I remember at the time, was it seemed complicated. Good luck and hope you get it back and working.
jimtom1948 said:
I was successful twice with this method. The third time, it bricked so hard I couldn't even get into download mode. After a ton of reading, I found a recommendation in
verizon-lg-g3/general/restore-verizon-to-stock-t2827878/page24 no. 236 by jhtrades 1 at the bottom of his recommendation (ALT METHOD #2).
http://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928. I followed along starting with step 6, no wire, and somehow got the phone back to a version of verizon with a problem in the bootloader. At least, I was able to get into download mode and did a KDZ to 10b. After that everything was back on track.
I am not absolutely sure if this will work for you, or exactly sure what I did, but it's the best I can come up with. All I remember at the time, was it seemed complicated. Good luck and hope you get it back and working.
Click to expand...
Click to collapse
It doesnt seem to be working for me. It is pulling up as the Qualcomm 9008 and i have tried with and without wire. It keeps failing and I end up with the error "No response from the device. Check PMIC first and if still boot problem replace AP." I noticed that I have a vs985k. Do you think that could contribute to the failure?
If you are on 35b (rooted or unrooted) without TWRP here is a simple guide to get TWRP and rooted Marshmallow 46A on your phone. This is all info available in various threads here on XDA (typically mentioned by roirraW "edor" ehT) and I take no credit for any of this work. After going thru the process yesterday I simply thought it would make it easy for others to find everything in one place with links. Standard disclaimer : use this method at your own risk
1.Use the TOT method to return to 10B (backup your data, this will wipe your phone) http://forum.xda-developers.com/verizon-lg-g3/general/restore-verizon-to-stock-t2827878
The most helpful posts in this thread were the OP, #9 and #236 note: if this doesn't work for you look here http://forum.xda-developers.com/verizon-lg-g3/general/ks-version-error-downgrade-trouble-t3306028
2. Root your phone (now on 10B) using Stump http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
3. After rooted Install SuperSu https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
4. After SuperSU is installed install TWRP using TWRP manager https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
5. Reboot into TWRP recovery and factory reset (just to be safe)
6. Flash 35B bootstack from TWRP recovery http://forum.xda-developers.com/verizon-lg-g3/development/xdabbeb-s-vs980-2-0-0-t3231279
7. Wipe data/cache within TWRP
8. Flash 46A in TWRP link to stock http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365 Or use the rom of your choice
9. Reboot to system (do not install superSU from TWRP if using the link above)
For ease of installation I suggest downloading everything to your PC first then create a folder on your SD card called flash and copying the needed apk and zip files to that folder before you get started. This way you won’t have to sign into your google account in 10B to download the APK for SuperSu and TWRP manager. Use apkmirror or a similar site to download what you need.
Any issues to report on running 46A? Any issues with having an SD card?
No issues, I flashed stock 46A yesterday and everything has worked perfectly so far. No problems with SD card, (Sony 32Gb Class 10-UHS1) I mostly have it for photos and music. I have only disabled/uninstalled some preinstalled apps and flashed the hotspot mod so far. Can't comment on battery life, needs a few days to settle.
Are you still able to downgrade back to 35B, if need be?
Not sure haven't tried but I assume this method would work
someguyatx said:
Not sure haven't tried but I assume this method would work
Click to expand...
Click to collapse
I am trying to downgrade, but it fails. It fails with model information check FAIL! I have downgraded before without a problem. Is there a fix for this or am I doing something wrong?
I don't know, you will probably get a better answer in one of the other threads. You may also have to try the alternate method of the tot method doesn't work.
chadhoard said:
I am trying to downgrade, but it fails. It fails with model information check FAIL! I have downgraded before without a problem. Is there a fix for this or am I doing something wrong?
Click to expand...
Click to collapse
I think I answered you in another thread where you asked. Use the 10B TOT method with the new 35B .DLL that came inside in the 35B KDZ, available in the other thread I referenced in my other answer.
roirraW "edor" ehT said:
I think I answered you in another thread where you asked. Use the 10B TOT method with the new 35B .DLL that came inside in the 35B KDZ, available in the other thread I referenced in my other answer.
Click to expand...
Click to collapse
You did!! Everything worked and I am up and running!! Thank you!
Would you happen to know, before I start searching, if Xposed works? If so, where I would be able to downlload it?
chadhoard said:
You did!! Everything worked and I am up and running!! Thank you!
Would you happen to know, before I start searching, if Xposed works? If so, where I would be able to downlload it?
Click to expand...
Click to collapse
Great, glad to hear it. Xposed works for me. I always have to Google for:
Code:
xposed lollipop
I'm pretty sure the Marshmallow xposed can be reached that way too. I think SDK23 is Marshmallow, so that's what you'll look for in the different Xposed flashables.
I have an issue and I had it before I did the above steps I was just hoping upgrading to 6.0 would fix the problem. My G3 boots into the fine but the wireless says "turning On" for about 1 minute and then it finally turns on and asks to connect to my home wireless, I enter the password and within 2 minutes the phone shuts down and will not go past the Red V Verizon screen, it just keeps rebooting. I can go back into TWRP and wipe it and it will boot back into 6.0 again. I was able to turn the wireless off before it went on and side loaded 25 diffenent apps and was able to use the phone for 4 hours without any issues but then I thought I would try the wireless again and it took like 4 minutes to finally turn on then as soon as I connected to a wireless network (office network this time) within 2 minutes it shut down. I was able surf the web and get on Google play store before it shut down but then it went back to the endless reboot loop..
My thoughts are that I might be able to flash a bootstrap update and I am not completely sure if a new one came in the 6.0 Android updated listed above actually came with one and if not I am not sure which one to use.
This all started in middle of December when the daily CM updates went from 5.1 to 6.0 overnight and everything got messed up. I was over trying to fix it so I ordered myself a Nexus 6P for Christmas and then life was good till I ran over it yesterday with my Jeep and destroyed it.. So back to trying to get the G3 working...
thanks for the help
Doug
Doug, What a strange problem. If you use the TOT method to go back to 10B then turn on the Wi-Fi in 10B does it still lock up and boot loop?
I can confirm this method works and I had no issues except for steps that i misread and had to repeat..
I used to be on Rooted on 35B with no Recovery. Now I am on 46A rooted with Recovery.
I am having an issue with a checksum fail on 46a during the twrp install, any suggestions?
(file d-loaded onto PC then copied into the phone memory download folder)
Nesbocaj said:
I am having an issue with a checksum fail on 46a during the twrp install, any suggestions?
(file d-loaded onto PC then copied into the phone memory download folder)
Click to expand...
Click to collapse
Did you verify the md5 on your pc before copying to your sd card?
someguyatx said:
Did you verify the md5 on your pc before copying to your sd card?
Click to expand...
Click to collapse
Yes.
Second try: I d-loaded directly into the phone mem and flashed that, seems to have done the job overnight (!!! ), restoring applications right now.
Thank you for the most excellent guide, not that simple (for me), but very well done.
The phone has become un-rooted with this last flash, TWRP app will not load. OK reloaded and back.
Glad it helped you. I spent several hours reading the forums and installing and wanted to save others some time. Everything was here already just not easy to put the pieces together.
someguyatx said:
Doug, What a strange problem. If you use the TOT method to go back to 10B then turn on the Wi-Fi in 10B does it still lock up and boot loop?
Click to expand...
Click to collapse
Yes it did the same thing in 10B, I was hoping install 6.0 would help the issue but it does the same thing. I can get the wireless to work maybe for a minute, maybe for 30 minutes but then it shuts down and will not boot again till I do a factory reset.
duglas said:
Yes it did the same thing in 10B, I was hoping install 6.0 would help the issue but it does the same thing. I can get the wireless to work maybe for a minute, maybe for 30 minutes but then it shuts down and will not boot again till I do a factory reset.
Click to expand...
Click to collapse
Hardware issue perhaps.
wait how do you know if you are on 35b?
I tired a search and the only similar thread i found was someone who was able to boot into twrp. I am not able to do that. over a year ago i rooted my phone. but i haven't had any issues. out comes this stupid update and my phone tried to install it and failed. since then I've had issues so i figured i'd just reset the phone. I go to pull up adb and adb will force my phone to reboot but does not recognize it after its in bootloader mode. Okay weird also will show my phone in adb when i type adb devices, and will force it to reboot to firmware update, but never sees it. Figured I'd start back at square one Load up the patched version of LGUP, it recgnizes my phone when its NOT in bootloader mode, but the second i try it in bootloader it doesn't see my phone. I've tried deleting the adb Lgup the device drivers i've revoked debuggin authorization I just can't think of anyreson other than so messed up firmware that the phone would be doing this
Will doing the "button dance" get you into twrp?
What's the button dance?
deplorableone said:
What's the button dance?
Click to expand...
Click to collapse
Google LG V30 button dance.
Yeah all it does is restart my phone and when I get to the reset screen is just wipes my device
Yeah all it does is restart my phone and when I get to the reset screen is just wipes my device
deplorableone said:
Yeah all it does is restart my phone and when I get to the reset screen is just wipes my device
Click to expand...
Click to collapse
If you did it correctly, then that means you must not TWRP installed. If you had TWRP the button dance would boot to TWRP instead of wiping your phone. I hate doing the button dance as it takes specific timing to hit the buttons correctly.
In all my Guides there's only one scenario where I tell people they have no other choice than to use the button dance. In all others I stress other options.
I also tell people to never take an OTA update if you have TWRP installed.
ChazzMatt said:
If you did it correctly, then that means you must not TWRP installed. If you had TWRP the button dance would boot to TWRP instead of wiping your phone. I hate doing the button dance as it takes specific timing to hit the buttons correctly.
In all my Guides there's only one scenario where I tell people they have no other choice than to use the button dance. In all others I stress other options.
I also tell people to never take an OTA update if you have TWRP installed.
Click to expand...
Click to collapse
Yeah I woke up to the "update not installed" nag screen...I know i had twrp installed since it's how i installed magisk, and the VS99630c .zip. Those are still on my SD card. At least after wiping the phone it seems to be behaving properly, but magisk is now gone and being unable to boot into twrp means I can't put it back. It's all good though it's a 3+ year old phone figured if i can't fix it i'll just replace it. Didn't know if anyone had an experience like this with lgup and adb not recognizing the handset in download mode. Seemed like a strange quirk...
deplorableone said:
Didn't know if anyone had an experience like this with lgup and adb not recognizing the handset in download mode. Seemed like a strange quirk...
Click to expand...
Click to collapse
Yes, sometimes reinstalling drivers helps. Also trying a different computer.
Your bootloader is still unlocked, but because you are on Verizon firmware it's not giving you the scary warning. To reinstall TWRP and Magisk, using Dev Patched LGUP you would have to temporarily flash back to US998 firmware (Oreo would be best), then use go through Section 6 of the WTF Instructions to install TWRP, reformat internal memory, install Magisk. Then you could re-flash VS996 30C (until a TWRP flashable zip of 30d comes along). You would need to freeze the update files so this doesn't happen again.
ChazzMatt said:
Yes, sometimes reinstalling drivers helps. Also trying a different computer.
Your bootloader is still unlocked, but because you are on Verizon firmware it's not giving you the scary warning. To reinstall TWRP and Magisk, using Dev Patched LGUP you would have to temporarily flash back to US998 firmware (Oreo would be best), then use go through Section 6 of the WTF Instructions to install TWRP, reformat internal memory, install Magisk. Then you could re-flash VS996 30C (until a TWRP flashable zip of 30d comes along). You would need to freeze the update files so this doesn't happen again.
Click to expand...
Click to collapse
Yes i've been trying to just start back over at square one using the patched LGUP, but it doesn't recognize the phone. I've numerous cables and 2 different PC's and no luck yet. I am going to try and buy a new cable though since I just used the ones I've had around the house. Seems odd that the phone is recognized using the cables up until i place it into download mode though. Might try and clean out the ole charging port as well. Again i originally followed the instructions to a T and have had absolutely no issues but noticed i lost voice commands and my sms/mms were messed up, immediately after the failed update. the phone seems to be 100% now with no issues due to the wipe. SO it's not the end of the world if I can't figure it out, but more like a challenge of fixing it
If someone can capture and share that OTA update you received, you can flash it using LGUP in FOTA mode. This often restores a broken Download Mode, even if the system update itself fails due to the phone not being stock and/or lacking stock recovery.
LGUP FOTA mode works inside the OS (with the phone in File Transfer mode) and doesn't require working Download Mode.
Just a thought
Caveat: The purpose of this would ONLY be to fix your Download mode. However there is a risk it might actually mess up your OS (which is currently working). So if it doesn't fix your Download mode, you'll actually be worse off.
I have the exact same issue so you're not alone, I'm trying anything I can think of, lmk if you figure something out. It's weird it sees phone in desktop with phone booted then a glitch in download mode and it never pulls up. I'm due for a new phone anyway, the update slipped thru somehow, lost root and twrp, can't flash. I'll let you know if I figure it out as well. If Chazz don't know how to fix itwe might be out of luck.
cpete2112 said:
I have the exact same issue so you're not alone, I'm trying anything I can think of, lmk if you figure something out. It's weird it sees phone in desktop with phone booted then a glitch in download mode and it never pulls up. I'm due for a new phone anyway, the update slipped thru somehow, lost root and twrp, can't flash. I'll let you know if I figure it out as well. If Chazz don't know how to fix itwe might be out of luck.
Click to expand...
Click to collapse
Which model do you have, and which ROM are you on?
If you are "somewhat stock", on a model for which we have OTA files, you can force flash those using LGUP FOTA mode. This works inside the OS, doesn't require Download mode, and will often restore Download mode as the first thing -- even if the update itself fails because the phone isn't completely stock.
If you are on T-Mobile H932, we have a separate thread to help restore Download mode using OTA files and LGUP FOTA mode:
https://forum.xda-developers.com/lg-v30/help/h932-url-h932-pie-ota-file-t3991417/page7
And if you are on any model OTHER than
T-mobile H932, and you cannot find an OTA file, you can use the firehose and guidance in the thread linked below to re-flash the laf partition (Download mode).
https://forum.xda-developers.com/lg-v30/how-to/lg-v30-unbrick-guide-qualcomm-edl-9008-t4048661
I have a Verizon on 30c, I would like to make it to 30d, this phone started out as a ls998 sprint model, not that that matters idk. Yah I'm gonna try one of those mentioned routes to fix, I'm out of ideas.
cpete2112 said:
I have a Verizon on 30c, I would like to make it to 30d, this phone started out as a ls998 sprint model, not that that matters idk. Yah I'm gonna try one of those mentioned routes to fix, I'm out of ideas.
Click to expand...
Click to collapse
You're in luck then: If you're on Verizon 30c, it *should* offer you a 30d OTA update. And if you accept that, it *should* repair your Download mode as part of the update
The potential risk here is when you're not completely stock, the OTA probably won't complete. That's ok as long as it repairs your Download mode, since then you can re-flash with LGUP. But in case it *doesn't* repair your Download mode, you could theoretically be worse off. I haven't heard of cases where that happened, I'm just pointing out the potential risk.
Good luck to you :fingers-crossed:
Edit: No wait, if you started out as LS998, Verizon won't offer you the OTA. But I believe somebody captured the 30d OTA file and shared it in another thread (about the 30d). If so, you can force flash it with LGUP FOTA mode. Make sure the PC can see the phone as MTP (USB File mode) before attempting this.
TheDannemand said:
Which model do you have, and which ROM are you on?
If you are "somewhat stock", on a model for which we have OTA files, you can force flash those using LGUP FOTA mode. This works inside the OS, doesn't require Download mode, and will often restore Download mode as the first thing -- even if the update itself fails because the phone isn't completely stock.
If you are on T-Mobile H932, we have a separate thread to help restore Download mode using OTA files and LGUP FOTA mode:
https://forum.xda-developers.com/lg-v30/help/h932-url-h932-pie-ota-file-t3991417/page7
And if you are on any model OTHER than
T-mobile H932, and you cannot find an OTA file, you can use the firehose and guidance in the thread linked below to re-flash the laf partition (Download mode).
https://forum.xda-developers.com/lg-v30/how-to/lg-v30-unbrick-guide-qualcomm-edl-9008-t4048661
Click to expand...
Click to collapse
My friend was just looking for this information. Thanks
gimpy1 said:
Will doing the "button dance" get you into twrp?
Click to expand...
Click to collapse
Doin' the buttons in DL mode.