Quote:
Originally Posted by Vancer
When I make an OEM with OEM Package Creator I notice that many of the files have 000- in front of them. and this is represented in the initflashes.txt as well. Then when I look at the OEMs from the PPCGeeks_OEM.rar, none of these OEMs have the 000- in them. Do you know if they just went in and removed the 000- from the file names and the associated syntax in the initflashes files? Or maybe they were created a different way or created with a different version of OEM Package Creator?
When I first noticed this difference b/t the PPCGeeks OEMs and the ones I created it made me hesitant to use mine and think I was doing something wrong.
|
The 000- is to prevent duplicate files when creating a rom, this can be turned off when you first open the package creator.
The ppckitchen oem's, their approach is to leave the files in \windows if possible to save phone memory space. (When you cook a rom, ALL files get permanently placed into \windows) But on my vogue which has plenty of memory, I try to have my oems put them on the device as the author intended. This way making skinning/upgrading to a newer version easier. While either way is ok, I prefer my way...
Quote:
Originally Posted by xd1936
Hmm... That OEM kinda worked. The .mscr files had the right icon, but I got the 'not a trusted certificate' error... I'll try again later, unless someone else has an already-built one
|
You need to ask in the PPCKitchen thread how to relax security in your rom... I don't use the ppckitchen, but it does work fine in Dogguy's kitchens.