time to try USB or SPI usb flasher (backup chip.. then merge update with the backup.. reflash.. test.
The board does not do anything, brick. No beep buzzer ... No hint of initialization. I am short out main BIOS to recovery and nothing....
Sorry to hear that. And even more sorry, because I thought with the new EFI boards recovery will work any time. Nothing seems to have changed...modding remains to be risky...
Sorry for bad English 1) we Disconnect a network and all devices. (CD, DVD, HDD, USB and тп.) 2) It is pressed the button of inclusion and after 1 - 1,5 seconds we close 1 and 8 leg (contact) on the chip bios (It is artificial we create short-circuit at a stage of initialization of the control sum bios). View attachment 16195 Important: Do not mix the chip on what to close contact. The first (M) - Master on it also we close legs (contacts) " on it and will be corresponding marks the letter (M)" The second (B) - Backup it is not touched, is reserve from it and there is a restoration. " On it also will be corresponding marks with the letter (B) " That to not mix what legs (contacts) will close near the first to stand a point, the account of legs is made counter-clockwise. (it is very convenient to close a tweezers)
All tested - main board is a brick @ kaput. New mobo I have at home, 2.1 slic mod was successful (Award BIOS).
I tried several times download PhoenixTools v2.9 and it always give me CRC errors when I unziping it. What am I doing wrong? TIA
PhoenixTool modded my HP fine AndyP, thanks as usual.. I did update to the latest bios first, made an rweverything report off the latest bios, modded the bios using all defaults using the rweverything report and flashed using the windows flash tool and all went well. One thing I did notice was it gave me the filename for recovery which was cool but it didn't let me copy and paste it, I was unable to highlight it to copy it so I had to manually type it. Is there a simple way to make it copy and paste in a future version of Phoenix tool just to make life that little bit easier? Thanks again for everything!
yep, that's true but still handy to just copy and paste and i doubt it would be very hard to adjust to add that, obviously if it is hard then it's not worth doing but if its simple then it's worth doing.
Hi, first of all. great tool! is it possible to change the sdt, rsdt and pubkey with this tool? i tryed several times and after flashing only the maker was changed.
Error 5 - Offset and length when trying to replace DSDT Hi Andy, Great tool. Thanks for writing it. I have one small problem when I try to update the buggy DSDT on a MSI P45 Platinum (UEFI Click BIOS.) I get: "Error 5 - Offset and length were out of bounds....." This error happens when the I try to fix one specific DSDT compile error by changing package to buffer. No SLIC mods at all. Code: dsdt.dsl 1924: Name (_FDE, Package (0x05) Error 4080 - Invalid object type for reserved name ^ (found PACKAGE, requires Buffer) Compiled AML sizes (bytes) 24893 - original_dsdt.aml 24893 - mostfixes.aml (all fixes except Package to Buffer fix.) 24891 - allfixes.aml (all fixes including buffer fix.) Compiled DSDT is two bytes smaller than the original and Phoenixtool throws an error. UPDATE I managed to make the DSDT mods so that it Phoenixtool updates the BIOS file by padding strings or by changing the name block to a method. However, when I try to boot the Windows 7 installer, it give me a BSOD saying that my BIOS is not fully ACPI compliant. Even if I only make a trivial change to the DSDT (string change, 0x0FFF to 0xFFFF), Windows gives me a BSOD saying my BIOS is not fully ACPI compliant. Something is wrong with DSDT patching or I'm doing something wrong. Can anyone help?