Dear BIOS-Mods.com community, BIOS-Mods.com for years has been and continues to be an open, collaborative space to help users around the world make the most of their motherboards, hardware platforms, and computers as a whole. Over the years we have had many talented developers come and go who have all left tremendous impacts on our ability to modif...
In case you didn’t already know, the Extensible Firmware Infrastructure’s Human Interface Infrastructure uses Internal Forms Representation protocol to display things like your setup utility’s menu. By having access to the Internal Forms Representation, we can know everything about a menu which can assist us immensely when modding bios. I’ll also be using this application in a few of the tutorials I write, so get used to using it now
I was getting tired of all the requests to expand EFI IFR Dumper to include support for UEFI’S IFR protocol, and as a result I decided that now is a better time than any to update my program. So here’s Universal IFR Extractor, the successor to EFI IFR Dumper. Designed to easily extract and convert the Internal Forms Representation used in EFI modules into a human readable format. Now supports both EFI and UEFI IFR protocols, so it should work with all cases
In additional, Universal IFR Extractor now has a graphics user interface to make it easier to use. It’ll quickly tell you what protocol a selected module uses so that you’ll be able to know what protocol format you should know in order to modify the forms. Intel has great documentation on how EFI and UEFI IFR is formatted, so it should be too hard to start modifying it after reading through those. I’ll also create a tutorial on how to preform simple modifications, like how to unsuppress hidden options, so stay tuned. Hope you all enjoy! Download it here
I first started working on Module Helper back in September when Andy’s tool V2.19 was released. As some of you may know, that iteration altered the format of the extracted EFI modules by storing a module’s header, code, and name all in the same file. This created some issues with disassemblers not being able to automatically recognizing the format of the EFI modules and the size of data modules not being updated if changed. Dealing with all these negative aspects was trivial but annoying, which is why Module Helper was developed. It was originally capable of splitting the modules header and data into separate files an it could update the sizes in the headers. It also had a renaming feature that would make locating certain modules easier. I only made this program only for Linux, but I had always planned to port it over to Windows before releasing it.
However, Andy’s tool V2.50 was recently released, and it has switched back to using the earlier format for the extracted modules. This event made Module Helper obsolete, but by this time I had gotten used to how it would rename functionality. I didn’t want to lose this convince, so I changed it a little to work with the latest version of Andy’s tool.
BIOS-Mods.com for years has been and continues to be an open, collaborative space to help users around the world make the most of their motherboards, hardware platforms, and computers as a whole. Over the years we have had many talented developers come and go who have all left tremendous impacts on our ability to modify BIOS images and provide the know how for people who like “Do it Yourself” projects.
We would like to start an open-knowledge initiative to help recruit and train new moderators at BIOS-Mods.com With the wealth of information there is to be shared, we are looking for several interested enthusiasts who want to learn more about the process behind BIOS modifications and who are willing to learn with the rest of us. BIOS modifications are an evolving process, and as UEFI continues to gain market share the techniques must also evolve to make the most of the new emerging technologies.
Starting in May, we would like to refresh our tutorials section by making available many of our BIOS modification methods that we use regularly on the site but have not been publicly documented. We hope by sharing new information with the community we can encourage users to become more involved in the process so that we can meet the rising demand of BIOS modification requests.
This article documents the exciting work being done by some of our top contributers in our forum. The modifications performed on systems like the Dell 15z reflect the most advanced examples of BIOS modifications done within our community. For more information, please visit the thread.
Phoenix SecureCore Tiano, used by Dell, is a tough nut to crack – we came to what we have today by taking little steps on a road that wasn’t smooth to begin with. Phoenix nor Dell have provided any information regarding SCT 2.0 and to this day the BIOS on these machines has not been upgraded to 2.3.1 which allows for ME v8 (brings IVB CPU support) and SecureBoot capabilities.
The number one utility in all of our research is without a doubt AndyP’s Tool, which can be found here. Huge props to him – without his tool our work wouldn’t be possible. Please note, that for some reason later versions of this tool such as 2.11 don’t seem to unpack the BIOS.wph’s capsule properly, so use versions prior to that if you are going to attempt doing some *magic* on your own. There have been a new Phoenix Tool release v2.12 but I have yet to try it, I personally still use 2.02 and it has been producing stable and working output.
The BIOS chip structure is the following:
Platform: Intel(R) HM67 Express Chipset
— Flash Devices —
Size: 4096KB (32768Kb)
00000000h – 00000FFFh: Flash Descriptor Region