Hi ! Tito Thanks for reply. How to check the AsRock UEFI have or have NO Digital signing ? I mod 6 and 7 series with Tool earlier version (older than 2.50) without any problem and can flash Mod UEFI with UEFI build in tool with success . Many thanks in advance. Regards nel1156
Check out the size. If its exactly 2^13=8192 KB or less, then there is no digital signing. But if its 8196 KB (4 KB extra), then remove the first 4 KB (1000h).
As I said, modding with ASUS isn't a problem - but the BIOS seems to be signed/protected. The flashtools (EZ Flash/BUPDATER) complain when trying to flash back, no matter if the additional 2K are there or not.
Thanks for the feedback. This bios already contains SLP module (9528...), therefore I have used "Structure" function to insert the modules with Gigabyte's Pubkey&Marker (2.1) and to replace (with HEX editor) "ALASKA" & "A M I " strings in 4 modules.
Will test this ASAP (may take a few days though until I can return to the board). Since I want to learn, a few questions: 1. Since there's an AMI dummy SLIC (2.0) already present, the tool recommended Dynamic. In the past it always worked, even for my present board (ASUS M5A97). This is now out of the question because of the new protection? If yes, maybe the tool could propose the New Module method for these new boards. 2. The existing SLIC/marker shouldn't make any issues? It's removed/dormant? 3. The modded update is universal (I have two boards of the very same model and revision). Sorry for the questions, but I eventually want to to this myself.
1. The dummy AMI SLIC isn't a full table, just a placeholder header. So you can insert any valid pubkey+marker pair to get a valid SLIC table. The main problem is the RSA signature checking which is a part of newer bios updates released by Asus. When you are using Dynamic method, the signature breaks. On the other hand, New Module method uses leaked private key to insert the module so that the signature remains intact. 2. As I said before, there is no marker at all. You can't dump a 374 bytes long AMI SLIC. 3. Yep, it is.
Thanks. That explains it. So the tool should, when it encounters a .CAP file with signature, automatically propose New Module as method, as Dynamic would never work.
I'm can't recall exactly, but Serg008 has some 'secret' knowledge to do Dynamic 'Custom' mod on *.CAP.
Feedback: The EFI flashed and RWEverything can see the SLIC. That would mean the mod is successful. You might want to add it to the collection.
Hi ! Andy and all experts Great thanks for Andy and all experts. But, I find the modded UEFI (MSI H61m-P31 UEFI Ver 2.4 and 2.7) 's ACPI's auto power on DON'T WORK. Meanwhile, the modded AMI8 BIOS (also MSI MOBO) works with ACPI's auto power on by Andy's tool for AMI8 BIOS. The setting for ACPI's auto power on should be correct that ACPI enabled as S3 and wake up by RTC alarm by setting the date. Many thanks in advance EDIT : No ACPI's auto power on problem with Mod UEFIs of ASROCK 6 and 7 series MOBO. It may be specific regarding MSI H61m-P31 itself. Anyway many thanks.
Hi Do the inserted modules have to be immediately after the 9528 module or can they be at the end of the FV?? A
v2.55 will be able to do this (recognises 9528 module) - will need to untick 'only alter tables in main ACPI module' A