CM12 based on 5.0.2 (Lollipop) OTA

Search This thread

ddzado

Senior Member
Nov 21, 2012
282
48
Try going to settings > mobile network > access point names and then switch to another one, then switch back to the one it was on.

Sent from my LG-VS980 using Tapatalk

Unfortunately I've done a good share of troubleshooting before I announced it was gone. APN switching, reset to default, remove sim card, switch preferred network. I'll have to probably wait for the next build or go to stock again.
 

da_reeseboy

Senior Member
Oct 30, 2008
1,301
535
Atlanta, GA
Unfortunately I've done a good share of troubleshooting before I announced it was gone. APN switching, reset to default, remove sim card, switch preferred network. I'll have to probably wait for the next build or go to stock again.
Sorry to hear. Thanks for replying tho, you saved me several hours of building a rom that wouldn't work.

Sent from my LG-VS980 using Tapatalk
 

ddzado

Senior Member
Nov 21, 2012
282
48
Well I wouldn't say don't build it. I'm the only one that is reporting an LTE problem of this magnitude. I'd love to be building the code on my own. I could probably find and fix this bug.
 
  • Like
Reactions: da_reeseboy

[] AL []

Recognized Contributor
Feb 22, 2011
2,870
4,636
Unfortunately there will be no build today. My build environment is all mucked up with the new 5.0 Lollipop source so I will have to sort everything out before making a build for us :/

But I did manage to get Lollipop to boot on my device -> http://imgur.com/OF1sNqg

Nothing works (yet) but the biggest obstacle of getting a booting build has been overcome

Next I'll have to start setting up SELinux our device

Hi there JC!

First off: thank you very much for all the work and support you've done and provided here for the VS980 - much, much appreciated.

Well, I very sorry to wake up the dead by quoting such an old post (KitKat break anyone?), but I thought that since I'm here to thank you, I would use the occasion to ask (although I think I know the answer -especially after seeing that you've just got a Moto X...). Anyway...: have you finally ever got your VS980 CM11 work environment up and running again? I ask because I've just order my G2 a few hours ago (thanks to this thread and CM11 KK-based) and I want to run CM11 on it and I've noticed that your M12 build links are down (was there an issue with it?). Anyhow, the last nightly is newer anyway, so no biggie there really! But, I'm wondering if you've ever thought of following what CM did and release a final M13 (actually labeled differently, but you know what I'm referring to here I'm sure). That was almost 6 months after the M12. There weren't many commits in the mean time, but I do believe that some important security fixes (heartbleed) were implemented -that unless I'm mistaken and they were actually fixes that people unofficially brought over from CM12...

Anyway, I know - I know: I should really stop and start learning how to build from sources myself (it's about time!!). But I thought I'd ask because I'm a die hard fan of CM11 and it might be all my G2 will ever run on...

Thanks again for everything and long live CM11! :p
 

Zimeron

Senior Member
Nov 4, 2010
429
247
Hi there JC!

First off: thank you very much for all the work and support you've done and provided here for the VS980 - much, much appreciated.

Well, I very sorry to wake up the dead by quoting such an old post (KitKat break anyone?), but I thought that since I'm here to thank you, I would use the occasion to ask (although I think I know the answer -especially after seeing that you've just got a Moto X...). Anyway...: have you finally ever got your VS980 CM11 work environment up and running again? I ask because I've just order my G2 a few hours ago (thanks to this thread and CM11 KK-based) and I want to run CM11 on it and I've noticed that your M12 build links are down (was there an issue with it?). Anyhow, the last nightly is newer anyway, so no biggie there really! But, I'm wondering if you've ever thought of following what CM did and release a final M13 (actually labeled differently, but you know what I'm referring to here I'm sure). That was almost 6 months after the M12. There weren't many commits in the mean time, but I do believe that some important security fixes (heartbleed) were implemented -that unless I'm mistaken and they were actually fixes that people unofficially brought over from CM12...

