Database Develop

[Q] So I want to port a rom......

What is porting a rom? I think it is just taking a rom from different phone and making it work on another device....is that right?
If that is right I want to port a rom or roms from the Nexus One to the HTC Hero CDMA.
But can anyone list what tools and knowledge I will need? I'm running windows 7. So any programs or books I need to read can someone give links to information about the book, or links to download/buy the program that I'll need to get started on porting roms to our HTC Hero CDMA.
Also can someone tell me the pros and cons of porting roms as well?
Thanks, I can't wait to get started on this

Try using the ultimate theme injector is what I've been using
Sent from my DROIDX using XDA App

If you really want to get into it I suggest running a Linux distro. I run ubuntu 10.04. Haven't had windows on my computer since August of last year. Took a little while to get use to, but I now like it better. Also gives you the ability to get repos, compile Android and kernels, and much more.
Depending on what you are porting it might require new drivers, xml edits and resizing, the theme injector will only do so much. I think it will only replace and resize images.
Sent from my dual-booted liquidsense 2.1

spleef said:
Try using the ultimate theme injector is what I've been using
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
so i use this for resizing/replacing images.....
unCoRrUpTeD said:
If you really want to get into it I suggest running a Linux distro. I run ubuntu 10.04. Haven't had windows on my computer since August of last year. Took a little while to get use to, but I now like it better. Also gives you the ability to get repos, compile Android and kernels, and much more.
Depending on what you are porting it might require new drivers, xml edits and resizing, the theme injector will only do so much. I think it will only replace and resize images.
Sent from my dual-booted liquidsense 2.1
Click to expand...
Click to collapse
and then you say use my linux distro for everything else.....but where are the links tutorials/books i need to read/tools i'll need to get started on the rest of the stuff for porting roms?
thanks for helping btw

Have you built any roms yet? I'd suggest getting a kitchen and playing around with a known good rom - get used to what's there, what you can change, things like that. I've been playing around with dsixda's HTC Android Kitchen (on WinXP using Cygwin) lately with a few ROMs (my stock rom, liquid sense, aosp, and CM6). That's the best way to learn IMO.

TJinWV said:
Have you built any roms yet? I'd suggest getting a kitchen and playing around with a known good rom - get used to what's there, what you can change, things like that. I've been playing around with dsixda's HTC Android Kitchen (on WinXP using Cygwin) lately with a few ROMs (my stock rom, liquid sense, aosp, and CM6). That's the best way to learn IMO.
Click to expand...
Click to collapse
OOOOOOOOOH!!!!!11
that sounds like that might actually work....once i get a kitchen set up on linux mint. play around with a few different roms and see what i'm able to change, find out what it is that i'm changing and what changing it does.....AAAAHHH YOU'RE A GENIUS!
That sounds like that will work for learning to begin to develope beginner roms, and improve roms.
But now that you've got me set for like the first few months of learning. I don't want to post another thread about porting roms, so anyone know any information on porting roms? I know the user above said use a theme injector but that is for resizing and editing the images of the rom im porting. There has to be more to porting a rom than just resizing images. I'm trying to get all my information ahead of time so that i can just jump into developing with little to no questions for our device

kifno, that kitchen also has "experimental" porting tools in the Advanced Menu. I meant to say that in my original post.

TJinWV said:
kifno, that kitchen also has "experimental" porting tools in the Advanced Menu. I meant to say that in my original post.
Click to expand...
Click to collapse
Thanks for letting me know. Now once I begin porting roms I'll have at least a start. Thanks everyone
Sent from my DROIDX using XDA App

kifno said:
Thanks for letting me know. Now once I begin porting roms I'll have at least a start. Thanks everyone
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
If your open to Suggestions... Try going to theunlockr.com, and Select the "How to's" Then Look for the Rom Development section... Know what, I'll do it for you!
Hold on!!
Ok here you go:
Watch these videos, see if they Help you out a bit!
http://theunlockr.com/category/howt...-development-how-tos/rom-development-how-tos/
Sent from my Hero using XDA App

Developing Sense ROM

Hi guys!
Since two days I'm trying to create a ROM based on HTC Sense, porting from HTC Desire to our Nexus One using, as a base, the RCADSmixHD ROM.
I've been able to complete the entire package .zip and installing succesfully, BUT at reboot I'm stuck at the Nexus logo...
Do you think it's a kernel-related issue?
I really don't have any other ideas...
EDIT: I'd also like to know how to develop/modify a kernel for our Nexus One, but based on HTC roms... Someone has guides/links?

