Dreambox DM920 firmware: image update 2026

Updating the Dreambox DM920 firmware is not a process where you can act randomly. One mistake in choosing the image or the structure of the flash drive, and the receiver freezes on the logo, while the CCcam and OScam configurations disappear. I will break down the entire process step by step: from choosing the right image to restoring the softcam after reflashing.

DM920 UHD is not the easiest device to maintain. Multi-boot, several slots, a specific bootloader — if you don't know the details, it's easy to make things worse. But once you figure it out, everything becomes predictable.

Which image to choose for DM920 UHD and where to get the firmware

The first thing to understand is that images for DM920 are not interchangeable with images for DM900, DM820, or any other Dreambox. DM920 runs on the Broadcom BCM7252S SoC, and its flash memory layout is unique. Flashing a "similar" image is a sure way to brick the device.

Factory Dreambox OE 2.6 vs OpenATV and OpenPLi

The official image from Dreambox is provided as a .zip archive. Inside is a folderdreambox/ with files for a specific model. Third-party builds — OpenATV and OpenPLi — are structured differently: separatelyrootfs.tar.bz2 andkernel.bin. The structure is different, and this is important when manually unpacking onto the flash drive.

For cardsharing, the difference between images is noticeable. OpenATV has a built-in feed with OScam, OScam-emu, and CCcam — they can be installed through the package manager in a few clicks. With the factory OE 2.6, you will have to manually search for and install .ipk packages. If OScam is needed with extended emulation (OScam-emu), OpenATV is more convenient.

OpenPLi is a more minimalist option, stable, but the feeds with softcam are scarcer there. It will suffice for a simple CCcam client, but for a server with multiple readers, OpenATV is better.

What distinguishes the DM920 model (BCM7252S) from the DM900

The DM900 also uses the BCM7252S, but that doesn't mean the images are compatible. Different hardware revisions, different NAND memory layouts, different bootloader versions. Dreambox intentionally creates images for specific models — even within the same line, there can be board revisions where a newer image loads, while an image for another revision freezes completely.

In practice: always download the image marked specifically "DM920" and check the file's hash after downloading. MD5/SHA256 for official images are published next to the file.

Checking the compatibility of the image and the current bootloader

The version of the current bootloader can be viewed in the menu:Menu → Information → About. There you can also see the version of the current image and the slot it is in. If the bootloader is old (before 2023), some newer OpenATV images may not start — you will need to update the loader first using the official Dreambox image.

Another point: DM920 supports multi-boot — several independent slots for images. This really helps: keep a working image in one slot and an experimental one in another. If something goes wrong, switching takes seconds.

Preparing the USB flash drive and backing up settings

Before starting the Dreambox DM920 firmware update, you need to save everything that has been painstakingly earned. After completely rewriting the softcam slot, configurations and channel lists are reset. Restoring everything from scratch is a less than pleasant experience.

Formatting the flash drive to FAT32 and folder structure

The flash drive for the firmware must be FAT32 — no exFAT, NTFS, or ext4. The DM920 simply will not see the image on another file system. Flash drives larger than 32 GB are formatted to exFAT by default in Windows — this is a problem. Use a utility like Rufus or the commandmkfs.fat -F 32 /dev/sdX in Linux to forcibly create FAT32.

File structure on the flash drive: for the official image, unpack the .zip so that the folderdreambox/ is at the root of the flash drive. For OpenATV, the filesrootfs.tar.bz2 andkernel.bin are placed in the root or in a folder named after the model — it depends on the version of the installer, read the README in the archive.

Backup of CCcam.cfg and oscam.server configurations before flashing

The paths of CCcam configs on DM920 depend on how it was installed. Usually, it is one of two options:

• /etc/tuxbox/config/CCcam.cfg
• /usr/keys/CCcam.cfg

OScam stores configs in the directory/etc/tuxbox/config/oscam/. There are three main files:oscam.conf (general settings and httpport),oscam.server (readers and C-line/N-line),oscam.user (users). Copy the entire folder.

Copying via SSH is the easiest:

scp -r [email protected]:/etc/tuxbox/config/oscam/ ./backup/

Or just mount a USB flash drive to the receiver and copy there. The main thing is to do this before flashing, not after.

Saving the channel list, bouquets, and SoftCam Panel

Bouquets and the channel list are located in/etc/enigma2/. There are files likeuserbouquet.*.tv andlamedb. Save the entire folder.

The built-in backup in Enigma2 is done throughMenu → Setup → Software → Backup — it will automatically pack most of the settings. But softcam configs do not always get included, so manual copying is essential.

Updating firmware via the internet (flashonline) and via USB

There are three ways to update the firmware of Dreambox DM920: online through the menu, manually from a USB flash drive, and via RescueLoader over the network. Each is suitable for its own situation.

Method 1: online update flashonline through the menu

The simplest option when the receiver is working and there is a stable internet connection. Path:Menu → Standby/Restart → Flash Online. The receiver connects to the Dreambox servers, shows available images for your model, and uploads the selected one to the specified slot.

One downside: a stable internet connection is needed throughout the loading and writing of the image. If the connection is interrupted during the writing process — it can lead to a potentially bad situation. With an unstable connection, it is better to use USB.

Method 2: manual flashing from a USB drive

Insert a prepared FAT32 flash drive with the unpacked image, restart the receiver. Enigma2 detects the presence of the image on the flash drive at startup and offers installation. Choose the target slot, confirm — and do not touch anything until the process is fully completed and the automatic reboot occurs.

Do not turn off the power during the writing process. At all. Even if it seems to be frozen — wait at least 10 minutes. Writing to NAND memory is slow, and interruption at this stage will definitely damage the slot.

