[mattjackson]

All somebody sent me some logs:

The drive initially identified as BDR-S11JX 1.54.
User selected a BDR-209M 1.54 package with a different hardware family ID. Flash and Recovery both blocked it without writing anything.

This is correct. Wrong family, wont flash. No bug.


User then enabled Bypass compatibility checks and forced that package onto the drive. The write completed, and Kernel and Normal contents verified successfully.

Just because and it flashed doesn't mean it works. If you are using Bypass it indicates a problem and all safety is off the table people!!!


Now identifying as 209M, the drive accepted S12JX 1.03 because that package matched the hardware family of the firmware user had forced onto it. That check could no longer establish compatibility with the original physical hardware. User subsequently reported that the tray would not open.

Not a surprise, this hardware and this firmware should not be together.


User selected the previous S11JX firmware to return. The family check blocked that transition too, so user used bypass again. Restoration completed, with Kernel and Normal verified. The reports do not confirm whether tray operation returned.

This time bypass was "correct" to use as it was forced into the wrong family and you had to force it back.


My summary here: Glad you didn't brick it, but I can not help you if you use bypass. You are acknowledging you are forcing a firmware onto a drive it shouldn't run on. If you did it and knew what you were doing, great. If you were unclear and think my app needs to be made clearer please let me know.


UD02 has been confirmed to read UHD.
1959 drives are capable of firmware modification to enable UHD
1939 drives are being looked into, 50/50 right now