ASUS Z170 non-k unlock

[90Ninety_1]

I also have the Z170P 

I'd previously loaded unlocked Bclck with Provided unofficial BIOS for Z170 motherboards , as you can see here , there are many unofficial BIOS for unlocking the Bclck, on Z170 motherboards . : 
I previously had a 6500 running at 4.5Ghz on a GA 170 ( Gigabyte ) board . This was around a year ago . 

Today I flashed an ASUS Z-170 P , I flashed using a FreeDOs USB with the 'AFUDOS.exe' program ( See video Youtube vid)  . The board was previously running a 2018 BIOS ( 3805 ) with ME Firmware 11.8.50.3470. I downloaded the custom firmware from this thread ( Asus Z170-P 8008.cap)  . THe flash ran, it verified 100% , I restarted the machine , once , twice and realised I was stuck in the 'ASUS EZ flash' menu , It asked for the 8008.CAP, which I used to flash again . Ever since , I have been stuck on an 'EZ Flash ' menu , that fails to run with any USB drive connected . As shown in attached picture 

 

Luckily this Motherboard has a socketed type of EEPROM BIOS chip, and I can get a preflashed version for this board , though I might just bin this motherboard if it cant run unclocked Bclck BIOS .  SO  I am curious why this did not work out ? Is the BIOS and ME Firmware Related ? Does the ME Firmware prevent older or modded BIOS versions from working at all ?

Edited January 26, 2020 by 90Ninety_1

[90Ninety_1]

Added entry for notifications 

[DarthFK]

  

On 1/26/2020 at 1:20 PM, 90Ninety_1 said:

I also have the Z170P 

I'd previously loaded unlocked Bclck with Provided unofficial BIOS for Z170 motherboards , as you can see here , there are many unofficial BIOS for unlocking the Bclck, on Z170 motherboards . : 
I previously had a 6500 running at 4.5Ghz on a GA 170 ( Gigabyte ) board . This was around a year ago . 

Today I flashed an ASUS Z-170 P , I flashed using a FreeDOs USB with the 'AFUDOS.exe' program ( See video Youtube vid)  . The board was previously running a 2018 BIOS ( 3805 ) with ME Firmware 11.8.50.3470. I downloaded the custom firmware from this thread ( Asus Z170-P 8008.cap)  . THe flash ran, it verified 100% , I restarted the machine , once , twice and realised I was stuck in the 'ASUS EZ flash' menu , It asked for the 8008.CAP, which I used to flash again . Ever since , I have been stuck on an 'EZ Flash ' menu , that fails to run with any USB drive connected . As shown in attached picture 

Luckily this Motherboard has a socketed type of EEPROM BIOS chip, and I can get a preflashed version for this board , though I might just bin this motherboard if it cant run unclocked Bclck BIOS .  SO  I am curious why this did not work out ? Is the BIOS and ME Firmware Related ? Does the ME Firmware prevent older or modded BIOS versions from working at all ?

 

A similar issue here today, January 27, 2020 -- I very recently purchased an Asus z170 Pro Gaming and had some 2016 bios on it, so obviously not over 3xxx (not sure what firmware it was). I ran AFUDOS today with BIOS 1301 from Play3r and Overclockers (for non-k overclocking) - after AFUDOS "done, done, done" messages and all seemingly ok, the motherboard brings up EZ Flash in a loop, with the same loop "To finish BIOS update..." requesting the same CAP file as the ROM file used for AFUDOS flash. Huh?! Last summer I was able to flash with AFUDOS an Asus z170-A without any problems and in my case today I wasn't downgrading from 3xxx. Is it possible that some of the linked BIOSes are corrupt?

EDIT: I upgraded to 3805 via EZ Flash, otherwise was stuck. 3805 is the latest BIOs and then tried downgrading to 1301 and am still stuck in the same loop. I also tried using FPT to no avail, as the bios file is reported to be locked (error 368, I believe). Help!

Edited January 28, 2020 by DarthFK

[DarthFK]

  

19 minutes ago, DarthFK said:

  

 

A similar issue here today, January 27, 2020 -- I very recently purchased an Asus z170 Pro Gaming and had some 2016 bios on it, so obviously not over 3xxx (not sure what firmware it was). I ran AFUDOS today with BIOS 1301 from Play3r and Overclockers (for non-k overclocking) - after AFUDOS "done, done, done" messages and all seemingly ok, the motherboard brings up EZ Flash in a loop, with the same loop "To finish BIOS update..." requesting the same CAP file as the ROM file used for AFUDOS flash. WTF?! Last summer I was able to flash with AFUDOS an Asus z170-A without any problems and in my case today I wasn't downgrading from 3xxx. Is it possible that some of the linked BIOSes are corrupt?

EDIT: I upgraded to 3805 via EZ Flash, otherwise was stuck. 3805 is the latest BIOs and then tried downgrading to 1301 and am still stuck in the same loop. I also tried using FPT to no avail, as the bios file is reported to be locked (error 368, I believe). Help!

Hi @elmor and @der8auer - sorry for necrobumping this thread to 2020, but we're stuck. Your guide on overclocking guide, Der8auer, was taken down, so I am not usre what's going on, but we're stuck in an EZ Flash loop after trying the AFUDOS downgrade (in my case from a BIOS from 2016), and I got am error 368 BIOS locked, when I tried the FPT command prompt option. Help, please! Thank you and lots of respect!

[90Ninety_1]

12 hours ago, DarthFK said:

  

Hi @elmor and @der8auer - sorry for necrobumping this thread to 2020, but we're stuck. Your guide on overclocking guide, Der8auer, was taken down, so I am not usre what's going on, but we're stuck in an EZ Flash loop after trying the AFUDOS downgrade (in my case from a BIOS from 2016), and I got am error 368 BIOS locked, when I tried the FPT command prompt option. Help, please! Thank you and lots of respect!

Hi DarthFK 

I dont see the harm in adding to this thread, as it gives a better context of what we are trying to achive and shows its been done before 

I suspect the issue is the Intel ME firmware which  somehow interferes with the BIOS versioning. I heave heard from a BIOS chip supplier that the ME Firmware is burned onto the BIOS chip or added to the Microcode and it cannot be downgraded . 

 Lucky for me, I have a socketed type of BIOS chip . I also went out to and Purchased a USB Bios programmer tool ( the tool has a clip on alligator style  receptacle for soldered on chips though ! - See image )   and a spare bios chip with release BIOS ( earliest ).  I  think I fried my original BIOS chip after I re-flashed it ,  as I inserted it incorrectly ( it was super hot ) 

However I am hoping that the replacement chip will 'Just work' , then allow me to update to the 8001custom BIOS  ( as opposed to downgrade/ retro-burn ) . I am told by the supplier that the chip will not include the ME update and thus will work .  I will let you know how it goes .  

 

Edited January 28, 2020 by 90Ninety_1
spelling

[elmor]

I think on most platforms the ME is stored in a specific region on the BIOS chip, and a normal BIOS update using EZFlash or AFUDOS would just not update that area. Flashing through software (which usually uses the PCH interface) may have checks for version numbers to prevent downgrades. Using an external tool should always work as far as I know, with the only issue being losing the MAC address which is also stored on the BIOS chip. It may be possible to restore it if you made a backup, not sure. I think using an external flasher would have a very high chance of working.

 

Inserting it the wrong way reverses the VCC and Ground pins, worst case it should only damage the flash chip. I've done it myself in the past and nothing ever died, so you should be ok.

[DarthFK]

Thanks for the replies guys. It seems that we were thinking along the same lines. I already had a programmer, CH341A (and both 1.18 and 1.29 software for it), but never used it before - bought it for another project that finally never happened.

I also have a socketed type of the BIOS chip on this Asus z170 Pro Gaming - Winbond 25Q128FVIQ. I pulled it out and connected to my main PC via the CH341A etc. What happened, however, is that while it sees and reads the chip:

1. I saved the latest working 3805 BIOS into a backup in bin format, all ok seemingly (seemingly only!)

2. then downloaded the custom CAP (1301) from Play3r website and extracted the body into a BIN using UEfitool. I didn't try the hwbot "version" yet. Strike that - same story.

3. However, when I (erase and then) write the 1301.bin onto the chip I get "Chip main memory with the contents are in disagreement" upon verification. I tried to reconnect the chip to MB as is, and indeed it did not work.

4. If I extract the entire BIOS into a Bin file, then I get another error (BIOS too long or something like that).

5. When I tried to reflash the saved 3805 bios in bin format back onto ROM, I got the same "Chip main memory with the contents are in disagreement" - how can the original backed up BIOS re-written back onto the chip be a mismatch is beyond me!?

