Develop Bugs

[DEV][OTA] OmniROM Galaxy 551/Callisto Port [OmniARMv6]

OmniROM Galaxy 551/Callisto port [OmniARMv6]
Current port status: beta - may not be suitable for daily use. For experienced users only.
Latest Google Apps package: not yet available
Pre-requisites:
ClockworkMod or TWRP recovery
Initial install:
Download the latest build that supports OTA updates from: http://dl.androidarmv6.org/callisto
Reboot to recovery, wipe data and install the update package normally.
How to perform OTA (over the air) update:
Go to Settings -> About phone -> System updates. The latest diff between your current ROM and the latest build will be downloaded, which will be used to create a new update zip in the /sdcard/OpenDelta folder.
If you are using OmniARMv6 TWRP recovery, it can flash the new update automatically [not yet tested].
If you are using CWM recovery, you can flash the patched package (/sdcard/OpenDelta/omni-*.zip) manually.
Source:
Complete project: https://github.com/omniarmv6
Device (note: relies on shared device configuration): https://github.com/omniarmv6/android_device_samsung_callisto
Kernel: https://github.com/androidarmv6/android_kernel_samsung_msm

Reserved #1

Reserved #2

I have tested and found camera is not working , document (file manager) unable to open apk file and need some work on lock screen except that rom is smooth.
Thank for creating thread.

thanks

ROM is very smooth and fast. Works much faster than CM11.
Very thanks

@psyke83 omni rom will be used kernel 3.×.× as per source given above.

@psyke83 omni project has been abanded ? after bunch of ota failed ota disappeared from Jenkins. This rom is smooth and fast except few problems like camera,keyboard back light and lock screen resize.

Last builds (also for other devices) are dated June 15. And the last Android version was 4.4.3. Is it just a build process that got stuck, or is it more serious?

Links are down!
Hey man,
Thank you and others in armv6 team for their incredible work. You guys brought CM11 to a number of devices and that's a BIG DEAL.
Since our device is quite old now, I can see why the project died.
Now, the only thing we want is the links of the latest stable (RC) builds of the devices hosted somewhere. I can (at-least) host (CM11 and OMNI) stable builds of callisto in my GDrive.

Anyone knows what the license for ready-built ROMs is? That is, if the original source goes down, would anyone be allowed to upload a copy?
I'm not thinking about modified images yet - but it'd be easy to make people download something that isn't identical to the original thing, and the md5sum files have also gone - would archive.org be able to help? https://web.archive.org/web/*/http://download.androidarmv6.org/_builds/callisto/* seems to return something at least

Can Someone reupload this?

OnePlus One DroidKit | by iTechy OPEN SOURCE! | No longer being maintained

