[REF] GT-I9300 PIT and Flash Analysis

Search This thread

Odia

Guest
Jan 4, 2009
668
785
The structure of the PIT is defined below:-

Code:
Based on PIT GT-I9300_mx_20120329.pit

Block Size = 0x200

Partition Name	Image Name	LEN		LEN in BLK	OS Partition	Physical Partition

BOOTLOADER	sboot.bin	0x000D8C00	0x06C6		0x50		0x50
TZSW		tz.img		0x00027000	0x0138		0x51		0x51
PIT		mx.pit		0x00002000	0x0010		0x46		0x46
MD5HDR		md5.img		0x00100000	0x0800		0x47		0x47
BOTA0		-		0x00400000	0x2000		0p1		0x01
BOTA1		-		0x00400000	0x2000		0p2		0x02
EFS		efs.img		0x01400000	0xA000		0p3		0x03
PARAM		param.bin	0x00800000	0x4000		0x4		0x04
BOOT		boot.img	0x00800000	0x4000		0p5		0x05
RECOVERY	recovery.img	0x00800000	0x4000		0p6		0x06
RADIO		modem.bin	0x02000000	0x10000		0p7		0x07
CACHE		cache.img	0x40000000	0x200000	0p8		0x08
SYSTEM		system.img	0x60000000	0x300000	0p9		0x09
HIDDEN		hidden.img	0x23000000	0x118000	0p10		0x0A
OTA		-		0x00800000	0x4000		0p11		0x0B
USERDATA	userdata.img	0x00000000	0x0000		0p12		0x0C


The offsets in the flash are as follows:-

Code:
Flash Reserved Area 0
Partition Name	Start Address

BL1		0x0000000000000000
BL2		0x0000000000002000
BL3		0x0000000000006000
uTZ		0x00000000000D6800
TZSW		0x00000000000D8C00
DDI		0x00000000000FFC00



Flash Reserved Area 1

<empty>


Flash User Area
Partition Name	Start Address		Mount Point

GUID Header	0x0000000000000000
GPT Header	0x0000000000000200
PIT		0x0000000000004400
MD5HDR		0x0000000000006400
BOTA0		0x0000000000400000
BOTA1		0x0000000000800000
EFS		0x0000000000C00000	/efs
PARAM		0x0000000002000000	/param
BOOT		0x0000000002800000	/boot
RECOVERY	0x0000000003000000	/recovery
RADIO		0x0000000003800000	/radio
CACHE		0x0000000005800000	/cache
SYSTEM		0x0000000045800000	/system
HIDDEN		0x00000000A5800000	/preload
OTA		0x00000000C8800000
USERDATA	0x00000000C9000000	/data	(this is grown on the remaining flash space, depending on the model 16/32/64)
 
Last edited:

rulala

Senior Member
Jan 12, 2011
385
99
I have a question

GT-I9300_mx_20120329.pit can used for 32GB(S3) ?

sorry my bad english:rolleyes:
 

Blindi1985

Senior Member
Oct 14, 2011
151
24
Linz
Which *.pit-file is correct for the 16GB Version?

GT-I9300_mx_20120220.pit
GT-I9300_mx_20120322.pit
GT-I9300_mx_20120329.pit
M0_20120220.pit
M0_20120220.pit

I dont want to flash with the wrong file

Thanks
 

ZACQ8

Senior Member
Jan 24, 2012
1,187
560
Kuwait
A noob Question, Can we access OTA partion, the OTA file which is downloaded can be accessed before flashing it?
 

E:V:A

Inactive Recognized Developer
Dec 6, 2011
1,447
2,222
-∇ϕ
It would be useful and interesting to know what is inside and the function of the various partition images. For example, why is there a cache image? I would have assumed the default cache.img should have been empty.

In addition what is the "new" TZSW partition? I've never heard of this one before. Finally, is the GT-I9300 PARAM the same as for I9100?
 

A.S._id

Inactive Recognized Developer
Sep 21, 2010
1,211
2,583
Partition Table for I9300 vs SGS&SGSII

mmcblk0p1 BOTA0 = sboot.bin = boot.bin
mmcblk0p2 BOTA1 = sboot. bin = Sbl.bin
mmcblk0p3 EFS = efs.img = efs.img
mmcblk0p4 PARAM = param.bin = param.lfs
mmcblk0p5 BOOT = boot.img = zImage
mmcblk0p6 RECOVERY = recovery.img = no
mmcblk0p7 RADIO (MODEM) = modem.bin = modem.bin
mmcblk0p8 CACHE = cache.lmg = cache.img
mmcblk0p9 SYSTEM = system.img = factoryfs.img
mmcblk0p10 HIDDEN = hidden.img = hidden.img
mmcblk0p11 OTA = data = data.img
mmcblk0p12 USERDATA = userdata.img = UMS.img
 
Last edited:

gcrutchr

Senior Member
Jun 11, 2009
1,573
739
73
Bangkok
@odia

Thanks for the infomation about mmcblk0p4 (param.bin).

There are 26 jpg images in this partition - one is the boot logo.

I replace the boot logo (logo.jpg) and reflashed mmcblk0p4, but the original boot logo is showing.

Do you know if there is a backup of this partition somewhere?
Or, if the logo.jpg (boot logo) is in the SBL partition?

