Database Develop

[DEV][G925F] CyanogenMod 12.1 Development

Hello there, it's time to get this rolling somewhere.
This is a Development-Thread. Please don't post if you aren't a developer.
What this IS
This is a Development thread, a platform for developers to discuss the development of CyanogenMod for the G925F. It's made so that we can get this working, fix up the problems - because there will be severe ones - and achieve a working official Rom at some point.
At the moment it's @OldDroid and me with help, but it would be awesome if interested devs would join in so that we can make this a team effort.
In short, it's a Dev-Thread in a dev section.
Right now it doesn't work and I'm not sure that it will work.
What this IS NOT
This is NOT a working Rom. Not even close. I can only link you to the kernel repo and soon to device and vendor, as they are almost completed for a first try.
And yes, there is no download link for the Rom. Because there isn't anything you could download yet.
This is also NOT intended as a Q&A thread. Please don't ask if your variant will be supported, I will respond by trolling. Firstand only priority is to get this running, then we'll talk about variants.
And ETA is an evil word with no meaning here. I work slowly, deal with it
Where are we currently?
Much further than a day ago
Thanks to @OldDroid, we've teamed up
All the links you want (minus the download link :angel
device: (soon, almost complete)
https://gitlab.com/mythos234/device_samsung_zeroltexx
vendor:
https://gitlab.com/mythos234/vendor_samsung_zerolte
kernel:
https://gitlab.com/mythos234/zerolte-kernel-CM
Once available, buggy alpha builds will be posted here
///
vendor and device will soon be pushed to my github
​

Reserved

i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)

vendor is setup
OldDroid said:
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
Click to expand...
Click to collapse
Welcome aboard then
vendor is finally setup and good to go!
https://github.com/mythos234/vendor_samsung_zerolte
It's apparently not without some minor casualties, but we got it. Huge thanks to @RaymanFX, he's helping me, since I'm not that much into CM building yet and I'm also basing this project on his CM for the N910C, which's 5433 is darn similar to our 7420, so we got a pretty good base to begin with.

add me as participant to the repos ^^
https://github.com/OldDroid

OldDroid said:
add me as participant to the repos ^^
https://github.com/OldDroid
Click to expand...
Click to collapse
Done for all the 3 of them

Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.

mythos234 said:
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
Click to expand...
Click to collapse
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?

nasko_spasko said:
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
Click to expand...
Click to collapse
I'm currently building the Rom with completely removed Bluetooth support

First Build is compiled and ready for a test.. But I can't install the zip. This would be hillarious if it wasn't so annoying

mythos234 said:
Besides I said it can't be installed Hard to test something you can't even install
Click to expand...
Click to collapse
I think that there was a mistake in the partition sizes.. /system was declared as 4.1GB, but it's only 3.6GB. Recompiling with a new value, should be able to flash it then

Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer

Aircondition said:
Good luck develop without documentation for exynos chipset.
Click to expand...
Click to collapse
The lack of drivers makes this a fun exercise almost Where's be the challenge if everything was easy...?

Aircondition said:
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Click to expand...
Click to collapse
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself

mythos234 said:
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
Click to expand...
Click to collapse
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk

lch920619x said:
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
As a base to know how to do it, obviously we can't just use drivers for a different chipset

Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.

mythos234 said:
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
Click to expand...
Click to collapse
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.

-Mr. X- said:
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
Click to expand...
Click to collapse
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes

mythos234 said:
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
Click to expand...
Click to collapse
I would personally flash an Engineering boot loader while doing this, to ensure version checking is not the issue.

[DEV] [WIP] Unofficial CM13 for the p880

