qtm, that did the trick! What did you do differently? For the record, M-Flash worked as well. That is, telling M-Flash to boot from USB with that BIOS file on it, resulted in SLIC Toolkit finding SLIC. This gives many options for using SLIC without flashing. I flashed the BIOS anyway and have installed all Windows Updates and all hardware is performing OK. It's a nice board, but the MSI software is a bit iffy.
BIOS HOME member tungcheng & qsyjcs say need change another one code to unlock at 4C494E55-5849-5342-4554-544552212121_1_242.ROM module,offset 4CFh 75 change to EB View attachment 10867
K53U - bios v.213, patched by PhoenixTool 1.90 and flashed - result - black screen after restart, don`t start (original 213 without problem). P.S. After long reading internet posts recovered to original BIOS v.213 from CD with renamed BIOS file to K53BY.BIN + pressing Ctrl-Home with Power button.
Used the phoenixtool v1.90 to mod a Insyde bios on a HP DV3500ea laptop. Again big thanks to AndyP for his great work and all who have contributed in the development of all of Andy's bios mod toolkits. The mod was straight forward. One interesting bit of info that i have observed when using all the bios mod tools. My Avast AV always interferes with the mods even when disabled. As a rule i now always have to disable the AV and then re-boot. After the re-boot with the AV disabled i get no problems. The errors experienced using the award. ami and phoenix toolkit with the AV interfering has been unable to load epa module, check sum error etc. But with AV completely disabled the mods can be carried out successfully. Might be worth a note on the first page sticky mentioning that AV's should be disabled when using the toolkit's. Many thanks
Longshot, but...does this work for unlocking shielded SLICs? I'm trying this with a Dell Optiplex 790's UEFI/BIOS hybrid, and the legacy ASSET/SVCTAG method no longer works for unlocking. The new utility, smmfgcfg, is not available out on the net (at least not yet). I select the A05 BIOS, enter it into the Phoenix tool (latest version 1.90), and I get the following error: "Failed to extract HDR file." (same error that shows up if a really old Dell BIOS is used). Thoughts?
qtm et al.. I am looking at the mod method for K53/K43 boards. 2 questions: 1) Does anyone have a copy of both the original downloaded EFI and a copy of an EFI that is backed up from ROM. I would like to see what the differences are 2) How do we know to change the flag bytes and put the marker at A0200 and A0300. I can find no reference to this in the code. Andy
I modified the BIOS of ASUS K43/K53 Notebook boards , can't be used to phoenix tool modify the bios of official homepage ,because the offset 0xA01B8h~0xA01C7h is PC UUID ,Including computer MAC address, 0xA01D7h~0xA01DCh also is computer MAC address , each computer MAC address is different ,and 0xA0200h~0xA02FFh is 2.0 SLIC marker ,0xA0300h~0xA03FFh is 2.1 SLIC marker ,the above all of these offset address all in this 0xA0000h~0xAFFFh , this area can be called NVRAM ,so can't be normal flash ,must use special parameters of the flash tool to flash files ,if like this flash so every computer's MAC address will be erased ,will lead to network card can't work normally . so this mod method can only mod the original computer BIOS backup
hello andyp what can i say... you developed so much your application that ok i mean WOW congrats mate!!! so i come with a proposition... can you also give us the choice to change the boot logo cause your tools already decompiles the bios image... So if it's an easy to add feature will be great... My regards, Ribben
Oh, I don't think there's a straight-forward way to do this. Every bios manufacturer has its own idea of how to put a bios logo into the image. For example: On old HP Insyde bios images, there's a LOGO at the start of the image which needs to be replaced "by hand". Whereas on new HP Insyde bios images it's just a regular file in the FVH volume, it can be replaced easily just like any other module. Also, some of HP business class laptops can grab a logo from the local harddisk [h20000.www2.hp.com/bc/docs/support/SupportManual/c01564727/c01564727.pdf - see details on page 5]