CM 13.0 Release – ZNH5Y

DEF CON 24 is officially in the books, so what better time to release a new CM snapshot, full of new features and security updates? These releases were branched on August 1st, 2016 (branch stable/cm-13.0-ZNH5Y) and bring our snapshot releases up from Android 6.0.1 r17 to Android 6.0.1 r61.

The first thing you should notice is our new custom boot & dexopt screen, getting rid of that bright white for something a bit prettier and informative to look at while your phone upgrades; AMOLED users rejoice! Shoutout to Asher, Joey and Alexander M. for the awesome work!

On the features front, the full change log is linked off below, but we’ll call out some of the big ticket items:

  • Wi-Fi Tethering – automatically turn off hotspot after X minutes of inactivity
  • Profiles – add notification light controls
  • Do Not Disturb/Priority Mode – add notification light controls
  • Privacy Guard/App data usage – Restrict apps to Wi-Fi or Cellular data only or block all internet access, per app
  • Bluetooth Devices battery support – For compatible devices, a new battery icon will appear in the status bar to show the paired devices’ battery level
  • Lockscreen Wallpaper picker makes its return
  • Lockscreen Weather and new Weather plug in support – see weather blog post
  • Lockscreen Blur support (on a per device basis) and the ability to disable the effect
  • Live Lockscreen support
  • New LiveDisplay hardware enhancements and API
  • Snap Camera (per device basis)
  • Gello Browser (per device basis)
  • Lots of translations – shout out to the CM translations team on CrowdIn
  • Cyanogen Apps support (see blog post, x86 is not supported yet)
  • Additional CM SDK APIs
  • Security fixes galore

Full change log:

Speaking of security, let’s touch on a few items. First, this release incoporates every Android security bulletin this year to-date, with a reported security patch level of August 5th, see and prior bulletins on what this entails.

Second, many users have likely read about the Quadrooter vulnerability coming out of DEF CON. Here, we have a bit of bad news. Of the four reported CVEs, we’ve been able to plug the ones that affected OSS code (ie the kernel), specifically CVE-2016-2059 and CVE-2016-5340. However, some of the reported vulnerabilities lie within OEM binary blobs, meaning we don’t have source access to resolve them.

So what does this mean? Unfortunately, for many devices we may never be able to completely resolve the outstanding issues, as OEMs are unlikely to release updated blobs across the generations of devices CM 13.0 supports, many of which were end of lifed on Lollipop or even earlier. We’d like to take this opportunity to remind you to be smart about where you source your applications, whether the Play Store, a FOSS equivelent or elsewhere on the internet – we’ve done our part to ensure the security of your device, but this and other parts are entirely up to you.

Builds will be rolling out as they complete from the build bots, with today’s roster below. As a reminder, you can flash this safely on top of the previous CM 13.0 ZNH0E releases without wiping. For further flashing instructions, see the wiki and the previous release post’s information.


  • acclaim
  • angler
  • bacon
  • bullhead
  • cancro
  • crackling
  • d800
  • d801
  • d802
  • d803
  • deb
  • falcon
  • flo
  • flounder
  • flounder_lte
  • hammerhead
  • himaul
  • himawl
  • huashan
  • i9300
  • jflteatt
  • jfltespr
  • jfltetmo
  • jfltevzw
  • jfltexx
  • kipper
  • klte
  • kltechn
  • kltechnduo
  • klteduos
  • kltedv
  • kltekdi
  • kltespr
  • klteusc
  • kltevzw
  • lt03lte
  • m8d
  • maguro
  • mako
  • manta
  • maserati
  • mt2
  • otus
  • peregrine
  • serrano3gxx
  • serranoltexx
  • shamu
  • sprout4
  • sprout8
  • spyder
  • targa
  • thea
  • titan
  • toro
  • toroplus
  • umts_spyder
  • xt897
  • Z00L
  • Z00T

