SDFtool Flasher

[cinerama19806]

Update to my previous posting: it appears the "startindex" error might be a "showstopper" after all as it appears the earlier poster had the same error and the same inability to choose drive letters in the application. (I'm not inclined to use the command line version unless absolutely necessary.)

[MartyMcNuts]

Many thanks for all your efforts here. Hopefully this one's an easy fix and I'm just missing something simple trying to use the SDFtool Flasher. (Side note: I previously successfully flashed an Asus drive but I don't remember when or how, and that drive has pretty much given up the ghost for burning and hasn't successfully opened a 4K disc in ages (lots of grinding) even though it's Libradrive enabled.)

I've now purchased a Verbatim external 4K drive from Amazon (not too many options out there now) which Makemkv is reading as

Drive Information
OS device name: D:
Manufacturer: HL-DT-ST
Product: BD-RE BU40N
Revision: 1.05
Serial number: MO6PAKA5435
Firmware date: 2124-04-23 13:47
Bus encryption flags: 17
Highest AACS version: 82

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

When I open the SDFtool Flasher for this drive I get the same error previously noted: StartIndex cannot be less than zero (which I believe is not a "show stopper". Once I advance to the software window, I don't see a drive available for flashing (i.e. there's no option available in the pulldown menu for the drive. I don't know if it matters, but I've removed my previous Asus drive as an option and have assigned the new drive the "D" drive letter. (I believe I'm OK with the flash version needed and it's available to me from the "all you need firmware pack" (LG Slim BU40N) - but I can't get there without being able to select a drive.) Please let me know what I'm missing here.

Ensure you have MakeMKV installed in the default location (C:\Program File (x86)\MakeMKV).
Ensure there is no disc in the drive and the tray is closed.

If the drive still isn't seen, try changing ports. Best to use USB ports direct from the motherboard, not case ports. An AC self-powered USB hub of at least 24w is even better.

Once the drive is showing in SDFtool Flasher, flash it to BU40N 1.03-MK.

[MartyMcNuts]

Hey MartyMcNuts!

Thank you so much for replying.

It is an internal Sata. Works with CD's and DVD's.
I'm running Windows 11 Pro 25H2 OS Build: 26200.7462

Cheers!

I know what the model is as it's in the MakeMKV drive info.

So is it installed internally and connected via SATA or externally using something else?

It is installed internally and connected via SATA, yes.

Did you power cycle the PC after flashing? Not restart, full shutdown and power back up after a minute.

Also, it might have something to do with your SATA ports, especially if using an AMD board/chipset. If using AMD, I think it should not be connected to SATA ports 0 or 1. If not using AMD, you still might need to change SATA ports anyway.

Other options are to try a SATA to USB powered adapter with your PC or connect the drive to another PC to flash.

[benraro]

Hello, I'm having trouble understanding which firmware I should use. I get that it's MK version, but I'm unsure which one.
I have the SDFtool, and downloaded the list here: viewtopic.php?f=19&t=19113

Since mine is BU40N with UHD compatible, but made in Taiwan on the back I wasn't sure if I should use: \mk-firmware-pack-20200720\MK\HL-DT-ST\BU40N-R-Tier2-Taiwan\
Or another one. Thank you.

Code: Select all

Drive Information
OS device name: G:
Current profile: BD-ROM
Manufacturer: HL-DT-ST
Product: BD-RE BU40N
Revision: 1.05
Serial number: MODPAKB1710
Firmware date: 2124-04-23 13:47
Bus encryption flags: 17
Highest AACS version: 76

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

I ended up figuring it out. Thank you very much.

Did you grab my all you need firmware pack from the same place you downloaded the SDFtool Flasher? If so, it has BU40N 1.03-MK in it. Flash this. You can then leave it on BU40N 1.03-MK or you can flash it down to BU40N 1.00 for more UHD software compatability.

[cinerama19806]

Many thanks for all your efforts here. Hopefully this one's an easy fix and I'm just missing something simple trying to use the SDFtool Flasher. (Side note: I previously successfully flashed an Asus drive but I don't remember when or how, and that drive has pretty much given up the ghost for burning and hasn't successfully opened a 4K disc in ages (lots of grinding) even though it's Libradrive enabled.)

I've now purchased a Verbatim external 4K drive from Amazon (not too many options out there now) which Makemkv is reading as

Drive Information
OS device name: D:
Manufacturer: HL-DT-ST
Product: BD-RE BU40N
Revision: 1.05
Serial number: MO6PAKA5435
Firmware date: 2124-04-23 13:47
Bus encryption flags: 17
Highest AACS version: 82

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

When I open the SDFtool Flasher for this drive I get the same error previously noted: StartIndex cannot be less than zero (which I believe is not a "show stopper". Once I advance to the software window, I don't see a drive available for flashing (i.e. there's no option available in the pulldown menu for the drive. I don't know if it matters, but I've removed my previous Asus drive as an option and have assigned the new drive the "D" drive letter. (I believe I'm OK with the flash version needed and it's available to me from the "all you need firmware pack" (LG Slim BU40N) - but I can't get there without being able to select a drive.) Please let me know what I'm missing here.

Ensure you have MakeMKV installed in the default location (C:\Program File (x86)\MakeMKV).
Ensure there is no disc in the drive and the tray is closed.

If the drive still isn't seen, try changing ports. Best to use USB ports direct from the motherboard, not case ports. An AC self-powered USB hub of at least 24w is even better.

Once the drive is showing in SDFtool Flasher, flash it to BU40N 1.03-MK.

Are we referencing the same thing about a drive not being "seen"? I can burn discs with no problems, but no drive is visible in the pulldown menu of the tool. (Someone a page or so back said they had the same problem with the startindex error and resorted to the command line version of the software to perform the flashing.) (Someone on reddit noted some time ago that the pull-down for the drives is very small and perhaps even smaller on a 4K monitor. I had to resort to the "change high DPI settings" to get the software window to a point where I could see anything.)

[MartyMcNuts]

Many thanks for all your efforts here. Hopefully this one's an easy fix and I'm just missing something simple trying to use the SDFtool Flasher. (Side note: I previously successfully flashed an Asus drive but I don't remember when or how, and that drive has pretty much given up the ghost for burning and hasn't successfully opened a 4K disc in ages (lots of grinding) even though it's Libradrive enabled.)

I've now purchased a Verbatim external 4K drive from Amazon (not too many options out there now) which Makemkv is reading as

Drive Information
OS device name: D:
Manufacturer: HL-DT-ST
Product: BD-RE BU40N
Revision: 1.05
Serial number: MO6PAKA5435
Firmware date: 2124-04-23 13:47
Bus encryption flags: 17
Highest AACS version: 82

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

When I open the SDFtool Flasher for this drive I get the same error previously noted: StartIndex cannot be less than zero (which I believe is not a "show stopper". Once I advance to the software window, I don't see a drive available for flashing (i.e. there's no option available in the pulldown menu for the drive. I don't know if it matters, but I've removed my previous Asus drive as an option and have assigned the new drive the "D" drive letter. (I believe I'm OK with the flash version needed and it's available to me from the "all you need firmware pack" (LG Slim BU40N) - but I can't get there without being able to select a drive.) Please let me know what I'm missing here.

Ensure you have MakeMKV installed in the default location (C:\Program File (x86)\MakeMKV).
Ensure there is no disc in the drive and the tray is closed.

If the drive still isn't seen, try changing ports. Best to use USB ports direct from the motherboard, not case ports. An AC self-powered USB hub of at least 24w is even better.

Once the drive is showing in SDFtool Flasher, flash it to BU40N 1.03-MK.

Are we referencing the same thing about a drive not being "seen"? I can burn discs with no problems, but no drive is visible in the pulldown menu of the tool. (Someone a page or so back said they had the same problem with the startindex error and resorted to the command line version of the software to perform the flashing.) (Someone on reddit noted some time ago that the pull-down for the drives is very small and perhaps even smaller on a 4K monitor. I had to resort to the "change high DPI settings" to get the software window to a point where I could see anything.)

The SDFtool Flasher GUI is a front end for the MakeMKV CLI application and requires MakeMKV to be installed in the default location. I said this because of the StartIndex error you said you were getting.

[RSMegane]

I know what the model is as it's in the MakeMKV drive info.

So is it installed internally and connected via SATA or externally using something else?

It is installed internally and connected via SATA, yes.

Did you power cycle the PC after flashing? Not restart, full shutdown and power back up after a minute.

Also, it might have something to do with your SATA ports, especially if using an AMD board/chipset. If using AMD, I think it should not be connected to SATA ports 0 or 1. If not using AMD, you still might need to change SATA ports anyway.

Other options are to try a SATA to USB powered adapter with your PC or connect the drive to another PC to flash.

Yep, I shut down every day.

I just attempted it again as I've shut down multiple times since the first attempt, but it didn't work.

I also switched the SATA port from 5 to 1, then tried it again, still no luck

[MartyMcNuts]

It is installed internally and connected via SATA, yes.

Did you power cycle the PC after flashing? Not restart, full shutdown and power back up after a minute.

Also, it might have something to do with your SATA ports, especially if using an AMD board/chipset. If using AMD, I think it should not be connected to SATA ports 0 or 1. If not using AMD, you still might need to change SATA ports anyway.

Other options are to try a SATA to USB powered adapter with your PC or connect the drive to another PC to flash.

Yep, I shut down every day.

I just attempted it again as I've shut down multiple times since the first attempt, but it didn't work.

I also switched the SATA port from 5 to 1, then tried it again, still no luck

You are trying to flash WH16NS60 1.02-MK firmware aren't you? If so, I'm out of ideas. As I said, you may need to try a SATA to USB powered adapter from the Ultimate UHD Drive Flashing Guide 2026 or try a different PC.

[RSMegane]

Did you power cycle the PC after flashing? Not restart, full shutdown and power back up after a minute.

Also, it might have something to do with your SATA ports, especially if using an AMD board/chipset. If using AMD, I think it should not be connected to SATA ports 0 or 1. If not using AMD, you still might need to change SATA ports anyway.

Other options are to try a SATA to USB powered adapter with your PC or connect the drive to another PC to flash.

Yep, I shut down every day.

I just attempted it again as I've shut down multiple times since the first attempt, but it didn't work.

I also switched the SATA port from 5 to 1, then tried it again, still no luck

You are trying to flash WH16NS60 1.02-MK firmware aren't you? If so, I'm out of ideas. As I said, you may need to try a SATA to USB powered adapter from the Ultimate UHD Drive Flashing Guide 2026 or try a different PC.

Good news. I tried something I probably shouldn't have, and it worked.

I used the RECOVER DRIVE option instead of the WRITE FIRMWARE option, and it wrote it.

I am now able to read the Blu-Ray disc through MakeMKV

[cinerama19806]

Ensure you have MakeMKV installed in the default location (C:\Program File (x86)\MakeMKV).
Ensure there is no disc in the drive and the tray is closed.

If the drive still isn't seen, try changing ports. Best to use USB ports direct from the motherboard, not case ports. An AC self-powered USB hub of at least 24w is even better.

Once the drive is showing in SDFtool Flasher, flash it to BU40N 1.03-MK.

Are we referencing the same thing about a drive not being "seen"? I can burn discs with no problems, but no drive is visible in the pulldown menu of the tool. (Someone a page or so back said they had the same problem with the startindex error and resorted to the command line version of the software to perform the flashing.) (Someone on reddit noted some time ago that the pull-down for the drives is very small and perhaps even smaller on a 4K monitor. I had to resort to the "change high DPI settings" to get the software window to a point where I could see anything.)

The SDFtool Flasher GUI is a front end for the MakeMKV CLI application and requires MakeMKV to be installed in the default location. I said this because of the StartIndex error you said you were getting.

MakeMKV 1.18.2 is installed in the default location. I'll be attempting to burn a double layer disc soon. If that works, the ability to read 4K discs (and copy to one of my many hard drives) is just "icing on the cake" Side question: is there anywhere to find step-by-step instructions for using the command line tool? (As noted earlier, I don't know now how and when I successfully flashed my most likely dead ASUS.)

[MartyMcNuts]

Are we referencing the same thing about a drive not being "seen"? I can burn discs with no problems, but no drive is visible in the pulldown menu of the tool. (Someone a page or so back said they had the same problem with the startindex error and resorted to the command line version of the software to perform the flashing.) (Someone on reddit noted some time ago that the pull-down for the drives is very small and perhaps even smaller on a 4K monitor. I had to resort to the "change high DPI settings" to get the software window to a point where I could see anything.)

The SDFtool Flasher GUI is a front end for the MakeMKV CLI application and requires MakeMKV to be installed in the default location. I said this because of the StartIndex error you said you were getting.

MakeMKV 1.18.2 is installed in the default location. I'll be attempting to burn a double layer disc soon. If that works, the ability to read 4K discs (and copy to one of my many hard drives) is just "icing on the cake" Side question: is there anywhere to find step-by-step instructions for using the command line tool? (As noted earlier, I don't know now how and when I successfully flashed my most likely dead ASUS.)

The Ultimate UHD Drive Flashing Guide 2026 has the commands needed.

[cinerama19806]

Apropos of maybe nothing, but I had a successful burn of a double layer disc on my new "Verbatim" external drive. (FWIW: as an experiment, I disconnected the new burner from the computer, tried the SDFtool Flasher again and STILL get the StartIndex error - one I also get with the 1.35 version and the original version from 2020. When I open MakeMKV, I still see my old Asus drive with LibreDrive enabled, but I don't expect to have any luck using it to open 4K discs or burn any kind of BluRay. (I don't remember having any problems flashing my old Asus using - I believe - some version of the flashing tool, as I very much doubt I would have gone to the trouble of using the Command Line version.)

As I'm sure you're aware, the StartIndex error is not specific to this particular software, as I've discovered in a quick jaunt down the Google rabbit hole. Just a thought: could our present problems be related to the version of MakeMKV that's being used rather than the SDFtool Flasher itself? (FYI: no plans here to use the command line version as I would need a LOT of hand holding to do so and I'm reasonably OK just finishing up the burning of the few 3D files I have which must be viewed from disc rather than from my PLEX server. I did attempt to set up a Zidoo in the past so I could read from an .iso file for 3D, but Zidoo - unlike Plex - seems not too happy unless running from a well organized NAS. My Shield and Plex work great, and my Oppo works OK playing discs as needed.

[nicholfd]

Apropos of maybe nothing, but I had a successful burn of a double layer disc on my new "Verbatim" external drive. (FWIW: as an experiment, I disconnected the new burner from the computer, tried the SDFtool Flasher again and STILL get the StartIndex error - one I also get with the 1.35 version and the original version from 2020. When I open MakeMKV, I still see my old Asus drive with LibreDrive enabled, but I don't expect to have any luck using it to open 4K discs or burn any kind of BluRay. (I don't remember having any problems flashing my old Asus using - I believe - some version of the flashing tool, as I very much doubt I would have gone to the trouble of using the Command Line version.)

As I'm sure you're aware, the StartIndex error is not specific to this particular software, as I've discovered in a quick jaunt down the Google rabbit hole. Just a thought: could our present problems be related to the version of MakeMKV that's being used rather than the SDFtool Flasher itself? (FYI: no plans here to use the command line version as I would need a LOT of hand holding to do so and I'm reasonably OK just finishing up the burning of the few 3D files I have which must be viewed from disc rather than from my PLEX server. I did attempt to set up a Zidoo in the past so I could read from an .iso file for 3D, but Zidoo - unlike Plex - seems not too happy unless running from a well organized NAS. My Shield and Plex work great, and my Oppo works OK playing discs as needed.

This problem is known & specific to your PC/Windows/MakeMKV installation/settings, at least when using SDFtool.exe - current and many previous versions of MakeMKV work perfectly well on Windows 10/11 with SDFtool.exe. Answer is here in the forums - check DPI/screen % settings (set to 100%). Make sure MakeMKV is installed in the standard/default location, etc. Make sure the USB -> SATA enclosure/adapter is standard compliant. Make sure the drive is receiving sufficient power via USB. Could be specific to your computer's USB chipset.

The "StartIndex error" message is a generic error message when an empty list/array is trying to be used to display something (drop-down list, etc. - your empty list of drive to flash), or be used. That's why you found a "rabbit hole" via Google.

Note that drives are flashed to be able to rip/backup discs - not burn them. Flashing a drive may impact its ability to burn media.

Thanks,
Frank

[cinerama19806]

Many thanks for your reply; lots to deal with here.

I find it somewhat disconcerting that flashing might impact the ability to burn. Where is this unfortunate
"side effect" documented? It there's the possibility I'll lose the ability to burn, I'll burn the 3D files that
I need to and hold off on any attempts to flash the drive. (I believe all's good with the drive as far as power and
whatever as I've had no issues burning double layer discs, but I'll go back to examine all the elements you noted as
something I should search for. As noted elsewhere, the ability to "read" 4K discs is a "nice to have" feature as it lets
me put the files on one of my various hard drives and access them in a somewhat more "elegant" fashion than using
my Oppo player.

Something to consider after I complete all my immediate burning needs: are you perhaps suggesting going back to an
earlier version of MakeMKV might prove helpful? (I was earlier successful flashing my ASUS, but it's no longer able to read
4K or burn discs of any kind. It CAN FWIW use MakeMKV to extract files from BluRay discs)

[nicholfd]

Many thanks for your reply; lots to deal with here.

I find it somewhat disconcerting that flashing might impact the ability to burn. Where is this unfortunate
"side effect" documented? It there's the possibility I'll lose the ability to burn, I'll burn the 3D files that
I need to and hold off on any attempts to flash the drive. (I believe all's good with the drive as far as power and
whatever as I've had no issues burning double layer discs, but I'll go back to examine all the elements you noted as
something I should search for. As noted elsewhere, the ability to "read" 4K discs is a "nice to have" feature as it lets
me put the files on one of my various hard drives and access them in a somewhat more "elegant" fashion than using
my Oppo player.

Something to consider after I complete all my immediate burning needs: are you perhaps suggesting going back to an
earlier version of MakeMKV might prove helpful? (I was earlier successful flashing my ASUS, but it's no longer able to read
4K or burn discs of any kind. It CAN FWIW use MakeMKV to extract files from BluRay discs)

Note that 4K/UHD reading can require more power than audio/DVD/Blu-Ray. With USB, this can be an issue. The USB standard is 5v, 500ma. This is not enough, and some Wintel systems barely meet that spec (and some do not). A good, powered USB hub (some are recommended in these forums - search) can help eliminate this as a possible issue.

This is a forum for software designed to backup/rip a disc, not burn discs. The point of flashing firmware is to be able to backup/rip discs. Changes to the firmware are to allow this to happen & optimize backup/ripping, without necessarily considering burning media. Different versions of firmware have different "features". With different firmwares specifically for backing up/ripping discs, I don't think there is much consideration for the ability to burn. I'm not saying you will lose the ability, but I am saying no one is intentionally trying to verify/retain the ability to burn discs (and I'm not trying to say they are intentionally trying to remove the ability - just not a consideration).

I am not suggesting using an older version of MakeMKV. Other than running MakeMKV under Linux, and an issue with the current major version, I know of no benefit/reason to use an older version of MakeMKV on macOS or Windows 10/11.