Related
You can find HERE the IRUS tools and HOW TO build your own ROM
http://forum.xda-developers.com/showpost.php?p=2176131&postcount=3
Very fine tools
I hope my internet will be fixed eventualy, so I can download this tools to try it. It is a time to learn something new.
Tadeusz said:
I hope my internet will be fixed eventualy, so I can download this tools to try it. It is a time to learn something new.
Click to expand...
Click to collapse
thats the spirit, if you have any questions just post'em
I'd actually consider downloading this, but I tend to be pretty picky about knowing where all the files came from and what changes were made, so I'll probably stick with my own kitchen I'm futzing around with. I'll take a peek, though, and I might be able to suggest a change or two if I notice things I've figured out that you've not yet implemented yet.
Sogarth said:
I'd actually consider downloading this, but I tend to be pretty picky about knowing where all the files came from and what changes were made, so I'll probably stick with my own kitchen I'm futzing around with. I'll take a peek, though, and I might be able to suggest a change or two if I notice things I've figured out that you've not yet implemented yet.
Click to expand...
Click to collapse
Why don't you also post your kitchen and instruction on how to use it too?
eaglesteve said:
Why don't you also post your kitchen and instruction on how to use it too?
Click to expand...
Click to collapse
You want the honest truth? A couple of reasons.
In order to have something that I'd feel comfortable with other people using, it would require several more weeks of futzing around with the files. I've already been at this for almost three weeks now, and I'm tired of using my HTC Typhoon. I want my real phone back (since the Athena >>> Typhoon).
The final ROM that I'll be using won't match the ROM that other people will be using, period. It's because I'll be putting some of the software that I've bought into my ROM, and putting in some hard-coded dependencies upon those (since there are some interesting things here and there you can do).
I hate doing support. For which I heartily applaud irus, since he's been single-handedly patiently trying to help everyone who's been using his ROM. Pawel was doing the same for a while, albeit a little less patiently, although I don't know where he's disappeared off to recently.
There are probably other reasons as well, but those are the ones I can think of for now. I mean, if there's truly interest, I can see what I can do, but one of the other things that bit me the last time is that I don't want to debug things alone again - the last time, it sucked well over a month from my life to handle all that.
Anyways, this is the thread for the IRUS ROM Kitchen, not the maybe Sogarth ROM kitchen, so I'll leave it at that.
What about mixing Chinese with new Irus one?
I wonder if there could be a way to mix Irus rom with this Chinese one to get a new WWE version based on the newest built and fastest up to now?
It should not be e big problem to put mui files from Irus kitchen into Chinese rom and change a mui to English. There is a reg key setting language for the rom. Irus knows it better then me, anyway.
Unfortunately I can't download anything from rapidsare nor from megaploads because of me being behind a proxy of my 3G network.
Irus, if you could upload your kitchen on my eurotelefon server, then I could get it here and start learning. Today I have some work to do yet, but maybe later I could start.
Edit:
We have to test new rom of Irus first, and then compare it with the Chinese version. It could be very interesting. Steve has very good experience with this Chinese rom so we eventually could use it in future works. Of course we need to ask for the permission, but I am sure the Chinese producer can be proud of his work and let us use it to build something new on it. This is how the development goes, anyway.
Sogarth said:
You want the honest truth? A couple of reasons.
In order to have something that I'd feel comfortable with other people using, it would require several more weeks of futzing around with the files. I've already been at this for almost three weeks now, and I'm tired of using my HTC Typhoon. I want my real phone back (since the Athena >>> Typhoon).
The final ROM that I'll be using won't match the ROM that other people will be using, period. It's because I'll be putting some of the software that I've bought into my ROM, and putting in some hard-coded dependencies upon those (since there are some interesting things here and there you can do).
I hate doing support. For which I heartily applaud irus, since he's been single-handedly patiently trying to help everyone who's been using his ROM. Pawel was doing the same for a while, albeit a little less patiently, although I don't know where he's disappeared off to recently.
There are probably other reasons as well, but those are the ones I can think of for now. I mean, if there's truly interest, I can see what I can do, but one of the other things that bit me the last time is that I don't want to debug things alone again - the last time, it sucked well over a month from my life to handle all that.
Anyways, this is the thread for the IRUS ROM Kitchen, not the maybe Sogarth ROM kitchen, so I'll leave it at that.
Click to expand...
Click to collapse
Ready to change the 3d into something different....
Tadeusz said:
I wonder if there could be a way to mix Irus rom with this Chinese one to get a new WWE version based on the newest built and fastest up to now?
It should not be e big problem to put mui files from Irus kitchen into Chinese rom and change a mui to English. There is a reg key setting language for the rom. Irus knows it better then me, anyway.
Unfortunately I can't download anything from rapidsare nor from megaploads because of me being behind a proxy of my 3G network.
Irus, if you could upload your kitchen on my eurotelefon server, then I could get it here and start learning. Today I have some work to do yet, but maybe later I could start.
Edit:
We have to test new rom of Irus first, and then compare it with the Chinese version. It could be very interesting. Steve has very good experience with this Chinese rom so we eventually could use it in future works. Of course we need to ask for the permission, but I am sure the Chinese producer can be proud of his work and let us use it to build something new on it. This is how the development goes, anyway.
Click to expand...
Click to collapse
i took a brief shoot as i have never done a language swap before and it did not work i will consider it but im still fussing around with new bt stack so people can send files back and forth between phones and laptop and phone. that is the last thing i need to do to make my rom complete. i will want a monday release as i said i would release on monday and i don't like being late. but on the other hand the chinese rom works better at transferring files so if this becomes a dead end then i might have no choice but to push back the release date and work with the chinese rom. i will make an official announcement tomorrow night
Sergiopi,
Please see my post on the Chinese ROM thread regarding caution in using this download.
irus,
This looks like a user friendly tool, but I've a question at the stage where we're looking at the dump: How do you go about finding out which pieces are for which ? Is there a website to go to in order to make sure we're removing the right thing? Or is it a trial and error kind of process? If I want to extract out the new cotact application from a newer ROM, for example, how do I know what the pieces are?
eaglesteve said:
irus,
This looks like a user friendly tool, but I've a question at the stage where we're looking at the dump: How do you go about finding out which pieces are for which ? Is there a website to go to in order to make sure we're removing the right thing? Or is it a trial and error kind of process? If I want to extract out the new cotact application from a newer ROM, for example, how do I know what the pieces are?
Click to expand...
Click to collapse
to me i think the easiest way, if you upgrading the app, is to look and see what files are in the new app and just replace the old. you could make packages but then you have to make a rom folder and xip subfolder and IMO buildos is sometimes picky about reg entries. so the best way is to just replaces the files in the dump folder and then edit the hv and if needed the inflashfiles.dat
This is also in conjuction with eaglesteves previous question.
So I do all of the 'editing' of the ROM in the dump folder right? Second, what if I want to remove entire program, is there an easy to extract 'everything' and its components from the ROM? For instance, what if I want to remove the calculator and put in a freeware calc. do I just remove the calculator folder or is there more to this process?
In the ROM that I'm editing...really just for experiment....I want to remove alot of things and add some, and see if I can put it back together.
I hope this makes since.
Thanks Irus for a good tutorial.
Kenjari
Need help for Exract Bluetooth stack and wireless manager from Taxist V10 rom
Hi
Anyone please help me to extract Bluetooth Stack and the wireless manager from taxist V10 rom.
Just i need to know that which files are needed for Bluetooth Stack and Which files for wireless manager.
I have seen the files in the os.nb but i do not know which files for the bluetooth and wireless.
Thanks in advance.
I downloaded the instructions but for some reason, it can't be read with any of my programs even Microsoft Word.
If I want to extract a particular file off from a WM6.1 RUU_signed.nbh file, which of the included programs should I use?
I tried Scoter Kitchen, but it does not read .nbh files.
NetCF3.5 OEM?
Hi Irus,
I was trying to get an OEM for NETCF3.5 from your FULL ROM using Sogarth kitchen, but with no joy.
Could you suugest any place I could look for it? The same for FTouch?
Is it possible for someone to start a ROM Bible thread similar to what I found when looking for info for my wife's G1, but for the Rhodium?
Sorry if one exists, but I have yet to find it if it does...
It would help an Android noob out a ton so that I actually understand a bunch of the terminology and build references/names when in this forum.
I am almost totally new to Android, having run WM for 6 or 7 years, and it can get a bit overwhelming to try and figure it all out. Though, having recently switched my whole house network to Ubuntu/Mint, it's a lot less "greek" to me than it was a year ago.
I'd also like to start helping in some way if possible, as the work you're all doing is so awesome and gives me hope to keep running my TP2 for a lot longer than I otherwise would. Any pointers there either?
I think the best all in one resource I've seen is the FAQ over on PPG:
http://forum.ppcgeeks.com/tp2-andro...e-android-tp2-cdma-tips-faq-s-jan-2011-a.html
Hey guys,
I am really curious as to what it takes to build a custom ROM. I am very interested in building my own and want some pointers on the best places to start so I don't waste my time. Any advice will be useful, books, websites, w/e.
Thank you,
r3xx3r
get ready cause this one's going wayyy over your head.
Its one of those things where if you have to ask, you'll never know.
spitefulcheerio said:
Its one of those things where if you have to ask, you'll never know.
Click to expand...
Click to collapse
I really hate this mentality. People have to start somewhere. Sure they could spend years figuring everything out on their own. Or you could save them a year by pointing them in the right direction. There is such little discussion about this and it's honestly just annoying and a huge negative aspect about the development community.
EDIT: This is for HTC and I haven't watched it, but it might get you started: http://www.youtube.com/watch?v=94Az1kcQvc4
Also, you should definitely look through the source code for open source ROMs. I'm not a ROM developer so I can't really help you more than that, but I hope a real dev gives you an answer.
first and foremost, learn how to use ADB. if you cant use ADB without some kind of script/batch file to do it for you, then stop right here!
personally the first thing i learned was how the updater-script (at the time, we didnt have edify scripting, so it was plain-jane update-script) worked. have a look in a rom's zip file and learn the layout.
learn how to edit apks (decompile/compile) with apktool.
get comfortable with linux (this is just an opinion, as you CAN build roms in windows, but i have found it much easier on my dev laptop with ubuntu 10.10 64bit)
apkmanager is a good tool to have if you are on windows (there is a linux/osx version too, but i havent used it)
learn what zip-aligning means and what it does for your rom
learn what deodexing means and what it does for your rom
different devices benefit from different tweaks within your /system/build.prop . learn which ones work best for your rom (this requires a lot of flashing and testing on your own device)
this whole process is very time consuming and takes a ton of effort on your part. be prepared. while it is a lot of work, it is a lot of fun learning.
once you get proficient at building and tweaking roms, you can start learning how to edit smali
Pirateghost said:
first and foremost, learn how to use ADB. if you cant use ADB without some kind of script/batch file to do it for you, then stop right here!
personally the first thing i learned was how the updater-script (at the time, we didnt have edify scripting, so it was plain-jane update-script) worked. have a look in a rom's zip file and learn the layout.
learn how to edit apks (decompile/compile) with apktool.
get comfortable with linux (this is just an opinion, as you CAN build roms in windows, but i have found it much easier on my dev laptop with ubuntu 10.10 64bit)
apkmanager is a good tool to have if you are on windows (there is a linux/osx version too, but i havent used it)
learn what zip-aligning means and what it does for your rom
learn what deodexing means and what it does for your rom
different devices benefit from different tweaks within your /system/build.prop . learn which ones work best for your rom (this requires a lot of flashing and testing on your own device)
this whole process is very time consuming and takes a ton of effort on your part. be prepared. while it is a lot of work, it is a lot of fun learning.
once you get proficient at building and tweaking roms, you can start learning how to edit smali
Click to expand...
Click to collapse
This is good information. I, personally, build Aura completely on windows with minimal assistance from cygwin. I use batch files for the common things I use on ADB and the like but I built the scripts myself, so it isn't like I can't do it manually I just don't wanna.
It is both easier and harder than it looks. Aura is the first rom I have built.
One thing, though, is to not accept the current ways as best. Things can always be improved. I have two common mods in my rom that are done completely differently in my rom, without either database editing through scripts or modifying smali inside apk's (the hotspot entitlement check and the 1 signal bar fix). No other roms for the Atrix (I haven't check other phones...) do it this way, not even Darkside which is based somewhat no Aura.
If you are building a rom through the Rom Kitchen... don't use the garbled updater-script it puts out. It mostly works, but it is trash and you won't learn much from it.
Experimentation!
Diviance said:
This is good information. I, personally, build Aura completely on windows with minimal assistance from cygwin. I use batch files for the common things I use on ADB and the like but I built the scripts myself, so it isn't like I can't do it manually I just don't wanna.
It is both easier and harder than it looks. Aura is the first rom I have built.
One thing, though, is to not accept the current ways as best. Things can always be improved. I have two common mods in my rom that are done completely differently in my rom, without either database editing through scripts or modifying smali inside apk's (the hotspot entitlement check and the 1 signal bar fix). No other roms for the Atrix (I haven't check other phones...) do it this way, not even Darkside which is based somewhat no Aura.
If you are building a rom through the Rom Kitchen... don't use the garbled updater-script it puts out. It mostly works, but it is trash and you won't learn much from it.
Experimentation!
Click to expand...
Click to collapse
Thanks for the input. I love hearing from other devs and the methods they prefer.
Sent from my Inspire 4G
this thread died quickly.
too bad because I want to do some studying up on it and creating some coolness myself eventually.
I know with iphones a lot of development was done right from the phone itself especially for app development, is there the same concept here?
and one other question, do you guys make any money off of these things at all? Im always looking for side work...
supermerkin said:
too bad because I want to do some studying up on it and creating some coolness myself eventually.
I know with iphones a lot of development was done right from the phone itself especially for app development, is there the same concept here?
and one other question, do you guys make any money off of these things at all? Im always looking for side work...
Click to expand...
Click to collapse
you can create scripts, push and pull files directly from the phone, so in a sense, yes you can work straight from the phone.
as for money...LOL...dont look to this for a secondary income by any means.
i have made all of $28 for my work on the inspire, and nothing from my work on the captivate
Pirateghost said:
you can create scripts, push and pull files directly from the phone, so in a sense, yes you can work straight from the phone.
as for money...LOL...dont look to this for a secondary income by any means.
i have made all of $28 for my work on the inspire, and nothing from my work on the captivate
Click to expand...
Click to collapse
Hey 28 bucks is 28 bucks, granted I made 40 per screen when I used to replace iphone digitizers but money is money you never have enough.
Thanks for the info though!
Sent from my MB860 using xda premium
I spend a lot of time flashing my Rom when I am working on it. I usually don't push and pull from the phone since most users aren't doing that and I want to emulate what they will be doing.
As for money... Yeah, not a method of reliable I income if you intend to use it as such. I have probably had around... $125 donated to me by some incredibly awesome people.
If you intend to become a Rom dev, be friendly and responsive. People really appreciate someone who is willing to answer questions and give help where needed. Being standoffish like some I have seen is a sure way to get labeled with some bad words
Thank you guys for the responses. This is something I've been wondering as I've taken the plunge into modifying my Atrix. To say it's been addictive is an understatement. I started toying with the idea of putting my own ROM together pretty early on, so basic info like this is much appreciated.
Like someone said early on in the thread, everyone has to start somewhere so even seemingly small bits of info are always welcome.
The biggest hurdle is understanding adb commands and when to use them. Then, how to view the individual file strings inside the /sytem/build.prop and apks AND actually understand what it means. I have spent hours wandering around in root explorer look in folders and seeing what is inside. Pulling something with adb actually removes it from the phone right? Then I have to adb push back into the folder I pulled from. Should I use Ubuntu on my Win7 pc? I tried eclipse, installer r13, and I do have apkmanager but have yet to figure out how to actually use it.
I learn by doing what someone is telling me so reading it sometimes doesn't make sense since I can't "see" it and what it's supposed to look like. WIsh someone lived nearby to just to help get me started.....Beers and food on me LOL. Or at least had some time over the phone even.
Thanks Diviance (again) and to you PirateGhost for your help.
no adb pull does not remove it from the device. it copies to your local machine
as far as using windows vs linux. use whatever will make you more comfortable. i can assure you a lot of tutorials, and howtos are written with linux in mind, but if you can understand the basics, you will be able to translate it to windows. not to mention once you get into tearing down APKs, jars, dexes, etc....its all the same code inside no matter what tools you are using to get to them. i find linux easier to work with when it comes to stuff like this, some people think windows is easier.
If I were to get linux on my PC, would adb work within the linux evironment...meaning can I adb from linux and compile/decompile etc from there?
Phoneguy589 said:
If I were to get linux on my PC, would adb work within the linux evironment...meaning can I adb from linux and compile/decompile etc from there?
Click to expand...
Click to collapse
well you would compile/decompile directly on the phone unless you were using the sdcard....it wouldnt be pretty
you adb pull /system/file modify it, then adb push /system/file
it works the same in windows as it does in linux from that aspect. i just find working in linux easier.
here, this should help get you started somewhere, its not exactly like this phone, and the guide should be used as a reference and not a manual.
http://forum.xda-developers.com/showthread.php?t=915435
if you are technical enough, just by looking at that thread, you will understand a good portion of whats going on.
Thanks for all the help. Im getting bored flashing other peoples work and would like to help tweak things. And develop some stuff.
Thanks bro.
hey everyone. ive been googleing and googleing for weeks and weeks trying to educate myself on how the android build process works and how a device tree works. what i have been able to figure out is the device configuration has been moved form /vendor to /device between eclair and froyo. although i am very lost and confused. i have gone through source.android.com several times, and i have also gone through the very outdated platform developers guide. right now i am trying to teach myself how to set up a build environment for a real device. im doing this purely out of learning experience so i can apply it to something useful in the future. i have several devices at my disposal (epic 4g, droid1, atrix 4g, acer iconia a500) any of which i would be willing to use for learning. does anyone have any recommendations on reading material im missing? any good place to ask stupid questions? there is lots of documentation out there but i just cant seem to find it. where should i go from here? i wish i could just take a class on this. because there is so much information out there i have no idea where to go from here.
I was actually going to make a post along the same lines as yours. From what I have found the pinned post in this forum from cyanogen about cooking is probably the most useful information to get started.
The issue I have is a forum just on this topic alone. It would be nice to have a forum that only discussed merging manufacturers released code into AOSP. By googling I have found the Atrix source code that Motorola has released and also the AOSP itself. By reading cyanogens post and mucking around with the source this should give you a good start.
Good luck and if you come across a forum with just this topic discussed post a link.
Also for setting up an environment this post is good for getting everything setup to compile what you need. It is a post to compile CM7 but it can be used for what you are looking for.
gh123man said:
hey everyone. ive been googleing and googleing for weeks and weeks trying to educate myself on how the android build process works and how a device tree works. what i have been able to figure out is the device configuration has been moved form /vendor to /device between eclair and froyo. although i am very lost and confused. i have gone through source.android.com several times, and i have also gone through the very outdated platform developers guide. right now i am trying to teach myself how to set up a build environment for a real device. im doing this purely out of learning experience so i can apply it to something useful in the future. i have several devices at my disposal (epic 4g, droid1, atrix 4g, acer iconia a500) any of which i would be willing to use for learning. does anyone have any recommendations on reading material im missing? any good place to ask stupid questions? there is lots of documentation out there but i just cant seem to find it. where should i go from here? i wish i could just take a class on this. because there is so much information out there i have no idea where to go from here.
Click to expand...
Click to collapse
2nd hit googling android porting.
http://www.netmite.com/android/mydroid/development/pdk/docs/
Nothing is truly "update-to-date" there are somethings that your going to have to do your homework on. That is a very detailed guide on the basics of getting a port going and working towards the "device tree"
Unless the device tree is from a google nexus phone, then most likely the trees are not perfect. Cyanogenmod for example, the devs that work hard on creating those device trees don't just know what will and won't work. Each phone is different alot of trial and error. Do you build a binary from source, or do you use prop files already on the phone, that is all based on what is trying to be done and how much you know. Eventually you figure it out. It hard to just say what creates the device tree. Its just like someone asking for tips on how to write Java.
Bottom line, just do it and have fun.
lithid-cm said:
2nd hit googling android porting.
http://www.netmite.com/android/mydroid/development/pdk/docs/
Nothing is truly "update-to-date" there are somethings that your going to have to do your homework on. That is a very detailed guide on the basics of getting a port going and working towards the "device tree"
Unless the device tree is from a google nexus phone, then most likely the trees are not perfect. Cyanogenmod for example, the devs that work hard on creating those device trees don't just know what will and won't work. Each phone is different alot of trial and error. Do you build a binary from source, or do you use prop files already on the phone, that is all based on what is trying to be done and how much you know. Eventually you figure it out. It hard to just say what creates the device tree. Its just like someone asking for tips on how to write Java.
Bottom line, just do it and have fun.
Click to expand...
Click to collapse
thanks for the response. maybe im just searching for the wrong things... that and its not sinking in to my thick skull lol.. ill keep reading. im just trying to learn how it all works. some of the things i read either dont make sense or are really vague. i am currently cramming java into my head for app development. i suppose thats a good place to start. my end goal is to contribute.
gh123man said:
hey everyone. ive been googleing and googleing for weeks and weeks trying to educate myself on how the android build process works and how a device tree works. what i have been able to figure out is the device configuration has been moved form /vendor to /device between eclair and froyo.
Click to expand...
Click to collapse
I am trying to figure out how to build/port ROMs too. It has been a nightmare trying to study that. Not enough material, or the material is incomplete. Most of the tutorials are meant to be done with nexus devices wich has a native suport from android. No such a help for someone who is seeking a way to build for a new, unusual device (like me).
I didn't get this "three" thing. And, In my case, it is a little bit weirder because I am trying to build for a MTK6577 processor. (Some may say I am screwed).
although i am very lost and confused. i have gone through source.android.com several times, and i have also gone through the very outdated platform developers guide.
Click to expand...
Click to collapse
Many years ago I said: there will be a Time when people will know the "internet junkyard" or the "virtual online trash can".
I was reffering to outdated information. This information is available now and is not completely reliable because it is old and no one got rid of it.
It is something that is new (although the information is old, the event is pretty new) and we must learn how to deal with it. Unfortunally.
To de development point of view, I've been facing an incredible hard time just to find new information about building a custom rom from the source or porting an existent one.
I know i didn't help at all, but, I felt I must say that.
Anyway, knowing about anything, let me know.
Best regards!
gh123man said:
hey everyone. ive been googleing and googleing for weeks and weeks trying to educate myself on how the android build process works and how a device tree works. what i have been able to figure out is the device configuration has been moved form /vendor to /device between eclair and froyo. although i am very lost and confused. i have gone through source.android.com several times, and i have also gone through the very outdated platform developers guide. right now i am trying to teach myself how to set up a build environment for a real device. im doing this purely out of learning experience so i can apply it to something useful in the future. i have several devices at my disposal (epic 4g, droid1, atrix 4g, acer iconia a500) any of which i would be willing to use for learning. does anyone have any recommendations on reading material im missing? any good place to ask stupid questions? there is lots of documentation out there but i just cant seem to find it. where should i go from here? i wish i could just take a class on this. because there is so much information out there i have no idea where to go from here.
Click to expand...
Click to collapse
Here is the Small Guide Made to Begin from scratch for Android Device Tree Building
Hi XDA,
first of all, let's introduce myself. I'm a greenhorn at an indian outsourcing company working in the netherlands. my job is primarily 'being dutch' which happens to be a 24h a day job but something i can very easily multitask
so in a moment of 'what the coitus are they paying me for' i decided that i wanted to use a 'controlling-parent-or-boss-friendly' version of android. but it doesnt exists because android doesnt really allow such 'control' apps to work properly if they are 'only' an app (I tried a few to combat my infobesitas which is also the real reason why i'm doing this).
so why not. i'm a developer, i've got time. i know next-to-nothing about android, but i'm young and naive and terribly optimistic. lets get the source, modify it so it has baked in 'parental' controls, build it, use it, be happy with my lack of infobesitas, maybe sell it to my boss-and-other-evil-people?
so i tried to build AOSP using googles guidelines
i installed the latest ubuntu. i downloaded the packages (one didn't when i tried first but it worked when i downloaded it apart), created the working directory, got repo, repo-ed the source, ran the source configure.sh thing ran lunch and ran make.
my disk ran out of pizza space (i thought a 66gb partition would be enough, but not so much) so i enlarged my petition, throw the entire working directory away and repeated the process
only i get this error
out/host/linux-x86/obj/SHARED_LIBRARIES/libart_intermediates/arch/x86_64/quick_entrypoints_x86_64.o:function art_quick_instrumentation_entry: error: undefined reference to 'art_quick_instrumentation_exit_local'
googled this to no avail. put some post on my fb wall if anybody could teach me Android OS/ROM development for 150 euro (or more if i needed the person more than the ammount justifies). but i guess my 'friends' dont make roms in their free time (which is reasonable sinds im the 1337est h4ckz0r i know),
please help me with this.
so now i'm here. bounty is up for you too but for it ill expect a bit more than getting android to build. a teacher would teach me the ropes of rom dev using skype or something.