90Ninety_1

topic locked

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

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

Try using Asprogrammer , there is support for Ch341 added . I https://www.goprawn.com/forum/action-cam-control-software/8588-asprogrammer-with-ch341a-support

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

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

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 .

Historically I have successfully overclocked 'non-K' Skylake CPU's using modified Z170 BIOS for Gigabyte Mobos (bclk unlock) . I used modded BIOS files that are based on older BIOS versions IIRC . I done this around 2017 and subsequently acquired more PC's to play with . Today I forced downgraded My ASUS Z-170 P , the mobo's built in flash tool "EZ FLASH" would not allow me to downgrade . So I flashed using a FreeDOs (created with RUFUS ) 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 HWBOT 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 I have looked into why this went wrong, I have read some rumours that the Intel ME Firmware prevents old BIOS code from working. Before the downgrade the board had ME FW version 11.8.50.3470. However my understanding is that the ME FW resides on the BIOS chip, or am I wrong ? I presumed the ME version would be included as part of the Bios or modded BIOS image ? 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/ get rid this motherboard if it cant run unlocked 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 ?

Added entry for notifications

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 ?