[Teclast X98 Air 3G] Moximos:
Understood thanks, I've done that now. It still didn't work, but after some poking around I found that after going into fastboot the VID/PID change in Device Manager. I changed the Android device PID variable to 0FFF.

It partitioned successfully but formatting failed.

07/12/15 09:12:00.446 INFO : Port 0/0/2 #0: fastboot -s BaytrailE34B52A6 -S 100M oem partition /tmp/partition.tbl
07/12/15 09:12:00.849 INFO : Port 0/0/2 #0: fastboot -s BaytrailE34B52A6 -S 100M format factory
07/12/15 09:12:00.971 WARNING: Port 0/0/2 #0: Failed to execute "fastboot -s BaytrailE34B52A6 -S 100M format factory":
Creating filesystem with parameters:
Size: 16777216
Block size: 4096
Blocks per group: 32768
Inodes per group: 1024
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 4096
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/1024 inodes and 1102/4096 blocks
formatting 'factory' partition...
error: wipe_block_device: wipe not supported on non-linux platforms
sending 'factory' (0 KB)...
FAILED ()
finished. total time: 0.105s
07/12/15 09:12:01.222 WARNING: Port 0/0/2 #0: Retry to execute fastboot -s BaytrailE34B52A6 -S 100M format factory
07/12/15 09:12:01.344 WARNING: Port 0/0/2 #0: Failed to execute "fastboot -s BaytrailE34B52A6 -S 100M format factory":
Creating filesystem with parameters:
Size: 16777216
Block size: 4096
Blocks per group: 32768
Inodes per group: 1024
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 4096
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/1024 inodes and 1102/4096 blocks
formatting 'factory' partition...
error: wipe_block_device: wipe not supported on non-linux platforms
sending 'factory' (0 KB)...
FAILED ()
finished. total time: 0.105s
07/12/15 09:12:01.595 INFO : do_flash_finished END OF FLASH
07/12/15 09:12:01.595 ERROR : Port 0/0/2 #0: Flash failure

I thought it might have been permissions, but I did run it with Administrator.

I opened a CMD prompt and executed the fastboot format factory manually which worked without a problem. So I continued executing the remaining fastboot commands in the order they appear in the xml without any errors.

fastboot -s BaytrailE34B52A6 -S 100M format factory
fastboot -s BaytrailE34B52A6 format system
fastboot -s BaytrailE34B52A6 format cache
fastboot -s BaytrailE34B52A6 format config
fastboot -s BaytrailE34B52A6 format logs
fastboot -s BaytrailE34B52A6 format data
fastboot -s BaytrailE34B52A6 oem stop_partitioning
fastboot -s BaytrailE34B52A6 oem wipe ESP
fastboot -s BaytrailE34B52A6 oem wipe reserved
fastboot -s BaytrailE34B52A6 flash ESP esp.img
fastboot -s BaytrailE34B52A6 flash fastboot droidboot.img
fastboot -s BaytrailE34B52A6 flash boot boot.img
fastboot -s BaytrailE34B52A6 flash recovery recovery.img
fastboot -s BaytrailE34B52A6 flash system system.img
fastboot -s BaytrailE34B52A6 continue

Hopefully I didn't neglect some implied parameters. Would be nice to see the full output of a successful run from the mfg tool in case I need to go back over it.

It's booted Android successfully now.

Android 5.0, Kernel 3.10.2, Build Number V1.02_20150515.

Edit: Warning for others, this procedure prevented Windows from booting. I probably should have used the nopartition xml but I was trying more risky things until this worked.