Docomo Phones by Mitsubishi

This page is a work in process.

Check the dumping hardware overview for a list of known preservation hardware.

If you need help, please come chat with us on the VGPC or No-Intro discord servers.

Mitsubishi phones were only manufactured in the early era of Docomo Foma phones. Current tools allow us to extract full data from some phones, and partial data (apps only) from other phones.

Phone Model	Extractable?	File System/FTL	Tools
D2102V	Unknown	Unknown	Unknown
D900i	Chip dump only	DATA Structure	Unknown
D901i	Unknown	Unknown	Unknown
D901iS	Java only	Unknown	In development (export does not include .jam)
D701i	Unknown	Unknown	Unknown
D701iWM	Java only	Unknown	None (Java folder exports directly)
D902i	Java only	Unknown	None (Java folder exports directly)
D902iS	Java only	Unknown	None (Java folder exports directly)
D702i	Java only	Unknown	None (Java folder exports directly)
D702iF	Unknown	Unknown	Unknown
D903i	Yes	FAT16 + “SH704i/D904i” FTL	assemble_sh704i_d904i + TestDisk
D903iTV	Yes	FAT16 + “SH704i/D904i” FTL	assemble_sh704i_d904i + TestDisk
D703i	Java folder confirmed Full extractability unknown	Unknown	None (Java folder exports directly)
D904i	Yes	FAT16 + “SH704i/D904i” FTL	assemble_sh704i_d904i + TestDisk
D704i	Yes	FAT16 + “SH704i/D904i” FTL	assemble_sh704i_d904i + TestDisk
D905i	Yes	FAT32 + “B4B4” FTL	b4-ftl-extract + TestDisk
D705i	Yes	FAT16 + XSR2	fs-tools (XSR2) + TestDisk
D705iμ	Yes	FAT16 + XSR2	fs-tools (XSR2) + TestDisk
D800iDS	Java only	Unknown	None (Java folder exports directly)

Extracting Data

ktdumper

Reading File Systems

assemble_sh704i_d904i
b4-ftl-extract
fs-tools

Note that the dump_java script does not require the use of file extraction tools because it extracts individual files directly from the phone.

Ktdumper is a tool for extracting data from feature phones that are compatible with the Foma debug adapter, which includes all Docomo phones and select SoftBank phones. Please note that ktdumper will not work unless you have the Foma debug adapter.

Ktdumper is compatible with Linux and WSL (Windows System on Linux). It can be used as a command line tool or as a live Linux iso with a GUI.

Make sure your phone is connected to the PC (if using WSL, you will need to bind your USB device)
Download the ktdumper repository from Github
Navigate to the main ktdumper folder, where the code will be executed.
You can execute the following commands

NAND (contains user data, downloads, etc.)

sudo ./ktdumper.sh [insert phone model] dump_nand

NOR

sudo ./ktdumper.sh [insert phone model] dump_nor

JAVA Folder (only works on select Mitsubishi/Fujitsu phones)
```
sudo ./ktdumper.sh [insert phone model] dump_java
```

Sample For D904i

sudo ./ktdumper.sh d904i dump_nand

WIP

Before using assemble_sh704i_d904i.py, you must separate the NAND and OOB (out of bounds) data.

Download the separate_nand_oob.py script from Github and place it into the folder generated by ktdumper

Execute the following script

python separate_nand_oob.py nand_mixed.bin

When given a set of options, select 0 (the other options are not needed for D904i/SH904i devices)
```
0: Data = 512 Bytes, OOB = 16 bytes, divisible = True
```

To remove the FTL:

Download the assemble_sh704i_d904i.py script from Github

Execute the following command

python assemble_sh704i_d904i.py nand_mixed_separated_512.bin output.bin

After this, you must use TestDisk to acquire the data.

Download the b4-ftl-extract scripts from Github
Place scripts in the same folder as nand.bin
EITHER drag nand.bin into b4b4.bat or enter the following command
```
python extract.py -s nand.bin output_dir
```
This code will unscramble the FTL and place all data into a folder called output_dir

After this, you must use TestDisk to acquire the data.

NOTE: This extraction method may not work on WSL. If you are having errors after trying all steps, try switching from WSL to a full Linux installation.

Download fs-tools from Github

In the XSR2 folder, run the following command

sudo apt install gcc-arm-linux-gnueabi qemu qemu-user-static qemu-system-arm

Then build with the following command

arm-linux-gnueabi-gcc xsr_stl.ko main.c -o main

Place onenand.bin and onenand.oob into the XSR2 folder and run the following command based on the type of part

export QEMU_LD_PREFIX=/usr/arm-linux-gnueabi
./main onenand.bin onenand.oob B output.bin

export QEMU_LD_PREFIX=/usr/arm-linux-gnueabi
./main onenand.bin onenand.oob A output.bin

export QEMU_LD_PREFIX=/usr/arm-linux-gnueabi
./main onenand.bin onenand.oob 8 output.bin

After this, you must use TestDisk to acquire the data.

TestDisk can be used on either Windows or Linux. It is available for download here. Once you have downloaded TestDisk, use the program to open your current .bin file.

When you open a .bin file with TestDisk, you will have the option to select a media. There should only be
```
>Disk <your file>
```
Press enter to proceed.
When asked to select a partition table type, select None
```
[None ] Non partitioned media
```
On the following page, press q to quit or select
```
[ quit ]
```
In the new menu, move up the menu and select
```
[ Analyse ]
```
Press enter to continue with
```
[Quick Search]
```
You should now see a partition labeled with a file system like FAT16 or FAT32. Don’t press ENTER. Instead, press p to list files.
Press a to select all files.
Press C (note the capitalization and hold the shift button!) to copy the selected files.
Choose the output folder. Press C when the folder is correct.

You should now have all the extracted files.

Note: For select devices (such as F905i and D905i), you need to select None → Undelete rather than the usual TestDisk procedure.

Once you've dumped your games, it's time to generate and submit metadata to a preservation project for validating and cataloging. See the dump submission instructions for more information.