My goal is to generate my own SLIC, OEM SLP Key, and certificate from machines that are in my possession I have a new hp pro 3130 desktop that came w/ windows 7 pro. I copied out the SLP key and the Certificate with 7tokens - it seems as if there was no problem. The Certificate does not match with any of the BIOS SLIC 2.1 mods that come with the unofficial the AMI tool download. Is there any way I can extract the SLIC 2.1 string from my current BIOS to apply on older BIOSes?? I downloaded the bios from support.hp.com and when I extracted it, I have the following files: AFUWIN.exe......184,320 Flash.bat.......23 ion6.16........2,097,152 sp52775.cva.....1,351 Ucoresys.sys....15,432 UCOREVXD.VXD....7,840 UCOREW64.SYS....14,632 when I load ion6.16 in the AMI tool it detects that it already has SLIC 2.1 so I am assuming that this is the BIOS file. BIOS d/l link: http:||h20000.www2.hp[dot]com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=12454&prodSeriesId=4191693&prodNameId=4191694&swEnvOID=4059&swLang=13&mode=2&taskId=135&swItem=vc-93306-1 I would like to get the string from the BIOS to match with the certificate that I pulled off the same computer. Is this possible?
I tried to open the ion6.16 with SLIC toolkit and I get "Error Read Ext SLIC File Error !" the ami editor recognizes this as a SLIC 2.1 bios but when I open the file SLIC Toolkit I get that error. Is there any way to extract out of that file or do I have to actually run this program on the computer?
SLIC Dump Toolkit, OEMDump and Windows Loader can rip the slic from the bios of the physical machine, not from the bios image file. To get the slic from the bios image file, u need to search in the modules of it by any suitable bios manipulation utility. Freestyler may help you to do so
Thanks guys, I was able to copy it off the hp with no problem. I tested it on asus mobo and now 7 is activated. I was a little worried about using the mmtool method to extract the SLIC - I didnt want to kill the bios I was going to flash. But I will try the mmtool method and compare it to what was pulled w/ the OEMDump tool.