Technical topic solo2 clone (please only technical talk)

It looks as we finaly are going to get the longwaited RS232 Support....Hopely also for oure boxes:


SOLO2 encryption system with USB-V2.0 has been released, directly support the original BlackHole2.0.9.1, and is not dead brush. Also supports other VU SOLO2 latest software. Requires supporting the use of USB-V2.0 chip
1, each machine independent MAC code, the same LAN can support multiple machines simultaneously.
2. adding a SERVICE interface, support directly through the USB port upgrade encryption chip (SOLO2 special new feature).
3, you can brush by brush machine software startup. Comprehensive solution to the brick machine (formerly confidential purchase a brick Brush debugging device drivers installed on your computer Broadcom information through JTEG debugging to brush). (SOLO2 special new feature)
4, support for the latest version of the original software, the latest information on the original drive.
5, directly to the CPU cooling fan to cool.
6, FPGA with an exclusive upgrade information. (SOLO2 proprietary information)
7, with a super-VU + remote control. (Coming soon), supported by the European common TV encoder, supporting automatic search TV encoder, support learning TV encoding.

revised version with ability to recover easily if similar was to happen again ? like the dreambox 800se ?
 
Exactly!But therefor they offcourse must have write some kind of a bootloader...Whenever VU attacks and the sh..thits the van,you always can go back to the default bootloader...Thats what we were saying here for months now!
 
Evening all.

Just replaced my chip, and very happy to have a working box back.

Got impatient waiting for chip holders to turn up so, gave it a go.

Board (Main PCB) out, takes 3 minutes, its worth it.

Using a Jet Gun,(mines a Leister) and angled tweeters, removed chip (easy bit), went for heat 5, blow 1.

I didn't risk cleaning pads (pad lifting can happen), so with my Antex M12 12w iron (smallest point), re-flowed each pad with a dab of low melting point solder (on the tip only), and a fraction of a second on each pad to flow it, as even this small iron gets too hot.

Took the new chip and stuck it down to a bench (or held it), and tinned the connecting side of the legs (same iron).

Position the new chip on to the board (check the spot allocation), and hold it down (use magnifying equipment and a suitable pick to steady the IC, Maplins sell both).
Then I used the same Jet Gun, while applying gentle pressure to the chip, to heat the pads / legs, until you can tell / smell that the solder has flowed, the chip lends itself to do one side at a time.

Then with a magnifying glass (x10 for me), I checked every leg with a pick just to make sure, any dubious ones can be re-done with the above iron, with a very clean tip (one by one).


My end result was good, I did notice on inspection that I had inadvertently heated up a surface mount cap to the point the contacts had bridged, but easily sorted with the above iron.

So in short, heat off, clean up, rework chip and area, heat on, inspect.

NOTE- This is what I had available and it worked, don't assume anything, (anyone without soldering skills, Please give it to someone who goes 'oooohhh' when you point out the chip to be changed).

Final Note - Please, please take your PCB to a local electronics company / person (goggle is your friend), if any of the above are in any any way out of your comfort zone.

Hey it worked for me, and I'm so glad I have a box back.

BUT...

If I could offer any advice, read, read, watch, then listen. It's sad that so many now have big burn holes or no pads left.

Hope it helps,

(PS, Apart from plumbers, i had no flux in the house).
 
Well my chip from China finally arrived and I've got it installed and one thing I did notice is that after I installed the chip the MAC address of my box had changed. This isn't something that you'd normally spot but I have a DHCP reservation setup for my box so that the box always get the same IP address but when I booted it up it didn't have the IP address I'd expect. So had a look around and the MAC address of the box had changed.

Why am I posting this? When dirkjan73 posted earlier about the spec of what looked like a revised box and one of the lines in that spec was related to the MAC address and it being unique. I wonder if this is how the vu time bomb worked out what to hit?

...
1, each machine independent MAC code, the same LAN can support multiple machines simultaneously.
...
 
I know that and that wasn't the point of my post.

I changed over the chip and reflashed using an unaltered ViX 3.0-808 image and the MAC address had changed, so it looks like there is something in the flash that we can't see that sets the MAC address?

Could they target boxes via mac address checking with original stb database

Sent from my GT-I9300 using Tapatalk
 
So what are peoples MAC addresses, rather than make them public, maybe drop me a PM, if a few people send me theirs I might be able to see if they are the same or same sets of MACs being used.
 
So what are peoples MAC addresses, rather than make them public, maybe drop me a PM, if a few people send me theirs I might be able to see if they are the same or same sets of MACs being used.

I am still waiting for my chips mate otherwise I wud have made my mac available to u

Sent from my GT-I9300 using Tapatalk
 
Intresting so the recievers are using a spoofed MAC address which appears to be held in the Flash IC chip. Theyre not using the actual Burnt In Address of the Ethernet Interface. Maybe the VU anti clone measure was using the BIA MAC of the clone ethernet interface to identify the reciever was a clone i.e: maybe clones used a different manufacturer for the ethernet interfaces than the original boxes uses hence the first part of the MAC address or the OUI used to identify the manufacturer will be different.

To be fair this issue should have been forseen, it's poor design from the clone manufacturers to not have any mechanism such as a service port or workign JTAG solution to recover the reciever in the event that the bootloader is erased or corrupted. The removal and install of a new flash IC is a pretty primitive solution.

It's good that they've decided to implement a service port solution, which probably means the issue of the flash IC being set to read only must also be reversible by software.
 
Intresting so the recievers are using a spoofed MAC address which appears to be held in the Flash IC chip. Theyre not using the actual Burnt In Address of the Ethernet Interface. Maybe the VU anti clone measure was using the BIA MAC of the clone ethernet interface to identify the reciever was a clone i.e: maybe clones used a different manufacturer for the ethernet interfaces than the original boxes uses hence the first part of the MAC address or the OUI used to identify the manufacturer will be different.
I suppose it's possible VU used the MAC address to identify clones knowing that none of theirs use that mac address. There could have possibly been other ways to determine this.

If it's true that lorison clones suffered from the clone bomb but other manufacturers like Gold didn't then if it was MAC address that gave them away then that would mean all lorison clones would have same mac (at least first few characters) but likes of the other manufacturers like Gold had a completely different mac (again the first few characters).
 
Well my chip from China finally arrived and I've got it installed and one thing I did notice is that after I installed the chip the MAC address of my box had changed. This isn't something that you'd normally spot but I have a DHCP reservation setup for my box so that the box always get the same IP address but when I booted it up it didn't have the IP address I'd expect. So had a look around and the MAC address of the box had changed.

Why am I posting this? When dirkjan73 posted earlier about the spec of what looked like a revised box and one of the lines in that spec was related to the MAC address and it being unique. I wonder if this is how the vu time bomb worked out what to hit?
The spec also mentions same LAN. I think they meant for those having more than one clone on same router network (LAN) as routers are likely to object to that so having different macs would help.
 
My god these chips are tiny postage stamp size how do you guys even see the pins to solder them!!!!
Mine do not have any markings on them no name or numbers
 
Last edited:
It should have Samsung or Toshiba with a part number etched on the top of the chip. The indented circle indicates where pin number 1 is.

In the picture below is my old chip that I removed, the indented circle is on the top right.

20140513_110422_zps8c834ea3.jpg
 
OK found the writing and circle my sight is not very good

Sent from my XT1032 using Tapatalk
 
Maybe something similar can be done in SOLO2 to protect it against accidental recording or update drive in the background?

Ps.: After changing the flash chip.

<span id="result_box" class="" lang="en"><span class="">[video=youtube_share;wsZEDMh3pOU]http://youtu.be/wsZEDMh3pOU[/video]
 
Bro there is no...i repeat THERE IS NO automatic,background of secret driver update,so dont worry about this...Just take a safe image,dont do a online update and u are safe!
 
Bro there is no...i repeat THERE IS NO automatic,background of secret driver update,so dont worry about this...Just take a safe image,dont do a online update and u are safe!

How do we know this may not be implemented in the future? is it impossible? - just asking out of curiosity.
 
How do we know this may not be implemented in the future? is it impossible? - just asking out of curiosity.

what merit would a image team have to provide mandatory, automatic image updates ?. It would cause way more problems than it could ever hope to resolve. I cant speak for other images but i can say with 100 percent certainty that ViX will never force a user to update their image with any form of automatic update, the decision whether or not to accept a update will always lie with the end user.
 
Back
Top