SDFtool Flasher 1.3.6 crashes + "No drive tool logic found in SDF.bin" on WP50NB40 (FR07 / 0.FR07J, MT1959)

[dtysoo]

Hi,

I'm trying to flash a brand new LG WP50NB40 slim drive and I'm blocked at the
very first step on both the GUI and the CLI. I'd appreciate any guidance on
whether this firmware revision is supported at all.

=== Drive Information (from MakeMKV 1.18.4) ===
OS device name: G:
Manufacturer: HL-DT-ST
Product: WP50NB40
Revision: FR07
Serial number: 904HS022202
Firmware date: 2118-01-22 15:36
Bus encryption flags: 1F
Highest AACS version: 82

LibreDrive Information:
Status: Possible (with patched firmware)
Drive platform: MT1959
Hardware support: Yes
Firmware support: No
Firmware type: Original (patched version available)
Firmware version: 0.FR07J
DVD all regions: Possible (with patched firmware)
BD raw data read: Possible (with patched firmware)
BD raw metadata read: Possible (with patched firmware)
Unrestricted read speed: Possible (with patched firmware)

So the platform is MT1959 and LibreDrive says "Possible (with patched
firmware)", which suggests the drive should be flashable. But neither the GUI
nor the CLI can talk to the drive's tool layer.

=== 1. SDFtool Flasher 1.3.6 (GUI) ===
Running as administrator makes no difference. The application throws an
unhandled exception the moment the drive is selected in the drive list:

************** Exception Text **************
System.FormatException: Input string was not in a correct format.
at System.Number.ThrowOverflowOrFormatException(ParsingStatus status, TypeCode type)
at SDFtool_Flasher_Updated.Form1.comboBox_DriveList_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
at System.Windows.Forms.ComboBox.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, WM msg, IntPtr wparam, IntPtr lparam)

Loaded assemblies include System.Private.CoreLib 6.0.0.0 and
SDFtool Flasher 1.3.6.0 (i.e. the .NET 6 self-contained build).

My guess is that the drive list handler parses the firmware revision ("FR07")
or the firmware version string ("0.FR07J") with Int32.Parse, which fails because
this revision is not numeric.

=== 2. sdftool / makemkvcon (CLI) ===

> makemkvcon64.exe f -l

Found 1 drives(s)
00: \Device\CdRom0, \Device\CdRom0, G:
HL-DT-ST_WP50NB40_FR07_211801221536_904HS022202

Note there is no platform identifier in the drive ID line.

> makemkvcon64.exe f -d G: help

No drive tool logic found in SDF.bin
Internal error 0x8d000000

The same error occurs for every command, including read-only ones:

> makemkvcon64.exe f -d G: --all-yes dump -o C:\temp\fw_backup

No drive tool logic found in SDF.bin
Internal error 0x8d000000

I also tried the device path instead of the drive letter
(makemkvcon64.exe f -d "\Device\CdRom0" help) with the same result.

=== Environment ===
- Windows 10 Pro 22H2, build 19045, x64
- MakeMKV 1.18.4 win(x64-release)
- LibDriveIo/SdfTool version: 2.6
- SDFtool Flasher 1.3.6 (also tried 1.3.5, same behaviour)
- Only one optical drive present (G:), no virtual drives installed
- Drive connected with both USB plugs (Y-cable) directly to rear ports, no hub
- MakeMKV itself detects the drive without problem (DRV:0 flags 0)
- VC++ 2015-2022 runtime present, plenty of disk space

=== Questions ===
1. Is FR07 / firmware version 0.FR07J supported by the current SDF.bin, or is
this a new locked revision that the tooling does not recognise yet?
2. If it is not supported yet, can support be added to SDF? I'd be happy to run
any diagnostic commands you need and send the output.
3. Is there any way to make sdftool talk to this drive (a specific SDF version,
a different switch, an older/newer LibDriveIo), given that LibreDrive reports
MT1959 with "Firmware support: No"?
4. If this revision cannot be flashed, is the recommendation simply to return
the drive and source a unit known to be flashable (BU40N 1.03-MK or
BP60NB10 1.02-MK)?

I have not attempted to write any firmware, since every SDF command is rejected
and I don't want to leave the drive in a half-flashed state.

