Open Black Hole 0.1 update 06-06-2015 Vu+ Duo

Ev0

Ev0

Admin
Open Black Hole 0.1

0-jpg.jpg

​
Whats New:
  • Open Black Hole now includes OpenMultiBoot patched by Meo.

Main Features:
  • Full Hd skin (1920x1080)
  • HbbTv
  • Open GLes animations (Duo2, Solo2, SoloSE)
  • Xbmc (Duo2, Solo2, SoloSE)

Black Hole:
  • Blue panel
  • Green Panel
  • Extra Settings
  • Addons panel
  • Compatible with Pli plugins and Skins

*** WARNING *** If you have used Open Multiboot previously, you must remove all folders and files from your Usb and Hdd devices before you use this patched version.​

What is Open Multiboot ?​

OpenMultiBoot is a newer and more advanced version of Meoboot.

It does not mix drivers and kernels so you can run any Vu+ image, and even use the online update function for that image, without the risk of corrupting the multiboot image or the main image in flash.


With OpenMultiBoot you can have Open Black Hole in flash and classic Black Hole in multiboot.


OpenMultiboot has been tested and is working with the following images:
- Open Black Hole
- Black Hole 2.1.6.1
- OpenPli
- OpenAtv
- OpenVix
- Vti
- Vu+ original
​
What is Open Black Hole ?

It is an exciting new project from the same team that produce the Black Hole images.

This new project is based on the PLi git and coding infrastructure, which means it is not only Open Source, but it is also compatible with all PLi plugins, feeds and skins and it also features full online update support (for those users that do not like having to do a full reflash everytime there is an image update). We have just given it the Black Hole touch.

This means it has the Green Panel and Blue Panels as found in the standard Black Hole images, we have also added the Black Hole addons panel and included Full HD skin support, OpenGLes Animations and of course included Xbmc .

As with the standard Black Hole images, we continue to support Genuine Vu+ Boxes only and therefore our images are optimised for Vu+ boxes and will only work on these models (any Open Black Hole, or Black Hole images you see on the internet for other box models or clone models are not official images and we offer no support for those boxes or images).


Do I have to upgrade to this new Open Black Hole image ?

No you don't have to upgrade to the new Open Black Hole image, this image is completely separate from the original Black Hole image, this is simply a new image so we can offer our users more choice, if you are happy with your current image, then you can continue to use that image, if you want to try the new Open Black Hole image then you can do so.


What about the Black Hole and Black Hole Prism Images ?

For those of you worried about the standard Black Hole and Prismcube image, please don’t worry, we remain committed to the standard Black Hole and Black Hole Prism images and image updates will continue as normal, this new Open Black Hole image is an additional project and we are fully committed to all images.

Where can I find the Open Black Hole git ?

The Open Black Hole git is located here: http://git.vuplus-community.net

1-jpg.jpg

2-jpg.jpg

3-jpg.jpg

4-jpg.jpg

5-jpg.jpg

6-jpg.jpg

7-jpg.jpg

8-jpg.jpg

DISCLAIMER​


THE OPEN BLACK HOLE IMAGE DOES NOT CONTAIN ANY EMULATOR, K E Y S, SOFTCAMS OR OTHER SYSTEM FOR VIEWING PAY - TV WITH OR WITHOUT A PAID SUBSCRIPTION.​


THE OPEN BLACK HOLE IMAGE DOES NOT CONTAIN ANY SYSTEM TO DOWNLOAD PLUGINS OR EMULATORS FROM EXTERNAL SERVERS OR SOFTWARE THAT MAY BE USED FOR ILLEGAL PURPOSES SUCH AS CARD SHARING.​
 

Attachments

hello,

rn formatted usb ext 4 when I try to install open multiboot usb green screen. a thank you idea.
 
extrait crash log :

File "/usr/lib/enigma2/python/mytest.py", line 196, in processDelay
callback(*retval)
File "/usr/lib/enigma2/python/Plugins/Extensions/OpenMultiboot/OMBManager.py", line 118, in initCallback
File "/usr/lib/enigma2/python/Plugins/Extensions/OpenMultiboot/OMBManager.py", line 57, in getFSType
File "/usr/lib/python2.7/os.py", line 707, in popen4
ImportError: No module named subprocess
< 77.977458> [ePyObject] (CallObject(<bound method Session.processDelay of <__main__.Session instance at 0x1d195d0>>,()) failed)
]]>
</enigma2crashlog>
</crashlogs>
</openpli>
 
gecko said:
extrait crash log :

File "/usr/lib/enigma2/python/mytest.py", line 196, in processDelay
callback(*retval)
File "/usr/lib/enigma2/python/Plugins/Extensions/OpenMultiboot/OMBManager.py", line 118, in initCallback
File "/usr/lib/enigma2/python/Plugins/Extensions/OpenMultiboot/OMBManager.py", line 57, in getFSType
File "/usr/lib/python2.7/os.py", line 707, in popen4
ImportError: No module named subprocess
< 77.977458> [ePyObject] (CallObject(<bound method Session.processDelay of <__main__.Session instance at 0x1d195d0>>,()) failed)
]]>
</enigma2crashlog>
</crashlogs>
</openpli>
Click to expand...

I will report this to the coders, but for a fix, if you log into telnet then type

opkg update (press enter)
then type
opkg install python-subprocess (press enter again)

it should install the missing files and then it will work for you
 
Ev0 said:
I will report this to the coders, but for a fix, if you log into telnet then type

opkg update (press enter)
then type
opkg install python-subprocess (press enter again)

it should install the missing files and then it will work for you
Click to expand...

thanks. it's ok for multiboot.
 
What is the difference from patched openMultiboot in openBlackhole an Standard openmultiboot in openATV and Alliance Images?
 
humiboy said:
What is the difference from patched openMultiboot in openBlackhole an Standard openmultiboot in openATV and Alliance Images?
Click to expand...

Think they are similar, but patched ( adapted ) for making it work with OBH in flash and multiboot other images like, BH, OpenPli, OpenAtv, Vix, etc ...

best regards
nunigaia
 
I have testet it and with openBlackhole takes an installation to usb about 15 minutes. With openATV Images takes an installation to usb about 30 minutes.
 
gecko said:
thanks. it's ok for multiboot.
Click to expand...
hello,

new problem: OpenPLi in multiboot started and it can be configured, settings etc. by cons, if you go to menu / parameters / .screen green and crash restarts.
no way to recover crash log via FTP / media / nothing ????
I can not find the way to set up assembly / disassembly peripherals.
just for info, for your developers.
thank you for everything, if need tests do not hesitate.
 
gecko said:
hello,

new problem: OpenPLi in multiboot started and it can be configured, settings etc. by cons, if you go to menu / parameters / .screen green and crash restarts.
no way to recover crash log via FTP / media / nothing ????
I can not find the way to set up assembly / disassembly peripherals.
just for info, for your developers.
thank you for everything, if need tests do not hesitate.
Click to expand...
What is the actual problem you are having ?

OpenPLi 4.0 is working in OpenMultiboot for me.
 
Ev0 said:
What is the actual problem you are having ?

OpenPLi 4.0 is working in OpenMultiboot for me.
Click to expand...
hello,

OpenPLi 4.0 is working in OpenMultiboot for me too, but if I go to menu / parametrer / green screen crash.
thank you
 
hello,

after update of the day, my flash openblackhole is blocked on screen >>> boot booting writing, no hourglass nothing. I tried to restart with button on / off and also stops here.
I will reflash openblackhole 0.1.
I can not tell you what caused this, just update the day before I'd had a problem with crossepg but nothing serious and I had nothing n installed or modified.
 
@ Flash and updating done everything works.
I think the flash image was corrupt, given the concerns posted (read my previous posts).
I 'd made a backup stored on my hard drive, as the flash image does not boot it m have been for nothing.

Dormir.gif
 
You must log in or register to reply here.
Back
Top