Droidkit OnePlus One Windows
Hey guys iTechy21 here and I am glad to announce I have a NEW project I'm working on to make an open source toolkit made from c# to allow easy development for other devices. This project will aim to support as many devices as possible with different toolkits for different devices therefore unifying the experience between them.
This will also be 100% open source when fully complete and is released under the GPLV3 licence (apart from the stuff I did not develop e.g. Custom Recoveries, root.zip, adb / fastboot and stock software all rights go to their respective owners).
Features
Support for any android version and Rom
Full Backup and Restore of apps + data (Nandroid is in the works...)
Unlock / Lock your bootloader (removed locking due to possible issues)
Flash a custom recovery (all supported including stock)
Shows attached device(s) in status bar
Advanced CMD mode for power users - type any ADB Command you want!(Will be reimplemented!)
Booting the device into and out of fastboot with a button click
Flash back to stock (Lollipop!) and keeps your bootloader unlocked
To come
Flash 100% stock DONE!
Save backups with custom names DONE!
Install APK's through ADB DONE!
Flash zip via recovery commands DONE!
Improve UI to make it look cleaner...
Backup the EFS Partition (will be coming Soon) DONE!
Log screen to help amateurs with adb learn (and also output errors to be more verbose) Abandoned due to too many issues
Ability to change colour theme from light to dark and the colours (coming Soon™)
Improve OTA system (continuous)
I am accepting requests if they are not too obscure to find out (even better if you find a way to do it as it cuts down on my research time which I don't have a lot of )
Legal
This is an unofficial toolkit made by an independent developer who has no association with oneplus apart from the fact that he owns a 64gb Sandstone black phone. I cannot be held responsible for anything that may happen to your phone! Even if it is just exploding, catching fire or just voiding the warranty.
Changelog
Material 0.0.1.5 ) - Major Milestone! - Untested Oxygen OS flashing. Do-so at your own risk! (Might not work not fully tested)
Improved theming
Updates to internal .dll's
Stability improvements
UI Tweaks
More verbosity via dialogue messages
System requirements​To run this needs an x86 or x64 based system (Not supported on Windows RT)
And version 4.5 of the .NET framework (which is installed upon install if missing (needs testing!) and requires Windows 7 or Higher (sorry XP users )
Downloads​No Download as no longer maintained and buggy​QR for nerds
[QRCODE]http://repo.itechy21.com/toolkit.html[/QRCODE]
Known issues​You tell me...
XDA:DevDB Information
DroidKit | OnePlus One Windows *STABLE*, Tool/Utility for the OnePlus One
Contributors
itechy, All the helpful folks over at Stack Overflow
Source Code: https://github.com/Droidkit/OnePlus-One/tree/master
Version Information
Status: No Longer Updated
Current Stable Version: V0.0.1.5
Stable Release Date: 2015-09-17
Created 2015-03-16
Last Updated 2015-12-06​

FAQ
Q: How do I do X?
A: You click the button corresponding to the action
Q: How do I flash to stock and then unlock the bootloader?
A:
You put your device into fastboot mode.
Once done select your device model (16Gb or 64Gb) and then click flash to stock.
The Bootloader should stay unlocked after the flashing process...
Q: What Roms do this ToolKit support?
A: Any android based ROM with the ADB Debugging interface!
Q: Help it's not working!
A: Try 3 things.
Re-installing the toolkit to re-install the drivers
Enable ADB in the developer settings (tap on build number (in about phone) x times until you get a toast notification)
Update the ToolKit

I found a Bug!
Great and thanks for finding one! I can now hopefully track it down and fix it if you provide the following:
The Computer's OS
What you were doing
How you can reproduce this
Your device
The code from the message that appeared
This will help me track down and hopefully fix the error. And once open sourced these can be reported via GitHub!
Please be aware that messages that just say "HELP" or "IT CRASHED" will be ignored as they don't help...

GOOD JOB .....Bro

kishorparmar said:
GOOD JOB .....Bro
Click to expand...
Click to collapse
Thanks
I hope it isn't too buggy and it works for you

Anyone already try this tool? I want download, but size so damn high

zipperX said:
Anyone already try this tool? I want download, but size so damn high
Click to expand...
Click to collapse
I knew that would be an issue. That's due to the fact it includes all the stock files for CM11S. However I will make it possible by downloading it within the app unzipping it and then flashing the device. But I'm fairly novice at c# and I don't have a lot of time to develop at this moment in time...

Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up

timmaaa said:
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Click to expand...
Click to collapse
Thank you I'll finally get noticed for something XD

... It works great but the size is a big deal.
Also, i suggest that ... you show what version of recovery you will flash - TWRP ( is generic and the filename does not gives you clue, the same for the others )
Also, for the Stock firmware ( wich version is it ?! )
SuperSU is not updated ... you could improve and use the last stable from chainfire
all the other things looks great so far.

itechy said:
Hey guys iTechy21 here and I am glad to announce I have a toolkit I have made. This is my first toolkit and is currently still being developed (adding / tweaking features) to allow you to easily do basic adb stuff and more advanced things are coming when I have time to develop this :silly:
This will also be 100% open source when fully complete but is released under the GPLV3 licence (apart from the stuff I did not develop e.g. Custom Recoveries, root.zip, adb / fastboot and stock software all rights go to their respective owners).
Click to expand...
Click to collapse
Can we have more mirrors (faster ones)? Like MEGA? Google Drive is kind of slow :cyclops: Great work!:good:

ygor.almeida said:
... It works great but the size is a big deal.
Also, i suggest that ... you show what version of recovery you will flash - TWRP ( is generic and the filename does not gives you clue, the same for the others )
Also, for the Stock firmware ( wich version is it ?! )
SuperSU is not updated ... you could improve and use the last stable from chainfire
all the other things looks great so far.
Click to expand...
Click to collapse
Thanks for the feedback. I may improve that make to another form with information on the specific versions (along with a built in download tool). Along with updating the SuperSU.zip
The first thing I'll do is work on that once all the basic features are there. But generally its the latest version of TWRP that is stable along with the other recoveries...
As for the stock I think the one I included was 44s but it may be 5Q (ew). Ill be implementing a downloader for the stock images to download whatever the latest version is from cyanogen...
sabrefresco said:
Can we have more mirrors (faster ones)? Like MEGA? Google Drive is kind of slow :cyclops: Great work!:good:
Click to expand...
Click to collapse
I'll see what I can do but the size will be reduced in the next update as it will remove the stock zip and replace it with a downloader which will download the stock images and then flash them reducing the size massively... (but I use Gdrive as its easy to find the download link unlike with Dev-host...)

I can´t flash twrp with this toolikt any one have a clue?

Do you have the adb drivers installed? Or is it throwing an error?

Updated to fix issues, add ota support, install APK's and improve performance
Sent from my A0001 using Tapatalk

Is "fully complete" v1.0.0? I'd love to stretch my C# muscles a bit.
EDIT: I can't read. Sorry.

dont worry about it
we always have moments... Its almost ready but I don't have a lot of time to develop so it may take me a while to get everything in there....
Just improving the ota updater now as its throwing exceptions...

Download link is not working. Please re-up. Thanks

godzulu said:
Download link is not working. Please re-up. Thanks
Click to expand...
Click to collapse
+1

If anyone has this file, send it to me and I can host it on one of the servers I rent. If we use a Dropbox link, it's going to get so much traffic that the persons account will get suspended.

[ROM] [4.4.4] [UNOFFICIAL] CyanogenMod 11 for Ascend Mate 7 (MT7-L09)

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4.4 (Kitkat), which is designed to increase performance and reliability over stock Android for your device.
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 it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Additonal source code for Ascend Mate 7: https://github.com/Demelza/android_device_huawei_mt7_l09
Additonal source code for Honor 6: https://github.com/honor6-dev
KNOWN ISSUES
- Bluetooth audio not properly working
WONTFIX
- Infrared
- FMRadio
- MHL
- DualSIM support
- EAP-SIM
- USSD-Code execution
- Fingerprint scanner
READ BEFORE FLASHING!
These builds are NOT official and will never be!
Do not submit bug on CyanogenMod issue tracker
HOW TO INSTALL CM?
Unlock your bootloader else flashing via fastboot will be impossible
Upgrade your phone to the latest available stock rom (to get latest bootloader and baseband firmware)
Download ClockworkMod Recovery for your specific variant
Download CyanogenMod for your specific variant
Download Google Apps
Copy CyanogenMod and Google Apps zips to your external sdcard
Flash ClockworkMod Recovery via fastboot. (fastboot flash recovery cwm-mate7_YYYYMMDD.img)
Reboot into ClockworkMod Recovery
Do a Data wipe / Factory reset (This is IMPORTANT!)
Flash CyanogenMod zip
Flash Google Apps zip
Goto "Mounts & Storage" and select "Format /data and /data/media" (This is also IMPORTANT!)
Reboot and Enjoy
If you're getting error messages while trying to flash the CyanogenMod zip, THEN FOLLOW THE ABOVE INSTRUCTIONS.
Especially the part where it says "Flash ClockworkMod Recovery".
The ClockworkMod Recovery you've got from somewhere else is FAULTY!!!
WHERE TO GET CM?
Unofficial builds:
MT7-L09: cm-11-20150410-UNOFFICIAL-mt7_l09.zip - 243 MB
Google Apps:
https://www.androidfilehost.com/?fid=95832962473395379
Old builds:
None yet
HOW TO GO BACK TO STOCK ROM?
Download B127 stock firmware - 1.26 GB (ONLY FOR L09 !!!)
Extract it
Copy the Update.app into DLOAD folder on your external sdcard (sdcard1/DLOAD/Update.app)
Power off phone
Hold all 3 Buttons till "Fastboot & Rescue Mode" appears. Flashing should start automatically.
HOW TO BUILD CM FROM SOURCES?
http://forum.xda-developers.com/showpost.php?p=60019676&postcount=2
DEAR KANGERS
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't meant Out-of-Respect!!!
Thanks to all contributors, especially codeworkx, without whom this project wouldn't even exist!!!
XDA:DevDB Information
CyanogenMod 11 for Ascend Mate 7 (MT7-L09), ROM for the Huawei Ascend Mate 7
Contributors
Demazda, codeworkx
Source Code: https://github.com/Demelza/android_device_huawei_mt7_l09
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2015-04-10
Created 2015-04-10
Last Updated 2015-04-10

Reserved
HOW TO BUILD?
1. Prepare your build environment and get the CM11 sources. Read the official CM wiki if you don't know how.
2. Add our local manifest
https://raw.githubusercontent.com/Demelza/manifests/cm-11.0/local_manifest.xml (goes to .repo/local_manifests/local_manifest.xml)
3. repo sync -j10
4. Run following commands to start building:
Code:
. build/envsetup.sh
lunch cm_h60_l01-eng
brunch cm_h60_l01-eng
Currenlty supported: cm_h60_l01-eng
Code:
Yes, h60-l01 is the identifier for Honor 6. The .zip will also be named "cm-11-YYYYMMDD-UNOFFICIAL-h60_l01.zip" if you build it yourself. But it'll flash and work on Mate 7 too.

Very nice, unfortunately it can no longer wake up after some time. Screen remains black.

Fooox1 said:
Very nice, unfortunately it can no longer wake up after some time. Screen remains black.
Click to expand...
Click to collapse
I've had this bug with my first build, but I uploaded another one a couple hours after, which does not have this bug. You can redownload and retry if you want.

Quick question: how is this ROM different from the other CM11 4.4.4 ROM that's available?

AhsanU said:
Quick question: how is this ROM different from the other CM11 4.4.4 ROM that's available?
Click to expand...
Click to collapse
It's more up-to-date and it's open-sourced. Other CM11 rom doesn't have source available.

Works great! Thank you for your efforts! =)

