solo2 clone

[bbb_uk]

The it looks like your's has been hit the same as others are reporting, my guess and it's just a guess but i'd say Vu+ have implemented something that has corrupted the boot sector and if that is the case you would need to reflash the bootloader but that's not so easy for the reasons i gave above. at this moment it looks like the box is bricked for the foreseeable future.

Do clones not have same bootloader as originals? If yes, why can't clone be flashed with an original bootloader?

I realise this may cause it to become a brick but by looks of things it may already be that.

[bbb_uk]

thanks matey.

total bummer or what.

Cant you try contacting where you bought it from as you have only recently bought it? They may accept a return of the board itself (too expensive for you to return the entire unit)

[eattheliving]

Cant you try contacting where you bought it from as you have only recently bought it? They may accept a return of the board itself (too expensive for you to return the entire unit)

did that this morning mate. just waiting for a response.

[Sharpy47]

This is a reply email from a supplier in China to a owner on another forum

"hello friend.
the problem is not for the box, I think it is for the server or the software, all the solo 2 in Europe can not work in the same time..many customer from different country tell me the same probelm. i think the software is crush. a Germany customer tell me that it is not just my company solo2 cant work .all the solo2 solo(vu product ) cant work. my engineer will look for the problem .i am waiting for his reply. sorry. pls give me time to solve it"

[bbb_uk]

Reading that looks like most people are having this problem regardless, it seems, of the image installed.

Looks like it is a clone bomb and rubberduck is probably right what he said back in post #73

[RuberDuck]

Do clones not have same bootloader as originals? If yes, why can't clone be flashed with an original bootloader?

I realise this may cause it to become a brick but by looks of things it may already be that.

A) yes it's the same bootloader from what i understand
B) because there has never been a bootloader update for the solo2 and as such there is no bootloader in the public domain.
C) because in the receivers current state there is no way to flash the bootloader, you would need to identify the J-Tag points first.

[RuberDuck]

This is a reply email from a supplier in China to a owner on another forum

"hello friend.
the problem is not for the box, I think it is for the server or the software, all the solo 2 in Europe can not work in the same time..many customer from different country tell me the same probelm. i think the software is crush. a Germany customer tell me that it is not just my company solo2 cant work .all the solo2 solo(vu product ) cant work. my engineer will look for the problem .i am waiting for his reply. sorry. pls give me time to solve it"

Sorry mate but he or she is selling you a load of twoddle, no other Vu+ receiver is affected except the Solo2 clones.

[Sharpy47]

Yes mate it seems it is only the solo2. That email was not sent to me, was just high lighting the fact that the suppliers in China are aware of the issue and are trying to address it.

[RuberDuck]

China are aware of the issue and are trying to address it.

More like shitting them selves at the prospect of many thousands of potential claims going in for refunds.

[eattheliving]

just been reading some posts on another site and the guy's on there are indicating that a chip on the mobo needs to be replaced.

below is a quote from the other site. don't know if this makes any sense to you smart guy's

"The chip that needs replaced is the Samsung k9f2g08u0b (or thats what it is on my board). Its the chip nearest the card reader assembly"

[lombard]

just been reading some posts on another site and the guy's on there are indicating that a chip on the mobo needs to be replaced.

below is a quote from the other site. don't know if this makes any sense to you smart guy's

"The chip that needs replaced is the Samsung k9f2g08u0b (or thats what it is on my board). Its the chip nearest the card reader assembly"

good luck replacing that

[westkill]

that will teach me mine gone to pmsl

[endemall]

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!!

[bbb_uk]

"The chip that needs replaced is the Samsung k9f2g08u0b (or that's what it is on my board). Its the chip nearest the card reader assembly"

That is a Samsung flash memory. If the flash memory has got corrupt then need to find why it has.

So much flash memory going at same time in all the solo2 clones means something caused it like a clone bomb. Therefore, changing the flash memory may not solve the problem as whatever caused it may cause it again depending on what did cause it.

For example, if the it was a clone bomb and it was programmed to go on just 19th april then replacing the flash memory after 19th april may be okay but on the other hand a clone bomb programmed to go on 19th april and after could mean it will happen again once flash memory is replaced.

Also, it would have to be something to cause the flash memory to go faulty itself rather than its contents. Corrupting the contents of the flash memory (ie what is saved on it) is lot easier than causing actual damage to the flash memory.

Assuming it's just the contents (ie bootloader) that is corrupted then a re-flash could potentially be done assuming you can get a copy of the bootloader and reflash it (Rubberduck discussed it briefly when he answered my questions in post #81).

[lombard]

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!!

stay that way mate, i think upto offical vix 3.0 build 808 is fine, after seems vu drivers had a timebomb, so dont update to a newer image with new drivers