ressite.blogg.se

Uefitool releases
Uefitool releases










uefitool releases
  1. Uefitool releases update#
  2. Uefitool releases manual#
  3. Uefitool releases full#
  4. Uefitool releases pro#
  5. Uefitool releases windows#

Please proceed with caution and do not simply “try” something. We are modifying during this process the BIOS of your beloved Matebook, which can possibly brick it.

Uefitool releases update#

Finally, we need to delete any microcode update from Microsoft (removal of mcupdate_GenuineIntel.dll).īefore we start, a little warning. As multiple variables use the same offset in the Huawei BIOS, I suggest using Ru.exe instead of the default setup_var tools, as with Rue, we can select VarOffset and VarStore.

uefitool releases

Next, we need to modify this variable back to 0x0. In order to activate it, we need to do three things: First we need to find the offset (the location) of the variable in the UEFI variable storage. In recent BIOS, this variable was changed to 0x1 (enabled) and so undervolting was no longer possible. Until BIOS 1.5, this variable was set to 0x0 and so disabled. However, they were not really removed, they were only locked by an UEFI variable called “Overclocking Clock”. Some of you may remember that officially undervolting is only possible with BIOS versions up to 1.5 as, due to Plundervolt, Intel forced the device manufacturers to remove undervolting capabilities.

Uefitool releases pro#

Undervolting on Huawei Matebook X Pro 2020 i5 with BIOS 1.12, -75mV is stable for me. As proof, I present you here the results of this work on my Matebook X Pro, 2020, i5 version with BIOS 1.12 that I’ve undervolted to -75mV.

  • added support for parsing some some HP images that use EFI_GUIDED_SECTION_LZMA_HP GUID for their LZMA-compressed sections, thanks to added support for "Extract Uncompressed." and "Uncompressed Hex View." actions in UEFITool, both are useful in expecting the raw uncompressed data of compressed items, and will help catch and fix some otherwise invisible issues like #178, thanks to added support for proper parsing of ME File Partition Table header version 2.1, improved parsing of the previous versions 1.0 and 2.0, thanks to and fixed CI\CD, updated its configuration to use newer runners, fixed some Coverity warnings found because it's working again, thanks to and built Qt 5.6.3 as universal library for macOS, and updated unixbuild.Thanks to excellent posts of /u/Snoozhead and /u/Wouter_001, I have found a way of how we can enable undervolting on all Huawei Laptops, with all BIOS versions.
  • uefitool releases

    when the single binary is built natively for both x86-64 and arm64), but it also has some improvements and bugfixes:

  • fix for builds on multiple BSD variants for multiple architectures, thanks to and fix for C++17 compatibility, thanks to fix for CMake files to make UEFITool compatible with Qt 6.0/6.1/6.2, thanks to fix for OSes that call Qt5 qmake not just qmake, but qmake-qt5 (Fedora, FreeBSD), thanks to fixes to make static analysers happier, thanks to hack to make Kaitai-based parsers do one less memory copy, thanks to and new FlatHub app for UEFITool and the files required for it, thanks to first release of 2022 is mostly about testing the new universal binaries for macOS (i.e.
  • Uefitool releases windows#

  • fix for builds on Windows with MinGW, thanks to for reporting and for the fix.
  • fix for a crash during ME FPT parsing, thanks to for reporting and for the fix.
  • support for x86-64 128Kb Recovery Startup AP Data, a special 16 byte entry at a fixed address inside a Padding file in some PEI volumes on x86-64 PCs, thanks to support for AMI ROM Hole files, that need to remain at fixed base addresses inside the image, thanks to fixes and small improvements:.
  • It also adds FreeBSD to the list of supported OSes thanks to effort to make the tools buildable there.

    Uefitool releases full#

    This release is full of minor improvements and fixes for minor issues that laid unresolved for several years due to them being so minor. "Extract body" action did not work for some section types.Issues in descriptor and capsule parsing are non-fatal now, thanks to for reporting.UEFIExtract and UEFIFind can again be built with slightly older versions of CMake, thanks to for reporting.Unicode text search is working again, thanks to and for reporting.Universal macOS package for UEFITool is an app bundle again, thanks to and for reporting.Added -help (-h) and -version (-v) to UEFIExtract and UEFIFind, this makes them easier to use in scripts.Fixes are now in development, will be gradually included in the next updates. Added fuzzing targets for libFuzzer-compatible and AFL-compatible fuzzers, which already uncovered a treasure throve of issues.

    Uefitool releases manual#

    This is another step towards "minimize manual parsing" goal stated by rewriting FIT/ACM/BootGuard parsers in KS, other NVRAM-related parsers will follow in the next updates.

  • Replaced AMI NVAR parser with KaitaiStruct-based one.
  • uefitool releases

    A bugfix release, with huge thanks to all the people that reported those new bugs.












    Uefitool releases