![]() ![]() X99 D8 motherboard can be branded as Kllisre or JingSha, but it's the same motherboard with the same BIOS. ❗ This BIOS was not tested with the original Huananzhi motherboards.ĭownload Original BIOS for a noname X99 motherboard, which looks similar to Huananzhi X99-8MD3. ❗ This BIOS was taken from a motherboard with Intel B85 chipset. ![]() You have an LX vers 2.0, but there is an LX2 vers 1.0, that has similar numbers to mine, but only go up to 1701 and only shows on U.K.Can be found on AliExpress under Kllisre and Qiyida names.ĭownload Original BIOS for Machinist X99Z 16 MB. We also have vidcards with hybrid UEFI bios now, similarly causing anomolies during boot.Īnd yes, your LX bios have slightly dif numbers from mine (V-Pro/Deluxe). What you wind up with is based on how you configure settings in bios and how you configure MODE of install during O/S load.Īnd Intel says the UEFI org will continue to support MBR for 13 more years! "Bios" is no longer basic - its now legacy, but still around for compatibility. I think I would be relatively safe when flashing Haswell mobo, but dont know yet. efi file also on the USB stick, but only very slightly - lol.Īlways nice to know about the things NOT to do, so I do keep an eye on this issue. I am slightly tempted to try the CAPSULE cmd in AFUDOS with the 356K. I suppose I could start to investigate this, spending hours and hours of my precious time trying dif stuff, but I really dont care that much. So, yes bios settings (not the O/S installed per se) might now affect bios flash. Upon first glance, it would seem for the Secure Boot/CSM bios feature (Win 8 only) the loaded flash image itself NOW appears to be part of the "security". Note the new cmds for these types of flashes My guess is Microsoft had some input on this, either for hacking/modding prevention or better safety for those using Win 8, perhaps for secure boot related secure flash. There is really no reason I can think of to implement such a troublesome change to the bios flash. I really dont think ASUS should be blamed for this. net 4.5 (SP1) - it even is included in some ME driver downloads on ASUS site pages. I might also mention that your IMEI entry in dev man/system devices should have a driver AT LEAST as high as your current ME Oprom showing in bios. ![]() I forgot to mention you absolutely must use the Aptio folder for the flashers, not AMIBIOS folderįwiw I have found in the past that using latest DOS vers of AMI flasher works better (using cmds) for bad flashes, than the Win GUI. If you had a FB module you could downflash to say UEFI 1616 (after renaming to Z77VPRO.CAP) FIRST, then reflash back to 1908 or 2003. You have no flashback module - low end mobo vers, so you are essentially screwed. Of course any bios flash that includes an ME upgrade must also include a PSU unplugged CMOS reset before any first boot attempt. You cant fix a Z771908 (or higher) bad flash (interrupted/corrupted/aborted) by any other means than using flashback module to strip the new protections. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |