Ultimate UHD Drives Flashing Guide Updated 2026

[jatenk]

What?!?

Your Verbatim should be a BU40N drive with 1.05 on it. There's no trick to flashing it. Just use SDFTool flasher and flash it directly to BU40N 1.03-MK (we call all firmware in the pack "MK" as it's far easier than NM000343.....) first, which will remove the firmware encryption and the drive is now ready for use with MakeMKV. If you also want to use other ripping software such as DVDFab etc, then you can flash it to DE BU40N 1.00.

I can't use the GUI SDFTool since I'm on macOS, but I'm okey with using Terminal. So just side-grading it to 1.03 (from MK/old) will be enough to make it usable and able to rip UHD movies already? Sorry for my slow uptake - english isn't my first language.

ah, ok. there's no side-grade. You are using the same model firmware at all times.

Yes, use firmware BU40N 1.03-MK from the MK/old folder and make sure you have rawflash enc in your command. Once the drive has been flashed and shows as firmware BU40N 1.03 you are done and can start using it to rip your UHD discs.

Wow, that was exceedingly simple. Thanks a bunch, it seems to be working! Does this mean I should never update my driver's firmware from here on out? Since I sent my 1.05 firmware dump to MakeMKV's support email, will it be flashed/flashable soon?

[MartyMcNuts]

I can't use the GUI SDFTool since I'm on macOS, but I'm okey with using Terminal. So just side-grading it to 1.03 (from MK/old) will be enough to make it usable and able to rip UHD movies already? Sorry for my slow uptake - english isn't my first language.

ah, ok. there's no side-grade. You are using the same model firmware at all times.

Yes, use firmware BU40N 1.03-MK from the MK/old folder and make sure you have rawflash enc in your command. Once the drive has been flashed and shows as firmware BU40N 1.03 you are done and can start using it to rip your UHD discs.

Wow, that was exceedingly simple. Thanks a bunch, it seems to be working! Does this mean I should never update my driver's firmware from here on out? Since I sent my 1.05 firmware dump to MakeMKV's support email, will it be flashed/flashable soon?

There was no need to send in that firmware dump as we can already flash it. It's really only useful if it inhibits us from flashing the drive.

Correct. No need to ever update the firmare.

[jatenk]

ah, ok. there's no side-grade. You are using the same model firmware at all times.

Yes, use firmware BU40N 1.03-MK from the MK/old folder and make sure you have rawflash enc in your command. Once the drive has been flashed and shows as firmware BU40N 1.03 you are done and can start using it to rip your UHD discs.

Wow, that was exceedingly simple. Thanks a bunch, it seems to be working! Does this mean I should never update my driver's firmware from here on out? Since I sent my 1.05 firmware dump to MakeMKV's support email, will it be flashed/flashable soon?

There was no need to send in that firmware dump as we can already flash it. It's really only useful if it inhibits us from flashing the drive.

Correct. No need to ever update the firmare.

Wait, so if my dump could already be flashed, why didn't I just flash that instead of replacing the firmware? Or is it possible, but not published yet? Also, to make sure, my question is, _should_ I never update my firmware? (Instead of just not needing to?)

[MartyMcNuts]

Wow, that was exceedingly simple. Thanks a bunch, it seems to be working! Does this mean I should never update my driver's firmware from here on out? Since I sent my 1.05 firmware dump to MakeMKV's support email, will it be flashed/flashable soon?

There was no need to send in that firmware dump as we can already flash it. It's really only useful if it inhibits us from flashing the drive.

Correct. No need to ever update the firmare.

Wait, so if my dump could already be flashed, why didn't I just flash that instead of replacing the firmware? Or is it possible, but not published yet? Also, to make sure, my question is, _should_ I never update my firmware? (Instead of just not needing to?)

No, you are misunderstanding. I said the drive can already be flashed to v1.03-MK without issue so there is no need for a v1.05. v1.03-MK is recommended and is what you flash it to. Once on v1.03-MK, there's no need to ever update it.

[jatenk]

Weird, a couple UHD discs worked, but I'm getting the same error message again:

Code: Select all

...
Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - KEY NOT ESTABLISHED' occurred while issuing SCSI command AD010..080002400 to device 'IoKit:/IOBDServices/D48F36DD'
Can't read AACS VID from disc - most likely current AACS host certificate is revoked by your drive
Saved AACS dump file as /Users/xxxxx/Library/MakeMKV/yyyyy.tgz
LibreDrive compatible drive is required to open this disc - video can't be decrypted
Failed to open disc

Would this be due to a disc whose key isn't known yet?

[MartyMcNuts]

Weird, a couple UHD discs worked, but I'm getting the same error message again:

Code: Select all

...
Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - KEY NOT ESTABLISHED' occurred while issuing SCSI command AD010..080002400 to device 'IoKit:/IOBDServices/D48F36DD'
Can't read AACS VID from disc - most likely current AACS host certificate is revoked by your drive
Saved AACS dump file as /Users/xxxxx/Library/MakeMKV/yyyyy.tgz
LibreDrive compatible drive is required to open this disc - video can't be decrypted
Failed to open disc

Would this be due to a disc whose key isn't known yet?

No. It appears your drive has been revoked. Did you flash it?

Post your drive and libredrive info sections.

[jatenk]

Weird, a couple UHD discs worked, but I'm getting the same error message again:

Code: Select all

...
Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - KEY NOT ESTABLISHED' occurred while issuing SCSI command AD010..080002400 to device 'IoKit:/IOBDServices/D48F36DD'
Can't read AACS VID from disc - most likely current AACS host certificate is revoked by your drive
Saved AACS dump file as /Users/xxxxx/Library/MakeMKV/yyyyy.tgz
LibreDrive compatible drive is required to open this disc - video can't be decrypted
Failed to open disc

Would this be due to a disc whose key isn't known yet?

No. It appears your drive has been revoked. Did you flash it?

Post your drive and libredrive info sections.

Yes, like I said, a couple discs worked, then none worked anymore, even the ones that used to work. I re-flashed it, even though the firmware was already the same I was flashing it with, and it's working again now. What's happening here?

[MartyMcNuts]

Weird, a couple UHD discs worked, but I'm getting the same error message again:

Code: Select all

...
Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - KEY NOT ESTABLISHED' occurred while issuing SCSI command AD010..080002400 to device 'IoKit:/IOBDServices/D48F36DD'
Can't read AACS VID from disc - most likely current AACS host certificate is revoked by your drive
Saved AACS dump file as /Users/xxxxx/Library/MakeMKV/yyyyy.tgz
LibreDrive compatible drive is required to open this disc - video can't be decrypted
Failed to open disc

Would this be due to a disc whose key isn't known yet?

No. It appears your drive has been revoked. Did you flash it?

Post your drive and libredrive info sections.

Yes, like I said, a couple discs worked, then none worked anymore, even the ones that used to work. I re-flashed it, even though the firmware was already the same I was flashing it with, and it's working again now. What's happening here?

Post your drive and libredrive info sections.

What USB are you using?? I wonder if the drive lost connection for a moment?

[jatenk]

No. It appears your drive has been revoked. Did you flash it?

Post your drive and libredrive info sections.

Yes, like I said, a couple discs worked, then none worked anymore, even the ones that used to work. I re-flashed it, even though the firmware was already the same I was flashing it with, and it's working again now. What's happening here?

Post your drive and libredrive info sections.

What USB are you using?? I wonder if the drive lost connection for a moment?

Lost connection when? Surely not during the flashing process, since a couple discs worked. Or does the drive need to be permanently connected once flashed in order to not lose it?

Drive Information
OS device name: /dev/rdisk8
Current profile: BD-ROM
Manufacturer: HL-DT-ST
Product: BD-RE BU40N
Revision: 1.03
Serial number: MO4OB1E3451
Firmware date: 2118-10-24 19:34
Bus encryption flags: 17
Highest AACS version: 81

LibreDrive Information
Status: Enabled
Drive platform: MT1959
Firmware type: Patched (microcode access re-enabled)
Firmware version: 1.03
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes

Don't have those sections copied from when it didn't work (since it works again after re-flashing it with the same firmware), but I know for a fact that it said Revision 1.03 already while it wasn't working. Connected with USB-C to USB-A cable to a hub which is connected to my M4 Pro through USB-C.

[keydb_helper]

No. It appears your drive has been revoked. Did you flash it?

Post your drive and libredrive info sections.

After a drive has been flashed with a LibreDrive compatible firmware AACS certificate revocation is largely irrelevant from MakeMKV's perspective.

Can't read AACS VID from disc

The fact that AACS authentication was even attempted by MakeMKV indicates that the LibreDrive microcode is not behaving as expected, so MakeMKV had to resort to the non-LibreDrive fallback authentication option. This can usually be avoided by power cycling the drive and allowing MakeMKV to start from a clean slate.

Yes, like I said, a couple discs worked, then none worked anymore, even the ones that used to work. I re-flashed it, even though the firmware was already the same I was flashing it with, and it's working again now. What's happening here?

Reflashing the drives firmware has the side effect of triggering a self-reboot of the drive at the end of the flashing process. So to be clear, your issue was not resolved by the firmware flash itself - it was resolved due to the drive rebooting.

Lost connection when? Surely not during the flashing process, since a couple discs worked. Or does the drive need to be permanently connected once flashed in order to not lose it?

No, the drive can be freely powered down, unplugged, re-plugged etc after it has been flashed with a LibreDrive compatible firmware. There is no requirement for regular drive flashing. I have some drives which were flashed exactly once 4-5 years ago and they still work as expected with BD/UHD discs.

[jatenk]

No. It appears your drive has been revoked. Did you flash it?

Post your drive and libredrive info sections.

After a drive has been flashed with a LibreDrive compatible firmware AACS certificate revocation is largely irrelevant from MakeMKV's perspective.

Can't read AACS VID from disc

The fact that AACS authentication was even attempted by MakeMKV indicates that the LibreDrive microcode is not behaving as expected, so MakeMKV had to resort to the non-LibreDrive fallback authentication option. This can usually be avoided by power cycling the drive and allowing MakeMKV to start from a clean slate.

Yes, like I said, a couple discs worked, then none worked anymore, even the ones that used to work. I re-flashed it, even though the firmware was already the same I was flashing it with, and it's working again now. What's happening here?

Reflashing the drives firmware has the side effect of triggering a self-reboot of the drive at the end of the flashing process. So to be clear, your issue was not resolved by the firmware flash itself - it was resolved due to the drive rebooting.

Lost connection when? Surely not during the flashing process, since a couple discs worked. Or does the drive need to be permanently connected once flashed in order to not lose it?

No, the drive can be freely powered down, unplugged, re-plugged etc after it has been flashed with a LibreDrive compatible firmware. There is no requirement for regular drive flashing. I have some drives which were flashed exactly once 4-5 years ago and they still work as expected with BD/UHD discs.

So I can fix it by unplugging and replugging it (which is what power-cycling is, as I understand?), but how did it happen in the first place, might it happen again, and how do I make sure it doesn't?

[keydb_helper]

So I can fix it by unplugging and replugging it (which is what power-cycling is, as I understand?)

Yes, that is correct

(B)ut how did it happen in the first place, might it happen again, and how do I make sure it doesn't?

It can be caused by a number of things: bugs in the stock firmware, limitations of the LibreDrive microcode, transient power supply issues etc.

A popular suggestion on this forum is to use an externally powered USB hub to minimise the likelihood of power supply induced problems. Apart from that there isn't much you can do avoid the issue entirely. I know it sounds like a cop out but power cycling the drive will address most issues.

[jatenk]

So I can fix it by unplugging and replugging it (which is what power-cycling is, as I understand?)

Yes, that is correct

(B)ut how did it happen in the first place, might it happen again, and how do I make sure it doesn't?

It can be caused by a number of things: bugs in the stock firmware, limitations of the LibreDrive microcode, transient power supply issues etc.

A popular suggestion on this forum is to use an externally powered USB hub to minimise the likelihood of power supply induced problems. Apart from that there isn't much you can do avoid the issue entirely. I know it sounds like a cop out but power cycling the drive will address most issues.

Just so I can categorise the issue correctly, is this an issue with the flash, with the flashed 1.03 firmware, with the original 1.05 firmware or something else inside the drive? In my 10 years of using my old drive, in many of which I used makeMKV, I never had any such problems, but that was a standard blu-ray drive and even with this issue I was still able to rip standard blu-rays.

[keydb_helper]

Just so I can categorise the issue correctly, is this an issue with the flash, with the flashed 1.03 firmware, with the original 1.05 firmware or something else inside the drive?

The firmware which you flashed to your drive is cryptographically signed. If there was any corruption with the firmware flash, your drive would boot into a very limited recovery mode. That is not what happened to you. Remember, re-flashing the firmware did not fix anything that power cycling couldn't. Your drive is still running the exact same code as it was before you re-flashed it with the same MK firmware binary.