Hey guys
In memory of a very dear friend who passed away yesterday, I am starting this thread and a new era for our x3.
CM has pushed their CM13 branches yesterday, which means it's time for a new project. This time, though, I will be all by myself.
Please do not expect any miracles soon, as the M sources still need to settle a bit before we can even hope for a halfway working build.
Once again, you have several ways to get in touch with me/us:
You can use this thread (but keep it development related)
We have our own IRC channel on freenode, called #p880-dev
Use our github site
PM (even though the other ways are preferable)
We are of course still open source, and you can find the repos on our github:
Device tree
Kernel
Blobs
Any help is greatly appreciated, be it pre-alpha testing, or helping with actual development and fixing bugs. Feel free to make a pull request on github, which we will most likely merge happily. If you're not that experienced in git, feel free to contact me about it.
If you want to use this sources/ROM as your base, you sure are allowed to, but please let me/us know about it before you release it and give proper credits.
That's all we're asking for.
I know you want to know the actual Status, so I try to always keep it updated in this OP:
Not working:
Most likely everything
Working:
Most likely nothing ​
Now, the most important part:
If you like our work and all the time we spent in order to get it working, feel free to buy us a coke/beer/whatever by donating a litte bit
Special thanks go to: (names in no particular order)
@Daniel Kng
@fritzcola
@sunsettrack4
@thegrim11
@LGaljo
@alfsamsung
@Adam77Root
kingf1 from IRC
And last but not least, please keep this thread on topic! All OT posts will be deleted without further warnings!
XDA:DevDB Information
[DEV] [WIP] Unofficial CM13 for the p880, ROM for the LG Optimus 4X HD
Contributors
laufersteppenwolf
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-10-06
Last Updated 2015-10-06

Reserved

A quick update, CM's sources are still not compilable as they are still working on the initial bringup.
I will stay on it and see what I can do

I will pay you, just please make final ROM for 4X, with everything working as it shoud be! That would be awesome!
Wysłane z mojego LG-P880 przy użyciu Tapatalka

I will pay you too. I would like when I will be to have the final ROM fo 4x. Thanks

Make it working relibly and responsively, and I will pay you too. You deserve it!
I don't mind if it takes months to achieve it. Just make it at some point, and I'll be happy!

Can't wait !!!
ps. i'm sorry for your friend

laufersteppenwolf said:
A quick update, CM's sources are still not compilable as they are still working on the initial bringup.
I will stay on it and see what I can do
Click to expand...
Click to collapse
I'm also waiting for complete bringup tried for daily driver... failed. If you need help just send me message on hangouts/mail

@laufersteppenwolf, I was hoping you could give insight regarding this current dilemma seen with CM13. http://pastebin.com/vHMRMS0E
Feel free to PM me or reach out on here. Wanting to know if you were successful getting past the problem and if so what was your solution. Your time and consideration is appreciated.

SHM said:
@laufersteppenwolf, I was hoping you could give insight regarding this current dilemma seen with CM13. http://pastebin.com/vHMRMS0E
Feel free to PM me or reach out on here. Wanting to know if you were successful getting past the problem and if so what was your solution. Your time and consideration is appreciated.
Click to expand...
Click to collapse
that's a CM issue and needs their fixing. Hence I did not look into it, because if I go on do my "fix" it will most likely differ from CM's fix and may then cause some later issues.
So I'm currently waiting for CM to fix it

Some days ago is builded a cm13 ZIP, but it doesnt even pass bootloader.
Here are my commits for device tree. I disabled most likely everthong what causes building errors like Audio and CameraWrapper.
Here are my commits https://github.com/lenzwagner/android_device_lge_p880/commits/cm-13.0
@laufersteppenwolf will be on IRC the next evenings. Hope you'll be there too.
---------- Post added at 07:45 PM ---------- Previous post was at 07:40 PM ----------
laufersteppenwolf said:
that's a CM issue and needs their fixing. Hence I did not look into it, because if I go on do my "fix" it will most likely differ from CM's fix and may then cause some later issues.
So I'm currently waiting for CM to fix it
Click to expand...
Click to collapse
They fixed it some days ago.
Look here:
1. http://review.cyanogenmod.org/114239
2. http://review.cyanogenmod.org/114277
3. http://review.cyanogenmod.org/112338

I already fixed the device tree quite some time ago without disabling it, will have to look into it another time as I have to fix my mom's lappy first...

laufersteppenwolf said:
I already fixed the device tree quite some time ago without disabling it, will have to look into it another time as I have to fix my mom's lappy first...
Click to expand...
Click to collapse
If you find time, i'm on IRC atm

