[Utility] Rom cooker...

[Codeneos]

Latest version: 0.7.5.0

Never flash UBOOT, NBL1 or NBL2. Untick the bootloader option in the symbian rom flasher. Flashing UBOOT can brick your phone!

Note: you need to extract all files from the CSC and CODE directories into one and the same folder do not leave any files out, the more the better. You might be asked if you want to merge directories (ROFS2, ROFS3 and ROFS4 for example are both in the CSC and CODE folder) always click yes as the CSC and CODE directories contain different files that do not conflict with each other.

Seeing all those people creating roms for use I decided to create a utility that enables thoso who are in the business of cooking roms to extract and repack roms the easy way.

The utility extracts all ROFS images using the latest symbian image dumper, rebuilds the CSC and CODE xml files which define the portioning of our dear I8910. And last but not least repacks the changed files into a brand new ROFS image.

The utility automatically adjusts partition size and MD5 hash. Note: at the current stage it is still a command line utility!

It can be used like:

SRomUtility 0.7.4 build 98 - Symbian ROFS and ROM unpacker/repacker.
Developed by Neos; this product contains Symbian SDK utilities.

Usage: RofsRomUtility [arguments]
Arguments:
        /unpack working_directory source
           working_directory: Unpacked files will be written to this location.
           source: Source directory from where the images are read.
        /unpackrom source destination
           source: Samsung Symbian ROM image.
           destination: Directory where the rom files will be extracted.
        /repack working_directory source destination (model) (provider) (version)
           working_directory: Modified firmware files.
           source: Source directory where the original images are stored.
           destination: Destination for the newly created firmware.
           model: Model of the device, example: I8910.
           provider: Provider ID code to be included in the firmware name.
           version: Version to be included in the firmware name, example: 2.
        /help OR /?
           Displays the current message.

To use it you will need a firmware image, let’s take II1 for example. You need join all the directories from both the CSC and CODE directory into one new directory called II1 (xml files are optional).

The to extract these files to a new working copy run from the command line: RofsRomUtility /unpack .\WC\ .\II1\. This will unpack all files from the II1 firmware and put the extract files into the directory WC (working copy). Then modify these files, add, remove or edit these files until you are satisfied. Now to repack these files into a new firmware run from the command line: RofsRomUtility /repack .\WC\ .\II1\ .\COOK_II1\.
The utility will recreate the XML files for both the CSC and CODE directories and repack the modified files into ROFS images.

To extract a single ROM file run from the command line: RofsRomUtility /unpackrom ubootldr.rom.img .\UBOOT\. This for example will extract the Uboot loader to a new directory called UBOOT. The same can be applied to the core rom image.

Requirements
* Any windows version that has the .net framework 2.0 or higher installed.
* A set of correct ROFS and ROM files (can be obtained from this forum).
* Last but not least, brains!

Download
Version 0.7.5.0: Mediafire
Version 0.7.4.0: Mediafire
Version 0.7.3.0: Mediafire
Version 0.7.0.0: Mediafire
Version 0.6.2.0: Mediafire
Version 0.6.1.0: Mediafire
Version 0.5.1.0: Mediafire
All versions: Mediafire

Plans
Adding support to repack the ROM files is on it's way. But be warned adding things other then ordinary files (device drivers, etc) requires some knowledge of the S60 operating system. Further more for most of the casual repackers I would not recommand editing the genrated OBY scripts used to generate the ROM image as it can seriously messup your phone.

Update 0.6.1.0 (13-09-2009)
* Extracts the rom images such as UBOOT and CORE.
* Can decode BPE (BytePairEncoding) compression.
* Can read on-demand-pages from roms.
* Fixed a small issue with calculating the MD5 for rom files.

Update 0.6.2.0 (13-09-2009)
* Added more checks when reconstructing the XML code files (fixes several issues when the original source was incomplete).

Update 0.7.0.0 (13-09-2009)
* Added support for unpacking ROFS images without external tools.
* Improved OBY file generation, ROFS now use the image size as specified in the original ROFS.

Update 0.7.3.0 (14-09-2009)
* Added configuration ini file.
* Added automatic updating of timestamp files and version files in the versions directory for each ROFS, this will automatically assign a version based on the config file or parameters passed to the utility.

Update 0.7.4.0 (16-09-2009)
* Fixed issues with unpacking custom firmwares without correct timestamp.

Update 0.7.5.0 (16-09-2009)
* No significant changes, only upgrade if you have a problem with version 0.7.4
* Should fix the bug where time settings affected succesfull repacking or ROFS files.

[djsaad1]

This is perfect! Thanks!

[Quist]

Can't wait to try this out! Cheers!

This will only unpack and repack the rofsX.img files, right? Or will it do so with the rom image in Code as well?

[Codeneos]

The rom image is not a symbian complained rom image and I do not know how to repack it correctly. Though extracting it should be possible after some research on the file structure.

And for those intrested I just found out that the PE files (all DLL's and EXE's in the rom image) are also not standart Symbian PE files, I compared the java installations of both the XM5800 and I8910 and was unable to open the PE files with the symbian SDK kit whereas I was able to inspect the java installation of the XM5800.

My guess is that samsung has modified some part of the S60 operation system and SDK and hench therefor symbian utilities are partially useless. It would be nice if we could get our hands on those tools :P, this would enable us to rebuild the main system rom.

[djsaad1]

anyone else having trouble running the exe? even the /? or /help command won't work for me. It just returns to the command prompt

[gnusmas8910HD]

Brilliant stuff indeed

[Codeneos]

Originally Posted by djsaad1

anyone else having trouble running the exe? even the /? or /help command won't work for me. It just returns to the command prompt

Do you have .net framework 2.0?

[djsaad1]

Yeah I do, not quite sure why it's not working here. Was waiting to see if anyone else had the issue before I started troubleshooting on my end.

[Codeneos]

Hmm, I'll upload a virtuallized version of the tool, you can try that one. It is a bit bigger due to the fact that the .net framework is embedded in it, download VM from mediafire. If you still have problems I'll upload a special debug build which generates a log file.

[djsaad1]

That didn't work either, still doing the same thing. But I am about to leave work and go home. I will try it there, this computer is having issues right now.