[vilord]

I am in the process of updating an HW3.2 evo from J16383I (2017-02?) to 2018-07.
I am working on a bench, with a ZGW2. I've flashed the ZGW2 with an updated FA including the VIN, type and VO for the car the HU_NBT2 came from (I don't have access to anything else from the HU_NBT2's vehicle).

I'm running e-sys 3.27.1, with 4.13.14 PsdZData. Flashing worked fine for the ZGW2.
When I try to run the TAL execution, updating the blFlash, swDeploy, cdDeploy, and ibaDeploy for the HU_NBT2, the evo screen goes black, the progress indicates:

preparevehicleforflash started
preparevehicleforflash finished

and then the time left goes from 35 minutes to 1 minute, and it eventually comes back FinishedWithError, but has nothing else in the log to indicate what happened (or didn't).

I have a DHCP server running, using connection type gateway connection, target F020_18_07_531_V_005_005_000, Connection via VIN.

Anyone have any ideas?

---

The vehicle was built 2016-11-4, I guessed the shipping i-step as F020-16-07-506, since there's no way to read the i-step from the nbt directly