Should I be using

fptw64 -BIOS -F

?

@MentalNomad In your previous post it says ME is disabled, can you post your output from MEInfo and MeManuf using these commands;

MEInfoWin64

MEInfoWin64 -verbose

MEManufWin64

If there are no error messages then the Error 451 might just be a problem with the Windows 64-bit FPT, you can try using the DOS version from a bootable USB stick e.g.

fpt -f Z170-AR-ASUS-3504.MOD1.bin

Yes, you could try flashing just the BIOS region but you should try the DOS version of FPT first.

MEManufWin64:
Intel(R) MEManuf Version: 11.8.70.3626
Copyright(C) 2005 - 2019, Intel Corporation. All rights reserved.

MEManuf Operation Passed

MEInfoWin64
https://pastebin.com/ahu7J7U1

MEInfoWin64 -verbose
https://pastebin.com/D8rh6pJa

------------------------

Zitat von chinobino im Beitrag #17

---

If there are no error messages then the Error 451 might just be a problem with the Windows 64-bit FPT, you can try using the DOS version from a bootable USB stick e.g.

fpt -f Z170-AR-ASUS-3504.MOD1.bin

---

@MentalNomad Thanks for posting all the info, at least we know you don't have any ME FW corruption.

You can try flashing BIOS region only as it is the same size and location as the original.

If that doesn't work then you'll need to either try the HDA pinmod or use a programmer.

It's working!

fptw64 - bios -f z170-ar-asus-3504.mod1.bin
------------------------------

FPT Operation Successful

Rebooting now... we may have a reboot loop... not getting into BIOS...

------------------------------

Yep. Definitely trouble.

Does not POST; just keeps power cycling. Nothing on the screen at all.

Next step?

----------------------------------

By the by, I'm not giving up... I didn't menntion this, but I have two of this motherboard. If necessary, we can work on the second one until I get a programmer to fix the first. :)

@MentalNomad

This is as far as we can go as the Z170-AR does not have USB flashback to recover from bad flash (although it says it does in the manual and on Asus web site!!!).

I'm afraid you will need to buy a programmer, I would suggest getting a ch134A with the green PCB (not black, it over volts).

[̶E̶d̶i̶t̶]̶ ̶M̶a̶k̶e̶ ̶s̶u̶r̶e̶ ̶y̶o̶u̶ ̶a̶l̶s̶o̶ ̶b̶u̶y̶ ̶a̶ ̶S̶O̶I̶C̶ ̶8̶ ̶t̶e̶s̶t̶ ̶c̶l̶i̶p̶ ̶s̶o̶ ̶t̶h̶a̶t̶ ̶y̶o̶u̶ ̶c̶a̶n̶ ̶p̶r̶o̶g̶r̶a̶m̶ ̶t̶h̶e̶ ̶B̶I̶O̶S̶ ̶c̶h̶i̶p̶ ̶w̶i̶t̶h̶o̶u̶t̶ ̶r̶e̶m̶o̶v̶i̶n̶g̶ ̶i̶t̶ ̶f̶r̶o̶m̶ ̶t̶h̶e̶ ̶b̶o̶a̶r̶d̶.̶

[Edit] The BIOS chip is actually socketed (as shown here) so can be extracted and flashed externally as Lost_N_BIOS has pointed out.

Did you try with your old CPU? If yes, then sounds like the BIOS region you flashed in was a bad BIOS edit (or FPTw64 issue)
From what I see here, if no FPTw64 caused issue, reboot should have been fine (unless bad BIOS region was flashed in)
Give me your mod BIOS, I will check it vs stock and tell you if I see anything that normally causes bricked BIOS (ie missing padding files, added padding files, other issues etc) << This is VERY common issue = brick, usually due to incorrect microcode edit method

Zitat von Lost_N_BIOS im Beitrag #22

---

Did you try with your old CPU? If yes, then sounds like the BIOS region you flashed in was a bad BIOS edit (or FPTw64 issue)From what I see here, if no FPTw64 caused issue, reboot should have been fine (unless bad BIOS region was flashed in) Give me your mod BIOS, I will check it vs stock and tell you if I see anything that normally causes bricked BIOS (ie missing padding files, added padding files, other issues etc) << This is VERY common issue = brick, usually due to incorrect microcode edit method

---

Zitat von chinobino im Beitrag #21

---

I'm afraid you will need to buy a programmer, I would suggest getting a ch134A with the green PCB (not black, it over volts).

