Help with i9100 Partitions/Pit-file (Heimdall) - Galaxy S II Q&A, Help & Troubleshooting

Hey all.
Sorry if this has been asked before, but I can't seem to find a proper answer on the forums. Am using Heimdall 1.4 rc1/2, on Arch Linux.
Not sure whats happened to my phone as its been flashed so many times in the past, and can't remember what might have caused this.
First time using Heimdall, as I got sick of having to keep a partition spare for XP which in the end only got used for flashing to the S2
I would really like a stock PIT file or even some feedback as to whether my partitions are correct?
Notice that the Boot partition is read only and I also have an SBL1 and an SBL2???
Please help....
HTML:
Entry Count: 15
Unknown 1: 0
Unknown 2: 0
Unknown 3: 0
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 0
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 0
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: GANG
Flash Filename: emmc.img
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 0
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.bin
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 8192
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 49152
Partition Block Count: 2560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL1
Flash Filename: Sbl.bin
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 53248
Partition Block Count: 2560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL2
Flash Filename:
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 57344
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.lfs
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 73728
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: KERNEL
Flash Filename: zImage
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 90112
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename:
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 106496
Partition Block Count: 204800
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 311296
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEM
Flash Filename: modem.bin
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 344064
Partition Block Count: 1048576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FACTORYFS
Flash Filename: factoryfs.img
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 1392640
Partition Block Count: 4194304
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DATAFS
Flash Filename: data.img
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 5586944
Partition Block Count: 24133632
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: UMS
Flash Filename:
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 29720576
Partition Block Count: 1048576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:
--- Entry #14 ---
Binary Type: 1 (CP)
Device Type: 1 (File/FAT)
Identifier: 9
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 0
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name:
Flash Filename:
FOTA Filename:

---

Can someone tell me if the partitioning for a Gingerbread S2 work with a Jelly Bean ROM. I can build a PIT file off my Dads galaxy S2 which has never been touched. Not sure what it looks like yet as I need to get hold of him (and his phone).
If anyone's running JellyBean perhaps you can generate a PIT file with Heimdall and send it across to have a bash with?

---

Hutchism said:
Can someone tell me if the partitioning for a Gingerbread S2 work with a Jelly Bean ROM. I can build a PIT file off my Dads galaxy S2 which has never been touched. Not sure what it looks like yet as I need to get hold of him (and his phone).
If anyone's running JellyBean perhaps you can generate a PIT file with Heimdall and send it across to have a bash with?
Click to expand...
Click to collapse
Hi, one time I broke the partition information and I used the attached file to fix it.
I hope it helps.
Running stock jelly bean by the way.
Regards
JP

---

Thanks for digging that out for me pacmanman! I did also manage to find one for download over at Droidevelopers.com. If anyone needs pit's for future reference they have a good selection www . droidevelopers.com /f363/11722-%5Bdownload%5D-ops-pit-files.html
^Wouldn't let me post the link ^^^^
Turns out that my tables are as they should be so no cause for concern. Just a little user error on my part. Wouldn't let me write the BOOT partition, so I just left it out. To be honest I don't really understand the partitions on these things. I thought the boot partition was required, but its 0 in size. Never paid any attention to it in the past.
BIG WARNING. IF YOU DON'T KNOW WHAT YOUR DOING WITH PIT FILES THEY WILL LIKELY KILL YOUR PET RABBIT!!!!!!
Big thumbs up for Heimdall. Easy once you know how
Incidentally this was my useage:
Open 2 terminals or 1 and copy the partition lists into a text editor for reference.
"heimdall" on its own gives you the useage and options
"sudo heimdall print-pit" gives the partitions on your phone as shown in the original post.
Reference the partition names with the files in the ROM as shown below.
"sudo heimdall flash --SBL1 Sbl.bin --PARAM param.lfs --KERNEL zImage --CACHE cache.img --MODEM modem.bin --FACTORYFS factoryfs.img --HIDDEN hidden.img --verbose --no-reboot"
If anyone wants to correct me on the above please be my guest, as I just used it as surmised.

---

Your command looks perfect to me.
BTW. Heimdall/Samsung is using boot.bin and BOOT as names for the primary boot loader (and normally you shouldn't need to flash this), while on other systems boot-partition / boot.img is exactly that what Heimdall/Samsung is calling KERNEL / zImage
Sent from my Nexus 7 using xda app-developers app

---

Aaah, thank you. Excuse my ignorance, but is it reporting the block size to be 0 because it uses less than a full block for BOOT?
How do I go about writing the boot image to BOOT as I still seem to have clockworkmod on this partition and Heimdall brings up an error for this partition, assumedly because the BOOT partition is Read-Only?

---

SGS2 stores kernel and recovery combined in the kernel partition, i.e. the zImage (which is flashed to kernel partiyion) is for booting the rom as for launching recovery.
Sent from my GT-I9100 using xda app-developers app

---

I hear you there, but it seems there are actually 2 bootloaders?
i,e, there can be 2 different versions of clockworkmod installed at the same time. One is called by pressing the combination at boot. The other can be called by restarting the phone into.
After flashing the phone it restarted into a broken version of clockworkmod (similarly this same version would be called from if you have the option in android to restart in recovery mode). Switching the phone off and on again had me booting into Android, while using UP, HOME + POWER had me at the default Android recovery menu.
Quite strange....

---

Probably you have flashed one "new" kernels, I.e. Philz 4.93 or something like that. These have the possibility to boot different kernels depending on the buttons you are pressing when recovery is started. I didn't look very deep into that new feature yet, but as you describe your phones behaviour it must be something like that. Probably the 'second' kernel is again a kernel having CWM included so that your phone boots sometimes into one and other times into the other CWM.
Edit: no, I was wrong, it s not, that a different kernel is started, but you can define some boots scripts which will be executed on startup. Nevertheless also from here you can start CWM it provocate strange behavior.
Sent from my Nexus 7 using xda app-developers app

---

Read Only?
I am a noob with this but all the partitions listed on my pit file are marked as read-only and I'm curious as to whether or not these attributes can be changed to read/write so I can flash to these partitions or if that is done by flashing a different pit file and if so how do you flash just a pit file
Using heimdall on Linux mint