Custom / Unofficial Build Open BlackHole 0.6 vuplus-images custom build

[Ten Below]

Not sure if I've found an issue with OBH on my Solo4K, and wondered if it can be checked to see what's going on.

Once you change from the MX_HQ9W skin to any other skin (including <default>), trying to enter Devices Manager via the blue button x 2 gives me a blank screen, and I have to press exit to get back to the menu.

At first I thought it was to do with the s*y skin, but then when I found it doesn't work on default ether, that's got me totally stumped.

You have as this is happening on the VU+Zero as well, other BH skins in the feeds should be ok though. There reason will be that the device manager & probably other screens have not been skinned so cannot display on the sly skins so this will need done in order to fix it.

 

[LandRocket]

I see it now.... line 2798 of skin.xml on the MX_HQ9W mentions a screen called DeliteDevicesPanel, at least I'm 100% sure what's going on now.

Many thanks again

 

[LandRocket]

Is it still the best way to edit the .xml by hand?

This has become too addictive... I've just built the OBH build from the 4.0 branch, and got it to install on my Solo4K (Image 1.0.001). It's got more bugs than a roach hotel (Black Hole apps crashes due to a problem with SoftwareManager.BackupRestore

I've decided I need a proper development environment, parallels on the Mac just doesn't cut it, hey stuff it, it's only money lol.

By the end of the year I might actually use this receiver for viewing something instead of seeing how badly I can mess it up lol....

 

[andrewg]

hi Guys any luck for the vu duo yet?
regards

 

[Ten Below]

hi Guys any luck for the vu duo yet?
regards

Sorry about the wait is it attached to post #1 now for you to test, however is is looking like this build may soon be obsolete due to the release of a new image.

 

[Cookie1953]

I see it now.... line 2798 of skin.xml on the MX_HQ9W mentions a screen called DeliteDevicesPanel, at least I'm 100% sure what's going on now.

Many thanks again

What do I Need to do to get the device manager working on my solo2 using the sky.new (alternative) skin -- or is there another way to mount my USB stick ??? _ Thx

 

[LandRocket]

Seriously, I would switch to the MX_HQ9W skin, use the device manager, then switch back. Once your mountpoints are set, it's not going to be destroyed unless you change devices or have to do a full flash

If you're sadistic, you can use the command line with blkid to get your device IDs and add them to fstab...... if they are initialised they will show up in df as well

nah, switch skins for 2 seconds

-- LR

For reference :

You can see "df -h" shows me /dev/sda1 as 465.6GB, /dev/sdb1 as 28.7GB



blkid tells me:
/dev/sda1: UUID="e86d6654-2c87-4af9-b542-d53fffe2ed85" TYPE="ext4" PARTUUID="60810099-01"
/dev/sdb1: UUID="18645836-399a-4481-9a67-55b1af629241" TYPE="ext4" PARTUUID="3fbc51c6-01"

and fstab:
UUID=e86d6654-2c87-4af9-b542-d53fffe2ed85 /media/hdd auto defaults 0
UUID=18645836-399a-4481-9a67-55b1af629241 /media/usb auto defaults 0

 

[Cookie1953]

Seriously, I would switch to the MX_HQ9W skin, use the device manager, then switch back. Once your mountpoints are set, it's not going to be destroyed unless you change devices or have to do a full flash

If you're sadistic, you can use the command line with blkid to get your device IDs and add them to fstab...... if they are initialised they will show up in df as well

nah, switch skins for 2 seconds

-- LR

For reference :

You can see "df -h" shows me /dev/sda1 as 465.6GB, /dev/sdb1 as 28.7GB

View attachment 15862

blkid tells me:
/dev/sda1: UUID="e86d6654-2c87-4af9-b542-d53fffe2ed85" TYPE="ext4" PARTUUID="60810099-01"
/dev/sdb1: UUID="18645836-399a-4481-9a67-55b1af629241" TYPE="ext4" PARTUUID="3fbc51c6-01"

and fstab:
UUID=e86d6654-2c87-4af9-b542-d53fffe2ed85 /media/hdd auto defaults 0
UUID=18645836-399a-4481-9a67-55b1af629241 /media/usb auto defaults 0

View attachment 15863

Thanks vm -- Worked perfectly swapping skins for a couple of mins, reason I asked was one of your previous posts, #61 threw me - I thought it didn't work in that skin either so didn't try it !!

 

[LandRocket]

No, it actually works in the MX_HQ9W skin, what I didn't realise at the time is that the <default> skin still relies on .xml files and the associated "skin stuff".... the default skin *can* be broken if the files aren't there. I believed because it was <default> it didn't have any dependencies, so it would just work all the time no matter what. I supposed I assumed "<default>" was the equivalent of Safe Mode.... stupid me.

That's what threw me until I actually took the time to take out the spade and start digging

 

[Ten Below]

Just a headsup for anyone using this build, the feeds will be unavailable today but should be restored by evening.

 

[vusolosev2]

Hi,have vu solo se,just wanted to ask if i use this image Open BlackHole 0.6 vuplus-images custom build with IPTV Player hosts configured as per @danny187 guide HERE,then should i use vpn service to watch these iptv channels and other content it has? If yes,then what kind of vpn you reccommend? thank you

 

[danny187]

Hi,have vu solo se,just wanted to ask if i use this image Open BlackHole 0.6 vuplus-images custom build with IPTV Player hosts configured as per @danny187 guide HERE,then should i use vpn service to watch these iptv channels and other content it has? If yes,then what kind of vpn you reccommend? thank you

Its not "torrents" / "p2p" so personally MYSELF I do not use a VPN, however like anything with "protecting" yourself when online its subjective and in my opinion its very individual on if you should or shouldn't.

Best of researching but more into what ones the better and how much they cost etc.

I have used IP vanish (that was good for USA sports, didnt slow speeds before), I now have VPN unlimited but only use for geo content that a dns don't cover, or if I need to view a blocked website.

So I would have a look around/research on them more etc.

 

[vusolosev2]

Strange,after enabling Kodi from OpenBlackhole speedup menu or even after installing it from original OpenBlackhole image plugins menu my vu solo se box wont boot anymore,cant access to box even from telnet. Any ideas? What files to remove to try to reinstall it? Thank you

 

[LandRocket]

I was going to suggest running "opkg --autoremove remove enigma2-plugin-extensions-vuplus-kodi" until I read that you say you can't get access via telnet? Have you tried SSH? I've been messing around with my own compiled versions of OpenBH/ATV/VIX and as yet, I've not managed to kill command line access.... you say "What files to remove to try to reinstall it?" so I'm just wondering what you *can* get to?

Sorry I can't be of more assistance at this time Still got my 'L' plates

 

[vusolosev2]

Trying to acess with winscp and with PuTTY,but nothing,no response from box,everything worked ok,but after installed Kodi and rebooted it wont boot anymore. Tried re image couple of times already,but nothing so far,have no idea what causes it.

 

[LandRocket]

OK, I just had the impression you had *some* sort of access.... based on what you've told me I can only go with the following ideas:

1) Ensure that all HDD/USB media is removed from the box, set up a USB stick with original VU+ flash files, to see if you regain access. If this fails:
A) Your box has been flashed to the point where there are no longer any "good" blocks left on the flash memory. I would say highly unlikely, considering the fact that my box is well over a year old and I don't think I keep the software on it for more than 12 hours
B) Box could be a "clone"? A lot of plugins just need high-level access (for example CrossEPG even with OpenTV just asks the box to tune into a channel, reads the data, and stores it) whereas Kodi needs low-level access (it needs to be able to access drivers, even on install it mentions about doing something to bluetooth) so it could be that when you install Kodi, it needs access to hardware that it can't find because it's not a genuine box.