@fritzcola, just got home from work, gonna check out those commits now. Thanks for posting them. ffmpeg has been a pain for me this past week trying to compile CM13 :-/. Gotta love a fresh brunch out the kitchen lol.
edit: eh, those commits have already been merged so problem still persists.
Sent from my Ascend Mate 2 using Tapatalk

SHM said:
@fritzcola, just got home from work, gonna check out those commits now. Thanks for posting them. ffmpeg has been a pain for me this past week trying to compile CM13 :-/. Gotta love a fresh brunch out the kitchen lol.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Just run "make clean" and "repo sync". Commits are already merged in source apart from one.
@laufersteppenwolf Can you upload the fixes to a " cm-13.0" branch?
And do you already go further than BL?

fritzcola said:
Just run "make clean" and "repo sync". Commits are already merged in source apart from one.
@laufersteppenwolf Can you upload the fixes to a " cm-13.0" branch?
And do you already go further than BL?
Click to expand...
Click to collapse
Yea, just verified I already have them in the source. Stagefright still being an issue. Need to look at gerrit and see if there is a commit on standby that may resolve my problem. codecs_utils.cpp fails to compile over at external/stagefright-plugins/utils/.

SHM said:
Yea, just verified I already have them in the source. Stagefright still being an issue. Need to look at gerrit and see if there is a commit on standby that may resolve my problem. codecs_utils.cpp fails to compile over at external/stagefright-plugins/utils/.
Click to expand...
Click to collapse
Weird cause i just compiled a build with no errors.

fritzcola said:
Weird cause i just compiled a build with no errors.
Click to expand...
Click to collapse
I got passed it finally. Seemed it was just a fluke with no explanation. Got to deal with this problem now. Take note of line 232 specifically. Haven't had time to mess with it yet.
Sent from my Ascend Mate 2 using Tapatalk

SHM said:
I got passed it finally. Seemed it was just a fluke with no explanation. Got to deal with this problem now. Take note of line 232 specifically. Haven't had time to mess with it yet.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Are you sure you're building for P880!? MSM8974 is Snapdragon stuff

fritzcola said:
Are you sure you're building for P880!? MSM8974 is Snapdragon stuff
Click to expand...
Click to collapse
No sir I am not. For another device, forgive me if that caused any confusion. My initial post on here was with regards to ffmpeg. A hunt for an unofficial build on xda brought up a few links and so wanted to make contact with the dev(s) to see if they had the same problem and/or fix so I may compare and possibly adapt if applicable my previous outcome. As for my current issue I do not expect any answer or results from here since its completely off topic from this device. I merely shared it in response with no intention or expectations for a solution. . I did take a look at your repo and saw ffmpeg is obsolete so I removed it from my tree as well since it was most definitely causing my builds to break.

Axon 7 GitHub Resources

@jcadduono - http://forum.xda-developers.com/showpost.php?p=68223333&postcount=5
sources: https://github.com/jcadduono/android...e_zte_ailsa_ii
kernel: https://github.com/jcadduono/android...mmits/twrp-6.0
@Unjustified Dev
TWRP: https://github.com/TeamRegular/android_device_zte_ailsa_ii
A user on the Chinese ZTE forums has created a github with the Axon 7 kernel code in it based on the A2017U B18 kernel dump.
http://www.myzte.cn/thread-272111-1-2.html
https://github.com/snowwolf725/ZTE_Axon7

TeutonJon78 said:
A user on the Chinese ZTE forums has created a github with the Axon 7 kernel code in it. Seems based off of the A2017U kernel dump.
http://www.myzte.cn/thread-272111-1-2.html
https://github.com/snowwolf725/ZTE_Axon7
Click to expand...
Click to collapse
ZTE have the kernel uploaded. (been up for quiet a while now)
http://opensource.ztedevice.com/
Under smartphone - ZTE A2017U

DrakenFX said:
ZTE have the kernel uploaded. (been up for quiet a while now)
www.opensource.zte.com
Under smartphone - ZTE A2017U
Click to expand...
Click to collapse
Yes, I've had since then. However, this is all github'ed, compile tested, and ready for forking.

