Develop Bugs

Switch recoveries

Is there a need to switch recoveries when switching back and forth between kitkat to JB ?

Do you mean from cwm and twrp and contrariwise? No, you don't need to.
Sent from my LG-E986 using xda app-developers app

tomi001 said:
Do you mean from cwm and twrp and contrariwise? No, you don't need to.
Sent from my LG-E986 using xda app-developers app
Click to expand...
Click to collapse
I meant like are higher/newer recoveries for g pro able to install JB roms such as stock based

optimusv45 said:
I meant like are higher/newer recoveries for g pro able to install JB roms such as stock based
Click to expand...
Click to collapse
No for JB you don't need but for KK you must have cwm 6.0.4.4 and about twrp i m not sure.

tomi001 said:
No for JB you don't need but for KK you must have cwm 6.0.4.4 and about twrp i m not sure.
Click to expand...
Click to collapse
So basically need to switch to older recoveries every time switching from kitkat to JB ?

optimusv45 said:
So basically need to switch to older recoveries every time switching from kitkat to JB ?
Click to expand...
Click to collapse
No for downgrade you don' have to flash another recovery.

tomi001 said:
No for downgrade you don' have to flash another recovery.
Click to expand...
Click to collapse
Ic, so newer recoveries for this phone are backward compatible

optimusv45 said:
Ic, so newer recoveries for this phone are backward compatible
Click to expand...
Click to collapse
Yes.

What is the difference between loki-fied and not loki-fied recovery ? .. when do I need which ? Shellnuts freegee and cubes cwm and twrp threads don't say if their recoveries are lokified or not. Phlis touch cwm thread makes a mention of it, but was very confusing, "lokified during flash" , what's that supposed to mean ? He also speak of lokified if bootloader is locked ? So if bootloader is unlocked through freegee you don't need a lokified recovery ? ... I'm super confused ..

I have flashed every KK ROM for the e980 with CWM 6.0.3.7 without fail, fwiw
e980 - I'd tell you which ROM, but I'd have to update my signature thrice daily

thathamiam said:
I have flashed every KK ROM for the e980 with CWM 6.0.3.7 without fail, fwiw
e980 - I'd tell you which ROM, but I'd have to update my signature thrice daily
Click to expand...
Click to collapse
Thats good to know. Did you get the recovery through freegee ? Do you ever switch back to JB ? Switching back and forth without issues too ?

optimusv45 said:
Thats good to know. Did you get the recovery through freegee ? Do you ever switch back to JB ? Switching back and forth without issues too ?
Click to expand...
Click to collapse
Yes, I got this recovery from Freegee. First and only recovery I installed. Have never updated it, because if it ain't broke...
When KK first came to the OGP, I switched back and forth between that and Vanir 4.3 and BS Harmony 4.3 with no problems, back or forth. YMMV, but for me there has never been a problem. One thing to note is that I haven't flashed any of the stock based roms. I am a custom ROM guy through and through.
e980 - I'd tell you which ROM, but I'd have to update my signature thrice daily

thathamiam said:
Yes, I got this recovery from Freegee. First and only recovery I installed. Have never updated it, because if it ain't broke...
When KK first came to the OGP, I switched back and forth between that and Vanir 4.3 and BS Harmony 4.3 with no problems, back or forth. YMMV, but for me there has never been a problem. One thing to note is that I haven't flashed any of the stock based roms. I am a custom ROM guy through and through.
e980 - I'd tell you which ROM, but I'd have to update my signature thrice daily
Click to expand...
Click to collapse
Sounds good. Thanks man

optimusv45 said:
Sounds good. Thanks man
Click to expand...
Click to collapse
[emoji106]no sweat
Sent from my LG-E980 using Tapatalk

The OGP has a locked bootloader. We use Loki as a way to bypass this so we have the full functionality of an unlocked bootloader. The recoveries included in freegee have the loki bypass just as every recovery here on XDA, for our device, has it (I think).
Stock-based ROMs don't require loki as they can run on the stock kernel included with the phone while loki is needed for AOSP-based ROMs due to the change of kernel. Without an unlocked bootloader (or Loki in our case) we'd be stuck on stock-based ROMs which is exactly what happened to the Atrix HD.
Sent from my ColorOS LG-E980

