BP50NB40 not working; "Failure #3"

[forresthopkinsa]

I'll try to make this brief.

I bought an LG BP50NB40. SVC-NB50, manufactured 2019-09-10, FW 1.02. Goal is to rip UHD discs.

I installed MakeMKV on a Windows 10 machine, installation went fine, sdf_xxxxx.bin is visible in ~/.MakeMKV/_private_data.tar. However, when I open the program, I don't see any LibreDrive info for my drive:

makemkv.PNG (45.95 KiB) Viewed 20778 times

Okay, weird, maybe it'll show up after I flash. I follow all the instructions in Marty's ASUS Flasher thread, and I try to use that tool to flash either the 1.01_MK or Hybrid firmwares. However, neither work -- when I start the flashing process, the drive ejects instantly and the process fails, saying "Failure #3":

asus-fw.PNG (48.18 KiB) Viewed 20778 times

Pretty weird. A couple people, in connection to this error, have suggested perhaps a faulty/incompatible drive enclosure -- but this advice doesn't seem relevant to the BP50NB40, which can only be used externally, communicating over USB. There are no SATA cables or drive enclosures; the whole thing is self-contained.

Any ideas?

Thanks.

[MartyMcNuts]

I'll try to make this brief.

I bought an LG BP50NB40. SVC-NB50, manufactured 2019-09-10, FW 1.02. Goal is to rip UHD discs.

I installed MakeMKV on a Windows 10 machine, installation went fine, sdf_xxxxx.bin is visible in ~/.MakeMKV/_private_data.tar. However, when I open the program, I don't see any LibreDrive info for my drive:

makemkv.PNG

Okay, weird, maybe it'll show up after I flash. I follow all the instructions in Marty's ASUS Flasher thread, and I try to use that tool to flash either the 1.01_MK or Hybrid firmwares. However, neither work -- when I start the flashing process, the drive ejects instantly and the process fails, saying "Failure #3":

asus-fw.PNG

Pretty weird. A couple people, in connection to this error, have suggested perhaps a faulty/incompatible drive enclosure -- but this advice doesn't seem relevant to the BP50NB40, which can only be used externally, communicating over USB. There are no SATA cables or drive enclosures; the whole thing is self-contained.

Any ideas?

Thanks.

To see the LibreDrive info, please insert a disc.

To rip UHD, First, you need to flash the BP50NB40 1.02 MK firmware from the MK folder. Then you can cross-flash using the hybrid BP60NB10 1.00 firmware.

[jinx100]

forresthopkinsa wrote:

I installed MakeMKV on a Windows 10 machine, installation went fine, sdf_xxxxx.bin is visible in ~/.MakeMKV/_private_data.tar. However, when I open the program, I don't see any LibreDrive info for my drive:

If you lack LibreDrive information, then sdf.bin is probably not installed in your data directory. Is the option "allow contacting the server" enabled and do you have an internet connection?

[orrelljet]

I'm getting the same error, with the same drive on the same firmware version (1.02).

Any suggestions?

EDIT. Silly question but would this have anything to do with the year on the firmware showing as "2119"?

EDIT 2. Just spotted the drive I've just bought is actually SVC: NB40; am I out of luck?

[forresthopkinsa]

Okay so I guess this thread is probably going to be a dud, but maybe the solution will be helpful to someone out there.

The problem was a stupid one. It looks like the first time I downloaded the ASUS Flasher, I did it from the MediaFire link, and the .exe must have been corrupted in transit or something. I tried downloading it again, this time from the direct link, and that .exe worked fine.

FWIW here are the checksums:

From the MediaFire link, here's the broken ASUS_ODD_FW_Changer_(Modified).exe MD5:

e83e8c24545da818475ec765479ed696

From the direct link, here's the working ASUS_ODD_FW_Changer_(Modified).exe MD5:

61a8bc642db0c5bca7a12282aad66f7d

Sorry for the waste of time guys, it's all working brilliantly now. I appreciate the support.

[MartyMcNuts]

I'm getting the same error, with the same drive on the same firmware version (1.02).

Any suggestions?

EDIT. Silly question but would this have anything to do with the year on the firmware showing as "2119"?

EDIT 2. Just spotted the drive I've just bought is actually SVC: NB40; am I out of luck?

To enable libredrive, you need to flash the BP50NB40 1.02 MK firmware from the MK folder.

To rip UHD, after flashing 1.02-MK, you can cross-flash using the hybrid BP60NB10 1.00 firmware.

1. No. That is just the way the year is shown.
2. It could still work on the SVC: NB40 so long as MakeMKV shows the drive as "Drive platform: MT1959"

[orrelljet]

The problem was a stupid one. It looks like the first time I downloaded the ASUS Flasher, I did it from the MediaFire link, and the .exe must have been corrupted in transit or something. I tried downloading it again, this time from the direct link, and that .exe worked fine.

Bloody genius!!

Worked for me too.

[pawsoffroad]

I have a BP50NB40 SVC CODE NB40 and drive platform MT1959 but after performing the firmware update, I can no longer eject or read disks, is my drive toast or what should be done to fix this? I did copy the original firmware but that isn't loading back for some reason.
Hopefully I didn't screw anything up...

[Billycar11]

I have a BP50NB40 SVC CODE NB40 and drive platform MT1959 but after performing the firmware update, I can no longer eject or read disks, is my drive toast or what should be done to fix this? I did copy the original firmware but that isn't loading back for some reason.
Hopefully I didn't screw anything up...

And what did you flash it to?

[pawsoffroad]

HL-DT-ST-BD-RE_BP50NB40-NB50-1.03-NM00800-212005070917.bin

[jonghotti]

HL-DT-ST-BD-RE_BP50NB40-NB50-1.03-NM00800-212005070917.bin

Ouch!

So you have a BP50NB40-NB40 and you flashed it to BP50NB40-NB50

[pawsoffroad]

Correct, it was mentioned that as long as the platform is MT1959 then it “could” work. I was willing to take the gamble but, maybe I did something wrong? That’s why I’m here asking.
If more information is needed, I am willing to provide answers.

[erict7862]

Correct, it was mentioned that as long as the platform is MT1959 then it “could” work. I was willing to take the gamble but, maybe I did something wrong? That’s why I’m here asking.
If more information is needed, I am willing to provide answers.

I know this thread is a bit old, but were you able to resolve the issue or do you still happen to have a copy of the original firmware.

I risked the flash as well and I have the same issue now.