Related
This is an unofficial build of Omni Rom based on KitKit 4.4.2. There is no official support for the d2 variants. Props to androidsftw for picking apart what was needed for our d2s.
I am not the dev of this rom, all I did was add in necessary device/vendor/d2 files for d2. This is not a port, everything has been built from source.
As with all things root, I am not responsible for anything that happens while flashing this rom. You take responsibility for your actions. Nandroid is your friend.
----------------------------------
Downloads:
Omni Rom for the D2LTE - Droidhype Roms
GAPPS 4.4.2 - PA 0-Day
SuperSU - Chainfire
Kernel (optional) - BMS
----------------------------------
Installing for the first time? Grab the newest full zip from the D2LTE directory. For future updates, just go to Settings -> System Updates and let the magic happen.
HOW TO INSTALL
1. Factory Data reset
2. Wipe System/Data/Dalvik/Cache
3. Install ROM zip from Sdcard
4. Install GAPPS zip from Sdcard
5. Install SuperSU from Sdcard
6. Reboot to home screen to confirm good flash
7. (Optional) Reboot to recovery and flash kernel
TO USE DELTAS, YOU HAVE TO USE TWRP OR PHILZ RECOVERY. CWM WILL NOT WORK BECAUSE IT DISABLES SCRIPTING CAPABILITIES BY DEFAULT. If there's anything that you want the updater to flash automatically after it flashes your update, put the file(s) in the FlashAfterUpdate directory inside your Opendelta folder in your internal storage.
Join the BMS G+ community which will have quicker release info in the future for all things BMS and roms.
Enjoy!
Cherry-picks:
- Multi-window
This build is unofficial, so I don't exactly carry around a changelog. However, you can always check cmxlog for omni and see what's been changed with each version of one of their nightlies. It won't be exact as some have specific device merges, but it will give you a good idea. The dates on my builds will correspond with the officials listed on cmxlog.
You can also check their gerrit or git to see what's been merged.
This question gets posted pretty frequently so if some users could please bookmark this post, we can just repost it when needed. Here are all the links you can peruse for your changelog/update enjoyment.
cmxlog - http://omni.cmxlog.com/4.4/
gerrit - https://gerrit.omnirom.org/#/q/status:merged,n,z
github - https://github.com/omnirom/
G+ - https://plus.google.com/u/0/communities/102450203113748251717
XDA - http://forum.xda-developers.com/omni
XDA:DevDB Information
Omni Rom for the d2tmo, a ROM for the T-Mobile Samsung Galaxy S III
Contributors
GideonX
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: Omni
Version Information
Status: Beta
Created 2014-02-18
Last Updated 2014-02-18
Reserved
FIRST!
Thanks, Will try!
2nd haha anyways will give this a try when i get home c:
Sent from my SGH-T999 using xda app-developers app
Hell yes finally, thanks for this for sure
Sent from my SGH-T999 using Tapatalk
So what I'm getting is that a d2lte build will work on all d2 variants, no updater-script editing required?
Screenies??
As GideonX has said, these builds support all the d2 variants. Everything is automatically done during flashing. You don't need to do anything but flash like normal
downloaded and working
Except for su recconising apps. have tried manual install also just can't seem to make it work. appreciate this rom otherwise. will keep trying. thanks:good:
Is anyone having problems with swipe typing?
trofmoc said:
Except for su recconising apps. have tried manual install also just can't seem to make it work. appreciate this rom otherwise. will keep trying. thanks:good:
Click to expand...
Click to collapse
4.4 needs special twrp jyst in case you restored back on to tw or never updated.
Anyways seems like the rom had little to offer in my personal opinion. I decided to just go an restore previous rom instead
Sent from my SGH-T999 using xda app-developers app
I just installed the Rom! Working great! Thank you.
Wp4Wp4:good:
twrex82 said:
Is anyone having problems with swipe typing?
Click to expand...
Click to collapse
Try PA's gapps. If you're talking about how no letters actually get inputted on the screen even though it is showing the swipe, then that's what you need.
http://forum.xda-developers.com/showthread.php?t=2397942
New D2LTE 2014-02-21 Build - http://goo.gl/zJwFzA
- Had some opendelta issues. Please flash this entire zip this time around, thanks.
- Screen rotation is in settings now.
where are the screen shots for this rom?
Thank you for this rom and one quick question, can't Sync facebook contacts info anymore on the last build?
"Envoyé depuis mon SGH-T999 avec Tapatalk"
Can someone on tmobile verify uploading pictures and video works with this rom in instagram? it may be a kitkat issue with instagram but previously I have gotten a lot of freezes, FC, and reboots while trying to upload video. anybody willing to test this on the latest release?
Dude sorry but are u spamming the threads with the same question?
Sent from my SGH-T999 using xda app-developers app
Anyone have OpenDelta mess up their phone? Every time I booted into recovery it would install the update. Then lost root and my gapps. It was hell trying to get it all back.
Purplezigar said:
Anyone have OpenDelta mess up their phone? Every time I booted into recovery it would install the update. Then lost root and my gapps. It was hell trying to get it all back.
Click to expand...
Click to collapse
I'm using Philz recovery, opendelta updates work as expected. What's your setup?
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?
[Q&A] CM13/Android Marshmallow Test Builds (Feedback, Troubleshoot & Discussion)
CM 13 / Android Marshmallow Test Builds for Xperia Play
Please Post all your Feedback, Fixes or Discovery of new Bugs and Discussion about Mike's CM13 here.
Its compiled by me and released here for some public testing. It was and is Mike's CM !! its his Hardwork !
I have been trying to build some test builds for Xperia Play.. builds have been successful but iv not been able to boot the ROM. if anyone else can do it.. and let us know how to as well.. its only a matter of time when MIKE is able to debug all of this.. but playing with Test Builds and bricking our devices is the Romance of Xda Community.. haha
Warning
Im not responsible if u Brick ur device/sd card. Everything at your own Risk buddies.
Backup Everything. Your ROM specially Your SD Card as this may brick your sd Card. and you would have to FORMAT it again totally.
About Recovery - Move about with Volume Keys. To select something, its the Power Button.
Builds Included in my Download folder. Separate Images of Kernel that I built also included. Boot.img present inside the Zip files don't boot. you can play and try as much as you want though.
1. Test Build 1 (9 Nov 2015)
Kernel from Zip file only keeps vibrating and didn't boot to recovery. Built a separate image of a kernel and that booted. but Doesn't load SD Card. for sure ROM needs to be booted from ADB Sideload but I don't know how.
2. Test Build 2 (23 Nov 2015)
Kernel from Zip file again keeps vibrating like hell and didn't boot to recovery. Built a separate image of Kernel only after ROM was built, Kernel boots to recovery but gives error.
Tried old build Kernel with New ROM. Still SD Card Error.
For neo l?
Please remove the download links. The source is highly unstable at the moment.
I haven't released any builds yet for a reason, you shouldn't distribute broken builds.
mikeioannina said:
Please remove the download links. The source is highly unstable at the moment.
I haven't released any builds yet for a reason, you shouldn't distribute broken builds.
Click to expand...
Click to collapse
Done.. I thought by posting them someone besides you also could help towards them :/ or help boot them. Il keep posting build feedbacks though.
Thread closed.
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
The Unlegacy Android Project
TF201 | TF300T/TG/TL | TF700T
Introduction
Unlegacy Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.
On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for the Asus Transformer Series include:
- Linux kernel 3.4.y (currently 3.4.113)
- BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
- F2FS support from kernel 4.9 (for /data and /cache)
Installation
You must have NvFlash backup. It is MANDATORY!
You need to use modified TWRP recovery that works with updated F2FS. If you're planning to install GApps, be sure to read the second post!
Problems
Non working/Known bugs:
- GPS; - need a device owner to configure!
- Camera (both);
- Dock special keys (top row);
- Modem on TG and TL;
- GUI crashes; - occure less often
Currently, no one from Unlegacy Team, has TF300T/TG/TL device. Help in developing or device donation would be highly appreciated.
Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds Else is enclosed in downloads.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see the second post). The aim of this project is to create a fast and stable ROM - although, one could use Xposed (or similar) to add extra features.
As usual, feedback is appreciated
Contacts
You may join Telegram development group, where all fresh staff is published and tests are made.
XDA:DevDB Information
Unlegacy Android Project, ROM for the Asus Transformer TF300T
Contributors
Clamor, Ziyan
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Bootloader 4.2 JB
Based On: AOSP
Version Information
Status: Beta
Created 2018-02-18
Last Updated 2018-10-17
Installation gide (for those who uses F2FS)
Before installing ROM you need to update your current recovery with this TWRP, else you will get a bootloop with next format from fastboot. Install zip from your current recovery and reboot into your current system. Than boot into new recovery and install ROM (with factory reset).
Currently 3.4 kernel isn't stable enough for daily use. You may use updated 3.1 _that16 kernel, it works fine with this ROM. To make wifi work with _that16 kernel just move nvram_nh615.txt from system/etc to data/misc/wifi and rename to nvram.txt
You may use KatKiss 7.1 if you want, but you must flash a _that16 kernel every time after flashing KatKiss ROM. Else you will get a bootloop with next format from fastboot.
If you want to go back to ordinary TWRP, you need to make a format from fastboot, flash TWRP and make formats from there as well.
REPARTITION and TREBLE
I worked on this for few last weeks to make it stable and simple enough to any user to install this update. As usual NvFlash is MANDATORY! TF300TG/TL users shouldn't use this as it can harm your tablet.
So, UA_Bootloader.zip includes latest JB4.2 10.6.1.27.5 bootloader, modified TWRP [email protected] from Downloads section and my new partition table. It's main benefits are /system partition increased to 1GB and /vendor partition. This means that we may install bigger gapps packages and support of TF's may be extended plus having /vendor partition gives us at least hardware support for Project Treble, even if there is no 8.1 builds currently.
Before installation copy everything from tablet on PC, else all you data will be lost! To install this update just install it via TWPR and when flashing is finished press reboot into system. Than wait till blue line gets to the end and tablet reboots. Tablet will than stuck into ASUS screen with Device is Unlocked sign in top left corner. Than reboot manually into recovery and format /system to ext4; /cache to ext4 or f2fs; /data to ext4 or f2fs and you are good to go.
New partition table is compatible with all existing ROMs for TF's. If you flash ROM with system in .img file you need after flash into recovery do Wipe -> System -> Advanced Wipe -> Change or resize partition -> Resize filesystem. If you want to restore 4.2 state you can flash Stock or Bootloader 4.2 attached in Downloads section.
How is this project going? and why you choose android 7.1? instead of the new android 8.0? because i would definitely want to help with a android 8.0/8.1 rom
androidjel said:
How is this project going? and why you choose android 7.1? instead of the new android 8.0? because i would definitely want to help with a android 8.0/8.1 rom
Click to expand...
Click to collapse
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.
Clamor said:
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.
Click to expand...
Click to collapse
Ah okay thats clear, a other question i want to try this rom but there are no downloads.
I want to test for you if you want? :good:
androidjel said:
Ah okay thats clear, a other question i want to try this rom but there are no downloads.
I want to test for you if you want? :good:
Click to expand...
Click to collapse
All needed files you can find in Downloads tab on top of this thread
Clamor said:
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.
Click to expand...
Click to collapse
Clamor said:
All needed files you can find in Downloads tab on top of this thread
Click to expand...
Click to collapse
I see tnx, what do you want to know or what do you want to have tested to help you?
and Btw which TWRP is that? i have the last one already installed.
androidjel said:
I see tnx, what do you want to know or what do you want to have tested to help you?
and Btw which TWRP is that? i have the last one already installed.
Click to expand...
Click to collapse
Nothing, you may install Rom to see current project progress (If you have TF300T there will be no sound). For further developement test device is needed, or a developer with TF300T(better solution). Mostly all major functions are fixed, see buglist, and 3.4 works on all transformers on Tegra 3.
That is KANG TWRP with support of updated F2FS
TF300T users, if you are interested in further developement, please help me with debuging sound driver. I need a tester, with TF300T and some free time.
Clamor said:
TF300T users, if you are interested in further developement, please help me with debuging sound driver. I need a tester, with TF300T and some free time.
Click to expand...
Click to collapse
I am more than willing to be a tester if you want. Heck, I will even find a cheap TF300T to load only this on. My mornings are relatively free as my business doesn't pick up till noon or so. Just PM me specifics of what you need. Any more development for our tablets is a blessing as far as I am concerned
I would love to help debugging, testing and developing. I'm currently in possession of a tf300t with dock and an me301t. Do you think it will be possible to port this to the ME301t?
@gs-crash-24-7 please write me in PM. Actually ME301t was supported at early stages of 3.4 bringup. I fully excluded it from board since I couldn't test it and Memopad parts made transformers board really messy. I had enough problems with TF stuff at that moment.
3.4 kernel porting and repartitioning before were just a dream, but now they are real. Memopad bringup depends only on your interest in it.
Oreo 8.1
Yesterday I have quickly build 8.1 ROM for transformers. There doesn't work almost anything and I won't have excess to my TF201 for a while to fix stuff Rom can be booted with same requirements as N roms. Here is first build. Please don't post any issues/logs here from O for now. I know already about all major issues.
I have some good news. Here is mostly working Oreo build with issues from N + non working bt. I'm still working on fixing staff so this isn't last build.
P.S. Remove system/lib/hw/bluetooth.default.so to avoid constant bt crash
Any possibility of sharing the 3.4 kernel supporting the ME301t...I have that little bugger and the latest software updates from my TV provider and Netflis like programs are all KK dead for the most part. Having unlegacy on the Me301t would be a dream come true and would avoid trashing this one and getting a new one just because I want to see some shows or TV. Thank you for your work. I will assist to the best of my knowledge.
@AlphaDivxMovies nothing impossible, but first of all, I have no MemoPad and it's hardware isn't that close as my Prime is with TF300T. Second is that I put huge amount of my time and afforts in porting transformer board so I have no desire at all to do this once more time, I can help with suggestions but actual development will lie on your shoulders.
P.S. To just boot rom atm you would need only a kernel port, ROM is mostly compatible. Almost all drivers memopad uses are already included. You may contact @gs-crash-24-7 as well, he has memopad and if he agrees, than work in pair is much more simple.
@Clamor , Where is the oreo version? https://builds.unlegacy-android.org/ here i could only find the 7.1.2 version.
The other downloads in this post dont work anymore (oreo).
@androidjel sure, since there are no stable enough builds on O and even N builds aren't for everyday use with 3.4 kernel. I didn't launch O builds for a long time.
Clamor said:
@androidjel sure, since there are no stable enough builds on O and even N builds aren't for everyday use with 3.4 kernel. I didn't launch O builds for a long time.
Click to expand...
Click to collapse
@Clamor But could you launch a O build again? maybe i could try to help, I have some time to do that at the moment.