Thanks in advance for any help.

[dtysoo]

SVC code on the label is NB50, so this is one of the documented flashable batches (BP50NB40/WP50NB40). The unit is brand new and shipped with FR07 / 0.FR07J from the factory. This looks like a supported batch with a newer-than-expected factory firmware, not an unsupported drive.

[MartyMcNuts]

Hi,

I'm trying to flash a brand new LG WP50NB40 slim drive and I'm blocked at the
very first step on both the GUI and the CLI. I'd appreciate any guidance on
whether this firmware revision is supported at all.

=== Drive Information (from MakeMKV 1.18.4) ===
OS device name: G:
Manufacturer: HL-DT-ST
Product: WP50NB40
Revision: FR07
Serial number: 904HS022202
Firmware date: 2118-01-22 15:36
Bus encryption flags: 1F
Highest AACS version: 82

LibreDrive Information:
Status: Possible (with patched firmware)
Drive platform: MT1959
Hardware support: Yes
Firmware support: No
Firmware type: Original (patched version available)
Firmware version: 0.FR07J
DVD all regions: Possible (with patched firmware)
BD raw data read: Possible (with patched firmware)
BD raw metadata read: Possible (with patched firmware)
Unrestricted read speed: Possible (with patched firmware)

So the platform is MT1959 and LibreDrive says "Possible (with patched
firmware)", which suggests the drive should be flashable. But neither the GUI
nor the CLI can talk to the drive's tool layer.

=== 1. SDFtool Flasher 1.3.6 (GUI) ===
Running as administrator makes no difference. The application throws an
unhandled exception the moment the drive is selected in the drive list:

************** Exception Text **************
System.FormatException: Input string was not in a correct format.
at System.Number.ThrowOverflowOrFormatException(ParsingStatus status, TypeCode type)
at SDFtool_Flasher_Updated.Form1.comboBox_DriveList_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
at System.Windows.Forms.ComboBox.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, WM msg, IntPtr wparam, IntPtr lparam)

Loaded assemblies include System.Private.CoreLib 6.0.0.0 and
SDFtool Flasher 1.3.6.0 (i.e. the .NET 6 self-contained build).

My guess is that the drive list handler parses the firmware revision ("FR07")
or the firmware version string ("0.FR07J") with Int32.Parse, which fails because
this revision is not numeric.

=== 2. sdftool / makemkvcon (CLI) ===

> makemkvcon64.exe f -l

Found 1 drives(s)
00: \Device\CdRom0, \Device\CdRom0, G:
HL-DT-ST_WP50NB40_FR07_211801221536_904HS022202

Note there is no platform identifier in the drive ID line.

> makemkvcon64.exe f -d G: help

No drive tool logic found in SDF.bin
Internal error 0x8d000000

The same error occurs for every command, including read-only ones:

> makemkvcon64.exe f -d G: --all-yes dump -o C:\temp\fw_backup

No drive tool logic found in SDF.bin
Internal error 0x8d000000

I also tried the device path instead of the drive letter
(makemkvcon64.exe f -d "\Device\CdRom0" help) with the same result.

=== Environment ===
- Windows 10 Pro 22H2, build 19045, x64
- MakeMKV 1.18.4 win(x64-release)
- LibDriveIo/SdfTool version: 2.6
- SDFtool Flasher 1.3.6 (also tried 1.3.5, same behaviour)
- Only one optical drive present (G:), no virtual drives installed
- Drive connected with both USB plugs (Y-cable) directly to rear ports, no hub
- MakeMKV itself detects the drive without problem (DRV:0 flags 0)
- VC++ 2015-2022 runtime present, plenty of disk space

=== Questions ===
1. Is FR07 / firmware version 0.FR07J supported by the current SDF.bin, or is
this a new locked revision that the tooling does not recognise yet?
2. If it is not supported yet, can support be added to SDF? I'd be happy to run
any diagnostic commands you need and send the output.
3. Is there any way to make sdftool talk to this drive (a specific SDF version,
a different switch, an older/newer LibDriveIo), given that LibreDrive reports
MT1959 with "Firmware support: No"?
4. If this revision cannot be flashed, is the recommendation simply to return
the drive and source a unit known to be flashable (BU40N 1.03-MK or
BP60NB10 1.02-MK)?

