Wiz Firmware Tools

[prl]

I have a new version of Eric Fry's Wiz Firmware Tools ready to distribute.

It adds machine type support to wiz_pack for the new Australian model DP-P2 and the Finnish models FT-P1, FT-H1, FC-P1 and FC-H1. To accommodate this, the type specifications "-t s", "-t p" and "-t h" are now deprecated. They are equivalent to the new type specifications "-t DP-S1", "-t DP-P1" and "-t DP-H1", and a warning message is printed if you use the old machine type names. I hope this should be uncontroversial, especially since the type specification "p" is ambiguous for Australian models, and even the types H1 and P1 are ambiguous across the Australian and Finnish models. The "-" may be omitted ("-t DPS1"), and the comparisons are case-insensitive ("-t dp-s1").

Earlier versons of wiz_pack required that the bytes of the "-T" machine code to be entered in little-endian order, the opposite order from what they appear in the Beyonwiz SETUP>System>Firmware>Firmware Information and in the OpenWiz hardware page. The new version requires them in big-endian order, i.e. the same order as they appear in Firmware Information.

For example, in the DP-S1, the System Id in its Firmware Information is 0808 0000 0E20 BE3E. The current version of wiz_pack requires you to enter:

Code: Select all

wiz_pack -T 3ebe200e00000808 ...

The new version requires:

Code: Select all

wiz_pack -T 080800000E20BE3E ...

Both versions allow either upper or lower case for letters in hex numbers. The new versions also allow ' ' or '-' as separators between bytes for legibility, so you can use:

Code: Select all

wiz_pack -T "0808 0000 0E20 BE3E" ...

or

Code: Select all

wiz_pack -T 0808-0000-0e20-be3e ...

I don't think that -T is used much (apart from its recent use by janilxx), so I don't think that this should cause many problems.

Anyone with any strong opinions about the changes?

[prl]

A new version of Eric Fry's Wiz Firmware Tools WizFwTools_20081108 is available on the OpenWiz Subversion repository (http://trac.openwiz.org/wizfwtools) and BeyonwizSoftware.net (http://www.beyonwizsoftware.net/softwar ... 53/#msg653). The ZIP file on BeyonwizSoftware.net includes compiled versions of the tools that will run on Windows and on Cygwin under Windows.

Win32 firmware unpacking and repacking tools. Instructions, source and GPL licence included.

Currently supports the Australian DP-S1, DP-P1, DP-P2 and DP-H1 and Finnish FT-P1, FT-H1, FC-P1 and FC-H1.

Version: 20081108
Author: Eric Fry

Version 20081108 release notes:

• Added README.txt describing how to build and install
• Fixed bug in wiz_unpack that was mangling the names of '.' and '..' directory names. Added -q option for less verbose and distracting output
• In wiz_pack, added support for DP-P2 and Finnish Beyonwizes. Change the order of the system ID code so that it's the same as in the Beyonwiz Firmware Infoemation. Allow the use of ' ' or '-' as byte separators in the system ID code for readability (in scripts, etc).
• genromfs now exits with an error if the input directory doesn't exist.
• In svctool, fixed the code so gcc stops whinging
• In Makefile & Makefile.win32, did some tidying-up, added PREFIX to allow the installation directory to be specified easily, ensure that installed binaries have read/execute permission to everyone. Added new Makefile.osx for OS X builds.

[prl]

A new version of Eric Fry's (efry) Wiz Firmware Tools (20090802) is available on the Openwiz Software page.

The new version adds support for the FV-L1 machine type.

[DaveR]

I've been waiting for this. I'll let you know if it works on a P1 with a 500GB HDD

BTW I tried changing the system id in a hex editor... but of course that broke the checksum.

[prl]

I've been waiting for this. I'll let you know if it works on a P1 with a 500GB HDD

BTW I tried changing the system id in a hex editor... but of course that broke the checksum.

There wasn't really any need to wait. The -T argument to wiz_pack allows you to specify any 16-digit hex string ad a system ID. Having the names ID compiled in is really only a convenience function.

It's more important in BWFWTools' pack_wrp, which digs the model name out of the firmware and uses that to set the default system id, but you can still give pack_wrp (and bw_patcher) an arbitrary systemid if you want.

[DaveR]

Well... all I can say is... it works!

[prl]

Well... all I can say is... it works!

Hmmm...

[DaveR]

Well... all I can say is... it works!

Hmmm...

http://www.beyonwiz.com.au/phpbb2/viewtopic.php?t=4297

[prl]

Well... all I can say is... it works!

Hmmm...

http://www.beyonwiz.com.au/phpbb2/viewtopic.php?t=4297

I've been following that topic with interest

[DaveR]

Here's some basic instructions on how the Wiz Firmware Tools are used

Wiz Firmware Tools is used for unpacking, building a romfs image, and repacking any Beyonwiz firmware. To use Wiz Firmware Tools for something simple like just changing the displayed version info - i.e. instead of 'Official.Version' you could change it to 'Daves.DP-S1' - you need to unpack the original firmware to a folder. Then make any modifications - like replace the menu background image. Then run wiz_genromfs to build the new romfs file. Then pack the new firmware, with your desired version info.

1. Assuming you wanted to unpack DP-P1 firmware, say to replace the menu's background image:

Code: Select all

del /s /q out\*
wiz_unpack -i -x out DPP1_Firmware_04Jun2009_ver_01.05.301.wrp

2. Then, say after replacing the background image with your new one, you create a new romfs image file from the unpacked firmware:

Code: Select all

del test.img
wiz_genromfs -i -f test.img -d out/ -V mambo

3. Then finally you repack the firmware, complete with your new background image etc, into a valid wrp file. Make sure that you specify the correct model. You can make the version string anything you want, but normally it starts with the firmware version number string followed by 2 underscores followed by 2 words separated by a dot and ending with 2 underscores. Example: 01.05.301__Official.Version__

Code: Select all

del test.wrp
wiz_pack -t DP-P1 -V 01.05.301__My.Version__ -i test.img -o test.wrp

4. Then rename test.wrp to something relevant - like my-new-firmware.wrp.
5. Check the results using my BW Firmware Identifier. Make sure that the wrp file does NOT contain a boot loader or you may permanently brick your Beyonwiz if you are trying something silly.
6. Confirm that you are able to perform a remote firmware recovery (in case you screwed up and the Beyonwiz won't boot with your new firmware).
7. Load your new firmware onto your Beyonwiz.

Or in step 3 above, you could even use a different model version IF you are absolutely certain that the specified model will not brick your model:

Code: Select all

del test.wrp
wiz_pack -t FV-L1 -V 01.05.123__My.Version__ -i test.img -o test.wrp

[prl]

The procedure above only unpacks and repacks the application file system in the Beyonwiz firmware.

The root file system can be unpacked and repacked as well by using BWFWTools. BWFWTools makes use of Wiz Firmware Tools, and offers some fully automatic modifications to Beyonwiz firmware (but not any automatic changes to run "foreign" firmware on another model).

[prl]

Version 20100914 of Eric Fry's Wiz Firmware Tools is available.

It has been updated to recognise and build .wrp files for the DP-Lite. The executable for Windows and Cygwin have been built on a newer version of Cygwin, and the corresponding cygwin1.dll has been included. The format of its help messages have been tidied up.

Source code is also available from http://redmine.openwiz.org/projects