We also have @jcadduono device tree and kernel posted from his TWRP work: http://forum.xda-developers.com/showpost.php?p=68195475&postcount=17

anks329 said:
We also have @jcadduono device tree and kernel posted from his TWRP work: http://forum.xda-developers.com/showpost.php?p=68195475&postcount=17
Click to expand...
Click to collapse
Indeed, I recommend folks clone this:
https://github.com/jcadduono/android_kernel_zte_msm8996/commits/stock-6.0
It's merged into CAF and allows future CAF merges without any issues. I updated it just the other day. Very clean kernel from ZTE, I've been really impressed.
From my stock-6.0 branch you can just run ./build.sh to compile a Image.gz and ./dtbgen.sh is automatically run after build to create a dtb.img.
I dont recommend using Image.gz-dtb as dtb building was not correctly set up by ZTE and I haven't bothered fixing it. Separated dtb.img works great though.
DEFCONFIG=zte_defconfig
DEVICE_DEFCONFIG=device_ailsa_ii
Otherwise you can use opensource-caf branch which is pure ZTE with no build modifications or scripts from me.
As for flashing kernels you build, check out LazyFlasher installer at:
https://github.com/jcadduono/lazyflasher
It will dynamically replace kernel image and dtb, and has a folder to put patch shell scripts. dm verity and forced encryption disabling already included as an example. Supports LZ4, Gzip, Bzip2, and LZO so far. Readme has more info. Avoids the need to constantly update ramdisks, and other branches have examples of things like SuperSU policy mod.

Hey guys, I am a developer thinking of buying this great cell phone. I've never tried to develop kernels or ROMs but I would love to learn and contribute to this community.
How could be the easiest way to learn and to start working in things related with this phone?
Thanks.

Thanks a lot for all the info!
@TeutonJon78 Maybe it would be beneficial to add these infos to the OP?

So...now we have two competing TWRP/device tree setups. @jcadduono and @Unjustified Dev it might make sense to keep them similar as make sure there aren't competing versions running around and making support harder.
Edit: I also updated the title of the thread to reference a more generic change -- just listing all known github resources.

grujildo said:
Hey guys, I am a developer thinking of buying this great cell phone. I've never tried to develop kernels or ROMs but I would love to learn and contribute to this community.
How could be the easiest way to learn and to start working in things related with this phone?
Thanks.
Click to expand...
Click to collapse
Well first of all you need the cellphone but it is heavily back-ordered, you can pre-order it now and you might or might not get it on 09/09/16.
I pre-ordered a month ago so I'll get my Gray Axon 7 on monday 08/22/16 (already have the tracking number), I would be willing to sacrifice it (selling it to you) if you want it, for the full price of course ($400 plus shipping). No means to sell anything, I'm not here to sell phones BUT if it is for a developer I'll do it and sacrifice a couple more weeks of wait time. All for the team.

grujildo said:
Hey guys, I am a developer thinking of buying this great cell phone. I've never tried to develop kernels or ROMs but I would love to learn and contribute to this community.
How could be the easiest way to learn and to start working in things related with this phone?
Thanks.
Click to expand...
Click to collapse
https://wiki.cyanogenmod.org/w/Doc:_porting_intro
This would be the best place to start learning Rom building.

Jose-MXL said:
Well first of all you need the cellphone but it is heavily back-ordered, you can pre-order it now and you might or might not get it on 09/09/16.
I pre-ordered a month ago so I'll get my Gray Axon 7 on monday 08/22/16 (already have the tracking number), I would be willing to sacrifice it (selling it to you) if you want it, for the full price of course ($400 plus shipping). No means to sell anything, I'm not here to sell phones BUT if it is for a developer I'll do it and sacrifice a couple more weeks of wait time. All for the team.
Click to expand...
Click to collapse
Hey thanks bro, don't worry. I just checked in Amazon and they are announcing that they will have stock on the 22 August, so maybe I will buy it there.
---------- Post added at 02:03 AM ---------- Previous post was at 01:58 AM ----------
Recon Freak said:
https://wiki.cyanogenmod.org/w/Doc:_porting_intro
This would be the best place to start learning Rom building.
Click to expand...
Click to collapse
Hey thanks Recon Freak. Are you going to start developing for this phone? Who are the developers that want to be involved porting CM for the Axon 7.
It would be great to have a master dev on porting ROMs and lp him with the process. Otherwise are there any devs interested on porting CM to this phone?
Thanks.

