Yep, I would recommend finding one of the two chips I mentioned and putting it on instead. I bet it would work. After the kext is extracted, it loads. Code inside the kext itself decides that it shouldn't succeed because of the chip ID. So if the kext has extracted itself I'm pretty sure your chip has good firmware on it, just it's failing the chip ID check.
The only problem is I believe CC_333 has discovered that the MX29LV040 chip doesn't work with the WiebeTech flasher, so you will probably need to use the DOS flasher (or a chip burner) to get the contents on there initially.
I'm experimenting with a few ideas for how to force the FirmTek flasher to recognize a card with blank or corrupt firmware on it.
Edit: Yep, it works! I force-quit the FirmTek updater in the middle of an update. It no longer loaded a driver or anything, so the firmware was corrupt.
If you save the two kexts in that cache folder, then manually load them with kextload:
sudo kextload -d ~/Desktop/Sil3112DeviceNub.kext ~/Desktop/FT_ATA_Sil3112.kext
Then the FirmTek updater will allow you to run and flash the card. But again, the chip has to be one of the chips that is allowed to be used by the driver.
The only problem is I believe CC_333 has discovered that the MX29LV040 chip doesn't work with the WiebeTech flasher, so you will probably need to use the DOS flasher (or a chip burner) to get the contents on there initially.
I'm experimenting with a few ideas for how to force the FirmTek flasher to recognize a card with blank or corrupt firmware on it.
Edit: Yep, it works! I force-quit the FirmTek updater in the middle of an update. It no longer loaded a driver or anything, so the firmware was corrupt.
If you save the two kexts in that cache folder, then manually load them with kextload:
sudo kextload -d ~/Desktop/Sil3112DeviceNub.kext ~/Desktop/FT_ATA_Sil3112.kext
Then the FirmTek updater will allow you to run and flash the card. But again, the chip has to be one of the chips that is allowed to be used by the driver.
