How To Request: Cook your Own ROM

So...I did a little poking around with search and stuff, but I didn't come across too much info. Now, I'm comfortable with both Linux and Windows, however I don't have a distro installed at the moment. That said, how would one go about cooking their own ROM? I'm interested in using No2Chem's 6.1 Build104 rom for a base, and adding in a few things like HTC Home, TouchFLO, just apps that make the experience better. How does somebody cook their own ROM?

[Mutiny32]

Seconded. Found some kitchens, but I'm a little weary to use them because they aren't made for the Touch/Vogue

[mrgeoff]

There is a Vogue kitchen under Lattisimo's Vogue folder. That is what I am using for my ROM creation.

Wing, I replied to your XDA post. I didn't know you posted here too lol

http://forum.xda-developers.com/show...41&postcount=6
^That was my second reply that had some additional tools.

Gee...now that I've spent the past 5 hours installing all my apps on top of No2Chem's clean base...thanks! No really, thanks >.<
I should have searched better. Oh well.

[pnyce777]

i also found a vogue kitchen cant remeber where i dled it from ppc geeks though i have rar file if anyone needs it

yep mr geoff is correct its on the ftp under vogue\users\lattisimos

[buddatech]

can you post, thanks!

[kellybrf]

i dont know what to do with it, but heres the kitchen
http://forum.ppcgeeks.com/showthread...hlight=kitchen

[mrgeoff]

Be careful with BRLE's kitchen. That one requires you to contact him for a password. Somehow, he incorporated it based on your ESN.

[OMJ]

I've cooked many ROM's on the 6700, but using BuildOS, it was a piece of cake.....I've downloaded a few Vogue kitchens, there's definitely more involved when you don't have a gui doing the work for you, but it doesn't look too difficult. Most of the README's look similar, the one thing I'm not sure of is, after adding your OEM's what needs to be edited/added in the registry??? What I'd like to see is something that breaks it all down in translated geek terms, lol.

This kitchen breaks custom rom creation down into five steps.

1) PrepIt.bat, will start with a .nbh file, move to a neatly packaged dump, and then finish by building proper kitchen structure.
2) Add / Modify / Delete files and OEMs by hand. Update your Registry.
3) Run BuildOS.exe to recreate a dump based on your modifications.
4) BuildIt.bat, takes that new BuildOS dump and ends with OS-old.nb, OS-new.nb and a flashable RUU_signed.nbh.
5) Flash that pretty new RUU_signed.nbh. This file will not require titan_exitbl, nor should it throw any errors on completion of the update.

[mrgeoff]

Originally Posted by Old_Man_Jenkins

I've cooked many ROM's on the 6700, but using BuildOS, it was a piece of cake.....I've downloaded a few Vogue kitchens, there's definitely more involved when you don't have a gui doing the work for you, but it doesn't look too difficult. Most of the README's look similar, the one thing I'm not sure of is, after adding your OEM's what needs to be edited/added in the registry??? What I'd like to see is something that breaks it all down in translated geek terms, lol.

This kitchen breaks custom rom creation down into five steps.

1) PrepIt.bat, will start with a .nbh file, move to a neatly packaged dump, and then finish by building proper kitchen structure.
2) Add / Modify / Delete files and OEMs by hand. Update your Registry.
3) Run BuildOS.exe to recreate a dump based on your modifications.
4) BuildIt.bat, takes that new BuildOS dump and ends with OS-old.nb, OS-new.nb and a flashable RUU_signed.nbh.
5) Flash that pretty new RUU_signed.nbh. This file will not require titan_exitbl, nor should it throw any errors on completion of the update.

I personally don't touch the registry files directly. I'm sure I would screw it up something fierce lol.

When you build a package, you can create a RGU file. That file can contain Registy entries that will be ran when the package is integrated. Also, you can build a option.xml file for each package. That XML file will allow you to use BuildOS to enable/disable a package.