[ROM][7.1][CM14.1][UNOFFICIAL] CyanogenMod 14.1 [Angler][11.10.2016 FINAL BUILD]

Status
Not open for further replies.
Search This thread

kronflux

Senior Member
Jun 6, 2012
524
530
35
Edmonton
Samsung Galaxy S7
Google Pixel 2
cyanogenmod-10-banner-600.jpg


Code:
#include 
/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because
 * the alarm app failed. Please do some research if you have any concerns about features included in this ROM
 * before flashing! YOU are choosing to make these modifications, and if you point the finger at me for messing
 * up your device or causing issues, I will laugh at you.
 *
 */
This rom is NOT an official build. Official Nightlies can be found > HERE <
Big shoutout to sam3000, as his updated sources made this build possible!​

NOTE
  • Now that official CyanogenMod Nightlies have started, this thread is redundant and builds will no longer be released.
    Please see > HERE < for Official Nightlies.


NOT WORKING/BROKEN/ISSUES
  • Forced encryption previously caused issues, disabled this for all future builds
  • Battery Icon Customization, Landscape and Circle) - Percentage next to and inside icon now working
  • Most GApps packages currently have an issue on first boot during the setup wizard, where you cannot get past the "Copy from another phone" stage.
    There is no reliable 1-stop fix for this as of right now, however the most common workarounds are as follows:
    -Omit GApps from first boot(do not flash it), get through the setup, then reboot and flash GApps.
    -Cause the setup wizard to crash(I usually just click the next/skip buttons as fast as possible for several seconds), most of the time it will continue the setup

FREQUENTLY ASKED QUESTIONS
  • Is this stable/daily driver ready? - Currently it is fairly stable, however please note the current issues, particularly with GApps.
  • Do I have to update TWRP to 3.0.2-2 or later? - Only if you're upgrading with an encrypted storage and wish to retain that encryption/data. It is, however, recommended regardless.
  • Do I have to update my Vendor image? - Yes, although untested, this ROM theoretically will not boot without the latest Vendor image. I also recommend the latest -STABLE- Bootloader and Radio images for best results. This does not include Developer Preview images.
  • Why are my app permission dialogs enlarged/unclickable OR Why do apps require me to manually set their permissions? - You need to exclude Google's Package Installer when flashing GApps
  • Is <GoogleAppNameHere> working? - Probably. But maybe not. This thread, however, is intended for CyanogenMod testing, NOT Gapps testing
  • SIM card not detected/com.android.phone crashing - This is a database issue when upgrading from a previous CM14.1 to a newer CM14.1 build. Delete the following: /data/user_de/0/com.android.providers.telephony/databases and /data/com.android.dialer/databases then reboot.
  • What's changed in the latest build? - Any specific changes will be listed in the below changelog, however for routine/regular builds no changes will be listed. Check CMXLog for general CM changes

CHANGELOG
  • 11-10-2016: November security update to system image
  • 11-07-2016: November security update to Angler Blobs(NOT Android Patch Level) (Make sure to update bootloader, radio and vendor images)
  • 10-28-2016: Rebased on CM14.1, included Google Chrome WebView signatures
  • 10-13-2016: Sources merged into main branch, rebased on CyanogenMod branches
  • 10-05-2016: Disabled DEXPREOPT (This will increase first boot time)
  • 10-03-2016: staging/cm14.0 branch deprecated, rebased on cm-14.0
  • 09-28-2016_2: Disabled forced encryption
  • 09-28-2016: Initial release

CREDITS

DOWNLOAD
  • THIS ROM CURRENTLY HAS MANY CM FEATURES MISSING OR BROKEN.
    MAKE SURE TO READ THE ISSUES SECTION ABOUT GAPPS BEFORE PROCEEDING OR POSTING ABOUT IT.

    IF YOU'RE LOOKING FOR OFFICIAL CM14.1 NIGHTLY BUILDS, > GO HERE <

  • 11-10-2016: ROM | Mirror
    SHA1: 71FCA1F7DF679EAF5440B8ED86A8A4C7535CDF1D
    MD5: EB16610F4A708B61CC49136BCBE007E8
  • 11-08-2016: Previous Build | Mirror
    SHA1: 5C6606851ED2CCEF1992903918898A0963CC2168
    MD5: 557FBA44D220CD7F7840568749231288