6. I just downloaded the 3805 bios from Asus, extracted it into a bin file and flashed onto the chip. Nope, "disagreement" again upon software verification.

Whatever I do, the chip is actually read, erased, but I cannot write anything onto it without an error message upon verification and even if I disregard the error, it still doesn't work with the mobo. It is again read by the programmer ok, but no luck with verification or actual functioning.

Any ideas would be really welcome:/

 

Edited January 28, 2020 by DarthFK

[90Ninety_1]

38 minutes ago, DarthFK said:

Thanks for the replies guys. It seems that we were thinking along the same lines. I already had a programmer, CH341A (and both 1.18 and 1.29 software for it), but never used it before - bought it for another project that finally never happened.

 

I have the same model Programmer but , not having this issue . Though I did note that only the 1.18 version of the program allowed to read the chip, all other versions had problems . The 1.18 version did not identify my BIOS chip and the chip is not listed within the lookup utility within the  flashing program . I noticed the newer versions of the flashtool has more entries within the chip finder utility  .

I could also write to my chip  though something must have gone wrong as I cannot get a POST with the chip irrelevant of version I flash to it . I originally presumed I fried the chip , or something is wrong was wrong  the Flashing Method I am using . I am thinking the the ME Version is preventing the BIOS from flashing  correctly, perhaps that was part of its purpose .  In any case a new chip with stock BIOS seems the best option so far. 

Not sure what the MAC address will be on the new chip or how to program it , I will cross that bridge when I get to it . I hope it just has a copy from another board I guess 

 

 

[90Ninety_1]

All fixed now . A New BIOS chip with release BIOS  (first version ) worked perfect . I then proceeded to update to 8001

 

@DarthFK 

Go get yourself a new BIOS chip with a Preloaded early BIOS version ( as I did for £8 )  , chances are the Intel ME Firmware has bricked the BIOS chip 

 

 

[90Ninety_1]

6 hours ago, DarthFK said:

Thanks for the replies guys. It seems that we were thinking along the same lines. I already had a programmer, CH341A (and both 1.18 and 1.29 software for it), but never used it before - bought it for another project that finally never happened.

I also have a socketed type of the BIOS chip on this Asus z170 Pro Gaming - Winbond 25Q128FVIQ. I pulled it out and connected to my main PC via the CH341A etc. What happened, however, is that while it sees and reads the chip:

1. I saved the latest working 3805 BIOS into a backup in bin format, all ok seemingly (seemingly only!)

2. then downloaded the custom CAP (1301) from Play3r website and extracted the body into a BIN using UEfitool. I didn't try the hwbot "version" yet. Strike that - same story.

3. However, when I (erase and then) write the 1301.bin onto the chip I get "Chip main memory with the contents are in disagreement" upon verification. I tried to reconnect the chip to MB as is, and indeed it did not work.

4. If I extract the entire BIOS into a Bin file, then I get another error (BIOS too long or something like that).

5. When I tried to reflash the saved 3805 bios in bin format back onto ROM, I got the same "Chip main memory with the contents are in disagreement" - how can the original backed up BIOS re-written back onto the chip be a mismatch is beyond me!?

6. I just downloaded the 3805 bios from Asus, extracted it into a bin file and flashed onto the chip. Nope, "disagreement" again upon software verification.

Whatever I do, the chip is actually read, erased, but I cannot write anything onto it without an error message upon verification and even if I disregard the error, it still doesn't work with the mobo. It is again read by the programmer ok, but no luck with verification or actual functioning.

Any ideas would be really welcome:/

 

Try using Asprogrammer , there is support for Ch341 added . I

https://www.goprawn.com/forum/action-cam-control-software/8588-asprogrammer-with-ch341a-support

[DarthFK]

Thanks for the update! I got the AsProgrammer, but never tried it. Need to learn how. 

Assuming this is ME, I'll probably still need to buy a new chip. Where did you buy yours? That seller on ebay from Netherlands? Any recommendations? (I am in New York though, seeing you buying in pounds, recommendations may not be valid, but who knows:)

[DarthFK]

P.S. my chip is also read and is written y programmer, but throws the verification error and fails to post. So, I assume that buying a new chip is the only solution to this possible ME block.

[90Ninety_1]

5 minutes ago, DarthFK said:

Thanks for the update! I got the AsProgrammer, but never tried it. Need to learn how. 

 

Its piss easy, just download the zip from the GitHub link , within the above post . Extract ,  run both the serial and parallel driver exe's ( you may need to uninstall first - I did  ) 

Restart your machine, Load the 'Asprogrammer.exe' , click on hardware tab >select CH341a ( or whatever matches your usb tool ) >  Click 'IC' >search Type in your IC code ( the markings on your chip - Mine is 25Q128F) >select your IC from results > Click read .  From this point its pretty straight forward 

[DarthFK]

3 hours ago, 90Ninety_1 said:

 

Its piss easy, just download the zip from the GitHub link , within the above post . Extract ,  run both the serial and parallel driver exe's ( you may need to uninstall first - I did  ) 

Restart your machine, Load the 'Asprogrammer.exe' , click on hardware tab >select CH341a ( or whatever matches your usb tool ) >  Click 'IC' >search Type in your IC code ( the markings on your chip - Mine is 25Q128F) >select your IC from results > Click read .  From this point its pretty straight forward 

OMG, OMG, OMG, OMG, OMG!!!!!!!!! Your simple but useful intro to Asprogrammer and that software did it!!! No error, nothing bad, just did the job. I am now running the custom bios - I was able to downgrade via the CH341A usb programmer and Asprogrammer 1.41:) Thank you kindly @90Ninety_1  

So, the conclusion in my case is that in worst case scenario it is possible to downgrade a BIOS via an USB programmer and AsProgrammer software, rather than "native" CH341 software. I am actually writing this post from that (10 minutes ago) bios-downgraded Asus z170 Pro Gaming PC  

Edited January 29, 2020 by DarthFK

[90Ninety_1]

13 hours ago, DarthFK said:

OMG, OMG, OMG, OMG, OMG!!!!!!!!! Your simple but useful intro to Asprogrammer and that software did it!!! No error, nothing bad, just did the job. I am now running the custom bios - I was able to downgrade via the CH341A usb programmer and Asprogrammer 1.41:) Thank you kindly @90Ninety_1  

So, the conclusion in my case is that in worst case scenario it is possible to downgrade a BIOS via an USB programmer and AsProgrammer software, rather than "native" CH341 software. I am actually writing this post from that (10 minutes ago) bios-downgraded Asus z170 Pro Gaming PC  

Glad it worked out for you . I fried my chip ( inserted it wrong ) 

Send us a like if I was helpful , make a name here for myself 
Thanks 

[olain]

On 1/28/2020 at 9:59 PM, 90Ninety_1 said:

Ebay 

 

Here for example: 

https://www.ebay.co.uk/itm/BIOS-Chip-ASUS-Z170I-PRO-GAMING/401105188104?hash=item5d63bb7508:g:RpAAAOSwKfVXEKR1

 

Message the seller , ask for board and bios version - Bingo !

Hi 90Ninety_1

I have an ASUS Z170i Pro Gaming, and I found the BIOS that allows BCLK OC here: Z170I-PRO-GAMING-ASUS-9006.zip

So I am curious, wouldnt I be able to just us an official ASUS Bios PRIOR to the Microcode update back in february 2016? Did those previous BIOS not allow for BCLK, or what was the reason for all the custom BIOS that were made?

Anyway, Hope to hear from you, since I want to buy a new BIOS on ebay and make sure its already flashed with the correct BIOS And old Intel ME Firmware.

[scrchd]

Hello! I dloaded custom bios for my asus z170-a and it works completely fine, but there is an issue in windows, after about 15 minutes of using the computer with my overclocked i7 6700

(4.7 ghz 1.35v) the "clock watchdog timeout " blue screen appears, did anyone face this problem or can anyone give me some advive? After this i had to install the latests bios again and it works stable.

[DarthFK]

On 5/29/2020 at 7:38 AM, scrchd said:

Hello! I dloaded custom bios for my asus z170-a and it works completely fine, but there is an issue in windows, after about 15 minutes of using the computer with my overclocked i7 6700

(4.7 ghz 1.35v) the "clock watchdog timeout " blue screen appears, did anyone face this problem or can anyone give me some advive? After this i had to install the latests bios again and it works stable.

Yes, I did. In my case it was a too high memory speed. I also added some voltage to my memory. When I lowered it manually in BIOS, the BSODs went away.

My memory timings are 3600cl17 and it would refuse to start in XMP at that speed - I did not use the XMP for that reason, but had to manually select a memory speed close to 3000mhz. Der8auer in his old posts recommended lowering the memory speed to at least (as in no higher than) 2800mhz, if I remember correctly. You may want to try that.

