Develop Bugs

[ROM][UNOFFICIAL][4.4.3][D2TMO/D2LTE] Omni Rom for all D2s [Multi-window][OpenDelta]

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?

[ROM][5.1][Flounder] Pure AOSP 3/18/15 [LMY47D]

Hello! I'll be posting pure AOSP builds whenever there are new versions of android released (providing I have the time).
If you choose to use these builds, please ensure you have unlocked your bootloader and have custom recovery installed. I have also noticed that TWRP seems a little wonky at this point, so in order for me to flash it correctly, I had to wipe, then restart recovery, then flash. Hope that's not the case for everyone else.
3/18/15
Added ability to change DPI.
3/15/15
No longer messes with recovery at all. Bluetooth working, data does not force encrypt.
3/13/15
Android 5.1.0_r1 (LMY47D)
This release will wipe your recovery. If anyone needs this changed let me know and I will build another.
1/3/2015
Android 5.0.2_r1 (LRX22G)
Data is now encryptable, meaning your unencrypted data should stick going forward.
Included my own build of stock kernel with Linaro 4.9.3 toolchain.
Fixed bluetooth (thanks Lollipopalooza/Craig)
No longer need to re-flash recovery.
12/6/2014
Android 5.0.1_r1 (LRX22C)
You will need to install separate gapps
You will need to re-flash your custom recovery after you install (you all let me know if I should change this or not, I think I will on future builds)
I am not responsible for anything that happens to your device or to you, yourself while flashing this.
Latest DL Links will be in post #2.
XDA:DevDB Information
Pure AOSP Flounder, ROM for the Nexus 9
Contributors
gchild320
ROM OS Version: 5.0.x Lollipop
Based On: AOSP
Version Information
Status: Stable
Created 2014-12-06
Last Updated 2015-01-03

Downloads
3/18/15
https://www.androidfilehost.com/?fid=95916177934543409
3/15/15
https://www.androidfilehost.com/?fid=95916177934541983
3/13/15
5.1 - https://www.androidfilehost.com/?fid=95916177934540786
1/3/14
Flounder Android 5.0.2_r1 build LRX22G https://www.androidfilehost.com/?fid=95864024717074545

