All credit for this goes to r2DoesInc and the OMGB team for the initial development work, and to thoughtlesskyle for bringing it to the attention of the HeroC community and performing the initial port.
For those who may be interested in building a HeroC OMGB ROM from source as a learning experience or to customize for your personal preferences, this guide should help you get started.
First of all, you will need a properly configured Linux environment. This post does not cover that, so you will need to look elsewhere (search is your friend) for help if you need help to get that setup.
The following are the commands you need (in bold) with a brief comment (# lines) before each step.
# create working directory somewhere (you will need about 10GB for building, I would recommend 15GB or more for growth)
# you can call it whatever you want, I am just using OMGB as an example
# I will later set up an env variable and refer to this directory as $OMGB_DIR
mkdir OMGB
# change to working directory
cd OMGB
# setup an environment variable for this directory called $OMGB_DIR
# you can also skip this and use full or relative paths to the appropriate directories
export OMGB_DIR=`pwd`
# initialize repo from github remote
repo init -u git://github.com/OMGB/manifest.git
# modify manifest for revision mismatches to avoid sync failures
# (change revision="master' to revision="gingerbread" for external/v8 and external/webkit projects)
# feel free to use your preferred editor, nano, emacs, ed, gedit, or whatever
vi .repo/manifest.xml
# pull source from remote repos to local source tree
repo sync
# checkout 2.3.3 version from all korg repos (from android.git.kernel.org)
# this will set the korg repos back to appropriate versions to match OMGB repos
repo forall -c git checkout android-2.3.3_r1.1
# prepare to add heroc device tree
cd device/htc
# clone HeroC Device Tree from github remote to local
git clone git://github.com/wjb/android_device_htc_heroc.git -b OMGB
# rename directory to standard heroc name
mv android_device_htc_heroc heroc
# move into device tree directory
cd heroc
# set up device specific makefiles
./setup-makefiles.sh
# prepare to copy device proprietary files to vendor tree
cd prebuilt
# copy proprietary files to vendor tree
cp -r proprietary $OMGB_DIR/vendor/htc/heroc
# go to OMGB vendor tree
cd $OMGB_DIR/vendor/omgb
# patch vendor tree to add heroc device
patch -p1 < $OMGB_DIR/device/htc/heroc/patch_vendor_omgb.txt
# move to top level build directory
cd $OMGB_DIR
# setup environment for build
. build/envsetup.sh
# choose your lunch menu
lunch OMGB_heroc-eng
# build the ROM (you can add the appropriate thread count if desired. I normally use 'make -j8 bacon')
make bacon
If none of this makes sense, you probably need to do some additional reading/searching. Hopefully, there are not too many typos/errors here, and I apologize in advance if I missed something.
As always, please help each other with issues, suggestions, improvements, etc.
Let the wild rumpus begin.
Let me be the first to say thank you, jaybob.
~ π ~
sent from GB hero.
so i am a noob and am having problems even getting the intial stuff set up (i am reading up and hopefully i will get it) i dont know if me being 32bit has anything to do with it.
but if you guys do compile a build anyway you can post it in the OMGB thread so i can put it in the OP for others to use.
also let me know what languages are present in the build.
thank you jaybob for your help in getting this ready for the HeroC
thoughtlesskyle said:
so i am a noob and am having problems even getting the intial stuff set up (i am reading up and hopefully i will get it) i dont know if me being 32bit has anything to do with it.
but if you guys do compile a build anyway you can post it in the OMGB thread so i can put it in the OP for others to use.
also let me know what languages are present in the build.
thank you jaybob for your help in getting this ready for the HeroC
Click to expand...
Click to collapse
I believe 64 bit is required for building gb. I think there is a hack for making it work on 32 though
Sent from my HERO200 using XDA Premium App
Dammit. Xp 32 bit. My girl has win 7, maybe I can convince her that she needs a linux dual boot on her laptop....
~ π ~
sent from GB hero.
ch1naski said:
Dammit. Xp 32 bit. My girl has win 7, maybe I can convince her that she needs a linux dual boot on her laptop....
~ π ~
sent from GB hero.
Click to expand...
Click to collapse
It might be easier to just set up a virtual linux environment using Virtualbox, VMware, etc. This will be a little bit slower than a native environment, but it does work. Just be sure that your virtual disk is big enough. That is often the issue with laptop environments, as they are typically more limited in storage capacity.
griffincash said:
I believe 64 bit is required for building gb. I think there is a hack for making it work on 32 though
Sent from my HERO200 using XDA Premium App
Click to expand...
Click to collapse
Haven't tried it personally, but here is a post with details on building on 32 bit.
jaybob413 said:
Haven't tried it personally, but here is a post with details on building on 32 bit.
Click to expand...
Click to collapse
Thanks for the link, I will look into building on 32 bit first, since I have an unopened 500gb hd sitting here for my pc.
~ π ~
sent from GB hero.
ch1naski said:
Thanks for the link, I will look into building on 32 bit first, since I have an unopened 500gb hd sitting here for my pc.
~ π ~
sent from GB hero.
Click to expand...
Click to collapse
What kind of cpu do you have, almost all semi modern pcs are capable of 64 bit, it doesn't matter what windows version you have
Sent from my HERO200 using XDA Premium App
jaybob413 said:
Haven't tried it personally, but here is a post with details on building on 32 bit.
Click to expand...
Click to collapse
I've been building with that 32-bit Patch since 2.3 release, haven't had a problem
i just back from a interFUSE, so ive been busy. Our main rom OMFGB is almost finished,t hen we wil start the merge for omgb. that will cut down substantially on the steps. we will also be officially supporting the hero along with the other in the coming weeks,
r2DoesInc said:
i just back from a interFUSE, so ive been busy. Our main rom OMFGB is almost finished,t hen we wil start the merge for omgb. that will cut down substantially on the steps. we will also be officially supporting the hero along with the other in the coming weeks,
Click to expand...
Click to collapse
You rock.
10 char
jaybob413 there is one mistake in your instructions. Where you say to use the command "./setup_makefiles.sh" it should be "./setup-makefiles.sh"
dastin1015 said:
jaybob413 there is one mistake in your instructions. Where you say to use the command "./setup_makefiles.sh" it should be "./setup-makefiles.sh"
Click to expand...
Click to collapse
Fixed. Thanks.
Related
Ok,let's start with kernel first....
I want this guide to be n00b friendly...so lets start!
1)Install Ubuntu 10.10 or later(virtual distro may work too!)......Ubuntu coz its easy for beginners....This guide should work on Fedora distros,but u will need to download separate packages.
Use this for samsung devices:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
2)Download the source code from opensource.samsung.com
3)Open terminal and download the the necessary tools:
For 32/64 bitsi use this)
Code:
apt-get install git-core gnupg sun-java6-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev
For 64 bits ONLY:
Code:
ia32-libs lib32z1-dev lib32ncurses5-dev gcc-multilib g++-multilib
4)Download the code soucery toochain:Toolchain
Note:This is an old toolchain.u may/should use a newer one...(optional)
ur machine is good to GO!
Ok,so i assume u have set up your machine
Now,all of the files should be placed in ~/Downloads (for my convinience to explain!but u may put it anywhere)
extract the sources and everything else u downloaded....then go into the top directory
Code:
cd Kernel
u enter into the root of the kernel directory with this
then type :
Code:
gedit Makefile
The Make file will open.........look out for this and change CROSS_COMPILE= "your toolchain path"
EXAMPLE:
Code:
CROSS_COMPILE ?= /home/sarthak/Downloads/Toolchains/arm-eabi-4.4.3/bin/arm-eabi-
This will open up the Makefile in a gedit,and the changed values will correspond to wherever u placed your toolchain................the EXTRAVERSION refers to current sub-version of your linux kernel version on ur phone
Get the config from your phone..Type:
Code:
adb pull /proc/config.gz
This will fetch a working config from the current kernel on your phone....u can alternatively make a new one with "make menuconfig"
Then gunzip it and copy it to to ur kernel source root:
Code:
gunzip config.gz
rename to .config
Now,make the necessary changes in your source.When you are done,type:
Code:
make -jX
,where X=no.op cpu threads multiplied by 1 or 2.
Sit down and have a smoke!
The resulting kernel will be in Kernel/arch/arm/boot/zImage
MORE COMING SOON!guide unfinished
reserved..................
last one!!!!!1
sakindia123 said:
last one!!!!!1
Click to expand...
Click to collapse
Sir why dont you create yourself a good Powerfull kernel for us please.............Thanks in advance
rohit589769 said:
Sir why dont you create yourself a good Powerfull kernel for us please.............Thanks in advance
Click to expand...
Click to collapse
Respect bro.
@Saki* you have any links for other toolchain compiler.
Sent from my LG-P920 using xda premium
Will this work with virtualbox as well?
bumslayer said:
Will this work with virtualbox as well?
Click to expand...
Click to collapse
yap but i think it requires a different set-up
cool sir saki
i think ill wait until i get my Comp.
we're using win7 Ult. pretty dumb =="
btw, can i be ran in Fedora?
mtvtitan said:
Respect bro.
@Saki* you have any links for other toolchain compiler.
Sent from my LG-P920 using xda premium
Click to expand...
Click to collapse
u can pick arm toolchains from Codesoucery site(google it)..
i personally use 2011.03
@bumslayer-yes it will work,but it will be slower
sakindia whats the point for this?you also try it but didnt work on flashing.so why to create unusable kernels?
sakindia123 said:
u can pick arm toolchains from Codesoucery site(google it)..
i personally use 2011.03
@bumslayer-yes it will work,but it will be slower
Click to expand...
Click to collapse
ok googling............
thanks anyway..........
bumslayer said:
Will this work with virtualbox as well?
Click to expand...
Click to collapse
sakindia123 said:
@bumslayer-yes it will work,but it will be slower
Click to expand...
Click to collapse
novaday's virtual machines does not have significant overhead, so performance degradation is negligible. Go ahead, using vm is a good choice!
Me personally using Ubuntu inside a Microsoft Virtual PC (sometimes Oracle VM VirtualBox). My suggestion is not to use the virtual machines virtual desktop it's a bit laggy, but telnet or ssh into the virtual machine, you feel more convenient.
The only drawback, than you don't have direct USB connection to the phone. You have to transfer the files between the Linux and the phone using the host OS (eg Windows).
Doky73 said:
The only drawback, than you don't have direct USB connection to the phone. You have to transfer the files between the Linux and the phone using the host OS (eg Windows).
Click to expand...
Click to collapse
I wonder whether USB support would be sufficient in VirtualBox to support the SDK. some USB devices work quite well in a VM.
But i didnt understand what is use of compiling kernel?
Kernel Compiling is not easy task like making ROM.
1st you have to understand linux enverioment
2nd you have to make Android Enverioment in linux enverioment
3rd you have to sound knowledge of C
4th you have to know how to patch kernel
5th you have to be ready to brick phone (atleast your)
so better is leave kernel stuff to a developer who understand this and enjoy either stock kernel or patched kernel which developer release frequently.
I suggessing dont go for kernel compiling if you didnt know what it is.
sajidmkhan said:
But i didnt understand what is use of compiling kernel?
Kernel Compiling is not easy task like making ROM.
1st you have to understand linux enverioment
2nd you have to make Android Enverioment in linux enverioment
3rd you have to sound knowledge of C
4th you have to know how to patch kernel
5th you have to be ready to brick phone (atleast your)
so better is leave kernel stuff to a developer who understand this and enjoy either stock kernel or patched kernel which developer release frequently.
I suggessing dont go for kernel compiling if you didnt know what it is.
Click to expand...
Click to collapse
Very well said..
i've seen many people who know the stuff but are not familiar how it works with android.....
sakindia123 said:
i've seen many people who know the stuff but are not familiar how it works with android.....
Click to expand...
Click to collapse
actually i agree w/ saki. i've visited ace's and htc evo 4g. some ppl dunno how those linux things works but thy have compiled a kernel =="
We must learn ,sudnt leave the responsibility to only a few.Also I think kernel can be ported?
premolikeshtc said:
We must learn ,sudnt leave the responsibility to only a few.Also I think kernel can be ported?
Click to expand...
Click to collapse
135MB Size of Kernel Source
2693 Directory
35492 Files
This is exact situation of 5360 Galaxy Y Kernel source which you have to mod and compile.
dude Start learning from now
---------- Post added at 06:35 AM ---------- Previous post was at 06:34 AM ----------
musashihatred said:
actually i agree w/ saki. i've visited ace's and htc evo 4g. some ppl dunno how those linux things works but thy have compiled a kernel =="
Click to expand...
Click to collapse
compile didnt take anything its just one command.
Important is patching kernel cuz without patching output will be worst then stock kernel
YEah,someone with zero knowledge wouldn't dabble into the source.....Tis guide is just a simple tut to set up the environment and compile stock zImage.
Requirements :
OS linux Ubuntu 12.04 32bits
2Gb RAM with 3Gb swap or above
Processor dual core or above
120Gb Harddisk or above
Fast internet connection ( i have no this )
First download this file
Installer SDK and Build packages by squadzone modified for me
you will get installerBuildRomGalmin.sh , run this file via Terminal on Ubuntu!
Code:
chmod a+x ~/installerBuildpackages.sh
installerBuildpackages.sh
Create the Directories
You will need to set up some directories in your build environment.
To create them:
mkdir -p ~/bin
mkdir -p ~/android/system
Install the Repository
Enter the following to download make executable the "repo" binary:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
NOTE: You may need to reboot for these changes to take effect.
Now enter the following to initialize the repository:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
repo sync -j16
Device repo !
clone its
choose branch master
put on device tree or replace totoro folder on device tree
(/device/samsung/totoro)
Vender folder clone its
pu on vendor folder !
(/vendor/samsung/totoro)
Download RomManager
NOTE: This only needs to be done when an update to RomManager is released. If you are-up-to date, you may skip to Building CyanogenMod.
Download RomManager which is needed by the build:
~/android/system/vendor/cyanogen/get-rommanager
Configure Build & Compile
Now, the environment must be configured to build and the ROM compiled, from code, for the Galaxys2.
. build/envsetup.sh && brunch totoro
Notes :
based on tutorial for galaxy mini by squadzone
the device repo created for me ( add credits if you use its )
sorry bad english !
changelog :
1.0
-initial tutorial for cm7 galaxy y ( may need some modifications! )
reserved for more updates if necessary !
Thanks for this buddy :good:
OFF : Any news about CM9 ?
wow.. reserved sir whitexp.. long time no post? D
I WIIL TRY IT BOR
By SOMKLL
But this Cyanogen has the same bugs,right?
whitexp what about cm9 ? when will u continue xD
and great guide
This message is COPYRIGHTED to me and stolen from:My post
Cyanogen 7/9 only get developed again when the gpu driver become released
Awesome tutorial sir...
Just one question...if we still have GPU restrictions while compiling CM7/9/10, then what is the use of the tutorial? Is there any update I should be aware of?
I'm not at all disrespecting OP's efforts...I respect him...he is doing commendable job for this device..hat's off! this question is just out of curiosity!
everyone needs brodcom drivers,without it nothing is possible.
PREMOLIKES said:
everyone needs brodcom drivers,without it nothing is possible.
Click to expand...
Click to collapse
Well it's still possible to boot it, so yeah. It's a handy tutorial, LEARN to appreciate guys! That's the reason why SGY devs are leaving, 1 by 1, because of you people that whine! Thank them for the effort!
PREMOLIKES said:
everyone needs brodcom drivers,without it nothing is possible.
Click to expand...
Click to collapse
Without this kind of tutorial and with gpu drivers will you make cm7 for sgy????
Awesome tutorial sir!!
Tutotial is good.no doubt.I said drivers are a stumbling block.
PREMOLIKES said:
Tutotial is good.no doubt.I said drivers are a stumbling block.
Click to expand...
Click to collapse
Drivers will be here soon! I am gettin ready already!
Sent from my GT-S5360 using XDA
Mohamed.Anwar said:
Thanks for this buddy :good:
OFF : Any news about CM9 ?
Click to expand...
Click to collapse
what gaming rom r using
Exellent tut buddy.:thumbup::thumbup:
sent while doin' some burnouts
hell_lock said:
Drivers will be here soon! I am gettin ready already!
Sent from my GT-S5360 using XDA
Click to expand...
Click to collapse
really?
broadcom will release their drivers or are you just joking around because i just installed windows again on my pc ...
cosminx13 said:
really?
broadcom will release their drivers or are you just joking around because i just installed windows again on my pc ...
Click to expand...
Click to collapse
A suggestion from me.you can use both os like dualboot.for info about this try google
MANY GREEEEETZ!!!
Hello guys i'm here with my first guide of how to build cyanmobile from source for galaxy fit ......
As you all might know cyanmobile went opensource thanks to squadzone now we can compile it from source with our own modifiactions.....
Requirements
1)Linux machine (recommended 64bit and ubuntu) with atleast 50gb free space
2)Common sense of how to use google and fix errors
3)Basic knowledge of git and its commands
4)A possibilty of bricking your fit
5)A fast and stable internet connection
now lets get started
Assuming we have linux installed
installing required build packages
from terminal
HTML:
sudo apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev sun-java6-jdk pngcrush schedtool
Note:- All the packages are important dont skip any of them
now making the directories to download the source
HTML:
mkdir -p ~/bin
mkdir -p ~/android/system
here mkdir stands for make directory
~ refers to your home folder (incase if you are a beginner)
Next
making the repo command executable
copy paste this terminal
HTML:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
Reboot your system after executing this
This defines the repo command or the repo command usable on your machine
chmod is giving permissions to the folder a+x is the permissions given don't go deep into this.
Next
Downloading the source
i will be referring execute to copy pasting in the terminal
HTML:
repo init -u git://github.com/CyanMobile/android_cyanmobile.git -b gingerbread
now
repo sync
alternatives
repo sync -jx
here x can be anything depends on your internet speed ther will x number of simultaneous download if you use the arguement
like if you use
repo sync -j4
There will 4 downloads going on simulatneously
Next after the source has been downloaded you will find someting like this...
syncing working tree 100
now you have the source downloaded
Preparing the build environment
install java jdk6 or jdk 5 using this tutorial
http://codingforme.wordpress.com/2012/05/14/installing-oracle-java-jdk-6-or-7-on-ubuntu-12-04/
Install the android sdk following this tutorial
http://www.howtoforge.com/setting-up-an-android-app-build-environment-with-eclipse-android-sdk-phonegap-ubuntu-11.04
not testsed on jdk 7 so better use 6 or 5
fix its path using "export PATH=$PATH:"ur sdk path""
ur sdk path depends on where you install it
install adb using this guide
http://forum.xda-developers.com/showthread.php?t=921169
Connect your phone with usb debugging enabled and execute this
preferable do this when you are on a cm based rom ..
HTML:
adb devices
if you see something like this its working for you
HTML:
List of devices attached
S5670efac482b device
now go to device > samsung > beni execute extract-files.sh as root use sudo and drag that to terminal and hit enter
now cd into the root of your source folder
HTML:
cd ~/android/system
then
HTML:
source buid/envsetup.sh
HTML:
lunch
you will see all the build properties something like this
HTML:
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=2.3.8
TARGET_PRODUCT=cyanogen_beni
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=false
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv6-vfp
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=GINGERBREAD
now type make -jx otapackage
x depends on your hardware more it is faster the build
you will find the built one in out/samsung/beni /cm--xxx.zip
Flash it and enjoy
credits
wilfredcool007
vishwanthptl
sakindia123
yajnab
ravi h basawa
adit_pat
squadzone
google
xda
without these guys it wouldnt be possible pree thanks for them plz
1 st reserved
Thumbs up
Nice guide ajay :good:
Its same as the building of cyanogenmod. But to continue this thread u have to first build a copy too for promoting this and the errors while building , so start repo syncing. I am syncing the jelleybean now.
Best of luck for this thread
yajnab said:
Its same as the building of cyanogenmod. But to continue this thread u have to first build a copy too for promoting this and the errors while building , so start repo syncing. I am syncing the jelleybean now.
Best of luck for this thread
Click to expand...
Click to collapse
i am too doing a list of common errors encountered and will update the op
speed_bot said:
i am too doing a list of common errors encountered and will update the op
Click to expand...
Click to collapse
I'm on a low bandwidth. Can u please make a highly compressed .uha or Uharc compression package of the cyanmobile so that i can also help u in building this. not having the cm7 sources too. It cn be a grat sart for making a more modified cyanombile than squadzone.
yajnab said:
I'm on a low bandwidth. Can u please make a highly compressed .uha or Uharc compression package of the cyanmobile so that i can also help u in building this. not having the cm7 sources too. It cn be a grat sart for making a more modified cyanombile than squadzone.
Click to expand...
Click to collapse
dude do this remove all devices and sync only beni and tass the source is small and use aosps prebuilt the download is only 3gb bro...and can plz upload the prebuilt directory for me i will upload frameworks and devices by tmrw for you..........plz i need the prebuilt directory
You rock man, keep up the good work.. thank you..
praveen_kalasa said:
You rock man, keep up the good work.. thank you..
Click to expand...
Click to collapse
thanks bro..
Nice Work
Very useful Guide for Begineers. Keep this thread updated
RishabhAd said:
Very useful Guide for Begineers. Keep this thread updated
Click to expand...
Click to collapse
but only few people responded to it so what can i update with
??
hi.i am trying to build from your how to...will report ...thank you for this...
desalesouche said:
hi.i am trying to build from your how to...will report ...thank you for this...
Click to expand...
Click to collapse
im already compiling for your device
How to build cyanmobile x from source for p500?
thanks
x-dira said:
How to build cyanmobile x from source for p500?
thanks
Click to expand...
Click to collapse
just choose p500 during lunch
building for huawei u8800pro and u8860
hi can i build with 3.0.87 kernel?
or should i use a 2.6.35 one?
can we build only gingerbread or is there possibility to build 4.2.2?
thank you
Nice guide :thumbup:
I'll try it for GalaxyW
desalesouche said:
hi can i build with 3.0.87 kernel?
or should i use a 2.6.35 one?
can we build only gingerbread or is there possibility to build 4.2.2?
thank you
Click to expand...
Click to collapse
u need kernel 2.6 for gb 3.x supports only ics and above.android 4.2.2 is buildable provided u have all drivers and other binaries
K_TECH said:
Nice guide :thumbup:
I'll try it for GalaxyW
Click to expand...
Click to collapse
dude this guide is for galaxy fit but u can build it for w or any device by using the tress specific for that device.
Bump
I wanna try to port this ROM to the LG e739, but I have no idea what to do at this point. I downloaded the sources, but the device tree I have from cm7.2 is just plain, it lacks everything else the other devices have and to be honest I'm overwhelmed. Any help is greatly appreciated
This is a PURE AOSP ROM build guide. I have opted not to post an actual AOSP ROM based on 6.0.0 due to the fact I just dont care for it much. The instructions are up to date as of 10/21/2015
Deprecated-> This thread is about learning to build your own ROM following the instructions in post #2. The ROM posted in this thread is for example output. Feel free to download and use the ROMS @GROGG88 and I build! Feel free to try and build your own. We will try to help!
Quick Change Log
10/21 - Updated guide to reflect Android version 6.0.0_r1. No ROM for download (at this time).
1/17 - Updated build with official 5.0.2 Binaries. Fixed Browser "Settings" crash.
12/19 - Updated my Flo builds to Android 5.0.2_r1
12/9 - Updated my Flo build. Will not be doing a Deb Build any more.
12/2 @GROGG88 has updated his builds. I have not! I will update tomorrow. I did however get thefactory stock rooted ROM up HERE!
11/18 - @GROGG88 and I have joined forces to create two ROMS! I will be creating PURE AOSP ROMS and he will be creating Modified ROMS with many useful features! Each ROM can als be user built because all commits are shared in post #2!!!
11/15 - B8 - Updated the 5.0.0_r6. Deb is only using preview binaries due to lack of final binary files.
11/14 - B7 - Updated the 5.0.0_r5. Deb is only using preview binaries due to lack of final binary files.
11/10 - B6 - File system install instead of block install, Added Google Location Services to framework, Fixed a root issue that couple DEB users were having
11/9 - B5 - Changed wallpaper again. Fixed stock recovery at source level (Thanks to @Gnome and @GROGG88)
11/8 - B4 - Changed wallpaper to android 5 Wallpaper, fixed reverting to stock recovery (No need for save-recovery.zip), pre-rooted boot.img (No need for extra boot.img!)
11/7 - B3 - Removed it. Bad files. Reverted back to Build 2.
11/5 - B2 -- Fixed MTP bug that google has left in every version of AOSP, made ROM recovery flashable and added 2 zips to the OP
11/4 - B1 - Update to 5.0.0_r2. PC install via fastboot
Additional Downloads
Root by @Chainfire HERE!
Gapps for Lollipop HERE! There may be others so shop around!
Stericson's Busybox in flashable zip format is attached! Thanks to @Stericson for the binaries!
@GROGG88's Special Builds are HERE!
MOD EDIT: Link removed as domain has expired. Thread closed until new links can be installed
Please hit Thanks! It just as easy as hitting Download!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Ubuntu 14.04 Set up and Build Guide
Updated 11/05/2014
Feel free to ask any questions about the build process. Do not ask questions about Ubuntu!
This guide assumes the following
Have Ubuntu 14.04 setup, fully operation, and up to date. Hard Machine or Virtual, makes no difference. Must meet the minimum specs for compiling. Info from Google HERE
Understand terminal command line entry as this is all command line processors.
You are not here to ask for help with Linux, only the Android build process!
Add Java
Code:
sudo apt-get install openjdk-7-jdk
Add Build tools (Adds the required packages at the time of this posting)
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
Add Repo command (Syncs Google Repository with your local machine)
Code:
mkdir ~/bin && curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo
Add bin folder to path for repo command (After you do this close Terminal and re-open to institute changes (easy way))
Code:
sudo gedit .bashrc
export PATH=~/bin:$PATH <-(add to end of bashrc)
Identify Yourself to the Repo (One day you may make commits so think about that when choosing your info!)
Code:
git config --global user.email "[email protected]"
git config --global user.name "yourpreferredusername"
Synch Repo (Download source... Sit back and grab a pop and a sandwich...)
Code:
mkdir ~/AOSP
cd ~/AOSP
repo init -u https://android.googlesource.com/platform/manifest -b android-6.0.0_r1
repo sync
Note: I use AOSP as my directory name. You can use what you want. You could use "aosp" or "Source" or "android" or "whateveryoulike"
Install proprietary binaries (Needed for things like GPS and Bluetooth, they are not Open Source like android) (Install proprietary binaries from here in the root of AOSP folder (or whatever you called yours))
Code:
[url]https://developers.google.com/android/nexus/drivers[/url]
Run envsetup.sh
Code:
source build/envsetup.sh
Choose Device
Code:
lunch
Build it!
Code:
make -j8 otapackage
See Build Notes and ramblings from me in post #3!
Notes
The ROM build will be a PURE AOSP ROM with no Gapps at all. See links in post #1 to PA Gapps for a good set of Google Apps!
The ROM will also have terminal level SU. So becareful! In other words its fully rooted and could be open to vulnerabilities. Flash your favorite Superuser Package if you need it. I dont. I recommend SuperSU by @Chainfire HERE. Download the flashable zip and flash after you flash ROM.
make -j8 is the number of worker threads that the make command will use to build. To me 8 is a safe number for an i7 processors. For an i5 Processor I would use -j4. I have experimented with a multitude of different values and it seems to me that the number of logical cores is also the best number to use with the make command.
Google recommends between -j24 and -j32 (to me that is excessive and causes my machine to error out every once in a while). Keep in mind the higher you push the more load the CPU will undertake. If your O/C'ing real hard you better have some nice cooling! I had to cut back OC on my 4770k from 4.65 to 4.4 with a Corsair H60 cooler just so it wouldn't over heat. When in doubt start low.
My i7 machine clocked at 4.4 and 16 gigs of RAM on a Samsung 840 Pro 256 Gig SSD take about 38 minutes to build the entire ROM.
With a 50 Meg download link it took maybe 30 to 45 minutes to sync the repo.
Changes from Source
Check out @GROGG88 patches HERE!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Mindrocket said:
Right on Scott! Can't wait to give it a spin.
---------- Post added at 07:37 PM ---------- Previous post was at 07:15 PM ----------
Security settings crashes says"unfortunately settings has stopped" .
Click to expand...
Click to collapse
I think its the same error some other folks are facing. Rascarlo and a few others would release their AOSP builds but it appears this blocks them from releasing. Read this over on a few pages on a few ROMs in this neighborhood.
whoamanwtf said:
I have faith in you making it work
Click to expand...
Click to collapse
Can anyone post a snippet of logcat during the crash? Particular the actually error itself.
Place it in the
Code:
box if you can.
If not I get out of work in a few hours and can look then...
mjwhirly said:
Nice to see you venturing into new projects. Most people start with CM since its not to hard to compile, but you did it the opposite way which will make all the difference in the end
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
IMHO: If you dont start with the basics you will end in a mess
got to try this as your clean rom works well iam sure this one will be great also
keep up the great work to you and who helps you.
Where would i start to try baking my own cake .. i use archlinux what programs needed to do a build
rocksyjj said:
got to try this as your clean rom works well iam sure this one will be great also
keep up the great work to you and who helps you.
Where would i start to try baking my own cake .. i use archlinux what programs needed to do a build
Click to expand...
Click to collapse
Never used archlinux but I used Ubunutu 13.04
Here is where I started: http://forum.xda-developers.com/showthread.php?t=2224142
(I hate nano so used gedit of course. )
But at the last two shell commands i didint use the AOKP tree I used the AOSP base so you want to look here for that: http://source.android.com/source/downloading.html
Then follow the instructions from that page on forward until you have yourself a ROM :highfive:
Also pay attention to the blurb about proprietary binaries
Obtaining proprietary binaries
The Android Open-Source Project can't be used from pure source code only, and requires additional hardware-related proprietary libraries to run, specifically for hardware graphics acceleration.
Official binaries for the supported devices can be downloaded from Google's Nexus driver page, which add access to additional hardware capabilities with non-Open-Source code.
When building the master branch for a device, the binaries for the most recent numbered release or with the most recent date are the ones that should be used.
Click to expand...
Click to collapse
There is a link for the Nexus binaries in that blurb. Make sure you install them before building and you are good.
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
scrosler said:
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
Click to expand...
Click to collapse
You fixed the security settings fc! Mind sharing how you managed to fix that?
Sent from my Nexus 7 using Tapatalk 4
scrosler said:
Also pay attention to the blurb about proprietary binaries
There is a link for the Nexus binaries in that blurb. Make sure you install them before building and you are good.
Click to expand...
Click to collapse
Where is the link to download the Nexus binaries btw? I didn't see a proprietary binaries blurb in the above 2 links.
Thanks.
vibranze said:
Where is the link to download the Nexus binaries btw? I didn't see a proprietary binaries blurb in the above 2 links.
Thanks.
Click to expand...
Click to collapse
Its under the actual "Building for devices" page...
http://source.android.com/source/building-devices.html
Wich leads to...
https://developers.google.com/android/nexus/drivers
scrosler said:
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
Click to expand...
Click to collapse
Hi Scott. Where is the download link for this one? I think a few folks would love to know the fix for the security fc since last I read it was blocking their update as well. Definitely want to try the aosp one.
Sent from my Nexus 7 using XDA Premium 4 mobile app
scrosler said:
Its under the actual "Building for devices" page...
http://source.android.com/source/building-devices.html
Wich leads to...
https://developers.google.com/android/nexus/drivers
Click to expand...
Click to collapse
hi scott,
could you please share the sources you build from? and specifically how you fixed the Security settings FC?
thanks.
vibranze said:
Thanks Scotts, appreciated your fast response. :good:
Click to expand...
Click to collapse
Your welcome!
mpmilestogo said:
Hi Scott. Where is the download link for this one? I think a few folks would love to know the fix for the security fc since last I read it was blocking their update as well. Definitely want to try the aosp one.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Its in the OP. Post 1. I just changed the link. Happy downloading!
TheDarkDefender said:
hi scott,
could you please share the sources you build from? and specifically how you fixed the Security settings FC?
thanks.
Click to expand...
Click to collapse
The source is the AOSP tree and it can be found here: http://source.android.com/source/downloading.html (thats all I am using).
Fixing the Settings F/C was creative... had to Google to get the answer, lol
Here is what I found...
CM 10.2 initially had this issue as its based from AOSP like this rom (SOURCE). They did not explain a fix... Also, note this is a less than one week old issue. So I continued on with Google... (Google is a son of a ***** when you need it )
Then found this thread on XDA from the Nexus 4 about an update to 4.2.2 HERE! This started to make sense as they posted a fix for the N4. HOWEVER that fix was not applicable to our N7.2 because we did not have the keymaster files on the vendor partition!!!
So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM. VIOLA! It worked and solved the problem.
Now I will admit I am not sure why these files are not in the AOSP source tree as I am still learning... If you can shed more light then please do! But I do know that it fixed the issue. Was not seemingly prevalent before October 2nd (or maybe it was but thats when it was reported on CM10.2) and moving those files into the ROM base resolved (granted they are not in the same spot as the N4).
Please feel free to share anything you know in this thread.
scrosler said:
Your welcome!
Its in the OP. Post 1. I just changed the link. Happy downloading!
Click to expand...
Click to collapse
Thanks Scott. I think I found something rather strange with my tablet with just about any of the AOSP builds. I found this on another as well. It seems whenever I enable locations in chrome or chrome beta the tablet soft resets immediately. If I turn off location reporting, nothing happens but I get no location updates. I decided to restore things using the factory images. For the umpteen thousandth time, thanks to the Android team for providing the safety net!
Gonna try again later today and see if this issue persists after resetting the device to the factory image and reflashing the AOSP build.
mpmilestogo said:
Thanks Scott. I think I found something rather strange with my tablet with just about any of the AOSP builds. I found this on another as well. It seems whenever I enable locations in chrome or chrome beta the tablet soft resets immediately. If I turn off location reporting, nothing happens but I get no location updates. I decided to restore things using the factory images. For the umpteen thousandth time, thanks to the Android team for providing the safety net!
Gonna try again later today and see if this issue persists after resetting the device to the factory image and reflashing the AOSP build.
Click to expand...
Click to collapse
No this very possible depending on the GAPPS used. I think this is more a GAPPS issue then a ROM issue. I cant say for sure but I might have time to look later.
If someone else knows then do tell.
However I dont much care for Chrome on mobile (love it on PC) so I use AOSP and it runs well. But have not tested location.
Im sure a fix can be found with enough effort.
scrosler said:
No this very possible depending on the GAPPS used. I think this is more a GAPPS issue then a ROM issue. I cant say for sure but I might have time to look later.
If someone else knows then do tell.
However I dont much care for Chrome on mobile (love it on PC) so I use AOSP and it runs well. But have not tested location.
Im sure a fix can be found with enough effort.
Click to expand...
Click to collapse
Interesting. I've tried the BANKS minimal GAPPS core and photosphere as well as the goo.im gapps in clean flashes of other aosp based ROMs but still had the same issue. Perhaps I'll try the PA gapps next since they seem to have everything in them. Gonna give the whole thing a try a bit later today as well. I'm lucky enough to have two Nexus 7 tablets so one has your latest CleanROM on it which I love! The other seems to have descended into flashing heaven or the other place .
Any help appreciate on the issue though. I'd love to run AOSP on the second tablet since one of them is destined for my daughter when she realizes she wants one.
scrosler said:
The source is the AOSP tree and it can be found here: http://source.android.com/source/downloading.html (thats all I am using).
Fixing the Settings F/C was creative... had to Google to get the answer, lol
Here is what I found...
CM 10.2 initially had this issue as its based from AOSP like this rom (SOURCE). They did not explain a fix... Also, note this is a less than one week old issue. So I continued on with Google... (Google is a son of a ***** when you need it )
Then found this thread on XDA from the Nexus 4 about an update to 4.2.2 HERE! This started to make sense as they posted a fix for the N4. HOWEVER that fix was not applicable to our N7.2 because we did not have the keymaster files on the vendor partition!!!
So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM. VIOLA! It worked and solved the problem.
Now I will admit I am not sure why these files are not in the AOSP source tree as I am still learning... If you can shed more light then please do! But I do know that it fixed the issue. Was not seemingly prevalent before October 2nd (or maybe it was but thats when it was reported on CM10.2) and moving those files into the ROM base resolved (granted they are not in the same spot as the N4).
Please feel free to share anything you know in this thread.
Click to expand...
Click to collapse
Thank you very much. Did you figure out the commit in the CM repo that actually solved this issue?
Also, what do you mean by So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM ? Could you elaborate please?
I'd be happy to share anything I get to know about this. Been researching about this too. Thanks.
Hi,
New to building Android and want to build the code by cr3pt for the p700.
I have check out the base CM 11 code but I am guessing there is additional code by cr3pt to build the LG 7 p700 parts. Are these available to download and if so where?
I am assuming, and I could be wrong, that either the additional code is independant of the base code or the two can be merged. I have never used GIT so it is all a bit new but I am sure it will be no harder than svn (probably easier).
Any howtos gratefully received.
Thanks,
bibble_235 said:
Hi,
New to building Android and want to build the code by cr3pt for the p700.
I have check out the base CM 11 code but I am guessing there is additional code by cr3pt to build the LG 7 p700 parts. Are these available to download and if so where?
I am assuming, and I could be wrong, that either the additional code is independant of the base code or the two can be merged. I have never used GIT so it is all a bit new but I am sure it will be no harder than svn (probably easier).
Any howtos gratefully received.
Thanks,
Click to expand...
Click to collapse
You can check out xda university.
But the basics are a kernel that works, correct libs for accessing your devices hardware, and using logcat/dmesg/strace to debug everything else.
I have never used git either, but kgit is a nice kde gui for git.
You should look around for tutorial's on git. (There has got to be one.)
Lgrootnoob said:
You can check out xda university.
But the basics are a kernel that works, correct libs for accessing your devices hardware, and using logcat/dmesg/strace to debug everything else.
I have never used git either, but kgit is a nice kde gui for git.
You should look around for tutorial's on git. (There has got to be one.)
Click to expand...
Click to collapse
Thanks this is a fine place to start.
Good place to start indeed. Sound like all I need to do is change
lunch cm_i9100-userdebug
to
lunch cm_p700-userdebug
I wouldn't know. Im not a rom dev. But I do know that for testing builds, the userdebug will have adb and everything ready.
So you got that right.
Anyways, you can use the tool in my signature to help debug your rom.
It has strace, auto logcat capture, and is about to add auto dmesg but you can do that by typing.
Code:
adb shell dmesg | more
or for output to notepad
Code:
(adb shell dmesg > dmesgout.txt)&(notepad dmesgout.txt)
Just not in linux though.
If you plan on becoming a rom dev full on, then you can link to my post and have your windows users collect logcats with my tool (For eaasy debugging) and upload the txt file output.
Code:
lgctnp
Well lunch did not work. Guessing the p700 code is not on the cm11 branch
Sent from my GT-N8013 using Tapatalk
bibble_235 said:
Well lunch did not work. Guessing the p700 code is not on the cm11 branch
Sent from my GT-N8013 using Tapatalk
Click to expand...
Click to collapse
This is what I want I think, I case others find my thread.
http://forum.xda-developers.com/showthread.php?t=2329641