I know this is probably not what you want to hear, but I seriously can't see any other reasons Based on the fact you have *no* access at all, at the minute you have a very expensive paper weight so don't really have a lot to lose.

I don't think you specified exactly which VU box you have, but my Solo 4K has an RS232 jack on the back (easily confused for a telephone port) so that really would be the only other option to talk to the box without networking capability.

 

[vusolosev2]

1)I have usb Turbo tuner on usb port on it.
A)I dont believe it also,because it boots fine after new flash,it only fails after installing Kodi.
B)Also not possible,bought it from hm-sat
Box model is Vu+ solo se v2

Also first post says After updating you should be able to install Kodi 17.0 RC4 (Listed as vuplus-kodi 17.0)
Solo2 is tested & working other models please let us know how you get on..
Installed all updates,but my solo se box wont boot now even past splash screen

 

[LandRocket]

Ahh, OK so you can reflash then? That's cool

I don't own that specific box, so unable to test I did start having a look at

Please, Log in or Register to view URLs content!

and I see that there is the VU Solo2, SoloSE and SoloSEv2. The main difference I can see is that the SoloSEv2 has 512MB Flash, whereas the Solo2 and SoloSE only have 256MB Flash....

So AFAIK I don't think the image has been tested on a SoloSEv2, but I am pretty certain the resident madman who puts all this stuff together (Ten Below) will be able to give you better advice than I can

 

[vusolosev2]

Anyway re flashed again with danny187 OpenPli 5.0 w/Kodi:ServiceApp:IptvPlayer-pre config: Updated,and everything is working fine,too bad i cant use OpenBlackhole with Kodi

 

[Ten Below]

So AFAIK I don't think the image has been tested on a SoloSEv2, but I am pretty certain the resident madman who puts all this stuff together (Ten Below) will be able to give you better advice than I can

Better advice im not sure about that lol much of this is new to me as well , it was tested on the Solose but at the time the version on the feeds was 17.0 rc1 so could well be an issue with the later kodi version which was not tested.

Anyway re flashed again with danny187 OpenPli 5.0 w/Kodi:ServiceApp:IptvPlayer-pre config: Updated,and everything is working fine,too bad i cant use OpenBlackhole with Kodi

Glad to hear you found another with kodi working for you & sorry to hear about the problems you had with this build, the person who did test the solose builds has upgraded his box so can no longer test. There is a new OBH build with kodi 17.0 final in the feeds on the way so if you have not been put off & ever have some spare time to test another any help you can offer would be much appreciated.

 

[Ten Below]

Not sure if I've found an issue with OBH on my Solo4K, and wondered if it can be checked to see what's going on.

Once you change from the MX_HQ9W skin to any other skin (including <default>), trying to enter Devices Manager via the blue button x 2 gives me a blank screen, and I have to press exit to get back to the menu.

At first I thought it was to do with the s*y skin, but then when I found it doesn't work on default ether, that's got me totally stumped.

You have as this is happening on the VU+Zero as well, other BH skins in the feeds should be ok though. There reason will be that the device manager & probably other screens have not been skinned so cannot display on the sly skins so this will need done in order to fix it.

 

[LandRocket]

I see it now.... line 2798 of skin.xml on the MX_HQ9W mentions a screen called DeliteDevicesPanel, at least I'm 100% sure what's going on now.

Many thanks again

 

[LandRocket]

Is it still the best way to edit the .xml by hand?

This has become too addictive... I've just built the OBH build from the 4.0 branch, and got it to install on my Solo4K (Image 1.0.001). It's got more bugs than a roach hotel (Black Hole apps crashes due to a problem with SoftwareManager.BackupRestore

I've decided I need a proper development environment, parallels on the Mac just doesn't cut it, hey stuff it, it's only money lol.

By the end of the year I might actually use this receiver for viewing something instead of seeing how badly I can mess it up lol....

 

[andrewg]

hi Guys any luck for the vu duo yet?
regards

 

[Ten Below]

hi Guys any luck for the vu duo yet?
regards

Sorry about the wait is it attached to post #1 now for you to test, however is is looking like this build may soon be obsolete due to the release of a new image.

 

[Cookie1953]

I see it now.... line 2798 of skin.xml on the MX_HQ9W mentions a screen called DeliteDevicesPanel, at least I'm 100% sure what's going on now.

Many thanks again

What do I Need to do to get the device manager working on my solo2 using the sky.new (alternative) skin -- or is there another way to mount my USB stick ??? _ Thx

 

[LandRocket]

Seriously, I would switch to the MX_HQ9W skin, use the device manager, then switch back. Once your mountpoints are set, it's not going to be destroyed unless you change devices or have to do a full flash

If you're sadistic, you can use the command line with blkid to get your device IDs and add them to fstab...... if they are initialised they will show up in df as well

nah, switch skins for 2 seconds

-- LR

For reference :

You can see "df -h" shows me /dev/sda1 as 465.6GB, /dev/sdb1 as 28.7GB



blkid tells me:
/dev/sda1: UUID="e86d6654-2c87-4af9-b542-d53fffe2ed85" TYPE="ext4" PARTUUID="60810099-01"
/dev/sdb1: UUID="18645836-399a-4481-9a67-55b1af629241" TYPE="ext4" PARTUUID="3fbc51c6-01"

and fstab:
UUID=e86d6654-2c87-4af9-b542-d53fffe2ed85 /media/hdd auto defaults 0
UUID=18645836-399a-4481-9a67-55b1af629241 /media/usb auto defaults 0

 

[Cookie1953]

Seriously, I would switch to the MX_HQ9W skin, use the device manager, then switch back. Once your mountpoints are set, it's not going to be destroyed unless you change devices or have to do a full flash

If you're sadistic, you can use the command line with blkid to get your device IDs and add them to fstab...... if they are initialised they will show up in df as well

nah, switch skins for 2 seconds

-- LR

For reference :

You can see "df -h" shows me /dev/sda1 as 465.6GB, /dev/sdb1 as 28.7GB

View attachment 15862

blkid tells me:
/dev/sda1: UUID="e86d6654-2c87-4af9-b542-d53fffe2ed85" TYPE="ext4" PARTUUID="60810099-01"
/dev/sdb1: UUID="18645836-399a-4481-9a67-55b1af629241" TYPE="ext4" PARTUUID="3fbc51c6-01"

and fstab:
UUID=e86d6654-2c87-4af9-b542-d53fffe2ed85 /media/hdd auto defaults 0
UUID=18645836-399a-4481-9a67-55b1af629241 /media/usb auto defaults 0

View attachment 15863

Thanks vm -- Worked perfectly swapping skins for a couple of mins, reason I asked was one of your previous posts, #61 threw me - I thought it didn't work in that skin either so didn't try it !!

 

[LandRocket]

No, it actually works in the MX_HQ9W skin, what I didn't realise at the time is that the <default> skin still relies on .xml files and the associated "skin stuff".... the default skin *can* be broken if the files aren't there. I believed because it was <default> it didn't have any dependencies, so it would just work all the time no matter what. I supposed I assumed "<default>" was the equivalent of Safe Mode.... stupid me.

That's what threw me until I actually took the time to take out the spade and start digging

 

[Ten Below]

Just a headsup for anyone using this build, the feeds will be unavailable today but should be restored by evening.

 

[vusolosev2]

Hi,have vu solo se,just wanted to ask if i use this image Open BlackHole 0.6 vuplus-images custom build with IPTV Player hosts configured as per @danny187 guide HERE,then should i use vpn service to watch these iptv channels and other content it has? If yes,then what kind of vpn you reccommend? thank you

 

[danny187]

Hi,have vu solo se,just wanted to ask if i use this image Open BlackHole 0.6 vuplus-images custom build with IPTV Player hosts configured as per @danny187 guide HERE,then should i use vpn service to watch these iptv channels and other content it has? If yes,then what kind of vpn you reccommend? thank you

Its not "torrents" / "p2p" so personally MYSELF I do not use a VPN, however like anything with "protecting" yourself when online its subjective and in my opinion its very individual on if you should or shouldn't.

Best of researching but more into what ones the better and how much they cost etc.

I have used IP vanish (that was good for USA sports, didnt slow speeds before), I now have VPN unlimited but only use for geo content that a dns don't cover, or if I need to view a blocked website.

So I would have a look around/research on them more etc.

 

[vusolosev2]

Strange,after enabling Kodi from OpenBlackhole speedup menu or even after installing it from original OpenBlackhole image plugins menu my vu solo se box wont boot anymore,cant access to box even from telnet. Any ideas? What files to remove to try to reinstall it? Thank you

 

[LandRocket]

I was going to suggest running "opkg --autoremove remove enigma2-plugin-extensions-vuplus-kodi" until I read that you say you can't get access via telnet? Have you tried SSH? I've been messing around with my own compiled versions of OpenBH/ATV/VIX and as yet, I've not managed to kill command line access.... you say "What files to remove to try to reinstall it?" so I'm just wondering what you *can* get to?

Sorry I can't be of more assistance at this time Still got my 'L' plates

 

[vusolosev2]

Trying to acess with winscp and with PuTTY,but nothing,no response from box,everything worked ok,but after installed Kodi and rebooted it wont boot anymore. Tried re image couple of times already,but nothing so far,have no idea what causes it.

 

[LandRocket]

OK, I just had the impression you had *some* sort of access.... based on what you've told me I can only go with the following ideas:

1) Ensure that all HDD/USB media is removed from the box, set up a USB stick with original VU+ flash files, to see if you regain access. If this fails:
A) Your box has been flashed to the point where there are no longer any "good" blocks left on the flash memory. I would say highly unlikely, considering the fact that my box is well over a year old and I don't think I keep the software on it for more than 12 hours
B) Box could be a "clone"? A lot of plugins just need high-level access (for example CrossEPG even with OpenTV just asks the box to tune into a channel, reads the data, and stores it) whereas Kodi needs low-level access (it needs to be able to access drivers, even on install it mentions about doing something to bluetooth) so it could be that when you install Kodi, it needs access to hardware that it can't find because it's not a genuine box.

I know this is probably not what you want to hear, but I seriously can't see any other reasons Based on the fact you have *no* access at all, at the minute you have a very expensive paper weight so don't really have a lot to lose.

I don't think you specified exactly which VU box you have, but my Solo 4K has an RS232 jack on the back (easily confused for a telephone port) so that really would be the only other option to talk to the box without networking capability.

 

[vusolosev2]

1)I have usb Turbo tuner on usb port on it.
A)I dont believe it also,because it boots fine after new flash,it only fails after installing Kodi.
B)Also not possible,bought it from hm-sat
Box model is Vu+ solo se v2

Also first post says After updating you should be able to install Kodi 17.0 RC4 (Listed as vuplus-kodi 17.0)
Solo2 is tested & working other models please let us know how you get on..
Installed all updates,but my solo se box wont boot now even past splash screen

 

[LandRocket]

Ahh, OK so you can reflash then? That's cool

I don't own that specific box, so unable to test I did start having a look at

Please, Log in or Register to view URLs content!

and I see that there is the VU Solo2, SoloSE and SoloSEv2. The main difference I can see is that the SoloSEv2 has 512MB Flash, whereas the Solo2 and SoloSE only have 256MB Flash....

So AFAIK I don't think the image has been tested on a SoloSEv2, but I am pretty certain the resident madman who puts all this stuff together (Ten Below) will be able to give you better advice than I can

 

[vusolosev2]

Anyway re flashed again with danny187 OpenPli 5.0 w/Kodi:ServiceApp:IptvPlayer-pre config: Updated,and everything is working fine,too bad i cant use OpenBlackhole with Kodi

 

[Ten Below]

So AFAIK I don't think the image has been tested on a SoloSEv2, but I am pretty certain the resident madman who puts all this stuff together (Ten Below) will be able to give you better advice than I can

Better advice im not sure about that lol much of this is new to me as well , it was tested on the Solose but at the time the version on the feeds was 17.0 rc1 so could well be an issue with the later kodi version which was not tested.

Anyway re flashed again with danny187 OpenPli 5.0 w/Kodi:ServiceApp:IptvPlayer-pre config: Updated,and everything is working fine,too bad i cant use OpenBlackhole with Kodi

Glad to hear you found another with kodi working for you & sorry to hear about the problems you had with this build, the person who did test the solose builds has upgraded his box so can no longer test. There is a new OBH build with kodi 17.0 final in the feeds on the way so if you have not been put off & ever have some spare time to test another any help you can offer would be much appreciated.