MFG Tool Stuck when formatting Android partition

[disheng]

Hello,

I am using android_m6.0.1_2.1.0_ga_tool to flash Android software with mfg firmware made from Yocto imx-4.1.15-1.0.0_ga, emmc 8 GB, the first time we flash to our board, the mfg tool shows success, but when the second time we try to flash, it gets stuck during partitioning:

/dev/mmcblk3p1 16384 49151 32768 16M 83 Linux
/dev/mmcblk3p2 51200 83967 32768 16M 83 Linux
/dev/mmcblk3p3 83968 2885631 2801664 1.3G 5 Extended
/dev/mmcblk3p4 2885632 14876671 11991040 5.7G 83 Linux
/dev/mmcblk3p5 86016 1724415 1638400 800M 83 Linux
/dev/mmcblk3p6 1726464 2775039 1048576 512M 83 Linux
/dev/mmcblk3p7 2777088 2793471 16384 8M 83 Linux
/dev/mmcblk3p8 2795520 2807807 12288 6M 83 Linux
/dev/mmcblk3p9 2809856 2813951 4096 2M 83 Linux

Partition table entries are not in disk order.

The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
formating android data partition
mke2fs 1.43-WIP (18-May-2015)
/dev/mmcblk3p4 contains a ext4 file system labelled 'data'
created on Thu Jan 1 00:00:31 1970
Proceed anyway? (y,n)

We tried to send 'y' but nothing happens.

Attached is the full log, do you have some ideas?

Thank you,

Di

[disheng · Accepted solution]

Ok, I found the solution. Add these two lines to the ucl2.xml before partitioning will do the trick

<CMD state="Updater" type="push" body="$ wipefs -a /dev/mmcblk%mmc%p[1-9]*"> delete filesystem information from each partitions.</CMD>
<CMD state="Updater" type="push" body="$ wipefs -a /dev/mmcblk%mmc%"> delete partition table..</CMD>

[disheng]

By the way, I am trying to flash with mfg firmware generated by  Yocto imx-4.1.15-1.0.0_ga, but the android files such as system.img is from android_L5.0.0_1.0.0-ga, would this work?

[jimmychan]

Basically, the firmware is a small linux system. The image files of the firmware are build from the Yocto Linux BSP for the EVK board. So, if your own board design (mainly the DDR parts) is almost the same as the EVK board, the firmware should also bootable for your board.

[disheng]

Hi Jimmy,

Thanks for the reply, the reason I try to use a different version of yocto than my android is that my board refers to the scm and the yocto project for my android no longer exists, that's why i ported to a different yocto, anyway, what you said definitely correct, unfortunately we changed ddr and had to rebuild the mfg tool firmwares. This way it should work, mfg tool firmware is just to help to write to emmc, it does not care what android version of the image it writes.

There are must be some emmc settings that blocks this emmc partitioning process, because if I erase the emmc entirely, then I will be able to flash correctly.