I try some commands with verbose.

The dummy is include but not the internal (what needed to detect/read/write/etc... without external programmer).
flashrom -p internal (command needed but internal is not included on the one you shared, I check also other binary that actually have more chip added but
what is weird is that the windows doesn't have the internal programmer included).

Concerning recovery menu, I know that there more than recovery menu, there is even a blind mode too but I can't not find how to trigger this one.
The recovery menu I found work with Ctrl-home after successive holding on power button 3 time. But before going to this recovery menu, it take even more
to boot on it than boot normally to windows, basically, the PC turn on after like 3 to 5min, there is this G light (left corner of the keyboard who turn on, after like 2 to 3min it turn off)
and after 1min it show the logo (it take like 1min more to go to recovery) and it goes to the bios menu with recovery.
I guess there a lot of routines behind this.

I don't know which name bios the it try to check, I was thinking it was X5.BIN, AMIBOOT.ROM or AMI.BIN like mentioned inside the FSrecovery (bios file) but apparently not that.
I also try different name (X5BF, X5K, X5WT, BIOS.BIN, AMI.ROM, X5.ROM, X5BF.B07, etc...) nothing, when I press process to flash, it don't even check anything or don't even try,
it directly said flash failed, probably because I don't have the right name.

I tried fat32, ntfs, gpt part, etc..

Just to keep you updated.

I found other flashrom binary (last one pre built in date was February 2016) I will share it with you.
But doesn't contain internal.

I have some good news and bad news.

Let's start with the good one.

I kinda cheat the bootloader of Windows and forced a boot to GRUB instead of the Windows BootLoader
But, I need another storage to point a different chainloader boot.
I was after able to boot into Ubuntu for example.

Now I have the possibility to boot in Linux ! this was a big step, I just remind you that I can't not boot anything else than Windows 10.
F12/F9 broken bootloop, even more when I put another storage, the only one who boot is the one with Windows
Bios settings not saved, etc..

So this is good, I also compiled a version of Flashrom under ubuntu with the internal feature.
Everything seem to work good under Linux + Flashrom (chip seem to be detected)

Now the bad news, I faced another problem and it seem that the real problem is not the ME nor the BIOS but the flash descriptor itself
that seem broken or not valid, probably the reason why I can't not flash with official tools etc..

I guess I need to force somehow the usage of a external flash descriptor to be take into account and flash the chip.
Here's the verbose of Flashrom under Linux

You are right about FD, but I was also surprise that FD is that much problematic, normally we could dump/write/erase without taking in consideration FD with
FPT for example. I tried every possible command with FPT but it was a bad shot (I mean on Windows, didn't try on FPT Linux), I don't know all the possible third party software out there.
I know just that, hopefully flashrom or any alternative tool would be able to flash the chip in proper way.

Flashrom apparently need FD for the hardware sequencing, so far from what I've read and try the learn the last hours.
I'm sure in the end I would be able to flash and back to factory bios but at this point, I'm facing this other problem that I need to resolve too.

Thinking that I could boot in a weird way to linux and use flashrom, I feel a little bit more confident.
I didn't know that have fpt in Linux, I was thinking that fpt are only available on Win32,win64 and dos.

I will check.

It probably can be done without consulting FD, etc... but I'm still learning Flashrom, read the source code itself and check any return of similar error (didn't find anyone in the
same position)

Honestly I never faced that type of issue and is a first, hopefully the last but if I find the solution, that probably can help other people who are in the same situation ?

Here's the last binary revision flashrom for Windows (if you need, but on my side, It didn't help without the internal feature, only available on Linux version, or maybe can be compiled but I'm not sure because apparently it need a strong admin access)
http://s000.tinyupload.com/index.php?fil...940374528654580

Yes unfortunately only on Windows but Flashrom look like a more powerful tool.
Apparently Flashrom purposely lock write when is about ME/Description region.

I'm still working on it and try to figure out Flashrom itself.

At the same time, I use ich_descriptors_tool (interesting too)
with the original firmware available on the OEM website.

Here's the answer about the descriptor part.

I'm trying everything with Flashrom, still need figure out the hidden or secret part of this tool.
But right now I'm facing a OPCODE 0x03, one of the user on the flashrom irc recommend a flash external programmer
but I'm pretty sure that it don't know all story behind this and that I can use the computer in a weird way.

In case anyone have more knowledge than me in Flashrom, here's the flashrom output.
I found how to find the chip (using the swseq instead of hwseq that avoid the usage of FD)
I also find a way to load partially a layout and flash a specific region but either way, something is wrong about the OPCODE 0x03
What is weird is that flash image seems to be a legacy bios.