Future FAQ if necessary (let's hope not).

Thank you!!!!
Will test it tomorow
I hope cm12 will build on arm64 soon

Just a few questions. What gapps do you recommend? What twrp ? There is the mainline version and the one @USBhost did. Thanks for the ROM!! Really appreciate seeing this show up.

mpmilestogo said:
Just a few questions. What gapps do you recommend? What twrp ? There is the mainline version and the one @USBhost did. Thanks for the ROM!! Really appreciate seeing this show up.
Click to expand...
Click to collapse
I didn't realize that there were two versions of twrp...I used the one from twrp website.

gchild320 said:
I didn't realize that there were two versions of twrp...I used the one from twrp website.
Click to expand...
Click to collapse
Yep
https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery
I fixed some things
in it
Factory reset will not encrypt data
fixed the device name
look bit better
custom built FIRE-ICE kernel for recovery

USBhost said:
Yep
https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery
I fixed some things
in it
Factory reset will not encrypt data
fixed the device name
look bit better
custom built FIRE-ICE kernel for recovery
Click to expand...
Click to collapse
Hell yes checking this out tomorrow.

build
Awesome !!!! Been waiting for this. How did u build? Last week since their are little options for roms decided to build one on my own and i did a repo sync to Google source but when i did lunch flounder wasn't listed in the build options ?

Flounder still isn't listed just lunch it anyway

Made a video running the ROM. Works very well!!
https://www.youtube.com/watch?v=kVQW-PMepn0

Hello,
can anyone provide a minimal gapps pack? I would like to avoid too much bloatware

http://fitsnugly.euroskank.com/?rom=banks&device=gapps
This maybe what you are looking for.
Hiro Nakamura said:
Hello,
can anyone provide a minimal gapps pack? I would like to avoid too much bloatware
Click to expand...
Click to collapse

belair56 said:
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
This maybe what you are looking for.
Click to expand...
Click to collapse
Well i don't think it's 64bit version or is it ?

Hiro Nakamura said:
Well i don't think it's 64bit version or is it ?
Click to expand...
Click to collapse
From what I understand the apps themselves need to be optimized for 64 internally. These are all Google apps so they are if Google did so. As you update from the play store you don't choose if you're running 64bit or not.
As always I can be wrong.

Hiro Nakamura said:
Well i don't think it's 64bit version or is it ?
Click to expand...
Click to collapse
This is actually a great question.

Adaptive brightness doesn't work. Other than that everything seems to be working.
Edit: Okay so I used an app to look at which sensors were working and which ones weren't... The proximity sensor is not working at all.

omvir said:
Adaptive brightness doesn't work. Other than that everything seems to be working.
Edit: Okay so I used an app to look at which sensors were working and which ones weren't... The proximity sensor is not working at all.
Click to expand...
Click to collapse
Adaptive brightness is working flawlessly. Maybe you had a bad download or flash.

gchild320 said:
Flounder still isn't listed just lunch it anyway
Click to expand...
Click to collapse
I use USBhost's version of TWRP. I tried to flash the rom following directions in OP. It wouldn't flash. First it said for flounder and this device is flounder. Also said something about updater binary. I got this with the other rom also. I tried un-mounting and mounting system, but I still got the error messages. Any ideas?

jlokos said:
I use USBhost's version of TWRP. I tried to flash the rom following directions in OP. It wouldn't flash. First it said for flounder and this device is flounder. Also said something about updater binary. I got this with the other rom also. I tried un-mounting and mounting system, but I still got the error messages. Any ideas?
Click to expand...
Click to collapse
I manually changed it to work with official twrp... Not sure why twrp is calling it volantis instead of flounder but that's why. Also, to get anything to flash in twrp at the moment, I have to reboot recovery after wiping. Hope this helps.

[Q] Switch parition

Hello, i have managed to root my Find 7 x9076 on Cos 2.0.4i b and will be following Recovery Flasher for flashing recovery. My question here is:
1. on 2.0.4ib it gives option for Switch Partition (to merge some partition to get more space) but is it called LVM or Unified?
2. Once i have flashed TWRP or any other recovery and after having used Switch Partition, will i be able to flash any custom rom for find 7 or does it have to be only Unified rom?
will appreciate the help i can get.

treacherous_hawk said:
Hello, i have managed to root my Find 7 x9076 on Cos 2.0.4i b and will be following Recovery Flasher for flashing recovery. My question here is:
1. on 2.0.4ib it gives option for Switch Partition (to merge some partition to get more space) but is it called LVM or Unified?
2. Once i have flashed TWRP or any other recovery and after having used Switch Partition, will i be able to flash any custom rom for find 7 or does it have to be only Unified rom?
will appreciate the help i can get.
Click to expand...
Click to collapse
LVM.
More info at http://www.oppoforums.com/threads/reference-lvm-storage-user-guide.23440/

Entropy512 said:
LVM.
More info at http://www.oppoforums.com/threads/reference-lvm-storage-user-guide.23440/
Click to expand...
Click to collapse
Read that already and thank you for such a great post. Now, once i have done LVM using switch parition will i be able to flash any custom rom or just those which say unified?

treacherous_hawk said:
Read that already and thank you for such a great post. Now, once i have done LVM using switch parition will i be able to flash any custom rom or just those which say unified?
Click to expand...
Click to collapse
You can only flash ROMs which support LVM repartitioning.
---------- Post added at 11:56 PM ---------- Previous post was at 11:52 PM ----------
I've compiled a list of ROMs here: http://www.oppoforums.com/index.php?threads/23362/

Irwenzhao said:
You can only flash ROMs which support LVM repartitioning.
Click to expand...
Click to collapse
how to distinguish between the 2, if i take omnirom example it only says Find7 https://dl.omnirom.org/find7/
doesn't mention if it is supports LVM or not.
Also which all roms are available for Find7 with LVM Support?
Edit: Got it from your post on oppoforum. Thanks mate.
Edit: @Irwenzhao can i flash DU on Find7 x9076 as it says 7a.

treacherous_hawk said:
how to distinguish between the 2, if i take omnirom example it only says Find7 https://dl.omnirom.org/find7/
doesn't mention if it is supports LVM or not.
Also which all roms are available for Find7 with LVM Support?
Edit: Got it from your post on oppoforum. Thanks mate.
Edit: @Irwenzhao can i flash DU on Find7 x9076 as it says 7a.
Click to expand...
Click to collapse
Yes I believe DU is universal.

Irwenzhao said:
Yes I believe DU is universal.
Click to expand...
Click to collapse
Ok. so are these rom with LVM repartition are LVM aware and automatically detect if the phone is LVM or not? and it is not it will install like normal rom and if it is then it will install with LVM?
can you also tell me all the model number for Find 7 and 7a? as i also see Find7s as model

treacherous_hawk said:
Ok. so are these rom with LVM repartition are LVM aware and automatically detect if the phone is LVM or not? and it is not it will install like normal rom and if it is then it will install with LVM?
can you also tell me all the model number for Find 7 and 7a? as i also see Find7s as model
Click to expand...
Click to collapse
Find 7s is the Find 7QHD model.

Irwenzhao said:
Find 7s is the Find 7QHD model.
Click to expand...
Click to collapse
this is the one with model number x9076?
Edit: more i read more i get confused. I was going through @Entropy512 thread on 4.4.x omnirom and he has provided lvm script for setup and remove. So if i already setup lvm using the inbuilt feature on cos 2.0.4ib and then install twrp (i believe it has to be lvm aware twrp? does such twrp exist?) and then flash either omni 4.4 or 5.0 or nameless rom kk or LP then it will still be lvm remaped?
2nd scenario: i do not have to do lvm remapping, install omni rom 4.4 or 5.0 and after installing omni i can run setuplvm and removelvm as required?

treacherous_hawk said:
this is the one with model number x9076?
Edit: more i read more i get confused. I was going through @Entropy512 thread on 4.4.x omnirom and he has provided lvm script for setup and remove. So if i already setup lvm using the inbuilt feature on cos 2.0.4ib and then install twrp (i believe it has to be lvm aware twrp? does such twrp exist?) and then flash either omni 4.4 or 5.0 or nameless rom kk or LP then it will still be lvm remaped?
2nd scenario: i do not have to do lvm remapping, install omni rom 4.4 or 5.0 and after installing omni i can run setuplvm and removelvm as required?
Click to expand...
Click to collapse
I don't use LVM repartitioning, nor do I support using that method. Coldbird's method is much simpler in my opinion. You'll need to do more research/reading up on your own.

Irwenzhao said:
I don't use LVM repartitioning, nor do I support using that method. Coldbird's method is much simpler in my opinion. You'll need to do more research/reading up on your own.
Click to expand...
Click to collapse
Well after reading entropy's posts i have decided not to use unified method, also why risk it when there is already an option for lvm. If someone else could answer me on this as to if LVM repartition would remain while switching from COS to Omni or nameless.

Um, pretty much every question you've asked was answered in the post that I linked to... (With the exception of nameless adding autodetect last week, I need to update the list)
Other than the question of switching from one firmware to another (like COS 2.0.4 to Omni) - If you've got LVM set up, and you switch from one thing that supports LVM to another, all you need to do is Wipe Data/Factory reset in recovery (which you need to do whenever switching anyway...)
setuplvm/removelvm are only for enabling/disabling LVM - once it's enabled it stays enabled

maybe someone can help. LVM doesnt seem to make my device 32GB. still shows 3GB in nameless
1. flashed twrp 3.0.2-0
2. wipe/format all (no more OS, clean device)
3. flash setuplvm
4. reboot twrp
5. flash nameless 6, gapps (no root needed right? nameless already rooted?)
am i doing something wrong here?

[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

[ROM][unified][4.4.4] OmniROM

OmniROM
[#KITKAT]
for Samsung Galaxy Nexus (Unified)
​
[#WHATSOMNI]
[#WARRANTY]
Downloads:
[#DLGITHUBIO]
[#INFOOMNI]
Specials added on top of Official OmniRom Source
All in One Animation Control
Battery Saver mode
On-The-Go mode
Implement App circle sidebar
follow dark 4.4 UI
Those features have never been ready for official Omni, but people spend a lot of time writing those features and i really like those.
I am trying to release an security update monthly after google publish android security bulletins.
Support development
[#DONATETOME]
XDA:DevDB Information
[unified][4.4.4] OmniROM, ROM for the Samsung Galaxy Nexus
Contributors
Android-Andi, Ziyan
Source Code: https://github.com/omni-security
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Current Stable Version: Final Build availabl
Created 2017-08-12
Last Updated 2017-08-18

Hello everyone, first of all, great work @Android-Andi thank you to take the time to support our old device !
And then sorry for my noob questions but :
- I didn't quite understand the difference between device specific and unified builds and I don't want to make a mistake flashing the wrong one.
- What is the main difference between Omni 4.4, Omni 6.0 or Slim 6.0? I want to use one of those but I don't know which one I think Omni 4.4 is the closest from what I had with the official Jelly Bean ROM and the 2 others are optimized version of Marshmallow. And is Slim 6.0 faster than Omni 6.0?
Thank you again

Radder124 said:
I didn't quite understand the difference between device specific and unified builds and I don't want to make a mistake flashing the wrong one.
Click to expand...
Click to collapse
Unified builts are for all types of tuna: Maguro, Toro, Toro+. When booting only the needed (device specific) drivers are loaded, but the drivers fir all supported devices are on board...

Unified works on all tuna variants: maguro, toro and toroplus at same time. It detects your variant on first boot and places needed files. That's the one I'll compile in future too.
Which rom is the best? Use the power of your TWRP and try it out. Test one, check if it fits your needs. If not, make a backup and try a different rom.

Android-Andi said:
Which rom is the best? Use the power of your TWRP and try it out. Test one, check if it fits your needs. If not, make a backup and try a different rom.
Click to expand...
Click to collapse
I can ask you a different question With all the new ROMs, I don't know which ROM you would like to receive bug reports from. Crash logs, etc. I know there is no point giving you CM12.1 crash logs. Which ROM would you like us testing and reporting bugs from?

Thank you for providing this ROM! I finally found a ROM with a working camera for the Gnex with security patches (from 2017-07).

...anyone gotten Xposed Framework installed/working with this? Halp

JLsoft said:
...anyone gotten Xposed Framework installed/working with this? Halp
Click to expand...
Click to collapse
There's somewhere an updated version flying around on XDA, maybe you'll find it (i don't have it anymore)

JLsoft said:
...anyone gotten Xposed Framework installed/working with this? Halp
Click to expand...
Click to collapse
try this

@Android-Andi is it possible to use this ROM with F2FS file system? Which DDK version is included in this ROM? Thank you for your contribution.

Those who are on 4.4:
AOSP Browser was removed for security reasons. Most lightweight Browser use KitKats webview which isn't up to date any more and there's ATM no proper way to update it.
You should use a browser which has its own webview implementation like Chrome, Firefox or Chromium.
From what I have tested Chromium seems to be a good solution. Here's my self compiled Chromium:
https://github.com/andi34/prebuilt_chromium/raw/master/ChromePublic.apk
(It's only missing h264 encoder for legal reasons...H.264 is not a free codec and I don't have the license for distributing)
For Android 5+
https://github.com/andi34/prebuilt_chromium/raw/master/ChromeModernPublic.apk
For Android 7+
https://github.com/andi34/prebuilt_chromium/raw/master/MonochromePublic.apk

New builds are up.
Switched to default libion, thx to @Ziyan and @amaces !
Note: don't flash any custom kernel on this build (also AnyKernel isn't compatible ATM)!

I've been away from the scene for a while so please catch me up. Does this rom bypass carrier limitations when using usb tether?

madspeed said:
I've been away from the scene for a while so please catch me up. Does this rom bypass carrier limitations when using usb tether?
Click to expand...
Click to collapse
Yep, these custom ROMs have nothing to do with carriers

March update is online. Enjoy!

Dear developer,
firstable many thanks for your Rom
I was using OMNI 4.4.4 dated 2015 but I was living issue with GMAIL, HANGOUT and GDRIVE
Today I discovered your product and Installed it on my MAGURO with a clean installation
Unfortunately after few hours I am suffering reboot
The system boots well but after few seconds it reboots itself ... continuosly ...
I am using omni_tuna-4.4.4-20180311-1556
I used GAPPS open_gapps-arm-4.4-pico-20180427
I rooted with SUperSU 2.82 R5
I tried to wipe cache, dalvik-cache, system and reinstall the rom and the gapps wo success
I tried to remove root wo success
HAve you some idea to help me ?
Thanks
Paolo
[EDIT]
I wiped all (clean installation) and installed the older version of rom (omni_tuna-4.4.4-20180128-0005)
[I noted that this version is bigger than the newer of around 30MB ...)
Same GAPPS af above
Same root of above
It runs well now ... cross the fingers and stay tuned

People having issues on latest build could try https://forum.xda-developers.com/showpost.php?p=76429699&postcount=188

The request from root was one of my suspect
Do you suggest to flash new kernel after last updated ROM, gapps and root and so before the first boot ?
Do you confirm that this workaround is not necessary with the previous version ?
Are you able to identify which version needs and which didn't ?
For instance I am using the January version .... Did I need to flash new kernel ?
Inviato dal mio Galaxy Nexus utilizzando Tapatalk

It could be it's needed on all KK roms since end of last year. But only works for latest builds using default libion.

Android-Andi said:
It could be it's needed on all KK roms since end of last year. But only works for latest builds using default libion.
Click to expand...
Click to collapse
Excuse my noob ... What does it mean default libion ?
Inviato dal mio Galaxy Nexus utilizzando Tapatalk