Is my BD-RE WH14NS40 bricked?
Posted: Fri Aug 02, 2024 11:10 am
Blanket admission: I was foolish and attempted a firmware upgrade that wasn't warranted.
Build date: 2013
Purchase date: 2015
Initial drive report in MakeMKV:
I was incredibly stupid and ignored the following:
Is it worth trying dosflash to fix this or should I just take my punishment and buy a new drive?
P.S. I'm using this on a Turing Pi 2 with a Turing RK1 SoM, Ubuntu ARM64. (not that it matters, just showing my very niche use case)
Build date: 2013
Purchase date: 2015
Initial drive report in MakeMKV:
I performed a dump before the upgrade:Drive Information
OS device name: /dev/sr0
Current profile: BD-ROM
Manufacturer: HL-DT-ST
Product: BD-RE WH14NS40
Revision: 1.03
Serial number: K9LD1TG5701
Firmware date: 2114-03-26 11:05
Bus encryption flags: 17
Highest AACS version: 14
LibreDrive Information
Status: Enabled
Drive platform: MT1939
Firmware type: Original (unpatched)
Firmware version: 1.03
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Partial
Unrestricted read speed: Yes
Code: Select all
dump_full_HL-DT-ST_BD-RE__WH14NS40_1.03_211403261105_K9LD1TG5701.binDon't be me!1. Make sure your Drive was built after 2016 on label or late 2015 if you want to risk it.
2. Drive Platform MT1959<Most important in makemkv
3. SVC NS50+ LG only on label for NB drives NB50+
4. Just because your drive is the same model number does not mean it will work, if you are unsure ask me i offer remote flashing and check everything before i flash.
5. Dont flash your dive if it does not meet these requirements if you do you will be unable to read all disks and unable to restore without dosflash that does not work on most modern computers
Is it worth trying dosflash to fix this or should I just take my punishment and buy a new drive?
P.S. I'm using this on a Turing Pi 2 with a Turing RK1 SoM, Ubuntu ARM64. (not that it matters, just showing my very niche use case)