Last night it was very late to prepare the raspberry to plug in the BIOS chip. and I could only do a reading test to see that everything worked correctly. tonight I will try to flash as you say by removing the AMI heading.

My chip is Winbond 25Q64FVAIG. I have to take into account something special to connect it and flase it correctly with the raspberryPi and the Flasrom? he recognizes it as Winbond W25Q64.V

@Lost_N_BIOS @plutomaniac
When using usb hardware programmer and stock downloaded bios image, MB's credentials(MAC ID,serials and etc.) will be preserved(is there fpt's -savemac parameter equivalent when using programmer)?

So, if the MB is bricked, I can't eject/desolder chip and reflash it with USB programmer using downloaded stock spi image(what credentials I'll loose in this case)? Sorry, I didn't get it.

@andr84 You can program your chip with the stock bios, it will at least work even without serials, MAC etc. If you don't have a backup you can only hope to find some of this on the board itself on some stickers or the packaging. You could try to insert them in the bios image before programming the chip. There are some helpful posts about this in this forum.

SOLVED !!!!!!! I have managed to revive my ASUS P9X79-PRO motherboard by reprogramming the BIOS chip with a RaspberryPi and the tutorial from this same Pacman user forum: [Guide] Recover from failed BIOS flash using Raspberry PI

I have to thank everyone for your support and interest in solving my problem that I already thought was lost. And above all, your quick answers.

Definitely a flaseo with BIOS programmer restored normality.

1000 thanks for your support.

I thought so @plutomaniac - I've seen more than a few boards in trashed ME states due to various issues, I buy and sell boards all the time so I'm always getting something messed up BIOS-wise (Only shop As-is on purpose)
Thanks for the tip on flashback, I was not aware of that, I'll have to keep in mind for the future! Do you know if that also still applies in these two instances? 1. You manually edit the BIOS to enable the ME Re-flash option, and 2. when ERALL method is used?

You have to pull all your board details from a backup dump to put back in new BIOS when you program in new BIOS, you can do that before you program or later after your back up and running again.
But you must have a valid verified backup before you write to the chip or you will loose all that and then can only get some of those details from the boards stickers, product boxes etc.

Cool you got your board fixed up @Chumet Since you did make a backup first, if you didn't get your boards details transferred (UUID, DTS Key, Serial, LAN MAC ID) over before re-programming and need help with that let me know.

Zitat von Lost_N_BIOS im Beitrag #4123

---

I thought so @plutomaniac - I've seen more than a few boards in trashed ME states due to various issues, I buy and sell boards all the time so I'm always getting something messed up BIOS-wise (Only shop As-is on purpose)
Thanks for the tip on flashback, I was not aware of that, I'll have to keep in mind for the future! Do you know if that also still applies in these two instances? 1. You manually edit the BIOS to enable the ME Re-flash option, and 2. when ERALL method is used?

You have to pull all your board details from a backup dump to put back in new BIOS when you program in new BIOS, you can do that before you program or later after your back up and running again.
But you must have a valid verified backup before you write to the chip or you will loose all that and then can only get some of those details from the boards stickers, product boxes etc.

Cool you got your board fixed up @Chumet Since you did make a backup first, if you didn't get your boards details transferred (UUID, DTS Key, Serial, LAN MAC ID) over before re-programming and need help with that let me know.

---

Yes, that's what you need to do, hopefully BIOS is not too corrupt, and hopefully you "verified" when you made the backup. You can use software called FD44, or can be done by hand.
https://github.com/LongSoft/FD44Editor/releases

Open two instances of the program side by side, one side drag your backup onto the app and it will fill in all your details. On second instance open your new BIOS same way, then copy details from one to the others, make all settings same and match, then save on your new BIOS side.
It can't make new BIOS file, you have to select the original BIOS and it will overwrite it, so make a copy of that first if you need to. If you can't figure it out, send me your backup and I can do it for you.

Then you flash BIOS or use programmer again, it may need to be programmed in if you can't flash from within BIOS and or if the BIOS flasher does not write to all regions containing this data (GbE region usually stores MAC, and this may not be updated with normal BIOS flashing)
If you still see MAC Address 88:88:88:88:87:88 at ipconfig /all once you are done, then you'll need to program the BIOS in again with programmer

Why would you need to transfer your settings from your BIOS to the ME that you will be flashing? As @plutomaniac mentioned, this is not needed at all. So I'm confused.

Because you do not understand what they are talking about, probably because you don't read the messages carefully.

And since you do not have your own thread, nor quoted what you're referring to @kevindd992002 I am not sure what your asking that in regards to.
If you are talking about our posts just towards the bottom of the last page @ 275, no one is discussing transferring setting to ME

@Lost_N_BIOS @plutomaniac
Thnx for clarifying about the credentials.
Honestly, I'm quite surprised. I always thought that board's and its components unique info(serials, IDs)is stored in a permanent location on motherboard itself and being collected by BIOS during boot process and then transfered to OS. For example PCI LAN/USB adapters contains their own MAC ID/serials and I thought that integrated peripherals also store its own unique info somewhere, but not in BIOS chip which can be fully re-flashed in case of being corrupted.

BIOS is as permanent as it gets for most motherboards. Same for the PCI/USB LAN adapters, if you reflash their FW and corrupt or write over their serials or MAC ID's you'll loose those too