Neroga said:
The OGP has a locked bootloader. We use Loki as a way to bypass this so we have the full functionality of an unlocked bootloader. The recoveries included in freegee have the loki bypass just as every recovery here on XDA, for our device, has it (I think).
Stock-based ROMs don't require loki as they can run on the stock kernel included with the phone while loki is needed for AOSP-based ROMs due to the change of kernel. Without an unlocked bootloader (or Loki in our case) we'd be stuck on stock-based ROMs which is exactly what happened to the Atrix HD.
Sent from my ColorOS LG-E980
Click to expand...
Click to collapse
Thanks man. Sounds like HTC s-on/off

I guess the next obvious question is why wouldn't people just unlock through freegee ? Is it not reliable ?

I rooted mine with 10p and 10k, used a flashable 10k and used lg flash tools. As of right now I still have this error message coming up in freegee telling me "com. lg.hidden menu has stopped working. I thought maybe there was something wrong, that's why I did all these flashes and recoveries. But I still get this error in freegee. I have also NEVER to date seen the "unlock" or "security off" option in freegee.
The last recovery I did was because I flashed a security app, Cerberus, to my phone and it caused it to get stuck on the LG logo. When I flashed Cerberus I got some error message at the end about there being a Loki error. It was a long name and I don't remember it off hand. You guys have to forgive my ignorance as this phone is new to me and I'm just learning all this stuff for it. Am I doing something wrong here? Is there a way to unlock the bootloader now without using freegee? I don't plan to flash a custom rom on here so is freegee and an unlocked bootloader even needed?
Help me out here guys. A really good in-depth sticky on all this stuff would be great but there isn't one, that I found anyway.

That's interesting. I unlocked my optimus g with freegee. I thought one couldnt even have a custom recovery with bootloader locked .. Maybe this is where the Loki thing comes in play
Don't blame yourself man, it is very confusing here with all variants of the phone in one forum. Also I don't think you'll need freegee at all since you aren't planning on using a custom rom.

Freegee is what I used as well. Yes, it's pretty much like S-Off for HTC which is why you see the Secure Boot Error message on boot. :3
For the OGP, instead of freegee unlocking the bootloader it applies Loki. On my old LGOG (E970) freegee actually unlocks the bootloader. But having a locked bootloader has saved me quite a bit of trouble. Just now got my 4th replacement phone (Middle of the screen was waaaaay too bright compared to the rest) for free by using LGFlashTool and putting it back to stock before sending it in. Otherwise I would've ended up owing AT&T around $1,200 lol.
Sent from my ColorOS LG-E980

OTA Update for rooted g pad

Hi!
Has anyone installed the update OTA on a rooted g pad?
Is it safe to do it or it's not possible?
How can I install the update if I am rooted and keep my root?

goldengutz13 said:
Hi!
Has anyone installed the update OTA on a rooted g pad?
Is it safe to do it or it's not possible?
How can I install the update if I am rooted and keep my root?
Click to expand...
Click to collapse
I have seen people reporting problems in other threads here on XDA. Here in the US they haven't yet released the OTA update. If this is anything like my experience with my phone (a GS3). OTA update of a factory rom when rooted often does seem to cause problems. The only device I haven't had problems with taking an OTA when rooted were a Nexus device (Nexus 7) and something running CyanogenMod.

muiriddin said:
I have seen people reporting problems in other threads here on XDA. Here in the US they haven't yet released the OTA update. If this is anything like my experience with my phone (a GS3). OTA update of a factory rom when rooted often does seem to cause problems. The only device I haven't had problems with taking an OTA when rooted were a Nexus device (Nexus 7) and something running CyanogenMod.
Click to expand...
Click to collapse
so I have to unroot it first, install update then root again?

I have a related question - how to unroot and install OTA??
I tried to install, but it didn´t work, tablet said there´s no OTA for rooted devices.
I unrooted using SuperSU, but the situation is still the same.

Dekxster said:
I have a related question - how to unroot and install OTA??
I tried to install, but it didn´t work, tablet said there´s no OTA for rooted devices.
I unrooted using SuperSU, but the situation is still the same.
Click to expand...
Click to collapse
I used the LG Support Tool method which involves putting the tablet into download mode and doing the update recovery procedure in the LG Support Tool. This (after a long download process) should result in a tablet which is identical to what came in the box. (in the US the procedure currently installs 4.2.2). When it finished the download and install, it reboots the tablet, if you then are stuck in a boot loop, simply do the key combination for a factory reset and it then should boot.
The unroot procedure via SuperSU does seem to leave something behind that the OTA still detects...
If you need further details I have another post in one of these threads detailing exactly what I did...
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
goldengutz13 said:
so I have to unroot it first, install update then root again?
Click to expand...
Click to collapse
That is what I plan on doing once the US version is released, however it is potentially a little more complicated since I have heard that LG has patched the LOKI vulnerability which means no custom roms or custom recovery until a new boot loader vulnerability is found, or until you revert to the original boot loader instead of the new one in the 4.4.2 release (if possible)...

muiriddin said:
That is what I plan on doing once the US version is released, however it is potentially a little more complicated since I have heard that LG has patched the LOKI vulnerability which means no custom roms or custom recovery until a new boot loader vulnerability is found, or until you revert to the original boot loader instead of the new one in the 4.4.2 release (if possible)...
Click to expand...
Click to collapse
Nah. You can bet that within 48 hours after the US version is released, there will be a flashable build available with root and recovery.

Subtleone said:
Nah. You can bet that within 48 hours after the US version is released, there will be a flashable build available with root and recovery.
Click to expand...
Click to collapse
True, more than likely a flash-able version will exist once someone makes it.

It already has a work around for loki by reinstalling the old aboot
http://forum.xda-developers.com/showthread.php?t=2698267
Just do steps 2 and 3.
Works fine on mine
Sent from my LG-V500 using xda app-developers app

I upgraded Via OTA my rooted lgpad and when it rebooted... stuck in recovery.
So i had to flash with lg tool.
I did not lose any data but a bit of time.
My suggestion is to flash with lg tool and then root again.
sent from tablet

I think the issue with this procedure is the recovery / bootloader, not the rooting itself. Still, you will most likely end with an unbootable OS. You are better off flashing via recovery a perfectly stock, pre-rooted image, like this http://forum.xda-developers.com/showthread.php?t=2707363

Trunkam said:
I upgraded Via OTA my rooted lgpad and when it rebooted... stuck in recovery.
So i had to flash with lg tool.
I did not lose any data but a bit of time.
My suggestion is to flash with lg tool and then root again.
sent from tablet
Click to expand...
Click to collapse
When you use the lg tool (pc software) did it automatically download the kitkat update?
Did you encounter any issue when you used lg tool?

Trunkam said:
I upgraded Via OTA my rooted lgpad and when it rebooted... stuck in recovery.
So i had to flash with lg tool.
I did not lose any data but a bit of time.
My suggestion is to flash with lg tool and then root again.
sent from tablet
Click to expand...
Click to collapse
So you did NOT unroot first?
Steps you did were: (with rooted only g pad)
Update via pc lg tool
Root using IOROOT25.zip method
This correct?

goldengutz13 said:
When you use the lg tool (pc software) did it automatically download the kitkat update?
Did you encounter any issue when you used lg tool?
Click to expand...
Click to collapse
I had to click on "recover" Something sorry I have no my PC now.. I left it at work. But I think you'll find.
U got some option and considering lgpad did not boot after update.. I had only one.
It's the procedure that you got to follow after you set gpad in download mode.
No issue at all, just one thing: after rooting you will have to flash a custom recovery if you need, because flashing with lg, flash even lg stock recovery.
erwaso said:
So you did NOT unroot first?
Steps you did were: (with rooted only g pad)
Update via pc lg tool
Root using IOROOT25.zip method
This correct?
Click to expand...
Click to collapse
No I did not unroot.. But only because I did not think about it. And that's the reason why gpad was not able to boot to system and I had to flash it via lg software.
I set gpad in download mode,,then flash via lg software, root with ioroot and finally flashed with flashify custom recovery
Hope to have helped guys
Now I'll go to sleep!
tapatalked..

I updated to version 4.4.2 Via OTA my rooted gpad and not had any problems
Steps:
1- factory reset
2- update via OTA
Attention: I think the rom has to be original (no eliminated sys apps with titanium or other) because it goes check the integrity of the rom (4.2.2)
------------------------------------------------------------ Edit --------------------------------------------------------------------------
3- Rooted with IOroot25

