solo2 clone

[cactikid]

would you not be better off using clonesafe images?

[digicon]

What ever image you use just make sure that where ever you get it from that its noted to include Drivers from Pre December 2013 and everyone should be fine, I also think its been clarified enough that it is NOT the IMAGE that Kills your Clone receiver it is the DRIVERS contained inside said image that will kill it. Vu+ will undoubtedly deny they have implemented anything in the latest Drivers but everything points to the Drivers being at fault here.

As with other suggestions those who have working Clone Solo2's it may be prudent to load an older image as been mentioned just to prolong use of your receiver until the powers that be in PRC come up with a Fix, A working clone box is better than a dead one.

[toysoft]

Does someone is able to do this ? The memory location called mac has nothing to do with the MAC Addresses naturally, but is replacement of "cfe" name.

Searching for that dump from original Solo2 and from Lonrisun Clone Solo2, if possible various, so we can all understand what happened as well as to be able to load it back via USB/Rs232 or at least JTAG as it's possible for VU+ Solo/Duo/Uno.

--------

"VU+ Solo2 : mtd3: 00100000 00020000 "mac"

PHOENIX can you login into the box, get the nanddump, and go to the tmp folder and send command :

1) Download nandump (if FTP remember use "binary") to the /tmp folder on your box
2) Change attributes with "chmod 755 nanddump"
3) send command "nanddump -nf /tmp/mtd3 /dev/mtd3"
4) Upload here the mtd3 file, that should be the cfe_cfe_auto.bin

We need this to be done also on a working Lonrisun Solo2 clone box, to get the CFE from them.

[toysoft]

Exactly, images with old drivers such as december ones, are still working fine as the drivers were not updated to the ones with the timebomb.

Listening executives of VU+, is something funny, they know what we all know. Also claiming that the clone manufacturers would have done this, I don't believe it. Again giving out that idea from VU+ executives is even more to try to blame chinese and show the involvement of VU+.

But one very important point, DON'T UPDATE ONLINE your image, also if drivers stay pre-december. The box will be also attacked and will fail. You will not be able to load a new image, it will be stuck at the "UBIFS" LCD message. Seems that the CFE is also corrupted or that it is upgraded by online update, and probably incompatible with clones (;o)))) just by chance for VU+ ;o)))))))))) as an executive of VU+ would tell you !

It's natural that VU+ reacts against the Solo2 clones that for sure reduce drastically their business, as the box is really of high level... but they should do as for the VU+ Duo, reduce by half the price the day the clone appeared. In the other side, damaging people property is illegal as much as these people buying clones knowing it !

TS

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.

[toysoft]

Can you get the mtd3 out of your box ? See p9 on how to do it. Your box is then a clone from Lonrisun. The ones beeing killed.

TS

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

[toysoft]

Can you get out the mtd3 ? as explained on my last post ? This would help the guys who suffered from this Lonrisun VU+ attack and let us understand all what happened.

Yes, keeping older drivers is always the way... but this time VU+ were clever, they were waiting some time before the bomb would explode, to be sure as many as possible boxes were having drivers. It seems that drivers from 2014.03.10 are also touched, as these are the ones on the BH repository... BH 2.0.9 Solo2 clone boxes were also killed.

Some people are giving feedbacks that VU+ Solo mini and VU+ Duo mini are also beeing killed, as well as iCloud mini too. So it's general, same way, time bomb for Easter gift to everybody ! ;o)

Thanks,

TS

Just read all these crazy goings on. Just for your info guys.
Got an original solo2 downstairs vix zeus fine
solo2 clone upstairs bought a week ago from mixeshop, came with BH updated straight away to vix 808 Ferrari editon. This box is also still fine. Turned off and on no probs!! Yet!!

[digitaly]

Can you get out the mtd3 ? as explained on my last post ? This would help the guys who suffered from this Lonrisun VU+ attack and let us understand all what happened.

Yes, keeping older drivers is always the way... but this time VU+ were clever, they were waiting some time before the bomb would explode, to be sure as many as possible boxes were having drivers. It seems that drivers from 2014.03.10 are also touched, as these are the ones on the BH repository... BH 2.0.9 Solo2 clone boxes were also killed.

Some people are giving feedbacks that VU+ Solo mini and VU+ Duo mini are also beeing killed, as well as iCloud mini too. So it's general, same way, time bomb for Easter gift to everybody ! ;o)

Thanks,

TS

Just comeback from my easter holidays in disneyland and found my little surprise just now ... what vu+ doesn't knows is that now lot's of people are going to come together and with the help of china we are going to get a solution for this ...

I never bought a Vu+ receiver before. But from my DM experience after gemini released the dm500s (the famous bomb firmware) it has got fixed pretty fast....

I know Vu+ rely to some stronger security. But peps are on the works!!!! :-) the good thing was that I was happy with this solo2 and I was convincing my self to get a duo2 original... But now I will go for a gigablue instead!!!

I should be upset? I'm not !!! I love to own broken devices as I get a good feeling when I get to fix them.

P.S.
Worst scenario all we have to do is swap a nand flash and leave it on 2.0.7 (pre december 2013 drivers) and leave the write legs disconnected (dis-soldered) and wait for a better solution until then. Please guys keep this board update with all the communications you might have with your supplier. :-)

Koreans you keep eat your dogs!!!

P.S (2
Excuese my english... I just ended a 1000 miles trip and should get some rest now but I could not wait for tomorrow

[pugwas]

Got a response from L&W this morning
"You install the latest blackhole 2.0.9.1 software?
This software is currently not compatible, do not worry, our engineers have been in the emergency treatment of this problem, I will give you an answer as soon as possible, please give me your email, I will send the right software the first time to you
You have any needs,please tell me,thank you
Sincerely wendy"
Hopefully fix coming soon

[westkill]

would be nice if some clever person could make a .nfi extention to a solo2 image bricked breaker box image to flash through a a rs232 lead and use dreamup or something would that not work loooool just thinkin out loud looooooool or am i a knob to a gimp idea pmsl or is it a stupid idea

[westkill]

thinking about it i guess still nothing to boot to to load it either looooool i get me coat pmsl

[DOUGALMCD]

Made me laugh

[Sharpy47]

Sent to me today from my supplier

"have you updated blackhole2.0.9.1 these days?
if you have updated on forum, just as there is virus on the software, so clean your flash
so please update the software from this website: by RS232
to see whether can be back to the first ."


"please update the software by RS232 from this link

VU+SOLO2 software"

[cactikid]

think westkill is talking meathead again

[westkill]

think i am must had a blonde moment

[cunny]

Has anyone managed to get thier box going again. If so how

Sent from my GT-P5110 using Tapatalk HD