Hello, Using v2.04 or earlier versions would produce BIOS files with identical binary contents. Version 2.05 or later like v2.11 would produce BIOS files with another identical binary contents but the binary contents are different from v2.04 or earlier versions. MMTool of course have no issue to load both images with different binary contents. I used to mod the BIOS for my mainboard using v2.04 or earlier. I still have no idea whether v2.11 would work because I haven't tested it yet. My question is : Which version to opt?
Hi andyp and all, First of all I want to thank andyp for all the great tools he created and shared. I recently updated my BIOS from Award to AMI UEFI, used Phoenix tool to insert GIGABYTE SLIC 2.1 with module method. The tool reported that SLIC added successfully. After flashing the bios, windows 7 crashes with BSOD on startup, but boots in to safe mode without problems. I have windows 8 on my pc as well and it has no problems to boot and works fine. From the described above I suspect that windows 7 crashes at the point when it tries to verify the license, because it is not validating the license in safe mode. When I tried modding with SSV2 method, I got “Unable to add SLIC code” error message. -Manufacturer: GIGABYTE -Motherboard Model: GA-Z68X-UD4-B3 -Bios revision: U1c -Bios Type: AMI UEFI -RW Everything Report: If you’d be so kind, please look at this issue and advise me how to mod my bios, so it will work properly.
Hey, Andy! I know you are busy, but I will think it's worth reporting. Dell's Phoenix SecureCore Tiano BIOS is packaged the following way: - BIOS1.WPH which is used to flash from WinFlash consists of RAW capsule and a PFlash.efi rom as well as a padding layer. - The RAW capsule has to be decompressed by PhoenixTool again to reveal all the modules of the actual BIOS. The problem is that after I select Dell as a manufacturer and in Advanced set 'No SLIC' and 'Allow user to modify other modules' in PhoenixTool 2.11 after pressing Go it says 'Invalid Firmware Volumen Header' when altering the "second stage" of BIOS1.WPH capsule (ie the RAW part of it). If however I try it with version 2.02 it works perfectly. Then just out of curiosity I tried recompressing the RAW part with v2.02 and compressing back to BIOS1.WPH using 2.11 and it didn't give any errors. BIOS version is not important .. it happens with every version I've tried. But v2.02 works perfectly fine.
First off, thank you andyp for providing a really great tool! It is really amazing work! I have been playing around with these utilities (my computer is a dell optiplex 980, bios revision A09). I have a few questions (thank you everyone in advance for any information or pointers for me to look at that are provided): 1) is possible to obtain the same compression ratio when compressing one of the decompressed ROM files in the dump folder? So that an unmodified ROM that I compress using lzss-r.exe (for example) will be the same as the compressed version I pull out of the HDR? 2) If it is not possible with the utilities we have, could someone provide some advice on what I would need to do do to achieve this? (I would share with the community if I can get it working) 3) How can I tell what utility to use to compress these files? 4) What is the "manual PBE method", related to ssv2? JF