User talk:HeroponRikiBestest

From Redump Wiki

Hexalock AutoLock

If a Hexalock AutoLockdisc does not have protection info provided, it will be identifiable from redumper logs by a +50 subcode desync near the end of the disc like

[LBA:   7562] subcode desync (shift: -20)
[LBA:   7582] subcode desync (shift: -40)
[LBA:   7592] subcode desync (shift: -50)
[LBA:   7681] subcode desync (shift: +0)
[LBA:   7682] subcode desync (shift: -50)
[LBA:   7683] subcode desync (shift: -51)

or like

[LBA:   7631] subcode desync (shift: +50)
[LBA:   7632] subcode desync (shift: +0)
[LBA:   7633] subcode desync (shift: -1)
[LBA:   7634] subcode desync (shift: -2)
[LBA:   7635] subcode desync (shift: -3)
{etc}

They can also be identified by ~120 MSF errors in the log, which look like

CD-ROM [spaceBound.bin]:
  sectors count: 7682
  mode1 sectors: 7682
  MSF errors: 120

Hexalock Autolock discs are only accepted via dumps made on a JB8 ASUS/LG drive cross-flashed with ribshark firmware, and with 0 read errors or ECC/EDC errors (aside from "MSF errors: ~120", which isn't treated as an error for redump purposes anyways), ideally dumped twice to ensure matching hashes. If you're unsure if the dumper is using ribshark firmware, this is technically a redundant check, as the only purpose of the ribshark firmware in this case is to allow the drive to read to the end without errors in the first place.