[REF] GT-I9100 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 u1_02_20110310_emmc_EXT4.pit

Partition Name	LEN		LEN in BLK	OS Partition	Physical Partition

GANG		00000000	0000				0
BOOT		00000000	0000				1
EFS		013FFFFF	00A0		0p1		4
SBL1		0013FFFF	000A		0p2		2
SBL2		0013FFFF	000A		0p3		3
PARAM		007FFFFF	0040		0p4		5
KERNEL		007FFFFF	0040		0p5		6
RECOVERY	007FFFFF	0040		0p6		7
CACHE		063FFFFF	0320		0p7		8
MODEM		00FFFFFF	0080		0p8		9
FACTORYFS	1FFFFFFF	1000		0p9		a
DATAFS		7FFFFFFF	4000		0p10		b
UMS		2E07FFFFF	1704000		0p11		c
HIDDEN		1FFFFFFF	1000		0p12		d


The offsets in the flash are as follows:-

Code:
Partition Name	START

GANG		0x0000000000000000
BOOT		0x0000000000000000
PIT		0x0000000000004400
EFS		0x0000000000400000
SBL1		0x0000000001800000
SBL2		0x0000000001A00000
PARAM		0x0000000001c00000
KERNEL		0x0000000002400000
RECOVERY	0x0000000002C00000
CACHE		0x0000000003400000
MODEM		0x0000000009800000
FACTORYFS	0x000000000A800000
DATAFS		0x000000002A800000
UMS		0x00000000AA800000
HIDDEN		0x000000038B000000

SBL1 v SBL2 Explanation

The system (SBL) when downloading checks which SBL is active, this is done via a marker, in the GT-I9100 this is SNBL (GT-I9000 was OFNI, INFO in correct endian) and the SBL being downloaded is flashed to the opposite SBL partition, this is a safe guard and is how the 301k resistor on the ID pin can still enter DLM, it does not care which SBL is active, just some SBL can be executed.

Boot Sequence

iRBL > EBL > IBL > PBL > SBL

iRBL = iROM Bootloader (0x02000000)
EBL = Encrypted Bootloader (0x02021400)
IBL = Initial Bootloader (0x02023400)
PBL = Primitive Bootloader (0x4D300000)
SBL = Secondary Bootloader (0x4D400000)
 
Last edited:

tamas970

Senior Member
Jan 2, 2010
88
3
hi Odia,

Many thanks for sharing, I can just blame myself not checking this tread before: I formatted my mmcblk0p2 partition->result: bricked phone, doesn't even show the galaxy or battery logo. On top of that, no download or factory reset mode.

What you are writing here gives me hope, that a JIG can help... I don't understand, why SBL2 doesn't come out with a button combination (or in normal download mode). Is there a documentation on SBL2 somewhere?
 

Odia

Guest
Jan 4, 2009
668
785
hi Odia,

Many thanks for sharing, I can just blame myself not checking this tread before: I formatted my mmcblk0p2 partition->result: bricked phone, doesn't even show the galaxy or battery logo. On top of that, no download or factory reset mode.

What you are writing here gives me hope, that a JIG can help... I don't understand, why SBL2 doesn't come out with a button combination (or in normal download mode). Is there a documentation on SBL2 somewhere?

Ouch, I hope you have at least updated the firmware once on your phone, if its from new and never flashed then 0p3 will also be empty and that is bad news for you. There is no real documentation on the SBLs, but I understand them, what are you thinking?
 
  • Like
Reactions: tamas970

tamas970

Senior Member
Jan 2, 2010
88
3
Ouch, I hope you have at least updated the firmware once on your phone, if its from new and never flashed then 0p3 will also be empty and that is bad news for you. There is no real documentation on the SBLs, but I understand them, what are you thinking?

Oucha. Only the kernel was flashed for rooting, I am heading to the local repair service, I hope they have a jtag.

on documentation I meant only infos, such as you mentioned, if the backup partition is populated with the right stuff or not...
 

tamas970

Senior Member
Jan 2, 2010
88
3
The backup partition will be populated if you have updated the firmware at least once, but flashing just a kernel does not count.

Sad... I was hoping, that doing something in download mode already initiated the backup. I guess in the factory they directly flashed KE2 on it, but let's see what the service says...

I see the recovery (0p6) is also empty.

Thanks anyway!
 
Last edited:

tamas970

Senior Member
Jan 2, 2010
88
3
Just a weird idea: is it possible, to put a bootloader on the microSD and boot from there?
 

Mackzen

