Firmware update for Dreambox DM920 for CCcam/OScam: complete guide 2026

If you have a DM920 for sharing and haven't touched the firmware for a long time — you have probably already encountered the issue that OScam starts glitching, ECMs hang, or decryption disappears altogether after the next emulator update. Updating the firmware for Dreambox DM920 is not scary, but it requires preparation. Without a backup of configurations and an understanding of how the bootloader works, you can lose the working configuration that you have built over months.

This guide is for those who are already working with the receiver in sharing, know the difference between oscam.server and CCcam.cfg, and want to safely reflash the machine without panic.

What you need to know before updating the DM920 firmware

DM920 UHD is not a budget receiver with a single boot slot. It has a Broadcom BCM7252S, ARMv7 architecture, and the bootloader can work with multiple multiboot slots. This is important: you can hold two images simultaneously and switch between them without panic. But the basic principles of flashing need to be understood before you press the button.

Hardware features of DM920 UHD and bootloader

The Broadcom chip and built-in rescue bootloader make the DM920 practically unbrickable. Even if something goes wrong, the bootloader remains untouched and allows you to start recovery from USB. This fundamentally distinguishes the DM920 from cheaper clones, where a failed flash turns the box into a paperweight.

The receiver has two NAND slots for images. They are completely independent — configurations, emulators, keys in one slot do not affect the second. Switching between slots occurs through the bootloader menu at startup.

Choosing an image: OpenATV, OpenPLi, factory Dreambox OS

The native Dreambox OS from Dream Multimedia is an Enigma2-based system focused on stability. It supports tuners well, but there are fewer plugins and the feed updates more slowly.

OpenATV 7.5 (current branch for 2026) is the most popular choice for sharing. Huge repository, OScam and CCcam can be installed via feed with one click, active community. OpenPLi 9.x is a bit more conservative, but very stable. Both officially support DM920. The practical difference: OpenATV updates more often, sometimes something breaks; OpenPLi updates less frequently, but usually works predictably.

What are the risks of incorrect firmware and how to avoid a "brick"

The main risk is downloading an image not for the correct model. DM920 and DM900 look similar externally, but they are different machines with different SoCs. An image from DM900 will not install correctly on DM920. Always check: the file name must containdm920, notdm900 ordm7080.

The second risk is losing power during the writing process. If flashing is interrupted halfway, the bootloader will survive, but the slot with the image will be damaged. This can be resolved by reflashing from rescue mode — there is no need to panic.

Backing up CCcam/OScam configurations before flashing

Flashing completely erases the root file system. All your configurations, emulators, and keys go along with it. Before updating the firmware for Dreambox DM920, copy the following paths via FTP or SSH:

• /etc/tuxbox/config/oscam/ — the entire directory (oscam.conf, oscam.server, oscam.user, oscam.dvbapi)
• /etc/CCcam.cfg or/var/etc/CCcam.cfg — depending on the image
• /usr/keys/ — SoftCam.Key and all key files
• /etc/enigma2/ — channel list and tuner settings

If you use a backup plugin (for example, BackupSuite in OpenATV), it will save Enigma2 settings, but OScam configurations may not be picked up — check this separately. The most reliable way is to manually copy the folders before flashing.

Ways to flash Dreambox DM920: USB, online, and multiboot

There are several scenarios, and they are fundamentally different. Online update is an update within the same image, without changing the distribution. USB flashing is changing the image or a clean reinstall. Multiboot is a completely different story.

Online update via the menu (Software Update)

Menu → Settings → System → Software → Check for updates. Works only within the same image. If you are on OpenATV 7.5 — update to the current build of OpenATV 7.5, you won't be able to update to OpenPLi.

The downside of the online update: sometimes the SoftCam plugin fails after it. This is a known issue — the plugin is installed over the image, and after the image update, the path to the binary may break. It can be resolved by reinstalling the plugin through the feed after the update.

Firmware from USB flash drive (recovery / rescue mode)

The flash drive must be formatted in FAT32. The bootloader does not recognize NTFS and exFAT. The maximum file size on FAT32 is 4 GB; images are usually smaller, but if the archive happens to be larger — unpack it before writing to the flash drive.

