Tool to Insert/Replace SLIC in Phoenix / Insyde / Dell / EFI BIOSes

Discussion in 'MDL Projects and Applications' started by andyp, Nov 26, 2009.

  1. Asparagus Lover

    Asparagus Lover MDL Senior Member

    May 17, 2019
    334
    69
    10
    Cannot replicate this error. Tried PRIME-B660M-K-D4, PRIME-B660-PLUS-D4.
     
  2. DrunkF

    DrunkF MDL Junior Member

    Jun 15, 2010
    78
    23
    0
    Thanks for trying - that is quite bizarre. Anyway, tried to reproduce with the BIOS you mentioned:

    Downloaded "PRIME-B660-PLUS-D4-ASUS-3010.CAP". Is this the version you tried? Or maybe much older?

    PhoenixMod 2.73 from here
    Manufacturer: ASUS
    SLIC file: Dell 2.6 SLIC binary from here
    Key file: KEY.TXT as included
    Method: New Module

    Main points from log here.

    --
    Finished Extracting
    LZMA and EFI module compression methods used
    EFI / Insyde BIOS
    Full SLIC table found in 9E21FD93-9C72-4C15-8C4B-E77F1DB2D792_42.ROM at 71885C <- should be "A1902AB9-5394-45F2-857A-12824213EEFB"
    OEM/Table IDs identified are:
    1. A M I OEMSLIC
    Complete SLIC (2.0) (A M I OEMSLIC ) (x1)
    SLIC digital signature valid
    Are you SURE you want to modify without a RW Everything report <- Yes
    --
    Finished Extracting
    LZMA and EFI module compression methods used
    SLIC module size is 374 bytes
    The SLIC checksum has been corrected to 0
    OEM Activation 2.0 SLIC
    No SLP2 module

    I've attached the full log. Can you see any differences in what you are doing and what I am doing?

    AFAIK seems clear it is not finding "A1902AB9-5394-45F2-857A-12824213EEFB" as per PhoenixTool docs but "9E21FD93-9C72-4C15-8C4B-E77F1DB2D792" instead that it does not modify.
     

    Attached Files:

  3. DrunkF

    DrunkF MDL Junior Member

    Jun 15, 2010
    78
    23
    0
    I've also tried:

    1st BIOS release: "PRIME-B660-PLUS-D4-ASUS-0418.CAP" -> same error, no SLP2 found

    Method: Module -> Error: Unable to resize Firmware Volume
    Method: Dynamic -> Error: Module count mismatch
    Method: DMI -> Error 9: Index was outside bounds of array
    Method: Code -> Error: Unable to add SLIC code

    The only one left is Method: NVRAM for that I need to dump the actual BIOS and modify it and then find a way to flash it back - likely with programmer.
     
  4. RobrPatty

    RobrPatty MDL Expert

    Jul 23, 2009
    1,287
    598
    60
    Didn't work for me. Tried with hacked PhoenixTool. used flashback & now lost bios access. :eek:
     
  5. DrunkF

    DrunkF MDL Junior Member

    Jun 15, 2010
    78
    23
    0
    What happened with PhenixTool - did you follow the procedure like above and it all went well with no errors at all - but then when you flash it did not work?

    I never needed to use flash-back to comment on it - but always used the standard flash (EzBIOS Flash) in the BIOS itself.

    I use Intel platform (not AMD), so I only used Asus Z390, Z590, X299 (old BIOS thus original PhoenixTool) and new Asus B660, B760 (new BIOS thus modified PhoenixTool) but they have all worked just fine. I've had issues modifying some BIOSes but once they did build flashing them has always worked.

    I think the idea is to always upgrade to the latest original BIOS if not already on that then flash over it the SLIC-modified BIOS of the same version through the normal BIOS EzFlash. This way it should only add the new module with the SLIC blob and not anything else.
     
  6. RobrPatty

    RobrPatty MDL Expert

    Jul 23, 2009
    1,287
    598
    60
    #4308 RobrPatty, Aug 30, 2024
    Last edited: Aug 30, 2024
    I followed instructions above & SLIC was built successfully but did not take. So then went to flashback.
    Maybe because I have an Asus ROG CROSSHAIR X670E EXTREME board.
    Great now I have to haul her down to the local shop. You win some you loose some.
     
  7. RobrPatty

    RobrPatty MDL Expert

    Jul 23, 2009
    1,287
    598
    60
    My board has a bios safe boot button. Got me back into bios & everything is back to normal. whoooow
     
  8. pm67310

    pm67310 MDL Guru

    Sep 6, 2011
    3,376
    2,554
    120
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. DrunkF

    DrunkF MDL Junior Member

    Jun 15, 2010
    78
    23
    0
    That's a pity. Perhaps another option would be to run a KMS server in a VM somewhere on your network and activate using it? If you set up a "_kms" forwarder in AD/DNS to it then it will activate automatically.
     
  10. pm67310

    pm67310 MDL Guru

    Sep 6, 2011
    3,376
    2,554
    120
    Or use kms38 to activate up to january 2038
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. RobrPatty

    RobrPatty MDL Expert

    Jul 23, 2009
    1,287
    598
    60
    Already used kms38. job done
     
  12. Drak_iaji

    Drak_iaji MDL Novice

    May 22, 2022
    17
    1
    0
    I encountered a similar issue where PhoenixTool does not work on MSI H110M PRO-V, but works on HM77 and GA-B85M-D2V (rev. 3.0).
     
  13. DrunkF

    DrunkF MDL Junior Member

    Jun 15, 2010
    78
    23
    0
    Check out the "fix" above (checking for and modifying a different GUID) - so far it has worked on the new ASUS BIOSes that I've tried.