I have enabled a lock on this site to keep trollz out. This is a team of Android hackerz that believes in teamwork. So, Kinfolk if you wouldn't mind, please register and log in and help us grow. A.S.A.P...


We Are Legion
HomePortalCalendarGalleryFAQSearchMemberlistUsergroupsRegisterLog in

Share | 


Go down 

Posts : 195
Points : 3002164
Thanks : 7
Join date : 2014-01-02
Age : 41
Location : In da Swamps

PostSubject: WARP3D420 $OURCE TUTORIAL   Fri Jan 03, 2014 3:54 pm

I started this thread because my pre-paid phone is not a supported device.
I have to start this over from scratch, so no need to dwell in the past. The reason I started learning this stuff was to help others. I don't even use custom roms in my phone. I have always liked computers, and anything to do with electronics. I don't care for this N00Bz word. I don't care for people that look down on another human being for anything. God above made us all differently for a reason. Society made sellers and buyers, translated to the Android community as builders and users.. My old lady thinks ROOTING is something you do in the garden.. My new project has nothing to do with Cyanogenmod,AOKP, or JellyBeer. I like to do things that no one has done yet. That is why I am not going to reveal my new Source code. Seems like everytime I come up with an idea somebody else gets "motivated" to do it. lol To be honest I will be working on two seldom done roms, i'm repo sync'n the first one right now. Also, @ legion modz forum - i will make a very detailed tutorial on building from Source. Starting with

1. dual and tri booting your PC, for the Windows lovers. (u need Linux 2 build)
2. Learning to use "Google" , this is your new best friend, It never gets tired of your questions, it never runs out of answers, and open 24 hours a day...
3. Learn basic linux commands ....cd, su, apt-get, etc
4. Setting up your build by yourself
5. Setting up a pre-made build box (see step 1)
6. Learn to use Github
7. Use your newly acquired knowledge to "git" your Sources
8. Build a device tree
9. Build a kernel
10. Put together a script to pull Prop files
11. Building
12. Beating your head on the desk when you can't figure out why it wont build, boot , and why you have so many "bugz"


But when i finish this tutorial, U may be.
this tutorial will not cover anything to do with "cooking" a rom, that is cheating...lol
Now I'm going to try my luck at these new $ROM$.
Thank you for visiting and God bless you


Last edited by WARP3D420Admin on Sun Jan 05, 2014 8:51 pm; edited 1 time in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1

Posts : 195
Points : 3002164
Thanks : 7
Join date : 2014-01-02
Age : 41
Location : In da Swamps

PostSubject: In the Beginning ,there was DARKNESS and cheap phones    Fri Jan 03, 2014 4:08 pm


Windows 7 and Ubuntu,BBQ, or Mint,etc,Build boxes or from live CD. Despite their opposing missions, can get along like best pals on a single computer. Here's how to set up a dual boot or tri boot system that lets you enjoy the best of both worlds in perfect harmony. I know this works because it is how my system at home and on my laptop are setup.

HINT: Linux has around 100 viruses, Windows , it can't be counted. In linux it is harder to get viruses on a PC. Also, Windows viruses don't carry over to your Linux build OS.

Seen in this comparison article

"The expression is intended to suggest that proprietary software is more secure by virtue of its closed nature. If hackers can't see the code, then it's harder for them to create exploits for it--or so the thinking goes.

Unfortunately for Windows users, that's just not true--as evidenced by the never-ending parade of patches coming out of Redmond. In fact, one of Linux's many advantages over Windows is that it is more secure--much more. For small businesses and other organizations without a dedicated staff
of security experts, that benefit can be particularly critical."


1. Make sure you have CD's or USB's with your Distro's on them. I use image burn. If it's Windows, PAY FOR IT!!! if it's Linux, IT'S FREE!!!
2. You are going to need extra space on your hard drive, or PG suggested you can use an extra hard drive.
a. Each repo is going to use up 30 GB
b. Your build tools maybe 5 GB
c. 300 mb for the boot
d. 5-10 GB for the SWAP
e. I use a 1TB for a tri-boot ,500 GB for Windows 7- 250 GB for each of my Linux distros
f. RAM,RAM,RAM,RAM and then some more RAM-- u can thank me later.
g. If you don't have RAM, like on my laptop, I just hooked it to my Internet connection, and let it pull Source while I was sleeping.
3. I like to start fresh--Make a backup, Then I use "KILLDISK" ,it is free and it will write zero's on your hard drive. "Warp, Why do u do that?"
I don't like viruses.
4. Use your Recovery partition or your Windows XP/VISTA/7/8 disk to install the OS.
5. Many hours later, boot into Windows, and hit Start..type diskmgmt.msc
6. If you haven't partitioned a hard drive ,Google it, and learn, this is not a game.
7. Dual boot = 2 primary partitions Tri boot = 3 primary partitions.
Logical is OK for Linux, but dynamic is no good.
8. Pop that fresh copy of your distro in
9. If you are new to Linux "Google it"
10. If you press install alongside windows, it will search out the empty partition and install
11. I don't like GRUB2.
12 Get the non-commercial version of "EasyBCD for Windows, install it, u will be needing it.
13. This is also a free app Google "use easy BCD for dual boot"
14. The only other step needed on the tri boot setup is logging into the first Linux distro u install, open terminal and execute

update-grub2 .

after everything else is done...
15. If you opted for the "Build Box, skip the setting up build step....

There is also another method to installing Linux on a Laptop, or a stubborn PC with Graphics issues and that is with the "Alternate Ubuntu installer"


Open Disk management ,

give SYSTEM a drive letter of z:

Run CMD as Admin

reg  unload  HKLM\BCD00000000 (if you get an ERROR: bla bla bla) then this may already be removed)

robocopy  z:\  c:\  bootmgr

robocopy  z:\Boot  C:\Boot  /s

dir  c:\  /ah

If the bootmgr file and the Boot folder show up in the list, the procedure was successful.

bcdedit  /store  c:\boot\bcd  /set  {bootmgr}  device  partition=C:

bcdedit  /store  c:\boot\bcd  /set  {memdiag}  device  partition=C:

Close the Command Prompt window.

Return to Disk Management

Right-click on the Windows partition and select Mark Partition as Active
IF YOU HAVE TO ASK "WHY" I DID THIS ...DON'T DO IT (see number 7.) also easyBCD can do this process as well

Last edited by WARP3D420Admin on Sun Jan 05, 2014 10:50 pm; edited 5 times in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1

Posts : 195
Points : 3002164
Thanks : 7
Join date : 2014-01-02
Age : 41
Location : In da Swamps

PostSubject: Then came GOOGLE!    Fri Jan 03, 2014 4:16 pm


This is a SIMPLE STEP...
Not www.goggle.com which is a real site, made by Hack3rz. it will mess your PC up.
This step is not limited to one search engine, Google is just my preferred one, because it links in UTUBE in search results and i like it.
Here is a list of other search engines.


No. Name            

1 Baidu              
2 Bing                      
3 Blekko            
4 DuckDuckGo    
5 Exalead              
6 Gigablast              
7 Google              
9 Sogou              
10 Soso.com              
11 Volunia              
12 Yahoo!              
13 Yandex              
14 Youdao              

P2P search engines

No. Name              

1 FAROO            
2 Seeks                      
3 YaCy                      

Metasearch engines

No. Name              
1 Blingo              
2 Yippy                      
3 DeeperWeb      
4 Dogpile              
5 Excite              
6 Harvester42  
7 HotBot              
8 Info.com              
9 Ixquick (StartPage)
10 Kayak & SideStep    
11 Mamma      
12 Metacrawler      
13 Mobissimo              
14 Otalo English        
15 PCH Search and Win
17 WebCrawler      

