[TUT] Creating OEM's for your ROM
 

This tutorial is designed to teach you the method I use to make simple OEM's.

Not all .cabs can be made into OEM's. Some will need some advanced trickery. This thread will be open to discussing that advanced trickery. I will answer any questions that arise, and other members can share their experiences/knowledge as well.

Not all topics are going to be added to this initial release, but I will add them with time, So check back later for more details!

Insert bold colored disclaimer here about how it is not my fault
if you mess up your phone or lose sleep after reading this tutorial...

Thanks go's out to:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- Ervius @ xda. It's his program
- PPCGeeks.com users. I've learned most everything here and can't list everyone.


Misc. Stuff
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- For this Tutorial, Ervius's Package Creator will be reffered to as EPC.
- Here are some links to some other tutorials that may be helpfull when making OEM's:


Prerequisite Reading, Recommended...
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Tutorial: Adding Registry Entries to your Rom (RGU Method) - Helpfull for learning the RGU structure
Customizing Your Rom: Adding Personal Files & Other Stuff - Helpfull information on the initflashfiles.txt file.


What is an OEM?
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
An OEM... It's a package that Rom Chef's use to install files into a Rom. once a Rom is flashed, .cab files are installed. Cab files are converted to an OEM so those programs can be installed into a rom. Not a good definition, but it'll do.


Files inside an OEM, What are they?:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
{guid}.DSM - I don't know the contents, I don't care, never needed them, so who cares what it contains? It's just gotta be there...
{guid}.RGU - This file contains the registry entries for your OEM
initflashfiles.txt - This file copies your files to where they need to be when winmo starts.
option.xml - This file is needed by BuildOS. Specifies the Name, GUID, BuildOS description, other OEM requirements, etc...

Everything else should be from your .cab file


Prepare your HDD
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
By this I mean, download the attachments. Here is a look at my directory structure looks like on my harddrive where I prepare my OEM's:
..\oem_requests
..\oem_requests\vga_oems
..\oem_requests\regular_oems
..\oem_requests\ervius package creator
..\oem_requests\a_c

When you are doing OEM's, EPC will create your oem's directory directly off of where your input cab was. So I would place my cab files in the appropriate directory.

So decide how you want to do it, make your directories, unarchive the attached EPC, and copy the attached Kevtris.cab to your new OEM directory. Once you've got that done, here is a walkthrough of making an OEM out of kevtris.cab


Let's build a simple OEM from Kevtris.cab:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
1. Open Ervias's Package Creator 5.4

2. Click the "Open Cab File" button bottom left

3. Select your .cab file and click "Open"
(This will open your .cab with a program called "WinCE CABs Analyzer" program)

4. On the top row, Click the 7th icon from the left. When you roll your cursor over it, it will say "Extract CAB Files with original name in folder". This will open a directory selection window, DO NOT CHANGE THIS, I ALWAYS just click the "OK" button

5. Once this is done, you can exit WinCE CABs Analyzer simply by clicking the "Red X" in the top right corner.

6. This will take you back to EPC to the initflashfiles tab. This where you create your start menu shortcuts. For this example, click kevtris.exe in the window, select the Games button, and then click apply. You should see that it created/added Kevtris.lnk.
Click the "Done" button on the left, this will take you back to the main screen.

7. Here, click "Complete Package" and the program will tell you that you are Done, and you are. :)

Now back to your File Explorer, you will notice that a new directory was made where the original .cab file was, this is your OEM. Copy to your kitchens ..\kitchen\OEM folder and enjoy. If you are using PPCKitchen.orgs kitchen, copy the OEM into your ..\USeR_OEM folder and restart BuildOS.
I've included a basic .cab file and it's finished OEM. Here are a few notes on this one.
- This contains a SetupDLL.dll file... You know how when you install some cAB's they prompt you for your language, screen resolution, unzips files (weatherpanel), etc??? This file is responsible for this. Now while this one does nothing, I always delete them. You will have to figure out what it does and manually adjust your OEM to compensate. Each one will be different and will come to you with experience.

Figure 1: Screen shot of Main Screen w/correct options selected.
http://i483.photobucket.com/albums/r...m_tut_main.gif

Figure 2: Screen shot of WinCE CAB Analyzer and location of the 7th Icon

http://i483.photobucket.com/albums/r...abanalyzer.gif

Figure 3: Screen shot of the initflashfiles tab

http://i483.photobucket.com/albums/r...ut_iff_tab.gif

Re: [TUT] Creating OEM's for your ROM
 

Advanced Topics & Tricks:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
1: Tweaking the "option.xml"
2: Tweaking the "initflashfiles.txt"
3: Importing Program Settings
4: Handling the Setupdll.dll file
5: Adding multiple files using OEMIzer (Good for Skins-n-Things)