[Edit] Make sure you also buy a SOIC 8 test clip so that you can program the BIOS chip without removing it from the board.

---

If you order a U Type Flat IC extractor ($1 on ebay), you can pull chip from one board and put in the other.
So you can revive both by booting to BIOS on working one, pull the chip out while in BIOS, put in the bad flash chip, then enter EZ Flash and reflash the bad chip with stock BIOS.
Then shut down and pull chip and put back in other board.

You should go ahead and order CH341A now + U Type Flat IC Extractor. You're going to need it anyway, unless you plan to do pinmod.
You don't need SOIC8 test clip with cable, at least not for this board because it's BIOS is in a socket, but they are only $3.50 and you'll want one in the future for other boards with soldered in-place BIOS
If you need links to examples of these on ebay let me know. Once you have these tools you are in control and there will be nothing you need to work around or try to fight to flash this or that etc.

* Edit - @MentalNomad - What you sent me is a stock BIOS that's been modified, this should not be FPT Flashed (for starters)
Only FPT Dumped BIOS should be reflashed with FPT, even if you insert some (or all) system details back into the BIOS, it's still incomplete and would be missing all your original NVRAM
None of that would cause brick, usually, but sometimes missing NVRAM can if certain things are not in the stock BIOS "Upgrade" Downloaded from Asus.

This mod BIOS is missing your system details in one area. Aside from that stuff, which may be non-critical (NVRAM May be, only testing later can confirm or not), I do not see any usual issues that might cause a brick.
So, possibly FPTw64 caused issue, I always suggest against using x64 version for this. Please send me dump of the now bricked BIOS on this board so I can see what's in there and possibly tell you what happened/why etc.
Also, send me your original FPT Dumped BIOS from BEFORE you did any of this, hopefully you made a backup!


* Edit - Sorry, I forgot to tell you how to send me the dumped chips contents without a flash programmer. Ideally it would be best if you had the chip puller, because if you pull chip without it you can easily damage the legs.
It's possible, and if you are VERY careful you can do it, but just when you think it's almost out it can all go terribly wrong VERY quickly. So, if you attempt, be SUPER careful. Rock chip back and forth from side to side, with slight upward pressure.
Use something hard, small, and plastic, like maybe pointed pin cap or small wedge tool corner etc. Be extra light on the upward pressure as you get it more and more out, because if you pop it out too quickly from one side it will bend the legs all terribly.
Once it's almost out, try to slide a thin ribbon or piece of string underneath it and then you can pull up and out from straight above with equal pressure on both sides at once.

So, if you try that, or wait on chip puller, here's what you do to dump the dead chips contents (unless you have flash programmer, if you get one of those just dump it with that)
Pull chip out of working board carefully, then set it back in slightly, just enough so there is good contact but so that it can easily be pulled out.
While you have it out, before you put it back for this, you could attach some string, or tape around it etc, so you can easily pull up and out from straight above. Do this with both chips.
So, you boot to windows with the good chip in place. Once in windows at desktop pull the good chip out, and carefully set in the dead one (make sure it's slightly snug so good contact, and be sure you set in carefully so no shorts)

Also, while doing any and all of this, pay attention to the chip orientation. on the edge of the BIOS socket there is a notch, and on the BIOS chip itself there is a notch/half-moon on the top side.
Always make sure these line up/match as you insert BIOS. Notch in socket always same side as notch/half-moon on BIOS chip.

Once you've swapped in dead chip, dump it with FPT >> FPTw.exe -d Bricked.bin
if you get permission error on that, dump each part one by one, probably ME region will be the fail/error (skip/carry on if it errors, get the rest and package it up to send to me)
FPTw.exe -desc -d FD.bin
FPTw.exe -gbe -d gbe.bin
FPTw.exe -me -d me.bin
FPTw.exe -bios -d brickedBIOSregion.bin

So I'm back on this project now, have the two mobos at hand.

I only see one significant socketed chip, but am looking for positive confirmation that it's the BIOS chip. I'm 99%, because it's next to the Flashback Header, but looking for 100%.

I'm an old-timer and feel confident about pulling/setting these ICs... just never expected to do it while the mobo is hot!

*edit* found 100% confirmation - it's not mentioned in the manual's, but the diagram shows the chip next to the FLBK_HEADER as BIOS, as expected.

I may have an old IC puller from 25 years ago, if not, I'll rig something. Wish me luck!

@MentalNomad Pull as slowly as possible directly upwards, it usually comes out pretty quick when it lets go and that's the danger time to bend the legs - Good luck!

Good Luck, and be careful if not using a chip puller (even then, be careful too)! @MentalNomad - it's the one directly above PCIE slot, should be only socketed chip on the board I think.

Zitat von Lost_N_BIOS im Beitrag #27

---

Good Luck, and be careful if not using a chip puller (even then, be careful too)!

---

We shall see, IF I can tell what went wrong. If dumped BIOS region is match to the mod you flashed (minus expected NVRAM area changes due to boot attempt), then it's just bad mod, it happens to the best of us, so nothing against anybody!
If BIOS region does not match or is corrupted etc, then something went wrong during flash, due to random glitch, or FPTw64, or some screw up with the previous issues you mentioned (or combo of all that) * Edit - OR, this system doesn't like to boot with ONLY stock NVRAM (ie stock BIOS flashed via FPT)
If FD + ME missing, and BIOS region starts in it's place, you left out -bios flag (this also happens to the best of us, so don't feel bad if this is the case either ) << This did NOT happen, so all good there - still checking, but doesn't look corrupted, may just be random issue or this ^^, or FPT/Previous issue etc
I will update thread soon with my findings

