Database Info

[Guide]How to download/compile specific ROM parts

This is a tutorial about how to download and compile specific parts in aosp based roms (such as CM10)
Written for AOSP noobs like me a year ago.
Note: I wrote this tutorial actually for my blog, as a beginners repo/compile tut, but why not share here
Introduction:
Downloading rom sources is done with the tool “repo”, this is the most awesome downloader in existence. Not only it looks very cool, it also reaches top speed at all times. But it’s only for linux (which is good since when you are busy with aosp roms you should be on linux)
Why is it awesome? Since you decide yourself how many jobs (aka connections) you make with the server. This means you always will get top speed, there is probably no faster download method available on the Internet (except for speedtests, but they don’t count). Next to the downloading of specific parts it’s of course also handy to know how to actually compile them.
Download:
The easiest way of fetching for example a batch of AOSP apps is like this:
1. Choose the desired tag you want to use, in the example I will use android-4.2.2_r1
2. Now make a dir somewhere:
Code:
- mkdir ~/aosp-apps
- cd ~/aosp-apps
3. Download repo when not installed yet:
Code:
- curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
- chmod a+x ~/bin/repo
4. Enter the line that will download the initial manifest.
for AOSP:
Code:
- repo init -u https://android.googlesource.com/platform/manifest -b android-4.2.2_r1
Enter your name and email address and wait until it completes
for CM
Code:
- repo init -u https://github.com/Cyanogenmod/android -b cm-10.1
5. Go in the hidden “.repo” dir and change the manifest
Code:
- cd .repo
- gedit manifest.xml (if you don’t have decent text editor such as “gedit”, install it! “sudo apt-get install gedit”
)
For example when you only want to download the apps, just remove all lines that are not app related. simple as that:
Code:
<?xml version=”1.0″ encoding=”UTF-8″?>
<manifest>
<remote name=”aosp”
fetch=”..” />
<default revision=”refs/tags/android-4.2.2_r1″
remote=”aosp”
sync-j=”4″ />
<project path=”packages/apps/BasicSmsReceiver” name=”platform/packages/apps/BasicSmsReceiver” />
<project path=”packages/apps/Bluetooth” name=”platform/packages/apps/Bluetooth” />
<project path=”packages/apps/Browser” name=”platform/packages/apps/Browser” />
<project path=”packages/apps/Calculator” name=”platform/packages/apps/Calculator” />
<project path=”packages/apps/Calendar” name=”platform/packages/apps/Calendar” />
<project path=”packages/apps/Camera” name=”platform/packages/apps/Camera” />
<project path=”packages/apps/CellBroadcastReceiver” name=”platform/packages/apps/CellBroadcastReceiver” />
<project path=”packages/apps/CertInstaller” name=”platform/packages/apps/CertInstaller” />
<project path=”packages/apps/Contacts” name=”platform/packages/apps/Contacts” />
<project path=”packages/apps/DeskClock” name=”platform/packages/apps/DeskClock” />
<project path=”packages/apps/Email” name=”platform/packages/apps/Email” />
<project path=”packages/apps/Exchange” name=”platform/packages/apps/Exchange” />
<project path=”packages/apps/Gallery” name=”platform/packages/apps/Gallery” />
<project path=”packages/apps/Gallery2″ name=”platform/packages/apps/Gallery2″ />
<project path=”packages/apps/HTMLViewer” name=”platform/packages/apps/HTMLViewer” />
<project path=”packages/apps/KeyChain” name=”platform/packages/apps/KeyChain” />
<project path=”packages/apps/Launcher2″ name=”platform/packages/apps/Launcher2″ />
<project path=”packages/apps/LegacyCamera” name=”platform/packages/apps/LegacyCamera” />
<project path=”packages/apps/Mms” name=”platform/packages/apps/Mms” />
<project path=”packages/apps/Music” name=”platform/packages/apps/Music” />
<project path=”packages/apps/MusicFX” name=”platform/packages/apps/MusicFX” />
<project path=”packages/apps/Nfc” name=”platform/packages/apps/Nfc” />
<project path=”packages/apps/PackageInstaller” name=”platform/packages/apps/PackageInstaller” />
<project path=”packages/apps/Phone” name=”platform/packages/apps/Phone” />
<project path=”packages/apps/Protips” name=”platform/packages/apps/Protips” />
<project path=”packages/apps/Provision” name=”platform/packages/apps/Provision” />
<project path=”packages/apps/QuickSearchBox” name=”platform/packages/apps/QuickSearchBox” />
<project path=”packages/apps/Settings” name=”platform/packages/apps/Settings” />
<project path=”packages/apps/SoundRecorder” name=”platform/packages/apps/SoundRecorder” />
<project path=”packages/apps/SpareParts” name=”platform/packages/apps/SpareParts” />
<project path=”packages/apps/SpeechRecorder” name=”platform/packages/apps/SpeechRecorder” />
<project path=”packages/apps/Stk” name=”platform/packages/apps/Stk” />
<project path=”packages/apps/Tag” name=”platform/packages/apps/Tag” />
<project path=”packages/apps/VideoEditor” name=”platform/packages/apps/VideoEditor” />
<project path=”packages/apps/VoiceDialer” name=”platform/packages/apps/VoiceDialer” />
</manifest>
When done, save it and go a dir back in the terminal
Code:
- cd ..
6. Download the packages
Code:
- repo sync -j16 (-j16 stands for 16 jobs max. This is for around a 100mbit line)
(With my 60mb/s connection I get max speed 7.2mb/s at -j8)
The packages will be download as quickly as possible to your harddrive now.
Compile:
To compile the obtained packages separately you will need a AOSP environment (or CM/AOKP etc). When you have a succesfull environment which is able to compile for your device you may enter:
Code:
- source build/envsetup.sh
- lunch (now choose your device, for example, full_ariesve-userdebug)
- now you’re theoretically ready to compile
to compile an app on the easiest way:
Code:
- make Appname -j8
where “Appname” is the name of the folder placed in packages/apps/..
This also counts for “SystemUI” which is not in that folder.
Code:
- make Calculator -j8 (for example)
And the -j param again stands for the number of jobs, remember that this is compiling and not downloading, so the “standard rule” with this is, number of cores of your CPU + 1.
Which makes a regular quad core (-j5) but makes a i7 CPU with Hyper threading (-j9). When using -j16 for example there could be moments that your cpu will be overloaded so much that your mouse will lag all over the place.
(Linux forces the cpu to perform higher then it actually should, resulting in a very strange fan sound in my case)
When having trouble, when it stops or just nags about some useless stuff.
You should try using the “-k” param, this tells the make command to keep going when a non-critical error occurs.
Code:
- make Calculator -k -j8
When having issues with the local module tags, you should enter this:
Code:
- make Calculator -k LOCAL_MODULE_TAGS=optional -j8
To compile other parts you also need to enter the folder name, here are some examples from /frameworks/base
Code:
- make policy (the power menu and lockscreen)
- make framework (the initial framework files)
- make framework-res (the initial framework resources)
- make services (the services.jar file)
or more examples:
Code:
- make sdk (builds the android sdk)
- make modules (builds all modules)
- make installclean (removes all staging directories, such as out/target/product/boardname/system)
- make clean (removes the whole /out directory)
:silly:

Good Job
this isnt so bad I will be giving your guide to people from my community who want to compile.
only problem is the cm branch you put jellybean you should put cm-10.1 if you are using googles 4.2.2 source
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1

Unjustified Dev said:
this isnt so bad I will be giving your guide to people from my community who want to compile.
only problem is the cm branch you put jellybean you should put cm-10.1 if you are using googles 4.2.2 source
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
Click to expand...
Click to collapse
Thanks for mentioning

broodplank1337 said:
Thanks for mentioning
Click to expand...
Click to collapse
Can you teach me everything you know
Do you know how to cherry Pick? I need help merging it when it conflicts other strings
I want to learn everything im only 15 and I have time to learn now.
I plan on eventually building my own rom based off aosp here's my github
https://github.com/TeamRegular
I took a look at your projects and tutorials you are awesome.

This looks like a great tutorial :good: and when I saw it I thought it might answer a question I've been thinking about for a while now: would it be possible to compile Pie controls from Paranoid Android into one independent app?
I'm a n00b at compiling anything, I've attempted (and failed) to compile a kernel, so could you give me some direction on how air would do this? Thanks :laugh:

[GUIDE]Building any ROM from source for HTC One S aka ville!

Do you know about a ROM that it's not builded for our beloved One S? Do you want to port it for our device? This easy guide will help you.
Requirements:
A One S.
A relatively recent computer (Linux, OS X, or Windows) w/a reasonable amount of RAM and about 35 GB of free storage. The less RAM you have, the longer the build will take. Using SSDs results in faster builds than traditional hard drives.
A micro USB cable.
A decent Internet connection & reliable electricity
Some familiarity with basic Android operation and terminology. It would help if you’ve installed custom roms on other devices and are familiar with what a recovery image such as ClockworkMod is, for example. It may also be useful to know some basic command line concepts such as cd for “change directory”, the concept of directory hierarchies, that in Linux they are separated by /, etc.
​HERE IS THE GUIDE.
Installing Build Packages
Open the terminal and type: (for 64-bit&32-bit)
Code:
sudo apt-get install bison build-essential curl flex git-core gnupg gperf libesd0-dev libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop openjdk-6-jdk openjdk-6-jre pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev
In addition to the above, for 64-bit systems:
Code:
sudo apt-get install g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev
Creating Directories
In order to start building ROMs you'll need to create some directories
Code:
mkdir -p ~/bin
mkdir -p ~/yourworkingdirectory
Installing the REPO command
Enter the following to download the "repo" binary:
Code:
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
Now lets give this the proper permissions to make it runnable:
Code:
chmod a+x ~/bin/repo
Put the ~/bin directory in your path of execution
Make sure that the ~/bin directory you just created is in your path of execution so that you can easily run the repo command even when you're not in ~/bin.
Code:
export PATH=${PATH}:~/bin
Initialize the source repository
Code:
cd yourworkingdirectory
Now you'll need the repo init related to the rom you'd like to build. Here i will insert some of the I used. Anyway to find this you can go the rom's github and search for the manifest (android or platform-manifest).Just choose the right branch.
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
repo init -u git://github.com/LiquidSmooth/android.git -b kitkat
repo init -u git://github.com/SlimRoms/platform_manifest.git -b kk4.4-caf
Download the source code
This will download all the source code to your computer.Prepare to wait a long time while the source code downloads.
Code:
repo sync
Download device,kernel and vendor tree for Liquid
We will use CM ones. Thanks a lot.
Basically we need to add some projects to the download list. To do this we'll need a local_manifest.
Go in the .repo folder in your working directory(it's an hidden folder press ctrl+h). Create a new folder called "local manifests" then double click on it. Now you'll have to create a roomservice.xml file for the most of the ROMs and a slim_manifest.xml for SlimRoms, it's the same thing just the name it's different.
Open this file and paste this inside:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github"
fetch="git://github.com/" />
<project name="CyanogenMod/android_device_htc_ville" path="device/htc/ville" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_htc_s4-common" path="device/htc/s4-common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_htc_msm8960-common" path="device/htc/msm8960-common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_kernel_htc_msm8960" path="kernel/htc/msm8960" remote="github" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-11.0" />
</manifest>
Now give another:
Code:
repo sync
and wait.
Do some modifications to the .mk files
Since we are using CM device tree we need to modify them for the choosen ROM.
Go into the device folder(device/htc/ville) and do some modifications. I will explain you what i mean using LiquidSmooth as example.
1) Create a new file called vendorsetup.sh . Open it and inside you'll have to write a script to add it to the lunch list.
Code:
add_lunch_combo liquid_ville-userdebug
You can choose if you want an userdebug version of the rom or an eng one just by writing eng instead of userdebug.
2) Now rename cm.mk into liquid.mk(for other ROMs this file should be renamed in a different way. Use an existing device tree to see the correct naming.)
3) Open the .mk file. You'll find something like this:
Code:
# Release name
PRODUCT_RELEASE_NAME := ville
# Boot animation
TARGET_SCREEN_HEIGHT := 960
TARGET_SCREEN_WIDTH := 540
# Inherit some common CM stuff.
$(call inherit-product, vendor/cm/config/common_full_phone.mk)
# Inherit device configuration
$(call inherit-product, device/htc/ville/device_ville.mk)
# Device naming
PRODUCT_DEVICE := ville
PRODUCT_NAME := cm_ville
PRODUCT_BRAND := htc
PRODUCT_MODEL := One S
PRODUCT_MANUFACTURER := HTC
# Set build fingerprint / ID / Product Name ect.
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=htc_ville BUILD_FINGERPRINT=htc_europe/ville/ville:4.1.1/JRO03C/128506.8:user/release-keys PRIVATE_BUILD
You need to modify some things to make it buildable:
Code:
# Inherit some common CM stuff.
$(call inherit-product, vendor/cm/config/common_full_phone.mk)
becomes:
Code:
# Inherit some common LiquidSmooth stuff.
$(call inherit-product, vendor/liquid/config/common_phone.mk)
To understand the changes you'll have to go in the vendor folder searching the rom specific vendor and open the config folder to see what .mk file you need.You need to use your brain to understand what you should write instead of cm every ROM has different naming conventions.
This:
Code:
PRODUCT_NAME := cm_ville
becomes:
Code:
PRODUCT_NAME := liquid_ville
4) Now rename cm.dependencies in liquid.dependencies(SlimRoms does not require this step for unsupported devices.)
Start the build
Code:
source build/envsetup.sh
If you created the vendorsetup.sh in the right way you will read the ville folder.
Code:
lunch
Now you have to choose the number near the ville in the list of the supported devices.
If you have done all in the correct way in your terminal you'll see a page like this:
View attachment 2470228
Build
After lunching you have to start the build using the right command:
For liquid:
Code:
time mka liquid
For others:
Code:
make bacon
make
brunch devicename
Wait some time till the build ends hopefully with no errors.​
Now You could think that i forgot you hboot 2.16 users.But this is not true. This is a cherry-pick that let you build every rom for 2.16 hboot.
Code:
cd device/htc/ville
git fetch http://review.cyanogenmod.org/CyanogenMod/android_device_htc_ville refs/changes/47/53647/9 && git cherry-pick FETCH_HEAD
Since you have no 4.4 recovery you'll need this other step:
Code:
Flashable via normal TWRP
add this line
SKIP_SET_METADATA := true
in device/htc/s4-common/BoardConfigCommon.mk
cherry-pick i think.
Code:
cd workingdirectory/build
git fetch http://review.cyanogenmod.org/CyanogenMod/android_build refs/changes/59/53559/6 && git cherry-pick FETCH_HEAD
​
Credits: http://wiki.cyanogenmod.org/w/Build_for_ville
and all the experience i got in this 2 months of building.

