by default people would download the latest (topmost) which is NE… I was trying your post and noticed that, what is NE anways?
should post the hint somewhere people can’t see (ie: don’t hide it in the spoiler) I didn’t follow your post to the letter, because I already had Uefitool installed from the past…
Maybe in the "My favorite UEFI BIOS modding tool is the “UEFITool”, " put "My favorite UEFI BIOS modding tool is the “UEFITool (don’t use NE for writing)”
@Kocoman : I have tried to put the appropriate words into the start post and hope, that it is ok for you.
That is a Alpha/Beta version of the UEFITool for BIOS modding experts/developers.
@Fernando { What data in the bios makes posible for 2 motherboard of the same chipset and socket, but diffrent manufactures display a verry diffrent bios navigation.
The circurt is diffrent, but the components should take the same voltage to run (if they are exactly the same).
If somthing small was diffrent across the boards like an audio chip, how could you look at a bios and and view the difrence in operation, on a hexy view. how could you pin point that out
@Nickperry420 Welcome to the Win-RAID Forum!
This is the thread just about the procedure, if you want to extract, insert or replace a certain EFI BIOS module.
All other BIOS modding requests should be posted within the "BIOS Modding Requests" Sub-Forum. There you have the best chances to get help from a Forum member, who knows much more about BIOS modding options than me.
Good luck!
Dieter (alias Fernando)
Good morning
I would like to know if it was possible to replace the “setup” module of a bios by that of another bios.
@francky88
You can replace each BIOS module, but it is not easy to predict what will happen after having flashed the modded BIOS.
What is the reason for your request and from which BIOS would you take the module?
I have a rampage iv extreme and on the rampage iv extreme black edition version, in the control fan menu, there is the possibility to control the fans independently "chassis q-fan1, chassis q-fan2 and chassis q-fan3 " . in the extreme version, all 3 are managed at the same time. these 2 cards are almost identical except for a few small improvements such as the TPM, audio chip. Using UEFITOOL, I replaced in the “setup” section the “PE32 image section” successfully. but now, AMIBCP4.53 does not want to open it so I think the modified bios will not work.
You might also replace the FE612B72-203C-47B1-8560-… to get AMIBCP working.
But modules replacement is not always an option. BIOS of black edition may have different var. stores size and functions mapping. Eg fan control will be responsible for virtualization and vice versa.
which I need to replace the “PE32 image” or “setupdata”.
GUID pattern “fe612b72-…-…-…-…” found as “722B61FEC644242885C6442429606689” in AMITSE/…/PE32 image section at header-offset 3A752h
GUID pattern “fe612b72-…-…-…-…” found as “722B61FE3C20B1478560A66D946EB371” in AMITSE/…/setupdata at header-offset 04h
I suddenly replaced the 2 by trying to open it with “AMIBCP” but still impossible to open the bios.
@francky88
It seems to me, that your specific problem has not much to do with the topic of this thread.
If you want, I will split it and put all contributions regarding your request into a separate thread. Which topic title would you like?
1 Like
I was going to just give it a shot in a few different ways this weekend but I may as well ask first.
Dell precision bios with a c612 chipset. I would like to add 2 dxe drivers from a similar supermicro board. Both boards have the drivers in the same guid and for the most part contain the same drivers. First of all. Can I implement these into the Dell ? If so would I add them to the end of the dxe driver list similar to adding rebar support? Or since both bios share mostly the same drivers I could install them into the new list in the same place the appear on the supermicro bios.
@frankr2994
Since your main questions have been already answered within the first post of this thread, I have moved your request here.
Generally I do not recommend to insert a complete DXE driver module, which has been taken from a BIOS of another manufacturer as *.ffs file (with GUID header), into a Dell BIOS. The chances are high, that the modded BIOS will either not be accepted (better option) or not work (worst option).
Before you start with the extraction of the “DXE Drivers” from the Supermicro BIOS, I recommend to check
a) the GUID header of them (first 8 bytes should match your Dell BIOS) and
a) their content and fuction (more than 1 DXE driver with the same function within a BIOS may induce problems).
Question: What is the sense of your project? Which benefit do you expect by doing that? Is it worth despite all the risks of a bricked Dell system?
Good luck!
Ive bricked my bios 3 dozen times last couple years. I don’t care about recovery lol.
So the purpose is to add a XTU dxe driver and a cpuPerfTune dxe driver. I have unlocked the bios to the point where windows XTU can change clock speed and voltage. XTU will not write any settings back to nvram andI have no access to ICC overclocking. Any attempts to modify ME using Intel FIT result in hard brick.
So I’m hoping to fully integrate XTU at which point the software should show icc overclocking, all available voltage adjustments and be able to write back and save to nvram.
Real purpose is just to do this. I like playing with bios mods and that’s about it.
You’re adding a DXE driver to a bios, used on EFI/PEI initialization only, that has no instructions/calls to load it and ICC is fused on PCH.
My pov only… but i doubt that will gain any access to ICC OC options.
Anyway, good luck.
Icc overclocking is a 98 percent chance of failure. There is only a standard profile in ME with frequency locked down to 99.8mhz.
Regardless I have a copy of the XTU development kit and it’s looking for the SMI address. Supposedly the interrupt address is provided through device int 3394 which is the XTU driver for the bios.
If you or anyone else has any ideas on modifying ME to create an icc overclocking profile without bricking the board automatically let me know and I’ll make a new thread.
@Fernando
I followed your guide to insert @Kuri0 's ReBarDxe.ffs in my bios, dump but I am getting the pad file corruption issue. There are 3 pad files in the DXE volume and there’s also a module “volume free space”. Firstly, I tried the simplest method using the UEFITool but it removed one pad file completely and altered the size of another pad file. Next, I used MMTool but it not only changed the pad file size but also the contents and location, interestingly the “volume free space” also expanded when I used MMTool to mod the bios. In the third method i used HxD Hex Editor to manually insert the ffs file into the dump, the file was 0xA12 in size but I added 6 bytes of 1s after the ffs module to make it 8 byte aligned and then removed 0xA18 bytes of 1s from the “volume free space”. This time, all the pad files are okay, there is a reduction of 0xA18 bytes from “volume free space” but I get a different error: “FfsParser::parseFileHeader: unaligned file” for two files in DXE volume, I checked in HxD they look aligned to me. Is there anything to make it work or am I missing something? Any help will be appreciated.
P. S. pictures of comparison attached
Comparision.zip (632.3 KB)
@Ahmad_Salal
Welcome to the Win-Raid Forum!
As the thread title indicates, this thread is just about the usage of the UEFITool, because this tool - contrary to AMI’s Aptio IV/V MMTool versions - is
a) free available for all users and
b) works with all AMI Aptio IV/V UEFI BIOSes.
You can find a Guide about the usage of the AMI Aptio IV MMTool v4.50.0023 within the start post of >this< thread (Step 2 of the Chapter “This is what you should do:”), but the related thread has nothing to do with your specific problem.
To be able to help you, you should
a) give us information about your in-use mainboard (manufacturer/model) and
b) attach the original BIOS file (or link to it).
Good luck!
Dieter (alias Fernando)