Advanced Topics: Tweaking the "option.xml"
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
The file option.xml is basically for BuildOS. Here is the contents from a freshly made OEM:
Now let's take a look at each one:
Kevtris - This is the name that show up in BuildOS
Apps - This is the category sub-folder that the program will show up in BuildOS.
True - True, it is checked when BuildOS is first started and will be included in the build. The other option is "False" for it will not be checked.
Tip - This is the program description when you roll your mouse over that option in BuildOS (older) or to the right of the program name in the newer kitchen.
Guid Type - This is the GUID of the OEM, the DSM and RGU files have this same name as well.

Now let's add a few more components to the file.
Above I've added, the OEM Date, Author, Version, and a URL link. The information in orange is just text format. Adding this information is handy, especially if your using the latest ppckitchens buildos.


This is a text file I keep so I can easily cut and paste the above information into the option.xml of most of the OEM's I do.
Other option.xml commands are:
<Require> {GUID} </Require> - Adding this line will require BuildOS to include that OEM as well. Replace the {GUID} with the actual GUID of the OEM.


Advanced Topics: Tweaking the "initflashfiles.txt"
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Here is a look at the file:
Sometimes cabs will install some additional .lnk files, misplace a file that got copied into the program directory that should have been left in the \windows directory, or will have multiple language files and depending on your language selection will copy only one to a different filename inside the program directory. I almost always anymore copy my .links from the device after a .cab install. I check the \windows\startup and \windows\program files directories. I then manually copy them from my device into the OEM and create an initflashfiles.txt entry for it. Other files, you will have to install the .cab on your device, then examine the structure within the OEM and adjust your OEM so it mimics the .cab install file placements, etc...

I've already covered handling this file in some other tutorials. So check out this tutorial to find out more:

Customizing Your Rom: Adding Personal Files & Other Stuff (the beef is in post #2 for those quick learners)

Re: [TUT] Creating OEM's for your ROM
 

Advanced Topics: Importing Program Settings
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Reserved for later...

Advanced Topics: Setupdll.dll
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This file sometimes has some additional code that will run doing a .cab install. When installing a .cab on Windows Mobile, there are four "Hooks" that winmo looks for when dealing with .cabs. There are only two that we are concerned with. There is a "hook" that is called before the .cab is installed and another one after the .cab is installed. If this file is present, more than likely there is something more and YOU WILL HAVE TO MANUALLY EDIT YOUR OEM.

Etiquette Note: This file is almost always and exclusively used in this fashion, and some PPCGeeks etiquette...If an OEM contains this file, it is considered a "poorly" put together OEM. This file will also almost always create that "Duplicate File" error is BuildOS (or whatever else you use) so just get rid of it!

Here are some things it can do:
MemMaid: Calls that little help screen (harmless), PocketTunes: Displays a license agreement (harmless), WeatherPanel: UnZips all the graphics files, Touchpal: Prompts you for your device type and then copies the VGA/QVGA files depending on your choice... Those are just a couple, thank goodness that this is not used much, but it is out there.

How to defeat it:
You will need to install the .cab to your device, preferably to a clean rom. Then you will have to match up the files from the OEM to where the files were installed on your device. Then edit the initflashfiles.txt, and files in your OEM to make the changes. I'm not going any further with this, YOU will have to figure it out. There are just too many variables and it just takes experience... You can always visit one of my oem requests threads and request it. If you ask I will actually post the "trickery" I found briefly.


Advanced Topics: Adding multiple files using OEMIzer (Good for Skins-n-Things)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I don't use the OEMIzer much, but I have found it a very good use for it. Say you are wanting to install a skin that installs all the files to \program files\weatherpanel\skins and all you have is a zip file with those files. Here is a brief how-to do that...

Create in your oem-making directory a directory called ..\oemizer, the inside create two directories, ..\oemizer\oemizer and ..\oemizer\OEM. Copy the 3 oemizer files from one of blank kitchens (found in my Adding/Removing Programs Tutorial in my sig) into the ..\oemizer\oemizer directory.

Now that your prepped, let's do it!
Open up OEMIzer and move the window to the left side of the screen, then open up a windows explorer window and move it the right side so you have the two windows open in a side-by-side style.
In OEMIzer, click the "Files and Shortcuts" tab and make sure its checked.
Next, from your file explorer, select and drag-n-drop those files into the OEMizer window.
Now in OEMizer, select all the files in the window.
Down below in the box that says "\windows\", change this filename to where you want your files installed. Be sure to put a trailing \, so it's "\program files\weatherpanel\skins\".
Now click the "edit" button. You should see that this changed all the items in the window.
Now your ready to make the OEM, so click the Green globe above that says "Create OEM".

Your oem was created in the ..\oemizer\oem directory. Now what I do is copy the files into the OEM I was creating, and APPEND the contents of the initflashfiles.txt from the newly created OEM into the one I was originally working with.

It can be a pain to manually create an initflashfiles entry when your skin is 400+ files, I've found this to be a huge timesaver!

Re: [TUT] Creating OEM's for your ROM
 

I haven't looked at that .cab in a while, but doesn't it just install extensions so you can use picturemail? I still use sMMS. You will have to setup an account for that using the EMAIL2 provisioning for it to show up I beleive.

Re: [TUT] Creating OEM's for your ROM
 

Sorry about posting in your other thread :)

