yashsingh1/xdaforums huggingface dataset:
[ZenFone 2 Original Android Development] jrior001:
The verification thing is expected, as is permissive for now on this test build. The windows script I can't really test on my own, if you have and suggestions on correcting it, I'm all ears.
[ZenFone 2 Original Android Development] gameeater:
It would not work to install the official rom 6.0 using FlashTool asus?

This would not update BOOTLOADER / IFWI?

Then I would install the TWRP-MM and then the CM13 with MM blobs.
[ZenFone 2 Original Android Development] jrior001:
Is there a 6.0 raw file for the flash tool? Isn't that what that tool requires? Otherwise the process would be flash tool to 5.0, upgrade to 6.0 and then unlock/twrp/CM

Additionally all of the above require a data wipe. Using my script to go from nightly to mm based cm13 does not.
[ZenFone 2 Original Android Development] gameeater:
This version that you uploaded with blobs of MM, is running super resolution? what can you tell us about it.

I have the inconvenience of my sensors can stop working (as soon as my device and Brazil) but I'm willing to test depending on the benefits I can get.
[ZenFone 2 Original Android Development] jrior001:
Super red seems to work, but I'm also currently shipping the entire stock media stack so I would expect media things to work better.

Fwiw the sensor issue was the big thing I kept seeing on the beta testers forum. Lots of devices had sensor issues on the beta MM releases. I haven't seen any reports on the first official release I regards to this.
[ZenFone 2 Original Android Development] kenbo111:
It seems that a lot of Brazilian phones have the sensor issue. But asus has announced they have a fix coming out soon.
[ZenFone 2 Original Android Development] Adhe_88:
how to Asus Z00ED ??
[ZenFone 2 Original Android Development] kamildouglas31:
just tried flashing the latest build of cm 13 9-5-16 and it wont work
[ZenFone 2 Original Android Development] tomg09:
Used the windows script... Everything seemed to work great (make sure to run as administrator). I'll use for a while and report if anything seems amiss.

Thanks jrior. Appreciate it!

Edit: By the way, tried a dirty flash from I think the Aug 8 build (wiped cache). I'll clean flash if I run into issues, but seems to be working for now.
[ZenFone 2 Original Android Development] Adhe_88:
are u sure ?? i will try this
[ZenFone 2 Original Android Development] Wo11ven:
Got the same result that most Brazilians are reporting with Asus' M. No sensors working. I've followed [MENTION=2836769]jrior001[/MENTION] guide to install the build with the new blobs merged and it was flawless, besides this know sensors problem. I'm a Brazilian myself and I must probably wait till Asus fix this issue.
[ZenFone 2 Original Android Development] Ashtrix:
Edited

:

The CM12.1 was dead before It stabilized, Seems like CM13 also same, I'm not blaming anybody here It's the way the things work for Non Nexus phones I presume, but hey I enjoyed CM13 here since It's inception ;)

So I guess I we got to wait for a couple of days to decide to go either the - Bootloader, IFWI firmware and Recovery upgrade for the MM (Marshmallow blobs based CM13) method

or

