Galaxy Camera Partitions

Search This thread

AdamOutler

Retired Senior Recognized Developer
Feb 18, 2011
5,224
9,809
Miami, Fl̨̞̲̟̦̀̈̃͛҃҅͟orida
Hey, I was able to make changes to the Heimdall repository to easily gain access to flashing with Linux to the Galaxy Camera. This is important because this is the only way to get a PIT file unless Samsung themselves make changes and issue a new pit.
Here is the PIT for the Samsung Galaxy Camera. http://forum.xda-developers.com/attachment.php?attachmentid=1487728&stc=1&d=1353110552


Here is the partition table:
Code:
Entry Count: 17
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 30797
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: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size: 0
Partition Block Count: 1734
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename: 


--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 81
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 1734
Partition Block Count: 312
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TZSW
Flash Filename: tz.img
FOTA Filename: 


--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: camera.pit
FOTA Filename: 


--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 50
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename: 


--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 8192
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA0
Flash Filename: -
FOTA Filename: 


--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 16384
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA1
Flash Filename: -
FOTA Filename: 


--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 24576
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename: 


--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 65536
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin
FOTA Filename: 


--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 81920
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename: 


--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 98304
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename: 


--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 114688
Partition Block Count: 65536
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RADIO
Flash Filename: modem.bin
FOTA Filename: 


--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 180224
Partition Block Count: 2097152
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename: 


--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 2277376
Partition Block Count: 3145728
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename: 


--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 5423104
Partition Block Count: 737280
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename: 


--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 6160384
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash Filename: -
FOTA Filename: 


--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 6176768
Partition Block Count: 409600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TDATA
Flash Filename: -
FOTA Filename: 


--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 6586368
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img
FOTA Filename: remained

Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...

[email protected]:~/code/heimdall/Heimdall/heimdall$
I wanted to log this here for others to use.

To reproduce the changes to Heimdall for the Galaxy Camera, you simply need to "git clone" the heimdall repo located here: https://github.com/Benjamin-Dobell/Heimdall

Then find the line that says kPIDGalaxyS2 in /Heimdall/heimdall/source/BridgeManager.h:
Code:
				kPidGalaxyS		    = 0x6601,
				[B]kPidGalaxyS2        = 0x685d,[/B]
				kPidDroidCharge     = 0x68C3

Then make Heimdall as usual. It's able to pull the Partition Information Table easily.
 

Attachments

  • GalaxyCamera-EKGC100.pit.zip
    2.3 KB · Views: 829

AdamOutler

Retired Senior Recognized Developer
Feb 18, 2011
5,224
9,809
Miami, Fl̨̞̲̟̦̀̈̃͛҃҅͟orida
... And root achieved under Linux. I spoke to Chainfire about CF AutoRoot. He requested a recovery.img. He then posted the binary here. http://download.chainfire.eu/283/CF-Root/CF-Auto-Root/CF-Auto-Root-gd1-ekgc100.zip

I extracted all files from that binary, built heimdall as above and was able to flash. Heimdall will be built for this device soon. I've submitted a ticket.

Code:
[email protected]:~/Desktop/heimdall$ /usr/local/bin/heimdall flash --cache ./cache.img --recovery ./recovery.img 
Heimdall v1.4 RC1

Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...

Checking if protocol is initialised...
Protocol is not initialised.

Initialising protocol...
Protocol initialisation successful.

Beginning session...
Session begun.

Downloading device's PIT file...
PIT file download successful.

Uploading CACHE
100%
CACHE upload successful

Uploading RECOVERY
100%
RECOVERY upload successful

Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...

[email protected]:~/Desktop/heimdall$ adb shell
[email protected]:/ $ su
[email protected]:/ #
 

E:V:A

Inactive Recognized Developer
Dec 6, 2011
1,449
2,213
-∇ϕ
Actually that list above, makes little sense. Where are the mount points and "block size" is probably not a block size etc... I'd much rather see the output from these commands...

EDIT:

BTW. Have you managed to rip this thing apart yet? I'd love to see some internal pictures...
 
Last edited:

davioxx

Senior Member
Jun 12, 2009
139
26
mexico
Hey Adam thanks for this but one question, should I use this pit file with heimdall or with odin, in both cases which firmware gave you this pit partitioning( on the mexican sgs sometimes different firmwares had different pit)

