12-22-2014, 04:43 PM
I'm trying to mod the Insyde bios in my Y50-70 4k (remove white list, custom splash screen, enable hidden menus) but am having some trouble. I am using a combination of Andy's SLIC tool, IDA Pro, and a hex editor to do my hacks and build the rom, but this is my time so I'm not sure if I'm doing something wrong.
Anyway, when I try to flash using Windows tool (iscflash), it reboots into InsydeH2O and gives a 'Secure Flash/Invalid Firmware' error and doesn't flash. For the time being, I'm only trying to remove the white list, which only changes 2 bytes in the entire rom.
I've tried building the rom both using a backup image and using the downloaded update which didn't make a difference. I admit I'm a little confused about which one I should use and how I should flash it.
One thing I noticed is the backup image is exactly 64Mbits, while the downloaded update image is a bit longer. I opened the update in a hex editor to investigate and see the actual rom is prefaced with an executable ('MZ' are first 2 bytes, follow by a few k of machine code and string tables) and followed by what appears to be a cryptographic signature (I see the text 'Trust - Lenovo Certificate' and a bunch of seemingly random bytes). When I opened this image in the SLIC tool, I didn't receive a notice about encryption. Is it possible the built in update utility is verifying a signature before flashing?
I know other people were able to flash their Y50-70's without issue, so maybe I'm doing something wrong. My concern though is that since this is the newer 4k model, Lenovo may have subsequently locked down the updater. I am willing to pull the flash IC and program on the bench if needed, but obviously would rather not. Any suggestions on what I should do from here?
Thanks!
Anyway, when I try to flash using Windows tool (iscflash), it reboots into InsydeH2O and gives a 'Secure Flash/Invalid Firmware' error and doesn't flash. For the time being, I'm only trying to remove the white list, which only changes 2 bytes in the entire rom.
I've tried building the rom both using a backup image and using the downloaded update which didn't make a difference. I admit I'm a little confused about which one I should use and how I should flash it.
One thing I noticed is the backup image is exactly 64Mbits, while the downloaded update image is a bit longer. I opened the update in a hex editor to investigate and see the actual rom is prefaced with an executable ('MZ' are first 2 bytes, follow by a few k of machine code and string tables) and followed by what appears to be a cryptographic signature (I see the text 'Trust - Lenovo Certificate' and a bunch of seemingly random bytes). When I opened this image in the SLIC tool, I didn't receive a notice about encryption. Is it possible the built in update utility is verifying a signature before flashing?
I know other people were able to flash their Y50-70's without issue, so maybe I'm doing something wrong. My concern though is that since this is the newer 4k model, Lenovo may have subsequently locked down the updater. I am willing to pull the flash IC and program on the bench if needed, but obviously would rather not. Any suggestions on what I should do from here?
Thanks!