[Moto G4 Plus Questions & Answers] Amberdawn:
The problems I am having are the same as previously. I can confirm that I am using the blankflash still as provided in the link you quoted.

I'm going to post again what I'm obtaining after executing the blankflash

Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM3
[ 0.001] Detecting device
[ 0.002] ...cpu.id = 2418 (0x972)
[ 0.003] ...cpu.sn = 30778144 (0x1d5a320)
[ 0.003] Opening singleimage
[ 0.003] Loading package
[ 0.005] ...filename = singleimage.pkg.xml
[ 0.006] Loading programmer
[ 0.007] ...filename = programmer.mbn
[ 0.007] Sending programmer
[ 0.230] Handling things over to programmer
[ 0.231] Identifying CPU version
[ 0.237] Waiting for firehose to get ready
[ 63.482] Waiting for firehose to get ready
[127.045] ...MSM8952 unknown
[127.046] Determining target secure state
[127.052] Waiting for firehose to get ready
[188.612] ...secure = no
[188.624] Flashing GPT...
[188.625] Flashing partition:0 with gpt_main0.bin
[188.625] Initializing storage
[188.629] Waiting for firehose to get ready
[252.178] Configuring device...
[252.184] Waiting for firehose to get ready
[312.752] Waiting for firehose to get ready
[373.317] Waiting for firehose to get ready
[436.386] Waiting for firehose to get ready
[497.451] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error
[497.452] Check qboot_log.txt for more details
[497.455] Total time: 497.457s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error

Log from qboot_log.txt file:

[ -0.000] Opening device: \\.\COM3
[ 0.001] Detecting device
[ 0.002] ...cpu.id = 2418 (0x972)
[ 0.003] ...cpu.sn = 30778144 (0x1d5a320)
[ 0.003] Opening singleimage
[ 0.003] Loading package
[ 0.005] ...filename = singleimage.pkg.xml
[ 0.006] Loading programmer
[ 0.007] ...filename = programmer.mbn
[ 0.007] Sending programmer
[ 0.230] Handling things over to programmer
[ 0.231] Identifying CPU version
[ 0.237] Waiting for firehose to get ready
[ 63.482] Waiting for firehose to get ready
[127.045] ...MSM8952 unknown
[127.046] Determining target secure state
[127.052] Waiting for firehose to get ready
[188.612] ...secure = no
[188.624] Flashing GPT...
[188.625] Flashing partition:0 with gpt_main0.bin
[188.625] Initializing storage
[188.629] Waiting for firehose to get ready
[252.178] Configuring device...
[252.184] Waiting for firehose to get ready
[312.752] Waiting for firehose to get ready
[373.317] Waiting for firehose to get ready
[436.386] Waiting for firehose to get ready
[497.451] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error
[497.452] Check qboot_log.txt for more details
[497.455] Total time: 497.457s
[497.456]
[497.456] qboot version 3.40
[497.456]
[497.456] DEVICE {
[497.456] name = "\\.\COM3",
[497.456] flags = "0x64",
[497.456] addr = "0x61FE5C",
[497.456] sahara.current_mode = "0",
[497.456] api.buffer = "0x2F01020",
[497.456] cpu.serial = "30778144",
[497.456] cpu.id = "2418",
[497.456] cpu.sv_sbl = "0",
[497.456] cpu.name = "MSM8952",
[497.456] storage.type = "eMMC",
[497.456] sahara.programmer = "programmer.mbn",
[497.457] module.firehose = "0x3088C78",
[497.457] cpu.ver = "0",
[497.457] cpu.vername = "unknown",
[497.457] api.bnr = "0x2746888",
[497.457] }
[497.457]
[497.457]
[497.457] Backup & Restore {
[497.457] num_entries = 0,
[497.457] restoring = "false",
[497.457] backup_error = "not started",
[497.457] restore_error = "not started",
[497.457] }
[497.457]

I can also confirm that I have tried following the steps from that post. It's true that sometimes I need to follow these tips in order for blankflash to start executing.

However, the blankflash process doesn't work properly.

I think that the device is still under warranty. I have realised that more and more people are reporting the same problem.