Buffalo ext drive will not open after Firmware flash

[MartyMcNuts]

PS C:\Program Files (x86)\MakeMKV> .\makemkvcon64.exe f --all-yes -d D: rawflash nocheck,boot="MT1959 Boot BU5 " -i "C:\replace-this-with-correct-firmware-path\DE_LG_WH16NS60_1.02_MK.bin"
Input file not found -- C:\replace-this-with-correct-firmware-path\DE_LG_WH16NS60_1.02_MK.bin
Internal error 0x83000001
PS C:\Program Files (x86)\MakeMKV> .\makemkvcon64.exe f --all-yes -d D: rawflash "main,nowait,nocheck,boot=MT1959 Boot BU5 " -i "C:\replace-this-with-correct-firmware-path\DE_LG_WH16NS60_1.02_MK.bin"
Input file not found -- C:\replace-this-with-correct-firmware-path\DE_LG_WH16NS60_1.02_MK.bin
Internal error 0x83000001

"C:\replace-this-with-correct-firmware-path\DE_LG_WH16NS60_1.02_MK.bin"

this is not an actual path to your firmware file. You should replace it with the actual path to your DE_LG_WH16NS60_1.02_MK firmware file. The easiest way to do this is to right click on the DE_LG_WH16NS60_1.02_MK.bin file and select "Copy as path" then paste that in your command. For example:

"D:\Downloads\Firmware_Files\DE_LG_WH16NS60_1.02_MK.bin"

Just use whatever the actual path is to your DE_LG_WH16NS60_1.02_MK.bin firmware file.

[zittrig]

1. What does the recovery mode different to flash another firmware directly?

RECOVER/rawflash "main,nowait,nocheck,boot=[wrong boot ID]", aka "flash with fake boot ID", is much more powerful. You can do things with it that you can't do with a normal flash, such as crossflash a BP55EB40 without doing a bootloader flash/rawflash full beforehand, and it also allows you to recover a wrongly flashed drive such as this one (nowait,nocheck is also nice to have when the drive tray doesn't respond anymore). It is also, apparently, more dangerous than a normal flash if done wrong.

2. Why is a drive more likely dead in relation how long it runs with the wrong firmware? Installed is installed. Or what other technical aspects need to be considered here?

I believe it's because a slim firmware installed on a desktop drive (or the opposite ! especially the opposite) is dangerous. It interacts with the hardware in a way that a "correct" firmware wouldn't. Some people actually managed to set their slim drives on fire by flashing desktop firmware onto them, according to Mike.

Please give me a bit more time and I will post detailed instructions on the command line version very soon, which for some reason seems to work for some people when the SDFtool Flasher way fails.

Thanks for the explanation!