sorry,bad eng not slp addr problem,phoenixtool185 add slp string is ok,but reitegrate a062 module all slp string is missing. u can check like this,at "Advanced" tick "Allow user to modify other modules" View attachment 9677 when the tool popup windows msg,hold on,use winhex open a062 module at "DUMP" folder,u will see View attachment 9675 slp string is add ok,now u press "ok" continue mod, use tool select modded bios,use winhex chechk a062 module at "DUMP" folder,slp string is missing View attachment 9676 use slic toolkit post i mod slp1.0 results,thks
BIOS CPU microcode If I replace the existing cpu*.bin code in the .hdr (7168-48=7120 bytes since first 48 characters don't exist in the .hdr) with a standard (2048 bytes) cpu*.bin code and gzip the new .hdr file, name it bios.gz, boot it up with FreeDOS and run "d4700a10.exe -readgzfile" would it attempt the flash but possibly give a CRC mismatch error which can be corrected I believe? Do you know which 2 CRC's? Can the CPUID be just 4 characters? So 0f34 & 0f65 would just be 00000f34 & 00000f65 from the cpu000*****_.bin file names (characters 4 to 11) from the decoded microcode.dat update package? Are the CPUID's even required if I'm going to hack my BIOS as I described?
thanks for reply and reason for phoenix tool failing-I might have another shot using winhex although as I said previously, I bricked my bios somhow after trying to modify a062 module myself using winhex but your multil slp version works fine
Hi QTM, I'm struggling with the same problem with a VMWare Linux bios. Do I understand correctly that this is a Phoenixtool bug ? As you can see from the attached slic toolkit dump, there seems to be some SLP1.0 strings in the bios but only at a invalid offset. ildoc View attachment 9720
Folks, I have been pretty busy at work and home recently. I have had a trawl of the thread and will try to summarise outstanding issues here - in no particular order. 1) MXM parsing (@ .NetRoller 3D) - could you point to more info?? why would we want to do this?? 2) Better support for SLP1.0. Just to confirm these offsets: +BB0 "ASUS_FLASH" -CF0 "SAMSUNGPC" +A7E "BenQHub" -12D2 "LG Electronics" -C00 "Sony Corporation" +B75 "MSI-PC" or "MSI-PenNote" -BC0 "Gateway" -BC0 "Tektronix" -BCA "Dell QuantaDell Computer" 3) Inserting modules (@KaminoReal) 4) Replace already compressed modules (@Apokrif) 5) Encryption of HP EFI 6) Empty module replacement as default for Acer 7) New Asus patching Could someone just clarify which asus need a dyanmic mod (with lock patching) and which need the bios dumping from ROM and various bytes modified?? Do all ASUS EFI work with this new method?? Is there a consistant pattern in which bytes need modding?? Anything else i've missed?? Andy
Andy, I’ve an idea how to do #3 & #4 in "user friendly manner". Not posting yet - you might come with better approach. PM me when you are ready to hear mine
andy for me personally-I was having problem with slp string in asus p867pro bios 1600-it just did not work. Mdl member qtm kindly helped me out and he thinks the reintegrate a062 module all slp string is missing in tool 1.85-see post #1936 this will explain thanks again for a great tool
bad eng However, those positions must be determined to be "00 00" or "FF FF" and enough space to write slp string, Otherwise brick
Yep. Done that already. I have implemented SLP support for those strings Added support for already compressed modules Fixed Acer emtpy modules THe code is already there to insert new modules, I just need to add something. New release soon!! Andy
Hi, Andy! I have a trouble while trying to build Thinkpad X220 Bios using your great Tool. The error is already known: Unable to compress... I tried 1.85 and 1.86b4 - same result. I had a go inside the issue and realized what is happening. This BIOS has Tiano compression method. I did measurement and realized that the EFIDC.exe tool compresses the BIOS file (DUMP\TEMP.ROM) using Tiano within 15 seconds. However after 10 seconds the Tool kills EFIDC process and says "Unable to compress ..." Please implement a wait till the compressor's process complete its work. A constant wait is not a good idea here. Otherwise it will be connected with CPU speed. However on my C2D 2.4 (locked at 2.4) it compresses 15 sec.
Hi Just to keep u all informed. I have 'happened' accross a copy of MMTool for EFI. I can't say where or share it or output unfortunately. But I am setting up my tool to insert/extract modules in the same way. I am doing it through the tree view you see when u press verify, as that should be easiest. But it will be possible through the manual mode by putting in the DUMP directory as well - although each will work in a slightly different way. Should be out in the next few days. Andy
It already does check to see if completed, but a few of the tools it runs have a habit of randomly freezing, so unfortunately the absolute time check is needed as well. I will increase to 20sec. Andy
Heh, I just put my C2D's SpeesStep into 600 Mhz mode and measured time of the compression. The result of this bios is 27 seconds! Please set this timeout at least to 60 seconds. You can put "wating 60 seconds till finish of the module compression..." message into log window during this wait. UPD: Or you can remove this timeout in RunEFIDC method only, and keep timeouts for other tools you run.