Database Users

[GUIDE] How to build AOSP kernel from source S4 Mini (i9195 & i9190)

Welcome to Kernel build guide.
WITH THIS METHOD YOU WILL GET installable zip for your kernel.
My english is not best but i think you all will understand this guide . I write this guide because i dont own S4 Mini anymore and unfortunally i cant build kernels or roms anymore for s4 mini.
this is my kernel build method. you will have everything (tools) for build a kernel for s4 mini device. if you have questions, then ask it here. this kernel method is working only aosp based kernel (not tested for tw kernel but it may also work but you need ramdisk of tw kernel)
be sure you have packages installed for build something like this, or edit or clone a github source. look at cm kernel build guides.
1. Download build-s4-mini-kernel.zip [here]
extract it to root of your user directory (my is /home/proxuser/)
2. We need toolchain 4.7.4 by Christopher83 original thread [here]
download
arm-unknown-linux-gnueabi-linaro_4.7.4-2013.07-build_2013_07_12.tar.bz2
extract arm-unknown-linux-gnueabi-linaro_4.7.4-2013.07 folder to toolchains folder (home/yourusername/toolchains) and name it linaro_4.7.4
Download Build scripts from my source here
download:
- abooteur_3g.img
- abooteur_lte.img
- build_all.sh
- build_eur_3g.sh
- build_eur_lte.sh
- build_master.sh
- mkbootfs
- mkbootimg
and put them to your kernel folder "root folder of your kernel".
if you want clone a kernel source: example CyanogenMod's cm-10.2 kernel then
open Terminal, and be in user root folder /home/yourusername (just open terminal and your there)
Code:
git clone https://github.com/CyanogenMod/android_kernel_samsung_msm8930-common.git -b cm-10.2
if you want clone my Kartal kernel then
Code:
git clone https://github.com/proxuser/kartal.git -b master
it will named "if you cloned cyanogenmod kernel android_kernel_samsung_msm8930-common" if you clone my kernel then it will named "kartal"
you can rename kernel folder, its not problem.
if you want change of kernel name(example kartal), then go yourkernel/arch/arm/configs/kartal_defconfig and edit CONFIG_LOCALVERSION="-Kartal" change only "Kartal" for your kernel's name. if you want change defconfig example "kartal_defconfig" to "yourkernel_defconfig" then you need change it in build_master.sh too that it builds with your config file.
if you downloaded your kernel source and your build tools are there then lets start
Open terminal
type
Code:
cd yourkernelfolder
for build both phones i9195 & i9190
Code:
./build_all.sh
if it denies access for build_all.sh then type
Code:
chmod 777 build_all.sh
you can give all files access with this command.
for build i9195
Code:
./build_eur_lte.sh
for build i9190
Code:
./build_eur_3g.sh
finally it will start building. it will done within 4-5 min. depend your pc speed.
after it builds succesfully, your kernel will be in your /home/yourusername/Packages/ folder
IF YOU WANT add new changes from CM or other kernel to your kernel
then open Terminal
cd yourkernelfolder
git remote add CyanogenMod https://github.com/CyanogenMod/android_kernel_samsung_msm8930-common.git
git fetch CyanogenMod
this will fetch CyanogenMod kernel changes but it will not apply to your kernel. you will add changes step by step yourself. copy commits SHA from CyanogenMod kernel and
open Terminal
Code:
git cherry-pick 2108e6c3109ae126590a81876145a1f17d6771b5
if you get success on pick a commit then you will get a message like this
Code:
[email protected]:~/kernel$ git cherry-pick a41564437a0eb910d0347d274456f3f0116c3c77
[master 5dd0694] net-fixes: flow_dissector: prevent an infinite loop (CVE-2013-4348)
Author: Eric Dumazet <[email protected]>
1 file changed, 3 insertions(+), 1 deletion(-)
if you get an error like this
Code:
[email protected]:~/kernel$ git cherry-pick 63ee35463ea3ec5d4e8f2c60ad0f70abd8463733
error: could not apply 63ee354... ARM: 7809/1: perf: fix event validation for software group leaders
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add <paths>' or 'git rm <paths>'
hint: and commit the result with 'git commit'
thats mean it is not applied to your files. just type "git status" to see what files are not modified.
then type: git reset --hard for go to your last commit.
this will make changes of error commit back.
Work always with git because with this way you can save a lot your changes and you can restore anything anytime.
Credits:
XDA Community
Christopher83 for toolchain
ktoonsez for build scripts
arco68 for s4 mini kernel development
cyanogenmod

