---1. Did this update brick your PS3?
---2. Define "brick" in your case
---3. If it did brick your system, how many times did you reboot your PS3 before it bricked?
Speevy said:~150 users, not one brick because of the update so far.
Metalmurphy said:Some one mail Kotaku and tell them the problem is alot wider then they reported!
Seriously now, after reading the thread on the Playstation forums where Kotaku got the "story" it seems the few guys having the problems got they're update download disconnected serveral times, which means the file probably got saved incorrectly, hence the problem.
I don't believe there's actually anything wrong with 2.4.
Metalmurphy said:I don't believe there's actually anything wrong with 2.4.
dallow_bg said:Would have been easier to only ask people whose PS3 bricked to post.
Which doesn't seem to be anyone here unless I missed a post.
What I'd like to know is how many times you've turned the system on and off.
Metalmurphy said:it seems the few guys having the problems got they're update download disconnected serveral times, which means the file probably got saved incorrectly, hence the problem.
Alcahest said:impossible. before the ps3 actually launches the updating process, it checks the md5 of the downloaded firmware file. If it were corrupted in ANY WAY, md5 wouldn't match and ps3 would refuse to start updating.