Zitat von plutomaniac im Beitrag #3276

---

Zitat von MonarchX im Beitrag #3275

---

I have a few questions and I hope someone could help me out.

---

1 & 5: Read the first post, everything is there
6: No such thing exists or will exist in the future
Rest: Off-topic

---

I also have another quesiton that I hope someone kind enough will help me with. I am not sure why, but simply placing BIOS file on USB drive does not work with ASUS Flashback. It may have something to do with UEFI/GPT formatting - not sure. I do know that following these specific steps does make USB drive work as it should for ASUS Flashback:

Zitat

---

diskpart
listdisk
select diskn (where n is the number of the pendrive)
clean
create partition primary
select partition 1
active
format fs=fat32 quick
assign
exit

---

1. Why does the above method work for ASUS Flashback and the common method (right-click on USB drive & select Format) does not? In both cases USB drive gets successfully formatted, but if you do it through Windows and not DiskPart, then ASUS Flashback fails to detect BIOS files on USB drive. If you do it through DiskPart, then ASUS Flashback detects BIOS file without problems.
2. Is there another utility that can do the same thing as DiskPart without requiring typing? I have the latest RUFUS, but I am not sure which settings to select to make formatting equivalent to the one DiskPart uses.

Sorry, I got a two threads confused. The only question about MEI I have is - which version of MEI Tools should I use to update MEI 11.6 to 11.7? OP states that 11.6 Tools should be used to update BIOS with MEI 11.6 and 11.7 Tools for BIOS with MEI 11.7. OK, but what if current BIOS uses 11.6 and you want to upgrade MEI FROM 11.6 to 11.7? What version of tools should be used in such a case - 11.6 or 11.7?

Thank you!

Hmm... I just re-read the OP and got confused again... The OP states that it is not advised to update version 11.0 to either 11.6 or 11.7, but if BIOS does come with 11.6 or 11.7, then updating to later versions of either 11.6 or 11.7 is OK...

Hi. I need some help. After flashing of my laptop bios

mobo ms-1727
Intel(R) HM55 Express Chipset Revision: B2
BIOS Build: E1727IMS.10F, 05/27/2011
EX Build: 1727EMS1.406, 05/28/2010

the loading-time error has appeared: me fw update failed, please try again later. Also the laptop shuts down unexpectedly after some little amount of time. When flashing with fpt the error has appeared:

(In yellow):

--- Flash Devices Found ---
MX25L3205D ID:0xC22016 Size: 4096KB (32768Kb)

Address 0x00000000 is not within any region.

(In red:)

Error 26: The host CPU does not have read access to the target flash area. To enable read access for this operation you must modify the descriptor settings to give host access to this region.

PC spec: msi gx740 with i7 720qm

Could it be me just have used the wrong version of bios (4mb instead of 8) and what the firmware I exaclty need to get things right?

https://www.blackhat.com/eu-17/briefings...ent-engine-8668

Hi, I'm sorry to reply .. Since the last time I've tried several methods to avoid locking FD with no success: 1) pinmod 2) meset. Could you tell me, the pinmod is actually works with hm55 chipsets or not? And if it's not, is there any method to unlock the fd programmically? May be fwupdate from the similar fw package (it's boils down I have the ME 6 ignition fw, so there is not such tool in my version package)

Thanks in advance!

Thanks for the reply! fptw -i gives the same error. Here is a screenshot:


Also the audio chip is alc888s, so I've shortened 1 and 5 pins. As far as I know we must shorten the pins before laptop is actually on until to the "post" message will have appeared. It's correct?

flashrom -V - p internal

Initializing internal programmer
no coreboot table found
Using internal DMI decoder

.....
W836xx enter config mode worked or we were already in config mode. W386xx leave config mode had no effect,
Active config mode, uncnown reg 0x20 ID: 85
....

Found ITE EC, ID 0x8511, Rev 0x00 on port 0x4e

Aborted
Error: Programmer initialization failed

So flashrom has done nothing, but Backup ToolKit has done something. I've attached the file to the post (it was possible to select the size of backup and I've selected 8M, don't know actually what is the real image size).

What's interesting, Image Tool(FITC) cannot read this but AMIBCP can.

Any ideas?