NAND Partitioning

---

Hey I just tried to repartition my NAND for some testing but it seams something don't like that I'm doing that. first the fdisk-log of my changes:

Command (m for help): n
First cylinder (13-122496, default 13):
Using default value 13
Last cylinder or +size or +sizeM or +sizeK (13-16, default 16):
Using default value 16
Since here I had a a new partition(mmcblk1p26) at the end of the table
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
After that the kernel only showed me 21 partitions instead of 26. Seems something really went wrong. A reboot ended in bootloader failure-message. Had to flash an sbf...

Is it just some configuration-problem or is the partition-table signed?

If there was a 'tag' feature like facebook here on xda, I would have tagged Epsylon3 in this thread

bdw, what will be the benefit of partitioning NAND.

It was just an experiment. If it would work we could resize the system-partition to a minimum and create a new one in ext4-format and toys like that

But it takes much time to test this because if it does not work you have to flash an sbf

Originally Posted by m11kkaa

It was just an experiment. If it would work we could resize the system-partition to a minimum and create a new one in ext4-format and toys like that

But it takes much time to test this because if it does not work you have to flash an sbf

I have seen something like this in wildfire forum a long ago.

http://forum.xda-developers.com/show....php?t=1233340

just to archive:

Original Partition-Table(Normal-Mode):

Disk /dev/block/mmcblk1: 1958 MB, 1958739968 bytes
16 heads, 16 sectors/track, 14944 cylinders
Units = cylinders of 256 * 512 = 131072 bytes

              Device Boot      Start         End      Blocks  Id System
/dev/block/mmcblk1p1   *           2           2         128  83 Linux
/dev/block/mmcblk1p2               5           8         512  83 Linux
/dev/block/mmcblk1p3               9          12         512  83 Linux
/dev/block/mmcblk1p4              13      122496    15677952   5 Extended
/dev/block/mmcblk1p5              17          20         512  83 Linux
/dev/block/mmcblk1p6              21          24         512  83 Linux
/dev/block/mmcblk1p7              25          56        4096  83 Linux
/dev/block/mmcblk1p8              57          60         512  83 Linux
/dev/block/mmcblk1p9              61          64         512  83 Linux
/dev/block/mmcblk1p10             65          72        1024  83 Linux
/dev/block/mmcblk1p11             73          88        2048  83 Linux
/dev/block/mmcblk1p12             89          92         512  83 Linux
/dev/block/mmcblk1p13             93          96         512  83 Linux
/dev/block/mmcblk1p14             97         128        4096  83 Linux
/dev/block/mmcblk1p15            129         192        8192  83 Linux
/dev/block/mmcblk1p16            193         256        8192  83 Linux
/dev/block/mmcblk1p17            257         368       14336  83 Linux
/dev/block/mmcblk1p18            369         372         512  83 Linux
/dev/block/mmcblk1p19            373         376         512  83 Linux
/dev/block/mmcblk1p20            377         408        4096  83 Linux
/dev/block/mmcblk1p21            409        3024      334848  83 Linux
/dev/block/mmcblk1p22           3025        3028         512  83 Linux
/dev/block/mmcblk1p23           3029        3032         512  83 Linux
/dev/block/mmcblk1p24           3033        4632      204800  83 Linux
/dev/block/mmcblk1p25           4633      122496    15086592  83 Linux

Original Partition-Table(Expert-Mode):

Disk /dev/block/mmcblk1: 16 heads, 16 sectors, 14944 cylinders

Nr AF  Hd Sec  Cyl  Hd Sec  Cyl      Start       Size ID
 1 80   0   1    1  15  16    1        256        256 83
 2 00   0   1    4  15  16    7       1024       1024 83
 3 00   0   1    8  15  16   11       2048       1024 83
 4 00   0   1   12  15  16  639       3072   31355904 05
 5 00   0   1    4  15  16    7       1024       1024 83
 6 00  15  16    7  15  15   11       2047       1024 83
 7 00  15  15   11  15  14   43       3070       8192 83
 8 00  15  14   43  15  13   47      11261       1024 83
 9 00  15  13   47  15  12   51      12284       1024 83
10 00  15  12   51  15  11   59      13307       2048 83
11 00  15  11   59  15  10   75      15354       4096 83
12 00  15  10   75  15   9   79      19449       1024 83
13 00  15   9   79  15   8   83      20472       1024 83
14 00  15   8   83  15   7  115      21495       8192 83
15 00  15   7  115  15   6  179      29686      16384 83
16 00  15   6  179  15   5  243      46069      16384 83
17 00  15   5  243  15   4  355      62452      28672 83
18 00  15   4  355  15   3  359      91123       1024 83
19 00  15   3  359  15   2  363      92146       1024 83
20 00  15   2  363  15   1  395      93169       8192 83
21 00  15   1  395  14  16  963     101360     669696 83
22 00  14  16  963  14  15  967     771055       1024 83
23 00  14  15  967  14  14  971     772078       1024 83
24 00  14  14  971  14  13  523     773101     409600 83
25 00  14  13  523  14  12  627    1182700   30173184 83

And I think there is an signature in the table, because a little thing like changing system-id will brick the phone. but if I write back the table without changes that's no problem.

Excuse me... but why this thread under "dev section"?

I don't want to be annoying (like others i know), but this wouldn't be at General Section?

Originally Posted by espaciosalter20

Excuse me... but why this thread under "dev section"?

I don't want to be annoying (like others i know), but this wouldn't be at General Section?

LOL, this is developement of course.

@m11kkaa: I seriously think that u shud not go ahead with this project. This thing is really dangerous and we all want ur device to be alive.

two points:
1) you don't have todo everything which is possible (I read over the word "your", thanx anyway )
2) I have the theory that the partition-table is completely ignored by the bootloader and that he uses his own hardcoded table.

BTW, I should let repair my Defy as long as it's under warranty because the ear-piece is dead since months...