Skip to content


Heimdall 1.2.0 Command Line Released

I’ve just finished uploading the Heimdall 1.2.0 command line binaries. The 1.2.0 release doesn’t contain any Heimdall Frontend updates however Heimdall Frontend 1.1.1 is forwards compatible and works fine with the 1.2.0 command line binaries.

The following information is shamelessly taken from my own forum post.

The update will be command line only (for now) and adds the following functionality:

    Support for the Galaxy S II! (Hopefully, keep reading.)

  • Support for SHW-M110S (Korean Galaxy S).
  • Improved support for Galaxy Tab, Captivate and Vibrants (see below).
  • No reboot option.
  • Dump the devices PIT file and print the information in a human readable format.
  • Support for more named partition parameters i.e. –hidden, –movinand.
  • One more major feature (read below).

The biggest change is probably that proper support for PIT files is now included. This means that less things are hard-coded. Instead Heimdall will be grabbing data from your device’s PIT file or the PIT file you specify when repartitioning. This may seem like it has minor impact on the usefulness of Heimdall but it actually allowed me to add a second method of specifying files to be flashed to your phone.

You can now type:

heimdall flash --<partition identifier> <filename>

i.e.

heimdall flash --6 zImage

This essentially means you can flash any file your device supports as long as you know the partition identifier. Of course I don’t expect you to know them off the top of your head. This is where the PIT file dumping functionality comes in.

heimdall print-pit

Presto! You now have a complete list of all the flashable partitions on your device.

Another minor change is that I’ve removed the restriction on needing to specify bootloaders (or any files in particular) when repartitioning. However, this was in place as a safety feature. I honestly have no idea whether repartitioning without certain files is safe, and I have no immediate plans to find out. So please be careful!

As usual, to get your mitts on the latest release, just head over to the heimdall product page.

Posted in Devblogs.


8 Responses

Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.

  1. robgarth says

    Heimdall refuses to successfully communicate with my device on Fedora 15. Ubuntu/Debian and earlier version of Fedora work fine. Anyone else encounter this?

  2. buti says

    thanks a lot. works perfectly for samsung galaxy s 2.

  3. vbraun says

    I’m also having problems with Fedora 15. That version did change something in libusb, but that should only affect the old libusb-0.1. Verbose heimdall log is here:

    http://pastebin.com/2zLHW2LG

  4. pollute says

    I can communicate with my device. But thats all, i dontn know where to go from there. Is there some kind of tutorial for this.

  5. imatt.au says

    Optus Australia Galaxy S2 – Failed to detect compatable device. Heimdall 1.2.0. Mac OSX 10.6.8.

    Device is listed in the System Profiler when in download mode. i.e vendor id 0×04e8 and product id 0×685d.

  6. Benjamin Dobell says

    @imatt.au: This has been fixed for Heimdall 1.3.0, the issue was that the kext wasn’t compatible with OS X’s 64-bit kernel.

  7. Benjamin Dobell says

    Instructions are included in the README.

  8. eBug says

    I’m having a problem with USB communication:

    Manufacturer: “Sasmsung”
    Product: “MSM7×30″
    Serial No: “?”

    length: 18
    device class: 2
    S/N: 0
    VID:PID: 04E8:6601
    bcdDevice: 0100
    iMan:iProd:iSer: 1:2:0
    nb confs: 1

    interface[0].altsetting[0]: num endpoints = 1
    Class.SubClass.Protocol: 02.02.01
    endpoint[0].address: 82
    max packet size: 0010
    polling interval: 09

    interface[1].altsetting[0]: num endpoints = 2
    Class.SubClass.Protocol: 0A.00.00
    endpoint[0].address: 81
    max packet size: 0200
    polling interval: 00
    endpoint[1].address: 01
    max packet size: 0200
    polling interval: 00

    Claiming interface… Success
    Setting up interface… Success
    Beginning session…
    Failed to initialise usb communication!

You must be logged in to post a comment.