Insyde Driver



  • BIOS Recovery
  • Modification Downloads
  • Help Resources

Inside Drivers

WIFI Whitelist Removal Petition

Insyde Airplane Driver

Debug codes: Can be used by any PEIM/driver for debug: 10 – 1F: Host Processors: 20 – 2F: Memory/Chipset: 30 – 3F: Recovery: 40 – 4F: Reserved for future use: 50 – 5F: I/O Busses: PCI, USB, ISA, ATA, and so forth: 60 – 6F: Not currently used: 70 – 7F: Output Devices: All output consoles: 80 – 8F: Reserved for future use (new.

A vulnerability exists in older versions of a kernel mode driver (version 100.00.09.01 or earlier) included in Insyde Software’s BIOS tool. The driver creates a virtual note and loads the kernel driver at runtime to gain access to system resources for flashing BIOS. The only thing that prevented that worthless Insyde Airplane driver from constantly reinstalling itself was to disable the Windows Update service. That registry hack shown at howtogeek sure looked promising, and maybe it used to work, but it certainly isn't working now.

Recently one of our forum members, EvanCarroll, started an online petition to request the removal of WIFI whitelists from Lenovo bios. I highly encourage everyone here to support this effort by taking a minute out of your day to sign it. If an online petition can get 270,000+ signatures supporting the deportation of Justin Bieber, then we should at least be able to get a few thousand to support the removal of WIFI whitelists. Thanks! 😀

… >>>Click Here To Continue Reading

Universal IFR Extractor

In case you didn’t already know, the Extensible Firmware Infrastructure’s Human Interface Infrastructure uses Internal Forms Representation protocol to display things like your setup utility’s menu. By having access to the Internal Forms Representation, we can know everything about a menu which can assist us immensely when modding bios. I’ll also be using this application in a few of the tutorials I write, so get used to using it now 🙂

I was getting tired of all the requests to expand EFI IFR Dumper to include support for UEFI’S IFR protocol, and as a result I decided that now is a better time than any to update my program.… >>>Click Here To Continue Reading

Module Helper

I first started working on Module Helper back in September when Andy’s tool V2.19 was released. As some of you may know, that iteration altered the format of the extracted EFI modules by storing a module’s header, code, and name all in the same file. This created some issues with disassemblers not being able to automatically recognizing the format of the EFI modules and the size of data modules not being updated if changed. Dealing with all these negative aspects was trivial but annoying, which is why Module Helper was developed. It was originally capable of splitting the modules header and data into separate files an it could update the sizes in the headers.… >>>Click Here To Continue Reading

Training the Next Generation of BIOS Modders

Dear BIOS-Mods.com community,

BIOS-Mods.com for years has been and continues to be an open, collaborative space to help users around the world make the most of their motherboards, hardware platforms, and computers as a whole. Over the years, we have had many talented developers come and go who have all left tremendous impacts on our ability to modify BIOS images and provide the know-how for people who like “Do it Yourself” projects.

We would like to start an open-knowledge initiative to help recruit and train new moderators at BIOS-Mods.com with the wealth of information there is to be shared.… >>>Click Here To Continue Reading

Inside Driver Door Panel 2009 Traverse

BIOS Spotlight: (UEFI) Dell XPS 15z L511z

This article documents the exciting work being done by some of the top contributors in our forum. The modifications performed on systems like the Dell 15z reflect the most advanced examples of BIOS modifications done within our community. For more information, please visit the thread.
Phoenix SecureCore Tiano, used by Dell, is a tough nut to crack – we came to what we have today by taking little steps on a road that wasn’t smooth to begin with. Phoenix nor Dell have provided any information regarding SCT 2.0 and to this day the BIOS on these machines has not been upgraded to 2.3.1 which allows for ME v8 (brings IVB CPU support) and SecureBoot capabilities.… >>>Click Here To Continue Reading

Product Review: Eken 7″ Android MID Tablet M009F

The Eken 7″ Android MID M009F tablet is powered by an InfoTMIC 800MHz CPU, 186 MB RAM, 2 0r 4 GB of storage space (Upgradeable to 16GB via an SD memory card), a 7″ 800×480 resistive screen, and WiFi (802.11 a/b/g/n).

Beware of this and other copycat tablets like it. If you are in the market for a tablet, do your homework first. These tablets do run Android, and the one I tested was quite compatible with most Android apps. However, these tablets do not perform anything like an iPad. It has a “resistive” touch screen that requires a stylus, or fingernail, to operate. Using the tip of your finger just will not work, which makes this tablet hard to use.… >>>Click Here To Continue Reading

Driver Agent: Finding BIOS Upgrades and Drivers Quick and Easy

Driver Agent, one of esupport.com’s flagship products, makes it easy for the average user to scan a computer for out-of-date drivers and software. In addition to the Driver Agent software, BIOS Agent helps customers locate the best BIOS stock BIOS image for their computer. For users who are tentative about upgrading their computers to the latest version of drivers and software, Driver Agent shows you out of date drivers with an effective online web scan.

BIOS-Mods.com had the opportunity to review the software to assess whether or not it is truly a viable solution for the average consumer to keep their PC up-to-date.… >>>Click Here To Continue Reading

Inside Driver Side Of Truck

The INs and OUTs of Windows 8 Consumer Preview

After using Windows 8 Consumer Preview since the release date, there are certain issues that should be addressed. Not only does Windows 8 have a new “Metro” interface that many people are still adapting to, but there are several changes to how software will behave while running Windows 8 CP.

The first and possibly the most important one is Windows 8 does NOT support the Microsoft Visual C++ 2005 Redistributable Package. This means that if your software requires this package, you will have to buy new software that has a later version of the package or one that does not use it at all.

Another issue with Windows 8 is browsing the web with Firefox on a computer with an NVIDIA GPU.… >>>Click Here To Continue Reading

Contact UsAbout Us

Copyright © 2013 Bios Mods -The Best BIOS Update and Modification Source. All Rights Reserved.

  • Note: With OpenCore 0.6.6, Bootstrap.efi has been replaced with LauncherOption. See here for more info on updating: Updating Bootstrap in 0.6.6

With OpenCore 0.6.6 and newer, we are now able to launch OpenCore directly from our firmwares without needing a launcher (Bootstrap.efi or BOOTx64.efi) as an intermediary. This allows us to add OpenCore to our motherboard's boot menu and prevent issues where either Windows or Linux try to overwrite the EFI/BOOT/BOOTx64.efi path, which can happen when installing or updating Windows and therefore breaking OpenCore's ability to boot.

# Prerequisites

  • OpenCore 0.6.6 or newer(opens new window)
    • For 0.6.5 and older users upgrading, see here: Updating Bootstrap in 0.6.6
  • config.plist settings:
    • Misc -> Boot -> LauncherOption = Full
      • Use Short for Insyde based firmwares, commonly found on laptops
    • UEFI -> Quirks -> RequestBootVarRouting = True
  • OpenShell(opens new window)
    • Bundled with OpenCore
    • Remember to add this to both EFI/OC/Tools and Misc -> Tools
    • This is mainly for troubleshooting

# Booting

If everything is set up correctly, the first boot will have OpenCore create a new boot option in our BIOS (pointing to EFI/OC/OpenCore.efi) and future boots will update the entry making sure it's correct and ensuring it is still present. This now allows us to remove BOOTx64.efi and not worry about other OSes overwriting the EFI/BOOT/BOOTx64.efi path.

# Troubleshooting

If no new boot option is created, you can follow these troubleshooting steps but first double-check the prerequisites were met. The following sections are a mini-guide in case LauncherOption doesn't work or you'd like to do it manually.

Insyde software driver

# Verify LauncherOption entry was applied

For those wanting to verify that the entry was applied in OpenCore, enable logging (see OpenCore Debugging(opens new window)) and check for entries similar to these:

# Removing LauncherOption entry from BIOS

Because the LauncherOption entry is a protected entry when resetting NVRAM, you'll need to disable LauncherOption first before you can remove it:

  • Misc -> Security -> AllowNvramReset -> True
  • Misc -> Boot -> LauncherOption -> Disabled

Once these are set, you can reboot into the OpenCore picker and select the Reset NVRAM entry to clear your NVRAM, which will remove the LauncherOption entry too..

# Updating Bootstrap in 0.6.6

For those updating to 0.6.6, you may have noticed Bootstrap.efi has been removed from OpenCore. This is due to changes with how OpenCore works; specifically OpenCore is now a UEFI application instead of a driver. This means OpenCore.efi can be loaded directly and a launcher (Bootstrap.efi) is no longer needed.

# With Bootstrap disabled

If Bootstrap is disabled prior to updating to 0.6.6, you don't need to make any changes, just the usual file swapping. If afterwards you would like to try LauncherOption, you can do so with no issues.

Driver

# With Bootstrap enabled

If Bootstrap is enabled prior to updating to 0.6.6, and your motherboard's firmware will autodetect EFI/BOOT/BOOTx64.efi, you can do the following before you update:

  1. Set Misc -> Security -> AllowNvramReset to True and Misc -> Security -> BootProtect to None, then reset NVRAM (either outside of or in OpenCore) and boot. This will get rid of the old Bootstrap boot entry.

  2. Update your OpenCore setup as normal, ensuring that you copy BOOTx64.efi from the OpenCore package to EFI/BOOT/BOOTx64.efi and set Misc -> Boot -> LauncherOption in your config.plist to Full (or Short if previously using BootstrapShort).

  3. Reboot.

    On first boot you will need to boot from EFI/BOOT/BOOTx64.efi, but on subsequent boots you should see the LauncherOption entry created by OpenCore directly booting OpenCore.efi.

If your firmware does not automatically detect EFI/BOOT/BOOTx64.efi or you cannot put OpenCore's launcher there for any reason, you have multiple other options:

Driver Insyde Bios

  • Put OpenShell.efi on a USB, rename and move to EFI/BOOT/BOOTx64.efi, and follow the above steps, except insteading of selecting BOOTx64.efi from the boot menu, boot into the USB and launch OpenCore from there directly.
  • Add a folder EFI/OC/Bootstrap and copy and rename BOOTx64.efi from the OpenCore package to EFI/OC/Bootstrap/Bootstrap.efi. Then, after updating your OpenCore setup, set Misc -> Boot -> LauncherOption to the appropriate option (Full, or Short if previously using BootstrapShort) and boot OpenCore using the existing entry create by Bootstrap. After your first boot, you should see a new OpenCore boot entry added. You can then reset NVRAM in OpenCore (making sure to keep LauncherOption enabled so you don't delete the new entry) to get rid of the old Bootstrap boot entry.

Conversion notes:

Insydeflash Driver

0.5.8 - 0.6.50.6.6+
Misc -> Security -> BootProtectMisc -> Boot -> LauncherOption
BootstrapFull
BootstrapShortShort