@Donovan6k, that extra stuff is a file section header (0x18 bytes in section, type - RAW). Just remove it before disassembly, if you need. I think the new format is actually better. @andyp, am I right that modified ASUS BIOS can be signed with a key present in OA30.txt file and then flashed by EZ Flash and other ASUS BIOS flashing tool? Is any type of modification (like 0xE2 MSR unlock, to name a few) possible or just "New Module" method?
@CodeRush Thanks for the header explanation. I mainly just don't want to rewrite parts of my tutorials to fit the new format, but I guess it can't be helped @andyp Thanks for the quick response. Got things cleared up. Also who's the author of hewprsa.exe? I'd be very interest in talking to them
Just to be clear there should NOT be a difference unless you are looking in the DUMP directory whilst manipulating in treeview They are the file section header (internally I refer to them as submodules just because I figured it all out manually from old Insyde BIOSes before the EFI specs where published with the correct nomenclature) A
Thanks for fast reply, but I run the bios update in dos "phlash16.exe /bu /v /swap=no bios.slic" and it says "BIOS ROM file may be corrupt (Extended checksum not zero)". Is it ok to flash? I try to make backup but it won't allow me without bios.wph?? edit: running in dos because I installed x64 windows 7 and winphlash doesn't seem to work. edit2: managed to successfully flash and activate using BartPE. Thanks very much Serg008!
how to remove slic 2.1 with new module use phoenixtool218 Tool I Use this method : Transfer your board data with FD44Editor from BIOS backup to vanilla BIOS file and then flash the modified file with "flashprp" command using FTK, and your "permanent" is no more. I get this Error 280:failed to disable write protection for the bios space my motherboard is asus B75M-A-ASUS-0602
I just tried v2.18, been using v2.13 and missed the other updates so I don't know since when this occurs, but I noticed that the modules no longer get split up into it's separate parts, i.e. actual data of the module, header, name, tail... Is this behavior intended? I prefer the old behavior since it makes it easier to work with the actual content of a module without having to mess with the extra data. Here's a screenshot showing the behavior of v2.18 (left) vs v2.13 (right). I tried it on different bios and always got the same result, no more module splitting. View attachment 23906