the CM14 with (MM Blobs based again ) to go forward, I think the latter is better since It'd be hard to keep two-three things going with a limited resources, developers. Also given that there's is no significant improvement based off our devs with the former option too. Also sticking to the third option - LP Blobs based CM13 is not advisable on long run, anti development again..:(

There's also this 4th option to downgrade to 5.0 and upgrade everything again, but that's official ASUS MM 6.0 route, Posting It so that people don't get confused.

Plus that CM14 (Nougat !!) running off a ZF2, Cheer up guys, Oh yeah also we will lose XPosed love for sometime. Wish there was some more better option for us (Multirom :p), But can't have everything right...Instead we will be on the bleeding edge, haha ;)

Good to see the development going forward, thanks to say99 and jrior001 for the much needed insight and goodluck :good: :cowboy: !!

Back on the thread's topic didn't test the latest build tho...
[ZenFone 2 Original Android Development] thariq06:
Yup,that's right.. The time flew too fast, before everything become stable,another thing already out..even cm13 is nightly version,im still enjoy it.. This is my 1st experience using CM ??
[ZenFone 2 Original Android Development] Druboo666:
@ jrior001 [MENTION=7111568]say99[/MENTION]

maybe this can help for verified boot issue

http://xdaforums.com/showpost.php?p=68532230&postcount=32
[ZenFone 2 Original Android Development] krasCGQ:
[MENTION=6810551]BORETS24[/MENTION] already tried it but it didn't solve 'Your device has failed verification and may not work properly' warning pop-up.
[ZenFone 2 Original Android Development] jeffrey roy:
:crying: im on official marshmallow now...but damn i miss cm13....if only,,if only,,the cam on cm13 works like the stock cam of asus, man i will not revert to stock rom ever again....
[ZenFone 2 Original Android Development] nutcasev1.5:
You will have to wait until cm14 for that
[ZenFone 2 Original Android Development] bjf182:
I had the same issue with the script on Win10 - it failed on the install of recovery and I had to manually install. Received the insecure boot indicator, which I think is more related to the unlocked bootloader than obtaining root.

Thanks Jason!
[ZenFone 2 Original Android Development] kamildouglas31:
nevermind i got it to work the file mustve didnt went all the way though
[ZenFone 2 Original Android Development] zanitos1991:
[MENTION=2836769]jrior001[/MENTION] maybe you should open up a new forum for cm13 unofficial, to get all the help there for members who would like to help you.
[ZenFone 2 Original Android Development] gameeater:
I think it would be a great idea, so instruct to use the stock 6.0 as a base.
[ZenFone 2 Original Android Development] ponnuvelpandian:
When can I expect the Official CM13 Built From Official MM Sources from ASUS without any known issues....?

Any Idea...?
[ZenFone 2 Original Android Development] juraci:
I'd like to know if the most recent CM13 build has corrected the mobile signal bug (that one we used airplane on/off as workaround). Thanks!
[ZenFone 2 Original Android Development] broomer68:
No, it is not fixed. Maybe with mm blobs, but they have troubles with sim2.

Verstuurd vanaf mijn ASUS_Z00A met Tapatalk
[ZenFone 2 Original Android Development] say99:
why do we even need to fix it if it isn't creating any issue?? [emoji14]
[ZenFone 2 Original Android Development] Luq4dmin:
I just want to ask. Can Camera2 api be implemented in this rom since the stock one doesnt support it ?
[ZenFone 2 Original Android Development] cl3i550nBR:
CM 14 is coming :o
[ZenFone 2 Original Android Development] ishantanish:
CM 14 is coming ????

When

How

????

:D
[ZenFone 2 Original Android Development] Trafalgar Square:
When it's ready.
[ZenFone 2 Original Android Development] Druboo666:
Don't Ask for ETA most imp rules on XDA REMEMBER
[ZenFone 2 Original Android Development] kenbo111:
Do you people even read the thread?
[ZenFone 2 Original Android Development] zanitos1991:
GPS and pixel master are amazing on merged blobs cm
[ZenFone 2 Original Android Development] beamscotty:
Cm13+MM blobs "hack"

I have two questions, before/if I jump:

1. I assume that any previous TWRP backup will not be valid once CM13 w. MM blobs is installed?

2. Will it be a straight upgrade from CM13+MM blobs to CM14 at a later stage, or will it require data-wipe?

Thanks.
[ZenFone 2 Original Android Development] xjammetx:
+1 I wanna know this too.
[ZenFone 2 Original Android Development] jupucino01:
https://vimeo.com/181812117

Why ambient display do this? Why not only one time?
[ZenFone 2 Original Android Development] Vazeka:
Hi,

1st thank you for what you guys do cyanogen is awesome!

2nd i'm trying to flash the new CM13 with new blobs but when i try to flash with adb sideload i get error message :

E: failed to verify whole-file signature

E: signature verification failed

Installation aborted.

I downloaded the rom 2 times with different browser but i always get this error at a random percentage of the sending.

Thanks and sorry for bad english! :)
[ZenFone 2 Original Android Development] jrior001:
1. you assumed right, bootloader/fw compatability will render old backups useless