For most ROMS you'll have some overlays errors.
Just go in the overlay folder linked in the error and open config.xml. Just delete the lines in the error or search in the folder history the commit that you have to revert.
To revert a commit:
Code:
cd intheinteressedfolder
git revert thenumberofthecommit
Here is a screenshot of the what the number/name of the commit is:
View attachment 2470242

it might be a stupid question: so i dont need any programing skills?

Hai96 said:
it might be a stupid question: so i dont need any programing skills?
Click to expand...
Click to collapse
For building from source nope

phoenixita said:
For building from source nope
Click to expand...
Click to collapse
Ok, then I will test your Guide

Hai96 said:
Ok, then I will test your Guide
Click to expand...
Click to collapse
Added some lines in purple for 2.16 users.

@phoenixita Iam stucking at the point of doing modifications to the mk. files, i dont have a ville folder in my device folder...
View attachment 2471072

Hai96 said:
@phoenixita Iam stucking at the point of doing modifications to the mk. files, i dont have a ville folder in my device folder...
View attachment 2471072
Click to expand...
Click to collapse
Download device,kernel and vendor tree for Liquid
We will use CM ones. Thanks a lot.
Basically we need to add some projects to the download list. To do this we'll need a local_manifest.
Go in the .repo folder in your working directory(it's an hidden folder press ctrl+h). Create a new folder called "local manifests" then double click on it. Now you'll have to create a roomservice.xml file for the most of the ROMs and a slim_manifest.xml for SlimRoms, it's the same thing just the name it's different.
Open this file and paste this inside:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github"
fetch="git://github.com/" />
<project name="CyanogenMod/android_device_htc_ville" path="device/htc/ville" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_htc_s4-common" path="device/htc/s4-common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_htc_msm8960-common" path="device/htc/msm8960-common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_kernel_htc_msm8960" path="kernel/htc/msm8960" remote="github" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-11.0" />
</manifest>
Now give another:
Code:
repo sync
and wait.

@phoenixita I had followed your guide and now I have the 3.0 liquid smooth build and it boots.
But the build process was very slow, my computer needed 4 hours to build this. Does it need only at the first building process so long or it's my computer ?
If I want to build paranoid android, what do I need to change?

Hai96 said:
@phoenixita I had followed your guide and now I have the 3.0 liquid smooth build and it boots.
But the build process was very slow, my computer needed 4 hours to build this. Does it need only at the first building process so long or it's my computer ?
If I want to build paranoid android, what do I need to change?
Click to expand...
Click to collapse
Paranoid android it's a different thing anyway rmbq has written a guide for porting PA.
4 hours it's okay...

i have another question
When I want to build AOKP,Slim Rom,... I need to create for every Rom a new working directory and download Repositorys,or?

Hai96 said:
i have another question
When I want to build AOKP,Slim Rom,... I need to create for every Rom a new working directory and download Repositorys,or?
Click to expand...
Click to collapse
Yes you need to download each source for each ROM you want to build in its own directory
---------- Post added at 09:02 PM ---------- Previous post was at 08:48 PM ----------
Hai96 said:
@phoenixita I had followed your guide and now I have the 3.0 liquid smooth build and it boots.
But the build process was very slow, my computer needed 4 hours to build this. Does it need only at the first building process so long or it's my computer ?
If I want to build paranoid android, what do I need to change?
Click to expand...
Click to collapse
Google how to set up ccache. It will reduce the time of the builds after you first initial build using it

phoenixita said:
Download device,kernel and vendor tree for Liquid
We will use CM ones. Thanks a lot.
Basically we need to add some projects to the download list. To do this we'll need a local_manifest.
Go in the .repo folder in your working directory(it's an hidden folder press ctrl+h). Create a new folder called "local manifests" then double click on it. Now you'll have to create a roomservice.xml file for the most of the ROMs and a slim_manifest.xml for SlimRoms, it's the same thing just the name it's different.
Open this file and paste this inside:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github"
fetch="git://github.com/" />
<project name="CyanogenMod/android_device_htc_ville" path="device/htc/ville" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_htc_s4-common" path="device/htc/s4-common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_htc_msm8960-common" path="device/htc/msm8960-common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_kernel_htc_msm8960" path="kernel/htc/msm8960" remote="github" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-11.0" />
</manifest>
Now give another:
Code:
repo sync
and wait.
Click to expand...
Click to collapse
Can you incorporate the above instructions in the OP? You did lose me a bit.
Thanks for the guide perhaps a sticky?

ttaidapos said:
Can you incorporate the above instructions in the OP? You did lose me a bit.
Thanks for the guide perhaps a sticky?
Click to expand...
Click to collapse
they are in the OP...I've copied them........................................................

I want to build omni Rom for the One S but i get big Error after the lunch command...
Do you know what iam doing wrong?
View attachment 2474393

Hai96 said:
I want to build omni Rom for the One S but i get big Error after the lunch command...
Do you know what iam doing wrong?
View attachment 2474393
Click to expand...
Click to collapse
Have you renamed cm.mk in omni.Mk? And have you done the right chsnges?

phoenixita said:
Have you renamed cm.mk in omni.Mk? And have you done the right chsnges?
Click to expand...
Click to collapse
Yes I have renamed the .Mk files....
What do you mean with changes?
I have changed all the things from liquid to Omni
Gesendet von meinem HTC One S

Hai96 said:
Yes I have renamed the .Mk files....
What do you mean with changes?
I have changed all the things from liquid to Omni
Gesendet von meinem HTC One S
Click to expand...
Click to collapse
If you are just starting to build. Pick a different ROM than omni. It has a few more changes that needs made than the ones in this guide. And it will error with invalid integers which will be difficult for a new builder to fix.

WhiTeRhiNo said:
If you are just starting to build. Pick a different ROM than omni. It has a few more changes that needs made than the ones in this guide. And it will error with invalid integers which will be difficult for a new builder to fix.
Click to expand...
Click to collapse
I will give omni a try!

WhiTeRhiNo said:
If you are just starting to build. Pick a different ROM than omni. It has a few more changes that needs made than the ones in this guide. And it will error with invalid integers which will be difficult for a new builder to fix.
Click to expand...
Click to collapse
Can you name one Rom that can be build with this guide?

Trying To Build Cm11 For P3100 First Time. Help Needed.

ello,
I am trying to build cm11 using https://github.com/CyanogenMod/android_device_samsung_p3100/tree/cm-11.0
I am running ubuntu 13.10 64 bit server edition and created the folders as below,
[email protected]:~$ tree
.
|-- android
| `-- system
`-- bin
`-- repo
I cd to ~/android/system and I am trying to initiate repo using below command,
Code:
repo init -u git://github.com/CyanogenMod/android_device_samsung_p3100.git -b cm-11.0
getting below error,
Code:
[email protected]:~/android/system$ repo init -u git://github.com/CyanogenMod/android_device_samsung_p3100.git -b cm-11.0
fatal: manifest 'default.xml' not available
fatal: manifest default.xml not found
[email protected]:~/android/system$
Can anyone assist?
Thanks,
Simon Mandy

Wrong repo init command. For your references:
1. Outdated but still useful how to build CyanogenMod for P3100: http://wiki.cyanogenmod.org/w/Build_for_p3100
2. @gr8nole 's personal notes how to build CyanogenMod for Tab 3 8.0: http://forum.xda-developers.com/showpost.php?p=49751306&postcount=578

Use the wiki @ketut.kumajaya linked, i used it when i started compileing
for CM 11 you need to run
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
(wiki needs an update )
After you have synced CM's repo (this will take some time ) you need to create "local_manifest.xml" inside the ".repo" folder (hidden folder, find it "~/android/system/.repo") to sync the vendor-blobs too.
You need this inside:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
</manifest>
if you run "breakfast p3100" this should download all needed repos to build CM.
If not you can use this in your local_manifest.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_p3110" path="device/samsung/p3110" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_p3100" path="device/samsung/p3100" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_p5110" path="device/samsung/p5110" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_p5100" path="device/samsung/p5100" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_kernel_samsung_espresso10" path="kernel/samsung/espresso10" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_omap4-common" path="device/samsung/omap4-common" remote="github" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-11.0" />
</manifest>

Thank you all for helping me out. Now I initated the repo from cm11 folder using below command,
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
But my repo sync get errored as below, (Only the last parts included here. It always end at the same place. I ran so many time)
Code:
Fetching projects: 46% (205/444) Fetching project CyanogenMod/android_external_libnfc-nxp
Fetching project platform/external/marisa-trie
Fetching project platform/prebuilts/gcc/darwin-x86/x86/x86_64-linux-android-4.7
Fetching project CyanogenMod/android_system_vold
Fetching project CyanogenMod/android_external_jmdns
Fetching projects: 47% (209/444) Fetching project device/generic/mini-emulator-armv7-a-neon
Fetching project platform/frameworks/uiautomator
Fetching project platform/external/smack
Fetching project CyanogenMod/android_device_generic_mips
Fetching project CyanogenMod/android_vendor_cm
Fetching projects: 48% (214/444) Fetching project CyanogenMod/android_external_apache-http
Fetching project CyanogenMod/android_packages_providers_ApplicationsProvider
Fetching project CyanogenMod/android_hardware_qcom_audio
Fetching project CyanogenMod/android_hardware_broadcom_wlan
error: Cannot fetch CyanogenMod/android_hardware_qcom_camera
Fetching project CyanogenMod/android_external_zxing
Fetching projects: 49% (218/444)
error: Exited sync due to fetch errors
[email protected]:~/cm11$
Please help me on how to proceed.

delete the folder and try it again on a new created folder

Android-Andi said:
delete the folder and try it again on a new created folder
Click to expand...
Click to collapse
Did you mean delete cm11 folder (where it had already downloaded some 6 GB data) and create another cm11 and do repo init and do repo sync again?
Thanks,
Simon Mandy

if nothing else worked, yes.

[Q]How To Build Ubuntu Touch For S2vep?

Hello mate i am trying to build an image of Ubuntu Touch by following their official guide with the following steps:
Install Required Packages​
Installing required packages between 12.04 and 13.10.
$ sudo dpkg --add-architecture i386
$ sudo apt-get update
Then install packages:
sudo apt-get install git gnupg flex bison gperf build-essential \
zip bzr curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 ubuntu-dev-tools tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386 schedtool bsdiff
Click to expand...
Click to collapse
Install JDK 6​
Type in the terminal the following command to install JDK 6.
sudo apt-get install openjdk-6-jdk
Click to expand...
Click to collapse
Install PPA Tools​
OK we need to install Android PPA Tools and Phablet Tools
To install PPA Tools type in the terminal:
sudo add-apt-repository ppahablet-team/tools
Then add the following command line if you are using 12.04:
sudo add-apt-repository ppa : ubuntu-sdk-team/ppa
To install PPA Tools type:
sudo apt-get update
sudo apt-get install ubuntu-device-flash
To install Phablet Tools:
sudo apt-get install phablet-tools
Click to expand...
Click to collapse
Making Working_Directory​
Now we need to make a directory that should be used to download Ubuntu Touch sources, type in the terminal:
mkdir /root/WORKING_DIRECTORY
Click to expand...
Click to collapse
Download Sources​
Now it's time to get Ubuntu Touch source code that's will take from
1 hour to 3 hours depends from your internet connection's speed
(I have a 8mb dsl and take about 1 hours and 30 minutes so type:
ubuntu-dev-bootstrap -c /root/WORKING_DIRECTORY
Click to expand...
Click to collapse
Enable S2vep​
Our device doesn't has official support to port, so we should create it manually by following this steps:
1-Cd to WORKING_DIRECTORY.
2-Type mkdir .repo/local_manifests/ .
3-create a file called roomservice.xml so type: gedit .repo/local_manifests/roomservice.xml and insert the following elements:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="git://github.com/" name="gh" />
<project name="KINGbabasula/android_kernel_samsung_i9105P" path="kernel/samsung/i9105P" remote="gh" revision="cm-10.1" />
<project name="KINGbabasula/android_device_samsung_s2vep" path="device/samsung/s2vep" remote="gh" revision="cm-10.1" />
</manifest>
4-Type repo sync to download s2vep's source.
Click to expand...
Click to collapse
Extracting Blobs Files​
I can't find extract-files.sh on KINGbabasula's btw you can do it if having one:
1-Type cd device/samsung/s2vep .
2-Run ./extract-files.sh .
P.S. :make sure to have enable debug and accept the connection that appear on your phone.
Click to expand...
Click to collapse
Brunch and Build​
When you are ready type the following command:
make -# otapackage (change # with the numbers of your cores).
P.S: i use this and not brunch because i don't have vendor files.
Click to expand...
Click to collapse
I got this error during compilation by attacched image and my questions are for devs and expert users:
1-Can i use original stock android 4.2.2 vendor?
2-Are my steps is correct to compile Ubuntu Touch?
3-Which sources is recommend to use?
@KINGbabasula @skullface1
thanks for any idea or answer or suggestions that can help me

I hope someone will help you, it would be fantastic if we can get it working

Porting Ubuntu Touch On S2 Plus i9105P
lukypuie said:
I hope someone will help you, it would be fantastic if we can get it working
Click to expand...
Click to collapse
Yeah man i know that, where can i get the vendor of s2 plus?

What do you mean by vendor?

Thanka
SethPDA said:
What do you mean by vendor?
Click to expand...
Click to collapse
I mean about blobs files that we can extract them by extract-file.sh by the way i just compile one for ubuntu touch but i don't think to get booting

Use this manifest, also if you got it working release it :3
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="git://github.com/" name="gh" />
<project name="SamsungBCM-Cyanogenmod/android_kernel_samsung_galaxys2plus-common" path="kernel/samsung/galaxys2plus-common" remote="gh" revision="cm-10.1" />
<project name="SamsungBCM-Cyanogenmod/android_device_samsung_s2vep" path="device/samsung/s2vep" remote="gh" revision="cm-10.1" />
<project name="SamsungBCM-Cyanogenmod/proprietary_vendor_samsung" path="vendor/samsung" remote="gh" revision="cm-11.0" />
</manifest>

Thanks
LuK1337 said:
Use this manifest, also if you got it working release it :3
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="git://github.com/" name="gh" />
<project name="SamsungBCM-Cyanogenmod/android_kernel_samsung_galaxys2plus-common" path="kernel/samsung/galaxys2plus-common" remote="gh" revision="cm-10.1" />
<project name="SamsungBCM-Cyanogenmod/android_device_samsung_s2vep" path="device/samsung/s2vep" remote="gh" revision="cm-10.1" />
<project name="SamsungBCM-Cyanogenmod/proprietary_vendor_samsung" path="vendor/samsung" remote="gh" revision="cm-11.0" />
</manifest>
Click to expand...
Click to collapse
Really? can i use cm-11 and cm-10.1 revisions together? i'll try it later, if get booting i'll release but in Original Android Section? thanks

haky 86 said:
Really? can i use cm-11 and cm-10.1 revisions together? i'll try it later, if get booting i'll release but in Original Android Section? thanks
Click to expand...
Click to collapse
I think you can use cm-11.0 kernel for cm-10.1 too.

Thanks
Ok i build a flashable ubuntu touch for s2 plus using old roomservice.xml but boot stuck on animation then reboot automatically, i try to format cache, my phone shutdown on animation, so i am going to try using your configuration

haky 86 said:
Ok i build a flashable ubuntu touch for s2 plus using old roomservice.xml but boot stuck on animation then reboot automatically, i try to format cache, my phone shutdown on animation, so i am going to try using your configuration
Click to expand...
Click to collapse
Try flash on older bootloader (4.1.2).

Thanks
LuK1337 said:
Try flash on older bootloader (4.1.2).
Click to expand...
Click to collapse
I'll take your option in cosideration because i clean everything and resync again by the way if i repo sync phanlet-saucy should i flash saucy armf too?

haky 86 said:
I'll take your option in cosideration because i clean everything and resync again by the way if i repo sync phanlet-saucy should i flash saucy armf too?
Click to expand...
Click to collapse
I don't really know, but also you will need to fix device tree (WiFi, NFC)

Not only that. You need a new ril etc.
Sent from my GT-I9105P using XDA Premium 4 mobile app

OK
CoolDevelopment said:
Not only that. You need a new ril etc.
Sent from my GT-I9105P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So that should be extracted from phone by extract-files.sh and is that necessary to be cm10.1?

haky 86 said:
So that should be extracted from phone by extract-files.sh and is that necessary to be cm10.1?
Click to expand...
Click to collapse
That needs to be coded
Sent from my GT-I9105P using XDA Premium 4 mobile app

Thanks
CoolDevelopment said:
That needs to be coded
Sent from my GT-I9105P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok i got it, by the here the result of second test :/ and here the actual roomservice.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="KINGbabasula/android_device_samsung_s2vep" path="device/samsung/s2vep" remote="github" revision="cm-10.1" />
<project name="KINGbabasula/android_kernel_samsung_i9105P" path="kernel/samsung/i9105P" remote="github" revision="cm-10.1" />
<project name="CoolDevelopment/proprietary_vendor_samsung" path="vendor/samsung/dlx" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-10.1" />
</manifest>
Click to expand...
Click to collapse

change
Code:
<project name="KINGbabasula/android_kernel_samsung_i9105P" path="kernel/samsung/i9105P" remote="github" revision="cm-10.1" />
to
Code:
<project name="KINGbabasula/android_kernel_samsung_i9105P" path="kernel/samsung/galaxys2plus-common" remote="github" revision="cm-10.1" />

Something new?

Not yet
lukypuie said:
Something new?
Click to expand...
Click to collapse
Nothing new, i have a few questions
-can i extract the boot.img from original firmware?
-is that necessary to edit vendor/cm/vendorsetup.sh by add_lunch_combo $cm_i9105P or cm_s2vep?
i am watching this 2 video to fix bootlop part 1 and part 2.
is still a work in progress

haky 86 said:
Nothing new, i have a few questions
-can i extract the boot.img from original firmware?
-is that necessary to edit vendor/cm/vendorsetup.sh by add_lunch_combo $cm_i9105P or cm_s2vep?
i am watching this 2 video to fix bootlop part 1 and part 2.
is still a work in progress
Click to expand...
Click to collapse
Why you can't compile kernel?
Sent from my GT-I9105P using XDA Premium 4 mobile app

[GUIDE] Build any Custom ROM from Source [Noobfriendly]

I know there are many of these guides on XDA, but when I wanted to learn how to compile ROMs, all those guides didn't help me out cause all those guides are for more advanced users. I will try to explain every step clearly.
Step 1: Prepare your PC for building Android
Here's a good guide how to do that. http://forum.xda-developers.com/showthread.php?t=2639611
Follow this guide up to step 9, then return to this thread.
Step 2: Downloading the sources
First, in terminal type "mkdir <android>" and then "cd <android>". Replace <android> with the ROM name that you want to build. For example if you want to build omni, type "mkdir omni" and "cd omni". Now you created a directory called "omni" and switched to it. Now, pick a ROM that you want to build and go to its github page. Then search for a repository that has the word "manifest" in it (sometimes it's also just called "android"). Click on it. On the top, select the branch. Most times every branch is for a different android version. Select the latest android version (For this guide it's Android 5.1.1, so the branch most times is LP-5.1). Then scroll down to the readme, copy the command starting with "repo init" and paste it in your terminal. Now just type "repo sync" and it will download the sources. This will take time, since it's about 15gb that will be downloaded.
Step 3: Download the Device specific sources
Next, you have to download the device tree, the kernel and the vendor files. If you're lucky, someone already put together a roomservice.xml for your device where all the needed stuff is declared. Search for "<devicename> roomservice" and hopefully you'll find a github page with this file. If you do, download it and push it to <android>/.repo/local_manifests/. Then go back to the terminal and type "repo sync" again. This time it won't take that long. If there's no roomservice.xml for your device, You have to create it. The device tree and kernel most times can be found by going to github.com/CyanogenMod and searching for your brand. For example, if you have a Motorola Moto G 2nd Generation (codename titan), search for motorola and open android_device_motorola_titan (sources for titan), android_device_motorola_msm8226-common (sources for titan's chipset) and android_kernel_motorola_msm8226 (sources for the kernel of the chipset) in a new tab. Also you need the vendor files which can be found at github.com/TheMuppets. For motorola devices, open proprietary_vendor_motorola. Create a new file on your desktop called "roomservice.xml" and open it. Paste this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="" path="" remote="github" revision="cm-12.1" />
<project name="" path="" remote="github" revision="cm-12.1" />
<project name="" path="" remote="github" revision="cm-12.1" />
<project name="" path="" remote="github" revision="cm-12.1" />
</manifest>
Then go back to the github pages, copy the names of the repositorys and paste <project-name-on-github>/<name-of-the-repository> in the quotes after "name=". For titan, it would look like this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_motorola_titan" path="" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_device_motorola_msm8226-common" path="" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_kernel_motorola_msm8226" path="" remote="github" revision="cm-12.1" />
<project name="TheMuppets/proprietary_vendor_motorola" path="" remote="github" revision="cm-12.1" />
</manifest>
Now for the path, just copy the name of the repository, remove "android_" or "proprietary_" and replace each "_" with a "/"
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="android_device_motorola_titan" path="device/motorola/titan" remote="github" revision="cm-12.1" />
<project name="android_device_motorola_msm8226-common" path="device/motorola/msm8226-common" remote="github" revision="cm-12.1" />
<project name="android_kernel_motorola_msm8226" path="kernel/motorola/msm8226" remote="github" revision="cm-12.1" />
<project name="proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="cm-12.1" />
</manifest>
Sometimes you need some more repositorys, for example for titan you also need android_hardware_qcom_fm and android_device_qcom_common. Add them the same way as you added all the other sources. You can find out which repositorys you need by opening cm.dependencies in your decive- and chipset sources.
Now save the file and push it to "<android>/.repo/local_manifests/". Now return to your terminal and type "repo sync" again.
Step 4: Edit the device tree
You have to edit the device tree so that it fits to the ROM that you want to build. Go to <android>/vendor. In there you will find a folder with the abbreviation for the ROM. For example for CarbonROM the abbreviation is carbon, for EuhoriaOS it's eos, for AOKP it's aokp and for CyanogenMod it's cm. Remember this abbreviation. Back in terminal, type "cd device/<brand-you-are-building-for>/<phone-you-are-building-for>/" and then "mv cm.mk <remembered-abbreviation>.mk" and "mv cm.dependencies <remembered-abbreviation>.dependencies". After that, type "nano <remembered-abbreviation>.mk" and replace "cm" with "<remembered-abbreviation>" where ever you see it. To save the file, hit Ctrl+O, then Enter and then Ctrl+X. Now type "cd .." and then "cd <chipset-you-are-building-for>. Now, type "mv cm.dependencies <remembered-abbreviation>.dependencies" again.
Step 5: Building
We finally arrived there! To build our ROM, in terminal type ". build/envsetup.sh" and then "brunch <codename-for-your-device>".
This process takes time, depending on your PC specs. On my PC (2 cores, 3gb RAM), building takes about 8h. On my friends Server (12 cores, 128gb RAM), building takes about 20 mins.
Happy building!
Credits:
@Sarath280 for teaching me how to build ROMs
My dad for teaching me everything else aboout technology
@sylentprofet for the guide how to prepare linux to build Android

@notiflux
Het Max, Amol here. Thank You So Much. Love ya.
Sent from my Moto G 2014 using Tapatalk

Thanks! For this great tutorial! I am testing it right now I had problems making the roomservice.xml but with this tutorial it was very easy .
I am using a china device so not so many ROMs avalible so I am building one myself

Hello @notiflux,
Thanks for the guide,
I have a little issue though,
The thing is that the device that i want to build the rom for(SM-T211) DO NOT have a device tree already built. So I need to make that first. Can you help me with that?

sscsps said:
Hello @notiflux,
Thanks for the guide,
I have a little issue though,
The thing is that the device that i want to build the rom for(SM-T211) DO NOT have a device tree already built. So I need to make that first. Can you help me with that?
Click to expand...
Click to collapse
I'm not really into that kinda stuff since I never worked on such a device, but I know that there are guides here on xda on how to create your own device tree. But I think your device needs to be rooted for that
http://forum.xda-developers.com/showthread.php?t=2010281 you can try this guide. Good luck!

help in source tree
Sir, i downloaded ,android aosp open source tree ,,in desktop directory ,,linux 16:10 ,next i downloaded open source ,,kernal and android files from lg website ,,as i am using lg ,,,in open source lg ,,i got 2 tar files,,1 android ,2nd is kernal tar,,and ine readme.txt i opened it ,,it showing that untar android. tar and merge ,in download.android source tree ,,but where i am not getting ,,please tell me where ,,please sir

I see this thread is from 2015, does the guide work for nougat also?

Any solution for this error?
Code:
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/harshone/android/lineage/out/target/product/m8/obj/KERNEL_OBJ/usr', needed by '/home/harshone/android/lineage/out/target/product/m8/obj/STATIC_LIBRARIES/libsdcard_intermediates/sdcard.o', missing and no known rule to make it
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/harshone/android/lineage'
#### make failed to build some targets (02:30 (mm:ss)) ####

Hi, how do I apply security updates to the source?

HarshOne said:
Any solution for this error?
Code:
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/harshone/android/lineage/out/target/product/m8/obj/KERNEL_OBJ/usr', needed by '/home/harshone/android/lineage/out/target/product/m8/obj/STATIC_LIBRARIES/libsdcard_intermediates/sdcard.o', missing and no known rule to make it
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/harshone/android/lineage'
#### make failed to build some targets (02:30 (mm:ss)) ####
Click to expand...
Click to collapse
It seams you don't have libsdcard folder/file in your device tree.
So try to search and download that file from github.
then copy and paste that file to your device tree

Hello respected developers,
I'm very enthusiastic and inspired by viper os to develop it for my other devices too. But first I tried to build the rom for my redmi 4a because i wanted to test the success of my building. I would like to inform you that i have gone through every process of establishing environment to reposync all learnig from aosp document and manifests on the viper os github and even downloaded device tree,vendor and kernel as from git hub . and i made neccessary edits to androidproducts.mk , lineage_rolex.mk to naming viper_rolex.mk and setting device path.
And finally i proceeded by :
Code:
./build/envsetup.sh
lunch viper_rolex-userdebug
mka poison
The build process then followed for about 5 hrs and i was hopefully waiting close success but alas! I came up with a error given this way:
Warning: Stripped invalid locals information from 2 methods.
In /home/shrawan/Desktop/workon_viper/out/soong/.intermediates/frameworks/base/packages/EasterEgg/EasterEgg/android_common/combined/EasterEgg.jar:kotlin/collections/SlidingWindowKt$windowedIterator$1.class:
Methods with invalid locals information:
java.lang.Object kotlin.collections.SlidingWindowKt$windowedIterator$1.doResume(java.lang.Object, java.lang.Throwable)
In /home/shrawan/Desktop/workon_viper/out/soong/.intermediates/frameworks/base/packages/EasterEgg/EasterEgg/android_common/combined/EasterEgg.jar:kotlin/sequences/SequencesKt___SequencesKt$zipWithNext$2.class:
Methods with invalid locals information:
java.lang.Object kotlin.sequences.SequencesKt___SequencesKt$zipWithNext$2.doResume(java.lang.Object, java.lang.Throwable)
Some warnings are typically a sign of using an outdated Java toolchain. To fix, recompile the source with an updated toolchain.
[ 82% 60970/74331] build /home/shrawan...icy_tests_intermediates/sepolicy_tests
FAILED: /home/shrawan/Desktop/workon_viper/out/target/product/rolex/obj/ETC/sepolicy_tests_intermediates/sepolicy_tests
/bin/bash -c "(/home/shrawan/Desktop/workon_viper/out/host/linux-x86/bin/sepolicy_tests -l /home/shrawan/Desktop/workon_viper/out/host/linux-x86/lib64/libsepolwrap.so -f /home/shrawan/Desktop/workon_viper/out/target/product/rolex/obj/ETC/plat_file_contexts_intermediates/plat_file_contexts -f /home/shrawan/Desktop/workon_viper/out/target/product/rolex/obj/ETC/vendor_file_contexts_intermediates/vendor_file_contexts -p /home/shrawan/Desktop/workon_viper/out/target/product/rolex/obj/ETC/sepolicy_intermediates/sepolicy ) && (touch /home/shrawan/Desktop/workon_viper/out/target/product/rolex/obj/ETC/sepolicy_tests_intermediates/sepolicy_tests )"
The following types on /data/ must be associated with the "core_data_file_type" attribute: netmgrd_data_file
[ 82% 60975/74331] //bionic/libc:commo...ioner preprocess include [linux_glibc]
warning: attempted to generate guard with empty availability: obsoleted = 23
warning: attempted to generate guard with empty availability: obsoleted = 21
ninja: build stopped: subcommand failed.
11:58:35 ninja failed with: exit status 1
#### failed to build some targets (04:38:04 (hh:mm:ss)) ####
I did a enough of the search in and out of the forum but i couldn't able to know what problem is this and i dont have any idea how to solve this. Please give me some light on what problem is this and guide me where should i be looking to solve. I have a great enthusiasm of learning but this problem solution isn't available or discussed properly in any place or maybe i didn't find the place where to look. Please help me on this

[[/COLOR]I was able to fix it by modifying the file at device/qcom/sepolicy/vendor/common/file.te and specifying
Code:
type netmgrd_data_file, file_type, data_file_type, core_data_file_type;
I don't know why / how this file is ending up here though

HarshOne said:
Any solution for this error?
Code:
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/harshone/android/lineage/out/target/product/m8/obj/KERNEL_OBJ/usr', needed by '/home/harshone/android/lineage/out/target/product/m8/obj/STATIC_LIBRARIES/libsdcard_intermediates/sdcard.o', missing and no known rule to make it
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/harshone/android/lineage'
#### make failed to build some targets (02:30 (mm:ss)) ####
Click to expand...
Click to collapse
mine have same error, seem like kernel have wrong config (i dont know how to fix ) )