Overview
** This tool is freeware and may not be sold or redistributed for a charge **
This tool inserts a SLIC table into Phoenix (original and Lenovo) and Dell BIOSes and EFIs.
There are 3 main code paths:
- One for Dell
- One for Phoenix (old and new, including Lenovo)
- One for EFI (and Insyde)
Exactly what happens varies for each one. Generally dynamic means an existing SLIC is updated and SSV2
means a NEW SLIC is inserted.
Dell
- SSV2 - a new SLIC is inserted in one of the first modules
- Dynamic - an existing SLIC and any OEM/Table ID strings are updated
Phoenix
- Module - for interest only - uses the Phoenix tools PREPARE/CATENATE (old) and FI/FP (new) - this often
screws the bios and causes bricks
- SSV2 - a new SLIC is inserted in a new ACPIxx module
- Dynamic - an existing SLIC is updated, OEM/Table ID strings updated, locks removed
EFI (All)
- Module - a pubkey and marker are inserted as two new modules with a typical GUID (this was how Insyde
was originally done - but still works for some EFIs). In addition for EFIs, if it is not already present, the
SLPSupport module (GUID 4C494E55-5849-5342-4554-544552212121) will be added.
- SSV2 - a module is modified with code to build a SLIC table at boot. This can cause a brick and is no longer
first line.
- Dynamic - an existing SLIC table is modified and strings updated.
EFI (ASUS)
In addition to the above methods, there are 3 ASUS specific methods:
- NVRAM – The NVRAM is modified to contain SLIC data. This method requires a dumped BIOS (ie. It is
individual to the computer). It is also persistent and survives subsequent flashes.
- New module – If a SLP2 module (GUID A1902AB9-5394-45F2-857A-12824213EEFB) is already present then
a combined pubkey+marker module is added. In addition a signing key is added (significance uncertain).
- DMI – SLIC is added in the DMI region.