Recovery multiboot Amiko viper4kv40

Congratulations for your work !!!

Two years ago I've tested the compatibility of Dinobot images with Viper V20,V30 and V40 !

except of different names for archive image folders ... the image works and Viper RC was

understood in Dinobot image ! Sure ... there is not a certitude that this is true at Bootloader

lowest level !

Unfortunately , for the moment I cannot test your procedure ! the Viper is not Home !!!

I believe that the first step , installing bootloader extension, will work on

any Viper 4K ... V20,V30,V40 ! then user must adapt the /backup image

to his real model ! The only thing that bothers me is the RC !!! if we don't

have a Dinobot RC ... the procedure is useless !

Regarding the return to the original state ! it can be done using the

"recovery image" I've posted ! it was tested on V20 and V30 and is

working ... is reinstalling the original boot context for V30 but after that

you can reflash any image for V20 or V30 as well !

Recovery file for V30 : https://mega.nz/file/L8lwlTbT#…IXoZj3UNjUYsdt4mAEdizlLtg

I have a question who and when creates the multiboot partitions ?

I cannot see in the Menu a section to initialize the EMMC !

Quote from MAHDI-DZ

1. Put usb_update.bin in USB and update by green button

2. Download from opena.tv image for u571. Unzip and rename folder to \backup

3. Copy files to a new USB and make sure directory is like \backup\rootfs.tar.bz2 and \backup\kernel.bin

4. Connect new USB to box and update by green button

5. Choose second option when new update panel shows up

- noting remote Amiko viper4kv40 do not work with recovery must remote dinobot 4k

1) eth0 MAC address is changed to aa bb cc dd ef 22

2) Tuner B is not working

Display More

hello, I wanted to ask you if it can work on amiko viper v30 decoder I had so many problems with this machine as it does not have a recovery partition

Don't try this procedure on Viper V30 !!! will hang the STB !!!

To recover Viper V30 use this : https://mega.nz/file/L8lwlTbT#…IXoZj3UNjUYsdt4mAEdizlLtg

Quote from mihaip

Don't try this procedure on Viper V30 !!! will hang the STB !!!

To recover Viper V30 use this : https://mega.nz/file/L8lwlTbT#…IXoZj3UNjUYsdt4mAEdizlLtg

thank you bro yesterday i managed to recover my box with your bin file i was wondering if it's possible to have a multiboot but if it's not possible i'm satisfied

Don't try it ! will hang your box ! unless you have a Dinobot RCU !!!

there is no simple way to go back !!!

Quote from mihaip

Don't try it ! will hang your box ! unless you have a Dinobot RCU !!!

there is no simple way to go back !!!

with your bin file I recovered the box from an image installed incorrectly the problem that I can only install the openatv 6.3

My "bin" is restoring OpenATV 7.0 on a Viper V30 ! then from "flash online"

menu , with a USB stick inserted , you can restore any of 6.4 , 7.0 , 7.2 and 7.2

from official feeds !!!

I think I sent it to brick mode it doesn't flash anymore udate even with its bin file

I insert a pen usb from the format with disk genius I insert the image with the amiko folder into the usb the decoder on the display exits udite by pressing the green button several times the flash tool screen appears and tells me that the operation was successful, the decoder it restarts and I have a black screen after starting with logo if I use the openatv 6.4 image it works otherwise the decoder is blocked

The bin file I've sent is to be used in the root of the USB stick !!!

not in any folder !!!

Quote from mihaip

The bin file I've sent is to be used in the root of the USB stick !!!

not in any folder !!!

I tried it flashes sometimes I have to press the green button quickly and I see udp on the display the screen comes out but openatv 7.0 doesn't start on startup I can't install any image except openatv 6.4

Don't use this package !

- there is no way back to the single boot !

- the package creates a multiboot partitions system non standard

it destroys some box descriptors and some devices cease to work !!!

- after some images writes from the "flash online" menu the boot

menu cease to show up !!!

In my case ....

- second tuner cease to work

- after a image rewrite , no image on TV !!!!

- boot menu cease to show at GREEN button

- the only RC understood by boot menu is Dinobot

The way back was proven to be a adventure !!!

Quote from MAHDI-DZ

1. Put usb_update.bin in USB and update by green button

2. Download from opena.tv image for u571. Unzip and rename folder to \backup

3. Copy files to a new USB and make sure directory is like \backup\rootfs.tar.bz2 and \backup\kernel.bin

4. Connect new USB to box and update by green button

5. Choose second option when new update panel shows up

- noting remote Amiko viper4kv40 do not work with recovery must remote dinobot 4k

1) eth0 MAC address is changed to aa bb cc dd ef 22

2) Tuner B is not working

Display More

can you give more detail about how you produced this multiboot?

loader_multi is written by you?

My representation about the multiboot structure is like this ...

- first partition contains apploader.bin , the menu for managing multiboot

structure at boot moment requested by GREEN and some info about the

content of multiboot system

- then a pair of partitions (kernel and rootfs ) for each image installed in multiboot

Apploader must have knowledge about HW of host machine ! At the multiboot

system creation the EMMC will have a large number o f partitions ... I think

to acomodate some 16 images ! witch are resized and located at the moment

when each of them is populated.

Hello everyone, I would like to ask for help in amiko viper v40, I uploaded the recovery-multibot-viper4kv40.zip, but I can't use it because it is completely stopped, what can be done with it? Only the multi boot version is on the TV screen and it does not respond to anything. Thank you for the answers.

If you want to restore the viper4k to the original firmware you can find the details and a zip archive on openbh board