The folder structure on the flash drive is important. For OpenATV: the unpacked image is placed in the root of the flash drive or in a folder named after the model — check the README of the specific build. For the factory Dreambox OS, the structure is different, as described in the manufacturer's official documentation.

Installing multiple images via multiboot

DM920 supports two slots. When starting with the button pressed or through the bootloader menu, you can choose which slot to boot from. This is a real safety measure: keep a working tested image in the first slot, experiment in the second. Configurations between slots are not shared — each has its own file system.

Flashing over the network (NFI/FlashWizard, FTP)

FlashWizard is a Windows utility that allows you to upload an image over the network. Direct access to the receiver in the local network is required. FTP access works on the standard port 21 (login root, password usually dreambox or empty — depends on the image). Through OpenWebif (port 80), you can update plugins and configurations, but not reflash the image itself. Network flashing is convenient if you don't have a USB drive at hand, but it is slower and more sensitive to network interruptions.

Step-by-step instructions: flashing DM920 with USB

Let's go through the steps as specifically as possible. Updating the firmware of the Dreambox DM920 via USB is the most reliable method when changing the image.

Preparing the flash drive and unpacking the image

Step 1. Download the current image for DM920 from the official website of the distribution developer (openatv.org or openpli.org). Make sure that your model is mentioned in the file name:dreambox-image-dm920....

Step 2. Format the USB flash drive to FAT32. In Windows — right-click → Format → FAT32. In Linux:mkfs.vfat -F 32 /dev/sdX. A flash drive of 2 GB will be sufficient with a margin.

Step 3. Unpack the image archive, preserving the directory structure. Do not drag files manually — just unpack zip/tar.gz to the root of the flash drive. The typical structure for OpenATV looks like this: a folderdreambox-image-dm920 and a fileMANIFEST or similar.

Booting into recovery mode

Step 4. Insert the flash drive into the rear USB port of the receiver (the front one may not work in rescue mode). Turn off the receiver using the power switch at the back. Wait 5–10 seconds.

Step 5. Turn on the receiver while holding the power button on the front panel, or wait for the bootloader to appear on the screen. The bootloader menu will appear on the screen with options: boot from slot 1, slot 2, rescue mode. Select "Flash from USB" or a similar option. Control is via buttons on the panel or remote, depending on the version of the bootloader.

Writing the image and first launch

Step 6. After confirmation, the flashing will begin. A progress bar or text output will be displayed on the screen. Typical time is 3–7 minutes. Do not turn off the power, do not remove the flash drive.

Step 7. After completion, the receiver will automatically reboot. The first launch of the new image takes 1–2 minutes longer than usual — this is normal, initialization is taking place.

Checking the firmware version and tuner drivers

Step 8. Go to Menu → Information → About system (or similar in your image). Make sure that the version matches the downloaded build. Then check the tuner: Menu → Settings → Tuner → check if it has been recognized correctly.

If a replaceable tuner module (DVB-T2, DVB-C instead of the standard DVB-S2) is installed in the DM920, a different driver may be required after flashing. OpenATV and OpenPLi include drivers for most modules, but if the tuner is not recognized — check the feed for the packagedreambox-dvb-modules or a similar one for your configuration.

Setting up CCcam and OScam after firmware update

After a clean installation of the image, you have a bare system. There are no configs, no emulators. First, restore, then configure.

Restoring configs from backup

Connect to the receiver via FTP (port 21, login root) or SSH (port 22). Copy your saved configs back. But don't rush to just overwrite everything as it is — first install the required version of OScam or CCcam, then restore the configs. Configs from the old version of OScam on the new binary may cause the emulator to crash on startup, especially if the syntax of oscam.conf has changed between versions.

Check compatibility: the version of OScam in the log at startup will show the build number. If the config was written for r11700, and now it's r11800+ — go through the emulator's changelog for changes in the sections[global] and[reader].

Paths to files: /etc/tuxbox/config and /usr/keys

Standard paths after installation in most images:

• OScam configs:/etc/tuxbox/config/oscam/ — files oscam.conf, oscam.server, oscam.user, oscam.dvbapi
• OScam binary:/usr/bin/oscam
• CCcam config:/etc/CCcam.cfg (in some images —/var/etc/CCcam.cfg)
• Keys and SoftCam.Key:/usr/keys/
• OScam log: the path is set inoscam.conf in the section[global], parameterlogfile, usually/tmp/oscam.log

Paths may vary depending on the image and installation method. If something is not found — check viafind / -name oscam.conf 2>/dev/null.

Installing OScam/CCcam as a plugin or binary

In OpenATV and OpenPLi, the easiest way is through Menu → Plugins → feed. Look for packagesoscam,oscam-emu (the version with softcam-emulation support),cccam. After installation via feed, the launch occurs through the SoftCam menu or MultiCAM plugin.

An alternative is to install the binary manually. Download the latest OScam build for ARMv7 (architecture DM920), place it in/usr/bin/oscam,chmod 755 /usr/bin/oscam, create an init script or use a ready-made one from the package. The advantage of this approach is complete control over the emulator version.

Checking ports and protocols (newcamd, cccam)

Inoscam.conf the section[dvbapi] is responsible for decrypting the local card. The parameterenabled = 1,user = dvbapi,pmt_mode depends on your setup. For sharing via the CCcam protocol inoscam.server add a reader withprotocol = cccam, the default port for the CCcam server is 12000 (but the actual port is set in the server config provided by your sharing provider). For newcamd —protocol = newcamd, typical ports are 28910–28950.

In CCcam.cfg, the connection string to the server looks like:C: hostname port username password. The line F: — is your local cardserver for clients. Make sure the file ends with a newline — CCcam sometimes ignores the last line without it.

Typical problems after flashing and their solutions

Most problems after updating the firmware of the Dreambox DM920 can be resolved in 10–15 minutes if you know where to look.

The receiver does not boot / hangs on boot

If after flashing the receiver is stuck on boot — do not panic. The DM920 bootloader is alive. Turn off the receiver with the switch at the back, insert the USB with the image, enter rescue mode, and repeat the flashing. Check the folder structure on the flash drive — this is the most common reason. Also, make sure the image is specifically for DM920, not for a similar model.

If the receiver does not respond at all — try another USB flash drive. Some flash drives with write protection or non-standard controllers are not recognized in the bootloader.

The tuner does not see the signal or there are no channels

First, go to the tuner settings and check if it is recognized at all. If a non-standard DVB-T2 or DVB-C module is installed — the image may not include the driver for it by default. Install the corresponding driver package from the feed.

If the tuner is DVB-S2 and there is no signal — rescan the satellites. After a clean installation of the image, the channel list is empty or uses a default list that does not match your antenna configuration.

The emulator does not start or there is no ECM/decryption

Check the log.tail -f /tmp/oscam.log will show everything: config errors, connection issues to the server, dvbapi refusal. Common reasons:

• File permissions for the config files:chmod 644 /etc/tuxbox/config/oscam/*
• Incorrect system time — ECM requires synchronization. After a clean flash, NTP may not work. Check the time settings in Enigma2, add the NTP server (pool.ntp.org) manually if needed
• Incorrect oscam.dvbapi — make sure it is correctly specifiedapi = 9 orapi = 1 depending on the version
• Incompatibility of the config with the version of the binary — delete the configs, run OScam with default settings, make sure it starts, then add readers one by one

OScam status in real time — web interface on the port specified in the section[webif] in oscam.conf (parameterhttpport, usually 8888). You can see active readers, ECM requests, and responses there.

Rollback to the previous firmware via multiboot

If the new image works worse — switch in the bootloader to the second slot with the previous image. This takes less than a minute. That’s why it makes sense to ensure that a verified working image is in another slot before updating the firmware of the Dreambox DM920 — multiboot is created for such cases.

If there is no second slot or both slots have the same image — reflash the saved old image from USB. Therefore, it is advisable to keep the archive of the previous firmware for at least a couple of weeks after the update.