2. Assuming we get to cm14 release, yes update would idealy be seemless, for those still on the official cm13 at that point will need to take the BL upgrade to proceed to cm14.

Ask google, that's the default behaviour on this feature.

Assuming you are using TWRP, Disable signature checking.
[ZenFone 2 Original Android Development] xjammetx:
thanks for that CM build on MM bootloader, seems way stabler, no signal drops for me. :D

I hope custom kernels come to this. :D
[ZenFone 2 Original Android Development] Vazeka:
Thanks, i was using the upgrade "kit" you provided but for some reason it didn't flash the recovery (message "FAILED no device found" Windows 10 x64, the other stuff worked), so i did it manually and it worked :)

Pixelmaster works perfectly!
[ZenFone 2 Original Android Development] septimvs80:
Is there any chance that the upgrade process to the MM kernel will become more straightforward in the near future, maybe with a new version of TWRP? I doubt that many would upgrade without the ability to use previous backups.
[ZenFone 2 Original Android Development] VinzNguyen:
where i can see mm blobs update process ? share me link . please
[ZenFone 2 Original Android Development] jrior001:
http://xdaforums.com/showpost.php?p=68542370&postcount=8551

I just added this link to the OP as well for easy reference
[ZenFone 2 Original Android Development] sd3993:
On the mm based cm 13 build, things like systemless supersu, magisk etc which repack the boot image don't seem to work. I'm guessing this is normal since mm bootloader needs a signed image. Is there any workaround for these systemless mods apart from using them in system mode of course?
[ZenFone 2 Original Android Development] catinsunshine:
For the new mm blobs kernel, it's 64 bits or still 32 bits?

http://theflamingskull.com/downloads/z00a/MM_BL_STUFF/
[ZenFone 2 Original Android Development] bmMachine:
First of all, thanks for this Rom!

After a decade finally had the balls to install Cm13. I been using it for almost a month and no major issues, one thing that I notice is the pixel master camera. It's a bit of noisy and the quality of picture is a bit degraded, another one is if you switch to video, youll notice that it is zoomed-in versus on the stock LP rom which is again reduce the quality of the video. I don't know if this issue has been addressed and already has a fix or it is just me.

Anyway official Mm has been released now by asus but theres no way im going to devolve my self back. it's just sad to sacrifice my camera in the name of performance.
[ZenFone 2 Original Android Development] catinsunshine:
Refer first page for Broken Features / Known Issues. They're all there. You can expect CM14 to fix camera problem. I found a guy mentioned it been fixed with new MM blobs version. But I didn't try it.

http://theflamingskull.com/downloads/z00a/MM_BL_STUFF/
[ZenFone 2 Original Android Development] Sayan44:
[MENTION=2836769]jrior001[/MENTION] So for the people with Older blobs will receive the Nightly updates or do we have to switch to the newer blobs updates? Because I was planning to do MM blobs update when we receive CM 14.
[ZenFone 2 Original Android Development] say99:
I do have something in head for that. but still need to give it a shot, basically it is something that I will have to do if I still want to have unified FlareM kernels
[ZenFone 2 Original Android Development] bmMachine:
Thanks dude, Ill just wait CM14 :good:

I just flashed the latest nightly, it seems fine now, Turning on the flash in slightly dim environment can also help to reduce the noise in picture and video.
[ZenFone 2 Original Android Development] sd3993:
So if my bootloader is unlocked with the official unlock tool and then i use to script to update bootloader & ifwi, the new bootloader is also unlocked right? or do i need to fastboot twrp everytime i need to use it?
[ZenFone 2 Original Android Development] kuyakom:
I think we just have to wait for the OP to release the CM14.
[ZenFone 2 Original Android Development] extreme.samir:
no new bulid ?
[ZenFone 2 Original Android Development] andrea.giommi:
hi,

