I Have an LG 16Ns55 that gives almost always this error in anydvd when inserting in it a UHD-BD:
Summary for drive G: (AnyDVD HD 8.2.7.3, BDPHash.bin 18-01-30)
ASUS BW-16D1HT 3.02
{...}
Does it have an LG Logo on the cover?
If yes It looks like a crossflashed LG drive to an Asus BW-16D1HT.
E.g. could be crossflashed (even from an UHD offcicial drive WH16NS60) converted to to Asus-BW16D1HT UHD-friendly.
The are people using the EEPROM data mover even for from a real-UHD-official drives, to do the converting, although Teddy Raspin does not at all mention to use this as alternative method here, eg- also from an BE16NU50/40 not sure, because it's more easy, than with the manual editing.
The reported it to work with DeUHD. But I can't remember anyone telling that it worked with AnyDVD before, before RedFox did that nice valu ignore-update.
What I've noticed when feeding the "EEPROM data mover" program with an original WH16NS60 backup dump, to export into laser CB-data and drv value into an BH16NS55 Clean- or BW16D1Ht clean-firmware, the data mover gets another resulting file, than using the manual hexediting method for this with "dd" or hexeditor.
I'm 100% sure I did correct manual hexediting. Rechecked the hex- and decimal values with calculator etc.
When using dtandard UHD-"friendly"-drive's ori firmware (eg updated BH16NS55 or Bw-16D1HT 1.03 or 3.03)and feed it with 1.02 / 3.02 Clean firmware, JUST here the resulting file on EEPROM data mover matches to the manual hexediting method.
---
(Even when using usual firmware-downgrade hexrange editing procedure on WH16NS60 firmware by "dd" or "hexedit", the output file on EEPROM data mover does not match)
As said before EEPROM data mover has strange behavior in some special occasions
Maybe the 1st ownder from "mfast"' 's drive used the "EEPROM" data mover which might not be optimal , so maybe it's better to directly convert the firmfare, and with Teddys' hexrange manually with "dd" or a "hexeditor".
If that's the case (WH16NS60 unit), so if the previous owner used the EEPROM data mover, that may cause of that earlier AnyDVD behaviour mfast experienced, more or less/ at least sufficiently resolved by AnyDVD now!
https://forum.redfox.bz/threads/converting-uhd-friendly-drive-into-uhd-real-and-viceversa.74544/
Here Teddy doesn't mention to use any "EEPROM data mover"(!) here!! only for a standard-UHD-friendly drive!!
There must be some reason...
(standard-UHD-friendly drive=standard-UHD-friendly drive with just updated firmware to close AACS loophole.)