Page 3 of 31
#31 RE: [Guide] Manual AMI UEFI BIOS Modding by rootuser123 08.06.2015 11:14

I tried to use MMTool 4.5 but I can't find the Module that specifies the 3D-BIOS when I was opening BIOS F14.

EDIT by Fernando: Unneeded fully quoted text removed (to save space)

#32 RE: [Guide] Manual AMI UEFI BIOS Modding by lordkag 09.06.2015 23:52

avatar

Your 3D GUI is in the attached file. You have the GUID of images location and also an offset in that specific GUID. The problem is that Gigabyte is using a header for each image, that stores info related to its properties or placement in GUI, so any image change will have to be reflected in that header. You said you just want to port this GUI, so this problem is out. But the new file is changed, images are stripped, the GUID is different. Even if you insert the old GUIDs, the menu won't change, since it is likely that there is nothing in the BIOS code that will try to use them.

However, if you have Dual BIOS, you can try to insert these old GUIDs and see if the menu is changing. Notice that two GUIDs are already present and don't contain relevant changes, so you might just leave them as is.

#33 RE: [Guide] Manual AMI UEFI BIOS Modding by rootuser123 10.06.2015 09:49

Will try it now :D
@lordkag What tool did you use to extract all these files?
I tried to insert the files and rebuild the BIOS by using the UEFI Tool 0.20.5 and I flashed it to my computer but the GUI didn't change.
Am I doing it right?
So how do I reflect the change in the header to make the 3D-BIOS as a option in the GUI and make the menus useable like BIOS F14?

#34 RE: [Guide] Manual AMI UEFI BIOS Modding by plutomaniac 10.06.2015 13:34

avatar

