@ArashMiniStar - Yes, if it will let you flash entire BIOS at once with FPT Like that. But, it may not, if BIOS lock is be enabled, so you may not be able to flash entire BIOS with FPT like that, this is why I gave you the split commands above to flash FD/ME with FPT, then M-Flash the mod BIOS to flash in the mod BIOS region itself.
You can M-Flash mod BIOS first, but before you use Coffee CPU you must FPT flash the mod BIOS FD and ME, M-Flash isn't going to flash those in.

You use your dumped BIOS instead of MSI Download because it has your specific system details in it, serial, UUID, MAC ID etc, and if you flash stock BIOS from MSI with FPT those will be erased.

Zitat von Lost_N_BIOS im Beitrag #1111

---

@ArashMiniStar - Yes, if it will let you flash entire BIOS at once with FPT Like that. But, it may not, if BIOS lock is be enabled, so you may not be able to flash entire BIOS with FPT like that, this is why I gave you the split commands above to flash FD/ME with FPT, then M-Flash the mod BIOS to flash in the mod BIOS region itself.
You can M-Flash mod BIOS first, but before you use Coffee CPU you must FPT flash the mod BIOS FD and ME, M-Flash isn't going to flash those in.

You use your dumped BIOS instead of MSI Download because it has your specific system details in it, serial, UUID, MAC ID etc, and if you flash stock BIOS from MSI with FPT those will be erased.

---

Hi, bad news@Lost_n_bios

So I flashed the BIOS and now is not booting up with neither one of them, however the have different behavior
When I tried to turn on the computer with the coffelake cpu the same thing happened the fan will just start spinning and then stops after a few seconds

And then I switched back to the 6500 and this one seems like is booting however I do t get am imagine on the screen

https://drive.google.com/file/d/1OYI4NGC...ew?usp=drivesdk

https://drive.google.com/file/d/1OOrv8gu...ew?usp=drivesdk

Zitat von Lost_N_BIOS im Beitrag #1111

---

@ArashMiniStar - Yes, if it will let you flash entire BIOS at once with FPT Like that. But, it may not, if BIOS lock is be enabled, so you may not be able to flash entire BIOS with FPT like that, this is why I gave you the split commands above to flash FD/ME with FPT, then M-Flash the mod BIOS to flash in the mod BIOS region itself.
You can M-Flash mod BIOS first, but before you use Coffee CPU you must FPT flash the mod BIOS FD and ME, M-Flash isn't going to flash those in.

You use your dumped BIOS instead of MSI Download because it has your specific system details in it, serial, UUID, MAC ID etc, and if you flash stock BIOS from MSI with FPT those will be erased.

---

@kazp3r - Sorry, I forgot some Asus BIOS you can't use dumped BIOS, not sure why, this is 2nd or 3rd time I've seen this happen, I guess I will have to start using only stock for Asus and copy over details Unless it's a programmer write issue...
That, or it may be the tool I used for main Coffee changes, sometimes one works better than the other on certain BIOS. BIOS removed above, here is new to test, this should work with both CPU's, but for sure with older one if Coffee one fails.
If Coffee fails, and then you try older CPU and it doesn't work too, then that means there must be a write issue (programmer write I mean), and you probably can't write back your original dump and start the board either.
In that case, please confirm that is the issue before we try other software to write instead. Please erase then write in BIOS again, do not start board, close program, open it again and read/verify, then save file.
Then compare that to what you wrote in hex editor, if it's not 100% match then = write issue and we'll have to try the previous CH341A version you used before (select correct size) << If it comes to that, test first BIOS I sent you

Test CTTWOALL First
http://s000.tinyupload.com/index.php?fil...551391695080411

Love the white theme

@ArashMiniStar - Stop, slow down, before you brick your board since you do not have programmer, one wrong flash with FPT will = brick BIOS. Coffeetime CPU patch error, Not sure, sounds like you are doing something wrong, but it's not my program so I can't say for sure.
Make sure you are using latest version and updates to it, I say this because all CPU microcodes should be there unless you deleted them or files not up to date etc. No, you cannot use BIOS without GOP, unknown does not mean no GOP, check version with UBU if you don't know how to check manually.
Either tool can cause issue/problematic BIOS in some cases, so I can't really comment on either one for your board, unless I know what motherboard and BIOS version you are using so I can test build BIOS myself to see outcome file from each.

Hi @Lost_N_BIOS

I woke up a little bit earlier and I flashed the back up made with asprogrammer and the same thing happened, so my guess is that I am not able to write in it, I will try to do what to mention above and confirm in hex editor, I will edit with the outcome

@kazp3r - Ahh yes, then that means the write is the issue, so first BIOS I sent you may be OK
Please try programming in the first BIOS I sent you again, but use the CH341AFree and pick correct size. Be sure to erase, then blank check first, then open BIOS file and write/verify.
Sadly, you got in hurry and never made, or never sent me, clean EZ Flashed backup made with CH341Afree, so hopefully ASProgrammer dump was OK and it's just writes that fail
If it all fails, then we'll have to fix you a BIOS with your AFU backup, program that in and get booting, then reflash stock BIOS again with EZ flash and make a proper dump with CH341AFree this time around as initially intended

