Concerning the Solo2 drivers we can find out that :
- HW Error message is present only on drivers dated 20131212 and 20131224, prior to this there is no such message (20131106 or before).
- On drivers dated 20140306, 20140310, 20140316, 20140318, 20140403, 20140424, there is no such message (HW Error), so it's very relevant to think that the TimeBomb was implemented from drivers dated 20140306.
- On new drivers dated 20140715, there is no such message (HW Error)
The hack/crack of the HW Error is very simple, everyone of you can try, you need to replace a byte from 40 to 00 as per below.
.text:00030468 beqz $v0, loc_304C0
15 00 40 10 8C 00 BF 8F 00 00 02 3C
to
15 00 00 10
.text:00030468 b loc_304C0
The sub where this is happening is : brcm_fpga_secu_check
You can easily change / patch the dvb-bcm7356.ko file just searching for the string above and replacing the 40 to 00.
The drivers from 12.12 and 24.12 will then work with V1 boxes also.
The Timebomb implemention has to be studied then from the March 06 drivers.
Omni