Error 451: The host CPU does not have write access to the target flash area. To enable write access for this operation you must modify the descriptor settings to give host access to this region. FPT Operation Failed.
Doesn’t look good.
It is reporting what I’ve said before, your Descriptor Region is locked. It’s very strange that you’re experiencing such issues as other users trying the same MEI firmware on the same chipset, have no problems at all. I think you should better try to do a Clear CMOS and trying to set up bios settings and boot into Windows and see if your LAN works.
Error 451: The host CPU does not have write access to the target flash area. To enable write access for this operation you must modify the descriptor settings to give host access to this region. FPT Operation Failed.
Doesn’t look good.
It is reporting what I’ve said before, your Descriptor Region is locked. It’s very strange that you’re experiencing such issues as other users trying the same MEI firmware on the same chipset, have no problems at all. I think you should better try to do a Clear CMOS and trying to set up bios settings and boot into Windows and see if your LAN works. Well i’ve done it multiple times already while trying 4 different BIOS versions. I also tried removing and reinstalling the drivers. Does this mean my ethernet is bricked completely?
No you haven’t bricked anything. Maybe there is some incompatibility between the MEI Firmware and the LAN, but if it worked before flashing the modded bios, it can’t suddenly stop to work.
You could try to boot a linux live distro, like Parted Magic and see if the LAN works. If it does, then it’s a Windows issue strictly related to the MEI firmware.
No you haven’t bricked anything. Maybe there is some incompatibility between the MEI Firmware and the LAN, but if it worked before flashing the modded bios, it can’t suddenly stop to work.
You could try to boot a linux live distro, like Parted Magic and see if the LAN works. If it does, then it’s a Windows issue strictly related to the MEI firmware.
Okay I tried to boot Lubuntu live usb and it still didn’t work. I tried wifi usb dongle just in case and that one worked so the problem is indeed in the ethernet controller and not in the linux distro.
Ok but if previously, with the MEI FW 11.0.0.1068 (native FW of Asus original bios) your LAN worked, then it could only be the MEI FW updated which makes your LAN to not properly work. In your case you can’t downgrade it in the “normal ways”, you’ve to remove your bios chip (after saving your info like the mac address, UUID and Mobo S/N) and reprogram it via external SPI Flash Eeprom programmer.
I’m very sorry my modded bios caused such issues, but these procedures are only at the risk of anyone who wants to try them.
Maybe it should be written in capital letters “Do it at your own risk”. I’ve modded so many bioses so far, and I always check if there could be any issues or compatibility problems. But things are never perfect.
I’m so sorry, anyway here is a video allowing to understand (if you will decide to do it yourself) how an eeprom programmer works and how reflash your bios.
I’m so sorry, anyway here is a video allowing to understand (if you will decide to do it yourself) how an eeprom programmer works and how reflash your bios.
I think I’d do more harm than good when physically removing the bios chip and soldering it back but thanks for the tip anyway. I guess I’ll just buy an external ethernet card.
I did so to solve the problem to the LAN took the old bios on asus site then deleted lan driver. USB BIOS Flashback bios 1 and 2 lan running again. Today proved again mod bios from a friend of mine and same problem with LAN
Please try this flasher. It is the same MEI version but without SKU, so the flasher should be able to reflash it correctly and maybe your LAN, after rebooting, will come back to work.
It doesn’t make sense for the problem to be ME-related. A locked ME region does not allow reflashing and thus the only change was the BIOS. Something is wrong there then. Some comments:
1. Use MEInfo (no errors) and MEManuf (Operation Passed) tools to verify the health of the ME region as a first step (even though I don’t believe the problem lies there).
2. That motherboard has a socketed SPI chip which can be very easily removed, reflashed and reinserted with a cheap programmer. There is no need for anything expensive or pin soldering.
3. ASUS USB BIOS FlashBack, which is what I assume you are using, flashes ONLY the BIOS region and nothing else from the SPI chip. So no Flash Descriptor, no GbE (if it exists), no ME etc. Only BIOS. Besides the Flash Descriptor being locked on that model, you cannot have caused harm to the ME region via BIOS FlashBack, not possible.
4. Since the Flash Descriptor is locked, sometimes the in-BIOS/UEFI flashers implemented by the OEMs can temporarily disable the ME in order for it to be serviced (reflashed) so they are capable of reflashing it if needed. If ASUS has such a feature, get the latest stock BIOS from them and flash it via the BIOS/UEFI menus and not USB FlashBack or anything else software-related.
5. By “no SKU” I assume you mean that the firmware is RGN and not EXTR, meaning no pre-configured (adjusted settings via FIT). This makes absolutely no difference when it comes to FWUpdate tool, only FPT or any other flasher (the latter when the FD is unlocked only).
6. The ME firmware is compatible/suitable with all these SKL-SPT S/H motherboards, there is no compatibility issues. The problem is not there. Maybe the updated LAN module is incompatible but I wouldn’t know about that. Ask SoniX at the UBU Discussion Thread.