I have one dump made with CH341AFree after the EZ Flash with the correct file size I just didnt upload it since we were working with the asprogrammer, I am flashing with CH341AFree right now I will let you know the outcome.

Edit 1: After I flash, when I click verify a message says Chipwith the contents are in disagreement, this was using the fist BIOS and the CH341AFree programmer

Edit 2: If I erase and then check the blanks I get an error message that says chipare not null

I am not sure if this thing is doing what I am telling it to do

@kazp3r - No, you sent me that dump, it's corrupted, look at it in hex editor vs any other or stock, you'll see the corruption/repeating mess right from the start

Yes, those messages are normal.
#1 - This means write was not proper. Did you erase first, then blank check? If not, do that always, before any write, and with this software ALWAYS pick correct size of chip before you do anything
#2 - This means it's not erasing properly. Did you pick correct size before you started? If yes, then this also is not compatible, or there is an issue with the clip etc (This version confirmed by others to be best one to use - the 1.31(1.4)Free one, so should be compatible)

You're steps with this software should always be >>
Read - Pick correct size, read, verify, save
Write - Pick correct size, erase chip, blank check, open BIOS file, write, verify

If you continue to not get anywhere with this version, go back and do an erase, blank check, write cycle with ASProgrammer, then close app, open again and dump contents then compare with what you wrote (do not try to power on system before doing this, or it changes data)
If that is 100% match then ASProgrammer is writing correctly, but your dump I built first file with is corrupted. If this is case, then use last BIOS set I sent you, it's built from stock BIOS so would not be corrupted (try CTTWOALL first)

* Edit - Always refresh page when you come back to look, I'm often always putting in edits

Zitat von Lost_N_BIOS im Beitrag #1115

---

@kazp3r - Sorry, I forgot some Asus BIOS you can't use dumped BIOS, not sure why, this is 2nd or 3rd time I've seen this happen, I guess I will have to start using only stock for Asus and copy over details Unless it's a programmer write issue...
That, or it may be the tool I used for main Coffee changes, sometimes one works better than the other on certain BIOS. BIOS removed above, here is new to test, this should work with both CPU's, but for sure with older one if Coffee one fails.
If Coffee fails, and then you try older CPU and it doesn't work too, then that means there must be a write issue (programmer write I mean), and you probably can't write back your original dump and start the board either.
In that case, please confirm that is the issue before we try other software to write instead. Please erase then write in BIOS again, do not start board, close program, open it again and read/verify, then save file.
Then compare that to what you wrote in hex editor, if it's not 100% match then = write issue and we'll have to try the previous CH341A version you used before (select correct size) << If it comes to that, test first BIOS I sent you

Test CTTWOALL First
http://s000.tinyupload.com/index.php?fil...551391695080411

Love the white theme

@ArashMiniStar - Stop, slow down, before you brick your board since you do not have programmer, one wrong flash with FPT will = brick BIOS. Coffeetime CPU patch error, Not sure, sounds like you are doing something wrong, but it's not my program so I can't say for sure.
Make sure you are using latest version and updates to it, I say this because all CPU microcodes should be there unless you deleted them or files not up to date etc. No, you cannot use BIOS without GOP, unknown does not mean no GOP, check version with UBU if you don't know how to check manually.
Either tool can cause issue/problematic BIOS in some cases, so I can't really comment on either one for your board, unless I know what motherboard and BIOS version you are using so I can test build BIOS myself to see outcome file from each.

---

Hi @Lost_N_BIOS

This is the only BIOS I believe I havent sent to you, if this is also corrupted then all the back ups are corrupted except the one made with afuwin,
Asus BIOS CH341AFree

And yes I am picking the right size now, after sending all those unnecessary backups I learned to always select 16M while using CH341AFree

@ArashMiniStar - Before I do anything, confirm you can write entire BIOS with FPT or not >> FPTw.exe -f spi.bin
Show me image so I can see what all it writes or not

@kazp3r - I can't download that without signing in. You sent me 16MB dump after EZ Flash >> clean back up 16m.bin << This is corrupted
Please do test write and dump/compare with hex editor using ASProgrammer as I mentioned, do that with CTTWOALL and then once done see if system will start or not.

Zitat von Lost_N_BIOS im Beitrag #1122

---

@ArashMiniStar - Before I do anything, confirm you can write entire BIOS with FPT or not &gt;&gt; FPTw.exe -f spi.bin
Show me image so I can see what all it writes or not

---

@ArashMiniStar - Yes, or I would not have told you to You're writing the exact contents that are in the chip now anyway, except maybe date/time changes in NVRAM nothing would be different.
FPT does not corrupt dumps, it reads correctly and properly direct from chip, corrupted dump only happens with programmers and software

Zitat von Lost_N_BIOS im Beitrag #1124

---

@ArashMiniStar - Yes, or I would not have told you to You're writing the exact contents that are in the chip now anyway, except maybe date/time changes in NVRAM nothing would be different.
FPT does not corrupt dumps, it reads correctly and properly direct from chip, corrupted dump only happens with programmers and software

---