Quote:
Originally Posted by paravis
Hey I definitely commend you on the effort, but there are already 2 guides like this stickied in this forum, such as:
http://forum.ppcgeeks.com/showthread.php?t=9927
^which personally, I find to be a bit simpler and easier to read. Mainly due to the added numbering and additional links. |
There are certainly a bunch of step by step guides on how to flash, and they all say pretty much the same thing (the one you like is one of the very first specifically for the the Titan - back when the tools still had some issues). More guides isn't a bad thing - so long as they're correct. The fact that he's making a tremendous effort to answer questions, be supportive, and update his guide is to his credit.
Quote:
Originally Posted by paravis
However, if you were able to write up a bigger guide, that would include how to use the ppcgeeks kitchen to make your own custom rom, specifically, how to add in applications not included in any kitchen into a custom rom. That would help me out a ton ;P
Oh and you'd get a donation from me if you could explain in detail, how to not only add apps not included in the kitchen, but also how I can add those apps to my custom rom, including how to load the serial / registration keys for my apps into a custom rom. That would be amazing  |
The guide to creating OEMs was written by JBabey and can be found in the kitchen documentation directory c:\program files\ppckitchen.org\buildos\Help and Support files\Apache kitchen walkthrough r1.0. While the kitchen/flashing steps are about Bepe's first kitchen and the apache (I suppose it should be updated), the later sections on OEM creation are the best around.
That being said, I strongly advise you to use an autoinstall program such as Tautoinstall to install your .cabs instead of converting them to OEMs. You can also find a bunch of ready made OEMs if you search here and xda-developers. If you really want to make your own OEMs, start with OEMizer by tiermann. It will convert many simple .cabs to OEMs.
Registration serial keys are trivial to build in IF you can find how they are stored. It varies from program to program. Once you find your key, how to replicate it will be obvious 99% of the time.