Reflash With Open-ATV From The Terminal

We asking all new users to read the articles below, before creating their first posting or thread.

  • 4. Instruction Articles

    • Please note, in this forum are only English threads and postings allowed, without any exception!

      Please follow the forum rules, thank you for your understanding.

  • This method will not really be applicable or desirable for everyone, but it can get you out of trouble under some circumstances, so:-

    If you have just done a software update and found the box won't boot...


    You just turned your box on and found that it only boots up so far and hangs there...


    You just turned your box on and found that it gets caught in a loop with the numbers counting up and then starting again...


    You went to try to reflash online and found that your build is so old you don't have the option to flash the latest version of Open-ATV via the Flash Online utility...


    You want to reflash your box but have not got a spare USB stick or your box will not "see" the USB stick...


    Your box blue-screens when selecting system functions...

    Then this is a possible solution for you.

    It will find the latest build of the current stable version of Open-ATV and will then flash your box.

    All you need is :

    Your box with an existing USB stick or recording disk mounted on /media/hdd, (this should normally be the case for recordings etc).

    You need to be able to connect to your box with a Laptop or PC via Putty or Zoc, (or any other ssh client program), or the OpenWebIf terminal.

    The default hostname of your box if you have changed it from the default.

    Please note that this does NOT backup any of your settings or anything else.

    Now connect to your box from a PC or Laptop using a terminal program such as Putty, Zoc, any other ssh client, or using the terminal option of OpenWebIf in your browser and log in using the username root

    Now paste all the code below into the terminal window.

    wget --no-check-certificate -O && bash

    After a few seconds you will be asked to enter the box's default hostname.

    If you've never changed the hostname of your box then just accept the default by pressing enter key, if you have previously changed the hostname in the past then you need to enter the original default hostname for your box, (ie formuler4turbo), and then press the enter key.

    Now you are prompted which partition you want flashed, this is for boxes with multiboot facilities.

    If you don't use multiboot or your box doesn't have multiboot facilities just hit the enter key.

    If your box is configured to use multiboot enter the partition number and then press enter key. Most people here will not need to worry about Multiboot as the majority of boxes do not support that facility. That said, if your box does support Multiboot then I am going to assume that you already know what to do.

    The latest stable nightly build will then be downloaded to /media/hdd and then the reflashing process will begin. Either way, it's now time to reach for your remote.

    If it is your intention to just flash to the current version of Open-ATV then follow the guided installation process.

    Edited once, last by xero ().

  • This didn't work for me! Still stuck on my old and broken version of 6.3. I got the following in Terminal. Any ideas?

    zgemmah9s login: root

    [email protected]:~# wget --no-check-certificate -O && bash

    --2019-10-11 18:31:35--

    Resolving 2620:100:6020:1::a27d:4001,

    Connecting to|2620:100:6020:1::a27d:4001|:443... connected.

    HTTP request sent, awaiting response... 301 Moved Permanently

    Location: /s/dl/nqbo698rxconave/ [following]

    --2019-10-11 18:31:36--

    Reusing existing connection to []:443.

    HTTP request sent, awaiting response... 302 Found

    Location: https://uc153997689718910807f7…wzpfBev9_dRjvDAvUs_NXi4io

    Hq9ZcELwWw8XM8EbpMy2HRAvXN3tjR0OtRYDK8GZkq-T8IoqBXNz_V-wFQ5U2wGyQEYmOmqSsqyECOSg/file?dl=1# [following]

    --2019-10-11 18:31:36-- https://uc153997689718910807f7…/cd/0/get/AqNxrwzpfBev9_d


    Resolving 2620:100:6020:6::a27d:4006,

    Connecting to|2620:100:6020:6::a27d:4006|:443... connecte


    HTTP request sent, awaiting response... 200 OK

    Length: 896 [application/binary]

    Saving to: ‘’ 100%[===========================================>] 896 --.-KB/s in 0s

    2019-10-11 18:31:37 (11.4 MB/s) - ‘’ saved [896/896]

    You are about to flash your zgemmah9s box with the latest stable image of ATV

    If using multiboot box please enter partition to flash:

    --2019-10-11 18:31:48--…v-6.3-zgemmah9s-20191010_


    Connecting to||:80... connected.

    HTTP request sent, awaiting response... 200 OK

    Length: 214547027 (205M) [application/zip]

    Saving to: ‘latestatv’

    latestatv 100%[===========================================>] 204.61M 837KB/s in 7m 17s

    2019-10-11 18:39:06 (479 KB/s) - ‘latestatv’ saved [214547027/214547027]


    inflating: bootargs.bin

    inflating: fastboot.bin

    creating: h9/

    inflating: h9/imageversion

    inflating: h9/bootargs.bin

    inflating: h9/rootfs.ubi

    inflating: h9/noforce

    inflating: h9/logo.img

    inflating: h9/pq_param.bin

    inflating: h9/rootfs.tar.bz2

    inflating: h9/fastboot.bin

    inflating: h9/baseparam.img

    inflating: h9/uImage

    ofgwrite Utility v4.5.5

    Author: Betacentauri

    Based upon: mtd-utils-native-1.5.1 and busybox 1.24.1

    Use at your own risk! Make always a backup before use!

    Don't use it if you use multiple ubi volumes in ubi layer!

    Flashing rootfs

    Flashing kernel

    Searching image files in ./ resolved to /media/hdd/atvimage/h9

    Found rootfs file: /media/hdd/atvimage/h9/rootfs.ubi

    Found rootfs file: /media/hdd/atvimage/h9/rootfs.tar.bz2

    Found kernel file: /media/hdd/atvimage/h9/uImage

    Found UBIFS rootfs

    Found mounted /newroot

    Found mountpoint for rootfs file: /media/hdd

    Found /proc/mtd entries:

    Device: Size: Erasesize: Name: Image:

    mtd0: 00100000 00020000 "boot"

    mtd1: 00100000 00020000 "bootargs"

    mtd2: 00100000 00020000 "baseparam"

    mtd3: 00100000 00020000 "pqparam"

    mtd4: 00100000 00020000 "logo"

    mtd5: 00100000 00020000 "deviceinfo"

    mtd6: 01000000 00020000 "kernel" -> /media/hdd/atvimage/h9/uImage

    mtd7: 0ea00000 00020000 "rootfs" -> /media/hdd/atvimage/h9/rootfs.tar.bz2

    Using kernel mtd device: /dev/mtd6

    Using rootfs mtd device: /dev/mtd7

    killall: CCcam: no process killed


    kill [options] <pid> [...]


    <pid> [...] send signal to every <pid> listed

    -<signal>, -s, --signal <signal>

    specify the <signal> to be sent

    -l, --list=[<signal>] list all signal names, or convert one to a name

    -L, --table list all signal names in a nice table

    -h, --help display this help and exit

    -V, --version output version information and exit

    For more details see kill(1).


    kill [options] <pid> [...]


    <pid> [...] send signal to every <pid> listed

    -<signal>, -s, --signal <signal>

    specify the <signal> to be sent

    -l, --list=[<signal>] list all signal names, or convert one to a name

    -L, --table list all signal names in a nice table

    -h, --help display this help and exit

    -V, --version output version information and exit

    For more details see kill(1).

    killall: kodi.bin: no process killed

    killall: hddtemp: no process killed

    killall: transmission-daemon: no process killed

    killall: openvpn: no process killed

    sh: /etc/init.d/sabnzbd: No such file or directory

    Stopping automount: done.

    Syncing filesystem



    start umount_rootfs

    [email protected]:~# cp: can't stat '/lib/libcrypt*': No such file or directory

    Switching to user mode 2

    Session closed.

  • SAM

    Closed the thread.