thanks!
 
  • Like
Reactions: zyawoo

AdamOutler

Retired Senior Recognized Developer
Feb 18, 2011
5,224
9,809
Miami, Fl̨̞̲̟̦̀̈̃͛҃҅͟orida
I set up a job to analyze PIT files over at http://jenkins.CASUAL-Dev.com and you can analyze PIT files with more accuracy there.

This is my own breed of Print-Pit.
Code:
PIT Name: Mx
Entry Count: 17
File Type: COM_TAR2


--- Entry #0 ---
ID: 80   Partition Name: BOOTLOADER
Filename: sboot.bin   param: md5
Block Size: 1734 (887.8kB)
Block range: 0 - 1733 (hex 0x0 - 0x6c5)
PartType: 2   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The BOOTLOADER partition, identified as partition number 80, is 887.8kB in size. It carries a Basic format and Bootloader data type. The partition resides on the AP EMMC. It identifies itself to Odin as sboot.bin   param: md5.


--- Entry #1 ---
ID: 81   Partition Name: TZSW
Filename: tz.img   param: md5
Block Size: 312 (159.7kB)
Block range: 1734 - 2045 (hex 0x6c6 - 0x7fd)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The TZSW partition, identified as partition number 81, is 159.7kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as tz.img   param: md5.


--- Entry #2 ---
ID: 70   Partition Name: PIT
Filename: camera.pit
Block Size: 16 (8.2kB)
Block range: 34 - 49 (hex 0x22 - 0x31)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The PIT partition, identified as partition number 70, is 8.2kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as camera.pit.


--- Entry #3 ---
ID: 71   Partition Name: MD5HDR
Filename: md5.img   param: in.md5
Block Size: 2048 (1.0MB)
Block range: 50 - 2097 (hex 0x32 - 0x831)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The MD5HDR partition, identified as partition number 71, is 1.0MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as md5.img   param: in.md5.