Senior Member
Apr 20, 2009
125
40
I hope this is the right thread to post this.

What is data.img for file? It seem it make an hard reset if you flash it.

It contains most zeros.
 

Attachments

  • data.zip
    44.3 KB · Views: 354

Odia

Guest
Jan 4, 2009
668
785
I hope this is the right thread to post this.

What is data.img for file? It seem it make an hard reset if you flash it.

It contains most zeros.

Probably is the wrong place for your post, but I will try to help anyway.

Need some more information, like where did you get this file from?
 

Odia

Guest
Jan 4, 2009
668
785
  • Like
Reactions: Mackzen

mimstyle

Senior Member
Jun 18, 2010
79
2
I can put a KE7 pit on my android 2.3.4 with KG2?

Where i can find it?

Because there are some lag in home screen.
 

Top Liked Posts

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

    Code:
    Based on PIT u1_02_20110310_emmc_EXT4.pit
    
    Partition Name	LEN		LEN in BLK	OS Partition	Physical Partition
    
    GANG		00000000	0000				0
    BOOT		00000000	0000				1
    EFS		013FFFFF	00A0		0p1		4
    SBL1		0013FFFF	000A		0p2		2
    SBL2		0013FFFF	000A		0p3		3
    PARAM		007FFFFF	0040		0p4		5
    KERNEL		007FFFFF	0040		0p5		6
    RECOVERY	007FFFFF	0040		0p6		7
    CACHE		063FFFFF	0320		0p7		8
    MODEM		00FFFFFF	0080		0p8		9
    FACTORYFS	1FFFFFFF	1000		0p9		a
    DATAFS		7FFFFFFF	4000		0p10		b
    UMS		2E07FFFFF	1704000		0p11		c
    HIDDEN		1FFFFFFF	1000		0p12		d


    The offsets in the flash are as follows:-

    Code:
    Partition Name	START
    
    GANG		0x0000000000000000
    BOOT		0x0000000000000000
    PIT		0x0000000000004400
    EFS		0x0000000000400000
    SBL1		0x0000000001800000
    SBL2		0x0000000001A00000
    PARAM		0x0000000001c00000
    KERNEL		0x0000000002400000
    RECOVERY	0x0000000002C00000
    CACHE		0x0000000003400000
    MODEM		0x0000000009800000
    FACTORYFS	0x000000000A800000
    DATAFS		0x000000002A800000
    UMS		0x00000000AA800000
    HIDDEN		0x000000038B000000

    SBL1 v SBL2 Explanation

    The system (SBL) when downloading checks which SBL is active, this is done via a marker, in the GT-I9100 this is SNBL (GT-I9000 was OFNI, INFO in correct endian) and the SBL being downloaded is flashed to the opposite SBL partition, this is a safe guard and is how the 301k resistor on the ID pin can still enter DLM, it does not care which SBL is active, just some SBL can be executed.

    Boot Sequence

    iRBL > EBL > IBL > PBL > SBL

    iRBL = iROM Bootloader (0x02000000)
    EBL = Encrypted Bootloader (0x02021400)
    IBL = Initial Bootloader (0x02023400)
    PBL = Primitive Bootloader (0x4D300000)
    SBL = Secondary Bootloader (0x4D400000)
    3
    I can put a KE7 pit on my android 2.3.4 with KG2?

    Where i can find it?

    Because there are some lag in home screen.

    My car is getting lousy fuel economy, can someone tell me how to fit a new radio antenna to fix please?
    2
    on documentation I meant only infos, such as you mentioned, if the backup partition is populated with the right stuff or not...

    The backup partition will be populated if you have updated the firmware at least once, but flashing just a kernel does not count.
    2
    Just a weird idea: is it possible, to put a bootloader on the microSD and boot from there?

    Thats not as weird as you may think ;)
    1
    Hi,

    My SGS2 is bricked. I've already opened a post here.

    I was running Slim Bean ROM (4.2.2) without any problem for more than a month.
    However, few days ago it was suffering some lag and I decided to reboot.
    Since then, it remains in Samsung logo screen and nothing happens.

    I can access Download mode and Recovery.
    Nevertheless, Recovery mode doesn't show any options so I'm not able to do a wipe or install a new ROM from there.


    I've been trying anything with Odin (flashing recovery, kernel, stock firmware...) and I always get an error in NAND write Start! statement.

    I discovered Heimdall last night by chance and I tried to flash a kernel with it. Didn't work.

    Could you lend a hand on this? Find attached my results for "heimdall print-pit" command.


    Thanks in advance,
    Mario.