OK, I have failed to get the BIOS sections on the bricked chip flashed back to the original state.

Almost, though. It would not even begin to flash until I did the following:

1. POST on good BIOS chip.
2. Delete Secure Boot keys, Exit to shell.efi on USB
3. Modify setup_var 0x8c6 0x00; remove USB
4. POST/boot on good BIOS chip, allow Windows to load.
5. hot-swap the bricked BIOS chip in place of the good BIOS chip.
6. Run fptw64. Here is the output:

C:\Tools\Intel\Flash Programming Tool\WIN64>fptw64 -bios -f backup.bin

Intel (R) Flash Programming Tool. Version: 11.8.70.3626
Copyright (c) 2007 - 2019, Intel Corporation. All rights reserved.

Reading HSFSTS register... Flash Descriptor: Valid

--- Flash Devices Found ---
GD25B128C ID:0xC84018 Size: 16384KB (131072Kb)


- Reading Flash [0x1000000] 13824KB of 13824KB - 100 percent complete.
- Erasing Flash Block [0x29A000] - 100 percent complete.
- Programming Flash [0x029A000] 104KB of 104KB - 100 percent complete.
- Erasing Flash Block [0x2C1000] - 100 percent complete.
- Programming Flash [0x02C1000] 136KB of 136KB - 100 percent complete.
- Erasing Flash Block [0x2F0000] - 100 percent complete.
- Programming Flash [0x02F0000] 64KB of 64KB - 100 percent complete.
- Erasing Flash Block [0x640000] - 100 percent complete.
- Programming Flash [0x0640000] 2900KB of 2900KB - 100 percent complete.
- Erasing Flash Block [0x66C000] - 100 percent complete.
- Programming Flash [0x066C000] 172KB of 172KB - 100 percent complete.
- Erasing Flash Block [0x7FE000] - 100 percent complete.
- Programming Flash [0x0686000] 96KB of 1600KB - 6 percent complete.
Error 317: Hardware sequencing failed. Make sure that you have access to target flash area!
Error 317: Hardware sequencing failed. Make sure that you have access to target flash area!
FPT Operation Failed.


C:\Tools\Intel\Flash Programming Tool\WIN64>

Interesting note: during the actual flash, I did not get the Error 317. Rather, the screen went blank at:
- Programming Flash [0x0686000] 96KB of 1600KB - 6 percent complete.


The machine would not respond, reboot, or POST. I swapped in the good BIOS chip to get it to boot... and my Admin command prompt was there with the Error 317 messages, still on-screen for me to copy.

So, restoring the original BIOS to the bricked chip has failed.

I'll try again with fptw.exe, just to be sure.

EDIT: same results with fptw.exe.

Next: will boot on good BIOS chip and look for S3 bug.

@MentalNomad - "Bricked BIOS" = brick, this BIOS shouldn't start system, let alone sleep??? So, what do you mean you tested this BIOS for S3 sleep bug? Is this bricked or not?
Maybe you misunderstood what I said for you to test? S3 sleep bug should be tested on working system only, with working BIOS only. Sorry if there was any confusion here

So, your comments above are confusing to me about this due to all the unnecessary BIOS swapping and info. Please redo test with working system, working BIOS only.
Then do as I mentioned in PM.

If you simply want to "Fix" the other board, do the hot swap while in BIOS. Boot to BIOS, enter EZ Flash, switch chips here, program in stock BIOS from Asus (renamed to Z170AR.CAP), reboot done.
Then once in windows, you can reflash the BIOS region from your original dump of that system using FPTw, before all this, to fix your serial info (LAN MAC ID we can fix later via FPT too.) << For this, you will need to redo the BIOS/SMI Lock stuff in grub once more first (at this stage, not before here)

The S3 sleep bug test, was meant so we could see if you could do two things. Do sleep 1+ minute, wake system up to windows, using FPTw (not FPTw64) do the following
Dump and write back FD (FPTw.exe -desc -d fd.bin >> FPTw.exe -desc -f fd.bin) and see if you could dump and write back ME (FPTw.exe -me -d me.bin >> FPTw.exe -me -f me.bin)
If either of those fail, you do not have S3 sleep bug in this BIOS, OR, it only allows to bypass SMI/BIOS lock (writing BIOS region locks, nothing we are concerned with here, we only care about above fail/pass)

If you can do both of those things, due to S3 sleep bug, then we can unlock your FD and reprogram FD/ME/BIOS all at once so the coffee mod can be used on this system.
At this point, it's still not 100% mod BIOS is OK, so up to you if you want to retest flashing that in again as test, and have to recover again, or have me make you another mod one to try?

If you do not have S3 bug (ie write back of FD and or ME fails at S3 test), then pinmod or programmer is only method to unlock FD. Once FD unlocked you can do it all with FPT

* Edit - Sorry, I didn't see above post until my reply posted. First, please stop using FPTw64. Then, see what I outlined above for you to fix the other BIOS chip so both boards are in working state

