843 posts
Thanks Meter: 600
By Benjamin Dobell, Inactive Recognized Developer on 11th July 2011, 09:52 PM
Post Reply Email Thread
The Heimdall Suite 1.3 release includes a major overhaul of Heimdall Frontend. The most important feature is that Heimdall Frontend now provides a means for you to easily package your firmware/ROMs/kernels in a "Heimdall Firmware Package".

Heimdall Firmware Packages contain any files users will need to flash as well as additional information including supported devices, developer names, homepage and donate URLs etc.

Heimdall Firmware Packages can be customised by users or flashed directly as provided by firmware developers. Generally users won't want or need to customise the firmware so flashing your firmware becomes as simple as loading the firmware package and pressing the "Start" button.

Distributing your firmware via Heimdall Firmware Packages should simplify the flashing process for end users and decrease the number of bricks that occur as a result of users flashing incorrect firmware.

Heimdall 1.3.0 has officially been released and can be download from the Heimdall product page.

Feedback is very welcome! As always donations are also very much appreciated.
The Following 51 Users Say Thank You to Benjamin Dobell For This Useful Post: [ View ] Gift Benjamin Dobell Ad-Free
11th July 2011, 09:57 PM |#2  
OP Inactive Recognized Developer
Flag Melbourne
Thanks Meter: 600
Donate to Me
The following information/tutorial is included in the official README for all platforms but is reprinted here so developers can gain an understanding of the process before downloading Heimdall Frontend.

How to Create a Heimdall Firmware Package:
Firstly, Heimdall's firmware package format is just a regular TAR archive
compressed with gzip. The only two real requirements are that a valid
firmware.xml must be included (refer to Appendix A) and you can only
include files (no directories, links etc.) As such if you'd like there is
nothing preventing you creating Heimdall packages manually. Of course
Heimdall Frontend provides a simple user interface that takes care of all
the hard work for you.

There are two ways in which you can create a firmware package. You can
create a package from scratch, or you can load an existing package, apply
modifications and then save the package. Creating a package from scratch
is the preferred approach, by taking this approach you're far less likely
to run into file name length limitations, these are not Heimdall's own
limitation but rather a limitation of the TAR archive format.

Before you can access Heimdall Frontend's firmware creation functionality
(available from the "Create Package" tab) you must first specify which
files will be included in your package as well as a few flashing options
i.e. Whether or not users should repartition when flashing. This
information must be filled out from the "Flash" tab in exactly the same
fashion you would provide information to flash your device (see "Performing
a Custom Flash with Heimdall Frontend"). As mentioned above, it's not the
preferred means, but you're able to load an existing package as a starting
point for this information.

Once you've specified the files/partitions you wish to include in your
firmware package the "Create Package" tab will become available. Clicking
this tab will display additional information that you can include in your
package. In order to continue you must fill out all sections except for the
URLs section, which is optional. The following is break-down of what all
these options mean.

- General Firmware Information: -
Firmware Name - This is the name of your particular firmware. An
example would be "Cyanogenmod".

Firmware Version - This is the particular version identifier for your
package. Any valid string will be accepted although a the inclusion
of decimal point version number is preferred releases i.e. "7.1".
If it makes sense then feel free to append a text string like "RC1"
or "Beta 1" to the decimal point version.

Platform Name - This is the name of platform (or operating system) that
your firmware is based on. In most cases this will simply be

Platform Version - This is the operating system version that your
firmware is based on. Again decimal point version numbers are
preferred over text, i.e. "2.3.4" is preferred over "Gingerbread".

- Developers -

URLs (Optional):
Homepage - Here you can enter your personal URL or a URL particularly
pertaining to the firmware being packaged. The URL must be well
formed for it to work. An example of a well formed URL is
"". It is
important to include "http://" in order to specify the protocol as
other protocols such as "ftp://" are equally valid although
unlikely to be used.

Donate - Here you can enter a URL that will link users to a page to
make donations for the effort you've put into developing your
firmware. Once again the URL must be well formed but there is no
requirement on how your donation page should work. For instance
both "" and
"" are
equally valid.
Developer Info:
Name - Here you can enter in the name of individual team members or a
team name. Click "Add" and the developer will be added to the list
on the right. If you make a mistake you can select a developer from
the list and click "Remove". You can list as many developers as you
like however size constraints of the "Load Package" means only a
few will be visible. Where possible you may want to opt for team
names over listing individual team members.

- Supported Devices -

This section allows you to create a list of devices that are supported by
your particular firmware. Although Heimdall isn't capable of enforcing this
we strongly recommend you take this section seriously. If filled out
correctly you could help save a number of accidental bricks!

Device Info:
Manufacturer - This is where you can enter the name of the manufacturer
for a particular device. For now this will most likely be

Name - This is the human readable name for a particular device.
"Galaxy S", "Galaxy S II", "Droid Charge", "Vibrant" and
"Galaxy S (Telstra)" are all valid names. There are a lot of
possible variations here so be as specific as you think is

Product Code - This is by far the most important bit of device
information. Device names tend to be region specific and further
subject to the whims of telecommunication companies and resellers.
Product Codes (or product IDs) are designated by manufacturers and
are generally the definitive means of referring to a particular
device. Examples are "GT-I9000", "GT-I9100" and "SCH-I897". If
you're unsure of a particular product code then Google and
GSMArena are your friends!

After filling out all the necessary information the "Build" button will be
enabled. If it's still disabled then you know you're missing some required
information. In particular you must specify at least one developer and at
least one supported device. Pressing the "Build" button will bring up a
save dialogue where you must chose a file name for your particular package.
Don't worry about specifying the ".tar.gz" extension Heimdall Frontend will
take care of this automatically.

Once you've chosen a file name Heimdall Frontend will begin the process of
building the firmware package. In doing so a valid firmware.xml file will
be generated from the information entered, all files will be archived in a
single TAR file then the TAR archive will be compressed via gzip
compression. Compression will take a little while but you will see progress
bars so you know the application hasn't hung. When the progress bars
disappear you're finished making your package.

Congratulations! You're now ready to redistribute your firmware package
online or by any means you see fit.

Appendix A - firmware.xml

The following details a part of the Heimdall Firmware Package format. This
is only relevant to developers or advanced users who wish to create Heimdall
Firmware Packages outside of Heimdall Frontend or in some way integrate support
for the format in their own software.

All Heimdall Firmware Packages must contain a file called firmware.xml. This
file stores information stores meta-data for the package as well as information
about other files contained in the package that indicates how they should be

The format is fairly straight-forward so it won't be explained in great detail,
nonetheless the following is an example of a valid firmware.xml file.

<?xml version="1.0" encoding="UTF-8"?>
<firmware version="1">
	<name>Test Firmware</name>
		<name>Benjamin Dobell</name>
		<name>Hedonism Bot</name>
			<name>Galaxy S</name>
			<name>Galaxy S (Telstra)</name>
	<pit>Nl3276-I9000 s1_odin_20100512.pit</pit>

New lines need not be included and the order in which elements are specified
does not need to match that of the above example.

One and only one <firmware> element must be included. The <firmware> element
must also have a version attribute specified. The version must be parsable as
an integer and indicates what version of the Heimdall Firmware Package
specification the package adheres to.

All data is stored as strings, however a <file>'s <id> element must be parsable
as an integer. The <id> value represents the partition ID (according to the
specified PIT file) that the file should be flashed to.

A <firmware>'s <repartition> and <noreboot> elements must also be parsable as
an integer. However, as they represent boolean values, a value of zero ("0")
means false (or disabled) where as a non-zero value (typically "1") means true
(or enabled).

File names are specified relative to the TAR archive in which firmware.xml and
all other files are to be stored. Heimdall Firmware Packages do not support
directories or links, as such file names should only be a name and not a path.

<url> and <donateurl> are the only optional elements, all other elements must
be included.
The Following 21 Users Say Thank You to Benjamin Dobell For This Useful Post: [ View ] Gift Benjamin Dobell Ad-Free
12th July 2011, 03:06 AM |#3  
Recognized Contributor
Flag Amsterdam
Thanks Meter: 2,062
This is AWESOME! Hope people adopt this fast!
12th July 2011, 03:41 AM |#4  
Rahulrulez's Avatar
Senior Member
Flag India
Thanks Meter: 1,479
Donate to Me
Thanks a lot for this. I was waiting for such a tool since long long time

Now I can make my development even more faster.
The Following User Says Thank You to Rahulrulez For This Useful Post: [ View ] Gift Rahulrulez Ad-Free
15th July 2011, 10:44 AM |#5  
Darkyy's Avatar
Retired Recognized Developer
Flag Winterthur
Thanks Meter: 2,971
Donate to Me
I'm really thankful for your shared knowledge and your hard work.
The Following 2 Users Say Thank You to Darkyy For This Useful Post: [ View ] Gift Darkyy Ad-Free
17th July 2011, 01:47 AM |#6  
DAGr8's Avatar
Inactive Recognized Developer
Thanks Meter: 6,382
Donate to Me
Originally Posted by Darkyy

I'm really thankful for your shared knowledge and your hard work.


in case you havent noticed theres a thx button fo rthat you might go ahead and click it :P
The Following 4 Users Say Thank You to DAGr8 For This Useful Post: [ View ] Gift DAGr8 Ad-Free
18th July 2011, 10:35 AM |#7  
uppon2's Avatar
Recognized Contributor
Thanks Meter: 1,506
i9100 support?
18th July 2011, 11:01 AM |#8  
OP Inactive Recognized Developer
Flag Melbourne
Thanks Meter: 600
Donate to Me
Originally Posted by uppon2

i9100 support?

Yeah, all Galaxy S devices, well except maybe the Droid Charge which we've had problems flashing with Heimdall.

The firmware package format itself isn't tied to any particular device.
The Following 2 Users Say Thank You to Benjamin Dobell For This Useful Post: [ View ] Gift Benjamin Dobell Ad-Free
19th July 2011, 01:20 PM |#9  
Darkyy's Avatar
Retired Recognized Developer
Flag Winterthur
Thanks Meter: 2,971
Donate to Me
Originally Posted by DAGr8


in case you havent noticed theres a thx button fo rthat you might go ahead and click it :P

I did

You know, sometimes a sentence says more than thousand clicks
The Following 3 Users Say Thank You to Darkyy For This Useful Post: [ View ] Gift Darkyy Ad-Free
20th July 2011, 07:31 AM |#10  
SamHaLeKe's Avatar
Senior Member
Thanks Meter: 3,313
Donate to Me
Alright, let's see what this can do. Many thanks for this project!
27th July 2011, 02:00 AM |#11  
Thanks Meter: 5
I am trying to put together a package for the Vibrant's original firmware, JFD. The one clarifying question that I have is: Is IBF/PBF the same as the primary boot loader? That is, should I set that partition (0) to boot.bin?

Thank you for the hard work!
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes