[REF] GT-I9300 PIT and Flash Analysis

Search This thread

kalagas

Senior Member
Dec 25, 2006
2,873
2,261
Crete
www.foodsafe.gr
Which *.pit-file is correct for the 32GB model?

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

Thanks for your help
 

spirol

Senior Member
I'm currently trying to get started creating my own custom rom. Setting up dsixda's kitchen went fine (cygwin-method), but the SGS3 is not supported by the kitchen by default..
Referring to "how to add new devices"-section in the thread (Thread), I started to make a file for SGS3 with the correct mount points.

So far, I've come up with the following:

# Samsung Galaxy S3 GT-I9300

change_mnt=yes

param1=ext4
param2=EMMC

param1_sdcard=vfat
param2_sdcard=MTD

sys_mnt=\/dev\/block\/mmcblk0p9
cache_mnt=\/dev\/block\/mmcblk0p8
boot_mnt=\/dev\/block\/mmcblk0p5
data_mnt=\/dev\/block\/mmcblk0p12
sdcard_mnt=\/dev\/block\/mmcblk0p??

modem_mnt=\/dev\/block\/mmcblk0p7

I've used the layout from the Galaxy SII (I9100), and then changed the mount points to those above. As you can see it's not complete and possibly incorrect.
I was wondering if anyone could help me figuring out with which mount point is used for the sdcard, and also if I should add a line for the recovery partition?
 

RazielSasy

Senior Member
Jul 6, 2012
72
12
My mmcblk0p1 is corrupt (error log says somthIng about mIssIng dIrectory). I can't format sdcard because cwm can't mount it. How can I fix this ? Thanks

Sent from my GT-I9300 using xda app-developers app
 

sorg

Senior Member
Sep 5, 2006
1,059
1,136
台灣
I was wondering if anyone could help me figuring out with which mount point is used for the sdcard, and also if I should add a line for the recovery partition?

i'm not sure which devices are supported already by that kitchen, but if there is Galaxy Nexus support, then you can get sdcard options from this device.

sdcard on SGS3 is a virtual FS mounted through FUSE. Actual location is on /data partition. /data/media if to be precise.
To mount sdcard, u need to use mounter binary /system/bin/sdcard
 
  • Like
Reactions: spirol

spirol

Senior Member
i'm not sure which devices are supported already by that kitchen, but if there is Galaxy Nexus support, then you can get sdcard options from this device.

The international Galaxy Nexus (maguro) is supported by the kitchen, and the file for that device has the following:

Code:
# Samsung Galaxy Nexus (GSM/HSPA+)

change_mnt=yes

param1=ext4
param2=HSMMC

sys_mnt=\/dev\/block\/platform\/omap\/omap_hsmmc.0\/by-name\/system
cache_mnt=\/dev\/block\/platform\/omap\/omap_hsmmc.0\/by-name\/cache
boot_mnt=\/dev\/block\/platform\/omap\/omap_hsmmc.0\/by-name\/boot
data_mnt=???
sdcard_mnt=???

fix_boot3=yes

As I already have sys, cache, boot and data, I guess I can safely ignore the differences from these.
Do you know if our SGS3 is also using HSMMC, and not EMMC?

sdcard on SGS3 is a virtual FS mounted through FUSE. Actual location is on /data partition. /data/media if to be precise.
To mount sdcard, u need to use mounter binary /system/bin/sdcard

So mounting sdcard is done in the ROM, and should not be mentioned in the kitchen file, right? Do you happen to know anything about the line saying fix_boot3=yes, what it refers to and if it is necessary for S3 compability?

Please PM me if this is not the right thread for this :)
 

sorg

Senior Member
Sep 5, 2006
1,059
1,136
台灣
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.
 
  • Like
Reactions: dsixda and spirol

eric-filth

Senior Member
Nov 18, 2011
1,510
1,013
41
Ponta Grossa - PR
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

Any expert please confirm this?

Enviado do meu GT-I9300
 

pelpa87

Senior Member
Apr 2, 2012
1,041
414
Pilar
can anyone, pleeeeaaasssseeeee, tell me wich block is the internal SDcard? mmcblk0pxx??????? and wich is it's mounting point. for using in a updater-script for CWR. i just tried everithing...but obviously i'm missing something...i can't nail it...
thanks :)

pd:(my head is burnned of all i've read today about thisssss lol :)
 

Odia

Guest
Jan 4, 2009
668
785
can anyone, pleeeeaaasssseeeee, tell me wich block is the internal SDcard? mmcblk0pxx??????? and wich is it's mounting point. for using in a updater-script for CWR. i just tried everithing...but obviously i'm missing something...i can't nail it...
thanks :)

pd:(my head is burnned of all i've read today about thisssss lol :)

mmcblk1p1
/mnt/sdcard or
/data/media
 
Last edited:
  • Like
Reactions: pelpa87

E:V:A

Inactive Recognized Developer
Dec 6, 2011
1,447
2,222
-∇ϕ
Some parts are wrong but why would you want to represent in this way?

Because it is useful to correlate what we know from before, to understand the new partition layout/format. But I agree, this is useless, unless you specify what is an SGS/SGS2. Because if it's the US versions, they're probably based on Qualcomm processors, and those devices almost always have quasi random partition schemes, because of their complicated bootloading procedure...

This is for the US SGS3 (SCH-I535) !!

Edit: Removed picture to avoid confusing people...

If you're looking for that partition table, I just posted it here.
 
Last edited:

pelpa87

Senior Member
Apr 2, 2012
1,041
414
Pilar
Sorry my bad, I wrote the wrong mount point only, rest is correct, should look like this, sorry for the confusion.

mmcblk1p1
/mnt/sdcard or
/data/media

Thx for the answer...i m faceing a problem...maybe you can help me
I'm trying to make a flashable zip where it inserts data in external memory.

So far i couldnt do it. Don't know what i'm doing wrong.
In updater script i'm mounting external sdcard...but aparently i m not doing it wright because data is not inserted when it finish.
I'm using this for mounting:
Run_program("/sbin/busybox", "mount", "t", "auto", "mmcblk1p1", "/mnt/sdcard");

And then for extracting this:
Package_extract_dir("sdcard", "/mnt/sdcard");


What am i doing wrong??

Excuse the OT...

Sent from my GT-I9300 using xda premium
 

pelpa87

Senior Member
Apr 2, 2012
1,041
414
Pilar
maybe because you have /dev/block/ missing from the partition name, but I really have no idea, the OS is too high level for me, I like the low level hardware sh1ts :p

Loooll....forgot that...
I ll try again
Thxxx
EDIT:nop still no luck....i can t nail it....thx odia for your help anyway :)..
Maybe someone else can help me??

EDIT2: FINNALLLYYY i could do itt. Using /data/media it works....using /mnt/sdcard it doesn't

THANKS AGAIN YOU GUYSSS

Thx in advance!!
Sent from my GT-I9300 using xda premium
 
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.