QUOTE=Noxious Ninja;28991583]I think the bootloader dump is separate from the boot.img in the ROM. The PDA package in Adam's post is the ROM from the stock ROMs thread. I believe they're meant to be used together if you really, really need to wipe everything.[/QUOTE]
Yes, boot.img is the kernel. Contains a 2KB header, the kernel, then a gzipped ramdisk (initialization files). In our case the boot.img also contains a signature that is checked by the bootloader (the reason we can't run custom kernels from the default boot.img partition (mmcblk0p7). For anyone interested in learning more, I recommend googling mkbootimg.c and bootimg.h. This is the C program used to package a kernel/ramdisk into the boot.img form. I recommend reading this small program while having the stock boot.img open in a text editor (to follow along).
The bootloader consists of several partitions on the gs3. I forget all of them, but opening Adam's bootloader tar will show what partitions belong to the bootloader on the gs3. The first page of Adam's post also has each mmcblk listed with a name associated (for most of them). The list of the files in the bootloader tar can be matched to the mmcblk locations.
Note: We may be able to flash the bootloader tar in Odin if your phone is working (haven't tried it), BUT if your phone isn't booting correctly (i.e. you messed around with one of the bootloader partitions) it may never get to a state that would allow Odin to work. I'm not positive about this, but better to be safe.
Sent from my SCH-I535 using xda app-developers app