83 replies to this topic

[littlesat]

Everyone can modify startup files... and add stuff.... there is only no enigma2 user interface yet that adds slots for sd card, usb, or harddisk.... since we para the Startup files multiboot is ‘universal’
But it is still special a plugin in android creates an extra slot....

Edited by littlesat, 8 January 2021 - 23:23.

[cobus]

I look for an answer and i found this site from HDF.  (google translating)

 

 

Hello everybody

I bought a Maxytec Multibox 4K. This was delivered with an OpenPli image (slot 5).
Flashing the HDF image (slot 1-4) of the Anadol Multibox 4K works flawlessly and runs great.

Well my problem.
If Android has been started and I want to go back to Linux, this is possible with the Android app "TransE2", but only in the OpenPli image in slot 5.
I cannot find a selection / setting in the TranE2 app for starting in another slot.
An update of the image in slot 5 is also not possible, since then only an update is offered in slots 1-4.

Now the image in slot 5 was accidentally deleted. I suspect slot 5 is the flash memory.

Now my question to you: Is it possible to flash an image in slot 5, or is there a possibility to reset the receiver to the delivery state?
I have already started several searches in this direction but unfortunately found nothing.

Thank you in advance for your replies.

 

 

and the answer is.

 

 

TransE2 only works with slot 5, if the image (slot 5) is deleted, it can no longer be used. It's actually a bug in the TransE2 app because it doesn't access the other slots. And if you do a factory setting, slot 5 does not come back.

I would never activate Android !! Can not be deactivated anymore and is not good.

 

How can i update the slot 5 image (with Telnet) to Openpli 8 release ?

Edited by cobus, 9 January 2021 - 15:24.

[littlesat]

I'm afraid not... Android's TransE2 app needs an update so you can select here from the orriginal 4 slots...

[cobus]

Jammer ik had gehoopt dat dat kon dan is deze image ook uptodate.

 

Too bad I had hoped that was possible, then this image is also up to date.

Edited by Frenske, 9 January 2021 - 17:14.
Please use English overhere.

[littlesat]

Kan je de inhoud van die slot 5 file eens tonen? Als je mount via het cat commando? dat weten we ook beter wat die doet... Doe de STARTUP_1 t/m 4 er ook maar bij...

 

Can you show the contents of that slot 5 file? If you mount via the cat command? We also know better what it does ... Add the STARTUP_1 to 4 as well ...

Edited by Frenske, 9 January 2021 - 17:15.
Please only use English in this section.

[Dorfkind]

I don´t understand nothing...

[littlesat]

Sorry we were hooked back into dutch.... in short it seems the android plugin creates the 5th slot... I asked for the content (cat) of all the setup files and it seems the android plugin need a fix.

@Frenske thanks for the translation!!!

Edited by littlesat, 9 January 2021 - 17:31.

[cobus]

Oh sorry !!

[cobus]

Look here.

openpli 8.0-release multibox