Honestly, I don't know. I am still pretty new at OEM creating and rom building in general.

Did i miss something about email provisioning? Where can I learn about that? It might be just that simple...isn't that something that can be done in OEMizer? It makes sense now that you mention it since it does add to the email tab it probably works just like email. I don't set up my email through the tab. I use Seven and set up email that way...I still need to work that out as well so I don't have to manually setup Seven.

Re: [TUT] Creating OEM's for your ROM
 

I don't mind answering questions to the best of my ability, just don't want my other thread....well...

Learn about EMAIL2 configurations service in the following thread, post #5
http://forum.ppcgeeks.com/showpost.p...76&postcount=5

Re: [TUT] Creating OEM's for your ROM
 

Ok, I read over this EMAIL2 thing. Been trying to wrap my head around it all day actually. I assumed that some of those setings would already bee in teh registry in order for picture mail to be identified but I have not seen anything associated with Picture mail and anything in the EMAIL2 provisioning. Even if I did set up according to that, I am not sure where I would get even half of the settings that need to be used in it.

Re: [TUT] Creating OEM's for your ROM
 

I use it to setup my gmail accounts. But for picturemail, I registered sMMS that's made from some mms guy, don't really know who...lol back on track. But I registered sMMS, and exported the settings into an OEM that takes care of my personal settings/registrations. But I send like one pic per month...

edit: I have heard that some have just copied \cemail.vol over and cook it into their roms...

Re: [TUT] Creating OEM's for your ROM
 

It's a manifest file. In a nutshell, it's the module name and version, target processor, and file list. Some .dsms have more stuff in them.

They are mostly rebuilt when you build, which is why you can mostly ignore them. I think they're completely ignorred in Bepe's latest kitchen.

Re: [TUT] Creating OEM's for your ROM
 

Oh, there are more now.

See this: PPCkitchen BuildOS tags

Re: [TUT] Creating OEM's for your ROM
 

BTW, woodson made an app that will configure phone specific settings on boot. We'll probably expand on the idea a bit to make it more flexible.

Re: [TUT] Creating OEM's for your ROM
 

Can you point me to this app? Picturemail is killing me here. Everything seems right but the app won't fully install. Trying the cemail.vol thing but I think that will be just corruption waiting to happen.

You heard right! I just tried it and anything email was saved...sms too. So, since I am really only concerned about picture mail, I am doing a fresh flash, installing picturemail by cab then making a copy of cemail.vol and using that in my rom. I'd like to do this for Seven as well but I don't want old emails popping back up and I am not sure how to prevent Seven from pulling emails once it's set up...for the first time anyway. After I get a clean cemail.vol I don't care if it pulls emails.

Re: [TUT] Creating OEM's for your ROM
 

not very upgradeable. Expect it to break when changing CE builds.

Re: [TUT] Creating OEM's for your ROM
 

Not sure to what extent that files serves but if it's just basic email information then I am not sure how it will break when changing CE builds. Not very upgradeable is very true though. It's a royal pain to make a copy of that specific file. For my needs though, I won't need to upgrade it. I have no desire to save all of my emails or texts and I only needed it specifically for the final install of my OEM picture mail. It works great so far.

Re: [TUT] Creating OEM's for your ROM
 

If they ever modify what a "record" consists of, then an old file will be "corrupt" when used with the new build. Doesn't happen often, but it does happen.

Re: [TUT] Creating OEM's for your ROM
 

Guys,I loss my sleep lol.This post is priceless!!!Im getting better and better iand my vogue too!!!http://forum.ppcgeeks.com/images/icons/icon14.gif

Re: [TUT] Creating OEM's for your ROM
 

What if application contains 3 different .exe?Like s2u2?Do I have to use package creator 3 times for each exe,so they will be as 3 single oems(1-ilock2,2-setting,3-s2y2 itself)?Attaching latest s2u2 1.40.cab.

Re: [TUT] Creating OEM's for your ROM
 

