overlapping partitions issue with resize of 8GB image put on 16GB sd card

[z4v4l]

• Device Boot      Start         End      Blocks   Id  System
  
• /dev/mmcblk0p1         5251072    15194110     4971519+   b  W95 FAT32
  
• /dev/mmcblk0p2   *       73728      139263       32768    6  FAT16
  
• /dev/mmcblk0p3               1     5251072     2625536   85  Linux extended
  
• /dev/mmcblk0p5          139264      172031       16384   83  Linux
  
• /dev/mmcblk0p6          172032      204799       16384   83  Linux
  
• /dev/mmcblk0p7          204800     3350527     1572864   83  Linux
  
• /dev/mmcblk0p8         3350528     3383295       16384   83  Linux
  
• /dev/mmcblk0p9         3383296     3448831       32768   83  Linux
  
• /dev/mmcblk0p10        3448832     5021695      786432   83  Linux
  
• /dev/mmcblk0p11        5021696     5054463       16384   83  Linux
  
• /dev/mmcblk0p12        5054464     5087231       16384   83  Linux
  
• /dev/mmcblk0p13        5087232     5251071       81920   83  Linux
  

With such a crappy layout, it would be hard to do something. It uses "linux extended partition". Funny thing about it, it grabs the range of the other (and active) MBR partition (FAT16). Why? Then this is overlapping partitions by this funny design. Since an active (bootable) FAT partition must have its own entry in MBR. And linux extended partition must have its own MBR entry. But the latter claims its beginning is at LBA 1. This means it overlaps with FAT16 partition. That's crap.
If you just want to extend the last partition (FAT32) to the end of the disk, or create yet another partition in the free space there, then there should not be any overlapping. If it complains about the overlapping I mentioned, then congratulations - linux disk utility cannot deal with the quirks of its own system, since it sees overlapping between FAT16 partition and linux extended partition.