[TUTORIAL] Setting up and Compiling JB and ICS from AOSP

Search This thread

EddyOS

Senior Member
Jan 2, 2010
15,279
4,034
London
Still not working, getting same error, even though the update-script is now:

assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "/dev/block/platform/omap/omap_hsmmc.0/by-name/boot"),
delete("/tmp/boot.img"));

Change it to this (as per Paul O'Brien's MCR) and it works:

package_extract_file("boot.img", "/tmp/boot.img");
run_program("/sbin/busybox", "dd", "if=/tmp/boot.img", "of=/dev/block/platform/omap/omap_hsmmc.0/by-name/boot");
delete("/tmp/boot.img");
 

TulpiX

Senior Member
Sep 8, 2008
89
4
I got it to compile thx for the tutorial
i chose to compile to get an .img file

but i have a question:
how would you add files to or delete files from (or directories) the .img file ?

thx
 

scratch42069

Member
Dec 13, 2011
41
5
I'd also like to know how to go about modifying after everything has been built. I currently have 4.0.3 pulled and built on 20/12/2011 and as far as I know it built successfully because it didn't error out and everything appeared in the out folder.
 

xHausx

Inactive Recognized Developer
Jul 5, 2010
6,778
4,519
Central Florida
If you didn't code it yourself, it doesn't belong in dev subforum. There's Q&A subforum for that.

/me sent this on a i9250 using tapatalk

I can see you're point with Q&A but when it comes down to it the whole point of this site is to share stuff you've created with others. Q&A is more for people to ask questions while development is for those who want to share something they've done. Although, I do wonder why the OP didn't host it on XDA instead? :p
 
Last edited:
  • Like
Reactions: Jaredsk74

RogerPodacter

Senior Member
Apr 12, 2010
5,654
425
Los Angeles, CA
I'd also like to know how to go about modifying after everything has been built. I currently have 4.0.3 pulled and built on 20/12/2011 and as far as I know it built successfully because it didn't error out and everything appeared in the out folder.

You mean modifying code? Once you compile the stock AOSP code, now you can go into whatever file or driver etc, make the code change and compile and it will only compile the new change making it much quicker to compile. I'd there was a problem with your change you may error or get warnings.
 
  • Like
Reactions: scratch42069

TulpiX

Senior Member
Sep 8, 2008
89
4
You mean modifying code? Once you compile the stock AOSP code, now you can go into whatever file or driver etc, make the code change and compile and it will only compile the new change making it much quicker to compile. I'd there was a problem with your change you may error or get warnings.

I think he meant the same as i did.
Not modifying code but if you have a compile .img file, how do you add or remove files or directories from it ?

or more global where do you go from there ?
 
  • Like
Reactions: scratch42069

nprussell

Inactive Recognized Developer
Sep 18, 2009
1,296
363
I can't believe Shen kanged my guide and claimed it as his own. -_-

(I'm just trolling)
 
Last edited by a moderator:

scratch42069

Member
Dec 13, 2011
41
5
You mean modifying code? Once you compile the stock AOSP code, now you can go into whatever file or driver etc, make the code change and compile and it will only compile the new change making it much quicker to compile. I'd there was a problem with your change you may error or get warnings.

That's exactly what I wanted to know, thank you. I didn't want to have to rebuild the entire 4.0.3. pull for something minor. I'm also glad to know my build is most likely good because there were no errors during compile.
 

shenye

Inactive Recognized Developer
Oct 29, 2009
506
1,289
London
I can't seem to find the radio binaries for the VZW Galaxy Nexus, does anyone know where I can get them?

Not sure, I have sent a message to an AOSP dev to see if there should be or if it will work without them.

EDIT: Seems there are still licensing issues between Samsung and Verizon that need to be sorted before the CMDA/LTE binaries get released.
 
Last edited:

gferen

Senior Member
Nov 16, 2011
284
40
Sofia
great tutorial. one question maybe is not for this section.
if i want to compile any other version of android? lets say 2.3.7 for example.

i am noob in this things :)
 
G

GuestK0045

