I've been digging through the Vibrant forums for a while now, and I would like to try my hand at building the Froyo release. I downloaded the source and can compile the kernel just fine, but the platform part I am in the dark. Could someone help me with how to build the platform part? Once I get that done, I'll dig around to see how to convert it over to a flashable zip. Thanks in advance.
Slashazard said:
I've been digging through the Vibrant forums for a while now, and I would like to try my hand at building the Froyo release. I downloaded the source and can compile the kernel just fine, but the platform part I am in the dark. Could someone help me with how to build the platform part? Once I get that done, I'll dig around to see how to convert it over to a flashable zip. Thanks in advance.
Click to expand...
Click to collapse
Hey. I myself learning to build my own custom rom too!
Sent from my SGH-T959 using XDA Premium App
The platform source has not been released (and never will be). Only kernel source is required to be released.
Sent from my SGH-T959 using XDA App
In the source package there is a platform tar file. Do I download the AOSP code and overwrite those folders with what was in the platform tar from Samsung? Then build like AOSP?
go into android developement section here on xda or Ask some of developers here, if u ask nicely i think they might help u.
Related
I am currently trying to learn how to modify a kernel. Unfortunately, I cannot find ANYTHING that explains any of the files in the kernel source. I would greatly appreciate if someone would fill me in or show me where I can find any information on the subject.
Thank you in advance!
Sent from my PG86100 using XDA App
lyon21 said:
I am currently trying to learn how to modify a kernel. Unfortunately, I cannot find ANYTHING that explains any of the files in the kernel source. I would greatly appreciate if someone would fill me in or show me where I can find any information on the subject.
Thank you in advance!
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Google search is your best friend.
Compiling kernels from source isn't the hardest thing to do but cooking your own is a whole diff story. Heres a few suggestions!
You need to run a linux distro or run in a virtual box (if in windows or mac); I run ubuntu and Fedora.
Get familiar with github dude.
Learn linux basic commands.
Gbhil wrote this guide a while back so it will show outdated software but its pretty damn accurate. (just to give some insight)
http://forums.androidcentral.com/ht...how-build-your-own-kernel-package-source.html
I suggest following this guide:
Its for the EVO 4G so dont download the tar its telling you to DL, you need to get the EVO 3D kernel source.
http://htcevohacks.com/htc-evo-hacks/how-to-build-your-own-htc-evo-4g-android-kernel/
With a few variations
First clone the repository you want to build off of (Also, all of this needs to be done on a linux box or in a virtual machine running linux) You need to fork a repo from github of your fav kernel.
For example, to clone:
git clone git://github.com/insertkernelhere.git
cd insertkernelhere
Then you need a cross compiler for ARM, which is explained in the guide.
And the guide also explains menuconfig and building the kernel.
Kernels explained.
http://androidforums.com/evo-4g-all-things-root/278898-android-partitions-kernels-explained.html
You need to visit square one.
http://developer.android.com/guide/basics/what-is-android.html
For learning purposes: The anatomy of the linux kernel.
http://www.ibm.com/developerworks/linux/library/l-linux-kernel/
And last, Kernel Newbies!!! Great place for aspiring linux kernel devs
http://kernelnewbies.org/
Thats about all I got man, its alot but every question you have should be hanging around one of these links. You will have to dig around, read around, and browse around. Good luck
dirkyd3rk said:
Google search is your best friend.
Compiling kernels from source isn't the hardest thing to do but cooking your own is a whole diff story. Heres a few suggestions!
You need to run a linux distro or run in a virtual box (if in windows or mac); I run ubuntu and Fedora.
Get familiar with github dude.
Learn linux basic commands.
Gbhil wrote this guide a while back so it will show outdated software but its pretty damn accurate. (just to give some insight)
http://forums.androidcentral.com/ht...how-build-your-own-kernel-package-source.html
I suggest following this guide:
Its for the EVO 4G so dont download the tar its telling you to DL, you need to get the EVO 3D kernel source.
http://htcevohacks.com/htc-evo-hacks/how-to-build-your-own-htc-evo-4g-android-kernel/
With a few variations
First clone the repository you want to build off of (Also, all of this needs to be done on a linux box or in a virtual machine running linux) You need to fork a repo from github of your fav kernel.
For example, to clone:
git clone git://github.com/insertkernelhere.git
cd insertkernelhere
Then you need a cross compiler for ARM, which is explained in the guide.
And the guide also explains menuconfig and building the kernel.
Kernels explained.
http://androidforums.com/evo-4g-all-things-root/278898-android-partitions-kernels-explained.html
You need to visit square one.
http://developer.android.com/guide/basics/what-is-android.html
For learning purposes: The anatomy of the linux kernel.
http://www.ibm.com/developerworks/linux/library/l-linux-kernel/
And last, Kernel Newbies!!! Great place for aspiring linux kernel devs
http://kernelnewbies.org/
Thats about all I got man, its alot but every question you have should be hanging around one of these links. You will have to dig around, read around, and browse around. Good luck
Click to expand...
Click to collapse
Thank you very much! I would push the thanks button but I'm on my phone. Will do it when I get on the computer next time.
Sent from my PG86100 using XDA App
I've tried porting several roms to my devices and every time I try to flash I always get status 0 or some type of error! I can't logcat from recovery because some things do not work completely with clockworkmod I have. I even manually tried porting the same method that android kitchen does and still run into the same problem. I have no idea what I should try next? This is really making me made. I get no help at all after searching and searching every where!
android kitchen
http://forum.xda-developers.com/showthread.php?t=633246
all in one guide
http://forum.xda-developers.com/showthread.php?t=1273718
And some other methods and still no luck!!
You are right. There is no guide. It's trial and error. Logcat helps and if you know what certain files do that helps too.
It's simple:
grab the sources from github, add your device and vendor folder, add the device to the list in the mk files, lunch, and build.
openetna is a repository with many bugfixes, as you will have them.
Easy ****!
mDroidd said:
It's simple:
grab the sources from github, add your device and vendor folder, add the device to the list in the mk files, lunch, and build.
openetna is a repository with many bugfixes, as you will have them.
Easy ****!
Click to expand...
Click to collapse
Thats great if building from source
but i think he is talking about porting roms that are not AOSP.
The problem with a porting tutorial is that all devices and roms are a bit different so there will never will be a tutorial to get this done 100%. They are great guides to give you a start but it can take a lot more to get things ported.
if the device architecture is similar
Ex... Evo 4g to Incredible
than porting is fairly easy
being able to logcat is very necessary when porting roms
getting that working is your first step.
I always gave up on porting just because i dont have the patients to do it.
Exactly. I've ported several roms from the E3D and Sensation to the Rezound, and they are easy because the processor is the same. All you really need to get it booting is the kernel in most cases.
mDroidd said:
It's simple:
grab the sources from github, add your device and vendor folder, add the device to the list in the mk files, lunch, and build.
openetna is a repository with many bugfixes, as you will have them.
Easy ****!
Click to expand...
Click to collapse
Not that simple if you have to make a device tree from scratch like I'm doing
I've a question!!
I have an HTC Explorer (based on Qualcomm MSM7227) and I'd like to build a rom (AOSP or Cyano)...
I've downloaded Kernel Source Code but after hours of researches I haven't found a guide for merge a rom with a kernel..
can you help me?
thank you!
Can we port a rom from HTC desire to Motorola defy....is it easy??
HIT THANKS IF IVE HELPED
extremists said:
Can we port a rom from HTC desire to Motorola defy....is it easy??
HIT THANKS IF IVE HELPED
Click to expand...
Click to collapse
That's about as hard as it gets.
Unless building from source its not as difficult.
Sent from my PG86100 using Tapatalk
wes342 said:
That's about as hard as it gets.
Unless building from source its not as difficult.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Do u know how to port??
HIT THANKS IF IVE HELPED
The thing is there's also no real guide on how to make your own public repo for devices who don't have one .
E.g. Galaxy R
Herpderp Defy.
So I found out how to build from cm7 sources and it is a no go... I do not know how in the world you guys can port any roms. How do you get your files up on git hub any way? There is more to it then just compiling from cm sources..
Here's a slightly outdated one
EmoBoiix3 said:
The thing is there's also no real guide on how to make your own public repo for devices who don't have one .
E.g. Galaxy R
Herpderp Defy.
Click to expand...
Click to collapse
Just so its clear... this (slightly outdated) guide would be (the best I've found) for building a device tree (that you may elect to throw up on github) that can be used to build AOSP.. the same device tree probably could build CyanogenMod or MIUI fairly easily (minimal editing) but you are correct... no exact guide bc its not an exact science (lots of different devices out there with lots of different device configurations; even kernels different some are ti omap, some are qualcomm msm, etc.). Basically you build a tree to define your hardware.. AOSP, CM or MIUI will build themselves based on this definition (device) tree.
http://www.kandroid.org/online-pdk/guide/build_new_device.html
Now after you follow this guide, google the various build errors you get (one at a time) and perfect your tree until you get basic bring up... then perfect it some more until you get all your modules working (will take some aosp kernel cooking as well)... then perfect it some more... in a few months you should have something pretty decent (and learn tree building a bit more; we all learn by doing ) Best advice I have for you; going through the same thing myself.
Also wouldn't be a bad idea to download Hardware Info apk (Sleek Apps) and email yourself the info it spits out. That way you at least have a list of some of the hardware you are trying to define.
Rob
mDroidd said:
It's simple:
grab the sources from github, add your device and vendor folder, add the device to the list in the mk files, lunch, and build.
openetna is a repository with many bugfixes, as you will have them.
Easy ****!
Click to expand...
Click to collapse
How exactly do you do this? How do you build it completely specifically for your device?
Sorry, I'm a complete noob on building from scratch and Linux. Could anyone shed some some light?
Thanks you guys
What are the languages/tools you need to build a rom for scratch and i dont mean just adding themes and someone else's stuff..?
Thanks
Android SDK, a good graphics editor (not ms paint), Google and xda forums.
Also, open source means building on the work of others. Its recommended to use a working rom as base, then remove what you don't want, and add what you need (this includes all system apps, files, kernel, etc)
You need Ubuntu and a whole lot of code knowledge
This was sent from a Galaxy Ace. Problem?
Ubuntu . Python
Jdk
Sdk
And more i thought
Sent from my GT-i9070 using xda premium
Hello !
In Tutorial about compile AOSP GB i see one think. When I write in terminal lunch i have list devices which i can compile. So I am in trouble becouse i don't know how can i add My device. I Download Source GB to my device but I have external folder, bionic and probably hardware (and kernel) So My Question is - How can I Add My phone to compile list, to compile flashable zip work?:fingers-crossed:
cheqolada said:
Hello !
In Tutorial about compile AOSP GB i see one think. When I write in terminal lunch i have list devices which i can compile. So I am in trouble becouse i don't know how can i add My device. I Download Source GB to my device but I have external folder, bionic and probably hardware (and kernel) So My Question is - How can I Add My phone to compile list, to compile flashable zip work?:fingers-crossed:
Click to expand...
Click to collapse
What is your device?
Sent from my GT-I9100 using xda app-developers app
xSkArx said:
What is your device?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Alcatel Ot - 908 / T-Mobile Move.
Hi,
As a noob i came across a word related to android "compiling". What does compiling exactly mean?
Not very experienced with android but compiling usually means converting codes to executables
Sent from my LT30p using xda app-developers app
Zip->unzip
Compile->install
sony xperia ray
ics 4.0.4 rooted
stock rom
126 posts on XDA and you still don't know how to use Google or a dictionary?
snapper.fishes said:
126 posts on XDA and you still don't know how to use Google or a dictionary?
Click to expand...
Click to collapse
i do but i am not sure does compling mean making a rom?
Nono...see in terms of android.
Decompiling= breaking some files into many parts
Compiling=Joining the broken parts to get back the original file back.
Its usually associated with Decompiling and Compiling apk files to mod them or stuffs.
Dont worry we all were "noobs" once
TarunDham said:
i do but i am not sure does compling mean making a rom?
Click to expand...
Click to collapse
It's not too different from the usual programming definition of compiling. When you write a programme, you write it in a higher language that reads almost like English (unless if you are a nut case/genius who likes coding in assembly). However, for a computer (in this case your phone) to run it you have to translate the programme into machine readable language first. This translation process is called compiling.
Sent from my Nexus 4 using Tapatalk 2
---------- Post added at 01:11 AM ---------- Previous post was at 12:59 AM ----------
Rittik said:
Nono...see in terms of android.
Decompiling= breaking some files into many parts
Compiling=Joining the broken parts to get back the original file back.
Its usually associated with Decompiling and Compiling apk files to mod them or stuffs.
Dont worry we all were "noobs" once
Click to expand...
Click to collapse
I am afraid that is not the correct definition of compiling. The apk file is just a zip file of media files and code. When you break apart an apk file all that you are doing is just unzipping. The codes are still inaccessible. To be able to read them humanly you need to decompile the codes, which is usually impossible. That is why people need to post source codes.
Compiling takes quite a bit of computing power and can take hours if your code is long. Packaging and signing an apk? Not si much.
Sent from my Nexus 4 using Tapatalk 2
phew........... dat was a lot... hahaha i read a tutorial here that says "compile a gingerbread rom" so will that tut make me a gb rom??
It should, just make sure it's meant for your phone
Sent from my Nexus 4 using Tapatalk 2
snapper.fishes said:
It should, just make sure it's meant for your phone
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
here's the link
http://forum.xda-developers.com/showthread.php?t=1598713
so what do u think?
That guide was for porting roms made for other devices using roms that already exist for your device. For example, someone has already made a cm7 rom for your device, but you want a miui rom. Since miui is based on cm7, you can use the guide to create a miui rom for your device. However, if nobody has made a cm7 rom for your device, you cannot use that guide to port miui rom.
If you read the guide carefully, it's just a while load of copy and paste work, hence not compiling. The guide teaches you to take advantage of existing work done by other people instead of starting from the scratch, but it can't teach you to build a rom from scratch.
Sent from my Nexus 4 using Tapatalk 2
snapper.fishes said:
That guide was for porting roms made for other devices using roms that already exist for your device. For example, someone has already made a cm7 rom for your device, but you want a miui rom. Since miui is based on cm7, you can use the guide to create a miui rom for your device. However, if nobody has made a cm7 rom for your device, you cannot use that guide to port miui rom.
If you read the guide carefully, it's just a while load of copy and paste work, hence not compiling. The guide teaches you to take advantage of existing work done by other people instead of starting from the scratch, but it can't teach you to build a rom from scratch.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
i totally agree with you but in the start of the post the guy says "Android Source | Compile GB | Compile ICS | Compile JB ~ Thanks dastin1015 |- Building/Compiling - Durations" what does that mean? will the link to the tut help me make a gingerbread for my ics based device??
and last advice will porting any roms to my device has any threat to it like bricking???
I took a look at those links. The first link is simply what it says - the basic source code for Android. The other compile links contain instructions on how to compile the source code into roms. They do not teach you how to write the source code for different devices, which is the most difficult part of porting a rom. Anyone can learn to compile a rom from pre written codes. It's the writing part that matters. You need to find the drivers and other proprietary codes for your device.
The guides can help you get started on making a gingerbread rom, but it won't fix the hundreds of bugs you are sure to encounter.
As for bricking, there's always going to a chance that flashing a rom might brick your device.
Sent from my Nexus 4 using Tapatalk 2
snapper.fishes said:
I took a look at those links. The first link is simply what it says - the basic source code for Android. The other compile links contain instructions on how to compile the source code into roms. They do not teach you how to write the source code for different devices, which is the most difficult part of porting a rom. Anyone can learn to compile a rom from pre written codes. It's the writing part that matters. You need to find the drivers and other proprietary codes for your device.
The guides can help you get started on making a gingerbread rom, but it won't fix the hundreds of bugs you are sure to encounter.
As for bricking, there's always going to a chance that flashing a rom might brick your device.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
thaknz a lot for ur help
To sum up in basic words, compiling is turning a code from a high language into machine code so the computer can read it.
Also , if you din't know what is compiling i don't think you should be making roms