www.makemkv.com

Closes thing I see is DE_LG_WH16NS40-NS50_1.02.bin
The -N550 is not on my drive.

Plus, make the window resizable.
Windows 11 sucks on scaling and I can't read all that is in the small window.

Sandman192 wrote: ↑

Sun Dec 17, 2023 12:23 am

Closes thing I see is DE_LG_WH16NS40-NS50_1.02.bin
The -N550 is not on my drive.

Plus, make the window resizable.
Windows 11 sucks on scaling and I can't read all that is in the small window.

First of all, no one has any idea on what "window" you are talking about resizing....

Second, if your WH16NS40 is not a SVC:NS50, then it must be an old NS40 (manufactured before October 2015) and cannot be flashed.

First of all, no one has any idea on what "window" you are talking about resizing....

Second, if your WH16NS40 is not a SVC:NS50, then it must be an old NS40 (manufactured before October 2015) and cannot be flashed.

The window for SDFtool Flasher is so messed up.

And what do you mean if it has no NS50 it's old? My Blue-Ray can read and burn BD-R XL 128GB Disks. I don't thank it's that old.
Also I get a strange reading from MakeMKV that my BD firmware is dated "Firmware date: 2120-05-06 14:40"

And for some reason I can't add an attachment. I get "Sorry, the board attachment quota has been reached.". Which I don't know what it means.

Sandman192 wrote: ↑

Mon Dec 18, 2023 10:49 am

The window for SDFtool Flasher is so messed up.

In the first post of the SDFtool Flasher thread, right near the top, there's a note that reads:

NOTE: If the GUI looks a bit deformed (happens on a 4k monitor), you can right click the exe and select properties. In the compatibility tab, click "Change high DPI settings" then under "High DPI scaling override" tick the box and select "System (Enhanced)" in the dropbox.

Sandman192 wrote: ↑

Mon Dec 18, 2023 10:49 am

And what do you mean if it has no NS50 it's old? My Blue-Ray can read and burn BD-R XL 128GB Disks. I don't thank it's that old.
Also I get a strange reading from MakeMKV that my BD firmware is dated "Firmware date: 2120-05-06 14:40"

And for some reason I can't add an attachment. I get "Sorry, the board attachment quota has been reached.". Which I don't know what it means.

In the first post of the Ultimate UHD Drives Flashing Guide, there's a section
with big red letters that says STOP READ BEFORE FLASHING and has a bunch of warnings about the necessity about the various requirements for things like the drive platform (MT1959) and SVC:NS50 among others. It also lists the consequences of trying to flash something that's too old.

NOTE: If the GUI looks a bit deformed (happens on a 4k monitor), you can right click the exe and select properties. In the compatibility tab, click "Change high DPI settings" then under "High DPI scaling override" tick the box and select "System (Enhanced)" in the dropbox.

Thank for that but as stupid as Windows is on scaling... And now I don't see the SDFtool flasher on screen when I turned on "System (Enhanced) and I know it's off screen since Windows did it to other programs. Some I could shift right click on the open programs in the Taskbar and click move. But doesn't work for SDFtool.

But if anyone reading this and has this problem when you can't see the SDFtool when enabling "System (Enhanced)" is to close program and turn off "System (Enhanced)" and open the program again and move it to the top of the screen (for me anyway) and close SDFtool again and turn on "System (Enhanced)" again and reopen the program you should hopefully see it screen.