Whats wrong whith this rom ?!
before i have installed this rom i dont have problems with "cm-11-20150205-UNOFFICIAL-mate7" but with this -11-20150410-UNOFFICIAL-mt7_l09 i have errors Status 7 and when i del "getprop" from update-script i have status 4 .......
Who can help me ?! I have a Huawei Ascend MAte 7 TL10
EDIT://
only what i have do is i update CWM to 6.0.5.1

Hello everybody
I cannot install this ROM.
In recovery I get error status 7 (kinda "this ROM is for MT7-09, your device is H60" i don't remember exactly...). I tried to flash the CMW recovery provided by Demazda in the thread [RECOVERY][CWM] ClockworkMod Recovery 6.0.5.1 for Ascend Mate 7 (MT7-L09), but i get error message (target reported max download size of 471859200 bytes error: cannot load 'cwm_mate7_20150410.img': NO error).
The CMW recovery I'm running now is v.6.0.5.1: the one I flashed when I rooted and that I use for backups and to flash the ROM I'm using now MK44.4(CM11)(4.4.4).
Any suggestions?
Thanks...

leonardus_magnus said:
Hello everybody
I cannot install this ROM.
In recovery I get error status 7 (kinda "this ROM is for MT7-09, your device is H60" i don't remember exactly...). I tried to flash the CMW recovery provided by Demazda in the thread [RECOVERY][CWM] ClockworkMod Recovery 6.0.5.1 for Ascend Mate 7 (MT7-L09), but i get error message (target reported max download size of 471859200 bytes error: cannot load 'cwm_mate7_20150410.img': NO error).
The CMW recovery I'm running now is v.6.0.5.1: the one I flashed when I rooted and that I use for backups and to flash the ROM I'm using now MK44.4(CM11)(4.4.4).
Any suggestions?
Thanks...
Click to expand...
Click to collapse
Have you tried redownloading the CW image? Could be corrupt?
Thanks for getting this build going, Demazda. I was on the fence about flashing CM given the other CM build had Chinese bloatware in it, but now there's this clean version . I flashed it last night, and now there's no more lag when swapping apps or scrolling like stock has. It's almost like there's some decent NAND in there .
Why is the fingerprint scanner in the won't fix list? Is it because it's reliant on some proprietary blobs or ?
Also is there any reason I'm seeing a red outline around some apps that flashes for a quick second? I've noticed it a lot in Chrome, but it isn't just that. Just me?

NiceCarpet said:
Have you tried redownloading the CW image? Could be corrupt?
Click to expand...
Click to collapse
Thanks for your suggestion. I already solved. I flashed the stock recovery and than I flashed the CMW recovery provided by Demazda. THan I flashed without any issue this ROM...
I like it very much but I prefer the MK44.4... I miss PIE controls and I do no like PIE available with gravityBox. Thanks to Demazda for his work, anyway.

so i got my mate7 on monday and thanks to this thread i unlocked/rooted it today (thanks Demazda!!!). it took me awhile but i finally got CM11 installed and WOW!! i erased/reset my nexus 5 and gave it to my dad cause i now have the best phone ever! i hope to acquire some skills for android over the summer so that i could help out in developing for the mate7. hopefully PAC-ROM will be available some day. thanks for all the hard work to all that contribute to this great cause!

wifi....
Sometimes do not Wi-Fi....

0 WiFi issues here. Could you elaborate?

Really thanks demazda.
I install it yesterday and everything is working good (right now).
I just revert back the DPI to 480 because it's to small for my opinion and some app (launcher and others) don't display good with 320DPI.
Just a question, with this ROM as a base can we expect some port of other KK rom ? did you plan to update it ?

Really want to use this, since i love the material look you can give to it.
Unfortunately, i won't try to use this, since i really need the fingerprint scanner on the device.
Isn't there any way to fix it?

Djordie said:
Really want to use this, since i love the material look you can give to it.
Unfortunately, i won't try to use this, since i really need the fingerprint scanner on the device.
Isn't there any way to fix it?
Click to expand...
Click to collapse
Don't Expect any fingerprint for custom ROM, the sourcecode isn't available and huawei don't release any code (as i know) for that. only the kernel is available and i don't think the code for this is inside kernel.
After 2 days of use it's working good, BT audio don't work at all like demazda say in OP and i really need it so i cannot use as daily rom until someone fix it.
Wait for the futur

Demazda said:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4.4 (Kitkat), which is designed to increase performance and reliability over stock Android for your device.
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 it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Additonal source code for Ascend Mate 7: https://github.com/Demelza/android_device_huawei_mt7_l09
Additonal source code for Honor 6: https://github.com/honor6-dev
KNOWN ISSUES
- Bluetooth audio not properly working
WONTFIX
- Infrared
- FMRadio
- MHL
- DualSIM support
- EAP-SIM
- USSD-Code execution
- Fingerprint scanner
READ BEFORE FLASHING!
These builds are NOT official and will never be!
Do not submit bug on CyanogenMod issue tracker
HOW TO INSTALL CM?
Unlock your bootloader else flashing via fastboot will be impossible
Upgrade your phone to the latest available stock rom (to get latest bootloader and baseband firmware)
Download ClockworkMod Recovery for your specific variant
Download CyanogenMod for your specific variant
Download Google Apps
Copy CyanogenMod and Google Apps zips to your external sdcard
Flash ClockworkMod Recovery via fastboot. (fastboot flash recovery cwm-mate7_YYYYMMDD.img)
Reboot into ClockworkMod Recovery
Do a Data wipe / Factory reset (This is IMPORTANT!)
Flash CyanogenMod zip
Flash Google Apps zip
Goto "Mounts & Storage" and select "Format /data and /data/media" (This is also IMPORTANT!)
Reboot and Enjoy
If you're getting error messages while trying to flash the CyanogenMod zip, THEN FOLLOW THE ABOVE INSTRUCTIONS.
Especially the part where it says "Flash ClockworkMod Recovery".
The ClockworkMod Recovery you've got from somewhere else is FAULTY!!!
WHERE TO GET CM?
Unofficial builds:
MT7-L09: cm-11-20150410-UNOFFICIAL-mt7_l09.zip - 243 MB
Google Apps:
https://www.androidfilehost.com/?fid=95832962473395379
Old builds:
None yet
HOW TO GO BACK TO STOCK ROM?
Download B127 stock firmware - 1.26 GB (ONLY FOR L09 !!!)
Extract it
Copy the Update.app into DLOAD folder on your external sdcard (sdcard1/DLOAD/Update.app)
Power off phone
Hold all 3 Buttons till "Fastboot & Rescue Mode" appears. Flashing should start automatically.
HOW TO BUILD CM FROM SOURCES?
http://forum.xda-developers.com/showpost.php?p=60019676&postcount=2
DEAR KANGERS
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't meant Out-of-Respect!!!
Thanks to all contributors, especially codeworkx, without whom this project wouldn't even exist!!!
XDA:DevDB Information
CyanogenMod 11 for Ascend Mate 7 (MT7-L09), ROM for the Huawei Ascend Mate 7
Contributors
Demazda, codeworkx
Source Code: https://github.com/Demelza/android_device_huawei_mt7_l09
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2015-04-10
Created 2015-04-10
Last Updated 2015-04-10
Click to expand...
Click to collapse
Sorry, but anyway to fix USSD-Code execution? if not, is there any replacement?

Just wanted to pop in and say thanks Demazda, for this good clean CM11 for my device.
While I really like the look of the stock ROM and all it's extra benefits. Cyan/AOSP is just so reliable and I never used my fingerprint scanner anyway. Looking forward to see how battery life compares, anyone have any thoughts on how big of a difference it is to the stock ROM battery life?

I've been using MK44.4 and decided to try this. When I try to flash, the installation is aborted and it's telling me that my phone is something other than it actually is and refuses to install. WTF?

[ROM] [7.1.x] Unofficial CyanogenMod 14.1 Nightly Builds (Z00A/Z008)

CyanogenMod 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-22

Reserved
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!!

Yes!!!

yes u made it sir.. most awaited build of the year.. we really appreciate your time and efforts given to the project.. May God bless you.. behalf of all the zf2 a big thanks to @jrior001 and @say99
Sent from my ASUS_Z008 using XDA-Developers mobile app

just a question. Do i need to be on MM Bloobs or can I upgrade straight from LP bloobs? Also has the Brazilian sensors bug been fixed on CM14.1?

leoarten said:
just a question. Do i need to be on MM Bloobs or can I upgrade straight from LP bloobs? Also has the Brazilian sensors bug been fixed on CM14.1?
Click to expand...
Click to collapse
Has this been resolved in stock? I've heard mixed reports. I've included the updated sensor firmware from the .144 stock update so if it's in there we got it.
See post 2 as I update it, gonna try trying o cover all possible situations in guide there.
Sent from my ASUS_Z00A using Tapatalk

Awesome!
Downloading...

Downloading now.
Is the camera bug still present on N? Shouldn't the MM BLOBS fix that?
Thanks for your effort, @jrior001 !!!!

Thanks.. but just to clarify.. I need to update bootloader to MM Blobbs before I install CM14 right? or just flash new TWRP and flash rom as per usual (from LP Bloobs)? Im a bit confused.. Yes I saw theres a MM Bloobs session.. but couldnt find the answer to this.
Awesome work btw
jrior001 said:
Has this been resolved in stock? I've heard mixed reports. I've included the updated sensor firmware from the .144 stock update so if it's in there we got it.
See post 2 as I update it, gonna try trying o cover all possible situations in guide there.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse

leoarten said:
Thanks.. but just to clarify.. I need to update bootloader to MM Blobbs before I install CM14 right? or just flash new TWRP and flash rom as per usual (from LP Bloobs)? Im a bit confused.. Yes I saw theres a MM Bloobs session.. but couldnt find the answer to this.
Awesome work btw
Click to expand...
Click to collapse
Direct from post #2:
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
Sent from my ASUS_Z00A using Tapatalk

Thank you very much..
jrior001 said:
Direct from post #2:
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
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse

Thanks for your job, but no sensors found in brazilians devices...

ysllan said:
Thanks for your job, but no sensors found in brazilians devices...
Click to expand...
Click to collapse
Not that I can do anything about Asus's fail here but I'd like to see a logcat & dmesg captured from boot on this issue.
Sent from my ASUS_Z00A using Tapatalk

Is there Xposed for CM 14?

yumms said:
Is there Xposed for CM 14?
Click to expand...
Click to collapse
Nope right now. Just stay tuned for updates from rovo's thread.
Sent from my ASUS_Z00A using XDA Labs

jrior001 said:
Not that I can do anything about Asus's fail here but I'd like to see a logcat & dmesg captured from boot on this issue.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Did you use the 144 blobs? Asus solved problems with this version.
Enviado de meu ASUS_Z00A usando Tapatalk

I'm sorry to be a pain in the ars*. But you've mentioned you're basing on .144 stock update right? Having said that the link you posted with the zip to update bootloader Ive found files mentioning 4_21_40_134.bin (.134) wouldnt this be the reason sensors arent still working for brazilians devices? I had a look at Asus website and this is fix has been implemented on .144 update. So is this update on script and files updating bootloader or are they on the ROM itself..
Now I know the rules on XDA and I wouldnt dare to ask for ETA, however if this is the case, I would ask very politely if you could update the scripts files to .144 whenever's convenient for you and whenever you have time. That would be much appreciate. I will be coming back to this post and will be waiting anxiously for this.. Take you time and Thank you again.
jrior001 said:
Has this been resolved in stock? I've heard mixed reports. I've included the updated sensor firmware from the .144 stock update so if it's in there we got it.
See post 2 as I update it, gonna try trying o cover all possible situations in guide there.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse

jrior001, crpalmer, say99 are best!)) Makes backup and installed

