LG BH16NS40 bricked?

[Billycar11]

Thank you very much!!!
I followed the procedure in dosflash and now everything has started working as usual again

great glad it back up and working

[PauloCZ]

Hi, I also have an LG BH16NS40 (NS40) with a bad firnwere 1.05 (NS50). I followed the steps above, but the process failed. The drive now has the correct version 1.03, but still does not read any media. Please, give me an advice. Thanks

[twiztedtbone]

Sorry in advance for the slight necro, but I think I'm having the exact same issue as PauloCZ (and, minus the success, didoin).

I have a 2014 LG BH16NS40 that, in my infinite wisdom, I flashed with the 1.05 FW for NS50 drives. I followed the exact steps in this thread (including matching when didoin would get errors) and I was able to get 1.03 back onto the drive. Now both Device Manager and MakeMKV (not to mention the LG flasher, DOSflash, etc.) see the drive as being on 1.03, but the drive continues to be unable to read any discs (I'll put discs in but nothing happens).

Any advice for an occasionally hopeless idiot?

[Billycar11]

Sorry in advance for the slight necro, but I think I'm having the exact same issue as PauloCZ (and, minus the success, didoin).

I have a 2014 LG BH16NS40 that, in my infinite wisdom, I flashed with the 1.05 FW for NS50 drives. I followed the exact steps in this thread (including matching when didoin would get errors) and I was able to get 1.03 back onto the drive. Now both Device Manager and MakeMKV (not to mention the LG flasher, DOSflash, etc.) see the drive as being on 1.03, but the drive continues to be unable to read any discs (I'll put discs in but nothing happens).

Any advice for an occasionally hopeless idiot?

are you using ns40 1.03 and not 1.03 ns50?

[twiztedtbone]

are you using ns40 1.03 and not 1.03 ns50?

I'm pretty confident; I downloaded direct from LG "[The Latest Firmware] Firmware (ver. 1.03-A0) for only BH16NS40(SUPER MULTI BLUE BLU-RAY)" from 8/29/2014

[Billycar11]

are you using ns40 1.03 and not 1.03 ns50?

I'm pretty confident; I downloaded direct from LG "[The Latest Firmware] Firmware (ver. 1.03-A0) for only BH16NS40(SUPER MULTI BLUE BLU-RAY)" from 8/29/2014

show us the makemkv drive info if its mt1959 its the new firmware you need 1939 i have it linked in my thread i think for the old stuff

[twiztedtbone]

show us the makemkv drive info if its mt1959 its the new firmware you need 1939 i have it linked in my thread i think for the old stuff

Here you go!

5gvSzbBqC4.png (9.27 KiB) Viewed 16127 times

[Billycar11]

show us the makemkv drive info if its mt1959 its the new firmware you need 1939 i have it linked in my thread i think for the old stuff

Here you go!

5gvSzbBqC4.png

I see it is the correct firmware Im guessing when you flashed it with dos flash you didn't use the data mover tool so your drive has no calibration data

[twiztedtbone]

I see it is the correct firmware Im guessing when you flashed it with dos flash you didn't use the data mover tool so your drive has no calibration data

Oh damn...you're probably right. Am I completely screwed? At one point I took a read of my current firmware (it backed it up to a .tar archive) using the SDFtool, is that enough to recover something?

[Billycar11]

I see it is the correct firmware Im guessing when you flashed it with dos flash you didn't use the data mover tool so your drive has no calibration data

Oh damn...you're probably right. Am I completely screwed? At one point I took a read of my current firmware (it backed it up to a .tar archive) using the SDFtool, is that enough to recover something?

possibly you were supposed to follow my dos flash video though. and make a backup with that.
i dont know how the cal data is stored in the tar file or if it is but i think it is. maybe mike could offer advice on how to move move it out to a firmware to flash.

[twiztedtbone]

i dont know how the cal data is stored in the tar file or if it is but i think it is. maybe mike could offer advice on how to move move it out to a firmware to flash.

Here's a screenshot of what's in the .tar archive if it helps (this dump was taken from the bad (NS50) firmware that still should've had my calibration data, as I had just flashed it over the stock and working 1.03)

2021-03-29_13-21.png (17.57 KiB) Viewed 15983 times

[MastersEyes]

Hello how about, I have the same inconvenience that twiztedtbone (before message)
Please help!!

Edit: I updated my unit to the FW LG 1.05 and I did a dump only with SDF Tool. I do not have firmware backup done with dosflasher, although I could return to flash the unit to version 1.03, do not read any disk, I have the NS40 model

[Woodstock]

Have you tried the things already posted in this topic? If it is truly the "same inconvenience", the same solutions should work.

[twiztedtbone]

Have you tried the things already posted in this topic? If it is truly the "same inconvenience", the same solutions should work.

In my first post I said:

I followed the exact steps in this thread (including matching when didoin would get errors)

The problem is that I'm an occasional dumbass and, because I was being too literal in following the steps in the thread, I skipped the step in Billy's YouTube video on using the data mover tool to transfer my drive's calibration data to the new firmware prior to flashing it. While my drive now has the correct firmware on it, it has no calibration data, and as such still doesn't work.

I have no clue (Billy indicated he didn't either, perhaps you do?) if it's possible to recover my calibration data from the dump I made of my old firmware using sdftool, but that's my only chance at this point. It seems Mike might be the only one with those answers so I'm probably just hoping he responds at some point. The sdftool read firmware function makes a .tar archive with six different .bin files, and I'm definitely not confident enough to guess which one is which or how to properly flash them back to my drive.

Based on the man page for sdftool and the filename of the .tar archive, I probably did a non-volatile user data dump:

OUor4eLS6d.png (17.52 KiB) Viewed 15750 times

...but the filenames it creates are a bit too cryptic for me to confidently start flashing them to my drive (see the pic in my previous post), and I can't find any further info on what each of the .bin files might be.

Chances are that I just bricked my drive, and I'm just gonna have to own that and buy a new one at some point. My own fault for not following directions, but I figured I'd hop on and see if anything was possible.

[MartyMcNuts]

Have you tried the things already posted in this topic? If it is truly the "same inconvenience", the same solutions should work.

In my first post I said:

I followed the exact steps in this thread (including matching when didoin would get errors)

The problem is that I'm an occasional dumbass and, because I was being too literal in following the steps in the thread, I skipped the step in Billy's YouTube video on using the data mover tool to transfer my drive's calibration data to the new firmware prior to flashing it. While my drive now has the correct firmware on it, it has no calibration data, and as such still doesn't work.

I have no clue (Billy indicated he didn't either, perhaps you do?) if it's possible to recover my calibration data from the dump I made of my old firmware using sdftool, but that's my only chance at this point. It seems Mike might be the only one with those answers so I'm probably just hoping he responds at some point. The sdftool read firmware function makes a .tar archive with six different .bin files, and I'm definitely not confident enough to guess which one is which or how to properly flash them back to my drive.

Based on the man page for sdftool and the filename of the .tar archive, I probably did a non-volatile user data dump:
OUor4eLS6d.png
...but the filenames it creates are a bit too cryptic for me to confidently start flashing them to my drive (see the pic in my previous post), and I can't find any further info on what each of the .bin files might be.

Chances are that I just bricked my drive, and I'm just gonna have to own that and buy a new one at some point. My own fault for not following directions, but I figured I'd hop on and see if anything was possible.

So, if you skipped that step, then you now have a drive with no calibration data... It is possible to get a drive working again using another drive's calibration data. Here is a WH16NS40 1.02 dump that has not been cleaned, meaning it still has all the data intact. Use dosflash to write this firmware to the drive and hopefully it will start working again.

If it doesn't work, throw the drive in the bin and get a new one!

LG_WH16NS40_(NS40)_Original_1.02_Dump.zip

(1.16 MiB) Downloaded 531 times