Re: Weird Bios won't update any more
Posted: Tue Mar 27, 2018 2:07 am
So want is needed is a UEFI shell tool that flags the UEFI to do the reclaim function now on the EFI Variable Storage area.
Now the "BIOS Engineer" should be call PHOENIX on the phone for the special little EFI application here. After all Compulab is the ODM/OEM .
They will not talk to the end customer. Only the ODM/OEM.
This web page is 100% relevant in my view to the EVSA exhaust issue.
https://countchu.blogspot.com/2014/10/o ... 9563175323
Wow he's even in Taiwan.
In this write-up "ToolB.efi" was used to force the reclaim function to engage using Fault Tolerant Write Protocol. Thus, writing the only most Current version variables to the backup area. Then setting the Primary EVSA area to all 1's then coping only the current version variables back to the primary area. They then occupy a minimum amount of space. Housekeeping.
And bingo the the EVSA area would be cleaned up. Thus ESVA error should be gone and the Firmware updating would then go thru.
Only issue with the article is that it does not tell where he got the "ToolB.efi" app from? Now I'm looking all over the net for it with no luck so far trying to find it.
Again it be way simpler for the BIOS ENGINEER to contact PHONENIX for such an APP and FIT-PC to post it on the website. Hell maybe PHOENIX is the source of the "ToolB.EFI" app in first place.
It just simple tool you run from shell64.
Now the "BIOS Engineer" should be call PHOENIX on the phone for the special little EFI application here. After all Compulab is the ODM/OEM .
They will not talk to the end customer. Only the ODM/OEM.
This web page is 100% relevant in my view to the EVSA exhaust issue.
https://countchu.blogspot.com/2014/10/o ... 9563175323
Wow he's even in Taiwan.
In this write-up "ToolB.efi" was used to force the reclaim function to engage using Fault Tolerant Write Protocol. Thus, writing the only most Current version variables to the backup area. Then setting the Primary EVSA area to all 1's then coping only the current version variables back to the primary area. They then occupy a minimum amount of space. Housekeeping.
And bingo the the EVSA area would be cleaned up. Thus ESVA error should be gone and the Firmware updating would then go thru.
Only issue with the article is that it does not tell where he got the "ToolB.efi" app from? Now I'm looking all over the net for it with no luck so far trying to find it.
Again it be way simpler for the BIOS ENGINEER to contact PHONENIX for such an APP and FIT-PC to post it on the website. Hell maybe PHOENIX is the source of the "ToolB.EFI" app in first place.
It just simple tool you run from shell64.