I know I flashed it correctly, as I copied it back and dumped it. It was as I created it.
BTW - I had no errors on boot because of my changes.

Edit: I did clear the cache

Thanks.
 

Odia

Guest
Jan 4, 2009
668
785
@odia

Thanks for the infomation about mmcblk0p4 (param.bin).

There are 26 jpg images in this partition - one is the boot logo.

I replace the boot logo (logo.jpg) and reflashed mmcblk0p4, but the original boot logo is showing.

Do you know if there is a backup of this partition somewhere?
Or, if the logo.jpg (boot logo) is in the SBL partition?

I know I flashed it correctly, as I copied it back and dumped it. It was as I created it.
BTW - I had no errors on boot because of my changes.

Edit: I did clear the cache

Thanks.

Yes logo.jpg is also part of sboot (sboot has 8 JPEGs) so that must be taking over.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 29
    The structure of the PIT is defined below:-

    Code:
    Based on PIT GT-I9300_mx_20120329.pit
    
    Block Size = 0x200
    
    Partition Name	Image Name	LEN		LEN in BLK	OS Partition	Physical Partition
    
    BOOTLOADER	sboot.bin	0x000D8C00	0x06C6		0x50		0x50
    TZSW		tz.img		0x00027000	0x0138		0x51		0x51
    PIT		mx.pit		0x00002000	0x0010		0x46		0x46
    MD5HDR		md5.img		0x00100000	0x0800		0x47		0x47
    BOTA0		-		0x00400000	0x2000		0p1		0x01
    BOTA1		-		0x00400000	0x2000		0p2		0x02
    EFS		efs.img		0x01400000	0xA000		0p3		0x03
    PARAM		param.bin	0x00800000	0x4000		0x4		0x04
    BOOT		boot.img	0x00800000	0x4000		0p5		0x05
    RECOVERY	recovery.img	0x00800000	0x4000		0p6		0x06
    RADIO		modem.bin	0x02000000	0x10000		0p7		0x07
    CACHE		cache.img	0x40000000	0x200000	0p8		0x08
    SYSTEM		system.img	0x60000000	0x300000	0p9		0x09
    HIDDEN		hidden.img	0x23000000	0x118000	0p10		0x0A
    OTA		-		0x00800000	0x4000		0p11		0x0B
    USERDATA	userdata.img	0x00000000	0x0000		0p12		0x0C


    The offsets in the flash are as follows:-

    Code:
    Flash Reserved Area 0
    Partition Name	Start Address
    
    BL1		0x0000000000000000
    BL2		0x0000000000002000
    BL3		0x0000000000006000
    uTZ		0x00000000000D6800
    TZSW		0x00000000000D8C00
    DDI		0x00000000000FFC00
    
    
    
    Flash Reserved Area 1
    
    <empty>
    
    
    Flash User Area
    Partition Name	Start Address		Mount Point
    
    GUID Header	0x0000000000000000
    GPT Header	0x0000000000000200
    PIT		0x0000000000004400
    MD5HDR		0x0000000000006400
    BOTA0		0x0000000000400000
    BOTA1		0x0000000000800000
    EFS		0x0000000000C00000	/efs
    PARAM		0x0000000002000000	/param
    BOOT		0x0000000002800000	/boot
    RECOVERY	0x0000000003000000	/recovery
    RADIO		0x0000000003800000	/radio
    CACHE		0x0000000005800000	/cache
    SYSTEM		0x0000000045800000	/system
    HIDDEN		0x00000000A5800000	/preload
    OTA		0x00000000C8800000
    USERDATA	0x00000000C9000000	/data	(this is grown on the remaining flash space, depending on the model 16/32/64)
    3
    Partition Table for I9300 vs SGS&SGSII

    mmcblk0p1 BOTA0 = sboot.bin = boot.bin
    mmcblk0p2 BOTA1 = sboot. bin = Sbl.bin
    mmcblk0p3 EFS = efs.img = efs.img
    mmcblk0p4 PARAM = param.bin = param.lfs
    mmcblk0p5 BOOT = boot.img = zImage
    mmcblk0p6 RECOVERY = recovery.img = no
    mmcblk0p7 RADIO (MODEM) = modem.bin = modem.bin
    mmcblk0p8 CACHE = cache.lmg = cache.img
    mmcblk0p9 SYSTEM = system.img = factoryfs.img
    mmcblk0p10 HIDDEN = hidden.img = hidden.img
    mmcblk0p11 OTA = data = data.img
    mmcblk0p12 USERDATA = userdata.img = UMS.img
    2
    Yeap...but what about INTERNAL sdcard??? Thats the one is giveing me a headache...
    Thxxx
    The "internal SD card" on the S3 is actually only a subfolder of /data, the /data/media Odia mentioned above to be precise.

    It's kinda loop-mounted to /mnt/sdcard (or the /sdcard symlink) via fuse.
    2
    Here is my dump of mmcblk0boot0.

    I hope this is where the .pit file is.
    2
    I never used this kitchen. Actually, i don't know why someone still uses kitchens for android. It's not so complicated as it was in Windows Mobile.
    All you need is just deodex the ROM and put whole system files into ZIP along with installation script. You can take script from any other custom ROM close to yours, if you are not familiar with updater scripts.

    As for partitions: everything is mounted in boot.img, so you don't need to worry about it at all. I have no idea why this kitchen requires it.