Dunno what I am doing wrong, but on my ASUS Z77 board I still get the message :"Security verification failed." when I try to flash it.
Try ticking "Don't alter any ACPI tables" and unticking "Replace all OEM/Table ID occurences" in advanced options Andy
Nope, any alteration to the cap image will lead to that message. Anyway many thanks to the new tool, I love the speed boost! A small bug in module manpullation, if I insert one module, old image will be renamed to .old, on second module, old image will be renamed .old.old and new image will be .old Yeah, I was hopping that the new tool will sign it back, and I wont have to use flashback or external tool. Maybe next version
HI, maybe like this,if tools detect asus recover bios file name is xx.cap, tick"Don't alter any ACPI tables" and unticking "Replace all OEM/Table ID occurences" by default setting
AMIBCP Ver4.53 can do only change the default value and do NOTHING about SLP and SLIC. Only OEM official tool and Andy tool can add SLP and SLIC into UEFI-bios. Someone say enable SLIC by AMI BCP and use Andy Tool add SLP and SLIC as other manufacturer. I find that it doesn't work and NO SLIC (tested by me in MSI H61M-P31) Pls note. Regards nel1156
Dear, I dont understand what you are talking about. i asking for H61M-P20 bios. You are talking about Z77? Please explain. Regards Manu
Whenever a module is replaced/inserted MMtool will set byte 0x17 (EFI_FFS_FILE_STATE) to 0xF8 replicating this may prevent a few bricks.
GenFfs.exe sets the file state field to Code: FfsFileHeader.State = EFI_FILE_HEADER_CONSTRUCTION | EFI_FILE_HEADER_VALID | EFI_FILE_DATA_VALID; on line 869 of GenFfs.c which is 0x07 it could be set to 0xF8 when GenFv.exe is used, I haven't dug that deep into it yet. EDIT: found it in GenFvInternalLib.c line 381 Code: VOID UpdateFfsFileState ( IN EFI_FFS_FILE_HEADER *FfsFile, IN EFI_FIRMWARE_VOLUME_HEADER *FvHeader ) /*++ Routine Description: This function changes the FFS file attributes based on the erase polarity of the FV. Update the reserved bits of State to EFI_FVB2_ERASE_POLARITY. Arguments: FfsFile File header. FvHeader FV header. Returns: None --*/ { if (FvHeader->Attributes & EFI_FVB2_ERASE_POLARITY) { FfsFile->State = (UINT8)~(FfsFile->State); // FfsFile->State |= ~(UINT8) EFI_FILE_ALL_STATE_BITS; } }
chose no. only modify 3 modul acpi 16D0A23E-C09C-407D-A14A-AD058FDD0CA1_1_189.ROM (RSDT, XSDT) 69009842-63F2-43DB-964B-EFAD1C39EC85_0_312.ROM (maker) 996AA1E0-1E8C-4F36-B519-A170A206FC14_0_314.ROM (Pubkey) (manufacturer: chose other, no select Msi) ---------- It's guide H61M-P20.
Thanks. The tool doesn't use any of the sample EFI code, it is all custom written in vb.net. I actually figured out the headers/modules by hand before the EFI docs (as the old Insyde BIOSes were effectively a subset of EFI). The only EFI code I use is the compress/decompress sample code with a few lines added for DLL Andy