Geographically limited scope

No. Name

1 Accoona
2 Alleba
3 Ansearch
4 Biglobe
5 Daum
5 Egerin
6 Goo
7 Guruji.com
8 Leit.is
9 Maktoob
10 Miner.hu
11 Najdi.si
12 Naver
13 Onkosh
14 Rambler
15 Rediff
17 Search.ch
18 Sesam
19 Seznam
20 Walla!
21 Yandex.ru
22 Yehey!
23 ZipLocal
I got this list from using "Google"
1. you need to know how many MB in a GB , Google it =1024
2. You need a copy of a missing file ...
3. Anything you aren't sure of.....
4. If you can't find it then go to another forum, and Search it. Chances are somebody has had the same problem as you..


Last edited by WARP3D420Admin on Sun Jan 05, 2014 9:24 pm; edited 6 times in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1

Posts : 195
Points : 3002164
Thanks : 7
Join date : 2014-01-02
Age : 41
Location : In da Swamps

PostSubject: No, You mean I have to learn something to make a $ROM$    Fri Jan 03, 2014 4:25 pm



Unix commands
Note that there are thousands of commands available on a typical unix box. In bash, just hit the "Tab" key twice and say yes, to display the the commands currently available on your machine. A standard unix operating system lists currently thousands of commands. Type x to list all commands starting with x. The following list contains some of the more frequently used programs.

Access Control

exit - terminate a shell (see "man sh" or "man csh")
logout - sign off; end session (C shell and bash shell only
passwd - change login password
rlogin - log in remotely to another UNIX system
ssh - secure shell
slogin - secure version of rlogin
yppasswd - change login password in yellow pages


mail - send and receive mail
mesg - permit or deny terminal messages and talk requests
pine - send and receive mail
talk - talk to another logged-in user
write - write to another logged-in user

Programming Tools

as - assembler, specific to each machine architecture
awk - pattern scanning and processing language
bc - online calculator
cc - C compiler
csh - C shell command interpreter
dbx - source-level debugging program
f77 - Fortran compiler
gdb - GNU Project debugger
gprof - display profile of called routines
kill - kill a process
ld - the UNIX loader
lex - generate lexical analysis programs
lint - check C source code
make - maintain large programs
maple - symbolic mathematics program
math - symbolic mathematics program
nice - run a command at low priority (see "man nice" or "man csh")
nohup - run a command immune to hangups
pc - Pascal compiler (xlp on ADS)
perl - Popular script interpreter
prof - display profile data
python - Python programming language
sh - Bourne shell command interpreter
yacc - generate input parsing programs
xcalc - graphical calulator under x


apropos - locate commands by keyword lookup
find - locate file (i.e. find . -name *.tex -print)
info - start the info explorer program
man - find manual information about commands
whatis - describe what a command is
whereis - locate source, binary, or man page for a program


emacs - screen-oriented text editor
pico - screen-oriented text editor (renamed called nano)
sed - stream-oriented text editor
vi - full-screen text editor
vim - full-screen text editor ("vi-improved")
File and Directory Management

cd - change working directory
chmod - change the protection of a file or directory
chown - change owner (or group) of a file or directory
chgrp - change group of a file or directory
cmp - compare two files
comm - select/reject lines common to two sorted files
cp - copy files
crypt - encrypt/decrypt files (CCWF only)
diff - compare the contents of two ASCII files
file - determine file type
grep - search a file for a pattern
gzip - compress or expand files
ln - make a link to a file
ls - list the contents of a directory
lsof - list of open files
mkdir - create a directory
mv - move or rename files and directories
pwd - show the full pathname of your working directory
quota - display disk usage and limits
rm - delete (remove) files
rmdir - delete (remove) directories
stat - status of file (i.e. last access)
sync - flush filesystem buffers
sort - sort or merge files
tar - create or extract archives
tee - copy input to standard output and other files
tr - translate characters
umask - change default file protections
uncompress - restore compressed file
uniq - report (or delete) repeated lines in a file
wc - count lines, words, and characters in a file

File Display and Printing

cat - show the contents of a file; catenate files
fold - fold long lines to fit output device
head - show first few lines of a file
lpq - examine the printer spooling queue
lpr - print a file
lprm - remove jobs from the printer spooling queue
more - display a file, one screen at a time
less - like more with more features
page - like "more", but prints screens top to bottom
pr - paginate a file for printing
tail - show the last part of a file
zcat - display a compressed file
xv - show print, manipulate images
gv - show ps and pdf files
xpdf = shopw pdf files (use gv)

File Transfer

ftp - transfer files between network hosts
rsync - fast and flexible sync between computers
scp - secure version of rcp


alias - define synonym commands
chquota - change disk quota on ACITS UNIX systems
chsh - change default login shell
clear - clear terminal screen
echo - echo arguments
pbm - portable bitmap manipulation programs
popd - pop the directory stack (C shell only)
pushd - push directory on stack (C shell only)
script - make typescript of terminal session
setenv - set an environment variable (C shell only)
stty - set terminal options


netstat - show network status
rsh - run shell or command on another UNIX system
ssh - secure-shell version of rsh

Process Control

bg - put suspended process into background
fg - bring process into foreground
jobs - list processes
^y - suspend process at next input request
^z - suspend current process

Status Information

clock - determine processor time
date - show date and time
df - summarize free disk space
du - summarize disk space used
env - display environment
finger - look up user information
history - list previously issued commands
last - indicate last login of users
lpq - examine spool queue
manpath - show search path for man pages
printenv - print out environment
ps - show process status
pwd - print full pathname of working directory
set - set shell variables (C shell, bash, or ksh)
spend - lists year-to-date ACITS UNIX charges
stty - set terminal options
time - timing programs
top - list top cpu processes
uptime - show system load, how long system has been up
w - show who is on system, what command each job is executing
who - show who is logged onto the system
whois - Internet user name directory service
whoami - who owns the shell

Image Processing

gimp - photoshop type image processing program
xfig - drawing program
xv - image viewer
xvscan - scan picture
xpaint - paint program
kpaint - kde paint program


mplayer - mpg player
realplay - realaudio player
timidity - midi to wav converter and player
xmms - mp3 player

Text Processing

abiword - open source word processor
addbib - create or extend bibliographic database
col - filter reverse line feeds
diction - identify wordy sentences
diffmk - mark differences between files
dvips - convert TeX DVI files into PostScript
explain - explain phrases found by diction program
grap - pic preprocessor for drawing graphs
hyphen - find hyphenated words
ispell - check spelling interactively
latex - format text in LaTeX (based on TeX)
pdfelatex - latex with pdf output
latex2html - Latex to html
lookbib - find bibliography references
macref - make cross-reference listing of nroff/troff macro files
ndx - create a subject-page index for a document
neqn - format mathematics with nroff
nroff - format text for simple display
pic - make simple pictures for troff input
psdit - filter troff output for Apple LaserWriter
ptx - make permuted index (not on CCWF)
refer - insert references from bibliographic databases
roffbib - run off bibliographic database
sortbib - sort bibliographic database
spell - find spelling errors
ispell - interactive spell checker
style - analyze surface characteristics of a document
tbl - format tables for nroff/troff
tex - format text
tpic - convert pic source files into TeX commands
wget - grab webpage

X windows

grabmode - info on screen: i.e. "1152x864" 51.213kHz/56.59Hz
import - grab window (i.e. import ppm:- >out.ppm)
xdpyinfo - number of colors
xkill - kill xwindow
xlock - lock screen
xterm - xterminal
xwininfo - information on open window


html2ps - html to ps
latex2html - latex to html translator
lynx - text based webbrowser
netscape - webbrowser
sitecopy - sitecopy is for easily maintaining remote web sites.
weblint - html sytax and style checker


Last edited by WARP3D420Admin on Sun Jan 05, 2014 9:14 pm; edited 3 times in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1

Posts : 195
Points : 3002164
Thanks : 7
Join date : 2014-01-02
Age : 41
Location : In da Swamps

PostSubject: All by myself, I did it!!    Fri Jan 03, 2014 4:35 pm


This next step is not easy, it is time-consuming. So if you chose a "Build Box" I understand..
Lucky for you, i have already found everything for you , So split your screen .
On one side a fresh terminal, on the other side my tutorial, and copy/paste from the beginning of part B).
HINT: When adding any file with apt-get. Watch for anything being removed and anything being added. Also copy any SUGGESTED programs to a text- editor ,research them and add them if you like..
Also when adding things with the command--- $ sudo apt-get install , numerous items can be added behind the command, but i recommend doing it one by one.
This is because of obsoleted software or missing software errors.
This is only going to be a basic list: Seperated in two parts, by A)what you need and B)how to get it.


