1306 replies to this topic

[digidude]

would it be possible to add the new Technomate-OE receivers to this plugin? the code is very similar to the Vu+ receivers, and from looking at this, and the ViX backup .py script, they seem very similar

[digidude]

from a quick look (but have had a few beers lol) it looks like this is the extras, ive tried a rough copy into the existing plugin, but am going wrong somewhere

 

ive only copied the main bits that ive edited stuff into

 

[ -f /proc/stb/info/hwmodel ] ; then
    MODEL=$( cat /proc/stb/info/hwmodel )
    TYPE=TM
    SHOWNAME="$MODEL"
    MAINDEST="$MEDIA/update/$MODEL/cfe"
    EXTRA="$MEDIA/fullbackup_$MODEL/$DATE/update/$MODEL/cfe"    
    MKUBIFS_ARGS="-m 2048 -e 126976 -c 4096 -F"

 

 

    $NANDDUMP /dev/mtd6 -q > "$WORKDIR/vmlinux.gz"

 

 

    mv "$WORKDIR/root.ubifs" "$MAINDEST/oe_rootfs.bin"
    mv "$WORKDIR/vmlinux.gz" "$MAINDEST/oe_kernel.bin"

[Pedro_Newbie]

I've no intention to support this box, I even don't know them.

I'll stick to all Openpli supported boxes except the Dreambox models

 

What is going wrong with your attempts?

What is the output of the command:

cat /proc/mtd

[digidude]

id had quite a few beers last night while trying, the error i was getting was something along the lines of unexpected end of file, expected 'fi'

 

heres the output

 

root@tmtwinoe:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00300000 00010000 "vmlinux"
mtd1: 00100000 00010000 "splash"
mtd2: 00080000 00010000 "cfe"
mtd3: 02d00000 00020000 "tmtwin"
mtd4: 0be00000 00020000 "rootfs"
mtd5: 00b00000 00020000 "bcmdrv"
mtd6: 00900000 00020000 "nkernel"
root@tmtwinoe:~#

[bosspapy]

Good evening Pedro

I'm testing for GoldenMedia decoder on the Hypercube OpenPLi 2.1 and, after many tests, we are managing to make it all work thanks to the team of Oscam.

I am part of Team Italysat and would like to ask if it is possible a collaboration to test your plugin on this decoder Hypercube.

 

Hypercube root @: ~ # cat / proc / mtd

dev: size erasesize name

mtd0: 00500000 00020000 "rcv.kernel"

MTD1: 00a00000 00020000 "rcv.rootfs"

MTD2: 00800000 00020000 "e2.kernel"

MTD3: 05a00000 00020000 "e2.rootfs"

mtd4: 00a00000 00020000 "android.param"

mtd5: 00800000 00020000 "android.kernel"

mtd6: 00e00000 00020000 "android.rootfs"

mtd7: 06e00000 00020000 "android.appfs"

mtd8: 10100000 00020000 "android.datac"

mtd9: 00100000 00010000 "loader"

mtd10: 00060000 00010000 "boot"

mtd11: 00020000 00010000 "env"

mtd12: 00280000 00010000 "extra"

Hypercube root @: ~ #

 

files that appear on the firmware are arranged as follows:

 

folder "su980"

within a folder with "e2" that contains these two files:

 

e2-kernel.bin

e2-rootfs.jffs2

 

Can you give me a hint how to proceed?

 

Thanks

[Satpal]

I made a backup of an OpenPli 3.0 which I had flashed some weeks ago. I'm not sure now which tool I used, "Automatic Full Backup" or "Backupsuite". One is showing in the plugin menu as "Automatic Full Backup/2.2" while the "Backupsuite" is showing as "Voll-Backup auf HDD/USB". In my opinion this caused my problems in the first degree as I wanted to use the backupsuite but apparently used the other tool. I hope you can understand why I was a bit confused by the names of the tools as one just looks very much as if it's just a translated version of the other.

 

Anyway it seems that I used the wrong tool but as I don't really know where else to turn I hope to find some help here.

 

I found a folder "automatic_fullbackup" containing the backup files but when I tried to flash them I noticed that they looked pretty odd to me. There is a file "kernel_cfe_auto.bin" with a size of 230 MB and a "root_cfe_auto.jffs2" with 54 MB.

 

Can those sizes be correct? Is there any way of restoring this image? What might have gone wrong while creating the backup?

[Dimitrij]

Voll-Backup auf HDD/USB=Backupsuite

[Bag58]

@Satpal

Are you sure about the 230 MB? In my full backups, made wit the backup suite the kernel_cfe_auto.bin is only 4 MB! B.t.w. I have a Vu Duo.

[Satpal]

That's my point, 230 MB for the kernel file sounds wrong, even for the root file I would say that's a bit much. The root file with 54 MB sounds about right, but I don't know how to get it back on the box. Would it be possible to just try to add the original kernel file and use the jffs2 that was backed up (maybe renamed to bin)?

[Pedro_Newbie]

Which receiver are you talking about? By any chance a VU Solo2

From which date is your back-up

Which versions of software are you using?

 

If you have a VU+ Solo2 and the backup is made with a version prior January the 17th it could be the case that the wrong mtd was used for the kernel, it has to be mtd2 but in the very first versions for the solo2 the wrong mtd1 was used

Edited by Pedro_Newbie, 23 May 2013 - 19:21.

[Satpal]

Yes, it's a Solo2, sorry I believe I had mentioned it but probably edited it out at some point. The backup was made on May 16th, but as everything is gone now I can't give you too much other information. The Openpli 3.0 was released on Feb 27 2013. The problem is probably caused by the bug you mention.

So there's no way of restoring the image?

[Pedro_Newbie]

You could try to copy the right kernel-image to the root you want to restore but try it at your own risk.

[Satpal]

Yes, I already tried that in the meantime, I just took 3 of the original files, added the root-jffs2 to the folder and renamed it to bin (don't know if that's necessary). Worked like a charm.

So now I can tell you that the program I had used for the back-up was most likely "Automatic Full Backup 2.0".

[rtzhjgg0]

Anyone tested this plugin on Duo2 ?

[Pedro_Newbie]

The BackupSuite is tested on the Duo2 and everything worked fine, also flashing back the image is no problem.

Tested on the original image of VU+

 

This weekend there will be a new version released but the current version will work fine but will show a message that the support for the Duo2 isn't tested but this isn't the case anymore

Edited by Pedro_Newbie, 26 July 2013 - 05:48.

[rtzhjgg0]

Ok - thanks

[Pedro_Newbie]

Here's the new version suitable for Openpli 3.0 and Openpli 4.0

Should be available with the next build.

 

When installing on an Openpli version 3.0 receiver there will be a warning (no error) about an unsatisfied recommandation which can be ignored

Upgrading enigma2-plugin-extensions-backupsuite on root from 12.6 to 12.7...   

enigma2-plugin-extensions-backupsuite: unsatisfied recommendation for mtd-utils-ubifs

This package is required for Openpli 4.0 (and can be ignored for version 3.0)

Attached Files

•  enigma2-plugin-extensions-backupsuite_12.7_mips32el.ipk   42.77KB   46 downloads

Edited by Pedro_Newbie, 13 August 2013 - 18:09.

[rtzhjgg0]

BackupSuite27 results on Duo2+PLi4:
I created a backup of Duo2+PLi4 with your BackupSuite27 on HDD. This worked perfectly. Than flashed this backup with FlashGordon - this too worked perfectly

 

 

Attached Files

•  backupsuite27_pli4duo2_A.jpg   57.72KB   73 downloads
•  backupsuite27_pli4duo2_B.jpg   65.87KB   72 downloads

[Pedro_Newbie]

Another new version

In this version will be shown the root size, kernel size and total size to be backed up. Also is made a prediction about the needed time to complete the back-up. This prediction is made on bases from the last back-up.

At the end of the back-up process the real time will be shown and also the speed in KB/s. This speed is stored and used for the next back-up.

 

The first back-up made with this plugin will be calculated with a default speed of 250KB/s, this is only used on the first back-up, the later back-up will be more accurate calculated (I hope )

Attached Files

•  enigma2-plugin-extensions-backupsuite_12.9_mips32el.ipk   45.68KB   18 downloads

[Pedro_Newbie]

Here's a new version, this contains a little bugfix. On some STB there was an error

 

Attached Files

•  enigma2-plugin-extensions-backupsuite_13.0_mips32el.ipk   46.3KB   48 downloads