How to build your own CyanogenMod 7:
Install the Build Packages
Install using the package manager of your choice:
For 32-bit & 64-bit systems:
Code:
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
For 64-bit only systems:
Code:
g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline5-dev gcc-4.3-multilib g++-4.3-multilib
NOTE: gcc-4.3-multilib g++-4.3-multilib is no longer available for Ubuntu 11.04 64-bit, but should still build without issue.
NOTE: On Ubuntu 10.10, and variants, you need to enable the parter repository to install sun-java6-jdk:
Code:
add-apt-repository "deb http://archive.canonical.com/ maverick partner"
Create the Directories
You will need to set up some directories in your build environment.
To create them:
Code:
mkdir -p ~/bin
mkdir -p ~/android/system
Install the Repository
Code:
curl "http://php.webtutor.pl/en/wp-content/uploads/2011/09/repo" > ~/bin/repo
chmod a+x ~/bin/repo
PATH=~/bin:$PATH
Now enter the following to initialize the repository:
Code:
cd ~/android/system/
repo init -u git://github.com/ProTekk/android.git -b gingerbread
repo sync -j16
Copy proprietary files
Code:
git clone git://github.com/koush/proprietary_vendor_htc.git ~/android/system/vendor/htc
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:
Code:
cd ~/android/system/device/htc/mecha
~/android/system/vendor/cyanogen/get-rommanager
Check for updates
First, check for updates in the source:
Code:
cd ~/android/system/
repo sync
Configure Build & Compile
Now, the environment must be configured to build and the ROM compiled, from code, for the Thunderbolt.
Code:
. build/envsetup.sh && brunch mecha
Now for the lazy people who don't want to type all that crap:
Download and run the new script: http://fzservers.com/newmecha.sh
You can do whatever you like while it runs. If you have never created a CyanogenMod repo on your local system then go out to dinner, grab some coffee, call your mother or do something time consuming because this will be a LONG wait depending on your Internet connection and system performance. The build will run as soon as the script sets everything up and again it is LOOOONG depending on the performance of your system.
Everything will be located in
Code:
~/android/system
Once it's done you can locate the flashable .zip in the "out" directory of your CyanogenMod repo. Happy crackflashing to all!
Reserved....
Fixed an issue with the build script. Please redownload it and try again.
Please not that i don't take credits for this tutorial its dastin1015 who made this! but as many people don't look in other forums except the forum for their devices i would like to give you the info here about how to build JB from source
Original Thread;Here=)
dastin1015 said:
To compile Jellybean on Ubuntu I'm going to first give you steps to set up your computer to get this thing rolling. Also note that this appears to be a development preview source code.
This will NOT make a fully functional ROM, but will give you a place to start. Also I CANNOT fix every error you run into.
Note: The source download is approximately 6GB in size. You will need 25GB free to complete a single build, and up to 80GB (or more) for a full set of builds.
1) You need the following:
-JDK 6 if you wish to build Jellybean. You can download it from java.sun.com. Or:
Code:
$ sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"
$ sudo apt-get update
$ sudo apt-get install sun-java6-jdk
-Python 2.4 -- 2.7, which you can download from python.org. Or:
Code:
$ sudo apt-get install python
-Git 1.7 or newer. You can find it at git-scm.com. Or:
Code:
$ sudo apt-get install git-core
-Android SDK:
Download the SDK here: http://developer.android.com/sdk/index.html
Extract the SDK and place it in your home directory.
I renamed my SDK to android-sdk to make it easier to navigate to.
Go to your home folder, press Ctrl+H to show hidden files, and open up your .bashrc file.
Add these lines at the bottom of the file:
Code:
# Android tools
export PATH=${PATH}:~/android-sdk/tools
export PATH=${PATH}:~/android-sdk/platform-tools
export PATH=${PATH}:~/bin
Find your .profile file and add this at the bottom of the file:
Code:
PATH="$HOME/android-sdk/tools:$HOME/android-sdk/platform-tools:$PATH"
You have now successfully installed the Android SDK.
To check for updates issue this into your terminal:
Code:
$ android
2) Install required packages. 64-bit (recommended)
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 lib32readline5-dev lib32z-dev \
libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
libxml2-utils
On newer versions of Ubuntu such as 11.10 you may need to do the following:
Code:
$ sudo ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so
Building on Ubuntu 12.04 is currently only experimentally supported and is not guaranteed to work on branches other than master.
Code:
$ sudo apt-get install git-core 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 openjdk-6-jdk tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
3) Configure your USB.
Code:
$ gksudo gedit /etc/udev/rules.d/51-android.rules
Inside of this blank text file insert:
Code:
#Acer
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
#Samsung
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
4) Save the file and close it and then issue this command: [CODE]$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
5) Install the repo:
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
6) Initialize the repo:
Code:
$ mkdir WORKING_DIRECTORY
$ cd WORKING_DIRECTORY
$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.1.1_r1
6.1) For people who have already done a repo init:
Code:
$ cd WORKING_DIRECTORY
$ repo init -b android-4.1.1_r1
$ repo sync
7) When prompted, enter your real name and email address.
8) Gather the files: [CODE]$ repo sync
9) Compiling:
Code:
$ source build/envsetup.sh
Or:
Code:
$ . build/envsetup.sh
10) Issue:
Code:
$ lunch
11) Pick your poison.
12) Now issue (The '#' is the number of cores your processor has plus 1, ex. I have a dual core processor so I type 'make -j3':
Code:
$ make -j#
~How To Add A Device To The List~
1) Find the github for your device you wish to add. (For me it is the HTC Evo 3D CDMA)
2) Now navigate to the location you are going clone the device tree to:
Code:
$ cd WORKING_DIRECTORY/device
$ mkdir samsung
3) Clone the github device tree from remote to local: (The shooter would be whatever you want that folder to be named so make sure it is whatever standard name would be for your device, example: Nexus One [passion], Nexus S [crespo], Motorola Droid [sholes], HTC Incredible [inc], etc.)
Code:
$ git clone git://github.com/CyanogenMod/android_device_htc_shooter.git shooter
4) Now navigate into the folder:
Code:
$ cd shooter
5) Connect phone to computer and make sure USB debugging is enabled and you have adb set up.
6) Extract Device Proprietary Files:
Code:
$ ./extract-files.sh
7) Navigate back to your home directory for building:
Code:
$ cd ~/WORKING_DIRECTORY
8) Prepare To Compile:
Code:
$ source build/envsetup.sh
Or:
Code:
$ . build/envsetup.sh
9) Get your list of devices:
Code:
$ lunch
10) Pick your poison.
11) Now compile:
Code:
$ make -j#
Or for a flashable zip:
Code:
$ make -j# otapackage
~NOTE~
If you are running into issues such as:
Code:
Which would you like? [full-eng] 5
build/core/product_config.mk:209: *** No matches for product "full_shooter". Stop.
Device shooter not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for shooter not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:209: *** No matches for product "full_shooter". Stop.
** Don't have a product spec for: 'full_shooter'
** Do you have the right repo manifest?
What you need to do is to edit your blob to match the PRODUCT_NAME to the file name. For example with mine I have full_shooter.mk therefore in this file I need to have PRODUCT_NAME to match it. Whatever error it is looking for you just need to change the PRODUCT_NAME line to match what the error shows.
Click to expand...
Click to collapse
reserved for Q/A
It's frowned upon to re-distribute threads across multiple forums, trust me it wasn't allowed for a thread compiled by RC's so the same will go for this and any other thread especially one that was published on the portal as has been made aware to alot of people. Regardless of them reading other forums its clear to see thanks to the new 2013 theme having the new sidebar with top stories where I saw it earlier today. Just a heads up
AvRS said:
It's frowned upon to re-distribute threads across multiple forums, trust me it wasn't allowed for a thread compiled by RC's so the same will go for this and any other thread especially one that was published on the portal as has been made aware to alot of people. Regardless of them reading other forums its clear to see thanks to the new 2013 theme having the new sidebar with top stories where I saw it earlier today. Just a heads up
Click to expand...
Click to collapse
theres alot of people like me who never goes to the porta, dunno why tough
LastStandingDroid said:
theres alot of people like me who never goes to the porta, dunno why tough
Click to expand...
Click to collapse
Either way if it's already posted somewhere it's not advised to repeat the information in device specific forums as it's not device specific and why it's been put in a general section.
Yeah, listen to AvRS, you can face some warnings because it counts as duplicate thread spam. Calling a mod here to decide. Thanks! :good:
protomanez said:
Yeah, listen to AvRS, you can face some warnings because it counts as duplicate thread spam. Calling a mod here to decide. Thanks! :good:
Click to expand...
Click to collapse
thats amazing i never heard of it,
ill make this as much as possible for the SII
Thread closed
AvRS said:
Either way if it's already posted somewhere it's not advised to repeat the information in device specific forums as it's not device specific and why it's been put in a general section.
Click to expand...
Click to collapse
protomanez said:
Yeah, listen to AvRS, you can face some warnings because it counts as duplicate thread spam. Calling a mod here to decide. Thanks! :good:
Click to expand...
Click to collapse
LastStandingDroid said:
thats amazing i never heard of it,
ill make this as much as possible for the SII
Click to expand...
Click to collapse
And the mod has decided, as stated above, the thread is in General for a reason, it's applicable across phones.
LITESTALK
Litestalk is for users who want a stable better batttery life more free ram pleasent kitkat experience overall
for thier devices it is the rom based on "What u See is What u Get conecpt" a simple rom which user can customise it like he want
So your interested in Building..! Follow this guide! For any 2011 xperia device!
Setup to build - This section can be skipped if youve ever built anything before. This is for first time build setup.
1. From your root terminal location, type the following:
Code:
sudo apt-get install curl 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 g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline5-dev gcc-4.3-multilib g++-4.3-multilib
Download google repo tool
2. Type: mkdir ~/bin
3. Type: PATH=~/bin:$PATH
4. Type: curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
5. Type: chmod a+x ~/bin/repo
Code:
[B][U]From terminal[/U][/B]
1. mkdir kk
2. cd kk
3. mkdir system
4. cd system
5. repo init -u git://github.com/LiteStalk/android.git -b cm-11.0
8. repo sync
9. curl https://raw.github.com/LegacyXperia/local_manifests/cm-11.0/updates.sh > ~/beanstalk/system/updates.sh
10. chmod a+x updates.sh
11. ./updates.sh
12. cd ~/kk/system/vendor/cm
13. ./get-prebuilts
14. cd ~/beanstalk/system
15. . build/envsetup.sh
16. breakfast anzu
17. brunch anzu
- you can chnage device name to yours
How to AICP11 6.0 for I9300
You need:
PC/Laptop with 4GB RAM
Good internet connection
Linux 64 Bit
Open the Terminal in your Linux distribution and copy the following command:
Code:
sudo apt-get install bison build-essential curl flex git gnupg gperf libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop openjdk-7-jdk openjdk-7-jre pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev
Creating directories:
Code:
mkdir -p ~/bin
mkdir -p ~/AICP
Install repo:
Code:
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
Initialize the AICP source repository:
Code:
cd ~/AICP
repo init -u https://github.com/AICP/platform_manifest.git -b mm6.0
Download the source code:
Code:
repo sync
Download device-specific files:
Code:
. build/envsetup.sh
breakfast i9300
Start the build:
Code:
brunch i9300
Build will be in: AICP/out/target/product/i9300
Reserved
Reserved
How To Build MoKee Rom For Exynos5420 Device (7.1.2)Support Device :
HTML:
klimtwifi # Samsung T700
klimtlte # Samsung T705
chagallwifi # Samsung T800
chagalllte # Samsung T805
chagallltetmo # Samsung T807T
ha3g # Samsung Note3 (N900)
Step 1: Setting Up A Compile Environment
You must have a 64-bit environment.
A Linux computer should have 8 GB RAM or more, otherwise build errors may occur.
Ubuntu 16.04
These instructions should work for other version of Ubuntu and most other Debian-based systems.
Install build packages
Open a terminal (ctrl + alt + t). First install the necessary packages; copy paste the code below and hit enter.
HTML:
sudo apt-get update
sudo apt-get install git ccache automake lzop bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 g++-multilib python-networkx libxml2-utils bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev squashfs-tools pngcrush schedtool dpkg-dev liblz4-tool make optipng maven bc pngquant imagemagick yasm libssl-dev
sudo apt-get install openjdk-8-jdk
HTML:
mkdir -p ~/bin
mkdir -p ~/mokee
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
Add bin to PATH
HTML:
echo "export PATH=~/bin:$PATH" >> ~/.bashrc
Configure git:
HTML:
git config --global user.email "[email protected]"
git config --global user.name "Your Name"
Move to build directory and sync the source code:
HTML:
cd ~/mokee
repo init -u https://github.com/Cyborg2017/android_mokee.git -b mokee-7.1.2
repo sync -j8 -f --no-clone-bundle
Let's configure ccache too. It will reduce the build time to 40% after first build
HTML:
echo "export USE_CCACHE=1" >> ~/.bashrc
~/mokee/prebuilts/misc/linux-x86/ccache/ccache -M 25G
25G means it will use upto 25 gb of disk space for ccaching. Atleast 10 gb is recommended. But if you want to compile for more devices, use more space for ccache.
Step 2: Compiling For Your Device
# MoKee Rom For Samsung Exynos5420 Chips Device
============================================================
To initialize your local repository using the MoKee trees, use a command like this:
HTML:
repo init -u https://github.com/Cyborg2017/android_mokee.git -b mokee-7.1.2
Then to sync up:
HTML:
repo sync
Start Work
-------------------------------------------------------------
To work faster, we introduced a new build script to help you start compiling.
First, go to the root path of your project. We assume that your source is under
(/mokee):
HTML:
cd /mokee
then feel free to use the build script:
HTML:
. build/envsetup.sh
lunch mk_klimtwifi # T700
lunch mk_klimtlte # T705
lunch mk_chagallwifi # T800
lunch mk_chagalllte # T805
lunch mk_chagallltetmo # T807T
lunch mk_ha3g # N900
mka bacon -j8
The script is interactive so everything else is self-explanatory.
Source:
https://github.com/Cyborg2017/android_mokee
https://github.com/Cyborg2017/android_device_samsung_exynos5420-common
https://github.com/Cyborg2017/android_device_samsung_chagalllte
https://github.com/Cyborg2017/android_device_samsung_chagallwifi
https://github.com/Cyborg2017/android_device_samsung_klimtlte
https://github.com/Cyborg2017/android_device_samsung_klimtwifi
https://github.com/Cyborg2017/android_device_samsung_chagallltetmo
https://github.com/Cyborg2017/android_device_samsung_ha3g
https://github.com/Cyborg2017/android_kernel_samsung_exynos5420
Thanks:
MoKee Rom Team: https://github.com/MoKee
Exynos5420 Team: https://github.com/exynos5420
LineageOs Team: https://github.com/LineageOS