Page 6 of 65
#76 RE: [Guide] How to flash a modded ASUS or ASRock AMI UEFI BIOS by lowicunr 09.03.2016 03:41

avatar

@jan771:
I am located in Germany. If you want CH341 programmer quickly, then you may order at Amazon.de
They ship form UK and it takes 3-4 days to Germany.

Or here are all trader from EU:
http://www.ebay.de/sch/i.html?_from=R40&...=p2045573.m1684

#77 RE: [Guide] How to flash a modded ASUS/ASRock/Gigabyte AMI UEFI BIOS by SignedAdam 11.03.2016 14:13

avatar

The newest build of AFU does not allow me to flash the BIOS on a P8Z77V PREMIUM, (The workaround is, to find an older build of AFU)

I would use BFlasher by asus, but I can't for the life of me find the old version of bflasher, that allowed you to by pass the Security verification failed rubbish, you could use some command to bypass it, can't recall what that was now! so the only way i'm able to flash at the moment, is to use an older type of AFU, and flashing a bios.bin file, because i dont think AFU supports .cap

* This is way over the top Security, I wont be buying an Asus board ever again after this, it's so crazy, i dont even know if flashing worked, AFU says it did flash the bios i made in UBU_Upd_2_1,

* before anyone says, use stup!d rubb!sh flashback, flashback is dead on my board, I format a stick as fat32, i rename the bios file, i turn the system off, i put this usb stick in the flashback usb port, that is clearly marked out in green, i press and hold the button, and the light flashs every 1 second, for 1 millisecond, I let go after 5 seconds, and the light stops flashing every millisecond, and just stays on, (it does not flash) ive tried holding it for 10 seconds, 20 seconds, even 1 min, even 10 mins, ive tried cmos reset, removing the battery, cmos reset again, changing the pins with the blue connecter, using a other usb stick, nothings makes it work,

#78 RE: [Guide] How to flash a modded ASUS/ASRock/Gigabyte AMI UEFI BIOS by SignedAdam 12.03.2016 15:29

avatar

Hello, it was very hard for me to get my bios to update, with out the Security verification failed message, it does not help that AMIBIOS has different types of its program, some don't work on your bios, some do work, so im posting this guide for noobie bios modders like me

1st off you will need to download lots of different things, they also need to be the right things too, in the right place, you don't need to be a command line Computer Nerd, to make this work, you just need alot of time, and take things very slow, or you will end up with a computer, that wont even post,


1st download : Here

download both UBU_Upd_2_1.exe
and
UBU_v1_47_1.rar

once downloaded, extract both UBU_v1_49_1 and UBU_Upd_2_1, you should then end up with two folders, you then want to move all folders out of UBU_Upd_2_1, "MEA" and "Modules" too UBU_v1_49_1, you then need to rename "UBU_v1_49_1" to "UBU" and move it to the root of your system drive, "c:\" one you have done that, download your bios, and move the .cap file, or .bin file, to the UBU folder, we just moved to your c:\ drive,

open a admin command prompt, by right clicking on your start button, or by right clicking on command prompt in all programs, once open, type in

CD C:\UBU

UBU

now wait till it says : Press any key to continue...

now if you know what your doing, you may start, but if you don't, follow what i do,

press the number 1 then enter, press the number 7 then enter, then just enter after , 2 enter, 1 enter, enter, 3 enter, 1 enter, enter, 5 enter, 1 enter, enter,

