How to Customize a Custom Rom: Adding/Removing Programs

[rstoyguy]

Originally Posted by mattdahack

that file is NOT there please check before you post

Um yes it is....Here is a direct link since you are having trouble...

I clicked on the above mentioned link, and copied the link to the file....hmmm... (thought you had me there for a minute, cause that original post was all from memory...)
http://ppckitchen.org/Downloads/PPCkitchen_OEM.rar

[puff]

Originally Posted by mattdahack

that file is NOT there please check before you post

unless the ppckitchen crew did some updates or something, it should be exactly where rstoyguy said.

http://ppckitchen.org/Downloads/PPCkitchen_OEM.rar

oh look, i found it there

[ivan1.ruiz]

Any way I can get a kitchen for the DIAMOND??? not the GF/TC kitchen though.

[rstoyguy]

Originally Posted by ivan1.ruiz

Any way I can get a kitchen for the DIAMOND??? not the GF/TC kitchen though.

That's what theirs is based off of I beleive. You should be able to take their rom, copy prepit.bat over from this kitchen and you could work on a nice stock rom using all the same methods from here. That's what I've been doing...just no device to flash it too.

[rstoyguy]

Here is prepit.bat so that you can play with the stock rom. Be sure to use their kitchen to start off with, it has a few changes to make it work on your specific device...

Just unarchive it into the root kitchen directory, copy the nbh you want to play with into the root as well, run prepit and voila! This will delete their SYS, ROM, and OEM directories and create new ones from your donor rom...

[spetrillo]

I am trying to add my own dialer to a ROM, and when I run BuildOS I get an error saying one of the dialer images is already there, and then it dies. Is there anyway to just let it overwrite what is there, or what do I have to delete in order to let my dialer build correctly?

Ok some more info...it seems that you get the conflict when things exist in \OEM\OEMAPPS. So the real question is can I delete what is in OEMAPPS so that the conflicts dont happen. I am trying to use the leaked VZW ROM for this.

Steve

[rstoyguy]

Originally Posted by spetrillo

I am trying to add my own dialer to a ROM, and when I run BuildOS I get an error saying one of the dialer images is already there, and then it dies. Is there anyway to just let it overwrite what is there, or what do I have to delete in order to let my dialer build correctly?

Ok some more info...it seems that you get the conflict when things exist in \OEM\OEMAPPS. So the real question is can I delete what is in OEMAPPS so that the conflicts dont happen. I am trying to use the leaked VZW ROM for this.

Steve

There will be duplicates. The best way to handle these is this.
- I have buildos open on the right half, and explorer open on the left with the OEM directory selected.
- As buildos pops up those "already exists" file errors, I type in the offending name into the search input box in explorer. Then delete the files that are usually in OEMAPPS.

But you don't want to delete the whole OEMAPPS, there is quite a bit of other stuff in there.

[spetrillo]

Originally Posted by rstoyguy

There will be duplicates. The best way to handle these is this.
- I have buildos open on the right half, and explorer open on the left with the OEM directory selected.
- As buildos pops up those "already exists" file errors, I type in the offending name into the search input box in explorer. Then delete the files that are usually in OEMAPPS.

But you don't want to delete the whole OEMAPPS, there is quite a bit of other stuff in there.

This is way cool. So basically I can take this VZW stock ROM and then customize it to my liking.

One other thing..is it possible that BuildOS is double loading the OEMs. Some of the duplicates that I am running into look like they are coming from the OEMs I am trying to introduce. Based on that I am seeing BuildOS goes through SYS, then custom OEMS, OEMAPPS, and OEMDrivers.

Steve

[rstoyguy]

Originally Posted by spetrillo

This is way cool. So basically I can take this VZW stock ROM and then customize it to my liking.

One other thing..is it possible that BuildOS is double loading the OEMs. Some of the duplicates that I am running into look like they are coming from the OEMs I am trying to introduce. Based on that I am seeing BuildOS goes through SYS, then custom OEMS, OEMAPPS, and OEMDrivers.

Steve

Yes, the duplicates are from your OEM's that you've added usually. The files in them will sometimes conflict with a file that your carrier has included. Usually files associated with a skinned application, such as your dialer.

Beware: It is addictive once you get the hang of it. If you click on my kitchen thread in my signature, I've already seperated out most of the commonly replaced components in my OEM packages...

[spetrillo]

Originally Posted by rstoyguy

Yes, the duplicates are from your OEM's that you've added usually. The files in them will sometimes conflict with a file that your carrier has included. Usually files associated with a skinned application, such as your dialer.

Beware: It is addictive once you get the hang of it. If you click on my kitchen thread in my signature, I've already seperated out most of the commonly replaced components in my OEM packages...

It is incredibly addicting but very empowering at the same time. I am loving it and want my signature on my OWN ROM...thanks for all this!

One other question...where does the name of the image version come from? Right now it says 1.12.latti but I would like to put my own image name on it.

Steve