Difference between revisions of "Flashing BIOS from Linux"

From ArchWiki
Jump to: navigation, search
m (Images that are too large for a floppy)
m (add T450s)
 
(43 intermediate revisions by 24 users not shown)
Line 1: Line 1:
 
[[Category:Mainboards and BIOS]]
 
[[Category:Mainboards and BIOS]]
 +
[[ja:Linux から BIOS を書き換える]]
 
This article aims on providing information on flashing your system BIOS under Linux. Most manufacturers provide a Windows executable or a BIOS executable that can only be run under Windows. However, there are a few utilities, that allow you to upgrade your system BIOS under Linux.
 
This article aims on providing information on flashing your system BIOS under Linux. Most manufacturers provide a Windows executable or a BIOS executable that can only be run under Windows. However, there are a few utilities, that allow you to upgrade your system BIOS under Linux.
  
{{Warning|Flashing motherboard BIOS is a dangerous activity that can render your motherboard inoperable! While the author of this article has successfully run this procedure many times, your mileage may vary. Be careful!}}
+
{{Warning|Flashing motherboard BIOS is a dangerous activity that can render your motherboard inoperable! While the author of this article has successfully run this procedure many times, your mileage may vary. Be careful! You may want to consider updating [[microcode]] instead if it is supported by your system.}}
  
