If Your Clone Solo Boxes are Working

If Your Clone Solo Boxes are Working and You Want to Save them From Attack
Then Fallow These Tips .
1. Dont use the images After the March
2. Dont use images Blachole/Vti .Vix update online command
3. Use BH 207/208 VTI/ or VIX which one is before from 15/12/2013

When U Update Image
Keep in mind .One copied from online update/ or from fresh release images . This Anti-Clone attack in the new images start when the unit has synchronized its time with the satellite...And thats why you must avoid this!.When the old images and old drivers are installed then there is no danger anymore...

1. Remove All the Cables including Satellite and Network cable .
2. Connect Only AV and Power cable
3. Get a old original image BEFORE 15/12/2013
4. Format a USB with Fat32,copy the image on this USB
5. Put it in your Clone Power On and let It complete

The Links u can find Safe Images for your Solo Clones

http://www.digitalworldz.co.uk/downloads.php?do=cat&id=125

Click to expand...

VU+ and X --- DownLoads

Click to expand...

*Thanks to the all peoples who are Working day and night to finding the solution*
its Just an small effort to save ur boxes from anti-clone measures. All tips are collected from different thread and link in this forum if u have any update kindly share it with Others Here

Thanks @Ali

It will also be great to have a list with the Clone Safe Images because you say driver before 15/12/13.
Ok, but for example: BlackHole 2.0.9 Solo2 Old drivers, is this image SAFE? what old drivers mean ? -> http://www.digitalworldz.co.uk/index.php?resources/1531/

I think it will be easier for everyone to add this kind of list.
What do you think ?

openvix 3.808 solo 2 backup image says old drivers to but not how old they are or from what date. AJT will probably know

I posted this in the main Solo2 thread a while back:

Just trying to establish which images are safe to use, so looking back through various posts:

BH 2.0.6 had drivers dated 2013/09/18
BH 2.0.7 had drivers dated 2013/10/23
BH 2.0.8 had drivers dated 2013/12/16
BH 2.0.9 had drivers dated 2013/12/30
BH 2.0.9.1 had drivers dated 2014/03/10

For ViX:

ViX 3.0-802 had drivers dated 2013/11/06
ViX 3.0-808 had drivers dated 2013/12/12 ( I think but I'm not too sure )

Can we compile some sort list to see what images that people were using that got blatted? Hopefully from that we can deduce what images to avoid.

Mine was ViX 3.0-808 but I had updated the drivers to the latest ones that came out in April.

Click to expand...

Thank u @iamatheaf but when i bought my Box back to live again,i am going to back to the safest image and thats the one who gave the "Hardware Error" i am going back to 15/12/13 Till theres a JTAG or another way to let it act as a genuine again

mine arrived after the timebomb so i flashed it with blackhole 2.0.7 straight out the box but didnt like it so i flashed it to vix 3.0.748 so far all okay

From what I can tell you should be safe with either vix 3.0 802 or 808 untouched images.

Edit: just realised that 808 actually gave the HW Error before we had the fpga and flash updates so I'm not too sure now.

Sent from my GT-I9505 using Tapatalk

IAmATeaf said:

From what I can tell you should be safe with either vix 3.0 802 or 808 untouched images.

Edit: just realised that 808 actually gave the HW Error before we had the fpga and flash updates so I'm not too sure now.

Sent from my GT-I9505 using Tapatalk

Click to expand...

808 is fine, had it running myself

Personally I would advise sticking with the older images from December 12th 2013 as well as the older driver. We dont actually know the full details of what the VU+ clone attack involved.
Yes it defintiely included a time bomb in the broadcom drivers, but there may well have been other software modules involved in the attack. If your just patching new images with old drivers how do you know the other "up to date" software modules dont have anti clone measures as well, they may jsut have not triggered yet.
Stick with old images and dont do any online updates.

VTI 6.0.5 with the following drivers is running in my box from many days. Works fine also Opera Browser, YoutubeTV and hbbtv

brcmfb.ko 24.12.2013
cdfs.ko 17.06.2013
dvb-bcm7356.ko 25.12.2013
fpga_directc.ko 24.12.2013
procmk.ko 24.12.2013

where did cdfs.ko come from
you only need the other 4

This driver is oly in VTI image

In the VTI 6.0.4 the driver cdfs.ko has the same date. The other 4 are of 13.12.2013