SDFtool Flasher

[Billycar11]

But what if you want to copy discs but not with jamless playback introducing fake data in error regions?

then you get a pioneer
but its not normal on a lg makemkv will report it as errors
then do the usual thing power off the drive for a few mins then try again if that dont help clean the disc then replace disc then clean lasers then get a nonexistent pioneer

[meepster]

i have a ASUS usb drive was wonderring what do i need to flash with to make is Usable.
i have the flasher and all the firmwares just wondering what one or ones i need to use the drive is encrypted.

Drive Information
OS device name: G:
Manufacturer: ASUS
Product: BW-16D1X-U
Revision: A105
Serial number:
Firmware date: 2120-12-02 11:14
Bus encryption flags: 1F
Highest AACS version: 70

LibreDrive Information
Status: Possible, not yet enabled
Drive platform: MT1959

No disc inserted

If you still write/burn discs, use BW-16D1HT 3.10-MK. If you only rip discs and don't care about writing/burning discs, use WH16NS60 1.02-MK.

shweet thank you all working

[kaysee]

but its not normal on a lg makemkv will report it as errors

MakeMKV will report hash-check errors. But if MakeMKV receives error messages from the drive, then it can retry reads a number of time, and avoid hash-check errors.

In addition, if someone is trying other copy methods like ddrescue, then error reporting from the drive is required.

[Billycar11]

but its not normal on a lg makemkv will report it as errors

MakeMKV will report hash-check errors. But if MakeMKV receives error messages from the drive, then it can retry reads a number of time, and avoid hash-check errors.

In addition, if someone is trying other copy methods like ddrescue, then error reporting from the drive is required.

i know and agree thats why pioneers are best they dont lie like lg

[kaysee]

Three suggestions for the utility:

1. If only one optical drive is found, then it should be automatically selected as the default. Most people only have one drive connected. And needing to click a drop-down menu to select the only option is a bit pointless.

2. Correct the GUI scaling problem properly. The window should be larger to allow for discrepancies. When I run the software, the settings for the checkboxes are not visible. I have to go into OS settings to guess some different scaling/high-DPI settings, then sign out/in again and hope it works.

3. For the recovery option, users are confused because the utility does not display the recovery-from firmware, which is inconsistent. The selected drive is displayed at the top; and the selected firmware to write is displayed (for both recovery and write modes) at the bottom. Both of these indications make sense. The inconsistency is after clicking "Recover", the user chooses the recover-from firmware and then nothing seems to happen, and there is no display of what was selected. In this thread, there have been many posts from confused users which stem partly from this ambiguity in the software. The effect is that in recover mode it is unclear to some people WTF the software is doing.

[Noob123]

I have a question about the Pioneer BDR-XS06 Drive.

Can it be flashed with the SDFtool flasher?

Is there any benefit to patching the firmware?

The firmware appears to be original.

Thanks!

Here’s the drive info:

Drive Information
Manufacturer: PIONEER
Product: BD-RW BDR-XS06
Revision: 1.10
Serial number:
Firmware date: 2017-06-22
Bus encryption flags: 13
Highest AACS version: 82

LibreDrive Information
Status: Enabled
Drive platform: RS8722
Firmware name: PIONEER BDR-XS06
Firmware type: Original (unpatched)
Firmware version: 1.10
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes

[Billycar11]

I have a question about the Pioneer BDR-XS06 Drive.

Can it be flashed with the SDFtool flasher?

Is there any benefit to patching the firmware?

The firmware appears to be original.

Thanks!

Here’s the drive info:

Drive Information
Manufacturer: PIONEER
Product: BD-RW BDR-XS06
Revision: 1.10
Serial number:
Firmware date: 2017-06-22
Bus encryption flags: 13
Highest AACS version: 82

LibreDrive Information
Status: Enabled
Drive platform: RS8722
Firmware name: PIONEER BDR-XS06
Firmware type: Original (unpatched)
Firmware version: 1.10
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes

Sorry man there is no UHD fw for that drive

[MartyMcNuts]

Three suggestions for the utility:

1. If only one optical drive is found, then it should be automatically selected as the default. Most people only have one drive connected. And needing to click a drop-down menu to select the only option is a bit pointless.

2. Correct the GUI scaling problem properly. The window should be larger to allow for discrepancies. When I run the software, the settings for the checkboxes are not visible. I have to go into OS settings to guess some different scaling/high-DPI settings, then sign out/in again and hope it works.

3. For the recovery option, users are confused because the utility does not display the recovery-from firmware, which is inconsistent. The selected drive is displayed at the top; and the selected firmware to write is displayed (for both recovery and write modes) at the bottom. Both of these indications make sense. The inconsistency is after clicking "Recover", the user chooses the recover-from firmware and then nothing seems to happen, and there is no display of what was selected. In this thread, there have been many posts from confused users which stem partly from this ambiguity in the software. The effect is that in recover mode it is unclear to some people WTF the software is doing.

1. No. Most people have 2+ drives. Very nitpicky! So what if you have to select your single drive...

2. No you don't. Read the first post as it explains you just edit the DPI settings of the exe.

3. It is explained in detailed english. The gif explains it even more. The recover from firmware isn't used for anything other than to obtain a 16 byte string for use in the recover command. There is no need for it to be displayed anywhere. No one needs to know any more than the instruction text each firmware file selection window provides.

[kaysee]

1. No. Most people have 2+ drives. Very nitpicky! So what if you have to select your single drive...

Some people have multiple drives, including myself, but most of these people have only one drive connected at a time -- especially if they are actually updating the firmware for a drive. Standard software behavior is to select a default if it is obvious; like the first item in an enumerated list. The first and only drive in a list of optical drives would be a simple thing to default to. And what else could or would be selected if there is only one?

2. No you don't. Read the first post as it explains you just edit the DPI settings of the exe.

I did exactly that before posting my previous message. The point is that it did not work. Specifically: in the properties for SDFTool 1.3.6 running on up-to-date Windows 10, on the "Compatibility" tab -> Button "Change high DPI settings" -> Section "High DPI scaling override": select "Override high DPI scaling behavior -> Scaling performed by: "System (enhanced)". This did not solve the problem, and made no visual difference. After testing several combinations of compatibility settings including the one described in the first post, I concluded that if the operating system's scaling is something greater than 100%, the SDFTool GUI is malformed no matter what the compatibility settings. The checkbox for "Encrypted" is absent or cut off; a button is labeled "STAR" instead of "START", etc. So changing the override for high DPI scaling to "System (Enhanced)" makes no difference. The only solution is in the system's advanced scaling settings, changing custom scaling to 100%, which requires signing out/in again to apply; it also might not be what the user wants to do for the entire OS appearance. Then SDFTool runs with the GUI properly formed; and SDFTool still is unaffected by what the compatibility settings for it are set to. So SDFTool looks correct only if the OS scaling is 100%, no matter what the compatibility settings are, and looks incorrect if OS scaling is >100%, no matter what the compatibility settings are. This is what I wrote in my previous message.

3. It is explained in detailed english. The gif explains it even more. The recover from firmware isn't used for anything other than to obtain a 16 byte string for use in the recover command. There is no need for it to be displayed anywhere. No one needs to know any more than the instruction text each firmware file selection window provides.

Yes, it is explained, and I did work through the quirky GUI to flash BU40N firmware to a BP50NB40 unit with SVC code NB52 successfully on my first attempt. But confusion over several years among other people, evident from many forum posts, stems partly from odd behavior of the software in recovery mode. The process is not complicated, but the software's behavior is strange. Therefore, yes, there is a need to display what recover-from firmware is currently selected. In order for a write command using recover-from firmware to execute correctly, the correct recover-from firmware needs to be selected. So the current selection of the recover-from firmware should be displayed, just like the correct drive choice and firmware to write should be displayed. All three need to be selected correctly. If any of those selections are wrong, then obviously there will be a problem in the procedure. Why hide the current choice of recover-from firmware? To summarize, the recovery mode requires three correct settings, which should all be shown from top to bottom in the UI:
1. Optical drive
2. Recover-from firmware
3. Firmware to write.

#1 and #3 are displayed. #2 is hidden. All three matter.

[kaysee]

Two responses to the first message:

A. In the list of encrypted firmware in the first message of this thread, this one is missing:

"ASUS_BW-16D1X-U_A105_212012021114_KLQM29F1658"

For this drive/firmware, SDFTool indicates MT1959 platform, encrypted.


B. The first message in this thread has the instruction: "If your desktop drive has encrypted firmware, flash WH16NS60 1.02-MK first, then you can either leave it as is or flash any other desktop drive firmware if you want to." I chose not to write that firmware to the above desktop ASUS drive with encrypted firmware; and instead to directly write "DE_ASUS_BW-16D1HT_3.10_MK.bin". This worked. So, with encrypted firmware as a starting point, there are more options as a first (and possibly final) firmware to write aside from "WH16NS60 1.02-MK".

[MartyMcNuts]

Two responses to the first message:

A. In the list of encrypted firmware in the first message of this thread, this one is missing:

"ASUS_BW-16D1X-U_A105_212012021114_KLQM29F1658"

For this drive/firmware, SDFTool indicates MT1959 platform, encrypted.


B. The first message in this thread has the instruction: "If your desktop drive has encrypted firmware, flash WH16NS60 1.02-MK first, then you can either leave it as is or flash any other desktop drive firmware if you want to." I chose not to write that firmware to the above desktop ASUS drive with encrypted firmware; and instead to directly write "DE_ASUS_BW-16D1HT_3.10_MK.bin". This worked. So, with encrypted firmware as a starting point, there are more options as a first (and possibly final) firmware to write aside from "WH16NS60 1.02-MK".