==Introduction==
+
== BiosDisk ==
There are a few ways that you can use to flash the system BIOS under Linux.
+
[http://linux.dell.com/git/biosdisk.git BiosDisk] BiosDisk simplifies the process of flashing your system BIOS under Linux
  
==BiosDisk==
+
=== Installation ===
[http://linux.dell.com/biosdisk/ BiosDisk] BiosDisk simplifies the process of flashing your system BIOS under Linux
+
[[Install]] the {{AUR|biosdisk-git}} package.
===Installation===
+
====Method 1: AUR (Recommended)====
+
[https://aur.archlinux.org/packages.php?ID=38248 BiosDisk] is available from the Arch User Community Repositories.
+
  
====Method 2: From Source====
+
=== Usage ===
Grab the source from the [http://linux.dell.com/biosdisk/ biosdisk] web page. Extract the source from the tar ball, cd into the directory and run
+
sudo sh install.sh
+
 
+
===Usage===
+
 
To use the biosdisk utility to create a BIOS flash image, first download the latest raw BIOS image for your system from your manufacturer's website. Make sure however, that you always get the BIOS executable and NOT the Windows executable. You then have one of several options: create a floppy, create a dd floppy image, create a user-installable distribution-specific package (e.g. RPM), or actually install the image for your bootloader.
 
To use the biosdisk utility to create a BIOS flash image, first download the latest raw BIOS image for your system from your manufacturer's website. Make sure however, that you always get the BIOS executable and NOT the Windows executable. You then have one of several options: create a floppy, create a dd floppy image, create a user-installable distribution-specific package (e.g. RPM), or actually install the image for your bootloader.
  
Line 36: Line 30:
 
     biosdisk install [-o option] [--name=] /path/to/{.exe | .img}
 
     biosdisk install [-o option] [--name=] /path/to/{.exe | .img}
  
==Flashrom==
+
== Flashrom ==
 
[http://www.flashrom.org/Flashrom Flashrom]is a utility for identifying, reading, writing, verifying and erasing flash chips. It is designed to flash BIOS/EFI/coreboot/firmware/optionROM images on mainboards, network/graphics/storage controller cards, and various programmer devices.
 
[http://www.flashrom.org/Flashrom Flashrom]is a utility for identifying, reading, writing, verifying and erasing flash chips. It is designed to flash BIOS/EFI/coreboot/firmware/optionROM images on mainboards, network/graphics/storage controller cards, and various programmer devices.
  
===Installation===
+
=== Installation ===
====Method 1: Community Repo (Recommended)====
+
sudo pacman -S flashrom
+
  
====Method 2: AUR====
+
[[Install]] the {{pkg|flashrom}} or {{AUR|flashrom-svn}} package.
[https://aur.archlinux.org/packages.php?ID=23390 Flashrom-svn] is also available from the Arch User Community Repositories.
+
  
====Method 2: From Source====
+
=== Usage ===
Grab the source from the [http://www.flashrom.org/Flashrom Flashrom] web page. Extract the source from the tar ball, cd into the directory and run
+
Find out if your motherboard and chipset (internal) is supported by flashrom at this website. [http://www.flashrom.org/Supported_hardware Supported Hardware]
make
+
make install
+
 
+
===Usage===
+
Find out if your motherboard and chipset is supported by flashrom at this website. [http://www.flashrom.org/Supported_hardware Supported Hardware]
+
 
You can also find out if your hardware is supported by issuing the following command
 
You can also find out if your hardware is supported by issuing the following command
  sudo flashrom
+
  # flashrom --programmer internal
The above command will tell you your motherboard and chipset. You can then find out if your's is supported by issuing this command
+
 
  flashrom -L | grep whatevernameyougotfromthefirstcommand
+
The above command will tell you your motherboard and chipset. You can then find out if yours is supported by issuing this command:
 +
  # flashrom --programmer internal -L | grep CHIPNAMEfrompreviouscommand
 +
 
 +
On modern mainboards you probably get more than one rom chip listed. You have to select the chipname you get from the upper command. Then you use the {{ic|-c}} option to select which rom is affected by the command
 +
# flashrom --programmer internal -c "CHIPNAME" -r backup_CHIPNAME.bin
 +
 
 +
Write and verify the new BIOS image (proprietary or Coreboot) on the ROM chip:
 +
# flashrom --programmer internal internal -c "CHIPNAME" -w newbios.bin
  
Read the BIOS image into a file:
+
If you want to flash other flash chips on your mainboard, you will find all options with
  $ flashrom -r backup.bin
+
# flashrom
Write a BIOS image (proprietary or LinuxBIOS) on the ROM chip:
+
  $ flashrom -w newbios.bin
+
  $ flashrom -v newbios.bin
+
  
==FreeDOS==
+
== FreeDOS ==
 
[http://www.freedos.org/ FreeDOS] a free DOS-compatible operating system, is up to the challenge, no need for proprietary DOS versions. So, all you need is a bootable floppy disk image with FreeDOS kernel on it.
 
[http://www.freedos.org/ FreeDOS] a free DOS-compatible operating system, is up to the challenge, no need for proprietary DOS versions. So, all you need is a bootable floppy disk image with FreeDOS kernel on it.
  
===Unetbootin===
+
=== Unetbootin ===
By far the easiest way to make a bootable FreeDOS USB Stick is using {{pkg|unetbootin}}, available in the [[Official Repositories]].
+
By far the easiest way to make a bootable FreeDOS USB Stick is using {{pkg|unetbootin}}, available in the [[Official repositories]].
  
You should format a pendrive with FAT16 and flag it as "boot" (you may do this through a GUI with {{Pkg|gparted}}, {{AUR|qtparted}} or {{AUR|partitionmanager}}). Then, after mounting the flash drive, select under distribution '''FreeDOS''' and your mounted stick. The app will automatically download the image for you and copy it to the drive. Finally, you may copy everything you want to flash there (BIOS, firmwares, etc).
+
You should format a pendrive with FAT16 and flag it as "boot" (you may do this through a GUI with {{Pkg|gparted}}, {{AUR|qtparted}}{{Broken package link|{{aur-mirror|qtparted}}}} or {{Pkg|partitionmanager}}). Then, after mounting the flash drive, select under distribution '''FreeDOS''' and your mounted stick. The app will automatically download the image for you and copy it to the drive. Finally, you may copy everything you want to flash there (BIOS, firmwares, etc).
  
If you want to do it the hard way, keep reading. ;)
+
{{Warning|Unetbootin may not function properly on some Lenovo systems. It may be necessary to create the bootable stick on a different device. See [http://reboot.pro/topic/9849-blinking-cursor-at-boot/ here].}}
  
===Gentoo===
+
=== Gentoo ===
Check out [http://en.gentoo-wiki.com/wiki/FreeDOS_Flash_Drive FreeDOS Flash Drive] on the Gentoo Wiki if you want to create a bootable FreeDOS Flash drive.
+
Check out [https://wiki.gentoo.org/wiki/BIOS_Update#FreeDOS_environment FreeDOS Flash Drive] on the Gentoo Wiki if you want to create a bootable FreeDOS Flash drive.
  
===Images that are too large for a floppy===
+
=== Prebuilt images ===
 +
 
 +
Yet another simple solution: [http://chtaube.eu/computers/freedos/bootable-usb/ FreeDOS prebuilt bootable USB flash drive image by Christian Taube]
 +
 
 +
=== Images that are too large for a floppy ===
 
If your flash image is too large for a floppy, go to the [http://www.fdos.org/bootdisks/ FreeDos bootdisk website], and download the 10Mb hard-disk image.  This image is a full disk image, including partitions, so adding your flash utility will be a little trickier:
 
If your flash image is too large for a floppy, go to the [http://www.fdos.org/bootdisks/ FreeDos bootdisk website], and download the 10Mb hard-disk image.  This image is a full disk image, including partitions, so adding your flash utility will be a little trickier:
  
{{bc|
+
First find the first partition (at time of writing, the first partition starts at block 63; this means that the partitions starts at offset <tt>512 * 63 = 32256</tt>).
# modprobe loop
+
You can either use:
# losetup /dev/loop0 <image-file>
+
# file -sk ''<image-file>'' | sed -r 's/.*startsector ([0-9]+).*/\1/'
# fdisk -lu /dev/loop0
+
'''63'''
}}
+
  
You can do some simply maths now: block size (usually 512) times the start of the first partition.  At time of writing, the first partition starts at block 63.  This means that the partitions starts at offset 512 * 63 = 32256:
+
Or:
  
{{bc|1=
+
# fdisk -l ''<image-file>''
# mount -o offset=32256 /dev/loop0 /mnt
+
}}
+
Units = sectors of 1 * '''512''' = 512 bytes
 +
 +
      Device  Boot  Start    End  Blocks  Id  System
 +
              *        '''63'''  19151  9544+  1  FAT12
  
Now you can copy your flash utility onto the filesystem as normal.  Once you're done:
+
Now you can mount the image:
  
{{bc|
+
# mount -oloop,offset=$((63 * 512)) ''<image-file>'' /mnt
# umount /mnt
+
 
# losetup -d /dev/loop0
+
Then you can copy your flash utility onto the filesystem as normal.
}}
+
Once you're done:
 +
 
 +
# umount /mnt
  
 
The image can now be copied to a USB stick for booting, or booted as a memdisk as per normal instructions.
 
The image can now be copied to a USB stick for booting, or booted as a memdisk as per normal instructions.
  
===Usage===
+
=== Usage ===
'''Step 1: Download FreeDOS boot disk floppy image'''
+
 
We are fortunate that guys at FDOS site have prepared one suitable for us. Use the OEM Bootdisk version, the one with just kernel and command.com, because it leaves more free space on disk for the flash utility and new BIOS image. After you download the image, you need to decompress it. In other words:
+
The OEM Bootdisk version is recommended, as it only includes {{ic|kernel}} and {{ic|command.com}} thus leaving more space for the flash utility and new BIOS image. Download and decompress the FreeDOS image:
  wget http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz
+
 
  gunzip FDOEM.144.gz
+
  $ wget http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz
 +
  $ gunzip FDOEM.144.gz
 +
 
 +
Copy your BIOS flash utility and new BIOS image to the mounted floppy disk image. Load the necessary modules:
  
'''Step 2: Copy your BIOS flash utility and new BIOS image to the mounted floppy disk image'''
+
# modprobe vfat
 +
# modprobe loop
  
Requirement for this step is that you have support for the vfat and loop file systems in the kernel. Or you can have those features compiled as modules. In the latter case, load the modules before the next step, like this.
+
{{ic|/proc/fileystems}} shows if the needed file systems are supported. "loop mount" the floppy disk image to a temporary path:
modprobe vfat
+
modprobe loop
+
  
Consult {{ic|/proc/fileystems}} to see if you have the needed file systems supported. If you do, you should be able to "loop mount" the floppy disk image to some temporary path:
+
  $ mkdir /tmp/floppy
  mkdir /tmp/floppy
+
  $ mount -t vfat -o loop FDOEM.144 /tmp/floppy
  mount -t vfat -o loop FDOEM.144 /tmp/floppy
+
  
If the mount went without errors, copy BIOS flash utility and new BIOS image to the mounted floppy disk image. You'll probably have to unzip the archive you downloaded from your motherboard vendor site, to get to those two files. Here's just an example for my motherboard (in your case, files will have different names, of course):
+
If the mount went without errors, copy the BIOS flash utility and new BIOS image to the mounted floppy disk image. You will probably have to unzip the archive you downloaded from your motherboard vendor site, to get to those two files. For example:
  
 
  # unzip 775Dual-VSTA\(2.60\).zip
 
  # unzip 775Dual-VSTA\(2.60\).zip
Line 125: Line 124:
 
  # cp 75DVSTA2.60 ASRflash.exe /tmp/floppy
 
  # cp 75DVSTA2.60 ASRflash.exe /tmp/floppy
  
Doublecheck that everything went OK, that those two files weren't too big for the floppy:
+
Check that the two files were not too big for the floppy:
  
 
  Filesystem          1K-blocks      Used Available Use% Mounted on
 
  Filesystem          1K-blocks      Used Available Use% Mounted on
 
  /tmp/FDOEM.144
 
  /tmp/FDOEM.144
 
                           1424      990      434  70% /tmp/floppy
 
                           1424      990      434  70% /tmp/floppy
Finally, unmount the floppy disk image:
+
Unmount the floppy disk image:
 +
 
 
  umount /tmp/floppy
 
  umount /tmp/floppy
  
'''Step 3: Burn a bootable CD which will emulate floppy device for us'''
+
The next step is to burn the floppy image to a CD/DVD-RW media, but in a way that it can be booted afterwards. First create a bootable CD image, and then burn it.
  
Next step is to burn the floppy image to a CD/DVD-RW media, but in a way that it can be booted afterwards. First we need to make a bootable CD image, and then burn it. Notice that on some modern distributions, cdrecord is renamed to wodim, and mkisofs to genisoimage, but the parameters below should be the same.
+
genisoimage -o bootcd.iso -b FDOEM.144 FDOEM.144
mkisofs -o bootcd.iso -b FDOEM.144 FDOEM.144
+
  wodim -v bootcd.iso
  cdrecord -v bootcd.iso
+
  
'''Alternative Step 3: Add your image to Grub's menu.
+
You may alternatively add your image to the [[GRUB]] menu. Install [[syslinux]] and copy {{ic|memdisk}} and your image to {{ic|/boot}}:
You will need to install syslinux and copy memdisk to {{ic|/boot}}, and put your image there as well.
+
  
 
   cp /usr/lib/syslinux/memdisk /boot
 
   cp /usr/lib/syslinux/memdisk /boot
 
   cp FDOEM.144 /boot/flashbios.img
 
   cp FDOEM.144 /boot/flashbios.img
  
Now add an entry to your {{ic|/boot/grub/menu.lst}}:
+
Now add an entry to {{ic|/boot/grub/menu.lst}}:
 
    
 
    
 
   title Flash BIOS
 
   title Flash BIOS
Line 158: Line 156:
 
   }
 
   }
  
'''Step 4: Reboot, flash, reboot, enjoy your new BIOS'''
+
Or for syslinux in {{ic|/boot/syslinux/syslinux.cfg}}:
 +
 
 +
LABEL flashbios
 +
MENU LABEL Flash BIOS
 +
LINUX ../memdisk
 +
INITRD ../fdboot.img
 +
 
 +
Finally reboot your machine, making sure the CD drive is first in the boot sequence, and run the BIOS upgrade procedure when the CD boots. If using the GRUB method, choose the new entry on the list, and it should boot into FreeDOS.
 +
 
 +
== Bootable optical disk emulation ==
 +
The script Geteltorito.pl will extract the [[wikipedia:El Torito (CD-ROM standard)|El Torito]] boot image. It has worked on Lenovo laptops like X220, X230, W540 and T450s. It may work for other vendors as well.
 +
 
 +
=== Installation ===
 +
Install the {{AUR|geteltorito}} package.
 +
 
 +
=== Usage ===
 +
 
 +
Get the bios update iso from the vendor support site. Run the ''geteltorito'' image extraction:
 +
 
 +
$ geteltorito.pl -o <image>.img <image>.iso
 +
 
 +
Copy the image to the usb thumbdrive:
 +
 
 +
# dd if=<image>.img of=<destination> bs=512K
 +
 
 +
Reboot and boot from the USB drive, follow vendor directions.
  
Finally reboot your machine, make sure that your CD drive is first in the boot sequence, and then run your BIOS upgrade procedure when the CD boots. If using the GRUB method, just choose the new entry on the list, and it should boot into FreeDOS.
+
{{Note|If you get the message "Secure Flash Authentication failed!", it means that some security check did not allow the flash to happen. It can help to go to the BIOS options page "Security" > "UEFI BIOS Update Option" and disable "Secure RollBack Prevention" and enable "Flash BIOS Updating by End-Users". You can set them to what you want after flashing.}}

Latest revision as of 20:40, 3 April 2016

This article aims on providing information on flashing your system BIOS under Linux. Most manufacturers provide a Windows executable or a BIOS executable that can only be run under Windows. However, there are a few utilities, that allow you to upgrade your system BIOS under Linux.

Warning: Flashing motherboard BIOS is a dangerous activity that can render your motherboard inoperable! While the author of this article has successfully run this procedure many times, your mileage may vary. Be careful! You may want to consider updating microcode instead if it is supported by your system.

BiosDisk

BiosDisk BiosDisk simplifies the process of flashing your system BIOS under Linux

Installation

Install the biosdisk-gitAUR package.

Usage

To use the biosdisk utility to create a BIOS flash image, first download the latest raw BIOS image for your system from your manufacturer's website. Make sure however, that you always get the BIOS executable and NOT the Windows executable. You then have one of several options: create a floppy, create a dd floppy image, create a user-installable distribution-specific package (e.g. RPM), or actually install the image for your bootloader.

  • The mkfloppy action will create the biosdisk image and write it directly to a floppy disk. Usage is the following:
    biosdisk mkfloppy [-o option] [-d device] [-k baseimage] /path/to/.exe 
  • The mkimage action will create a floppy image on the user's hard drive. Usage is the following:
    biosdisk mkimage [-o option] [-i destination] [-k baseimage] /path/to/.exe 
  • The mkpkg action will create the floppy image, and use it to create a user-installable package specific to the distribution (example: RPM). When the package is installed, it will use the distribution's built-in tools to update the system's bootloader so that the user can boot to the image from the hard drive to flash the BIOS, without needing a floppy drive. Currently only Red Hat/Fedora RPM packages are supported. Usage is as follows:
    biosdisk mkpkg [-o option] [--install] [--distro=] [--name=] [--version=] [--release=] /path/to/{.exe | .img}
  • The install action will create the biosdisk image, copy the image file to /boot, and then update the bootloader with an entry for the image. Then all the user has to do is boot the system and select the image to flash the BIOS; this will load the biosdisk image directly from the hard drive and flash the BIOS.
    biosdisk install [-o option] [--name=] /path/to/{.exe | .img}

Flashrom

Flashromis a utility for identifying, reading, writing, verifying and erasing flash chips. It is designed to flash BIOS/EFI/coreboot/firmware/optionROM images on mainboards, network/graphics/storage controller cards, and various programmer devices.

Installation

Install the flashrom or flashrom-svnAUR package.

Usage

Find out if your motherboard and chipset (internal) is supported by flashrom at this website. Supported Hardware You can also find out if your hardware is supported by issuing the following command

# flashrom --programmer internal

The above command will tell you your motherboard and chipset. You can then find out if yours is supported by issuing this command:

# flashrom --programmer internal -L | grep CHIPNAMEfrompreviouscommand

On modern mainboards you probably get more than one rom chip listed. You have to select the chipname you get from the upper command. Then you use the -c option to select which rom is affected by the command

# flashrom --programmer internal -c "CHIPNAME" -r backup_CHIPNAME.bin

Write and verify the new BIOS image (proprietary or Coreboot) on the ROM chip:

# flashrom --programmer internal internal -c "CHIPNAME" -w newbios.bin

If you want to flash other flash chips on your mainboard, you will find all options with

# flashrom

FreeDOS

FreeDOS a free DOS-compatible operating system, is up to the challenge, no need for proprietary DOS versions. So, all you need is a bootable floppy disk image with FreeDOS kernel on it.

Unetbootin

By far the easiest way to make a bootable FreeDOS USB Stick is using unetbootin, available in the Official repositories.

You should format a pendrive with FAT16 and flag it as "boot" (you may do this through a GUI with gparted, qtpartedAUR[broken link: archived in aur-mirror] or partitionmanager). Then, after mounting the flash drive, select under distribution FreeDOS and your mounted stick. The app will automatically download the image for you and copy it to the drive. Finally, you may copy everything you want to flash there (BIOS, firmwares, etc).

Warning: Unetbootin may not function properly on some Lenovo systems. It may be necessary to create the bootable stick on a different device. See here.

Gentoo

Check out FreeDOS Flash Drive on the Gentoo Wiki if you want to create a bootable FreeDOS Flash drive.

Prebuilt images

Yet another simple solution: FreeDOS prebuilt bootable USB flash drive image by Christian Taube

Images that are too large for a floppy

If your flash image is too large for a floppy, go to the FreeDos bootdisk website, and download the 10Mb hard-disk image. This image is a full disk image, including partitions, so adding your flash utility will be a little trickier:

First find the first partition (at time of writing, the first partition starts at block 63; this means that the partitions starts at offset 512 * 63 = 32256). You can either use:

# file -sk <image-file> | sed -r 's/.*startsector ([0-9]+).*/\1/'
63

Or:

# fdisk -l <image-file>
…
Units = sectors of 1 * 512 = 512 bytes
…
      Device  Boot  Start    End  Blocks  Id  System
              *        63  19151   9544+   1  FAT12

Now you can mount the image:

# mount -oloop,offset=$((63 * 512)) <image-file> /mnt

Then you can copy your flash utility onto the filesystem as normal. Once you're done:

# umount /mnt

The image can now be copied to a USB stick for booting, or booted as a memdisk as per normal instructions.

Usage

The OEM Bootdisk version is recommended, as it only includes kernel and command.com thus leaving more space for the flash utility and new BIOS image. Download and decompress the FreeDOS image:

$ wget http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz
$ gunzip FDOEM.144.gz

Copy your BIOS flash utility and new BIOS image to the mounted floppy disk image. Load the necessary modules:

# modprobe vfat
# modprobe loop

/proc/fileystems shows if the needed file systems are supported. "loop mount" the floppy disk image to a temporary path:

$ mkdir /tmp/floppy
$ mount -t vfat -o loop FDOEM.144 /tmp/floppy

If the mount went without errors, copy the BIOS flash utility and new BIOS image to the mounted floppy disk image. You will probably have to unzip the archive you downloaded from your motherboard vendor site, to get to those two files. For example:

# unzip 775Dual-VSTA\(2.60\).zip
Archive: 775Dual-VSTA(2.60).zip
 inflating: 75DVSTA2.60
 inflating: ASRflash.exe
# cp 75DVSTA2.60 ASRflash.exe /tmp/floppy

Check that the two files were not too big for the floppy:

Filesystem           1K-blocks      Used Available Use% Mounted on
/tmp/FDOEM.144
                         1424       990       434  70% /tmp/floppy

Unmount the floppy disk image:

umount /tmp/floppy

The next step is to burn the floppy image to a CD/DVD-RW media, but in a way that it can be booted afterwards. First create a bootable CD image, and then burn it.

genisoimage -o bootcd.iso -b FDOEM.144 FDOEM.144
wodim -v bootcd.iso

You may alternatively add your image to the GRUB menu. Install syslinux and copy memdisk and your image to /boot:

 cp /usr/lib/syslinux/memdisk /boot
 cp FDOEM.144 /boot/flashbios.img

Now add an entry to /boot/grub/menu.lst:

 title Flash BIOS
 kernel /memdisk
 initrd /flashbios.img

Or for GRUB2 in /boot/grub/grub.cfg:

 menuentry "Flash BIOS" {
 linux16 /boot/memdisk
 initrd16 /boot/flashbios.img
 }

Or for syslinux in /boot/syslinux/syslinux.cfg:

LABEL flashbios
	MENU LABEL Flash BIOS
	LINUX ../memdisk
	INITRD ../fdboot.img

Finally reboot your machine, making sure the CD drive is first in the boot sequence, and run the BIOS upgrade procedure when the CD boots. If using the GRUB method, choose the new entry on the list, and it should boot into FreeDOS.

Bootable optical disk emulation

The script Geteltorito.pl will extract the El Torito boot image. It has worked on Lenovo laptops like X220, X230, W540 and T450s. It may work for other vendors as well.

Installation

Install the geteltoritoAUR package.

Usage

Get the bios update iso from the vendor support site. Run the geteltorito image extraction:

$ geteltorito.pl -o <image>.img <image>.iso

Copy the image to the usb thumbdrive:

# dd if=<image>.img of=<destination> bs=512K

Reboot and boot from the USB drive, follow vendor directions.

Note: If you get the message "Secure Flash Authentication failed!", it means that some security check did not allow the flash to happen. It can help to go to the BIOS options page "Security" > "UEFI BIOS Update Option" and disable "Secure RollBack Prevention" and enable "Flash BIOS Updating by End-Users". You can set them to what you want after flashing.