Creating a framework for Marvel Future Fight exploration


autoanalyze [-v] [-v] -i input_directory -o output_directory
autoanalyze -h


autoanalyze automates the process of extracting program structure and function from Marvel Future Fight installation packages and performing automated analysis of the code while creating project layouts for further exploration and analysis.


-i input_directory

Specify the directory in which installation files are stored.

-o output_directory

Specify the directory in which to store newly created project layouts.


Output more information when running. May be specified 0, 1, or 2 times.


Output brief usage instructions but take no other action.

Extended Description

autoanalyze uses Il2CppInspector to prepare data structure information (C types, function signatures, string references, and other items) from the Marvel Future Fight installation packages obtained via apkdl or similar tools. It then uses JADX to decompress and decode the packages and decompile the Java code used for parts of the program into source files. Finally, autoanalyze creates a new Ghidra project, imports the binary application data, applies the information from Il2CppInspector, and performs a Ghidra auto-analysis.

autoanalyze uses Ghidra’s analyzeHeadless mode to perform these processes without a GUI, and this ends up being significantly faster than importing these items manually, even if the point-and-click tasks themselves are minimal. If Ghidra is installed somewhere (and in only one place) under /usr/local, this will be found automatically; otherwise, set the GHIDRA environment variable to the path of the analyzeHeadless script (which, in most releases, is in the support/ subdirectory).

With a minimum of pre-installed software (see REQUIREMENTS), autoanalyze will obtain the remainder of necessary software. autoanalyze installs software into temporary directories in an attempt to minimize changes to its host system, but does not use a chroot jail or other mechanisms to truly isolate itself.

By default, autoanalyze prints only errors. To add brief informational messages about the current step in the process, add the -v option. Adding the option again enables “debug” output that includes echoing all shell commands in autoanalyze and printing the output from each individual tool called. Adding further -v options has no effect.

autoanalyze evaluates files within input_directory, which is expected to contain somewhere beneath it files named base.apk and config.abi.apk (for some ABI name). This may be a simple directory containing these files, such as the mff-apks-version directory made by apkdl, some subset of an Android filesystem such as the mff-device-files-version directory created by the autoextract program, or any other searchable file hierarchy containing these two files. If more than one of each type of file is located, an error message is printed; the easiest way to fix this is to choose a better subdirectory or relocate the files you wish to analyze into a directory of their own.

The final products created by autoanalyze are directories named mff-ghidra-version and mff-jadx-version within the directory output_directory, where version is determined from the version of Marvel Future Fight evaluated. Within mff-ghidra-version are files and directories used by the new Ghidra project, as well as multiple log files created during the import and processing steps. mff-jadx-version contains the decompiled Java code from the device-independent portion of the application.

In many circumstances, autoanalyze will take several hours to complete.


  • POSIX-like environment for which all the used programs are available (Linux, macOS/OS X, or Windows with Cygwin or another POSIX layer)

  • git (used to obtain automatically downloaded tools)

  • .NET 5.0 SDK (required for building automatically downloaded tools)

  • Ghidra

  • Java runtime (required by Ghidra); consider Temurin 11

  • A reasonable machine upon which to run these; Ghidra can be quite resource intensive.

See also

  • apkdl

  • Other concepts, examples, and workflows including autoanalyze are in the User Guide.