--- Entry #4 ---
ID: 1   Partition Name: BOTA0
Filename: -
Block Size: 8192 (4.2MB)
Block range: 8192 - 16383 (hex 0x2000 - 0x3fff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The BOTA0 partition, identified as partition number 1, is 4.2MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. 


--- Entry #5 ---
ID: 2   Partition Name: BOTA1
Filename: -
Block Size: 8192 (4.2MB)
Block range: 16384 - 24575 (hex 0x4000 - 0x5fff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The BOTA1 partition, identified as partition number 2, is 4.2MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. 


--- Entry #6 ---
ID: 3   Partition Name: EFS
Filename: efs.img   param: md5
Block Size: 40960 (21.0MB)
Block range: 24576 - 65535 (hex 0x6000 - 0xffff)
PartType: 5   FilesystemType: 5   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The EFS partition, identified as partition number 3, is 21.0MB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as efs.img   param: md5.


--- Entry #7 ---
ID: 4   Partition Name: PARAM
Filename: param.bin   param: md5
Block Size: 16384 (8.4MB)
Block range: 65536 - 81919 (hex 0x10000 - 0x13fff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The PARAM partition, identified as partition number 4, is 8.4MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as param.bin   param: md5.


--- Entry #8 ---
ID: 5   Partition Name: BOOT
Filename: boot.img   param: md5
Block Size: 16384 (8.4MB)
Block range: 81920 - 98303 (hex 0x14000 - 0x17fff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The BOOT partition, identified as partition number 5, is 8.4MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as boot.img   param: md5.


--- Entry #9 ---
ID: 6   Partition Name: RECOVERY
Filename: recovery.img   param: md5
Block Size: 16384 (8.4MB)
Block range: 98304 - 114687 (hex 0x18000 - 0x1bfff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The RECOVERY partition, identified as partition number 6, is 8.4MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as recovery.img   param: md5.


--- Entry #10 ---
ID: 7   Partition Name: RADIO
Filename: modem.bin   param: md5
Block Size: 65536 (33.6MB)
Block range: 114688 - 180223 (hex 0x1c000 - 0x2bfff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The RADIO partition, identified as partition number 7, is 33.6MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as modem.bin   param: md5.


--- Entry #11 ---
ID: 8   Partition Name: CACHE
Filename: cache.img   param: md5
Block Size: 2097152 (1.1GB)
Block range: 180224 - 2277375 (hex 0x2c000 - 0x22bfff)
PartType: 5   FilesystemType: 5   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The CACHE partition, identified as partition number 8, is 1.1GB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as cache.img   param: md5.


--- Entry #12 ---
ID: 9   Partition Name: SYSTEM
Filename: system.img   param: md5
Block Size: 3145728 (1.6GB)
Block range: 2277376 - 5423103 (hex 0x22c000 - 0x52bfff)
PartType: 5   FilesystemType: 5   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The SYSTEM partition, identified as partition number 9, is 1.6GB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as system.img   param: md5.


--- Entry #13 ---
ID: 10   Partition Name: HIDDEN
Filename: hidden.img   param: md5
Block Size: 737280 (377.5MB)
Block range: 5423104 - 6160383 (hex 0x52c000 - 0x5dffff)
PartType: 5   FilesystemType: 5   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The HIDDEN partition, identified as partition number 10, is 377.5MB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as hidden.img   param: md5.


--- Entry #14 ---
ID: 11   Partition Name: OTA
Filename: -
Block Size: 16384 (8.4MB)
Block range: 6160384 - 6176767 (hex 0x5e0000 - 0x5e3fff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The OTA partition, identified as partition number 11, is 8.4MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. 


--- Entry #15 ---
ID: 12   Partition Name: TDATA   param: TA
Filename: -   param: erdata.img   param: md5
Block Size: 409600 (209.7MB)
Block range: 6176768 - 6586367 (hex 0x5e4000 - 0x647fff)
PartType: 5   FilesystemType: 5   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA:    param: emained
The TDATA   param: TA partition, identified as partition number 12, is 209.7MB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. 


--- Entry #16 ---
ID: 13   Partition Name: USERDATA
Filename: userdata.img
Block Size: 0 (0B)
Block range: 6586368 - 6586367 (hex 0x648000 - 0x647fff)
PartType: 5   FilesystemType: 5   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: remained
The USERDATA partition, identified as partition number 13, is 0B in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as userdata.img. The partition will expand to fill the remainder of the EMMC.

Here's the PIT file: http://d-h.st/3B3
Here's the link where you can analyze a PIT: http://jenkins.casual-dev.com/job/Analyze PIT File/build?delay=0sec
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    Hey, I was able to make changes to the Heimdall repository to easily gain access to flashing with Linux to the Galaxy Camera. This is important because this is the only way to get a PIT file unless Samsung themselves make changes and issue a new pit.
    Here is the PIT for the Samsung Galaxy Camera. http://forum.xda-developers.com/attachment.php?attachmentid=1487728&stc=1&d=1353110552


    Here is the partition table:
    Code:
    Entry Count: 17
    Unknown 1: 1598902083
    Unknown 2: 844251476
    Unknown 3: 30797
    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: 80
    Attributes: 2 (STL Read-Only)
    Update Attributes: 1 (FOTA)
    Partition Block Size: 0
    Partition Block Count: 1734
    File Offset (Obsolete): 0
    File Size (Obsolete): 0
    Partition Name: BOOTLOADER
    Flash Filename: sboot.bin
    FOTA Filename: 
    
    
    --- Entry #1 ---
    Binary Type: 0 (AP)
    Device Type: 2 (MMC)
    Identifier: 81
    Attributes: 5 (Read/Write)
    Update Attributes: 1 (FOTA)
    Partition Block Size: 1734
    Partition Block Count: 312
    File Offset (Obsolete): 0
    File Size (Obsolete): 0
    Partition Name: TZSW
    Flash Filename: tz.img
    FOTA Filename: 
    
    
    --- Entry #2 ---
    Binary Type: 0 (AP)
    Device Type: 2 (MMC)
    Identifier: 70
    Attributes: 5 (Read/Write)
    Update Attributes: 1 (FOTA)
    Partition Block Size: 34
    Partition Block Count: 16
    File Offset (Obsolete): 0
    File Size (Obsolete): 0
    Partition Name: PIT
    Flash Filename: camera.pit
    FOTA Filename: 
    
    
    --- Entry #3 ---
    Binary Type: 0 (AP)
    Device Type: 2 (MMC)
    Identifier: 71
    Attributes: 5 (Read/Write)
    Update Attributes: 1 (FOTA)
    Partition Block Size: 50
    Partition Block Count: 2048
    File Offset (Obsolete): 0
    File Size (Obsolete): 0
    Partition Name: MD5HDR
    Flash Filename: md5.img
    FOTA Filename: 
    
    
    --- Entry #4 ---
    Binary Type: 0 (AP)
    Device Type: 2 (MMC)
    Identifier: 1
    Attributes: 5 (Read/Write)
    Update Attributes: 1 (FOTA)
    Partition Block Size: 8192
    Partition Block Count: 8192
    File Offset (Obsolete): 0
    File Size (Obsolete): 0
    Partition Name: BOTA0
    Flash Filename: -
    FOTA Filename: 
    
    
    --- Entry #5 ---
    Binary Type: 0 (AP)
    Device Type: 2 (MMC)
    Identifier: 2
    Attributes: 5 (Read/Write)
    Update Attributes: 1 (FOTA)
    Partition Block Size: 16384
    Partition Block Count: 8192
    File Offset (Obsolete): 0
    File Size (Obsolete): 0
    Partition Name: BOTA1
    Flash Filename: -
    FOTA Filename: 
    
    
    --- Entry #6 ---
    Binary Type: 0 (AP)
    Device Type: 2 (MMC)
    Identifier: 3
    Attributes: 5 (Read/Write)
    Update Attributes: 5 (FOTA)
    Partition Block Size: 24576
    Partition Block Count: 40960
    File Offset (Obsolete): 0
    File Size (Obsolete): 0
    Partition Name: EFS
    Flash Filename: efs.img
    FOTA Filename: 
    
    
    --- Entry #7 ---
    Binary Type: 0 (AP)
    Device Type: 2 (MMC)
    Identifier: 4
    Attributes: 5 (Read/Write)
    Update Attributes: 1 (FOTA)
    Partition Block Size: 65536
    Partition Block Count: 16384
    File Offset (Obsolete): 0
    File Size (Obsolete): 0
    Partition Name: PARAM
    Flash Filename: param.bin
    FOTA Filename: 
    
    
    --- Entry #8 ---
    Binary Type: 0 (AP)
    Device Type: 2 (MMC)
    Identifier: 5
    Attributes: 5 (Read/Write)
    Update Attributes: 1 (FOTA)
    Partition Block Size: 81920
    Partition Block Count: 16384
    File Offset (Obsolete): 0
    File Size (Obsolete): 0
    Partition Name: BOOT
    Flash Filename: boot.img
    FOTA Filename: 
    
    
    --- Entry #9 ---
    Binary Type: 0 (AP)
    Device Type: 2 (MMC)
    Identifier: 6
    Attributes: 5 (Read/Write)
    Update Attributes: 1 (FOTA)
    Partition Block Size: 98304
    Partition Block Count: 16384
    File Offset (Obsolete): 0
    File Size (Obsolete): 0
    Partition Name: RECOVERY
    Flash Filename: recovery.img
    FOTA Filename: 
    
    
    --- Entry #10 ---
    Binary Type: 0 (AP)
    Device Type: 2 (MMC)
    Identifier: 7
    Attributes: 5 (Read/Write)
    Update Attributes: 1 (FOTA)
    Partition Block Size: 114688
    Partition Block Count: 65536
    File Offset (Obsolete): 0
    File Size (Obsolete): 0
    Partition Name: RADIO
    Flash Filename: modem.bin
    FOTA Filename: 
    
    
    --- Entry #11 ---
    Binary Type: 0 (AP)
    Device Type: 2 (MMC)
    Identifier: 8
    Attributes: 5 (Read/Write)
    Update Attributes: 5 (FOTA)
    Partition Block Size: 180224
    Partition Block Count: 2097152
    File Offset (Obsolete): 0
    File Size (Obsolete): 0
    Partition Name: CACHE
    Flash Filename: cache.img
    FOTA Filename: 
    
    
    --- Entry #12 ---
    Binary Type: 0 (AP)
    Device Type: 2 (MMC)
    Identifier: 9
    Attributes: 5 (Read/Write)
    Update Attributes: 5 (FOTA)
    Partition Block Size: 2277376
    Partition Block Count: 3145728
    File Offset (Obsolete): 0
    File Size (Obsolete): 0
    Partition Name: SYSTEM
    Flash Filename: system.img
    FOTA Filename: 
    
    
    --- Entry #13 ---
    Binary Type: 0 (AP)
    Device Type: 2 (MMC)
    Identifier: 10
    Attributes: 5 (Read/Write)
    Update Attributes: 5 (FOTA)
    Partition Block Size: 5423104
    Partition Block Count: 737280
    File Offset (Obsolete): 0
    File Size (Obsolete): 0
    Partition Name: HIDDEN
    Flash Filename: hidden.img
    FOTA Filename: 
    
    
    --- Entry #14 ---
    Binary Type: 0 (AP)
    Device Type: 2 (MMC)
    Identifier: 11
    Attributes: 5 (Read/Write)
    Update Attributes: 1 (FOTA)
    Partition Block Size: 6160384
    Partition Block Count: 16384
    File Offset (Obsolete): 0
    File Size (Obsolete): 0
    Partition Name: OTA
    Flash Filename: -
    FOTA Filename: 
    
    
    --- Entry #15 ---
    Binary Type: 0 (AP)
    Device Type: 2 (MMC)
    Identifier: 12
    Attributes: 5 (Read/Write)
    Update Attributes: 5 (FOTA)
    Partition Block Size: 6176768
    Partition Block Count: 409600
    File Offset (Obsolete): 0
    File Size (Obsolete): 0
    Partition Name: TDATA
    Flash Filename: -
    FOTA Filename: 
    
    
    --- Entry #16 ---
    Binary Type: 0 (AP)
    Device Type: 2 (MMC)
    Identifier: 13
    Attributes: 5 (Read/Write)
    Update Attributes: 5 (FOTA)
    Partition Block Size: 6586368
    Partition Block Count: 0
    File Offset (Obsolete): 0
    File Size (Obsolete): 0
    Partition Name: USERDATA
    Flash Filename: userdata.img
    FOTA Filename: remained
    
    Ending session...
    Rebooting device...
    Releasing device interface...
    Re-attaching kernel driver...
    
    [email protected]:~/code/heimdall/Heimdall/heimdall$
    I wanted to log this here for others to use.

    To reproduce the changes to Heimdall for the Galaxy Camera, you simply need to "git clone" the heimdall repo located here: https://github.com/Benjamin-Dobell/Heimdall

    Then find the line that says kPIDGalaxyS2 in /Heimdall/heimdall/source/BridgeManager.h:
    Code:
    				kPidGalaxyS		    = 0x6601,
    				[B]kPidGalaxyS2        = 0x685d,[/B]
    				kPidDroidCharge     = 0x68C3

    Then make Heimdall as usual. It's able to pull the Partition Information Table easily.
    2
    ... And root achieved under Linux. I spoke to Chainfire about CF AutoRoot. He requested a recovery.img. He then posted the binary here. http://download.chainfire.eu/283/CF-Root/CF-Auto-Root/CF-Auto-Root-gd1-ekgc100.zip

    I extracted all files from that binary, built heimdall as above and was able to flash. Heimdall will be built for this device soon. I've submitted a ticket.

    Code:
    [email protected]:~/Desktop/heimdall$ /usr/local/bin/heimdall flash --cache ./cache.img --recovery ./recovery.img 
    Heimdall v1.4 RC1
    
    Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
    http://www.glassechidna.com.au/
    
    This software is provided free of charge. Copying and redistribution is
    encouraged.
    
    If you appreciate this software and you would like to support future
    development please consider donating:
    http://www.glassechidna.com.au/donate/
    
    Initialising connection...
    Detecting device...
    Claiming interface...
    Attempt failed. Detaching driver...
    Claiming interface again...
    Setting up interface...
    
    Checking if protocol is initialised...
    Protocol is not initialised.
    
    Initialising protocol...
    Protocol initialisation successful.
    
    Beginning session...
    Session begun.
    
    Downloading device's PIT file...
    PIT file download successful.
    
    Uploading CACHE
    100%
    CACHE upload successful
    
    Uploading RECOVERY
    100%
    RECOVERY upload successful
    
    Ending session...
    Rebooting device...
    Releasing device interface...
    Re-attaching kernel driver...
    
    [email protected]:~/Desktop/heimdall$ adb shell
    [email protected]:/ $ su
    [email protected]:/ #
    1
    Hey Adam thanks for this but one question, should I use this pit file with heimdall or with odin, in both cases which firmware gave you this pit partitioning( on the mexican sgs sometimes different firmwares had different pit)

    thanks!
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone