note to moders, Starting with Acer Aspire 5552G 2.13 and Acer TravelMate 5740 1.23 a new SLIC protection/activation have been put in place by ACER. How to recognize these bios: When AndyP tool pause at the end of bios dump, we can see that the tool inform of 2 empty modules. View attachment 9529 8325948F-03E7-468E-96D8-7A8639AA8B54_1_738.ROM and A4E128E7-3D90-4BAA-B6C9-714C6B95AF40_1_741.ROM in this example, The name of modules may differ with the model. 8325948F-03E7-468E-96D8-7A8639AA8B54_1_738.ROM have a size of 156 octets and must be filled by ACER pubkey Code: 00 00 00 00 9C 00 00 00 06 02 00 00 00 24 00 00 52 53 41 31 00 04 00 00 01 00 01 00 B3 6D 83 60 8D 83 65 6E E6 4B A7 6F 38 04 31 C1 E2 45 BF 34 66 1F 17 91 7F 5C 15 12 B7 01 4D 57 6D 8E AE 6B E4 CC F8 A0 E1 BB 79 FF 08 53 E3 77 E7 D4 70 5E 5C EF 6F 81 DD 1B 5F 30 E2 99 9B B9 D0 93 46 AB D8 17 7A E0 F0 A7 4C 32 D4 91 86 BA A1 6C A2 3C 73 CF 86 2D 95 9A 06 50 F3 F7 7E 06 5B 5E 27 66 01 3A 31 9F 0C B1 91 96 49 5C CC 81 BA 77 32 52 B2 10 5D 5B CA DE 9D 25 90 95 F7 97 A4E128E7-3D90-4BAA-B6C9-714C6B95AF40_1_741.ROM have a size of 182 octets and must be filled by ACER marker Code: 01 00 00 00 B6 00 00 00 00 00 02 00 41 43 52 53 59 53 41 43 52 50 52 44 43 54 57 49 4E 44 4F 57 53 20 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 49 90 AC 34 3B 98 88 52 62 2C FB 25 A8 A9 A0 7D 2D 12 70 EE D5 9A 7C CF 0C 83 B4 29 1B 55 3B 88 A5 F7 E6 29 A9 2C E7 17 5D 7A EE 38 4D 27 E0 A9 69 7C FC 20 4A 68 0B 5D 83 AD E5 D6 6E 49 C1 66 28 E4 D4 CE 72 64 A1 7C BE 93 AD 64 32 DA CC 72 24 47 FE B4 97 87 01 55 A0 5D 2F EF 06 93 E8 87 84 59 D3 9B 25 53 27 E7 CA 75 65 CF 0E 40 C9 3B AA 03 F2 83 7E 27 E7 CA 47 A4 4B 1F C5 77 DF 8C These 2 modules are in a protected zone of bios, platform.ini must be modify as follow: [ForceFlash] ALL=1 and option /all must also be used for flas**t DOS utility. Hope that will help.
Uefi Partition I flashed a patched bios rom into my asus p8p67 evo board and after installing windows 7 x64 and doing the usual activation procedure, everything worked fine. So I decided to wipe windows 7 x64 and reinstall using the uefi installation method which adds a uefi system partition at the start of my HDD. after everything installed, I tried to activate and windows wont activate, my toolkit just says that the slic in the bios is wrong. I'm assuming this is caused because the ACPI table is now on the HDD in that uefi partition and it no longer has the patch that my bios rom has. I decided to retest w/o uefi partition install and it still works. So my question is, does anyone know if there is a way to get windows activated while running windows with a uefi partition?
Nevermind to my last post. I just figured out what went wrong. Apparently you must grap a RW everything file from the windows with the efi installation for it to activate correctly. So if you mod in non uefi windows it will only activate not uefi windows.
Just to be clear, the option is already there (in advanced page), its just not ticked by default. Andy
I have successfully modded the Asrock z68 pro3-m bios 1.20 using the methods described here and using the fantastic phoenix tool. There are some tricky steps I have to spend time to figure out but it works in the end.
Just a quick summary of what I did: 1. Get just the BIOS ROM file. 2. Flash it using the BIOS's Instant Flash feature. 3. Reboot. 4. Go to BIOS and make sure it has correct setting. For RAID, you need to set it to RAID again. 5. Run the rw tool to generate ACPI table. 6. Run Andy's phoenix tool to generate the new BIOS. 7. Repeat 2-4. Good luck!
very simple,for asus,msi, biostar,asrock,onda,colorful...all uefi bios mod this 5 module ,no need owner machine rw
Hi You are replacing some AMI ALASKA strings with OEM/Table ID manally. If you use a RW report the tool does this automatically. Andy
Sorry for cross posting, I think it belongs to this thread… Update CPU microcode module with Andy tool: I’ve never done it, but it should be piece of cake job for Andy tool. IMO, all we have to do it is to extract CPU microcode module from any of the latest BIOS and replace it our BIOS. I guess, it’s completely independent module - nothing else needs to be updated with it. If somebody knowledgeable could put a little tutorial together - everybody will appreciate it. Something to think about: Is there a way to parse CPU microcode to determine what CPUs are supported to make sure we add what we want and don’t drop out current CPU by mistake?
For more information on the Intel CPU microcode update, you can read the Intel® 64 and IA-32 Architectures Software Developer’s Manual Volume 3A, chapter 9.11. In Phoenix BIOS, the CPU microcode update are located in UPDATE0.ROM or _C0x.PEI. x stand for 0, 1 & so on. (These last two statements are strictly for Intel CPU microcode update) In this module, you can find more than one CPU Microcode update. Each microcode update is for specific CPUID. It won't caused any serious problem if you mistakenly removed CPU microcode update for current CPU. You'll just get warning message regarding missing microcode update whenever powering on the computer. Just need to press <some key> to resume. For AMD, I dunno.
Interesting... I do recall Dell boards display message "unsupported CPU" and hung. Does it mean, even if we update a BIOS CPU microcode section, it won't boot still? The behavior might depend on BIOS brand (Phoenix, Dell, etc.) I guess, we never know until we try