Guest
Ok what is the repo (sorry about being a noob) I have jdk6 installed and ubuntu 11.10 also
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 118
    Quite a few people have asked about compiling ROMs from source, so here's a guide.

    This guide is directed mainly at compiling JB or ICS for the GSM Galaxy Nexus.

    It will show you how to set up the building environment really quickly with a few simple commands in the Terminal, then show you how to sync up with the repository and compile a ROM.

    http://www.freeyourandroid.com/guide/compile-ics

    It can also be done in a Virtual Machine.

    Thanks Nathan (nprussell) for the write up!



    My XDA TV Video Guide:

    http://www.youtube.com/watch?v=H_ReU-0w4IE&feature=g-u&context=G2a40714FUAAAAAAAZAA


    ---




    Here are the steps:
    (There are additional things you can do via the link above).




    ======================

    4star.png



    IMPORTANT NOTES:

    - For the purposes of this guide, you MUST be running 64-bit Ubuntu. This can be set up on a VM (it will compile if set correctly).
    - If using a VM, ensure you give it at LEAST 2gb RAM and 2xCores (it'll take 3-4 hours at best)
    - The source download is approximately 6gb.. you're going to need 25gb HD space for a single build.

    To learn how to setup a Ubuntu 64bit VM on your Windows PC, use THIS GUIDE. I recommend using 10.04.

    So... let's assume you're running Ubuntu 64 bit for the first time, and start right from the beginning.

    NOTE : You're probably better of copying and pasting these commands, as some are quite long! All commands are in RED!


    ======================


    1. Preparing your development environment

    The very first thing you're going to need to do, is ensure you're working in a root terminal. Much like when using your Android phone, you'll want the # and not the $. In order to do this, open TERMINAL, and type:

    sudo -i

    Then type in your password. From this point forward, all of the commands in this guide assume you have root priviliges (saves typing sudo *superuser do* before everything!)

    Next, we need to add a repository so that apt-get knows where to look for Java JDK:

    add-apt-repository "deb http://archive.canonical.com/ lucid partner"

    After that, you'll need to update the repository with the following command:

    apt-get update

    Now that your repository has been updated, you can proceed with installing the required packages to make building Android from source possible. The first thing you're going to need is the Java Development Kit 6:

    apt-get install sun-java6-jdk

    Followed by (and this may already be installed depending on which version of Ubuntu you went for):

    apt-get install python

    Now you're going to need Git. Git is the revision control system.

    apt-get install git-core

    Now, you're going to pull in all the required packages needed for the build process. As I have stated already, this guide is for 64 bit ONLY. Some of these will not work on 32-bit, so if you're using 32 bit, you're reading the wrong guide (sorry)!

    apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils

    IF YOU'RE USING UBUNTU 11.10, TYPE THIS COMMAND (if not, ignore this next one)

    ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so

    Congratulations; you now have all the required packages to proceed with the next step!


    ======================


    2. Installing and initialising the repo

    Now we need to download repo, add it to our path and set the permissions . Please note that if you close terminal, you'll have to do this again. Type each command on a new line, pressing enter after each:

    mkdir ~/bin
    PATH=~/bin:$PATH
    curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
    chmod a+x ~/bin/repo


    Now we need to create a directory for where our source is going to be pulled to, and change directory to it:

    mkdir ICS_SOURCE
    cd ICS_SOURCE


    Next, you'll need to initialize the repo. There are two commands below; the top one initializes the specific branch, and the bottom is the master.

    ONLY USE ONE OF THE FOLLOWING COMMANDS (recommended - TOP)

    ICS: repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.4_r1
    Jellybean: repo init -u https://android.googlesource.com/platform/manifest -b android-4.1.2_r1

    OR:

    repo init -u https://android.googlesource.com/platform/manifest

    You will now be prompted to provide your name and email address. Please give it real details; that way you can use the gerrit code review tool if your email is connected with a Google account.


    ======================


    3. Downloading the source (sync)

    This is probably the most simple part, but depending on your connection speed, it could take a while. I am on 40mb download/10mb up, and it took about 25 mins. If you're on a typical DSL connection, expect to be waiting 60-120 minutes.

    repo sync


    ======================


    4. Obtaining proprietary binaries

    New for ICS, Android cannot just be compiled from source code only. It requires additional hardware-related proprietary libraries to run, specifically for graphics acceleration (and GSM/LTE).

    The binaries must first be downloaded from here

    Each set of binaries comes as a self-extracting script in a compressed archive. After uncompressing each archive, run the included self-extracting script from the root of the source tree, confirm that you agree to the terms of the enclosed license agreement, and the binaries and their matching makefiles will get installed in the vendor/ hierarchy of the source tree. For example... after extracting one of the files, you will have 'extract-imgtech-maguro.sh'. Simply run:

    sh extract-imgtech-maguro.sh

    From your ICS_Source directory.

    IMPORTANT NOTE : If you are building for the Nexus S, you will need the Nexus S binaries.


    ======================


    5. It's build time!

    If you're a JAVA developer, feel free to have a play with the source and make any changes you want to make at this stage. Be careful though, adding rubbish/old syntax code to the source (formatting is slightly different to gingerbread) will cause the build to fail.

    Assuming that you just want to get on with building ICS, set the build environment up with:

    source build/envsetup.sh

    Next, you'll need to lunch. I don't mean go and have a sandwich, I mean... select which device you're building for.

    NOTE - you can add other devices to this list PRIOR to proceeding with this step. If you're NOT building for the GNexus, go to the bottom of this guide and look at how to add devices to the list.

    As previously stated, we're going to assume you're building for the Galaxy nexus, so type:

    lunch

    You'll be presented with a number of options (full-eng, etc).
    ASlBF.png


    If you're building for the Galaxy Nexus (codename: Maguro), type:

    8

    (7 for Nexus S and 6 for Nexus S 4G)


    and hit enter. Now, we're ready to set the compile in motion, ladies and gentlemen. There's a lot of debate over the next bit. the -j part of the below command is technically not needed, but I have had MUCH more success compiling on a virtual machine with the -j1 added. Could be random... who knows...

    Anyway, to set your build in motion, you now have TWO options. The first option will output the build as img files. The second option will output a flashable .zip file. I recommend the latter if you intent to use CWM over fastboot.

    make -j1

    or

    make -j1 otapackage

    Congratulations - in a few hours, you should have a working AOSP build for the Galaxy Nexus!
    8
    Ok, here's what I'm doing...I downloaded the aosp source tree and compile for the toro build. I created a repo in github and pushed the frameworks/base/ to it so I can make edits and compile based from those edits. A friend told me to just repo what I want to edit. So my question is, how do I implement my repo in the build when compiling but yet pull the rest of the things I didn't change from the aosp repos? Another friend told me the default.xml but I don't know where to look for that. Any help in this matter would be most appreciated.

    Are you literally making a new project and uploading to it? Or are you going to github.com/android and forking the platform_frameworks_base from there into your git and then modyfying your own fork?

    Personally, best practice is to fork projects from github.com/android into your own repo by pressing the
    repostat_forks.png
    Fork button, then clone your own repo

    Within there, you then want to add the upstream branch, eg:

    git clone git@github.com:YourUserName/platform_manifest.git
    cd platform_manifest
    git remote add upstream git://github.com/android/platform_manifest.git
    git fetch upstream
    git merge upstream/master

    (note, I use Master branch, hence upstream/master. For other branches, simply replace master for the branch)

    Same for other projects (frameworks_base) that way, to keep up to date with google's commits too, you simply go into the folder and type:

    git fetch upstream
    git merge upstream/master

    :)

    Also, fork your own copy of github.com/android/platform_manifest

    Then to pull your own repo from git instead of Androids, edit the file platform_manifest/default.xml and include the following:

    Where it says this:
    Code:
      <remote  name="aosp"
               fetch=".."
               review="https://android-review.googlesource.com/" />
      <default revision="master"
               remote="aosp"
               sync-j="4" />

    Change it to this
    Code:
      <remote  name="aosp"
               fetch="https://android.googlesource.com/"
               review="https://android-review.googlesource.com/" />
               
      <remote  name="gh"
               fetch="git://github.com/"
               revision="master" />
    
      <default revision="master"
               remote="aosp"
               sync-j="4" />

    Then to pull your own packages (for instance, your own platform_frameworks_base, do this change:

    From
    Code:
      <project path="frameworks/base" name="platform/frameworks/base" />

    To
    Code:
      <project path="frameworks/base" remote="gh" name="PaulW/platform_frameworks_base" />

    (Change PaulW to whatever the username of your github account is)

    Hope this helps a little!
    5
    Where do I find these proprietary blobs to include?
    I only have the google-supplied extract sh-scripts..
    This explains why my gps won't work..

    You've got 2 options:

    Git clone a vendor/samsung repository into your [built root]/vendor directory.

    or

    install a working 4.0.3 rom from here plug your phone into your computer and do this:

    Code:
    cd [build root]/vendor
    rm -rf samsung
    rm -rf imgtec
    cd [build root]/device/samsung/[maguro or toro]
    ./extract-files.sh

    That'll pull the proprietary files from the working build into your vendor directory. They'll all be in vendor/samsung rather than split between vendor/samsung and vendor/imgtec but they'll all be there.

    Might be a good idea to make clean before you build again after that.
    4
    Has anyone managed to build the android-4.0.1_r1.2 branch with Ubuntu 11.10?

    I know it works on the master branch and the r1 branch supposedly didn't support it but have the build tools been updated this one?

    Just wanted to check before commiting to a massive download!

    The only thing to note with 11.10, is when you install all the build libraries, one of them is incorrect (no longer available in 11.10). Instead of installing lib32readline5-dev you need to install lib32readline-dev instead.

    Code:
    $ sudo apt-get install git-core gnupg flex bison gperf build-essential \
      zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs \
      x11proto-core-dev libx11-dev lib32readline-dev lib32z-dev \
      libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
      libxml2-utils