Hey all,
So that we don't all have to reinvent the wheel, is it possible where we could share OEM Package setup info to be used in the Faria ROM Kitchen. I know a number of your are adding your own packages, and this could save a lot of work for those of us just starting to look at customizing this tool. Use ftp://ftp.xda-developers.com/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf to read up on how to create OEM packages and how they work.
What I'm thinking is that this thread could be a repository for packages (not for requests, but for packages people want to share). Bascially you would reply to this thread with what the package is for, and any special information and setup (or things people may want to look at and change), and then attach a zip file (or pointer to the package file) that people can then download and put into their devwiz folder. If its for a commercial (non-free) program, leave out the commercial program / dlls but just to have the other files setup and instructions on what to put into the folder could be very useful for people.
When you provide the packages, try to provide it with the original package.rgu and/or package.dsm filenames (not with the GUID that was generated for you). People will then be able to just run the buildos.exe and the GUID will get created for them without changing filenames. Then just edit the options.xml file to use the newly generated GUID.
so screenshot + cab + short info + status: freeware/shareware/etc. would be fine?
mfrazzz said:
Hey all,
So that we don't all have to reinvent the wheel, is it possible where we could share OEM Package setup info to be used in the Faria ROM Kitchen. I know a number of your are adding your own packages, and this could save a lot of work for those of us just starting to look at customizing this tool.
What I'm thinking is that this thread could be a repository for packages (not for requests, but for packages people want to share). Bascially you would reply to this thread with what the package is for, and any special information and setup (or things people may want to look at and change), and then attach a zip file (or pointer to the package file) that people can then download and put into their devwiz folder. If its for a commercial (non-free) program, leave out the commercial program / dlls but just to have the other files setup and instructions on what to put into the folder could be very useful for people.
The only tricky thing here would be the guid for the files. I'm still new to this, so if someone has an idea how to handle that (maybe the person does the package.rgu and runs the program where it generates the guide, then unzips the files and modifies the guid to the new one in the right places).
Click to expand...
Click to collapse
The GUID is so simple, if you to use a package, just go to http://www.famkruithof.net/uuid/uuidgen . Then you just get a new GUID and paste it in all the different palces in the package, then you dont have to chnage file names then have them chnaged again by buildOS
I thik this is a good idea, would be good to share and also good for problem finding, cus i have one that i cant for the life of me get the today plugin to work how it is meant to!!!
GSFinder Package
[... This package has been updated and can now be found in post 23 of this thread ...]
This is a package for GSFinder. This is a freeware file manager (like TotalCommander).
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
MoDaCo NoData
[... This package has been updated and can now be found in post 23 of this thread ...]
This is a package for MoDaCo NoData. This is a freeware program that allows you to turn off and on what data sources will work on your device (so if you don't have a GPRS plan, you can turn off GPRS so your phone will not use it).
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
mUn Keyboard Skin
This is a package for the mUn keyboard skin. This is a freeware skin file to modify the look of the on screen keyboard to be like what is in the mUn aRTM WM6 rom.
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
NOTE: If you have other keyboard skin files in your OEM directory, you may get an error when you build this initially (or if more than one is selected). You can only have one of the keyboard skins selected.
XPlore Keyboard Skin
This is a package for the XPlore keyboard skin. This is a freeware skin file to modify the look of the on screen keyboard to be like what is provided for the XPlore 2.0 WM6 rom.
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
NOTE: If you have other keyboard skin files in your OEM directory, you may get an error when you build this initially (or if more than one is selected). You can only have one of the keyboard skins selected.
mfrazzz said:
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
Click to expand...
Click to collapse
Thanks for putting this together!
I tried building via your instructions, but got an error (buildos.exe crashed). I deleted the options.xml file and then re-ran the build and it worked. Then copied back in an options.xml file and edited the GUID and it ran fine.
I'd noticed this when I was building another package. In my experience, I have to do a build without the options file, let the [GUID].dsm file get built, then create the options.xml file with the correct GUID in it and then rerun.
saeba said:
Thanks for putting this together!
I tried building via your instructions, but got an error (buildos.exe crashed). I deleted the options.xml file and then re-ran the build and it worked. Then copied back in an options.xml file and edited the GUID and it ran fine.
Click to expand...
Click to collapse
Yep I figured this out an hour ago. The options.xml should be renamed until the first run of builos.exe completes, then rename it back and change the guid inside the file.
I'll redo the packages tomorrow and update the instructions on them.
mfrazzz said:
Yep I figured this out an hour ago. The options.xml should be renamed until the first run of builos.exe completes, then rename it back and change the guid inside the file.
I'll redo the packages tomorrow and update the instructions on them.
Click to expand...
Click to collapse
Can i jst say that the chnace of the same number being used again in you kitchen is really high, so you should not have to chnage it!!! Try run the buildOs without chnaging anything!
Has anyone figured out how to move files yet?
RickoT said:
Has anyone figured out how to move files yet?
Click to expand...
Click to collapse
The initflashfiles.txt moves the files (doesn't just make duplicates). So you just have to put a line in for everyfile to "move" it to a different location. The next post will be for BatteryStatus and you can look at that one as thats what it does. All the graphic images are moved into a directory it creates.
Battery Status Package
[... This package has been updated and can now be found in post 23 of this thread ...]
Here is the package for Battery Status. I initially put this together but had some errors in how I did things. Thanks to ADB100 for cleaning it up! This is the same one he reposted for me in the Faria Rom Kitchen thread.
ALso going with Funman's point that its unlikely to hit a duplicate GUID, so I'm leaving the GUID alone. So just extract to the OEM directory and you are ready to go.
This package contains Battery Status 1.04.202 Beta 3 Build 0195 (latest version at the time of this posting).
Reposting with generic Registry Entries (removing ADB100's custom settings he mentions in his post below)
WM5torage Package
[... This package has been updated and can now be found in post 23 of this thread ...]
Package for WM5torage (version 1.73). Just unzip in your OEM folder.
Note, the package puts a shortcut in the \Windows\Start Menu\Accessories folder for WM5torage. Edit the initflashfiles.txt if you want the shortcut to be located someplace else.
mfrazzz said:
Here is the package for Battery Status. I initially put this together but had some errors in how I did things. Thanks to ADB100 for cleaning it up! This is the same one he reposted for me in the Faria Rom Kitchen thread.
ALso going with Funman's point that its unlikely to hit a duplicate GUID, so I'm leaving the GUID alone. So just extract to the OEM directory and you are ready to go.
This package contains Battery Status 1.04.202 Beta 3 Build 0195 (latest version at the time of this posting).
Click to expand...
Click to collapse
I should note that it is pre-configured with the following options:
General Tab - Show CpuSpeed, Show Mobile Operator
Indicator Tab - Show more Indicators, Use Small Fontsize, Show Powerdrain, Show Temperature
Tools Tab - DeviceLock on Wakeup, Lock if Display..., Backlight fix - 30-seconds
Omap Tab - Overclock to 247Mhz, Overclock on Wakeup, Remember last CpuSpeed, Overclock after reboot
Traylaunch Tab - All disabled
Not sure this will suit everybody so be warned...
Andy
Adobe Reader LE
[... This package has been updated and can now be found in post 23 of this thread ...]
Package for Adobe Reader LE. This is the "faria Adobe Reader" cab thats been posted, but then I've altered the .rgu to fix the registry entry for opening docs that have spaces in the name (Thanks ADB100 for pointing that fix out), and made a couple of fixes to the initflashfiles.txt (it had moves for files that didn't exist and I've added where it moves a shortcut into \Windows\Start Menu\Programs\Accessories
Just unzip into your OEM directory.
ADB100 said:
I should note that it is pre-configured with the following options
[... snip ...]
Not sure this will suit everybody so be warned...
Click to expand...
Click to collapse
I've reloaded the zip file in my post above for Battery Status and put the registry entries back to generic like a fresh install. If you want specific settings, then install BS, tweak it to your heart's content, then dump out the registry entries and replace them in the .rgu file.
mfrazzz said:
Package for WM5torage (version 1.73). Just unzip in your OEM folder.
Note, the package puts a shortcut in the \Windows\Start Menu\Accessories folder for WM5torage. Edit the initflashfiles.txt if you want the shortcut to be located someplace else.
Click to expand...
Click to collapse
Sorry mate but your package is not right! The .rgu was not setup right!
funman said:
Sorry mate but your package is not right! The .rgu was not setup right!
Click to expand...
Click to collapse
Arrrgh! Sorry about that. I was putting that one together and got interupted with a concall at work, and some other things. I went back to working on it, and I guess I didn't edit and fix what I thought I had done... Sheesh...
Thanks...
mfrazzz said:
The initflashfiles.txt moves the files (doesn't just make duplicates). So you just have to put a line in for everyfile to "move" it to a different location. The next post will be for BatteryStatus and you can look at that one as thats what it does. All the graphic images are moved into a directory it creates.
Click to expand...
Click to collapse
Are you sure, because I think I read in faria's rom thread that it copies the files, not moves them, (Unless im utterly retareded and misread it, which is very possible)
Hello ALL!
Here is the long awaited HTC Tornado ROM kitchen
This Kitchen is in actual fact the Molski DEVPACK kitchen but its been MODIFIED by myself, Duke_Stix in order to be compatible with the HTC tornado and to make rom editing and cooking easier for EVERYONE!
Please note, before anybody starts pointing fingers, FULL permission was obtained from molski himself before any modifications were made and full permission was obtained in order for me to release this kitchen as the initial kitchen was of course, by MOLSKI!
This was the first kitchen that i learnt to use so it was the first kitchen i modified!
There will also be a modified CORE kitchen released soon too once i can iron out any and all bugs.
Anyway:
Pretty simple to run really. heres a few instructions to get you all started:
Download the attached file: Molskis_Devpack_modified_for_tornado_by_duke_stix.exe
READ THE PDF FILE THAT IS IN C:\DEVPACK\tools\batch\readme
Here are steps:
1) RUN the executable file, you should end up with TWO folders, DEVPACK and Molski.biz Devpack. MOVE the 'DEVPACK' folder to the ROOT of your C: drive.
2) Place ANY nk.nbf that you wish to 'unpack' into the source folder of the DEVPACK folder. so.....
' C:\DEVPACK\source ' Contains your NK.NBF file
3) Go to your desktop and into the 'molski.biz devpack' folder, this has lots of little shortcuts in it.
4) first of all, click the 'dump rom' script.
5) Let it do its thing
6) in the C:\DEVPACK folder there should now be a new folder called......ROMDUMP! (<-- guess whats in here?!)
7) Edit as much as you wish, dont forget to get rid of the first two bytes in the initflashfiles.dat file before you build rom again
8) once you've clicked the 'build rom' script go back into c:\devpack\tools and in there should be nb2nbf_tornado.exe
9) open that, dont touch anything atthe top apart fro the output field, here, I would suggest selecting your desktop and you MUST issue the file name as 'nb.nbf'
10) below that click the tick box next to 'File #1:' it will allow you to select 'file #1' point it to c:\DEVPACK\ROMDUMP and to the file called 82040000-OS.nb
11) back in the nb2nbf program select 'OS' under image name
click translate
go to your desktop, move the nk.nbf file there into C:\DEVPACK\tools\RUU_2001
run the 'ROMUpdateUtility.exe'
and away you go! should start flashing
IT IS IMPORTANT THAT YOU READ THE README FILE! i will also attach it to the post
also, anyone willing to donate can send any paypal donations to [email protected] and reference them 'duke'! very much appreciated!lol
MIRROR:
http://www.megaupload.com/?d=VWCLXM6Z
ENJOY!
post any questions here
AND DO NOT FORGET TO READ THE README FILE!!!!!
ALSO READ: http:\\www.molski.biz
HAPPY COOKING!
duke_stix said:
How to use this Rom Cooking Pack:
I tried to make everything as simple as possible, still you definitely need to know what you are doing!
Step 1:
Extract the nk.nbf file from a Rom archive (all Rom archives can be opened with tools like WinRAR) into the X:\DEVPACK\source directory.
Step 2:
Execute the DUMP_ROM script when the script is finished a ROMDUMP folder is created in X:\DEVPACK, with all the .nb files found in the nk.nbf file, the 80040000-OS.nb file will be splitted into 2 template (.bin) files and the contents of the OS templates is placed in the “dump” folder.
Step 3:
When the script is finished you can start adding and deleting (watch out what you delete!) files in the dump folder.
Step 4:
Editing the initflashfiles.dat file!
Execute the EDIT_INITFLASHFILES script so the file gets copied to the ROMDUMP directory, a backup of this file is placed in the Backup folder inside the ROMDUMP directory!
This is a very important file, when the Wizard gets a hard-reset or is flashed to another Rom, this file builds the directory structure, copys files from Windows to (as example) the Program Files directory.
These are some examples from the initflashfiles.dat file:
root:-Directory("My Documents")
Directory("My Documents"):-Directory("My Pictures")
Directory("\Windows\Start Menu")ermDir("Programs")
Directory("\Windows\Start Menu")ermDir("Settings")
Directory("\Windows\Start Menu"):-File("Messaging.lnk","\Windows\tmail.lnk")
Directory("\Windows\Start Menu\Programs"):-File("File Explorer.lnk","\Windows\fexplore.lnk")
Directory("\My Documents\Templates"):-File("love.gif","\Windows\love.gif")
As you can see, not so tough as it looks, I am not going to explain every single line of this file, but will give you one example….just to make things a little bit easier to understand!
All files from the “dump” folder are basically placed in \Windows and get copied to other directories from this point, so when a shortcut is copied from \Windows to \Windows\Start Menu\Programs you will have a shortcut in both directories (but that’s not a big deal!).
I am going to explain this line, to let you know what this line actually does
Directory("\Windows\Start Menu\Programs"):-File("File Explorer.lnk","\Windows\fexplore.lnk")
The shortcut fexplore.lnk in \Windows gets copied to the \Windows\Start Menu\Programs directory and gets renamed to File Explorer.lnk
Very easy….isn’t it? J
So…after adding all files to the “dump” directory, adding the lines of the added files (IF needed) to the initflashfiles.dat file you can save this file, make sure the last line in this file is a blank line (otherwise your device will be stuck at the second Splash Screen)!!
Example:
When you want to add a program named ABC.exe to \Start Menu\Programs, just copy the ABC.exe file to to the “dump” folder and place a shortcut named ABC.lnk in the “dump” folder and add a line for ABC.lnk into the initflashfiles.dat file.
To create a shortcut for ABC.exe, simply open Notepad, create a line like this:
24#"\Windows\ABC.exe"
(the number can be different), save it as ABC.lnk and add this to the initflashfiles.dat file:
Directory("\Windows\Start Menu\Programs"):-File("Alphabet.lnk","\Windows\ABC.lnk")
In this example the shortcut ABC.lnk, that points to ABC.exe gets placed in Programs with the name Alphabet.
After saving the initflashfiles.dat file, open the file in WinHex and remove the first 2 bytes (FF FE)!
If you don’t remove these 2 bytes your device will also be stuck at the second Splash Screen!!
After removing the 2 bytes and saving the file you can copy it to the “dump” folder (overwrite the original initflashfiles.dat file….don’t worry, you still got the backup of the original file in the Backup folder)!
Step 5:
Editing the HV Files!
Okay, let’s say that the application used in the example (ABC.exe) has a few Registry Values and will not work without it, therefore we will need to edit the default.hv and/or user.hv files.
Execute the script CREATE_RGU_FILES, this will copy the default.hv and user.hv files from the “dump” folder into a directory called HV Files in the Romdump directory and convert the 2 .hv files into .rgu files so we can edit them with notepad.
When editing .rgu files there are 4 things that are very important!
Turn off Word Wrap in Notepad
The 1st line is a blank line, type “REGEDIT4” (without quotes) on this line
Make sure the last line of the file is a blank line
Make sure the files are saved in Unicode and not in ANSI
The Windows Mobile Registry has 4 keys:
[HKEY_CLASSES_ROOT] à These Registry keys gets insert in the default.rgu file
[HKEY_LOCAL_MACHINE] à These Registry keys gets insert in the default.rgu file
[HKEY_CURRENT_USER] à These Registry keys gets insert in the user.rgu file
[HKEY_USERS] à These Registry keys gets insert in the user.rgu file
When you are finished editing the .rgu files, execute the CREATE_HV_FILES, watch properly of the files get converted without errors, if everything went okay, copy the default.hv files from the HV Files directory to the “dump” folder (overwite the original files….don’t worry, you still got the backup of the original file in the Backup folder)!
Step 6:
Okay, by now we have extracted and dumped the nk.nbf file, added and/or removed files from the “dump” folder, edited the initflashfiles.dat file, added registry values in default.hv & user.hv and copied the 3 edited files to the “dump” folder.
Now we are (finally…) ready to build the Rom!
Execute the script BUILD_ROM and wait till it’s finished (will take a couple of minutes depending on the speed of the computer).
This script will add the modified “dump” folder to the OS template files (.bin files) and when that is done it will build the 8004000-OS.nb file from the OS template file.
[\QUOTE]
Click to expand...
Click to collapse
Click to expand...
Click to collapse
reserved yet again
Thanks a lot for this tool i'll look that when i will go at home.
Thanks for all your job
can't get to megaupload.
can you upload it to rapidshare? thanks for your work.
ericjm said:
can't get to megaupload.
can you upload it to rapidshare? thanks for your work.
Click to expand...
Click to collapse
http://rapidshare.com/files/46589256/Molskis_Devpack_modified_for_tornado_by_duke_stix.exe.html
burkay said:
http://rapidshare.com/files/46589256/Molskis_Devpack_modified_for_tornado_by_duke_stix.exe.html
Click to expand...
Click to collapse
thanks dude!
anyone tried this yet then?!
\
im awaiting feedback!
When I tried to dump rom, I get this
Splitting 80040000-OS.nb into .bin files....
Unable to open source image [80040000-OS.nb]
Creating Dump directory....
Dumping Rom content into dump directory....
Please wait a couple of minutes, depending of the speed of your computer!
Dump folder is ready in ROMDUMP directory!
Press any key to continue . . .
Why is it that I am unable to open source image ?
Looks like duke stix forgot to add a rename command in the batch file.
The wizard NBF WDATA start address for the OS is 80040000 and the tornado WDATA start address is 82040000, so rename 82040000-OS.nb to 80040000-OS.nb and it should work.
Phil
jm012a9749 said:
Looks like duke stix forgot to add a rename command in the batch file.
The wizard NBF WDATA start address for the OS is 80040000 and the tornado WDATA start address is 82040000, so rename 82040000-OS.nb to 80040000-OS.nb and it should work.
Phil
Click to expand...
Click to collapse
Actually im dumping using Mozbi Devpack for Wizard, thought it is the same, it works now.
Thanks
oioi
I'll get to changing that right now. didnt notice that!
Good tools and good explanations.
I dumped I rebuilt a Qtek ROM today for my wizard, and the advices of this thread were the biggest help.
Thanks and well done.
Customized ROM hanging in spash screen
Hello Duke,
I am currently in the process of customizing my own ROMs from other user builds thanks to the tools you provided. I am having problems though...I have used multiple nk.nbf (different os) files and dumped then rebuilded without modification just to make sure I have the technique correct. That is without modifying initflash or hv files and going right to rebuilding after dumping and I am hanging on the first screen. I then need to manually go to bootloader for reinstall.
I then checked with my modified ROMs following pdf religiously (ie deleting first 2 bytes and leaving last empty line-initflash...and adding REGEDIT4 and leaving last line saving as unicode-rgu...following instructions provided) and yet I continue to hang on the first screen.
Do you have any suggestions??
Thanks again,
vjgrace
I have this comm manager that I found from the forums a while back.. It was made my MFRAZZ... This installs correctly and works fine... However, I wanted to change the color of the buttons from blue to a maroon color that fades to black to match the theme on my phone
I opened the cab file and found quite a few files and an XML file... I found out the the other files were actually .png files renamed. I renamed them to ] .PNG and used Gimp to edit the pictures. I then renamed the files back to the origional file extension and used winrar to make it back into .cab.
I have a pic of the comm manger below, a pic of the error message and a pic of my current theme listed below. I also have the comm manager made by MFRAZZ and the comm manager I have edited attached below. They are clearly labeled.
Any help would be greatly appreciated. Maybe you could enlighten me on what I did wrong.
This is not an issue where the comm manager is open or running in the background. I think I might have done something to the files when editing them to change their colors. Any help would be greatly appreciated.
Picture titled Comm manager: This is the comm manager successfully installed to my device. This shows the blue Icons which I have changed to maroon.
Picture titled Unsuccessful: Error when I try to install the new edited comm manger.
Cab file titled Touch Comm Manager: The blue comm manger made by MFRAZZ
Cab file titled Comm Manager Maroon: The comm manager that I edited the picture colors and which will not install to my Device.
Help??
So no one interest in helping someone out?
you cant simply repack the cab with winrar , you need to sign the Comm Manager with Certificates, search the ofrum for msigner, download it and sign the comm manager with it and then hopefully you'r good to go
Do i run msigner on the cab file or do i run it on the individual files packed into the cab file? thanks
Msigner
Alright, this is what i got when using msigner on the cab file as well on the individual files inside of the cab file.... Looks like I'm doing something wrong.. Heres the error message
Error: Signing Failed. Result = 800b0003, (-2146762749)
I only found 2 threads on this error message while using msigner. Neither one was successful at helping me with my issue.
Thanks in advance
I searched some other forums on signing cab files as well as my best friend.... GOOGLE. It appears that im going to need a windows mobile 6 sdk and a program called MSDN.. Is this correct? Is there an easer way to do this?
i think it misses the Certificates, make sure you dnt take the EXE out of its root folder
Use MSCEinf to dump the CAB file (7th button from the left on the toolbar), then edit the PNGs, then repack the CAB with Cabwiz:
cabwiz "fullpath\filername.inf"
Cabwiz is included with XP, but if you can't find it, you can get it here.
the CAB does not have to be signed, and since you're not editing the EXE, it doesn't have to be signed either.
Thanks to Benthon for his wonderful MSCEinf. A free program that he continually updates for the benefit of us WinCE users.
J03M4N
Ok...
I have a folder on my desktop thats says Msigner. When I open it up, I see a file that says Ssigner.exe. I can click on that and it opens up but it wont let me write a certificate to my cab file. there is also a yellow folder that is labled tools..... It has a quite a few dll files in it.
Any help would be appreciated
Joemanb,
thanks for the software. Tried it out and it wont open up my cab file that I created. however it will open up the origional cab file... Maybe i did something wrong haha.....
*Update*
I used the program in the last post. it wouldnt readthe cab file that I created but It read the origional cab file from MFRAZZ. I put the origional cab file from MFRAZZ into the program and extracted the files.
It extracted all the files into the correct file format. All my pictures were .png. I thought I was on the right track. I went aheadand edited all the pictures to make them the colors I wanted them to be. I also saw a .mui file... and I saw comm.exe. I expect thats the comm manager. There is not .xml fle now.
How to I repack all of this back into a cab file?
Thanks in advanced
Instructions on how to create the CAB are in my first post :
then repack the CAB with Cabwiz:
cabwiz "fullpath\filename.inf"
Cabwiz is included with XP, but if you can't find it, you can get it here.
Click to expand...
Click to collapse
Type the command at a DOS prompt: 'fullpath' is the full path to the folder you dumped the CAB to, and 'filename.inf' is the name of the .inf file created when you dumped the CAB. Don't forget the quotes.
J03M4N
Sorry. I get a little ahead of myself. This is my first go at making a cab file. if all goes well i might do this more.
Nice I read on later and back tracked. I noticed that the link provided takes me to msdn's website with a title of Cabwiz(PPC Only) there is no download option. IS cabwiz built into the Windows Mobile 6 sdk?
Thanks in advanced again
ok im slowly getting this.... HaHa. I used command prompt and cabwiz. I took the inf file and pasted it into the folder that was dumped from the other program. I typed it in like this in command prompt.
cabwiz "d:\documents and settings\rzrgs6\desktop\windows\maroon_comm_manager.inf"
it kicked back with this error message...
Error: section [CEStrings] key"installDir" - data value must be an absolute path, or must start with a supported windows CE DirID <of the form %CEx%>
confused on this, maybe a little light shining on this might help.. Any Clues?
Heres an attachment of what I have so far...
you shouldn't have to move or copy the .inf, it should already be in the folder you dumped the CAB to.
It dumped a folder on my desktop callled windows. The comm manager.inf file was dumped on my desktop next to the yellow folder called windows. what you are saying is to do this
in command prompt, navigate to the cabwiz file. Type in cabwiz "d:\documents and settings\rzrgs6\desktop\windows" for the filename and just leave the .inf file on the desktop?
What to type exactly in command prompt is what is confusing me.
Thanks
Ok... I got frusturated with the .cab making process. I just took the pictures for the comm manager that I edited in GIMP and dropped them in my windows directory of my device.
It will keep me happy for now.
Below is my comm manager now and my theme on my phone which i created for Manila 2D
I'd like to help but it's hardfor me to describe it in english(my english is poor).I suggest that you can open it by winrar,see what it likes.And you can search it on google.
I appreciate everyones help.
I used WinCE to unpack the .cab file. It left me with a windows folder on my desktop with a bunch of .png files. I edited those from blue to the maroon fading black. The windows folder also had a .dll file a .mui file and the comm manager.exe file.
Next to the yellow windows folder I saw a .inf file which was dumped from the origional cab file. I expect this was the .xml installation file that was packaged in the origional cab.
Heres what I did. I searched and found Cabwiz and a few other cab making programs. I tried them all out with no success. I keep trying to use cabwiz as I fell it will do what I want. The only think is, I get an error when using Cabwiz which is in an earler post.
For now I gave up.... I just took the .png files that I edited in Gimp and copied them over to my windows Directory on my phone. I soft reset and the icons on my comm manager are the way that I want them to be
If someone could help me actually in the making of this file or just get me back on my feet and try again. I want to understand what it is that I am doing wrong.
Thanks
use the path to the .INF file like I said....
if you dumped the stuff to your desktop (WHY?) then your path to the inf file is:
"d:\documents and settings\rzrgs6\desktop\maroon_comm_manage r.inf"
so your command line is:
cabwiz "d:\documents and settings\rzrgs6\desktop\maroon_comm_manage r.inf"
why you stuck 'windows' in your path I don't know since that is NOT the path to the .INF file. The Windows folder was dumped along with the .INF file, but it was NOT the folder you dumped the CAB to. the Folder you dumped the CAB to is the folder you select after clicking the seventh button from the left in MSCEinf. Obviously you just selected the folder that was presented to you in the dialogue (Desktop) instead of navigating to a work folder and dumping it there.
I did NOT say to navigate anywhere after going to the command prompt (Cabwiz is in the system path). Nor did I say to move or copy anything.
You're reading alot into what I've said, and that seems to be your problem.
[GUIDE] How to Cook [WING]
How to Cook a ROM
Table of Contents
Intro (in this post)
How to Cook your First ROM (T-Mobile Wing)
How to customize your cooked ROM
How to Cook a .CAB file into your ROM
How to Cook a .CAB file into your ExtROM (So that it can be uninstalled by user later)
How to Cook a Theme into your ROM
How to Create a Shortcut/How to make a program automatically boot after setup
How to Port Individual SYS Folders (They're half of what defines WinMo 6.1 from 6.5, and on)
How to Port a ROM (So that you can have the latest and greatest version of Windows Mobile)
Porting from the Same Resolution
Porting from a Different ResolutionMy OEM Collection
My SYS Collections
My XIP Collections
Intro
Cooking. Cooking? Huh? Well, get your aprons out, because this might get messy! What you're going to be cooking up isn't going to be nearly as tasty as Pizza Hut's Oven Baked Tuscani Pastas (my fav), but it will be fun to use! You are going to be "cooking" something that is called a "ROM". That is basically like an Operating System for your phone. A ROM includes these things...
The mobile Operating System: Windows Mobile. What a chef (that's you) can do is create a ROM with the latest version of Windows Mobile (right now, 6.5). Versions are sub-catagorized by "builds". The latest build of Windows Mobile 6.5 (as of 8/10/09) is build 23024. So, as a chef, you can port and cook in this to your ROM. More on that later.
The Programs: YOU get to decide what comes in your ROM. When you cook a program (CAB) into a ROM, then the program cannot be removed, but it will perform a little better, since it was cooked in. So, consider those two factors if you are cooking a ROM for a group of people, not just yourself.
The Registry/Settings/Etc: You can setup your phone so that many things are pre-configured for you! Need Exchange setup right after flashing, done! Choose what Today Screen items you want, done! YOU get to set it up how you like.
First you have to start off with a kitchen. For T-Mobile Wing/Herald users, there are some options. There is Holly's Kitchen, SuperJustKitchen, and StrippedKitchen. Holly's Kitchen is a kitchen based off of Ivan's old kitchen, which is based off of Bepe's old old kitchen. It is the "classic", non-visual style of kitchens. SuperJustKitchen is a new, "visual" kitchen, meaning that it has a GUI (a more friendly interface). SuperJustKitchen should be easier to use, but it isn't covered in this guide yet. Then there is StrippedKitchen, which is built off of Holly's Kitchen! It will give you the most amount of free RAM from Windows Mobile 6.5 without even doing anything, and the guides for cooking with Holly's Kitchen will follow for StrippedKitchen. So, take your pick, and cook! If you want to build a ROM with Holly's Kitchen, just follow the post below. If you want to use StrippedKitchen, go HERE. If you want to use SuperJustKitchen, go HERE.
To do advanced cooking, you must enable the viewing of hidden files!!!
Open a file explorer from any location (Like, go to the Start Menu -> Documents).
For Windows XP, you can probably just click on the Tools menu. For Vista and Windows 7, you have to press Alt to get to the menu first.
Go to Tools -> Folder options.... In the new Folder Options windows, go to the View tab.
Select Show hidden files, folders, and drives. Uncheck Hide extensions for known file types and uncheck Hide protected operating system files (Recommended).
Now click Apply and then OK.
How to Cook your First ROM using Holly's Kitchen (for the T-Mobile Wing)
Holly's Kitchen is based off of Ivan's kitchen, which is based off another kitchen. The Build of the default ROM that it will make is 21051, the latest WM6.1 ROM. But you don't need to know all of that. All you have to do is use it! Let's get started...
Download the kitchen HERE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Use 7zip or another program to extract the kitchen folder. Once you get it extracted, you should have a folder called HollysKitchen.
Place that folder in the root of your hard drive (should be the C:\ drive). Make sure that you don't have HollysKitchen within another folder. Your file root should now be "C:\HollysKitchen", and then the next file path should be "C:\HollysKitchen\Working_Folder".
If you are running Vista or Windows 7, then you must disable the UAC. Go to your Start menu, type in "UAC", and then press enter. In Windows 7, you have a sliding bar to the left of that window. Slide that all the way to the bottom, so that it's set to "Never notify". In Vista, you should be able to just click Disable. This step is necessary for the kitchen to work.
Now let's just build the basic ROM that's included in this kitchen. You can make modifications later.
Go to the root of your kitchen ("C:\HollysKitchen") and start the StartKitchen.bat file. This will open a white command prompt.
You now have the option of building a ROM or configuring the kitchen. Right now let's just build the ROM. Press 2 and then Enter.
The white screen should proccess some commands briefly, and then a new window will open. This is the BuildOS window, where you can select what OEM packages you want to cook into (install) on your ROM.
The default kitchen has a Comm Manager, Dummy SQM (required for some programs), Essential Tweaks (registry edits), and the HTC Task Manager (for the Today Screen). Those are all located in your kitchen's OEM folder (C:\HollysKitchen\Working_Folder\OEM). For now, we don't have to be concerned with that.
So, you should still be on that BuildOS window. Leave everything checked, and then click the green "Go" arrow on the top left. You will see a progress bar appear on the bottom right corner. Let it work. Then the progress bar will start over when it is creating the Registry. Still let it go. Once you see the progress bar disappear, and you see DONE on the bottom left corner, close out of the BuildOS window.
You should be back in the white command prompt for a second, and then a new black command prompt will pop up. Let it run, and then it will automatically close itself. You will then be back in the white command prompt window. It will continue proccessing commands. Just let it work.
Finally, it will say, "Launching Pagepool Changer...", when a new window will pop up, the Multiplatform PagePool Changer.
Click on the Select button within the PagePool Changer window.
Navigate to your kitchen's folder (C:\HollysKitchen\) and then go into the Working_Folder. Then open the BUILD folder (C:\HollysKitchen\Working_Folder\BUILD). You should find a file called "os.nb". Double click it to open it.
Now you are back in the PagePool Changer window. Time to pick your PagePool. PagePool is the memory (RAM) allocated to running Windows Mobile. You should pick 6 MB for the T-Mobile Wing (you can pick something else, but this is the best). Your settings in the window should look like this...
Once you have the PagePool setting selected, click the Change to button. Then click the Close button.
Now a new window should have appeared, the htc rom tool 1.1.4 window. Your settings should already be enabled for your phone. In the Device drop down menu, you can pick another device, but I'm not sure if it'd work, never tried it. T-Mobile Wing users: leave the settings as-is. If you want, you can change the Version text box with the name of your ROM, which will be seen when flashing (not necessary). And if the settings page isn't already filled in, then that means that you didn't disable UAC in Vista or Win7.
So, you didn't have to change anything in that window. Just click the Build! button. Now a file explorer window opens. Navigate to your kitchen's folder (C:\HollysKitchen\), open the Working_Folder folder, and then open the BUILD folder (C:\HollysKitchen\Working_Folder\BUILD). In the File name text box, pick a name for your ROM, such as "First ROM", and then click Save.
[*]A Process log window will appear. Let it work. Once it's done, it will say "DONE: All seems to be ok!", and the OK button will become active. Then it will have a 5-second countdown until it automatically closes. You can click OK yourself if you don't want to wait.
[*]Now you have built your ROM, and you are back in the htc rom tool 1.1.4 window. Just close out of the window. Now you are back in the white command prompt window.
[*]It will tell you "That's it. We're done." and then it asks you, "Would you like to Flash your ROM now?" If you are HardSPLed already and you want to flash, then respond with "y" and enter. Then connect your phone to your computer through USB. Make sure that ActiveSync is connected. (If you aren't HardSPLed, then respond with "n", then navigate to the C:\HollysKitchen\Working_Folder\Flash folder, where you will find your .NBH file, flash that as normal.)
[*]Now you are in the flashing window. Check the first box there, click Next, then check the steps list on the next page, check the box, click Next. It will load for a few seconds, and then pop up with another window. Click Update, and then click Next. It should start flashing!
[*]Once completed, your phone will re-boot, and then it will boot up into the new ROM you created! Success!
So, you just created the default ROM from Holly's Kitchen. Now that you learned how to cook a ROM, you want to make it yours! You'll find more guides below, on how to customize your ROM.
How to Cook a .CAB file into your ROM
Here's how to take a .CAB file, convert it to the OEM format, and then cook your new ROM with it.
Download Package Creator v 2.7.zip
Extract it to a location of your choice
Open the extracted folder, Package Creator v2.7
You should see this in the folder...
You can go ahead and remove the Pointui Home v 1.51a.CAB file. It is not necessary. But it is also not necessary to remove that file, since you can have mulitple .CAB files in that folder. Do what you want with it.
Take the .CAB file that you want to be cooked in your ROM, copy it, and paste it into the Package Creator v2.7 folder.
Now your Package Creator v 2.7 folder should be similar to the screenshot shown in step 4, but you should have the .CAB file that you just pasted into it there.
In the same folder (Package Creator v2.7), run the Package Creator v2.7.exe file.
You should see this screen...
Click the Open Cab file button. A new window will then pop up. Navigate to the location of your Package Creator v2.7 folder (if it's not already there), and then double click your desired .CAB file.
Wait for one second, and then a window will pop up, saying Done. Click OK.
Now go back to your Package Creator v2.7 folder, and observe that a new folder was created there. Whatever the name of it is, it is now your .OEM app folder.
You now need to remove the spaces from that folder's name. Click on the folder once (so that it's highlighted), and then click on it a second time (so that you can re-name it). You can change the name of the folder to whatever you like, but make sure that there are NO spaces left in the folder's name!!
Open your kitchen folder up.
Navigate to your OEM folder within your kitchen.
Take the folder that you created and re-named (in steps 12 and 13) and drag it into your OEM folder. Just place it in the root of your OEM folder.
Cook your ROM like normal now. Your new .CAB program will be automatically installed! If you have more questions, just ask, and I'll clarify it more.
How to Cook a .CAB file into your ExtROM (So that it can be uninstalled by user later)
The ExtROM is what you see running after you flash your ROM. That initial setup "customization" screen that you see after booting your ROM for the first time is the ExtROM. One thing you can do with it is install a .CAB file that can later be uninstalled by the user. I'll show you how...
Get the .CAB file that you want to have installed by the ExtROM. Have it in a handy folder.
Now... Download WinImage, Dutty's, and HTC Tools.zip
Unzip it to the location of your choice. Open the WinImage, Dutty's, & HTC Tools folder. You should find three files in there, winimage, duttys tool nbhtool, and Htc Rom Tool, as you can see below...
Run winimage from within that folder. Click OK to the Trial Registration screen (you have a 30 day trial, and the days only count when you use the program).
Now you should see this screen...
On that screen, go to File -> Open, and then navigate to your kitchen's folders. Now navigate to your kitchen's Build folder. Locate a file that has "ExtROM" in it's filename and make sure that the extention is a .NB file. (For users of Holly's Kitchen, the file is called WingDev_ExtROM.nb) Double click on the file, and then you should see something like this...
Double click on the __TFAT_HIDDEN_ROOT_DIR__ folder. Now you should see something like this...
Go back to the folder that you have your .CAB file in, and then drag and drop it into the window from the previous step. It will ask you, "Do you want to inject 1 files occupying XXX bytes?". Click Yes.
Now you should have your .CAB file in your ExtROM. All you have to do is write the command that executes it...
In the same window, (WinImage), drag and drop the Config.txt file from that window to your Desktop (or any other location of your choice)
Now open your Config.txt file from your Desktop (or wherever you placed it). You should see something similar to this in the notepad window...
Code:
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
LOCK:Disabled
RST: Reset
Add an empty line just before the LOCK: command. Then in that line, write in "CAB:", like shown below...
Code:
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
CAB:
LOCK:Disabled
RST: Reset
After writing that, make a space, and then copy/paste this line in..."\Extended_ROM\". It should look like this now...
Code:
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
CAB: \Extended_ROM\
LOCK:Disabled
RST: Reset
Now, write in the exact name of your .CAB file, including the ".cab" extension. It should look like that below, but with your CAB's name in place of mine.
Code:
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
CAB: \Extended_ROM\Google Maps v 3.2.cab
LOCK:Disabled
RST: Reset
Save and close that notepad (Config.txt) window. You are now done editing it!
Return to the WinImage program (you should have left it running this whole time).
In WinImage, select your Config.txt file, and press Del on your keyboard.
Now in a File Explorer, navigate to your Config.txt file that you just edited (I told you to place it on your Desktop). Drag and drop that Config.txt file into the WinImage program. It will ask you, "Do you want to inject 1 files occupying xxxxx bytes?" Click Yes.
In WinImage, right click the Config.txt file that you just placed there. Click File properties. Then check the Read-only box and click OK.
Go to File -> Save. Once it saves, (it saves quickly, so you probably don't even notice it saving), close the WinImage window.
Now cook your ROM like usual. Once you flash your ROM, "customization" will run after booting it, and your program will be installed. And if users of your ROM decide that they don't want that program installed, they can easily uninstall it like normal! That is useful for programs like Google Maps, since they are updated frequently. If you have any more questions, or need more clarification, just ask!
How to Cook a Theme into your ROM
Start with your .tsk file (That's the theme file). Rename it so that it has no spaces.
Open up your kitchen's folder. Locate the SYS folder. Then locate this folder, "Base_Lang_0409_DPI_96_RESH_240_RESV_320". That is where all the theme files are stored.
You should already have some themes in that folder. Take your .tsk theme file (from step 1) and place it in the folder from step 2. Remember, you can't have spaces in the name of the .tsk file.
Now... Download WinImage, Dutty's, and HTC Tools.zip
Unzip it to the location of your choice. Open the WinImage, Dutty's, & HTC Tools folder. You should find three files in there, winimage, duttys tool nbhtool, and Htc Rom Tool, as you can see below...
Run winimage from within that folder. Click OK to the Trial Registration screen (you have a 30 day trial, and the days only count when you use the program).
Now you should see this screen...
On that screen, go to File -> Open, and then navigate to your kitchen's folders. Now navigate to your kitchen's Build folder. Locate a file that has "ExtROM" in it's filename and make sure that the extention is a .NB file. (For users of Holly's Kitchen, the file is called WingDev_ExtROM.nb) Double click on the file, and then you should see something like this... (You will probably need to select All Files from the Files of type drop down menu)
Double click on the __TFAT_HIDDEN_ROOT_DIR__ folder. Now you should see something like this...
Drag and drop the Config.txt file from that window to your Desktop (or any other location of your choice)
Now open your Config.txt file from your Desktop (or wherever you placed it). You should see something similar to this in the notepad window...
Code:
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
LOCK:Disabled
RST: Reset
Just before the "LOCKisabled" line, create a new line, and write in, "EXEC: \Windows\cusTSK.exe", like below...
Code:
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
EXEC: \Windows\cusTSK.exe
LOCK:Disabled
Then, press space and write in "\Windows\". Now, write in the name of your theme's file, and remember to include the .tsk extention. It should look like this, with "PointUI_Theme" being replaced by your theme's file name...
Code:
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
EXEC: \Windows\cusTSK.exe \Windows\PointUI_Theme.tsk
LOCK:Disabled
Save and close that notepad (Config.txt) window. You are now done editing it!
Return to the WinImage program (you should have left it running this whole time).
In WinImage, select your Config.txt file, and press Del on your keyboard.
Now in a File Explorer, navigate to your Config.txt file that you just edited (I told you to place it on your Desktop). Drag and drop that Config.txt file into the WinImage program. It will ask you, "Do you want to inject 1 files occupying xxxxx bytes?" Click Yes.
In WinImage, right click the Config.txt file that you just placed there. Click File properties. Then check the Read-only box and click OK.
Go to File -> Save. Once it saves, (it saves quickly, so you probably don't even notice it saving), close the WinImage window.
Now cook your ROM like usual. The theme will be applied just after the ROM flashes, while the Setup is running! If you have any more questions, or need more clarification, just ask!
How to Create a Shortcut using the Extended ROM
It's fairly simple...and useful, if you want to make a program automatically boot up after your ROM customizes the phone.
Download WinImage, Dutty's, and HTC Tools.zip
Unzip it to the location of your choice. Open the WinImage, Dutty's, & HTC Tools folder. You should find three files in there, winimage, duttys tool nbhtool, and Htc Rom Tool, as you can see below...
Run winimage from within that folder. Click OK to the Trial Registration screen (you have a 30 day trial, and the days only count when you use the program).
Now you should see this screen...
On that screen, go to File -> Open, and then navigate to your kitchen's folders. Now navigate to your kitchen's Build folder. Locate a file that has "ExtROM" in it's filename and make sure that the extention is a .NB file. (For users of Holly's Kitchen, the file is called WingDev_ExtROM.nb) Double click on the file, and then you should see something like this...
Double click on the __TFAT_HIDDEN_ROOT_DIR__ folder. Now you should see something like this...
Drag and drop the Config.txt file from that window to your Desktop (or any other location of your choice)
Now open your Config.txt file from your Desktop (or wherever you placed it). You should see something similar to this in the notepad window...
Code:
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
LOCK:Disabled
RST: Reset
Now, to create the shortcut, first you must have a pre-existing shortcut .lnk file. If you're trying to automatically start a program upon boot that you cooked in, then you will most likely find the location of the .lnk file by navigating to the OEM\ folder within your kitchen. Find your program's folder, open it, and then open the initflashfiles.txt file within there. Try to find a string of code that looks similar to this...
Code:
Directory("\Windows"):-Directory("Start Menu")
Directory("[B]\Windows\Start Menu[/B]"):-File("[B]Pointui Home.lnk[/B]","\Windows\Pointui Home.lnk")
Once you find a code that looks similar to that, write down the final directory (for me, it would be \Windows\Start Menu) for later use in step 13. Also write down the link's file name (Pointui Home.lnk) for step 14, too.
Go back to the other notepad window (Config.txt). Remember that the notepad window should have something like this in it still...
Code:
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
LOCK:Disabled
RST: Reset
Just before the LOCKisabled line, create an empty line, as such...
Code:
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
LOCK:Disabled
RST: Reset
Now fill that line in with CPY1:
Code:
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
CPY1:
LOCK:Disabled
RST: Reset
Remember back in step 9 where you wrote down a folder path? Well put that folder path right after the CPY1: command, as such...
Code:
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
CPY1:\Windows\Start Menu
LOCK:Disabled
RST: Reset
From step 9, you also wrote down the file name of the shortcut (the second thing you wrote down). First place a "\" after step 13, and then copy/paste in your file name, like so...
Code:
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
CPY1:\Windows\Start Menu\Pointui Home.lnk
LOCK:Disabled
RST: Reset
Then press enter after that line to create another empty line, and fill that one in with CPY2:
Code:
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
CPY1:\Windows\Start Menu\Pointui Home.lnk
CPY2:
LOCK:Disabled
RST: Reset
Now you can decide where you want to place the shortcut. CPY1: was used to find the inital location of the file (you can move any file you'd like), and CPY2: is used to place the file where you'd like. If you want your program to automatically boot, then you would add \Windows\StartUp after the CPY2: prompt, like below...
Code:
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
CPY1:\Windows\Start Menu\Pointui Home.lnk
CPY2:\Windows\StartUp
LOCK:Disabled
RST: Reset
Now, in the line right above where you are currently at in the Notepad window, on CPY1: line, copy the last part of that line (for me, I would copy \Pointui Home.lnk) Then paste that on the end of the CPY2: line. Your code should look like this...
Code:
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
CPY1:\Windows\Start Menu\Pointui Home.lnk
CPY2:\Windows\StartUp\Pointui Home.lnk
LOCK:Disabled
RST: Reset
Save and close that notepad (Config.txt) window. You are now done editing it!
Return to the WinImage program (you should have left it running this whole time).
In WinImage, select your Config.txt file, and press Del on your keyboard.
Now in a File Explorer, navigate to your Config.txt file that you just edited (I told you to place it on your Desktop). Drag and drop that Config.txt file into the WinImage program. It will ask you, "Do you want to inject 1 files occupying xxxxx bytes?" Click Yes.
In WinImage, right click the Config.txt file that you just placed there. Click File properties. Then check the Read-only box and click OK.
Go to File -> Save. Once it saves, (it saves quickly, so you probably don't even notice it saving), close the WinImage window.
Now cook your ROM like usual. The shortcut will be automatically placed! If you have any more questions, or need more clarification, just ask!
How to Port Individual SYS Folders
How to Port Individual SYS Folders (They're half of what defines WinMo 6.1 from 6.5, and on)
SYS folders contain lots of important things. They hold most of the files that define the different versions of Windows Mobile (6.0, 6.1, 6.5). You'll find your browser files, media files, NetCF files, and more. You can take almost any folder from another ROM's SYS and port it into your ROM. For example, I will be porting the Notification Manager from a Rhodium ROM to my ROM.
Download your SYS folder that you want. I'll be using this one, HERE. That is an Audio Booster program from a Raphel ROM. Extract the folder if you haven't yet.
Once you've extracted that, you should have two folders like below. You might only have one folder, or three, or four folders, depending what component you're porting.
Now go to your kitchen's SYS folder (for users of Holly's Kitchen, that would be found in \Working_Folder\SYS). Notice the similarities of the folder in the previous step and your current SYS folder.
If you got your individual SYS folder from a ROM that has the same resolution as yours, then you can skip to step 8. If not, then you have to continue below, with manually changing the pictures.
Since your individual SYS folder is from a ROM with a different resolution, we have to change the image files within it, or else your program won't display properly.
Look inside your individual SYS folder, and find where the images are. You should find them in the folder without the "Lang_0409" name on it. But look through any folders there, just to be sure. So, you identified your image files...
Now what you'll have to do is find another SYS folder that is from a ROM with the same resolution. For example, with the Audio Booster one, lets say that I already have Audio Booster in my current kitchen's SYS folder, and that I just want to port a newer version of the Audio Booster.
Have both your individual SYS folder open, and your kitchen's SYS folder open. From your individual SYS folder, select all of the image files, and delete them. Then, from your kitchen's SYS folder, select all of it's corresponding image files, and paste them into the individual SYS folder. (the "kitchen's SYS folder" can also be another SYS folder taken from a ROM with the same resolution).
Now that you have your individual SYS folder with the correct resolution images, you can go to the root of your kitchen's SYS folder and delete the old folders from there (if your kitchen didn't have those folders yet, then ignore that step). I am deleting both the "AudioBooster_2_0_18192227_0" and the "AudioBooster_2_0_18192227_0_Lang_0409" from my kitchen's original SYS folder, since I have both of those folders in my new individual SYS folder.
From your new individual SYS folder, copy and paste those folders into your kitchen's SYS folder.
So, basically, you just replaced your old kitchen's SYS folder (for that individual app) with the new one! Quite simple. And if you had different resolutions, then you just kept the image files. Simple enough? If you need more help, just ask.
Again, taken.
Still taken--
How to Port a ROM (to get a newer build for Windows Mobile) (Same Resolution)
If you want to get the latest and greatest Windows Mobile version, then follow these steps! They should work for WM6.5, WM6.1, etc. Should work for other phones, too. This guide covers how to port a ROM that has the same resoution as your phone.
Starting Points:
Here are the most probable setups that you have...
If you have an official .NBH ROM (custom ROM might work) that is a newer version, then go to Option I
If you have the kitchen of your ROM that you want ported, then you can locate the SYS and XIP folders inside it, and go to Option II
If you only have the SYS and XIP folders, then go to Option II.
Option I
You are on Option I because you now have a .NBH ROM file. Now, you need to download NBH Tool v 1.1, and extract it to your Desktop (or elsewhere).
Run the nbhtool.exe that you just extracted. You will see dutty's nbh tool window pop up. Make sure that you are on the NBH to NB tab at the top. Then click Decompile NBH file.
You should see a file explorer now. Navigate to the location of your NBH ROM file (that you said you already had), and double click it to open it.
Now a new file explorer window pops up. Navigate to a location of your choice, where you would like to place the extracted NBH. I would create a folder on your desktop called EXTRACTED, and then select that as the location to dump the extracted files. Once you selected your folder, click OK.
Let it work.
Once it finishes, it will say, "Done! Wrote ...." Click OK.
You can now close out of dutty's nbh tool.
Navigate to the folder that you picked in step 5. I told you to extract it to your Desktop in a folder called EXTRACTED. In that folder, you will hopefully find a file called, "Windows.nb", among others. Delete any other files in that folder, except the Windows.nb file.
Now, you need to download Bepe's TOOLSET, HERE. Extract that to somewhere, like your Desktop.
Open the TOOLSET folder from your Desktop (or elsewhere). You should find three files/folders there: dump xip, imgfs tools, and packagebuilder.exe.
Open the imgfs tools folder. Then open up the folder from step 8 (I told you to call it EXTRACTED, and place it on Desktop). Set the two folders up side-by-side.
In your imgfs tools folder, you should have these files/folders: bin, Dump_200.bat, and Dump_800.bat. We will be using the Dump_800.bat file. Now switch to that EXTRACTED folder, and drag and drop the "Windows.nb" file from the EXTRACTED folder onto the Dump_800.bat file. Yes, you place it right on the file.
A command prompt (black window) will pop up. Let it work. Yes, it seems like it's not doing anything at the beginning. Just let it work! Wow, it does take a while for it to complete. But let it go! Finally! The commands stop moving, and at the bottom, it says, "Press any key to continue . . ." Press Enter.
The command prompt closes. Now, notice that in your EXTRACTED folder, there is a second file, called "Windows.nb.payload".
Return to the TOOLSET folder, go to the root of it, and then open the dump xip folder. There are two files/folders in this folder: bin and dumpxip.bat. We will be using dumpxip.bat.
From your EXTRACTED folder, drag and drop the "Windows.nb.payload" file onto the dumpxip.bat file, just like last time.
Another command prompt opens. This one goes faster. Once finished, it says, "Press any key to continue . . .". Press Enter.
Back in your EXTRACTED folder, you should find two new folders: IMGFS and XIP. Open your XIP folder.
You should have a folder that looks like an XIP folder. But first, we have to do the following steps.
Have your TOOLSET folder next to your new XIP folder from the last step. Make sure that you are in the root of your TOOLSET folder, and in the root of your XIP folder (EXTRACTED\XIP). Scroll down to the bottom of the XIP folder. Notice the .DSM files. They are the important ones. You will drag each .DSM file onto the packagebuilder.exe file from the TOOLSET folder. Drag them one-by-one, and wait till it appears that it's finished until doing the next. Once finished, your XIP folder should consist of folders only.
Your folders in the XIP will be: LangDB, MSXIPKernel, MSXIPKernelLTK, OEMXIPKernel, and WinCENLS_WWE.
Go to your kitchen's XIP folder (for user's of Holly's Kitchen, that would be found in C:\HollysKitchen\Working_Folder\ROM\XIP). Repeat the same proccess on the .DSM files, from two steps above, but with your kitchen's old XIP folder. You will then end up with the same folders in both your kitchen's old XIP, and your EXTRACTED\XIP. In your kitchen's old XIP, remove all of the folders, except the OEMXIPKernel folder. Then, go to your new EXTRACTED\XIP folder, and select all of the folders, except the OEMXIPKernel folder. Copy and paste those into your kitchen's old XIP folder.
Now, you have to remove all of the folders, so that you just have files in your kitchen's XIP folder. Go into your LangDB folder (in your kitchen's XIP), select all the files/folders, and cut them (Ctrl-X). Then go back to your kitchen's XIP root folder, and paste the files there (Ctrl-V). Do the same procedure with the MSXIPKernel, MSXIPKernelLTK, OEMXIPKernel, and WinCENLS_WWE folders. You are now done with your XIP!
Go back to your EXTRACTED folder, and then open the IMGFS folder. You should hopefully have a folder called SYS there, if it ported properly. Go to your kitchen's folders (for Holly's Kitchen, C:\HollysKitchen\Working_Folder\), and delete your SYS folder. Then copy and paste your SYS folder from EXTRACTED\IMGFS to your kitchen's folder, where your old SYS folder used to be.
Cook your ROM like normal, and you'll be running a new version of Windows Mobile!!
Option II
So, you are here because you either have a newer kitchen's files that you want ported, or you have just the SYS and XIP folders of the new ROM you want ported.
First, you need to download Bepe's TOOLSET, HERE. Extract that to somewhere, like your Desktop.
Open the TOOLSET folder from your Desktop (or elsewhere). You should find three files/folders there: dump xip, imgfs tools, and packagebuilder.exe.
Open your new XIP folder (from the kitchen or just from the folder) and keep that window open next to the TOOLSET folder.
Scroll down to the bottom of the XIP folder. Notice the .DSM files. They are the important ones. You will drag each .DSM file onto the packagebuilder.exe file from the TOOLSET folder. Yes, drag and drop the .DSM files onto the packagebuilder.exe file. Drag them one-by-one, and wait till it appears that it's finished until doing the next. Once finished, your XIP folder should consist of folders only.
Your folders in the XIP will be: LangDB, MSXIPKernel, MSXIPKernelLTK, OEMXIPKernel, and WinCENLS_WWE.
Go to your old kitchen's XIP folder (for user's of Holly's Kitchen, that would be found in C:\HollysKitchen\Working_Folder\ROM\XIP). Repeat the same proccess on the .DSM files, from two steps above, but with your kitchen's old XIP folder. You will then end up with the same folders in both your kitchen's old XIP, and your new XIP folder. In your kitchen's old XIP, remove all of the folders, except the OEMXIPKernel folder. Then, go to your new XIP folder, and select all of the folders, except the OEMXIPKernel folder. Copy and paste those into your kitchen's old XIP folder.
Now, you have to remove all of the folders, so that you just have files in your kitchen's XIP folder. Go into your LangDB folder (in your kitchen's XIP), select all the files/folders, and cut them (Ctrl-X). Then go back to your kitchen's XIP root folder, and paste the files there (Ctrl-V). Do the same procedure with the MSXIPKernel, MSXIPKernelLTK, OEMXIPKernel, and WinCENLS_WWE folders. You are now done with your XIP!
Now go to your kitchen's old SYS folder. Select all of the files/folders within it, except the .VM folder, and then delete them.
Go to your new SYS folder and select all of the files except the .VM folder. Copy them (Ctrl-C), and then paste them into your kitchen's old SYS folder (Ctrl-V).
Now you should be done porting the ROM! Go ahead and cook your ROM, and hope it works!
Dam, that was a big guide. And it's not finished!! I'll finish the other part later..give me time!!
How to Port a ROM (to get a newer build for Windows Mobile) (Different Resolution)
If you want to get the latest and greatest Windows Mobile version, then follow these steps! They should work for WM6.5, WM6.1, etc. Should work for other phones, too. This guide covers how to port a ROM that has adifferent resoution than your phone.
Starting Points:
Here are the most probable setups that you have...
If you have an official .NBH ROM (custom ROM might work) that is a newer version, then go to Option I
If you have the kitchen of your ROM that you want ported, then you can locate the SYS and XIP folders inside it, and go to Option II
If you only have the SYS and XIP folders, then go to Option II.
Option I
You are on Option I because you now have a .NBH ROM file. Now, you need to download NBH Tool v 1.1, and extract it to your Desktop (or elsewhere).
Run the nbhtool.exe that you just extracted. You will see dutty's nbh tool window pop up. Make sure that you are on the NBH to NB tab at the top. Then click Decompile NBH file.
You should see a file explorer now. Navigate to the location of your NBH ROM file (that you said you already had), and double click it to open it.
Now a new file explorer window pops up. Navigate to a location of your choice, where you would like to place the extracted NBH. I would create a folder on your desktop called EXTRACTED, and then select that as the location to dump the extracted files. Once you selected your folder, click OK.
Let it work.
Once it finishes, it will say, "Done! Wrote ...." Click OK.
You can now close out of dutty's nbh tool.
Navigate to the folder that you picked in step 5. I told you to extract it to your Desktop in a folder called EXTRACTED. In that folder, you will hopefully find a file called, "Windows.nb", among others. Delete any other files in that folder, except the Windows.nb file.
Now, you need to download Bepe's TOOLSET, HERE. Extract that to somewhere, like your Desktop.
Open the TOOLSET folder from your Desktop (or elsewhere). You should find three files/folders there: dump xip, imgfs tools, and packagebuilder.exe.
Open the imgfs tools folder. Then open up the folder from step 8 (I told you to call it EXTRACTED, and place it on Desktop). Set the two folders up side-by-side.
In your imgfs tools folder, you should have these files/folders: bin, Dump_200.bat, and Dump_800.bat. We will be using the Dump_800.bat file. Now switch to that EXTRACTED folder, and drag and drop the "Windows.nb" file from the EXTRACTED folder onto the Dump_800.bat file. Yes, you place it right on the file.
A command prompt (black window) will pop up. Let it work. Yes, it seems like it's not doing anything at the beginning. Just let it work! Wow, it does take a while for it to complete. But let it go! Finally! The commands stop moving, and at the bottom, it says, "Press any key to continue . . ." Press Enter.
The command prompt closes. Now, notice that in your EXTRACTED folder, there is a second file, called "Windows.nb.payload".
Return to the TOOLSET folder, go to the root of it, and then open the dump xip folder. There are two files/folders in this folder: bin and dumpxip.bat. We will be using dumpxip.bat.
From your EXTRACTED folder, drag and drop the "Windows.nb.payload" file onto the dumpxip.bat file, just like last time.
Another command prompt opens. This one goes faster. Once finished, it says, "Press any key to continue . . .". Press Enter.
Back in your EXTRACTED folder, you should find two new folders: IMGFS and XIP. Open your XIP folder.
You should have a folder that looks like an XIP folder. But first, we have to do the following steps.
Have your TOOLSET folder next to your new XIP folder from the last step. Make sure that you are in the root of your TOOLSET folder, and in the root of your XIP folder (EXTRACTED\XIP). Scroll down to the bottom of the XIP folder. Notice the .DSM files. They are the important ones. You will drag each .DSM file onto the packagebuilder.exe file from the TOOLSET folder. Drag them one-by-one, and wait till it appears that it's finished until doing the next. Once finished, your XIP folder should consist of folders only.
Your folders in the XIP will be: LangDB, MSXIPKernel, MSXIPKernelLTK, OEMXIPKernel, and WinCENLS_WWE.
Go to your kitchen's XIP folder (for user's of Holly's Kitchen, that would be found in C:\HollysKitchen\Working_Folder\ROM\XIP). Repeat the same proccess on the .DSM files, from two steps above, but with your kitchen's old XIP folder. You will then end up with the same folders in both your kitchen's old XIP, and your EXTRACTED\XIP. In your kitchen's old XIP, remove all of the folders, except the OEMXIPKernel folder. Then, go to your new EXTRACTED\XIP folder, and select all of the folders, except the OEMXIPKernel folder. Copy and paste those into your kitchen's old XIP folder.
Now, you have to remove all of the folders, so that you just have files in your kitchen's XIP folder. Go into your LangDB folder (in your kitchen's XIP), select all the files/folders, and cut them (Ctrl-X). Then go back to your kitchen's XIP root folder, and paste the files there (Ctrl-V). Do the same procedure with the MSXIPKernel, MSXIPKernelLTK, OEMXIPKernel, and WinCENLS_WWE folders. You are now done with your XIP!
Go back to your EXTRACTED folder, and then open the IMGFS folder. You should hopefully have a folder called SYS there, if it ported properly.
Now, that SYS folder is in a different resolution than your current phone is. You have two options: If you are porting a build that is fairly similar to your last ROM's build, then you can use your SYS's old resolution folders. The other option is, if you are porting a very different build (like from 6.1 to 6.5), then you need native resolution folders. You have to search and find them yourself. Once you have them, follow below.
Go into your kitchen's SYS folder (or your downloaded resolution folder, if you chose option 2 from the previous step). Resolution folders have the following tags on the names "..._DPI_96" or "..._DPI_96_RESH_240_RESV_320".
If you are choosing option 1 (keeping your old resolution folders), then, in your old SYS folder, delete EVERY folder, EXCEPT the resolution folders (previous step) and the .VM folder. If you chose option 2, then delete the entire contents of your kitchen's old SYS folder, except the .VM folder, and then paste your resolution folders that you downloaded into your kitchen's SYS folder.
Now, no matter which option you chose, you should have a SYS folder in your kitchen that only contains a .VM folder and resolution folders.
Return to that old EXTRACTED folder from a while ago. Open the IMGFS folder within it. Find the SYS folders there, and then select all of the folders except the resolution folders and the .VM folder. Copy the selected folders, and then paste them into your old kitchen's SYS folder.
You've just ported your SYS folder! Hopefully, all goes well. Cook and flash your ROM like normal.
CONTINUED FROM ABOVE
Option II
So, you are here because you either have a newer kitchen's files that you want ported, or you have just the SYS and XIP folders of the new ROM you want ported.
First, you need to download Bepe's TOOLSET, HERE. Extract that to somewhere, like your Desktop.
Open the TOOLSET folder from your Desktop (or elsewhere). You should find three files/folders there: dump xip, imgfs tools, and packagebuilder.exe.
Open your new XIP folder (from the kitchen or just from the folder) and keep that window open next to the TOOLSET folder.
Scroll down to the bottom of the XIP folder. Notice the .DSM files. They are the important ones. You will drag each .DSM file onto the packagebuilder.exe file from the TOOLSET folder. Yes, drag and drop the .DSM files onto the packagebuilder.exe file. Drag them one-by-one, and wait till it appears that it's finished until doing the next. Once finished, your XIP folder should consist of folders only.
Your folders in the XIP will be: LangDB, MSXIPKernel, MSXIPKernelLTK, OEMXIPKernel, and WinCENLS_WWE.
Go to your old kitchen's XIP folder (for user's of Holly's Kitchen, that would be found in C:\HollysKitchen\Working_Folder\ROM\XIP). Repeat the same proccess on the .DSM files, from two steps above, but with your kitchen's old XIP folder. You will then end up with the same folders in both your kitchen's old XIP, and your new XIP folder. In your kitchen's old XIP, remove all of the folders, except the OEMXIPKernel folder. Then, go to your new XIP folder, and select all of the folders, except the OEMXIPKernel folder. Copy and paste those into your kitchen's old XIP folder.
Now, you have to remove all of the folders, so that you just have files in your kitchen's XIP folder. Go into your LangDB folder (in your kitchen's XIP), select all the files/folders, and cut them (Ctrl-X). Then go back to your kitchen's XIP root folder, and paste the files there (Ctrl-V). Do the same procedure with the MSXIPKernel, MSXIPKernelLTK, OEMXIPKernel, and WinCENLS_WWE folders. You are now done with your XIP!
Now, that new SYS folder that you have is in a different resolution than your current phone is. You have two options: If you are porting a build that is fairly similar to your last ROM's build, then you can use your SYS's old resolution folders. The other option is, if you are porting a very different build (like from 6.1 to 6.5), then you need native resolution folders. You have to search and find them yourself. Once you have them, follow below.
Go into your kitchen's SYS folder (or your downloaded resolution folder, if you chose option 2 from the previous step). Resolution folders have the following tags on the names "..._DPI_96" or "..._DPI_96_RESH_240_RESV_320".
If you are choosing option 1 (keeping your old resolution folders), then, in your old SYS folder, delete EVERY folder, EXCEPT the resolution folders (previous step) and the .VM folder. If you chose option 2, then delete the entire contents of your kitchen's old SYS folder, except the .VM folder, and then paste your resolution folders that you downloaded into your kitchen's SYS folder.
Now, no matter which option you chose, you should have a SYS folder in your kitchen that only contains a .VM folder and resolution folders.
Return to your new SYS folder (the different resolution one). Select all of the folders except the resolution folders and the .VM folder. Copy the selected folders, and then paste them into your old kitchen's SYS folder.
You've just ported your SYS folder! Hopefully, all goes well. Cook and flash your ROM like normal.
Almost done with these taken posts
.........-------
If my ROM's work, then I guess pig's can fly.
My OEM Collection
Comm Manager (6 Button)(Blue)
File Explorer Extention
HTC Task Manager (For Today Screen)
Java and Opera Mini (Thanks to Ivan for it)
Palringo (Best IM Software)
PIMBackup
PointUI Home v 1.51a
My SYS Collections
These are already ported over to the T-Mobile Wing. If you want to use these in your kitchen for the Wing/Herald, then you just replace your old XIP with this one. No porting necessary. If you want this for another phone, then you have to port it using my instructions.
PointROM: Windows Mobile 6.1 Build 21051.
DOWNLOAD
numb3rs: Windows Mobile 6.5 Build 23016.
DOWNLOAD
My XIP Collections
These are already ported over to the T-Mobile Wing. If you want to use these in your kitchen for the Wing/Herald, then you just replace your old XIP with this one. No porting necessary. If you want this for another phone, then you have to port it using my instructions.
PointROM: Windows Mobile 6.1 Build 21051.
DOWNLOAD
numb3rs: Windows Mobile 6.5 Build 23016.
DOWNLOAD