[Verizon Samsung Galaxy Note II] soba49:
Now that Adam's new jailbreak is favoring heimdall for all platforms, it's likely there will be a lot of people with heimdall configured but not Odin, even on Windows.

Could you please provide heimdall instructions for this image. I've done a lot of the reading, I'm mostly looking for confirmation in case I made any mistakes.

Please include 2 and 3.

1. The official md5 for the stock.tar.md5 files themselves*

Example, I got MD5 (CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5) = f5a374385da4151ab756c361efe5a278

2. A command line for extracting the file

Example, tar -xvf stock.tar.md5 seemed to extract correctly. Couldn't find any mention of people having issues with the last file extracted being corrupt or anything like that.

3. A command line for flashing its contents with heimdall

heimdall flash --verbose --primary-boot boot.img --cache cache.img --hidden hidden.img --modem modem.bin --param param.bin --recovery recovery.img --secondary-boot sboot.bin --factoryfs system.img --11 tombstones.img --81 tz.img

Is --11 "TOMBSTONES" synonymous with --dbdata, and --81 "TZSW" synonymous with --kernel? Is there any reason to include --pit and --repartition?

I looked at my PIT file, which you can extract from your phone in download mode:

heimdall download-pit --output note2.pit
heimdall print-pit note2.pit > note2_pitprint.txt

here's a shorter version of that command.

heimdall flash --verbose --80 sboot.bin --81 tz.img --7 param.bin --8 boot.img --9 recovery.img --10 modem.bin --11 tombstones.img --12 cache.img --13 system.img --14 hidden.img

If you're looking for other identifiers, either look at your own PIT above, or here's the output from mine today.

*: I know this is redundant since it includes its own checksum, but cutting off the tail file and comparing the md5s is a little awkward, and mysteriously heimdall has never added a feature to do this easily

PS> If anyone is looking for PIT files here are 2. One I downloaded from XDA some time ago, and Another that I just copied off of my phone (running Beans ROM) today. For reasons unknown to me they're slightly different, but agree so far as the partitions in this stock ROM are concerned.

---------- Post added at 12:54 PM ---------- Previous post was at 12:04 PM ----------

All I found about how to check a tar.md5 file is here. This provides a script to do it, your mileage may vary...

Because of the way tar files are made, there's apparently empty space at the end of the file. The file is made by making the archive, then concatenating the output of md5sum onto the tail of that file.

So basically it's as onerous as you'd expect it to be. You either undo the process, or you look at it like it's 2 separate files:

1.You figure out the length of the file, wc -c stock.tar.md5

a. you write down the length, 1653944426 in my case

b. output was 1653944426 stock.tar.md5
​

2. Then look at the last few characters to find that md5 output using tail, and count them, tail -c 256 stock.tar.md5

a. you count the number of letters in this output, for me it was 106 (I counted by copying and pasting into an echo command and piping that through wc)

b. output was c5167c5413b6c8cea609db49a5896f34 CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar

c. in one line, using wc, tail, and perl, tail -c 256 stock.tar.md5 | perl -pi -e 's/\x00//g' | wc -c will give you 106 directly​

3. Then you pipe all but the end of the archive through md5, and compare the number to the on you found in 2. (head -c ### stock.tar.md5 | md5 )

a. To compute ###, you subtract the number you found from 2. from the number you found in 1: 1653944426 - 106 = 1653944320.

b. output is c5167c5413b6c8cea609db49a5896f34, a match

c. NOTE: if you don't get the right value for ### the MD5 WILL NOT MATCH​

The two md5sums match for me. Woohoo. This is why the guy who answered posted a script. It's simple to do, but tedious.