COMPILE From Source For Any Phone On Linux Distros [BUILD ENVIRONMENT TO COMPILE]

Search This thread

Ryuinferno

Senior Member
Apr 3, 2012
3,548
7,112
ryuinferno.github.io
Last edited:

181charan

Senior Member
Aug 14, 2011
209
119
What if i want to compile the PAC rom?
https://github.com/PAC-man

Downloading Ubuntu now!! Excited!! :)

Edit figured it out myself!!
repo init -u git://github.com/PAC-man/android.git -b jellybean
thankx anyways...
 
Last edited:

speed_bot

Senior Member
Jan 18, 2012
1,604
1,275
Bangalore
What if i want to compile the PAC rom?
https://github.com/PAC-man

Downloading Ubuntu now!! Excited!! :)

Edit figured it out myself!!
repo init -u git://github.com/PAC-man/android.git -b jellybean
thankx anyways...

ya and you might need a minor edits to makefiles in the config ...


btw

this is a thread maintained by me
http://xdaforums.com/showthread.php?t=2059939

so feel free to post your errors that you encounter....

@op

explain what every step means rather then just copy paste....

---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------

Isn't "apt" the "stock" package manager in (K)Ubuntu?

But I've another question @mithun46: Is it possible, that your guide only works on a 64bit edition of ubuntu? So that 32bit installations ain't supported?

32bit systems don't have the packages to build jb and above.. so it wont work with 32bit systems..
 

OmarBizreh

Inactive Recognized Developer
Oct 26, 2011
2,109
3,499
Damascus
plus.google.com
Just when I found time to continue learning Python, I came across this guide from Xda's page on Google+ !!
Let's hope I fail to enter my S3 settings so I can get back to Python :p
No way I'm gonna let such great guide pass me by without learning something from it :)
 
F

Fabe

Guest
When i build it how to edit it's look like boot anim or theme,wallpaper ?
 

jjhiza

Senior Member
Dec 19, 2010
3,163
2,697
Dirty Jersey
@OP,

Very nice guide! I just got a new machine (i7 3630QM, 6GB RAM, 640GB HDD), and I've been eyeing a bunch of "how to compile" threads for a while. Now that I have a fully functional machine, with 100GB allocated to Nadia, I should be able to get up and running. One quick question though...Is it safe for me to assume that the majority of the command line stuff will remain the same, between Quantal and Nadia? This is going to be my first attempt at compiling, and I plan to compile from AOSP, so I figured I'd ask before I take the plunge.

Thank you for the guide...I'm really looking forward to putting this information to work, and getting my own build made for Toro. As an aside, what kind of compile time do you think I'm looking at with my setup? If an i3 compiles in 80-90 minutes, would it be fair to assume that my i7 should do the job in 55-60 minutes or so? Thank you again for an excellent guide! Much appreciated!
 

Cloversmoke

Member
Nov 17, 2012
24
7
Hey great tut thanks!

so complete noob at all of this. If my device is not supported by the team hacksung code I would edit my manifest to...
Code:
<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project name="madmack/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jellybean" />

<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="jellybean" />

<project name="madmack/android_device_samsung_i317" path="device/samsung/i317" remote="github" revision="jellybean" />

<project name="madmack/android_device_samsung_smdk4412-common" path="device/samsung/smdk4412-common" remote="github" revision="jellybean" />

<project name="madmack/android_kernel_samsung_smdk4412" path="kernel/samsung/smdk4412" remote="github" revision="jellybean" />

<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="jellybean" />

</manifest>

