Shixinyuan
compartirás este BIOS?
ROG-STRIX-Z270-I-GAMING-ASUS
8)
I intend to buy a Gigabyte Z390 aorus ultra motherboard for my processor
QuadCore Intel Core i7-6700K knowing that the chipset is not compatible in theory
I integrated in the BIOS of the motherboard Gigabyte Z390 aorus ultra features,
of my current QuadCore Intel Core i7-6700K processor.
I would have liked to know if there are any chances for this to work in anticipation,
a future purchase of an Intel processor when prices will be more affordable.
I hope to have a response.
Thanking you in advance, I will translate this message into English hoping that it will still be understanding.
cordially
Thanks to this thread and its contributors and the especially the clever folks that figured this out I managed to get an 8700k running just fine on my ASUS ROG IX Code.
I tried this tool - Easy-automated-Mod-tool-for-Coffee-Lake - but the system would not post, it powered, gave me the ROG splash screen then all I got was a flashing white cursor top left of the screen, I tried both iGPU and ROG Strix 1080ti and both the same.
So put back the 7700k, flashed a Z370 ROG X Code bios image (used FD44 to put all the important information in the image). To make this work I swapped the AuraSync RGB modules from the 1301 IX Code bios into the 1701 X Code bios image. Downgraded ME to 11.6.0.1126, removed GUID: 63F23E9D-5FDA-415E-9C2A-64C4E2A6ECE8 which is an ME 11.8 update. Unlocked ME regions and BIOS regions using GRUB and then used Intel FPT (Windows) and downgraded (flashed) the ME and flashed then the X Code BIOS image. iROG modules all updated to Z370 versions just fine and all works great. Just like I would expect a Z370 board X Code board works, to be honest.
TL;DR
There was an issue that took me a while to figure out, after flashing with FPT the iROG modules would either not, or partially update (some said Z270 & some Z370) or the board would hang with a flashing cursor as if it was UEFI expecting something to happen which didn’t, I tried a few times and could not get a complete flash of the X Code bios, when this happened I would flashback an IX Code bios. I eventually figured out in order to make the process work properly I needed to disconnect the DisplayPort cable from the Strix 1080ti and connect it to the iGPU. everything went very smoothly then.
@brams - would you be willing to share your bios file? I used the mod tool with the newest bios version available for the IX Code but haven’t had much luck getting it to post with the coffeelake CPU… Did you do any of the hardware mods on the mobo? I noticed that the Apex mobo is similar enough that the hardware mods would probably work but not 100% sure.
When you say it won’t post fans run for half a second then it goes off or it powers up with a blank screen? I experience both these issues, half a second was due to pads not being shorted properly (I tried a pencil and it didn’t work), once I got it to power up, I had a blank screen (that was trying to use a modded IX Code bios) I then gave up on that idea and used an X Code bios which works perfectly.
I used an MG Chemicals nickel circuit pen to short the two pads, and two tiny pieces of Kapton tape to isolate the two pads, I used a razor blade and USB microscope for this as its to bloody small otherwise. Photo is available on this site I won’t link it as I guess you have seen the photo anyway.
Sure pls find attached BIOS image. I guess you figured out how to downgrade ME? and flash the bios image? This is an X Code bios image as per my original post, you will need to use FD44 Editor to transfer your motherboard info (UUID, Mac and SN). I really suggest that whilst flashing it you use the iGPU as I wasted a lot of time messing around until I realized my 1080ti was borking the flash routine, once done flashing I reconnected the 1080ti and it works fine now.
I will PM link for bios as I can’t upload here
Hey guys,
Anyone have bios to Asus Maximus IX Formula z270, i look bios to compatibility with 8700k / 9700k/9900k if possible…
I finally received my 9700k from Amazon and tried to install the CPU on my Asus Z170-A with some moderate success. I have been following this thread and the automated tool thread with great anticipation. However, I need some help to solve the remaining issues. I did the following:
0. Connected and isolated the necessary pins on the 9700k CPU.
1. Started with @chinobino BIOS that was provided to @JoeBlow on this post: [TOOL] Easy automated Mod tool for Coffee Lake bios (9) thanks to the work that was done here. As he reported success with this BIOS, I decided to start with that one.
2. Using modified MMTool from UBU package elsewhere on this forum, I removed all CPU microcodes from the above BIOS then added microcodes for my current 6600k and my new 9700k CPU. The goal was for the new modified BIOS to be compatible with both.
3. Used FD44Editor to put my MAC Address, UUID and Serial Number back in (retrieved from original BIOS backup using AFUWIN).
4. Flashed using USB SPI programmer CH341A. I have several spare Winbond chips and backups 
With these changes, I experience very unreliable booting. Here are my issues:
- 6600k actually does not boot, I’m not sure I have done the microcode insertion properly for this or it is another issue. It powers on with the DRAM LED solid red and repeats boot loop on the same error LED.
- 9700k can do one of the following:
* Boots into Windows (this only worked once or twice). In Windows, the screen can go black for a second then come back to normal.
* Boots into BIOS, cannot find my M2 SSD or one of my two SATA SSDs so does not boot into Windows.
* Powered on, DRAM LED solid red, repeats boot loop on the same error LED. This happens most often.
* Powered on, DRAM LED solid red, after pressing MEMOK button the system reboots then the DRAM LED blinks 3 times before powering off by itself.
I tried the following:
- Sometimes pressing MEMOK button works and lets me boot to BIOS or Windows.
- Changing any BIOS settings (core ratio, voltage etc.) seems to randomly stop the board from booting (no POST, DRAM LED solid on) also noticed that the CPU turbo speed can be detected sometimes as 4500MHz or 4900MHz. I have to clear the CMOS to get back to a booting state.
- Modified the BIOS with a version using ME_cleaner https://github.com/corna/me_cleaner, this did not work at all (no POST, DRAM LED solid on)
- Removed all 4 sticks of my RAM and tried with 1 stick, no difference (no POST, DRAM LED solid on)
- Removed video card, same issues as above with DRAM LED but the iGPU is working.
- Resetting the CMOS using the jumper, this seems to let me boot at least once after settings have been reset. (CPU defaults to 3600MHz and RAM at 2133MHz)
Could someone take a look at the BIOS I created and see if there is anything obvious I did wrong?
I’d also like to say thanks to everyone in this forum that I am able to get this far at all.
@Shad0w59 ,
I have modified your BIOS for Coffee Lake 9x00 Series (Skylake and Kabylake microcodes remain) and added your MAC address, give it a try and let me know how it goes.
Z170-A-ASUS-3802-MOD9-MAC
RAR SHA1: f577e3cb695f6d7a6e1ca8bfc7bdbd796f0b4a1b
MOD BIOS SHA1: f7f03c7435e1ea8fbb6ce4500179426b6fa9f9e7
Mods on the BIOS:
506E3 Microcode C6 updated for Skylake
906E9 Microcode 9A updated for Kabylake
906EC Microcode A2 added for Coffee Lake (9x00 Series)
Updated EFI GOP Driver SKL-CFL - 9.0.1080
Updated OROM VBIOS SKL-KBL - 1059
Applied PCIe patch
Changed SKU to Z370
Set all cores sync
HT Patch (up to 16 CPU cores)
Patched ACPI tables
Patched CPUmpPEI at both locations
Added Shad0w59’s MAC Address
Here is the same BIOS without Shad0w59’s MAC Address should anyone else want it:
Z170-A-ASUS-3802-MOD9
RAR SHA1: 95202abfd07f35fe9f906cbabc1380b2eb925444
MOD BIOS SHA1: 083ead517b5b2d815482996d9019ad1a71ebe537
Mods on the BIOS:
506E3 Microcode C6 updated for Skylake
906E9 Microcode 9A updated for Kabylake
906EC Microcode A2 added for Coffee Lake (9x00 Series)
Updated EFI GOP Driver SKL-CFL - 9.0.1080
Updated OROM VBIOS SKL-KBL - 1059
Applied PCIe patch
Changed SKU to Z370
Set all cores sync
HT Patch (up to 16 CPU cores)
Patched ACPI tables
Patched CPUmpPEI at both locations
Good stuff Shad0w59!
I had another person (Momento) request a modded Asus Z170-E BIOS for Coffee Lake also, he has tested and confirmed it working with his 8700.
Z170-E-ASUS-3801-MOD for 8x00 Series (Skylake & Kabylake microcodes remain)
RAR SHA1: 3587f10b5b94891c29c6e425797e43b829412a13
MOD BIOS SHA1: 7d208542a2f6a26dabe2d8ff418c2aafb52ecadd
Mods on the BIOS:
506E3 Microcode C6 updated for Skylake
906E9 Microcode 9A updated for Kabylake
906EA Microcode 9A added for Coffee Lake (6 cores)
906EB Microcode A4 added for Coffee Lake (4 cores)
Updated EFI GOP Driver SKL-CFL - 9.0.1080
Updated OROM VBIOS SKL-KBL - 1059
Applied PCIe patch
Changed SKU to Z370
Set all cores sync
HT Patch (up to 16 CPU cores)
Patched ACPI tables
Patched CPUmpPEI at both locations
Z170-E-ASUS-3801-MOD9 for 9x00 Series (Skylake & Kabylake microcodes remain)
RAR SHA1: 6478d508d12039c520867165f2eb5333468f6f70
MOD BIOS SHA1: a94068a2a5b78dbb24fd8c76751cef0447abc5bc
Mods on the BIOS:
506E3 Microcode C6 updated for Skylake
906E9 Microcode 9A updated for Kabylake
906EC Microcode A2 added for Coffee Lake (9x00 Series)
Updated EFI GOP Driver SKL-CFL - 9.0.1080
Updated OROM VBIOS SKL-KBL - 1059
Applied PCIe patch
Changed SKU to Z370
Set all cores sync
HT Patch (up to 16 CPU cores)
Patched ACPI tables
Patched CPUmpPEI at both locations
@chaplin_lee I wrote some detailed instructions when I got the i7-8700 working on my ASRock H110-M board. See my posts #122 and #178 in this thread. And other posts by me and other people in response to those. I wasn’t correct the first time about a lot of things, but I put in details that nobody did, so maybe it will help you.
First, though, did you short the two pins (see the posts above). You have to mask some pads for all coffee lake, and short two others for the 8500 and 8700 (six-core) CPUs. Read my posts and search this thread for mention of the HWBOT forum and posts over there that were started by Splave. There are pictures of what you need to short, and how. And I posted some pics of the pins that I melted on my motherboard, yay! I did not mask them as I should have. It is working right now, so I guess I never needed them.
I finally received my 9900k and tried to get it going on my ASUS Maximus IX Code motherboard with minimal success. I have been reading up as much as I can within the forums and ran into some issues that maybe someone more knowledgeable can help me solve. I did the following:
- Connected the pins on the motherboard and isolated the pins on the CPU. Used the info from a thread about the ASUS Apex board and used a multimeter to make sure the CPU pinout corresponded to the same area on the motherboard as they are different. It looks like they share the same bios so I did that mod too although I honestly don’t have a clue of what the purpose of it is.
- Started with the newest bios for the iX Code from ASUS site and then ran it through [TOOL] Easy automated Mod tool for Coffee Lake bios. The tool worked flawlessly but the board wouln’t take it. Got some help from @Lost_N_BIOS as he corrected some stuff but even then, the USB Flashback wouldn’t take the bios file. Then I tried just flashing an OEM file and that didn’t work either. The flash utility in the bios would flash any OEM file without a hitch but the flashback wouldn’t work.
- Read through more threads on the forums in an effort to sort out my USB flashback problem, and ran into a post somewhere stating that hyper threading wouldn’t work unless a newer gen motherboard bios was modified to make it work. Luckily, I ran across a thread where @brams had done that exact thing and was fortunate enough to get a copy of it from him, as well as a considerable amount of help that I didn’t even know I needed.
- Retrieved the UUID, Serial Number and MAC address via Intel FPT and used the FD44Editor to copy it over to new bios file I got from @brams
- Turns out my ME was too high at 11.7.0.229 and I guess I needed the 11.6.0.1126 that was present in the Maximus Code X bios that was modified. To do that, I had to pray to a higher power as using UEFI grub and then FPTW64 while elevated in Windows did not work. Did everything I could to get it to work but failed over and over and over again. I must have repeated the process in excess of a hundred times. Read through a thread that explained different options available and I just went down deeper into the rabbit hole. Probably spent a good day trying and I don’t know what happened or what I did differently but eventually persistence paid off and somehow I was able to downgrade it via FPTW64.
- After the BIOS finally flashed, there was a good five or six very nerve wrecking reboots before the UEFI finally fired up on the 7700K. I wanted to make sure everything still worked with my “old” stuff before trying out the new processor. Turns out the motherboard was showing a high voltage for the CPU at over 1.5V and manually changing it did nothing. I booted into Windows and used hardware manager to keep an eye on it and it looked normal. Voltages were somehow in the 1.1 to 1.2 range and CPU temps were within range. Not really sure what’s going on there either but I wasn’t a fan of it either way. I don’t want to burn out the old CPU and definitely don’t want to hurt the new one.
- After all that was done, I finally decided to throw in the 9900K in to no avail. No matter what, I can’t get the motherboard to post. It turns on for maybe a second and shuts off almost instantly. There appears to be a little tiny red LED that turns on that is labled CPU and that’s when the motherboard shuts off. Since the pins are shorted (on the motherboard) and the other two pins are blocked off with Kapton tape, I’m not sure what the problem is. The ME is downgraded so that shouldn’t be causing the problem and that’s where I’m lost.
Could someone take a look at the BIOS file and see if there’s anything obvious or not so obvious that was missed or omitted?
I would also like to thank everyone in these forums for providing the resources and making them available to us. And a special thanks for those who have helped out on this journey so far @Lost_N_BIOS and @brams Both of you guys rock!
Here’s the file: http://s000.tinyupload.com/?file_id=96375957719417370084
Joining in on this: I did not try MIXCode, yet, but Maximus VIII Ranger and Hero. Flashing was not an issue for me (well - did take some time until I found out how to flash .bins from SKU-mods and automated mod tool), but no matter how I modify the UEFIs, I only get 1 sec “00” and immediate shutdown. The pin mod (I only shorted as there were no reports of isolating being necessary on M8R/M8H) does work, though, because without the board would not switch on at all.
Sample from my UEFI tries:
http://s000.tinyupload.com/index.php?fil…469531399341112
Asus UEFI 3802 for Ranger with Video and GOP update according to guide; Microcodes 506E3 for 6500K + 906EA/B/C
http://s000.tinyupload.com/index.php?fil…624177126061695
The same, but with SKU changed to Z370.
http://s000.tinyupload.com/index.php?fil…730491755466556
M8R8: Asus 3802 modded with revlaays tool + 906EC added with UBU.
http://s000.tinyupload.com/index.php?fil…764081323987149
M8HA: Asus 1001 for Hero with GOP-update and Microcodes 506E3 and 906EC. Uses IME 11.0.0.1168, while all Rangers are 11.6.10.1196
Neither of these does work (with CFL - SKL is no problem) and I hate not having a single clue why they don’t work 
@Deez and @revlaay - I often wondered why ME version was 11.7.0.229 in this tool, and in the past had always/only seen many users using 11.6.0.1126 or other similar. May be the solution for @mini-stx too
The actual ME version is 11.7.0.1229 and has proven to work.
Anything with 11.7.0.3xxx or above will fail.
Thanks for the confirmation @chinobino - is that confirmed for any/all cases now, and use of 11.6…x.x is no longer needed ever?
The source of the info is HWBot, dsanke used it with ASUS ROG MAXIMUS IX APEX.
[Edit] Looking for links
Has the inverse been proven as well:
Is anything below 11.7.0.1229 unsuitable for CFL-8?
That could be the reason for my failure (I do not have a CFL-6 ready for testing). I thought that only too new IMEs would prevent boot, so I tested with the oldest I could get my hands on without downgrade modding.
Yes, but maybe that does not apply to all cases, or has there been no other reports of issues on boards edited with that one since? Also good question @PCGH_Torsten