1vyrain: A LiveUSB BIOS Modding Chain for xx30 ThinkPads

What the Exploit Chain Actually Unlocks

1vyrain is described as a software jailbreak that allows all IvyBridge-based xx30 ThinkPads to softmod custom BIOS images. The repository holds the main script and the pre-compiled binaries used in the 1vyrain image to flash machines, and the ready to go live USB image is linked separately.

The mechanism is an automatic exploit chain that unlocks the BIOS region for flashing, combined with model detection and automatic BIOS flashing. So the tool does two things: it gets past the check that normally prevents a modified BIOS from being written, and then it does the writing for you, picking the right image for the machine it detects.

The two halves matter separately. The exploit chain is what makes the operation possible at all on these machines, and the automatic flashing is what makes it repeatable rather than a manual procedure with a different set of steps per model.

The repository is small and readable: a start.sh, a tools/ directory, a patched-bios directory and a .gitmodules file, with the README carrying the operating instructions and the caveats. The project also publishes revisions with an MD5 given for each, so you can check that the image you downloaded is the one the author meant.

The Features You Get Once the BIOS Is Modded

The BIOS mod features are the reason to do this at all, and they are listed under their own heading.

Overclocking support is there for 35xx, 37xx, 38xx and 39xx CPUs, which is the set of processors where the stock firmware leaves performance on the table. Whitelist removal lets you use any WLAN or WWAN adapter, which is the feature most often cited by people who have replaced a card that was not on the list. The advanced menu exposes custom fan curve and TDP settings, which matters for anyone running a modified or quiet machine. And there is an Intel ME Soft Temporary Disable option through the advanced menu, which is the firmware management engine being held rather than fully disabled.

There is also support for custom BIOS images, with coreboot, skulls and heads named as examples, and the flashing process offers an option to flash a custom BIOS from a URL, so you are not restricted to the images the project ships.

The model detection and automatic flashing are worth calling out again, because they are the difference between this and a set of instructions. You boot the image, it works out which machine it is looking at, and it flashes the right thing.

Supported Machines, and the X330 Detection Quirk

The supported list is short and specific: X230, X330, X230t, T430, T430s, T530 and W530.

Two footnotes qualify it. The X330 machines are supported but not automatically detected, and they are detected as normal X230 machines, with the flashing menu carrying an additional option to flash a BIOS with the LVDS patch for machines detected as an X230. The LVDS patch is the display panel fix, and it is the option you need if you are on an X330 and want the correct screen behaviour.

The second footnote is broader: the -i models of the above are also supported because of a shared firmware and motherboard. It works because the firmware and the board are the same.

The BIOS version is a separate axis of compatibility, and the README is emphatic that you check it before beginning, linking to a compatibility list of BIOS versions. If you are not on a compatible version, or you are unsure, you run IVprep first, a separate project by the same author that prepares the machine for flashing. Clearing any BIOS passwords or settings prior to flashing is also required, and a BIOS settings reset is recommended if you can do one.

Burning the Image and Booting From USB

The installation is four steps, and two of them are about the hardware rather than the software.

First you burn the 1vyrain image onto a flash drive, and the validated and recommended tools are dd, Win32DiskImager, and Rufus with the note that you have to use DD mode. Second you boot in UEFI mode from the flash drive with Secure Boot off, and only boot the USB via the onboard USB ports, because USB ports on a docking station, an ultrabase and external USB hubs can cause issues. Third you follow the on-screen instructions, and fourth you are done.

The on-screen part is the flashing step, and the README pre-empts the most common panic. It says not to be alarmed if your ThinkPad or ThinkLight power cycles a few times after a flash, or if you get a CRC Security error, because that is normal and will go away after another restart.

The single most reassuring sentence in the README is about the EC. This will NOT modify the EC, so you are safe to flash your EC with the battery or keyboard mod at any time as long as you are on a version compatible with the EC mod, and both IVprep and 1vyrain will only modify the BIOS region. That means you can use this image to update to the latest modded BIOS without losing an EC mod, which is the constraint that would otherwise make people nervous about updating.

