VU+ Solo2 Daily clone safe images (All clones)

SpaceRat

DW Member
Joined
Feb 25, 2015
Messages
32
Imagesammlung für die Solo² Clones
Collection of images for Solo² clones


All images are designed to be safe for online updates, but you do that on your own risk!

Wichtig ist, dass Ihr nur Images flasht, die für Eure Boxversion geeignet sind.
It's important to only flash images suitable for your box variant!



Unterstützte/Supported Images:
(In alphabetischer Reihenfolge/In alphabetical order)

OpenATV 5.3 (Nightly)

Dragonworth / Lonrisun / Sunray



---


OpenATV closed beta (Nightly)
Dragonworth / Lonrisun / Sunray
Links zeigen auf OpenATV 5.3!
Was Ihr an der URL verändern müßt und das Passwort müßt Ihr selber rausfinden. URL ist offensichtlich, wenn Ihr die Version der closed beta wißt und das Passwort wissen die Beta-Tester.



Links pointing at OpenATV 5.3!
You need to find out yourself what to change within the URL and the password. URL change is obvious as long as you know what version the new beta has and real beta testers will know the password.

---

OpenBH 0.6 (Open Black Hole)
Dragonworth / Lonrisun / Sunray
Funktion auf Dragonworth und Lonrisun ungetestet. Kann sein, daß es nicht wirklich geht, weil mit Kodi/xbmc verheiratet.
Functionality on Dragonworth and Lonrisun untested. It could be it doesn't work, as OpenBH heavily relies on Kodi/xbmc.



---


OpenDroid 5.5
Dragonworth / Lonrisun / Sunray



---


OpenHDF 5.5 (Nightly)

Dragonworth / Lonrisun / Sunray


---


OpenPLi 4.0 (Nightly)
Lonrisun / Sunray


---


OpenSPA 6.0

Lonrisun / Sunray


---


OpenViX 4.2

Dragonworth / Lonrisun / Sunray


---

VTi 11.0.0
Lonrisun / Sunray

Warnung!
VTi baut immer wieder Clone-Erkennungen samt Komplett-Lösch-Routine in seine Images ein.
Dementsprechend riskiert Ihr bei einem Online-Update oder auch bei Nachinstallationen vom Feed den Verlust aller Aufnahmen und Einstellungen!
VTi ist das riskanteste Image für Eure Clones!


Warning!
VTi keeps implementing clone detection incl. "wipe all" routines in their images.
You risk losing all recordings and settings on each online update and plugin installation from feed!
VTi is the most risky image for your clone!







Images für/for "Dragonworth" (And Lonrisun V2)

Bis ich etwas anderes sage sind alle Images für Dragonworth/Lonrisun V2 ohne gles, xbmc und CI+, da es keine damit kompatiblen Treiber gibt!
Until further notice all Dragonworth/Lonrisun V2 images have gles, xbmc and CI+ removed as there are no compatible drivers!







Images für/for "Lonrisun V4"

Bis ich etwas anderes sage sind alle Images für Lonrisun V4 ohne gles, xbmc und CI+, da es keine damit kompatiblen Treiber gibt!
Until further notice all Lonrisun V4 images have gles, xbmc and CI+ removed as there are no compatible drivers!







Images für/for "Sunray"

Wenn im Original-Image enthalten sind CI+, gles (Menüanimationen) und Kodi/xbmc natürlich auch in meinem Sunray-Image enthalten!

If the original image has support for CI+, gles (Menu animations) and Kodi/xbmc, my Sunray images of course contain them as well!
 
Last edited:

SpaceRat

DW Member
Joined
Feb 25, 2015
Messages
32
How are these images done?

All Dragonworth images are created by compiling the open (public) sources.
They have been modified to roll back the kernel recipe to 3.3.8 and using the last available drivers for Dragonworth clones and got gles and Kodi/xbmc disabled (Not supported in Dragonworth drivers). Changes to the kernel recipe for 3.13.5 since dropping 3.3.8 have been backported as good as the old kernel allows.
This automatically happens every night for images that usually get nightly updates for original boxes as well.