I really appreciate these posts! :good:

wonderful. thank you very much :good:

Srry wrong topik..

I have built your kernel successfully, but after flashing the .zip the device is stuck on the "Samsung Galaxy S4mini" Bootscreen.
I tested it with the this two roms:
- cm-10.2-20131102-SNAPSHOT-M1-serranoltexx
- CARBON-JB-UNOFFICIAL-20131026-1327-serranoltexx
Do you have any idea why it's not working?
Edit: I used arcos source and it is working fine now

@junkyde
Can't get the stock kartal kernel to build.
What for OS are you running in your virtual box? ubuntu? 86x or 64x?
Did you install any other buildtools?

there isn't a stock kartal kernel. kartal kernel is aosp. I am using Linux Mint 15 in a 64bit version on Virtual Box.
Ps: I had also my troubles with ubuntu x86 and x64, thats why I switched.

junkyde said:
there isn't a stock kartal kernel. kartal kernel is aosp. I am using Linux Mint 15 in a 64bit version on Virtual Box.
Ps: I had also my troubles with ubuntu x86 and x64, thats why I switched.
Click to expand...
Click to collapse
Thanks for you reply!
With "stock" I meant: without changing anything....
I will try mint 15 64bit with xfce!

you can also take a look into this tutorial: http://forum.xda-developers.com/showthread.php?t=1748297

junkyde said:
you can also take a look into this tutorial: http://forum.xda-developers.com/showthread.php?t=1748297
Click to expand...
Click to collapse
Got it working under Ubuntu 12.04 64bit.
Had some troubles because mkboofs and mkbootimg could not be found.
After installing : "sudo apt-get install ia32-libs" everything was fine
Now I will try to compile the 10,1 kernel from source, lets see how that goes..

Keon91 said:
After installing : "sudo apt-get install ia32-libs" everything was fine.
Click to expand...
Click to collapse
Yes I know, that this is required, when you are working with a 64bit system. But I couldn't get this installed in Ubuntu. On Mint everything worked fine. But I am glad you made it

@junkyde
After some trial and error I've succesfully compiled the cm 10.1 kernel.
Can you give me any direction on how to compile the custom liblights?
Do I need to download the full cm 10.1 source?

I used proxusers tutorial on how to build carbon rom. Downloaded full rom, modified lights.c and compiled whole rom.

Can someone build a kernel for the i257m
It would be nice if there was some kernel mods for this. especially just a near stock one with insecure root permissions.
The source is out if anyone was wondering
opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=i257

IF YOU WANT add new changes from CM or other kernel to your kernel ...
Click to expand...
Click to collapse
What do you mean by this? Add changes that cm has done after you last downloaded them or changes you want to do to customize the kernel?
git cherry-pick 2108e6c3109ae126590a81876145a1f17d6771b5
Click to expand...
Click to collapse
What does this means and where do you get that ID? I would think that after fetching the changes from the source it will have been added to all the files you have already downloaded. Thanks for the tutorial!
---------- Post added at 05:58 PM ---------- Previous post was at 05:55 PM ----------
junkyde said:
I used proxusers tutorial on how to build carbon rom. Downloaded full rom, modified lights.c and compiled whole rom.
Click to expand...
Click to collapse
junkyde here you don't mention lights.c, aren't they needed for 10.1? http://forum.xda-developers.com/showpost.php?p=49958578&postcount=215