Thanks for your works

1 info: i'm on stock 6.0.1 MM rom on my 551. in your opinion, can i flash your TWRP 3.0.2 by fastboot command without problems? actually i've the 2.8.7.0, and if i've understand, there's not TWRP official working with stock 6.0.1 rom

Thanks
[ZenFone 2 Original Android Development] puppetminds:
DELETED
[ZenFone 2 Original Android Development] sebx_g1:
Is in official new Marshmallow FM Radio functional ? If yes can it be ported to CM ?
[ZenFone 2 Original Android Development] putzgonzalez:
First of all, thanks for the AMAZING work being done on Zenfone 2. Even Asus couldn't do this much!

Just a simple question. If I try the new build with the MM blobs and I decide to go back to the official CM13 (with the old blobs), will it be possible?

Thanks!
[ZenFone 2 Original Android Development] xjammetx:
pixelmaster works well in the mm blobed cm13. many many thanks. also, battery life is better.
[ZenFone 2 Original Android Development] VinzNguyen:
your script for z008 are wrong in droidboot (54 not 112. the droidboot file is 54)

i flash the new MM blob rom. when reboot. the screen show "your device are not verification ............................." then go on. and SElinux is enforcing

anything wrong ?

sorry my english
[ZenFone 2 Original Android Development] lcsilveira:
Does anyone know if this latest build has problems with sensors in brazilian Z00A phones (like the official MM has)?

Thanks!
[ZenFone 2 Original Android Development] charliecantsurf:
help please !

i've used the script for bl upgrade [MENTION=2836769]jrior001[/MENTION] provided and it comes up with error : out of memory after rebooting into bootloader, now i'm stuck.

Start flashing ..

target reported max download size of 536870912 bytes

sending 'splashscreen' (464 KB)...

OKAY [ 0.203s]

writing 'splashscreen'...

OKAY [ 0.207s]

finished. total time: 0.410s

target reported max download size of 536870912 bytes

sending 'token' (3 KB)...

OKAY [ 0.188s]

writing 'token'...

OKAY [ 0.282s]

finished. total time: 0.469s

target reported max download size of 536870912 bytes

sending 'dnx' (108 KB)...

OKAY [ 0.188s]

writing 'dnx'...

OKAY [ 0.250s]

finished. total time: 0.438s

target reported max download size of 536870912 bytes

sending 'ifwi' (4096 KB)...

OKAY [ 0.281s]

writing 'ifwi'...

OKAY [ 0.391s]

finished. total time: 0.672s

target reported max download size of 536870912 bytes

sending 'fastboot' (15986 KB)...

OKAY [ 0.560s]

writing 'fastboot'...

OKAY [ 0.438s]

finished. total time: 1.013s

rebooting into bootloader...

OKAY [ 0.097s]

finished. total time: 0.100s

sending 'recovery' (15699 KB)...

FAILED (command write failed (No such device or address))

finished. total time: -0.000s

Done.
[ZenFone 2 Original Android Development] extreme.samir:
will I be able to install CM14 without any changes from CM13? or there is any procedure to follow?
[ZenFone 2 Original Android Development] jrior001:
Windows script? Just fastboot flash the new recovery manually.
[ZenFone 2 Original Android Development] jrior001:
If/ When there is a CM14 to consider I'll post instructions.
[ZenFone 2 Original Android Development] 1boy1dr:
I have an issue with some apps that go into expanded desktop. With some apps it's only every once and a while when the screen is touched but others it's always there, until you pull down the notification drawer. A bunch of very thin black and white line do across the screen, depending on the app it's there until pull down the notification drawer (as previously mentioned) or its only there for a few seconds until the screen goes black and then back to normal. Two examples are Monument Valley (free on amazon underground) and ES Image browser (part of ES File browser). Not sure on the exact steps of reproducing the bug, it just happens.