grujildo said:
Hey thanks bro, don't worry. I just checked in Amazon and they are announcing that they will have stock on the 22 August, so maybe I will buy it there.
---------- Post added at 02:03 AM ---------- Previous post was at 01:58 AM ----------
Hey thanks Recon Freak. Are you going to start developing for this phone? Who are the developers that want to be involved porting CM for the Axon 7.
It would be great to have a master dev on porting ROMs and lp him with the process. Otherwise are there any devs interested on porting CM to this phone?
Thanks.
Click to expand...
Click to collapse
I wish I had the time and skilz. I can build roms and tweak stuff, but that's it. I know the processes but time and knowledge are not on a 44 year old father of two's side. Tree development is best left to the young and knowledgable.

grujildo said:
Hey thanks bro, don't worry. I just checked in Amazon and they are announcing that they will have stock on the 22 August, so maybe I will buy it there.
Click to expand...
Click to collapse
I just ordered one yesterday and it will arrive 8/25, but seems that they are already out of stock by now... 1 to 2 months is the status now

Recon Freak said:
I wish I had the time and skilz. I can build roms and tweak stuff, but that's it. I know the processes but time and knowledge are not on a 44 year old father of two's side. Tree development is best left to the young and knowledgable.
Click to expand...
Click to collapse
Nice, If I managed to get the phone early I will tell you and we'll be able to port CM for sure
---------- Post added at 08:05 PM ---------- Previous post was at 08:05 PM ----------
Gachmuret said:
I just ordered one yesterday and it will arrive 8/25, but seems that they are already out of stock by now... 1 to 2 months is the status now
Click to expand...
Click to collapse
Yes ****, I just saw. Anyone know another way to get the phone?

grujildo said:
Nice, If I managed to get the phone early I will tell you and we'll be able to port CM for sure
---------- Post added at 08:05 PM ---------- Previous post was at 08:05 PM ----------
Yes ****, I just saw. Anyone know another way to get the phone?
Click to expand...
Click to collapse
There is some on Ebay right at the $400 mark, that's how I planned to sell you mine in case you wanted it.

[DISCUSSION] Nougat AOSP for ZE500KL ?

I was thinking: since we have an unlocked bootloader and custom roms, how hard would be to port AOSP Nougat?
There is any tecnical difficulty, like kernel version, that can block us?

Not much, I would imagine.
As far as I can tell, it'd just take a dev that's interested in putting in the effort.
Yes, this counts as my "yes, please" vote for Z00T.

I am votting with yes

I was thinking about do a try and compile it straight away, but i fear i'm not experienced enough to make something bootable

I don't think that the kernel or other thing will block it, but we got a custom ROM so late and I don't think we'll have a CM14 very soon

Cm14 should be prettt easy since we have cm 13, the point is that right now is not worth it because it's still in early stage, so a fully fledged cm13 would be more usefull.
AOSP is another talk because it's so barebone

Jhyrachy said:
Cm14 should be prettt easy since we have cm 13, the point is that right now is not worth it because it's still in early stage, so a fully fledged cm13 would be more usefull.
AOSP is another talk because it's so barebone
Click to expand...
Click to collapse
Umm, thanks for your thoughts about trying to bring N, it seem you got the answer yourself
from what i look at Z00L/T source, other than some fix and caf one, they could bring N to L/T with some borrowed libs. And looking from our source, I still found some line with L/T on it, so, yes, dev may bring N to this device, just hope that libs going to work with this devices.
But as you said, a fully fledged cm13 would be useful, using RR build for 3 days, and got the problem as they says. Plus, for me, front camera isn't working (called arclib or something, front camera effect when using asus camera, it's working fine with other camera because they didn't load that lib). Constant lag when using GPS other than "gps only" (might RR only problem). etc..
Either way, I hope that you could join the team (or, is he a one man army?) maintaining this device, fixing things come first, upgrade when everything is fine. At least "ok".
I don't know about AOSP, but many say choose CM because of CM broad compatibility layer. If that's true, then AOSP might slightly harder...
or... not really.
Sent from my ASUS_Z00RD using XDA Labs