GAPPS
  • OpenGApps (Make sure you select ARM64 and Android 7.1 for this ROM)

SOURCES
 
Last edited:

kronflux

Senior Member
Jun 6, 2012
524
530
35
Edmonton
Samsung Galaxy S7
Google Pixel 2
Anyone managed to boot it all up?
I've had it boot several times, although it seems after I flash GApps, it decides to no longer boot

hows battery life and stability? good for daily driving?
Please read the opening thread post before posting questions. It clearly says in red text, NOT stable, NOT good for daily driver.
As for battery life, no idea as of yet.

mine stuck on google logo :/
This seems to be related to the forced encryption, and only happens for me after I flash GApps, if I only flash CM, it works fine.

I'll have to look into disabling forced encryption, and see if that helps at all for the issues we're having so far.
 

rachnov55

Senior Member
Aug 18, 2008
98
30
ok I need some help here...

i used fastboot to wipe userdata and now i can't get back into twrp :S

how do i go about reflashing twrp and get recovery to boot back up? it's just stuck at the opening Team Win screen of twrp

---------- Post added at 09:59 PM ---------- Previous post was at 09:57 PM ----------

nevermind i got it to work :D
 

kronflux

Senior Member
Jun 6, 2012
524
530
35
Edmonton
Samsung Galaxy S7
Google Pixel 2
ok I need some help here...

i used fastboot to wipe userdata and now i can't get back into twrp :S

how do i go about reflashing twrp and get recovery to boot back up? it's just stuck at the opening Team Win screen of twrp

---------- Post added at 09:59 PM ---------- Previous post was at 09:57 PM ----------

nevermind i got it to work :D

Future notice, just reflash TWRP if you ever end up in a situation where you can't boot into it. Get to the bootloader, and "fastboot flash recovery twrp-whatever.img"
Also would recommend not using experimental/unstable roms if you're not all that experienced. You can end up doing damage to your device. Just a warning, obviously your own choice :p
 

Zavon

Senior Member
Aug 8, 2012
72
59
Able to boot fine and keep Gapps after flashing ElementalX kernel. However, play services does not work and force closes. (OpenGapps)

And Gello force closes
 
Last edited:
  • Like
