How to Use the Bluetrum Firmware Build Tool

The Bluetrum Firmware Build Tool allows you to rebuild a Bluetrum firmware file from the components extracted by the Unpack Firmware tool.

It is useful when you have modified the firmware components and want to package them back into a new .BIN firmware file.

1. Prepare the Unpacked Firmware

Before using the Build tool, you need to have a firmware package previously extracted using the Unpack Firmware tool.

After extracting the downloaded ZIP file, you should have files similar to:

header.bin
boot-code.bin
app.bin
res.bin
res/

The exact files may vary depending on the firmware.

Keep all required files together in the same folder.

2. Create a ZIP Package

The Build tool accepts the firmware components as a ZIP file.

Create a ZIP archive containing the required files.

For example:

firmware.zip
├── header.bin
├── boot-code.bin
├── app.bin
├── res.bin
└── res/

If you have modified resources, make sure the updated files are included in the ZIP archive before uploading it.

Important

Do not change the filenames of the required firmware components unless you know exactly what you are doing.

The Build tool uses these filenames to identify the different firmware sections.

3. Prepare the Code Key

The Build process requires the correct Code Key for the firmware.

Enter the Code Key in hexadecimal format.

For example:

0x675BD6D3

The Code Key should match the firmware you are rebuilding.

If you obtained the firmware package using the Unpack Firmware tool, use the Code Key provided by the unpacking process.

4. Upload the Firmware Package

On the Bluetrum Firmware Build page:

Step 1: Select the ZIP File

Click Choose File and select the ZIP package containing your firmware components.

For example:

firmware.zip

Step 2: Enter the Code Key

Enter the correct Code Key in the Code Key field.

Example:

0x675BD6D3

Step 3: Click “Build”

Click:

Build

The tool will process the firmware components and generate a new Bluetrum firmware .BIN file.

5. What the Build Tool Does

During the build process, the tool will:

• Read the firmware components from the ZIP package.
• Process the Resource files.
• Rebuild the Resource section.
• Reconstruct the firmware regions.
• Apply the specified Code Key.
• Rebuild the firmware structure.
• Generate the final .BIN firmware file.

The processing time depends on the size and structure of the firmware.

6. Download the New Firmware

When the build process is completed successfully, the tool will provide the rebuilt firmware for download.

The result will normally be a .BIN file, for example:

firmware-built.bin

Save the file to your computer before testing it.

7. Recommended Workflow

For the safest workflow, keep the original firmware and work on a copy.

A typical workflow is:

Original Firmware
       ↓
     Unpack
       ↓
Modify App / Resource
       ↓
Create ZIP Package
       ↓
     Build
       ↓
New Firmware BIN

This allows you to keep the original firmware unchanged while working on a modified version.

8. Important Notes

Use the Correct Code Key

The Code Key is an important part of the firmware build process.

Using an incorrect Code Key may result in a firmware file that cannot be used correctly.

Keep the Original Firmware

Always keep a backup of the original .BIN file.

Do not overwrite your original firmware with the rebuilt version.

Keep the ZIP Structure Correct

Make sure the required files are inside the ZIP archive and that their filenames remain unchanged.

For example:

header.bin
boot-code.bin
app.bin
res.bin
res/

Do Not Add Unnecessary Files

Only include the files required by the firmware package.

Unnecessary files may cause the build process to fail or produce an unexpected result.

9. Quick Usage

For experienced users, the process is:

Prepare the unpacked firmware → Modify the required files → Create a ZIP package → Upload the ZIP → Enter the Code Key → Click Build → Download the new BIN file.

The resulting firmware can then be inspected or tested on the target device.

Important

Always keep a backup of the original firmware before rebuilding it.

Make sure the firmware components and Code Key belong to the same firmware. An incorrect combination may produce an invalid or incompatible firmware file.