I've done an OTA update on my rooted G Pad, no issues either. I didn't do a factory reset, just did the update.

I updated my rooted v500 2 days ago using LGs PC software. The process took around 45 minutes and resulted in a successful KitKat update, however I no longer have root. I have a few strange issues with random unmounting of the SD card, which happened about 4 times while Play Music was copying 2gig of on device songs to it. I also seem to have lost quiet mode - maybe it's been moved out of the sound settings menu - would appreciate a comment if anyone knows where it is.
Sent from my LG-V500 using Tapatalk

Hugo-PT said:
I updated to version 4.4.2 Via OTA my rooted gpad and not had any problems
Steps:
1- factory reset
2- update via OTA
Attention: I think the rom has to be original (no eliminated sys apps with titanium or other) because it goes check the integrity of the rom (4.2.2)
Click to expand...
Click to collapse
I froze a few apps using rom toolbox, think that would matter?
---------- Post added at 07:29 AM ---------- Previous post was at 07:28 AM ----------
GePeKo said:
I updated my rooted v500 2 days ago using LGs PC software. The process took around 45 minutes and resulted in a successful KitKat update, however I no longer have root. I have a few strange issues with random unmounting of the SD card, which happened about 4 times while Play Music was copying 2gig of on device songs to it. I also seem to have lost quiet mode - maybe it's been moved out of the sound settings menu - would appreciate a comment if anyone knows where it is.
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
The development section has a thread on IOROOT and it works. Have at it! I'll do this whole thing when the kids nap lol

erwaso said:
I froze a few apps using rom toolbox, think that would matter?
Click to expand...
Click to collapse
with frozen apps you shall have no problems.

[Q] stuck on twrp flash fails

hello everyone . First I want to thank you for helping me out. I havent flashed anything in over a year. The phone has been good to me . Ok I was running OpTimuSDE_v1.8 ZVA since last year Feb or so. yesterday I get up and notice that the phone is stuck on recovery TWRP 2.6.3.4. I havent the need to flash since last year and now this. I dont know what to do. Ive tried flashing my backup to no avail. there were some there this morning but now theyre gone. Before I go ahead and brick this i need to ask for some sort of assistance from those in the know. Is it possible to push a different rom and then flash that rom or do I need to update the recovery image then push the rom and then flash?? Any assistance would be awesome . Thank you ..

You may be slightly bricked. Though you have recovery. I would say your option is either tot or as you said try side load or if you have storage device that you can access from the phone. You could update TWRP from cm12 thread. Flash cm12 then modem to zv8, then gapps. Or as before might be best to tot so you know your safe.
If you tot. Which I believe in sorting g2 general there is a zve tot. Then stump root, auto-rec. Update TWRP, flash lollipop rom, zv8 radio, gapps. Prosper
Sent from my LG-LS980 using Tapatalk

thanks
secret.animal said:
You may be slightly bricked. Though you have recovery. I would say your option is either tot or as you said try side load or if you have storage device that you can access from the phone. You could update TWRP from cm12 thread. Flash cm12 then modem to zv8, then gapps. Or as before might be best to tot so you know your safe.
If you tot. Which I believe in sorting g2 general there is a zve tot. Then stump root, auto-rec. Update TWRP, flash lollipop rom, zv8 radio, gapps. Prosper
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
wow I have my work cut out for me me then. I will try the easy way first . thank you S-animal for your help.

[Q] Lg G2 LS980