Reactions: D@rekills4
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 32
    cyanogenmod-10-banner-600.jpg


    Code:
    #include 
    /*
     * Your warranty is now void.
     *
     * I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because
     * the alarm app failed. Please do some research if you have any concerns about features included in this ROM
     * before flashing! YOU are choosing to make these modifications, and if you point the finger at me for messing
     * up your device or causing issues, I will laugh at you.
     *
     */
    This rom is NOT an official build. Official Nightlies can be found > HERE <
    Big shoutout to sam3000, as his updated sources made this build possible!​

    NOTE
    • Now that official CyanogenMod Nightlies have started, this thread is redundant and builds will no longer be released.
      Please see > HERE < for Official Nightlies.


    NOT WORKING/BROKEN/ISSUES
    • Forced encryption previously caused issues, disabled this for all future builds
    • Battery Icon Customization, Landscape and Circle) - Percentage next to and inside icon now working
    • Most GApps packages currently have an issue on first boot during the setup wizard, where you cannot get past the "Copy from another phone" stage.
      There is no reliable 1-stop fix for this as of right now, however the most common workarounds are as follows:
      -Omit GApps from first boot(do not flash it), get through the setup, then reboot and flash GApps.
      -Cause the setup wizard to crash(I usually just click the next/skip buttons as fast as possible for several seconds), most of the time it will continue the setup

    FREQUENTLY ASKED QUESTIONS
    • Is this stable/daily driver ready? - Currently it is fairly stable, however please note the current issues, particularly with GApps.
    • Do I have to update TWRP to 3.0.2-2 or later? - Only if you're upgrading with an encrypted storage and wish to retain that encryption/data. It is, however, recommended regardless.
    • Do I have to update my Vendor image? - Yes, although untested, this ROM theoretically will not boot without the latest Vendor image. I also recommend the latest -STABLE- Bootloader and Radio images for best results. This does not include Developer Preview images.
    • Why are my app permission dialogs enlarged/unclickable OR Why do apps require me to manually set their permissions? - You need to exclude Google's Package Installer when flashing GApps
    • Is <GoogleAppNameHere> working? - Probably. But maybe not. This thread, however, is intended for CyanogenMod testing, NOT Gapps testing
    • SIM card not detected/com.android.phone crashing - This is a database issue when upgrading from a previous CM14.1 to a newer CM14.1 build. Delete the following: /data/user_de/0/com.android.providers.telephony/databases and /data/com.android.dialer/databases then reboot.
    • What's changed in the latest build? - Any specific changes will be listed in the below changelog, however for routine/regular builds no changes will be listed. Check CMXLog for general CM changes

    CHANGELOG
    • 11-10-2016: November security update to system image
    • 11-07-2016: November security update to Angler Blobs(NOT Android Patch Level) (Make sure to update bootloader, radio and vendor images)
    • 10-28-2016: Rebased on CM14.1, included Google Chrome WebView signatures
    • 10-13-2016: Sources merged into main branch, rebased on CyanogenMod branches
    • 10-05-2016: Disabled DEXPREOPT (This will increase first boot time)
    • 10-03-2016: staging/cm14.0 branch deprecated, rebased on cm-14.0
    • 09-28-2016_2: Disabled forced encryption
    • 09-28-2016: Initial release

    CREDITS

    DOWNLOAD
    • THIS ROM CURRENTLY HAS MANY CM FEATURES MISSING OR BROKEN.
      MAKE SURE TO READ THE ISSUES SECTION ABOUT GAPPS BEFORE PROCEEDING OR POSTING ABOUT IT.

      IF YOU'RE LOOKING FOR OFFICIAL CM14.1 NIGHTLY BUILDS, > GO HERE <

    • 11-10-2016: ROM | Mirror
      SHA1: 71FCA1F7DF679EAF5440B8ED86A8A4C7535CDF1D
      MD5: EB16610F4A708B61CC49136BCBE007E8
    • 11-08-2016: Previous Build | Mirror
      SHA1: 5C6606851ED2CCEF1992903918898A0963CC2168
      MD5: 557FBA44D220CD7F7840568749231288


    GAPPS
    • OpenGApps (Make sure you select ARM64 and Android 7.1 for this ROM)

    SOURCES
    20
    Not to be rude but don't you think its a little... Early to do that? The ROM dosent even boot properly with gapps and its not intended for average users... AFAIK mainly new users use the index.... Sorry I'd that came off as rude just was wondering if I was the only one who thought adding it to the index was a bit early...
    This is a development site, not just a ROM shop as many people incorrectly think, so not everything found on XDA is finished or stable. The fact that a ROM isn't fully finished should never exclude it from an index. An index should include everything, regardless of its current state of development. Plus, as has already been pointed out there are plenty of warnings, users flash anything at their own risk on XDA.
    13
    FYI - security updates to angler cm-14.1 from google build NBD91K were pushed to cm repos earlier today.

    When installing the next build of cm-14.1, you should update your bootloader/modem/vendor from https://dl.google.com/dl/android/aosp/angler-nbd91k-factory-6f206c95.zip to match.

    Nightlies are currently due to start tomorrow according to Steve Kondik comment here: http://review.cyanogenmod.org/#/c/169116/

    Noticed the security updates, currently already building.
    If official nightlies start tomorrow as expected, this may be my last build for this thread. We'll have to see how things go.
    Build should be up later this evening. New (and possibly final?) Build is up!
    10
    New build is up
    8
    I installed this ROM and I couldn't get past setup wizard, because it was forcing me to restore from another device. No other option... Did I do anything wrong?

    Yes! Yes you did!
    You have to set your oven to 450, and preheat it for 15 minutes!

    Read opening posts before you flash random roms!

    Giant block of red text. Read it.