(02-10-2012, 06:00 AM)GoingDeaf Wrote: Ok, but do the values reported by AMIBCP reflect the actual values? The show column for example shows "Yes" for all settings, even though they aren't visible in bios.Well, think this as a BIOS Config. Template. Clevo uses this template for most of its APTIO Bios'ed products.
(02-10-2012, 06:00 AM)GoingDeaf Wrote: Hmm, how do we know if a settings is ignored or not?There is no way to find out which ones are ignored unless flashing..
(02-10-2012, 06:00 AM)GoingDeaf Wrote: Ok, so that my settings are reflected in the image file? I'm on linux and just running the AMIBCP in a virtual machine. Will try afuwin.exe via Wine and see if it works.I don't know what Wine is. If it is a VM with a Virtual AMI BIOS, AFUWIN may access VM's BIOS instead of host machine's
(02-10-2012, 06:00 AM)GoingDeaf Wrote: If I only modify the EC bios shouldn't I just have to flash the EC then?Most of the settings are stored in NVRAM.. But some of them requires EC or BIOS reflashing. Some settings changes EC/BIOS design i guess.
(02-10-2012, 06:00 AM)GoingDeaf Wrote: Hehe, I'd really like to avoid that.
I tried to compare two different versions in a hex-diff program but there are too many differences. There are probably some check sum which must be correct as well so you probably just can't change values at will...
On a side note; I looked att the strings in the bios file and I also saw the string P170HMx.rom pop up a few times. How's your un-bricking going?
Are there any articles/resources or any other information that one should read before trying to mod a bios?
This is because the BIOS Modules are different and sizes(and offsets of course) are completely different.
AMIBCP is just for change 'defined before' settings. These settings are defined in modules which are can not accessed without a proper decompiler. But you can access, remove, add, replace modules to your BIOS image by using AMI's MMTOOL. With MMTOOL, save reports of your BIOS Images and open the .rpt files with a text editor. You will see what differs between versions.
My reseller has bios chip reprogrammer device.. They have seperated the chip from the mainboard and reprogrammed. Everything is OK now. I just re-enabled 1600Mhz(not XMP) for my HyperXs.
(02-13-2012, 06:01 AM)Prema Wrote: Additional information from a reseller:
Quote:FN+B Does something...but we don't know what it does...try just hold down FN+B and then turn it on...When the HDD light flickers a bunch then let go...it also resets the EC and something else...also fixed NVRAM corruption with it...
(02-07-2012, 02:04 PM)Naman Wrote: ...Prema, if you are using the default BIOS 1.01.05 & EC1.00.09 can you please share your BIOS dump(from AFUWIN) in here? Thank you
Here the DUMP:
http://www.mediafire.com/?53dch8wialiox25
Naman, you where right! It should be named "P170HMx.rom" and be at CD001 (CD ROM DRIVE 1)
Attached are the recovery modules:
My reseller reprogrammed the BIOS version with .05 and EC version .06(not .09).
I liked the EC firmware fan are quite quiet now
I have tried FN+B with this config. and now I can boot with Fn+B+Power. But screen still does not show anything. When I relesase the keys, i get mssing operating system message.. I guess Fn+B loads Fail-safe defaults and executes recovery mode.
I am beginning to think Intel ME firmware has something with XTU support.. I am trying to find XTU Dev. documents and on some docs there is relation with XTU &ME & ICC& Watchdogs..