I put this tutorial together in an attempt to create the most complete and easy to follow guide for building a ROM from source. Including steps for adding apps to your build, changing toolchains and more... The entire guide uses a single Linux terminal window from start to finish in an attempt to keep everything as user friendly as possible. Please feel free to PM me suggestions on where changes need be made.
If you find this guide helpful please press the Thanks button on my posts and rate the thread a 5.
Prerequisites1. This guide is for Ubuntu 12+ based machine, I run Linux Mint 15. Follow links at end of OP for alternate directions
Windows Users: Setup Ubuntu in Virtualbox Instructions
2. You need to know the location for your device, vendor, and kernel repos. This can be found fairly easily in the forum for your phone. Also take note of your phones codename.
For example the Optimus G is the gee and its repos can be found here https://github.com/TeamPlaceholder
Note*All terminal commands will be in Code boxes*
Part 1 - Setting Up The Build Environment
Install Java JDK
Code:
sudo add-apt-repository ppa:webupd8team/java
Code:
sudo apt-get update
Code:
sudo apt-get install oracle-java6-installer
Installing required packages
Code:
sudo apt-get install git gnupg flex bison gperf build-essential \
zip 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 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
Code:
sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
Set-up ccache This Is Optional
Code:
nano ~/.bashrc
Add these two lines
export USE_CCACHE=1
export CCACHE_DIR=<path-to-your-cache-directory>
Click to expand...
Click to collapse
Save and exit by pressing ctrl+x, selecting Y then enter.
Install ADB & Fastboot This is optional, as you may already have them working. If not, they're a good thing to have.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Setup Repo
Code:
mkdir ~/bin
Code:
PATH=~/bin:$PATH
Code:
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
Code:
chmod a+x ~/bin/repo
Create working directory
Code:
mkdir [I][B]working-dir[/B][/I]
(Replace working-dir with whatever you'd like to call it, ie. aokp)
Code:
cd working-dir
Part 2 - Get SourceROM Source
Choose which custom rom you are going to build and initialize the repo for it
Code:
repo init -u [I][B]chosen-manifest[/B][/I]
(Replace chosen-manifest appropriately from the list below)
AOKP: https://github.com/AOKP/platform_manifest.git -b Branch
Cyanogenmod: https://github.com/CyanogenMod/android.git -b Branch
CarbonDev: https://github.com/CarbonDev/android.git -b Branch
Liquid Smooth: https://github.com/LiquidSmooth/android.git -b Branch
Replace Branch with appropriate branch from github repo ie cm-10.2 or jb3
If unsure which branch click the link above to locate appropriate branch
Click to expand...
Click to collapse
Device Source
Go HERE and follow instructions on obtaining your device specific repos.
Sync the repo
Code:
repo sync
This will take a while as it downloads all the required source
Part 3 - Preparing SourceBefore you're ready to build your source needs to be configured to include your device. This preparation varies slightly for different custom Roms.
Go HERE and follow instructions for your ROM choice
Part 4 - Edit SourceThis Is OptionalThis is where you can make edits to the source before building to suit your needs.
Go HERE and follow the instructions to tweak source
Part 5 - Building ROM
Code:
. build/envsetup.sh
Code:
lunch
Locate your device on the list and enter appropriate number
Code:
make -j[B][I]# [/I][/B]otapackage
Replace # with the number of cores in your system (Is the number of jobs that will be done at once, more cores means more jobs)
Build Errors
This can be hard, especially if you're new to programming languages and building. Meet Google your new best friend.
Here is a basic overview to get you started, and if no more at least googling in the right direction.
FinishedWhen it's done you're rom will be in working-dir/out/target/product/codename/
Enjoy.
I used these sites while making this guide
http://source.android.com/source/initializing.html
http://www.webupd8.org/2012/11/oracle-sun-java-6-installer-available.html
http://www.webupd8.org/2012/08/install-adb-and-fastboot-android-tools.html
Device Source As stated in the prerequisites you will need a device specific Device repo, Vendor repo, and Kernel repo. You can find links to them in the threads for your devices. Also take note of your device codename ie Nexus 4 is mako, Optimus G is gee.
There are two options for adding in device specific source, local manifest and git clone.
Note: The local path for your phone's repos should be device/manufacturer/codename, vendor/manufacturer/codename, kernel/manufacturer/codename regardless of method chosen.
Git Clone
Git clone is a one time download of a specific repo to the directory indicated and is not affected when a repo sync is run. This is probably the better choice if you make edits to the device source as they won't be over written or cause conflicts when syncing.
This method is used AFTER the inital rom source sync. Preform a repo sync before cloning repos
Code:
git clone [B][COLOR=DarkOrange]repo[/COLOR][/B] -b [B][COLOR=Red]branch[/COLOR][/B] [B][COLOR=Lime]destination-path[/COLOR][/B]
here is and example for the vendor repo for the E973 from TeamPlaceHolder
git clone https://github.com/TeamPlaceholder/proprietary_vendor_lge_gee -b cm-10.2 vendor/lge/gee
Click to expand...
Click to collapse
Local Manifest
Local manifest syncs the device repos each time a repo sync is run. This is probably the better choice if you don't make edits and rely on the repo's maintainer for changes. Be wary making edits locally to the repos you list as a repo sync may overwrite your changes.
This method is used BEFORE the initial rom sync. This gets your device source during the first repo sync
Code:
mkdir .repo/local_manifests
Code:
touch .repo/local_manifests/local_manifest.xml
Code:
nano .repo/local_manifests/local_manifest.xml
Add these lines:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="name-for-remote" fetch="remote-url" />
<project path="destination-folder-path" name="repo-location" remote="name-for-remote" revision="branch" />
</manifest>
Click to expand...
Click to collapse
name-for-remote - Any name you want to give to identify the url where your repos are stored
remote-url - The url for the remote location your repos are stored
destination-folder-path - Where do you want this repo stored locally
repo-location - Where on the remote url is your repo stored
branch - The branch of the remote repo you are using
**You will need a project line for each repo you wish to add to the source. **
Here is an example for E973 using TeamPlaceHolder repos, adding all device/vendor/kernel repos.
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="gh"
fetch="git://github.com/" />
<project path="kernel/lge/gee" name="TeamPlaceholder/android_kernel_lge_gee" remote="gh" revision="cm-10.2-update" />
<project path="device/lge/geeb" name="TeamPlaceholder/android_device_lge_geeb" remote="gh" revision="cm-10.2" />
<project path="device/lge/gee-common" name="TeamPlaceholder/android_device_lge_gee-common" remote="gh" revision="cm-10.2" />
<project path="vendor/lge/gee" name="TeamPlaceholder/proprietary_vendor_lge_gee" remote="gh" revision="cm-10.2" />
</manifest>
Click to expand...
Click to collapse
Preparing Source
Preparing SourceROM specific setup instructions prior to building. All source should be downloaded already.
All ROM setup is fairly similar,
1. You must add your device to the ROM's vendor repo(vendor/cm or vendor/aokp) This process is slightly different per rom. Look at how other devices are added in the vendor repo and emulate those.
2. A ROM specific makefile, again look at how other devices are added.
3. If building AOSP based ROMs, a pre-built kernel is generally required. Look here for instructions on how to compile a kernel separately.
Here are examples of how to set up AOKP or Carbon to build. Device used in example is Optimus G.
Manufacturer and codename MUST be updated to reflect your device.
AOKP
Code:
nano vendor/aokp/vendorsetup.sh
Add this line
add_lunch_combo aokp_geeb-userdebug
Click to expand...
Click to collapse
Save and exit by pressing ctrl+x, selecting Y then enter.
Code:
touch vendor/aokp/products/geeb.mk
Code:
nano vendor/aokp/products/geeb.mk
Add these lines
If building for CDMA network change gsm.mk to cdma.mk
# Inherit AOSP device configuration for geeb
$(call inherit-product, device/lge/geeb/full_geeb.mk)
# Inherit AOKP common bits
$(call inherit-product, vendor/aokp/configs/common.mk)
# Inherit GSM common stuff
$(call inherit-product, vendor/aokp/configs/gsm.mk)
# Setup device specific product configuration
PRODUCT_NAME := aokp_geeb
PRODUCT_BRAND := google
PRODUCT_DEVICE := geeb
PRODUCT_MODEL := Optimus G
PRODUCT_MANUFACTURER := LGE
Click to expand...
Click to collapse
Save and exit by pressing ctrl+x, selecting Y then enter.
Code:
nano vendor/aokp/products/AndroidProducts.mk
Add this line
$(LOCAL_DIR)/geeb.mk \
Click to expand...
Click to collapse
Save and exit by pressing ctrl+x, selecting Y then enter.
CarbonDev
Code:
nano vendor/carbon/vendorsetup.sh
Add this line
add_lunch_combo carbon_geeb-userdebug
Click to expand...
Click to collapse
Once your device has been added you're ready to build! Go back to the OP and complete the guide from where you left off.
good stuff haze
AGREED!!
What bout building ROMs based on LG source? I'd rather see more LG based ROMs because the camera quality is higher, and a lot of AOSP/AOKP ROMs feel more or less the same.
geokilla said:
What bout building ROMs based on LG source? I'd rather see more LG based ROMs because the camera quality is higher, and a lot of AOSP/AOKP ROMs feel more or less the same.
Click to expand...
Click to collapse
Seriously ? Find me LG source to build a rom and I'll make you one.
@moderator.
Btw, This post and the previous should be removed, that thread locked to prevent post like these and pinned. thanks.
Haze028 said:
Well I had put up build instructions for AOKP but thought I would generalize them so people could use them for other ROM bases. My therory is the more people that are trying to build, the more improvments/enhancements can be put forth to the OG community.
As I've stated before I do not consider myself a dev. So don't be afraid of giving this a try, even if you have little to no android building experience. The instructions are as step by step as I could make them, and I'll always try to help where I can.
When it's done you're rom will be in out/target/product/geeb/
I'm writing this now from memory, so if it doesn't work let me know so I may update accordingly
Enjoy.
Click to expand...
Click to collapse
It was what I'm looking for...
Thanks a lot..
Definitely I'll give a try!
chadouming said:
Seriously ? Find me LG source to build a rom and I'll make you one.
@moderator.
Btw, This post and the previous should be removed, that thread locked to prevent post like these and pinned. thanks.
Click to expand...
Click to collapse
Why would want to lock the thread? How do we suppose to learning? I think @Haze purpose was opposite that you suggest, if we do not learn, we'll keeping ask you to change this, or do that instead to help you and even do some nice stuff.
Don't be like that be patience and share your great knowledge. I'm your fan. :good:
d.terenzzo said:
Why would want to lock the thread? How do we suppose to learning? I think @Haze purpose was opposite that you suggest, if we do not learn, we'll keeping ask you to change this, or do that instead to help you and even do some nice stuff.
Click to expand...
Click to collapse
Yeah, I don't think it should get locked, I started it to try to help people out, so they can get assistance through this thread with their builds. Being new to building myself, I have found that the issues, and resolutions to them, in similar threads to this to be a wealth of knowledge.
getting error
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[vendor/aokp/products/geeb.mk]]: "device/lge/geeb/full_geeb.mk" does not exist. Stop.
** Don't have a product spec for: 'aokp_geeb'
** Do you have the right repo manifest?
Any idea what i missed?
Recon Freak said:
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[vendor/aokp/products/geeb.mk]]: "device/lge/geeb/full_geeb.mk" does not exist. Stop.
** Don't have a product spec for: 'aokp_geeb'
** Do you have the right repo manifest?
Any idea what i missed?
Click to expand...
Click to collapse
have you cloned the geeb device tree into device/lge/geeb? seems the error is saying that full_geeb.mk doesn't exist, so either you've not yet cloned the device tree, or you have it in a differnt folder name, I'm assuming currently.
let me know if that's not the case.
I know most people want to run latest and greatest but I'm curious if we could build a cm10 (4.1.2) using LG's released kernel sources?
Any thoughts??
Would be cool to get a 4.1.2 build without LG's proprietary software...
Hopefully you see my point in posting this here as building from lg's sources and either aosp or cm10 isn't the most straightforward.
I'm attempting but I don't expect to have much success...
Mate, how long does repo sync takes? I saw something to download about 10gb?
cheers
d.terenzzo said:
Mate, how long does repo sync takes? I saw something to download about 10gb?
cheers
Click to expand...
Click to collapse
It all depends on your internet connection, looking at around 10-20gb. I think my AOKP repo is 12gb...give or take
Haze028 said:
It all depends on your internet connection, looking at around 10-20gb. I think my AOKP repo is 12gb...give or take
Click to expand...
Click to collapse
"Once you know the truth, there is no going back"
for learning purpose:
Why should we have to download all projects in AOKP, if I wont use it.
There is a way to choice between what to download and what to not download?
cheers
d.terenzzo said:
"Once you know the truth, there is no going back"
for learning purpose:
Why should we have to download all projects in AOKP, if I wont use it.
There is a way to choice between what to download and what to not download?
cheers
Click to expand...
Click to collapse
In the third post i show you how to use a local manifest to remove projects you don't want/need from the repo before you sync, linked to in the build instructions. I always remove the device tree and vendor for other devices before my initial sync.
Yeah, I tried that, but I got weird error. Something about manifest, once I removed the example line about Samsung groups, it worked.
Would you mind to share your local_manifest.
Cheers
Sent from my LG-E971 using xda app-developers app
d.terenzzo said:
Yeah, I tried that, but I got weird error. Something about manifest, once I removed the example line about Samsung groups, it worked.
Would you mind to share your local_manifest.
Cheers
Sent from my LG-E971 using xda app-developers app
Click to expand...
Click to collapse
Sorry for the delay, didn't notice your post, anyways here is my current local manifest file for aokp
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/geeb" name="Haze028/android_device_lge_geebca" remote="aokp" revision="aokp"/>
<project path="vendor/lge/geeb" name="Haze028/android_vendor_lge_geeb" remote="aokp" revision="cm-10.1"/>
<project path="kernel/lge/geeb" name="Haze028/geeb" remote="aokp" revision="geeb"/>
<project path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" revision="master" groups="linux,arm" />
<project path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7" name="platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7" revision="master" groups="linux,arm" />
<remove-project name="AOKP/packages_apps_Launcher2" />
<remove-project name="AOKP/device_acer_a510" />
<remove-project name="AOKP/device_asus_grouper" />
<remove-project name="AOKP/device_asus_tilapia" />
<remove-project name="CyanogenMod/android_device_common" />
<remove-project name="device/generic/armv7-a-neon" />
<remove-project name="device/generic/armv7-a" />
<remove-project name="device/generic/common" />
<remove-project name="device/generic/goldfish" />
<remove-project name="device/generic/mips" />
<remove-project name="device/generic/x86" />
<remove-project name="device/google/accessory/arduino" />
<remove-project name="device/google/accessory/demokit" />
<remove-project name="AOKP/device_htc_evita" />
<remove-project name="AOKP/device_htc_msm8960-common" />
<remove-project name="AOKP/device_lge_iprj-common" />
<remove-project name="AOKP/device_lge_mako" />
<remove-project name="AOKP/device_lge_p930" />
<remove-project name="AOKP/device_lge_su640" />
<remove-project name="AOKP/device_lge_vs920" />
<remove-project name="AOKP/device_motorola_maserati" />
<remove-project name="AOKP/device_motorola_omap4-common" />
<remove-project name="AOKP/device_motorola_solana" />
<remove-project name="AOKP/device_motorola_spyder" />
<remove-project name="AOKP/device_motorola_targa" />
<remove-project name="AOKP/device_motorola_umts_spyder" />
<remove-project name="device/sample" />
<remove-project name="AOKP/device_samsung_aries-common" />
<remove-project name="AOKP/device_samsung_celox-common" />
<remove-project name="AOKP/device_samsung_d2-common" />
<remove-project name="AOKP/device_samsung_d2att" />
<remove-project name="AOKP/device_samsung_d2tmo" />
<remove-project name="AOKP/device_samsung_d2usc" />
<remove-project name="AOKP/device_samsung_d2vzw" />
<remove-project name="AOKP/device_samsung_galaxys2-common" />
<remove-project name="AOKP/device_samsung_hercules" />
<remove-project name="AOKP/device_samsung_i605" />
<remove-project name="AOKP/device_samsung_i9100" />
<remove-project name="AOKP/device_samsung_i9100g" />
<remove-project name="AOKP/device_samsung_i9300" />
<remove-project name="AOKP/device_samsung_l900" />
<remove-project name="AOKP/device_samsung_maguro" />
<remove-project name="AOKP/device_samsung_manta" />
<remove-project name="AOKP/device_samsung_msm8660-common" />
<remove-project name="AOKP/device_samsung_msm8960-common" />
<remove-project name="CyanogenMod/android_device_samsung_omap4-common" />
<remove-project name="AOKP/device_samsung_qcom-common" />
<remove-project name="AOKP/device_samsung_smdk4412-common" />
<remove-project name="CyanogenMod/android_device_samsung_smdk4412-qcom-common" />
<remove-project name="AOKP/device_samsung_t0lte" />
<remove-project name="AOKP/device_samsung_t0ltecdma" />
<remove-project name="AOKP/device_samsung_toro" />
<remove-project name="AOKP/device_samsung_toroplus" />
<remove-project name="AOKP/device_samsung_tuna" />
<remove-project name="AOKP/device_samsung_vibrantmtd" />
<remove-project name="device/ti/panda" />
<remove-project name="AOKP/vendor_htc" />
<remove-project name="AOKP/vendor_lge" />
<remove-project name="AOKP/vendor_motorola" />
<remove-project name="AOKP/vendor_samsung" />
<remove-project name="AOKP/vendor_acer_a510" />
<remove-project name="AOKP/vendor_asus" />
</manifest>
Click to expand...
Click to collapse
Haze028 said:
Sorry for the delay, didn't notice your post, anyways here is my current local manifest file for aokp
Click to expand...
Click to collapse
Hey Haze028, thanks for this great write up!
Anyways, im trying to build this for the Sprint LG OG. Do i need to sync with different device trees then this? Im very new at building from source, so, sorry if this is a stupid question.
Thanks!
eletendre84 said:
Hey Haze028, thanks for this great write up!
Anyways, im trying to build this for the Sprint LG OG. Do i need to sync with different device trees then this? Im very new at building from source, so, sorry if this is a stupid question.
Thanks!
Click to expand...
Click to collapse
I believe you will need different repo's, check out Team LGOG's github(https://github.com/TeamLGOG) They have device tree's for all variants, Chadouming is a member of that team and as such his CM10.1 uses those repo's. The local_manifest for Cyanogenmod in the OP should show you which repo's to use.... then depending on what rom you're looking to build some minor changes might be required.
I've not built using their repo's, but I'll help you in getting it all set up.
Since I sold my Galaxy Nexus and I won't continue to build crDroid rom for it, I made this step by step guide to build 4.4 KitKat crDroid rom running on this device from Cristiano Matos and cm's github.
This guide is meant for Ubuntu 13.10 64 bit. 32 Bit won't work.
If you want to use another ubuntu version, some things might be a little different. Just search on xda and you will find all the instructions that you need to complete the setup.
DISCLAMER
Although the procedures in this guide were tested on my pc/phone and produced a working build for my Galaxy Nexus, I take no responsibility for any consequences derived from their use.
1) SET UP THE BUILD ENVIRONMENT
Remove openJDK and install Java 6 jdk. Open a terminal and type:
Code:
sudo apt-get purge openjdk-\* icedtea-\* icedtea6-\*
This will uninstall openJDK.
Code:
sudo add-apt-repository ppa:webupd8team/java
Adds a PPA to your system, needed to download java.
Code:
sudo apt-get update && sudo apt-get install oracle-java6-installer
Download and installs java!
To make sure the correct version of Java is activated, run the following at the Terminal prompt:
Code:
java -version
You should see something like that:
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)
Now type:
Code:
sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 libc6-dev lib32ncurses5-dev x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 lib32z-dev libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc readline-common libreadline6-dev libreadline6 lib32readline-gplv2-dev libncurses5-dev lib32readline5 lib32readline6 libreadline-dev libreadline6-dev:i386 libreadline6:i386 bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev lib32bz2-dev libsdl1.2-dev libesd0-dev squashfs-tools pngcrush schedtool libwxgtk2.8-dev python lzop
This will install the needed packages.
When done, do this:
Code:
sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
Now, install the repo binary:
Code:
mkdir ~/bin && curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo && chmod a+x ~/bin/repo
Edit .bashrc:
Code:
sudo nano ~/.bashrc
At the bottom of the file, add the following line:
Code:
export PATH=~/bin:$PATH
Save it (In nano type Ctrl-O and then Enter, then Ctrl-X to exit back to a prompt).
Restart bash:
Code:
source ~/.bashrc
2) DOWNLOAD THE SOURCES:
Code:
mkdir ~/cyanogenmod
cd ~/cyanogenmod
This creates a folder named "cyanogenmod" and opens it.
Initialize the repo:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
Open cyanogenmod folder, press ctrl+H to show hidden files, open .repo, open local_manifests and edit roomservice.xml (If it isn't present create it) to be like this one:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="http://github.com/" name="gh" revision="master" />
<remote fetch="https://github.com/TheMuppets/" name="TheMuppets" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="gh" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_imgtec" path="vendor/imgtec" remote="gh" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_broadcom" path="vendor/broadcom" remote="gh" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_invensense" path="vendor/invensense" remote="gh" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_widevine" path="vendor/widevine" remote="gh" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_nxp" path="vendor/nxp" remote="gh" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_maguro" path="device/samsung/maguro" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_toroplus" path="device/samsung/toroplus" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_toro" path="device/samsung/toro" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_kernel_samsung_tuna" path="kernel/samsung/tuna" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_tuna" path="device/samsung/tuna" remote="github" revision="cm-11.0" />
<remove-project name="CyanogenMod/android_packages_apps_Dialer" />
<project name="cristianomatos/android_packages_apps_Dialer" path="packages/apps/Dialer" remote="github" revision="cm-11" />
<remove-project name="CyanogenMod/android_packages_apps_InCallUI" />
<project name="cristianomatos/android_packages_apps_InCallUI" path="packages/apps/InCallUI" remote="github" revision="cm-11" />
<remove-project name="CyanogenMod/android_packages_services_Telephony" />
<project name="cristianomatos/android_packages_services_Telephony" path="packages/services/Telephony" remote="github" revision="cm-11" />
<remove-project name="CyanogenMod/android_frameworks_base" />
<project name="cristianomatos/android_frameworks_base" path="frameworks/base" remote="github" revision="cm-11" />
<remove-project name="CyanogenMod/android_packages_apps_Settings" />
<project name="cristianomatos/android_packages_apps_Settings" path="packages/apps/Settings" remote="github" revision="cm-11" />
</manifest>
Download time!
Code:
repo sync
It will download about 10gb of data, so be patient!
Download the prebuilts:
Code:
~/cyanogenmod/vendor/cm/get-prebuilts
3) BUILD THE ROM:
Code:
. build/envsetup.sh && brunch name_of_device
Where "name_of_device" is maguro, toro or toroplus, depending for which ersion you want to build.
It will take some time (on my pc with 3GHz dual core and 4gb of ram about 2h30min)
If everything goes right the flashable zip of the rom will be in cyanogenmod/out/target/product/name_of_device/cm-11-XXXXXXXXX-UNOFFICIAL-name_of_device.zip
4) Install the rom on your phone!
-------------------------------------------------------------------------------------------------------------
Some other tips:
When you want to download latest crdroid/cm changes open a new terminal and type:
Code:
cd cyanogenmod
repo sync
When you want to delete the build products (because something has gone wrong or you want to make a new build):
Code:
make clean
Then:
Code:
. build/envsetup.sh && brunch name_of_device
To start building again.
Reserved
Simply perfect bro!
Inviato dal mio Galaxy Nexus utilizzando Tapatalk
Thanks for this useful tutorial, awesome #bow
Sent from my Galaxy Nexus using Tapatalk
--deleted--
Thanks for this useful tutorial
Thanks for this useful tutorial.
I can make other unofficial builds in your favor.
@elia222 any idea why I get this when I do a repo sync:
Code:
Fetching project platform/external/scrypt
Fetching project CyanogenMod/android_external_elfutils
Fetching project CyanogenMod/android_external_svox
Fetching projects: 66% (307/465) Fetching project CyanogenMod/android_external_grub
Fetching project platform/external/sfntly
error: Cannot fetch cristianomatos/android_frameworks_base
Fetching project platform/prebuilts/runtime
error: Cannot fetch cristianomatos/android_packages_apps_Settings
error: Exited sync due to fetch errors
linezero said:
@elia222 any idea why I get this when I do a repo sync:
Code:
Fetching project platform/external/scrypt
Fetching project CyanogenMod/android_external_elfutils
Fetching project CyanogenMod/android_external_svox
Fetching projects: 66% (307/465) Fetching project CyanogenMod/android_external_grub
Fetching project platform/external/sfntly
error: Cannot fetch cristianomatos/android_frameworks_base
Fetching project platform/prebuilts/runtime
error: Cannot fetch cristianomatos/android_packages_apps_Settings
error: Exited sync due to fetch errors
Click to expand...
Click to collapse
Probably Cristiano Matos has changed/removed something on his github repositories. I didn't followed the project recently, so your best bet would be to contact him to solve the issue.
So if we re-initialize repo, would that solve the fetch errors?
CristiS2012 said:
So if we re-initialize repo, would that solve the fetch errors?
Click to expand...
Click to collapse
You can try, not sure if it will work or not.
Could i just download resource for specify device only ?
Not download reaource for all device
Is this guide also work on non nexus device ?
Can i use the maguro CM device trees for other roms like slim, beanstalk for lollipop ??
iddu.daragah said:
Can i use the maguro CM device trees for other roms like slim, beanstalk for lollipop ??
Click to expand...
Click to collapse
Yes, but it might need some little corrections.
elia222 said:
Yes, but it might need some little corrections.
Click to expand...
Click to collapse
What should i exactly edit ??
iddu.daragah said:
What should i exactly edit ??
Click to expand...
Click to collapse
It depends from which rom are you building. You will see from build errors what needs to be edited
elia222 said:
It depends from which rom are you building. You will see from build errors what needs to be edited
Click to expand...
Click to collapse
I am building PA 5.0 and currently my device is running slimkat.
So if i flash PA 4.4 and extract the proprietary blobs from device or download the kitkat maguro device trees via local manifest so will it give me build errors ?? and okay ill know by the build errors what changes should i make ....
Thnk You
iddu.daragah said:
I am building PA 5.0 and currently my device is running slimkat.
So if i flash PA 4.4 and extract the proprietary blobs from device or download the kitkat maguro device trees via local manifest so will it give me build errors ?? and okay ill know by the build errors what changes should i make ....
Thnk You
Click to expand...
Click to collapse
I haven't followed maguro since a long time. There aren't 5.0 blobs available?
elia222 said:
I haven't followed maguro since a long time. There aren't 5.0 blobs available?
Click to expand...
Click to collapse
There are for cyanogemod .. but how will they work in PA ???
iddu.daragah said:
There are for cyanogemod .. but how will they work in PA ???
Click to expand...
Click to collapse
They work. Use cm vendor tree
First time building CyanogenMod from source and I've run into a roadblock.
I am at the point where I have CM12 repo synced and when i run
Code:
breakfast d2spr
I get the error:
** Don't have a product spec for: 'cm_d2spr'
** Do you have the right repo manifest?
so then I run
Code:
breakfast
it returns a list of devices and d2spr is not in the list.
So I'm kinda stuck here. how do I get the vendor files for d2spr?
Thanks!
I had to add a roomservice.xml to the local_manifests folder (under .repo in your main directory), to get it up and running:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Hrubak/d2spr-tools.git" path="d2spr-tools" remote="github" revision="cm-12.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" revision="cm-12.0" />
<project name="CyanogenMod/android_device_samsung_d2spr" path="device/samsung/d2spr" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" />
<project name="CyanogenMod/android_device_samsung_d2-common" path="device/samsung/d2-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_d2" path="kernel/samsung/d2" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
</manifest>
and then run
Code:
d2spr-tools/apply.sh
Be advised that when I ran the shell script I got a conflict with one of the files. You can either attempt to correct the error or run "git cherry-pick --abort" in the conflicting directory.
and then finally
Code:
. build/envsetup.sh && brunch d2spr
will compile it.
got these instructions from here:
github.com/Hrubak/d2spr-tools
I'm trying to build Nougat for this device, which has recently been given a CM14 branch.
I'm getting binary blobs from TheMuppets and after syncing, breakfast gives me this error.
Code:
$ breakfast mondrianwifi
including vendor/cm/vendorsetup.sh
build/core/config.mk:671: COMMON_GLOBAL_C(PP)FLAGS changed
build/core/config.mk:675: *** bailing.... Alto.
Device mondrianwifi not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_mondrianwifi
Default revision: staging/cm-14.0
Checking branch info
Using fallback branch: cm-14.0
Checking if device/samsung/mondrianwifi is fetched from android_device_samsung_mondrianwifi
CyanogenMod/android_device_samsung_mondrianwifi already fetched to device/samsung/mondrianwifi
Syncing repository to retrieve project.
Fetching project CyanogenMod/android_device_samsung_mondrianwifi
Fetching projects: 100% (1/1), done.
Repository synced!
Looking for dependencies
Done
build/core/config.mk:671: COMMON_GLOBAL_C(PP)FLAGS changed
build/core/config.mk:675: *** bailing.... Alto.
build/core/config.mk:671: COMMON_GLOBAL_C(PP)FLAGS changed
build/core/config.mk:675: *** bailing.... Alto.
** Don't have a product spec for: 'cm_mondrianwifi'
** Do you have the right repo manifest?
This is my local manifest.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_mondrianwifi" path="device/samsung/mondrianwifi" remote="github" revision="cm-14.0" />
<project name="CyanogenMod/android_external_sony_boringssl-compat" path="external/sony/boringssl-compat" remote="github" revision="cm-14.0" />
<project name="CyanogenMod/android_device_samsung_msm8974-common" path="device/samsung/msm8974-common" remote="github" revision="cm-14.0" />
<project name="CyanogenMod/android_kernel_samsung_mondrianwifi" path="kernel/samsung/mondrianwifi" remote="github" revision="cm-14.0" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.0" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-14.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-14.0" />
</manifest>
Any clue?
Thanks.
Did you forget to run envsetup.sh first?
Which version of the MSM are you attempting to use?
Ichijoe said:
Did you forget to run envsetup.sh first?
Which version of the MSM are you attempting to use?
Click to expand...
Click to collapse
I didn't forget to run envsetup.sh
I'm using the MSM8974 repo that appears on github.
https://github.com/CyanogenMod/android_device_samsung_mondrianwifi/blob/cm-14.0/cm.dependencies
Which is this one
https://github.com/CyanogenMod/android_device_samsung_msm8974-common/tree/cm-14.0
Thanks for your reply.
(ratafraking stupid spellcheck!!)
It corrected JDK (Java Development Kit), back to MSM... Which is (if we're to be quite honest) a redundant question. As you really don't have much choice beyond the 8974.
But, my rational thinking is either telling me that JDK 7 is no longer supported, or you might have missed some dependency for JDK 8.
I only have JDK 8 installed, I have successfully compiled CM13 with it.
I am trying to reduce the CyanogenMod source download as much as possible. So far I have:
Code:
repo init -u https://github.com/CyanogenMod/android.git -b cm-13.0 --depth=1 --groups=all,-notdefault,-device,-darwin,-x86,-mips,-exynos5,-intel,-eclipse,-device
Then I add Ziyans device tree in roomservice.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_maguro" path="device/samsung/maguro" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_tuna" path="kernel/samsung/tuna" remote="github" />
<project name="CyanogenMod/android_device_samsung_tuna" path="device/samsung/tuna" remote="github" />
<project name="Ziyann/proprietary_vendor_samsung" path="vendor/samsung" remote="github" />
</manifest>
However, when I do
Code:
repo manifest -o snapshot.xml -r
I still have over 500 projects.
This is a unique list of the groups in the xml file.
Which of them can I exclude without affecting the functionality of the ROM or causing compile issues?
Code:
apps_nfc
apps_stk
arm
broadcom_wlan
cts
dra
drm_
drm_hwcomposer
frameworks_ims
intel_sensors
invensense
libxml2
libyuv
linux
marvell_bt
mediatek
mediatek_wear
omap3
omap4
omap4-aah
pdk
pdk-cw-fs
pdk-fs
qcom
qcom_
qcom_audio
qcom_display
qcom_fm
qcom_keymaster
qcom_msm8960
qcom_msm8994
qcom_msm8x26
qcom_msm8x27
qcom_msm8x74
qcom_msm8x84
qcom_wlan
themes
tools
vboot
omap3 and mediatek look like candidates and some of the qcom ones maybe?
I have attached the snapshot.xml in case anyone has any suggestions of project level items that can be removed rather than group level.