Keep in mind this tool can't backup your original unit's firmware.
Also I had erased the EEPROM's content with Dosflash 1.7, and had left it erased temporarily and booted back to Windows.
To others, KEEP in mind do NOT do that. I have backup firmware dump stored savely elsewhere. This was here for testing, if "BH14NS40_N1.00-A4_patched.exe" still detects the UHD-unit allowing flashing back an original firmare-dump, the comfort way, from an already made original-firmware dump, made with Dosflash (original Backup dump very important, not to leave out), especially with this normally very risky step to erase the unit EEPROM or flashing other firmwares, without backuping firmware first!!!
---
BH14NS40_N1.00-A4_patched.exe was unable to detect the unit with an erased EEPROM.
Only with Dosflash_1.7 or Dosflash 2.0 for example (which still requires SATA-IDE mode), together with the original unit's firmware-dump-backup, was able to reanimate the drive.
So at might still be wise to still make a original firmware backup dump with Dosflash, and in case of failure have an SATA-IDE-capable computer in stock.
But on the other hand it is also a risk that people FALSELY press "E" (erase), directly next to "R" (read =backuping), so beware to have selected ONLY "R" when pressing return!!
Because they're editing the firmware bin files to make it downgrade enabled, that's why it works. And it does work. I used it to downgrade my NS50 1.01 to 1.00.
Thx for helping. You're certainly right. Did a few own tests and got to the same result, you described.
EEPROM content's with an (UN)friendly firmware:
"BH14NS40_N1.00-A4_patched.exe"
rejects flashing both, an friendly-original-firmware dump.
-
EEPROM content's with an (UN)friendly firmware:
As well prohibits to flash "flash_HL-DT-ST_BD-RE_BH16NS55_1.02.bin" (= NOT-specially adapted Clean-friendly firmware).
---
EEPROM content's with an (UN)friendly firmware:
Flashing an adapted special firmware, eg. "DE_flash_HL-DT-ST_BD-RE_BH16NS55_1.02.bin" for downgrade , gotten from other site linked here, worked successfully.
---
EEPROM content's with an UHD-friendly firmware:
Flashing a NOT-specially adapted original-firmware-dump from friendly to other firnedly-fw (e.g. lower version) or to a higher version (e.g. UHD-(UN)-friendly) anyway (
in such a case) with success
--
Also tested if BH14NS40_N1.00-A4_patched.exe is working properly:
Flashed temporarily into a 1st BH16NS55 with fw 1.02 friendly, an 1.03 firmware-dump (Un)friendly-firmware from a 2nd BH16NS55 unit, using BH14NS40_N1.00-A4_patched.exe: and I want to test if "BH14NS40_N1.00-A4_patched.exe" works properly.
Then made EEPROM-firmware dump of this with this Dosflash 1.7: Then extracted Teddy's three hexranges into a test-file 1 for comparison.
Then flashed back 1.02 firmware from 1.03 (UN)Friendly, but couldn't take 1.02 original firmware dump, taking "DE_flash_HL-DT-ST_BD-RE_BH16NS55_1.02.bin" instead, which "BH14NS40_N1.00-A4_patched.exe" just works successfully, and I want to test if "BH14NS40_N1.00-A4_patched.exe" works properly.
Then made EEPROM-firmware dump of this with this Dosflash 1.7
Then extracted Teddy's three hexranges into a test-file 2 for comparison.
File comparison check between test-file 1 and test-file 2 (the three Teddy's hex-ranges), checksums identical.
+ File comparison between
:
Original-firmware-1.02-dump of 1st BH16NS55 unit with Dosflash 1.7
and
from flashed "back" 1.02 (<= using "BH14NS40_N1.00-A4_patched.exe") with "DE_flash_HL-DT-ST_BD-RE_BH16NS55_1.02.bin", from 1.03 back to 1.02 ,
+EEPROM-dumped with Dosflash 1.7 - checksums identical.
=> BH14NS40_N1.00-A4_patched.exe has done its job properly
Flashing with "BH14NS40_N1.00-A4_patched.exe" confirmed working with UHD-unit connected via USB with an Asmedia ASM1153E SATA<->eSATA + USB 3.0 bridge-adapter), and also via SATA/eSATA (in AHCI mode).