PINE64

i put an android 5.1 dd image,
dd bs=4M if=/home/dkryder/Downloads/pine64/pine64-lollipop-beta-2-lcd-dd-8.img of=/dev/mmcblk0
it boots and runs fine. i would like to recover the unused space and add to the image. using gparted i get an error message about overlapping partitions. fdisk gives me this,
 sudo fdisk -l /dev/mmcblk0
[sudo] password for dkryder: 
omitting empty partition (14)

Disk /dev/mmcblk0: 16.0 GB, 16021192704 bytes
1 heads, 16 sectors/track, 1955712 cylinders, total 31291392 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x8b83061f

        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

Partition table entries are not in disk order

i can see what i think might be the problem but having never been in the situation i'm not sure what to do.  i found this page,
http://gparted.org/h2-fix-msdos-pt.php#o...partitions
i could use some help in what changes i need to make. thanks

i'm giving this a bump. there was a post i read recently that mentions problems with images and this overlapping partitions issue is hitting me when i try tp resize android 5.1 hdmi rooted/android 5.1 lcd rooted. i can't figure out how to get past it. gparted will not handle it. i'm surprised there has not been alot of discussion . i would like to learn how to get an image that is ,for instance, 8GB to resize to a 16GB SD card. as it stands all i'm getting is overlapping partitions.

(09-29-2016, 07:50 PM)dkryder Wrote: [ -> ]i'm giving this a bump. there was a post i read  recently that mentions problems with images and this overlapping partitions issue is hitting me when i try tp resize android 5.1 hdmi rooted/android 5.1 lcd rooted. i can't figure out how to get past it. gparted will not handle it. i'm surprised there has not been alot of discussion . i would like to learn how to get an image that is ,for instance, 8GB to resize to a 16GB SD card. as it stands all i'm getting is overlapping partitions.

Well, you can't do anything about this for the two Android 5.1 images. The only way to expand the partitions for those images to fill up the entire sd card is to use the PhoenixCard tool, other than that, you are totally out of luck.

You might want to try this Android Nougat image made by one of our members, it is progressing smoothly so far and you can also expand the partition using gparted to fill up the entire sd card.

tera854, the phoenix tool is limited to images built for that tool. the latest images do not have phoenix builds. the 7 build is improving with each new image. i have tried that build just to see how it was and when i tried it the camera did not work. i've read that the camera is now working so i probably will give it a try,

I managed to resize the /data partition on the old style Android images a while back, but it's not a straightforward thing to do. I ended up using sfdisk and a desk calculator since normal tools will refuse to work and/or calculate the start of the new partition wrong for some reason. The large partition entry at the beginning of the list has actually sane boundaries and starts where the extended partition containing all the other partitions ends, but most tools dont like the primary partitions sitting inside an extended partition and refuse to work on that....

Quote:

• 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.

(09-23-2016, 12:03 PM)dkryder Wrote: [ -> ]i put an android 5.1 dd image,
dd bs=4M if=/home/dkryder/Downloads/pine64/pine64-lollipop-beta-2-lcd-dd-8.img of=/dev/mmcblk0
it boots and runs fine. i would like to recover the unused space and add to the image. using gparted i get an error message about overlapping partitions. fdisk gives me this,
 sudo fdisk -l /dev/mmcblk0
[sudo] password for dkryder: 
omitting empty partition (14)

Disk /dev/mmcblk0: 16.0 GB, 16021192704 bytes
1 heads, 16 sectors/track, 1955712 cylinders, total 31291392 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x8b83061f

        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

Partition table entries are not in disk order

i can see what i think might be the problem but having never been in the situation i'm not sure what to do.  i found this page,
http://gparted.org/h2-fix-msdos-pt.php#o...partitions
i could use some help in what changes i need to make. thanks

What burn tool did you use to burn the image?

the same result with etcher, win32diskimager, and dd ,across 2 different computers, tells me it is an issue with the image, not the tool that writes it to sd card. it seems the problem is whatever method is being used to create these the images.

it's a broken partitioning of the image. it can be fixed only at the image creation level.

Having same problem with Android 5.1.1 v1.2.6 release.

So it's either have phoenix builds, or wait for the Android 7.0 build to mature.

Great...