Anyway, I know - I know: I should really stop and start learning how to build from sources myself (it's about time!!). But I thought I'd ask because I'm a die hard fan of CM11 and it might be all my G2 will ever run on...

Thanks again for everything and long live CM11! :p

Flash official CM12, it works fine.
 

[] AL []

Recognized Contributor
Feb 22, 2011
2,870
4,636
Flash official CM12, it works fine.
Thanks.
But for me, newer doesn't always equal better

I don't want to run CM12 or M (for now anyway) and I've chosen this phone because of the first half of this thread...

edit:

I would really like opinions from (maybe past) CM11 users here:

running an official C11-M9 (JB-based?) on a LS980 would be much less stable than @jacpotclavin"s last CM11 KK-based (~M12) nightly on a VS980?

I'be just received the Sprint and was expecting a Verizon...

The above dilemma represents 4 months of CM11 commits and from this thread's comments, a much more stable than JB-based...

So hard to quantify "much more stable", but is it really a deal breaker here? i.e: worth the hassle of returning this phone and re-ordering a VS980?

Thanks for any input in advance.
 
Last edited:

Zimeron

Senior Member
Nov 4, 2010
429
247
Thanks.
But for me, newer doesn't always equal better

I don't want to run CM12 or M (for now anyway) and I've chosen this phone because of the first half of this thread...

edit:

I would really like opinions from (maybe past) CM11 users here:

running an official C11-M9 (JB-based?) on a LS980 would be much less stable than @jacpotclavin"s last CM11 KK-based (~M12) nightly on a VS980?

I'be just received the Sprint and was expecting a Verizon...

The above dilemma represents 4 months of CM11 commits and from this thread's comments, a much more stable than JB-based...

So hard to quantify "much more stable", but is it really a deal breaker here? i.e: worth the hassle of returning this phone and re-ordering a VS980?

Thanks for any input in advance.

Uh, you're asking for a new cm11 build? Why not just get the cm12 build which has all the fixes and more. A lot has changed since this thread started and official cm12 is just as good as JPCs, but it's updated with fixes, so most would argue better. This thread and it's roms are for the Verizon variant, they are separate for a reason from the sprint ones. I would suggest the official cm12 for the ls980, but since you don't care for those, I'd find another rom designed for your phone.
 
  • Like
Reactions: [] AL []

El Ha$on

Senior Member
Mar 9, 2009
573
100
NYC
Thanks.
But for me, newer doesn't always equal better

I don't want to run CM12 or M (for now anyway) and I've chosen this phone because of the first half of this thread...

edit:

I would really like opinions from (maybe past) CM11 users here:

running an official C11-M9 (JB-based?) on a LS980 would be much less stable than @jacpotclavin"s last CM11 KK-based (~M12) nightly on a VS980?

I'be just received the Sprint and was expecting a Verizon...

The above dilemma represents 4 months of CM11 commits and from this thread's comments, a much more stable than JB-based...

So hard to quantify "much more stable", but is it really a deal breaker here? i.e: worth the hassle of returning this phone and re-ordering a VS980?

Thanks for any input in advance.

Uh, you're asking for a new cm11 build? Why not just get the cm12 build which has all the fixes and more. A lot has changed since this thread started and official cm12 is just as good as JPCs, but it's updated with fixes, so most would argue better. This thread and it's roms are for the Verizon variant, they are separate for a reason from the sprint ones. I would suggest the official cm12 for the ls980, but since you don't care for those, I'd find another rom designed for your phone.
I'm going to +1 @Zimeron here. Official cm12.1 is solid. At first I was hesitant towards making the plunge because JC cm11 was so dependable. I ran that last M build he built for 10 months with no issues what so ever. When I got a replacement device I immediately wanted to just go that route but after reading thru the forums I found out that official cm bad updated their kernel base using the most recent so I figured it would be stable enough for daily driver status and I was correct on my assumption.

No random reboots, no bugs nothing that hinders me from using the device day to day, and I'm on a nightly (there hasn't been an snapshot build for us yet) so you would think there might be a potential issue but none.

I would recommend official cm, its been working great for me. Just be sure to flash Rashed bootstacks those are the recommended ones for these builds if you decide to take a plunge.

Sorry for completely sidetracking this thread any further questions should probably be taken to the Q&A thread of official cm12.1.

Sent from my LG-VS980 using Tapatalk
 
  • Like
Reactions: [] AL []

jsight

Senior Member
Apr 18, 2010
94
16
When I got a replacement device I immediately wanted to just go that route but after reading thru the forums I found out that official cm bad updated their kernel base using the most recent so I figured it would be stable enough for daily driver status and I was correct on my assumption.

On the other hand, I've been thinking about trying to find a good, stable older ROM. I've used multiple ROMs based on the latest and all constantly lose LTE for me. I can't blame someone for wanting an older one of they hit these issues and the older ROM didn't have them.
 
  • Like
Reactions: [] AL []

[] AL []

Recognized Contributor
Feb 22, 2011
2,870
4,636
OK, I think that I need to bring up a few points here... Sorry if me asking about CM11 seems to be old and off-topic here, but it's not like my long posts are getting in the way of intense rom development discussion or anything and I'm sure that all all agree that if I go in the general Q&A section and ask about jackpotclavin's CM11, chances are close to nil that someone knowing anything about it would ever show up or reply...

Anyhow, CM12's reliability/stability has never been any of my concerns in regards to prefering CM11 over it. On my current phone, I've had 'tweaked' CM12 builds make by a chinese guy back in December. A couple weks later, our main CM11 maintainers were on it and pulled what was already pretty decently running builds and soon we even had inverted (dark themed) Validus rom available and even more feature complete than CM12. So again, CM12 development status was and definitely is not the issie here.

What you guys forget when you see me as an alien coming here asking for a new CM11 build is that a phone doesn't run on an OS alone. Like most of you Im sure, I have quite a collection of user apps that I've accumulated over the last few years. Many of them that I had to spend a lot of time on I order to find the best available version to fit my needs, avoid problems (wakelocks/incompatibilities or just useless options/functions added in). I also spent quite some time on theming most of them to fit my homemade theme and I've also hacked a few of them (to change things that the CM theme engine cannot cover (like apos layout or stuff defined in smali), to remove excessive/obtrusive advertisement or even remove buttons/option that I found either not needed or simply out of place. One example of this would be the "update all" button in the Playstore: I would NEVER press that and didn't want to even see it on my screen, so I removed it.

Talking of tge PS, maybe 80% of the alps on my phone are not even listed under "My Apps" because I've either modded and re-signed them, got them directly from a developer or never even wanted them to get updated to a newer, bigger and bloated with useless new functionalities (and problems).

CM12 Theming: like many people in the xda threads I follow/participate, I just cannot stand Google's choice of moving to a light themed OS and most importantly, the changes they brought to the way that apps are now themed. In Kk, it is simple: one icon, one png. A few colors and styles clearly defined and easy to change and your good to go. With LP, hello big mess of spaghetti coding, bye-bye colorful icons and buttons and welcome to a world full of monochrome color filters, vector drawned icons and well hidden (and truely unnecessary) smali defined design elements. In simple words: comparatively to CM11, it is a nightmare to theme CM12 and the end results afe arguably uggly and/or extremely time consumming (if similar results is attempted - if even possible....).