Interesting, I'm not developer but I think this is possibke, Android 7.0 supports S410, maybe CM14 will better than AOSP.

yeah i still waiting ??
Sent from my ASUS_Z00ED using Tapatalk

Who wants to test BeanStalk 6.25 for Z00RD/Z00E?

imjohncarlo9 said:
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
Click to expand...
Click to collapse
I, but it will be possible tonight because now i working , phone at home

imjohncarlo9 said:
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
Click to expand...
Click to collapse
i will try tomorrow ...good for this ??
Sent from my ASUS_Z00ED using Tapatalk

Some news?

waiting :victory:

Waiting for some USEFUL news.

Today I try to compile it, but do not know if I aim, because I'm not a developer and I have no experience, but I try the same, stay connected, sorry for my bad english

I can't download the sources because it me give an errore i can't compile a ROM,sorry

Still waiting for news.

I tried to compile it myself, I downloaded all the sources, but since the Z00ED / RD is not officially supported by CyanogenMod, and then the repository and everything else must be manually added, I tried but I get error during compilation. Now we must wait for some developer is able to have time to complete it, because basically if you have created for the Z00L / Z00T do not see why you can not fill because they have the same processor. Sorry for my bad English

kurnalcool said:
I tried to compile it myself, I downloaded all the sources, but since the Z00ED / RD is not officially supported by CyanogenMod, and then the repository and everything else must be manually added, I tried but I get error during compilation. Now we must wait for some developer is able to have time to complete it, because basically if you have created for the Z00L / Z00T do not see why you can not fill because they have the same processor. Sorry for my bad English
Click to expand...
Click to collapse
Hi! Could this help you in some way? I don't know how, but I hope there is something usefull. This is a link to a russian forum where CM13 for ZE500KL was first posted by his original creator. Is in russian but I think you can use google translate to read the forum http://4pda.ru/forum/index.php?showtopic=766921

[ABANDONED] MIUI 8 For Huawei P8Lite ALE-L21

--FOR MORE INFO AND NEWS ALWAYS CHECK MY LAST REPLY!--
Thanks for understanding!
PROJECT IS ABANDONED.
Regards,

Holy ****, finally. I cant try it out for my self cause i need to leave to malta tomorrow but i can try it later

MIUI Rom, finally!!!!
I hope they fix the bug as soon as possible

Again, the ROM is NOT bootable, I need logcats from you to fix the problem, hopefully.
So don't expect this to boot.
Thanks for understanding!

Try to take a look here Logcats
I hope to have helped

Giuseppe300715 said:
Try to take a look here http://https://forum.xda-developers.com/showthread.php?t=1726238
Click to expand...
Click to collapse
I cannot open the link. It gives me an error.

XTutorials said:
I cannot open the link. It gives me an error.
Click to expand...
Click to collapse
He meant this link https://forum.xda-developers.com/showthread.php?t=1726238

XTutorials said:
I cannot open the link. It gives me an error.
Click to expand...
Click to collapse
I just fix the connection
---------- Post added at 09:04 AM ---------- Previous post was at 08:50 AM ----------
[Universal] [Flashable] [Logcat] [Guide] So your test ROM build didn't boot
[UNIVERSAL][LOGCAT]How to get & read a logcat/ Troubleshoot your own issues!
That's all I've found and that can be useful for both this Rom and others that you will develop.

Thank you, but I know how to dump logcats. I asked you if you could provide me some logcats of the rom not booting from your device and send me.
Thank you.

