I'm sorry I think there is a misunderstanding, I did not mean to imply that there is a bug in Phoenix tool, or that you are using any of the open source tools or code. the point I am trying to make is that since MMTool.exe sets the state field in the FFS header that it would also be desirable if Phoenix tool also set the state field. If an individual were developing a firmware module using the official build tools they would stop the build after GenFfs.exe completed and not continue to build a firmware volume using GenFv.exe if they then use Phoenix tool to add the module into the firmware without setting the state field to 0xF8 they would experience a brick.
Ahh... I get u I can certainly make the tool flag up any modules that don't have F8h and ask to correct. ANdy
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
Can you elaborate a bit? What modules could you add/remove and still pass the "Security Verification Failed" problem? Thanks!
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