[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
Related
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 a cab with the following extentions
_setup.xml
JETBTC~1.001
JETBTH~1.000
JetBTHFix.002
JetBTHFix.999
I added the .dsm & .rgu files
I edited the _setup.xml file to redirect the Shortcut to a different folder.
Is that all I need to do?
Will it work puting it into an OEM folder now?
Can I remake it back into a cab file? (How do I make a cab file)
Thank you
You can't open a cab with a simple unzip program (which appears what you have done). You have to use a program that can pull a cab apart. In HyperCore there is a free utility that will do this (sorry, not on my computer with a kitchen so I don't remember what its called, but its in the tools and/or panel area of HyperCore). You can use Cabwuz (demo version) to see what I mean also.
MSCEinf
Its a tool called MSCEInf.exe, Windows CE CAB Analyser. It opens up Windows Mobile .CAB files and creates the original files and installation options (registry changes, shortcut creation etc).
http://www.codeppc.com/telechargements/msceinf/msceinf.htm
Andy
Ok I got the program up and running, but not sure how to use it. There seems to be no help files.
Anyone know how to use this. Can you give me a quick run though.
All that MSCEInf.exe does is extract the original files and settings from the .CAB file. What you should do is extract the files to a folder, then if the XML button is available click it and then look at the Registry Keys and Shortcuts tabs to see what shortcuts you need to create and what settings you need to add to the .RGU file. If the XML button isn't available then click the 'RTF Document' tab, this contains all the settings but is a bit harder to cut-&-paste from.
It is probably a good idea to look at on existing OEM package to see what files are included, what the shortcuts look like and what the .RGU file looks like.
HTH
Andy
Little more help.
Ok need a little help still.
This is what I have done.
1) created a folder with in the OEM folder called JETBT
2) Opened Msceinf
3) Loaded my cab file
4) Changed "Use Folder Name" to NO
5) Pressed "Extract Cab files with original names to a folder"
6) Extracted them to the JETBT folder I credated.
Now this is where I am at.
I have the following 5 files.
_setup.xml
BT HFP Extension 1.31.inf
JetBTConfig.exe
JetBTHFx.999
JetBTHFx.dll
I know I need to create a .dsm and .rgu file
the .rgu file is where I add reg entries
I also know I need to make a inirflashfile.dat
which is where I have it move the .ink file.
First how do I make a .ink file.
Then is this all I need to do?
Does the OEM folder us the info inside _setup.xml ?
If it does can I simply edit that file. Inside I see where it makes and moves the .ink file
And where it adds the reg info.
I could simply just add the info into that file.
and then create empty .dsm and .rgu files.
So what do I need to do? Am I missing any steps.
there are other cabs I need to edit aswell.
Thanks for your help.
? Anyone? PLEASE
Read my OEM package tutorial. 95% applies to all phones and Ervius Package Creator is the greatest thing to OEM packages since sliced bread
Thank Man!
if i am trying to add programs to a directory (i.e "Tools")
i know the way to create a directory within the programs folder named "Tools" via initflashfiles.txt would be:
Directory("\Windows\Start Menu\Programs"):-Directory("Tools")
but where would i want to use it, do i put this in the first program alphabetically that is going to go in this folder.
or do i just put it in the beginning of every initflashfiles.txt of every OEM that is going in that specific directory?
xsbeats said:
if i am trying to add programs to a directory (i.e "Tools")
i know the way to create a directory within the programs folder named "Tools" via initflashfiles.txt would be:
Directory("\Windows\Start Menu\Programs"):-Directory("Tools")
but where would i want to use it, do i put this in the first program alphabetically that is going to go in this folder.
or do i just put it in the beginning of every initflashfiles.txt of every OEM that is going in that specific directory?
Click to expand...
Click to collapse
Let me let you in on an inside secret... I never code the :-Directory line in any package I create. I found out (by accident when I mistyped a directory name) that if you move a file to a Directory that doesn't exist yet, then it creates it for you. So just do the file moves to whatever directory you want and they will automagically appear for you
How to clean up my windows folder
- Remove touchflo 2d
- remove Htc Home plugin
my folder size more than 136 mb :S make my deivce so heavy :S
Dr.Mazika said:
How to clean up my windows folder
- Remove touchflo 2d
- remove Htc Home plugin
my folder size more than 136 mb :S make my deivce so heavy :S
Click to expand...
Click to collapse
install a clean rom, or customize your own. the windows directory is going to be a little large regardless, the operating system is there..
what is the normal size of windows folder
any how can i customize my room to remove and add new applications
That's basically what got this community started... just about everyone here can testify to having looked into ROM Cooking... please research before asking how to do it, because I PROMISE there's a thread or two out there about it
Clean windows folder possible ?
I'm trying to cook my own rom but when I add an EXT module, all files are in Windows directory and the app.dat file only copy them in the app directory.
So is it realy possible to have a clean windows directory, how to put files directly in app folder? must I use an OEM module with initflashfile or ???
thanks all
superraoul said:
I'm trying to cook my own rom but when I add an EXT module, all files are in Windows directory and the app.dat file only copy them in the app directory.
So is it realy possible to have a clean windows directory, how to put files directly in app folder? must I use an OEM module with initflashfile or ???
thanks all
Click to expand...
Click to collapse
All files go into \windows. The first thing you need to ask is this: do I need to copy the file into another directory, like \program files? A lot of apps work just fine if you leave all of the files in \windows. The files are going to be in \windows in one form or another, so you save space by just running the app out of \windows. You need to change shortcut paths and sometimes registry key paths to get this to work, but in my experience, it works about 95% of the time. Usually, if you've got a multi-component application (several files besides just the .exe), the .exe will search for other files it needs to run in the same directory that the .exe is located in, so you're good to go if everything is in \windows. Some apps have sub-folders, so you'll have to get that folder and its contents into \windows. The best way to do this is with a .cab file or a zip file during customization (using a mortscript for the latter). Zip files are nice, because they install really quickly and are easy to make and edit.
Anyway, if you need to get files into another directory for whatever reason, I'd say that the app.dat method is probably the worst, because if you have multiple files, then you increase the file count in \windows by that amount. Put them in a zip file or a cab file, and then you'll reduce the file count to 1 for the particular package. You will also compress the files, and save some rom storage space.
You can also look into \extendir for another method to clean up the \windows directory.
You do need to be careful with some apps if they have an .ini file or an .xml file or something similar that is basically a settings file. It's usually better if these files aren't read only, so you may need to figure a way to copy the file into the \windows directory.
Hey guys,
Well, as some of you might have known, I struggled for a very, very long time
in correctly porting the XIP (the CE OS number), and the SYS (the Build
number) for quite some time. Thankfully, I figured it out using some other
tutorials that were not for the Kaiser. After a few people have asked me how
to do it, I decided to share this knowledge with this community. Please take
note that this tutorial works on KaiserKitchen and KaiserChef, and is written
specifically for Kaiser chefs who want to learn how to do this. So, without further ado,
How to Port the SYS (Build number) of a ROM:
So, what exactly is all this SYS stuff? Well, the SYS folder in your Kitchen stores all
kinds of Applications that are standard in Windows Mobile. For example, the
Transcriber and Microsoft Office, along with Windows Media Player and Internet Explorer.
It also includes many .dll files that are necessary for the ROM to survive.
So what does it mean to port it? Porting the SYS can result in many different things:
First, if ported correctly, it changes the Build number (found in Start > System > About) of the
ROM. Also, it updates many different applications in the ROM. A bigger number suggests a newer build.
For example: if you ported the 20755 build, then the version of Pocket Internet Explorer will be
a newer version than in the 19212 build. Also, ported builds are often much, much speedier than
stock builds, for some reason that is unknown to me.
So, here is how you port a build:
First, you need the ROM you want to port the build from. For example: for the
sake of this tutorial we are going to be porting the 19965 ROM, taken from the Diamond.
So, the first thing we're going to need to do is to download that ROM, which you can do
here: http://rapidshare.com/files/131846783/RUU_Diamond_hTC_Asia_HK_WWE_1.93.831.1.exe
Second, you need to dump the ROM. Now, I know that many new chefs
(including myself) tend to panic when they hear these words, but there really is
nothing to worry about. For this tutorial, we are only interested in the SYS. I
have found that the most consistent way to do this is to use HTC ROM Image
Editor, because sometimes IMGFS tools fail when trying to port from a device
like the Opal/Jade, for example. So, download this, then run the Application, then open th
.nbh we just downloaded from the Diamond. Now select all the files, and choose
to save them in a folder named "dump" (no quote) in My Documents.
Once you have all your files in a directory, we need to organize them. The easiest
way to do this by far is to download the PackageTool, which you can do so by going
here: http://myunspace.com/?d=B4BE8DA81. Download it, and extract it to
My Documents. Now, drag your "dump" folder on top of the packagebuilder.exe file.
Wait a few seconds, then look at your dump directory. In it should be two
folders: OEM and SYS, and some .dsm files. For this tutorial, we have no use for
the OEM folder, so you can feel free to delete that. Now all that should be left is the SYS folder and the .dsm files, which you can delete too. Now, we should just have the SYS folder.
Now, let's get on to the porting, now that we already have the SYS folder.
To get started, download G'Reloc to your Kitchen folder (the one that should contain
your OEM, SYS, and ROM folders). You can download it from here: http://myunspace.com/?d=0D2CE5741
Extract the .zip file to your Kitchen, be it KaiserChef or KaiserKitchen. Now
double-click on G'Reloc.exe, and keep it open. Do not close it until instructed to
do so. Now go into your Kitchen's SYS folder and delete all the files/folders in it
except the directory named ".VM" (no quotes). Now, copy all the files from your
dumped SYS except the folder ".VM" (no quotes) to your Kitchen's SYS.
Now, go into G'Reloc and click "Doit!" until it is finished. Congratulations, you
have just succesfully ported the SYS folder of the 19965 build!
Tips/Advice:
For this specific tutorial, we ported the SYS from the Diamond, which has
VGA resolution. Therefore, to put this on our QVGA display, we will need to take
all of the files/folders that are named *.192.dll and replace them with *.96.dll
folders/files in the Kaiser's SYS. To do this, you will need to replace those files
before deleting all the files in your Kitchen's SYS
How to Port the XIP (CE OS number) of a ROM: (all credit goes to Ameet and KMFM$!)
What you'll need:
A Hex Calculator
Insert.exe (used to insert the xip_out.bin into the OS.nb.payload)
XIPPort.exe
M'Reloc.exe
Kaiser's OS.nb.payload
XIP.bin from the build you want to port
NBMerge.exe (Needed to build OS.nb)
To keep it easy, I zipped all of these tools up (you'll need to get the XIP.bin
you want to port and the shipped ROM's OS.nb.payload, I'll tell you how
later). Just download the attachment at the bottom of this post. Just
download it and unzip it to a folder on your desktop.
Getting the Necessary Files
=====================
Now, we'll need to extract the OS.nb.payload and the XIP.bin from the Kaiser
Base ROM that you are using. For instance, I am using the newest HTC
Shipped Kaiser ROM (3.34), so I put NEWKAISERROM.nbh into the Extract
folder. If you are using the Kaiser 3.29 ROM as your base, you would put
that .nbh file in the Extract folder. Once you have the .nbh in the
Extract the Payload folder, double-click on RunMe.bat. Viola, the
OS.nb.payload and XIP.bin are now in your main folder, along with a new
ROM folder that I'll explain later. Don't delete anything yet
Now, enter back into your main folder and double-click on XIPPort.exe. Then
click on (in order): dump xip.bin, write maps, make pkgs. You should
now have an OUT folder in your main folder. Double-click it and you should
see some .txt files and Files and Modules folders. Enter the Files folder and
delete the MSXIPKernel and MSXIPKernelLTK folders. Delete the same folders
in the Modules directory.
Then, go back into your main folder, rename the OUT folder to OUT_original,
and the xip.bin file to xip_original.bin. Then, place the XIP.bin file from the
build you want to port in this main folder. Once it's there, double-click on
XIPPort.exe and click (in order): dump xip.bin, make pkgs. Now you
should have: an OUT folder, an OUT_original folder, a ROM folder, xip.bin, and
xip_original.bin. Go into your OUT folder, then your Modules folder, then your
MSXIPKernel folder and delete the following directories/files:
hd.dll (folder), hd.dll.txt (file), osaxst0.dll (folder), osaxst0.dll.txt (file).
Also, if you can find bmui.nb0 in one of your
MSXIPKernel folders in your OUT directory, delete it along with
bmui.nb0.imageinfo.txt. Don't worry if you can't find
it, though, because sometimes I can't myself .
Now, copy the folders MSXIPKernel and MSXIPKernelLTK from Files and
Modules folder in your OUT folder and paste them in their corresponding
folders in the OUT_original directory. Now, go back to your main folder,
rename OUT to OUT_port, and OUT_original to OUT. Now, double-click
XIPPort.exe and click (in order): undo, realloc p.
*Ignore any errors it might give you about unknown regions!.
Then click write maps.
Fixing the Addresses
================
Now, here's the tricky part. Open your MAP.txt file in the OUT folder. Look for !!!!!!!!!. If you don't find them (very rare), just skip to the end, called "Putting it All Together". If you do, we'll have to take care of that. Here's an example of the bottom part of MAP.txt:
[e32_vbase] addresses
02000000 - 03e16000 L01e16000 NUL
03e16000 - 03e1f000 L00009000 Virtual base address of wce_rex.DLL
03e1f000 - 03e24000 L00005000 Virtual base address of MMMAP.dll
03e24000 - 03e2b000 L00007000 Virtual base address of htcfsfilter.DLL
03e2b000 - 03e4c000 L00021000 Virtual base address of FLASHDRV.DLL
03e4c000 - 03e52000 L00006000 Virtual base address of ceddk.dll
03e52000 - 03e56000 L00004000 Virtual base address of cecompr.dll
03e55000 - 03e56000 L00001000 !!!!!!!!!!!!!!!!!!
03e55000 - 03e59000 L00004000 Virtual base address of regenum.dll
03e59000 - 03e68000 L0000f000 Virtual base address of pm.dll
03e68000 - 03e70000 L00008000 Virtual base address of mspart.dll
03e70000 - 03e80000 L00010000 Virtual base address of mencfilt.dll
03e80000 - 03e8c000 L0000c000 Virtual base address of imgfs.dll
03e8c000 - 03e96000 L0000a000 Virtual base address of fsreplxfilt.dll
03e96000 - 03eac000 L00016000 Virtual base address of fsdmgr.dll
03eac000 - 03eb5000 L00009000 Virtual base address of fatutil.dll
03eb5000 - 03ec8000 L00013000 Virtual base address of fatfsd.dll
03ec8000 - 03ece000 L00006000 Virtual base address of diskcache.dll
03ece000 - 03eda000 L0000c000 Virtual base address of devmgr.dll
03eda000 - 03f4c000 L00072000 Virtual base address of crypt32.dll
03f4c000 - 03fe2000 L00096000 Virtual base address of coredll.dll
03fe2000 - 03ff0000 L0000e000 Virtual base address of certmod.dll
03ff0000 - 03ffa000 L0000a000 Virtual base address of cachefilt.dll
03ffa000 - 04000000 L00006000 Virtual base address of busenum.dll
04000000 - 80000000 L7c000000 NUL
]]
<< The trick to reading the o32 and e32 table is this:
* the first column is the modules starting address (o32_realaddr or e32_vbase).
* the second column is it's ending address (which should be the same as the realaddr/vbase for the next module).
* the third column (The one that starts with 'L') is the file's "vsize".
>>
These are the overlaps which need to be taken care of by reallocating the modules in Initialized Data and Virtual Base addresses
You need to work our way up from the bottom of the list since the busenum.dll is reallocated at the last address of the memory.
For example:
03e4c000 - 03e52000 L00006000 Virtual base address of ceddk.dll
03e52000 - 03e56000 L00004000 Virtual base address of cecompr.dll
03e55000 - 03e56000 L00001000 !!!!!!!!!!!!!!!!!!
03e55000 - 03e59000 L00004000 Virtual base address of regenum.dll
Meaning, e32_vbase address of cecompr.dll is overlapping the reserved space of regenum.dll by 1000 (L00001000).
I recommend you use M’Reloc.exe for reallocating the addresses in imageinfo.bin and Notepad to reallocate the addresses in the corresponding imageinfo.txt files.
Since the binaries (S000, S001...) must actually be relocated using M'Reloc, it is not enough to just adjust the values in the imageinfo.txt files.
To calculate the new addresses of the overlapping modules, open the hex calculator.
* You can use windows calculator for this. Open the calculator, click "view" and select "scientific". Now, press "F6" or click "HEX" to put the calculator into hexidecimal mode.
Now to correct the e32_vbase of cecompr.dll, follow this calculation as a base (e32_vbase regenum.dll - e32_vsize cecompr.dll = correct e32_vbase cecompr.dll)
Meaning, (03e55000 – 4000 = 03e51000) hence the correct e32_vbase address for cecompr.dll is 03e51000
Now since the cecompr.dll is reallocated using the above calculation, the modules next in line above that will also have to be reallocated. Namely, ceddk.dll (although not overlapping cecompr.dll yet since we have not "realloc P").
To calculate the e32_vbase of ceddk.dll you will need the new e32_vbase address of cecompr.dll which you got just now (03e51000).
I recommend writing down the e32_vbase, e32_vsize, o32_realaddr and o32_vsize of each module so it will be easier to calculate the correct addresses for reallocation).
Remember, you need to work our way up from the bottom of the list since the busenum.dll is reallocated at the last address of the memory.
To reallocate the addresses for o32_realaddr, follow the above calculation. Only this time, replace the e32_vbase with o32_realaddr and e32_vsize with o32_vsize.
Now open the corresponding imageinfo.txt file for each module and change the e32_vbase and o32_realaddr address values in the txt file of the values mentioned with V= and D=, seen for e.g. like this:
Module name: cecompr.dll
e32_vbase: V=03E52000
...
o32[1].o32_realaddr: D=01FEE000
You will notice that the 'FLASHDRV.DLL' module has the realaddr at 2 regions. Although I have not found a way to calculate the difference between both regions but I change the values as per Abusalza’s MAP.txt
o32[1].o32_realaddr: D=01FCC000
o32[3].o32_realaddr: D=01FD4000
Since the OEMXipKernel modules never change, I only correct values of the ported MSXipKernel modules
This is helpful if the MSXipKernel modules ported from donor ROMs are similar in the sizes. If not then you will need to do the calculation and correction of values
Once completed the address reallocation, open XIPPort.exe and click “realloc P” to re calculate the addresses for writing maps. It will show you errors regarding some regions, ignore those and click “write maps”.
Open the new MAP.txt and recheck for (!!!!!!!!!!!!!!!!!!). If there are no errors that means the XIP has been sucessfully ported.
Putting it All Back Together
=====================
Now open XIPPort.exe and click “build xip_out.bin” to create the resulting XIP to be inserted into the ROM .payload file (xip_out.bin).
Now, double-click RunMe.bat in the MAIN folder. Congratulations chef, your ROM folder is ready! Now just move the ROM folder and replace the one in your kitchen with it!
You rock man!! Thanks for the contribution.
Thanks, mbarvian! I had been going through other forums putting pieces together for the kaiser as well. Seems that you figured it out a little more quickly than I.
Oh that one day I will get time to do what Sambartle did in the Hermes forums and combine this allong with instructions for Kaiserchef into one handy guide for how to cook.
Thanks for giving back to the newbie cooks mate. Much appreciated.
your are the best m8 great tutorial
for G reloc the VM numbers is already for the kaiser?
thanks!!
b16b said:
your are the best m8 great tutorial
for G reloc the VM numbers is already for the kaiser?
thanks!!
Click to expand...
Click to collapse
yes, but I always just click "Doit" just to make sure
Great tutorial, many new chefs will be very happy to see this!
really nice thing m8 but it was working on hermes exatly this way i ported always full sys port but on kaiser wont boot the full SYS port if i get the new SYS from HERMES no BOOTing
Waiting for the XIP guide
anryl said:
really nice thing m8 but it was working on hermes exatly this way i ported always full sys port but on kaiser wont boot the full SYS port if i get the new SYS from HERMES no BOOTing
Waiting for the XIP guide
Click to expand...
Click to collapse
i think you need vm numbers for HERMES is deferent from kaiser
Do you know how to get your initials in the sys build number, like the pro chef's do??
mbarvian, i have tested your method but, when I input the cmd pgktool dump from dos shell i had win error. Someone have tried this method!?
indagroove said:
Do you know how to get your initials in the sys build number, like the pro chef's do??
Click to expand...
Click to collapse
if you do this correctly, the build numbers will change
@furb3t: what errors did you get?
I have understood my error. I haven't put pkgcommon.dll into the same dir of pkgtool.exe . Now cmd goes, but into dir \dump I haven't a dir \Sys but only all files (.Vm and .Rom after cmd there aren't)
Gee, not many people wanted to share their secret recipes nowadays. My utmost salute for you mb... i always appreciate that kind of spirit highly.
Now,what i need is time to cook, oh well...
furb3t said:
I have understood my error. I haven't put pkgcommon.dll into the same dir of pkgtool.exe . Now cmd goes, but into dir \dump I haven't a dir \Sys but only all files (.Vm and .Rom after cmd there aren't)
Click to expand...
Click to collapse
thank you for bringing that to my attention. I just updated the instructions with the newer, easier PackageTool
indagroove said:
Do you know how to get your initials in the sys build number, like the pro chef's do??
Click to expand...
Click to collapse
You'll need to manually edit the d0b41563-b345-4444-aa15-986e7c7fff99.dsm file in SYS\OS.
That is, if I am reading your post correctly. You want the about screen to show something similar to the following, correct?
Code:
CE OS 5.2.20755 (Build 20755.1.4.0 Groove Edition)
as opposed to the standard
Code:
CE OS 5.2.20755 (Build 20755.1.4.0)
Are you sure about that?
How do you manual edit a .dsm?
KMFM$ said:
You'll need to manually edit the d0b41563-b345-4444-aa15-986e7c7fff99.dsm file in SYS\OS.
That is, if I am reading your post correctly. You want the about screen to show something similar to the following, correct?
Code:
CE OS 5.2.20755 (Build 20755.1.4.0 Groove Edition)
as opposed to the standard
Code:
CE OS 5.2.20755 (Build 20755.1.4.0)
Click to expand...
Click to collapse
Sorry about that, Laurentius26. I meant "hex edit" opposed to "manually edit". I can see where that would cause confusion.
There is another discussion that deals more with this:
http://forum.xda-developers.com/showthread.php?t=409845&page=3
(As you probably already know, Laurentius26. )
Haha... that's exactly what I needed and didn't know yet.
Thank you!
Grtz,
Leo
Edit: and this is not to fake CE OS version because I ported whole Opal OEM.
KMFM$ said:
Sorry about that, Laurentius26. I meant "hex edit" opposed to "manually edit". I can see where that would cause confusion.
There is another discussion that deals more with this:
http://forum.xda-developers.com/showthread.php?t=409845&page=3
(As you probably already know, Laurentius26. )
Click to expand...
Click to collapse