Quote:
Originally Posted by Vancer
Cool, but just for clarification. I deconstructed your generic custom and noticed that most of the added apps...AEPlus, GPSToday, HHC, etc... were actually in the \sys folder.
|
There are certain folder that will stay in the OEM folder. On decompiled roms, OEM's show up in the SYS directory. These are "Partial" OEM's and can be deleted, but are missing components to add into another rom.
Quote:
Originally Posted by Vancer
Sooo... the HTC stock type stuff is in \oem and when I add the other "after market" type stuff such as that from the PPCGeeks_OEM.rar and 000_Shareware.rar I need to drop that in the \sys folder. Correct?
|
NO!!!
All added OEM's need to go into the OEM directory so that BuildOs.exe can properly incorporate them into the rom. Here is how most kitchens handle the OEM and SYS directory.
Both directories - Files get pulled into the "dump directory" which when the Rom is transfered to your device is the \Windows directory...
- OEM directory
1. BuildOs.exe lets you check/uncheck apps according to info in the option.xml file.
2. BuildOs.exe incorporates the registry information contained in the *.RGU file into the system registry .hv files. (located in ..\SYS\MetaData)
3. BuildOs.exe appends the information from the initflashfiles.txt in each OEM into the system file initflashfiles.dat. (Located in ..\OEM\OEM_Lang_0409)
- SYS directory
Files get copied to the system. The RGU and initflashfiles.txt information is already incorporated so most of the time they do not exist.
That was a brief explanation. Alot more goes on, but I think should help you with why new OEM's go into the kitchens OEM directory.