yes you need custom liblights for BLN, but since I have compiled them already, you can use the one from inside the .zip of my kernel.

junkyde said:
yes you need custom liblights for BLN, but since I have compiled them already, you can use the one from inside the .zip of my kernel.
Click to expand...
Click to collapse
Doesn't it matter that you compiled it for 10.2? Also, where is the source for liblights?

proxuser said:
Welcome to Kernel build guide.
WITH THIS METHOD YOU WILL GET installable zip for your kernel.
Click to expand...
Click to collapse
On ubuntu I got this message after the process took a while:
KERNEL DID NOT BUILD! no zImage exist
Click to expand...
Click to collapse
At some point in the process it printed:
[email protected]:~/Development/SGS4Mini/build-s4-mini-kernel/android_kernel_samsung_msm8930-common$ ./build_all.sh
...
...
...
rm: cannot remove `/home/rpgdev/Development/SGS4Mini/build-s4-mini-kernel/Packages/AOSP/zImage': No such file or directory
rm: cannot remove `arch/arm/boot/zImage': No such file or directory
Make the kernel
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/zconf.lex.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
***
*** Can't find default configuration "arch/arm/configs/kartal_defconfig"!
***
...
...
...
Click to expand...
Click to collapse
And if I go there I indeed can't find the zImage, where can I get it?
PS: Used the characters "..." to denote abridgment of the compilation verbose printout.
Forgot to add, I'm downloaded the cyanogenmod kernel from build 10.1 since that's the cyanogenmod version I use and for the one I need to make this mod, could this be the cause of the problem? Googling it seems that the kernel version you use may need a specific toolchain version.

rpgdev said:
Doesn't it matter that you compiled it for 10.2? Also, where is the source for liblights?
Click to expand...
Click to collapse
I think it doesn't matter, I used the same for different roms and it worked. Source is as I said the lights.c file inside of the rom.
rpgdev said:
Can't find default configuration "arch/arm/configs/kartal_defconfig"!
Click to expand...
Click to collapse
This is why zImage can't be build.

junkyde said:
I think it doesn't matter, I used the same for different roms and it worked. Source is as I said the lights.c file inside of the rom.
This is why zImage can't be build.
Click to expand...
Click to collapse
I'm not using kartal but the one downloaded from cm. Thought the instructions were generic and the script took into account wether you had downloaded the kernel from cm or kartal :/, I did go inside the directory with all the defconfig files, how do I know which one should I point it to on cm-10.1 kernel?
Regarding the lights.c then I just have to include that library on the same directory you put it in your kernel AND add the changes you pointed to here http://forum.xda-developers.com/showpost.php?p=49958578&postcount=215 and I would be set?
Thanks!

[CyanogenMod] Need help!

Hi guy's!
I am BlackFoxy, and i start make sources for ASUS Zenfone 2 Laser
But i need help
If you can, please help me
I in Facebook - https://www.facebook.com/misha.scvorzov
Device sources and more you can see on my GitHub Profile - https://github.com/BlackFoxy757

M here !
Love to help @Shanmugam k @Sujeet Ranipa

What exactly do you need help with?

hardslog said:
What exactly do you need help with?
Click to expand...
Click to collapse
Help with make kernel and correct device and vendor tree

BlackFoxy757 said:
Help with make kernel and correct device and vendor tree
Click to expand...
Click to collapse
Ok I'll give you a little information
1) There is a very highly likely chance that the laser-auto-focus will not work. Of course we don't know until we try but I am not confident because getting things like that which are not in common android source code is very difficult to get working.
2) There are many versions of the ZF2 laser, some come with different kernels therefore will need sources for each kernel (potentially). They also might share the same source (won't know unless I take a good look at it)
3) I am downloading the Kernel source for the ZE551KL and will upload it to github for a starting point. You can easily fork it from there into your github repo. It should be up in a day or less. By the looks of your github repo, you have a different model (one with a 410 snapdragon). Kernel sources are available from the asus.com website under support. You can download it from there for now and I can show you how to upload it to github.
4) If you plan on supporting all the ZF2 laser models, I would suggest for the device repos to make a "common" repo as they will share a lot of the same code, then have separate repos for each model for all the unique characteristics of them.
Edit: kernel uploading to my github. Internet is slow but you can see it soon by going to https://github.com/Hardslog/android_kernel_asus_zf2l

