@hitman20 bios1.001: The archive is corrupt


snakeman

@snakeman Can you please try this one and remove the .zip at the end of the File?

Edit: I have uploaded it now to Sendspace. This is the Link: https://www.sendspace.com/file/6fzlq1 Password is snakeman.

@hitman20 That works thanks, They both work thanks.

Now to get up the courage and do some more reading!

snakeman

See @snakeman - that's why I cried when you had split files that needed renamed above too, it's just not possible or a huge hassle due to the way this forum attaches and renames files as you download them.

If I modify stock BIOS, you can ONLY flash it via Qflash, DO NOT use those files with flash programmer or FPT. And yes, as mentioned, if you use hitman20's files no matter how you flash it you will have his serial UUID and depending on how you flash it possibly his MAC ID too.
However, since you have programmer, you can easily backup your current BIOS, program in his and test, then program yours back. This way it doesn't matter if you have his info in there or not, since you would only use for a short test period then put your BIOS dumped back in.

I will make stock F5/F12 for you, please remember to only flash them with Qflash.... And, your links to gigabyte stock download are broken links. Please confirm your exact motherboard model and I will get them from the page myself.
Note to self >> confirm or add/UPD >> 906E9

@Lost_N_BIOS

F5 http://download.gigabyte.us/FileList/BIO...70n-wifi_f5.zip

F12 http://download.gigabyte.us/FileList/BIO...wifi_f12_v1.zip

These should be working,

Thanks for all the help

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

@Lost_N_BIOS Ok, I'm back @hitman20 bios worked only issue so far is ME driver under windows 10 so this has been great for testing my i5 7500
works in Win10 (me driver problems) Ubuntu 18.04.1 works

@hitman20 The bios flash worked my i5 7500 works. The bios version is F4. I have yet to work out my ME driver problem no big deal for testing.

Conclusions: The F4 bios boots 10-15 secs slower than F5 was, at boot up, other than that seems fine. I think the F5 and F12 might be faster.
Anyone have clues for the Me driver issues?

snakeman

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

@Lost_N_BIOS I am having problems with ME driver, Could that stop me from using all the features of the processor ................. ex 3D hevc encoding?

Edit button @snakeman

Thanks for links, will make you BIOS now

10-15 second slower boot, and ME driver issue, sounds like ME FW may possibly be corrupted. Do you see ME FW version shown in BIOS, or can you see this with HWINFO64, or do you see N/A or 0.0.0.0 (If this, it's corrupted ME FW) << Due to this question, I will wait to make BIOS until I hear your reply on this

Yes, ME FW / Driver issues can cause all kinds of things to not work properly, as for your specific 3D example I am not sure. You've not fully explained the issue though, what do you mean "having problems with ME driver"?

How did you put his BIOS on there? You may need to use certain ME driver package, since this is older ME FW, I am not sure. Check the ME driver thread and see what the info says about which version drivers for what FW, and or wait on hitman20's reply about what ME Driver package he's used.

@Lost_N_BIOS Thats was with the experimental firmware from @hitman20. I flashed the full bios with fptw -f I get no information from meinfo. I tried to install the driver with previous proper versions of the drivers, they would load but not "start" all other functions work great. I tried a 3D movies under kodi in windows never activated the glasses I thought that was strange, no matter. More interest in your version of the Bios at this point.

This board never showed the ME version in bios looking now.
Haven't tried HWinfo looking for it now.

Meinfo results
Intel(R) MEInfo Version: 11.8.60.3561
Copyright(C) 2005 - 2018, Intel Corporation. All rights reserved.

Error 86: Communication error between application and Intel(R) ME module (FWU client)

Error 81: Internal error (Could not determine FW features information)

That doesn't look good.

snakeman

@hitman20 Did you have these issues with Meinfo on your board?


snakeman

@snakeman I have currently no Windows installed on this PC, so I can't tell you right now. I used it also as an Hackintosh without Problems with ME. I can also try to Mod the latest BIOS and check it then with Windows if there is the same issue. First I have to find all Tools again to do it.

@Lost_N_BIOS Do you have maybe the Intel Flash Image Tool and can uload it somewhere, because I didn't find any real Download Link for it. Thanks.

Edit: I have found the Intel Flash Image Tool again on a USB Stick from me.

@hitman20 I just tried hackintosh and it seemed ok. Having problems with Kodi under windows no 3D maybe not even related. Already moved my coffeelake proc to another board.

@snakeman Then you don't need the BIOS or anymore or do you need it still, when you already moved?

@hitman20 Yes, I still need the bios if you are willing to help me. I am more than willing to try it myself if you want to instruct me.



snakeman

@snakeman - Without ME Drivers installed, you can't run MEInfo, except from DOS. Run it from DOS, and use -verbose flag (meinfodos.exe -verbose), show me image of the full output.
Do you have a flash programmer? If not, did you ever make a full BIOS backup with Qflash or AFU? If not, you've lost your second NVRAM volume probably, since you now flashed in hitman20's BIOS with FPT.
FPT also often does not flash or dump second volume, so you may be able to get a copy of it still, if AFU dumps second NVRAM volume (I am not sure).

I'll just go ahead and make you BIOS with new ME FW instead of using hitman20's ME FW region, sounds like it's messed up. OR!!! It may be that you need to run FPTw.exe -greset to reset the ME FW state, since you reflashed the entire BIOS and downgraded ME FW.
Please try this, then run MEInfoWin after that, if you can install drivers, if not then try from DOS. ME driver should already be installed, unless you didn't install it previously? And, since you can use FPT in windows, this tells me you already have ME drivers installed, and the issue is ME FW is corrupted.
This can be confirmed by HWINFO64, either ME entry will be missing entirely from motherboard section (in large AIDA64 like window), or it will show version as N/A or 0.0.0.0 - You can also check with this Intel tool, it will show ME FW Version at the bottom - http://s000.tinyupload.com/index.php?fil...768052205283107

@hitman20 - ME System tools are here in section "C" - Intel Management Engine: Drivers, Firmware & System Tools
The reason this concerned me and I paused, was I was just going to extract that ME FW region as-is from the BIOS you posted, since you guys have same exact model board correct?
But, due to these ME issues, I'm worried now it's corrupted, not a big deal there I can redo with fresh ME FW stock base.

@Lost_N_BIOS I reflashed it again with fpt same result. And, I also performed a -greset same result again. HWINFO shows 0.0.0.0.

Thanks for confirming, that 0.0.0.0 means ME FW is corrupted It's OK for us, I will make you fresh BIOS with newly redone ME FW (hitman20 will need this fixed too, can be reflashed via FPT or entire BIOS with fixed ME in his programmer if he wants)
Sorry, I got behind tonight trying to fix and test something on my end, so I wont have time to do this tonight. I will get it done for you first thing tomorrow.