solo2 clone

[RuberDuck]

no driver update for 2 and half months
then 6 come along all at once
i knew soon as that v1 fix came out what was going to happen
thats why i did not update the drivers on my box
and why would i need to update when everything was working as it should

most of you updated
for the sake of a date
got to have the latest
in one driver update its says fix audio on solo2
nothing wrong with the audio in the first ***** place

Thats hardly surprising with the so called experts on some other forums and their mythical solo2 hack, It was simply a matter of time before something like this happened and no contrary to popular belief on said forum, I knew nor had anything to do with this, Cant say i'm sorry about it though.

It's about time toe koreans took a swipe at the Chinese cloners, unfortunately it's the users who were first conned into buying counterfeit goods and then get hit by this who i feel for, the rest who knowingly buy and sell clones, I'm well chuffed there dropping like flies.

[RuberDuck]

To be honest guys every one here is just assuming that this is a Vu+ Driver thing, I can say for a fact it's not something put there by the image teams and it does affect all teams images. after speaking with RvB this morning he has spoken to some senior Vu+ executives who assure him it's not them, so what else could it be ?. My money would be on the Chinese them selves as a way to get extra income, how better to do that than a coordinated kill command in the clones so users have to buy new boxes or have old ones repaired at a cost ?.

[lincsat]

Well it does only seem to affect boxes using images with the latest drivers. I have tried a box today using the Ferrari patched Blackhole 2.0.9.1 and it's working fine, others have boxes with older images working fine. The common denominator is the recent Vu+ Drivers. There are other Chinese boxex, both Duo and Solo with original ViX Zeus 023 gone exactly the same on Saturday. It's not proof that the Vu Drivers are the culprit but they are certainly the prime suspect.

I doubt the Chinese ae doing anything deliberately, especially with relatively expensive and new boxes - customers are going to send those back for warranty returns (rather than just order a new box) and most respected Chinese sellers will do a free repair/exchange.

[RuberDuck]

I doubt the Chinese ae doing anything deliberately, especially with relatively expensive and new boxes - customers are going to send those back for warranty returns (rather than just order a new box) and most respected Chinese sellers will do a free repair/exchange.

As with all previous suggestions mine is just a personal supposition, but the Chinese are not exactly operating a legitimate business to start with, so it's not a massive stretch that they may want to thin out a already saturated clone market, Vu+ or any other legitimate business on the other hand would have a lot to loose and could potentially be taken to court if it was shown to be a deliberate act by them. But at least we are starting to see some rational and sensible posts about this, as the one going else where is a farce with slanderous and potentially libelous claims being flung in all directions by irate clone users.

[bbb_uk]

IMHO I agree with lincsat. The reports suggest it's not image related and the only obvious thing in common are VU drivers and chinese.

I doubt chinese would do this unless they did this to their older clones to stop recent people also suffering from problem. Also, as it stands, this looks bad for chinese so they will lose money for those thinking of buying a clone will now hold off and/or may get an original.

This is again just my opinion but VU have the most to gain from implementing something and of course they're not going to admit they did anything.

[Sharpy47]

Just like Jesus, they will rise again tomorrow. Well that`s what i`m pinning my hopes on

And for those on here and other forums having a good old laugh at us clone owners expense, remember, it might be your mobile/tv/computer next.

[dowlinr]

FFS Why don't I read threads to the end before rushing in and buying.

Are all images killing clones or just the VIX? If it works when I turn it on is the best advice not to update the image?

[pugwas]

It would appear to be all recent images I was not running VIX
Load an old image before booting up you may be lucky

[Sharpy47]

FFS Why don't I read threads to the end before rushing in and buying.

Are all images killing clones or just the VIX? If it works when I turn it on is the best advice not to update the image?

Mine came with BH 2.9 installed. From what i`m reading flash it with a "Pre-December" image.

[dowlinr]

So I should be ok if I flash it with a pre December image before its first boot?

Sent from my Nexus 5 using Tapatalk

[Sharpy47]

If i could roll back the clock to Friday night it would be the first thing i would have done. Fingers crossed it works for you mate.

[dowlinr]

Can anyone recommend a pre December image I should use?

[lombard]

i think official vix 3.0 build 808 is fine

[davvo]

Can anyone recommend a pre December image I should use?

Black Hole 2.0.7
release date october 2013

[lincsat]

As I posted earlier, the Ferrari patched Blackhole 2.0.9.1 works OK for me on a Solo2 with the X-Chip. I would imagine that all Ferrari patched images would be OK but don't know for sure - also, don't update the image from the menu.