XTutorials said:
The ROM is compiled, but it doesn't boot and me and @AymenDe7 need logcats.
I will provide a download link, but just in google drive so not much downloads will be allowed. Bootable version (if) will be released on androidfilehost.
https://drive.google.com/open?id=0Bx9qplihpe8YVUNZRTNnSFY1bkk
Full no reject source code:
https://github.com/aymende7/XTutorials_Miui8
For now I need logcats from you.
Thanks for understanding!
Click to expand...
Click to collapse
Here's my logcat. http://www117.zippyshare.com/v/WcWK3ksX/file.html

I think there's problem with OpenGL
06-13 10:04:20.297 2468 2468 E libEGL : load_driver(/system/lib64/egl/libGLES_mali.so): dlopen failed: library "/system/lib64/egl/libGLES_mali.so" not found
06-13 10:04:20.297 2468 2468 F libEGL : couldn't find an OpenGL ES implementation
--------- beginning of crash
Click to expand...
Click to collapse
And if you would copy libGLES_mali.so to /system/lib64/egl?
Would it work?

Thank you for your logcats. I will see what I can do.

How does it go with progress?

Should boot if you use custom kernel and copy&replace blobs

I am giving up on trying to fix that error message. I am trying to build AOSP 6 and then try again patchtom, hopefully I won't get that error.

I know how to get miui booted, making aosp is not enough, there is changes you need to play with them like .rej files and boot.img too experienced on my old s2 plus i9105p. as I got stuck at animation boot.

haky 86 said:
I know how to get miui booted, making aosp is not enough, there is changes you need to play with them like .rej files and boot.img too experienced on my old s2 plus i9105p. as I got stuck at animation boot.
Click to expand...
Click to collapse
MIUI ports were one of the most time-consuming ports. I'm not sure how does it look like today but I'm pretty sure it's identical to how it used to be. First you had to modify the ramdisk and then patch all java resourced and with a bit of luck you get bootable rom.
I'm really sick of seeing all those roms all based on 1 device tree which is not even fully functionall yet. People keep making "new" roms but all are actually the same, all have same list of non-working features. Just compiling different android distro with same device tree over and over.
XDA used to be place for original work and for people who put effort in their projects. Now kids keep spamming dev threads with copy&paste roms or useles threads.

lozohcum said:
MIUI ports were one of the most time-consuming ports. I'm not sure how does it look like today but I'm pretty sure it's identical to how it used to be. First you had to modify the ramdisk and then patch all java resourced and with a bit of luck you get bootable rom.
I'm really sick of seeing all those roms all based on 1 device tree which is not even fully functionall yet. People keep making "new" roms but all are actually the same, all have same list of non-working features. Just compiling different android distro with same device tree over and over.
XDA used to be place for original work and for people who put effort in their projects. Now kids keep spamming dev threads with copy&paste roms or useles threads.
Click to expand...
Click to collapse
Yeah. We have like 2 developers(one is a team) On this device. Haky and OpenKirin. And 6 "different" ROMs that all work the same, with the exception off the nougat FOMs, which have even more bugs.

lozohcum said:
MIUI ports were one of the most time-consuming ports. I'm not sure how does it look like today but I'm pretty sure it's identical to how it used to be. First you had to modify the ramdisk and then patch all java resourced and with a bit of luck you get bootable rom.
I'm really sick of seeing all those roms all based on 1 device tree which is not even fully functionall yet. People keep making "new" roms but all are actually the same, all have same list of non-working features. Just compiling different android distro with same device tree over and over.
XDA used to be place for original work and for people who put effort in their projects. Now kids keep spamming dev threads with copy&paste roms or useles threads.
Click to expand...
Click to collapse
I don't think that...I'm a kid...I make my own roms with my tree...:angel:

haky 86 said:
I don't think that...I'm a kid...I make my own roms with my tree...:angel:
Click to expand...
Click to collapse
I know man, I wasn't talking about you. I was talking in general. I know you're doing god work, despite I'm not developing anything since a long time I still read forum and follow what's happening.
Like @Vinnipinni said, 2 guys and 6 "different" roms. But all working the same.
Back in times people were more likely waiting for stable CM/AOSP before compiling bunch of other distros. Now it's just mess.
I really wish I could go back to developing for android devices, especially now when I have programming knowledge and experience.