Hi guys i have an LG Sprint LS980 and i factory reseted it a few days ago. After reset i was unable to use my GSM sim on it. Browsed through the forums and found a permanent unlock and now i can use my GSM sim again, however, i have a few problems discussed below:
1. The sim unlock method did not work with ZVE, ZVC and ZVA as i was unable to drag and drop " Property folder" from Carrier to/carrier/ in my device using Total commander from my PC, hence i had to flash to ZV8 then rooted with iroot and sim started working but now after accepting OTA the phone has updated to ZVA and sim still works. After this my g2 started to download ZVC OTA and i installed it too but after reboot my G2 still shows version as 4.2.2 (jelly bean) and as ZVA instead of ZVC. Software update also shows that phone is up to date. SO I AM STUCK AT JELLY BEAN ZVA.
2. In all the versions that i have flashed (ZVE, ZVC, ZVA and ZV8) i have been unable to go into recovery mode via TWRP app or quick boot. Clicking on flash in TWRP App does nothing, while in quick boot my g2 reboots but after lg logo boots into homescreen instead of recovery mode. So i am unable to flash cloudy G2 v 2.2 rom.
SUMMARY
- G2 won't update to Kit kat and stuck on ZVA jelly bean even though ZVC installed via OTA.
- G2 won't go into recovery mode no matter what i tried so can't install cloudy G2 v 2.2 rom.
- If i flash to ZVE then my GSM sim will not work and i will be unable to apply permanent sim unlock as it will not let me drag and drop " Property folder" via Total Commander.
So i am unable to update to latest version both via OTA as well as via flashing (as my sim will not work on it) and also unable to install custom cloudy G2 v 2.2 rom.
Please help out sirs. These couple of days were like hell to me :crying:

Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers from the owners/experts.
Stand by
Good luck

syedmoazzam said:
Hi guys i have an LG Sprint LS980 and i factory reseted it a few days ago. After reset i was unable to use my GSM sim on it. Browsed through the forums and found a permanent unlock and now i can use my GSM sim again, however, i have a few problems discussed below:
1. The sim unlock method did not work with ZVE, ZVC and ZVA as i was unable to drag and drop " Property folder" from Carrier to/carrier/ in my device using Total commander from my PC, hence i had to flash to ZV8 then rooted with iroot and sim started working but now after accepting OTA the phone has updated to ZVA and sim still works. After this my g2 started to download ZVC OTA and i installed it too but after reboot my G2 still shows version as 4.2.2 (jelly bean) and as ZVA instead of ZVC. Software update also shows that phone is up to date. SO I AM STUCK AT JELLY BEAN ZVA.
2. In all the versions that i have flashed (ZVE, ZVC, ZVA and ZV8) i have been unable to go into recovery mode via TWRP app or quick boot. Clicking on flash in TWRP App does nothing, while in quick boot my g2 reboots but after lg logo boots into homescreen instead of recovery mode. So i am unable to flash cloudy G2 v 2.2 rom.
SUMMARY
- G2 won't update to Kit kat and stuck on ZVA jelly bean even though ZVC installed via OTA.
- G2 won't go into recovery mode no matter what i tried so can't install cloudy G2 v 2.2 rom.
- If i flash to ZVE then my GSM sim will not work and i will be unable to apply permanent sim unlock as it will not let me drag and drop " Property folder" via Total Commander.
So i am unable to update to latest version both via OTA as well as via flashing (as my sim will not work on it) and also unable to install custom cloudy G2 v 2.2 rom.
Please help out sirs. These couple of days were like hell to me :crying:
Click to expand...
Click to collapse
So your download mode is broken or not? It sounds like you were only rooted. I don't know much on the Sim issue. But you could tot to zv8, and then maybe hit cm12 after running auto-rec.

secret.animal said:
So your download mode is broken or not? It sounds like you were only rooted. I don't know much on the Sim issue. But you could tot to zv8, and then maybe hit cm12 after running auto-rec.
Click to expand...
Click to collapse
No download mode is working fine. But recovery mode is not working whether via quick boot or TWRP so i am unable to install cloudy g2 rom. And if i flash to ZVE my sim does not work. Stuck on jelly bean
And what do you mean by "cm12 after running auto-rec"?
That is the problem man, recovery mode not working no matter what i try

syedmoazzam said:
No download mode is working fine. But recovery mode is not working whether via quick boot or TWRP so i am unable to install cloudy g2 rom. And if i flash to ZVE my sim does not work. Stuck on jelly bean
And what do you mean by "cm12 after running auto-rec"?
That is the problem man, recovery mode not working no matter what i try
Click to expand...
Click to collapse
So, you can run lg flash tool, and take it back to zva or zvc and root. Use auto-rec to get TWRP. Install cloudy g2. Putting your change in. Or use the flash tool to go to zv8, grab official cm12. Root, use auto-rec to get TWRP, update TWRP. Flash cm12 (lollipop) with gapps. And change what you need to get your Sim working.