see, told you guys that it will be soon please take use of logcat whenever you guys are reporting some issue, we won't be able to do anything without logcat if we can't produce it on our device. Enjoy people

jrior001 said:
CyanogenMod 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.
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 :
Ingress, Polaris Office, Chase Mobile, Showbox...
DRM content is currently broken
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-09
Click to expand...
Click to collapse
haha thx so much bt wechat isnt working too haha

[TWRP][OFFICIAL][3.2.2-0] TeamWin Recovery For Moto E4(woods)

TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.​
​
What's new in 3.2.2-0:
</> CHANGELOG : ? </>
Code:
Code:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
</> DOWNLOAD ? </>
https://twrp.me
​
$ TIP $
You can update it from previous TWRP recovery if you already have it installed, else install it as fresh by using adb or Official TWRP Installer app from google play store or similar
​
To flash with Fastboot/Adb:
Code:
Code:
make sure OEM-Unlocking is ON
$ adb reboot bootloader
$ fastboot flash recovery twrp-3.2.2-0-woods.img
To contribute:
TWRP Code Review
TeamWin
XDAevDB Information
Moto E4 ROMs, Kernels, Recoveries, & Other Development
Contributors
iykeDROID™ {dumbDevpr*}
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created: 2018-07-12
Last Updated: 2018-07-13

Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.

