ASUS motherboard adds SLIC2.5 and MSDM table tutorial

Discussion in 'BIOS Mods' started by angelkyo, Mar 16, 2019.

  1. botva

    botva MDL Junior Member

    Apr 10, 2012
    54
    10
    0
    #41 botva, May 14, 2019
    Last edited: May 16, 2019 at 05:24
    sorry, unfortunately, it already work as remote server, so i can't make dump, but you can use most of bios tool to find it. this information is not undercover.
     
  2. limurphy

    limurphy MDL Novice

    Jul 19, 2011
    12
    1
    0
    It's OK. I am trying to find out why my asus P8H61 UEFI bios does not work by using the tool which provided by angelkyo . I just can't insert MSDM table into the bios .
     
  3. Flipp3r

    Flipp3r MDL Expert

    Feb 11, 2009
    1,581
    676
    60
    Why would you want the MSDM table anyway. You don't have a valid Windows 10 OA3 key to inject to it anyway. The only useful thing is the Slic for server/win7 activation...
     
  4. limurphy

    limurphy MDL Novice

    Jul 19, 2011
    12
    1
    0
    As you said it for server activation. I can insert a MSDM table into legacy ami bios but not uefi one.
     
  5. Flipp3r

    Flipp3r MDL Expert

    Feb 11, 2009
    1,581
    676
    60
    I said SLIC. Inject the SLIC only. Forget about the unneeded MSDM table..
     
  6. limurphy

    limurphy MDL Novice

    Jul 19, 2011
    12
    1
    0
    I know how to mod slic,thank you.
     
  7. ssabb3

    ssabb3 MDL Novice

    Jan 31, 2016
    4
    0
    0
    Trying to add Fuji2.5 to an asus P8P67-m motherboard.
    Using updated/correct slp25.bin.
    Running cmd as admin, typing:
    SLPbuilderX64_3_6.exe /oa20:SLP25.bin /oemid:FUJ /oemtableid: PC /act:9C134SIMF51GYI8HEDJ2F47ZWOA3
    The command creates a file, arbitrarily named string.sys 16kb large. In my case 690b33e1-0462-4e84-9bea-c7552b45432a.sys
    Then the prompt returns stating;

    Invalid activation - program abort!
    Retyping the command creates the create ASIO driver file error, I think this is due to the file just created, which is impossible to delete, the command fails.

    Since it is a headless server, I tried to save time by not reinstalling a graphics card & flash bios normally. As such, I did not clean the existing dell slic 2.4 prior using:
    SLPbuilderX64_3_6.exe /clearoa30
    And due to heedlessness, I haven't enterd bios to check the security settings, I know I run UEFI.

    Any hints about the error?

    /ssabb3.
     
  8. botva

    botva MDL Junior Member

    Apr 10, 2012
    54
    10
    0
    read this
     
  9. ssabb3

    ssabb3 MDL Novice

    Jan 31, 2016
    4
    0
    0
    #49 ssabb3, May 16, 2019 at 05:47
    Last edited: May 16, 2019 at 12:07
    Thanks. I found that info since now I put a gfx card into the computer and flashed a phoenix-tool modified bios (slic 2.5) using the "new module" method.
    Only to find that the slic info hadnt changed since serv2016 was still activated.
    So I must have modified the previous bios version using also the "permanent" new-module method. So the Fujitsu 2.5 didnt write over the existing 2.4 dell, then really fulfilling the "permanent" denomination of the method. Surviging a flash with a new slic.

    So I am planning to do this:
    1. Download amiflash, extract the Aptio Afuwin64 folder.
    2. . Open it and run AFUWINGUI.EXE. Click Open and select modded bios file.
    3. On the opened SETUP tab uncheck all boxes and check only box #2 under "Non-critical block" caption. Press Flash and wait till it's green.
    4. Reboot. Enjoy.

    I guess the slic is removed then, and could be put back using another "permanent" new module, or oa_slpbuilder, or modify bios using the "dynamic" method & flash back.

    I will update the status once tried.

    Update:
    AptioV5 wingui64: read bios. Deselected "main block", only selected "block 2". clicking flash prompted me to use AptioV4 (too old of a motherboard I guess)
    AptioV4 wingui64: complains about it being impossible to flash ME Firmware. Flash button greyed out regardless of settings within the gui.
    Crap.

    Perhaps trying from DOS:
    afudos.exe biosfile.rom /K1
    from the dos-manual, where K means "Program the n'th non-critical block (n=0-15)"
    Programming Specific NCB Block – /Kn

    /Kn command is designed to program a specific non-critical block, or NCB block. AFUAPTIO
    would search ROM and identify the first NCB Block found as K0, and the second one as K1, etc.
    Therefore, command /K2 would program the third NCB Block found by AFU.
     
  10. ssabb3

    ssabb3 MDL Novice

    Jan 31, 2016
    4
    0
    0
    #51 ssabb3, May 16, 2019 at 16:53
    Last edited: May 16, 2019 at 16:58
    So, summary: running activated server 2016 using new Fuji 2.5 slic. This is the whole story.
    1. Existing slic dell 2.4. Probably modded by me using "new module" 2018 for headless server install.
    2. Tried adding fuji2.5 using SLPbuilderX64_3_6.exe, gave errors, posted here.
    3. Phoenix-tool 2.73 to modify latest bios, added fuji25.bin, "new module".
    4. Flashed this morning using bios easy flash.
    5. Server Still activated after reboot. rw-everything indicating still Dell 2.4 slic.
    6. Searched the net, eventually found info on Aptio, AMi flash, winflashgui with "non-critical-block 2" to remove permanent slic mod using "new module"
    7. Got similar reply from my post.
    8. Downloaded Aptio version 5, extracted winflash64, started gui, loaded Asus-standard-bios of latest release, deselected all flash options except non-critical block2
    9. Error. Too new tool for my old Bios.
    10. Downloaded Aptio 4. Same procedcure as above. New Result: "cannot flash something ME Firmware. Flash button grey.
    11. Tried 32-bit version. Did not even start on my Server 2016x64.
    12. Tried setting runas-win8,. win7 on the gui-version. Same error A1 "something ME", i.e. no effect.
    13. Tried AFUWINx64.EXE from prompt within windows. Possible to read & save the bios using /O option.
    14. Instead of hassling with bootable usb, I went ahead and tried AFUWINx64.EXE expecting it to fail.
    15. Tried typing AFUWINx64.EXE unmodded-biosfile.rom /K1
    16. /K1 is for block 2 since the command-prompt version starts with 0-15 but the wingui shows 1-16.
    17. Text indicating success. WTF!
    18. Reboot. Windows server not activated. Halleluja. Never been that happy seeing non-activated status.
    19. tried SLPbuilderX64_3_6.exe, since the slic must be gone, I flashed block /K1 using original bios, right!?
    20. Same error as before. WTF.
    21. Ew-everything indicating fuj PC slic of version 2.5
    22. WTF!!
    23. slmgr.vbs -fujitsu-xrm.mrs whatever the filename is.
    24. slmgr.vbs /ATO
    25. Windows Activated.

    So, success. But I have no clue what the "non-critical block 2" actually does, and how the fujitsu 2.5 slic was there after I used the original unmodded formware to flash block2. The logical would be that flashing block2 with unmodded fw would create an empty slic, needing reflash or as I intended; use SLPbuilderX64 to add it afterwards, and flashing block2 using a modded bios would add the slic infp from it into the seldom written area of the bios, i.e. block 2.
    In this case, the flash this morning with modded fuji25-bios did not manage to overwrite the dell slic. Flashing block2 from prompt within windows using un-modded bios made the dell 2.4 disappear, and the already flashed fuji2.5 to appear.
    Or did the SLPbuilderX64_3_6.exe command manage to write the fuji25 slic eventhough it gave the same error as before when it did not manage to write the info. So strange.

    Any1 that can explain what actually happens? Writing block2 does does what exactly? It did not write the slic info, but removed the "protection" of the dell2.4 so the flashed fuji2.5 became visible.

    Now I will update to 2019 to get rid of these unstable looooongish updates. Halleluja*2
     
  11. botva

    botva MDL Junior Member

    Apr 10, 2012
    54
    10
    0
    #52 botva, May 18, 2019 at 07:54
    Last edited: May 18, 2019 at 17:00
    ssabb3,
    you need to operate with same bios versions, because blocks may shifted depends of it.
    so, if you want to exactly clean from any slicks, msdn tables etc., you need to download last bios, flash it and clean all blocks except 1 via afuwin by using the same bios file.
    i'm little bit misunderstanding about your bios versions, but i think it was different.