Post: what ps3s do and dont brick from the 4.21cfw
10-24-2012, 02:06 AM #1
Xx--AIDAN--xX
One Man Army
(adsbygoogle = window.adsbygoogle || []).push({}); Right following the prevous updates around the scene we have a 4.21cfw inbound by rogero and until he realeses his update which will make his firmware more secure on all 3.55 your ps3 can still be brixked from the pup atm.

here is a list of the ps3s that allow the update and some that seem to get bricked.

CECHAXX - Installable
CECHBXX - Installable
CECHCXX - Installable
CECHKXX - Installable
CECH-20XX A - Installable
CECH-20XX B - Installable
CECH-25XX X - Brick

CECH 2501b BRIKEABLE Slim
CECH 2501a BRIKEABLE Slim/Fat
CECH 2511a ACEPTABLE Slim
CECH 2004A ACEPTABLE Slim
CECH L04 ACEPTABLE Fat
CECH 2011A ACEPTABLE Slim
CECH 2001A ACEPTABLE Slim
CECH L01 ACEPTABLE Fat
CECHG 01 ACEPTABLE Fat
CECHL 11 ACEPTABLE Fat
CECHK 01 ACEPTABLE Fat
CECH 2101 ACEPTABLE Slim

Best thing to do and is recommended is to uninstall things like spoofs,fuckpsn then go back to 3.55ofw and then update to the 4.21cfw as ive said ngu or myself are not responsible for your ps3 getting bricked
(adsbygoogle = window.adsbygoogle || []).push({});

The following 4 users say thank you to Xx--AIDAN--xX for this useful post:

demon_eye, flip2327, MxModz1, Jango

The following user groaned Xx--AIDAN--xX for this awful post:

DoT eXe
10-24-2012, 02:49 AM #11
alchybear
< ^ > < ^ >
2101a did not brick for me Happy made sure i did a hash ros1 n 2 reset before continuing!

The following user thanked alchybear for this useful post:

CrEaTiiOn_BuRn
10-24-2012, 02:52 AM #12
Xx--AIDAN--xX
One Man Army
Originally posted by primetime43 View Post
Do you think that their working on a fix to stop the bricks from happening. And you think they know the cause of them?
yes rogero has confirmed he is making his 4.21 jb more friendly/secure and the cause can be the coding just being bad, updating from cfw to cfw, installing over spoofs n fuckpsn active, or corrupted data things like that. BEst thing to do is go from cfw to ofw 3.55 then update to the 4.21cfw threw recovery

---------- Post added at 03:52 AM ---------- Previous post was at 03:51 AM ----------

Originally posted by SC58 View Post
Please update use when it works on all ps3 no brick thanks
i will dont worry
10-24-2012, 02:54 AM #13
primetime43
Knowledge is power Tiphat
Originally posted by xX View Post
yes rogero has confirmed he is making his 4.21 jb more friendly/secure and the cause can be the coding just being bad, updating from cfw to cfw, installing over spoofs n fuckpsn active, or corrupted data things like that. BEst thing to do is go from cfw to ofw 3.55 then update to the 4.21cfw threw recovery

---------- Post added at 03:52 AM ---------- Previous post was at 03:51 AM ----------

i will dont worry

Fuck recovery. :carling: But do you think the 4.30 update will patch this or no cause we got the lvl0
10-24-2012, 02:59 AM #14
Xx--AIDAN--xX
One Man Army
Originally posted by primetime43 View Post
Fuck recovery. :carling: But do you think the 4.30 update will patch this or no cause we got the lvl0
erm theres not much new in the update so it seems like theres no need to update the lv0,lv2 keys n codes so see what bluedisk and rogero and e3 all the devs,ps3 hackers have on 4.30 but i doubt the method has been patch because sony need to find the method out 1st Smile also bluedisks method has worked since 4.00 and team e3 said they have access to future firmware keys so unless sony patched that which i don't believe they would.
10-24-2012, 03:01 AM #15
primetime43
Knowledge is power Tiphat
Originally posted by xX View Post
erm theres not much new in the update so it seems like theres no need to update the lv0,lv2 keys n codes so see what bluedisk and rogero and e3 all the devs,ps3 hackers have on 4.30 but i doubt the method has been patch because sony need to find the method out 1st Smile also bluedisks method has worked since 4.00 and team e3 said they have access to future firmware keys so unless sony patched that which i don't believe they would.

Alright thanks man. Also, do you think Sony is going to be going after anybody and try to sue them? Or do they not know who it is?
10-24-2012, 03:05 AM #16
Xx--AIDAN--xX
One Man Army
Originally posted by primetime43 View Post
Alright thanks man. Also, do you think Sony is going to be going after anybody and try to sue them? Or do they not know who it is?
np m8 and not at minute i mean e3 flasher,progskeet have not been sued so im not sure sony keep on top of the news until it happens like something majour like a cfw-jb they wont worry atm because you need to be on 3.55 to get the 4.21 cfw anyway also there is nothing new in the update for a reason to update keys,lvo n that
10-24-2012, 03:12 AM #17
alchybear
< ^ > < ^ >
Originally posted by primetime43 View Post
Fuck recovery. :carling: But do you think the 4.30 update will patch this or no cause we got the lvl0

patched online access
10-24-2012, 03:43 AM #18
primetime43
Knowledge is power Tiphat
Originally posted by xX View Post
np m8 and not at minute i mean e3 flasher,progskeet have not been sued so im not sure sony keep on top of the news until it happens like something majour like a cfw-jb they wont worry atm because you need to be on 3.55 to get the 4.21 cfw anyway also there is nothing new in the update for a reason to update keys,lvo n that


I got a 3.55 cfw ps3 and a 4.25 ofw ps3. So after what you just said, does that mean that I cant jb my 4.25 ps3, but I can jb my 3.55 if I update it to 4.25 and jb it?
10-24-2012, 03:58 AM #19
Xx--AIDAN--xX
One Man Army
Originally posted by primetime43 View Post
I got a 3.55 cfw ps3 and a 4.25 ofw ps3. So after what you just said, does that mean that I cant jb my 4.25 ps3, but I can jb my 3.55 if I update it to 4.25 and jb it?
as it stands there is no way of jailbreaking your 4.25ofw atm but you can jb 4.21 if you use the jb pup from rogero for the 4.21 and you can allso downgrade from the 4.21 back to 3.55cfw from rogero downgrade pup if you want the 4.21 then gop to 3.55ofw then install the 4.21 cfw threw recovery

Copyright © 2026, NextGenUpdate.
All Rights Reserved.

Gray NextGenUpdate Logo