Skip to content

Installation

What you need to do to install/flash Freetz on your FRITZ!Box.

Installation paths

There are three ways to install firmware on a FRITZ!Box:

  • AVM web interface:

    Historically, both AVM and Freetz images could be installed this way. Starting around FRITZ!OS 6.5, AVM enforces signature checks on uploaded firmware.

    Those signatures are generated by AVM only, so modified images are rejected.

    If a self-signed (default) Freetz image is already installed, it includes an additional signature key and allows installing images signed with the same key.
  • Freetz web interface:

    AVM and Freetz images can be installed without signature checks. Downgrades are possible, though generally not recommended.
  • Bootloader/Urlader/ADAM2/ADAM/EVA/FTP:

    AVM and Freetz images can be installed without signature checks. The exact method depends on the device generation.

For initial installation, bootloader flashing is usually required.

Bootloader

The correct bootloader method depends on the device.
In general, tools/push_firmware from Freetz-NG works across all supported methods.
Other tools/scripts exist, and advanced users can also flash manually over FTP.

Bootloader defaults:
* IP: 192.168.178.1 (not necessarily the runtime IP configured in the web UI)
* Credentials: adam2 / adam2

If these credentials do not work, you are likely connected to the normal FRITZ!OS NAS FTP service instead.

The bootloader is reachable only for a few seconds after powering on the device. If you miss the timing window, retry.
Intermediate network devices (switches) can help or hurt timing. Avoid WLAN and powerline for flashing.

Most FRITZ!Box models (except very old single-boot units) have two firmware slots and alternate between them.
You can inspect/switch the active slot using GETENV linux_fs_start in bootloader mode:
BOOTSELECTION

Methods

Available scripts/tools for bootloader flashing:

  • Gen 0: kernel-boot / kernel24

    Early FRITZ!Box devices with Linux kernel 2.4

    • tools/recover-adam from ds-mod

      Kernel/filesystem are written separately (mtd1 kernel, mtd0 filesystem).

      After a bootloader update, partition layout changes and only kernel 2.6 images can be installed.

  • Gen 1: single-boot / NOR

    Early FRITZ!Box models (7050 to 7390)

  • Gen 2: ram-boot / NAND / inmemory

    Newer FRITZ!Box models after 7390, such as 7490 and 7590

    • tools/push_firmware from Freetz-NG
    • eva_tools from YourFritz for Windows/PowerShell

      Note: this script flashes only the intermediate inmemory format, not a full image. See tools/image2inmemory.
    • DieFlashe by BoxenLuther

  • Gen 5: fit-boot / fitimg

    Newest FRITZ!Box models such as 7530 AX and 5530

    • tools/push_firmware from Freetz-NG
    • fit_tools from YourFritz,
      used in Freetz-NG for AVM-specific headers/signatures, then processed by DTC/U-Boot.
    • DieFlashe by BoxenLuther

  • Gen 3: dual-boot

    Older cable FRITZ!Box models with Puma6 (for example 6490, 6590)

    • tools/push_firmware from Freetz-NG
    • DieFlashe by BoxenLuther

  • Gen 4: uimg-boot

    Newer cable FRITZ!Box models with Puma7 (for example 6591, 6660)

    • tools/push_firmware from Freetz-NG
    • uimg-tool by fesc2000 (pack/unpack), also used in Freetz-NG
    • BIOS/version notes: ffritz by fesc2000

Short version: use tools/push_firmware unless you explicitly need something else.

push_firmware

  • Show all options: tools/push_firmware --help
  • You can also call it via make push_firmware (no extra parameters)
  • Without parameters, it uses the latest built image
  • If you do not know why you need a parameter, do not use it; auto-detection should normally work

Notes

  • Terms like NOR, NAND, INHAUS are often community naming conventions, not official AVM terminology.
  • There is much more reference material in forums (IPPF, IPF) and on GitHub (Freetz-NG, YourFritz).
  • "FRITZ!Box" here also includes other AVM devices that are not branded as FRITZ!Box.