I have not attempted to write any firmware, since every SDF command is rejected
and I don't want to leave the drive in a half-flashed state.

Thanks in advance for any help.

You have a fake drive. Any actual new one of these would be SVC NB52, not NB50 and these never, ever come with FR07 firmware. That firmware version is included on some old OEM BU40N's. As you can see, the firmware date is from 2018.

Return it if you can!!

[dtysoo]

Hi,

I'm trying to flash a brand new LG WP50NB40 slim drive and I'm blocked at the
very first step on both the GUI and the CLI. I'd appreciate any guidance on
whether this firmware revision is supported at all.

=== Drive Information (from MakeMKV 1.18.4) ===
OS device name: G:
Manufacturer: HL-DT-ST
Product: WP50NB40
Revision: FR07
Serial number: 904HS022202
Firmware date: 2118-01-22 15:36
Bus encryption flags: 1F
Highest AACS version: 82

LibreDrive Information:
Status: Possible (with patched firmware)
Drive platform: MT1959
Hardware support: Yes
Firmware support: No
Firmware type: Original (patched version available)
Firmware version: 0.FR07J
DVD all regions: Possible (with patched firmware)
BD raw data read: Possible (with patched firmware)
BD raw metadata read: Possible (with patched firmware)
Unrestricted read speed: Possible (with patched firmware)

So the platform is MT1959 and LibreDrive says "Possible (with patched
firmware)", which suggests the drive should be flashable. But neither the GUI
nor the CLI can talk to the drive's tool layer.

=== 1. SDFtool Flasher 1.3.6 (GUI) ===
Running as administrator makes no difference. The application throws an
unhandled exception the moment the drive is selected in the drive list:

************** Exception Text **************
System.FormatException: Input string was not in a correct format.
at System.Number.ThrowOverflowOrFormatException(ParsingStatus status, TypeCode type)
at SDFtool_Flasher_Updated.Form1.comboBox_DriveList_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
at System.Windows.Forms.ComboBox.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, WM msg, IntPtr wparam, IntPtr lparam)

Loaded assemblies include System.Private.CoreLib 6.0.0.0 and
SDFtool Flasher 1.3.6.0 (i.e. the .NET 6 self-contained build).

My guess is that the drive list handler parses the firmware revision ("FR07")
or the firmware version string ("0.FR07J") with Int32.Parse, which fails because
this revision is not numeric.

=== 2. sdftool / makemkvcon (CLI) ===

> makemkvcon64.exe f -l

Found 1 drives(s)
00: \Device\CdRom0, \Device\CdRom0, G:
HL-DT-ST_WP50NB40_FR07_211801221536_904HS022202

Note there is no platform identifier in the drive ID line.

> makemkvcon64.exe f -d G: help

No drive tool logic found in SDF.bin
Internal error 0x8d000000

The same error occurs for every command, including read-only ones:

> makemkvcon64.exe f -d G: --all-yes dump -o C:\temp\fw_backup

No drive tool logic found in SDF.bin
Internal error 0x8d000000

I also tried the device path instead of the drive letter
(makemkvcon64.exe f -d "\Device\CdRom0" help) with the same result.

=== Environment ===
- Windows 10 Pro 22H2, build 19045, x64
- MakeMKV 1.18.4 win(x64-release)
- LibDriveIo/SdfTool version: 2.6
- SDFtool Flasher 1.3.6 (also tried 1.3.5, same behaviour)
- Only one optical drive present (G:), no virtual drives installed
- Drive connected with both USB plugs (Y-cable) directly to rear ports, no hub
- MakeMKV itself detects the drive without problem (DRV:0 flags 0)
- VC++ 2015-2022 runtime present, plenty of disk space

=== Questions ===
1. Is FR07 / firmware version 0.FR07J supported by the current SDF.bin, or is
this a new locked revision that the tooling does not recognise yet?
2. If it is not supported yet, can support be added to SDF? I'd be happy to run
any diagnostic commands you need and send the output.
3. Is there any way to make sdftool talk to this drive (a specific SDF version,
a different switch, an older/newer LibDriveIo), given that LibreDrive reports
MT1959 with "Firmware support: No"?
4. If this revision cannot be flashed, is the recommendation simply to return
the drive and source a unit known to be flashable (BU40N 1.03-MK or
BP60NB10 1.02-MK)?

