10-05-2012, 01:15 PM
Well, it seems that I'm not playing a Columbus here as the method apparently has been described by Ryan HERE
But .. again arises the mighty 'but'... he bricked his machine and possible corrupted the boot block those he was unable to reflash. According to a post from MDL the BIOS.cap has to be extracted using 7z from the OEM updater. But ... (again) the F33 part of the firmware he is referring to is identical in size to FvRecovery.fd file found in winflash's temp folder ? Shouldn't it have been used ? (I only assume that because it's called Recovery for a reason lol ... )
Anyway, I'm rambling here .. I got my hands on a Insyde bios rom from a Toshiba laptop that initiates the boot block with Fn+F ... the CdExpress module also has BIOS.cap string in the module, but the name of the recovery file the person reported working was based of off the platform model ..
But .. again arises the mighty 'but'... he bricked his machine and possible corrupted the boot block those he was unable to reflash. According to a post from MDL the BIOS.cap has to be extracted using 7z from the OEM updater. But ... (again) the F33 part of the firmware he is referring to is identical in size to FvRecovery.fd file found in winflash's temp folder ? Shouldn't it have been used ? (I only assume that because it's called Recovery for a reason lol ... )
Anyway, I'm rambling here .. I got my hands on a Insyde bios rom from a Toshiba laptop that initiates the boot block with Fn+F ... the CdExpress module also has BIOS.cap string in the module, but the name of the recovery file the person reported working was based of off the platform model ..