1. Compile Dependencies (libs)
2. Python 2.7.3 (3.2 and 3.3 opt.)
3. GNU MAKE (3.81 or 3.82)
4. Java JDK 6.xx ( not 7)
5. Android SDK
6. ADB & Fastboot
7. USB Configs
8. Repo command
9. Add everything to the PATH in ./bashrc

When you see this symbol "$", it means you are in terminal, but not as "ROOT"
Although if you see this symbol # , you are the "ROOT" user .
Your directory name will be in Red as well.

"But Warp, I don't know how to ROOT my Linux Box"
You don't say...

terminal: $ sudo passwd root
this will then open up Unix for you
add some passwords /confirm password /REMEMBER YOUR PASSWORD!!!
My password is ********** lol.

But Warp, I'm a brave "new user" I want "ROOT" access to file manager..

For Ubuntu
Terminal: $ gksudo nautilus
enter password-- DONE

For Mint (cinnamon)
Terminal: $ gksudo nemo
enter password-- DONE

For Mint (Mate)
Terminal: $ gksudo caja
enter password-- DONE!!!



1.. $ sudo apt-get install git
sudo apt-get install git-core
sudo apt-get install gnupg
sudo apt-get install flex
sudo apt-get install bison
sudo apt-get install gperf
sudo apt-get install build-essential
sudo apt-get install zip
sudo apt-get install curl
sudo apt-get install zlib1g-dev
sudo apt-get install libc6-dev
sudo apt-get install lib32ncurses5-dev
sudo apt-get install ia32-libs
sudo apt-get install x11proto-core-dev
sudo apt-get install libx11-dev:i386
sudo apt-get install libreadline6-dev:i386
sudo apt-get install lib32z-dev
sudo apt-get install libgl1-mesa-glx:i386
sudo apt-get install libgl1-mesa-dev
sudo apt-get install g++-multilib
sudo apt-get install mingw32
sudo apt-get install tofrodos
sudo apt-get install python-markdown
sudo apt-get install libxml2-utils
sudo apt-get install xsltproc
sudo apt-get install readline-common
sudo apt-get install libreadline6-dev
sudo apt-get install libreadline6
sudo apt-get install lib32readline-gplv2-dev
sudo apt-get install libncurses5-dev
sudo apt-get install lib32readline5
sudo apt-get install lib32readline6
sudo apt-get install libreadline-dev
sudo apt-get install libreadline6:i386
sudo apt-get install bzip2
sudo apt-get install libbz2-dev
sudo apt-get install libbz2-1.0
sudo apt-get install libghc-bzlib-dev
sudo apt-get install lib32bz2-dev
sudo apt-get install libsdl1.2-dev
sudo apt-get install libesd0-dev
sudo apt-get install squashfs-tools
sudo apt-get install pngcrush
sudo apt-get install schedtool
sudo apt-get install python
sudo apt-get install gcc-4.7-multilib
sudo apt-get install ccache
sudo apt-get install eclipse
sudo apt-get install lzop
sudo apt-get install libwxgtk2.8-dev
sudo apt-get install liblzo2-dev
sudo apt-get install uuid
sudo apt-get install uuid-dev
sudo apt-get install zlib1g-dev liblz-dev
sudo apt-get install wmctrl
sudo apt-get install kernel-package
sudo apt-get install jfsutils
sudo apt-get install mcelog
sudo apt-get install xfsprogs

sudo apt-get install git git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 lib32z1-dev libgl1-mesa-glx:i386  libgl1-mesa-dev g++-multilib  mingw32 tofrodos python-markdown libxml2-utils xsltproc readline-common libreadline6-dev libreadline6 lib32readline-gplv2-dev libncurses5-dev lib32readline5 lib32readline6 libreadline-dev libreadline6:i386 bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev lib32bz2-dev libsdl1.2-dev libesd0-dev gcc-4.6-multilib squashfs-tools pngcrush schedtool python  ccache eclipse lzop libwxgtk2.8-dev wmctrl debhelper liblzo2-dev uuid uuid-dev zlib1g-dev liblz-dev kernel-package jfsutils mcelog xfsprogs

EXTRAS suggested by apt-- I wouldn't advise you installing anything unless you need them...

apport-gtk apport-kde valac gnome-user-guide desktop-base lightdm
gnome-sushi python-launchpadlib python3-launchpadlib ri ruby-dev
ruby1.9.1-examples ri1.9.1 graphviz ruby1.9.1-dev ruby-switch
ubuntu-sso-client-gui ubuntuone-client-proxy zeitgeist-datahub

imagemagick-doc autotrace enscript ffmpeg gnuplot grads hp2xx html2ps
libwmf-bin povray radiance texlive-base-bin transfig ufraw-batch
libjline-java-doc librhino-java-doc xfonts-cyrillic

git-daemon-run git-daemon-sysvinit git-doc git-el git-arch git-cvs git-svn
git-email git-gui gitk gitweb

bison-doc lib32mudflap0 ncurses-doc libasound2-doc pulseaudio-esound-compat libglib2.0-doc

dh-make debian-keyring g++-multilib g++-4.7-multilib gcc-4.7-doc
libstdc++6-4.7-dbg libstdc++6-4.7-doc libmail-box-perl lib32stdc++6-4.7-dbg libxcb-doc libxext-doc gcc-doc cpp-doc

python-markdown-doc ttf-bitstream-vera ghc-prof ghc-doc haskell-doc llvm-3.0 libghc-bzlib-doc libghc-bzlib-prof
libgmp10-doc libmpfr-dev distcc distccmon-gnome distcc-pump
ant-gcj ant-doc libbsf-java liboro-java libxalan2-java libjaxp1.3-java
liblog4j1.2-java jython antlr libbcel-java libjdepend-java libgnumail-java
libcommons-net-java javacc ant-optional-gcj junit-doc
libcommons-beanutils-java-doc libcommons-collections3-java-doc
libcommons-dbcp-java-doc libcommons-digester-java-doc
libcommons-httpclient-java-doc libavalon-framework-java
libcommons-logging-java-doc libexcalibur-logkit-java libdb5.1-java-gcj
libeasymock-java-doc ecj libecj-java-gcj libfelix-bundlerepository-java-doc
libfelix-gogo-command-java-doc libfelix-gogo-runtime-java-doc
libfelix-gogo-shell-java-doc libfelix-osgi-obr-java-doc
libfelix-shell-java-doc libfelix-utils-java-doc
libgeronimo-jpa-2.0-spec-java-doc libgeronimo-jta-java-doc
libgeronimo-osgi-support-java-doc libice-doc jetty8 libjetty8-java-doc
libjtidy-java-doc libosgi-compendium-java-doc libosgi-core-java-doc
libosgi-foundation-ee-java-doc libsm-doc libswt-gtk-3-java-gcj tomcat7
wx2.8-doc libgnomeprintui2.2-0 libxt-doc openjdk-7-demo openjdk-7-source