The Upgrade Path, and the Step the README Says Not to Skip

Upgrading from an older 1vyrain to a newer one is a documented sequence, and updates may include security bug fixes.

You remove any BIOS passwords, including supervisor passwords. It is suggested to reset the BIOS to default settings and save. You take out any non-whitelisted devices, because the FL1s are untouched. And then the crucial one: you use IVprep to downgrade to a flashable stock BIOS version, which the README marks as very important, do not skip.

The emphasis is repeated. The README says do not skip the IVprep process at step 4, that it is needed to safely reset to a stock BIOS version, and that this is different from using IVprep during installation to ensure you are using the proper image.

The difference between the two uses is worth understanding, because it explains why the upgrade needs an extra step. During installation, IVprep confirms you are on a BIOS version the process can handle. During an upgrade, IVprep takes the machine back to a stock state so the new image starts from a known point rather than from a previously modified BIOS region.

The steps are the same for downgrading or moving to any version, and the rule is the same throughout: obtain a compatible image for your machine, reset all passwords, reset to defaults, and use IVprep to downgrade.

Custom Images and Custom Splash Screens

Flashing your own image is a supported path rather than a hack on top of the tool. By default the image includes the latest BIOS versions for all models, but you can flash a custom image such as heads, skulls or a coreboot build.

The constraints are specific. You must have wired ethernet attached on boot, and your image must be exactly 4MB and uploaded somewhere you can fetch with a simple wget command. The fetch is http only, https is not currently supported, and you can use the --ignore-check-certificates flag when running wget manually. When asked what to flash, you select Flash a custom BIOS from URL, which is option 2, and input the URL.

The failure mode is benign, and the README says so directly: if your download fails or the file size was wrong, the flashing simply fails and you will not brick.

A custom splash image takes a longer route. You update with the original Lenovo update tool following the LOGO.txt instructions, read back the bios region with flashrom or FPTW, and then cut the first 8M of the rom:

dd if=backup.rom of=4M.rom bs=1M skip=8

After that you apply the xx30 patches for your model from the firmware-patches repository and fix the checksum with uefi-sign, downgrade with IVprep, and write it as a custom binary from the live USB.

The Risk the README Accepts on Your Behalf

The README is candid about the failure modes, and you should read the warning before anything else.

It says that although 1vyrain has been very thoroughly tested and there were zero bricks during testing, there are some random quirks associated with bypassing normal flashing methods, that things can always randomly go awry, and that there is no warranty or support guaranteed. It ends with a blunt sentence: I am not responsible for broken devices.

What follows is the part that determines how bad a failure can be. It is impossible to permanently brick a device with this method, and in the worst case scenario you can flash a backup or a fresh BIOS using a hardware programmer.

So the realistic worst case is a machine that needs a programmer and a backup, not a dead machine. That is a meaningfully different risk from the general idea of flashing firmware, and it is the reason the project can make a strong claim at all.

The issue reporting section adds process rather than technical caveats. Read the long form FAQ before opening an issue, search for prior issues with the problem, only open issues related to 1vyrain and IVprep, and do not open version compatibility issues for machines that are already supported. The repository has no stated licence, publishes no releases, and the last push was on 2026-09-18.

Editorial conclusion

1vyrain fits an owner of a supported ThinkPad who wants the advanced BIOS menu, overclocking or a wireless card the whitelist would otherwise block, and who is comfortable with a firmware procedure that involves flashing and, in some cases, downgrading first. It is a poor fit if you want a supportable configuration on a machine that still has to pass a corporate warranty process, and a poor fit for a laptop whose BIOS you cannot recover, since the README notes that a hardware programmer is the worst case recovery. Before running it, follow the preparation section exactly, clear BIOS passwords, run IVprep if you are unsure of your BIOS version, and use the staging of the official compatibility list rather than assuming. The repository has no stated licence, publishes no releases, and the last push was on 2026-09-18.

Frequently asked questions

Official sources

1. Issues
2. n4ru/1vyrain on GitHub
3. README