damndl0ser said:
While I do not repair any type of console, I do work on electronic circuit boards and computers every day (gas pump dispensers). There are codes for everything in those that tell you what the problem is and all you have to do is know what the error # is to get an idea what your problem is. I would be willing to bet the PS3 has something similar. It makes a tech repairman's life much easier.
Even without the error codes you can track everything down with a basic knowledge of the system and an ohm meter. It just might take forever. So there are ways of knowing what has happend and why it has happend. This would be just an experts opinion and I am sure Sony can produce people who disagree. I guess its just which expert the jury believes most. |
Yeah, but I don't think there would be an error code that tells you the firmware was the cause for trouble. I'm sure you could tell the firmware was installed and there is an error code, but any number of things can cause your PS3 to break.
How do you prove the update was one of those things? Can you prove they are connected?
They could say the firmware caused x code but since I doubt the code is that specific Sony just comes back and says this, this, and this can cause that along with this and this. How do you prove it was the firmware that caused it?
Also, when say 20,000,000 people downloaded the update and say 19,999,750 didn't have any problems how do you prove that less than 1% of the total PS3's had that unique thing that made the PS3's brick?








