sorry for opening a new thread, but i can’t believe, i am the only one who is no longer able to “instant flash” an UBU-modded bios.rom on ASRock Z370 Motherboard. I would like to explain what happens in details:
I just got my new ASRock Z370 Professional Gaming i7 today and tried to update latest BIOS v3.10 with latest UBU (as i always did with my ASRock Z270 Super Carrier w/o any problems, evan when flashing). But when i try to flash it with ASRocks “Instant flash” method, i allways get the message “Secure flash check fail!” now. What am i missing? Or is it possible, that ASRock has changed their Capsule-Method once again and we need to patch this with a newer fix? Are there any other users facing the same problem?
PS: tried it with older UBU1.69.xx and with latest UBU1.70.rc8 - also tried the method mentioned here.
EDIT: This is what i tried so far:
opened the attached original ASRock Z370 Pro Gaming i7 BIOS v3.10 with UBU BIOS Updater v1.69.17 - and this is the log file:
Scanning BIOS... Please wait... Define BIOS platform - AMI Aptio V Brand ASRock Remove ASRock Protection Remove ASRock new protection... Found Option ROM VBIOS in GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0 C5A4306E-E247-4ECD-A9D8-5B1985D3DCDA Found Option ROM in GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0 50339D20-C90A-4BB2-9AFF-D8A11B23BC15 Found Option ROM in GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0 0FDD6564-FF41-4C31-8BC4-376130E5939A Found Option ROM in GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0 D46346CA-82A1-4CDE-9546-77C86F893888 Found EFI Intel GOP Driver GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0 380B6B4F-1454-41F2-A6D3-61D1333E8CB4 Found EFI Intel Raid Controller GUID 7B17F47D-DA3E-48F3-8EFE-ABC82CB77F2C Found EFI AMI NVMe Driver GUID 634E8DB5-C432-43BE-A653-9CA2922CC458 Found EFI Intel LAN PRO/1000 Undi GUID 48392194-D155-4567-9AAF-FA805BAEEC6C Found EFI Intel LAN Gigabit Undi GUID 9006872D-3A86-4BAE-A2F0-E527B9D7119E
This BIOS on Aptio V platform, known issues: - There may be problems with updating the CPU microcode
Drücken Sie eine beliebige Taste . . .
Enter number:0
1 - Rename to mod_Z37PG73.10 0 - As Is BIOS.BIN
Rename? :1 bios.bin ===> mod_Z37PG73.10
So you see, nothing was changed by myself - just opened and saved as modified BIOS file for "instant flash". But this gives error message "Secure flash check fail!":
So i tried same original, unmodified BIOS with latest UBU v1.70.rc8 - and this is the Logfile:
[OROM - Find and Extract] VBIOS in GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0 OROM in GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0 OROM in GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0 OROM in GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0 Drücken Sie eine beliebige Taste . . .
Enter number:0
1 - Rename to mod_Z37PG73.10 0 - As Is BIOS.BIN
Rename? :1 bios.bin ===> mod_Z37PG73.10
******************************************************** * Many thanks for the use of the project. * * See Information if You want to support this project. * ********************************************************
Also tried to "instant flash" this modified BIOS - but still the same message: "Secure flash check failed!"
The modfication seems to be ok, cause capsule is still in the same position in this BIOS:
But the UBUmodification still seems not to work on ASRock Z370 BIOS files and maybe some of the pros (@CodeRush@ket@SoniX@lordkag ) could take a look on it again to fix the “Secure flash check fail!”-message again. P L E A S E . . .
As i already mentioned above: always used UBU (v1.69.17 and v1.70.rc8) to bring my ASRock Z270 Super Carrier BIOS to the latest SATA-, VBIOS-, Network-EFI and Microcode and it never was a problem to “instant flash” those modified BIOS files before. So any help with this is greatly appreciated. Thanx in advise…
PS: what makes me wonder is also the fact, that i am not able to re-flash an original, unmodified ASRock BIOS twice! If i try that, the moment i want to re-flash it, Instant Flash gives me a message like "There is already the same version flashed to this board. Please select a newer BIOS file." Wasn’t also a problem on my ASRock Z270 Super Carrier board. Now i have to “downgrade flash” before flashing the latest BIOS for a second time. So i think, ASRock not just implemented a new “secure flash check” routine, they also implement a “same version already flashed” check routine.
EDIT by Fernando: Codes put into spoilers and pictures resized and directly attached by using the Forum software (to save space, the pics can be enlarged by clicking onto them) EDIT2: Thread title slightly customized to open it for users with another ASRock Intel 300-Series Chipset mainboard EDIT3: Thread stickied and title shortened
Did you try to flash via FPT yet instead? If not, try, here is FPT version you need in this package, run from command prompt at the folder location (put mod BIOS inside folder too) It’s inside “Flash Programming Tool” folder https://mega.nz/#!GB9XSBqZ!2lnEz1iVjW6Do…wS6ojpyYI29FUo0
Run this command from the folder containing the FPT exe and the mod BIOS.
fptw.exe -bios -f modbios.bin <<< DO NOT FLASH LIKE THIS, unless you have dumped your BIOS region previously, and then modified it, and this is your dumped modified BIOS region. DO NOT USE THIS command with stock BIOS!
If you get error, show me image of the command ran and the error all on same screen so I can try to help you around issue (If error like “Failed to disable write protection for BIOS space” etc we can fix)
If you need to update ME, you will have to use ME FW Update tool (I can show you later if you need)
your next drink is on ME ! Flashed successfully my modded BIOS with FPTW64.EXE. The “-bios” was the parameter that did the trick. Thank you so much. Here is the log:
Tried everything all day long - nothing worked so far. Evan with a CH341A programmer i had no luck. But now it is working and i am totally happy.
But anyway i would prefere to find a solution to get back the "instant flash" method. So if anybody is interested to find a way, i am willing to give it a try. Thanx in advance and regards...
Sweet success buddy, and you’re welcome! So you know, the -bios parameter only flashes the “BIOS” region, what you see in that region in UEIFTool - so no ME update using that method. For ME update when locked out of normal flashing you can use ME FW Update tool from the Intel System Tools package in FWUpdate folder (FWUpdLcl), provided your ME is not corrupt and you are not back flashing against current ME SVN/VCN restrictions
Ch341A should have worked for you no problem, provided you found working software version for your BIOS chip (and had driver installed). If you want help figuring out the programmer let me know!
And yes, I agree, solution needs to be found again to fix the capsule security like before with UBU. I’m sure those guys who figured it out before could figure it out now too, but maybe they don’t have this board so no lock on their end in their current BIOS to get around, so it may be more difficult for them to test other than creating a bunch of BIOS for you to try until it works. For that, you need to get your CH341A process figured out and working on your end
Result is success, BIOS (RGN) updated, I assumed, since he gave me a beer/drink
He still wants to find new working solution to the capsule security that used to be fixed by UBU, but that method no longer works on this latest version of his BIOS (FF “hidden” capsule method no longer works manually or via UBU)
@SoniX I flashed my UBUmodded BIOS now with FPT. The command “-f” means flash a file, “-bios” i think means flash only BIOS region. And “mod_bios” means the name of the bios file you want PFT to flash. Maybe i missunderstand you, because i think, you know what these parameters/options already stay for. But for me it was the only way, to get my UBUmodded BIOS to flash into my ASRock Z370 Professional Gaming i7 board. After modifying the original BIOS file in any way, i wasn’t able to “instant flash” it to the board, cause instant flash always replied with error message “secure flash check fail!” - even if UBU has patched the hidden CAPSULE region.
Unfortunately, for the new BIOS ASRock versions 3, xx and above, the method of removing the Capsule will no longer work. I have a suspicion that the guys from ASRock have made changes to the built-in Intstant Flash. And now it is necessary to check the availability of the Capsule, which was not before. Therefore, solution to the problem is correct to use FPT.
a) saved capsule before patching with UBU via UEFI-Tool 0.25.1 b) modded BIOS with latest UBU 1.70_rc10 c) re-insertet the under a) saved capsule data back to the place where it belongs. d) tried to “instant flash” the so modified BIOS - and got (as expected) the same message: “secure flash check fail”.
ASRock Instant Flasher for Z3x0 boards now ist v2216 I could live with the possibility to flash the so modded BIOS via FPT (now, that i know how to do it).
Maybe, take old BIOS, remove instant flasher module, replace in new BIOS, flash via FPT so onboard BIOS has old instant flash. Then test if modified BIOS via UBU can flash again.
I wouldn’t call myself a pro (yet anyway) I’m just an old skool PC enthusiast from back in the day when enthusiasts actually knew what they were talking about and doing thus could call manufacturers out when they were BSing us, which makes me competent at altering some aspects of firmware but I’m definitely not at the level of the likes of the legends that are SoniX and CodeRush ;). Anyway, regards your problem @MDoehler I would start by looking at or replacing the Instant Flash built-in flasher. Also somewhere in that flasher will be a preventative flag that stops someone from flashing a firmware image with the same revision as the currently installed firmware you’ll want to remove that too to save having to do anything like downgrading the firmware first to then be able to flash your modified firmware.
No, this does not solve the instant flash method for the future, but does allow BIOS region edits to be flashed via FPT. I didn’t look in BIOS to see if instant flash was it’s own module, but I’m surprised it’s not, I guess that’s out.
Please help me to upgrade Intel RST RAID driver to newest. My mainboard is Asrock Fatal1ty B360 Gaming K4. Bios ver: 3.10 I did it myself but I cant flash it. It show ‘Secure flash check fail’
@naonao5321 - above link works fine, if you have issue try refreshing your IP, or do not use a proxy then refresh the page, or try another browser. If you still cannot get it I will upload a copy to a free file host (tell me your preferred file host that I can upload to for free, otherwise I will choose one)
You should edit out that email, unless you don’t care about tons of spam
just got my new ASRock Z370 Professional Gaming i7 today and tried to update latest BIOS v3.10 with latest UBU (as i always did with my ASRock Z270 Super Carrier w/o any problems, evan when flashing). But when i try to flash it through “Instant flash” i allways get the message “Secure flash check fail!”. What am i missing? Or is it possible, that ASRock has changed their Capsule-Method once again and we need to patch this with a newer fix? I read the whole thread but could not find any post mention this behaviour.
Anyone who is able to patch latest ASRock Z370 BIOS and got this flashed to their MoBos successfully?
PS: tried it with older UBU1.69.xx and with latest UBU1.70.rc8 - also tried the method mentioned here.
Anyone interested in removing the newest ASRock protection, as described in the post above? I have a general idea on what to patch, but I will need some brave volunteers. There are some caveats, however: - if you are a volunteer, there is no guarantee on the safety of your board. I might find a solution, or I might serve you a “well done” board-steak. - it will not work like the previous patch. It will be a two-step solution: first (one-time) you have to flash a patched image with Intel FPT, then you can flash any modded image with Instant Flash. - the patch can be added to UBU, but it will have to be applied on every modded image. A vanilla (non-patched) Instant Flash module will lock your BIOS again. - basically, it will patch the Instant Flash module found on the BIOS to ignore the signature fail. As long as a patched module is on the BIOS chip itself, you can flash any image. - there is no time estimation on when the patch will be offered. I have a general idea on the patch, but I haven’t really narrowed it down to the final bytes. Maybe a few days or a week, if I’m in the mood and my schedule is available.