The old ME FW is in there still, so it's possible mod BIOS also bricks without the ME FW edit flashed in.
Generally I've always thought this just meant Coffee mod wouldn't work, but old CPU and BIOS still would, but I guess it would require lots of testing to confirm this if someone has not already.
And all instances may not be same so may have to be tested out on this exact board with this exact BIOS/Mod/ME FW etc.

Still checking, will update more as I check.

* Edit - @MentalNomad - OK - Bricked BIOS, aside from FD/ME and expected NVRAM is 100% hex match, system info padding left in place oddly, unsure how that is possible with FPT but it's good to see.
So, this either bad mod for some unknown reason, or it's OK mod but wont work without the updated FD and ME flashed in at same exact time. Or, there was some issue with FPTw64, or previous attempts, that messed something up in FD or ME and caused this glitched fail
I suspect, if BIOS OK, it may need FD+ME in there at same time (which is a KNOWN given for Coffee mod to function), unsure what is general expected outcome for old CPU in instance like this without the FD/ME flash during BIOS update.
I think this may vary from board to board, I see some users I KNOW didn't flash FD/ME so their Coffee CPU isn't working, but old CPU is, however I don't know for certain this can be accepted as a will always be like that for all BIOS/systems type of thing.

To move forward, without flash programmer, you will have to do pinmod, unless what I mentioned to you about S3 bug in PM works
Once you have unlocked FD or flash programmer, we can re-test this BIOS mod as a whole, and or I can make you another that will work for sure and you don't have to try testing/sorting this out etc.
All up to you, and of course depends on what options you have possible right now. Without unlocked FD via programmer or pinmod, you can't use Coffee CPU anyway, so your standstill is there for now.

Brief update:

Sorry for delay, busy times.

I began a test re: S3 bug. I learned that the machine will not emerge from S3 sleep if the bricked BIOS is in place when it goes to sleep (or perhaps it never properly enters S3 sleep.)

I'm going to try these tests today:
1. Swap in the good BIOS; boot Windows; go to S3 Sleep
2. Wake
3. check for S3 bug / FD unlock
4. Hot-Swap in the bricked BIOS
5. check for S3 bug / FD unlock

If failed:

1. Swap in the good BIOS; boot Windows; go to S3 Sleep
2. Wake
3. Swap in the bricked BIOS
4. check for S3 bug / FD unlock

If failed again:

1. Swap in the good BIOS; boot Windows; got to S3 Sleep
2. Swap in the bricked BIOS
3. Wake
4. check for S3 bug / FD unlock

If those fail, and nobody suggest another option, I plan to boot on the good BIOS, swap in the bad BIOS, and flash in the -BIOS section from the backup to see if I've restored the bad BIOS chips to normal function. Perhaps I should do that first; then I can avoid all the nonsense above... hmmm.... [EDIT: Yes, I'm going to try to restore that original BIOS chip, first. It's not like I'm going to double-brick it, and it will remove unknowns from the rest of the process.)

If the S3 bug is not present for me, I'll plan on PinMod. If PinMod doesn't work, I'll use a programmer. (I have a personal interest in attempting to do this without having to use external hardware.)