hardslog said:
Ok I'll give you a little information
1) There is a very highly likely chance that the laser-auto-focus will not work. Of course we don't know until we try but I am not confident because getting things like that which are not in common android source code is very difficult to get working.
2) There are many versions of the ZF2 laser, some come with different kernels therefore will need sources for each kernel (potentially). They also might share the same source (won't know unless I take a good look at it)
3) I am downloading the Kernel source for the ZE551KL and will upload it to github for a starting point. You can easily fork it from there into your github repo. It should be up in a day or less. By the looks of your github repo, you have a different model (one with a 410 snapdragon). Kernel sources are available from the asus.com website under support. You can download it from there for now and I can show you how to upload it to github.
4) If you plan on supporting all the ZF2 laser models, I would suggest for the device repos to make a "common" repo as they will share a lot of the same code, then have separate repos for each model for all the unique characteristics of them.
Edit: kernel uploading to my github. Internet is slow but you can see it soon by going to https://github.com/Hardslog/android_kernel_asus_zf2l
Click to expand...
Click to collapse
Yes. I think supported all Z2L

Thank you... we are waiting for you

How is it going?

do you can please creat a custom rom for ze500kl

BlackFoxy757 said:
Yes. I think supported all Z2L
Click to expand...
Click to collapse
There is already a custom ROM for Z00T and Z00L, and I think you should make one for a device that don't have it. Like Z00ED. Also I think you need to have the device so you can test it. No one likes broken ROMs

But.... Why u need make source for zen 2 laser?
Cyanogen have source for this.... And some device already custom.... Only ze500kl don't have.... But i think can use source of msm8916-common !

Sources

I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
If you are eager to Void your Warranty please Mind and Acknowledge that every modification only affects you and your contract and noone else.
custom rom
http://forum.xda-developers.com/xperia-xa/development/f3112-f3116-cyanogemod-13-project-t3488890

Silversniper said:
I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
Click to expand...
Click to collapse
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...

rrvuhpg said:
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...
Click to expand...
Click to collapse
Don't need to hesitate. I'll try to put the directions I've gathered here up today so it is done.

I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom

rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
cool.. if work I would like to have it on my f3111 !!

rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.

Silversniper said:
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.
Click to expand...
Click to collapse
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone

rrvuhpg said:
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone
Click to expand...
Click to collapse
good work , but I am noob to create rom with kitchen .. only zip edit I know

Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good

rrvuhpg said:
Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good
Click to expand...
Click to collapse
Love you!
I will buy this phone thanks to you :highfive:

Thank you for your work on our phone, it's very cool.
I would have helped if i could develop myself. If you need help get in touch with me i know some great devs who could maybe help you

any news @rrvuhpg ?

Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.

rrvuhpg said:
Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.
Click to expand...
Click to collapse
sorry first time I use sony ... I wish you to have nice holiday !

