Heads up - Support for LG UHD drives

[Billycar11]

Today the support for "official UHD" drives was finally enabled (not as smooth as it was hoped). As of today most "official" drives are supported, EXCEPT ones with latest firmware. If you have an "UHD official" drive, you should get one of two messages:
Code 03DF - your drive is working fine, you can make UHD backup with it
Code 01BE - your drive firmware version is not yet supported.
The proper explanation is coming soon. Thanks for the patience!

i have a question about how drives crossflashed to wh16ns60 1.00 will work will everything be fine? because before they worked but with failed key exchange errors i haven't given anyone a drive like that yet just me and a friend but many people want the sleep bug gone.

[forty2]

Today the support for "official UHD" drives was finally enabled (not as smooth as it was hoped). As of today most "official" drives are supported, EXCEPT ones with latest firmware. If you have an "UHD official" drive, you should get one of two messages:
Code 03DF - your drive is working fine, you can make UHD backup with it
Code 01BE - your drive firmware version is not yet supported.
The proper explanation is coming soon. Thanks for the patience!

Do I need to do anything special to get access to the new features? I've tried first with the version 1.14.2 that I already had installed, then tried again after redownloading and reinstalling. But in both cases, attempts to rip a UHD disk don't work, and I don't see either of these codes anywhere either. I'm sure I'm doing something wrong, but I can't seem to figure out what.

Thanks a lot for all the hard work; I'm a huge fan of this tool (and a paid-up license owner ), and I'm super excited to start ripping all my UHD disks.

[jsuaggie]

Owner of a ASUS BW-16D1HT, on its way, should have it next week!

Where did you purchase your drive? I hope it comes with the "UHD Friendly" firmware.

[Billycar11]

Do I need to do anything special to get access to the new features? I've tried first with the version 1.14.2 that I already had installed, then tried again after redownloading and reinstalling. But in both cases, attempts to rip a UHD disk don't work, and I don't see either of these codes anywhere either. I'm sure I'm doing something wrong, but I can't seem to figure out what.

Thanks a lot for all the hard work; I'm a huge fan of this tool (and a paid-up license owner ), and I'm super excited to start ripping all my UHD disks.

what official drive do you have right now only bu40n and clones on 1.00 and wh16ns60 1.00 are supported i think.
i tested a wh16ns60 on 1.00 and it worked, going to try a asus on 1.00 later and see what happens

[forty2]

what official drive do you have right now only bu40n and clones on 1.00 and wh16ns60 1.00 are supported i think.
i tested a wh16ns60 on 1.00 and it worked, going to try a asus on 1.00 later and see what happens

Ah, that might be my problem then. The drive is a bu50n. I'm pretty sure the firmware is 1.00, but I'm having trouble confirming that. I've had it for a while and never updated it, but of course that doesn't mean much.

[jonghotti]

>>going to try a asus on 1.00 later and see what happens

You're going to flash an ASUS with LG firmware 1.00? Why?

[demon]

Do I need to do anything special to get access to the new features? I've tried first with the version 1.14.2 that I already had installed, then tried again after redownloading and reinstalling. But in both cases, attempts to rip a UHD disk don't work, and I don't see either of these codes anywhere either. I'm sure I'm doing something wrong, but I can't seem to figure out what.

What OS are you on? For me, on Linux, this is what MakeMKV looked like after ripping a disc on my laptop:

https://owncloud.now.ai/index.php/s/UPb1hifvpgog22d

The "DEBUG: Code 03DF/..." line is what you should see if it's successfully able to rip from your drive. My BU40N worked fine with the 1.01 firmware (note the "Revision:" line in the box on the right; that's how the 1.01 firmware on this drive identifies itself).

And no, you don't need to redownload the app. The "Downloading latest SDF" and "Downloading latest HK" items in the log window are the app downloading the data it needs to do the rip. If you see "DEBUG: Code 01BE/...", as mike said, then your drive isn't cooperating. It looks like 1.00 is the latest firmware for that drive on the HLDS site, so it may just not work for a bit yet, but I'm sure mike is working on it.

[forty2]

What OS are you on? For me, on Linux, this is what MakeMKV looked like after ripping a disc on my laptop:

https://owncloud.now.ai/index.php/s/UPb1hifvpgog22d

The "DEBUG: Code 03DF/..." line is what you should see if it's successfully able to rip from your drive. My BU40N worked fine with the 1.01 firmware (note the "Revision:" line in the box on the right; that's how the 1.01 firmware on this drive identifies itself).

