Related
Version: 26/04/2009
Intro
Welcome; I wanted to offer a little "something" back to the XDA community in the hopes that it will benefit others and to show my appreciation to the folks that make XDA the great community that it is. Hopefully, this guide will help you work your way up the ranks to Chef … let’s begin!
There are many chefs that provide quality ROM's for you to use. However, if you've gotten excited about the idea of cooking your own ROM's, you've probably felt overwhelmed by the volume of Forum Threads and Wiki pages at your disposal to learn how to do this.
The sections are intended to be followed in sequence as the last section should provide you with a final product that can be flashed to your device – so you may want to read this guide once over before going through the motions … who am I kidding? You’re going to follow along aren’t you?
In case you're wondering ... I chose Sous-Chef because Commis or Chef De Partie just didn't have the same appeal
Applying Original/Cooked ROM's
You probably won't be able to apply an Original or Cooked ROM to your device as your Cellular Carrier has most certainly locked your device. You'll need to unlock your device before venturing into the world of ROM installation. These activities are beyond the scope of this guide; you can however, go to this Wiki page to learn more.
HTC Raphael
http://wiki.xda-developers.com/index.php?pagename=HTC_Raphael
Original VS Cooked ROM's
HTC periodically releases Official Generic ROM's that you can apply to your device. You can find a list of Original Shipped WM6.1 ROM's at this Wiki page.
Original Shipped WM6.1 ROMS
http://wiki.xda-developers.com/index.php?pagename=HTC_Raphael_WM6.1_ROMs
There are essentially two types of Cooked ROM's; those that another Chef makes available for you to use, and those that you cook yourself. You can find a list of Available Cooked WM6.1 ROM's at this Wiki page.
Available Cooked WM6.1 ROMS
http://wiki.xda-developers.com/index.php?pagename=HTC_Raphael_Cooked_WM6.1_ROMs
Outro
Lastly, this guide only covers the ROM cooking process; changing your device Startup Splash Screen and Radio or flashing a HardSPL are beyond the scope of this guide; you can however, go to these Wiki and/or Forum pages to learn more.
Radio
http://wiki.xda-developers.com/index.php?pagename=Raphael_ExtractedRadioRoms
http://forum.xda-developers.com/showthread.php?t=439566
Startup Splash Screen
http://forum.xda-developers.com/showthread.php?t=431161
Hard SPL
http://wiki.xda-developers.com/index.php?pagename=Raphael_HardSPL
This guide is intended to help you learn how to cook your own ROM's; it will walk you through the process of extracting the contents of an Official ROM, adjusting the Page Pool, changing the Data Cache Size, and Patching the ROM to remove Certificate verification. The guide does not cover the steps required to add/remove ROM packages or port an XIP from a different ROM version or device ... not yet anyway
Now for the disclaimer bit; I take no responsibility and will not be held liable for any problems you encounter with your device before and after following this guide … flashing a ROM is done at your own risk. If you spot mistakes or inaccuracies in the guide however, please let me know so that I may correct them. Now, read on if you still feel that this is your choice career path
Oh, one last thing ... to the following folks for sharing their knowledge with the rest of us ... thank you!
Da_G
Ameet
Bepe
Cmonex
Ervius
JCEspi2005
JugglerLKR
mskip
Olipro
Aruppenthal
NRGZ28
Noonski
If I missed someone, it's purely accidental – send me a note and I will add your name to the list.
[TUT] Sous-Chef's Guide to Da_G's Simple Kitchen 5.3 ... continued
Location, Location, Location
There are many fine Kitchens out there to use; Visual Kitchens (Ervius), Automated Kitchens (Bepe), and Semi-Automated Kitchens (Raphael, Da_G). This guide uses Da_G's Simple Kitchen to assist you in learning the basics of operating a Kitchen; which ultimately, allows you to produce your own ROM.
References
Da_G....: http://forum.xda-developers.com/showthread.php?t=471288
Raphael.: http://forum.xda-developers.com/showthread.php?p=2453788
Bepe....: http://forum.xda-developers.com/showthread.php?t=467488
Ervius..: http://forum.xda-developers.com/showthread.php?t=469420
Preparing Your Facility
Before you can begin to cook your own ROM, you need to equip your facility with some Kitchen utensils. Your Kitchen is going to require a good Unicode & UTF-8 text editor; I personally use ConTEXT & Notepad. Another handy utensil to have is a comparison utility for date/file/binary comparisons; I use WinDiff & BeyondCompare. Some other utensils that you're going to require are: Microsoft ActiveSync, .NET Framework 2.x/3.x. You will also need an archive extraction utensil; I use IZArc, WinRAR, and WinZIP. You’ll also need a good Hexadecimal calculator; I use Windows Calculator (Scientific Mode).
It's also a good idea to ensure that your Kitchen remains "pest" free; common pest control services include AVG, McAfee, and Symantec anti-Virus. You'll need to add the CustomRUU Updater tool to your list of anti-virus exclusions as it will be detected as a "Generic Dropper (Trojan)".
References
CustomRUU for Raphael
http://forum.xda-developers.com/showthread.php?t=410761
To assist you in your apprenticeship, I have included a link to the Generic Simple Kitchen that I used to prepare this guide - the kitchen also includes a .DOC and .PDF format of this guide. The procedures were tested against a GSM Raphael device. I can’t confirm that these procedures will work on CDMA device ROM’s. Additionally, other device ROM’s may not be compatible with this kitchen format. Make sure to review the _README.TXT before you begin.
Generic Simple Kitchen, 17 MB
You’re going to need a RUU_SIGNED.NBH file; I used the following HTC Official Generic ROM – you’ll need to extract the contents of the .EXE and .RAR/.ZIP using an archive utensil.
[ROM] [WWE] Raphael HTC 5.05.405.1 Radio Signed (52.58.25.3 0,1.11.25.01)
http://rapidshare.com/files/1939660...igned_Raphael_52.58.25.30_1.11.25.01_Ship.rar
http://www.megaupload.com/?d=0F50UM5K
For the purpose of this guide, I will assume that you have added the C:\XDA\ folder, sub-folder, and files to your anti-virus exclusion list – at the very least CustomRUU Updater.EXE – and that the contents of the Generic Simple Kitchen were extracted to the following folder.
C:\XDA\MY_KITCHEN
The guide is divided into the following sections:
Extracting the RUU_SIGNED.NBH Contents ... 3
Consolidating .RGU Files to BOOT.RGU ..... 4
Increasing the Data Cache ................ 5
Reducing the .PAYLOAD File ............... 6
Extracting the XIP.BIN Contents .......... 7
Unlocking the Paging Pool ................ 8
Disabling Certificate Checking ........... 9
Updating the XIP.BIN Contents ............ 10
Updating the .PAYLOAD file ............... 11
Changing the Unsigned CAB Policies ....... 12
Changing the Unsigned Themes Policies .... 13
Changing the Remote API (RAPI) Policies .. 14
Compiling the New RUU_SIGNED.NBH File .... 15
Flashing the RUU_SIGNED.NBH File ......... 16
Advanced Topic: XIP Porting .............. 17
Sous-Chef's TIPs ......................... 18
I will attempt to provide an overview, the list of tools required, and the process to follow in each section. As you become more comfortable (and familiar) with the activities, you will find that you can consolidate (or skip) certain outlined steps. Incidentally, you'll probably want to keep these web links open in case you need to lookup some of the terms or concepts in the guide.
Acronyms
http://wiki.xda-developers.com/index.php?pagename=Acronyms
Glossary
http://wiki.xda-developers.com/index.php?pagename=Glossary
Development Resources for Windows Mobile
http://forum.xda-developers.com/showthread.php?t=445396
Extracting the RUU_SIGNED.NBH Contents
Extracting the Contents
An .NBH is a signed group of modules or packages; they are typically comprised of .NB files. An .NBH can contain any combination of .NB files. An .NB file is a block of code that can be a Radio ROM, Operating System packages (XIP and IMGFS), Startup Splash Screen (or SPL).
The file we will be working with is the OS.NB file; it contains the ULDR, XIP, and IMGFS (OEM, SYS). To extract the contents of an .NBH file, we issue the following command.
NBHextract.exe RUU_signed.nbh
Upon completion, the following files will have been extracted: Unknown.nb, 01_SPL.nb, 02_MainSplash.bmp, 02_MainSplash.nb, and 03_OS.NB. For the purposes of this guide, the 03_OS.NB file is the file we will be working with; it will be renamed to OS.NB.
Splitting the OS.NB File
In any ROM, the OS.NB is padded with extra data that is split into packets for the flashing process. This ensures that incorrectly transmitted packets can be re-transmitted to a device without having to resend from the beginning. Packets are usually groups of bytes and vary between devices - a packet will typically contain of data followed by padding.
For the Raphael, the data packets are 800 bytes in size and padded with 8 bytes. For the purposes of this guide, this padded portion is not required and therefore, we strip it from the OS.NB using with the NBSPLIT tool by issuing the following command.
nbsplit -kaiser os.nb
The -kaiser option instructs the NBSPLIT tool to process 0x800 (2048 decimal) hexadecimal bytes of data and that 8 bytes of padding will follow each 800 bytes. Upon completion, the following will have been extracted: os.nb.payload, os.nb.extra. For the purposes of this guide, the os.nb.extra is not required.
At this point, we need to extract the contents of the ULDR, XIP, IMGFS (OEM, SYS) from the .PAYLOAD file as we will be changing the ULDR and XIP. Most of the .PAYLOAD file content is the IMGFS; this is the portion that makes up content of the OEM and SYS folders. Most chefs add/remove OEM packages in these folders during their cooking process - you'll eventually do the same.
Tools Required
The following tools are required for the RUU_SIGNED.NBH extraction activities.
NBHextract
NBSplit
ImgfsFromNb
ImgfsToDump
RomMaster
DumpROM
PKGTool
Procedure
The following procedure initiates the ROM Extraction (NBH, IMGFS, and XIP) activity via a script that is included in the Generic Simple Kitchen. The extraction process can take a significant amount of time to complete.
Copy the RUU_SIGNED.NBH file to the C:\XDA\My_Kitchen\BaseROM\ folder.
Navigate to the C:\XDA\My_Kitchen\Tools\ folder.
Launch RaphaelKitchen.cmd.
Select E, press ENTER.
Select A, press ENTER.
At the Done! message, allow the process to resume – do not close command prompt!
At the Now Start Cooking Your ROM! Press Any Key To Continue message, press ENTER.
Select X, press ENTER.
References
NBHextract: Extract Contents From NBH Files
http://forum.xda-developers.com/showthread.php?t=289830
[TUT] ROM For Everyone (Video Tutorial To Cook The ROM)
http://forum.xda-developers.com/showthread.php?t=413782
[REF] Cooking Class Class of 2008/09 [ONLINE]
http://forum.xda-developers.com/showthread.php?t=335631
Consolidating .RGU Files to BOOT.RGU
The boot hive contains system settings that are applied only during boot. The boot hive is read out of ROM and used to start drivers and file systems needed to reach the system hive file. Once the system hive is mounted, the boot hive is discarded. Changes made to the registry during the boot process are copied into the system hive once it is available. The boot hive in ROM remains unchanged.
The boot.hv registry hive, which contains the contents of all .RGU files in the XIP, provides the initial basic registry hive that is referenced during the loading of the kernel and any necessary drivers to mount the root file system. Once the file system is mounted the default.hv and user.hv registry hives are mounted and used. Most chefs add/remove/change entries from the BOOT.RGU file during their cooking process – you'll eventually do the same.
For the purposes of this guide, we will consolidate the contents of all .RGU files found in the Dump_XIP folder into the BOOT.RGU file. Consolidating the contents of the .RGU files found in the Dump_XIP folder to the BOOT.RGU file ensures that all necessary registry entries will be added during the ROM compilation activities.
Tools Required
The following tools are required to edit .RGU files.
Unicode Text Editor
Procedure
The following procedure will consolidate all of the .RGU files found in the Dump_XIP folder into the BOOT.RGU file.
Navigate to C:\XDA\MY_KITCHEN\Temp\Dump_XIP\ folder.
Launch a text editor and open the BOOT.RGU file.
Launch a text editor and open the next .RGU file that appears in the C:\XDA\MY_KITCHEN\Temp\Dump_XIP\ folder.
Select and copy all of the file contents.
Switch to the BOOT.RGU file and paste the content to end of this file.
Repeat steps 3 to 5 until the content of each .RGU file has been appended to the BOOT.RGU file.
Save the expanded copy of the BOOT.RGU file in the C:\XDA\MY_KITCHEN\ROM\XIP\ folder.
Tip
Make a backup copy of the BOOT.RGU file before editing; delete the backup file when done.
Observe the line formatting and spacing in the BOOT.RGU file and make certain to have an empty line as the last line of the file.
Comment lines, which usually begin with a semi-colon [;], can be omitted.
Registry removal lines usually begin with a minus [-] after the open square bracket.
References
Windows Mobile
http://msdn.microsoft.com/en-us/library/ms885472.aspx
Increasing the Data Cache
File caching improves performance and also improves power management; when an application accesses physical storage, the storage device uses much more power. The less often physical storage is accessed, the longer storage devices spend in a low-power state.
By increasing the DataCacheSize registry value, you effectively improve the performance of applications that are file system intensive such as database and mapping applications – which results in lower physical storage access requirements. Drastically increasing the DataCacheSize however, may have adverse effects and slow the device down as a result of longer auto-compaction processing.
For the purposes of this guide, we are going to increase the current DataCacheSize value from 4MB to 8MB.
Tools Required
The following tools are required to adjust the DataCacheSize value.
Unicode Text Editor
Hexadecimal Calculator
Procedure
The following procedure will change the current DataCacheSize value of 4MB to 8MB.
Navigate to the C:\XDA\MY_KITCHEN\ROM\XIP\ folder.
Launch a text editor and open the BOOT.RGU file.
Search for the following registry key entry:
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV\FATFS]
Locate the following registry value underneath the key:
"DataCacheSize"=dword:00000800 ;2048 sectors(2048*2048=4MB)
Change the registry value to the following:
"DataCacheSize"=dword:00001000 ;4096 sectors(4096*2048=8MB)
Save the BOOT.RGU file.
Exit the text editor.
Tip
Make a backup copy of the BOOT.RGU file before editing; delete the backup file when done.
Reducing the .PAYLOAD File
At this point, we need to remove the contents of the IMGFS (OEM, SYS) from the .PAYLOAD file in preparation for our changes to the ULDR and XIP. Removing the IMGFS (OEM, SYS) contents from the .PAYLOAD file will reduce the size of the .PAYLOAD file making it easier to work with.
To reduce the .PAYLOAD file, we essentially need to cook a new version of the .PAYLOAD file with an empty IMGFS partition – one which only contains the .VM and .ROM folder contents. For the purposes of this guide, we will use the Ervius Payload Reducer script to perform this process.
Tools Required
The following tools are required for the .PAYLOAD file reduction activities.
ImgfsFromNb
ImgfsFromDump
ImgfsToNb
Procedure
The following procedure initiates the .PAYLOAD file reduction activity via a script that is included in the Generic Simple Kitchen. The reduced os.nb.payload file will be required when we update the XIP.BIN file.
Copy the ReducePayload folder (and contents) from the C:\XDA\MY_KITCHEN\Tools\ folder to the C:\XDA\MY_KITCHEN\Temp\ folder.
Copy the OS.NB.PAYLOAD file from the C:\XDA\MY_KITCHEN\Temp\ folder to the C:\XDA\MY_KITCHEN\Temp\ReducePayload\ folder.
Navigate to the C:\XDA\MY_KITCHEN\Temp\ReducePayload\ folder.
Launch reduce_payload.bat.
At the OS.NB.PAYLOAD Successfully Reduced. Press Any Key To Continue ... message, press ENTER.
References
[TUT] Manual Full XIP Porting (& MANY MORE TUTORIALS)
http://forum.xda-developers.com/showthread.php?t=438676
Extracting the XIP.BIN Contents
The Execute-in-place (XIP) region is an area where an application can execute code directly from ROM rather than loading it from RAM. Before we can proceed to make changes such as unlocking the Page Pool and disabling Certificate checking, we need to extract the contents of the XIP.BIN file.
It is possible to use the XIP.BIN contents from a newer version of a ROM from a different device or a newer operating system. This is typically done by chefs who are looking for the most recent versions of system files from a specific device or version of an operating system – you'll eventually do the same.
For the purposes of this guide, we will be using the same version of the system files.
Tools Required
The following tools are required for the XIP.BIN file extraction activities.
XIPPort
Procedure
The following procedure will extract the contents of the XIP.BIN file. The extracted contents of XIP.BIN file will be required when we unlock the page pool and disable certificate checking.
1. Copy the XIPPort folder (and contents) from the C:\XDA\MY_KITCHEN\Tools\ folder to the C:\XDA\MY_KITCHEN\Temp\ folder.
2. Copy the XIP.BIN file from the C:\XDA\MY_KITCHEN\Temp\ folder to the C:\XDA\MY_KITCHEN\Temp\XIPPort\ folder.
3. Navigate to the C:\XDA\MY_KITCHEN\Temp\XIPPort\ folder.
4. Launch XIPPORT.EXE.
5. Click the Dump XIP.BIN button.
6. Exit XIPPORT.EXE.
References
[TUT] Manual Full XIP Porting (& MANY MORE TUTORIALS)
http://forum.xda-developers.com/showthread.php?t=438676
XIP Porting Guide
http://forum.xda-developers.com/showthread.php?t=379598
Unlocking the Paging Pool
The Paging Pool serves as a limit on the amount of memory that can be consumed by pageable data. It includes an algorithm for choosing the order in which to remove pageable data from memory. Pool behaviour is typically determined by the OEM – Microsoft sets a default value for the paging pool, but the OEM can change that value. Applications do not have the ability to set the behaviour for their own executables or memory-mapped files.
For the purposes of this guide, we are going to apply a change to the kernel binary file which will permit us to change the Paging Pool size (initially set to 6MB) to other sizes using the PagePool Changer tool.
Tools Required
The following tools are required for the Paging Pool unlock activities.
Hexadecimal Editor
Procedure
The following procedure will change the kernel binary file to permit adjustments to the Paging Pool size via the PagePool Changer tool.
Navigate to the C:\XDA\MY_KITCHEN\Tools\xvi32\ folder.
Launch XVI32.EXE.
Select File, Open.
Navigate to C:\XDA\MY_KITCHEN\Temp\XIPPort\OUT\MODULES\nk.exe\ folder.
Select the S000 binary file.
Select Search, Find.
In the Hex String box, type:
03 15 A0 03 02 15 A0 13
Click OK.
Change the following 4 bytes after the 03 15 A0 03 02 15 A0 13 string;
FROM: 00 10 82 E5
TO: 00 00 A0 E1
Select File, Save.
Select File, Exit.
Tip
Make a backup copy of the S000 file before editing; delete the backup file when done.
Disabling Certificate Checking
During the startup process of your device, the operating system verifies that each system file against an internal certificate store to ensure that each file is signed with a trusted certificate; if the system file is not signed, the file is ignored.
To allow execution of non-signed system files, we need to disable the internal certificate store verification. Once disabled, the operating system will trust all code installed regardless of its signature. This provides more control over the code that gets installed on the device – you no longer need to load and manually sign additional certificates such as those from the sdkcerts.cab into the device root certificate store.
For the purposes of this guide, we are going to apply a change to the kernel binary file which will disable the internal certificate store verification.
Tools Required
The following tools are required to disable the internal certificate store verification.
AutoPatcher01
Procedure
The following procedure will disable the internal certificate store verification.
Navigate to the C:\XDA\MY_KITCHEN\cmonex_AutoPatcher\ folder.
Launch AUTOPATCHER01.EXE.
Click the Cert Patch button.
Select All File (*.*) from the Files Of Type list.
Navigate to C:\XDA\MY_KITCHEN\TempXIPPort\OUT\MODULES\nk.exe\ folder.
Select the S000 binary file.
At the Successfully Patched... message, click OK.
Exit AUTOPATCHER01.EXE.
Tip
Make a backup copy of the S000 file before editing; delete the backup file when done.
References
[RES] RILPHONE.DLL And "How To" With A Radio
http://forum.xda-developers.com/showthread.php?t=481026
Kernel Overview
http://msdn.microsoft.com/en-us/library/aa909237.aspx
Updating the XIP.BIN Contents
The Execute-in-place (XIP) region is an area where an application can execute code directly from ROM rather than loading it from RAM. Now that we have unlocked the Page Pool and disabled Certificate checking, we need to assemble the extracted XIP.BIN contents back into a XIP.BIN file that includes our changes.
It is possible to use the XIP.BIN contents from a newer version of a ROM from a different device or a newer operating system. This is typically done by chefs who are looking for the most recent versions of system files from a specific device or version of an operating system – you'll eventually do the same.
For the purposes of this guide, we will be using the same version of the system files.
Tools Required
The following tools are required for the XIP_OUT.BIN file creation activities.
XIPPort
Procedure
The following procedure will compile the contents of the XIP.BIN file. To eliminate some confusion, the new .BIN file will be called XIP_OUT.BIN – the XIPPort tool creates the new .BIN file and renames it to XIP_OUT.BIN.
Navigate to the C:\XDA\MY_KITCHEN\Temp\XIPPort\ folder.
Launch XIPPORT.EXE.
Click the Build XIP_OUT.BIN button.
Exit XIPPORT.EXE.
References
[TUT] Manual Full XIP Porting (& MANY MORE TUTORIALS)
http://forum.xda-developers.com/showthread.php?t=438676
XIP Porting Guide
http://forum.xda-developers.com/showthread.php?t=379598
Updating the .PAYLOAD file
The Update Loader (ULDR) Partition
The boot loader can accommodate multiple execute-in-place (XIP) regions where individual modules can be updated after the initial operating system image file has been written to the device – the ULDR is an example of this use. The Update Loader (ULDR) provides Flash-Over-The-Air (FOTA) capabilities permitting your carrier to issue changes such as Hotfixes over the cellular network – generally, most carriers avoid this practice.
As this is generally undesirable in a cooked ROM, since we are making modifications that a carrier Hotfix might roll back, we will reduce the partition. This will cause the device to report insufficient ULDR space to the carrier FOTA request … and the freed up space becomes available for our uses. Lastly, we will remove some debugging system libraries from the XIP_OUT.BIN file – effectively providing approximately 3 MB of space.
Adjusting the ULDR and Updating the .PAYLOAD file
We will use the ROM Tools feature of the XIPPorterEx tool to adjust the ULDR, remove the debugging system library files. We will commit our changes which will replace the current XIP.BIN contents with our new XIP_OUT.BIN contents resulting in the final OS.NB.PAYLOAD file – which we will use when cooking our new ROM.
The new OS.NB.PAYLOAD file will be placed in the following folder – effectively replacing any existing OS.NB.PAYLOAD file.
.\XIPPorterEx\MyTools\os_nb.payload\
As we have already unlocked the Paging Pool and disabled Certificate checking, we will not use the Execute Cert Patcher, Execute PP Patcher, Change PP To MB features. As we will be using the same version of the system files, we do not need to port the MSXIPKernel or remove cachefilt.dll, mencfilt.dll, and encfilt.dll.
Tools Required
The following tools are required to perform the OS.NB.PAYLOAD file update activities.
XIPPorterEx
G’Reloc
ImgfsFromDump
ViewImgfs
XIPPort
Procedure
The following procedure will create a new OS.NB.PAYLOAD file which will be used when cooking our ROM.
Copy the XIPPorterEx folder (and contents) from the C:\XDA\MY_KITCHEN\Tools\ folder to the C:\XDA\MY_KITCHEN\Temp\XIPPorterEx\ folder.
Copy the .ROM folder (and contents) from the C:\XDA\MY_KITCHEN\SYS\ folder to the C:\XDA\MY_KITCHEN\Temp\XIPPorterEx\MyTools\sys\ folder.
Copy the .VM folder (and contents) from the C:\XDA\MY_KITCHEN\SYS\ folder to the C:\XDA\MY_KITCHEN\Temp\XIPPorterEx\MyTools\sys\ folder.
Copy the OS.NB.PAYLOAD file from the C:\XDA\MY_KITCHEN\Temp\ReducePayload\ folder to the C:\XDA\MY_KITCHEN\XIPPorterEx\MyTools\os_nb.payload\ folder.
Copy the XIP.BIN file from the C:\XDA\MY_KITCHEN\Temp\XIPPort\ folder to the C:\XDA\MY_KITCHEN\Temp\XIPPorterEx\MyTools\xip.bin_old\ folder.
Copy the XIP.BIN file from the C:\XDA\MY_KITCHEN\Temp\XIPPort\ folder to the C:\XDA\MY_KITCHEN\Temp\XIPPorterEx\MyTools\xip.bin_new\ folder.
Copy the XIP_OUT.BIN file from the C:\XDA\MY_KITCHEN\Temp\XIPPort\ folder to the C:\XDA\MY_KITCHEN\Temp\XIPPorterEx\MyTools\xip_new_ported\ folder.
Navigate to the C:\XDA\MY_KITCHEN\Temp\XIPPorterEx\ folder.
Launch XIPPORTEREX.EXE.
Clear the following check boxes:
Execute Cert Patcher
Execute PP Patcher
Port Only MSXipkernel
Delete CACHEFILT.DLL
Delete MENCFILT.DLL
Delete ENCFILT.DLL
Change PP To MB
Create OEM Package From Unused Xip Modules/Files
Don't Copy Xip Dsm
DEBUG Save Temp .BIN Files
Click the ROM Tools button.
Clear the following check boxes:
Conservative Mode
Write NEW Xip Size Into MBR
Select the DEBUG Delete Temp .BIN Files check box.
Click the Give From Your XIP_OUT.BIN button.
Click the Write button.
At the OS.NB.PAYLOAD Was Successfully Reduced... message, click OK.
Click the Done button.
Copy the OS.NB.PAYLOAD from C:\XDA\MY_KITCHEN\XIPPorterEx\MyTools\os.nb.payload_Reduced\ folder to the C:\XDA\MY_KITCHEN\XIPPorterEx\MyTools\os_nb.payload\ folder – overwriting the older version of the file.
Click the Find Start XIP Offset button.
Click the Write It button.
At the NEW OS.NB.PAYLOAD Was Updated Successfully... message, click OK.
Exit XIPPORTEREX.EXE.
Copy the OS.NB.PAYLOAD file from the C:\XDA\MY_KITCHEN\Temp\XIPPorterEx\MyTools\os_nb.payload\ folder to the C:\XDA\MY_KITCHEN\ROM\ folder.
Delete the OS.NB file from the C:\XDA\MY_KITCHEN\ROM\ folder.
Tip
You can change the ROM Date/Version in the Ervius PkGToolsBuildOs Kitchen 6.X-5.3 tool.
References
[TUT] Manual Full XIP Porting (& MANY MORE TUTORIALS)
http://forum.xda-developers.com/showthread.php?t=438676
Reduce ULDR Partition Size
http://forum.xda-developers.com/showpost.php?p=2916649&postcount=7
[TUT] ULDR Removal for Elf/Elfins
http://forum.xda-developers.com/showthread.php?t=446506
[Walkthrough] How to Port a ROM [XIP and SYS]
http://forum.xda-developers.com/showthread.php?t=389772
[14 NOV] M-Amine 2.0 Kitchens + Tutorials
http://forum.xda-developers.com/showthread.php?t=437898
[Full Guide Thread] TNT.Kitchen for Wizard, Auto XIP Porting and Modules Relocating
http://forum.xda-developers.com/showthread.php?t=388666
Changing the Unsigned CAB Policies
Security policies are used for configuring security settings that are then enforced with the help of security roles and certificates. They provide the flexibility to control the level of security on the device. The policies are defined globally and enforced locally in their respective components. The security policy is set during boot by executing a .provxml configuration file. This provisioning file is in ROM and contains the default setting specified by the OEM. The provisioning document is an Extensible Markup Language (XML) file that is assigns security settings to the device.
Typically, the mxipupdate_oemoperators_100.provxml file contains the default security policies that will be applied to the device. To allow execution of unsigned .CAB files, we need to change the default security policy settings that pertain to .CAB files.
For the purposes of this guide, we will add or change the following unsigned policy setting ID’s:
ID 4101: Unsigned CABS Policy = 8
ID 4102: Unsigned Applications Policy = 1
ID 4122: Unsigned Prompt Policy = 1
* IMPORTANT *
Policy settings may appear in other files. You may wish to perform a search through .TXT, .RGU, and other .PROVXML files using the keywords such as: security, policies, policy.
Tools Required
The following tools are required to edit .PROVXML files.
UTF-8 Text Editor
Procedure
The following procedure will add/change the unsigned policy settings to permit the installation of unsigned .CAB files.
Navigate to the C:\XDA\MY_KITCHEN\OEM\OperatorPkg\ folder.
Verify that the mxipupdate_oemoperators_100.provxml is not set as Read Only.
Launch your UTF-8 Text Editor.
Use the Search feature to find the following section:
<!--337.01_SecurityPolicy-->
Ensure that the following lines are present in the section:
<!--337.01_SecurityPolicy-->
<characteristic type="SecurityPolicy">
...
<parm name="4101" value="8" />
<parm name="4102" value="1" />
<parm name="4122" value="1" />
...</characteristic>
Save the changes to the mxipupdate_oemoperators_100.provxml; ensure that the file is saved in UTF-8 format.
Exit your UTF-8 Text Editor.
Verify that the mxipupdate_oemoperators_100.provxml is set to Read Only.
Tip
Make a backup copy of the mxipupdate_oemoperators_100.provxml file before editing; delete the backup file when done.
Observe the line formatting and spacing in the mxipupdate_oemoperators_100.provxml file.
When saving the file, select the Save As menu option and put quotes ["] around the file name so as to avoid additional file extensions.
References
Security Policy Settings for Windows 6.x Mobile-Based Devices
http://msdn.microsoft.com/en-us/library/bb416355.aspx
Security Policy Settings for Windows 5.x Mobile-Based Devices
http://msdn.microsoft.com/en-us/library/ms889564.aspx
What Do The SmartPhone Policy ID's Mean
http://www.xs4all.nl/~itsme/projects/xda/smartphone-policies.html
Changing the Unsigned Themes Policies
Security policies are used for configuring security settings that are then enforced with the help of security roles and certificates. They provide the flexibility to control the level of security on the device. The policies are defined globally and enforced locally in their respective components. The security policy is set during boot by executing a .provxml configuration file. This provisioning file is in ROM and contains the default setting specified by the OEM. The provisioning document is an Extensible Markup Language (XML) file that is assigns security settings to the device.
Typically, the mxipupdate_oemoperators_100.provxml file contains the default security policies that will be applied to the device. If a signed theme file does not have a matching root certificate in the Software Publisher Certificate (SPC) store, the file is unsigned and is therefore not executed. To allow execution of unsigned Theme files, we need to change the default security policy settings that pertain to Theme files.
For the purposes of this guide, we will add or change the following unsigned policy setting ID’s:
ID 4103: Unsigned CABS Policy = 16
* IMPORTANT *
Policy settings may appear in other files. You may wish to perform a search through .TXT, .RGU, and other .PROVXML files using the keywords such as: security, policies, policy.
Tools Required
The following tools are required to edit .PROVXML files.
UTF-8 Text Editor
Procedure
The following procedure will add/change the unsigned policy settings to permit the installation of unsigned .CAB files.
Navigate to the C:\XDA\MY_KITCHEN\OEM\OperatorPkg\ folder.
Verify that the mxipupdate_oemoperators_100.provxml is not set as Read Only.
Launch your UTF-8 Text Editor.
Use the Search feature to find the following section:
<!--337.01_SecurityPolicy-->
Ensure that the following lines are present in the section:
<!--337.01_SecurityPolicy-->
<characteristic type="SecurityPolicy">
...
<parm name="4103" value="16" />
...</characteristic>
Save the changes to the mxipupdate_oemoperators_100.provxml; ensure that the file is saved in UTF-8 format.
Exit your UTF-8 Text Editor.
Verify that the mxipupdate_oemoperators_100.provxml is set to Read Only.
Tip
Make a backup copy of the mxipupdate_oemoperators_100.provxml file before editing; delete the backup file when done.
Observe the line formatting and spacing in the mxipupdate_oemoperators_100.provxml file.
When saving the file, select the Save As menu option and put quotes ["] around the file name so as to avoid additional file extensions.
References
Security Policy Settings for Windows 6.x Mobile-Based Devices
http://msdn.microsoft.com/en-us/library/bb416355.aspx
Security Policy Settings for Windows 5.x Mobile-Based Devices
http://msdn.microsoft.com/en-us/library/ms889564.aspx
What Do The SmartPhone Policy ID's Mean
http://www.xs4all.nl/~itsme/projects/xda/smartphone-policies.html
Customizing the User Interface of Windows Mobile Powered Devices
http://msdn.microsoft.com/en-us/library/bb416487.aspx
Changing the Remote API (RAPI) Policies
Security policies are used for configuring security settings that are then enforced with the help of security roles and certificates. They provide the flexibility to control the level of security on the device. The policies are defined globally and enforced locally in their respective components. The security policy is set during boot by executing a .provxml configuration file. This provisioning file is in ROM and contains the default setting specified by the OEM. The provisioning document is an Extensible Markup Language (XML) file that is assigns security settings to the device.
The Remote API (RAPI) enables applications that run on a desktop to perform actions on a remote Windows Embedded CE-based device. This includes the ability to manipulate the file system on the remote device, including the creation and deletion of files and directories. Additionally, the Remote API (RAPI) functions can be used to create and modify databases, either in the device's object store or in mounted database volumes. The Remote API (RAPI) applications can also query and modify registry keys as well as launch applications and invoke methods on the remote device.
Typically, the mxipupdate_oemoperators_100.provxml file contains the default security policies that will be applied to the device. To allow unrestricted access by remote applications to implement ActiveSync operations on Windows Mobile powered devices, we need to change the default security policy settings that pertain to the Remote API (RAPI).
For the purposes of this guide, we will add or change the following unsigned policy setting ID’s:
ID 4097: Unsigned Prompt Policy = 1
* IMPORTANT *
Policy settings may appear in other files. You may wish to perform a search through .TXT, .RGU, and other .PROVXML files using the keywords such as: security, policies, policy.
Tools Required
The following tools are required to edit .PROVXML files.
UTF-8 Text Editor
Procedure
The following procedure will add/change the unsigned policy settings to permit the installation of unsigned .CAB files.
Navigate to the C:\XDA\MY_KITCHEN\OEM\OperatorPkg\ folder.
Verify that the mxipupdate_oemoperators_100.provxml is not set as Read Only.
Launch your UTF-8 Text Editor.
Use the Search feature to find the following section:
<!--337.01_SecurityPolicy-->
Ensure that the following lines are present in the section:
<!--337.01_SecurityPolicy-->
<characteristic type="SecurityPolicy">
...
<parm name="4097" value="1" />
...</characteristic>
Save the changes to the mxipupdate_oemoperators_100.provxml; ensure that the file is saved in UTF-8 format.
Exit your UTF-8 Text Editor.
Verify that the mxipupdate_oemoperators_100.provxml is set to Read Only.
Tip
Make a backup copy of the mxipupdate_oemoperators_100.provxml file before editing; delete the backup file when done.
Observe the line formatting and spacing in the mxipupdate_oemoperators_100.provxml file.
When saving the file, select the Save As menu option and put quotes ["] around the file name so as to avoid additional file extensions.
References
Security Policy Settings for Windows 6.x Mobile-Based Devices
http://msdn.microsoft.com/en-us/library/bb416355.aspx
Security Policy Settings for Windows 5.x Mobile-Based Devices
http://msdn.microsoft.com/en-us/library/ms889564.aspx
What Do The SmartPhone Policy ID's Mean
http://www.xs4all.nl/~itsme/projects/xda/smartphone-policies.html
Remote API (RAPI)
http://msdn.microsoft.com/en-us/library/aa920177.aspx
Compiling the New RUU_SIGNED.NBH File
Brief Review
At this point, we have consolidated the contents of various .RGU files found in the Dump_XIP folder to the BOOT.RGU file to ensure that all necessary registry entries will be added during the ROM compilation activities. We have increased the Data Cache size, unlocked the Paging Pool, disabled Certificate checking, reduced the ULDR, changed the Unsigned .CAB policy, changed the Theme policy, changed the Remote API (RAPI) policy, and reduced the .PAYLOAD file.
This guide did not go into details about adding, changing, or removing ROM packages to/from the OEM and SYS folders. Additionally, the guide did not cover the steps required to port an XIP from a different ROM version or device – you'll eventually want to learn how to do these types of activities.
Compiling the ROM
We now need to assemble all of these changes into a new RUU_SIGNED.NBH file – this process if often referred to as ROM compilation. We are going to use the Ervius PkgToolsBuildOS-5.3 tool to perform this process – there are newer versions of the Ervius PkgToolsBuildOS available.
Tools Required
The following tools are required for the RUU_SIGNED.NBH file creation activities.
PkgToolsBuildOS-5.3
ImgfsFromDump
NBMerge
Procedure
The following procedure initiates the ROM creation activity via a script that is included in the Generic Simple Kitchen. The creation process can take a significant amount of time to complete and requires user interaction at various stages.
Navigate to the C:\XDA\MY_KITCHEN\ folder.
Launch RaphaelKitchen.cmd.
Select C, press ENTER.
The Ervius PkgToolsBuildOs application will be launched.
Click the BuildOS tab.
Click the Load ROM button.
Select the All Packages In One check box.
In the Name box, type in the title: All Packages In One ROM
Select the Create_ROM_***.bat check box.
In the ROM Date Updater boxes, enter the desired date. Alternatively, click the Today button.
Click the Update Date button.
At the ROM Date On Flash Updated Successfully... message, click OK.
Click the Go button; allow the process to complete.
Wait for the Done message to appear in the Top Status bar.
Exit the Ervius PkgToolsBuildOs application to allow the process to continue.
The HTC ROM TOOL Process Log will appear.
Click the OK button on the Process Log window or allow it to auto exit.
At the Press Any Key To Continue... message, press ENTER.
Select X, press ENTER.
Copy the RaphaelCustomRUU.exe file from the C:\XDA\MY_KITCHEN\Tools\ folder to the C:\XDA\MY_KITCHEN\RUU\ folder.
Move the RUU_SIGNED.NBH file from the C:\XDA\MY_KITCHEN\ folder to the C:\XDA\MY_KITCHEN\RUU\ folder.
Tip
If the compilation is successful, the last three (3) lines in the Report window of the Ervius PkgToolsBuildOs application will display: Checking os-new.nb for bad NAND block marker. Checked 0x### sectors successfully! Done.
References
Ervius: Visual Multilang Kitchen For Last Bepe ROM-Tools
http://forum.xda-developers.com/showthread.php?t=469420
Flashing the RUU_SIGNED.NBH File
If you are reading this, you must have successfully compiled your RUU_SIGNED.NBH file and are now ready to flash it to your device … congratulations! Now for the disclaimer bit; I take no responsibility and will not be held liable for any problems you encounter with your device before and after following this guide … flashing a ROM is done at your own risk.
Also keep in mind that you'll need to unlock your device before venturing into the world of ROM flashing. If you haven’t unlocked your device and applied the Hard SPL, you need to complete these tasks before you can proceed.
The ROM Flashing process is relatively straight forward. You need to ensure that you can connect to your device via the ActiveSync application. Once you have connected to the device, launch the RaphaelCustomRUU tool to flash your cooked ROM to your device – I suggest temporarily disabling your anti-virus software to avoid unforeseen problems.
Tools Required
The following tools are required to flash the RUU_SIGNED.NBH file to your device.
RaphaelCustomRUU
Procedure
The following procedure initiates the ROM Flashing activity. The flashing process can take a significant amount of time to complete and requires user interaction at various stages.
Navigate to the C:\XDA\MY_KITCHEN\RUU\ folder.
Launch RaphaelCustomRUU.exe.
At the Welcome To The ROM Update Utility window, select the I Understand The Caution Indicated check box.
Click the Next button.
At the Follow The Instructions Below window, select the I Completed The Steps Indicated Above check box.
Click the Next button.
At the Current Information About Your PDA Phone window, click the Update button.
At the Verify That You Want To Update The ROM Version window, click the Next button.
At the You Are Now Ready To Update Your ROM Image window, click the Next button - allow the flashing process to complete.
Click the Finish button.
Tip
The current version of the PDA Phone ROM Update Utility 3.27.4.3 we are using has been modified to not format the device when only flashing a Radio, Startup Screen, or Operating System.
Your anti-virus will warn you that the RaphaelCustomRUU.exe contains the "Generic Dropper (Trojan)" – this is a false-positive indication; the .EXE is safe to use.
You can usually recover from a failed flash by copying a known "working" .NBH file to a MicroSD Card and starting your device in the Tricolour bootloader.
References
CustomRUU for Raphael
http://forum.xda-developers.com/showthread.php?t=410761
[Resources] Flashing your First GSM Raphael Rom (For Noobs)
http://forum.xda-developers.com/showthread.php?t=448008
Advanced Topic: XIP Porting
This guide is intended to help you learn how to port the Execute-In-Place (XIP) region from a new (donor) device for use in your kitchen; it will walk you through the process of extracting the contents of an Official ROM, obtaining the new (donor) device XIP, and porting the new (donor) device XIP into your kitchen.
[TUT] Sous-Chef's Guide to Aruppenthal’s XIP Porting Kitchen
http://forum.xda-developers.com/showthread.php?t=526804
Sous-Chef's TIPs
Tips and techniques passed down from the senior chefs in the business.
Love .PROVXML's? Hate Not Knowing If It Worked?
http://forum.xda-developers.com/showthread.php?t=519548
[WinXP Script] Extend Search Companion
http://forum.xda-developers.com/showthread.php?t=490216
[Guide] How to create .LNK files and use parameters
http://forum.xda-developers.com/showthread.php?t=490447
13/02/2010: Tutorial Statistics
Views: 8,744
Guide Downloads: 96
Kitchen Downloads: 118
Thank you very much for putting this together this will help newbs like me cook my own ROM instead of rely on others. Very great contribution.
Version: 15/06/2009
Intro
Welcome; I wanted to offer a little "something" back to the XDA community in the hopes that will benefit others and to show my appreciation to the folks that make XDA the great community that it is. Hopefully, this guide will help you work your way up the ranks to Chef … let’s begin!
So here you are; in the heat of the kitchen, adding your favourite ROM ingredients ... pinch of this, sprinkle of that. Like all good chefs, you decide to take a taste of your preparation before serving to others – so you try it ... wait! you say, something is not right; you're positive you added the ingredients but it's not right. You carefully review all of the portions; seem right; so you decide to look at the ingredients and you realize … you need to change suppliers.
This guide is intended to help you learn how to port the Execute-In-Place (XIP) region from a new (donor) device for use in your kitchen; it will walk you through the process of extracting the contents of an Official ROM, obtaining the new (donor) device XIP, and porting the new (donor) device XIP into your kitchen.
Obtaining Execute-In-Place (XIP) Files
The Execute-In-Place (XIP) region is an area where an application can execute code directly from ROM rather than loading it from RAM. It is possible to use the xip.bin contents from a newer version of a ROM from a different device or a newer operating system. This is typically done by chefs who are looking for the most recent versions of system files from a specific device or version of an operating system.
The process requires that you obtain the newer xip.bin and the corresponding .\SYS folder from the desired device .NBH package. Although it is possible to obtain a pre-extracted xip.bin and corresponding .\SYS folder, it is always preferable to perform the extraction activities yourself when possible – this ensures that you have a complete .\SYS folder and the extracted xip.bin to work with.
Outro
The sections are intended to be followed in sequence as the last section should provide you with a final product that can be used in your kitchen – so you may want to read this guide once over before going through the motions … who am I kidding? You’re going to follow along aren’t you?
The guide does not cover the steps required to inject the changes from a new .\SYS folder to your existing kitchen .\SYS folder or the comparison (verification) of the boot.rgu and supporting .RGU files typically found in the new (donor) device.
Now for the disclaimer bit; I take no responsibility and will not be held liable for any problems you encounter with your device before and after following this guide … flashing a ROM is done at your own risk. If you spot mistakes or inaccuracies in the guide however, please let me know so that I may correct them. Now, read on if you still feel it necessary to change suppliers
Oh, one last thing ... special thanks to the following folks for sharing their knowledge with the rest of us ... thank you!
Ervius
Ameet
Aruppenthal
Bepe
Cmonex
Da_G
Olipro
If I missed someone, it's purely accidental – send me a note and I will add your name to the list.
[TUT] Sous-Chef's Guide to XIP Porting in Ervius Visual Kitchen 9.7 ... continued
Preparing Your Facility
Before you can begin to port an Execute-In-Place (XIP) region, you need to equip your facility with some Kitchen utensils. Your Kitchen is going to require a good Unicode & UTF-8 text editor; I personally use ConTEXT & Notepad. Another handy utensil to have is a hexadecimal file/binary editor; I use XVI32. You will also need an archive extraction utensil; I use IZArc, WinRAR, and WinZIP. You’ll also need a good Hexadecimal calculator; I use Windows Calculator (Scientific Mode).
It's also a good idea to ensure that your Kitchen remains "pest" free; common pest control services include AVG, McAfee, and Symantec anti-Virus. You may need to temporarily disable your Anti-Virus Rootkit scanner while performing binary editing and porting activities.
The procedures were tested against a GSM Raphael device. I can’t confirm that these procedures will work on CDMA device ROM’s. Additionally, some device XIP’s may not be compatible with the Raphael device.
For the purpose of this guide, I will assume that you have added the C:\XDA\ folder, sub-folder, and files to your anti-virus exclusion list. You will additionally require the Generic Visual Kitchen from the Sous-Chef's Guide to Da_G's Ervius Visual Kitchen 9.7 tutorial (http://forum.xda-developers.com/showthread.php?t=521632) – extracted to the following folder.
C:\XDA\DONOR_NBH_VISUALKITCHEN
The guide is divided into the following sections:
Extracting the RUU_SIGNED.NBH Contents .............. 3
Reducing the .PAYLOAD File .......................... 4
Obtaining the Donor XIP.BIN Contents ................ 5
Extracting the Donor MSXIPKernel .................... 6
Confirming the Completion of the Porting Activity ... 7
Unlocking and Sizing the Paging Pool ................ 8
Disabling Certificate Checking ...................... 9
Reducing the Update Loader (ULDR) Partition ......... 10
I will attempt to provide an overview, the list of tools required, and the process to follow in each section. As you become more comfortable (and familiar) with the activities, you will find that you can consolidate (or skip) certain outlined steps. Incidentally, you'll probably want to keep these web links open in case you need to lookup some of the terms or concepts in the guide.
Acronyms
http://wiki.xda-developers.com/index.php?pagename=Acronyms
Glossary
http://wiki.xda-developers.com/index.php?pagename=Glossary
Development Resources for Windows Mobile
http://forum.xda-developers.com/showthread.php?t=445396
Extracting the RUU_SIGNED.NBH Contents
An .NBH is a signed group of modules or packages; they are typically comprised of .NB files. An .NBH can contain any combination of .NB files. An .NB file is a block of code that can be a Radio ROM, Operating System packages (XIP and IMGFS), Startup Splash Screen (or SPL).
The file we will be working with is the OS.NB file; it contains the ULDR, XIP, and IMGFS (OEM, SYS). To extract the contents of an .NBH file, we initiate the Ervius NBH/NB/PAYLOAD Dumper tool from within the Generic Visual Kitchen.
Upon completion, the following files will have been extracted: OS.nb, OS.nb.payload. Additionally, the Ervius NBH/NB/PAYLOAD Dumper tool creates a DUMP folder that contains all the files required.
Tools Required:
The following Ervius Visual Kitchen tool will be used for the RUU_SIGNED.NBH extraction activities.
Dump NBH/NB/PAYLOAD
Procedure
The following procedure initiates the ROM extraction activity via the Ervius NBH/NB/PAYLOAD Dumper tool built into the Generic Visual Kitchen. The extraction process can take a significant amount of time to complete.
Copy the RUU_SIGNED.NBH file to the C:\XDA\DONOR_NBH_VisualKitchen\BaseROM\ folder.
Navigate to the C:\XDA\DONOR_NBH_VisualKitchen\ folder.
Launch ErviusKitchen.exe.
At the multiple warning messages, click OK.
Warnings that may appear include:
Folder Not Found
Could Not Find A Part Of The Path
You Need To Specify … First
Click the Dump NBH/NB/PAYLOAD button.
Navigate to the C:\XDA\DONOR_NBH_VisualKitchen\BaseROM\ folder.
Select the RUU_signed.nbh file and then click Open.
At the All Done... Nbh/nb/payload Dumped and ''Kitchen'' created Successfull!!! message, close the Ervius Visual Kitchen application.
Navigate to the C:\XDA\DONOR_NBH_VisualKitchen\DUMP\ folder.
Move the sub-folders (and content) to the C:\XDA\DONOR_NBH_VisualKitchen\ folder.
At the Confirm Folder Replace message, click Yes To All.
At the Confirm File Move message, click Yes To All.
Tip
The C:\XDA\DONOR_NBH_VisualKitchen\BaseROM\Dump\ folder should be empty at this point – and can be removed.
References
Sous-Chef's Guide to Da_G's Ervius Visual Kitchen 9.7
http://forum.xda-developers.com/showthread.php?t=521632
Reducing the .PAYLOAD File
At this point, the Ervius NBH/NB/PAYLOAD Dumper tool has removed the contents of the IMGFS (OEM, SYS) from the .PAYLOAD file in preparation for changes to the ULDR and XIP. Removing the IMGFS (OEM, SYS) contents from the .PAYLOAD file reduces the size of the .PAYLOAD file making it easier to work with.
The Ervius NBH/NB/PAYLOAD Dumper tool has placed a copy of the reduced .PAYLOAD file in the C:\XDA\DONOR_NBH_VisualKitchen\ROM\<donordevice>\ folder.
References
Sous-Chef's Guide to Da_G's Ervius Visual Kitchen 9.7
http://forum.xda-developers.com/showthread.php?t=521632
Obtaining the Donor XIP.BIN File
Once again, the Ervius NBH/NB/PAYLOAD Dumper tool has extracted the xip.bin file from the new (donor) device os.nb.payload file. All that is left for us to do is copy the extracted xip.bin file to the current (base) kitchen in preparation for extracting the MSXIPKernel files.
Procedure
The following procedure will copy the xip.bin from the C:\XDA\DONOR_NBH_VisualKitchen\ kitchen to our current (base) kitchen.
Remove the contents in the following folders in your current (base) kitchen (ex: C:\XDA\My_Visual_Kitchen) – do not remove the folder:
.\TOOLS\xip.bin_new\*.*
.\TOOLS\xip.bin_old\*.*
.\TOOLS\XIP_new_ported\*.*
Copy the xip.bin file from the C:\XDA\DONOR_NBH_VisualKitchen\ROM\<donordevice>\ folder to the .\TOOLS\xip.bin_new\ folder of the current (base) kitchen.
References
http://msdn.microsoft.com/en-us/library/aa909237.aspx
Extracting the Donor MSXIPKernel
The Execute-In-Place (XIP) region is comprised of two significant regions – the MSXIPKernel and the OEMXIPKernel. The OEMXIPKernel typically contains system drivers that are specific to your device. On very rare occasions, these drivers can be changed for newer ones.
The MSXIPKernel however, usually contains drivers that are specific to the version of Windows Mobile that you are using – in our case, Windows Mobile 6.1. There are many different methods for porting the MSXIPKernel drivers; each method may yield different build numbers. For example, some chefs use the 723*.DSM for the build number, others use the COREDLL.DLL module to obtain the latest build numbers.
For the purpose of this guide however, we will leave the OEMXIPKernel drivers as-is and use a simpler method for porting the MSXIPKernel drivers from a new (donor) device XIP for use in your kitchen – and not concern ourselves with the build number.
Once the MSXIPKernel is extracted from the new (donor) device xip.bin, the OEMXIPKernel will be extracted from the current (base) kitchen. Both contents will be merged into a new xip.bin file.
Tools Required
The following tools are required for the new (donor) device MSXIPKernel extraction activities.
XIPPorterEx & ROM Tools
Procedure
The following procedure will extract the contents of the MSXIPKernel from the xip.bin of the new (donor) device, the OEMXIPKernel from the current (base) kitchen, and merge them into a new xip_out.bin file.
Navigate to your current (base) kitchen (ex: C:\XDA\My_Visual_Kitchen) folder.
Launch ERVIUSKITCHEN.EXE.
From the Device list, select your device – such as Raphael.
Click the XIPPorterEx & ROM Tools button.
Clear the following check boxes:
Execute Cert Patcher
Execute PP Patcher
Change PP To MB
Click the PORT IT! button.
At the Cert Patcher: Successfully Nocert Patched! message, click OK.
At the ALL DONE! \XIP Ported And Patched Folder And ROMHDR.BIN Copyed Into \ROM\Raphael\ Folder message, click OK.
Close the XIPPorterEx & ROM Tools Tool.
References
Kernel Overview
http://msdn.microsoft.com/en-us/library/aa909237.aspx
Confirming the Completion of the Porting Activity
The OEMXIPKernel folder contents will be identical to the current (base) kitchen device – for example, Raphael. The MSXIPKernel folder contents will be those of the new (donor) device. To confirm that the new (donor) device XIP was successfully ported, verify the .\ROM\ folder location in your current (base) kitchen – you should see a new set of folders that correspond to the new (donor) device.
For example;
.\ROM\Raphael\<donordevicebuildnum>\OEMXIPKernel
.\ROM\Shared\<donordevicebuildnum>\MSXIPKernel
References
Sous-Chef's Guide to Da_G's Ervius Visual Kitchen 9.7
http://forum.xda-developers.com/showthread.php?t=521632
Unlocking and Sizing the Paging Pool
The Paging Pool serves as a limit on the amount of memory that can be consumed by pageable data. It includes an algorithm for choosing the order in which to remove pageable data from memory. Pool behaviour is typically determined by the OEM – Microsoft sets a default value for the paging pool, but the OEM can change that value. Applications do not have the ability to set the behaviour for their own executables or memory-mapped files.
To change the Paging Pool size, add the –PP ## command line option to the implantxip command found in the kitchen_build_rom.bat.
Tip
Spaces are usually required between command line options; the command line option should only appear once.
Newer versions of Ervius Visual Kitchen provide an Option button to set the Paging Pool size.
Disabling Certificate Checking
During the startup process of your device, the operating system verifies that each system file against an internal certificate store to ensure that each file is signed with a trusted certificate; if the system file is not signed, the file is ignored.
To allow execution of non-signed system files, we need to disable the internal certificate store verification. Once disabled, the operating system will trust all code installed regardless of its signature. This provides more control over the code that gets installed on the device – you no longer need to load and manually sign additional certificates such as those from the sdkcerts.cab into the device root certificate store.
To disable the certificate store verification, add the -NoCERT command line option to the implantxip command found in the kitchen_build_rom.bat.
Tip
Spaces are usually required between command line options; the command line option should only appear once.
Newer versions of Ervius Visual Kitchen provide an Option button to disable the Certificate Store verification.
Reducing the Update Loader (ULDR) Partition
The boot loader can accommodate multiple execute-in-place (XIP) regions where individual modules can be updated after the initial operating system image file has been written to the device – the ULDR is an example of this use. The Update Loader (ULDR) provides Flash-Over-The-Air (FOTA) capabilities permitting your carrier to issue changes such as Hotfixes over the cellular network – generally, most carriers avoid this practice.
As this is generally undesirable in a cooked ROM, since we are making modifications that a carrier Hotfix might roll back, we will reduce the partition. This will cause the device to report insufficient ULDR space to the carrier FOTA request … and the freed up space becomes available for our uses.
To reduce the Update Loader (ULDR) Partition, add the –ULDR command line option to the implantxip command found in the kitchen_build_rom.bat.
Tip
Spaces are usually required between command line options; the command line option should only appear once.
Newer versions of Ervius Visual Kitchen provide an Option button to enable or disable ULDR reduction.
13/02/2010: Tutorial Statistics
Views: 6,284
Guide Downloads: 261
Kitchen Downloads: N/A
Very clear and succinct.
Any plans to create a guide for adding and removing new/updated packages from other ROMs or cabs using the Visual Kitchen?
rling said:
Any plans to create a guide for adding and removing new/updated packages from other ROMs ...
Click to expand...
Click to collapse
Porting packages from another ROM requires a fair amount of work; specially if the package has graphic/resources that must be resized. I'm willing to write it up if a senior (experienced) chef is willing to share their know-how.
rling said:
... or cabs using the Visual Kitchen?
Click to expand...
Click to collapse
I don't personally use any application in .CAB form, only debugging tools. Here are a few threads that cover .CAB processing and how it can be implemented by chefs in their kitchens.
ROM Chefs: SDAutoRun gives customziation to everybody!
http://forum.xda-developers.com/showthread.php?t=366333
[UC] XDA_UC, Looking for Experienced Cooks to test New XDA UC.
http://forum.xda-developers.com/showthread.php?t=525810
How do you convert packages from an existing kitchen over to the new format?
I see in the package sample that there is an app.dat, app.reg and the files folder - is there a utility to do the conversion?
Thanks
DT
d_train said:
How do you convert packages from an existing kitchen over to the new format?
I see in the package sample that there is an app.dat, app.reg and the files folder - is there a utility to do the conversion?
Thanks
DT
Click to expand...
Click to collapse
Use these tools, Readme in the file
http://xda.b4pjs.co.uk/Kitchen Convertor.zip
thanks for that
19/08/2009: Tutorial Update
Had a few requests for this now.
Added .ZIP which contains each thread post of the tutorial for folks who want to create a similar tutorial format in other device forums. All I ask is that folks not blindly copy the contents of each post file - please proof-read your final product to ensure that it applies to the device in question.
Cheers,
How about a tutorial for extracting the OEMXIPKernel from your current device, that way we know we have a working one for our particular model?
Few questions:
Do you mean dumping the OEMXIPKernel directly from the device?
Did you discover an issue with the OEMXIPKernel that is extracted from an official HTC device ROM upgrade (.NBH) file via the Ervius Visual Kitchen?
If you are referring to something entirely different, give me a few example/scenarios as I'm not certain I get what you are asking.
Cheers,
[WM Kitchen] OsKitchen Zero v1.33.5: The Easiest & Most Complete Kitchen (20/10/2010)
Index of this thread
(This Page) General Informations, Download links, Screenshots
Using OsKitchen Zero (Tutorial)
Moving from Ervius Visual Kitchen to osKitchen
Frequently Asked Questions
Useful Resources (Links where to find the latest Windows Mobile Builds and EXT packages)
Description
What does this kitchen do that others don't? You should ask yourself what the other kitchens do that this one doesn't because it literally does everything: importing the ROM directly from the EXE updater, detecting all the informations to rebuild the ROMs from the ROM file itself (no more messy BAT/CMD to edit to get things working), sorting the packages with the best EXT packages conversion engine available (no more EXT packages with weird names or out of place), building ROMs for different languages in the same pass picking all the correct windows mobile packages (EA/NonEA/AH/CS/Transcriber/Uniscribe/Fonts) to use, directly installing packages on the devices without having to flash each time (package installer), automatically recmodding of packages (without touching any of the original files) to allow cooking windows mobile 6.5 ROMs using older kernels, automatic manila CFC compression to save space and improve speed (and supporting latest manila builds where CFCGui has issues) and much, much more while keeping all the user interface well organized and being extremely easy to use. Start the kitchen, import a stock ROM and go! Give it a try and find out yourself how it lives up the hype or if still unconvinced scroll down to see how much simple yet complete the kitchen is by looking at the screenshots.
Features
The kitchen has the most streamlined and self-explanatory UI you can find, it can natively import and rebuild ROMs for all the devices in the supported list without having to mess with any batch/cmd files, it shows detailed informations about every Windows Mobile package and warn about conflicts and unmet dependencies, it can build multilanguage ROMs in the same pass by automatically choosing all the right localization packages required for each language, it can import windows mobile builds of any kind, convert OEM packages/CABS/HTC Hotfixes directly to EXT packages, can automatically recmod/UPX and natively compress/patch manila manila files with CFC, it automatically detects older kernels and suggests all the right packages to recmod to get the ROM working, it checks the ROM integrity while building to avoid many common user mistakes, has a lot of tweaks directly selectable with just a click from the kitchen interface, it has the most advanced search system available and much more.
Supported devices
HTC: Artemis, Athena, Blackstone, Diamond, Elf, Gene, HD Mini, Herald, Hermes, Iolite, Jade, Kaiser, Leo, Mega, Nike, Opal, Polaris, Pharos, Quartz, Raphael, Rhodium, Sedna, Titan, Topaz, Trinity, Vogue, Whitestone (CDMA variants of all phones are supported as well)
Palm: Treo Pro
Sony-Ericsson: Xperia X1 (HTC Kovsky)
Samsung: i900/i910 (Omnia) (delete the giisr.dll in the OEMXIPKernel folder or the ROM won't boot)
Asus: P565 (XDA Zest) (even thought not officially on the list the kitchen can import the NB0 ROM extracted from the ABI file with p835abisplit2)
Other devices, with caveats: as long as you have tools to convert between NB and your phone format the kitchen should work fine unless platformrebuilder doesn't support your device (I.E. it crashes). If platformrebuilder DOES NOT support your device you can still put a dummy NK.exe from another device to stop platformrebuilder from crashing (be sure the NK version (6.1/6.5) is the same) and insert your own crafted XIP.bin (there's a setting in Advanced Tweaks to use a custom xip file).
Download link
(First time using osKitchen? Read the brief tutorial in the 2nd post)
v1.33.5 All in one package:
http://forum.xda-developers.com/attachment.php?attachmentid=423263&stc=1&d=1287585346
DISCLAIMER: This software is provided "as is" and I don't take any responsibility for any damage caused to phones or anything else. I added all sorts of integrity checks I could think of to prevent the generation of invalid ROM files and so far none of the thousands of users who downloaded the kitchen reported invalid ROM files but just like when flashing any cooked ROM don't forget that there is always the risk that the phone may end up bricked (due to defective usb controllers, defective cables, defective phone memory, wrong radio file, software interfering with the flashing tools, power outages, etc).
System requirements
Microsoft .NET 2.0 (.NET 3.0 and 3.5 are 2.0 based so those work as well), already preinstalled on most computers, the kitchen won't start without it so it's easy to find out if it's missing
The following three system requirements also are preinstalled on most computers; the kitchen will warn you if they are needed so don't worry installing them unless required:
Microsoft Visual Studio 2008 runtime, required by xidump during the importing process
Visual Studio 2003 (7.1) Runtime Libraries, required by platformrebuilder to solve the "cereg400.dll cannot be loaded" error message, required by XIDump to solve the "Failed to init decompression!" error message and required by IMGFSFromDump to solve the "Unable to load compression DLL!" error message. Copy those libraries in the Resources\Tools folder and if that still doesn't work in the system32 subfolder of your windows folder (the right subfolder for 64bit systems is syswow64)
XmlLite Update Package required to solve the "Unable to load LibNB.dll" errors (only for Windows XP SP2)
Changelog from v1.33.4 to v1.33.5
Fixed os.nb file deletion issue for devices with no sectorinfo
Changelog from v1.33.3 to v1.33.4
Fixed delete shadow order entries not being saved
Implemented internal manifest management to reduce disk overhead during package scanning
Implemented detection of registry values that are found without a preceding registry key specifier
Improved file copy and file deleting speed
Changelog from v1.33 to v1.33.3
Fixed issue with packages with duplicate files causing errors in the package installer
Fixed issues on CAB files with "\." InstallPath attribute
Un-tied Calibration Data and Skip Welcome screen settings
Fixed IMGFS cache not being applied correctly
Fixed issues when installing packages registry files containing multi_sz strings with the package installer
Fixed new packages sorting issue
Changelog from v1.32 to v1.33
Fixed issue when using a drive root directory as temp folder
Fixed a localization manager issue that was causing longer startup times
Fixed some issues in CAB file folder mapping
Fixed the kitchen truncating i780/i900 BIN files
Added error messages when the DPI or MUI settings are missing on the phone
The kitchen now allows importing ROMs even when the language folder is missing (multilanguage Samsung ROMs)
Added a warning when the initflashfiles/app.dat files are not Unicode
The kitchen now reads app.dat as ASCII when Unicode characters are not detected
Fixed issue in which the initflashfiles.dat file was left locked for a few seconds during the import process prompting a retry/cancel file operation
Added detection and parsing of DPI_ EXT subpackages
Changelog from v1.31 to v1.32
Implemented total integrity check that checks all the structure of packages, modules and every single line of initflashfiles/registry files for issues. All the issues within the package will be shown next to the package name in the packages list.
Added support for variables in initflashfiles.dat, app.dat to make localization easier (because the variables will be replaced with the correct localized folder when the ROM is built). The list of supported variables can be found in the FAQ of the official osKitchen thread.
Added “RAM Drive Mode” setting to have additional cleanups performed during the build process to reduce the space usage of the temporary folder
Fixed crash when trying to open a search result file that has a defective associated application
Implemented total integrity system: every package, DSM, module and initflashfiles file will be validated for integrity and all the problems detected will be shown with an error/warning icon on the left of the package
When importing a ROM the initflashfile values are saved with the converted hexadecimal values like the generated app.dat files
When importing a ROM the progress bar will now warn of temporary folder cleanup even when the import has failed
Removed the unnecessary PackagePath attribute from the project files
Fixed the kitchen crashing when the resources folder was missing or the command line parameters were wrong
Renamed universal package converter to universal package importer
Fixed LCID validation not checking the LCID length correctly
Fixed the pagepool size patching message reporting unlimited instead of the real size
In-line comments are now maintained when the initflashfiles is split during the ROM import
When importing a ROM the initflashfiles lines that are not valid will now be commented out
Removed the %LCID% variable as alternative to %ROM_LCID% in the ROM filename
The ROM filename variables replacement is now case-insensitive and the value of the variables has any non-filename friendly characters removed
Remove Uniscribe/Transcriber mutual exclusion warning
Improved error handling during the NBH generation process
Fixed error message during build when packages contain more than one RGU file
Fixed some registry entries being unrecognized when tabs were used for spacing
Fixed the recmod messagebox appearing twice when the device is selected and no is chosen as answer
Fixed the windows mobile build importer not deleting the imageinfo.txt files in modules
Implemented a rudimentary “Install Package on device” function that allows installing a package on the device to avoid having to flash the phone for every changed file. Currently only sends the main package (no LCID/res subpackages), doesn’t apply registry entries and applies initflashfiles entries with no variables replacement.
Fixed the kitchen crashing when the packages contained corrupted DSM files
Fixed WinCENLS_Lang_RTL_0401 detected as having the wrong syntax
Fixed error messages saying that the packages had a wrong syntax on _CS packages
Fixed Danish appearing as “da-dk” and “Portuguese” listed as “Portugese”
Fixed the locale listview showing the LCID in the country code column
Now the locale combobox shows the locale name and country instead of just the LCID
Implemented automatic Unicode detection in initflashfiles.dat files
Fixed the file copy operations continuing even after the non-resumable error message
Fixed package validation not working in the universal package importer/windows mobile build importer
Added an “Expand all” context menu entry for search results
Added warning when wince.nls ends up in both XIP and IMGFS partitions
The packages issues are now listed by subpackage
The “Install Package on Device” function now also includes the subpackages, the settings to compile the packages are extracted from the phone itself and all registry values except multistring/binary are added
Removed missing DSM warnings
Implemented binary entries support in the “Install Package on Device” function and fixed temporary folder issues
Fixed duplicate DSM creation in package properties and reduced the wait before the packageproperties form is shown
Fixed error message when loading old kitchen project files
Added support for REG_NONE registry keys
The kitchen GUI is now shown before the project files or imported ROM informations are automatically loaded
Fixed the new DSMs file for SYS/OEM packages being saved with a Guid different from the registry key one
Added support for REG_MULTI_SZ on “Install package on device”
Fixed the kitchen leaving old combo box values when loading projects referencing non-existing devices, profiles or windows mobile builds
Search now removes unnecessary wildcard characters from the search string when wildcard mode is enabled to improve search speed
Renamed “Empty project” to “New project”
Fixed crashes in “Install package to device” with some SYS/OEM packages
Implemented integrity check support for boot_ms.rgu and boot.rgu files
Removed TGTool from the kitchen archive
Disabled F5 refresh during ROM generation
Implemented path variables support in the “Install package on device” function (note: the WM build on the phone must be present in the kitchen and have the build number as folder name for the localization to work)
Fixed issue with "Install package on device" function and short filenames and multiple initflashfiles files
Halved the time required for project loading and packages list refreshing
Implemented IMGFS support for unicode characters
Implemented CE variables support in “Install package to device” function
Added HTC Oboe to the devices list
The sort column order is now reapplied after loading a project instead of defaulting to sorting by name
Fixes some issues with empty DSM files
Fixed crash when using unicode package names
Added check to prevent boot.rgu and boot_ms.rgu from being present in non-XIPKernel packages
Fixed the locales combo box not being refreshed after a new ROM has been imported
Fixed issue in which the kitchen would save a DSM file with random name instead of overwriting the correct DSM file if the source DSM file was corrupted
Implemented case insensitive manila.exe/mode9 CFC patch
Completed translation entries list for ROM importer
Added tools error handling in UPX/Recmod/PNG Compression/xidump/nbimagetool/TGTool/o2Util/ImgfsFromDump/OsNbTool/Platformrebuilder
Fixed erroneous error handling in imgfsfromdump that was causing file copy error messages if the tool failed
Fixed reduced OS file generation ignoring imgfsfromdump error messages
Fixed TSW/MST management not checking that the output file was correctly created
Fixed the kitchen ignoring missing custom user tools error messages and continuing the build process
Initflashfiles parsing now parses files as UTF8 when the UTF16 BOM header is not detected
The registry file validation now checks if the REGEDIT4 header is present
Fixed the locales selection combobox not detecting new language changes during refresh
Fixed “Install to device” function copying square resolution packages for some resolutions
Fixed LCID EXT packages lacking the RGU file not being moved into the correct main package folder
Fixed registry validation generating errors about dwords where values have initial spacing/tabulation
Added translation entries for the module validation messages
The kitchen now reads partitions informations from the OS.NB file and calls osnbtool with the proper partition numbers (to support older ROMs without ULDR)
The kitchen can now extract BIN files from more updaters (Samsung i780 and others)
Added translation entries for OS.NB generation error management
Added translation entries for the registry validation error messages
Improved error messages (added categories) on the error tooltips
Added translation entries for the package validation error messages
Added translation entries for the initflashfiles validation error messages
Added translation entries for the manifest validation error messages
Added initflashfiles variables for Application Data (%CE19%) and Program Files\Games (%CE8%)
The initflashfiles entries of imported CAB files are now mapped to the correct initflashfiles variables
How to use
Once unpacked the kitchen is ready for use, as soon as you start it you will be asked to import data from a stock ROM.
Screenshots
{
"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"
}
Tree Structure
The new kitchen structure is very simple however it requires a ROM to be imported for device configuration files to be generated. Always import a ROM for your device and start working on it.
Output - Where generated roms are saved
Projects - Where the project files are saved
Resources - Tools and other internal kitchen files, shouldn't be touched!
Sources - Contains all the files of your Windows Mobile builds and Devices
Devices
#DEVICE NAME# (You can use the name "Common" to share packages between multiple devices)
EXT Packages - All the EXT packages must go here
OEM Packages - All the OEM packages must go here
Profiles
#Device Profile Name# - Contains the "Device Informations.XML" file and all the various packages required for building the ROM
NBH Structure - Contains files required by the kitchen to rebuild the NBH correctly
OEMXIPKernel - The OEMXIPKernel with all the device drivers and native kernel must go here
NB Structure - Contains files required by the kitchen to rebuild the Os.NB correctly
ROM Parts - .ROM, .VM, imgfs-template.bin, romhdr.bin and other files needed for relocation and XIP/IMGS generation must go here
Windows Mobile Builds
#Windows Mobile Build Number#
All - The language-neutral DPI and Resolution files must go here
Common - All the language-neutral Main Packages must go here
#LCID FOLDER# - All the localized packages must go in the appropriate LCID folder
Additional files
Visual Studio 2003 (7.1) Runtime Libraries, needed to solve the cereg400.dll cannot be loaded issue: http://www.mediafire.com/?mjmmgtwmion
ImplantXIP and ImgfsToNB tools, needed for the alternative building method: http://forum.xda-developers.com/attachment.php?attachmentid=374999&stc=1&d=1281153923
Using OsKitchen Zero
What you need to know first
The first thing you need to know is that Windows Mobile is not like a desktop operating system: you can't take a ROM from another phone and flash it on a different phone model because Windows Mobile relies on an extremely specific kernel and drivers that are compiled by the manufacturer for each device model. The Windows Mobile ROM contains only the Windows folder - yes, that's right, the ROM is just the plain Windows folder with NO subfolders - while every other folder (Windows\Start Menu, Program Files, My Documents and also Start Menu links etc.) is generated when the ROM boots the first time.
Every official Windows Mobile ROM is composed of packages. Microsoft and device makers create those packages to split windows mobile and the additional software into separated components. The real "Windows Mobile" code, interchangeable between phones, is stored in packages commonly called SYS packages, while everything the manufacturer added (the drivers and the additional applications for customization) are called the OEM packages. The EXT packages are "fake" packages that the kitchen uses to overcome the limitations of standard packages (for example EXT packages are often used to build multilanguage packages without having to create a single additional package for each language).
The Windows Mobile package structure is very simple. SYS and OEM packages are identical in structure and can only contain:
A DSM file (a file that contains some package informations, for example what other packages it require or what files it contains, most kitchens usually ignore this)
A RGU file (a registry file containing the registry entries associated with the packages)
Other files or modules that compose the package: the modules are folders that usually have file-like names (meaning they have an extension) and are a different way to store executable and DLL files on the ROM.
Note: A SYS/OEM package cannot have any subdirectory with the exception of modules directories.
EXT packages - that as already said are "fake" packages that are converted to the Windows Mobile package format by the kitchen - have a different layout: everything goes into a "files" folder except the registry files (app.reg), dsm files, initflashfiles entry files (.dat) and there can be subfolders with a LCID (language-ID) code as name (a LCID is a string composed of four HEXadecimal numbers identifying a language, e.g. 0409 for US English, 040C for Spanish, etc.) to store language-specific files in the same structure (.dsm and .reg in another "files" subfolder, like for the main folder).
EXT packages are the main way custom packages or packages from other devices are distributed on websites and forums. Recent HTC ROMs contains additional informations that allow kitchens to automatically convert OEM packages to the more user-friendly EXT packages: this allows to quickly remove applications just by disabling the package; other ROMs instead have everything stored in a single package (usually OEMMisc) and require more work to remove original applications.
The only important thing you still need to know is how the rest of the filesystem structure (Program Files, My Documents, Start Menu, etc.) is created during the first boot. All the system folders are generated and populated during the first boot because, as wrote before, the ROM contains only the Windows folder. Windows Mobile has two facilities for the first-boot (hard-reset) initialization: INITFLASHFILES.DAT, a text file that is usually in the OEM_Lang folder and that only allows creating folders and copying files (Documents folders, default pictures, and most start menu entries are usually added this way) and .PROVXML files that are some XML files that can do other advanced operations (like setting registry keys, certificates, phone settings).
Usually anything you can perform with PROVXML files, that unfortunately are difficult to edit and require a large knowledge of the format, can also be easily performed using initflashfiles and registry files. You can use the app.dat and app.reg files inside EXT packages (or initflashfiles.txt and RGU files in OEM packages) to add entries to both the initflashfiles file and to the registry: the kitchen will use them properly during the building process adding the app.dat entries to initflashfiles.txt and the reg entries to the final registry (the ROM boots with a precompiled registry HV file but you'll usually never have to mess with that when using a kitchen).
Manufacturers also use some advanced proprietary post-install tools to install custom cabs, apply themes and operator configurations (e.g. AutoRun, RunCC). Those rely on TXT configuration (*config.txt) files and can cause trouble (error messages about missing files during the first boot) when removing packages or files from packages that those config file point to if you don't update them.
When you want to upgrade a Windows Mobile Build the changes in the start menu are usually so many that it's REALLY recommended to start over with a new fresh initflashfiles.txt for that windows mobile build (you can find one for each language in the Da_G's rollup threads). Since in the official ROMs the start menu entries are all crammed into the initflashfiles.txt file (the app.dat exists only in the "fake" EXT packages) you will have to either take the time to create app.dat files for each package or to copy back all the initflashfiles entries for OEM/EXT applications back after you put the new initflashfiles for the windows mobile build you changed. The kitchen will try to move the config.txt and initflashfiles entries inside the correct packages while the ROM is imported to make SYS upgrades easier.
Now that you know the basics you can proceed to the first step...
Preparing the kitchen (Importing the Device ROM file)
1. Download osKitchen Zero and unpack the ZIP archive
2. Find a ROM update file for your device: the kitchen can import the EXE from all HTC and some Samsung updaters or alternatively the raw ROM file (the main used extensions: .NBH,.BIN and .NB are supported)
3. Open osKitchen Zero and the Import ROM Wizard will open
4. Select the device you want to work on from the drop-down list, you can actually write any device name because the list is just for reference to make sure people understand that the kitchen has been tested only with those devices
5. Select the ROM update file
6. Click NEXT
Building your first ROM to make sure everything works
At this point the main kitchen window will open. Since you imported a ROM all the "Project Settings" options will only have one choice, go on and select the only available choice for all the fields (device model, device profile, windows mobile build, language) and clicking Yes in case the kitchen asks you to automatically apply recommended changes should be enough to build a bootable and working ROM. The only setting that has more than one choice is the Compression setting that if you want to have the most available space to add your programs should be set to "LZX", if you want to use another compression first make sure that your phone will be able to flash a bigger ROM file.
Now you can go ahead and build your first ROM by clicking the "Start building button": the kitchen will work for a while, then tell you that the building process has been completed and ask you if you want to open the Output ROM folder; you can then answer yes, take the ROM file that has been generated and flash it, making sure it's the right format for your phone.
NOTE: don't try importing a ROM made for other phones different than the one you want to flash because the kitchen will rebuild the ROM for the device you imported and not any other. If you flash a ROM made for another device you risk bricking your device.
Once the ROM works (if it's a supported device it should work fine on the first try, if it doesn't please report the issue here so we can help fixing it) you can start working on the ROM. So that's it, you're ready to go. If you read the "What you need to know first" you will probably already have an idea of where to start for whatever change you want to do.
Moving from Ervius Visual Kitchen to osKitchen
Open osKitchen and import the latest ROM for your device
Replace the OEM packages
Locate the folder oskitchen created in your device (it's in the Sources folder) and delete all the packages in the "OEM Packages" folder
Open the OEM folder in the Ervius Kitchen folder, locate the folder of your device and copy&paste all the OEM packages that are inside the Common and the LCID folder (0409 for english, etc.) into a folder with any name you want inside the osKitchen "OEM Packages" folder (where you deleted them). The .VM folder can be ignored.
Replace the EXT packages
Locate the folder oskitchen created in your device (it's in the Sources folder) and delete all the packages in the "EXT Packages" folder
Open the EXT folder in the Ervius Kitchen folder, locate the folder of your device and copy&paste all the folders that are inside the Common (usually empty) and the Windows Mobile Build subfolder (it's a 5-digit number) in the osKitchen "EXT Packages" folder (where you deleted them).
Replace the OEMXIPKernel
Locate the folder oskitchen created in your device (it's in the Sources folder), go in the Profiles subfolder and then in its "default" subfolder, you'll find a folder named OEMXIPKernel, delete it.
Open the ROM folder in the Ervius Kitchen folder, locate the folder of your device, open the Windows Mobile Build subfolder (it's a 5-digit number) and then copy the OEMXIPKernel folder in the osKitchen "Profile\default" subfolder (where you deleted it).
Import the Windows Mobile Build
Locate the oskitchen Sources folder, open the "Windows Mobile Builds" subfolde and delete any folder in there.
Create a new folder with the number of the windows mobile build present in ervius kitchen (5-digit number) and create three subfolders inside: Common, All and a LCID one for each language (0409 for english, etc)
Open the ROM folder in the Ervius Kitchen folder, locate the folder named "Shared", open its Windows Mobile Build subfolder (it's a 5-digit number) and copy the MSXIPKernel folder in the osKitchen Windows Mobile Build "Common" folder you created earlier.
Open the SYS folder in the Ervius Kitchen folder, locate the Windows Mobile Build subfolder (it's a 5-digit number) and proceed as following:
Everything in the "Common" subfolders of the folders that start with DPI_ goes in the "All" folder you created in the osKitchen Windows Mobile Build folder.
Everything in the LCID (0409 for english, etc) subfolders of the folders that start with DPI_ and of the SHARED folder goes in the LCID (0409 for english, etc) folder you created in the osKitchen Windows Mobile Build folder.
Everything in the "Common" subfolder of the "SHARED" folder goes in the "Common" folder you created in the osKitchen Windows Mobile Build folder.
Frequently Asked Questions
How do I share packages between devices?
Create a folder named "Common" inside the "Sources" folder and put your packages (grouped in folders like standard device packages) in the "EXT Packages" and "OEM Packages" folders
Why is the final ROM file bigger or the total and available storage space lower than when using another kitchen?
It shouldn't. The other kitchens probably come with LZX compression selected as default while instead you told osKitchen to use XPR or None compression. You can also save additional space by using the ImplantXIP building method that removes the ULDR and some other wasted space.
How do I speed up the ROM generation process?
The kitchen needs to copy a lot of data and this may be a problem on computers where the hard-drive performance is low (i.e. laptops); antiviruses, firewalls and other applications may also interfere with the process speed therefore it's suggested to keep them off while the building process to save time. The kitchen allows setting another drive as a temporary folder to speed up the ROM generation and you can use a RAM drive (if you have enough RAM) or another hard-drive to improve the process speed.
How do I translate the kitchen?
When you start the kitchen for the first time if a translation file isn't found it will be created in "Resources\Localization" with the name matching your locale code (en-US.lng for american english, fr-FR.lng for french, it-IT.lng for italian, etc.): open that file with a text editor and translate all the text that comes after the "|||" separator (the text on the left of the separator shouldn't be touched, it's used both for reference and to identify the lines by the kitchen). Remember to post on this thread the translated files if you want them included in the official releases.
How do I reduce the space used by "Temporary OS.nb"?
It's suggested not to because the file will be needed in the next kitchen versions with the internal libnb NB dumping engine that will analyze the file, generate a new OS Structure.xml and delete it for good. The kitchen creates its own reduced files and keeps them in the Cache folder: if you really want to reduce the space used by the kitchen you can take the reduced file and replace the Temporary OS.nb with it.
How do I upgrade from an older kitchen version?
Simply delete oskitchen.exe and the Resources folder from your previous kitchen folder and put the new ones included in the archive or just unpack the archive overwriting the files. If you were using a version previous to 1.26 you will have to reimport a ROM and replace the imported packages with old ones (SYS/OEM/EXT/OEMXIPKernel (with nk.exe added inside) and remember to look at how the packages are structured). If you upgrade from 1.30 or below to 1.31 you may have to move your OEM Packages in a group subfolder because now the OEM packages are grouped like the EXT packages.
What are the variables that are supported in app.dat/initflashfiles.dat? (works only with 1.32 and higher)
%SystemDrive% (/)
%MyDocuments% (/My Documents)
%MyDocuments-MyMusic% (/My Documents/My Music)
%MyDocuments-MyPictures% (/My Documents/My Pictures)
%MyDocuments-MyVideos% (/My Documents/My Videos)
%MyDocuments-Templates% (/My Documents/Templates)
%ProgramFiles% (/Program Files)
%Windows% (/Windows)
%Windows-Fonts% (/Windows/Fonts)
%Windows-StartUp% (/Windows/StartUp)
%Windows-StartMenu% (/Windows/Start Menu)
%Windows-StartMenu-Programs% (/Windows/Start Menu/Programs)
%Windows-StartMenu-Programs-Games% (/Windows/Start Menu/Programs/Games)
Useful Resources
Windows Mobile Builds
Da_G All-In-One Windows Mobile 6.5.x Builds (Strongly recommended, contains all languages and all resolutions needed for almost any device)
Latest SYSs and OEMs XDA thread (where all the latest SYS builds are posted)
Common EXT Packages
(if you have suggestions or know where to find newer versions please post them)
Latest Touch Pro 2 EXT Packages (English-only, WVGA only)
Coming soon...
Help wanted!
1. Kitchen translation
Translators for the kitchens are needed! The kitchen is now completely localizable and will generate a translation template in the Resources\Localization folder when it's started up the first time: that file can be easily edited to translate all the text of the kitchen (also include an about entry for credits) and the kitchen will validate it and keep it updated every time it's launched organizing the entries that are missing or not found. If somebody has some spare time to help me translate the kitchen in other languages please attach a translated lng file to a post so I can include it in the kitchen archive.
2. Informations about the WM6.5.X packages required for each language
In order to improve the automatic localized packages selection I need to know which of the following packages:
Code:
BronzeEA BronzeNonEA BronzeAH | CommonEA CommonNonEA | SYSTEM_DEFAULT_FONTS COMPLEXSCRIPT_FONTS | gb18030 | Riched20 Riched20_CS | SipAR | Transcriber UNISCRIBE | Webview Webview_CS
are needed for each of the following languages:
Code:
0402 BRG Bulgarian (Bulgary)
0404 CHT Chinese Traditional
0405 CSY Czech (Ceská republika)
0408 ELL Greek (Ellas)
0411 JPN Japanese
0412 KOR Korean
0415 PLK Polish (Polska)
0419 RUS Russian
041B SVK Slovak" (Slovensko)
041D SVD Swedish (Sverige)
041F TUR Turkish (Türkiye)
0424 SVN Slovenian (Slovenija)
0804 CHS Chinese Simplified
081A SPB Serbian (Latin)
If anybody knows the right packages needed for one (or hopefully more) of those languages please let me know.
nice thread but i think u should post new sys files..... iam not able to cook may be still my format is wrong so i wanted to take reference but its old further links are broken
jagan2 said:
nice thread but i think u should post new sys files..... iam not able to cook may be still my format is wrong so i wanted to take reference but its old further links are broken
Click to expand...
Click to collapse
I uploaded 28223 SYS/XIP files, if you want other builds tell me.
@AirXtreme The kitchen is great and I like it way better than Ervius' VK, but I do have some small questions though. Since the split from the original osKitchen things have been a little vague, this is what I understand of it.
OndraSter developed the kitchens core code and you developed the new gui. Both trees still exist and both trees are 'updated' to RC3, but the version number in the .exe still says RC2.7.
Second, what is the latest version? Would it be possible to include build date and changelog in the first post, so it's easy to follow the updates to the kitchen? I know it's a lot to ask, but it would help a lot.
For the rest, great kitchen!
airxtreme said:
I uploaded 28223 SYS/XIP files, if you want other builds tell me.
Click to expand...
Click to collapse
Upload 23529 and I'll give this kitchen a whirl
Cheers.
KilZone said:
@AirXtreme The kitchen is great and I like it way better than Ervius' VK, but I do have some small questions though. Since the split from the original osKitchen things have been a little vague, this is what I understand of it.
OndraSter developed the kitchens core code and you developed the new gui. Both trees still exist and both trees are 'updated' to RC3, but the version number in the .exe still says RC2.7.
Click to expand...
Click to collapse
It's because my sources are from 2.7 and didn't update the titlebar.
KilZone said:
Second, what is the latest version? Would it be possible to include build date and changelog in the first post, so it's easy to follow the updates to the kitchen? I know it's a lot to ask, but it would help a lot.
Click to expand...
Click to collapse
The last version is the one in the first post, when I'll release other updates I'll update the first post and add a changelog.
dickenz said:
Upload 23529 and I'll give this kitchen a whirl
Cheers.
Click to expand...
Click to collapse
It was already up but with the wrong name (28223), now names are fixed.
Awesome, thank you that clears it I guess. Just forgive my stupidity... Downloading the ... latest ... version now (and updating my current version).
airxtreme said:
The last version is the one in the first post, when I'll release other updates I'll update the first post and add a changelog.
Click to expand...
Click to collapse
@Airxtreme
The version in 1st post supports Iolite?
I didn't see it in supported devices list.
dancer_69 said:
@Airxtreme
The version in 1st post supports Iolite?
I didn't see it in supported devices list.
Click to expand...
Click to collapse
Yes, I think I added its device file.
I'll download now and test, thanks.
EDIT
I just checked and I allready have this version(Os kitchen 1.4 RC2.7)
and I have successfully build an nbh with this version, I just not flash it yet.
So, it's supported.
Okay,
I just download the New ATT Shipped ROM from HTC and I was going to give this kitchen a try.
I extracted the files from the shipped ROM.
When I started the kitchen, it asked me to point to the RUU file. I selected the RUU_signed.nbh that I had just extracted and I get the message "There was no os.nb present i this file! Can't continue"
What am I doing wrong?
rgb-rgb said:
Okay,
I just download the New ATT Shipped ROM from HTC and I was going to give this kitchen a try.
I extracted the files from the shipped ROM.
When I started the kitchen, it asked me to point to the RUU file. I selected the RUU_signed.nbh that I had just extracted and I get the message "There was no os.nb present i this file! Can't continue"
What am I doing wrong?
Click to expand...
Click to collapse
Give me the link to download the rom so I can try to see why no OS.nb is detected.
airxtreme said:
Give me the link to download the rom so I can try to see why no OS.nb is detected.
Click to expand...
Click to collapse
http://www.htc.com/us/support/tilt-2-att/downloads/
Third download on the list. Complete ROM
airxtreme said:
I uploaded 28223 SYS/XIP files, if you want other builds tell me.
Click to expand...
Click to collapse
Thankyou actually i wanted to test the sys xip provided by u coz whenever i try to sort sys and xip myself for oskitchen it crashes platformbuilder.exe so will try the one made for oskitchen.
But plz plz its too big file for me. I request you to upload build 23529 qvga lang 0409 only and specially on mediafire or any uploading site which supports parallel downloads. I will be waiting ....
jagan2 said:
Thankyou actually i wanted to test the sys xip provided by u coz whenever i try to sort sys and xip myself for oskitchen it crashes platformbuilder.exe so will try the one made for oskitchen.
But plz plz its too big file for me. I request you to upload build 23529 qvga lang 0409 only and specially on mediafire or any uploading site which supports parallel downloads. I will be waiting ....
Click to expand...
Click to collapse
http://www.mediafire.com/?zy0ejwmiwmy
Intro
Welcome; I wanted to offer a little "something" back to the XDA community in the hopes that it will benefit others and to show my appreciation to the folks that make XDA the great community that it is.
If you've gotten excited about the idea of cooking your own ROM's, you've probably had to spend several weeks of reading, asking questions, getting acquainted with your facility, and figuring out where you're going to plug your utensils and/or appliances. Now comes the easy part, cooking quality ROM's ... right? It's gotta be simple after that, I mean that was all the hard stuff ... right? Well ...
As any seasoned chef will tell you, the quality of a meal greatly depends on quality ingredients, utensils, and appliances. Ingredients are a personal preference and some chefs can make Macaroni & Cheese taste like the best meal in the world; and how do they accomplish this? In many cases, they use quality utensils and appliances and understand the limitations of them.
Equipping your kitchen with the right tools ensures that you're able to provide quality meals to your patrons - resulting in return visits.
Outro
The goal of this thread is encourage seasoned chefs to share their knowledge of quality tools that they use in their day-to-day activities of ROM cooking.
Some of these tools are free, others have a trial version, and others must be purchased. The goal isn't to promote any one specific tool, it is to provide objective (and hopefully unbiased) reviews of these tools. Lastly, a moderator or senior chef may periodically review and cleanup this thread/post to ensure that it remains on-topic and consistent in format ... so don't take offense; you'll always be credited for your contribution.
Format For Each Post
Take a moment to review existing tool reviews; the goal is to share your experiences in using the tool. The review should contain the following information:
Name of the tool (same as in Title of post)
Version
Author
Link to tool
Cost (Free, Adware, Trialware, Purchase)
Reviewed by [your XDA member name]; in case the post is moved near the top of the thread at a later date.
Summary of what the tool does (uses) and any example you can think of.
Tips on how to use the tool; things you discovered when using the tool.
Potential pitfall (gotcha's) when using the tool; things you discovered when using the tool.
Reference threads (optional); links that might offer some additional usage information.
No attachments please. Post them in the original thread for the tool.
List Of Tools To Review
List Of Tools To Review
Here's a list of tools that I'd like to review and add to this thread. The goal is to review the various tools that chefs will often use while preparing their ROMS; any seasoned chefs (aka volunteers)? If so, post your review in the thread.
CABARC: MS Cabinet SDK in self executing zip
CABtoEXT
CeRegEditor
DSM Assembler Manifest: DSM Editor
EmEditor: advanced string search & editor
HEX Workshop: Intermediate HEX editor
ini2reg : Preformatted ini file for customized Registry extraction
IDA Pro: assembler/disassembler (extremlely advanced)
NBHextract: .NBH Extraction
NBHUtil: .NBH Generation
Notepad2: intermediate multi-editor (lua, xml, cmd, etc.)
Paint.NET: graphics editor
ProvXMLCreator: Autoconfiguration for WiFi, Certificates and email
PE Explorer: resource editor
PHM Registry Editor
PreKitchen Tool: import SYS to kitchen
RECMOD: recode/decode modules
REG2XML: convert .reg and .rgu files to xml
RegLogger: registry logging
ROM Extractor (Link 2)
TrayGUID PC: generate unique GUID to clipboard by clicking it
UAE Debugging Tool (UAEDT = Unrecoverable Application Error Debugging Tool)
WinCE CAB Analyzer (MSCEInf): .CAB extraction
WinCE CAB Manager: .CAB creation
XVI32: basic HEX editor
Resource Builder
Windows Mobile Developer Power Toys
Any others? Feel free to post a request in the thread or send me a PM.
Quick Post Index
Quick Post Index
Sorted alphabetically; at least I hope it is.
CAB/OEM Package Converters
CAB2OEM
CAB to OEM to EXT GUI Suite
Package Creator
Device Side Manifest (.DSM) Editors
BuildDSM
DSM Analyzer
DSM Builder
DSM Dependency Dumper
DSM Editor
Editors
EditPad
SciTE
Syn Text Editor
XML Notepad
Graphics (.BMP, .JPG, .PNG, etc.)
GNU Image Manipulation Program (GIMP)
IcoFX
Kitchen Porting Tools (SYS, OEM, etc.)
Initflashfiles Hex2Text
SYS Porting Tool For Ervius Kitchen
Process, Registry
FDC Task Manager (aka DotFRED)
Registry Workshop
Resource (.DLL, .EXE, etc.)
Dependency Walker
File Editor Suite
PEinfo
Resource Hacker
ROM Squeezer
Search/Comparison/File Managers
Beyond Compare
Compare It
Directory Opus
Senax's Library Of Links
Senax's Library Of Links
There are links to SDK's, developer tools, power toys and more. More links are better than less, so we say in Holland Don't you agree??
Have a nice day folks,
Senax
:UPDATE:
How could I forget to mention;
System Center Mobile Device Manager Resource Kit Tools
That was my left sleeve of links...
Q: Are you going to make it any easier for us?
A: That's a good question! No, (not for the Moderator(s) ) I've no intention of that just yet. First more power links, while thoroughly reviewing stuff, then searching for new links (references) and so on. Then a new review
Have a nice day / night while clicking all them links in ...,
Senax
Here some links to SDK's to inform others and get them reviewed:
Windows Mobile 5.0 SDK for Pocket PC
Windows Mobile 5.0 SDK Documentation
Windows Mobile 6 Documentation
Windows Mobile 6 SDK Refresh
Windows Mobile 6 SDK Documentation
Windows Mobile 6.5 Developer Tool Kit
Windows Mobile 6.5 Documentation
Windows Mobile 6.5.3 DTK
.NET XML PowerToys:
Generating XML Documents from XML Schemas
The XML Diff and Patch GUI Tool
Using the XML Diff and Patch Tool in Your Applications
Using the XSD Inference Utility
XML Tools Update
MSXML SDK
Power Toys for .NET Compact Framework 3.5
&
NETCFv35.Messages.EN.wm.cab ; exception messages
Windows CE CAB Installer SDK (though named SDK its more a CDK (Commercial DK), because you've got to pay $5 for it).
Awesome for UC (User Customization).
Microsoft SDKs (every and all SDKs from MS) for;
Azure Services Platform
Windows Desktop
Office
Devices
Windows Live Services
Server Technologies
Social
Games
Web Development
Other
Developer Tools:
Installing Developer Tools on Windows Mobile
Development Tools and Resources for Windows Mobile
Development Resources for WM on xda-developers.com
UPDATED: http://forum.xda-developers.com/showthread.php?t=445396
What Microsoft does not tell is that when they shot themselves in the foot with 'Vista', they were forced to introduce Win7 earlier as planned. Thus VS2008 (read WM) all its links have been moved to > :NULL
Well maybe not, though I've a hard time finding them .. and I do know how to tweak-search. We (the users) are forced into using VS2010 now! It's all 'embedded' now (cq sort of virtual). Ah, well.. it's not that bad
Windows Mobile 6 Localized Emulator Images
http://www.microsoft.com/downloads/...A8-1DD7-426F-A913-4F370A65A582&displaylang=en
Brief Description
This package includes localized Windows Mobile 6 emulator images that can be used with Visual Studio to test applications on different localizations or simply as standalone emulators without Visual Studio 2005!
Microsoft Power Toys:
Windows Mobile Network Analyzer PowerToy (Released with WM5 though usable with WM6)
Windows Mobile Device Security Manager PowerToy(Released with WM5 though usable with WM6)
General (Embedded) WM 6.x CE PowerToys link
Nowadays there 'll be no more Power Toys from Microsoft, instead we get:
Not (all) Windows Mobile specific: Microsoft Solution Accelerators & ~ A-Z technet :Free power(toys);
MSDN Code Galery third party resources
Windows Phone Developer Tools Beta
XML Notepad 2007 References:
Since this nice free editor is on CodePlex it is nice to mention this link;
http://xmlnotepad.codeplex.com/
I also found this link in my BookmarX_Manager; http://msdotnetsupport.blogspot.com/...-tutorial.html (their MORE button is the best TUTORiAL I've seen online about XML Notepad!!)
Hopper
There's a 'new' Hopper (device stress tester included In WM Developer Power Toys) for WM6> (not WP7). Hopper its two versions WM5 WM6; http://forum.xda-developers.com/show...45#post7549645
[PC] works for device too if its cradled.
Q: Is a file signed with a signature?
A: Let us check that using SystemInternals_Suite (click on the left of that page) its CLI SigCheck.exe
SigCheck; Verify that images are digitally signed and dump version information with this simple command-line utility.
ARM
These links are NOT for a review, these are to inform people about ARM processors used in WM and WP:
ARM Classic Processors
ARM Infocenter
ANDROiD SDK
http://developer.android.com/index.html
Phoenix SDK
Phoenix is the code name for a software optimization and analysis framework that is the basis for all future Microsoft compiler technologies. The Phoenix framework is an extensible system that can be adapted to read and write binaries and MSIL assemblies and represent the input files in an IR, which can be analyzed and manipulated by applications by using the Phoenix API. The code can then be written in binary or JITable form for execution.
It enables teaching and collaborative research in code generation, optimization, program analysis, binary transformation, and software correctness. Phoenix is used as a research platform by Microsoft Research and will be the universal compiler backend for upcoming Microsoft languages and development tools.
Phoenix SDK April 2008
How to install Phoenix SDK
Senax's Library of Links ... continued
AT Commander
{
"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"
}
[PC] ATCommander;
http://atcommander.com
The above link does not provide us with much information/links thus I searched some more
and came up with; http://atcommander.com/download/. Same page though not reachable via the first link. Anyway here you can download the latest .zip or .exe.
Note: My anti virus started to whine as soon as I unpacked the zip, though when I ran it in a VMware workstation everything worked smoothly.
Also do not forget to check this link;
http://atcommander.com/public/
Here some AT Commands reference links provided in two pdf files;
http://atcommander.com/download/AT_C...Specification/
[WM5/6] ATCommander;
http://forum.xda-developers.com/showthread.php?t=375395
Senax's Library of Links ... continued
Reserved for future expansion.
Resource Hacker
Name: Resource Hacker
Version: 3.5.2 beta
Author: Angus Johnson
Link: http://angusj.com/resourcehacker
Cost: Free
Reviewed By: Sous-Chef
Summary/Review:
Resource Hacker is a freeware utility to view, modify, rename, add, delete and extract resources in 32bit Windows executables and resource files (*.res). Cursor, Icon, Bitmap, GIF, AVI, and JPG resource images can be viewed and WAV, MIDI audio resources can be played. Menus, Dialogs, MessageTables, StringTables, Accelerators, Delphi Forms, and VersionInfo resources can be viewed as decompiled resource scripts. Menus and Dialogs can also be viewed as they would appear in a running application.
Resources can be saved as image files (*.ico, *.bmp etc), as script files (*.rc), as binary resource files (*.res), or as untyped binary files (*.bin). Resources can be modified by replacing the resource with a resource located in another file (*.ico, *.bmp, *.res). Dialog controls can also be visually moved and/or resized by clicking and dragging the respective dialog controls prior to recompiling with the internal compiler. Additionally, resources can be added to an application by copying them from external resource files (*.res).
Tips:
Always keep a copy of the unaltered file as a backup.
Gotcha's:
Even though it is possible to alter the resources, some applications automatically resize controls and dialogs during operation.
Some applications may cease to function when the resource file is altered.
Reference Links:
http://forum.xda-developers.com/showthread.php?t=511876
http://forum.xda-developers.com/showthread.php?t=562645
http://asukal.seesaa.net/article/6114096.html
Beyond Compare
Name: Beyond Compare
Version: 3.1.10
Author: Scooter Software, Inc.
Link: http://www.scootersoftware.com
Cost: Trialware, Purchase
Reviewed By: aruppenthal, Sous-Chef
Summary/Review:
Beyond Compare allows you to quickly and easily compare your files and folders. By using simple, powerful commands you can focus on the differences you're interested in and ignore those you're not. You can then merge the changes, synchronize your files, and generate reports for your records. You can compare entire drives and folders at high speed, checking just sizes and modified times. Or, thoroughly verify every file with byte-by-byte comparisons.
Once you've found specific files you're interested in, Beyond Compare can intelligently pick the best way to compare and display them. Text files can be viewed and edited with syntax highlighting and comparison rules tweaked specifically for documents, source code, and HTML. Data files, executables, binary data, and images all have dedicated viewers as well, so you always have a clear view of the changes. Beyond Compare is a "must have" tool; it will save hours of time. There is no better way to compare new builds and look for what has changed. When properly configured, it can display file versions which make integration of multiple sets of OEMdrivers a breeze. Swapping SYS files is never easier; you get to see dates of creation and can easily move files from one set to the other with a few clicks.
Here are some examples of how comparison can be used:
Compare one .\SYS folder version (ex: 23541) against an updated .\SYS folder version (ex: 23549) so as to determine what changes have occurred in registry files.
Compare one version of a ROM package (ex: Manila_2.1) against a newer version of the package (ex: Manila_2.1.1).
Compare a device ROM (ex: Mega_HTC_Europe_1.28.401.4) against another ROM (ex: Mega_TMO_UK_1.33.110.2) of the device to see what the HTC changed.
Compare specific files such as .XML, .PROVXML, etc.
Tips:
You can copy the installation folder from your system to an external drive. You can then launch the .EXE from the external drive on another system - no need for installation.
Enable the "Send Files To The Recycle Bin" option to avoid having a file permanently deleted when it is removed from the list.
Gotcha's:
Editing INITFLASHFILES.DAT with the built-in editor is not recommended as it may cause corruption resulting in ROM issues.
Reference Links:
http://forum.xda-developers.com/showpost.php?p=5979483&postcount=11
http://forum.xda-developers.com/showpost.php?p=6251478&postcount=27
IcoFX
Name: IcoFX
Version: 1.6.4
Author: Attila Kovrig
Link: http://icofx.ro
Cost: Free
Reviewed By: Sous-Chef
Summary/Review:
IcoFX is an all-in-one freeware icon editor solution for icon creation, extraction and editing. It is designed to work with Windows XP, Windows Vista, Windows 7, Windows CE and Macintosh icons supporting transparency.
Easily convert your favorite images into icons, or icons into images. IcoFX gives you the possibility to create icon libraries or change icons inside EXE files. You can extract icons from other files, including Windows Vista, Windows 7 and Macintosh files. You can easily work with multiple files using the batch processing capability of IcoFX.
Tips:
Always keep a copy of the unaltered file as a backup.
Choose free images to avoid potential copyright pitfalls.
Gotcha's:
None discovered.
Reference Links:
http://forum.xda-developers.com/showthread.php?t=511876
Dependency Walker
Name: Dependency Walker
Version: 2.2
Author: Steve P. Miller
Link: http://www.dependencywalker.com
Cost: Free
Reviewed By: Sous-Chef
Summary/Review:
Dependency Walker is a utility that scans any 32-bit or 64-bit Windows module (exe, dll, ocx, sys, etc.) and builds a hierarchical tree diagram of all dependent modules. For each module found, it lists all the functions that are exported by that module, and which of those functions are actually being called by other modules. Another view displays the minimum set of required files, along with detailed information about each file including a full path to the file, base address, version numbers, machine type, debug information, and more.
Dependency Walker is very useful for troubleshooting system errors related to loading and executing modules. Dependency Walker detects many common application problems such as missing modules, invalid modules, import/export mismatches, circular dependency errors, mismatched machine types of modules, and module initialization failures. It handles all types of module dependencies, including implicit, explicit (dynamic / runtime), forwarded, delay-loaded, and injected. For example, a quick way to determine what additional packages may be required for an application:
Open each .DLL/.EXE file in the package (ex: YouTube)
Note the files that are flagged as missing.
Search the source (usually an extracted ROM) for those files; odds are you'll need the entire package contents where the file is found.
Repeat the process until all of the necessary files are found.
Dependency Walker runs on Windows 95, 98, Me, NT, 2000, XP, 2003, and Vista. It can process any 32-bit or 64-bit Windows module, including ones designed for Windows CE. Windows CE modules use the same module format (known as the "Portable Executable" format) that is used for modules written for Windows 95, Windows 98, Windows Me, Windows NT, Windows 2000, Windows XP, Windows 2003, Windows Vista, and beyond. There is no version of Dependency Walker that actually runs on Windows CE, but you can open Windows CE modules with Dependency Walker on a standard Windows computer.
Tips:
Create a folder with all of the common WinCE files in it and set a custom search order that includes this path and save it to a file.
Use RECMOD to recode modules that may be required.
Use the "/d:your_file.dwp" command line option to pass a custom search order file to Dependency Walker.
Gotcha's:
Dependency Walker automatically tries to locate dependent modules using the default Windows module search path. For Windows CE modules, this can cause errors since non-CE modules may be found in the default search path. To fix this, you can use Dependency Walker's "Configure Module Search Order" dialog to remove all standard paths and then add a private folder of your own that contains only CE modules.
Reference Links:
http://forum.xda-developers.com/showthread.php?t=576027
FdcSoft Task Manager (aka dotFRED Task Manager)
Name: FdcSoft Task Manager (aka dotFRED Task Manager)
Version: 3.3
Author: FdcSoft (aka dotFred)
Link: http://www.dotfred.net/TaskMgr.htm
Cost: Free
Reviewed By: Sous-Chef
Summary/Review:
The Task manager application is a bunch of several useful tools in just one tool. It includes a Process manager, CPU usage, Application Manager, Service Manager, Device Manager (only WM2005 and above), Windows Manager, Notification Manager, IP Config utility, Ping utility, Net Stats utility, Registry Editor, and Run program utility.
Although, the application is intended to run on a Mobile Device, it is an excellent tool to use during the preparation of OEM packages. For example, the following procedure speeds up the process of converting from .CAB to OEM:
Copy the files from extract .CAB to the device
Import the registy settings
Process the .PROVXML files.
Reboot the device
Test application
Tips:
The application can run from an SD card.
.RGU files can be renamed to .REG; make sure to remove the hidden, system file attributes.
Gotcha's:
.PROVXML files require a minor adjustment; see reference link below.
Reference Links:
http://forum.xda-developers.com/showthread.php?t=519548
Directory Opus
Name: Directory Opus
Version: 9.5.3
Author: GP Software
Link: http://www.gpsoft.com.au
Cost: Trialware, Purchase
Reviewed By: ceesheim
Summary/Review:
Directory Opus 9 is a Windows File Manager & Explorer replacement that includes, user-definable file display views, User-definable toolbars, menus, file types, powerful image and file viewers, built-in ZIP and Secure SSL/SSH FTP, easily synchronize files & find duplicates, quick or advanced search and rename functions.
The file manager is extremely useful for moving files between folders, making backup copies of files, viewing pictures and playing sounds, running other utility programs on lists of files, deleting unwanted files and many other "housekeeping" tasks. If you are working with a lot of files in kitchens or Manila, this is a must have.
Tips:
Take a few moments to get familiar with the options.
Can view .XML , HEX , .TXT , .DOC , .CPR , .PROVXML , .MSCR , .DSM , .RGU And many more
In view mode it can tell you if a manila file is a lua or a QTC1 file (in HEX)
Download lot of Plugins & Media Capabilities (RTF-Viewer , CSV-Viewer , Source Code Viewer , Postscript-Viewer , RVF File , EXE/DLL Metadata)
Gotcha's:
None discovered.
Reference Links:
None.
XML Notepad 2007
Name: XML Notepad 2007
Version: 2.5
Author: Microsoft
Link: http://www.microsoft.com/DownLoads/...49-787d-4118-ba5f-4f30fe913628&displaylang=en
Cost: Free
Reviewed By: Sous-Chef
Summary/Review:
XML Notepad 2007 provides a simple intuitive user interface for browsing and editing XML documents. XML Notepad provide synchronized Tree View with Node Text View for quick editing of node names and values, incremental search (Ctrl+I) in both tree and text views, so as you type it navigates to matching nodes, Cut/copy/paste with full namespace support, drag/drop support for easy manipulation of the tree, even across different instances of XML Notepad and from the file system.
Additionally, XML schema are instantly validate while you edit with errors and warnings shown in the task list window. It includes intellisense on expected elements and attributes and enumerated simple type values, inplace HTML viewer for processing xml-stylesheet processing instructions, built-in XML Diff tool, support for XInclude, dynamic help from XSD annotations, and goto definition to navigate includes and XSD schema information.
It's a must have when working with .XML and .PROVXML files.
Tips:
Ensure that .NET Framework v2.0 (or higher) is installed
Gotcha's:
None discovered.
Reference Links:
http://forum.xda-developers.com/showthread.php?t=519548
Field Notes: Beyond Compare
Name: Beyond Compare
Version: 3.1.10
Click to expand...
Click to collapse
Hi Hilaireg Long time no talk
I want to emphasize the usage of Beyond Compare. This is the MOST important tool a chef can own. It will save hours of time. There is no better way to compare new builds and look for what has changed. When properly set up it shows file versions making integration of multiple sets of OEMdrivers a breeze. Swapping sys files is never easier as you get to see dates of creation and can easily move files from one set to the other with two clicks.
There is one thing not mentioned as far as cons. Using it on initflashfiles.dat is not recommended. Every time I have done so major issues followed by a restore of the original files.
Also when using beyond compare be SURE to set it to send files to the recycle bin. If not it will permanently delete them
EditPad
Name: EditPad
Version: Lite
Author: Just Great Software Co. Ltd.
Link: http://www.editpadpro.com/editpadlite.html
Cost: Free (Lite), Purchase (Pro)
Reviewed By: Laurentius26
Summary/Review:
EditPad Lite is a general-purpose text editor, designed to be small and compact, yet offer all the functionality you expect from a basic text editor. EditPad Lite works with Windows 98, ME, NT4, 2000, XP, Vista, and 7.
Additionally, You can open as many files in EditPad at a time as you want and change between the open files by clicking on their tabs without the hassle of overlapping windows. EditPad reads and writes UNIX (LF only) and Mac (CR only) text files (in addition to DOS/Windows CR+LF files, of course). EditPad natively supports Unicode text files and text files encoded in a variety of legacy code pages. EditPad supports all Windows and ISO-8859 code pages, plus a wide selection of DOS, KOI8 and EBCDIC code pages.
This means EditPad can edit any text file, whether it was saved on a Windows or Linux computer, an old DOS PC or an IBM mainframe. EditPad fully supports double byte character systems (DBCS) so you can edit texts written in Far East languages, such as Chinese, Japanese or Korean, as easily as those written in European languages.
EditPad is a very handy editor for viewing/editing .rgu, .dat, .xml, .html, and multiple formats - a must have for your kitchen.
Tips:
If you run EditPad again when there is already an instance running, the file(s) you wish to edit will be opened by the existing EditPad window. This means there will be at most one EditPad window open, which will save you from a lot of task switching. Of course, if you do need more instances, simply pick View|New editor from the menu.
EditPad puts an icon in the system tray that remains visible, even if EditPad is closed. This way you have easy and fast access to EditPad, without the need to keep it running all the time.
Gotcha's:
None discovered.
Reference Links:
None.
DSM Editor
Name: DSM Editor
Version: 1.7
Author: ervius
Link: http://forum.xda-developers.com/showthread.php?t=523139
Cost: Free
Reviewed By: Sous-Chef
Summary/Review:
In early kitchen and ROM cooking, chefs used to delete Device Side Manifest (.DSM) files from OEM packages that resided in the .\PACKAGES and/or .\EXT folder. Other chefs would delete the .DSM file and create an empty version of a .DSM file as a placeholder. As we learned more about the Windows Mobile, we discovered that .DSM files contained pertinent information that was used during the compilation of a ROM and should be properly managed. DSM Editor is a utility to view and modify components of a .DSM file .DSM such as certificates, dependencies, shadow order, and list of modules/files.
A Device Side Manifest file (.DSM) describes the contents of a package and has the name <GUID>.DSM. Each package has its own .DSM file. The .DSM file is a binary file and the format may change at any time. The .DSM file is created by parsing a package definition file, package shadow file, and a build manifest file. Each item specified within a build manifest file is used to determine the item's file type.
The .DSM file contains the following information:
Public key certificate data used for signature validation.
Version information which includes the previous version of a package so as to create a delta package between an older or baseline package and a new package.
Package GUID
Dependency GUID information
File names and file information in the form of raw file size and original VBase for MODULES so they can be re-based and differentiated during an update.
Tips:
Always keep a copy of the unaltered file as a backup.
A .DSM file should contain a complete (exact) list of all modules/files found in the package folder.
The .RGU file should be excluded from the .DSM file.
Kitchen-specific files should be excluded from the .DSM file.
Gotcha's:
Hidden (H) and/or System (S) attributes may need to be cleared (ATTRIB -s -h -r) from .DSM files before they can be edited.
Requires .NET Framework.
Reference Links:
http://forum.xda-developers.com/showthread.php?t=520009
DSMBuilder
Name: DSMBuilder
Version: 2008-08-08
Author: anmendes
Link: http://forum.xda-developers.com/showthread.php?t=412272
Cost: Free
Reviewed By: Sous-Chef
Summary/Review:
In early kitchen and ROM cooking, chefs used to delete Device Side Manifest file (.DSM) files from OEM packages that resided in the .\PACKAGES and/or .\EXT folder. Other chefs would delete the .DSM file and create an empty version of a .DSM file as a placeholder. As we learned more about the Windows Mobile, we discovered that .DSM files contained pertinent information that was used during the compilation of a ROM and should be properly managed. DSMBuilder is a utility to view and modify components of a .DSM such as certificates, dependencies, shadow order, and list of modules/files.
A Device Side Manifest file (.DSM) describes the contents of a package and has the name <GUID>.DSM. Each package has its own .DSM file. The .DSM file is a binary file and the format may change at any time. The .DSM file is created by parsing a package definition file, package shadow file, and a build manifest file. Each item specified within a build manifest file is used to determine the item's file type.
The .DSM file contains the following information:
Public key certificate data used for signature validation.
Version information which includes the previous version of a package so as to create a delta package between an older or baseline package and a new package.
Package GUID
Dependency GUID information
File names and file information in the form of raw file size and original VBase for MODULES so they can be re-based and differentiated during an update.
Tips:
Always keep a copy of the unaltered file as a backup.
A .DSM file should contain a complete (exact) list of all modules/files found in the package folder.
The .RGU file should be excluded from the .DSM file.
Kitchen-specific files should be excluded from the .DSM file.
Gotcha's:
Hidden (H) and/or System (S) attributes may need to be cleared (ATTRIB -s -h -r) from .DSM files before they can be edited.
Dumping a custom ROM where a .DSM file was altered with DSMBuilder may result in the package being placed in the SYS folder.
Reference Links:
http://forum.xda-developers.com/showthread.php?t=520009
DSM Dependency Dumper
Name: DSM Dependency Dumper
Version: 2009-06-19
Author: dj13241
Link: http://forum.xda-developers.com/showthread.php?t=527965
Cost: Free
Reviewed By: Sous-Chef
Summary/Review:
DSM Dependency Dumper is a handy tool to extract the list of dependency packages for a single Device Side Manifest file (.DSM) or an entire ROM. The DSM Dependency Dumper will produce a Comma Separated Values (.CSV) output file detailing all of the required dependencies for a package.
A Device Side Manifest file (.DSM) describes the contents of a package and has the name <GUID>.DSM. Each package has its own .DSM file. The .DSM file is a binary file and the format may change at any time. The .DSM file is created by parsing a package definition file, package shadow file, and a build manifest file. Each item specified within a build manifest file is used to determine the item's file type.
The .DSM file contains the following information:
Public key certificate data used for signature validation.
Version information which includes the previous version of a package so as to create a delta package between an older or baseline package and a new package.
Package GUID
Dependency GUID information
File names and file information in the form of raw file size and original VBase for MODULES so they can be re-based and differentiated during an update.
Tips:
Most ROM's are shipped with missing package dependencies.
Gotcha's:
None Discovered.
Reference Links:
http://forum.xda-developers.com/showthread.php?t=520009
Registry Workshop
Name: Registry Workshop
Version: 4.2.4
Author: Torchsoft
Link: http://www.torchsoft.com/
Cost: Trialware, Purchase
Reviewed By: Laurentius26
Summary/Review:
Registry Workshop is an advanced registry editor for Windows 2000 (Service Pack 4), Windows XP (32/64-bit), Windows 2003 (32/64-bit), Windows Vista (32/64-bit), Windows 2008 (32-bit and 64-bit), and Windows 7 (32/64-bit). It is a perfect replacement for RegEdit and RegEdt32 which shipped with Windows. In addition to all the standard features, Registry Workshop adds a variety of powerful features that allow you to work faster and more efficiently with registry related tasks. With Registry Workshop, registry editing becomes more safe than ever before. All changes except changing key permissions can be safely reversed (even registry replacing and importing), using multiple levels of Undo. You don't need to worry about making mistakes when editing registry.
Registry Workshop includes many useful features: multiple undo and redo, the undo history can be saved to disk and reloaded at startup, search and replace registry keys, values and data with super fast search algorithm, compare registry between computers and/or .REG files with super fast speed, connect mobile device (Pocket PC, SmartPhone, etc.) registry via ActiveSync, cut, copy and paste registry keys and values, drag and drop to move or copy registry keys and values, edit .REG files and .POL files in the same way as editing system registry, backup and restore registry, defragment registry with preview, easy and flexible favorites management, quickly browse registry with address bar, bookmarks and visitation history, context menus to navigate to referenced key: open containing folder or open URL if the key or value contains a ProgID, ClassID, folder, file path or URL, jump to the same key in HKLM or HKCU by context menu, open multiple local registry windows, allow to open secure registry keys when running under the administrator privilege, and edit binary data in BYTE, WORD or DWORD format.
Tips:
Excellent for editing/viewing/export/import registry keys on your device from your desktop using ActiveSync.
Gotcha's:
None discovered.
Reference Links:
None.
DSM Analyzer
Name: DSM Analyzer
Version: 1.5
Author: michyprima
Link: http://forum.xda-developers.com/showthread.php?t=444186
Cost: Free
Reviewed By: Sous-Chef
Summary/Review:
In early kitchen and ROM cooking, chefs used to delete Device Side Manifest file (.DSM) files from OEM packages that resided in the .\PACKAGES and/or .\EXT folder. Other chefs would delete the .DSM file and create an empty version of a .DSM file as a placeholder. As we learned more about the Windows Mobile, we discovered that .DSM files contained pertinent information that was used during the compilation of a ROM and should be properly managed. DSM Analyzer is a utility to view and modify components of a .DSM file such as certificates and list of modules/files.
A Device Side Manifest file (.DSM) describes the contents of a package and has the name <GUID>.DSM. Each package has its own .DSM file. The .DSM file is a binary file and the format may change at any time. The .DSM file is created by parsing a package definition file, package shadow file, and a build manifest file. Each item specified within a build manifest file is used to determine the item's file type.
The .DSM file contains the following information:
Public key certificate data used for signature validation.
Version information which includes the previous version of a package so as to create a delta package between an older or baseline package and a new package.
Package GUID
Dependency GUID information
File names and file information in the form of raw file size and original VBase for MODULES so they can be re-based and differentiated during an update.
Tips:
Most ROM's are shipped with missing package dependencies.
Gotcha's:
Does not provide dependencies or shadow order information.
Changes only appear after reloading the .DSM or .DSM(s) in a folder.
Reference Links:
http://forum.xda-developers.com/showthread.php?t=520009
Official XDA OSBuilder kitchen thread (developed by Barin)
this thread is dedicated to discussions related windows mobile
Official XDA OSBuilder 7 kitchen thread (developed by Barin)
this thread is dedicated to discussions/info related to windows phone 7
I'm honored to be allowed to officially announce/present/support osbuilder here in xda forums by barin. thank you.
this is a new kitchen (not based on old platform rebuilder) developed by asusmobile.ru member barin and tested by many others (mentioned below) including myself.
ultrashot is also developing some parts of osbuilder (custom imgfsfromdump with advanced parameter support for example).
"One word: SUPERIOR!" hd2owner
OS Builder V1.4.236 FULL (01.12.2012) - 3962+ downloads
OS Builder V1.4.235 FULL (25.11.2012) - 271 downloads (20590)
OS Builder V1.4.234 FULL (22.11.2012) - 91 downloads
OS Builder V1.4.223 FULL (02.10.2012) - 931 downloads
OS Builder V1.4.209 FULL (19.05.2012) - 2155 downloads
OS Builder V1.4.206 FULL (21.04.2012) - 531 downloads
OS Builder V1.4.205 FULL (16.04.2012) - 199 downloads
OS Builder V1.3.199 FULL (09.12.2011) - 4792 downloads
OS Builder V1.3.189 FULL (08.11.2011) - 1762 downloads
OS Builder V1.3.187 FULL (03.11.2011) - 159 downloads
OS Builder V1.3.163 FULL (29.09.2011) - 2183 downloads
OS Builder V1.2.157 FULL (20.09.2011) - 257 downloads
OS Builder V1.2.153 FULL (15.09.2011) - 157 downloads
OS Builder V1.2.148 FULL (04.09.2011) - 558 downloads
OS Builder V1.2.143 FULL (28.08.2011) - 412 downloads
OS Builder V1.2.140 FULL (21.08.2011) - 229 downloads
OS Builder V1.2.133 FULL (11.08.2011) - 337 downloads
OS Builder V1.2.124 FULL (28.07.2011) - 423 downloads
OS Builder V1.2.116 FULL (27.06.2011) - 1716 downloads
OS Builder V1.2.111 LE (08.06.2011) - 518 downloads
OS Builder V1.2.107 LE (05.03.2011) - 970 downloads
OS Builder V1.2.101 LE (21.02.2011) - 582 downloads
OS Builder V1.2.99 LE (19.02.2011) - 213 downloads
OS Builder V1.2.89 LE (31.12.2010) - 1244 downloads
Total osbuilder downloads on xda: 24552+
ATTENTION!
SINCE VERSION 1.2.81 (06.12.2010) OSBuilder IS DEPENDENT OF .NET FRAMEWORK 4 (runtime version not lower than 4.0.30319). Get .NET framework 4 here
DOWNLOAD (latest public osbuilder version by barin): OSBuilderSetup1.4.236-FULL.zip
OSBUILDER LATEST CHANGELOGS ->POST 3 & POST 4
NEW XPH COMPRESSION METHOD FROM WP7 MANGO
Since 1.2.153 we have possibility to use xph compression from wp7 mango (patched by ultrashot).
only usable on armv7 devices!! don't use xph on older arm devices! it won't work.
if you have a armv7 device and want to try xph->ultrashot's patched mango cecompr.dll thread
If someone wants to donate and help the project, take a look at the original thread on asusmobile.ru and the thread on mobileunderground.info
Many thanks to those, who helped to test osbuilder:
Alexx~, AndrewSh, greench, Lost_Angel, Vladimir1973
Special thanks to yad for the important and necessary information on relocation.
ENORMOUS thanks to alexx~ for many ideas and concepts, for THAT NOT VALUED! aid during the testing, and it is simple for the human support from the beginning also to the end of writing program.
{
"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"
}
Basic purpose of osbuilder
-assembling flat dump from the packets
-assembling IMGFS
-assembling ROM-File (for supported devices)
-extract/dump ROM-File (for supported devices)
OSBuilder can build NB0, NB and NBH files and for supported devices it can change rom version, date and/or some other data.
Also many other functions are included (Manila other language exclusion for example), which can be useful during creation and assembling of dump and ROM.
Basic possibilities
1. The group of packets (4 types of groups, the level of the nesting of groups is theoretically not limited, packets they are grouped by simple haul) and mapping packets and groups in the form of the tree
2. Convenient contextual menu for the work with the packets.
3. Selection of language for the piercing (co-existence of packets for the different languages)
4. Possibility to introduce detailed description for the packets and the groups (with the selection of packet or group description it will be automatically mapped into specially [otvedennom] for this window)
5. Import of configuration from the files of option.xml and their subsequent removal.
6. Retention of the configuration on silence and of any quantity of the configurations
7. Editing of dsm, rgu, initflashfiles, provxml of packet directly from the program
8. Possibility of the connection of external editors for dsm, rgu, initflashfiles, provxml
9. The survey of the folder of packet directly from the program (on silence conductor is used, but the connection of another file- manager is also possible)
10. Editing of boot.rgu, packages.sof, packages.cif, defaultcerts.dat, oem.cer directly from the program.
11. Survey and the editing of the order of assembling the list (it edits packages.sof)
12. The preliminary survey of the list, which must come out after assembling with the indication as and how often changed each parameter, such as file of rgu made change and in what line of the file of rgu this parameter is contained.
13. The preliminary survey of the file of initflashfiles.dat, which must come out after assembling.
14. Removal of files from modules and imageinfo.txt
15. Sufficiently flexible tuning of the parameters of assembling.
16. Possibility of the call of external programs from the menu.
17. Automatic forming or correction .VM and .ROM according to the data from the template or the file XIP
18. Built-in mechanism of readdressing the modules (Reloc) of the received flat dump.
19. Assembling the file of division IMGFS 20. Assembling file ROM - size of nb0 (payload)
program-window:
Contextual menu of the packet Built-in editor OF DSM (title)
the built-in editor OF DSM (modules and files)
the built-in editor OF DSM (dependence) information about the module Menu of additional tools
the editor of packages.sof (cif) Preliminary survey of list cleaning the modules Readdressing modules (Reloc) Tuning (parameters of assembling)
Program (assembling the files of payload NBH) is successfully tested with following HTC-devices:
HTC blueAngel
HTC touch 2 (Mega)
HTC touch of 3450 & 3452 (Elf of & Elfin)
HTC touch Of diamond
HTC touch HD
HTC touch diamond 2
HTC max 4G HTC Of iolite
HTC HD2
HTC HD mini
HTC kovsky (SE X1)
HTC WhitestoneW
If you have precise information about the special features of a certain new device model (structure of divisions and FLASH of regions, the signs of the search for date and version into nk.exe, and also other special features, for example, necessary whether to prescribe somewhere into nk.exe the sizes of rom, region etc, then the support of this can be added into osbuilder.
As to gather the dump without the template i tried to make the process of editing and assembling far more convenient and more visual. the result is osbuilder.
If you have ideas for improvements, write them down here and barin will take a look at them.
Tutorial Videos:
01-DumpNBH.zip
02-Grouping.zip
Manual:
WWE Manual Download Link
Multibuild feature (use more than one sys build):
http://www.mobileunderground.info/showthread.php?t=12348&p=42486#post42486
Porting XIP:
http://www.mobileunderground.info/showthread.php?t=12348&p=38546#post38546
http://www.mobileunderground.info/showthread.php?t=12348&p=38615#post38615
http://www.mobileunderground.info/showthread.php?t=12348&p=38829#post38829
Setting Package Build Order:
http://www.mobileunderground.info/showthread.php?t=12348&p=38558#post38558
Exclude/Include specific packages:
http://www.mobileunderground.info/showthread.php?t=12348&p=38622#post38622
OEM creator for EXT to OEM Conversion (another tool by ultrashot coming soon):
http://www.mobileunderground.info/showthread.php?t=12348&p=38919#post38919
Getting Started:
http://www.mobileunderground.info/showthread.php?t=12348&p=38859#post38859
List of supporters (fullversion):
Code:
Alexx ~, AndrewSh, HD2Owner, 3D MASTER,
ash172, bitje, Elesvil, erickwill, Feropont, fq3803, Gangsta-P,
Pgreench, GUG, Hellonasty, indagroove, Kristof Petho, LiquidStorm,
mishok_006, mondi, Mor-Da, MorzeCBP, mwalt2, NarkoZ,
NightOWL, Petrovych, rewwps, Satan!, serfer222, SergeyLAR,
tian tian, ultrashot, usv, Hacker, Zloy Pryanik, Vladimir1973
Other great tools by barin:
OS Builder 7 (WP7 Kitchen)
LEO Advanced ROM Update Utility
Titan Advanced ROM Update Utility
Mozart Advanced ROM Update Utility
Blackstone Advanced ROM Update Utility
Topaz Advanced ROM Update Utility
Kovsky Advanced ROM Update Utility
Whitestone Advanced ROM Update Utility
HTC Splash Tool
My projects:
HD2O ROM Series
X1O ROM Series
HTC HD2 stock ROM overview thread
Latest Opera 9.70 thread
HD2 WP7 donation fund for da_g
HD2 haret/linux/android donation fund for devs (cotulla, dcordes, markinus, letama, netripper)
HD2 6.5.3 global bold font fix (by ultrashot)
HD2Owner's youtube channel
TIPS & FUTURE CHANGELOG (web translation)
TIPS:
packages.sof/cif
i found it less complicated to re-build this lists myself than re-order the existing ones.
if you want to edit existing one:
-go to editor (packages.sof and cif same procedure)
-press "remove all missed" button
-mark all new packets you added on the right side
-place "cursor" on bottom of left side
-add packets from right side on bottom of left side with "move to packages.sof" button
if you want to re-order yourself, i am using this order currently (htc hd2 512mb):
-msxipkernel
-msxipkernelltk
-oemxipkernel
-langdb
-wincenls_xxx
-metadata (according sys version)
-oemdrivershigh
-os (according sys version)
-adobe flash (sys) (notice: make sure browsing is after browsingcore)
-....
-....(all sys packages)
-EXT/sys_fwupdate_mini (see tutorial videos)
-EXT/sys_sqm_mini (see tutorial videos)
-OEM/BuildInfoPkg
-....
-....(all OEM packages)
-AdobePDF
-....
-....(all OEM ext packages in oem format)
-All custom apps
-All custom mods
HD2 WM KITCHEN EXAMPLE (TEMPLATE):
DOWNLOAD HD2O template kitchen v1.1 (htc hd2, 14 languages supported; wm6.5.0/wm6.5.3)
DOWNLOAD HD2O template kitchen v1.15 patch
DOWNLOAD HD2O template kitchen v1.16 patch
OS Builder HD2 Template Kitchen v1.15 (27.07.2011) - 554+ downloads
OS Builder HD2 Template Kitchen v1.0 (21.06.2011) - 386+ downloads
template kitchen changelog:
v1.16 changes (03.10.11) patch
-xph compression integrated
v1.15 changes (27.06.11) patch
-lockscreen issue fixed on 6.5.3
-lockscreen media controls added
-lockscreen slider in middle instead top
-configurations adjusted
-packages.sof/cif adjusted
v1.1 changes (27.06.11)
-packages.sof/cif adjusted (now stock order)
-some sys packages of both builds adjusted (packages.sof related)
-ext packages cleaned
-paths in osbuilder settings adjusted (sorry, now fixed relative paths)
-wince.nls for asian roms added (only replace in rom if cooking asian rom)
-other minor changes in oem (mui's etc)
notes about template kitchen:
-all configs for 14 languages included (28 configs, 6.5&6.5.3) incl. manila exlusion list
-oem packages merged as far as possible if useful
-all "ext" language folders merged into one folder for each language for better overview
-if you are cooking chinese rom, replace wince.nls in rom with one from asian leo rom
-if you add your own apps, generate new dsm and add it on bottom of packages.sof/cif with built in editor
-navipanel, jetcetprint, copilot and jbed removed
-very close to stock but restructured
For chefs coming from a platformrebuilder kitchen i will add a tool by ultrashot to convert ext to oem later (osbuilder uses only oem packages).
you can use this for now - link
LATEST CHANGELOGS (web translation)
OSBuilder V 1.4.236 (01.12.2012)
Code:
1. Serious internal issue is fixed
OSBuilder V 1.4.235 (25.11.2012)
Code:
1. Fixed a serious issue that occasionaly appears while generating the version of the package by default
OSBuilder V 1.4.234 (22.11.2012)
Code:
1. Internal processing algorithm of XIP packages is changed (NK, SLDR)
2. Configuration menu item "Group language packs" is added. In the packages view tree (for packages selecting) the package group LANG is created and language packs are grouped into subgroups by codes (eg 0419, 040C, etc.) and placed in the LANG group.
3. More detailed information is displayed about the versions of packages (Tools -> Packages versions (DSM))
4. Saving files in editors of sof / cif, dsm and certificate files is now possible by hotkey Ctrl-S
5. In sof / cif editor - added the ability to automatically select all the language packs at the right window (see the toolbar)
OSBuilder V 1.4.223 (02.10.2012)
Code:
1. "Copy path to clipboard" item is added to Package context menu.
2. Files with nbh, nb, esco, nb0, payload, ffu extensions are associated with Dump Tool. Warning! Dump Tool works only with FFU WP7 files. All attempts to open FFU WP8 files will return error.
3. For WP7 second generation devices: logo file generator is added to Tools/Built-In.
4. Added ability (Additional tools) to view the policy.xml files (like provxml files - processing order and editing)
5. Added context menu of the kitchen root folder path (lower left corner of the main window) – possibility to open in a file manager or the command line, also possibility to copy the path to the clipboard
6. DSM Editor: added ability to set flags Boot hive and Allow Downgrade. Also added the opportunity to set the flags DIFF and DEL for FileEntry
7. In Tools/Built-In: added Cab Builder, allowing to create Cab file from the folder with files and to sign it with the certificate.
8. In Settings: changed an option to automatically include 0409 packages to rom. Now it's 0409/0809
9. A hell of internal changes in routines of processing and assembling
OSBuilder V 1.4.209 (19.05.2012)
Code:
1. Minor improvements in registry parser
2. Minor improvements in WMSTORE and NBH generators
OSBuilder V 1.4.206 (21.04.2012)
Code:
1. Dump tool supports esco files completely. You don't need to extract boot.img from esco files youself. Just open original esco file in Dump tool.
2. Minor improvements in Complex RGU
OS Builder V1.4.205 (16.04.2012)
Code:
1. New settings form
2. More responsive UI
3. WMSTORE rom format support.
4. Significantly updated D000FF support. Thanks, Andim! !!!Be VERY careful with maximum ROM size!!!
5. Automatic o32_dataptr fixing - important for system updates
6. WP7 DSM support improved. New module size calculation subroutine.
7. WP7 page pool changing support. (!) You have to keep original not patched NK, otherwise pool won't be changed during building.
8. Package file browser performance improved.
9. Simple algorithm against ROMs with hexed headers added. No need to use such protections anymore.
10. Language packages sorting function added to CIF/SOF editor.
11. RGU: Now OSB ignores most of errors OEMs and MS got used to.
12. SLDR certs edit button.
OS Builder V1.3.199 FULL (09.12.2011)
Code:
1. Removed NBH dialogue, which earlier could be called during the ROM building (correspondent checkbox and timer are removed from settings)
2. Context menus allowing moving packages are added to the Packages.sof / cif Editor.
3. The possibility to drop packets (drag and drop) is added to the Packages.sof / cif Editor. Drag and drop mode button switch is in the toolbar (see tips). In drug-n-drop mode packets multiple files selection is unavailable, you can drag and drop the package from the right side to the left or move the package to the left.
4. The ability to dump the IMGFS section file is added in Dump Tool (for example - one extracted from the ROM imgfs.bin)
5. HTC NBH Extractor tool is added to the built-in utilities. Use it to extract sections (nb files) from NBH file. See menu Utilities-> Built-in (Menu Tools-> Built-in)
6. The ability to display and handle package flags Reserved, Uldr / Sldr, Regular, etc. is added to DSM Editor.
7. The ability to extract SLDR1/SLDR2 packages from template to ROM \ SLDR folder is added (See additional. Tools-> Templates)
8. The ability to automatically rebuild SLDR and add custom certificate to its dat files is implemented. SLDR can be rebuilt either from template or from packages in your ROM \ SLDR folder.
9. The ability to save the module as a file MNGE is added in the ModuleInfo (see Toolbar ModuleInfo). You must specify the Vbase module address with which it is stored in MNGE in the dialog box before saving it.
10. The ability to apply a DIFFBIN patch is added to the ModuleInfo (see Toolbar ModuleInfo). Before patching you must specify the address of the module Vbase for applying the patch in the dialog box.
11. The ability to write a file in MNGE format is added in FileInfo (file is implicitly converted to a module and then stored in MNGE format). Original will stay unchanged, if you don’t specify Replace the original file in Save File dialogue.
12. Added the ability to build the file NB (D000FF) with sections written in the DIRECT_MAPPING form. This process uses only the template, so the base NB file is not needed. This method improves ROM performance. I want to warn you that updates (cab) in this case will setup slower, but thanks god – we don’t have them every day. The corresponding checkbox can be found in ROM files and Formats settings.
13. Added the ability to upgrade the kitchen packages directly from cab files (see Additional Tools). You can update all the packages except Reserved. While upgrading first packages versions will be verified the and in case of successful validation updates will be permitted. In any case, it is recommended to do kitchen Backup before upgrading. If the updates contain Canonical packages, which just added to the kitchen but do not replace existing packages, then after the update it is recommended to check packages .sof / cif
New tutorial video about pakages.sof/cif editing can be found in the first post
OS Builder V1.3.189 FULL (08.11.2011)
Code:
1. For WP7 devices: added the ability to build the LOGO partition from custom BMP, JPG or PNG files, and to substitute original LOGO partition of ROM (in the D000FF container ).
To enable Custom Logo - go Settings/Build Dump and ROM and toggle the appropriate checkbox. Also specify custom image file(s) you are going to use in LOGO. Pictures should have a resolution 480x800.
2. Fixed a bug that could occasionally appear when porting / rebuilding NK WP7 - post [URL="http://forum.xda-developers.com/showpost.php?p=19149336&postcount=50"]http://forum.xda-developers.com/show...6&postcount=50[/URL]
OS Builder V1.3.187 FULL (03.11.2011) - supports WP7 ROM building
Code:
1. Fixed issue with deleting a parameter defined in boot.rgu, if the removing directive was stored in other packages - the post http://forum.xda-developers.com/show...&postcount=564
The second step to full WP7 support
2. Relocation engine is totally redesigned. (Hats off to Ultrashot for valuable help with WP7 modules Z .reloc sections)
3. Added possibility of porting/rebuilding XIP (NK) and the assembling IMGFS partition file for Windows Phone 7 with real registry recompiling and relocations according to WP7memory model (tested on HTC HD2, HTC HD7 and HTC Mozart. Credit for tests goes to Feropont and HD2Owner)
I want to warn that the registry files have to be checked by registry preview, because there is a hell of syntax errors in the original registry. Frankly, it seems (IMHO) that first the registry was generated and then some comments for dumb and mistakes were added.
Registry Preview will define incorrect lines to help you to fix that. The most common errors are:
- Parameter name without the quotes
- The comments are not marked with a semicolon or marked with colon.
- HEX type values end with point (the last or the only parameter line)
- The value MULTI_SZ contains comments between the lines parameter
- Existence of Directives for conditional compilation IF ... END (it's not a mistake, but currently these directives are not processed, so you should label them as a comment)
4. The dsm-editor has now the feature to set/clear Z-flags for modules.
Warning! This flag is used for WP7 XIP modules only if the RW section of a module must be located within the boundaries of RAMStart-RAMFree (nk.exe, kernel.dll, kitl_noplat.dll and similar)
5. For WP7 - Added ability to edit the file MsDefaultcerts.dat (see Additional Tools)
6. For WP7- Added ability to edit files CoreOS.dat and initobj.dat (see Additional Tools)
7. Added ability to automatically insert a certificate which will sign files while assembling DefaultCerts.dat and MsDefaultCerts.dat (for WP7) - see the settings in Build Dump and ROM. The original files stay untouched.
8. XIP Port settings - added the list of additional MS packages (for WP7). When porting WP7 XIP, the packages specified in this list will be replaced with donor packages.
At the moment, we can safely add the following packages to this list:
BaseDrivers_NK
CCFGSVC
GFX_NK
KFPCRT
Watson_Core
WinCENLS
9. In Configuration and packages tab of Setting - added the option "Always include 0409packages." If your WP7kitchen allows the language selection, it is recommended to use this option enabled to include English-language packages by default to your ROM, otherwise there is risk to get non-bootable ROM.
10. Added - the ability to build NB files (! For the moment only D000FF container !, NB assembling for the new _wmstore structure devices is not supported yet) and NBH files for WP7
To build NB you should have the original NB and should define the way to it in Build ROM settings, for example ".\NB\OS.nb". Unfortunately, to get rid of the original NB is not yet possible, but the work is in process. Hats off to AnDim for help and information provided. NBH build configuration settings are similar to the previous version, except that the CID tab can contain multiple values (each value in a separate line)
Warning! If you plan to use for cooking WP7 dump obtained by earlier versions of OSBuilder, I would strongly recommend you to dump again, and to copy the new ROM template \ ROM.tpl to your kitchen. The new template will contain additional service information, which was not recorded in earlier versions of OSBuilder
11. OSBuilder is fully backward compatible with WM6.x kitchens, (it was a big deal btw, but it was implemented). When you open the kitchen OSBuilder automatically detects the required mode WM6/WP7.
This compatibility will remain for the future, but no new features for WM kitchens will be added. OSBuilder WM Kitchens Development is terminated due to the termination of WM6.5.x development from MS side.
Thanks again to the team (AndrewSh, Feropont, Vladimir1973) - for the support, for the tests, for your work!
Special thanks to HD2Owner for enthusiasm and his titanic work in testing WP7mode.
Thanks a lot to AnDim for his tenderness and important information provided.
Sincerely,
Barin and Ultrashot
OS Builder V1.3.163 FULL (29.09.2011) - supports WP7 ROM dumping
Code:
1. The first step to full WP7 rom assembling support - Added ability to dump HTC WP7 ROM (either with the FLPART structure, or with _wmstore structure - like Eternity or Omega roms).
Advanced Dump Tool also supports extracting sections, packages, modules and files from WP7 (HTC) ROM file.
WARNING! DO NOT ATTEMPT TO ASSEMBLE WP7 ROM WITH OSBuilder OR TO USE TPL Builder TO CREATE A WP7 TEMPLATE!!!
Special thanks to: AnDim, AndrewSh, Ultrashot, xb0xmod (xda)
CHANGELOG (web translation)
OS Builder V1.2.157 FULL (20.09.2011)
Code:
1. Added possibility to convert files to modules for WP7 files
2. To FileInfo menu - added possibility to convert file to module at a place (replacing file by the module or saving module to any folder/disk and leaving the file untouched).
3. Added possibility to select separate packages in XIP (drag and drop into the tree to select the package). This feature is recommended in case if XIP is assembled from packages in your ROM folder, or the packages from ROM folder are used as your OEM XIP
4. Added possibility to compress separate XIP objects. That feature reduces the amount of Physical Space and thus it can free-up some RAM. To specify that you want to compress an object, you must set up Flag C (full file or module compression) or Flag R (compression of all sections of module except those containing code) in DSM Rebuilder/Files and Modules tab.
Setting the Flag C for the filesys.exe module – works without any problems
Setting up C flag to the other modules can cause un-bootable ROM.
Example for LEO (tested on several devices):
Do not even touch dlls marked with Flag K
Code:
----------MSXIPKernel----------
For all files - Flag С
Modules:
coredll,dll - Flag R
device.exe - don’t touch
filesys.exe - Flag C
imgfs.dll - don’t touch
initvmmap.exe - don’t touch
regenum.dll - don’t touch
the rest of dll - Flag R
----------OEMXIPKernel----------
For all files - Flag С
Modules:
nk.exe - don’t you even think about touching it!!!!!!!!!!
cecompr.dll - don’t touch
QCBPM.dll - don’t touch
rpc_pmem_client.dll - don’t touch
wce_pmem.dll - don’t touch
the rest of dll - Flag R
----------WinCENLS_WWE----------
wince.nls - Flag С
With that above mentioned settings and squeezing nk RW sections in RAM – about 0,5 Mb of Program Memory (RAM) was added.
Changelog for OS Builder V1.2.153 FULL (15.09.2011) - now with XPH support
Code:
1. While registry preview or rom-cooking: if reg settings are not tied to a key (after removing the key directives), a comprehended syntax error indicating the line is displayed
2. Reloc engine is modified – now Reloc and Recmod is supported for WP7 Modules (REVERSMOD – still under development) for all new fixup types (3 - IMAGE_REL_BASED_HIGHLOW, 5 - IMAGE_REL_BASED_ARM_MOV32A and 7 - IMAGE_REL_BASED_ARM_MOV32T)
3. Added support for XPH compression - see the settings in Build Dump and ROM.
! ATTENTION!
To enable XPH compression – you would also replace cecompr.dll for that library in XIP.
It’s cecompr.dll ported from Mango WP7.1. Guy in charge – ultrashot (who doubts?) Thanx to him for fixing ordinals in the import table for WM6.5 compatibility.
Warning! This library contains the ARM v7 instructions, so it will only work on devices that support these instructions ( particularly on devices with a processor Snapdragon - like HTC HD2)
OS Builder V1.2.148 FULL (04.09.2011):
Code:
1. IMGFS assembling engine now supports paths and object names in UNICODE. (Hats off to ultrashot)
2. Several internal fixes (not visible from UI but important)
OS Builder V1.2.143 FULL (28.08.2011):
Code:
1. The item ZeroLength is added to UL partition drop-down menu (Settings\ Buid Dump and Rom) - ULDR partition is physically removed, but the record about it remains in the Partition Table (SectorsBefore = 0; SectorsCount = 0). In my opinion this is the most viable option for the removal of ULDR. (Here "my opinion" means the opinion of Barin but I would say that this feature removes a lot of bugs - especially if you build so called "empty" roms).
2. The option "Remove flag IMAGE_SCN_COMPRESSED" is added to Advanced IMGFS compression options. This option helps to avoid the idle invocation of the function CEDecompres and thus speeds up the loading of modules.
3. The check-box “Group modules at the beginning of IMGFS partition" is now available in Settings/Build Dump and Rom. Don’t use this option cooking for 6.0-6.1 nk devices and old devices. Good for Leo and other stuff like that. (feature is checked by Barin - for Asus P750, ultrashot - for X1, me - for Asus P525)
OS Builder V1.2.140 FULL (21.08.2011):
Code:
1. The random bug occurred sometimes while cleaning code from resource files - fixed
2. The code of several dlls and executables contains the useless invocation of CePerf.dll (module containing functions of monitoring and logging performance) - needed for debugging purposes only. This test fails to generate results if CEPerf.dll - dependent logging library - is missing. As far as we operate with ready MS Build - we don't need it. But this useless invocation spoils system time and resources. (The idea and cleaning algorithm - by ultrashot)
So now it's possible either to completely remove CEPerf.dll invocation from all files and modules containing it, or do it on the fly while assembling rom (leaving the original files untouched).
3. Earlier it was possible to manually add BuildImgfsGroupModules parameter to osb file to regularize modules and files in IMGFS. Now it's a default feature - while assembling IMGFS first all modules are processed, than all files...
4. When "Merge all Packages to one" option is toggled - registry assembling is highly optimized.
OS Builder V1.2.133 FULL (11.08.2011):
Code:
1. The ability to digitally sign cab and tsk files while assembling the rom (as it was for executable files in previous versions) is added. You can add cab or tsk files to the “sign files” list to sign files either manually or using the context menu of the package.
Not only target file itself is signed, but also all executable files inside it. The originals (source files) stay untouched.
2. The tool Cab/Tsk Signer is added to built-in utilities. With it you can sign cab and/or tsk files.
You can select either a single file or all files in a folder. It is possible to create a cab file to install the certificate, as well as the opportunity to add a certificate in _setup.xml of the cab file.
3. The item ‘Quick registry assembling” is removed from Settings/Build DUMP and Rom if packages are merged. Now this option is hidden but selected by default. If Merge All Packages to One checkbox is toggled - the rapid registry assembling algorithm will be executed. If this checkbox is cleared – registry assembling will be usual (old-fashioned).
4. The ability to sort / clean rgu files is added. Provides sorting/cleaning either the separate package rgu (via the package context menu), or all rgu files in the kitchen with a possibility to make a choice between EXT, OEM, ROM and SYS or all of them (Additional Tools-> Cleanup-> Sort / clean files rgu).
While sorting / cleaning process: double values will be removed from rgu (in case of different values of the same parameter the last value will be saved, as during the regular registry assembling), the removal directives for keys and values will be moved to the beginning of the file. Keys and values are sorted alphabetically.
If the key and value with OEM version (HKEY_LOCAL_MACHINE \ SOFTWARE \ OEM \ MASD) is present, it will be moved to the end of the file.
IMO optimized by this option rgu files are much more readable.
Remember that when sorting/cleaning rgu all comments will be deleted!
5. While installation OSBuilder sets association with hv files. You can open it for viewing just double-clicking it in Windows Explorer.
6. Registry comparer is added to Tools/Built-in. It can compare the contents of rgu and hv files, export to rgu either separate keys, or the difference obtained when comparing files.
OS Builder V1.2.124 FULL (28.07.2011):
Code:
1. Fixed some minor issues in Complex RGU
2. Added new features in IMGFS assembling - completely redesigned (actually written from scratch) utility for IMGFS assembling (Hats off to ultrashot for that work) .
In the configuration menu: added item "Advanced IMGFS compression options" (with a list of files / modules and additional compression options for sections in modules). Modules / files included in the list – will appear non-compressed in IMGFS. There is also a possibility to search and add all graphic manila files to that list (with signature QTC1)
Building the list - it’s possible to use templates, such as *.png, *.jpg. If someone wants to build a fully uncompressed section, just type *.* in the list.
Additional options of the modules sections compressing allow you not to compress the separate module sections containing code and / or RW sections of all modules, regardless whether they are in the list or not.
It’s also possible to control the compression of files/ modules setting flags U, R and S.
R flag can be used only for the modules. Flags U and C can be used for both modules and files. Flags in dsm have a higher priority than the list of Advanced compression options.
If you set U flag for a file or module in dsm editor, that file or the module will not be compressed in IMGFS not depending upon whether it is in the list or not.
If you set R flag for a module in dsm editor, then only the resource section of this module will be compressed in IMGFS.
If you set C flag for a file or module in dsm editor, the file or module is fully compressed in IMGFS not depending upon whether it is in the list or not.
Setting all flags U, R and C for the same object is not allowed. The built-in dsm editor will return warning.
The flag C has the highest priority among the flags.
3. In the configuration menu: added item " ?????? Demand paging ??? ???????." – sorrowfully it’s not correctly translated into English – will be fixed later. That means: The prohibition of "Demand paging" feature for modules.
The flag IMAGE_SCN_MEM_NOT_PAGED will be set up to the headers of modules in that list and also it will be set up to the modules with M flag in dsm
Wildcards such as *. exe are allowed in the list.
4. The item "Compress XIP even if it is not compressed in the ROM template." is added to Settings/Build Dump and Rom (reduces rom size for 1,6 Mb)
OS Builder V1.2.116 FULL (27.06.2011):
Full version - to the masses
Code:
1. In the Personal Data Generator in Wi-Fi setup added WPA2 and WPA2-PSK
2. In add. configuration property added to the item "Remove the attribute R with non-executable files." Attribute is removed directly into the headlines IMGFS (the originals stay untouched). The idea belongs to the distinguished Ultrashot.
Those who are transferred from the LE version to the FULL, be sure to read the post http://asusmobile.ru/board/viewtopic.php?p=336183 # 336 183
OS Builder V1.2.111 (08.06.2011):
Code:
1. Added scroll bar of the window of exceptions (the settings dsm) - Post http://asusmobile.ru/board/viewtopic.php?p=332069 # 332069
2. In the Personal Data Generator element in the list is opened for editing, not only the context menu, but doubleclick - post http://asusmobile.ru/board/viewtopic.php?p=332069 # 332069
3. To Dr.Freezer icon_smile - In the section [PortEngine] option has been added XIPPortKeepMSXIPDsm (default = False). When set to True XIP'a assembly is similar to version 1.2.1981 and earlier.
FULL VERSION:
4. When you open the list to set the flag in the configuration menu SHARED warning is issued only once per session
OS Builder V1.2.107 (05.03.2011):
Code:
1. Fixed a glitch with the cleaning of temporary folders in the Temp - post http://asusmobile.ru/board/viewtopic.php?p=331389 # 331389
2. Improved Personal data generator. If any field in the tab "Owner" does not fill these fields in the registry is not set to zero - a post http://asusmobile.ru/board/viewtopic.php?p=331437 # 331437
3. The path to the configuration file is transferred into an environment variable _CFGFILE (if the file exists)
4. In the configuration file in section [OSBuilder] option has been added WriteLogsToLOGFolder. If it is set to True, the log files will be written in assembly LOG folder in the root of the kitchen. The folder will be created automatically.
At the beginning of the assembly, this folder will be automatically cleared to logic from different assemblies are not mixed together. I consider this feature useful if enabled Auto clear folder TEMP.
5. Accelerated preprocessing (in the case of rewriting a large number of modules / files)
6. Fixed a throwback to boot.rgu - post http://asusmobile.ru/board/viewtopic.php?p=331579 # 331579
IMHO at this point has long been unnecessary, because the packets from XIP'a be learned all at once.
7. In the setting of the assembly item is removed, "an error message in case of duplication of files and modules for rewriting. By paragraphs "Override automatic ..." and "Confirmation".
8. Hung on the F5 key update, but at the start of the assembly F7
FULL VERSION:
9. Improved Complex RGU. Now you can view the remote key (Screenshot)
By doubleclick file is opened or rgu provxml, which removes the key. By pressing a button at the end of the line will state the key at the time of removal.
Switch to normal or deleted keys is carried out in the menu "View -> Remote Keys"
10. Fixed problem with saving the list of modules unmovable.
11. In the package for recmod allowed any modules, regardless of the settings
12. In Module Info / File Info added ability to set / unset the flag for the SHARED section RW. Author of ideas - respectable Ultrashot. All actions at your own risk.
13. In the configuration menu added to the list to set the flag for RW SHARED sections and modules. In assembling all files in / modules list will be flagged for RW SHARED sections. The originals are not touched.
14. In setting the item was added to "sign the files from the list of SHARE RW". No comments.
During the test items 12-13 special thanks Alexx ~, AndrewSh, Ultrashot, Vladimir 1973
OS Builder V1.2.101 (21.02.2011):
Code:
1. Fixed minor issues if OsBuilder is used in multilingual mode (several configurations for several rom languages)
2. Added the possibility to run SINGLE exe file with arguments while device first boot. Exe file will be executed after importing other Personal settings. The execution order corresponds to the order in the list.
3. Fixed English interface issues in Personal Data Generator
OS Builder V1.2.99 (19.02.2011):
Code:
1. Fixed package description window size (5 lines, 120 pxl)
2. Built-in HTC Splash Tool added - you can create Primary и Secondary boot Splash WVGA (480x800) in NB or NBH format. You can also extract image from NB splash. See Menu Tools -> Built-In.
3. Built-in HTC NBH Builder Tool added
– allows to create NBH file from NB files. You can import NBH header parameters from settings, registry or NBH file. Files and code sections are added and deleted using the context menu.
Sections, which should be included to NBH must be toggled in checkboxes. You also can save your settings in a separate file. See the menu Tools -> Built-In.
4. For HTC-LEO - in case when the date and time sync failed on first start - date and time of the ROM creation will be added.
5. Several improvements in assembly and merge dsm algorithm
6. Fixed a problem with new versions of Yandex-maps
7.The option RomConfirmOverwrite has been added to the section [OSBuilder] of configuration file. If the parameter = False, then the assembly of the ROM process does not display “Over-write?” dialogue (the file is automatically overwritten). By default, this option is True
8. Built-In Personal data generator tool is added
– see Additional Tools - Personalize. You can pre-enter owner name, Wi-Fi settings, mailboxes, VPN connections and favorites.
You can add, delete and change personal data by using the context menu.
Favorite links found in OEM provxml files are added automatically to the top list. Toggle correspondent checkbox if you want them to be added to Favorites. You can add your custom Favorites in the bottom list via context menu.
Personal data is stores in the root of OEM folder in the file Personal.dat. You can save it in menu File->Save to OEM.
To integrate your personal data to your custom rom you should go to Configuration Menu->Advanced Settings->Write Personal Data (toggle checkbox)
Full version:
9. Added the possibility to save personal data (paragraph 8) in a readable xml (provxml) file.
Keep in mind that not all data can be imported during provxml runtime.
OS Builder V1.2.89 (31.12.2010):
Code:
1. From tuning of assembling XIP' and are removed the points of the removal of the files of dsm and other files of rgu. The files of dsm and rgu (besides boot_ms.rgu and boot_oem.rgu) are moved away depending on the state of the button of the association of packets into one in. If it is selected to unite packets into one, then with XIP' and dsm and rgu from it will be removed. You remember that if you will use XIP with completely [udalennymi] of dsm in other kitchens, which do not consider the absence of dsm in XIP' e, then in the window Of about (information about the system) in you can be absent version OS CE!
2. In the window with the list of modules L is added the contextual menu, which makes it possible to open module or file of dsm, in which is contained the record about the module. Also with the aid of the contextual menu it is possible directly to establish or to remove flag L into dsm for the selected module
3. On the request is added the possibility of cleaning the resource modules/of files directly in the kitchen, but not only during the assembling. You be attentive! Confirmation will be inquired only one time, the then selected originals will be purified.
4. Is corrected omission into DumpTool - post [url]http://asusmobile.ru/board/viewtopic.php?p=325559#325559[/url]
5. In the form of cleaning the files of manila is added contextual menu (Select of all, Invert of selection)
6. In the form cleaning the files of manila is reflected only those languages, whose files are not located in the list of the exceptions of configuration.
7. In the form of the list of exceptions for the configuration is added the button of " To remove from the list the files of *manila"
8. In the self-correction of dsm it completed the correction of versions. Are corrected both the versions of packet and its interface and the versions of dependences. Are corrected all packets in SYS, ROM \ OF XIP, and also OEM_*, OEMDrivers*, LangDb. In the packets, which relate to OEM the number of [bilda] is set equalequal to zero. [Defoltnye] data for the version are formed in the dependence on the tuning DSM (on silence they are taken from the packet OS)
9. Now and into [pablik] of the version: Quotation: In Dump Of tool is added the additional tool, which makes it possible to extract divisions, packets, modules and files directly from the file ROM ([Skrinshot]1 Of [skrinshot]2 Of [skrinshot]3) COMPLETE VERSION:
10. In addition to point 3 is added the possibility of the signature of the purified files by certificate (point of contextual menu)
11. Is added the possibility of the auto-signature of the files of resources, purified during the assembling. See tuning the assembling dump and ROM
OS Builder V1.2.81 (06.12.2010):
Code:
Attention! Beginning from the current version Of oSBuilder it is re-aimed on .NET Of framework 4.0. See large [kra]c[nye] letters in the cap
1. the problem, connected with the list REVERSMOD - post [url]http://www.mobileunderground.info/showthread.php?t=12348&p=60619#post60619[/url]
2. the problem, connected with the record of the files of tuning the configuration Of oSBuilder' and into the dump - post [url]http://asusmobile.ru/board/viewtopic.php?p=323581#323581[/url]
3. Is corrected omission into ComplexRGU (parameters Of default and @ they are processed as one parameter. Earlier in one key was possible mapping @ and Default as the different parameters). With the search for the parameter Of default in the line of search can be introduced both Default and @
4. The editing of dsm of packet is additionally hung to the key F3
5. Rewrote in its own way RECMOD (earlier it was used " classic"). Now modules analogous (SkyBox) [rekmodyatsya] without the problems.
6. The search for the lingual files of Manila (for the exception or the removal) is substantially accelerated
7. In ModuleInfo is added the information about the imported libraries (given they are taken on the basis ImportDirectoryTable) and a quantity of the exported functions
8. Is added the possibility of retrieval for line and binary data in the files and the modules . Binary data can be searched for including on the pattern - the insignificant byte is designated by two signs of a question. The window of search is caused from the panel of tools (window of log' a) for the search in all files/modules, or from the contextual menu of packet for the search only in the selected packet.
9. In Dump Of tool with the discovery of file ROM the information about the packets is read now without the preliminary extraction of flat dump, that healthily economizes the time. In the panel of tools it is possible to select, what precisely dump must be obtained, flat, or immediately decomposed on the packets.
10. In Dump Of tool is added the possibility of the extraction of sections NB from the file NBH, if for the dump was selected file NBH
11. All tuning Of dumpTool are written in the list, but not into the file of osb
12. It built in the library of msvcr71.dll [installyator] (it is established automatically in the same folder, as OSBuilder)
13. In the additional tools added the search for modules L modules search for in all packets. As results of search show the modules, which are located in slot 0 the modules, for which is established the flag L into dsm. [Dablklik] on the module causes ModuleInfo
14. Wrote the component PE Of file Of info it derives information about the usable file (Headers, Sections, DataImageDirectories, etc.)
15. In the menu of configuration is added the list of resource files and modules, which must be cleaned during the assembling (it will be left only the section of.rsrc). The principle of cleaning is examined respected Of ultrashot' ohm in the separate theme Files and modules can be added in the list both by hand and the aids of additional tools (cleaning -> To remove the code from the resource files). In this case will be automatically brought out the list of all mui of the modules/of files. Addition/allotment from the list is produced with the aid of the contextual menu. Certainly before adding module or file in the list, should be focused attention, does export functions the selected module or file and that this for the functions. On double-click it is opened BY PE Of file Of info or Module Of info (depending on object). Cleaning occurs in the process of assembling. The originals in this case remain unchanged
16. Everyone of " " functions (cleaning modules, cleaning Manila and cleaning resources) are now grouped in one point of the add. of tools - cleaning. COMPLETE VERSION:
17. In ModuleInfo is added the possibility of the reconstruction of file directly into the folder of module, or into the folder on the selection.
18. In ModuleInfo is added the possibility of the survey of the tables of import and of export
19. In PE Of file Of info there is a possibility of the survey of the tables of the import/of export by analogy from Module Of info
20. As results of search from the contextual menu it is possible to open the obtained file/module by analogy with the window of packet
21. In the contextual menu of packet is added the point of " To verify dependence on the files/of [moduley]". With its aid it is possible to verify the direct and inverse dependences of the usable files/modules of packet on the usable files/of the modules of other packets. In the left window the list of the usable files/of the modules of packet is shown. In the average window is shown the list of the files/of modules on which it depends the selected in the left window file/module. In right window showed the usable files/modules which they depend on the file/of the module, selected in the left window. 1 and 2 Dependences are built EXCLUSIVELY! on the basis the tables of import.
22. In Dump Of tool is added the additional tool, which makes it possible to extract divisions, packets, modules and files directly from the file ROM
23. In addition to mui (point 15) into the window of the files/of modules are derived dll, that import not more 2nd functions and exporting is not more than 1. if the import of [idet] from mscoree.dll (.NET CF), then this dll in the list is not derived.
24. To add/to remove file or module in the list for the cleaning is possible with the aid of the contextual menu in the window of packet ([Skrinshot]) Are added in the list or removed from the list they can be only dll and mui.
OS Builder V1.2.64 (26.10.2010):
Code:
1. Is corrected the problem, which appeared when the size of the logic unit of [ravern] to the size of sector - post [url]http://asusmobile.ru/board/viewtopic.php?p=322363#322363[/url]
2. With the creation of template from the file ROM (including with the dump), in which is present initialized FAT32[b] now always they are considered tuning FAT32
OS Builder V1.2.62 (25.10.2010):
Code:
1. In cmd-file, which is carried out at the end of assembling XIP' and the variable environments are transferred
2. In the menu of configuration is added the point of " To rename packets on the names of [papok]" - in the configuration will be renamed the grouped packets (files of dsm they do not change) - post [url]http://asusmobile.ru/board/viewtopic.php?p=321278#321278[/url]
3. In the contextual menu of packet is added the point of " To appropriate to packet the name of [papki]" - it works by analogy with point 2, only for the single packet. The dialogue of confirmation in this case is not derived - renaming occurs immediately.
4. Is added the support O2 Of xda Of zinc (theoretically)
5. Trifle, but… In the basic ravine after [reloka] is derived the information about the vacant place in slot 0
6. Are added several parameters into the file of osb, which are concerned forestalling reading of packets (possibly Scanning can someone strain, or to someone it is not simply necessary with the presence Of core i7 and OF RAID 0 of SCSI or SAS of disks). In the section [Of oSBuilder.Trees] Of nodesEnableStartupScan - it solves either forbids forestalling reading, NodesScanModules - it solves or it forbids forestalling reading of modules, NodesScanFiles - it solves or forbids forestalling reading of files.
7. Wrote its dumper IMGFS (at long last it got rid of ImgfsToDump). If in someone was the problem, described in the post [url]http://asusmobile.ru/board/viewtopic.php?p=321427#321427[/url], then it must disappear (i have this problem it was not observed).
8. [Pofikseny] any trifles
9. [Izmenen] the cursor of assembling - files now in TEMP are not copied (with exception of those, which must be signed or reconstructed from the modules) Attributes are observed (about the attribute R now it is possible not to think generally), original files they do not change. Also [izmenen] the sequence of files and modules in IMGFS (for help the enormous thanks of airextreme)
OS Builder V1.2.50 (05.10.2010):
Code:
1. With preview of the list of rgu and provxml they are checked against the exceptions. If the file of rgu or provxml is present in the list of exceptions, then data from it will not be imported for [predprosmotra] - post [url]http://asusmobile.ru/board/viewtopic.php?p=319740#319740[/url]
2. Is solved problem with UL in the assembled by hand template - posts [url]http://asusmobile.ru/board/viewtopic.php?p=313397#313397[/url] [url]http://asusmobile.ru/board/viewtopic.php?p=313554#313554[/url]
3. Are removed the tuning, which relate to .VM and .ROM - now .VM and .ROM automatically are corrected or are created on the basis given XIP
4. Is [optimirovan] the algorithm of assembling the file of division IMGFS and files ROM NB0 (payload), nb and nbh
5. Is added the possibility ofredirection of folder TEMP - see tuning - > Packets and configuration ([Skrinshot]). For the folder TEMP are permitted ONLY absolute ways! [Perenapravlenie] of folder TEMP to RamDisk can substantially accelerate the process of assembling. For the optimization of the use Of ramdisk is added [chekboks]. If it is noted, then in the process of assembling temporary components ROM will be automatically moved away. Both these tuning are written in the list, but not into the file of osb!
6. For the use in [komandnikakh] is added the variable of the environment of _TEMPDIR (complete way to the folder TEMP)
7. Is added the possibility of " fast" assembling list - see tuning dump and ROM. Significant acceleration is perceptible with the large number of packets (but respectively the files of dsm and rgu). The parameter works only when selected the association of packets into one (in the tuning or in the panel of the tools of builder). If the rapid assembling of list is selected, then it is better to first ascertain that the files of list do not contain errors, for example to cause the preliminary survey of list.
CHANGELOG (web translation)
OS Builder V1.2.43 (24.09.2010):
Code:
1. Is corrected situation with the search for values in the list (Complex RGU) - post [url]http://asusmobile.ru/board/viewtopic.php?p=318704#318704[/url]
2. Is added the support Of hTC-RhodiumW (date and version into nk.exe)
3. Is added the possibility of correcting the version ROM for HTC Of touch HD (only for nucleus 6.5)
4. On the especially persistent requests is added the possibility of the complete removal of folder TEMP at the end of assembling and copying file ROM from TEMP into the folder on the selection. C[m]. Tuning dump and ROM - > Sizes and the designation of files ROM
5. Is added the possibility of the conversion of initflashfiles.dat from delirium (codes of the symbols of unicode) into the usual text. See additional tools - > Initflashfiles.dat
6. Analogous possibility is added into DumpTool - with the forming of the packets of initflashfiles.dat it can be automatically converted. See tuning - > Dismantling of dump.
7. Is added the possibility of the record of the tuning and configuration, with which it is gathered BY ROM, directly in ROM - post [url]http://asusmobile.ru/board/viewtopic.php?p=318987#318987[/url] After the starting of [devaysa] the files will be located in the folder Windows \ Of oSBuilder. See tuning dump and ROM
8. Are a little changed tuning NBH - now it is possible to add several components (sections) of piercing in the list and to note for the assembling only necessary ([skrinshot]) - see tuning dump and ROM - > Sizes and the designation of files ROM
9. Is added [vozmnozhnost] of dialogue during assembling of nbh for the selection of the components of [sm].[Nastroyki] of dump and ROM - > Sizes and the designation of files ROM) - post [url]http://asusmobile.ru/board/viewtopic.php?p=319418#319418[/url] In this dialogue it is possible to select for the section of piercing only. (Version, CID, Lang and so forth cannot be changed - they they are derived only for the information)
10. In the tuning is carried out control of all timers (specially for those, who their " dully [sozertsaet]" - is given quotation from post 319679 - and it does not read changelog). If is selected checkbox of " [Otklyuchit]" (value of timer it is automatically set equalequal to -1), then process it will expect the reaction of user - pressure OK, cancellation so forth if the value of timer is equal to zero, process begins immediately.
11. Is added the possibility of removal of files with unnecessary languages from packets of Manila Files it is possible either to add in the list of exceptions or to physically remove from the disk - see additional tools - > Manila
12. In last [komandnik] is added the variable of the environment of _ROMVERSION - version ROM in that form, as it appears in ROM Of builder' e. if in ROM Of builder' e version ROM is not reflected or empty, then variable _ROMVERSION into [komandnik] will not be transmitted.
13. Is added support SE X1 (HTC-Kovsky, date and version ROM) COMPLETE VERSION:
14. Is corrected problem with the auto-signature of the files Of custom by certificate with the work of program in Windows XP.
15. In the editor of iniflashfiles now can be transferred the number of line, for example with the preliminary survey of files. Example of tuning for notepad2 - " C:\Program Files (x86) \ Of notepad2 \ Of notepad2.exe" /g %2 " %1" - if in the command is present argument %2, then it will be [zameshchen] the number of line (with the usual discovery of file - [nulem]).
16. Is added the possibility of [predprosmotra] of files - is analyzed initflashfiles.dat initflashfiles.txt in the selected packets. Window is analogous with the window Of complex RGU. The command is reflected during the guidance of cursor to the number of line in the right lower part of the window. On double-click on the line is opened corresponding initflashfiles (dat or txt)
OS Builder V1.2.35 (10.09.2010):
Code:
1. Added ability to import settings from a file osb and export settings to a file osb - see Settings -> Packages and configuration
2. Add-in DumpTool: if layout dump the packets to the root of a new kitchen is recorded file OSBuilder.osb c default settings. If the dump file is derived from NBH, then OSBuilder.osb will contain all necessary information for an assembly file NBH (CID, version, Lang, model, data block size and code sections, OS)
3. Fixed a problem with the search date and version in ROM XIP'e HTC HD Mini
4. Fixed bug DSM Editor context menu when running in Standalone mode - post http://asusmobile.ru/board/viewtopic.php?p=318529 # 318529
5. Fixed bug in DumpTool (Automatic generation of a template for the dump nb0 (payload), nb, nbh) - Post http://asusmobile.ru/board/viewtopic.php?p=318554 # 318554
FULL VERSION:
6. Added ability to save settings in the registry editor and the possibility to import these settings from the registry - see Editor Options
OS Builder V1.2.32 (07.09.2010):
Code:
1. Added ability to copy the ROM file to a folder of your choice. See assembly dump and ROM-> formats and file naming.
2. In DumpTool added output vesii OEM package (key HKEY_LOCAL_MACHINE \ SOFTWARE \ OEM \ MASD), if it is registered in rgu package
3. Fixed bug in ComlexRGU - post http://asusmobile.ru/board/viewtopic.php?p=318367 # 318367
4. Fixed a glitch that caused crash if OSBuilder running on a computer with a single core processor.
5. Corrected entry routes in the settings
OS Builder V1.2.30 (06.09.2010):
Code:
1. Corrected parser provxml, so no problems with Int / UInt - post http://asusmobile.ru/board/viewtopic.php?p=312974 # 312974
2. Corrected the situation with the utility menu User - post http://asusmobile.ru/board/viewtopic.php?p=313364 # 313364
3. Fixed bug - when creating a group at the root of the tree was necessary to press the refresh button to make the shortcut menu for the new group - the post http://asusmobile.ru/board/viewtopic.php?p=312987 # 312987
4. Corrected spelling while maintaining dsm without certification - a post http://asusmobile.ru/board/viewtopic.php?p=314564 # 314564
5. If you check for files and modules in the editor dsm hand icon file or module is updated in accordance with the flags - the post http://asusmobile.ru/board/viewtopic.php?p=314564 # 314564
6. In setting the Dsm added an additional item "When you save a file in the editor DSM automatically set the attributes of S and H for the modules and files in accordance with entries in the DSM"
7. Corrected the situation sometimes arises when you move the group to itself (disappearance)
8. Corrected the situation with the files. Osb - post http://asusmobile.ru/board/viewtopic.php?p=315819 # 315819 (last sentence)
9. In setting the editors added item "Before you edit the file to remove the attribute Read-only". After editing an attribute can not be restored, if necessary, to bring back his hand. Setting up correctly grown for all editors package files
10. In the Registry Editor can now be transferred to line number, for example, when previewing the roster in case of error or when viewing a registry file from ComplexRGU. Example settings for notepad2 - "C: \ Program Files (x86) \ Notepad2 \ Notepad2.exe" / g% 2% 1 "- if a team is present argument% 2, it will be replaced by the row number (the usual opening a file - zero).
11. In ComplexRGU added the ability to export a key in a file rgu (context menu key)
12. Corrected the situation with the files. Osb - post http://asusmobile.ru/board/viewtopic.php?p=315819 # 315819 (last sentence)
13. In the configuration menu added to the list REVERSMOD - files that are present in this list in the assembly will be automatically converted into modules.
14. Added the ability to build a file NB (by analogy with NBMerge or osnbtool-extra) - see Settings dump ROM (formats and file naming ROM), you can also specify the file names nb0 (payload) and nb.
15. FOR OWNERS HTC! - Ability to Build File NBH (Screenshot). Build options (version, language, CID, data block size) can be imported from a factory NBH file or manually. OS, RADIO, SPLASH tested on HTC Leo and HTC Touch Diamond2. Attention! Attention! Code sections (eg 0x400 OS) are not automatically imported, so when you import carefully check box with the data.
16. In setting the item was added to the "Automatically determine the type of nucleus (WM6.1/WM6.5)". If this is checked (and it is selected by default), then choose the type of nucleus in the toolbar will not.
17. In batch files that run before assembly and after assembly ROM, passed environment variables:
_ROOTDIR - Full path to the root of the kitchen
_SYSDIR - Full path to SYS (may be useful in the regime multibild)
_LANG - Selected language ROM, for example 0419. If the setting is prohibited choice of language or language ROM ROM is not defined, then the variable is passed to komandnik will not be
_BUILD - Build number of the dsm package OS type xxxxx, for example 22040. If the package is missing OS or dsm is damaged, this variable is passed to komandnik will not
_INITFLASH - Full path to iniflashfiles.dat (for the selected language)
Example komandnika:
Code:
@ Echo% _ROOTDIR%
@ Echo% _SYSDIR%
@ Echo% _LANG%
@ Echo% _BUILD%
@ Pause
Result:
Code: Code:
D: \ WM_MULTIBUILD
D: \ WM_MULTIBUILD \ SYS \ SYS_23563
0419
23563
Press any key to continue. . . . .
Environment variables can be used to invoke external tools or editors. Just as an example of "Notepad.exe"% _INITFLASH%
Naturally permennye environment can be used if a OSBuilder'e open the folder with the kitchen.
18. In DumpTool added the ability to dump file "turnkey" (menu File-> Open File). Supported formats. Nb0,. Payload,. Nb, nbh.
When you open the file you will see information about it, checked and unpacked section IMGFS and then you will see information about the packages IMGFS, while in the folder where the file will create a folder called ROM Dump. Then, when you click on "Arrange a dump of the packets in the folder Dump will create a folder structure, ready for OSBuilder'a (OEM, ROM c pattern and packages XIP'a and SYS).
19. In setting the parameter "Automatically delete the folder Temp \ Dump and Temp \ XIP in the background." If this option is selected, deleting folders will happen after the assembly file section IMGFS in the background.
20. On the File menu item added "recent" - is stored up to 10 public folders. Last open folder will be the first in the list. The menu item is displayed only when OSBuilder
21. Altered the internal algorithms (all-rounder did not reach) - Open kitchen, Relocation, merging packages is now much faster.
Also slightly changed the build order - register now going before the packages are copied to the Dump, so that if the assembly Registry is an error, it will become clear before it begins copying files.
Only the full version:
22. In the popup menu item was added to the package - Displays a list of files and modules - in the log window displays a complete list of objects in your package. Can be useful eg for lists of files, exceptions
23. In setting the editors added items and HEX editor, resources editor and additional editor (screenshot). These editors can use the box to the contents of the package. In addition HEX Editor can be used in ModuleInfo (dablklik on sections of the module)
24. Added the content window of the package (screenshot) in the style of the conductor (right window can be switched in either log or in the mode of content is really a package). In this window you can delete and rename files and modules, add and remove them from lists RECMOD, REVERSMOD, Auto signature, Slot 0, and edited with podklyuchemyh HEX editor, resources editor, and additional editors. By dablkliku on the module will ModuleInfo. By dablkliku on section modulus section will open in a plug HEX editor.
OS Builder V1.1.5 (24.06.2010):
Code:
1. Removed checking for folders DONOR when rebuilding. Checked only when actual use folders DONOR (porting)
2. Corrected parser registry - a post http://asusmobile.ru/board/viewtopic.php?p=312791 # 312791
3. Added check blank line at end of file rgu preview the registry (see Settings -> Preview Register)
4. Configuration files and settings for the Public and the full version is now fully compatible - a post http://asusmobile.ru/board/viewtopic.php?p=312808 # 312808
5. For a complete feng shui ... if user selected XIP Rebuilding, not ported, then the path to the folder DONOR
OS Builder V1.1.02 (22.06.2010):
Code:
OSBuilder will now only available as an installer. OSBuilder will now only available as an installer.
We strongly recommend not to install OSBuilder the root of drive! We strongly recommend not to install OSBuilder the root of drive! Leave the installation folder, which is offered by the installer. Leave the installation folder, which is offered by the installer.
If you have a previous version OSBuilder'a (1.0.94-1.0.96), delete it manually via the control panel! If you have a previous version OSBuilder'a (1.0.94-1.0.96), delete it manually via the control panel!
Now there is no need for every kitchen to keep exe-Schnick OSBuilder'a and puzzle what version of this file. Now there is no need for every kitchen to keep exe-Schnick OSBuilder'a and puzzle what version of this file. Simply rename the file in OSBuilder.ini OSBuilder.osb and run the kitchen with the help file. Osb, while OSBuilder automatically finds the settings from this file. Simply rename the file in OSBuilder.ini OSBuilder.osb and run the kitchen with the help file. Osb, while OSBuilder automatically finds the settings from this file.
Can be kept in a kitchen, a few files. Osb c different settings. Can be kept in a kitchen, a few files. Osb c different settings.
Can also be used as open kitchen from the menu File-> Open. Can also be used as open kitchen from the menu File-> Open. In this case OSBuilder first looks for an open file folder settings OSBuilder.osb. In this case OSBuilder first looks for an open file folder settings OSBuilder.osb. If no such file exists, will be searched for a file OSBuilder.ini, and if the file OSBuilder.ini be found, it will be renamed OSBuilder.osb and then it will be read from the configuration. If no such file exists, will be searched for a file OSBuilder.ini, and if the file OSBuilder.ini be found, it will be renamed OSBuilder.osb and then it will be read from the configuration. If neither OSBuilder.osb, nor OSBuilder.ini not be found, then create a file OSBuilder OSBuilder.osb with default settings. If neither OSBuilder.osb, nor OSBuilder.ini not be found, then create a file OSBuilder OSBuilder.osb with default settings.
Which configuration file used at this time indicated at the bottom of the window. Which configuration file used at this time indicated at the bottom of the window. Configuration file. Osb, you can edit as well as ini. Configuration file. Osb, you can edit as well as ini.
OSBuilder now supports both Russian and English interface. OSBuilder now supports both Russian and English interface. Language can be selected when you first start. Language can be selected when you first start. The same interface language can be changed in Options - tab "Packages and configuration", click "Select interface language when the program starts." The same interface language can be changed in Options - tab "Packages and configuration", click "Select interface language when the program starts." To change the language interface to close OSBuilder and the next time he will propose to select the language. To change the language interface to close OSBuilder and the next time he will propose to select the language. The language for the program, rather than for specific settings. The language for the program, rather than for specific settings.
When installing OSBuilder automatically create associations with the files. Dsm,. Sof and. Cif, that allows you to edit these files by simply dablkliku in Windows Explorer. (Viewing and editing sof and cif without running OSBuilder'a only available in full version) When installing OSBuilder automatically create associations with the files. Dsm,. Sof and. Cif, that allows you to edit these files by simply dablkliku in Windows Explorer. (Viewing and editing sof and cif without running OSBuilder'a only available in full version)
OTHER CHANGES: OTHER CHANGES:
1. The general assembly of the log is written to the TEMP TEMP folder only if present at the time of writing - the post http://asusmobile.ru/board/viewtopic.php?p=306058 # 306058 The general assembly of the log is written to the TEMP TEMP folder only if present at the time of writing - the post http://asusmobile.ru/board/viewtopic.php?p=306058 # 306058
2. In the configuration menu item was added to the "Advanced" - allows you to save the configuration version of the ROM, the size of PP (including 0xFFFFFFFF) and the description of the configuration (for the full version is also available to install and KernelFlags FsRamPercent). In the configuration menu item was added to the "Advanced" - allows you to save the configuration version of the ROM, the size of PP (including 0xFFFFFFFF) and the description of the configuration (for the full version is also available to install and KernelFlags FsRamPercent). Description of the configuration will be shown when you hover over the configuration file in the lower right corner OSBuilder'a. Description of the configuration will be shown when you hover over the configuration file in the lower right corner OSBuilder'a. ROM version, it makes sense to set in the configuration for the supported handheld device. ROM version, it makes sense to set in the configuration for the supported handheld device. To search for PP in XIP'e can be selected as the automatic mode, and manually specify which section nk and at what offset in this section is the size of PP. To search for PP in XIP'e can be selected as the automatic mode, and manually specify which section nk and at what offset in this section is the size of PP. These settings will be saved to a file xip_new.bin during assembly. These settings will be saved to a file xip_new.bin during assembly.
If you are porting XIP separately (Additional Tools -> To port XIP), in which case these parameters in the XIP not be recorded. If you are porting XIP separately (Additional Tools -> To port XIP), in which case these parameters in the XIP not be recorded.
Due to the fact that it is now possible to keep the size of PP in the configuration file settings are removed from the parameters of PP, except for the CheckPagePoolSize, PP isolates search all. Due to the fact that it is now possible to keep the size of PP in the configuration file settings are removed from the parameters of PP, except for the CheckPagePoolSize, PP isolates search all.
3. In the build configuration XIP'a item added "Delete spaces between sections nk in RAM" - in some cases allow more densely arranged sections, and free up a little extra space RAM In the build configuration XIP'a item added "Delete spaces between sections nk in RAM "- in some cases allow more densely arranged sections, and free up a little extra space RAM
4. In the build configuration XIP'a added item "Use the direct search for addresses nk" - this method can also try to use, if any patch in the pre-patched nk after porting / rebuilding XIP'a not working as it should. In the build configuration XIP'a added item "Use the direct search for addresses nk" - this method can also try to use, if any patch in the pre-patched nk after porting / rebuilding XIP'a not working as it should. I warn in advance that this method could lead to inoperability XIP'a or unexpected glitches. I warn in advance that this method could lead to inoperability XIP'a or unexpected glitches.
5. Fixed a glitch with the print version DSM (and HTC) in the description window when you move to the package by using keys UP / DOWN - post http://asusmobile.ru/board/viewtopic.php?p=306717 # 306717 Fixed a glitch with the print version DSM (and HTC) in the description window when you move to the package by using keys UP / DOWN - post http://asusmobile.ru/board/viewtopic.php?p=306717 # 306717
6. Added option to remove the packages and groups from the grouped keys Del or Backspace. Added option to remove the packages and groups from the grouped keys Del or Backspace. Added a context menu of the package and the <Context> Added a context menu of the package and the <Context>
7. Added ability to edit the properties of a group or package (bundled in packages) by pressing F2 Added ability to edit the properties of a group or package (bundled in packages) by pressing F2
8. Reached his hands to a more thorough check on the membership package to the language (tested only on a special list of languages) Reached his hands to a more thorough check on the membership package to the language (tested only on a special list of languages)
9. In the settings (packages and configuration) is now generally possible to disable the check for membership to the language. In the settings (packages and configuration) is now generally possible to disable the check for membership to the language.
10. Corrected popup menu package, and the group - post http://asusmobile.ru/board/viewtopic.php?p=308167 # 308167 Corrected popup menu package, and the group - post http://asusmobile.ru/board/viewtopic.php ? p = 308167 # 308167
11. Fixed a glitch with retention of configuration (for loading the new configuration) - Post http://asusmobile.ru/board/viewtopic.php?p=309425 # 309425 Fixed a glitch with retention of configuration (for loading the new configuration) - Post http: / / asusmobile.ru / board / viewtopic.php? p = 309425 # 309425
12. Added progress window assembly file section IMGFS (thermometer) Added progress window assembly file section IMGFS (thermometer)
13. Fix a glitch with porting SYS (stop, if the packets are marked yellow) - Post http://asusmobile.ru/board/viewtopic.php?p=305775 # 305775 Fixed a glitch with porting SYS (stop, if the packets are marked yellow) - Post http://asusmobile.ru/board/viewtopic.php?p=305775 # 305775
14. Added support for Garmin-Asus M10, M20 (PP, date and version of the ROM) Added support for Garmin-Asus M10, M20 (PP, date and version of the ROM)
15. Packages are not included in packages.sof (cif) can now be sorted in the editor sof and cif for GUID - post http://asusmobile.ru/board/viewtopic.php?p=309858 # 309858 Packages are not included in packages.sof (cif) can now be sorted in the editor sof and cif for GUID - post http://asusmobile.ru/board/viewtopic.php?p=309858 # 309858
16. In additional instruments added item "Files provxml" (available only in full version). In additional instruments added item "Files provxml" (available only in full version). When you select a window appears with a list of files provxml in the order in which they are executed. When you select a window appears with a list of files provxml in the order in which they are executed. Files provxml, containing the registry settings and / or certificates that are marked with the icon. Files provxml, containing the registry settings and / or certificates that are marked with the icon. Double click opens the file for editing. Double click opens the file for editing. Using the context menu to open the file for editing, see the registry settings in Complex RGU, export the registry settings to a file rgu or browse the registry of all the files in provxml Complex RGU. Using the context menu to open the file for editing, see the registry settings in Complex RGU, export the registry settings to a file rgu or browse the registry of all the files in provxml Complex RGU.
17. Added the ability to both manual and automatic signature files or a built or self-signed certificate (only available in full version). Added the ability to both manual and automatic signature files or a built or self-signed certificate (only available in full version). In additional instruments added item "Create your own certificate to sign files. In additional instruments added item "Create your own certificate to sign files. In the configuration menu, added the ability to create a list for avtopodpisi (by analogy with the list RECMOD), and in the popup menu item was added to the package" to sign a file, with which you can either immediately sign files in the package (optional), or add files to the list for avtopodpisi. In the configuration menu, added the ability to create a list for avtopodpisi (by analogy with the list RECMOD), and in the popup menu item was added to the package " to sign a file, with which you can either immediately sign the files in the package (optional), or add files to the list for avtopodpisi.
ALL THE FACTS IN ADDITION TO MANUALS IN THE SECOND post topics. ALL THE FACTS IN ADDITION TO MANUALS IN THE SECOND post topics. MUST READ, Do not be lazy! MUST READ, Do not be lazy!
18. Removed from the settings option BuildImgfsV2. Removed from the settings option BuildImgfsV2. Assembling IMGFS made as if this option was set to True - see ChangeLog - OS Builder V1.0.65 RC4 (24.03.2010) para 14. Assembling IMGFS made as if this option was set to True - see ChangeLog - OS Builder V1.0.65 RC4 (24.03.2010) para 14.
19. As an OEM XIP porting is now also possible to use the packages in a folder ROM \ XIP - see the settings for an assembly XIP. As an OEM XIP porting is now also possible to use the packages in a folder ROM \ XIP - see the settings for an assembly XIP. The presence of files and romhdr.bin parthdr.bin in your ROM \ XIP necessarily. The presence of files and romhdr.bin parthdr.bin in your ROM \ XIP necessarily. Type settings XIP'a little has changed - see the updated manual on XIP'u second post topics. Type settings XIP'a little has changed - see the updated manual on XIP'u second post topics.
Attention! Attention! After the transition to the new version OSBuilder sure to check the configuration of assembly / porting XIP. After the transition to the new version OSBuilder sure to check the configuration of assembly / porting XIP.
20. Added mode multibild - in one kitchen, one can use several builds SYS - manual in the second post topics. Added mode multibild - in one kitchen, one can use several builds SYS - manual in the second post topics. Be sure to read and not lazy, it is important! Be sure to read and not lazy, it is important!
21. The full version adds a database GUID'ov package (currently only MS), which allows more accurate identification of dependencies and shadow in the dsm, and quickly change the DPI, LANG and RES in packages.sof and packages.cif. Planned to make the base through the Inet recharged. Planned to make the base through the Inet recharged.
RC CHANGELOG (web translation)
OS Builder V1.0.78 RC4 (23.04.2010):
Code:
1. In the form of packages combining fixed glitch with the "Cancel" In the form of packages combining fixed glitch with the "Cancel"
2. In setting the porting / assembly XIP'a item added "After the run" - you can specify komandnik, which will be executed at the end of the assembly XIP'a. In setting the porting / assembly XIP'a item added "After the run" - you can specify komandnik, which will be executed at the end of the assembly XIP'a. Allowed relative paths. Allowed relative paths. (The current directory at startup komandnika - the root of the cuisine) (The current directory at startup komandnika - the root of the kitchen)
3. Corrected the spelling in an editor file certificates - Post http://asusmobile.ru/board/viewtopic.php?p=302202 # 302202 Corrected the spelling in an editor file certificates - Post http://asusmobile.ru/board/viewtopic.php ? p = 302202 # 302202
4. Added ability to set the size of PP = 0xFFFFFFFF Collector ROM - post http://asusmobile.ru/board/viewtopic.php?p=301812 # 301812 Added ability to set the size of PP = 0xFFFFFFFF Collector ROM - post http://asusmobile .ru / board / viewtopic.php? p = 301812 # 301812
5. In the ini in the section [OsBuilder] added option DisablePagePool, DisablePagePool = True - the size of PP is set to 0xFFFFFFFF. In the ini in the section [OsBuilder] added option DisablePagePool, DisablePagePool = True - the size of PP is set to 0xFFFFFFFF. This option has a higher priority to the parameter DefaultPagePool This option has a higher priority to the parameter DefaultPagePool
6. In the ini in the section [OsBuilder] added option CheckPagePoolSize. In the ini in the section [OsBuilder] added option CheckPagePoolSize. If set = False, then the search or change the size of the PP do not will be done (default = True). If set = False, then the search or change the size of the PP do not will be done (default = True). This option has the highest priority over all other parameters of PP. This option has the highest priority over all other parameters of PP.
7. Added ability to run the cmd-file before dump Relocation - see the settings for an assembly dump ROM Added ability to run the cmd-file before dump Relocation - see the settings for an assembly dump ROM
8. In previewing the roster reformed to delete keys and parameters (for care thanks NarkoZ) In previewing the roster reformed to delete keys and parameters (for care thanks NarkoZ)
9. Timer output for various operations are now customizable - a post http://asusmobile.ru/board/viewtopic.php?p=302881 # 302881 Timer output for various operations are now customizable - a post http://asusmobile.ru/board/viewtopic . php? p = 302881 # 302881
In the ini file in section [OSBuilder] options: In the ini file in section [OSBuilder] parameters:
Code: Code:
TimerXIP - sets the timeout at the end of rebuilding XIP'a. TimerXIP - sets the timeout at the end of rebuilding XIP'a. Default value = 10 Default value = 10
TimerRebase - sets the timeout after forwarding modules. TimerRebase - sets the timeout after forwarding modules. Default value = 10 Default value = 10
TimerMergePkg - sets the timeout after the association dsm. TimerMergePkg - sets the timeout after the association dsm. Default value = 10 Default value = 10
TimerRomStart - sets the timeout BEFORE assembling the file ROM. TimerRomStart - sets the timeout BEFORE assembling the file ROM. Default value = 15 Default value = 15
TimerRomEnd - sets the timeout at the end of the assembly file ROM. TimerRomEnd - sets the timeout at the end of the assembly file ROM. Default value = 10 Default value = 10
Values mean a second. Values mean a second. If the value is 0, then the process will be completed (or started) immediately. If the value is 0, then the process will be completed (or started) immediately. If the value is -1, the process will wait for user response (pressing OK, etc.) If the value is -1, the process will wait for user response (pressing OK, etc.)
10. In connection with the search for innovations modified the time-bomb (thanks SergeyLar) In connection with the search for innovations modified the time-bomb (thanks SergeyLar)
11. In the menu of additional tools added item "Create Template". In the menu of additional tools added item "Create Template". You can create templates based on files nb0 or payload. You can create templates based on files nb0 or payload. There is an opportunity to enter into a template XIP, delete, substitute or leave blank ULDR, set the size of PP, as well as the date, version, etc. There is an opportunity to enter into a template XIP, delete, substitute or leave blank ULDR, set the size of PP, as well as the date, version, etc. for supported handheld device. for supported handheld device.
12. Added ability to append to the file ROM partition FAT32 (the file or empty, scored FF in size in FAT32 Partition Table) - see the settings for an assembly dump ROM Added ability to append to the file ROM partition FAT32 (the file or empty, scored FF in size in FAT32 Partition Table) - see the settings for an assembly dump ROM
13. Added the possibility of reconstruction of files from the modules in the editor dsm and the context menu of package Added the possibility of reconstruction of files from the modules in the editor dsm on the shortcut menu package
14. Added the possibility of reconstruction of files from the list of modules during assembly. Added the possibility of reconstruction of files from the list of modules during assembly. The list is saved in the configuration. The list is saved in the configuration. Modules in the list dobavt both manually and a list from the context menu of the package or the context menu of the file dsm. Modules in the list dobavt both manually and a list from the context menu of the package or the context menu of the file dsm. Originals of the modules in SYS, OEM, or EXT remain unchanged, the reconstruction takes place directly in the Dump, while in the dsm files Dump adjusted accordingly. Originals of the modules in SYS, OEM, or EXT remain unchanged, the reconstruction takes place directly in the Dump, while in the dsm files Dump adjusted accordingly. - See - See manual in the second post topics. manual in the second post topics.
15. Added the ability to build the file section IMGFS no pattern, just the file-header IMGFS. File should be named imgfs.bin and be in a folder ROM.
16. When cleaning the module if there is also deleted imageinfo_pe.txt - post http://asusmobile.ru/board/viewtopic.php?p=304958 # 304958
17. In the context menu items added to the package "Create initflashfiles.txt" and "Create a registry file." These menu items are visible only when the package is missing initflashfiles.txt or registry file - post http://asusmobile.ru/board/viewtopic.php?p=304816 # 304816
18. When you open a folder with a kitchen, if not found the default configuration file, OSBuilder try to load a configuration from file Option.xml (if any). I do not remember who requested such feature, but just someone asked
19. Package or group in the tree to select the packages you can celebrate a key "gap"
20. Added support for ASUS P527 (size of PP and the date of ROM)
21. Added support for Dell Axim X51 (the size of PP, the date and version of the ROM)
OS Builder V1.0.66 RC4 (26.03.2010):
Code:
1. I think that the problem with calling komandnika at the end of the assembly (and up if someone was) - the post http://asusmobile.ru/board/viewtopic.php?p=301381 # 301381
Before running komandnika current folder is the root of the kitchen. Consider it in teams and in relative paths in komandnikah.
2. Possible to run multiple instances OSBuilder (naturally in various kitchens icon_smile) - Post http://asusmobile.ru/board/viewtopic.php?p=301224 # 301224
OS Builder V1.0.65 RC4 (24.03.2010):
Code:
1. When you import configuration files from Option.xml Option.xml also searched in the folder EXT
2. Fixed a problem with the search for packages in a folder EXT - post http://asusmobile.ru/board/viewtopic.php?p=295521 # 295521
3. Fixed a problem with the "Build" and start a timer at the collector ROM - post http://asusmobile.ru/board/viewtopic.php?p=291362 # 291362
4. Fixed a problem with an error when creating a dsm, when empty or damaged dsm has an attribute ReadOnly (interestingly, some on an empty dsm took place ReadOnly icon_smile))
5. In the derivation of textual information about XIP'e displays information about devayse, date, version, PP, etc. (If the device is identified)
6. At the request of workers in the extra tools added item "Auto DSM". The settings are quite flexible - you can rebuild all the damaged and empty dsm, correct names and GUID's packets, synchronize files and modules. In essence - this synchronization as the editor DSM, not just for one but for a variety of packages.
7. Slightly changed parser provxml (hope that got rid of the error message described in this post.
8. In additional tools removed the item template \ Extract dsm and rgu. Instead, he added, click Templates \ extract the package into a folder XIP ROM \ XIP. In fact, it's a dump XIP'a template packages. In the folder ROM \ XIP also extracted ROM Header and PartHeader (data from the address physFirst and physFirst + 0x1000).
9. In additional instruments added item XIP (ROM \ xip.bin). The submenu items are the same as the template.
10. In the build configuration item was added to the Copy ROM file in the root folder (previously it was necessary to prescribe manually in ini)
11. Change search size PagePool (for ASUS P526) - Post http://asusmobile.ru/board/viewtopic.php?p=291932 # 291932
12. Added support for ASUS A696
13. Added ability to run a batch file to build (see build configuration).
14. Reduced assembly time file section IMGFS (thank AnDim and airxtreme). In the ini file in section [OsBuilder] option BuildImgfsV2 = True - a new method (the default), BuildImgfsV2 = False - the old method
15. Implemented rebuild / avtoportirovanie XIP'a - tested at various devaysa. During the tests many thanks to Alexx ~, AndrewSh, Feropont, Anper. A separate manual porting / rebuilding XIP'a here.
16. Changed build - you can explicitly specify what kind of XIP will be used to build - XIP from a template file ROM \ xip.bin or ported (rebuilt) XIP.
OS Builder V1.0.56 RC3 (21.01.2010):
Code:
1. Corrected job with the template (many thanks Anper 'y). Who had jumped out a bug related to the fact that the size of FLASH in the region 0 is zero, try ...
2. At the root of the kitchen at will, you can create a folder EXT for their packages. If the folder exists, then it will also be used autosearch packages. Requirements for the package in the EXT are the same as the OEM and SYS (not to be confused with the EXT packages EVK!!!!)
3. In the toolbar button added to expand / collapse the tree grouped packages.
4. Collector ROM file added to start the timer. If within 15 seconds. has not been altered by hand or one parameter, the assembly will start automatically.
5. Search box in the editor and sof cif made no modal
6. Fixed minor bug - box version definition dsm displayed only if the settings were set to "Show package versions HTC"
7. Now you can force the name of the file ROM. In the configuration file in section [OSBuilder] option RomFileName. For example RomFileName = OS.nb as a parameter, you can use the file name only, with no roads. If you no longer need this - leave this blank: RomFileName =
OS Builder V1.0.54 RC3 (14.01.2010):
Code:
1. Made drastic changes in reloker.
2. Substantial changes in the algorithm combining packages.
3. Something corrected in the parser for previewing the roster.
OS Builder V1.0.50 RC3 (19.12.2009):
Code:
Fixed bug in relokere - the distribution of the modules on the actual e32_vbase in some cases, could turn out intersection.
OS Builder V1.0.49 RC3 (15.12.2009):
Code:
1. Added ability to change to a blank section UL, a 1 logic block (filled with bytes of FF)
2. Relocation implemented by packages.cif - details of additional Manuale
3. Added exception for modules configured relocation. Modules specified in the exemption will always be placed in slot 0, even if there is room to another slot and selected "Break-ins L". In addition, you can choose the form of exclusion from the package and OEMDrivers OEMDriversHigh - details in the supplementary manuals.
4. Added function to port SYS (toolbar - additional instruments). SYS porting the new packages do not coincide with Lang, DPI, resh and resv not shown at all, if the ini file in section [PortEngine] option SysShowAllPackages = False. If SysShowAllPackages = True, show all the packages.
5. Added output versions dsm (by analogy with the versions of HTC) - in the right window will be derived dsm versions of all packages. If any files dsm replace or edit - just in case before the print version dsm better to update the information.
6. In settings (packages and configurations) item was added to the "Show version of DSM package in the Description window.
7. Added support for HTC Leo (while theoretically, almost as long as there is no way to verify icon_smile))
8. In the setting adds the ability to specify the name of the package when combined into one package.
9. Setting the boundaries of slots in a separate form
10. When the Preview. Browse registry in case of error. provxml treatment. provxml not stop and process the following file. provxml
11. Rewritten search and patch time-bomb - a huge spacibo SergeyLar
12. When combined into a single package in the combined DSM will be copied information about all files
OS Builder v1.0.42 RC2 (09.11.2009):
Code:
1. Added settings to a file ini:
- Section [OsBuilder], setting DisableCritical. DisableCritical = True denies access to "risky" settings. DisableCritical = False allows access to all settings. This option is useful if OsBuilder laid out in the kitchen, and the need to "protect" the end user of the reckless action, naprimet of change of noodle minimum limits slots.
- Section [OSBuilder] option DefaultPagePool. To ensure that every time you build does not change the size manually PagePool, you can enter it in the file ini. The size in megabytes in the range from 0 to 64. Fractional values are illegal. If you specify DefaultPagePool =- 1, the parameter is not used and the size PagePool will be taken from XIP'a (template). Exceed the value of 64 is impossible!
2. Packages HTC
- The settings (packages and configurations), added item "Show package version of HTC's description window. Clicking on the package (in both trees) will attempt to consider the key HKEY_LOCAL_MACHINE \ SOFTWARE \ OEM \ MASD and if one exists, the version will be added to the description of the package and displayed in the window description.
- A tool in the toolbar to add an item Version HTC - if they found bags HTC, a list of versions will be displayed in the right window
3. Fixed search engine time-bomb (stumbling and outreach to build of 23085)
4. At the beginning of the assembly collapses window ungrouped package, if it is open
5. Made a small change in the mechanism of correction and autogenerate. VM and. ROM
6. In Builder'e ROM ROM date is automatically set to the "Today". To date, actually prescribed in the NK Collector added to separate the "Date (nk)"
7. Fixed an issue with the record date of ROM for HTC devices
8. Fixed a few little things implicit
OS Builder v1.0.40 RC1 (25.10.2009):
Code:
the first Public version
HD2Owner, thank you very much for publishing and support.
Glad to see OSBuilder thread on XDA-DEVS
I have been using OSBuilder since its initial release and have successfully cooked ROMs for Topaz. This is a fantastic kitchen. Thanks to Barin and others who have supported him in the development.
This is, by far, the most advanced visual kitchen I have used
Great work indeed!
Has anyone tried this kitchen with Omnia II roms? There is one primitive kitchen only for this device on modaco forum.
javichampi said:
Has anyone tried this kitchen with Omnia II roms? There is one primitive kitchen only for this device on modaco forum.
Click to expand...
Click to collapse
i asked barin and this is what he told me:
it's the only way to try. OsBuilder can build NB0 for any device and then you need conversion tools to convert nb0 to omnia format.
if there is any old kitchen for omnia you can try to get conversion tools from it. i'm sure that every kitchen builds partitioned nb0 and then uses device specific tools to make special format rom file.
edit:
tutorial videos and more links from mobileunderground thread (by indiagroove) added.
edit2:
changelog added (old versions where missing). re-ordered changelog to save space for future changelogs.
HD2Owner said:
i asked barin and this is what he told me:
it's the only way to try. OsBuilder can build NB0 for any device and then you need conversion tools to convert nb0 to omnia format.
if there is any old kitchen for omnia you can try to get conversion tools from it. i'm sure that every kitchen builds partitioned nb0 and then uses device specific tools to make special format rom file.
Click to expand...
Click to collapse
Thank you for your response,
well, the Omnia II can be flashed with nb0 files, that isn't the problem. But OmniaII's stock rom file is a .MST with multilingual support, and you can only extract english part directly from this file. So for non-english roms there is a tool that can create a dump directly from device, but it creates a .BIN file. As you said, if I convert this .bin file to .nb0, will I be able to make the dump with OSBuilder?
I'm a newbie cooker, and Omnia II dump is different to dump of HTC devices(even Omnia I too), for this reason I make the first question to anybody who have an Omnia II and can help me with possible specific configurations of the kitchen with this device.
Sorry for my poor english!!
osbuilder should work with nb0, nb and nbh.
you should give it a try..
HD2Owner said:
osbuilder should work with nb0, nb and nbh.
you should give it a try..
Click to expand...
Click to collapse
Well, finally I can make the dump, but when I try to open the build to work with it, I obtain this error and OSBuilder closes.
If os Builder create better rom from PlateformeRebuilder, i will test it
I'm waiting for EXT packages support
Nixeus said:
If os Builder create better rom from PlateformeRebuilder, i will test it
I'm waiting for EXT packages support
Click to expand...
Click to collapse
afaik, osbuilder does not support ext-format for various (good) reasons.
you have to convert ext to oem packages if you are adjusting a previous prb kitchen for osbuilder.
if you dump the rom with osbuilder it's not needed (osbuilder creates oem pkg's).
there are ext to oem conversion tools out there.
ultrashot is working on a nice tool to do this (i already used it to convert my evk based kitchen).
I had been using EVK for over a year before I switched to os builder. I had close to a hundred EXT's that I had put together, and making the switch was daunting. I first decide to play around with OS Kitchen (easy switch), and found that it created dsm's for all of my EXT. Once I had the dsm's, it was very easy to convert my EXT's to OEM's, so that's why I switched over to OS Builder.
I want to try this kitchen, but it seems like I can't dump a stock ROM RUU in the kitchen? How can I extract the NBH file out of the RUU and dump it in the kitchen?
_Madmatt said:
I want to try this kitchen, but it seems like I can't dump a stock ROM RUU in the kitchen? How can I extract the NBH file out of the RUU and dump it in the kitchen?
Click to expand...
Click to collapse
first extract the content of ruu...exe with winrar.
then switch to "mode-dump tool" in osbuilder (upper right) and chose file->open file->open your nbh->create packages
a new "dump" folder will be created (this is your kitchen folder, time to move and rename it)
then switch to "mode-os builder" (upper right) and chose file->open folder->select kitchen folder (previously created "dump" folder)