Thanks Flipp3r, that makes perfect sense. I wasn't sure running the .exe would leave the files expanded on the USB.
hi: there are so many stickies figured I'd ask this question here. hope it pertains. Is there a way to run the slic tool to see what slic is in the bios without being booted up to windows? in other words if windows vista or 7 are corrupted can you boot to either a cd or flash drive (like you can oembios for XP) and check out the current slic table (none, 2.0 or 2.1)? regards...
===> u can use SLIC tool to read whether the SLIC in the the UEFI/ BIOS ROM or not after boot into Windows. So far I heard NO any offline tool can read the SLIC data without booting into Windows. *** The safe to write the MOD UEFI/ BIOS ROM is to write the same version UNMOD file first and then write the MOD file. eg. 1.1 in the PC. u want to write 1.3 mod bios. U should write the unmod 1.3 and write the mod 1.3 later. That can help to avoid the corrupted. **** *** Please note that some OEM has SLIC locks in the UEFI / BIOS and the lock changes each time after the new release of UEFI/BIOS. ANDY's tool sometime may fail to mod despite the mod is said as success. If u find out such issue, u should tell ANDY. In my experience, the tool are very safe, NO CORRUPTION in my M/B have been found after I mod the UEFI files in 5 M/Bs. So far I know MSI has lots SLIC locks to prevent the unauthorized mod. ***
Hi Andy, I have modded bios P9X79-PRO-ASUS-3009 with PhoenixTool 2.11 Manufacturer: Asus Slic File: ASUS.BIN SLP File: empty RW File: empty Didn't change anything in Advanced or Structure and then update bios with ASUS EZ Flash 2. I can confirm it's working. If i add, SLP File: Asus.txt I get "Security Verification Failed" when i try to update with ASUS EZ Flash 2. Is it not possible to add SLP with the new .cap bios?
Hello, Using v2.04 or earlier versions would produce BIOS files with identical binary contents. Version 2.05 or later like v2.11 would produce BIOS files with another identical binary contents but the binary contents are different from v2.04 or earlier versions. MMTool of course have no issue to load both images with different binary contents. I used to mod the BIOS for my mainboard using v2.04 or earlier. I still have no idea whether v2.11 would work because I haven't tested it yet. My question is : Which version to opt?
Hi andyp and all, First of all I want to thank andyp for all the great tools he created and shared. I recently updated my BIOS from Award to AMI UEFI, used Phoenix tool to insert GIGABYTE SLIC 2.1 with module method. The tool reported that SLIC added successfully. After flashing the bios, windows 7 crashes with BSOD on startup, but boots in to safe mode without problems. I have windows 8 on my pc as well and it has no problems to boot and works fine. From the described above I suspect that windows 7 crashes at the point when it tries to verify the license, because it is not validating the license in safe mode. When I tried modding with SSV2 method, I got “Unable to add SLIC code” error message. -Manufacturer: GIGABYTE -Motherboard Model: GA-Z68X-UD4-B3 -Bios revision: U1c -Bios Type: AMI UEFI -RW Everything Report: If you’d be so kind, please look at this issue and advise me how to mod my bios, so it will work properly.
Hey, Andy! I know you are busy, but I will think it's worth reporting. Dell's Phoenix SecureCore Tiano BIOS is packaged the following way: - BIOS1.WPH which is used to flash from WinFlash consists of RAW capsule and a PFlash.efi rom as well as a padding layer. - The RAW capsule has to be decompressed by PhoenixTool again to reveal all the modules of the actual BIOS. The problem is that after I select Dell as a manufacturer and in Advanced set 'No SLIC' and 'Allow user to modify other modules' in PhoenixTool 2.11 after pressing Go it says 'Invalid Firmware Volumen Header' when altering the "second stage" of BIOS1.WPH capsule (ie the RAW part of it). If however I try it with version 2.02 it works perfectly. Then just out of curiosity I tried recompressing the RAW part with v2.02 and compressing back to BIOS1.WPH using 2.11 and it didn't give any errors. BIOS version is not important .. it happens with every version I've tried. But v2.02 works perfectly fine.