Even though LiteOn’s latest and greatest BD writer family seems to have disappeared – taking the clones of the drive with it – there are undoubtedly still going to be some people lucky enough to find an HP, Optiarc/Sony, TEAC, ASUS, or Plextor that happens to be a rebadge of an iHBS112, iHBS212, or iHBS312. And maybe LiteOn’s firmware is more up-to-date than whatever HP/Sony/Optiarc/TEAC/ASUS/Plextor provide. (Or you just want to try out the different firmware).
Before we continue: make sure you’re using a LiteOn iHBSx12 clone! (no ASUS-branded LG drives allowed here)
Since the process isn’t straightforward, it might be best that we collect a bit of the knowledge we have so anyone who wants to crossflash can narrow their search down to one thread. This can be considered a How-To, or a FAQ thread.
Topics we will coverâ€¦[ol]
[li]backing up your drive
[/li]Your drive has firmware, and your drive has important calibration data stored in an EEPROM. You will want to back both the firmware and the EEPROM up before doing anything important. How will you do that? Well…we’ll talk about that soon enough.
[li]flashingâ€¦using extracted firmware
[/li]There may be something preventing you from using the LiteOn firmware update tool on your drive without some workaround or modification. (Trying to flash results in your drive not being detected by the flasher, even though every other piece of software sees your drive like normal).
[/li]Once you get the new firmware on your drive, the drive may blink at you. Nonstop. And refuse to work. You’ll see the drive, and you’ll be able to flash firmware to it, but they won’t see your discs while the light keeps blinking. So…yeah. We’ll talk about that, too. (But you’ll have to have a backup of your EEPROM first).
[li]using your drive!
[/li]Different firmware brands support scanning in different applications.
[/li]binary firmware files you can use to flash
[/li]I feel it only right to let you know: there are no firmware modifications available. What you get is what you get; the firmware is locked up with a checksum, and no tools exist to get around this limitation. There may also be a bit of encryption or scrambling within the firmware, preventing you from even analyzing media tables properly.
Note that tools mentioned are for Windows only. Figuring out how to run the tools in OS X or Linux is up to you.