HowTo Vu+ Multiboot in OpenBh 5.2

I made a simple image selector for older images
this time for
VTI 15.0.x and Pure2 6.5
Just two files in my zip for VTI 15.0.x and two files in my zip for Pure2 6.5
You will not get the names of the images, only the Slot numbers 1.2.3,4,5,6,7,8 and the Recovery image.
Copy menu.xml to /usr/share/enigma2/
(make a backup of the old one just in case)
and copy RecoveryStart.pyo to /usr/lib/enigma2/python/Screens/
Do not forget
Restart enigma2
Now you have in Standby/restart Menu ,image/slot selector for 8 slots/images.
===================================================
The same for OpenBlackHole 4.4 and Black Hole 3.1.0

Here


How to install flash and other new py3 images
(For Egami10.3 you can use the same method/Multiboot file as for OpenATV)
Here



shot1.jpg


shot3.jpg




shot2.jpg
 

Attachments

Last edited:
installed in vu+ uno4k in few minutes and running perfectly:
1. obh 5.2
2. openatv 7.2
3. openpli 8.3
recovery mode

thx a lot oft!
 
skier said:
VU+Solo4K installed and running images

Installs but stays on boot
openpli-8.3
BlackHole-3.1.0
VTi_15-0-02
View attachment 3732
Click to expand...

You probably meant Pli image, which means you didn't read the instructions for Pli image.

HowTo Vu+ Multiboot in OpenBh 5.2

It is highly recommended to install OpenBh 5.2 onto your Vu+ 4K box, and just setup the basic features (image resolution, network connection and set a password in telnet etc, you do not need to setup tuners as they will not be used) but not to install ANYTHING else into the image as it is best...
board.openbh.net board.openbh.net
 
Matrix10 said:
I made a simple image selector for older images
this time for
VTI 15.0.x and Pure2 6.5
Just two files in my zip for VTI 15.0.x and two files in my zip for Pure2 6.5
You will not get the names of the images, only the Slot numbers 1.2.3,4,5,6,7,8 and the Recovery image.
Copy menu.xml to /usr/share/enigma2/
(make a backup of the old one just in case)
and copy RecoveryStart.pyo to /usr/lib/enigma2/python/Screens/
Do not forget
Restart enigma2
Now you have in Standby/restart Menu ,image/slot selector for 8 slots/images.
===================================================
The same for OpenBlackHole 4.4 and Black Hole 3.1.0

Here


How to install flash and other new py3 images

Here



View attachment 3727


View attachment 3728




View attachment 3729
Click to expand...

thanks bro
The egami10.3rx image has been modified to the same addition to the open atv image. Are there any additions to the rest of the images?
 
I have 2 box uno4kse & duo4kse
for openatv 6.4 woking good, multiboot image selector on uno4kse exist. but no selector on duo4kse
con you advice
 
Matrix10 said:
I made a simple image selector for older images
this time for
VTI 15.0.x and Pure2 6.5
Just two files in my zip for VTI 15.0.x and two files in my zip for Pure2 6.5
You will not get the names of the images, only the Slot numbers 1.2.3,4,5,6,7,8 and the Recovery image.
Copy menu.xml to /usr/share/enigma2/
(make a backup of the old one just in case)
and copy RecoveryStart.pyo to /usr/lib/enigma2/python/Screens/
Do not forget
Restart enigma2
Now you have in Standby/restart Menu ,image/slot selector for 8 slots/images.
===================================================
The same for OpenBlackHole 4.4 and Black Hole 3.1.0

Here


How to install flash and other new py3 images
(For Egami10.3 you can use the same method/Multiboot file as for OpenATV)
Here



View attachment 3727


View attachment 3728




View attachment 3729
Click to expand...
The names of the images did not appear
dreamDroid_1678131121150.jpgdreamDroid_1678131007089_edit_31143785672851.jpg
 
haitham said:
The names of the images did not appear
View attachment 3734View attachment 3735
Click to expand...


In order for image names to appear, you must change the name in menu.xml instead of Start image slot 1, write Start image and then the image name.

</code>
</item>
<item weight="0" level="0" text="Start image OpenBh 5.2" entryID="start1">
<code>
from Screens.RecoveryStart import RecoveryStart
def msgClosed(ret):
if ret:
from os import system, _exit
system("cp /boot/STARTUP_1 /boot/STARTUP")
system("reboot")
_exit(0)
self.session.openWithCallback(msgClosed, RecoveryStart)
 

Attachments

  • 1_0_1_3E9_F01_22B0_EEEE0000_0_0_0_20230307051917.jpg
    1_0_1_3E9_F01_22B0_EEEE0000_0_0_0_20230307051917.jpg
    249.7 KB · Views: 43
Matrix10 said:
What is written in my information text ?
Click to expand...
djuro1 said:
In order for image names to appear, you must change the name in menu.xml instead of Start image slot 1, write Start image and then the image name.

</code>
</item>
<item weight="0" level="0" text="Start image OpenBh 5.2" entryID="start1">
<code>
from Screens.RecoveryStart import RecoveryStart
def msgClosed(ret):
if ret:
from os import system, _exit
system("cp /boot/STARTUP_1 /boot/STARTUP")
system("reboot")
_exit(0)
self.session.openWithCallback(msgClosed, RecoveryStart)
Click to expand...
thanks
Wasn't this done automatically, as in the rest of the pictures
 
haitham said:
thanks
Wasn't this done automatically, as in the rest of the pictures
Click to expand...
It's not done automatically, those teams have to go in their image for it to show automatically, but that's why Matrix10 made a simple image selector by slots for images that don't show Multiboot image selector
 
valery84 said:
Is there any workaround for use internal ssd to install and use images?
Click to expand...

For sure, it will work.

Make 2 partitions on your SSD, where one is mapped to handle recordings (for example):

Code: 
/media/hdd

and other mapped as:

Code: 
/media/usb

to handle the images for multiboot purposes ( working like an USB device ( pen )), as also "picons" or anything you want to handle there!

best regards
nunigaia

Note:

Not tested, but it should work! ;) In any case, it is more simple to remove an USB device if something was wrong, then remove an Internal SSD HDD, if needed!
 
Last edited:
Thank you, but this doesn't work. I already have a 32GB partition on SSD formatted as ext4 and mounted as /media/usb, but it is not possible to use it for multiboot. I have to put in an usb pen. I know that the usb pen is more manageable then an internal SSD, but it's much faster in all operations...
 
haitham said:
Yes, me too. It didn't work for me. We hope to find a solution to that with Hard hdd&ssd
Click to expand...
There is a solution, remove all usb, go to slot 0-RecoveryStart, after that do the initialization ssd disk and the possibility to add slots from 4 to 7 will appear, after that there will be no more possibility to add slots, but you can add it manually in the receiver slot 8 and so on further.
Tested to work
 
You must log in or register to reply here.
Back
Top