[ROM][XT16xx][7.1.0][CyanMod 14.1 [MotoG4 / G4 Plus] - Where are the BSP files?

Hello again,
Again I post here because I am denied posting in the correct spot. I suppose this silly denial will end, eventually.
I have a question for @Silesh.Nair :
In the dev thread, you tell somebody that he can build CM14.1 from source himself, using that guide:
http://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
In a further post, you seem to indicate that the Moto G4 Plus build is obtained direct from the CM source repo.
I found that github repo for CM on the moto G4: https://github.com/CyanogenMod/android_device_motorola_athene
Unfortunately, the latest tag is marked CM 13 ... and there is nowhere to find the BSP files for CM 14.1.
Now, since it seems quite evident to you, but not at all for me, could you please kindly tell us where we can obtain the BSP files (device tree, vendor, kernel) for CM14.1 - Athene?
Thank you for your understanding my confusion.

You cannot post on a dev forum till you get to 10 posts.
You obviously cannot build cm14.1 using the device tree in cm github.
You have to sync the sources and add your device, vendor and kernel repos from here in your local manifest file.

Thank you
Silesh.Nair said:
You cannot post on a dev forum till you get to 10 posts.
You obviously cannot build cm14.1 using the device tree in cm github.
You have to sync the sources and add your device, vendor and kernel repos from here in your local manifest file.
Click to expand...
Click to collapse
Thank you for this snippet of information. I will look further into it.
In the world of embedded systems, when you have a generic operating system that can be used with many different hardware targets, a Board Support Package ("BSP") is the set of files that are required to build the generic OS on a specific target. For example here the BSP is all the files that are specific for the Moto G4/Plus (e.g. device tree, vendor, kernel), once you have a generic CM 14.1 distribution to start with. "BSP" refers to all the target-specific files that would not be the same on another target (i.e. a different phone).
I think this nomenclature is quite appropriate for the subject at hand.

Building ROM from source

I want to build a custom ROM (CosmicOS) for my device (ZenFone Selfie, Z00UD, supports all Z00T roms).
I've already found a proper device tree, but I'm unsure about kernel and vendor trees I'm about to use.
Kernel:
https://github.com/LineageOS/android_kernel_asus_msm8916
Vendor:
https://github.com/TheMuppets/proprietary_vendor_asus
Am I using proper kernel and vendor trees?
The reason why am I asking this question is because I couldn't find a kernel tree for my processor (MSM8939) in Lineage OS' github and Asus' vendor's proprietary has no Z00T subfile.

you need proper device trees...send me the link for device trees and is your phone has any current rom supported...if yes paste a link

govind1233 said:
you need proper device trees...send me the link for device trees and is your phone has any current rom supported...if yes paste a link
Click to expand...
Click to collapse
Device tree:
https://github.com/LineageOS/android_device_asus_Z00T
Supported ROMs:
https://forum.xda-developers.com/zenfone-2-laser/orig-development/rom-cyanogenmod-14-0-t3459745
https://forum.xda-developers.com/zenfone-2-laser/development/rom-resurrection-remix-n-t3509698
https://forum.xda-developers.com/zenfone-2-laser/development/rom-viper-os-v2-1-t3640026
There are even more of them, of course
As I said before, my phone (ZenFone Selfie, Z00UD) supports all ROMs that support Z00T variant of device (ZenFone 2 Laser)
Also, a source code of ROM I want to build:
https://github.com/Cosmic-OS

Take the same kernel as the devs use to build for Z00T and vendor of Asus from Muppets...it will be no problem if it won't vendor of Z00T...and also include the common trees of ur device...while building...and for vendor just create a file named vendorsetup.sh in ur device trees...

govind1233 said:
Take the same kernel as the devs use to build for Z00T and vendor of Asus from Muppets...it will be no problem if it won't vendor of Z00T...and also include the common trees of ur device...while building...and for vendor just create a file named vendorsetup.sh in ur device trees...
Click to expand...
Click to collapse
So you say that the kernel tree I've included in this thread is proper one, right? Or should I download the one from ASUS?

Yes...and try including common trees also

govind1233 said:
Yes...and try including common trees also
Click to expand...
Click to collapse
This?
https://github.com/LineageOS/android_device_asus_msm8916-common

darkeyes22 said:
This?
https://github.com/LineageOS/android_device_asus_msm8916-common
Click to expand...
Click to collapse
Yes

govind1233 said:
Yes
Click to expand...
Click to collapse
Thank you

Now this:
https://pastebin.com/Nc4yzCNi
Any suggestions?