I was able to replicate your problem
I started with a dongle with version 2.00 and started an update procedure to 2.01
I waited until the
first 'Please wait' screen comes up, and then, when the reflashing procedure starts the second phase,
I brutally unplugged the dongle from the cable. I know this is not what you did
, but I did it to simulate a crash during reflashing.
I restarted the procedure, got the 'update firmware' screen, selected 2.01 again, and everything worked well until the phase one ('bootloading' 1, 'please wait' 1) finishes.
Then, the program dies.
I believe I have reached the same point that you are at.
It keeps dying the same way every time I try to 'update firmware' to the new version 2.01. If I select the previous version (2.00), then the procedure starts, and reaches the end properly, that is, I am returned to a working dongle 2.00. After which, I successfully reflashed it to 2.01.
Strangely, if I start a 'downgrade' from 2.01 to 2.00 and try doing the same, I have no problem (ever) while the reverse invariably ends up (if I unplug the dongle - that is if the reflashing crashes)
So:
if you started from 2.00, going to 2.01, and for some reason the bootloader failed, retry the procedure with the same version you started from. That is: reflash the dongle with 2.00 (if you started from 2.00). If, like it should, this reloads your dongle with the old software, you can then try a new procedure to go to 2.01.
If you can tell me what version you started with, and what version you were going to, I can do more testing next week
Regards
Maurizio