You don't really need it. You can toggle root on developer settings, and CM's built-in privacy guard will take care of root access requests
[ROM] [7.1.x] Unofficial CyanogenMod 14.1 Nightly Builds (Z00A/Z008)
- Thread starter jrior001
- Start date
- Status
You don't really need it. You can toggle root on developer settings, and CM's built-in privacy guard will take care of root access requests
@jrior001, you should say in the op to NOT DO A FACTORY RESET FROM THE DEVICE SETTINGS. ONLY USE TWRP TO FACTORY RESET, OR THE PHONE WILL BE STUCK IN RECOVERY.
if you are on mm blobs just flash the unofficial cm13 from theflamingskull.com
Thanks for the warning, one more of those details to fix when the ROM is at the polishing stage. Another thing I remember is Airplane mode not turning off the mobile radio, TWRP not supporting the new encryption scheme etc etc.
I can second this, the first tap on the button doesn't work as intented, it just vibrates. The second tap then works. After that the home button works flawless, but if you don't use it for a while (I think a couple of minutes), then you need the "double" tap again.
No, it stopped entirely but I figured out how to fix. It was a profile-related issue, my home profile disabled the lock screen and the buttons thought the phone was on the lock screen.
I just changed my profile from home to outside then back to home and it fixed it.
Is it normal to get this warning [edit: except the exact text is "has failed verification"] on every boot after the firmware upgrade? I haven't seen any mention of it thus far (though I might've missed it in the ~70 pages, my bad if I did).
It's entirely possible I derped when upgrading from the (non-MM) cm 13 builds. I followed the instructions in the post exactly as they were (connected phone, ran the firmware upgrade script, booted recovery, wiped everything and sideloaded cm14/gapps for a fresh start).
/data shouldn't influence device verification, unless there's something I missed?
edit: This is with the 2GB RAM Z00A variant.
This was also using the linux variants of the firmware upgrade stuff. I poked at the scripts some and they seem to be perfectly fine, but it's possible I derped or something derped and not everything that needed to be flashed got flashed.
It's entirely possible I derped when upgrading from the (non-MM) cm 13 builds. I followed the instructions in the post exactly as they were (connected phone, ran the firmware upgrade script, booted recovery, wiped everything and sideloaded cm14/gapps for a fresh start).
/data shouldn't influence device verification, unless there's something I missed?
edit: This is with the 2GB RAM Z00A variant.
This was also using the linux variants of the firmware upgrade stuff. I poked at the scripts some and they seem to be perfectly fine, but it's possible I derped or something derped and not everything that needed to be flashed got flashed.
Last edited:
But it is clear that you need to do factory reset in recovery/twrp. Why would you reset from device settings if the instruction clearly said that you need to reboot to recovery in order to do so?
It's actually been mentioned MANY times in this thread and others. It's normal.
Sent from my Zenfone 2 using Tapatalk
Ah, alright. I was skimming the thread before I got my coffee and it must have just not registered at all ¯\_(ツ)_/¯
thanks!
Currently on 16/11 build -
Screen recorder doesn't work - once the video is recorded, MXPlayer (or any video player) can't play the file. Happened with AZ screen recorder as well.
Screen recorder doesn't work - once the video is recorded, MXPlayer (or any video player) can't play the file. Happened with AZ screen recorder as well.
1. Bluetooth sharing makes phone to reboot.
2. Audio not playing in Music App but youtube working fine.
3. Permission changes after flashing new build and some apps FC after flash. Need to reinstall them.
2. Audio not playing in Music App but youtube working fine.
3. Permission changes after flashing new build and some apps FC after flash. Need to reinstall them.
This qsn has been answered numerous times on this thread just go back a page and you would find an answer for it
C
collm109
Guest
i accidentally did that, any fix?
---------- Post added at 05:41 PM ---------- Previous post was at 04:56 PM ----------
ok looks like only fix is to flash stock recovery try to boot then flash twrp again
What if you just do another factory reset while in recovery?
Sent from my Zenfone 2 using Tapatalk
I am facing wechat error, whenever i login to wechat's account, it crashes and never opens after that
And yes, i am not getting cm updates even if there is an update!!!
And yes, i am not getting cm updates even if there is an update!!!
Last edited:
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
156CyanogenMod is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:#include <std_disclaimer.h> /* * Your warranty is now void. * * We are 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 it! YOU are choosing to make these modifications, and if * you point the finger at us for messing up your device, we will laugh at you. * */
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 14.1 on your device, or coming from another ROM?
Unlock Bootloader!
Download the zip(s).
Install Appropriate FW base (STOCK MM 4.21.40.xx base is required) simple FW update package is available at my download link
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package. Open Gapps x86 7.1
Broken Features / Known Issues
- VIDEO ENCODER/DECODER ISSUES: This results in green lines on videos/pictures taken using the Intel HW encoder/decoder and other playback issues dependent on video formats. See the list below:
- Snapchat: thin greeen line tends to appear on recorded videos for snapchat
- Asus Pixelmaster Camera App: Super resolution mode does not work. Turning off "Optimizations" from settings clears up any green line issues.
- Some video formats do not play as expected
- FM Radio is unsupported.
- audio is a little weird in Real Racing 3.
- sim 2 cannot be disabled (this is true for all CM builds on non qualcomm hardware)
- Other than Fugu (Nexus Player TV box) there are no Vendor released M x86/x86_64 builds in existance. You may experience some issues with GAPPS and some known apps not loading or working correctly. Below is a list of KNOWN apps that do not currently run on CM13 based x86 Zenfone 2 builds :
Polaris Office, Chase Mobile, Showbox... - DRM content is currently broken
- Live Display (color calibration) not working yet
- Screen recording not working
- Chromecast screen mirroring not working, native casting works though.
- factory reset from setting menu has been reported to cause recovery boot loops.
- Battery life is horrible, numerous display wakelock issues
CM14 (not device specific issues)
No CMTE yet
Status bar icon changing broken
CM file manager has trouble accessing external sdcard
Battery profile is non functional/string errors
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
As the Zenfone2 has multiple models from multiple countries please include the following information in your report:
model #
CPU Speed / RAM Size
device state when errors occur (BT/wifi/nfc on ? On a call ? sitting idle on shelf ? )
method to reproduce if you've found something consistent
Download Links
CyanogenMod for Z00A/ ze551ml: ROM
CyanogenMod for Z008/ ze550ml: ROM
Recovery Links
Z00A
MM BL compatible TWRP: TWRP
Z008
MM BL compatible TWRP: TWRP
Google apps addon:
Recommend GAPPS for now as the updated x86 gapps.
Flashable Modem updates:
FOR INFO ON MM BOOTLOADER BASED BUILDS SEE THIS POST
XDA:DevDB Information
CyanogenMod 14.1 Nightly Bulids (Z00A/Z008), ROM for the Asus ZenFone 2
Contributors
jrior001, crpalmer, say99
Source Code: https://github.com/CyanogenMod/android_kernel_asus_moorefield
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 4.21.40.xxx stock base
Version Information
Status: Beta
Beta Release Date: 2016-11-09
Created 2016-11-09
Last Updated 2016-11-227266Reserved
Official CM-13.0 -> CM14.1 Upgrade Guide
As seen with my previous unofficial CM-13.0 builds based on the MM Stock roms, An upgrade to the MM Firmware and bootloader is required going forward.
This guide is here to assist.
1) Download ROM and 7.1 GAPPS
2) Download my Firmware Update package for Z00A or Z008 . FASTBOOT AND ADB ARE REQUIRED!
3) Follow the included instructions to update Firmware and flash the new compatible TWRP. If for some reason the new TWRP is not flashed automatically flash it manually via fastboot. "fastboot flash recovery recoverimagename.img
4) Reboot to recovery and flash CM 14 and Gapps, reboot and enjoy. Data Wipe on upgrade is not required
CM 14.1 from Stock MM
1) Unlock Bootloader
2) Flash compatible TWRP
3) Perform desired backups
4) From recovery, factory reset & install ROM & 7.1 GAPPS
5) Enjoy!
CM 14.1 from CM13 Mm based beta builds
1) Reboot to TWRP( should already have good version)
2) Flash CM14.1 and 7.1 GAPPS
3) Reboot and enjoy!!38I uploaded an Initial LineageOS build this morning, nothign exciting except a few weeks worth of bug fixes (most notably our live display feature seems to be workign again). The "Rebrand" is incomplete still so theres nothing exciting to see here.
I will create a new thread when the full rebranding is complete.36Brief development update.
I can confirm the Bluetooth/speakerphone issue with audio during screen off. Seems to only be an issue if there is a BT device connected.
I have the .184 Z00A update incorporated locally and will be testing that build today.
I have also found a kernel wake lock issue that is causing some less then ideal battery life. I haven't been able to track that down yet.
Also I want to thank the few folks here that have been coaching along the users struggling through the update process. I definitely don't have the time & patience to help everyone.
Sent from my ASUS_Z00A using Tapatalk - VIDEO ENCODER/DECODER ISSUES: This results in green lines on videos/pictures taken using the Intel HW encoder/decoder and other playback issues dependent on video formats. See the list below:
