Ultimate UHD Drives Flashing Guide Updated 2025

[Billycar11]

What about Leawo Prof. Media BR Ripper?

This is VERY old news, but on the off chance it still applies...

viewtopic.php?f=5&t=1514

Have no idea about that, but it works perfectly!
That's the official site I made the purchase 1 year ago:

Yes because it's using makemkv as a backend
It's not nice to push a program that's stealing from this one here

[hopefullythisworks]

Hello Billy, Thanks for making this flashing tool.
I was having some issues with flashing my drive. I have an LG WH16NNS60 with the encrypted (I guess? The dump matches one of the ones in the encrypted list and the flasher autoflags it) firmware 1.03. The drive is mounted internally in my case with a seta cable. I have tried flashing the 1.02-MK and another random 1.03 (I'm assuming it was "-MK" since I downloaded it from an older thread) firmware, but I get the same error every time, and the drive information in MakeMKV doesn't change.

Please see pictures below. I followed all the instructions, and searched for other users with this exact issue and couldn't find anything similar. So I made this account to hopefully get help resolving this issue. I purchased this drive around a year ago and it works find for regular blurays, but this is my first time trying to flash the firmware.

Thanks.

WhatHappensWhenITryToFlash.PNG (54.92 KiB) Viewed 12724 times

current_firmware.PNG (2.98 KiB) Viewed 12724 times

driveInfo1.PNG (44.03 KiB) Viewed 12724 times

[ibumpthis]

Hello Billy, Thanks for making this flashing tool.
I was having some issues with flashing my drive. I have an LG WH16NNS60 with the encrypted (I guess? The dump matches one of the ones in the encrypted list and the flasher autoflags it) firmware 1.03. The drive is mounted internally in my case with a seta cable. I have tried flashing the 1.02-MK and another random 1.03 (I'm assuming it was "-MK" since I downloaded it from an older thread) firmware, but I get the same error every time, and the drive information in MakeMKV doesn't change.

Please see pictures below. I followed all the instructions, and searched for other users with this exact issue and couldn't find anything similar. So I made this account to hopefully get help resolving this issue. I purchased this drive around a year ago and it works find for regular blurays, but this is my first time trying to flash the firmware.

Thanks.

WhatHappensWhenITryToFlash.PNG
current_firmware.PNG
driveInfo1.PNG

Googling your error code (the memory 0x code) I came across this post viewtopic.php?t=23587

Indicating from a few users that the error was caused by having a disc in the drive. Is that the case in your situation?

[Kainhander]

Longshot here, but are there any slot-loading 12.7mm drives that are recommended? I think I saw an off brand one on Amazon but thought I would check here.

[Baby_Groot]

Hi,

I finally got round to trying to flash my older LG BP50NB40 (Manufactured May 2016 - MT1959) external Blu-ray drive to enable 4K ripping but I must have done something wrong as it doesn't seem to work at all now (no eject & won't read discs - still recognised by Windows/MakeMKV). Would love it if someone could fill me in as to what went wrong and if there's any possible fix?

Using SDFTool 1.3.5, I firstly backed up my firmware and then updated the drive's firmware as per the guide using the files from the 'The all you need firmware pack':

My original firmware dump was: HL-DT-ST_BD-RE_BP50NB40_1.00_211504221517

I updated to: HL-DT-ST-BD-RE_BP50NB40-NB50-1.03-NM00800-212005070917 and then to: HL-DT-ST-BD-RE_BP60NB10-1.02-NM00800-212005070935.

Each step said it was completed successfully but the drive's bung.

If I bring it up in SDFTool/MakeMKV is recognises the drive as D: HL-DT-ST_BD-RE_BP50NB40_1.03_212005070917. If I try flashing it back to the original firmware, it says successful but nothing changes - still bung and still same says 1.03 firmware under MakeMKV and SDFTool.

I do have other 4k drives for ripping and previously had flashed an ASUS drive for 4K using the guides but not sure what I've done with this one.

Thanks!

[glc650]

I've been using an Asus BW-16D1HT drive (with 3.10 MK firmware) for a while now but I'm tired of dealing with the sleep bug so I want to switch firmware. Which firmware eliminates the sleep bug but also maintains AnyDVD compatibility?

[MartyMcNuts]

I've been using an Asus BW-16D1HT drive (with 3.10 MK firmware) for a while now but I'm tired of dealing with the sleep bug so I want to switch firmware. Which firmware eliminates the sleep bug but also maintains AnyDVD compatibility?

WH16NS60 1.00 or 1.02-MK

[glc650]

I've been using an Asus BW-16D1HT drive (with 3.10 MK firmware) for a while now but I'm tired of dealing with the sleep bug so I want to switch firmware. Which firmware eliminates the sleep bug but also maintains AnyDVD compatibility?

WH16NS60 1.00 or 1.02-MK

I thought the MK firmware doesn't work with anything but makemkv? Any performance or capability difference between the two?

[MartyMcNuts]

I've been using an Asus BW-16D1HT drive (with 3.10 MK firmware) for a while now but I'm tired of dealing with the sleep bug so I want to switch firmware. Which firmware eliminates the sleep bug but also maintains AnyDVD compatibility?

WH16NS60 1.00 or 1.02-MK

I thought the MK firmware doesn't work with anything but makemkv? Any performance or capability difference between the two?

No real diff. I haven't looked at AnyDVD for a few years. Try 1.02-MK. If it doesn't work with AnyDVD switch to 1.00

[glc650]

WH16NS60 1.00 or 1.02-MK

I thought the MK firmware doesn't work with anything but makemkv? Any performance or capability difference between the two?

No real diff. I haven't looked at AnyDVD for a few years. Try 1.02-MK. If it doesn't work with AnyDVD switch to 1.00

Ok I see a half dozen 1.02s in the mk firmware pack so which do I use? BH16NS60, WH16NS60 or one of the others?

[Mr_Orange]

I thought the MK firmware doesn't work with anything but makemkv? Any performance or capability difference between the two?

No real diff. I haven't looked at AnyDVD for a few years. Try 1.02-MK. If it doesn't work with AnyDVD switch to 1.00

Ok I see a half dozen 1.02s in the mk firmware pack so which do I use? BH16NS60, WH16NS60 or one of the others?

WH16NS60, as per the previous response.

[glc650]

No real diff. I haven't looked at AnyDVD for a few years. Try 1.02-MK. If it doesn't work with AnyDVD switch to 1.00

Ok I see a half dozen 1.02s in the mk firmware pack so which do I use? BH16NS60, WH16NS60 or one of the others?

WH16NS60, as per the previous response.

Flashed and tested. All good. Thanks.

[glc650]

Thinking about picking up a second drive for another PC. Any reason to get a Pioneer BDR-XS07UHD over a Archgon MD-8107S-U3-UHD (besides not having to flash)? Reliability? Performance? Software compatibility?

[MartyMcNuts]

Thinking about picking up a second drive for another PC. Any reason to get a Pioneer BDR-XS07UHD over a Archgon MD-8107S-U3-UHD (besides not having to flash)? Reliability? Performance? Software compatibility?

The Pioneer only works with MakeMKV and AnyDVD software. The Archgon, if flashed with BU40N 1.00 works with all ripping software. The Archgon is a little bit quicker (6x vs 4x). The Pioneer drives are generally a bit quieter.

[SamuriHL]

So I don't usually have any issues flashing drives but I'm new to the Mac. My dad got a new Archgon BU40n that came with 1.02. I attempted to flash that with 1.03MK from the terminal on my MacBook Pro M2. Said everything was successful, I power cycled the drive, and it still shows 1.02 non-LibreDrive enabled. Tried it a couple times and all claimed success in flashing the drive but none of them seemed to actually update the firmware. Any thoughts on this?

I will likely try with my own Archgon bu40n even though I have 1.00 on it already just to see if I can fix this process before Wednesday when I see my dad again and would like to try again. He doesn't get his new Windows laptop with USB-C on it til the end of the month and I'm not using USB-A to flash that thing given all the potential power issues. But I thought I'd post here in case anyone had run into this and had any suggestions. I tend to use VS Code and open a terminal inside of it but I also tried a standalone terminal. One thing I didn't try was to SUDO the command. Didn't think that'd be necessary but thinking about it now it's something I probably should have tried.