And no, you don't need to redownload the app. The "Downloading latest SDF" and "Downloading latest HK" items in the log window are the app downloading the data it needs to do the rip. If you see "DEBUG: Code 01BE/...", as mike said, then your drive isn't cooperating. It looks like 1.00 is the latest firmware for that drive on the HLDS site, so it may just not work for a bit yet, but I'm sure mike is working on it.

Thanks a lot for the screenshot; it's very useful to see what it's supposed to look like.

I've tried with both Linux and Windows, and I get the same results in either case. I do have debug logging turned on, but I don't see any Code 01BE or 03DF message.

https://snag.gy/0yermX.jpg

I notice that my Revision field says "0420" and "Firmware date" says "2116-05-24 19:01". I know I'm running the risk of asking questions no one has any way to know the answers to, but is there any reason to think that my firmware might actually be older than 1.00? I wonder if there's any value in trying to run the firmware update utility... On the other hand, I'd hate to ruin my chances of getting it working by doing something stupid...

Thanks again for the help!

[demon]

I've tried with both Linux and Windows, and I get the same results in either case. I do have debug logging turned on, but I don't see any Code 01BE or 03DF message.

Have you tried starting a backup? You won't see either of the debug code lines until you start a backup of a disc, at which point you'll get "Downloading latest SDF" and "Downloading latest HK" messages. That's the only way you'll know for sure if it works or not.

I notice that my Revision field says "0420" and "Firmware date" says "2116-05-24 19:01". I know I'm running the risk of asking questions no one has any way to know the answers to, but is there any reason to think that my firmware might actually be older than 1.00? I wonder if there's any value in trying to run the firmware update utility... On the other hand, I'd hate to ruin my chances of getting it working by doing something stupid...

Yeah, it's hard to know for sure. It's certainly possible that they shipped some hardware with a pre-1.0 firmware image, but I definitely can't confirm. I don't have extensive experience with LG's laptop drives, so dunno if that's ever something they do.

[forty2]

Have you tried starting a backup? You won't see either of the debug code lines until you start a backup of a disc, at which point you'll get "Downloading latest SDF" and "Downloading latest HK" messages. That's the only way you'll know for sure if it works or not.

Yeah, when I try an actual backup, I get a ton of "ILLEGAL REQUEST: COPY PROTECTION KEY EXCHANGE FAILURE" messages, and it eventually just fails to back up without any Code 03DF/01BE. This screenshot is on Windows, but I get the same results on Linux.

https://snag.gy/IWBG0O.jpg

Yeah, it's hard to know for sure. It's certainly possible that they shipped some hardware with a pre-1.0 firmware image, but I definitely can't confirm. I don't have extensive experience with LG's laptop drives, so dunno if that's ever something they do.

Makes sense. I guess I'll have to decide if I'm feeling lucky or not Thanks again!

[Billycar11]

>>going to try a asus on 1.00 later and see what happens

You're going to flash an ASUS with LG firmware 1.00? Why?

no sleep bug i have had it like this for months i mostly playback disks not rip them

[jonghotti]

You and that sleep bug

So it appears as of today's surprise update makeMKV users can be confident in the following models/firmwares working wonderfully:

WH16NS60 firmware 1.00
BU40N firmware 1.00, A101, 1.02? I've only had time to verify 1.00 but I've got no less than five flavors of BU40N firmware to go through.

Needs more work:
WH16NS60 firmware 1.01 (log will fill with illegal request: copy protection key exchange failure - key not present) and then error out
BU50N firmware ?? (I have a few of these to go through)
BP60NB10 firmware 1.00 (this spews out the key exchange failure message along with many many hash check this file is corrupt messages which are obviously bogus)

Way to go Mike though, this is huge.

And of course for those people needing a WH16NS60 or BU40N with or without external enclosures (the one i've got for the BU40N is super duper cool) please email or text me.

[mike admin]

I've tried with both Linux and Windows, and I get the same results in either case. I do have debug logging turned on, but I don't see any Code 01BE or 03DF message.
I notice that my Revision field says "0420" and "Firmware date" says "2116-05-24 19:01".

I want your firmware!!!!

Please navigate to MakeMKV data directory (location can be looked up in preferences). Inside you will find one or more files named dump_SD_xxxxx.tgz . Please send them all to support@makemkv.com . Thanks!

[jonghotti]

I’ve got one to send you that’s been growing for awhile. Sure hope there’s a way to make the 60/10 useful.

[Billycar11]

well i tried wh16ns60 1.00 on an asus with the new feature enabled it works fine no failed key exchanges like before but im just wondering if there ever could be some sort of problem from this like if aacs 2.x is ever cracked how would these drives handle it since they have no encryption chip.