I've dabbled with this stuff but have a pretty firm knowledge when it comes to phones, rooting, coding (a wee bit) and editing files. I was wondering if anybody could point me in the general direction of where I can learn to do such a procedure (in the title). I'd love to start contributing to the development of metroPCS phones.
Anyone?...
I found this, but it doesn't take into account that the RUU Rom.zip has several zip_0, zip_1, etc. Each zip contains a piece of the System.img.
Link: http://xda-university.com/as-a-user/zip-based-rom-tweaking
Related
How do you extract a custom Rom so that I can tweak it around and take/add a few programs to fit my own needs? I've read the countless number of pages on how to cook a Rom, and my head is about to explode from all the information I'm trying to take in, but nothing explains how to extract and dissect a custom rom.
I understand this is probably something people may not wish to explain so that others don't modify custom ROMs and name it their own, but this is something I wish not to do. I simply wish to take some programs out I never use and add a few that I always use into the ROM so that when I do a hard-reset I don't have to go through the time consuming process of copying and loading cabs all the time.
I've used the search function, but nothing truly explains how to do what I want.
Most chefs protect their ROMs, so you won't be able to extract them.
Here is an excellent guide about customizing an official ROM.
http://forum.xda-developers.com/showthread.php?t=494793
I figured so. Thank you for the link. I guess it's time for me to learn to cook my own ROMs now...hopefully they don't get burnt.
Some chefs upload their entire kitchens along with the finished ROM, so you can customize it to your taste.
I tried to extract R1A UK (the only rom that can play video without lag), but get an error during the extraction.
mah...
Greetings,
I have, over the course of a few years, tried several ROM's from some of the most notable Chefs here. And I thank you (Energy, No2CHem, Mighty, just the most recent I've used I know there are more). I have gotten to the point where I would like to try building my own. I have ventured over to PPCKithcen.org and downloaded their kitchen and updated it for the Rhodium. This morning I compiled Cooked the ROM, and have saved the data output file. I am wondering the danger of flashing this ROM. I know "I flash at my own risk, and could brick my device...yada yada." But what is the real danger here? Would the Kitchen break if the ROM was invalid? Is part of the cooking process verifying the data?
Anyway, I appreciate all of your guidance in this venture. I am NOT going to post the ROM, because...well it hasn't been tested on any device. I can post the Build Status Output, and will gladly send an Chef's my ROM to look at. Also are you all using/prefer one kitchen over another, or do you alternate between depending on the device and radios? Is there a "virtual machine" that one can use to test a ROM?
Mordekai
p.s. okay, message me here, and I can email you the files...can't post files and don't have a file hosting service...yet, maybe if this goes somewhere.
At microsoft.com there's a mobile emulator in the Windows Mobile SDK.
Google that and you shall find that.
Also, you should be fine, unless you're messing with something like the radio or unlockers, you can just reflash the stock rom(recommended but not really needed) then reflash a custom rom of your choice.
I've been searching for a way to repackage (maybe unpack is a better term) CWM flashable roms for use with heimdall.
It seems like every thread relating to this dies off after a few posts because the OP is clueless. I won't claim to be anywhere near an expert on this stuff but I have an idea how it works and haven't managed to foobar my captivate in the few dozen flashes I've done to date.
Back to my point: every dev seems to suggest flashing back to stock before moving to a new rom. Unfortunately the only way I can find to do this is through Odin 1Click which is windows only (to the best of my knowlegdge). As I live/work in a strictly linux/mac world, this is something of an inconvenience. Of course I could setup a vm with windows and do it that way... but heimdall is a solid piece of work and has great potential across all platforms and nothing beats the command line
If a solution does not already exist maybe someone could at least point me towards information that would help me better understand the different files that are used when flashing via odin/heimdall?
Thanks in advance
bump
Not even an I don't know?
First off, Thank you to all the dev's who've put out all the great roms (too many to mention)....
But, as I was reading through some of the most recent releases of roms, I found myself more and more frustrated with confusion. It wasn't the screenshots (thanks, it helps), it wasn't the list of changes/additions/subtractions (that really helps), it was more the complex install info.
I'm not trying to hurt anyone's feelings, but why would you go off on a tangent to left field while your writing down how to install something? Can we get a universal install procedure?
Most roms are released within hours and in some cases days of one another. Lets assume that rom a has what newest rom b needs and create something from that. Then if you need to express random thought for the new guy, that could be post #2. I guarentee that most of the people here have flashed and re-flashed and soft bricked and flashed again.
Guess what I'm trying to say is, rom dev's are releasing things that probably no one will use cause they aren't clear and concise on the install procedure.
FroztIkon said:
First off, Thank you to all the dev's who've put out all the great roms (too many to mention)....
But, as I was reading through some of the most recent releases of roms, I found myself more and more frustrated with confusion. It wasn't the screenshots (thanks, it helps), it wasn't the list of changes/additions/subtractions (that really helps), it was more the complex install info.
I'm not trying to hurt anyone's feelings, but why would you go off on a tangent to left field while your writing down how to install something? Can we get a universal install procedure?
Most roms are released within hours and in some cases days of one another. Lets assume that rom a has what newest rom b needs and create something from that. Then if you need to express random thought for the new guy, that could be post #2. I guarentee that most of the people here have flashed and re-flashed and soft bricked and flashed again.
Guess what I'm trying to say is, rom dev's are releasing things that probably no one will use cause they aren't clear and concise on the install procedure.
Click to expand...
Click to collapse
I see your on super nova. Have you looked at Mosaic. I tried to make the directions as simple as i could
right now with the recent port of the i9000 2.3.3 things have changed.
and changed very recently.
soon enough there will be an easier, more standard way to upgrade.
but keep this in mind....
what we are doing here is programming a phone. the devs AND YOU!
programming an electronic device is not a simple thing, and is not childs play.
the devs have YEARS of experience in programming to bring us the software,
we need to understand what we are doing in order to do it.
so we need to understand programming.
this cannot be done in 10 minutes by just reading instructions.
and this SHOULD NOT be able to be done in 10 minutes by reading instructions.
there are real risks in doing this, that is why it voids your warranty.
you need to understand what you are doing to be able to do it.
thats why you must LEARN in order to do this.
nobody ever learns with brain-dead instructions.
the more you LEARN first, before flashing, the better your chances at success.
the easier the instructions the easier noobs run into problems! Brick their device or get scared and confused about very simple things that they should have understood first!
so the complexity has a dual purpose, it forces you to go out and LEARN before you do anything AND also provides you with alot of information to start learning
<<Captivate Post of the Week>>
TRusselo said:
right now with the recent port of the i9000 2.3.3 things have changed.
and changed very recently.
soon enough there will be an easier, more standard way to upgrade.
but keep this in mind....
what we are doing here is programming a phone. the devs AND YOU!
programming an electronic device is not a simple thing, and is not childs play.
the devs have YEARS of experience in programming to bring us the software,
we need to understand what we are doing in order to do it.
so we need to understand programming.
this cannot be done in 10 minutes by just reading instructions.
and this SHOULD NOT be able to be done in 10 minutes by reading instructions.
there are real risks in doing this, that is why it voids your warranty.
you need to understand what you are doing to be able to do it.
thats why you must LEARN in order to do this.
nobody ever learns with brain-dead instructions.
the more you LEARN first, before flashing, the better your chances at success.
the easier the instructions the easier noobs run into problems! Brick their device or get scared and confused about very simple things that they should have understood first!
so the complexity has a dual purpose, it forces you to go out and LEARN before you do anything AND also provides you with alot of information to start learning
<<Captivate Post of the Week>>
Click to expand...
Click to collapse
Nice long post. Although alot of rambling Tru but I like your last line
As for a standard set of installation instructions, I dont think we will ever see it. Each rom is as unique as the person that developed it, and with that individuality comes an individual requirement for implementation.
ATM some ginger roms are wipes, some arent, this used to be true for all froyo/eclair roms.
that is why we USED TO have to flash to stock each time. same now. (for non wipe roms)
that changed! it can again!
as for getting the bootloaders, if you are installing a WIPE rom you dont need to flash the whole i9000 package. Just the bootloaders alone and ONLY ONCE. some roms currently use this method.
other roms that arent wipe roms depend on apps and framework to be there, or might not like other stuff left over that may still be there. so it is necessary to flash back to i9000 stock, this can be done with or without bootloaders if you already have them. but most of the non bootloaders packages have been taken down. once again you only need to get the bootloaders once.
once again all this can change and standardize again. with the following intructions:
from eclair or froyo
1. odin flash GB bootloader and CMW3 kernel in a single package. (small 4 MB package!)
2. boot into CWM3 and flash a WIPE ROM.
done and upgraded.
my fastest upgrade was one extra step. the bootloader package had re-orient kernel with no cwm3 so i had to reboot and odin flash talon between step 1 and 2.
still pretty easy with a wipe rom.
we grow up so quickly...
I want to learn how to build my own android roms from the source up. So does anyone recommend any literature to read, tutorials to follow, things I need to understand.
I do have two minor preferences; I prefer to develop on Windows, is this possible? And I would like all the literature to be on the internet, so actuaally to be free available....
About me, you can say that I am a noob (I did build an android app with a group of people for school), but I am willing to learn. So does anyone know what are the first steps to take to become a succesful developer.
*Also could someone explain to me: Is there a difference between a regular/rom cooker developer and kernel developer. Do you need to be both to for example make jelly bean working on your phone singlehandedly or do you just need to be a rom cooker?
Rom cookers are the sort of people that have all the required files and they just cook it up into a ROM, Developers are the sort that make things, Add things re-write things, then cook it up.
you will need to start by getting a stock ODIN ROM, and using the tools that can open it, As for these tools im unsure, The kernel is zImage << so you need to find a tool to read / edit that.
You will need to use linux, However you can use Cygwin (linux for windows) and you could try dsixda's rom kitchen,
You will also need 7zip and Notepad ++ , These are just a few of many stuff you will need
Here are a few guides to get you started
http://forum.xda-developers.com/showthread.php?t=633246
http://www.xda-developers.com/android/learn-to-build-kernels-and-roms-for-the-galaxy-s-ii/
http://forum.xda-developers.com/showthread.php?t=1069868
Everything you need to know will be on XDA somewhere
Good luck !!
PS: Make regular backups during development, You first aim should be to get a Stock ODIN ROM converted to a CWM zip file and get it booting, Then start to make tweaks / mods / themes
Good luck, and read this as a word of caution: http://forum.xda-developers.com/showthread.php?t=1690663
A question: how do you extract the boot.img from the SGN? I have already tried this with dsixda's kitchen and CM9, but all I get is the error; "Android Magic not found in ./boot.img". So what are the exact steps to follow for the SGN to extract the boot.img?
I also have a pice of advice. Get a cheaper android phone to play with (which you don't mind breaking). Emulators are great, but there's nothing like the real thing.
PS: For some reason, the image of Guybrush Treepwood saying "I want to be a pirate" came to my mind...