COMPILE From Source For Any Phone On Linux Distros [BUILD ENVIRONMENT TO COMPILE]
This is a guide to Compile From any Cyanogenmod or Cyanogenmod Source-Based source for Any Phone. This guide is for linux , Ubuntu etc.
Quote:
Note :- github is having issues as such you will not be able to follow this build guide until the issues have been resolved. This warning will be removed as soon as the issues have been resolved. For Checking if github is currently functional click here
What you’ll need
A Phone Which runs Android :P
A relatively recent computer (Linux, OS X, or Windows) w/a reasonable amount of RAM and 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.
Quote:
Note:
You want to use a 64-bit version of Linux. According to Google, 32-bit Linux environment will only work if you are building older versions prior to Gingerbread (2.3.x)/CyanogenMod 7.
Using a VM allows Linux to run as a guest inside your host computer-- a computer in a computer, if you will. If you hate Linux for whatever reason, you can always just uninstall and delete the whole thing. (There are plenty of places to find instructions for setting up Virtualbox with Ubuntu, so I’ll leave it to you to do that.)
So let’s begin!
Build ROM and ClockworkMod Recovery
Prepare the Build Environment
Quote:
Note:
You only need to do these steps the first time you build. If you previously prepared your build environment and have downloaded the CyanogenMod source code for another device, skip to Prepare the device-specific code.
Install the SDK
If you have not previously installed adb and fastboot, install the Android SDK. "SDK" stands for Software Developer Kit, and it includes useful tools that you will can use to flash software, look at the system logs in real time, grab screenshots, and more-- all from your computer.
Quote:
Helpful Tip!
While the SDK contains lots of different things-- the two tools you are most interested in for building Android are adb and fastboot, located in the /platform-tools directory.
Install the Build Packages
Several "build packages" are needed to build From Source. You can install these using the package manager of your choice.
Quote:
Helpful Tip!
A package manager in Linux is a system used to install or remove software (usually originating from the Internet) on your computer. With Ubuntu, you can use the Ubuntu Software Center. Even better, you may also use the apt-get install command directly in the Terminal. (Learn more about the apt packaging tool system from Wikipedia.)
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. Assuming you are using the BASH shell, the default in recent versions of Ubuntu, you can set it like this:
Code:
export PATH=${PATH}:~/bin
Quote:
Helpful Tip!
You can make this change to the path permanent for all future Terminal sessions:
Code:
gedit ~/.bashrc
This will launch a graphical text editor. Enter
Code:
export PATH=${PATH}:~/bin
on its own line, then save the file.
Initialize the source repository
Make a Folder to Download the Sources and cd to it. For That:
Helpful Tip!
The repo sync command is used to update the latest source code from CyanogenMod and Google. Remember it, as you can do it every few days to keep your code base fresh and up-to-date.
MAKE SURE YOUR PHONE IS ON OFFICIAL LATEST CYANOGENMOD ROM
Quote:
Helpful Tip!
If you get a command not found error for lunch, be sure you’ve done the “. build/envsetup.sh” command from ~/Source. Notice there is a period and space (“. ”) in that command.
Extract proprietary blobs
Now ensure that your Phone is connected to your computer via the USB cable and that you are in the ~/Source/device/***/***** directory (you can cd ~/Source/device/***/****** if necessary). Run as Root if on Debian using sudo. Then run the this script:
Code:
./proprietary-files.sh
or
Code:
./extract-files.sh
Quote:
Here ***** is Device codename and *** is the Phone Company like Samsung or HTC
For Example if my phone is note 2 then this will be the device path : ~/Source/device/Samsung/n7100
You should see the proprietary files (aka “blobs”) get pulled from the device and moved to the right place in the vendor directory. If you see errors about adb being unable to pull the files, adb may not be in the path of execution
Quote:
Note:
It’s important that these proprietary files are properly extracted and moved to the vendor directory. Without them, CyanogenMod will build without error, but you’ll be missing important functionality, such as the ability to see anything!
Turn on caching to speed up build
Code:
export USE_CCACHE=1
Start the build
Code:
cd ~/Source
brunch *****
Here ***** is the Phone Codename
Quote:
Helpful Tip!
If the build doesn't start, try lunch and choose your device from the menu. If that doesn't work, try breakfast and choose from the menu. The command make ***** should then work.
If the build breaks...
If you experience this not-enough-memory-related error...
...you may want to make the following change to This File : system/build/tools/releasetools/common.py
Change: java -Xmx2048m to java -Xmx1024m or java -Xmx512m
Then start the build again (with brunch).
If you see a message about things suddenly being “killed” for no reason, your (virtual) machine may have run out of memory or storage space. Assign it more resources and try again.
Install the build
Assuming the build completed without error (it will be obvious when it finishes), type:
Code:
# cd $OUT
in the same terminal window that you did the build. Here you’ll find all the files that were created. The stuff that will go in /system is in a folder called system. The stuff that will become your ramdisk is in a folder called root. And your kernel is called... kernel.
But that’s all just background info. The two files we are interested in are (1) recovery.img, which contains ClockworkMod recovery, and (2) cm-[something].zip, which contains ROM.
Install ROM
Back to the $OUT directory on your computer-- you should see a file that looks something like:
Code:
cm-10-20120718-UNOFFICIAL-***.zip
Here *** is the phone codename
Now you can flash the ...zip file above as usual via recovery mode. (Be sure you have backed up any previous installation before trying your new build.)
Feedbacks to this guide
Quote:
Originally Posted by tommyjt24
I got my build working!
Great tutorial by the way!
Tom
Quote:
Originally Posted by sevenup30
Well i finally sucessfully build.
thank you for your help
Quote:
Originally Posted by AndyFox2011
Works like a charm, used it a while ago too set up on 12.10
Quote:
Originally Posted by sswb27
Compiling cm10.1 worked great for my sgs3 d2tmo.Thank's for the tutorial it's been fun setting this up.
Quote:
Originally Posted by matt95
really really good guide, very detailed and precise.
Quote:
Originally Posted by Koetermann
Hi there,
I was finally able to compile Cyanogenmod from source.
So, thanks for your guide an your support.Thanks a lot.
Regards Koetermann
Quote:
Originally Posted by AndyFox2011
Used your guide again to setup my PC for building! Worked like a charm on 11.04
Quote:
Originally Posted by Melch1zedeK
thanks for post this, great and simple guide for n00bs (like me)
Quote:
Originally Posted by VipSaran
This tutorial ROCKS! . Successfully built i9300 starting from fresh ubuntu 12.10 installation w/o even a hickup
Read the Below Command Before Asking question regarding Device tree : Credit @speed_bot
HTML Code:
#include
#include /ps my own header/
main()
{
int device tree,rom;
for((device==1) || (device tree =1))
printf("you can build a rom");
else
printf("you cant :P");
}
Please Press "Thanks" Button If I Helped You | Current Device: X10 Mini | Future Device (July): SONY Xperia Z or Google Nexus 4 FOLLOW ON MY TWITTER | MY SITE | G+ COMMUNITY
jolly@ubuntu:~$ sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 libc6-dev lib32ncurses5-dev ia32-libs 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.6-dev python
[sudo] password for jolly:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package lib32bz2-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
Package lib32ncurses5-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
Package lib32readline-gplv2-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
Package lib32readline5 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
Package lib32readline6 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
Package ia32-libs is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'lib32ncurses5-dev' has no installation candidate
E: Package 'ia32-libs' has no installation candidate
E: Unable to locate package lib32z-dev
E: Package 'lib32readline-gplv2-dev' has no installation candidate
E: Package 'lib32readline5' has no installation candidate
E: Package 'lib32readline6' has no installation candidate
E: Package 'lib32bz2-dev' has no installation candidate
E: Unable to locate package libwxgtk2.6-dev
E: Couldn't find any package by regex 'libwxgtk2.6-dev
The issue with guides like these is they are specific to one version of Ubuntu. I successfully build Android on gentoo, which has about as little in common with Ubuntu as possible. Hence we prefer to go for guides which, where possible, teach the reasoning, rather than the method.
For building CM, this might be worthwhile merging into the "how to build android from source" one?
Unfortunately this guide isn't usable for most people, as it relies on the hacksung build scripts, so you can only build for certain devices...
What might be better is a guide on using roomservice via lunch, to build for any device?
If you wish to apply for one of the Recognized Themer/Contributor titles, or have a question, please DO NOT send me a PM about it. Instead please contact your device's forum moderator, or a senior moderator, who will deal with your application. Thanks
Recovering iPad users may still remember the multitasking function where you can swipe left or right to … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?