Edited May 30, 2020 by DarthFK

[scrchd]

On 5/30/2020 at 11:23 PM, DarthFK said:

Yes, I did. In my case it was a too high memory speed. I also added some voltage to my memory. When I lowered it manually in BIOS, the BSODs went away.

My memory timings are 3600cl17 and it would refuse to start in XMP at that speed - I did not use the XMP for that reason, but had to manually select a memory speed close to 3000mhz. Der8auer in his old posts recommended lowering the memory speed to at least (as in no higher than) 2800mhz, if I remember correctly. You may want to try that.

well my memory speed was 2133mhz so i dont thnk its too high, i dont really know what to do, any ideas?

 

[DarthFK]

10 minutes ago, scrchd said:

well my memory speed was 2133mhz so i dont thnk its too high, i dont really know what to do, any ideas?

 

Then, if you have a fresh windows & drivers install and you are running from a dedicated GPU, the only reasonable explanation to a clock watchdog timeout is insufficient vcore, possibly other voltages. I would normally try both a slightly higher vcore & lower too! I know, it doesn't sound scientific, but shtuff happens even in computers. Sometimes the CPU is not of the best quality, sometimes the interaction between the cpu & the boards is not.

It happened on one of my BCLK overclocks that I had to do a standard oc voltage upping, like on a K sku, as well as power limits removal, llc, etc (the whole oc) if you can imagine that. It was a Gigabyte board. But ultimately it worked. I haven't had a board yet to fail the BCLK oc, but initially I did had BSODs on all of them, until I did more fine-tuning, just like on a K sku overclocking.

So try only lowering vcore, then only upping vcore, to say 1.36v, then try full voltage/power oc and perhaps try after stabilizing it to slightly raise the RAM speed & dram voltage, and VCCSA/VCCIO voltages.

[scrchd]

On 6/3/2020 at 12:58 AM, DarthFK said:

Then, if you have a fresh windows & drivers install and you are running from a dedicated GPU, the only reasonable explanation to a clock watchdog timeout is insufficient vcore, possibly other voltages. I would normally try both a slightly higher vcore & lower too! I know, it doesn't sound scientific, but shtuff happens even in computers. Sometimes the CPU is not of the best quality, sometimes the interaction between the cpu & the boards is not.

It happened on one of my BCLK overclocks that I had to do a standard oc voltage upping, like on a K sku, as well as power limits removal, llc, etc (the whole oc) if you can imagine that. It was a Gigabyte board. But ultimately it worked. I haven't had a board yet to fail the BCLK oc, but initially I did had BSODs on all of them, until I did more fine-tuning, just like on a K sku overclocking.

So try only lowering vcore, then only upping vcore, to say 1.36v, then try full voltage/power oc and perhaps try after stabilizing it to slightly raise the RAM speed & dram voltage, and VCCSA/VCCIO voltages.

ok thank you so much, now i know that its my own problem, gonna try everything soon!

[Terminasitor]

Hi I have just downloaded and installed the bios in my z170-p mb.All seems to be working fine except that I can not properly restart my pc (when I try to restart I get an error message and get redirected to the bios).This does not happen when I start rhe PC normally.Is this to be expected or am I missing something?

[DarthFK]

40 minutes ago, Terminasitor said:

Hi I have just downloaded and installed the bios in my z170-p mb.All seems to be working fine except that I can not properly restart my pc (when I try to restart I get an error message and get redirected to the bios).This does not happen when I start rhe PC normally.Is this to be expected or am I missing something?

Not sure without seeing the error message and even then... But first can you take a picture of the error? Like a phone pic?

[Terminasitor]

On 6/23/2020 at 7:06 PM, DarthFK said:

Not sure without seeing the error message and even then... But first can you take a picture of the error? Like a phone pic?

I am sorry! I know I am really late to respond to this but I think the problem was with my windows installation, after a clean install everything worked fine!

[DarthFK]

10 minutes ago, Terminasitor said:

I am sorry! I know I am really late to respond to this but I think the problem was with my windows installation, after a clean install everything worked fine!

Cool! I always did clean installs on my z170 non-k experiments, as well as appropriate drivers. I no longer have any non-k or z170, though, so thanks for sharing with those who might one day dabble in this "antique" department :) 

Be well!! (not the most trivial wish these days)