How to Customize a Custom Rom: Adding/Removing Programs

[rstoyguy]

Originally Posted by spetrillo

What does the attached screenshot mean when I am running BuildOS? Does it mean that I have a GUID that is duplicated?

Steve

That's a formatting error in one of your RGU files and one of your registry entries. If you look in ..\kitchen\temp\log.txt, at the bottom of this log file it will tell you the OEM and the line # that is giving you the error. It's not always exact with the line #, but within 5 lines usually


Any problems post the RGU contents here and we can help find the error.

Also check out Tutorial: Adding Registry Entries to your Rom (RGU Method) for a few formatting tips.

[spetrillo]

Originally Posted by rstoyguy

That's a formatting error in one of your RGU files and one of your registry entries. If you look in ..\kitchen\temp\log.txt, at the bottom of this log file it will tell you the OEM and the line # that is giving you the error. It's not always exact with the line #, but within 5 lines usually


Any problems post the RGU contents here and we can help find the error.

Also check out Tutorial: Adding Registry Entries to your Rom (RGU Method) for a few formatting tips.

Aha...thanks!

[spetrillo]

Ok while I am not there yet I know I will want to do this at some point.

Clearly the VZW leaked ROM is built on a lower version than what is out in the PPC Kitchen(20931). How do you inject new OS updates into a kitchen, so you gain the benefits of the updated code, along with keeping the stock look and feel? Is there a tutorial on this?

Steve

[rstoyguy]

Originally Posted by spetrillo

Ok while I am not there yet I know I will want to do this at some point.

Clearly the VZW leaked ROM is built on a lower version than what is out in the PPC Kitchen(20931). How do you inject new OS updates into a kitchen, so you gain the benefits of the updated code, along with keeping the stock look and feel? Is there a tutorial on this?

Steve

Yes it was built with the stock rom. I am not one that jumps on the bandwagon of gotta have the latest SYS version in my rom. There is a tutorial over at xda on "porting a sys". I personally have no desire to learn as I will stick with the sys that was tested on my device.

[spetrillo]

Originally Posted by rstoyguy

Yes it was built with the stock rom. I am not one that jumps on the bandwagon of gotta have the latest SYS version in my rom. There is a tutorial over at xda on "porting a sys". I personally have no desire to learn as I will stick with the sys that was tested on my device.

So basically each new version that comes out is essentially a new SYS correct?

And if you had your druthers which SYS have you found the most stable?

Steve

[rstoyguy]

Yep, and I am quite happy with what came with the phone.

[spetrillo]

Ok not a new problem per say but I am hoping you can assist.

I took the 20931 kitchen, created a ROM, and then de-compiled it. When I try to flash it after I use the build tools my 6900 gets stuck at the splash screen. Any ideas on why that is happening?

Steve

[rstoyguy]

Never figured that one out, but any rom built with ppckitchen can be decompiled, but cannot be re-flashed. It will get "stuck"....

[spetrillo]

Originally Posted by rstoyguy

Never figured that one out, but any rom built with ppckitchen can be decompiled, but cannot be re-flashed. It will get "stuck"....

So weird...I am going to post in the kitchen thread and see what they have to say.

Steve

[gguruusa]

Originally Posted by rstoyguy

Never figured that one out, but any rom built with ppckitchen can be decompiled, but cannot be re-flashed. It will get "stuck"....

It can be rebuilt, you just need to use a buildos that doesn't have some of the bugs that Bepe's has. Of course, doing what spetrillo is doing (decompiling a rom he himself made) is complete b00nism.