From the initflashfiles tab, you simply highlight each .exe, check the "programs" button, then press the apply. This creates a link for each one.
With that one, I manually copy the .lnk's from the device and add an initflashfiles.txt entry al manually. And that one is in my custom vga oem requests link if you want to look into it to see how I did it...

Edit: I see I had a typo and called it v1.35... :)

OEM_S2U2-1_40-VGA................................................ Slide 2 Unlock 2 v1.40 VGA

Re: [TUT] Creating OEM's for your ROM
 

thats,what I thought,but for som reason I can highlight only 1 at a time...I will try again.what about manilla2d?should I check .exes as a programm or its something else?

Re: [TUT] Creating OEM's for your ROM
 

Not all .exe's require an entry. Usually you'll only want to create entries for those the .cab install does. Either \Windows\StartUp, or \Windows\Start Menu. And in EPC, click on each .exe individually, click apply, then highlight and apply the next .exe you want a link file created for before clicking done and proceeding to the next step.

Re: [TUT] Creating OEM's for your ROM
 

I did it!with a small custom touch...it will show 3 grafic shortcuts in programms menu. and custom wallpaper.If somebody want this OEM,here it is.It works on my vogue...S2V not included.I dont know what ilock2 made for,but readme doc said to run it first...Anyone knows whats the point of running ilock2 first?

Re: [TUT] Creating OEM's for your ROM
 

is there any tools to convert oem into cab?or can I compress oem with winrar and rename it to .cab?

Re: [TUT] Creating OEM's for your ROM
 

Thanks, this tutorial helped me a lot! :>

Re: [TUT] Creating OEM's for your ROM
 

Finally I made my own mega M2D-update 20,OEM...took me 2 weeks LOL of editing XMLs and initflashfiles,but I did it.Thanks to this tutorial!!!!!!

Re: [TUT] Creating OEM's for your ROM
 

That's what I'm talking about! Congrats vin! You did a whole GUI, I think my first oem was frogger... :)

Re: [TUT] Creating OEM's for your ROM
 

I really appreciate this thread. I spent a few days doing research, too bad I didn't find this first.

Re: [TUT] Creating OEM's for your ROM
 

thanks!

Re: [TUT] Creating OEM's for your ROM
 

Your welcome... Everyone should have these skills. It's the first step in breaking your dependances on forum chefs. :mrgreen:

Re: [TUT] Creating OEM's for your ROM
 

man u r like a saint lol thank you so much!!!

Re: [TUT] Creating OEM's for your ROM
 

thanks for the excellent tutorial...I have been researching for awhile and trying to learn this.....Cant wait to cook up the last part of the ROM i have been working on for Cricket for the Titan...Gonna be alot of late nights learning this and I am looking forward to it!!!!!:headbang:

Edit: My bad...wasnt paying attention to the device for this....was simply excited to learn about creating OEM....much obliged!

Re: [TUT] Creating OEM's for your ROM
 

Here's the test oem for pointui2vga. probably doesn't work though. thanks for looking at it RSTG.

Re: [TUT] Creating OEM's for your ROM
 

Promoted this thread to a Sticky as it deserves it.

Carry on.

Re: [TUT] Creating OEM's for your ROM
 

I demoted it -- carry on.

Re: [TUT] Creating OEM's for your ROM
 

I'm feeling like a yo-yo fella's... lol... The good stuff, make 'em search for it!

Re: [TUT] Creating OEM's for your ROM
 

hey man i love thread this is where i stsrted to learn how make oems for the most it always works the hard part is finding the dups so thanx my next thing to learn it how to make cabs with ceregitor

Re: [TUT] Creating OEM's for your ROM
 

Oh, that's easy. I already have a thread that I will be explaining it in here:
http://www.everythingdiamond.info/showthread.php?t=382

Re: [TUT] Creating OEM's for your ROM
 

Should we assume that creating an OEM for the Visual Kitchen is the same thing, just remove the option.xml file?

Re: [TUT] Creating OEM's for your ROM
 

That works, but there's easier ways to do it. Try the file I've attached and read the readme.txt for info. It'll batch convert cabs to OEMs and make them into EXT packages if you want. If you just want a simple way to make an OEM, just drag the cab onto Cab2OEM.exe...and poof you have an OEM. It works for most cabs, but there's been a few where I've had to use packages_creator_5.4.exe. Kraize from xda put this .zip together.

Re: [TUT] Creating OEM's for your ROM
 

Ok, everything looks good. I might add the following to it:
Copy your start menu link to the OEM and add it to the initiflashfiles.txt file.
Export some of the registry entries after you set it up into the RGU. I use CeRegistry Editor. Like the HKLM\Software\PointUI\Home 2 keys, and the today plugin key looks ok...

Other than that, I don't see any reason it should boot. I didn't install it, but it should be ok from what I see...