secret.animal said:
So, you can run lg flash tool, and take it back to zva or zvc and root. Use auto-rec to get TWRP. Install cloudy g2. Putting your change in. Or use the flash tool to go to zv8, grab official cm12. Root, use auto-rec to get TWRP, update TWRP. Flash cm12 (lollipop) with gapps. And change what you need to get your Sim working.
Click to expand...
Click to collapse
Thanks gonna try this auto-rec thingy and then post my feedback.

secret.animal said:
So, you can run lg flash tool, and take it back to zva or zvc and root. Use auto-rec to get TWRP. Install cloudy g2. Putting your change in. Or use the flash tool to go to zv8, grab official cm12. Root, use auto-rec to get TWRP, update TWRP. Flash cm12 (lollipop) with gapps. And change what you need to get your Sim working.
Click to expand...
Click to collapse
Will using Auto-rec be safe. Googled the app and many users reported white lines or bricked phones?

syedmoazzam said:
Will using Auto-rec be safe. Googled the app and many users reported white lines or bricked phones?
Click to expand...
Click to collapse
Bricked only if they used wrong one. If you are actually on ls980, use ls980.
Don't use t mobile version because you are using their service on an ls980 phone with Sim unlocked.
White lines is due to kernel. There was the two different screens used. That was identified but auto-rec kernel was never adjusted. When you flash new ROM, kernel will be replaced and that will be fixed.

secret.animal said:
Bricked only if they used wrong one. If you are actually on ls980, use ls980.
Don't use t mobile version because you are using their service on an ls980 phone with Sim unlocked.
White lines is due to kernel. There was the two different screens used. That was identified but auto-rec kernel was never adjusted. When you flash new ROM, kernel will be replaced and that will be fixed.
Click to expand...
Click to collapse
Ok thanks i will try it now

Thankyou very much sir.
Finally i have managed to access twrp and install cloudy g2 rom and i must say that this rom is fantastic.
Thankyou very much xda for solving my problem.
Bless you all guys ?

syedmoazzam said:
Thankyou very much sir.
Finally i have managed to access twrp and install cloudy g2 rom and i must say that this rom is fantastic.
Thankyou very much xda for solving my problem.
Bless you all guys ?
Click to expand...
Click to collapse
You are welcome. Glad things turned good for you

Having trouble putting TWRP on AS985, rooted

Hello!
I have a rooted AS985 currently running stock kitkat. Like many other phones that are available from my rural carrier, they are basically just Verizon variants that need Verizon variant ROMs, kernels, etc.. So, after viewing the LG G3 compatibility sheet I rooted successfully with Stump and then tried to flash a bump'd VS985 TWRP image. I've tried doing so with Flashify and the ADB method, but each time I boot into the recovery I get a black screen saying "[750] fastboot mode started". I've tried multiple versions of the VS985 TWRP to no avail.
If anyone could help I'd appreciate it!

BaconBaconBacon said:
Hello!
I have a rooted AS985 currently running stock kitkat. Like many other phones that are available from my rural carrier, they are basically just Verizon variants that need Verizon variant ROMs, kernels, etc.. So, after viewing the LG G3 compatibility sheet I rooted successfully with Stump and then tried to flash a bump'd VS985 TWRP image. I've tried doing so with Flashify and the ADB method, but each time I boot into the recovery I get a black screen saying "[750] fastboot mode started". I've tried multiple versions of the VS985 TWRP to no avail.
If anyone could help I'd appreciate it!
Click to expand...
Click to collapse
fastboot flash recovery "name of recovery image"

itsbighead said:
fastboot flash recovery "name of recovery image"
Click to expand...
Click to collapse
It appears to flash successfully, but when I enter recovery I see the same "fastboot mode started" screen.

Bump.
Anyone have any ideas of what to do here? Having (almost) vanilla Android on my phone would be amazing.

Have you looked here?
Works flawlessly
http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396

ingoljosh said:
Have you looked here?
Works flawlessly
http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396
Click to expand...
Click to collapse
I'm only able to select my tablet but not my phone for the download. Phone is still on KitKat, unfortunately.
Thanks.

If you find anything let me know. I tried to flash twrp with flashify but it is failing and I can't find anything to help me.

