https://wiki.redump.info/index.php?action=history&feed=atom&title=User_talk%3AHeroponRikiBestest 2026-07-24T12:25:22Z Revision history for this page on the wiki MediaWiki 1.46.0 https://wiki.redump.info/index.php?title=User_talk:HeroponRikiBestest&diff=65401&oldid=prev 2025-01-21T18:33:11Z

<p>Created page with &quot;=== 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 th...&quot;</p> <p><b>New page</b></p><div>=== Hexalock AutoLock ===<br /> 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 <br /> [LBA: 7562] subcode desync (shift: -20)<br /> [LBA: 7582] subcode desync (shift: -40)<br /> [LBA: 7592] subcode desync (shift: -50)<br /> [LBA: 7681] subcode desync (shift: +0)<br /> [LBA: 7682] subcode desync (shift: -50)<br /> [LBA: 7683] subcode desync (shift: -51)<br /> or like<br /> [LBA: 7631] subcode desync (shift: +50)<br /> [LBA: 7632] subcode desync (shift: +0)<br /> [LBA: 7633] subcode desync (shift: -1)<br /> [LBA: 7634] subcode desync (shift: -2)<br /> [LBA: 7635] subcode desync (shift: -3)<br /> {etc}<br /> They can also be identified by ~120 MSF errors in the log, which look like<br /> CD-ROM [spaceBound.bin]:<br /> sectors count: 7682<br /> mode1 sectors: 7682<br /> MSF errors: 120<br /> 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 &quot;MSF errors: ~120&quot;, which isn&#039;t treated as an error for redump purposes anyways), ideally dumped twice to ensure matching hashes. If you&#039;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.</div>

>HeroponRikiBestest