www.makemkv.com

Try to load a WIN PE version, in order to see if it is an OS issue or not.

It is very strange that even after reflashing the whole eeprom you still have such issues.

Is the flash utility being run as an administrator? Most systems will not let you access the drive at that level while running as a "normal" user....

Tomorrow I'll be home to check my drive version firmware. Hope it's not 3.03. If it is I guess I'll have to go capture route..... If I have bad luck I'll try these tips and post my results. Fingers crossed.

@Teddy Raspin
No, it does not come from the operating system I bought a ASUS BW-16D1HT and it works perfectly.
It is the reader who is involved.

barrett70 wrote:@Teddy Raspin
No, it does not come from the operating system I bought a ASUS BW-16D1HT and it works perfectly.
It is the reader who is involved.

Ok, but it is very strange. The erase option of DOSFLASH (under pure DOS) totally erases the eeprom and if you write the 1.01 or 1.02 dump
it writes the entire 16 Mbit firmware file, thus the BH16NS55 must come back to its original state.

If it doesn't, then your unit is eventually 100% damaged, I can't find any other valid solution for such behaviour.

Here is the result with the ASUS:

Summary for drive G: (AnyDVD HD 8.2.1.7, BDPHash.bin 17-07-03)
ASUS BW-16D1HT 3.02
Drive (Hardware) Region: 0 (not set!)
Current profile: BD-ROM
Media is a Blu-ray disc.

Total size: 29233824 sectors (57097 MBytes)
Video Blu-ray label: THE_REVENANT
Media is AACS protected!
Drive supports bus encryption!
Disc wants bus encryption!
AACS MKB version 60
UHD Blu-ray disc.
Hash: 0x472D69A15AAB68BD1F114BA3344EF8D9E386A421
Removed AACS copy protection!
Bad sector protection not found.
It works perfectly.
I do not see how he got damaged I did not do anything special.
Anyway, thanks for your help.

At last you can dump (with the R option in DOSFLASH) the Asus firmware and flash it
on the BH16NS55 in order to totally reset any LG information inside it.
Maybe in this way it could work.

I have no other ideas in my mind.

It's a good idea this method I had not thought of it.
I'm trying.
thanks.

barrett70 wrote:It's a good idea this method I had not thought of it.
I'm trying.
thanks.

Hi, barrett70.
I hope you get success for this idea.
And if you get success, would you share the method ?

Hi, barrett70.
I purchased two drives,
buffalo bruhd-pu3 bu11 and lg bh16ns55 1.03.
Unfortunately two drives do not work.
Would you upload asus drive's full dump with calibraton data ?
I will try to flash this dump on my bh16ns55.

TeddyRaspin wrote:@barret70

...

10) This time press 'W' (without quotes) and enter, as filename, DUMP102.BIN and press enter.

...

How did you obtain the orginial dump file of version 1.02 (CRC32: 2A1CB2E0)?
I ask this question, because a dump made with Devilsclaw's LG Renesas Drive Utility (Flasher) shows a different CRC32 checksum: DB34765A

The Devilsclaw's flasher dumps the whole firmware except the header, which is needed to correctly
flash firmware. DOSFlash is the only tool which properly dumps the eeprom, including also header,
and this is the tool I've used to obtain the original dump of my BH16NS55.

TeddyRaspin wrote:The Devilsclaw's flasher dumps the whole firmware except the header, which is needed to correctly
flash firmware. DOSFlash is the only tool which properly dumps the eeprom, including also header,
and this is the tool I've used to obtain the original dump of my BH16NS55.

That makes sense, thank you very much for your quick reply.

What I still find interesting though is that the former dump with laser calibration data you posted in another forum is slightly different compared to this one. However, the header is identical in both files.

Drive Information
OS device name: K:
Manufacturer: ASUS
Product: BW-16D1HT
Revision: 3.00
Serial number: SIK9KH1LF281
Firmware date: 2115-11-03 11:10:
Bus encryption flags: 1F

Time to start ripping my uhd collection on 64 disks.....im very happy