Forum - AsRock Z87 extreme4 modded bios

#1 | AsRock Z87 extreme4 modded bios - Security check failed. datum

Sun Nov 17, 2013 10:49 pm

Hi all,
I have AsRock Z87 extreme4, and cannot flash modded bios. It says "Security check failed". How can I over come this problem.
Thanks in advanced.

Asus Z97-PRO(Wi-Fi ac)/USB 3.1, Samsung 960 Pro 512Gb + 2x2 TB Seagate as RAID1 + 256Gb Samsung 850 Pro for acceleration, Intel® Xeon® Processor E3-1275 v3, 4x4Gb 1866Mhz CAS9, Windows 10 Pro Workstation x64

reply

#2 | RE: AsRock Z87 extreme4 modded bios - Security check failed. datum

Sun Nov 17, 2013 11:27 pm

@ saglamtimur:
Welcome at Win-RAID Forum!

Zitat von saglamtimur im Beitrag #1
I have AsRock Z87 extreme4, and cannot flash modded bios. It says "Security check failed".

What have you modded and how did you try to flash the modded BIOS?

Regards
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.

reply

#3 | RE: AsRock Z87 extreme4 modded bios - Security check failed. datum

Sun Nov 17, 2013 11:49 pm

I have modded it BIOS version 2.30 with using your guide "Easy AMI UEFI BIOS Modding:Use of the "UEFI BIOS Updater" (UBU)", and I used "Instant Flash"

Asus Z97-PRO(Wi-Fi ac)/USB 3.1, Samsung 960 Pro 512Gb + 2x2 TB Seagate as RAID1 + 256Gb Samsung 850 Pro for acceleration, Intel® Xeon® Processor E3-1275 v3, 4x4Gb 1866Mhz CAS9, Windows 10 Pro Workstation x64

reply

#4 | RE: AsRock Z87 extreme4 modded bios - Security check failed. datum

Sun Nov 17, 2013 11:59 pm

Zitat von saglamtimur im Beitrag #3
I have modded it BIOS version 2.30 with using your guide "Easy AMI UEFI BIOS Modding:Use of the "UEFI BIOS Updater" (UBU)", and I used "Instant Flash"

Which modules did you update?
Did you update the CPU Microcode as well?

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.

reply

#5 | RE: AsRock Z87 extreme4 modded bios - Security check failed. datum

Mon Nov 18, 2013 12:01 am

All of them, CPU Microcode as well. Shouldn't I ?

Asus Z97-PRO(Wi-Fi ac)/USB 3.1, Samsung 960 Pro 512Gb + 2x2 TB Seagate as RAID1 + 256Gb Samsung 850 Pro for acceleration, Intel® Xeon® Processor E3-1275 v3, 4x4Gb 1866Mhz CAS9, Windows 10 Pro Workstation x64

reply

#6 | RE: AsRock Z87 extreme4 modded bios - Security check failed. datum

Mon Nov 18, 2013 12:18 am (Last edited: Mon Nov 18, 2013 12:19 am)

I got it. I use afudos. First tried to flash with it but it said can't flash because of file size mismatch. Interesting, it was same before and after (8196 Kb). Anyway, I backed up the bios (which is latest genuine one) with afudos. More interesting it is 6144 Kb. And then I modded it, and flashed with afudos with success. Seems everything works fine and installed Win 8.1 without any problems.

Asus Z97-PRO(Wi-Fi ac)/USB 3.1, Samsung 960 Pro 512Gb + 2x2 TB Seagate as RAID1 + 256Gb Samsung 850 Pro for acceleration, Intel® Xeon® Processor E3-1275 v3, 4x4Gb 1866Mhz CAS9, Windows 10 Pro Workstation x64

reply

#7 | RE: AsRock Z87 extreme4 modded bios - Security check failed. datum

Mon Nov 18, 2013 12:19 am (Last edited: Mon Nov 18, 2013 12:22 am)

Zitat von saglamtimur im Beitrag #5
All of them, CPU Microcode as well. Shouldn't I ?

The simple reason for my question was to facilitate the search for the reason why the BIOS flashing procedure failed. According to SoniX, the developer of the UBU Tool, the CPU Microcode update should be not very problematic with ASRock mainboards.
I hope, that SoniX or someone else can help you to solve the problem.

EDIT:

Zitat von saglamtimur im Beitrag #6
I got it. I use afudos. First tried to flash with it but it said can't flash because of file size mismatch. Interesting, it was same before and after (8196 Kb). Anyway, I backed up the bios (which is latest genuine one) with afudos. More interesting it is 6144 Kb. And then I modded it, and flashed with afudos with success. Seems everything works fine and installed Win 8.1 without any problems.

Thanks for your updated information.
It is fine, that you succeeded at least!

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.

reply

#8 | RE: AsRock Z87 extreme4 modded bios - Security check failed. datum

Mon Nov 18, 2013 12:23 am

Thanks for your interest Fernando. As I mentioned previous post, I somehow able to flash it. Any clue why backed-up bios with afudos and genuine one's file size different?

Asus Z97-PRO(Wi-Fi ac)/USB 3.1, Samsung 960 Pro 512Gb + 2x2 TB Seagate as RAID1 + 256Gb Samsung 850 Pro for acceleration, Intel® Xeon® Processor E3-1275 v3, 4x4Gb 1866Mhz CAS9, Windows 10 Pro Workstation x64

reply

#9 | RE: AsRock Z87 extreme4 modded bios - Security check failed. datum

Mon Nov 18, 2013 5:19 am

You have to edit the BIOS file with HxD, highlight from offset 0000000 to 00001000, and delete it. Then click save.

reply

#10 | RE: AsRock Z87 extreme4 modded bios - Security check failed. datum

Mon Nov 18, 2013 6:39 am (Last edited: Mon Nov 18, 2013 1:03 pm)

Zitat von saglamtimur im Beitrag #8
Thanks for your interest Fernando. As I mentioned previous post, I somehow able to flash it. Any clue why backed-up bios with afudos and genuine one's file size different?

vendor supplied image is multipart and included with (signed cap header for security, me firmware and bios firmware,etc) but afudos doesn't care other parts of firmware it will only backup with bios region(firmware) that's why there is no security verification and backup is pure bios(uefi) image

off topic question
are you turkish because your nickname is a turkish name

reply

#11 | RE: AsRock Z87 extreme4 modded bios - Security check failed. datum

Mon Nov 18, 2013 9:10 am (Last edited: Mon Nov 18, 2013 1:04 pm)

Thanks for the info.

Zitat von yaclo im Beitrag #10
off topic question
are you turkish because your nickname is a turkish name

Yes.

Asus Z97-PRO(Wi-Fi ac)/USB 3.1, Samsung 960 Pro 512Gb + 2x2 TB Seagate as RAID1 + 256Gb Samsung 850 Pro for acceleration, Intel® Xeon® Processor E3-1275 v3, 4x4Gb 1866Mhz CAS9, Windows 10 Pro Workstation x64

reply

#12 | RE: AsRock Z87 extreme4 modded bios - Security check failed. datum

Mon Nov 18, 2013 9:13 am (Last edited: Mon Nov 18, 2013 1:04 pm)

Zitat von SimpleTech im Beitrag #9
You have to edit the BIOS file with HxD, highlight from offset 0000000 to 00001000, and delete it. Then click save.

If I remember correctly (I did lots of of test), I did it already but failed. But will try again. Thanks for that.

Asus Z97-PRO(Wi-Fi ac)/USB 3.1, Samsung 960 Pro 512Gb + 2x2 TB Seagate as RAID1 + 256Gb Samsung 850 Pro for acceleration, Intel® Xeon® Processor E3-1275 v3, 4x4Gb 1866Mhz CAS9, Windows 10 Pro Workstation x64

reply

#13 | RE: AsRock Z87 extreme4 modded bios - Security check failed. datum

Mon Nov 18, 2013 8:32 pm (Last edited: Mon Nov 18, 2013 8:34 pm)

Zitat von saglamtimur im Beitrag #11
Thanks for the info.
Zitat von yaclo im Beitrag #10
off topic question
are you turkish because your nickname is a turkish name
Yes.

me too :) //Merhaba

Zitat von saglamtimur im Beitrag #12
Zitat von SimpleTech im Beitrag #9
You have to edit the BIOS file with HxD, highlight from offset 0000000 to 00001000, and delete it. Then click save.
If I remember correctly (I did lots of of test), I did it already but failed. But will try again. Thanks for that.

correct way to edit bios image is tricky different offset used each model all you have to compare both of backup and original rom

but the best is to use the backup does not distress

reply

Please enter a reason for warning.