sync that, then I would need to do a lunch/breakfast (don't know which one or how to use it and google is being a pain showing me bed and breakfast places lol) followed by make.... is this correct or am I missing something :p

Thanks in advance!

Second question!
You say to add the manifest to the .repo folder inside ~/android/system I do cnt+H to show hidden files but there is not a .repo folder. The only one I can find is the one that already existed.
 
Last edited:

Logi_Ca1

Senior Member
Jun 29, 2011
475
98
Just wondering, how do I install and use third party toolchains like Linaro? I assume your guide uses the default Google GCC 4.7 by default? Thanks!
 

speed_bot

Senior Member
Jan 18, 2012
1,604
1,275
Bangalore
what should i search for. i tired all the things but unable t find the package manager.

Please give screen shots for me. I am a noob.

well hit ctrl+atl+t on your keyboard a nice looking rectangle will open copy paste it there..

---------- Post added at 07:27 AM ---------- Previous post was at 07:22 AM ----------

When i build it how to edit it's look like boot anim or theme,wallpaper ?

well swap the prebuilt anime with the one which you want..... to theme swap png's in frameworks and apps.

---------- Post added at 07:33 AM ---------- Previous post was at 07:27 AM ----------

Hey great tut thanks!

so complete noob at all of this. If my device is not supported by the team hacksung code I would edit my manifest to...
Code:
<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project name="madmack/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jellybean" />

<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="jellybean" />

<project name="madmack/android_device_samsung_i317" path="device/samsung/i317" remote="github" revision="jellybean" />

<project name="madmack/android_device_samsung_smdk4412-common" path="device/samsung/smdk4412-common" remote="github" revision="jellybean" />

<project name="madmack/android_kernel_samsung_smdk4412" path="kernel/samsung/smdk4412" remote="github" revision="jellybean" />

<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="jellybean" />

</manifest>

sync that, then I would need to do a lunch/breakfast (don't know which one or how to use it and google is being a pain showing me bed and breakfast places lol) followed by make.... is this correct or am I missing something :p

Thanks in advance!

Second question!
You say to add the manifest to the .repo folder inside ~/android/system I do cnt+H to show hidden files but there is not a .repo folder. The only one I can find is the one that already existed.

forget about adding it to manifest... find the device tree for your device on github... download it as a zip copy paste that zip to device/manufactureer/here. its easy as that ..
 
  • Like
Reactions: sswb27

moparfreak426

R.I.P.
Mar 22, 2012
6,743
1,197
East/Middle TN
I just wanna say thanks for this guide. I put wubi on windows 8 on my new asus and now i cant dual boot ubuntu:/ anyone care to help me partition my hdd so i can dualboot that way? Scared of screwing up new laptop...

Sent from an Apple killing JellyBean
 

speed_bot

Senior Member
Jan 18, 2012
1,604
1,275
Bangalore
I just wanna say thanks for this guide. I put wubi on windows 8 on my new asus and now i cant dual boot ubuntu:/ anyone care to help me partition my hdd so i can dualboot that way? Scared of screwing up new laptop...

Sent from an Apple killing JellyBean

find an empty partition assume you found c to be your empty partition

download gparted format that partition to ext4...(you need to boot from cd)

then boot from cd install it on that partition ...
 
  • Like
Reactions: moparfreak426

Top Liked Posts

  • There are no posts matching your filters.
  • 197
    buildve.png

    This is a guide to Compile From any CyanogenMod and CyanogenMod Source-Based source for Any Phone. This guide is for linux , Ubuntu etc.

    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.

    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



    buildenvironment.png


    Prepare the Build Environment


    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 Next Post.

    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.

    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.
    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.)

    For 32-bit & 64-bit systems, you'll need:
    Code:
    git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.8-dev squashfs-tools build-essential zip curl 
    libncurses5-dev zlib1g-dev openjdk-6-jre openjdk-6-jdk pngcrush schedtool
    For 64-bit only systems, get these:
    Code:
    g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline-gplv2-dev gcc-4.7-multilib g++-4.5-multilib
    For Linux Mint, you'll need:
    Code:
    libc6-dev x11proto-core-dev libx11-dev libgl1-mesa-dev mingw32 tofrodos python-markdown libxml2-utils

    Create the directories
    Code:
    mkdir -p ~/bin

    Install the repo command
    Enter the following to download the "repo" binary and make it executable (runnable):
    Code:
    curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
    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. 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

    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
    repox.png


    Make a Folder to Download the Sources and cd to it. For That:
    Code:
    mkdir -p ~/Source
    Code:
    cd Source

    Enter the following to initialize the repository:

    REPOSITORY'S OF FAMOUS ROMS (Select One)

    PAC-Man :
    Code:
    repo init -u git://github.com/PAC-man/android.git -b cm-10.2
    CM 11.0 :
    Code:
    repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
    CM 10.1 :
    Code:
    repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
    CM10 :
    Code:
    repo init -u git://github.com/CyanogenMod/android.git -b jellybean

    Download the source code
    Code:
    repo sync

    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.


    Get prebuilt apps
    Code:
    cd ~/Source/vendor/cm
    Code:
    ./get-prebuilts

    How To Compile is there on next post :D
    105
    Prepare the device-specific code

    After the source downloads, type:
    Code:
    . build/envsetup.sh

    Then Do This

    Code:
    breakfast ******
    Where ***** is the codename for your device

    MAKE SURE YOUR PHONE IS ON OFFICIAL LATEST CYANOGENMOD ROM


    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

    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

    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

    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...
    Code:
    ERROR: signapk.jar failed: return code 1make: *** [out/target/product/n7100/cm_n7100-ota-eng.root.zip] Error 1
    ...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
    I got my build working!
    Great tutorial by the way!
    Tom

    Well i finally sucessfully build.
    thank you for your help

    Works like a charm, used it a while ago too set up on 12.10 :)

    Compiling cm10.1 worked great for my sgs3 d2tmo.Thank's for the tutorial it's been fun setting this up.

    really really good guide, very detailed and precise.

    Hi there,
    I was finally able to compile Cyanogenmod from source.
    So, thanks for your guide an your support.Thanks a lot.
    Regards Koetermann

    Used your guide again to setup my PC for building! Worked like a charm on 11.04

    thanks for post this, great and simple guide for n00bs (like me)

    This tutorial ROCKS! :good: . Successfully built i9300 starting from fresh ubuntu 12.10 installation w/o even a hickup :D





    Read the Below Command Before Asking question regarding Device tree : Credit @speed_bot
    HTML:
    #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");
    }
    18
    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?
    6
    What if i want to compile the PAC rom?
    https://github.com/PAC-man

    Downloading Ubuntu now!! Excited!! :)

    Edit figured it out myself!!
    repo init -u git://github.com/PAC-man/android.git -b jellybean
    thankx anyways...

    ya and you might need a minor edits to makefiles in the config ...


    btw

    this is a thread maintained by me
    http://xdaforums.com/showthread.php?t=2059939

    so feel free to post your errors that you encounter....

    @op

    explain what every step means rather then just copy paste....

    ---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------

    Isn't "apt" the "stock" package manager in (K)Ubuntu?

    But I've another question @mithun46: Is it possible, that your guide only works on a 64bit edition of ubuntu? So that 32bit installations ain't supported?

    32bit systems don't have the packages to build jb and above.. so it wont work with 32bit systems..
    6
    Guys The Developer Comitee said me to apply for RC title. Don't know what to do.
    If I get more than ten thanks on this post I will apply

    Sent from my GT-P7300 using xda premium