ka4o_pi4a said:
Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.
Click to expand...
Click to collapse
from the looks of things on my side, i don't think that will happen in anytime too soon.
let's just hope for a God sent dev to take over the Moto E4(woods) development .

if any bug with the TWRP, create/open an issue regarding such bug on GitHub :
https://github.com/omnirom/android_bootable_recovery
( make sure to see how other issues were created and follow such trend )
thanks

I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.

EstebanxZ said:
I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.
Click to expand...
Click to collapse
wait for next update or use this at your own risk
https://t.me/motoe4woods/12179

Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.

ka4o_pi4a said:
Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.
Click to expand...
Click to collapse
i used it to install Both XOSP & Gapps Pico today.

Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).

ka4o_pi4a said:
Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).
Click to expand...
Click to collapse
please your issues on that specific ROM's thread.
As far as i know, the TWRP recovery works fine even before the unofficial beta... woods has come to it's best so far.
thanks.

Already do that. Also try with two or three different ROMs and get the same error. Doesn't matter, I'LL wait for some more stable version of twrp and some ROM.

Tks
Thanks man!

Laruzzo said:
Hi, this TWRP version to Moto E4 woods is not good.
It does not install GAPPS, and do not install SUPER SU.
With GAPPS the error is about 64 bits version. And with supersu it says that "Bad recovery no Unzip."
I tried with a unnoficial version and worked everything.
Please update in TWRP site to a new version with bug fix.
Look a this thread with the version that worked with Moto E4 woods.
https://forum.xda-developers.com/mo...rp-3-1-1-r1-port-xt1760-t3772249/post76177524
Click to expand...
Click to collapse
Dude,
learn how to read a full post with instructions & proper way of reporting an issue anywhere you find yourself.
Know you device SoC, Architecture, etc ... don't just talk any how.
also, commits has not been merged
see on gerrit.twrp.me :=> https://gerrit.twrp.me/#/c/android_device_motorola_woods/+/63/
Finally, always check to see if no one has report similar issue and been solved before you start writing sh*t into the air
https://postimages.org/
https://forum.xda-developers.com/showpost.php?p=77250466&postcount=6
NOTE : MOTO E4 SERIES IS ARM(32bit) Architecture Device, stop trying to flash/install ARM64 Gapps as you stop being dumb.

