Do you really tell people to follow this 'tutorial'? You picked up a blog post in chinese, simply tried to translate this to english, do NOT try out the instructions and let this become part of the official so called 'documentation'. Really?
- you recommend installing "gcc-4.7-arm-linux-gnueabihf-base g++-4.7-arm-linux-gnueabihf gcc-arm-linux-gnueabihf gcc-arm-linux-gnueabi cpp-arm-linux-gnueabihf". Why? Your BSP contains the necessary GCC versions already!
- then delete 1st partition of the SD card (why? partition table gets overwritten several times later)
- overwrite the whole card with zeros (why? this will also overwrite the partition table modified just before)
- then again overwriting the whole card with an OS image (overwrites the partition table again)
- then wiping out the partition table one more time with dd
- then sunxi_mbr.fex will be written to the card producing a dos disklabel
- then the user should start to add partitions manually by using fdisk and will be advised to use the card's maximum capacity
The whole process is time consuming and redundant and most likely you end up with something that's simply wrong. Since MPi M3 has a fast internal eMMC it's not advisable to expand such an image to the maximum when being written on a PC to a SD card. Better burn the image to eMMC before and modify the partition table on the BPi M3 instead. The eMMC is multiple times faster than the fastest SD card available (due to limitations of the SD card interface) and also as any SATA disk connected to the ultra slow GL830 USB-to-SATA bridge.
Using eMMC to burn an image onto is therefore always the best choice but unfortunately not possible following the tutorial.
This describes the whole mess regarding software/support: The vendor doesn't provide documentation. Users waste their time trying to figure out how things work. Thankfully they provide an installation log somewhere that might safe other users some time even if it's not perfect. And now the unbelievable happens and the vendor that does not provide proper documentation simply does a copy&paste from the user's installation log and uses this now as 'official documentation'.