i386 items

murrine-themes:i386 kde-config-gtk-style:i386 libpam-ldap:i386
libpam-winbind:i386 libnss-ldap:i386 libroar1:i386 libsndio0:i386
roaraudio-server:i386 libasound2-python:i386 nas:i386 glibc-doc:i386
locales:i386 libcanberra-pulse:i386 libdv-bin:i386 oss-compat:i386
pulseaudio-esound-compat:i386 rng-tools:i386 libgd-tools:i386 libglide3:i386 ibx11-doc:i386 xml-core:i386
gnome-keyring:i386 gnutls-bin:i386 gphoto2:i386 gtkam:i386 gpm:i386
krb5-doc:i386 krb5-user:i386 gstreamer-codec-install:i386
gnome-codec-install:i386 gstreamer0.10-tools:i386 jackd2:i386
libjasper-runtime:i386 liblcms-utils:i386 libmyodbc:i386
odbc-postgresql:i386 tdsodbc:i386 unixodbc-bin:i386 libportaudio2:i386
libroar-compat2:i386 ttf-baekmuk:i386 ttf-arphic-gbsn00lp:i386
ttf-arphic-bsmi00lp:i386 ttf-arphic-gkai00mp:i386 ttf-arphic-bkai00mp:i386
libqt4-declarative-folderlistmodel:i386 libqt4-declarative-gestures:i386
libqt4-declarative-particles:i386 libqt4-declarative-shaders:i386
qt4-qmlviewer:i386 libqt4-dev:i386 libicu48:i386 qt4-qtconfig:i386
libraw1394-doc:i386 librsvg2-bin:i386 hpoj:i386 hplip:i386
libsane-extras:i386 sane-utils:i386 libsasl2-modules-otp:i386
libsasl2-modules-ldap:i386 libsasl2-modules-sql:i386
libsasl2-modules-gssapi-mit:i386 libsasl2-modules-gssapi-heimdal:i386
speex:i386 libxcb-doc:i386

$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so

After you do all this, may be a good idea to add $ sudo apt-get upgrade

2. I don't get this step. Python is already on there, and if it ain't when you input "sudo apt-get install python" it will be...

3. Gnu Make , Your suppose to get this inside of build-essential , I like to know i got the newest one ,so i do it like thisgo to http://ftp.gnu.org/gnu/make/
Download GNU MAKE 3.82
Open up file manager
go to download folder
cut file
go to home directory
close file manager
Open Terminal:
$ cd <name of gnu make folder(exact)>
then it will look something like this
gnu make $
$ ./configure
$ make
# make install
# make clean...DONE

4. Get rid of pre-installed "JAVA"

$ sudo apt-get purge openjdk-\* icedtea-\* icedtea6-\*

Add new Oracle JAVA 6

sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java6-installer

If you want to check the version after it is done
Terminal: $java -version

5.Terminal: $ wget http://dl.google.com/android/android-sdk_r22-linux.tgz
When that finishes downloading
Terminal: $ tar -xvzf android-sdk_r22-linux.tgz

After extracting the package, run the command below to change into the tools directory.

cd ~/android-sdk-linux/tools

Finally, run the commands below to begin the installation.

./android update sdk


"wget" is the same thing as "curl"

6. This may seem like a pointless step.
Warp, I already have ADB & Fastboot when I installed SDK, but do you have the 4.2.2 update ??

Just to make sure..

Terminal: $ sudo apt-get install android-tools-adb android-tools-fastboot

7. Create a folder in Home dir "51-android.rules" .
Now open a terminal and input: $ gksudo gedit /etc/udev/rules.d/51-android.rules
When another screen pops up copy and paste this inside--

SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"

SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"

SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"

SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"

SUBSYSTEM=="usb", ATTR{idVendor}=="24e3", MODE="0666"

#KT Tech
SUBSYSTEM=="usb", ATTR{idVendor}=="2116", MODE="0666"

SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"

SUBSYSTEM=="usb", ATTR{idVendor}=="17EF", MODE="0666"

SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"

SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"

SUBSYSTEM=="usb", ATTR{idVendor}=="0409", MODE="0666"

SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"

SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"

SUBSYSTEM=="usb", ATTR{idVendor}=="2257", MODE="0666"

SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"

SUBSYSTEM=="usb", ATTR{idVendor}=="0471", MODE="0666"

SUBSYSTEM=="usb", ATTR{idVendor}=="04da", MODE="0666"

SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666"

#SK Telesys
SUBSYSTEM=="usb", ATTR{idVendor}=="1f53", MODE="0666"

SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"

SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"

#Sony Ericsson
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"

SUBSYSTEM=="usb", ATTR{idVendor}=="0930", MODE="0666"

SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"
Save & Close text-editor.

Now fire up another terminal
To set proper permisisons: (Provide read permission to all users, in addition to whatever other permissions are pre-set)


Terminal: $ sudo chmod a+r /etc/udev/rules.d/51-android.rules

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

Terminal: $ export PATH=${PATH}:~/bin

9. You can make this change to the path permanent for all future Terminal sessions:
Terminal: gedit ~/.bashrc

add export PATH=${PATH}:~/bin, on its own line, then save the file.

If you ever have problems with repo.. try this

- Make sure you have a bin/ directory in your home directory and that it is included in your path: (Very Important)

$ PATH=~/bin:$PATH

- Next,
$ curl http://commondatastorage.googleapis....downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

Last edited by WARP3D420Admin on Tue Jan 28, 2014 5:52 pm; edited 8 times in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1

Posts : 195
Points : 3002164
Thanks : 7
Join date : 2014-01-02
Age : 41
Location : In da Swamps

PostSubject: I don't want to do it   Fri Jan 03, 2014 4:37 pm


This step was included , for no particular reason. If you chose a build box, and you made it past step 1 without using it, you did something wrong. Go back to step 1

But I might as well include a few sources for build boxes
BBQLinux http://sourceforge.net/projects/bbqlinux/files/
h311sdr0id's--h311's kitchen http://forum.xda-developers.com/show....php?t=2152398

Last edited by WARP3D420Admin on Sun Jan 05, 2014 10:47 pm; edited 3 times in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1

Posts : 195
Points : 3002164
Thanks : 7
Join date : 2014-01-02
Age : 41
Location : In da Swamps

PostSubject: How did he do that???    Fri Jan 03, 2014 4:38 pm


GitHub is a web-based hosting service for software development projects that use the Git revision control system. GitHub offers both paid plans for private repositories, and free accounts for open source projects.

If you are a person that wants to "build" and become more than just a "user", then your next stop is at "Github"...
Your old buddy "Google" can get you there pretty fast.

The site provides social networking functionality such as feeds, followers and the network graph to display how developers work on their versions of a repository.

According to the terms of service,if an account's bandwidth usage significantly exceeds the average of other GitHub customers, the account's file hosting service may be immediately disabled or throttled until bandwidth consumption is reduced. In addition, while there is no hard limit, the guideline for the maximum size of a repository is one gigabyte.

GitHub also has their standard GUI application available for download (Windows, Mac, Linux) directly from the service's website.

Ever wonder, "How did this Dev get this unsupported device to boot the latest rom?" Chances are, the way they did it will be inputted in Github.
Pay attention to the device names and models, This is important, because like I said every device is different... Everyday lately, I spend an hour or two looking through Github. Not just at my device, but at other models, other kernels, other Solutions...