A. Thanks.

B. When a drive has encrypted firmware, there are only 2 compatible firmware options to begin with: WH16NS60 1.02-MK and BW-16D1HT 3.10-MK. The former is always the recommended firmware thus is part of the instructions. After flashing to either of these, you can then flash whatever firmware version you want.

[MartyMcNuts]

1. No. Most people have 2+ drives. Very nitpicky! So what if you have to select your single drive...

Some people have multiple drives, including myself, but most of these people have only one drive connected at a time -- especially if they are actually updating the firmware for a drive. Standard software behavior is to select a default if it is obvious; like the first item in an enumerated list. The first and only drive in a list of optical drives would be a simple thing to default to. And what else could or would be selected if there is only one?

2. No you don't. Read the first post as it explains you just edit the DPI settings of the exe.

I did exactly that before posting my previous message. The point is that it did not work. Specifically: in the properties for SDFTool 1.3.6 running on up-to-date Windows 10, on the "Compatibility" tab -> Button "Change high DPI settings" -> Section "High DPI scaling override": select "Override high DPI scaling behavior -> Scaling performed by: "System (enhanced)". This did not solve the problem, and made no visual difference. After testing several combinations of compatibility settings including the one described in the first post, I concluded that if the operating system's scaling is something greater than 100%, the SDFTool GUI is malformed no matter what the compatibility settings. The checkbox for "Encrypted" is absent or cut off; a button is labeled "STAR" instead of "START", etc. So changing the override for high DPI scaling to "System (Enhanced)" makes no difference. The only solution is in the system's advanced scaling settings, changing custom scaling to 100%, which requires signing out/in again to apply; it also might not be what the user wants to do for the entire OS appearance. Then SDFTool runs with the GUI properly formed; and SDFTool still is unaffected by what the compatibility settings for it are set to. So SDFTool looks correct only if the OS scaling is 100%, no matter what the compatibility settings are, and looks incorrect if OS scaling is >100%, no matter what the compatibility settings are. This is what I wrote in my previous message.

3. It is explained in detailed english. The gif explains it even more. The recover from firmware isn't used for anything other than to obtain a 16 byte string for use in the recover command. There is no need for it to be displayed anywhere. No one needs to know any more than the instruction text each firmware file selection window provides.

Yes, it is explained, and I did work through the quirky GUI to flash BU40N firmware to a BP50NB40 unit with SVC code NB52 successfully on my first attempt. But confusion over several years among other people, evident from many forum posts, stems partly from odd behavior of the software in recovery mode. The process is not complicated, but the software's behavior is strange. Therefore, yes, there is a need to display what recover-from firmware is currently selected. In order for a write command using recover-from firmware to execute correctly, the correct recover-from firmware needs to be selected. So the current selection of the recover-from firmware should be displayed, just like the correct drive choice and firmware to write should be displayed. All three need to be selected correctly. If any of those selections are wrong, then obviously there will be a problem in the procedure. Why hide the current choice of recover-from firmware? To summarize, the recovery mode requires three correct settings, which should all be shown from top to bottom in the UI:
1. Optical drive
2. Recover-from firmware
3. Firmware to write.

#1 and #3 are displayed. #2 is hidden. All three matter.

1. No, most people have all of their drives connected all the time. I know it is trivial but I am not going to do an update just for this. If the time comes when there are a few things that need updating then I will add this in. May not be relevant soon as there won't be any more optical drives anyway!

2. You are the first person I have heard say that changing the DPI settings of the exe did not resolve their issue.

3. There is no need to display this anywhere. The popup firmware selection box asks the user to select the current firmware that is on the drive. If the user cannot or doesn't know how to select the firmware version they just previously flashed to the drive then they should not be flashing a drive in the first place! A few months back the BP50NB40 guide section was rewritten to make it more clear to stop the confusion. Most of the time, confusion is a result of a user diving in and not actually reading the instructions or watching the gif.

[ChildishhAlbino]

Hey there,

Tried to run the tool and it keeps popping up with an error saying something to the effect of "Cannot find MakeMKV Installation. Please install MakeMKV and try again."

But I have MakeMKV installed. What could be causing the bug?

[Billycar11]

Hey there,

Tried to run the tool and it keeps popping up with an error saying something to the effect of "Cannot find MakeMKV Installation. Please install MakeMKV and try again."

But I have MakeMKV installed. What could be causing the bug?

install makemkv in the default location

[ChildishhAlbino]

Hey there,

Tried to run the tool and it keeps popping up with an error saying something to the effect of "Cannot find MakeMKV Installation. Please install MakeMKV and try again."

But I have MakeMKV installed. What could be causing the bug?

install makemkv in the default location

Worked thanks. I didn't realise it default installed to Program Files (x86).