Exactly my point, Drivers are closed source, there is no way for any team to know what's in the drivers unless the manufacturer tells them, for Genuine users driver updates are of no concern but for clone users they should always be wary and not so quick to try new drivers for just this reason.
solo2 clone
Collapse
X
-
Update drivers
20140403
- Fix audio problem(duo2, solo2)
for solo2 just over 2 weeks ago the 3rd of april
since the fix came out for a v1 solo2
to upgrade it to a v2
there have been 6 driver updates in less than a month
for solo2 6th of march to the 3rd of april
before them dates no solo2 clones where fo@oking up
hi davvo,
would these driver updates automatically download and install?
and if it is a driver issue would it completely destroy the front panel info as well: ie nothing showing on the display screen at the front of the box.
I have also tried to connect to the box via network and it's not even showing.Comment
-
The driver updates were the 3rd April according to davvo.
Why last night/this morning should, it seems, a lot of clones start going (seemingly) dead?
My field is IT and with regards to comment that those with genuine boxes have no cause for concern isn't entirely true. A driver update can cause problems for genuine boxes as well as clones (albeit I agree that clones may suffer more)Exactly my point, Drivers are closed source, there is no way for any team to know what's in the drivers unless the manufacturer tells them, for Genuine users driver updates are of no concern but for clone users they should always be wary and not so quick to try new drivers for just this reason.Last edited by bbb_uk; 19 April, 2014, 13:27.Comment
-
no there wont auto update drivers, the last drivers probably worked probably had some timer on them to stop the clones and seems like it was now , and no it cant destroy the front LCD, its probably chip that drivers messed uphi davvo,
would these driver updates automatically download and install?
and if it is a driver issue would it completely destroy the front panel info as well: ie nothing showing on the display screen at the front of the box.
I have also tried to connect to the box via network and it's not even showing.Comment
-
Which is precisely why we would never be knowingly involved in any clone bomb attempt, just incase it did impact genuine users. I my self ended up with a Genuine DM7020si dead as a result of the so called clone bomb the gemeni team released way back in the day, so i know how pissed off genuine users would be for something like that to happen to them.The driver updates were the 3rd April according to davvo.
Why last night/this morning should, it seems, a lot of clones start going (seemingly) dead?
My field is IT and with regards to comment that those with genuine boxes have no cause for concern isn't entirely true. A driver update can cause problems for genuine boxes as well as clones (albeit I agree that clones may suffer more)Comment
-
no drivers can not update automatically, but there is no way of knowing just when such a thing as a clone time bomb could have been introduced into them, it could have been several months ago for all we know.hi davvo,
would these driver updates automatically download and install?
and if it is a driver issue would it completely destroy the front panel info as well: ie nothing showing on the display screen at the front of the box.
I have also tried to connect to the box via network and it's not even showing.Comment
-
cheers guy's.
so the question is.... can I do anything to resurrect my box if it is a time bomb issue?Comment
-
Ruberduck, would re-flashing bootloader and/or Vix (or any other firmware) with serial null/RS232 cable help?Comment
-
Do you have a green light or red light with no other activity? I read on another forum (not related to this possible clone bomb thing though) that should try removing harddrive and reflashing with the image it came with when you purchased it.
This is just a guess but some have said harddrive can cause problems.Comment
-
That would be my first thing to look at, but you cant flash the bootloader via the Rs232 port, plus a) the bootloader is not in the public domain for this box at the moment and b) you would need to know the J-Tag points.Comment
-
I have tried that and i get nothing. Here`s hoping some sort of fix comes out soon. Could be ?150 down the drain by the looks of it.Do you have a green light or red light with no other activity? I read on another forum (not related to this possible clone bomb thing though) that should try removing harddrive and reflashing with the image it came with when you purchased it.
This is just a guess but some have said harddrive can cause problems.Comment
-
only the power light is on and that is in standby mode. If I press it then it lights up fully for a second then back to standby mode again.Do you have a green light or red light with no other activity? I read on another forum (not related to this possible clone bomb thing though) that should try removing harddrive and reflashing with the image it came with when you purchased it.
This is just a guess but some have said harddrive can cause problems.
I have just tried to install blackhole image and it's not even reading the mem stick in either usb ports. I will try unplugging HDD to see if that helps.Comment
-
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.only the power light is on and that is in standby mode. If I press it then it lights up fully for a second then back to standby mode again.
I have just tried to install blackhole image and it's not even reading the mem stick in either usb ports. I will try unplugging HDD to see if that helps.Comment
-
thanks matey.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.
total bummer or what.Comment
Comment