LongSoft

UEFITool

C2016–2023

LongSoft / UEFITool

UEFITool

UEFI firmware image viewer and editor

Explore on GitHub Read Hacker News discussions

6Distinct people

7Mentions

0Explicit recommenders

5.8KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

UEFI firmware image viewer and editor

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year7 dated mentions

Observed mentions: 2016-08-25 13:03:18 UTC to 2023-01-09 00:13:22 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	1	0	1
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	1	0	1
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	1	0	1
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	1	1	0
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	1	0	1
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	1	1	0
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	0	0	0
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	1	0	1

What Hacker News says

7 sources

iam-TJ·Jan 9, 2023

I wonder if this also should work with AMI APTIO UEFI capsules. Currently dealing with a similar issue where for no apparent reason on a regular reboot motherboard fails to even start to POST. Without RAM modules it emits the manual-defined two beeps, but with a RAM module in but no GPU it doesn't emit the defined no-GPU three beeps. Not clear if those beeps require a functioning CPU or not - but knowing that would be very helpful in knowing which component(s) might have failed! Working on the supposition the NOR Flash chip had somehow been corrupted I connected my long-unused TL866A EPROM programmer to the provided SPI header on the mobo via a mash-up of a PATA IDE 2.5" to 3.5" adapter (the only component in my collection that fits the mobo header) and fly leads to the TL866A. Repeatedly failed to read the chip ID until finally realising

Read the rest

the chip takes 1.8V not 3.3V! (Winbond W25Q128FW SPI NOR). Ordered a 1.8V interposer for the TL866A. Tried again with the same result but suspect reading using 3.3V might have killed an otherwise good chip! Ordered a couple of replacement chips early December that finally arrived early January (no, not from China, from 40 miles away - thanks UK Postal workers on strike!) only to discover they are 3.3V chips - I'd misread the listing and ordered W25Q128FV not "FW" (V = 3.3V, W = 1.8V). Finally took the plunge and desoldered the chip from the mobo whilst holding my breath in case the hot air gun blew the miniscule 1mm resistors close to the chip off the board! Tried reading the chip whilst disconnected but same failed result so assume device is trashed. Proved I can program one of the 3.3V chips so - assuming the 1.8V interposer isn't faulty - just need the correct chips and resolder. Am now awaiting delivery of the correct chips. At that point I'll likely discover the fault is either the motherboard or the CPU at which point it gets more expensive as have to obtain and swap in alternatives to deduce the failed part! Don't you just love the right (and ability) to repair!? ironic laugh On the positive side I discovered the completely open-source TL866A minipro software [0] and the TL866 firmware updater [1] tools that have made the software side of the process much easier than wrestling with MS Windows applications and WINE. Also UEFITool for inspecting and extracting binary ROM files from UEFI Capsules [2]. [0] https://gitlab.com/DavidGriffith/minipro [1] https://github.com/radiomanV/TL866.git [2] https://github.com/LongSoft/UEFITool (also available in Debian/Ubuntu archives)

In Unbricking a BIOS-Bricked Motherboard

rolph·Dec 2, 2021Submission

GitHub – LongSoft/UEFITool: UEFI firmware image viewer and editor

2 points · Open discussion

rmrfstar·Apr 14, 2020

It is really frustrating that they do not ship checksums for immutable sections of the UEFI image, as this would require almost no effort on their part [1]. Of course enterprise out of the extreme HAP universe doesn't care because it won't invest the effort to image their chips. [1] https://github.com/LongSoft/UEFITool

In Dell releases new tool to detect BIOS attacks

peter_d_sherman·Jan 30, 2019Submission

UEFITool

1 points · Open discussion

xvilka·Sep 28, 2018

Using flashrom [1] you can dump the contents of your SPI flash for the inspection and open the image with UEFITool [2]. Both tools are opensource and developed for years. Some people recommend to use chipsec [3], but it can less in terms of dumping and unpacking. The state of security in UEFI firmware is horrible, thing is overengineered and poorly written (bad code practices). Not to mention Intel ME/AMT/etc that also provide the easy way for attacker to persist and hide itself once compromised. Projects like coreboot [4] and vendors like Purism [5] allow the tighter control of your own hardware, but thanks to Intel it still has a lot of blobs of a bad code. Apple realized they can't trust Intel and other "BIOS" writers, so working on improving the security and codebase. Thus the state of affairs is slightly better on Macbooks. I believe

Read the rest

x86 firmware world is beyond any hope to get any better and everyone should focus on building better hardware/architectures from scratch. Hopefully companies like Raptor Engineering [6] can shift the mindset of consumers. [1] https://flashrom.org/Flashrom [2] https://github.com/LongSoft/UEFITool [3] https://github.com/chipsec/chipsec [4] http://coreboot.org/ [5] https://puri.sm/ [6] https://www.raptorcs.com/content/base/products.html

In LoJax: First UEFI rootkit found in the wild, courtesy of the Sednit group

xvilka·Mar 11, 2017

This can be done manually using flashrom [1] tool to read (and write) the SPI (and not only SPI) flash and UEFITool [2] to unpack the corresponding image. I've even done some patching for better support of Intel platforms here [3]. Now doesn't have much time to rebase/cleanup/improve it, but hopefully someone will start from where I've finished. Both tools clearly need more love, and I hope current revelations will help to do that. [1] http://flashrom.org/ [2] https://github.com/LongSoft/UEFITool/tree/new_engine (use 'new_engine' branch) [3] https://github.com/XVilka/flashrom/tree/layout_descriptor (use 'layout_descriptor' branch)

In After CIA leak, Intel Security releases detection tool for EFI rootkits

chme·Aug 25, 2016

UEFIFind would be available for other platforms too: https://github.com/LongSoft/UEFITool

In ME Analyzer – Intel Engine Firmware Analysis Tool