My log, taken right after I experienced this.

https://drive.google.com/file/d/0B4fICrsx5Ym4WTVVUm54dS1qVFk/view?usp=docslist_api

sent from my Asus Zenfone 2 running CyanogenMod 13
[ZenFone 2 Original Android Development] mr_gourav2000:
Ok
[ZenFone 2 Original Android Development] Jaybles22:
I confirm also that MP4 videos are working well on today's build (even in Chrome or Instagram). No more annoying bugs from my point of view, your work is stellar devs ! :)
[ZenFone 2 Original Android Development] hshaikh:
Found a new bug. If you change dpi, I used 440, pop up questions that need input are looking weird.
[ZenFone 2 Original Android Development] mr_gourav2000:
I try many ringtones and getting same problem.
[ZenFone 2 Original Android Development] wifestealer:
I'm on today's build. I did dirty flash from 14 December built but i haven't found any pop up question bug. I changed DPI same on 440

---------- Post added at 09:58 PM ---------- Previous post was at 09:58 PM ----------

No problem here like that.
[ZenFone 2 Original Android Development] bjf182:
Nine Exchange Email

Running the Nine Exchange client for my corporate email. Works properly on CM12.1, but fails when attempting to encrypt when setting up a new account.

Seems like there is either an issue accessing the local storage or perhaps an ARM/x86 library issue.

12/15/2015 build.
[ZenFone 2 Original Android Development] hshaikh:
Here is an example. This box looks normal in 480 dpi

---------- Post added at 10:36 AM ---------- Previous post was at 10:34 AM ----------

https://drive.google.com/file/d/0B3YJv7bPQ1kwNWs5QTA0VmhyNms/view?usp=docslist_api
[ZenFone 2 Original Android Development] jrior001:
I'll add this to my encryption to do list. Device encryption works, but changing any pin/pwd after that doesn't seem to be working.
[ZenFone 2 Original Android Development] mr_gourav2000:
One more problem (bug).

Charging current is less then stock by zenpower.

Don't now with original ac charger, due to fast charging not showing by ampere app.

model # Asus_Z00A

CPU Speed 2.3 ghz

RAM Size 4gb
[ZenFone 2 Original Android Development] nazagan:
I still have an issue with the network, i have to select manually for each reboot and after that (it connect) there is no data, I have to toggle on/ toggle off airplane made and I can use data.

I'm on 15/12 build with the orange mobile operator (France).
[ZenFone 2 Original Android Development] Ritik17:
if you'll use a theme then that bug will not appear
[ZenFone 2 Original Android Development] espeon:
Try loading https://streamable.com/2hvj in chrome or the default browser. (alternatively, try downloading http://techfo.xyz/i/2015-12-14_23-55-51.0c7ec9.mp4 and opening it in the gallery)

Audio playback works just fine, but video playback just never works. I'll try with the vlc player in a bit (I think they ship their own libraries?) so that _should_ work fine.

edit: vlc isn't available for 6.0 yet, apparently
[ZenFone 2 Original Android Development] XeidiDent:
Have you tried to do a clean flash?

Also, there's a new build already, try to clean flash it.
[ZenFone 2 Original Android Development] wifestealer:
Try MX player and uc browser, chrome ain't good.

---------- Post added at 11:21 PM ---------- Previous post was at 11:19 PM ----------