Now I'm not saying go there, Find a boardconfig you like, cut/paste it into your device tree, but you may find some answers to problems.

(some info from github Wiki)

beginner's links

git gui

Last edited by WARP3D420Admin on Sun Jan 05, 2014 9:48 pm; edited 3 times in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1

Posts : 195
Points : 3002164
Thanks : 7
Join date : 2014-01-02
Age : 41
Location : In da Swamps

PostSubject: "GIT" it!!!    Fri Jan 03, 2014 4:42 pm


"GOT RAM" This is when it will come in handy. EDIT: If you like to multi-task. "message for the anal thread readers"

Open up file manager, HOME directory ,make new folder, name it "android" (easy way to do it)
Open "android" folder, make new folder, name it "system"
Close file manager


Fire up a terminal
$ mkdir android
$ cd android
$ mkdir system

To get your Source, all you need are three things.
1. Git
2. Curl
3. Repo command
Whether you used a "build box" or set it up yourself , you have everything, but to pull Source, that's all it uses...

How to Initialize the source repository



repo init -u https://android.googlesource.com/platform/manifest -b android-4.2.2_r1.2

ChameleonO$ :

repo init -u git://github.com/ChameleonOS/android.git -b jellybean-mr1

repo init -u git://github.com/ChameleonOS/android.git -b jellybean

PAC-Man :

repo init -u git://github.com/PAC-man/android.git -b cm-10.1

repo init -u git://github.com/PAC-man/android.git -b cm-10.2

CM 10.1 :

repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1

CM10 :

repo init -u git://github.com/CyanogenMod/android.git -b jellybean

BeerGang :

repo init -u git://github.com/BeerGang/android.git -b cm-10.1


For 4.2

repo init -u https://github.com/AOKP/platform_manifest.git -b jb-mr1

For 4.1

repo init -u https://github.com/AOKP/platform_manifest.git -b jb


repo init -u git://github.com/MiCode/patchrom.git -b ics

Paranoid android

repo init -u git://github.com/ParanoidAndroid/android.git -b jellybean

slim bean

repo init -u git://github.com/SlimRoms/platform_manifest.git -b jb4.2


repo init -u https://github.com/TeamBAKED/platform_manifest.git -b jb

(I got this from another guide)

There are other codes out there, but these are main-stream.

So, what you want to do is , open a Terminal

cd = change directory

So you will
$ cd android
$ cd system
$ repo init -u git://github.com/PAC-man/android.git -b cm-10.1

At this point half your terminal or all your terminal will fill with text.
Two ways this will play out
1. it will let you register with name and email
2. it will give you on-screen codes to config it to your name and email

If you want the "Goodies" DO AS IT TELLS YOU

Now after you got that taken care of,

$ repo sync

Learn this code, remember this code, love this code.
it not only pulls the Source to your PC, but it also updates it every time you input it.
So, say Pacman adds a bluetooth update, BAM, that's how you get it.

It depends on your PC specs, to whether how long downloading your Source will take.
PG gets it quick, i get it slow, but we both get it...

For the next month or 4ever, this is where your "repo" will live..
Learn this folder, Open every folder, learn what's in there.

Last edited by WARP3D420Admin on Sat Jan 25, 2014 9:45 pm; edited 4 times in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1

Posts : 195
Points : 3002164
Thanks : 7
Join date : 2014-01-02
Age : 41
Location : In da Swamps

PostSubject: This tree has broken branches    Fri Jan 03, 2014 4:44 pm


Creating a basic new device tree

First step to this is to search Github for a device tree for your specific device.
This is where I got lucky.
PG and his associates lol, had already put together a working device tree for our device.
Chances are ,if your device didn't just hit the stores this week, somebody may have started work on a device tree for it.
Although if you do not have anything to start with, You must first open your device folder in the "repo" you "sync'd" to your PC, look at the supported devices
This will be a tool only for reference.
As I open my folder I notice the following

1. A "bluetooth" folder, with a config file
2. An "include" folder
3. An "overlay" folder
4. A "prebuilts" folder
5. A "recovery" folder
6. A "releasetools" folder
7. AndroidBoard.mk
8. AndroidProducts.mk
9. Boardconfig.mk
10. CM.mk
11. device_warp2.mk
12. extract-files.sh (this is to pull prop blobs)
13. full_warp2.mk
14. Proprietary-files.txt( a list of the prop files you will pull from your stock phone)
15. recovery.fstab
16. setup-makefiles.sh
17. system.prop
18. USBcontroller.cpp

With this group of files, i was able to get a built, but not bootable copy of Jellybeer 10.1.

Now some devices have less and some have alot more files in the device folder.
If you are really serious about becoming a developer, you have to search out others on Github, forums, etc
This step will take teamwork.

Below are two explanations of the files that go into making a device tree...

The directions below describe how to configure make files for new mobile devices and products.

Create a company directory in //device/partner.

mkdir device/partner/<company_name>

Create a products directory beneath the company directory you created in step 1.

mkdir device/partner/<company_name>/products/

Create a product-specific make file, called device/partner/<company_name>/products/<first_product_name>.mk, that includes the following code:

$(call inherit-product, target/product/generic.mk)
# Overrides
PRODUCT_NAME := <first_product_name>
PRODUCT_DEVICE := <board_name>

In the products directory, create an AndroidProducts.mk file that point to (and is responsible for finding) the individual product make files.

# This file should set PRODUCT_MAKEFILES to a list of product makefiles
# to expose to the build system. LOCAL_DIR will already be set to
# the directory containing this file.
# This file may not rely on the value of any variable other than
# LOCAL_DIR; do not use any conditionals, and do not look up the
# value of any variable that isn't set in this file or in a file that
# it includes.

$(LOCAL_DIR)/first_product_name.mk \

Create a board-specific directory beneath your company directory that matches the PRODUCT_DEVICE variable <board_name> referenced in the product-specific make file above. This will include a make file that gets accessed by any product using this board.

mkdir device/partner/<company_name>/<board_name>

Create a product_config.mk file in the directory created in the previous step (device/partner/<company_name>/<board_name>). If this directory does not include a product_config.mk file, the build will fail.

# These definitions override the defaults in config/config.make for <board_name>

If you wish to modify system properties, create a system.prop file in your <board_name> directory(device/partner/<company_name>/<board_name>).

# system.prop for
# This overrides settings in the products/generic/system.prop file
# rild.libpath=/system/lib/libreference-ril.so
# rild.libargs=-d /dev/ttyS0

Add a pointer to <second_product_name>.mk within products/AndroidProducts.mk.

$(LOCAL_DIR)/first_product_name.mk \

device/partner/<company_name>/<board_name> must include an Android.mk file with at least the following code:

# make file for new hardware from
LOCAL_PATH := $(call my-dir)
# this is here to use the pre-built kernel
ALL_PREBUILT += $(file)
# no boot loader, so we don't need any of that stuff..
LOCAL_PATH := partner/<company_name>/<board_name>
include $(CLEAR_VARS)
# include more board specific stuff here? Such as Audio parameters.

To create a second product for the same board, create a second product-specific make file called device/partner/company_name/products/<second_product_name>.mk that includes:

$(call inherit-product, partner/google/products/generic.mk)
# Overrides
PRODUCT_NAME := <second_product_name>
PRODUCT_DEVICE := <board_name>

By now, you should have two new products, called <first_product_name> and <second_product_name> associated with <company_name>. To verify that a product is properly configured (<first_product_name>, for example), execute the following:

cd device
. ./envsetup.sh
partner_setup <first_product_name>
make PRODUCT-<first_product_name>-user

You should find new build binaries located in device/out/target/product/<board_name>.
New Product File Tree

The file tree below illustrates what your own system should look like after completing the steps above.


Part 2

Right... So you want to build your own device tree, read on.

Disclaimer: this is by no means complete, and there will be omissions as have explained all this top of my head and copied pasted certain bits that I have here on my own device tree.

The device tree, for example, /device/lg/gt540would consist of the following make files:

Android.mk - this will tell the build system to include and to build sources specifically for your device. See below, for an example. This is dependant on the device and hardware, you could have libsensors, liblights, libcamera subdirectories under the example device tree, i.e. /device/lg/gt540/libsensors, /device/lg/gt540/liblights, /device/lg/gt540/libcamera etc.
AndroidBoard.mk - this is for the kernel, the build system uses that to drop the kernel image in place (more about this in a few minutes)
AndroidProducts.mk - specifies the appropriate device's make file, to use for building. i.e. /device/lg/gt540/device_gt540.mk, this is specific also.
device_xxxxx.mk - specifies the properties and extras to copy over into the final output, in this case, it could be for example, device_gt540.mk
BoardConfig.mk - This is the meat of it all, this is where compiler conditional flags are set, partition layouts, boot addresses, ramdisk size, and so on.
Lets peek into each of those to give a glance as to where it all fits in.[/code]


include $(call all-named-subdir-makefiles, recovery libsensors liblights libcamera ....)

This is how the build will use that to build recovery, sensors, lights and camera (of course there will be more), its saying 'Yo Builder, go into each of the directories specified, and build the respective sources plskthxbai'


LOCAL_PATH := device/lg/gt540/

# Boot files

ALL_PREBUILT += $(file)

Now this, is telling the build system, to be able to drop this kernel into the out/target/product/lg/gt540 (notice the correlation with the device tree directory?)



Its telling the build as in 'Yo Builder, read that device make file please and process it upon completion of build.'

*device_xxxxx.mk: (for this example, device_gt540.mk) *

PRODUCT_NAME := lg_gt540

... specific ...

ro.com.android.dateformat=dd-MM-yyyy \

... more stuff ...

This is where all the specifics for the device such as drivers, proprietary libraries, supporting scripts specifically for the device, gets copied over to out/target/product/lg/gt540/system/ in this case. Notice how the overrides for the properties, these end up in the build.prop found in the root of the /system of the Android ROM.


LOCAL_PATH:= $(call my-dir)

TARGET_PREBUILT_KERNEL := device/lg/gt540/kernel
TARGET_PREBUILT_RECOVERY_KERNEL := device/lg/gt540/recovery_kernel

# This will vary from device!
TARGET_CPU_ABI := armeabi
TARGET_CPU_ABI := armeabi-v6l
TARGET_CPU_ABI2 := armeabi

# OpenGL drivers config file path
BOARD_EGL_CFG := device/lg/gt540/egl.cfg

# Dependant, not to be taken literally!

# Dependant, not to be taken literally!
BOARD_KERNEL_BASE := 0x02600000

