Thanks, there is also a fixed attribute that indicates if a module can be moved or not, which could be handy when deciding weather or not padding should be added and where. and finely, with the ASUS firmware I have noticed that I can add/remove modules without the "Security Verification Failed" problem I suspect that only signed modules are being verified, and not necessarily the whole firmware file, I wounder if there is a way to "un-sign" a module maybe a flag in a file header or something.
Structure: insert the SLP modules to the bios Dynamic: change the Pubk&Mark&RSDT/XSDT table names according to the .BIN selected.
Must have missed that module move flag...... where is it?? Edit: Found it - FFS_ATTRIB_FIXED Edi2: Just looked - almost all modules in all EFIs are flagged as fixed..... Thanks Andy
Hello guys! I have just bought a new HP-DV7 7003xx laptop with Insyde UEFI BIOS and when I looked at the BIOS, it presented only few options (95% was system information. I know HP seriously cripples their BIOS (UEFI). Does this excellent Phoenix-Insyde-Dell-EFI-BIOSes tool has the ability to unlock the locked hidden options of HP BIOSes? I am also aware of the View attachment 15431 option in Advanced, but does it pose any kinda danger of bricking the board (I have seen several modules being modified by tool with corrected checksum on a test run). Surely I don't want to ruin the brand new laptop, that's why I am in need of an advice. Has anyone tested it before on HP latest generation machines? Your guidance will be appreciated.
if you break the DWORD in to 2 words the first WORD points to the beginning of the actual image that is written to the chip @ 0x0800 and the second WORD points to the end of the second EFI_CERT_BLOCK_RSA_2048_SHA256 structure and the beginning of the unknown section before the 0xFF's start. @ 0x0458
Have modified the tool to look to see if individual modules (those with PE/PE32+ format) are signed - by checking 5th entry in descripter tables - Have scanned several EFIs - NO modules are signed (even in those BIOSes where we know modifying a module causes problems) Tool will also now look for ASUS capsules and see if they have a WIN_CERTIFICATE following. Andy
Thanks Andy, I have read that the capsule GUID defines the format of the file and may define extensions to the capsule header, the firmware for the ASUS P8Z77 WS contains "SecSMIFlash" and "SMIFlash" which is used by the EZFlash module. So I am currently looking for any hint of a capsule header GUID for an unsigned firmware and I am hopeful that replacing the signed capsule header with an unsigned one will allow the modified firmware to be flashed. EDIT: nope, this idea is a dead end.
Hello! Thanks for the help, it works. Tell me how you managed to do it and why I did not work? What tools and settings were used?
You need to insert special SLP modules in the bios/efi & then mod it. Only modding by andyp's tool doesn't work.
I'm stuck here as well. Mod success, but not visible. I viewed the nicely done video by conghoaxa1 (Thank you very much, by the way,) but I cannot find a SLIC setting in AMIBCP. The board is an ASUS M5A97. I may have to revert to an older version if it will let me. Edit: Might not matter for a while. Bricked my BIOS in another attempt. Oh well, the risk was known. Wanted to mention though, I was pretty happy with the US support from ASUS. They have a web page where you can order new chips. Mine wasn't listed though, I had to call in. Might be time to invest in a programmer anyway.