Package: binwalk (2.1.1-16 and others)
4 stars based on
These docs may no longer be accurate. Why is this useful? Where to get the kit IV. Acknowledgements and more IX. Description This kit gives the user the ability to make changes to a firmware image without recompiling the firmware sources. It works by extracting the firmware into its component parts, then extracting the file system image assuming its in one the supported formats.
The user can tools included in the binwalk package make modifications to the extracted file system, and rebuild the firmware image. Although this kit completely automates the process, it is also useful for those who need a handy collection of utilities to manipulate firmware images. The following utilities are included in this kit, along with scripts to automate their use:.
This kit doesn't just collect existing tools, it also offers new ones and modifications to existing ones. Custom code currently is:. Currently TRX and uImage headers are supported. This tool wasn't officially made available until squashfs 3. A list of some of the many reasons this might be desired are:. The best way to download and use this kit is to check out the sources from the repository.
The automated scripts all automatically build the executables, and the sources. It is easy as downloading something and using it that way. Also, if you are unable to use a tools included in the binwalk package SVN checkout, then it is likely that this kit is a danger to you because it is for advanced users. Project hosting and repository new: I've worked to make sure the requirements are low enough for anyone to use this kit. However, to reduce distribution costs and better represent the multi-platform capabilities of this kit, the binary tools in the kit do automatically build themselves the first time you run one of the scripts.
The few requirements are all basic items that everyone has easy access to:. The kit is probably not far from compatibility, but easier to just install a linux VM. Any TRX style firmware image format should that uses squashfs-lzma as a root file system work fine. Firmwares that use regular zlib squashfs or unsupported file systems will work if the steps that extract the file system and rebuild the file system are tweaked. Instructions I've scripts that simply and abstract the firmware modification process.
Basically, it's a one-step process to extract the firmware, and a one-step process to rebuild the firmware. There are also scripts to install or remove individual packages or entire directories of packages. You must run this tool from inside the directory it exists in. This is where the intermediate files and the extracted file system will be stored.
Note that files in the working directory may be deleted! It doesn't matter which firmware image you supply, i. These images are usually all the same and differ only in the header format.
The rebuilding process will create images for the various models. An extraction log is created as extract. Making changes to the firmware's file system. Modifying the firmware is simple. Here are the subfolders of this directory: If you need to replace the kernel not at all recommendedyou can do so by replacing the appropriate file here usually segment2.
Although not all will work and a repository for packages verified to work has not yet been produced, many packages work just fine. Packages are pre-built collections of files pertaining to a set of software.
For a list of some of the available packages not all may worksee http: Rebuilding the firmware is as easy as extracting it. If images already exist here, they will tools included in the binwalk package over-written. Firmware images for various models will be emitted these images are all the same but have different header patterns so they are accepted by the target models.
There are a few things to watch out for when modifying firmware images. If you make reasonable changes these problems will probably never affect you. Be warned, this section may be technical in parts. Currently, the maximum firmware image size supported by this kit is 5, 0x5A bytes, but can be adjusted through the "-m [size]" parameter of the asustrx tool. Solutions to tools included in the binwalk package system incompatibilities. The squashfs file system is case sensitive i.
To support proper extraction of the file system, the working directory should be on a case sensitive file system and support symbolic links. The scripts will warn you if you attempt to use as working directory on a case INsensitive file system. You'll see a number of errors if you extract to a tools included in the binwalk package system that doesn't support symbolic links.
Case insensitivity doesn't always cause problems, especially if the file system preserves case ok. It depends on the firmware and version. Most of the time for DD-WRT as long as a case preserving file system is used as a working directory, all should work fine.
These solutions apply to those using CYGWIN, or some other environment that may not have a case sensitive file system by default. Example of how to create a temporary HSFX case sensitive file system: The authors and maintainers of this kit are Jeremy Collake db90h and Craig Heffner.
If YOU would like to contribute to this kit, send me an email at jeremy. Documentation updates, re-included pre-built executables v0. First decent public release. This tools included in the binwalk package c Jeremy Collake and Craig Heffner. This document may be freely republished in its unaltered and whole form only. Alterations or partial publishing requires approval of creator s. Visit the NEW bitsum. This tool replaces both 'normal' trx tool and addver.
Current versions included are: Tools included in the binwalk package analysis tool, used for searching firmware images for known file types. Used by the extract-ng. Current version included is 0. Builds a squashfs file system image. Builds a cramfs file system image. Coming in next version. Alternate tool to extracts a cramfs file system image. Use cramfsck instead whenever possible as it seems to be more reliable. Extracts an lzma cramfs file system image, specifically those included in OpenRG based firmware.
Extracts a zlib squashfs file system image. Tools included in the binwalk package versions included are 1. Extracts an lzma squashfs file system image. Not all squashfs-lzma patches are compatible with one another. I'm working on adding support for all common squashfs-lzma variations. Splits TRX style firmwares into their component parts.
Also supports pre-pended addpattern HDR0 style headers. This was developed exclusively for this kit. Use a network share to a case sensitive file system. This is, by far, the easiest solution. Simply use an appropriate network share for the working directory. For NT partitions it's reported you can enable case sensitivity through the following registry key, but I do not know if this works or not.
Mount an ext2 files system.