now the harder part, press 7 and then enter, a window will open, just press enter inside of it, then go back to the windows you were working in and press 1, then enter, type 1C, then enter, then type 29, then enter again, press enter on the new window that opens, (if at any point, pressing enter does not work, to close the extra opened window, close it, then type n, then enter,

now press 0, then enter, then press 1, then enter 1, then enter again, to close the window, job done!

you should find a new bios file in the UBU folder, with the correct name for flashing to your bios, if flashback is still working for your system, great, if not, then continue reading,

next you will need to download : here

then extract the following found here :
D:\Users\signe\Downloads\AMIBIOS_and_Aptio_AMI_Firmware_Update_Utility.zip\AptioV\afu\afuwin\64

open an old bios file, and flash it, using the program afu, then open and flash the new modded bios file with the program afu,the one found in the (UBU folder) make sure you do all blocks, this will by pass the Security verification failed message, if you still get a message, keep opening and closing the program, till it lets you flashed your bios, this is the only other way to flash your bios, if flashback is broken, :(

After you have flashed your bios, you will want to reboot, and clear cmos, to check that your modded bios did flash, you will want to open afu, then click save, then move the .rom file to ubu, if ubu shows the updated version numbers this time, then it worked, if it shows older version numbers, then the flashed failed, good luck

#79 RE: [Guide] How to flash a modded ASUS/ASRock/Gigabyte AMI UEFI BIOS by lordkag 13.03.2016 22:26

avatar

After Pacman notified me that newest ASRock boards have the "Secure Flash check fail!" message even on images without capsule, I began to investigate. I discovered that the capsule is still present, just moved inside the BIOS Region, specifically this section:



With his help, I tested different workarounds. What (still) worked was the capsule removal, any other modification to the capsule resulted in the same error message. There are others ways to patch this error, but until ASRock upgrades their "protection", you can simply do the following for every modding:







For anyone using this method, you should thank Pacman, it wouldn't have been possible without his help. [Pacman, you green traitor, why have you forsaken the purple cause? I must now do battle with a Ninja and a Knight?]

#80 RE: [Guide] How to flash a modded ASUS/ASRock/Gigabyte AMI UEFI BIOS by Fernando 13.03.2016 23:28

avatar

@lordkag:
On behalf of all users of a new ASRock mainboard, who want to modify its AMI AptioV BIOS, I want to thank you for your efforts to find a way how to get the modded BIOS properly flashed.
I just have added an update to the start post of this thread and a link to your post.

@all users with an Intel 100-/200-Series ASRock mainboard:
Please give us your feedback about your experience while trying to flash a modded AMI AptioV BIOS.
Thanks in advance!

#81 RE: [Guide] How to flash a modded ASUS/ASRock/Gigabyte AMI UEFI BIOS by SoniX 14.03.2016 02:59

avatar

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?

#82 RE: [Guide] How to flash a modded ASUS/ASRock/Gigabyte AMI UEFI BIOS by RoadrunnerDB 17.03.2016 06:13

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!

#83 RE: [Guide] How to flash a modded ASUS/ASRock/Gigabyte AMI UEFI BIOS by SoniX 17.03.2016 11:46

avatar

Zitat von RoadrunnerDB im Beitrag #82

"UBU" does not change the security check when no modules are exchanged.

Which version UBU you use?

#84 RE: [Guide] How to flash a modded ASUS/ASRock/Gigabyte AMI UEFI BIOS by RoadrunnerDB 17.03.2016 21:30

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.

#85 RE: [Guide] How to flash a modded ASUS/ASRock/Gigabyte AMI UEFI BIOS by RoadrunnerDB 18.03.2016 12:55

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"?

#86 RE: [Guide] How to flash a modded ASUS/ASRock/Gigabyte AMI UEFI BIOS by Fernando 18.03.2016 13:15

avatar

Zitat von RoadrunnerDB im Beitrag #85
Why is enabled in "UBU" no "Orom" update.
Because it doesn't work with AMI AptioV UEFI BIOSes properly by using the "official" AMI Aptio UEFI MMTool.

Zitat
Why a routine is not part of "UBU"?

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.

#87 RE: [Guide] How to flash a modded ASUS/ASRock/Gigabyte AMI UEFI BIOS by Pacman 18.03.2016 14:18

avatar

Zitat von RoadrunnerDB im Beitrag #85
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!

What version of UBU did you do this with? Only version 1.50 would work.

Zitat von RoadrunnerDB im Beitrag #85
I then only the "SLIC-TOOL" used. The "INSTANT-FLASH" process worked.
So is the culprit "UBU"!!

If you used any version of UBU below 1.50, then possibly.

Zitat von RoadrunnerDB im Beitrag #85
Who "BIOS" destroyed his own fault as are warranty provisions.

All changes made with UBU is completely reversible, nothing will be "destroyed", flash the stock BIOS file and Changes are reset.

Zitat von RoadrunnerDB im Beitrag #85
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"?

The capsule is replaced with padding.

#88 RE: [Guide] How to flash a modded ASUS/ASRock/Gigabyte AMI UEFI BIOS by RoadrunnerDB 18.03.2016 17:03

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.

#89 RE: [Guide] How to flash a modded ASUS/ASRock/Gigabyte AMI UEFI BIOS by Fernando 18.03.2016 17:21

avatar

Zitat von RoadrunnerDB im Beitrag #88
Decentralization is the magic word!
"UBU" for AMI Aptio IV and "UBU" with "UEFI-TOOL" for AMI Aptio V Motherboard!
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.

#90 RE: [Guide] How to flash a modded ASUS/ASRock/Gigabyte AMI UEFI BIOS by RoadrunnerDB 18.03.2016 18:12

@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?

Xobor Forum Software von Xobor
Datenschutz