And btw, (ok some will argue on its real utility or even its security -I got my reasons for it...,) but how's your Flash support in your CM12's browser? It works OK for me on CM11...
?

OK I could go on and on here, but I hope you get the point: I've spent a lot of time customizing and choosing every app installed on my phone and I'm not ready to move to a new OS just for the shake of of being "up to date". I don't want to do so and facing a large amount of now incompatible apps and have to start all of the above once again. And in many cases, those apps might have been updated for LP already yes, but so did all the built-up crap in them and bye-bye the possibility of trying original or older versions...

So thanks again for recommending me to move to CM12, but no thanks - not for now at least.

Sorry again for this long post, but I hope that I've brought a different perspective on things here -at least. Android is a world of diversity and freedom of choice; I'd never blame someone for choosing things that I wouldn't use. So please do the same here: my CM11 question of an updated build (with security patches) was not misplaced and perfectly appropriate.

Cheers,
/AL

(I don't feel like proof reading this post, so sorry for the typos)
 

Zimeron

Senior Member
Nov 4, 2010
429
247
OK, I think that I need to bring up a few points here... Sorry if me asking about CM11 seems to be old and off-topic here, but it's not like my long posts are getting in the way of intense rom development discussion or anything and I'm sure that all all agree that if I go in the general Q&A section and ask about jackpotclavin's CM11, chances are close to nil that someone knowing anything about it would ever show up or reply...

Anyhow, CM12's reliability/stability has never been any of my concerns in regards to prefering CM11 over it. On my current phone, I've had 'tweaked' CM12 builds make by a chinese guy back in December. A couple weks later, our main CM11 maintainers were on it and pulled what was already pretty decently running builds and soon we even had inverted (dark themed) Validus rom available and even more feature complete than CM12. So again, CM12 development status was and definitely is not the issie here.

What you guys forget when you see me as an alien coming here asking for a new CM11 build is that a phone doesn't run on an OS alone. Like most of you Im sure, I have quite a collection of user apps that I've accumulated over the last few years. Many of them that I had to spend a lot of time on I order to find the best available version to fit my needs, avoid problems (wakelocks/incompatibilities or just useless options/functions added in). I also spent quite some time on theming most of them to fit my homemade theme and I've also hacked a few of them (to change things that the CM theme engine cannot cover (like apos layout or stuff defined in smali), to remove excessive/obtrusive advertisement or even remove buttons/option that I found either not needed or simply out of place. One example of this would be the "update all" button in the Playstore: I would NEVER press that and didn't want to even see it on my screen, so I removed it.

Talking of tge PS, maybe 80% of the alps on my phone are not even listed under "My Apps" because I've either modded and re-signed them, got them directly from a developer or never even wanted them to get updated to a newer, bigger and bloated with useless new functionalities (and problems).

CM12 Theming: like many people in the xda threads I follow/participate, I just cannot stand Google's choice of moving to a light themed OS and most importantly, the changes they brought to the way that apps are now themed. In Kk, it is simple: one icon, one png. A few colors and styles clearly defined and easy to change and your good to go. With LP, hello big mess of spaghetti coding, bye-bye colorful icons and buttons and welcome to a world full of monochrome color filters, vector drawned icons and well hidden (and truely unnecessary) smali defined design elements. In simple words: comparatively to CM11, it is a nightmare to theme CM12 and the end results afe arguably uggly and/or extremely time consumming (if similar results is attempted - if even possible....).

And btw, (ok some will argue on its real utility or even its security -I got my reasons for it...,) but how's your Flash support in your CM12's browser? It works OK for me on CM11...
?

OK I could go on and on here, but I hope you get the point: I've spent a lot of time customizing and choosing every app installed on my phone and I'm not ready to move to a new OS just for the shake of of being "up to date". I don't want to do so and facing a large amount of now incompatible apps and have to start all of the above once again. And in many cases, those apps might have been updated for LP already yes, but so did all the built-up crap in them and bye-bye the possibility of trying original or older versions...

So thanks again for recommending me to move to CM12, but no thanks - not for now at least.

Sorry again for this long post, but I hope that I've brought a different perspective on things here -at least. Android is a world of diversity and freedom of choice; I'd never blame someone for choosing things that I wouldn't use. So please do the same here: my CM11 question of an updated build (with security patches) was not misplaced and perfectly appropriate.

Cheers,
/AL

(I don't feel like proof reading this post, so sorry for the typos)

If you truly do all that, you have a very unique and odd use case. With that being said, if you're capable of doing all that, then you're capable of building the rom yourself and should get used to doing that, since CM11 is now two versions behind, soon to be three.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 96
    This ROM is CM12 for the VS980 based on the Verizon LG G2's Lollipop update. It is different from the official CM11 and CM12 for the VS980 because those builds use LG's Jellybean kernel source merged into CAF's kernel source, and Jellybean blobs, and Jellybean modem; whereas this ROM uses LG's Lollipop kernel source and Lollipop blobs and the Lollipop modem.

    For best results on this ROM, install the stock VS980 39A build, ensure your sensors, 4G/LTE, and GPS are working 100%, then backup your phone and EFS partition; then you can install

    Issues:
    Some people have reported getting soft reboots (crashing back to the boot animation). I'm not 100% sure as to what the cause is, or how to replicate the issue.

    Requirements for this ROM:
    1. You must be on the VS980 39A modem/bootstack
    2. Your aboot version must be either from KitKat or Jellybean

    March 21st, 2015
    Uses newer CM source from March 21st. Also includes support for Android FLP, as well as a few GPS fixes here and there
    Note: some users have reported soft reboots using Bluetooth, and GPS not locking in the previous builds.
    https://www.androidfilehost.com/?fid=95916177934544450

    Click to expand older CM12 builds

    March 18th, 2015
    Uses newer source from March 18th. Note: some users have reported soft reboots using Bluetooth, and GPS not locking in the previous build.
    https://www.androidfilehost.com/?fid=95916177934543381

    March 14th, 2015
    Note: There may be regressions in this build as I could not test everything (this is the first build using VS980 39A blobs) so there may be something broken that I was not able to find. You should backup everything including your EFS partition before installing!
    Uses newer source from March 14th, as well as blobs from the VS980 39A build (Note: You must be on the VS980 39A modem now). I've switched from Loki to Bump, so the 12B aboot is no-longer a requirement (you can use KitKat if you want, or you can stick with 12B). I have also switched to AndroidFileHost.com!
    https://www.androidfilehost.com/?fid=95916177934541436

    March 4th, 2015
    Uses newer source from March 4th, uses the kernel source from Verizon's semi-official VS980-39A build, fixes the stock camera
    Code:
    903bd755dc4cca0b1ad7676a549a859c  cm-12-20150304-vs980.zip
    https://mega.co.nz/#!x951mQqY!dLAoDOdv_UloVmeR1UvkkE07LOZzdHGdpwAY3p8GoTY

    February 23th, 2015
    Uses newer source from February 23rd
    Code:
    bfdb82836a6744f6cf2e195fd95d67d0  cm-12-20150223-vs980.zip
    https://mega.co.nz/#!5oJi3K7Q!D0CWdosjdhMpC_qUJCX5LBVM8qCBX5D8LobD4qmxhOo

    February 17th, 2015
    Newer source synced from earlier today. Also includes a few radio-related patches (hopefully this will fix MMS for some users), and I enabled color gamma controls in the kernel
    Code:
    248c0c0fb8fba88c12f3395cb6fcaf93  cm-12-20150217-vs980.zip
    https://mega.co.nz/#!V9oDFS5I!ZZd1pmRQG_2csT-kNtVIHnc2K1W2JJAyqf0PGlHzySk

    February 15th, 2015
    Second build, fixes the low memory killer being too aggressive and killing background apps too frequently, which caused screen redraws, chrome tabs reloading, etc. Also should fix the sensors being broken for those who came from Jellybean modems; so now you shouldn't have to go back to stock anymore to get working sensors. Early on in CM11, sometimes enabling bluetooth would cause the wifi/bluetooth card to crash and result in slugging performance and battery drain as the kernel endlessly tries to turn on bluetooth. I made it so if the card crashes, it will just re-init the wifi card, so it won't cause excess battery drain and sluggish performance if it crashes (I'm not sure if it is a problem with CM12, but it doesn't hurt having it there in case)
    Code:
    4d570e16c5fff11ae5b6eaac673e894a  cm-12-20150215-vs980.zip
    https://mega.co.nz/#!ptxD0D4J!dySL2jwM5OlI7G3Da0XR4pmMUurB89ghl7_5AMkUtI4

    February 14th, 2015
    Initial alpha build
    Code:
    97410722f4545cb2e41a8b3a95d3fb16  cm-12-20150214-vs980.zip
    https://mega.co.nz/#!F5AyHZiZ!h5gakodilDVjEY-g9SdOYTjoaQn4YzyEpEKEiAosKvE

    2014: Click to show the older CM11 (KitKat) builds and instructions

    These builds from 2014 and no-longer truly supported
    Note: if you are already on 24A, 25A, 25B, or 26A, or 27A root it, and proceed to step 5. If you are on Lollipop, you must KDZ back to a version of KitKat and then follow the instructions.

    Warning: this process is not for beginners! Read the entire post before proceeding. Backup everything important first! It is important that your phone does not reboot until after you have completed all of the steps.

    Click below to expand instructions

    Step 1: Go back to build 12B (COMPLETELY STOCK!)

    Step 2: Root 12B and install a Superuser package

    Step 3: MAKING SURE YOU'RE ROOTED (There is no known root method after you're already on the KitKat OTA!)

    Step 4: Follow this guide to upgrade your phone to build 24A (This is the stock software that this ROM is based on) At this point, make sure that your device has everything working (like 4G, and also get a GPS lock on the stock software before proceeding to step 5)

    Step 5: At this point, you're on 24A and rooted; however, you cannot run custom boot images because the 24A OTA has patched the only known exploit which allows us to run custom boot images, so we must revert the one part that's exploitable to the 12B version. This file is called aboot, and is only a megabyte. However, this is imperative to boot your phone, so you CANNOT mess up this step. Failure to verify that your aboot download and flashing a broken aboot WILL PROBABLY RESULT IN A LEGITIMATE BRICK. So you MUST verify the download, and after pushing it to your device, you must verify that it is not broken in any way before writing the 24A aboot with the one from 12B. Download aboot from here and push it to your device. After pushing it to your device, run an md5sum check on it to ensure that the output is:
    Code:
    2ce58393effb26fe87b3e66ac6b433d8 aboot.bin

    Step 6A: Now you're ready to write the downloaded aboot to your aboot partition. You must run this command as root:
    Code:
    dd if=aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot

    Step 6B (April 6th edit): Mixing and matching the 4.2 aboot and 4.4 laf partition breaks download mode. The only way to fix it is to flash the 4.2 laf partition. Use this guide to fix your download mode with the following:
    Code:
    dd if=laf.bin of=/dev/block/platform/msm_sdcc.1/by-name/laf

    Step 7: THIS IS IMPORTANT! The old aboot is incompatible with the new boot image that comes from the 24A OTA, so you must install a boot image that's compatible with stock KitKat and also works with the old aboot, so download this boot image and verify its md5sum
    Code:
    200eb4b8fc165751aa24d770737b2716  boot.emmc.win
    and then write it to your boot partition with:
    Code:
    dd if=boot.emmc.win of=/dev/block/platform/msm_sdcc.1/by-name/boot

    Step 8: Since you're only running stock 24A, you don't have a custom recovery! So download this TWRP custom recovery (which is already loki'ed) and verify its md5sum
    Code:
    4835cdcf2432ee1c4eb8cef73e2a24c1  recovery.lok
    and then write it to your recovery partition with:
    Code:
    dd if=recovery.lok of=/dev/block/platform/msm_sdcc.1/by-name/recovery

    Step 9: At this point, you will essentially be running 24A, with a exploitable aboot which allows for custom boot images. You also have a working boot and recovery image which is compatible with the exploitable aboot. The rest is normal ROM flashing, and is cruising from here on out.

    Step 10: Take a breath

    Step 11: Download the ROM from below

    Step 12: Install ROM in recovery, if coming from a previous but recent CM11 build (say from within a week), you shouldn't have to do a factory reset, if you don't meet that criteria, just do a factory reset anyways.

    Step 13 (Optional): Install a gapps package

    Step 14: Reboot and enjoy!
    Zips and Changelogs below:
    If you are attempting to download a zip on your phone, try requesting desktop mode in the browser and it should download.

    Latest nightly build
    November 2nd, 2014: uses newer CM11 source from nightlies that were dated cm-11-20141102 (changelog here).
    Make a backup before installing just in case.
    https://mega.co.nz/#!JgYinZZJ!NXoyDMZvRmN0lYk6Q2mQMzI5iOMBKT1ZmexFa-SDLNg
    Code:
    1bfe4b0b3ec70da4d56129e7b32da177  cm-11-20141102-vs980.zip

    Latest snapshot build
    November 13th, 2014: Snapshot update (M12), uses newer CM11 source from snapshot builds dated cm-11-20141112 (changelog here). Note: you should not install this build if you are currently on a build dated after our November 2nd build! Make a backup before installing just in case
    https://mega.co.nz/#!o4ZSBQCK!17gQdjEs3ggw5wQCzUPdzsNsdD6tvUQNkxRLUsGpaAY
    Code:
    98cbe476ea837289bf5ee633677d39f1  cm-11-20141113-M12-vs980.zip

    Click below to show older builds

    October 8th, 2014: Snapshot update (M11), uses newer CM11 source from snapshot builds dated cm-11-20141008 (changelog here). Note: you should not install this build if you are currently on a build dated on or after September 30th build! Make a backup before installing just in case
    https://mega.co.nz/#!dkx2CJhY!AGQ1l1jwPhX-hDQ2JkdEiq87epP8pjm_3FXRbkdaqpw
    Code:
    ed0bdf1765d78218fb8d235d75e3c139  cm-11-20141009-M11-vs980.zip

    October 26th, 2014: uses newer CM11 source from nightlies that were dated cm-11-20141026 (changelog here).
    Make a backup before installing just in case.
    https://mega.co.nz/#!F0glXDxB!p_nshMSz_11ShNl7FHfmgEENu3FrE1lrxAtJ0ILKgiY
    Code:
    b5c02e87ec3bf575e6cb2f3b37c8b4fc  cm-11-20141026-vs980.zip

    October 19th, 2014: uses VS980-26A blobs and kernel sources, also uses newer CM11 source from nightlies that were dated cm-11-20141019 (changelog here).
    Make a backup before installing just in case.
    https://mega.co.nz/#!p5Rw1Z5Y!l1XQQ-nlWox1JoyeWGaRWw-pjy58VKGJu3rEb01bQs0
    Code:
    73f397ffdd0571f23ba2e056eb8df5bb  cm-11-20141019-vs980.zip

    October 13th, 2014: uses newer CM11 source from nightlies that were dated cm-11-20141013 (changelog here).
    Make a backup before installing just in case.
    https://mega.co.nz/#!FhYzxDoC!zDD9de-EodKFiHM3HPSnlVGko5BpkJD-tYWDvQOMVhM
    Code:
    a2aff425d2d1b2c9362c328eb0f762fe  cm-11-20141013-vs980.zip

    September 28th, 2014: uses newer CM11 source from nightlies that were dated cm-11-20140928 (changelog here).
    Make a backup before installing just in case.
    https://mega.co.nz/#!95oSDBrK!4yGRKLolLsinWHSgb_Jbd0LNUJxIKaZO15gPwhAEUp8
    Code:
    d9a851a63a6b9888bb6b984917dea41e  cm-11-20140928-vs980.zip

    September 21st, 2014: uses newer CM11 source from nightlies that were dated cm-11-20140922 (changelog here).
    Make a backup before installing just in case.
    http://www.mediafire.com/download/5wjqjxw7u4hud31/cm-11-20140922-vs980.zip
    Code:
    4efb342e927307a8df9ad8e8d39446a0  cm-11-20140922-vs980.zip

    September 16th, 2014: uses newer CM11 source from nightlies that were dated cm-11-20140915 plus a few more patches, but not exactly all of the patches that will be in builds dated cm-11-20140916(changelog here).
    Make a backup before installing just in case.
    https://mega.co.nz/#!VkRV1Kqa!cxC4Qzezkuc6nFrR-5BRQ-gYqVymIOzMQIU1b2GNpwo
    Code:
    0e56b5c6d31a7dbcb6eee47a7bbaee02  cm-11-20140916-vs980.zip

    September 15th, 2014: uses newer CM11 source from nightlies that were dated cm-11-20140915 (changelog here).
    Make a backup before installing just in case.
    Do this to fix MMS! Credit to bouchigo
    https://mega.co.nz/#!shYRyTyD!PNA9hbTkiXqMHo856RbhoBZ6OiWmxks40dKc5rKRHEY
    Code:
    a05b210b8aafeb6ea2bdfdae32e54e75  cm-11-20140915-vs980.zip

    September 7th, 2014: uses newer CM11 source from nightlies that were dated cm-11-20140907 (changelog here).
    Make a backup before installing just in case.
    https://mega.co.nz/#!ggBQlazY!9ivVHhuG_zhRfSSf83A8AVADTB8K1J7u7qF9IIdeZww
    Code:
    843d517cdf14253ec961801f426c0e25  cm-11-20140907-vs980.zip

    September 2th, 2014: uses newer CM11 source from nightlies that were dated cm-11-20140902 (changelog here).
    Make a backup before installing just in case.
    https://mega.co.nz/#!hxAlxSJI!9fCWtxYmp9LGrZ5WWodPZsCWQ614Fnx-Tyka5EdjNtw
    Code:
    dc3d57b92f90b1d6d6639b7264ed18c9  cm-11-20140902-vs980.zip

    August 24th, 2014: uses newer CM11 source from nightlies that were dated cm-11-20140823 (changelog here).
    Make a backup before installing just in case.
    https://mega.co.nz/#!RgRTyRBD!wiBiiuuMjcxDG5Do1GDtv2TxMfG9ZIiziRicNygAXb4
    Code:
    a3a534c374d6783d70af3be073acc4ad  cm-11-20140824-vs980.zip

    August 17th, 2014: uses newer CM11 source from nightlies that were dated cm-11-20140817 (changelog here).
    Tethering is now working :)
    Make a backup before installing just in case.
    https://mega.co.nz/#!Ag4QVJjR!bTWaAw1f1EQ-ZP97s5-C9rQwjZboaaxSEVRRDvlzvyg
    Code:
    2fe7f7a1205af7b0abafa678a6133647  cm-11-20140817-vs980.zip

    August 12th, 2014: uses newer CM11 source from nightlies that were dated cm-11-20140811 (changelog here).
    Tethering is not currently working
    Make a backup before installing just in case.
    https://mega.co.nz/#!p1ZFmIKI!efLfZ8iX7VHETKOt1PjCaMni2gGpoIlRPG9UMa9_FCg
    Code:
    e59f5f96d0b55c02399c01293b72552d  cm-11-20140812-vs980.zip

    August 4th, 2014: Snapshot update (M9), uses newer CM11 source from snapshot builds dated cm-11-20140804 (changelog here). Note: you should not install this build if you are currently on the July 29th build, older builds only! Make a backup before installing just in case.
    https://mega.co.nz/#!9lhHBCKS!Gfd17muV1kndFvbhfJCfjHt_dWp4uCocuZQDjwPEzbk
    Code:
    63e92c0f0571e2d405e1b4926474002d  cm-11-20140805-M9-vs980.zip

    July 29th, 2014: uses newer CM11 source from nightlies that were supposed to be dated cm-11-20140730 (changelog here).
    It should be noted that an official snapshot build (M9) is due to be right around the corner, and that taking this update may mean that you cannot take our version of an M9 release once I build it!!
    Make a backup before installing just in case.
    https://mega.co.nz/#!045xARzY!ltCgmiYjeHEJLZmB88yuLqGgOHWcEkzHpXCgqDUde1Q
    Code:
    df5f18689e2249fa3ef535d80ac3140b  cm-11-20140730-vs980.zip

    July 19th, 2014: uses newer CM11 source from nightlies dated cm-11-20140718 (changelog here). Make a backup before installing just in case.
    https://mega.co.nz/#!kxhBSKDQ!gWjazNvuh5horbPFWbVOA9XWarKwcOegTTTCbXs09yE
    Code:
    9137fc43068a71abc90a3b5f1f40a360  cm-11-20140719-vs980.zip

    July 10th, 2014: uses newer CM11 source from nightlies dated cm-11-20140709 (changelog here). Make a backup before installing just in case.
    https://mega.co.nz/#!V9IEBAaK!eldMtrTesNaCOn6TOaMQ3xfINmFDRSrSXgoYey5GdpI
    Code:
    c33f2034104a3d71519be4391c1bf816  cm-11-20140709-vs980.zip

    July 3rd, 2014: uses newer CM11 source from nightlies dated cm-11-20140703 (changelog here). Make a backup before installing just in case.
    https://mega.co.nz/#!FoB3ET5Y!KjMZGo6Prxl41T_tbwe0A0TcjIBshoC7HzsxVhr-E3U
    Code:
    df6e84f87df2267f8c59284acaa027e4  cm-11-20140703-vs980.zip

    June 30th, 2014: uses newer CM11 source from nightlies dated cm-11-20140629 (changelog here). Make a backup before installing just in case.
    https://mega.co.nz/#!dtYz0Cxb!q10Z3EifASfLwt67OPLveFdd3T2woiKyd7UKbVhTkxo
    Code:
    f3861e17dedc9bac2480d10f013fc8c6  cm-11-20140630-vs980.zip

    June 22th, 2014: uses newer CM11 source from nightlies dated cm-11-20140622, which includes the 'Heads Up' feature, and is Android 4.4.4 (changelog here). Make a backup before installing just in case.
    https://mega.co.nz/#!984SnZyQ!q5SAOuydLOGvxlSlrPMVlCuMIgpe8AYYx9joW-XLbko
    Code:
    4cf2e1e940332e0745c0df8bec6f68a4  cm-11-20140622-vs980.zip

    June 19th, 2014: uses newer CM11 source from nightlies dated cm-11-20140619 (changelog here). Make a backup before installing just in case.
    https://mega.co.nz/#!8tpDyD6a!p1Kx6sgVG-BKQhwD9mlYVGG6yL-9JedLqGi7oPgj414
    Code:
    9ccfdecc56ed21ccbb2abbaffa89190b  cm-11-20140619-vs980.zip

    June 12th, 2014: uses updated nightly source from the nightlies dated June 11th. This build fixes the YouTube playback issues and fixes a few mismerges of 4.4.3 into the CM11 source. I have also cherry-picked a few security patches in the kernel in this build. Make a backup just in case. There is also a new gapps package available.
    Futex vulnerability patched in this update, as well as all future updates.
    https://mega.co.nz/#!F9gRSahD!GTFiFCR2-YVGhqzOg23MBkDRdqPjBd5hETyqtKfmCLY
    Code:
    fc56617cd3e4577b004a4caa01a98ec7  cm-11-20140612-vs980.zip

    June 8th, 2014: Snapshot update, uses the stable CM11 branch source from snapshots dated cm-11-20140609-SNAPSHOT-M7-*.zip. You should not install this update if you are the June 6th (4.4.3) build, but installing this from any other build should be okay. (changelog here). Make a backup before installing just in case.
    https://mega.co.nz/#!9h5AgDqK!dhCrM7IL2za1O23pgFaNJK0M0garV6b0h3WiuLhg7qY
    Code:
    96984171b6c8386388fca3489e62c6d5  cm-11-20140608-M7-vs980.zip

    June 6th, 2014: uses newer CM11 (4.4.3!) source from nightlies dated cm-11-20140606 (changelog here). Make a backup before installing just in case.
    https://mega.co.nz/#!BxJ3XQzT!BGgneaGQCYZi8r-OeePlqTjth0EgimSF_Nl49Ahqkvo
    Code:
    81af1ad2225021035fc59b297ebeab43  cm-11-20140607-vs980.zip

    May 21st, 2014: uses newer CM11 source from nightlies dated cm-11-20140520 (changelog here). Includes support for covers with the lid, and also a fix for the gamma controls. Make a backup before installing just in case.
    https://mega.co.nz/#!99hVzYxK!Ot-Yvx52622R51drm5BniLe0V-5T8Rh9nYWiIC918g8
    Code:
    351cebe1259084b5ffe67f2ab9b76646  cm-11-20140520-vs980.zip

    May 4th, 2014: Ninth update, a snapshot build. Built off the CyanogenMod stable (snapshot) branch, so this is equivalent to every device's cm-11-20140504-SNAPSHOT-M6-* build. Make a backup before installing just in case.
    https://mega.co.nz/#!MlgCVCDC!rMDZ_l8TZOrWYsOdsJffP6BvvWrAHqSkJxuQrJnTfIo
    Code:
    2fb08218abbc777424d1366f0c58d8f4  cm-11-20140504-vs980.zip
    Mirror:
    Uploading

    April 30, 2014: uses updated nightly source from the nightlies dated April 30th. Fixes include a patch to make Bluetooth more stable (hopefully) and interactive governor is working now. Make a backup before installing just in case.
    https://mega.co.nz/#!skZ2gYzY!Jjqm_JgQ_DSwnhwDzt5bEXxgY2qKbqS8HXJuCey71fw
    Code:
    a0a269f405ae4ca8279aab77e445d759  cm-11-20140430-vs980.zip

    April 24, 2014: uses updated nightly source from the nightlies dated April 24th. Pandora should be fixed.
    https://mega.co.nz/#!Ihh2FKJa!YHlyP0zCIJYE8jwdh_gKPZS1jtJE0sQPZm7vDWKjDzk
    Code:
    91190b93c0dfa595eefe6d454e420328  cm-11-20140425-vs980.zip

    April 18, 2014: uses updated nightly source from the nightlies dated April 18th. It also uses the RIL files from 4.2; so there should be no issues with getting stuck with 3G.
    https://mega.co.nz/#!5swBXKwQ!3jphnECTxMrfIoAXg6HBg6vfxR9Qs5Qj5iiO6ePzs2E
    Code:
    6a224dd33a1b7165dd7e4eacd0206c10  cm-11-20140418-UNOFFICIAL-vs980.zip

    April 17, 2014: uses updated CM source, also uses the 4.4.2 RIL proprietary files. I highly suggest making nandroid backup of your efs partition before installing. That way you can restore in case anything goes wrong data connectivity wise
    Build pulled due to data connectivity issues.
    Code:
    714327997194e5ea6e36e2f85e32265a  cm-11-20140417-UNOFFICIAL-vs980.zip

    April 12, 2014: configuration files updated to 4.4.2. I would suggest making a nandroid backup before installing in case something is broken. Also updated CM source. Here's the changelog
    https://mega.co.nz/#!wsoQyAoL!AtQCsRmA4MmiNHwPceg68QMg_DT1ktT3JKXR6F6Lv9c
    Code:
    4ee5164055291f4eb6e44667dc62cff9  cm-11-20140412-UNOFFICIAL-vs980.zip

    April 5, 2014 BT NFC: Fixes BT and NFC (to my knowledge), also includes fixes in ROMs below
    http://www.mediafire.com/download/cl144fi3lhlc24c/cm-11-20140405-UNOFFICIAL-vs980-BT-NFC.zip
    Code:
    277e65dbec9704b91691450d2cf3a9e6 cm-11-20140405-UNOFFICIAL-vs980-BT-NFC.zip

    April 5, 2014: Fixed bug where only 3G service was not attainable in some cases, updated to April 4th CM sources, uses Verizon's 24A kernel source, still no bluetooth
    http://www.mediafire.com/download/otcaat3uf6n2bcb/cm-11-20140405-UNOFFICIAL-vs980.zip
    Code:
    f7299cd441e566521a977847fa33af9e cm-11-20140405-UNOFFICIAL-vs980.zip

    April 1, 2014: First upload
    http://www.mediafire.com/download/2pk3zeeawg3afr7/cm-11-20140402-UNOFFICIAL-vs980.zip
    Code:
    696027626342f47f4fe3b04d026c9550 cm-11-20140402-UNOFFICIAL-vs980.zip
    About this ROM:
    Official CM11 uses the proprietary binaries and libraries of the offical Android 4.2 build for the LG G2 (Jellybean).
    Its kernel sources were merged into CAF kernel sources, and along the way, something happened where occasionally, the device won't wake up and reboot upon pressing the post button (commonly called an SOD).
    This ROM is based on the CM11 sources, but updated with a 4.4.2 kernel, and 4.4.2 binaries and libraries from the official LG G2 OTA (VS98024A)

    I would like to thank:
    Everybody who has contributed to the CyanogenMod project
    Everybody who has contributed to Linux
    @xdabbeb for cracking the code to get the 24A OTA to install and for the well-written guide for installing 24A
    Dan Rosenberg (djrbliss) for Loki (the exploit that allows for custom boot images)
    @Dees_Troy (for TWRP)
    Ricardo Cerqueira and Erik Hardesty (and all other LG G2 device maintainers)

    Changes from the stock cm-11.0 branch:
    vendor/lge: https://github.com/JackpotClavin/proprietary_vendor_lge/commits/cm-11.0-4.4.2Kernel

    device/lge/g2-common: https://github.com/JackpotClavin/android_device_lge_g2-common/commits/cm-11.0-4.4.2Kernel

    device/lge/vs980: https://github.com/JackpotClavin/android_device_lge_vs980/commits/cm-11.0-4.4.2Kernel

    kernel/lge/msm8974: https://github.com/JackpotClavin/android_kernel_lge_msm8974/commits/cm-11.0-4.4.2Kernel

    hardware/qcom/display-caf: run this: git remote add CAF-display git://codeaurora.org/quic/la/platform/hardware/qcom/display && git fetch CAF-display && git cherry-pick 8fec5c360f8d9b888d605ce01cb7ffab6480623b

    hardware/qcom/media: revert cf8408186605323a6797e5f431192ab434e79fff

    frameworks/native: cherry-pick http://review.cyanogenmod.org/#/c/61459/ (no longer needed since we are going with the 4.2 RIL)
    49
    Unfortunately there will be no build today. My build environment is all mucked up with the new 5.0 Lollipop source so I will have to sort everything out before making a build for us :/

    But I did manage to get Lollipop to boot on my device -> http://imgur.com/OF1sNqg

    Nothing works (yet) but the biggest obstacle of getting a booting build has been overcome

    Next I'll have to start setting up SELinux our device
    35
    That the last snapshot for KitKat?

    yep

    I'm gonna work on getting Lollipop up to daily driver status (hopefully) this weekend
    33
    Just a quick update on the status of Lollipop:

    Media playback is not working, at all. Watching a video will freeze the device and it will soft reboot, the same goes for video encoding; so it is still pretty much unusable at this point. I'm still actively working on getting everything up and running, but it might take a while. It looks like I'm gonna have to update the kernel to work with Lollipop, so it will take time to get that all working (plus testing, I don't want anybody getting black lines or SODs on this ROM)

    I've refunded the two donations (thank you!) I received since I made the bold statement of trying to get a daily driver up and running by the weekend, because I failed to realize that LG's KitKat kernel isn't gonna play well with the the new changes made in Lollipop, so I'll need to upgrade it to get everything working well.

    In the meantime, you all should check out that other Lollipop thread if you wanna get your Lollipop-rocks off, I won't mind :p

    PSA, that said Lollipop ROM still uses the Jellybean kernel and proprietary files, so you'll need to downgrade your modem to 12B if you wanna run that, or else your device won't boot
    31
    I'm beginning to think I've fixed the CM12 lockup issue that I've been talking about for the past month or so that has been delaying the CM12 Alpha release

    If I go the rest of today and tomorrow without a lockup, I'll throw together a CM12 Alpha build on Sunday and post it Sunday night if everything goes well

    Here's to hoping I haven't spoken too soon...