Try to Flash this Kernel: 2.6.35.6-eViL--10-7--1-wmcfg by eViL D:
You can find dl link here : http://forum.xda-developers.com/showpost.php?p=16995049&postcount=2
I had problems with the kernel include in RCADS on my N1

Thanks but no changes here... BTW the kernel included in RCADS rom works with my Nexus.. But here in this new ROM that I'm trying to develop I don't know what's wrong...

My guess there's something wrong with the ROM itself you probably have a few lines of code somewhere that are not working right. Were you able to compile the code on your computer?

Well, actually I'm trying to port a Sense ROM from HTC Desire with 250mb fit into /system/... I think that's the problem because my Nexus One could have bad blocks and/or less space into /system/, so this ROM wouldn't fit. I think so.
Regarding the code, I haven't written any kind of code, apart from looking at updater-script to be ok... Other suggestions? Thanks anyway, much appreciated

Now I'm trying to port a different ROM, the Desire S Gingerbread 2.3.5 with Sense 3.0!
But after replacing many folders and files from a Sense Rom of the Nexus One and the target Sense Rom that I'm developing, I have replaced boot.img and edited the updater-script properly (I think).
After installation, it's stuck at the Nexus logo... always!
What's wrong????????

Look at your logcat.
And at your /proc/kmsg.
If you don't know what these 2 mean - read up on those, use some googling.
If you can't - I believe you won't be able to develop anything worthy, or anything at all.
Moreover, Nexus has 145MB on /system partition. You need to utilize SD-EXT partition and symlink parts of the ROM to make it fit.
If I'm speaking Chinese and you can't figure it out - read the previous paragraph

From your posts I can't detrmine if you are developing or just trying to flash the rom to your phone, since you haven't done any coding. Am I misunderstanding?

rugmankc said:
From your posts I can't detrmine if you are developing or just trying to flash the rom to your phone, since you haven't done any coding. Am I misunderstanding?
Click to expand...
Click to collapse
You're right, because I'm not coding for a completely new ROM..
I'm just trying to "assemble" different pieces of ROMs together, a porting!
The only thing to "code" is the updater-script (or update-script)...
I have some errors there and I can't really determine why certain things goes wrong.. for now I don't have full knowledge of system partitions of Android.
And now I don't have enough time to fully explore this complex world
I have just tried for a couple of days...

Iperzampem0 said:
You're right, because I'm not coding for a completely new ROM..
I'm just trying to "assemble" different pieces of ROMs together, a porting!
The only thing to "code" is the updater-script (or update-script)...
I have some errors there and I can't really determine why certain things goes wrong.. for now I don't have full knowledge of system partitions of Android.
And now I don't have enough time to fully explore this complex world
I have just tried for a couple of days...
Click to expand...
Click to collapse
What did you add to the updater-script? And which folders specifically did you replace and change? And did you use a rooted ROM or the OTA one for the desire?

@Ace42:
Hi, I had used a rooted ROM from the Desire thread and I have followed this pretty useful guide which illustrates how to port Sense Roms:
http://forum.xda-developers.com/showthread.php?t=1222746
I have also had a look at almost all the files into each folders to see if there was differences in the code between the 2 roms..!
BTW the problem is in the updater-script...
For example I'm not able to mount "sd-ext", which is one of the most important steps to do for the Rom to being able to run into the device.

Look at that link properly, porting sense to OTHER SENSE DEVICES.
N1 isn't a sense device.
First, porting is more than replacing your boot.img and changing your update-script.
Like the other user said, you need to symlink files to your SD card cause N1 just isn't big enough.
Second, you're taking roms from other devices, most probably you'd have to re-write or mod the drivers.
Third, Porting just isn't that easy.

@illuminarias:
-> I know that, and in fact N1 becomes a Sense device when it has a Sense rom already installed... so it can be compared with other Sense devices.
-> I also know that we must symlink files, and you do that by adding lines of code into the updater-script (or update-script)!
-> If no one starts from something, how do you think that development for N1 can continue??

Iperzampem0 said:
@illuminarias:
-> I know that, and in fact N1 becomes a Sense device when it has a Sense rom already installed... so it can be compared with other Sense devices.
-> I also know that we must symlink files, and you do that by adding lines of code into the updater-script (or update-script)!
-> If no one starts from something, how do you think that development for N1 can continue??
Click to expand...
Click to collapse
The n1 also runs miui, is comparable to the m1? No.
Sent from my HTC Sensation Z710e using xda premium

