How do I deal with "Writing device finished - INCOMPLETE" unbricking Mate 9?

[freakingrobot]

I'm trying to unbrick my Huawei Mate 9 (MHA-AL00) with DC-Phoenix, but failing with an error. It says: "Error writing Bootloader" and "Writing device finished - INCOMPLETE". I've tried both normal USB COM 1.0 method and USB COM 1.0 with test points method.

I originally bricked my Mate 9 by flashing the MHA-L29C636 firmware using the dload method, from Android 8.X Oreo to the 7.X in the dload rar. Since then, my phone won't boot. The screen stays off, without even the backlighting turning on. Trying to enter fastboot and recovery do nothing; when I hold the button combo and power on, nothing happens. When I plug my phone into the computer, it's recognized as "HUAWEI USB COM 1.0" (without needing to short the test points). The screen stays off, and my Mate 9 does not boot.

I have followed the unbricking guide https://www.dc-unlocker.com/flash-br...-huawei-1-mode, but came to the following error.

The file was loaded successfully
Looking for a device in force upgrade mode
Device detected:
5/14/2019 6:41:44 PM Starting to write device in FASTBOOT mode...
File to update: MHA-AL00A_HLMHAAL00AM00A063_Factory_firmware_China_Nonspecific_Android_7.0_EMUI_5.0.dgtks
Device detected:

Writing bootloader...
Writing MHA-AL00A_HLMHAAL00AM00A063_Factory_firmware_China_Nonspecific_Android_7.0_EMUI_5.0_3.dtwork...

Error writing Bootloader
5/14/2019 6:41:59 PM Writing device finished - INCOMPLETE

When the "Writing bootloader" message is displayed, I hear Windows' USB disconnect sound effect, even though I haven't unplugged anything. But even though I hear the USB disconnect sound effect, my phone continues to show in the Windows Device Manager app.

I've tried about five different firmware dgtks so far, and every one of them results in the above error. I tried booting with the testpoints method too, but it makes no difference at all. How can I get past this error? I've attached a log file and screenshot below. Please help!

[Valdemaras]

You need to go to upade oeminfo tab, select loader matching your phone processor (if there are multiple, you can try them all until one fits your device as they are harmless) then select oeminfo and flash, after that you should be able to apply full stock rom.

[freakingrobot]

Thank you for the fast reply, I've been able to auto-reboot into fastboot after flashing bootloader and oem. But now I have a new error:

(snip)

ERASE partition nvme : FAIL failed to erase partition
Trying to unlock device...
ERASE partition nvme : FAIL failed to erase partition

ERASE partition cust : FAIL failed to erase partition

ERASE partition misc : FAIL failed to erase partition

ERASE partition userdata : FAIL failed to erase partition
xloaderpartition is not written because is in the APP file

(snip)

Extracting partition XLOADER...
Writing XLOADER partition
XLOADER partition UPDATE :FAIL image xloader1 verification error
Trying to unlock device...
Writing XLOADER partition
XLOADER partition UPDATE :FAIL image xloader1 verification error

(the errors continue but end with the following)

Software written
5/15/2019 4:04:14 AM Writing device finished - INCOMPLETE

Waiting for fastboot device...
No devices detected in fastboot mode

Cannot update device in upgrade mode

After that, my phone still does not boot without first flashing bootloader and OEM. I searched the forum and saw that you replied elsewhere to flash the board by itself in advanced mode, then to flash the firmware and customization afterwards, but this also gives me the same error, and my phone still does not boot.

I've attached my setup and logs below. I don't see anyone else getting the same errors as me.

Is my phone dead for good?

[Valdemaras]

If you have done it with right files then yes, it is dead.

[freakingrobot]

I've tried just about every possible combination by now. I guess there's no helping it then...

[gsmgeo]

You have new xloader .. - its GPu- Turbo

[Valdemaras]

Refund now completed.

[freakingrobot]

Confirmed refund, thank you.