Happy Flashing,
The CyanogenMod Team

  • Amirul Ariff

    cant wait for cm14. please updateee!

  • P_V24

    Dude, you don’t need to install supersu to root CM. You only enable developer options, and there is root option

  • P_V24

    Why to install superSU? Root is in developer options in Cyanogenmod

  • P_V24

    They started working on CM14 now, but I guess we’ll have to wait for stable CM14’s snapshots for another year

  • P_V24

    Better later and stable, than soon and buggy. You always have the Nightly option if you want new CM versions ASAP

  • P_V24

    Shame on you for shaming CyanogenMOD team :)

  • Raphael

    Sorry, I don’t think so. It’s not better later when it becomes outdated.

  • raihan rana

    Plizz update kernel 3.10.54 android 5.0.2 Lollipop based cn13 ROM pliz pliz . help me pliz help me

  • kupadupa

    What about LG G3 ? ;-;

  • strange76

    I’m on CyanogenMod 13 nightlie on my zuk z1 for two weeks.
    No problems encountered. Maybe, but confirm at GPS level with waze eg. a problem of which localization precision rule after a few kilometers (A-GPS ??)

    Cyanogenmod is very fast and stable as (nightlie of 09.01.2016). No Pb with QuadRoot and more…

    When will snaphot Version (znh5y)? as on many peripheral galaxy s3 (i9300) but not on zuk z1 (ham).

    Maybe a long time more validation.
    Keep up the great work :)

  • Cassy Bella

    Please do one for SM-J500H. Please. 😯

  • Hussain_Alsaadi

    Can you update cm13 for s3 neo
    Big thanks

  • Hussain_Alsaadi

    Can you upload CM13 for S3 neo please
    Big thanks

  • Mohammed Aziz

    CM 13 is a great build for S4 mini and i thank you guys to keep this phone in your sections to upgrade list!!! till now i didn’t face any bugs but lock screen with 3/4 notification card and swiping to unlock i sometime see some lags…moreover switching to apps also force closes in some cases!!! is that a memory issue or the graphics issue that the phone cant handle? CM 12.1 worked like butter…but app force closing and sudden hiccups are kinda annoying!!! Can i have a FIX for that? or should i wait for the next update? :)

  • MichaÅ‚ M

    Well, ok very nice. But…. about cm14 there is nothing but silence. CM14 branch for oneplus3 is available already. What are the plans?

  • Tom

    Sony wasn’t that community friendly. If you bought a carrier-branded device in North America, chances are the bootloader was locked with no official unlocking method available. I had to return an Xperia after a week because of this. If anyone’s wondering why I bought a carrier branded device, it’s because you often have no choice – even third party resellers in North America tend to be selling branded devices that were later unlocked with codes.

  • James

    My wifi is broken on Angler, too.

    I tried wiping cache and dalvik, but still no wifi.

    Any idea how to fix it?

  • Jonathan Barbosa

    I would really love seeing CM 13 for the Samsung Galaxy Grand Prime SM-G530T1. A lot of people would really appreciate that CM Team!!

  • Mrinmoy Roy

    I need the volte update for yu yuphoria 5010..bcoz it does not support the HD call.. But yuphoria 5010A supports that… So its really urgent for the volte update for yu yuphoria 5010 model..

  • Nabil Ihza Ambariyono

    Please made it for infinix zero 3 :(

  • RMH

    When will this be available for the Oppo?

  • Amirul Ariff

    can’t upload video in instagrams!! fix it!

  • Aswin Bahulayan

    Kindly build a cynagenmod 13 for c6802

  • Vikas

    yes the rom is already rooted

  • Vikas

    Flashed Snapshot on Mote E2 3G(Otus) with GApps nano. every thing works fine except the call blocking option. cannot block calls for unsaved contacts and cannot block from the recent calls tab.

  • Vikas

    go to fastboot and falsh your nandroid

  • Paras Jain

    The snapshot for lettuce is out but not available from ota . When will be ota update available?

  • Paras Jain

    Can I install gapps manually through play Store rather than flashing gapps

  • sechebis

    terbaik poit!