Root Lets get ops mapping for ALL partitions

[saschaelble]

I FOUND ALL THE PARTITION NAMES!!!

Spoiler

bml1 address 0008:1010 AND a second almost exact copy at 0008:9010
0:MIBIB..................... bml1 mibib
0:QCSBL..................... bml2 qcsbl
0:OEMSBL1................... bml3 oemsbl1
0:AMSS...........F.......... bml4 amss
0:EFS2...........2.......... bml5 cdma.rfs aka /efs
0:NVBACKUP.................. bml6 Nvbackup (you pricks thats why flashing bml5 fails isnt it!!!)
0:FOTA...................... bml7 Firmware Over the Air. Which explains all the fffffffff's
0:APPSBL.................... bml8?? arm11boot... odd name doesnt match but its in order!
0:APPS...........(.......... bml9?? boot.img (linux kernel + ramdisk) also odd, but its in order!
0:RECOVERY.......(.......... bml10 recovery.img
0ARAM..................... bml11 Param?? Whats that? lol
0:SYSAPPS................... bml12 system partition
0ATA...................... bml13 data partition
0:CACHE.........D........... bml14 cache partitionn


bml3
0004B950
.[b.d(W..(W.
0:ALL...
0:QCSBL.x.c.
0:AMSS..
0:APPSBL....x.b.
0:APPS..x.b.
0:EFS2..
0:EFS2APPS..
0:SYSAPPS...
0ATA..
0:CACHE.
0:FOTA..
0SP1..
0SP2..x+c.

All partitions on prevail/precedent:

odin slot .... major ..... minor ........ #blocks ........... name ....... known use

..................179 .......... 0 .......... 3870720.......... mmcblk0..... Main Memory
..................179 .......... 1 .......... 3869696 .......... mmcblk0p1 Main memory with offset? (room for bad block mapping??)
..................137 .......... 0 ............ 513024 .......... bml0/c........????
0.................137 .......... 1 ............... 1536 .......... bml1 ........... mibib
1.................137 .......... 2 ................. 768 .......... bml2 ........... qcsbl
2.................137 .......... 3 ................. 768 .......... bml3 ........... oemsbl
3.................137 .......... 4 .............. 17920 .......... bml4 ........... amss
..................137 .......... 5 .............. 12800 .......... bml5 ........... cdma.rfs aka /efs
..................137 .......... 6 ................. 768 .......... bml6 ........... NVBACKUP
..................137 .......... 7 ................ 6144.......... bml7 ............ FOTA - all ffffffffffffs
4.................137 .......... 8 ................ 2048 .......... bml8 ........... arm11boot
5.................137 .......... 9 .............. 10240 .......... bml9 ............ boot.img (linux kernel + ramsdisk )
6.................137 .......... 10 ............. 10240 .......... bml10 .......... recovery.img
..................137 .......... 11 ............... 768 .......... bml11 ........... PARAM
..................137 .......... 12 .......... 173568 .......... bml12 ........... system partition
..................137 .......... 13 ........... 173056 .......... bml13 .......... data partition
..................137 .......... 14 ........... 102400 .......... bml14 .......... cache partition
7.................138 .......... 12 ........... 166912 .......... stl12 ........... system partition w/ bad block mapping
8..................138 .......... 13 ........... 166400 .......... stl13 ........... data partition w/ bad block mapping
..................138 .......... 14 ............ 97280 .......... stl14 ............ cache partition w/ bad block mapping

Device mounts:

Spoiler

rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl14 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioch
arset=utf8 0 0
/dev/stl12 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=u
tf8 0 0
Is realtime really spelt relatime ^ in android??????

device blocks (I WANT THAT MMC!!! BACKUP THE WHOLE PHONE)
Block devices:
1 ramdisk
259 blkext
7 loop
137 bml
138 stl
179 mmc

*note pda.tar prefers the smaller stl partiton for system and data instead of the bml partitions...
What is bml* and stl* actually mean:

Spoiler

Samsung uses its own layering of ways to access the actual flash chips. The idea is that on top of the low level NAND controller (and driver) a module takes care of wear leveling. This module is called XSR (eXtended Sector Remapper) and consits of two separate layers: BML (Block Management Layer) which exposes the NAND blocks directly and the STL (Sector Translation Layer) which exposes the remapped sectors.

What you generally see is that BML partitions contain 'static' data (bootloaders, boot / recovery images) and STL partitions contain 'live' filesystem (on android: /system, /data, /cache, /efs, /dbdata). The idea is that things directly on an BML partition don't change very often and wear leveling isn't required. Read/write filesystems however, do benefit from wear leveling and are thus placed on an STL partition.

On Linux, the kernel exposes both variants of the same device (bml and stl) at the same time through /dev/bmlXX and /dev/stlXX.

From what I've gathered bml is essentially a lower level interface to the same blocks accessed by stl, but the results differ somewhat in resulting file size.

What is the CSC partition? [/spoiler]

Spoiler

CSC is an acronym for Carrier/Country Specific Code. The csc.rfs file is a partition image file that, as far as I can tell, is merged with the contents of the system.rfs partition. In our case, the CSC file would contain the APN settings, as well as the Bell proprietary apps like self-serve and remote PVR.

Instead, since I took the system partition from a live phone, the CSC content is already in the system.rfs partition. I think the idea behind this is that Samsung can release new CSC packages without having to update the whole firmware when "new" carriers add the phone to their lineup.

boot.tar contains
BML1 MIBIB
BML2 QCSBL
BML3 OEMSBL
BML8 ARM11BOOT

phone.tar contains
BML4 AMSS

pda.tar contains
BML9 BOOT.IMG
BML10 RECOVERY.IMG
STL12 SYSTEM RFS
STL13 DATA RFS

 

[tfKamran]

I FOUND ALL THE PARTITION NAMES!!!

Spoiler

bml1 address 0008:1010 AND a second almost exact copy at 0008:9010
0:MIBIB..................... bml1 mibib
0:QCSBL..................... bml2 qcsbl
0:OEMSBL1................... bml3 oemsbl1
0:AMSS...........F.......... bml4 amss
0:EFS2...........2.......... bml5 cdma.rfs aka /efs
0:NVBACKUP.................. bml6 Nvbackup (you pricks thats why flashing bml5 fails isnt it!!!)
0:FOTA...................... bml7 Firmware Over the Air. Which explains all the fffffffff's
0:APPSBL.................... bml8?? arm11boot... odd name doesnt match but its in order!
0:APPS...........(.......... bml9?? boot.img (linux kernel + ramdisk) also odd, but its in order!
0:RECOVERY.......(.......... bml10 recovery.img
0ARAM..................... bml11 Param?? Whats that? lol
0:SYSAPPS................... bml12 system partition
0ATA...................... bml13 data partition
0:CACHE.........D........... bml14 cache partitionn


bml3
0004B950
.[b.d(W..(W.
0:ALL...
0:QCSBL.x.c.
0:AMSS..
0:APPSBL....x.b.
0:APPS..x.b.
0:EFS2..
0:EFS2APPS..
0:SYSAPPS...
0ATA..
0:CACHE.
0:FOTA..
0SP1..
0SP2..x+c.

All partitions on prevail/precedent:

odin slot .... major ..... minor ........ #blocks ........... name ....... known use

..................179 .......... 0 .......... 3870720.......... mmcblk0..... Main Memory
..................179 .......... 1 .......... 3869696 .......... mmcblk0p1 Main memory with offset? (room for bad block mapping??)
..................137 .......... 0 ............ 513024 .......... bml0/c........????
0.................137 .......... 1 ............... 1536 .......... bml1 ........... mibib
1.................137 .......... 2 ................. 768 .......... bml2 ........... qcsbl
2.................137 .......... 3 ................. 768 .......... bml3 ........... oemsbl
3.................137 .......... 4 .............. 17920 .......... bml4 ........... amss
..................137 .......... 5 .............. 12800 .......... bml5 ........... cdma.rfs aka /efs
..................137 .......... 6 ................. 768 .......... bml6 ........... NVBACKUP
..................137 .......... 7 ................ 6144.......... bml7 ............ FOTA - all ffffffffffffs
4.................137 .......... 8 ................ 2048 .......... bml8 ........... arm11boot
5.................137 .......... 9 .............. 10240 .......... bml9 ............ boot.img (linux kernel + ramsdisk )
6.................137 .......... 10 ............. 10240 .......... bml10 .......... recovery.img
..................137 .......... 11 ............... 768 .......... bml11 ........... PARAM
..................137 .......... 12 .......... 173568 .......... bml12 ........... system partition
..................137 .......... 13 ........... 173056 .......... bml13 .......... data partition
..................137 .......... 14 ........... 102400 .......... bml14 .......... cache partition
7.................138 .......... 12 ........... 166912 .......... stl12 ........... system partition w/ bad block mapping
8..................138 .......... 13 ........... 166400 .......... stl13 ........... data partition w/ bad block mapping
..................138 .......... 14 ............ 97280 .......... stl14 ............ cache partition w/ bad block mapping

Device mounts:

Spoiler

rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl14 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioch
arset=utf8 0 0
/dev/stl12 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=u
tf8 0 0
Is realtime really spelt relatime ^ in android??????

device blocks (I WANT THAT MMC!!! BACKUP THE WHOLE PHONE)
Block devices:
1 ramdisk
259 blkext
7 loop
137 bml
138 stl
179 mmc

*note pda.tar prefers the smaller stl partiton for system and data instead of the bml partitions...
What is bml* and stl* actually mean:

Spoiler

Samsung uses its own layering of ways to access the actual flash chips. The idea is that on top of the low level NAND controller (and driver) a module takes care of wear leveling. This module is called XSR (eXtended Sector Remapper) and consits of two separate layers: BML (Block Management Layer) which exposes the NAND blocks directly and the STL (Sector Translation Layer) which exposes the remapped sectors.

What you generally see is that BML partitions contain 'static' data (bootloaders, boot / recovery images) and STL partitions contain 'live' filesystem (on android: /system, /data, /cache, /efs, /dbdata). The idea is that things directly on an BML partition don't change very often and wear leveling isn't required. Read/write filesystems however, do benefit from wear leveling and are thus placed on an STL partition.

On Linux, the kernel exposes both variants of the same device (bml and stl) at the same time through /dev/bmlXX and /dev/stlXX.

From what I've gathered bml is essentially a lower level interface to the same blocks accessed by stl, but the results differ somewhat in resulting file size.

What is the CSC partition? [/spoiler]

Spoiler

CSC is an acronym for Carrier/Country Specific Code. The csc.rfs file is a partition image file that, as far as I can tell, is merged with the contents of the system.rfs partition. In our case, the CSC file would contain the APN settings, as well as the Bell proprietary apps like self-serve and remote PVR.

Instead, since I took the system partition from a live phone, the CSC content is already in the system.rfs partition. I think the idea behind this is that Samsung can release new CSC packages without having to update the whole firmware when "new" carriers add the phone to their lineup.

boot.tar contains
BML1 MIBIB
BML2 QCSBL
BML3 OEMSBL
BML8 ARM11BOOT

phone.tar contains
BML4 AMSS

pda.tar contains
BML9 BOOT.IMG
BML10 RECOVERY.IMG
STL12 SYSTEM RFS
STL13 DATA RFS

How did you find out which bml partition is you recovery partition?
Can you help me with this?

 

[vipersinu2]

this is intersing post, can i fix my phone? I have prevail stuck in airplane mode with corrupt efs, I did a dd if=/stl5.dd of=/dev/block/stl5, I have all info to restore cdma.rfs but needing some help restoring files.