For those with PhoenixCard "Error" during Burn

[Andrew2]

Thanks on the tips. I also use Diskpart to clean the SD partition. Just need to be extra careful not to clean your harddisk. My advise after launch diskpart, first action is immediately select to your SD card disk number to avoid any accidental mistake.
.. TL

You are right, I added another point in the steps to check the selected disk.

Sorry, but you're collecting here wrong/misleading 'information' (you should keep in mind that while Pine64 might be new the whole 'Android on Allwinner hardware' story is a bit older and everything you might wonder about is known since years).

When Phoenix Card is used in startup mode then the first step is cleaning out the first sectors of the card and writing an appropriate MBR + partition table to it that matches the card's size. Therefore using any tool like Dispart or SD Formatter is not only useless but dangerous instead (since you might wipe out your harddisk instead). It will later always look like this on the card (the first partition's size adjusted to use all available disk space):

Code:

Device     Boot   Start      End  Sectors  Size Id Type
/dev/sda1       5251072 15521790 10270719  4.9G  b W95 FAT32
/dev/sda2  *      73728   139263    65536   32M  6 FAT16
/dev/sda3             1  5251072  5251072  2.5G 85 Linux extended
/dev/sda5        139264   172031    32768   16M 83 Linux
/dev/sda6        172032   204799    32768   16M 83 Linux
/dev/sda7        204800  3350527  3145728  1.5G 83 Linux
/dev/sda8       3350528  3383295    32768   16M 83 Linux
/dev/sda9       3383296  3448831    65536   32M 83 Linux
/dev/sda10      3448832  5021695  1572864  768M 83 Linux
/dev/sda11      5021696  5054463    32768   16M 83 Linux
/dev/sda12      5054464  5087231    32768   16M 83 Linux
/dev/sda13      5087232  5251071   163840   80M 83 Linux

Then: Phoenix Card has some built-in checks relying on checksumming to verify whether some parts have been written correctly (does not apply to the largest part unfortunately). In case Phoenix Card throws errors then this is a sign of data corruption maybe caused by a bad (faulty or counterfeit) SD card or an SD card reader starting to corrupt data (well known problem with some USB readers that start to overheat and corrupt data after a certain amount of constant writing --> use USB2.0 when first connected to USB3.0, check the whole setup with one of the two tools below).

So instead of trying to workaround these issues ejecting/reinserting the card (which might work if speed negotiation between host and card reader might be adjusted -- check Device Manager) the only reasonable strategy is to stop at the very first error and check card reader with inserted SD card using H2testw or f3. Anything else is simply fooling yourself and most probably creating an Android image containing bit flips that lead to all sorts of random problems later.