www.makemkv.com

I'm officially throwing in the towel. I can't think of anything I haven't tried at this point, both intuitively and regarding everyone's suggestions. After Mike's reply, I used the following state as a starting point for each thing I tried: "Dirty" WH16 firmware from Marty (my calibration ...

Friendly bump

MartyMcNuts wrote: ↑

Sat Apr 03, 2021 9:28 am

This is amazing quest, please post your progress. I think that we might be able to recover your drive no matter what... Now that's downright inspiring...fk it, let's keep going. And to think I was about to purchase a new drive. Your first objective is to get rid of "BOOT" revision, i.e. f...

Welp, I think my drive might just be FUBAR...I've tried everything, both that I can think of and that everyone has suggested, and the drive still refuses to read anything. I copied the entire contents of my calibration data (1f0000.bin) over the last 64k of the file provided by Marty, one of the &qu...

rom_1f0000.bin is your calibration data. You need to replace the last 64K in a raw image (at offset 1f0000 naturally) with contents of this file and flash it with dosflash. In theory, it is possible to flash a working firmware using new method, and the use vendor commands to re-flash the calibratio...

I'm assuming since I'm dealing with raw binary images, the best (only?) way to do this would be in something like a hex editor (I've used HxD in the past)? Based on your language, neither sdftool nor dosflash have these capabilities; is there a specific tool you'd recommend? I think I might've figu...

rom_1f0000.bin is your calibration data. You need to replace the last 64K in a raw image (at offset 1f0000 naturally) with contents of this file and flash it with dosflash. In theory, it is possible to flash a working firmware using new method, and the use vendor commands to re-flash the calibratio...

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 firmwa...

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 dumba...

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...

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) us...

Billycar11 wrote: ↑

Fri Mar 26, 2021 3:24 am

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!

Billycar11 wrote: ↑

Fri Mar 26, 2021 2:28 am

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

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...