I've used Phoenix bios editor to rebuild the bios, and corrected the module. If error occurs press no. An alternative would be to use PBE alone without any further modification....
When I had my Clevo bios all I did was have PBE open it and let it rebuild after I had got done hex editing the files in the temp folder. (Ignoring the unsupported modules. p q or something like that) Is that what you had to do?
I've tried before a complete manually mod. You should know that I don't trust PBE at all. It caused some bricked boards before. But at new Phoenix bios structure using new version of FI and FP.exe it seems to be reliable. The only issue is that it sometimes creates additionally a strange MOD_000X.ROM module. If you let PBE rebuild the modified bios, reopen it and rebuild it again without any further modification, you'll see that it gives 3 errors at rebuild why???....... This makes me feel skeptical about PBE..... I corrected that strange module to a gap module and the issue is gone...... Modification itself was easy.....there are two dummy MOD_5A00.ROM and MOD_5A01.ROM modules which are prepared to contain the public key and marker. I've hexedited them (added the data), rebuilt bios with PBE and corrected MOD_0001.ROM module to gap module. You may check my mod to see what I've done.
ok, thanx. do you know what this Sys Info in the setup table means? why isn't it available in the bios itself? i tried to modify the manufacturer settings. but then the laptop doesn't boot anymore . samsung repaired it that's why i made a recovery disk.
I'm sorry, but it must be again a problem with PBE or a flashing issue what can happen from time to time. I never should use it again....I've tried to insert SLIC manually but without a complete reorganisation of the modules it wasn't possible, so I decided to use PBE for this job......next time I don't release a PBE mod.....
If it stopped 2/3 through the update I think it is more likely it was a problem with the flashing and not with the mod. It was probably bad luck. Sorry that happened to you fallan!
The byte to byte comparison of the original decompressed modules and of the decompressed modules of the mod matched exactly, except the BIOSCOD1.ROM module, the ROM.LOG and the ROM.SCR, that is of course plausible.....because BIOSCOD1.ROM was modified and ACPI2.ROM was added---> new ROM.LOG and ROM.SCR. A flashing issue was probably the reason, yes......after 8 month it happened again to one of my mods....I'm sorry....
Well, it is a useless brick now. Previously I had already tried the common method, but that's when the OEM Table ID kept the same 4 characters and I asked for your help. Then I tried the other suggested method, and while it goes thru the POST and I can get into the BIOS settings, it refuses to boot, no matter what. The blinking cursor stays in the upper left corner, but it doesn't boot to any device (tried CDROM, HD, USB, etc). So with no recovery method available, I guess I'll sell it for parts. Unless someone here knows of a recovery way. Other than that, I got a 50% success rate, 1 down and 1 good, luckily, the bricked notebook is a very very old one, maybe this BIOS was never meant to have a SLIC table? Or be modded? Thanks for all your help tho!