Samsung H1 OneNAND
From Samsung H1 Wiki
Contents |
Introduction
The Samsung H1 and M1 use a OneNAND chip with 512 Mbyte to store the System. There is generally no possibility to store data on it. Even through root access it is limited through the use of cramfs for most things.
It is formatted using Samsungs proprietary RFS filesystem/NAND flash management and contains 11 Partitions accessible over RFS as BML (block management layer) or STL (sector transaction layer).
Adresses of the BML partitions
minor position size blocks id
1: 0x00000000-0x00040000 0x00040000 2 0 2: 0x00040000-0x00640000 0x00600000 48 1 3: 0x00640000-0x00780000 0x00140000 10 2 4: 0x00780000-0x008c0000 0x00140000 10 3 5: 0x008c0000-0x00dc0000 0x00500000 40 4 6: 0x00dc0000-0x012c0000 0x00500000 40 5 7: 0x012c0000-0x02640000 0x01380000 156 6 8: 0x02640000-0x0da40000 0x0b400000 1440 7 9: 0x0da40000-0x1f280000 0x11840000 2242 8 10: 0x1f280000-0x1f380000 0x00100000 8 9 11: 0x1f380000-0x1f480000 0x00100000 8 10
Partition IDs as seen by Linux
major minor #blocks name
139 0 513280 tbmlc 139 1 256 tbml1 139 2 6144 tbml2 139 3 1280 tbml3 139 4 1280 tbml4 139 5 5120 tbml5 139 6 5120 tbml6 139 7 19968 tbml7 139 8 184320 tbml8 139 9 286976 tbml9 139 10 1024 tbml10 139 11 1024 tbml11 137 0 513280 bml0/c 137 1 256 bml1 137 2 6144 bml2 137 3 1280 bml3 137 4 1280 bml4 137 5 5120 bml5 137 6 5120 bml6 137 7 19968 bml7 137 8 184320 bml8 137 9 286976 bml9 137 10 1024 bml10 137 11 1024 bml11 138 2 5796 stl2 138 5 4674 stl5 138 9 275520 stl9
Mounting of the Partitions in the LiMo/Vodafone 360 System
/dev/root on / type cramfs (ro) /dev/stl5 on /mnt/.lfs type j4fs (rw) /dev/stl2 on /csa type rfs (rw,codepage=utf8,vfat,fcache(blks)=128,xattr) /dev/bml8 on /usr type cramfs (ro) /dev/stl9 on /mnt/rsv type rfs (rw,codepage=utf8,vfat,fcache(blks)=128,xattr)
Data from the Firmware Image contained on OneNAND
bml1 = boot.bin 262144 byte bml2 = ??? userdata? 6291456 byte bml3 = Sbl.bin 1310720 byte - (offset: 001000B80000000000000000 +bml3 = Sbl.bin) bml4 = ??? not to be found in flash-image 1310720 byte bml5 = params.lfs without a small sub-header and huge trailer (trailer seems to be the same content again -.-) 5242880 byte bml6 = kernel image zImage (j4fs,rw) 5242880 byte bml7 = initrd.cramfs 20447232 byte bml8 = factoryfs.cramfs 188743680 byte bml9 = datafs.rfs?! datafs is 1 MB bigger but content is similar 293863424 byte bml10 = EMPTY (bad block reserve?) 1048576 byte bml11 = EMPTY (bad block reserve?) 1048576 byte bml0!c = boot.bin + FFFF trailer 525598720 byte bml0/c = boot.bin + FFFF trailer 525598720 byte stl2 = /csa (rfs,rw) 5935104 byte stl5 = params.lfs (j4fs,rw) 4786176 byte stl9 = datafs.rfs userdata? /mnt/rsv (rfs,rw) 282132480 byte