@BaconBaconBacon - I am facing the same issues with my AS985. When I bought it from eBay, it was already on Lollipop 5.0.1. Build Number is LRX21Y and Firmware is 21A. I was just not able to root it using traditional one-click root methods. Only thing that worked for me was Kingroot.
However, after getting Root access, I tried to flash various Recoveries, including the Bump'd recovery for VS985. I get the same error - "Fastboot mode started".
I thought that this was due to my current firmware (21A), and I was thinking of downgrading to VS985 10B.
I am just concerned about whether or not this will brick my phone. I understand that VS985 and AS985 are essentially the same devices, but just in case.
Have you tried this method of downgrading to 10B and then flashing the custom recovery?

did you guys ever figure out how to put twrp recovery on the as985 i have my lg g3 rooted with kingroot i couldnt get it to root with the other methods so if you have it figured mind helping a fellow partner.

taco009 said:
did you guys ever figure out how to put twrp recovery on the as985 i have my lg g3 rooted with kingroot i couldnt get it to root with the other methods so if you have it figured mind helping a fellow partner.
Click to expand...
Click to collapse
Yes, I was facing the same issue with Firmware 21A on my AS985. I figured that VS985 (Verizon) firmware is compatible with AS985.
I downgraded my firmware from 21A to 10B(for Verizon) Using a .TOT, .DLL and LG Flash Tool.
Instructions on androidexplained-dotcom-downgrade-lg-g3 (sorry, unable to post a link, might find something equivalent on XDA as well)
Later, I rooted the VS985-10B firmware using One Click Root scripts. Post that, I flashed TWRP (Bump'd) recovery, followed by VS985-35B firmware, CM13 (Marshmallow) and GApps.
Took me a long time to figure this out, but all works now.

ScrewDryver said:
Yes, I was facing the same issue with Firmware 21A on my AS985. I figured that VS985 (Verizon) firmware is compatible with AS985.
I downgraded my firmware from 21A to 10B(for Verizon) Using a .TOT, .DLL and LG Flash Tool.
Instructions on androidexplained-dotcom-downgrade-lg-g3 (sorry, unable to post a link, might find something equivalent on XDA as well)
Later, I rooted the VS985-10B firmware using One Click Root scripts. Post that, I flashed TWRP (Bump'd) recovery, followed by VS985-35B firmware, CM13 (Marshmallow) and GApps.
Took me a long time to figure this out, but all works now.
Click to expand...
Click to collapse
thanks man ill have to check this out i really want to have a working rooted device and also try out CM13 just glad you were able to make it work

taco009 said:
thanks man ill have to check this out i really want to have a working rooted device and also try out CM13 just glad you were able to make it work
Click to expand...
Click to collapse
Sure. Let me know if you are stuck. Happy to help.

ScrewDryver said:
Sure. Let me know if you are stuck. Happy to help.
Click to expand...
Click to collapse
how did you get it too pass for me it says fail check phone or dll since im on as985a21a it looks up my model and it wont let it go back

here is what i get

I think I had changed the build.prop file. Replaced all occurrences of AS985 by VS985. I had done this unknowingly to make AutoRec work.
I am guessing that FlashTool also worked because of that.

ScrewDryver said:
I think I had changed the build.prop file. Replaced all occurrences of AS985 by VS985. I had done this unknowingly to make AutoRec work.
I am guessing that FlashTool also worked because of that.
Click to expand...
Click to collapse
where might i be able to change that
okay i found out how but all i see with the as985 is one thing which i changed to vs985 anything else maybe a screenshot of what you changed may help thanks again!

okay im on vs98510b now question do i lose my root when i flash the new firmware vs985-35B firmware or is the vs985 just the upgrde to lollipop ?

You won't lose access to root.
However, I would suggest that you go in this order.
1. Root Vs985 10b firmware and install TWRP. You need to install a bumped recovery.
2. VERIFY if you can boot into recovery.
3. Place 35b bootstack, cm13 and gapps on your SD card.
4. Go into Recovery, and wipe system, data, cache etc. DONT wipe your internal SD card.
5. Flash the above 3 zip files one by one in a single session. Don't reboot before you have flashed all 3 zip files.
6. You should be able to boot into CM13.