illuminarias said:
The n1 also runs miui, is comparable to the m1? No.
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
I'm sorry but personally I love HTC Sense, not a-bad-copy-of-iPhone such as MIUI.
And since now I don't have money to change the device, I'll stick with this for other time.
Cheers

Iperzampem0 said:
I'm sorry but personally I love HTC Sense, not a-bad-copy-of-iPhone such as MIUI.
And since now I don't have money to change the device, I'll stick with this for other time.
Cheers
Click to expand...
Click to collapse
Yes, the same for me. I Love my nexus one with sense. Currently i also working on a gb sense rom for my nexus. Update Script is done and system should fit now with 151mb into the nexus rom. I ll will try to install & boot it at the weekend. Base was the currrent 2.3.3 Desire Release... Hopefully it fits into the small system and boots , to get logcats to work with...
If someone want to help & try, please contact me. I can upload the rom then to test. Currently i don´t have a lot of time , maybe together we get a working release...

@Deep-Knight:
Yep, I was working yesterday evening with the official Desire gingerbread update from HTC, but, as always, I'm stuck at the Nexus logo, after the installation is done... :/
I think I'm doing something wrong with system partition.. I know that our N1 can handle only 150mb for /system...
But I must admit that I'm using almost the same updater-script and boot.img as the N1Sensation v0.5 rom or RCADSmixHD rom..

Deep-Knight said:
Yes, the same for me. I Love my nexus one with sense. Currently i also working on a gb sense rom for my nexus. Update Script is done and system should fit now with 151mb into the nexus rom. I ll will try to install & boot it at the weekend. Base was the currrent 2.3.3 Desire Release... Hopefully it fits into the small system and boots , to get logcats to work with...
If someone want to help & try, please contact me. I can upload the rom then to test. Currently i don´t have a lot of time , maybe together we get a working release...
Click to expand...
Click to collapse
Just make a thread and upload your beta version, theres a plenty of people here able to test and help.

Thank you Menelkir for your interest!
But first I'll have to create something useful.. Maybe later on I'll create a new thread..
Till now I'm using some HTC Desire's ROM from the dedicated section here at XDA.
Stay tuned guys
As always graphical glithces will not be solved, until HTC releases Desire's Source Code..

The code is released already.
Unfortunately, the real trouble with porting ROMs is fixing the things that don't work - which will include trackball, hotspot etc - and this is the part where most of ROMs fail, because very few developers are skilled enough for that.

[RUU][DEVS ONLY][For Porting] HTC Pico [Sense 3.5][Android 2.3.5][Sense Zero]

From the Hero section:
flashinglights said:
Found this while searching around google. It's a leaked RUU for the HTC Pico "explorer" which is a light version of Sense 3.5 on android 2.3.5 or most commonly known as "sense zero". I thought I would post it up so that you'll can start porting over to the hero.
The Pico specs are rather similar to our phone so it shouldn't be to difficult for someone to port it over, it's also mdpi so no resizing will be necessary.
If you are already considering taking on this project then more than likely you already know how to setup a flashable rom from a ruu but in case you need some refreshing the following will help:
Instructions:
- dsixda kitchen will need to be installed prior to starting.
1. Run RUU and leave open
2. Type %TEMP% in your computers start menu search bar.
3. Search through the folders in there with the long names with numbers and letters, you'll find a zip file named "rom.zip" in there.
4. Place the rom.zip in the original_update folder located in the "kitchen" directory
5. From there follow the steps on the kitchen menu to setup the rom.
6. Then proceed to porting to the hero. :]
- Download Pico RUU
Credits to capychimp for posting the leak up.
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/showthread.php?t=1275108
First ROM port to Hero: http://forum.xda-developers.com/showthread.php?t=1284083
EDIT: Sorry, i read this on the XDA front page where they wrote that Pico has QVGA resolution which apparently it has not. It´s HVGA.
...The interesting thing about the Pico is the fact that it is loaded with Sense 3.5, which happens to be called Sense Zero for this particular device. Due to having similar specs such as QVGA resolution and ARMv6 processor....
Click to expand...
Click to collapse
EDIT 2: It boots on QVGA brother Wildfire: http://forum.xda-developers.com/showthread.php?t=1285694

