If this protective capsule is present in all BIOS AptioV on the motherboard ASRock, and everywhere the same GUID 414D94AD-998D-47D2-BFCD-4E882241DE32 and Subtype GUID: 5A88641B-BBB9-4AA6-80F7-498AE407C31F , it is possible to implement this method to remove protection in UBU, using a ready-made FFS-file.
Edit:
Only, it is not clear. The entire file (2048K) must be filled FF or only at the offset 0x0-0x1FF?
Sorry for my bad english … google help
It is not necessary to use "AFU"!
A "Clear CMOS" is not necessary!
"UBU" does not change the security check when no modules are exchanged.
Load original "BIOS" in "UBU" and removed the security check.
Then the "BIOS" save without further changes, restore the original name of "BIOS" again.
Flash the "BIOS" on "INSTANT FLASH" finished.
Now should any new "BIOS" are previously read about "UBU" so that the security check is not written back into the "BIOS".
Now you can easily integrate the "BIOS" in "UBU" and replace the modules.
The people of "ASROCK" use a tool to this security check by the "BIOS" completion so to decorate …
I find it to be unnecessary especially if you have a dual "BIOS" on the Main board.
I have the motherboard "Z170Extreme4" …
versions tested with different "BIOS".
If "ASROCK" the address space do not change it should work on life …
I find "ASROCK" should make it exactly like "GIGABYTE"!
An entry in the BIOS interface so the user can determine whether the security check activated or deactivated.
Thanks!
Which version UBU you use?
I bought the board in August 2015 because I noticed the "ASROCK" has implanted a new security check.
I wanted to flash the "ROM" with "Slic tool" and then finish the "ROM" on "UBU".
It did not work so I went on troubleshooting!
I then only the "SLIC-TOOL" used. The "INSTANT-FLASH" process worked.
So is the culprit "UBU"!
Now I have changed every single "module" …
So only "EFI ROM Raid" then stored and worked on "INSTANT-FLASH".
Then again the edited "Rome" change in "UBU" to the "EFI GOP" again saved and tries error about "INSTANT-FLASH".
I then looked over the "UEFI-TOOL" to any entries.
but then I gave up!
I bought a "USB PROGRAMMER" with "DIP SOCKETS" and described the "BIOS" with it!
Read some point here about "AFU" and use the method!
It is the fakt "ASROCK" generates the checksum of the modules and "lordkag" has the address space found.
Congratulations!
The charade of "ASROCK" should be left.
Who "BIOS" destroyed his own fault as are warranty provisions.
A question?
Why is enabled in “UBU” no “Orom” update.
X99 and Z170 boards need to be updated to “UEFI-TOOL” manually by hand.
One need not a “UBU” anyway because 50% of the modules on
"UEFI-TOOL 'must be made.
Why a routine is not part of “UBU”?
The manual processing of “VBIOS” must be done with the known guide in the forum.
These instructions are completely unusable because the Intel Content protection is thus destroyed.
I start in “VBIOS” there is no sound on “HDMI DP DVI”!
If you start in “GOP UEFI” there are no problems.
The is also correct because “EFI GOP” does not have to be adjusted manually.
I always have to compare an original intel “VBIOS” with my mainboard “VBIOS”.
This I always do with “HEX EDITOR” because the original intel “VBIOS” must be adapted to the graphic connections.
The address range to remove the security check is quite large since a large area is cleared with “FF”.
Why is the area changed from “…” in “FF”?
Because it doesn’t work with AMI AptioV UEFI BIOSes properly by using the "official" AMI Aptio UEFI MMTool.
Because the implementation is very difficult.
You are invited to help SoniX to develop a method, which will make the update of any AMI AptioV UEFI BIOS as easy and safe as it is with AMI AptioIV UEFI BIOSes.
What version of UBU did you do this with? Only version 1.50 would work.
If you used any version of UBU below 1.50, then possibly.
All changes made with UBU is completely reversible, nothing will be "destroyed", flash the stock BIOS file and Changes are reset.
The capsule is replaced with padding.
Fernando I know that!
Decentralization is the magic word!
"UBU" for AMI Aptio IV and "UBU" with "UEFI-TOOL" for AMI Aptio V
Motherboard!
The Orom address areas in all Z170 motherboards are identical.
AMD I would not touch it!
Area:
Raid-rom GUID = D46346CA-82A1-4CDE-9546-77C86F893888
VBIOS GUID = C5A4306E-E247-4ECD-A9D8-5B1985D3DCDA
BootAgentCL GUID = 50339D20-C90A-4BB2-9AFF-D8A11B23BC15
ASUS, ASROCK, MSI and GIGABYTE!
Furthermore, AMI Aptio IV is no longer just asked about long.
Yet what the info!
A removal-of the board battery caused on Z170 deletion of MAC address.
In case of power interruption and battery removal-!
It must be installed by a manufacturer software the Mac by Dos surface.
AFAIK CodeRush and SoniX are working on that project since several months, but the realization seems to be not as easy as you may think.
@Pacman
Which version was active in August 2015?
The Slic tool does not work on ASRock Z170!
The slic is written in an empty address area without knowing.
ASRock has implanted no OEM Slic. Or Dummy ORM!
In my old Z68 or Z77 a dummy Slic was always present.
This was recognized by the Phoenix tool and replaced with a real Slic.
Version less than 2.66 the BIOS is crashed.
The "Gigabyte Z170" works is not important
You have no real UEFI! You have a work based.
Slic is my matter!
It was only my knowledge …
The Phoenix security protection not changed.
I will test it with UBU 1.50 and will report!
I need an older version of UBU where no security check is removed.
Have the old versions deleted…
who has an older version?
Fernando
Do you have an older version? UBU
Sorry for my bad English!
@ RoadrunnerDB
I know nothing of SLIC, you were talking about Asrock, Instant flash & UBU, as far as i can understand, you had problems flashing the UBU modded BIOS with instant flash.
So, if you used an older version of UBU than 1.50, instant flash of course would not work.
@Pacman
I know that an older version does not work!
@Fernando
Thank you have the version 1.49.4 itself found.
Back to the topic!
Have tested and found that it was my fault.
Module exchange no instant flash possible.
Sorry was all in August 2015!
But a CPU microcode update works on UBU.
Instant flash process successfully!
This security check includes all modules …
CPU patch is excluded thereof!
EDIT by Fernando: Unneeded blank lines removed (to save space)
Hello,
I hope you can help me!
I want to mod my Mainboard (ASRock X99M Extreme4 - BIOS V 2.00) with an Ozmosis-Mod. First it seems that the flash is getting good. But than I got the message: Secure Flash Check fail
How can I fix it?
Thanks and regards
@variousos :
Welcome at Win-RAID Forum!
Run the latest UBU tool version and let it open your modded ASRock AMI Aptio V BIOS. The tool is able to remove the hidden capsule header, which is responsable for the "Secure Flash check fail!" message.
Look into the "Guide for ASRock mainboards" within the start post of this thread and read the "Update 2" part of the chapter "B. Flashing a modded AMI Aptio V UEFI BIOS".
Good luck!
Dieter (alias Fernando)
You have new BIOS V. 3.00
Hi everyone,
I have a P8Z77-V LX motherboard I’m trying to flash with a modified bios (of 2501) with NVMe support. I have a few questions / problems.
When modding 2501 I’m unsure weather to add NvmeExpressDxE or (Nvme, NvmeSmm, NvmeInt13). Just to note, when importing the 3x modules from a Z97 bios, take the modules from a2501 bios as newer bios revisions of NvmeInt13 will receive GUID already exists when importing that module. Once I mod my cap file with MMTool, I soon realized my motherboard has no flashback USB so I’m unable to flash the bios. I then created a rom of the bios using AFU, applied new modules and saved. I tried to flash with /P /B /K and /GAN (on AFU v3.05). /P /B/ K cant write due to security, /GAN says complete but changes are not saved. I tried to rollback my bios to earliest possible version in hope that security is less, the earliest I could get was 1304 but still unable to flash with AFU or z-flash.
I will read some more, maybe I have missed something, but it’s looking like I made need one of these CH341H-based SPI programmer kits to apply my modded bios?
Help or suggestions appreciated.
@laffo16 :
Welcome at Win-RAID Forum!
You will probably only need to insert the EFI module named NVMeExpressDxE.
Unfortunately I don’t know a solution myself, but I hope, that anyone of our BIOS Gurus knows a solution and will give you an advice.
Good luck!
Dieter (alias Fernando)
For anyone willing to test, here is a patched BUPDATER. It goes without saying that I’m not responsible for any damages you may suffer. It is based on Asus BUPDATER 1.30.
It is offered for those with Asus boards (with or without USB BIOS Flashback) that get a “Security Verification Failed” on any BIOS modding. Mod your BIOS as usual, flash with the attached file from DOS, attach any feedback you can offer. I’m interested in the errors - exact message, screenshot is recommended. It probable will work, but I’m just testing an idea at the moment. Test only if you have a way to recover or you are not afraid of messing with patched files.
Edit: Also attached 1.31 modded and renamed as original for keeping with DOS short names. Please try with 1.30 first if your board is supported. If your board needs to restart for updating, chances are the signature is processed by your current UEFI firmware (on BIOS chip), thus any patch outside it is useless. And for patching the existing firmware you need a programmer in the first place, which makes the need for patching useless. Still, if someone has a programmer, but wants to avoid using it all the time, I can look into it.
BUPDATER130_mod.rar (36 KB)
BUPDATER131_mod.rar (36.4 KB)