Crossflashing patch

If your patched firmware is a flasher i. If your patched firmware is a raw binary firmware i. Method 2: Pre-Patched only when a pre-patched crossflashing firmware is available Download a crossflashing-patched firmware for the drive that you are flashing to from our firmware page.

After unpacking the RAR package, double-click on the firmware to start the flasher. Be sure to select the correct drive, and flash. Note: If a crossflashing-patched firmware is not available for download, please follow Method 1 instead the crossflashing-patched firmwares that we provide were created by simply following steps of Method 1. Note: For more information about the CGxx firmwares, click here. Make sure that you have version 3. After unpacking the RAR package, read the readme, and follow the instructions inside.

Unsupported crossflashes include S S, x51S 8x2S, and slimtype crossflashes you can still use one of the other three methods for these unsupported crossflashes. Updating to a Newer Firmware if using methods 1, 2, or 3 If, after crossflashing a drive, you wish to update to a newer firmware, you must follow one of the procedures listed above!

This is because, deep down inside, your S drive is still a S drive, and thus, any S firmware that you load onto your S--regardless of what firmware is currently loaded--must be patched!

Updating to a Newer Firmware if using method 4 Simply flash to the new firmware. No special steps are necessary. Undoing the Crossflash if using methods 1, 2, or 3 Simply flash your drive with the firmware for your drive's original model you may need to use FlashFix if you want to use an official flasher; most unofficial flashers, such as all of the ones found on this site, are already FlashFixed--once the crossflash is undone, FlashFixing will not necessary for any subsequent flashes.

Please consult the documentation for more details. Last edited by a moderator: Jul 26, Hi guys, New to the site, so first post.. My problem is this: My burner has been running perfectly since it's purchase a few months ago, but recently my dad has been using it to rip all of his cd's to mp3's because the CD read speed is faster than his CD Drive , and the other day the computer had a problem whilst doing so not sure specifically - but had to power off to recover.

Anyway, now the drive is running extremely slow, i. Not knowing too much about computer hardware, I figured trying to upgrade firmware might help it as long as there isn't physical damage, it should be fixable? I don't know.

But when I try to run the exe file in the zip, I get the following message: "No matched drive detected! Which is confusing. It then closes when I click OK. Any ideas? Is there some other driver available that I should try using? Also, does it sound like my drive itself has a problem? I don't really know too much, so any help would be appreciated.

Thanks for the advice. I've just written a couple of DVDs.. Thanks again, -Warren. TY shhhh, dont tell him Last edited by a moderator: Aug 1, Is this an OEM drive? LOL hahahaha.. I got the latest from Liteonit. It didn't want to update the BPSA firmware already in the drive. I think the problem is that the drive was provided by HP in one of their new Pavilion aa machines.

BIN , but keep reading. I tried a bunch, but what worked best for me was the UEFI version. I used the P19 version of the LSI sas2flash. USB drive , and:. Where ir. At first, I had issues getting this to work at all: the UEFI versions would detect the card and attempt to boot it, but fail. I was doing this on a consumer miniITX board, not the server, since the server takes ages to boot, but consumer hardware probably has a less reliable UEFI implementation.

Unfortunately, here I hit the first issue with flashing this Fujitsu card, which other people had also reported:. What is this Mfg Page 2? I have no idea. Why is it validating it? This sounds like an attempt to prevent crossflashing by making sure that e. So instead of trying to come up with a Rube-Goldberg solution as seems to be popular with these LSI cards, I threw sas2flash. It took 5 minutes to find the function responsible for the Mfg Page 2 message via string search and patch out the check.

Interestingly, sas2flash. With that patch, the flashing process completed successfully actually, I had to run it again after a reboot to get the BIOS flashed, probably due to the aforementioned UEFI issues.

Grab the patched sas2flash. Time to stick the card back into the server, plug the SFF connectors back in, and boot. Except… turns out the card only sees 3 drives.