@maxmen77 Opt for New Module method for this mobo. Always visit this link for updated SLIC/cert archive. @acc4iload Those are leaked keys required for inserting SLP modules in certain AMI Aptio UEFIs to turn on SLIC permanently. In case of Asus, its called as New Module method.
OK, thanks. But not the info I searched for (no offense meant). Some users report their Windows 10 key (OEM) is stored within the BIOS and activates Win10 after you enter no key during setup. I am searching for options how to do it. You know any? EDIT: Serg008 already told me about the token (genuineticket.xml) trick, but I want to hardcode it into my BIOS.
The key is injected into the UEFI by the OEM. Each key is unique. If you purchased without an OS, no OA3 key would exist in you UEFI(BIOS). Read here: https://forums.mydigitallife.net/threads/windows-8-preinstalled-licenses-aka-oa2-2-and-oa3-0.34580/
Getting a "module count mismatch" error when trying to update the Intel microcode in the Shuttle SH67H3 EFI. I don't want to double-post, so here is a link to my original post. Thanks in advance! https://forums.mydigitallife.net/threads/need-advice-for-shuttle-sh67h3-microcode-update.77073/ UPDATE: I was able to use UEFITool to replace the microcode module successfully. I now have the latest Intel microcode for Sandy Bridge and Ivy Bridge.
Oh... I know it's been manually modded before, in fact I've used one of those (or maybe even other) with 2.1 in the past in this machine; but I thought to report it because it seemed to be a bug in the app somewhere and I wanted to help iron it out. Thanks anyway Serg008!
Just to add, you can also find the correct name by searching the BIOS file with a hex editor and looking for .rom/.bin/.fd. The correct entry is in the "bootblock" and also the only occurrence you will find. Under Linux you can use: strings <filename> |grep <search term>
After getting a successful ROM file with the tool from a DELL bios file, how do I flash or convert that file?
This tool has helped me countless times, however I tried fiddling with a recently acquired Asus strix X470-F to no effect - I always get "unable to resize module" with the line above stating the module is 25 bytes too small. Tried all variations, with and w/o RW file. Any ideas?
@eSwYeL Yes, which mobo are you using? @maususys Which mobo/PC are you talking about? @Thisisntmyrealnameanyway Which method have you used?
SLP manufacturer string doesn't work for those new firmwares. I have also stepped into that trap. Wanted to cover all bases, but the mod failed. Ditched SLP 1.0 string, and, successful.