News

CyanogenMod releases final CM11 and CM12 builds as they focus on CM12.1

14

2000px-CyanogenMod_Cid.svg

Although we admit, we don’t ROM as hard as we used to, we know many of you are still rooting and flashing like it was 2009. Those of you who are fans of CyanogenMod’s custom ROM are in luck. The Android developers announced last night that final builds for both CM11 and CM12 have been released. Also known as a snapshot, these stable builds will officially conclude CyanogenMod’s work on 11.0 and 12.0 as they shift focus on CM12.1 (based on Android 5.1) and look ahead to Android M.

So, why did CyanogenMod release another CM11 build which is based on KitKat? Apparently, CyanogenMod found that a good amount of their users were still running these KitKat builds although they’re not exactly sure why. We know not everyone has been a fan of Lollipop or nightly builds, so perhaps these users were just waiting for a nice stable Lollipop build before moving forward. That, or they just like really enjoy KitKat.

In either case, you can find the snapshots on CyanogenMod’s download page here. As usual, CyanogenMod wouldn’t commit to a specific date users can expect a CM12.1 (Android 5.1.1) release build, so you’ll just have to hang in there a little while longer.

[CyanogenMod]

Chris Chavez
I've been obsessed with consumer technology for about as long as I can remember, be it video games, photography, or mobile devices. If you can plug it in, I have to own it. Preparing for the day when Android finally becomes self-aware and I get to welcome our new robot overlords.

Every Moto X (2nd Gen) Pure Edition is now receiving Android 5.1 Lollipop

Previous article

Our free Adult Swim VR headset finally arrived and it’s pretty great

Next article

You may also like

14 Comments

  1. I don’t know who I should be more grateful to – Cyanogenmod for making those final builds for KitKat or Chris for reporting it. I’ll split it 50/50. Thanks so much!

    Edit: Found out the Nexus 5 either never got any Cyanogenmod 11/KitKat updates after October or if it did they’re not on the Cyanogenmod website anymore. Kinda disappointing.

  2. Yay, the 5.1.1 nightlies have been pretty stable but there are definately a few annoying bugs I’m eager to be rid of.

    1. What phone and what bugs please?

  3. Son when I was your age, we were ROMin hard, just ROMin our faces off almost every day.

    1. You like ROM-ming your phone really hard, don’t you? ?

  4. Seriously the only reason that peeps aren’t going all in anymore is the lack of rootable devices. Locked boot loader devices across the board. The carriers did they’re jobs effectively (excluding TMO)
    Now all you have are imports and the Nexus line..
    Smh, I miss the wild west dayz….

    1. That’s why I ditched my Note 3 for the OnePlus. Rooted, unlocked, and ROM flashing at will. Like the good old days.

      1. Same here bud and have been happy ever since…

        1. Ditto!

      2. You can’t root or unlock the Note 3? Is that the case with all the versions of it? How about the Note 4?

        1. The AT&T Note 3 can be rooted, not unlocked. Samsung is amongst the worst now about locking the bootloader. They hide it under the veil of improved security, but it’s just them not wanting people to own their own phones and be able to do whatever they want.

          1. I don’t really get what the point of a locked bootloader is. What benefits/incentives exist for manufacturers to actually want to go through the trouble of locking the bootloader?

          2. You are forced to use their version of Android, their bloatware. But bigger than that, unlocking the bootloader allows you to install software that allows you to do things that your phone’s manufacturer and service provider don’t want you to do without paying more for it.

    2. Ummm, Sony?

Leave a reply

Your email address will not be published. Required fields are marked *

More in News