Afaik SamurilH did a testmod crossflashing with his WH16NS60 (offcial UHD drive) to e.g. an Asus BW16D1HT 3.02 firmware earlier to get it friendly. But afaik he had modded bit otherwise than described in Teddy's guides:
Before he had tested with LG/Asus utility, taking Asus BW-16D1HT firmware for crossflashing his LG WH16NS60 official to UHD-friendly, it went fine for UHD-friendly (ripping etc) afaik,
but there was trouble with burning (with the Asus friendly firmware).
So he did a special mod, which the patched LG/utility wouldn't flash, which requires risky Dosflash
(having a full original-firmware-safety-backup-dump from Dosflash (in READ-Mode ONLY!) earlier, once having the unit bought and first at hand in the beginning!)
Short story:
SamurilH special UHD-official to UHD friendly mod:
Encryption data from source drive's original firmware (WH16NS60) exported into target-firmware (Asus BW16D1HT 3.02 firmware-dump)
Laser calibration data, NOT EXPORTED from source drive's firmware to target-firmware. (target's firmware its CB data left unchanged in the target firmware)
(Asus BW16D1HT 3.02 firmware-dump instead Clean-fw taken for editing, because a Clean-FW, DOES NOT include any laser-CB-data, as SamurilH intended to copy ONLY the source's drive signature in the target-firmware.
The LG/ASUS patched utility wouldn't write the part of the CB-data + encryption signature (so his editings also not flashed along)
So risky Dosflashing that into unit's EEPROM (overwriting whole EEPROM),
----------------------------------------------------------------------------------------------------------------
Teddy's guide: "Converting UHD official drive to UHD-friendly and vice versa":
https://forum.redfox.bz/threads/converting-uhd-friendly-drive-into-uhd-real-and-viceversa.74544/
Encryption data from source drive's original firmware (WH16NS60) exported into target-firmware (into an Asus BW16D1HT 3.02 Clean-firmware)
Laser calibration data, EXPORTED AS WELL from source drive to target-firmware)
in Teddies guide: target firmware = "Clean"-firmware
Risky Dosflashing that into unit's EEPROM (overwriting whole EEPROM)
--
Principially (target-firmware file for editing, might also be firmware-dump instead of a clean-firmware, because both the laser-CB-data and the encryption signature from source-drive's firmware-file are move into target-fw-file)
--
The LG/Asus patched utility leave the original source-firmware's CB+encryption signature unchanged in the drive's EEPROM.
(seen from this angle: Teddies conversion guide method is needless anyway with the new safer method)
LG/Asus patched utility works getting WH16NS60 UHD-official friendly, crossflashing to Asus BW-16D1HT 3.02 but has trouble burning.
LG/Asus patched utility works getting WH16NS60 official friendly, crossflashing to LG B/WH16NS55 1.02 (and probably lower) + with full burning capabilities.
But all methods, neither Teddies conversion guide, nor the patched LG/Asus utility nor SamurilH's mod can make an UHD-friendly-drive (or UHD Friendly-drive with UHD Un-Friendly firmware) to UHD-official, tested NOT working from Mike
and SamurilH reported that there was more to the WH16NS60, probably due to the a new -AACS 2.x crypto-chip existing in the WH16NS60
(But other way round it principially was tested working, to convert an LG WH16NS60 official to UHD-friendly)
-------------------------------------------------------------------------------
But SamurilH's special mod is very complicated, hexediting and might require also dangerous Dosflash. And SamurilH special mod afaik isn't mentioned in any guides, afaik at least not by Teddy.
And read about somewhere here also, it/s.th. else wouldn't work at all getting WH160NS60 frineldy, and s.th. already tested unsuccessfully by experienced Mike. But maybe I misunderstood that a bit.
Me myself don't have trust in myself in trying SamurilH's mod out. Especially wouldn't without backup-dump. If were even thinking of using "Dosflash" and that modding, I strongly recommend to use Dosflashing only for dumping (reading original firmware/currently updated working firmware).
If attemtping such special mod it is mandatory to have original firmware backup dump first, because the essential specific original area not to be touched normally , the safe LG/Asus firmware flasher protect, is modified in SamurilH's special mod, and can only be flashed with risky Dosflash!
And flashing any kind of "Clean firmware" is only for patched LG/Asus utility, NOT for Dosflash (=bricked unit without working backup dump!!)
I'm not 100% certain, SamurilH knows better.
[Edit]
https://forum.redfox.bz/threads/dum...hd-friendly-devices.74479/page-34#post-499743
He used the safe method to cross flash... The same method I was testing. To be very clear here, I was only testing things because testiles was having issues with his ns60 cross flashed to Asus 3.02 using the safe windows flasher. He fried about 4 bd-r's after flashing it so he asked me if I could test with mine to see what results I got. Normally I keep mine on ns60 1.00. Anyway when I flashed mine using the windows flasher and tried to burn a verbatim bd-re 25 it fried the disc to the point I couldn't recover it. Flashing back to ns60 1.00 allowed me to burn the same image to the next disc in the spindle.
Now my curiosity got the better of me because I had used the dosflash method originally to downgrade the ns60 so I still have a USB stick to flash that method. I took my original extracted firmware that came with the drive, and manually moved the encryption data to an Asus 3.02 firmware that I extracted from my Asus drive. The end result is a firmware that matched my Asus drive except for the encryption data. Using dosflash I flashed that to the ns60 and tested another burn. No issues at all.
I feel like using the calibration data from the ns60 with the Asus firmware is what caused the burn to fail. Once I used the Asus calibration data the burn was successful. Testiles ultimately used s different LG firmware to make the drive uhd friendly for anydvd and has been able to burn fine with that.
Short version... Cross flashing using the patched windows flasher caused burn failures for two of us. Dosflashing the Asus calibration data while cross flashing worked for me. Cross flashing to another LG firmware worked for testiles using the patched windows flasher.
(Taking patched flasher for crossflashing WH16NS60 to Asus firmware, I assume with or without out SamurilH mod, causes burn failures, UHD-friendly might have worked at least.
And the patched LG/Assu flasher won't flash the specially hybrid-modded-part from SamurilH anyway, as they don't touch the area-part in the firmware, in which SamurilH did his special mod to regain full burning capabilites, he took Dosflash to flash his mod, but only there, and only having full original backup dump of original units' firmware made first, otherwise all lost unit bricked
)
--
Also to get a WH16NS60 official friendly, afaik WH16NS60 1.00 firmware is already UHD-friendly. But I'm not 100% sure. Just read that from somewhere from s.o, who might be wrong. Anyway the patched Asus/LG flashers are the way to go.
The "mk-firmware-pack-20190319" by Mike e.g. includes firmware "HL-DT-ST-BD-RE_WH16NS60-1.01-NM00100-211711202000.bin" in the WH16NS60 folder. Is this friendly/made friendly or "only" downgrade-enabled?
---
Keep in mind, also Mike's 3.10 Asus firmware blocks Dosflash access generally. So you will no longer be able to make backup-safety dump from your unit's firmware! Afaik it is still downgrade-enabled with the safe method (patched LG Asus utility) with a specially downgrade-enabled "Clean"-firmware from Mike's "mk-firmware-pack-20190319"; or "(Modified_new_fixes)
ASUS ODD FW Changer + UHD Friendly Firmwares.zip / LG_Downgrade_Enabled_Firmware.zip" / Downgrade Enabled Firmware.zip w(ith the "DE_flash_HL-DT-ST_BD-RE_BH16NS55_1.02.bin") etc.
Aftern downgrading with that lower version (with patched LG Asus utility) you get Dosflash-acess back generally (tested myself) (only for dumping Read-Out firmware, recommended,NOT flashing!!"
(Just as a tip/(sitenote) in case s.o. wants to try out SamurilH's mod on WH16NS60 to friendly Asus-firmware together + with full burning capabilites (like with the BH16NS55 /BH16NS40_(NS50-compatible firmwares), and needs backup safety dump!) but was having a blocked firmware with e.g. also a newer stock firmware, to do that).
(+Would need to find a good guide how to do SamurilH's special stuff.)
If HL-DT-ST-BD-RE_WH16NS60-1.01-NM00100-211711202000.bin already has UHD has that, it is all much easier.
Or just take the Asus BW16D1HT 3.10 mk firmware for crossflashing BW16NS60 friedly (not sure about burning issues, because it will take the CB-data from the source firmware which afaik made burning issues on WH16NS60 (in this case) crossflashed to other model-number line)