Hello, Previously I have modified my BIOS to include SLIC 2.2. Everything is working fine. Now I saw there is new BIOS for my mainboard, so I want to upgrade my bios. I wonder if SLIC mod will be preversed or I have to modify the new bios rom again?
Thanks for your answer. Is there a way to check what method I've used? I still have my BIOS .CAP file. Can I open it with MMTOOL or something to see if I used New Module?
Yep, open the modded bios in MMTool. If there are 4 unnamed modules after DummyMSOA, then it was modded using New Module method.
I out of luck. I got only 2 unnamed modules after DummyMSOA. Looks like I have to patch my new bios again. I have few questions in my mind: I have to do use phoenixtools? If my SLIC is Dell, on Manifacturer field I pick Dell, right? phoenixtools picks Dynamic because It seems I have some "generic" SLIC in the original bios. I wonder If I should go with New Module method to preserve SLIC on updates?! If I choose to. What is that Key field? Can I leave it empty or with wrong cd-key? Also RWeverything report need to be from unmodified bios? So I have to flash my new _unmodified_ bios and take report then? I guess I can't use my current modified bios for report? Some more questions: I am now with WS2012, I am planning to install WS2012R2 soon. What SLIC version should I put in my bios. Dell 2.2 should work for R2 too or if I put 2.3 will it work for WS2012 until I upgrade? Can I inject MSDM table in my bios to avoid event log 1058? (for R2)
I finally decided to go Dynamic method. I modified original .CAP file to include DELL SLIC 2.3. For Manufacturer I select: Dell. No SLP and no RW report added. The problem is that EZ Flash 2 wont let me flash that .CAP file. So I went USB Flashback method. First I flashed virgin .CAP file, then I flashed the modded .CAP file. The problem now is that my WS2012 is not activated anymore. SLIC Toolkit reports: What I am doing wrong? Maybe modded BIOS USB Flashback failed, because of the same error: "Security Verification Failed"?! Or maybe I should select SLP?
While trying to solve my problem I saw this post: h(t)tp://forums.mydigitallife.net/threads/43111-P8Z77-V-PRO-Security-Validation-Failed?p=724687&viewfull=1#post724687 If you can point me to more specific instructions I would like to do it. Because later when I want to eventually wipe my SLIC i prefer to do it just with flashing virgin BIOS, instead of playing with FTK/FD44Editor. Thanks.
Thank you for providing this mod. Can you tell me how you made it? I can test later today when I get back home.
FYI, the information is true but only applicable for newer ASRock bioses. You may compare the modules of Serg008's mod to determine which modules need hex-editing.
I already did some comparison. I opened both .CAP files with MMTOOL. Made a reports. And compared modules. Looks like my MSOA is different size 00132E, while Serg008 is 001200. This makes comparison really hard, because files are completely different. I guess I am doing something wrong with the original modification with PhoenixTool. That's why I look for help. In my MSOA file I see string "ALASKA" while in Serg008's they are replaced with DELL....
When I modify my BIOS (for mainboard P8Z77-V LE PLUS) using New Module method, and after that I open modified BIOS by PhoenixTool itself. It says that I still have the generic 2.0 SLIC. Code: Complete SLIC (2.0) (A M I OEMSLIC ) (x1) Pubkey and marker (2.3) (DELL PE_SC3 ) (x1) Anyway I tried flashing the BIOS and SLIC toolkit said "NO SLIC TABLE". Later I succeded to inject SLIC into BIOS using Dynamic method. However I wonder why phoenixtool is unable to generate New Module format BIOS for my board.