I have not attempted to write any firmware, since every SDF command is rejected
and I don't want to leave the drive in a half-flashed state.

Thanks in advance for any help.

You have a fake drive. Any actual new one of these would be SVC NB52, not NB50 and these never, ever come with FR07 firmware. That firmware version is included on some old OEM BU40N's. As you can see, the firmware date is from 2018.

Return it if you can!!

Marty, thank you so much for the quick and definitive answer — this explains
everything, including why every tool on my side refused to cooperate.

I bought it second-hand on Xianyu (a Chinese classifieds marketplace), so a
return is probably not realistic, but I'll still message the seller — at the
very least he deserves to know he's reselling fakes (or knows exactly what
he's selling).

Lesson learned: I'll check the SVC code and firmware date *before* paying next
time, and I'll stick to units that are verifiably flashable.

One last question, if you don't mind: since the board inside is apparently an
old OEM BU40N, is there any realistic path to flash it (FR07 -> 1.03-MK), or
should I just leave it alone and use it for regular BD/DVD reading? I have no
intention of forcing anything with the wrong firmware — I'd rather keep the
drive healthy than end up with a brick.

Either way, thanks again for your time and for maintaining these tools. This
thread will hopefully help other buyers spot the same fake.

[MartyMcNuts]

Hi,

I'm trying to flash a brand new LG WP50NB40 slim drive and I'm blocked at the
very first step on both the GUI and the CLI. I'd appreciate any guidance on
whether this firmware revision is supported at all.

=== Drive Information (from MakeMKV 1.18.4) ===
OS device name: G:
Manufacturer: HL-DT-ST
Product: WP50NB40
Revision: FR07
Serial number: 904HS022202
Firmware date: 2118-01-22 15:36
Bus encryption flags: 1F
Highest AACS version: 82

LibreDrive Information:
Status: Possible (with patched firmware)
Drive platform: MT1959
Hardware support: Yes
Firmware support: No
Firmware type: Original (patched version available)
Firmware version: 0.FR07J
DVD all regions: Possible (with patched firmware)
BD raw data read: Possible (with patched firmware)
BD raw metadata read: Possible (with patched firmware)
Unrestricted read speed: Possible (with patched firmware)

So the platform is MT1959 and LibreDrive says "Possible (with patched
firmware)", which suggests the drive should be flashable. But neither the GUI
nor the CLI can talk to the drive's tool layer.

=== 1. SDFtool Flasher 1.3.6 (GUI) ===
Running as administrator makes no difference. The application throws an
unhandled exception the moment the drive is selected in the drive list:

************** Exception Text **************
System.FormatException: Input string was not in a correct format.
at System.Number.ThrowOverflowOrFormatException(ParsingStatus status, TypeCode type)
at SDFtool_Flasher_Updated.Form1.comboBox_DriveList_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
at System.Windows.Forms.ComboBox.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, WM msg, IntPtr wparam, IntPtr lparam)

Loaded assemblies include System.Private.CoreLib 6.0.0.0 and
SDFtool Flasher 1.3.6.0 (i.e. the .NET 6 self-contained build).

My guess is that the drive list handler parses the firmware revision ("FR07")
or the firmware version string ("0.FR07J") with Int32.Parse, which fails because
this revision is not numeric.

=== 2. sdftool / makemkvcon (CLI) ===

> makemkvcon64.exe f -l

Found 1 drives(s)
00: \Device\CdRom0, \Device\CdRom0, G:
HL-DT-ST_WP50NB40_FR07_211801221536_904HS022202

Note there is no platform identifier in the drive ID line.

> makemkvcon64.exe f -d G: help

No drive tool logic found in SDF.bin
Internal error 0x8d000000

The same error occurs for every command, including read-only ones:

> makemkvcon64.exe f -d G: --all-yes dump -o C:\temp\fw_backup

No drive tool logic found in SDF.bin
Internal error 0x8d000000

I also tried the device path instead of the drive letter
(makemkvcon64.exe f -d "\Device\CdRom0" help) with the same result.

=== Environment ===
- Windows 10 Pro 22H2, build 19045, x64
- MakeMKV 1.18.4 win(x64-release)
- LibDriveIo/SdfTool version: 2.6
- SDFtool Flasher 1.3.6 (also tried 1.3.5, same behaviour)
- Only one optical drive present (G:), no virtual drives installed
- Drive connected with both USB plugs (Y-cable) directly to rear ports, no hub
- MakeMKV itself detects the drive without problem (DRV:0 flags 0)
- VC++ 2015-2022 runtime present, plenty of disk space

=== Questions ===
1. Is FR07 / firmware version 0.FR07J supported by the current SDF.bin, or is
this a new locked revision that the tooling does not recognise yet?
2. If it is not supported yet, can support be added to SDF? I'd be happy to run
any diagnostic commands you need and send the output.
3. Is there any way to make sdftool talk to this drive (a specific SDF version,
a different switch, an older/newer LibDriveIo), given that LibreDrive reports
MT1959 with "Firmware support: No"?
4. If this revision cannot be flashed, is the recommendation simply to return
the drive and source a unit known to be flashable (BU40N 1.03-MK or
BP60NB10 1.02-MK)?

I have not attempted to write any firmware, since every SDF command is rejected
and I don't want to leave the drive in a half-flashed state.

Thanks in advance for any help.

You have a fake drive. Any actual new one of these would be SVC NB52, not NB50 and these never, ever come with FR07 firmware. That firmware version is included on some old OEM BU40N's. As you can see, the firmware date is from 2018.

Return it if you can!!

Marty, thank you so much for the quick and definitive answer — this explains
everything, including why every tool on my side refused to cooperate.

I bought it second-hand on Xianyu (a Chinese classifieds marketplace), so a
return is probably not realistic, but I'll still message the seller — at the
very least he deserves to know he's reselling fakes (or knows exactly what
he's selling).

Lesson learned: I'll check the SVC code and firmware date *before* paying next
time, and I'll stick to units that are verifiably flashable.

One last question, if you don't mind: since the board inside is apparently an
old OEM BU40N, is there any realistic path to flash it (FR07 -> 1.03-MK), or
should I just leave it alone and use it for regular BD/DVD reading? I have no
intention of forcing anything with the wrong firmware — I'd rather keep the
drive healthy than end up with a brick.

Either way, thanks again for your time and for maintaining these tools. This
thread will hopefully help other buyers spot the same fake.

I suggest perhaps opening up the enclosure to confirm exactly what model drive it is. Depending on the actual drive model, it might possibly still be flashable outside of the enclosure.

[Billycar11]

Hi,

I'm trying to flash a brand new LG WP50NB40 slim drive and I'm blocked at the
very first step on both the GUI and the CLI. I'd appreciate any guidance on
whether this firmware revision is supported at all.

=== Drive Information (from MakeMKV 1.18.4) ===
OS device name: G:
Manufacturer: HL-DT-ST
Product: WP50NB40
Revision: FR07
Serial number: 904HS022202
Firmware date: 2118-01-22 15:36
Bus encryption flags: 1F
Highest AACS version: 82

LibreDrive Information:
Status: Possible (with patched firmware)
Drive platform: MT1959
Hardware support: Yes
Firmware support: No
Firmware type: Original (patched version available)
Firmware version: 0.FR07J
DVD all regions: Possible (with patched firmware)
BD raw data read: Possible (with patched firmware)
BD raw metadata read: Possible (with patched firmware)
Unrestricted read speed: Possible (with patched firmware)

I have not attempted to write any firmware, since every SDF command is rejected
and I don't want to leave the drive in a half-flashed state.

Thanks in advance for any help.

You have a fake drive. Any actual new one of these would be SVC NB52, not NB50 and these never, ever come with FR07 firmware. That firmware version is included on some old OEM BU40N's. As you can see, the firmware date is from 2018.

Return it if you can!!

these guys are so annoying the sellers are shooting them selves in the foot they have likely have an actual UHD drive this time as marty said BU40N but instead selling a bare drive or non spoof case they put it in a case that makes it impossible to flash and use libredrive then half of them get thrown out at the return centers they are wasting these drives and everyone's time