As for the firmware (I didn't mean drivers) I'll get back to that later.

I was asking if there any drivers (I mean firmware) for my WH16NS40 Blu-Ray as in if the developer would work on one.

Also, the SDFtool says it has a firmware update which I see is not true.

LibreDrive Information
Status: Possible (with patched firmware)
Drive platform: MT1959
Harware support: Yes
Firmware support: No
Firmware type: Original (patched version available)
Firmware version: 1.05
DVD all regions: Possible (with patched firmware)
BD raw data read: Possible (with patched firmware)
BD raw metadata read: Possible (with patched firmware)
Unrestricted read speed: Possible (with patched firmware)

Sandman192 wrote: ↑

Mon Dec 25, 2023 10:33 pm

I was asking if there any drivers (I mean firmware) for my WH16NS40 Blu-Ray as in if the developer would work on one.

Also, the SDFtool says it has a firmware update which I see is not true.

LibreDrive Information
Status: Possible (with patched firmware)
Drive platform: MT1959
Harware support: Yes
Firmware support: No
Firmware type: Original (patched version available)
Firmware version: 1.05
DVD all regions: Possible (with patched firmware)
BD raw data read: Possible (with patched firmware)
BD raw metadata read: Possible (with patched firmware)
Unrestricted read speed: Possible (with patched firmware)

Per the 1st post (maintained & current) of "the guide":

WH16NS40 on any Firmware directly to > WH16NS60 1.02MK

If running Windows, use the SDFtool Flasher, following the instructions in the 1st post.

Hint: v1.05 is encrypted (if you missed that in the guide) so flip the 'enc' switch.

WH16NS40 on any Firmware directly to > WH16NS60 1.02MK

I don't know what you means?

Hint: v1.05 is encrypted (if you missed that in the guide) so flip the 'enc' switch

Still don't know what you mean?
And I didn't need to do any of whatever you're talking about.

I used the "mk-firmware-pack-20200720" zip folder and used the "HL-DT-ST-BD-RE_BH16NS40-NS50-1.05-NM00600-212005061331.bin" file.
Found out the SDFtool Flasher 1.3.5.0 is a bit buggy. I had to select the .BIN file first and THEN select the drive.
The drive now plays UHD disk. Even after the flash I still got an error. No I will not try again to repercuss the error. It's working and I'll leave it at that.
And according to LG firmware program, it is a NS50. But SDFtool doesn't show any were that the drive is.

Bugs:
1. Select .BIN file first.
2. Doesn't show NS50 on a HL-DL-ST-BD-RE_BH16NS40.
3. Still got an error code but firmware was a success because I can play UHD.

I do have the error code I get every time on fail attempt, 1 looked promising because it took a little longer with the green bar moving across then error and on successful update of the drive but still got an error.

"Command produced error code 0x82062900"

Sandman192 wrote: ↑

Fri Dec 29, 2023 7:58 pm

I do have the error code I get every time on fail attempt, 1 looked promising because it took a little longer with the green bar moving across then error and on successful update of the drive but still got an error.

"Command produced error code 0x82062900"

You need to describe your hardware /software setup. The problem is on your side. Don't blame SDFTool Flasher.

Coopervid wrote: ↑

Fri Dec 29, 2023 8:09 pm

Sandman192 wrote: ↑

Fri Dec 29, 2023 7:58 pm

I do have the error code I get every time on fail attempt, 1 looked promising because it took a little longer with the green bar moving across then error and on successful update of the drive but still got an error.

"Command produced error code 0x82062900"

You need to describe your hardware /software setup. The problem is on your side. Don't blame SDFTool Flasher.

On my side how?
AMD 7 7700X, 32Gig RAM, HDs which I see is all irrelevant other then the Blu-Ray drive through SATA, the Win 11 and SDFtool v1.3.5.

Sandman192 wrote: ↑

Tue Jan 02, 2024 9:57 pm

Coopervid wrote: ↑

Fri Dec 29, 2023 8:09 pm

Sandman192 wrote: ↑

Fri Dec 29, 2023 7:58 pm

I do have the error code I get every time on fail attempt, 1 looked promising because it took a little longer with the green bar moving across then error and on successful update of the drive but still got an error.

"Command produced error code 0x82062900"

You need to describe your hardware /software setup. The problem is on your side. Don't blame SDFTool Flasher.

On my side how?
AMD 7 7700X, 32Gig RAM, HDs which I see is all irrelevant other then the Blu-Ray drive through SATA, the Win 11 and SDFtool v1.3.5.

amd sata chipsets seem to throw more errors most times the flash still goes through and if yours is seeing UHD discs your good now

Doesn't matter but AMD might still be the issue after all these years.