PPCGeeks - Kitchen OEMs

PPCGeeks (http://forum.ppcgeeks.com/index.php)

- HTC Apache (http://forum.ppcgeeks.com/forumdisplay.php?f=14)

- - Kitchen OEMs (http://forum.ppcgeeks.com/showthread.php?t=2258)

Installed Nonunicode version of SprintExtROM - #777 works

Schettj-

Thanks for the hardwork. I compiled the non-unicode version of your file above, and installed it on my 6700. Then, went to Internet Explorer, and cruised to yahoo.com and the phone autodialed #777. Checked on ##786#, and that pulled up Sprint EPST.

I havent checked out every ##CODE, but I will be over time.

Great job having done this. Thanks again. I will keep you posted as to issues I run across

Booya!

Thanks for the test - and that means the conversion from CAB to OEM is really simple, so I can write it up - granted there are 1000 "writeups" out there, and I have read them all, but they're all 4 lines long and that's it :D

Quote:

Originally Posted by schettj

Yeah, the conversion is really simple, especially if you use wince cab manager. I was able to make OEMs for handyswitcher, memaid, and threaded sms really easily (intentionally being cryptic on this last title) :o) I have virtually everything I use loaded in Rom and Ext Rom now, and I have 35 mb free!!! Only thing I don't have pre-loaded is Voice Command 1.6, because I am still trying to figure out the bluetooth issue.

Instructions re making OEM; Next steps (DOC repartition?)

Finster-

Any idea how to create OEMs either (a) without having to pay for license for Wincab, or (b) using freeware tools (mscie and cabwiz)? If so, please PM me or post.

Schettj-

Will you be posting instructions? If so, where? If not, care to PM me?

Also, as far as next steps, has any further thought been given to the concept of DOC repartitioning (something discussed a LONG time ago)? Just curious what the consensus is on that (and, yes, it may be considered off-topic, but it is a logical next step once Kitchen ROM is optimized to redo doc partition to JUST the right size (and no more)).

Thanks in advance

Re: Instructions re making OEM; Next steps (DOC repartition?

Sorry, didn't try it using those freewares. The method is pretty straight forward:

1. Extract all files (non-registry and shortcuts) to a folder.
2. Export all registries to a .reg file
3. Get a UUID number from http://kruithof.xs4all.nl/ (click on 1st link).
4. Open reg file with notepad and save as unicode, all files, with the UUID number .rgu as the name (xxxxxxx.rgu).
5. Open notepad and save a blank file unicode, all, with the UUID number.dsm (xxxxxx.dsm).
6. Make your initflash.txt file with any necessary shortcuts.
7. If you made a shortcut, then make the linkfile by opening up notepad and typing 25#"\windows\MemMaid.exe" or whatever. Save the file with the name of the .lnk file from the initflash.txt file (i.e. MemMaid.lnk).
8. Move the folder to OEM and you should be good to go!!!

Re: Instructions re making OEM; Next steps (DOC repartition?

Quote:

Originally Posted by finster869

Sorry, didn't try it using those freewares. The method is pretty straight forward:

1. Extract all files (non-registry and shortcuts) to a folder.

This can be done with the freeware MSCEInf.exe
http://www.codeppc.com/telechargemen...nf/msceinf.htm
(Get the english version :D )
Simply extract all files in the CAB to a folder

Quote:

2. Export all registries to a .reg file

With the above app, you will get a folder from the CAB - in the folder will be:
one or more folders
SETUPDLL.dll
Tools.inf
open the Windows folder
You're going to be using most everything in here, but you will be doing some work on it. You will not be using CheckFile.exe or __cusTSKTEMP.exe if they are there, and you will be using the contents of Platformxxx.reg (That's your registry entries!) and CM_Entries.xml (those are the ones that are going into your mxip_PACKAGE_REV.provxml file)

Ok - so copy all files except the above to your OEM folder, make a UNICODE reg file as in step 4 below and copy the contents of the .reg file into it, and make a plain text file named mxip_PACKAGE_REV.provxml (where PACKAGE is your package name, and REV is some 3 digit rev number) and copy the contents of the CM_Entries.xml into it. You do not need this proxml file if there is no CM_Entries.xml file, or if its empty.

Finally, look at the Customize.lst file in Notepad - it tells you where any addition files are in the CAB - for example if it says
\temp\PhoneSetting.htm
Then that file (PhoneSettings.htm) will be in the temp directory one up from Windows... so copy those files to your OEM folder too... and you'll then need to copy those files via initflashfiles.txt to their correct locations... often the correct location will be in the CM_Entries.xml file, so you can edit the move operations out of there and just put the right moves into initflashfiles.txt

Example:

Customize.lst :

Code:

\temp\PhoneSetting.htm

CM_Entries.xml

Code:

<wap-provisioningdoc>

















        <characteristic type="FileOperation">

                <characteristic type="\Program Files\IOTA\jTelDll.dll" translation="install">

                        <characteristic type="Copy">

                                <parm name="Source" value="\temp\jTelDll.dll" translation="install"/>

                        </characteristic>

                </characteristic>

                <characteristic type="\temp\jTelDll.dll" translation="install">

                        <characteristic type="Delete">

                                <parm name="ForceDelete"/>

                        </characteristic>

                </characteristic>

        </characteristic>



        <characteristic type="Registry">

        <characteristic type="HKLM\Software\Apps" translation="filesystem">

                <parm name="CabName" datatype="string" value="IOTA_v1_10" translation="filesystem"/>

        </characteristic>

        </characteristic>

</wap-provisioningdoc>

In this case, we will not use ANY of this, but it does tell us what we need to know... that the file \temp\jTelDll.dll in the CAB needs to be in \Program Files\IOTA\jTelDll.dll on the device...

initflashfiles.txt

Code:

Directory("\Program Files\IOTA"):-File("jTelDll.dll","\Windows\jTelDll.dll")

Phew!

Now, back to the checklist!

Quote:

3. Get a UUID number from http://kruithof.xs4all.nl/ (click on 1st link).
4. Open reg file with notepad and save as unicode, all files, with the UUID number .rgu as the name (xxxxxxx.rgu).
5. Open notepad and save a blank file unicode, all, with the UUID number.dsm (xxxxxx.dsm).
6. Make your initflash.txt file with any necessary shortcuts.
7. If you made a shortcut, then make the linkfile by opening up notepad and typing 25#"MemMaid.exe" or whatever. Save the file unicode with the name of the .lnk file from the initflash.txt file (i.e. MemMaid.lnk).
8. MOve the folder to OEM and you should be good to go!!!

I hope to be able to write up a better guide to the CM_Entries.xml stuff, as its kinda important to read it, delete what you don't need, and include what you do, but you get the general idea (hopefully!) and can start poking around with this.

schettj,
I tried both versions of the updated Sprint OEM package you made and neither have fixed the battery icon or #777 connection issue. Is there a file that needs to be run for it to work, or could they be converted to registry entries in the rgu?

Interesting cause i used shettj's release from this morning, and i'm gettin #777 connections perfectly, as well as the battery icon.. for me the release he did early today worked perfectly.

Quote:

Originally Posted by ImCoKeMaN

I'm confused now... we have two reports, one it works one it does not. Are you both on 3.5? CoKe are you sure you've got the updated one in your ROM (should not have any errors, and no warnings about PhoneSettings.htm) - it should be the nonUnicode version. I've checked a few other OEMs using the xml thing, and they do exactly what I did, so it should be working (unless there is a version difference in 3.3 vs 3.5, but I doubt it...)

Nothing needs to run, it should just be in the ROM, and on COLD/HARD BOOT it installs - are you doing a cold boot? It won't run on a soft-reset.

Pulling the 10KB of registry settings in the xml file and reformatting them to the reg format does not sound like fun, but maybe someone else is willing to do it :D It's just a text file.

I'm sure i did a hard boot, maybe there is a difference with the AKU 3.5. Also each time i'm loading it i'm testing something new with the USB. This shouldn't really be the issue though because everything else is stable i just changed the one driver and its reg entries. I completely understand not wanting to do the reg entries, we'll see what happens.

sfaure03,
You say this worked for you. Are you sure that you didn't let the "customizing" happen from the extended ROM? To actually test the OEM you will need to do a soft reset before the customizing in 3 seconds screen starts installing stuff.