Lordkag had written a very good post somewhere on how these work based on manufacturer and how to edit them (maybe even posted a small tool? don't remember). I can't find it now but I'll guess someone else will post a link to it.

#35 RE: [Guide] Manual AMI UEFI BIOS Modding by rootuser123 11.06.2015 02:08

@lordkag Do you have the link on about what @plutomaniac said about specific manufacturer bios mod?

#36 RE: [Guide] Manual AMI UEFI BIOS Modding by lordkag 11.06.2015 02:18

avatar

It is a personal tool, but it won't do any good for you. You are not trying to change something in the GUI, you are trying to replace it entirely, or more likely create it. I don't know why Gigabyte removed it (space problem or just to make newer cards look better), but they also changed the way the GUI is loaded. My bet is it has to do with AMITSE and you pretty much are out of options. I mean, if you look at the images, they left almost nothing.

#37 RE: [Guide] Manual AMI UEFI BIOS Modding by rootuser123 11.06.2015 03:17

So it looks like they rebuilt the BIOS from the ground up. I was trying to add it as an option in the BIOS like F14 where the was an option to click on '3D BIOS' and it would load up another GUI. They must of have deleted all references to it.

https://www.youtube.com/watch?v=C4Wf3yRc9H0

#38 RE: [Guide] Manual AMI UEFI BIOS Modding by rootuser123 12.06.2015 04:20

Does anyone know how to mod the BIOS and POST? They disabled it in the latest BIOS and I can't flash an older BIOS to mine.

#39 RE: [Guide] Manual AMI UEFI BIOS Modding by PhatAgent 28.06.2015 08:33

avatar

So, how do i go about updating my ASUS X99-A orom when its unsupported in these tools?

#40 RE: [Guide] Manual AMI UEFI BIOS Modding by Fernando 28.06.2015 09:34

avatar

Zitat von rootuser123 im Beitrag #38
Does anyone know how to mod the BIOS and POST?
I am sorry, that obviously nobody knows a way.

Zitat von PhatAgent im Beitrag #39
So, how do i go about updating my ASUS X99-A orom when its unsupported in these tools?
If your mainboard BIOS is an AMI AptioV one, you may have to use CodeRush's UEFITool.

#41 RE: [Guide] Manual AMI UEFI BIOS Modding by PhatAgent 29.06.2015 06:46

avatar

Zitat
If your mainboard BIOS is an AMI AptioV one, you may have to use CodeRush's UEFITool.



I figured, i read the page but didnt see any guide on how to use it, could you direct that to me?

Thanks

Edit: Looking to update raid rom to 14x from 13.1

#42 RE: [Guide] Manual AMI UEFI BIOS Modding by Fernando 29.06.2015 19:57

avatar

Zitat von PhatAgent im Beitrag #41

Zitat von Fernando
If your mainboard BIOS is an AMI AptioV one, you may have to use CodeRush's UEFITool.
I figured, i read the page but didnt see any guide on how to use it, could you direct that to me?

I am afraid, that such guide is not yet available.
You may ask CodeRush for help. because he is the developer of the UEFITool.

#43 RE: [Guide] Manual AMI UEFI BIOS Modding by Fernando 02.07.2015 17:28

avatar

Zitat von PhatAgent im Beitrag #41

Zitat
If your mainboard BIOS is an AMI AptioV one, you may have to use CodeRush's UEFITool.
I figured, i read the page but didnt see any guide on how to use it, could you direct that to me?

Recently I have asked CodeRush as the developer of the UEFITool, if he would like to write a guide about the usage of his tool and he promised to do it, when he has the needed time.


@ all AMI Aptio V BIOS users:
Update of the Start Post
Changelog:

  • new: Chapter "Modding of an AMI Aptio UEFI V BIOS" with a short guide about the replacement of an EFI BIOS module by using CodeRush's UEFITool.

Regards
Dieter (alias Fernando)

#44 RE: [Guide] Manual AMI UEFI BIOS Modding by Fernando 12.07.2015 19:31

avatar

@ all AMI Aptio V BIOS users:

Update of the Start Post
Changelog:

  • completely updated: Chapter "Modding of an AMI Aptio UEFI V BIOS" with a short guide about the replacement of an EFI BIOS module by using CodeRush's UEFITool.

I hope, that it will be useful until CodeRush will present his own guide within a separate thread.

Regards
Dieter (alias Fernando)

#45 RE: [Guide] Manual AMI UEFI BIOS Modding by lordkag 15.07.2015 02:30

avatar

There is problem with the Aptio V guide. When you use UEFITool, you either replace the body of PE section with an .efi file, or you replace the entire GUID with a .ffs file. The reason for this is that the ffs is a container for sections and has the header where you can see that GUID, while the PE section (or any section) can only make sense in a ffs and has a small header on its own, with size and extra data on a few special sections. To make things a little clear, an .efi file is an executable with a PE header and structure, it can be opened with any PE tool for inspection. The simplest way to determine if you have an .efi file is to look for the signature 4D5A in the beginning, PE pointer in 0x3C-0x3F and PE signature at that pointer. The easiest way to determine if you have a ffs file is to check the first 0x10 bytes (it should be random bytes) and the byte at offset 0x17 should be F8 - most common, or 07 - less common; other values are only transitional.

If you do plan or need to use UEFITool, replacing the body of a section is more than recommended: the file is left in its original structure, the compression method is not changed, the header or dependencies are not affected. The only inconvenient I would see in this method is when the UI has a specific name like IntelRaid12701936 and you simple want to avoid any confusion between original and modded file. The ffs replacement is more intended for MMTool (forced in fact), while for UEFITool is needed only when you plan on patching other sections than PE.

You can't normally use UEFITool for ROM replacement. The only exception is with ROMs in freeform sections or raw sections or raw files, where you can use "replace body", but it requires you to know where it is, what it is, which will put you above the necessity of a guide. So that leaves us with replacement of EFI drivers. The simplest and safest way is to use the replacement of PE section, with .efi files that are already offered in a separate thread. For a "replace as is" of a GUID it would require the user to know what a header is, how to check it, how it would compare with the file in respect of properties and dependencies... In other words, it would be used by users who aren't in a need of a guide. Under NO circumstance use the "replace as is" on a section. This might work if you are in a hurry and you simple patch a byte or two, with no size change, but it is dangerous otherwise. Especially the recommended action in the guide is dangerous, as it is replacing a section with a whole file. Luckily, UEFITool can detect such changes when it re-opens the file, but will a regular user know how to read the warning messages? The rule of thumb should be to replace as little as possible and target only what you want to change.

Xobor Forum Software von Xobor
Datenschutz