Now that is a progress.....
Sent from my HTC Tattoo using xda premium

Wow, fingers crossed. There haven't been any bigger breakthroughs ever since KalimochoAz figured out the cam drivers for 2.3...

I dont think this would be possible.. First of i dont think the tattoo is capable of running it smoothly enough.. And second the Hero's resolution is bigger than the one on the tattoo, so it would need to be resized..
And last .. Im afraid theres no devs with enough skill back with a tattoo

I'm interested on working on this but I have never worked on a rom before. I just have experience in java/c++ and some android app programming. Can anybody point me to the right direction? I think i can devote much time to this project.

i hope if this can be run on tattoo )))

KrisInfinity said:
I'm interested on working on this but I have never worked on a rom before. I just have experience in java/c++ and some android app programming. Can anybody point me to the right direction? I think i can devote much time to this project.
Click to expand...
Click to collapse
From what i can remember on my time with rom cooking you will need a so called "Rom kitchen" .. Try searching for it here.. Maybe you could ask someone who has more experience, and get them to point you to the right direction ?

Following links are at least a start
[DEV][SENSE] Porting sense to other sense devices
How To: Create Your Own Custom ROM for Android
[KITCHEN][September 10 '11] Android Kitchen, v0.179 [Linux / Mac / Windows]

Thank you for the links. I'll be starting right now reading.

KrisInfinity said:
Thank you for the links. I'll be starting right now reading.
Click to expand...
Click to collapse
you might want to consider my earlier post to have more system space, while you work on porting
[SCRIPTS][GUIDE] Resizing Tattoo partitions
it would give you flexibility to flash these ROMs with out an issue of system memory.

rallapag said:
you might want to consider my earlier post to have more system space, while you work on porting
[SCRIPTS][GUIDE] Resizing Tattoo partitions
it would give you flexibility to flash these ROMs with out an issue of system memory.
Click to expand...
Click to collapse
Thank you.
I had a look at the Wildfire section and saw a similar project. They had managed to get it booting, but at the moment it was unusable.
http://forum.xda-developers.com/showthread.php?t=1285694
In the meantime, to get more comfortable with the tools and development I've decided to resume the development of the Sense 2.2 Rom port from the wildfire.

KrisInfinity said:
Thank you.
I had a look at the Wildfire section and saw a similar project. They had managed to get it booting, but at the moment it was unusable.
http://forum.xda-developers.com/showthread.php?t=1285694
In the meantime, to get more comfortable with the tools and development I've decided to resume the development of the Sense 2.2 Rom port from the wildfire.
Click to expand...
Click to collapse
Hey good thinking, then you could use following ROMs as base (not exclusive):
Build Number : 2.37.415.1
Android Freedom Wildfire 2.2.1 Arabic sense
STEAM V1.0 by o TRiPPiNz (Also supports Arabic for Arabic users)
Based on official: 2.34.75.1
WildPuzzleROM_2.2.1 v0.8
as you know TatFroyoSense is based on build 2.22.405.1
2.22.405.1 r1 - MoDaCo Custom ROM (Froyo 2.2.1)
Later version had the contacts apk fixed and the live wallpaper support and slightly faster.
I could build a dirty ROM from DanneJo's Wildpuzzle ROM, but it has problem with wifi and accelerometer.
a dirty hack had activated wifi.
I am not a dev and had very poor programming experience.
If you can do this project, that is best for us to get a decent product.

rallapag said:
Hey good thinking, then you could use following ROMs as base (not exclusive):
Build Number : 2.37.415.1
Android Freedom Wildfire 2.2.1 Arabic sense
STEAM V1.0 by o TRiPPiNz (Also supports Arabic for Arabic users)
Based on official: 2.34.75.1
WildPuzzleROM_2.2.1 v0.8
as you know TatFroyoSense is based on build 2.22.405.1
2.22.405.1 r1 - MoDaCo Custom ROM (Froyo 2.2.1)
Later version had the contacts apk fixed and the live wallpaper support and slightly faster.
I could build a dirty ROM from DanneJo's Wildpuzzle ROM, but it has problem with wifi and accelerometer.
a dirty hack had activated wifi.
I am not a dev and had very poor programming experience.
If you can do this project, that is best for us to get a decent product.
Click to expand...
Click to collapse
Thank you for the links.
I've also seen RemPuzzleRom which is a continuation of WildPuzzleRom and contained some interesting hacks, especially one on keeping the launcher in memory (which TatFroyoSense lacked).
I'll try porting STEAM tomorrow and see how everything works. Once I get some concrete results I'll start a new thread as this is moving away from the original topic.

Onecosmic's ICS Port RC3 is up for i9000/b and vibrant and cappy will be very soon.

Code is back up, we're hosting there again now. Grooby's thread is not under control by us and anything he says/does is not condoned by onecosmic or his team.
We're up to rc3 now and the rom is much more stable than before, seems to be performing better and people are working on fixes for gps,it should be working soon. updates are on the google code pages here: http://code.google.com/p/ice-cream-sandwich-sgs/
The rom should now be flashable from anything,just wipe and flash.

Thanks, will give it a try
Sent from my SGH-T959 using XDA App

lol, hopefully someone is able to put up a new mirror for it.
xD
Seems like a very popular file.

CM t9 Dailer and cm launcher now as a flashable zip
Thread Link

This Rom is fast and smooth ,music player is perfect loving it, gallery work great too and there is a fix for root in the i9000 tread http://www.megaupload.com/?d=S67I9Q0L .front camera is still broken ,recorder.and brightness not working just those fews bugs to be fix and this rom is going to be one of the best ICS rom .great work onecosmic's..........

I really don't understand the vibrant dev community. Or maybe it's just a problem with xda in general the the belief that every single dev here is on his own to create his own grand master ROM and screw the rest (besides the big names like Cyanogen and others).
But when there is another perfectly good ROM out there, that is under active development and has already solved many of the major problems with the current code, and then someone forks the code and essentially starts over, it is a real tragedy.
"onecosmic," please work with the devs in this thread to improve the ICS build that already has months of work put into it, instead of creating your own:
http://forum.xda-developers.com/showthread.php?t=1362961

a2296455 said:
I really don't understand the vibrant dev community. Or maybe it's just a problem with xda in general the the belief that every single dev here is on his own to create his own grand master ROM and screw the rest (besides the big names like Cyanogen and others).
But when there is another perfectly good ROM out there, that is under active development and has already solved many of the major problems with the current code, and then someone forks the code and essentially starts over, it is a real tragedy.
"onecosmic," please work with the devs in this thread to improve the ICS build that already has months of work put into it, instead of creating your own:
http://forum.xda-developers.com/showthread.php?t=1362961
Click to expand...
Click to collapse
Taking nothing away from neobuddy or teamhacksung, onecosmic did have the first ICS for the Galaxy S posted.
http://forum.xda-developers.com/showthread.php?t=1338636

a2296455 said:
I really don't understand the vibrant dev community. Or maybe it's just a problem with xda in general the the belief that every single dev here is on his own to create his own grand master ROM and screw the rest (besides the big names like Cyanogen and others).
But when there is another perfectly good ROM out there, that is under active development and has already solved many of the major problems with the current code, and then someone forks the code and essentially starts over, it is a real tragedy.
"onecosmic," please work with the devs in this thread to improve the ICS build that already has months of work put into it, instead of creating your own:
http://forum.xda-developers.com/showthread.php?t=1362961
Click to expand...
Click to collapse
stop being a steve jobs

a2296455 said:
I really don't understand the vibrant dev community. Or maybe it's just a problem with xda in general the the belief that every single dev here is on his own to create his own grand master ROM and screw the rest (besides the big names like Cyanogen and others).
But when there is another perfectly good ROM out there, that is under active development and has already solved many of the major problems with the current code, and then someone forks the code and essentially starts over, it is a real tragedy.
"onecosmic," please work with the devs in this thread to improve the ICS build that already has months of work put into it, instead of creating your own:
http://forum.xda-developers.com/showthread.php?t=1362961
Click to expand...
Click to collapse
so you want onecosmic to stop working on the rom that allowed neo to even release ICS on the vibrant. Also he doenst have a vibrant, this rom is originally for the sgs and is ported over, hence why we need to flash another kernel. The problem with the vibrant community isnt the devs its the people like you that expect a rom that is 100 percent perfect and on top of that does your dishes and makes bacon
What you should do is go talk to neo about helping out with the rom instead of kanging cm and other applications. I swear his roms have more bloat on them then twiz.

a2296455 said:
I really don't understand the vibrant dev community. Or maybe it's just a problem with xda in general the the belief that every single dev here is on his own to create his own grand master ROM and screw the rest (besides the big names like Cyanogen and others).
But when there is another perfectly good ROM out there, that is under active development and has already solved many of the major problems with the current code, and then someone forks the code and essentially starts over, it is a real tragedy.
"onecosmic," please work with the devs in this thread to improve the ICS build that already has months of work put into it, instead of creating your own:
http://forum.xda-developers.com/showthread.php?t=1362961
Click to expand...
Click to collapse
LMAO, dude you're an idiot. I hope you brick your phone just because.

bearsfan85 said:
What you should do is go talk to neo about helping out with the rom instead of kanging cm and other applications. I swear his roms have more bloat on them then twiz.
Click to expand...
Click to collapse
Now that was uncalled for.
I understand that onecosmic was the first to build a functional ICS for the Galaxy S series, but that does not mean he has to be the only one. What's wrong with KANG'ing something? Neo isn't taking credit for anything, he's gave credit where credit was due.

I'm on neobuddy ics can i flash firs the rom and them the kernel or this rom uses a different partitions and i need to flash first the kernel reboot recovery flash rom/flash kernel and them reboot system
Sent from my SGH-T959 using xda premium

Passion v6 & v7 vs Onecosmic
What we want in this community is quality ROM's. No one has a monopoly on good ideas and we as users always benefit when we have more than one group working on competing ideas.
I tried and respect Neo's ICS Passion Roms. I've been using them since v5. v6 is a good daily ROM. v7 was too laggy for me.
Onecosmic's 4.0.3 ROM is much smoother. From the first boot. Brightness doesn't work. But everything else does.
For me, this demonstrates the value in alternatives.
Good work Onecosmic.

Try screen filter if you need to lower brightness
Sent from my SGH-T959 using XDA App

From my understanding, Neo's rom is still 2.X kernel while Onecosmic's is 3.X based. Different approaches I guess. Onecosmic is more than happy to help out with the Vibrant community, you just have to ask. I tried the latest and had an issue with the cpu staying on full blast and chewing up the battery so I went back to stock MIUI until he hammers a few other things out.

Nice way to turn a pretty thread in a flamewar, guys :/
Either way, does video recording works here?
And can I flash over Neo's ICS build or only over ICS?
I wish the OP was more informative...

So the OP says to first flash an ICS kernel.
Can I use the Vibrant ICS kernel here or do I use an i9000 one?

After installing this rom my phone will not reboot into recovery... is their a special way to get back into recovery?

Can anyone check if there mute/unmute issue present on this ROM ?

Anyone else have no service after flashing this?

Anybody willing to guide a newbie?

Hi everyone!
I'm looking to become a future dev of the Samsung Captivate Glide, but as we're awaiting the official ICS from AT&T the forum right now is pretty dead. We have a project going but nobody to guide us, and we wish to compile CM9 or AOSP ICS. Would anyone take me in and teach me the basics of ROMing? I would greatly appreciate it! I have a Mac and Windows, I'm not sure if Linux is required :|
~Aquethys

the rom is the least of the worries to get dev going on your phone, getting the kernel going is the hard part. does your phone have the source code released?

I don't believe so, people in our ics port thread are saying we don't have a working ics kernel. We do have a gingerbread kernel though... :/
How would I start?
Sent from my SAMSUNG-SGH-I927R using xda premium

well you take parts from the GB kernel and apply it to parts from the AOSP kernel, and troubleshoot until it boots. then you troubleshoot all the other issues, there will be issues, then you can start doing fancy things like add cwm. then tweak the kernel....
start reading on kernels, ramdisk, rils, libs, and drivers, linux, compiling, AOSP, github repositories.
you might be ready to take on this task in 6 months.... minimum
dont take that as snooty, ive been on here over a year, and know jack squat about half the things i just told you to study. though i have no desire to build kernels myself. there is lots of great info scattered all over xda. but you will need an experienced dev, to port ICS. you need to know basic kernel modification stuff before trying to do something as big as porting a new android version from out your but.
automated compiling isnt as automated as it sounds.

Alright. What programs will I need to begin with? Hopefully an experienced dev can guide me, I'm not too good @ following guides/tutorials but I'll try my best!
Sent from my SAMSUNG-SGH-I927R using xda premium
EDIT: Made a dropbox account, hopefully you could guide me through the basics?

So, is this the source code for SGH-I927 you were talking about? I downloaded it, what do I do with it? Is it different for ICS and GB?