Is it on contract?
[ZenFone 2 Original Android Development] nazagan:
I'm on the lastest build and I tried a clean flash.
[ZenFone 2 Original Android Development] wifestealer:
Still problem persists?
[ZenFone 2 Original Android Development] ELusiveLPFAN:
About DPI bug. I sat DPI via Build Prop Editor to 400 (works only if you previously not change default value via settings or ui tuner, wipe cache don't help after) and it properly render up.
[ZenFone 2 Original Android Development] Sayan44:
mp4 files are working fine again in chrome :)
[ZenFone 2 Original Android Development] nazagan:
Yes, I had already done that before my first post.
[ZenFone 2 Original Android Development] VinzNguyen:
pixelmaster work well but cant save to SD card
[ZenFone 2 Original Android Development] kenbo111:
You need to make it a system app
[ZenFone 2 Original Android Development] VinzNguyen:
guide me ! please
[ZenFone 2 Original Android Development] kenbo111:
Use this https://play.google.com/store/apps/details?id=de.j4velin.systemappmover
[ZenFone 2 Original Android Development] BuckyBug:
USB Logo on booting up in Bootloader Mode !

My phone(Zenfone 2) is working normally,but when i try to go into Bootloader mode or recovery mode it shows just shows USB logo.

How to get rid of it.(i have twrp recovery installed but cannot access it due to this issue).

Thanks
[ZenFone 2 Original Android Development] puppetminds:
[MENTION=2836769]jrior001[/MENTION] I get this upon bootup, which is no issue after the 5sec is up.....i followed the instructions for M_BL_upgrade_for_zf2_551ml_6.0......but just wondering because it looks weird when the rest of the system works? any thoughts? thanks in advance
[ZenFone 2 Original Android Development] puppetminds:
I followed it everything went fine except for the startup image which is no issue but just weird
[ZenFone 2 Original Android Development] bjf182:
If you read elsewhere in the thread this was already covered. This is standard behavior on stock MM if the bootloader is unlocked. Nothing to concern yourself with.

---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------

xjammetx - Does Super Resolution work properly for you in the MM blobbed CM13? It's still returning mangled photos for me.
[ZenFone 2 Original Android Development] zanitos1991:
[MENTION=7548534]BuckyBug[/MENTION] it seems you bricked your phone

Reflash twrp using fast boot "fastboot flash recovery (twrp name).IMG"
[ZenFone 2 Original Android Development] kenbo111:
No, as he said, it's only when he goes into recovery.
[ZenFone 2 Original Android Development] jupucino01:
Is there a way to use the "zenflash" with cm13?
[ZenFone 2 Original Android Development] putzgonzalez:
Just updated to the new MM based build. Still having the "no network" issue on mobile data :(. Still need to turn airplane on and off to connect :(

EDIT: Sensors not working also (Brazilian phone). I cannot rotate my screen.
[ZenFone 2 Original Android Development] kamildouglas31:
just tried flashing the recovery and i got an permisson denied messge help what do i do now
[ZenFone 2 Original Android Development] kenbo111:
1 use admin mode for your command line.

2 make sure USB debugging is on

3 turn off and pin/pattern lock you may be using
[ZenFone 2 Original Android Development] pedro1977:
I've just returned from a third world country to a 1st world one. While over there i would have frequent drops but since returning here I've had none that I've noticed. This problem could be network related (deployment) or a compatibility issue between the phone and network. Until the kernel is updated it wont be possible to analyze this any further.
[ZenFone 2 Original Android Development] zanitos1991:
Once updating with blobs should we use cm updater???
[ZenFone 2 Original Android Development] jrior001:
No
[ZenFone 2 Original Android Development] putzgonzalez:
I wish it was carrier problems, hahaha

I live in the city centre, and the LTE coverage is pretty good around here. Still, the connectivity on CM, even on the new blobs, is very inconsistent. I thought it would be solved this time, but I think it's just better to wait for the CM14 XD

Even more for the fact that the sensors are also not working, at least, not in here. I'm having the same problems that people had in the official Asus MM build. Not a single sensor working :(

PS: if I change to a new ROM after updating with the blobs, will I brick my phone? I mean, considering that I shouldn't use CM updater anymore...
[ZenFone 2 Original Android Development] kenbo111:
I think the safest way, for now, to do it, would be to get asus flash tool and flash a raw image of stock L. Then you can unlock, install TWRP, and have at it.