view ffstools/README @ 573:976aeaa2e6e1

gsm-fw/L1/include/l1_pwmgr.h: L1_PWMGR_APP_OFFSET definition needed for l1_trace.c to compile
author Michael Spacefalcon <msokolov@ivan.Harhan.ORG>
date Mon, 11 Aug 2014 01:46:50 +0000
parents 3d88461d8284
children
line wrap: on
line source

You are looking at the source for the TIFFS In Vitro Analyzer utility.  You may
have downloaded it either as a separate package or as part of the larger
freecalypso-sw suite.

See TIFFS-Overview (in ../doc if you are working with the full freecalypso-sw
source tree) for a general description of what TIFFS is and why it matters.

The utility contained in the present package runs on a general purpose GNU/Linux
(or other Unix) host and enables "in vitro" examination of Flash File System
images read out of TI-based GSM devices.  Using this utility, you can list the
directory and file content of an FFS image, cat any individual file in the FFS,
or extract the complete FFS content into your regular Unix file system.  Some
"forensic" operations are also supported: by listing the inode array, one can
deduce the order in which the present FFS content got created, and see what
files have been overwritten or deleted in the span of still-visible history.
One can then cat the old byte content of those overwritten or deleted files,
if those data chunks are still in the FFS image (i.e., if the flash sector in
question has not been reclaimed yet).

Compilation and installation are straightforward: run 'make' to compile the
source; you should get 3 executable binaries named tiffs, mokoffs and pirffs;
then run 'make install' as root to install them in /usr/local/bin.  The binary
named tiffs is the main program; mokoffs and pirffs are wrappers that simplify
the most common current use cases.

To install somewhere other than /usr/local/bin, edit the INSTBIN= setting in
the subdirectory Makefiles.  You will also need to edit
tiffs-wrappers/installpath.c accordingly, as the mokoffs and pirffs wrappers
are designed to exec tiffs by its absolute installed pathname.

See Usage for the usage instructions.