You need to think of your drive as essentially being a very small, low power computer running its own software stack or firmware. It is entirely possible that there are no significant issues in the firmware code. But just like a desktop computer overclocked beyond the point of stability, transient power supply issues can lead to problems and unexpected behaviour in otherwise stable code.

This is most likely what happened with your drive. It is effectively the same as running a stress test like Prime95 or Furmark on a barely stable overclock and observing a crash in Microsoft Outlook. Restarting the computer will address the issue and allow Outlook to function normally. Improving the stability by bolstering the power supply will reduce the likelihood of a repeat incident.

So if you must categorise your issue, I'd call it a temporary glitch caused by insufficient power supply.

In my 10 years of using my old drive, in many of which I used makeMKV, I never had any such problems, but that was a standard blu-ray drive and even with this issue I was still able to rip standard blu-rays.

To backup UHD discs, MakeMKV uploads a small 'blob' of code to your drives volatile memory. This is what I referred to as the LibreDrive microcode earlier.

The MakeMKV software which runs on your Linux/Mac/Windows computer can interact with this microcode to perform several functions, such as reading the AACS volume ID (VID) or preventing the drive from performing bus encryption.

This microcode based approach has been strict requirement for AACS2 (UHD) discs but it has not been mandated for AACS1 (regular BD) disc decryption as there has always been an abundance of AACS1 host certificate/keys. This may be why you never noticed such quirks in the past when backing up standard BD discs as even when LibreDrive is unavailable the native AACS fallback path is usable.

The overall stability of the microcode approach doesn't quite match that of native AACS authentication, but it is worth it to be functionally immune from AACS host certificate revocation.

[jatenk]

Just so I can categorise the issue correctly, is this an issue with the flash, with the flashed 1.03 firmware, with the original 1.05 firmware or something else inside the drive?

The firmware which you flashed to your drive is cryptographically signed. If there was any corruption with the firmware flash, your drive would boot into a very limited recovery mode. That is not what happened to you. Remember, re-flashing the firmware did not fix anything that power cycling couldn't. Your drive is still running the exact same code as it was before you re-flashed it with the same MK firmware binary.

You need to think of your drive as essentially being a very small, low power computer running its own software stack or firmware. It is entirely possible that there are no significant issues in the firmware code. But just like a desktop computer overclocked beyond the point of stability, transient power supply issues can lead to problems and unexpected behaviour in otherwise stable code.

This is most likely what happened with your drive. It is effectively the same as running a stress test like Prime95 or Furmark on a barely stable overclock and observing a crash in Microsoft Outlook. Restarting the computer will address the issue and allow Outlook to function normally. Improving the stability by bolstering the power supply will reduce the likelihood of a repeat incident.

So if you must categorise your issue, I'd call it a temporary glitch caused by insufficient power supply.

In my 10 years of using my old drive, in many of which I used makeMKV, I never had any such problems, but that was a standard blu-ray drive and even with this issue I was still able to rip standard blu-rays.

To backup UHD discs, MakeMKV uploads a small 'blob' of code to your drives volatile memory. This is what I referred to as the LibreDrive microcode earlier.

The MakeMKV software which runs on your Linux/Mac/Windows computer can interact with this microcode to perform several functions, such as reading the AACS volume ID (VID) or preventing the drive from performing bus encryption.

This microcode based approach has been strict requirement for AACS2 (UHD) discs but it has not been mandated for AACS1 (regular BD) disc decryption as there has always been an abundance of AACS1 host certificate/keys. This may be why you never noticed such quirks in the past when backing up standard BD discs as even when LibreDrive is unavailable the native AACS fallback path is usable.

The overall stability of the microcode approach doesn't quite match that of native AACS authentication, but it is worth it to be functionally immune from AACS host certificate revocation.

Thank you very much for the elaborate information, that's exactly what I'm looking for! I think I get it, except for the part where the drive wouldn't read any UHDs anymore at all, and is now reading every disc perfectly again. If the issue is found in a temporary power delivery issue combined with code injection every time a UHD disc is read, wouldn't that limit the issue to occurring only on every individual disc read attempt, instead of working several times, and suddenly not working at all anymore, until power cycling it? Or is the idea of what might have happened that the first faulty disc read attempt accidentally injected faulty microcode, because of some power issue, and that faulty code (presumably because of being faulty) then didn't reset itself once the disc was ejected and persisted into the following attempts, and only got flushed from the drive's system upon power cycling it?