OK
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.

Laruzzo said:
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.
Click to expand...
Click to collapse
Download ⍖ ?
TWRP-323.0-Unofficial-woods.img

iykeDROID™ said:
TWRP is an open source, community project.
..
..iykeDROID™[/URL] {dumbDevpr*}
Source Code: https://github.com/TeamWin
[/SIZE][...his other way cause I doubt about official ¿‽​
Click to expand...
Click to collapse

Abish4 said:
Format Data Partition with F2FS format is not available which is usually available with every Moto Device Kernel
Click to expand...
Click to collapse
please deal with the kernel source here : https://github.com/MotorolaMobilityLLC/kernel-mtk/tree/nougat-7.1.1-release-woods
Abish4 said:
Can you help with this other way cause I doubt about official ¿‽
Click to expand...
Click to collapse
due to negligence, you couldn't check the source code here : https://github.com/TeamWin/android_device_motorola_woods
also check the twrp site : https://twrp.me/motorola/motorolamotoe4.html

I cannot flash gapps arm 7.1.x

Hi. I have one MotoE4 XT1763 Mediatek MT6735 with unlocked bootload.
would you recommend flashing the
twrp-3.2.3-0-woods.img 15.1M
Or the
TWRP-323.0-Unofficial-woods.img 15.5M
for the Lenovo Moto E4(XT1762)
?
Thank you peoples. TWRP unofficial working fine

Hey peoples. Accidentally i wiped my system. I have a backup in pc. I dont have sd card right now. How can i put the backup wich is in pc back to TWRP backup folder in order to restore ?