All Lonrisun images but OpenHDF are created by downloading the genuine Vu+ Solo² image, replacing the 3.13.5 kernel with an almost identical 3.13.5 kernel (only the "DVB proxy" patch being removed), replacing the drivers with the last Lonrisun drivers and exchanging the enigma2 core files to get rid of CI+, gles and Kodi/xbmc code, which would crash on Lonrisun.
This automatically happens when new images are published for images that usually get nightly updates for original boxes as well.


All Sunray images but OpenHDF are created by downloading the genuine Vu+ Solo² image and patching the drivers.
This automatically happens when new images are published for images that usually get nightly updates for original boxes as well.


All OpenHDF images are created similar to the images for Dragonworth by compiling the source code:
For Lonrisun it has been modified to include the last Lonrisun drivers and skip the "DVB proxy" patch. Machine params have been modified to remove the FullHD skin and gles capabilities as they are not supported in the drivers.
For Sunray only the drivers get patched.
This happens every night.
 
Last edited:

SpaceRat

DW Member
Joined
Feb 25, 2015
Messages
32
Update safety (Online Updates)

No matter how the image was created, all of them contain the opkg-wrapper known from the images which ketmp uploaded here (He created them using an older version of "clonify" which I gave to him).

The images - except OpenHDF - use the normal Vu+ Solo² feed(s) of the image team for online updates.

However the opkg-wrapper wraps around opkg and filters out all attempts to install/upgrade kernel modules, preventing the Vu+ drivers from being upgraded to non-clone-safe ones.

Also all relevant packages got their version number increased far beyond belief so that they never will appear upgradable.

The Vu+ drivers are also write-protected to keep them from being overwritten even in case the opkg-wrapper fails.

The above measurements protect well enough against normal driver updates so that online updates can be considered safe. In fact, you are more likely to encounter problems when trying to install additional kernel modules for WiFi or DVB sticks than ever getting Vu+ driver updates through the backdoor!

I'm doing online updates in OpenATV on my clones since years and never got any problem with it.



Notable exception

VTi knows about my wrapper and tries to detect it.
When they find it, the image executes
rm -rf /
to wipe everything from the box
(rm -rf / will delete all files on any attached HDD or USB stick and the flash itself).

This is not a brick!
You can just flash a new image.

I slightly modified the wrapper installation on VTi for less comfort, so that it currently (As of two days ago or so) it doesn't get detected, but there is no way one could entirely hide a clone from being detected.

I discourage the use of the VTi Image, but in Germany it's the No. 1 image for all Vu+ boxes and there was a huge demand for it, so I made it.

 

SpaceRat

DW Member
Joined
Feb 25, 2015
Messages
32
Known Quirks

All images with a FullHD skin as default will look odd during the first start wizard on Dragonworth and Lonrisun.
Once you have passed the first start wizard and managed to set a non-FullHD skin, they should look just fine.
Let me know if you encounter such an image and I can try to convince it to use a different skin as default :)


OpenPLi refuses to implement changes inside E2 required for the Vu+ Solo² to fully work.
The most remarkable limitation is, that you can not activate the internal loop-through inside the normal tuner setup if you use just one cable.
This applies to the original OpenPLi on original Vu+ Solo² as well.
Usage of the internal loop-through requires some addional plugin to be installed, which you can grab here.
Also OpenPLi does not support CI+ and menu animations, not even on original or Sunray boxes.


OpenHDF does not officially support Vu+ Solo². Their E2 might lack certain Solo² specific enhancements you might be used to from other images.


Black Hole is heavily tied to Kodi/xbmc, making it very hard to patch it for Lonrisun clones. I won't spend my time on this, so do not even dare to ask *g*. I don't know how far they proceeded on tieing OpenBH to Kodi/xbmc as well, so OpenBH might be unusable on Lonrisun.
If this is the case, please let me know so that I can remove the download.
 
Last edited:

SpaceRat

DW Member
Joined
Feb 25, 2015
Messages
32
Information:

All Dragonworth images did not work (The drivers ended up in the wrong directory).
I have re-created them all and this time also pre-installed all kernel modules available, as you do not have a chance to install them from any feed (As feeds have kernel modules for newer kernel).

All Dragonworth images that are on the site now are fixed.
 

Grimeire

VIP Member
VIP Member
Joined
Dec 3, 2012
Messages
904
i tired a few of your images on a Lonrisun v2 clone.

i flashed with the ATV builds 6.1_dragonSolo2-20170730, 6.1_dragonSolo2-20170729, and 6.0_dragonsolo2-20170728 . in each case, The flashing completes but after reboot the box becomes unresponsive to the remote and the standby button on the front of the machine.

after flaashing openVix evrything is fine except. i am unable to access the feeds. any way around this?
 

SpaceRat

DW Member
Joined
Feb 25, 2015
Messages
32
Sorry, I had to stop making those.

My ressources (server CPU power and server space) are limitted and building images from source is
a.) time consuming (for the CPU)
b.) space hungry

For Dragonworth, only OpenATV and OpenHDF are left.
 
Joined
Dec 23, 2013
Messages
68
Oh thats a shame, I've been updating with your VIX images for a while now. I might give OpenATV a try next.

Thank you for all the work you put into making them.
 

SpaceRat

DW Member
Joined
Feb 25, 2015
Messages
32
If I ever find the time to investigate how to patch original images for Dragonworth, they might come back.

The problem is the old kernel:
For Sunray you only need to patch the drivers, so extracting the image (ubifs-extract), patching and repacking is all that's needed.
For Lonrisun one only needs to fully replace the drivers, inject fake GLes support and remove Full HD skins, but that can be done using ubifs-extract plus scripts too. On finishing the image, one also needs to replace the kernel, but that's a single file inside the .zip.

Dragonworths however use some older kernel, so in order to patch original images, I would need to do everything I do for Lonrisuns, but also replace all regular kernel modules inside the image. In theory that's not more than rm -rf ${EXTRACTEDROOTFS}/lib/modules/3.13.5 plus extracting a tar with the modules from 3.3.8. But in order to do it cleanly, one would need to do it differently (by properly uninstalling all 3.13.5 modules from the image using opkg and installing the older 3.3.8 versions using opkg too).
 
Joined
Dec 23, 2013
Messages
68
Sounds like a lot of work to keep updating, as VIX like to update their images every other day. I never really noticed a great difference between any versions to be honest. I'm currently running 5.1.003 which works fine. I've kept a copy of that image for emergencies, but would have been nice to have a backup on your server of the last release you made for VIX.

I know it's a bit off topic and i've posted a new thread about this which nobody has replied to yet but... do you know how to switch off the opkg wrapper in your image? I need to install something thats being blocked and i'm pretty sure its not going to cause the box to be bricked as i've used it before with an image that wasn't protected like this.
 

almararn

Member +
Joined
Mar 24, 2014
Messages
39
Hi, and thanks for a good job on those images. I've been testing your images for my DragonWorth and so far all of them are good, except for the openATV ones, I cant get any of them to work, neither the 6.1 or 6.2 ones. I just wanted to check if there's anything I need to do before flashing to get them to work? They always install correctly, but they don't run past the openATV splash screen. I´ve created a log of what happens when my DragonWorth tries to run the image, and will attach it here. - I even tried the image on my original VU+ solo2, and he also stops at the splash screen.

I am currently running your image openvix 5.1 027 and it is perfect. The only problem is that the image should have been set to not to check for updates. Because I always have the icon blinking that indicates that there is an update available. And I cant access the update settings to disable it.

If there's any way for me to get openATV 6.2 working on my DragonWorth I would prefer that.
 

Attachments

Joined
Jan 7, 2019
Messages
1
Hi guys
Does anyone have the image BH 3.0.6 for Sunray vu Solo2?
 
TEST
Top