Method 3: changing the image via RescueLoader (port 80)

RescueLoader is an emergency web interface built into the DM920 bootloader. It operates on port 80. To access it, you need to hold the power button on the front panel when turning on the receiver (or use the button on the back panel, depending on the revision). The receiver will not load Enigma2 but will enter recovery mode.

In the browser, openhttp://<IP receiver> (port 80). There will be a simple interface: select a slot and upload rootfs and kernel files. This method saves when the receiver does not boot at all — Enigma2 is unavailable, but RescueLoader works.

Through RescueLoader, it is also convenient to switch multi-boot slots without a complete reflash: just select another slot and reboot.

Restoring CCcam/OScam after firmware update

After a complete rewrite of the softcam slot, it is no longer available — it needs to be installed again. This is a mandatory step that many underestimate, and then wonder why channels are not decoded.

Installing softcam: CCcam, OScam, OScam-emu

On OpenATV, the path is simple:Menu → SoftCam → select the desired softcam from the list and install. The feed pulls the latest versions: OScam, OScam-emu (with emulation support), CCcam. OScam-emu should be taken if you need to work with emulated keys — it is built with additional modules.

On the factory OE 2.6, you will have to download the .ipk manually and install it via:

opkg install /tmp/oscam_XXXXXXXX_mips32el.ipk

The CCcam binary can be placed directly in/usr/bin/CCcam, give execution rights (chmod 755 /usr/bin/CCcam) and add an init script in/etc/init.d/ for auto-start. This path is more flexible but requires manual effort.

Restoring configs and access rights (chmod 600)

We restore the configs from the backup to their places:

• /etc/tuxbox/config/CCcam.cfg — for CCcam
• /etc/tuxbox/config/oscam/oscam.conf
• /etc/tuxbox/config/oscam/oscam.server
• /etc/tuxbox/config/oscam/oscam.user

Be sure to set access rights on the files with credentials:

chmod 600 /etc/tuxbox/config/oscam/oscam.server

This is not paranoia — this is minimal protection of C-line and N-line from being read by other processes. On OE 2.6, rights sometimes reset after a reflash, so check.

One nuance: the config paths between OE 2.6 and OpenATV may differ. On OpenATV, oscam sometimes looks for configs in/etc/oscam/ instead of/etc/tuxbox/config/oscam/. Check where the parameterConfigDir points in your version, and place the files there.

Checking ECM operation and decoding time

After starting OScam, we enter the web interface at the addresshttp://<IP receiver>:8888 (the port is set by the parameterhttpport inoscam.conf). Here you can see the statuses of readers, active connections, and ECM time — the time it takes to decode a packet.

Normal ECM time for a cardsharing client is up to 500 ms. If you see 2–5 seconds or errors like "no card," the problem is either in the oscam.server config (incorrect host/port/password) or in the network. The CCcam client is checked similarly: look at the log in/tmp/CCcam.log.

A separate trap: after flashing, the system time may reset. OScam relies on correct time — if the clock shows the year 2000, ECM will not decode at all. NTP synchronization is configured inMenu → Setup → System → Time& Date. Make sure that the NTP server is accessible and the time is set correctly before checking the softcam.

Another problem I have personally seen: if CCcam and OScam are running simultaneously on the receiver, they conflict over ports and resources. After installation via feed, it is easy to accidentally start both. Check viaps aux | grep -E 'CCcam|oscam' and leave only one softcam.

Typical firmware errors for DM920 and how to fix them

Updating the firmware of the Dreambox DM920 sometimes does not go as planned. Let's discuss real problems and their solutions — without fluff.

Black screen and hanging on boot logo

The most common issue is that the image was uploaded for the wrong hardware revision. The receiver turns on, shows the Dreambox logo, and hangs completely. Enigma2 does not start. This is not the end.

The solution is RescueLoader. You turn on the receiver while holding the power button (or the network button, depending on the device), open a browser to the receiver's IP on port 80. There you select another multi-boot slot with a working image — or re-upload a known working rootfs/kernel. The receiver gets its IP via DHCP even in RescueLoader mode, check in the router.

It can be more subtle: an old image works, a new one hangs on the same hardware. This often indicates different revisions of flash memory in different batches of DM920. In this case, refer to the official release notes of the image — they sometimes specify the supported board revisions.

The receiver does not see USB or the image is not found

Three reasons that occur most often:

• The flash drive is not FAT32. On flash drives larger than 32 GB, Windows automatically formats them as exFAT — DM920 does not mount it. Force format it to FAT32.
• Incorrect folder structure. The image must be placed exactly as described in the instructions for that specific image. Extra folders or renamed files — and the receiver sees nothing.
• The flash drive is connected to a USB 3.0 port through a hub with unclear power supply. It is better to connect directly, and preferably to a USB 2.0 port if there are several on the case.

Rollback to the previous multi-boot slot

Multi-boot is the main safety net when updating the firmware of the Dreambox DM920. If the new image in slot 2 does not work, you can switch to slot 1 with a working image via RescueLoader or directly from the Enigma2 menu, if it loads at all:Menu → Setup → Software → Select Image.

Through RescueLoader, this is done in 10 seconds: select the active slot — save — reboot. This is not a re-flash, just a change of pointer to the active image. Quick and safe.

Loss of C-line after changing the image can happen for another reason: some cardsharing providers tie the line to the external IP. If you have a dynamic IP and it changed during the receiver's downtime — the line may become non-functional regardless of the firmware. Check the current external IP and contact the provider if necessary to update the binding.