multibox login: root
root@multibox:~# cd /tmp
root@multibox:/tmp# mkdir b
root@multibox:/tmp# mount /dev/block/by-name/bootoptions /tmp/b
root@multibox:/tmp# ls -la /tmp/b
drwxr-xr-x    2 root     root         16384 Jan  1  1970 .
drwxrwxrwt    3 root     root           140 Jan  9 17:49 ..
-rwxr-xr-x    1 root     root           225 Jan  9 17:48 STARTUP
-rwxr-xr-x    1 root     root           136 Jul 11  2019 STARTUP_ANDROID
-rwxr-xr-x    1 root     root           136 Jul 11  2019 STARTUP_ANDROID_DISABLE_LINUXSE
-rwxr-xr-x    1 root     root           225 Jul 11  2019 STARTUP_LINUX_1
-rwxr-xr-x    1 root     root           225 Jul 11  2019 STARTUP_LINUX_2
-rwxr-xr-x    1 root     root           225 Jul 11  2019 STARTUP_LINUX_3
-rwxr-xr-x    1 root     root           225 Jul 11  2019 STARTUP_LINUX_4
-rwxr-xr-x    1 root     root           225 Jul 11  2019 STARTUP_LINUX_5
-rwxr-xr-x    1 root     root             0 Jan  1  1980 STARTUP_ONCE
-rwxr-xr-x    1 root     root            96 Jul 11  2019 STARTUP_RECOVERY
-rwxr-xr-x    1 root     root           141 Jan  1  1980 bootmenu.conf
root@multibox:/tmp# cat /tmp/b/STARTUP_LINUX_5
bootcmd=setenv bootargs $(bootargs) $(bootargs_common); mmc read 0 0x1000000 0x3BD000 0x8000; bootm 0x1000000; run bootcmd_fallback
bootargs=root=/dev/mmcblk0p15 rootsubdir=linuxrootfs5 rootfstype=ext4 kernel=/dev/mmcblk0p19
root@multibox:/tmp# cat /tmp/b/STARTUP_LINUX_1
bootcmd=setenv bootargs $(bootargs) $(bootargs_common); mmc read 0 0x1000000 0x3BD000 0x8000; bootm 0x1000000; run bootcmd_fallback
bootargs=root=/dev/mmcblk0p23 rootsubdir=linuxrootfs1 rootfstype=ext4 kernel=/dev/mmcblk0p19
root@multibox:/tmp# cat /tmp/b/STARTUP_LINUX_2
bootcmd=setenv bootargs $(bootargs) $(bootargs_common); mmc read 0 0x1000000 0x3C5000 0x8000; bootm 0x1000000; run bootcmd_fallback
bootargs=root=/dev/mmcblk0p23 rootsubdir=linuxrootfs2 rootfstype=ext4 kernel=/dev/mmcblk0p20
root@multibox:/tmp# cat /tmp/b/STARTUP_LINUX_3
bootcmd=setenv bootargs $(bootargs) $(bootargs_common); mmc read 0 0x1000000 0x3CD000 0x8000; bootm 0x1000000; run bootcmd_fallback
bootargs=root=/dev/mmcblk0p23 rootsubdir=linuxrootfs3 rootfstype=ext4 kernel=/dev/mmcblk0p21
root@multibox:/tmp# cat /tmp/b/STARTUP_LINUX_4
bootcmd=setenv bootargs $(bootargs) $(bootargs_common); mmc read 0 0x1000000 0x3D5000 0x8000; bootm 0x1000000; run bootcmd_fallback
bootargs=root=/dev/mmcblk0p23 rootsubdir=linuxrootfs4 rootfstype=ext4 kernel=/dev/mmcblk0p22
root@multibox:/tmp#

Edited by cobus, 9 January 2021 - 17:56.

[cobus]

kernel from slot 1, but slot 1 i have deleted the image

[littlesat]

When you delete an image it does actualy not delete it... I just renames the enigma2 binary.... a removed image can also be undone!

[cobus]

Thanks for this answer.

[cobus]

Image delete in the recovery not on the image.

[Aliraza63]

A question is here 

Does the loader knows about the multiboot table ?

because as you  have lost the startup 5 it shows to me there is no any emergency switchover one to another slot , 

if its true then its only the loader can do this . 

[cobus]

Sorry i dont no.

[Aliraza63]

Sorry i dont no.

Its ok.. actually I dont have this box . according to information/logs  you have shared I have observed the slot 5 partition  is just software base its not boot loader base . that's is the only reason after delete or reset you dont see it there .

Edited by Aliraza63, 11 January 2021 - 09:18.

[cobus]

I have now sold the box so it is no longer necessary.

 

Thanks for all the answers    and time to spend with this issue

[Dorfkind]

Poor buyer of the box

[cobus]

[Dorfkind]

What did you bought instead?

And adjust your signature