Forum - RE: [Discussion] UBU Tool related Questions, Reports and Suggestions

#2836 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Sat Mar 25, 2017 12:42 pm

Well, where can I find these versions?

OROM Boot Agent GE : 1.5.78
EFI Intel PRO/1000 UNDI : 7.0.06

This thread has been closed.

#2837 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Sat Mar 25, 2017 1:47 pm

Zitat von tecnics im Beitrag #2832
Well, where can I find these versions?

OROM Boot Agent GE : 1.5.78
EFI Intel PRO/1000 UNDI : 7.0.06

Only for i210/211/350 etc

For 82579/i217/u218/u219 - OROM CL and EFI Gigabit

This thread has been closed.

#2838 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Sat Mar 25, 2017 2:14 pm (Last edited: Sat Mar 25, 2017 2:39 pm)

Zitat von tecnics im Beitrag #2832
Well, where can I find these versions?
OROM Boot Agent GE : 1.5.78
EFI Intel PRO/1000 UNDI : 7.0.06

For example within the folder named Modules of the UBU tool.
You can download the "Modules" folder from the most recent UBU tool v1.66 >here<

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

This thread has been closed.

#2839 | RE: [Tool Guide+News] "UEFI BIOS Updater" (UBU) datum

Tue Mar 28, 2017 11:34 am

How can I find downloading URL

This thread has been closed.

#2840 | RE: [Tool Guide+News] "UEFI BIOS Updater" (UBU) datum

Tue Mar 28, 2017 11:53 am (Last edited: Tue Mar 28, 2017 4:27 pm)

@qvc2007:
Welcome at Win-RAID Forum!

Zitat von qvc2007 im Beitrag #205
How can I find downloading URL

As long as SoniX hasn't completed his work on the "new" UBU tool (without AMI Aptio UEFI MMTool), we do not offer any download link to the UBU tool.

Hoping for your understanding
Dieter (alias Fernando)

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

This thread has been closed.

#2841 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Tue Mar 28, 2017 11:22 pm

Zitat von Pacman im Beitrag #2828
Intel LAN EFI Gigabit Undi 0.0.16

Can we use it as the .efi images present in UBU, or do we need to do something, like removing the header as for Intel OROMs? thank you!

This thread has been closed.

#2842 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Tue Mar 28, 2017 11:49 pm

@gpvecchi:
EFI BIOS modules with header are the *.ffs files, after the removal of the header they are named *.efi files.
The handling of the Legacy mode Option ROM modules (usually as *.bin files) is totally different. They can be inserted as they are (without removing any header).

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

This thread has been closed.

#2843 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Wed Mar 29, 2017 7:43 pm

cpu000506E3_plat36_ver000000B2_date01-02-2017

plutomaniac has attached files to this post

cpu000506E3_plat36_ver000000B2_date01-02-2017.rar

This thread has been closed.

#2844 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Wed Mar 29, 2017 11:28 pm (Last edited: Wed Mar 29, 2017 11:57 pm)

Zitat von Fernando im Beitrag #2836
@gpvecchi:
EFI BIOS modules with header are the *.ffs files, after the removal of the header they are named *.efi files.
The handling of the Legacy mode Option ROM modules (usually as *.bin files) is totally different. They can be inserted as they are (without removing any header).

Many thanks, is there some tutorial on how to remove header? I assume it has to be done with hex editor...

EDIT: I removed the firts byte of the ffs file (I looked at the old .15 Intel Lan .efi in UBU modules folder and compared to the .ffs file from same version) and used old UBU to add latest Skylake microcode (no modding from the version posted).
Should I be fine?

This thread has been closed.

#2845 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Thu Mar 30, 2017 12:21 am (Last edited: Fri Mar 31, 2017 9:50 am)

Zitat von gpvecchi im Beitrag #2838
Many thanks, is there some tutorial on how to remove header? I assume it has to be done with hex editor...

Yes, what you need is an Hex Editor like HxD.
The procedure is very simple. All you have to do is to delete the hex code, which belongs to the header. All you must know is, that the "body" of the EFI module begins with the hex code "4D 5A".

Here is my "tutorial" about how to remove the header from any uncompressed EFI module named *.ffs:

Open the related EFI module as uncompressed FFS file (in my example it is the Intel "RaidDriver" v15.5.0.2813) with the tool HxD.
This is what you will see:

Mark the header as shown in the picture above (blue colored part). Make sure, that the marked hex code part ends just before the code "4D 5A".
Then hit "Edit" > "Delete" from the task bar.
Now you get the following warning:

Click onto "OK".
This is what you see now:

Save the modified module and name it like the source file, but with the suffix *.efi.
Now you have the "pure" EFI module (without header).

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

This thread has been closed.

#2846 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Thu Mar 30, 2017 12:30 am (Last edited: Thu Mar 30, 2017 12:44 am)

ffs is a container so there can be data like the module name at the end as well. In this case the executable has a size of 0x4BE20.

This thread has been closed.

#2847 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Thu Mar 30, 2017 5:06 am

Zitat von Pacman im Beitrag #2828
Intel LAN EFI Gigabit Undi 0.0.16

APPS\EFI\EFIx64\E0016X7.EFI in Intel® Ethernet Adapter Connections CD 22.1

This thread has been closed.

#2848 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Thu Mar 30, 2017 11:37 pm

Many thanks, I'll try to keep my bios updated till new UBU will came out. Regarding the microcode, may I just use it as it has been posted, or do I have to edit something?

This thread has been closed.

#2849 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Fri Mar 31, 2017 8:06 am

@plutomaniac: Since the number in the hex dump is 0x4be24, you subtracted 4 to get 0x4be20. Where did that magic adjustment come from? I'm guessing that it's a byte count from the first byte of the number (rather than from the start of the efi). With that extra 10 byte between the count and the efi that would make 4 bytes. Is that correct, or did you leave out the "24 00 00 15" at the end for some other reason? I'm asking because the ffs number, 0x4be88, is clearly the entire size of the file (and not a byte count from the start of that number).

This thread has been closed.

#2850 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Fri Mar 31, 2017 6:22 pm (Last edited: Fri Mar 31, 2017 6:27 pm)

@ gpvecchi:

Yes, ready for use.

@ rmongiovi:

The size mentioned at the first dword includes itself as well. The actual data starts after 4 bytes with dword_size - 0x4. That dword consists of Size [0x3] and Type [0x1]. In this case we have a size of 0x4BE24 - 0x4 = 0x4BE20 and Type 0x10 which stands for EFI_SECTION_PE32. Another example, after the PE32 image ends, you can see that the next section has a size of 0x24 - 0x4 = 0x20 and a Type of 0x15 (EFI_SECTION_USER_INTERFACE) and the last section has a size of 0xE - 0x4 = 0xA and a Type of 0x14 (EFI_SECTION_VERSION). All of these can be found at the public UEFI Specification.

This thread has been closed.

Please enter a reason for warning.