Well, I was trying to use the other (good) BIOS chip to check for the S3 sleep bug.

And I was trying to use the other (good) BIOS chip to boot the machine into windows, after which I thought I could hot-swap to the Bricked BIOS to restore the original BIOS section backup to it.

But no luck.... along the way, I got to the point where neither BIOS chip will boot. I get:
B1InitializeLibrary failed 0xc0000001

It happens on either BIOS chip.

I tried going into EZ-flash and restored BIO 3504, which was originally on the chip. But I still get B1InitializeLibrary failed 0xc0000001.

I think I need to clear CMOS.

Yes, that is valid for S3 test, you can use good BIOS to check for this bug (but do not involve the bricked BIOS chip, it's bricked )

For bricked BIOS chip, S3 test aside, you can fix it how I mentioned.
Make sure you are setting BIOS chips in carefully, correctly, and so that the legs are 100% straight and not shorting out on the edge of next pin metal clip thingie

Did you order these yet? If not, order now, that way they arrive sometime soon. And you can get on amazon or ebay shipped faster, these are just cheapest example so you know what you need
https://www.ebay.com/itm/332735580021
https://www.ebay.com/itm/123167465408

OK, update:

Sorry for the delay. Life is busy, and the world is crazy right now.

I finally had time to fix the unbootable mobo problem -would not boot with either BIOS chip; would not POST or enter BIOS setup; it just kept giving me error B1InitializeLibrary failed 0xc0000001

Finally resolved this by removing CMOS battery and shorting CLRTC.

Then I was able to reflash the "Bricked" BIOS chip by swapping chips while in EZ FLash as you suggested.

Afterwards, I booted into windows and things were working again.

I booted into BIOS to use the SMI BIOS lock bypass... after which I was able to restore the BIOS from my original backup, like this:

C:\Tools\Intel\Flash Programming Tool\WIN64>fptw -bios -f backup.bin

This also worked fine, and after reboot, the machine is back to original state - the UUID and MAC match the original settings, and the other BIOS chips is safely in its original motherboard.

NOW, I was ready to begin trying again.

I performed the S3 test.

I do not have the S3 bug i cannot write to FD or to ME.

I would like to make a second attempt at flashing just the BIOS, if you would be so kind as to provide.

I've already looked into pinmod prospects... can't figure out how to pry the CrystalSound steel cover off the sound chip; I believe the chip is under there.

Yes, chip would be under there You really need flash programmer, maybe you'll get lucky but I doubt it.
* Edit - I asked in PM, but I didn't see info was possibly here in post one! Please confirm the following is still valid and I will make you BIOS, but I assume above is true

Old CPU = G3900
New CPU = i5-9400F

Zitat von Lost_N_BIOS im Beitrag #36

---

Yes, chip would be under there You really need flash programmer, maybe you'll get lucky but I doubt it.
* Edit - I asked in PM, but I didn't see info was possibly here in post one! Please confirm the following is still valid and I will make you BIOS, but I assume above is true

Old CPU = G3900
New CPU = i5-9400F

---

Zitat von Lost_N_BIOS im Beitrag #36

---

Yes, chip would be under there You really need flash programmer, maybe you\'ll get lucky but I doubt it.

---

@MentalNomad - Here is mod BIOS, 906EA+906E9 only, for now, later if you want other microcode can be added back (maybe 1 or 2)
Until you get programmer, all you can do is try Flash BIOS region only via FPTw.exe -bios -f filename.bin
https://ufile.io/9f9zi0nz

FD/ME will need programmed in, I assume, before you can use the new CPU. You can try it without this, maybe you will get lucky since you are already on old ME FW (my doubts due to FD needs changes flashed in as well)

You may damage the board/PCB or traces etc in the middle of the board, trying to rip that cover out, I'd not mess with it. It may go through PCB, or it may be glued to top of chip etc.

OK, did lock bypass & BIOS region flash was successful... Windows reboots just fine, but I'm still on the old CPU. I think it's now time to try the new CPU...

Is there any other test I can do to see if it's pointless trying the new chip? I have a slight desire not to muck up the thermal paste on the (stock) cooler.

On the other hand, I don't want to wait for Friday (programmer arrives Friday)...

Decisions, decisions.
----------------------

Well, no good. Got the new i5 in but the behavior was:

Hit power button.
Lights flash and Fans spin for 1/4 second and stop.
Then nothing.

I put the old Celerion CPU back in, now the behavior is:

Hit power button.
Lights flash and Fans spin for 1/4 second and stop.
1 second passes.
Lights flash and Fans spin and system boots.

So, my question becomes:
Is this a sign that we need to flash ME FW?
Or is this a sign that I need to re-check my taping and tracing on the new i5?

@MentalNomad - Great, at least we now know BIOS is OK and you can boot old CPU, in this instance at least

Sounds like you need a good 4-8g tube of paste, you can get cheap 30g of paste on ebay/amazon for $2-3 for testing and save good stuff for final mounts (This what I always use in testing, $2 30g tube last forever)

You may have damaged the board, with incorrect tape previously, or incorrect pads connected, because it should have started right back up when you put in the old CPU again. Clear CMOS to be sure, then try old CPU once more.

The behaviors exhibited with the new CPU, could be what I said above about tape/connected pads, and or as I've mentioned all along FD and ME region need programmed in with programmer or unlocked FD before new CPU can function.
But, your lack of function when now putting back in the old CPU makes me think something was off on your CPU modifications. Hopefully you didn't blow out any traces, check back of board and front, look for lifted or burn traces across the PCB. Check bottom of CPU as well.
Then recheck your taping to be sure that is correct, and confirm you connected the correct pins. Also, look at CPU socket pins, do you see any burned?

Show me image of your CPU Bottom, before you try to adjust anything, so we can see if initial tape and connection was 100% correct.

Perhaps I was unclear...

With the old Celeron processor reinstalled, the system boots up into Windows just fine:
1. I hit power.
2. Lights flash and fans spin momentarily, then stop.
3. One second passes.
4. Lights flash and fans spin again, system booted into BIOS and then Windows started normally. All is fine.

Subsequent reboots after this do not have the one second pause - when fans and lights turn on, they stay on.

With the new i5 processor installed, the system did this:
1. I hit power.
2. Lights flash and fans spin momentarily, then stop.
3. Nothing else every happens.

I'll try to get a good picture of the taping/tracing.

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

Zitat von Lost_N_BIOS im Beitrag #40

---

Show me image of your CPU Bottom, before you try to adjust anything, so we can see if initial tape and connection was 100% correct.

---

@MentalNomad - Please edit your posts if you want to add more info and no one has replied yet, especially if same day, thanks

I understood with the old CPU all was fine..... Until you put in the new CPU. And then yes, I understood all that changed after you put in new CPU, then tried old again too. So yes, I understood all you re-affirmed above

With new CPU, the systems you describe could be short as I mentioned, or you need FD/ME regions written in via programmer.
OR, it may also mean 3504 BIOS wont work at all with that new CPU for some reason, but I doubt this has anything to do with it, and if this was the ONLY issue, then putting back in old CPU would restart system to working state as it was before.
Since putting old CPU back in and you then do not get proper function like you had before, that was why I said possibly something went wrong (short, wrong pads taped/not taped, wrong pads connected etc)

Dust on CPU pads is OK, but clean with alc if you are worried it may be something other than dust
I checked your image, it's hard to tell if you have the "connect" pads connected good enough. What is that you have on there? If solder paste, add more and heat it up more, does not look melted.
Ohh, silver ink?? Does that dry? If yes, tape off all pads around there, so you can only see those two pins, then you can glob on a good amount and let it dry, then remove tape.
Other than that, it looks correctly done

Maybe do nothing, wait until programmer arrives, then program in BIOS as I sent you and try again.
Since your CPU mod looks OK to me, other than maybe not good connect on those connect pads (but this would only cause non-start), the old CPU should be working again and it's not, so maybe once you tried new CPU it changed something in BIOS or corrupted it etc.
Right now I will make you new/latest BIOS version too. This way you can try that as BIOS region only flash too, to rule out any issue with 3504, otherwise, wait for programmer so you're not giving yourself headache over this for nothing.

* Edit - Never mind, I'd prefer you flash that BIOS version and dump then send to me, and you can't due to no BIOS switches or secondary BIOS, so board is bricked right now
I guess we wait for programmer

Zitat von Lost_N_BIOS im Beitrag #42

---

Please edit your posts if you want to add more info and no one has replied yet

---

Zitat von Lost_N_BIOS im Beitrag #42

---

then putting back in old CPU would restart system to working state as it was before.

---

Zitat von Lost_N_BIOS im Beitrag #42

---

Dust on CPU pads is OK, but clean with alc if you are worried it may be something other than dust

---

Zitat von Lost_N_BIOS im Beitrag #42

---

Ohh, silver ink?? Does that dry? If yes, tape off all pads around there, so you can only see those two pins, then you can glob on a good amount and let it dry, then remove tape.

---

Zitat von Lost_N_BIOS im Beitrag #42

---

I\'d prefer you flash that BIOS version and dump then send to me, and you can\'t due to no BIOS switches or secondary BIOS, so board is bricked right now

---

Ahh, great to hear that Celeron starts OK. Pause on first boot is fine, it probably has to reset some things, then reboots after that should be normal.
Great to hear this, I thought you were bricked and couldn't even get the Celeron to work anymore. So, all is OK for now, wait on programmer and then just program in the full BIOS I sent you then you will be able to use the new CPU

Yes, sadly many places have been forced to close due to virus, so may have to wait on that for a bit At least you can still use the old CPU and use this board now, which is nice, I thought you were bricked or damaged

I got a tracking notification! It took several days, but the programmer has shipped.

Zitat von Lost_N_BIOS im Beitrag #44

---

Pause on first boot is fine, it probably has to reset some things, then reboots after that should be normal.

---