# this will be device specific, and by doing cat /proc/mtd will give you the correct sizes
That is an excerpt, notice how we specify kernel's base address, this is how the boot.img gets generated after compilation is done and yet again, gets dropped into out/target/product/lg/gt540/boot.img. Also, more importantly, we're telling the build system to use the target platform for cross-compiling the sources (*TARGET_BOARD_PLATFORM*/*TARGET_CPU_ABI*) There will be more information in there such as conditional flags to pass to the compiler, for an example. we specified the directive HAVE_FM_RADIO to tell it, when it comes to handling the source for the FM radio system, to conditionally compile parts of the source. Again, this is hardware specific and mileage will vary, also this applies to the address for boot. In a nutshell, this is saying 'Yo Builder, read the damn variables and remember them and apply them when cross-compiling those source files!'

Now that the internals of each of those Android build make-files are shown.

Now, onto the vendor/ part of it, in AOSP, simply, once again, correlation and corresponds with the device/ tree, as in continuing with this example, vendor/lg/gt540/ which gets picked up by the lunch. There's more make files in there but the general consensus is there's a directory called proprietary which contains the proprietary libs (due to close-source etc) that gets copied over. The copying over of the libraries gets specified in the file device-vendor-blobs.mk, in this case, gt540-vendor-blobs.mk.

When the magic happens by doing the following:

. build/envsetup.sh

This is reading in the entire entries found in each of the device/ subdirectories and "remembers them", so the build system knows what type of target is used etc.

When the . lunch gets invoked, a menu appears prompting to pick the device that is required to build. Now the last and final step to do the build...

make -j5 > buildlog.log 2>&1

I run multitail on another terminal and monitor the buildlog.log file to check and make sure its building.

This last step will depend on how many cores you have (n cores + 1 as a rule) and it takes a while to build, GB build takes 40mins on my laptop running Arch Linux 64bit, ICS build takes about 2hrs 30 mins. So mileage will vary on what type of horsepower your machine has.

When the build is done, a little bell goes off and at the bottom of the said log file, I see this:

Combining NOTICE files: out/target/product/xxxxx/obj/NOTICE.html
Target system fs image: out/target/product/xxxxx/obj/PACKAGING/systemimage_intermediates/system.img
Install system fs image: out/target/product/xxxxx/system.img
out/target/product/xxxx/system.img+ total size is 108776448[/code]

As matter of interest JBQ (Jean Baptiste Queru - the 'boss' for managing/distributing the source from Google), his build step is this...

Extra code to use the ICS Repository

Now enter the following to initialize the repository:

cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b ics

Extra codes to use the JB Repository

Now enter the following to initialize the repository:

cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b jellybean

This is not everything, because a device tree for every device is different, To start from scratch will take alot of time.
You will add, then remove, and then add again.

Last edited by WARP3D420Admin on Thu Jan 16, 2014 2:12 am; edited 5 times in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1

Posts : 195
Points : 3002164
Thanks : 7
Join date : 2014-01-02
Age : 41
Location : In da Swamps

PostSubject: The president has spoken    Fri Jan 03, 2014 4:46 pm


Building a kernel.
You're in deep waters once again.
To explain the kernel, I would say he is like the president of your phone.
He tells everyone what to do, and when to do it, and how to do it.


The kernel is the core of an operating system. It functions on a low level (kernelspace) interacting between the hardware of the machine and the programs which use the hardware to run. To make efficient use of the CPU, the kernel uses a scheduler to arbitrate which tasks take priority at any given moment, creating the illusion of many tasks being executed simultaneously.
(From ahn article about Arch Linux)

"Do you like LAG?"
Well if you answered "no"
Then you better build a good kernel.

I entered "building a kernel for android" and i got a long list of tutorials on this.
So, if my section on kernels isn't enough, Google has more.

"git clone" is the code prefix if you luck out and find a kernel source on github.
first you would
$ cd android
$ cd system
$ cd kernel
$ mkdir <name of company>
$ cd <name of company>
$ git clone bla bla bla bla bla lol

But for the purpose of this step, you did not find a kernel source...

So, if you did step 8, or you found a device repo on Github, then you know alot more about your device now, specifically the hardware that pushes your device..

This table lists the name and locations of SOME kernel sources and binary

Device / Binary location / Source location / Build configuration

manta / device/samsung/manta/kernel / kernel/exynos / manta_defconfig
mako / device/lge/mako-kernel/kernel / kernel/msm / mako_defconfig
grouper / device/asus/grouper/kernel / kernel/tegra / tegra3_android_defconfig
tilapia / device/asus/grouper/kernel / kernel/tegra / tegra3_android_defconfig
maguro / device/samsung/tuna/kernel / kernel/omap / tuna_defconfig
toro / device/samsung/tuna/kernel / kernel/omap / tuna_defconfig
panda / device/ti/panda/kernel / kernel/omap / panda_defconfig
stingray /device/moto/wingray/kernel / kernel/tegra / stingray_defconfig
wingray / device/moto/wingray/kernel / kernel/tegra / stingray_defconfig
crespo /device/samsung/crespo/kernel / kernel/samsung / herring_defconfig
crespo4g / device/samsung/crespo/kernel / kernel/samsung / herring_defconfig [/code]

This is for reference, these devices are supported..

You will want to look at the git log for the kernel binary in the device project that you are interested in.

Device projects are of the form device/<vendor>/<name>. This example is for the Panda..
$ git clone https://android.googlesource.com/device/ti/panda
$ cd panda
$ git log --max-count=1 kernel[/code]

The commit message for the kernel binary contains a partial git log of the kernel sources that were used to build the binary in question. The first entry in the log is the most recent, i.e. the one used to build that kernel. You will need it at a later step.
Downloading sources

Depending on which kernel you want,
Device projects are of the form device/<vendor>/<name>.

The goldfish project contains the kernel sources for the emulated platforms.
The msm project has the sources for ADP1, ADP2, Nexus One, Nexus 4, and can be used as a starting point for work on Qualcomm MSM chipsets.
The omap project is used for PandaBoard and Galaxy Nexus, and can be used as a starting point for work on TI OMAP chipsets.
The samsung project is used for Nexus S, and can be used as a starting point for work on Samsung Hummingbird chipsets.
The tegra project is for Xoom and Nexus 7, and can be used as a starting point for work on NVIDIA Tegra chipsets.
The exynos project has the kernel sources for Nexus 10, and can be used as a starting point for work on Samsung Exynos chipsets.[/code]

To git these

$ git clone https://android.googlesource.com/kernel/common.git
$ git clone https://android.googlesource.com/kernel/exynos.git
$ git clone https://android.googlesource.com/kernel/goldfish.git
$ git clone https://android.googlesource.com/kernel/msm.git
$ git clone https://android.googlesource.com/kernel/omap.git
$ git clone https://android.googlesource.com/kernel/samsung.git
$ git clone https://android.googlesource.com/kernel/tegra.git [/code]

Here are some other links for sources

http://www.lg.com/global/support/ope...opensource.jsp [/code]
You may have to do some leg work and find your source.

As an example, we would build the kernel using the following commands:

Part A. Pre-build Steps
A. Open terminal and change to the root of your kernel directory
B. Type "export ARCH=arm"
C. Type "export CROSS_COMPILE=~/android/system/kernel/toolchains/arm-eabi-linaro-4.6.2/bin/arm-eabi-" (your toolchain may be different than this, it is an example)

Part B. The First Build
A. Type "make <your_config_name>_defconfig"
B. Type "make menuconfig" and make the required changes to use any modules you added or similar changes.
C. Type "make -j<maximum number of jobs>"

Part C. Re-Builds
A. Type "make clean"
B. Type "make oldconfig"
C. Type "make -j<maximum number of jobs>"

Part D. Building Modules
You have two options:
A. Type "make modules"
B. Type "make path/to/your/module.ko"

The above steps explained:
A-C. Self-Explanatory
D. Move our kernel binary into our output folder

E. This handy bit of magic finds all ".ko" modules and also copies them into your output file.

Part A.(These steps are required every time you close your terminal and re-open it to build again.)
A. Ok shouldn’t need to explain this.
B. This command sets your target architecture.
C. Defines the path to the toolchain we are going to use to compile our kernel. You can change this to point towards whatever toolchain you have downloaded or feel like using, the way it is currently configured it will use the Linaro toolchain that we downloaded above.

Part B.(These only need to be run the first time you build a kernel.)
A. Load's your configuration file from earlier.
B. Open up a menu to configure your kernel. It will use the config file you loaded in the previous step as a base.
C. Viola start the build. I typically allow 1 job per core, so on my quad core machine I put "make -j4". Just raising that number will not make your build faster, your processor needs to be able to support the number of jobs you are assigning it.

Part C. (Use the command's when you are building any-time outside of the first)
A. This command gets rid of any old/outdated binaries or modules you compiled before, and let's start fresh. I like to run it every I build unless my changes are really small and localized.
B. A very awesome command, it parses through what has changed and only prompts you about new options.
C. See the explanation for the above "Part C.".

Part D.(Use these for just building kernel modules.)
A. This will re-build all modules.
B. Will rebuild just the module you need. Very useful when you need to rebuild a WiFi module.

Outcome A. Build Succeds

W00t!! You have a kernel built by your self from source. There are a couple things you need in-order to use this kernel on your device any ".ko" modules and the zImage binary. If you pay attention to the output of your compiler then you will see the location of those objects. However the following commands will make your life a bit easier(Thanks Recognized Developer Hacre):
A. Open a terminal
B. Change to your root kernel directory
C. Type "mkdir ../<your_kernel>_output"
D. Type "cp arch/arm/boot/zImage ../<your_kernel>_output/zImage"
E. Type "find . -name "*.ko" -exec cp {} ../<your_kernel>_output \;"[/code]

The above steps explained:

You will also need to assemble a kernel image containing a initramfs for your device, along with the kernel binary and such. That however is beyond the scope of this tutorial. To get started though try searching the following phrases.

building android kernel image
xda build kernel image
xda unpack boot.img

Outcome B. Build Fails

Oh dear. It failed. Well guess what...this is going to happen..a LOT. Get used to it, and get used to googling and experimenting with different solutions. The following are some tips that will help you with debugging your issues.
Running a "Clean" build
A. Backup your config file(Type "cp .config ../backupConfig")
B. Re-run the build process using just your defconfig from earlier.

Limiting Output(Thanks Hacre.)
A. Another good tip is to run "make -j1" to get the error, as it will limit the amount of text you need to scroll through.[/code]

(from a kernel tutorial)(cred =thewadegeek)

The kernel binary is output as `arch/arm/boot/zImage`, and needs to be copied into the Android source tree in order to build the matching boot image.

Quotes from threads

"when building a whole ROM like AOSP,AOKP,PA or CM then they typically bundle the toolchain/kernel with the source, making this totally unneeded."

"You can typically find a manufacturer's configuration file in "arch/arm/configs". I believe the one for my HTC Flyer was called "flyer_hc_defconfig"

A Q&A from a thread

How can I build the latest kernel using all described stuff (aosp source, kernel config, latest kernel)?

Jean-Baptiste Queru
Mar 25
That's not possible without some work. Device-specific kernel are
typically 3 steps away from the upstream kernel: one step adds
android-specific code, one step adds chipset-specific code, one step
adds device-specific code.

THIS IS NOT COMPLETE.. IT IS A ADVANCED STEP ,LIKE STEP 8 it will take patience and time...

Last edited by WARP3D420Admin on Thu Jan 16, 2014 2:19 am; edited 2 times in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1

Posts : 195
Points : 3002164
Thanks : 7
Join date : 2014-01-02
Age : 41
Location : In da Swamps

PostSubject: iT'S JUST NOT THE SAME   Fri Jan 03, 2014 4:47 pm


This is the step for pulling the prop file or prop blobs from a "stock" phone...

This is the script that SuperR made for the Warp2



rm -rf $BASE/*

for FILE in `cat proprietary-files.txt | grep -v ^# | grep -v ^$`; do
DIR=`dirname $FILE`
if [ ! -d $BASE/$DIR ]; then
mkdir -p $BASE/$DIR
adb pull /system/$FILE $BASE/$FILE

This is one from the LGE Mako

and this one



rm -rf $BASE/*

for FILE in `cat proprietary-blobs.txt | grep -v ^# | grep -v ^$ | sed -e 's#^/system/##g'`; do
DIR=`dirname $FILE`
if [ ! -d $BASE/$DIR ]; then
mkdir -p $BASE/$DIR
adb pull /system/$FILE $BASE/$FILE

NOTICE: the main thing that changed was the


Your proprietary-file.txt depends on your phone.

I found that during a build, it actually told me diffrent .so files it needed.

Though if you made it this far, your phone is rooted, and you probably have "root explorer"
So you may want to open that up and orient yourself with what system files are in there.

Also, you can open other prop lists from similar phones and see what files they extracted.

Here is a list that PG and associates used

## RIL

## GPS

## Sensors


$$$$###$$# HINT #$$###$$$$


Last edited by WARP3D420Admin on Thu Jan 16, 2014 2:22 am; edited 4 times in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1

Posts : 195
Points : 3002164
Thanks : 7
Join date : 2014-01-02
Age : 41
Location : In da Swamps

PostSubject: Let's see if it works    Fri Jan 03, 2014 4:48 pm



Another time when RAM will help you out.

Whatever steps you actually took to get here all depends on how much work has been put into your phone and how much of it you were able to find..

So if you have the following things done, You can continue to build if not, you better go get them.

1. Linux 64 OS
2. Build environment
3. up to date Repo
4. device repo
5. kernel source
6. proprietary files text/ extract.sh
7. prebuilts
8. ccache
9. Build command
10 Teamwork and Patience

"But Warp, you never explained some of this stuff.."
Yep, that's why there is a step about actually building it...

This next section is pulled from PG's read me

Getting my ZTE Sequent repo

$ cd ~/android/system/device/

$ mkdir zte

$ cd zte

$ git clone https://github.com/playfulgod/androi..._zte_warp2.git warp2

Note it says ZTE, not Sony, not Samsung, ETC

Then cd to the kernel directory:

$ cd ~/android/system/kernel

$ mkdir zte

$ git clone https://github.com/playfulgod/kernel_zte_warp2.git warp2

Then prop files from stock..

$ cd

$ cd ~/android/system/device/zte/warp2

$ ./extract-files.sh

When the environment is setup, we need to grab a copy of Term.apk. This is necessary to build CM10.

$ cd ~/android/system/vendor/cm

$ ./get-prebuilts

O k so I waited to tell you about CCACHE at the end. I guess I did that, because you don't need it untill the end anyway..OR is building just the beginning
You decide...



There's a wonderful tool for gcc called ccache. You can read about it at their home page.

If you're always compiling the same programs over and over again — such as trying out several kernel patches, or testing your own development — then ccache is perfect. While it may take a few seconds longer to compile a program the first time with ccache, subsequent compiles will be much, much faster.

Now that we know what it is


Setting up ccache

You can optionally tell the build to use the ccache compilation tool. Ccache acts as a compiler cache that can be used to speed-up rebuilds. This works very well if you do "make clean" often, or if you frequently switch between different build products.

Put the following in your .bashrc or equivalent.

export USE_CCACHE=1

By default the cache will be stored in ~/.ccache. If your home directory is on NFS or some other non-local filesystem, you will want to specify the directory in your .bashrc as well.

export CCACHE_DIR=<path-to-your-cache-directory>
example: export CCACHE_DIR=$HOME/.ccache

The suggested cache size is 50-100GB. You will need to run the following command once you have downloaded the source code:

prebuilts/misc/linux-x86/ccache/ccache -M 50G

When building Ice Cream Sandwich (4.0.x) or older, ccache is in a different location:

prebuilt/linux-x86/ccache/ccache -M 50G

This setting is stored in the CCACHE_DIR and is persistent. (pulled str8 from the link)

Now, we build (system being your work directory):

$ cd ~/android/system

To build for the ZTE Sequent:

$ . build/envsetup.sh && brunch warp2

All credit to PG for his readme file...Which he updated it recently, this is the old one ,I think...

Last edited by WARP3D420Admin on Thu Jan 16, 2014 2:23 am; edited 4 times in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1

Posts : 195
Points : 3002164
Thanks : 7
Join date : 2014-01-02
Age : 41
Location : In da Swamps

PostSubject: Re: WARP3D420 $OURCE TUTORIAL   Fri Jan 03, 2014 4:50 pm

Beating your head on the desk when you can't figure out why it wont build, boot , ...


In the true nature of a 12 step program, this process never ends.. You will always run into errors, you will always be looking for fixes, patches, and anything to correct a problem you are having.

So, basically the 12th step is TEAMWORK

I hope if this tutorial didn't suck to bad, you will come on this thread and post your questions, post your answers, post your advice. I just started
AND no, just because I made a Tutorial and finished it, it DOES NOT make me a Developer. That was a joke. You have to earn that $hyt...

But one thing i am, is motivated...

I hope you enjoyed my rendition of "HOW-TO-BUILD-FROM-SOURCE"

Last edited by WARP3D420Admin on Sun Jan 05, 2014 10:37 pm; edited 4 times in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1

Posts : 195
Points : 3002164
Thanks : 7
Join date : 2014-01-02
Age : 41
Location : In da Swamps

PostSubject: Another piece of info.   Fri Jan 03, 2014 4:51 pm

"make clobber"

In software engineering, clobbering a file or computer memory is overwriting its contents. In makefiles, a common target clobber means complete cleanup of all unnecessary files and directories produced by previous invocations of the make command.

"make clean"

deletes any files generated by previous attempts, leaving you with clean source code

These are codes to use when

1. encountering fatal errors
2. when you "repo sync" new data
3. when you make changes to make files etc...

Last edited by WARP3D420Admin on Sun Jan 05, 2014 10:40 pm; edited 1 time in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1

Posts : 195
Points : 3002164
Thanks : 7
Join date : 2014-01-02
Age : 41
Location : In da Swamps

PostSubject: Re: WARP3D420 $OURCE TUTORIAL   Fri Jan 03, 2014 4:52 pm

Installation instructions
- Download ROM, Gapps ZIPs to your SD card
- Boot into clockworkmod
- Backup your current ROM (optional but highly recommended)
- Wipe Data / factory reset
- Wipe cache
- Advanced / Wipe dalvik cache
- install zip from SD card - choose ROM zip
- install zip from SD card - choose Gapps zip
- reboot
- let it settle for couple minute...

Last edited by WARP3D420Admin on Sun Jan 05, 2014 10:43 pm; edited 1 time in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1

Posts : 195
Points : 3002164
Thanks : 7
Join date : 2014-01-02
Age : 41
Location : In da Swamps

PostSubject: Re: WARP3D420 $OURCE TUTORIAL   Fri Jan 03, 2014 4:54 pm


but if your here
you already know that

They hack business'-- We hack phones

Your skill level..
Doesn't matter...

Hackerz, crackerz, even tallywhack smackerz
Coderz, themerz, modderz, NOOBian creeperz,
It doesn't matter

Just hit thankz and your name will be added to the team...

Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
Sponsored content

PostSubject: Re: WARP3D420 $OURCE TUTORIAL   

Back to top Go down
Back to top 
Page 1 of 1
 Similar topics
» Curl Tutorial!
» AOE_Fan's RMS Command Tutorial
» How to make .abk book ( Arena ) step by step... tutorial...
» i need help ;/
» IvanHoe 999946f x64 vs. IvanHoe B46fB x64, 2.800 games, still running

Permissions in this forum:You cannot reply to topics in this forum
Jump to: