[ibmAS400user]

Originally Posted by danixleet They are, half the dev_flash files are signed as 4.21 with the execption of vsh.self and a few others. so technically yeah, 4.21 and 4.25 are the same lol

if 4.21 and 4.25 are the same why is 4.25 bricking some ps3's ?

[tjhooker73]

Originally Posted by ibmAS400user if 4.21 and 4.25 are the same why is 4.25 bricking some ps3's ?

Because They are doing it wrong.

[bammo]

they arent doing it wrong they are just thinking thry are secured like they always do they dont see it as doing it wrong until they get cracked again then they will see

[tjhooker73]

Originally Posted by bammo they arent doing it wrong they are just thinking thry are secured like they always do they dont see it as doing it wrong until they get cracked again then they will see

If they brick while updating from 4.2x to 4.25 Then they are doing it ****ing wrong. My PS3s Updated fine, My friends PS3s Updated fine, Their friends updated fine.

[bammo]

you cant always get get all the bugs out of a fw frankly i dont care about anyones ps3 idc if you brick it or if its sonys fault i guess im just a prick but iv had 3 ps3s never bricked a single one on any fw or cfw so i blame sony and the end user but in the end i dont care because its not happening to me

[LoverboySimer]

Originally Posted by tjhooker73 If they brick while updating from 4.2x to 4.25 Then they are doing it ****ing wrong. My PS3s Updated fine, My friends PS3s Updated fine, Their friends updated fine.

no no no its really bricking
some ps3's after preparing fro update get black screen, no controller assignment, no recovery menu nothing.
i now have two bricked ones. it never happened to me before

[haz367]

wow that some crazy shiit there, thx sony, skipping 425 al the way

btw updated multiman, and the changelog has been changed/he removed that red power crap, stil shows support for 421CFW

maybe its like with cex2dex, we need per console keys and use them to calculate hashes or some to get a 421cfw, time wil tell, it isn't christmas yet...

[uchedus]

Originally Posted by bammo you cant always get get all the bugs out of a fw frankly i dont care about anyones ps3 idc if you brick it or if its sonys fault i guess im just a prick but iv had 3 ps3s never bricked a single one on any fw or cfw so i blame sony and the end user but in the end i dont care because its not happening to me

SOUnding like a loner... You dnt care because its nt hapening to you...

[fanboysarestupid]

Originally Posted by tjhooker73 If they brick while updating from 4.2x to 4.25 Then they are doing it ****ing wrong. My PS3s Updated fine, My friends PS3s Updated fine, Their friends updated fine.

Someone who simply pressed "Updated" via their PS3 or downloaded the firmware to the USB and then upgraded the PS3 are doing something wrong? No.

4.25 OFW is broken and it affects some people, fortunately not everyone or there'd be even more bricked PS3s.

I didn't update to 4.25 OFW:
1) There isn't content that I'm interested to make the update worthwhile.
2) It's reported to be bricking PS3 consoles.
3) For a chance to have a CFW I decided to stay on 4.21 OFW instead.

[tjhooker73]

Originally Posted by fanboysarestupid Someone who simply pressed "Updated" via their PS3 or downloaded the firmware to the USB and then upgraded the PS3 are doing something wrong? No. 4.25 OFW is broken and it affects some people, fortunately not everyone or there'd be even more bricked PS3s. I didn't update to 4.25 OFW: 1) There isn't content that I'm interested to make the update worthwhile. 2) It's reported to be bricking PS3 consoles. 3) For a chance to have a CFW I decided to stay on 4.21 OFW instead.

I have no Idea what they did while they updated,
They could have gone from 4.20 to 4.25 And thats not a very good idea,
They may have been installing kiosk FW And ****ed up the update,
Frankly I do not give a **** about the people that **** up an update.
************* [ - Post Merged - ] *************
Power surges, internet cutout, Anything could have happened to them while not looking, So do not blame the firmware, If your scared of it then you can still bypass it on 4.21