PS3 [GUIDE] Unbrick a PS3 after an unfortunate PS3Xploit flash

Intruder_911 said:
Hi. I have 43xx model REX-001 board semi bricked Super Slim with 8002f147 error. FW is 4.82. Before it had ODE on board, but now ODE is unistalled also there is no original HDD.The BD data line tiny capasitors are installed back of course. If there is any way revive this board by manual patching 16MB NOR dump. I heard before updating/reinstalling FW it must be changed to BD mode on XMB. But unfortunatly i can't do it because missing ODE and/or orginal HDD. I mean change it to BD mode in Hex editor. There is interesting issue with its dump, everytime even i patch it by dump checker, when i try install system software the ROS0 become corrupted (may be because of 8002f147 on 15%). Thanks.
Click to expand...
I have this same error here but I don't have a solution yet. Could you post your southbridge log?
 
RoboKing's Cosmos said:
According to the above this guy already extracted it but doesn't know how to extract the CoreOS package that is encrypted from Sony inside the PUP file
Click to expand...

My mistake, got lost with some of the messages.

Here are some tools to unpack a PKG file (not all PKGs are unpackable with these tools):
It can also be used PUAD GUI 2.0 (like @RoboKing's Cosmos correctly mentioned) + TrueAncestor for decryp/encrypt the PKG. But I've never got so far playing with PUP's content so I'm not 100% sure it will work.
 
mrg said:
Hi guys,

I have tried to solder the E3 flasher directly to the NOR testpoints under the board.
Unfortunately I have accidentally removed 3 pads (wires were too strong).

Are those pads just interfacing the NOR chip pins, or are they actually in the middle of a track that connects other ICs/components?

If its just the interface to the chip I have no other options than buying a new clip or soldering the wires directly to the chip pads.

motherboard schematics could help. its a KTE-001 board.


thanks in advance!
Click to expand...

were you able to do this on kte-001?
 
Hi guys
Do we have CosOFW for the 4.91?

W7l0uAb.png
 
Hi.
Ihave NPX-001 board with 5FFF error. Turns off after few seconds. The HDD led is blinks. The SouthBridge UART log gives interesting message log before the board turns off. I wonder what means - sysmgr : altering lv0 or lv1 is detected. If this is the problem?

Boot Loader SE Version 4.8.9 (Build ID: 5366,50740, Build Date: 2022-02-04_12:51:26)
SDK Version: 489.000
Copyright(C) 2022 Sony Computer Entertainment Inc.All Rights Reserved.
[INFO]: === eXtreme Data Rate Memory Subsystem ===
[INFO]: (Configured Memory Size per single XIO channel: 128 MBytes.)
[INFO]: XIO channel[0] is available.
[INFO]: XIO channel[1] is available.
[INFO]: ---> Total 256 MBytes are now in use.
[INFO]: SPU enable [0, 1, 2, 5, 6, 7] 11101111
[INFO]: BE:12S DD2.0, SB:ZX1.1
Cell OS SDK4.8.9 000 (release build: r50740 2022_02_04_120000)
Copyright 2022 Sony Computer Entertainment Inc.
revision: 50739
date: Fri Feb 4 12:53:01 JST 2022
sysmgr : altering lv0 or lv1 is detected.
 
Intruder_911 said:
Hi.
Ihave NPX-001 board with 5FFF error. Turns off after few seconds. The HDD led is blinks. The SouthBridge UART log gives interesting message log before the board turns off. I wonder what means - sysmgr : altering lv0 or lv1 is detected. If this is the problem?

Boot Loader SE Version 4.8.9 (Build ID: 5366,50740, Build Date: 2022-02-04_12:51:26)
SDK Version: 489.000
Copyright(C) 2022 Sony Computer Entertainment Inc.All Rights Reserved.
[INFO]: === eXtreme Data Rate Memory Subsystem ===
[INFO]: (Configured Memory Size per single XIO channel: 128 MBytes.)
[INFO]: XIO channel[0] is available.
[INFO]: XIO channel[1] is available.
[INFO]: ---> Total 256 MBytes are now in use.
[INFO]: SPU enable [0, 1, 2, 5, 6, 7] 11101111
[INFO]: BE:12S DD2.0, SB:ZX1.1
Cell OS SDK4.8.9 000 (release build: r50740 2022_02_04_120000)
Copyright 2022 Sony Computer Entertainment Inc.
revision: 50739
date: Fri Feb 4 12:53:01 JST 2022
sysmgr : altering lv0 or lv1 is detected.
Click to expand...
Sounds like coreos hash check fail.. is that with OFW 4.89 CoreOS? Maybe your ros bank doesn't match your coreos
 
Joonie said:
Sounds like coreos hash check fail.. is that with OFW 4.89 CoreOS? Maybe your ros bank doesn't match your coreos
Click to expand...
Hi. The original ROS0 and ROS1 was 4.84 and 4.80 with no error on Ps3dumpchecker. But error was same before i patched it to 4.90, 4,89, 4.88 etc with hope resolve problem. On original CoreOS 4.84 this - sysmgr : altering lv0 or lv1 is detected. - problem was same.
 
Hi people! I'm having a problem that may have to do with this. I installed a new motherboard on my ps3 super slim. I didn't formatted the disk before, which had modified firmware. I think it even had multiman installed? I'm not sure. Now, when I try to turn on ps3, it will be 30 seconds on but after that it will beep 10 times (siren/ambulance sound) and then turn off. I don't know why this happens. It could be that it bricked somehow? I don't even know what brick means. Sound like something got blocked. Here is the video I recorded:

https://youtube.com/shorts/1g4WrcgMFVk?si=zizx2aTIzsRBJMdq

Does this have to do with a bricking thing?
 
Lichi said:
Hi people! I'm having a problem that may have to do with this. I installed a new motherboard on my ps3 super slim. I didn't formatted the disk before, which had modified firmware. I think it even had multiman installed? I'm not sure. Now, when I try to turn on ps3, it will be 30 seconds on but after that it will beep 10 times (siren/ambulance sound) and then turn off. I don't know why this happens. It could be that it bricked somehow? I don't even know what brick means. Sound like something got blocked. Here is the video I recorded:

https://youtube.com/shorts/1g4WrcgMFVk?si=zizx2aTIzsRBJMdq

Does this have to do with a bricking thing?
Click to expand...
I'm not familiar with hardware issues, but a brick is basically when the system won't function. obviously, there are a number of things that can cause that. good luck getting it fixed. I wish I could help.
 
Charles_n_town said:
I'm not familiar with hardware issues, but a brick is basically when the system won't function. obviously, there are a number of things that can cause that. good luck getting it fixed. I wish I could help.
Click to expand...
I understand. But does your comment imply then that it's pretty sure that my problem is not about software such as OS corruption or some kind of block by the ps3 because of detecting modified firmware (software)? If you are pretty sure of that, that would already be a lot of help!
 
Lichi said:
I understand. But does your comment imply then that it's pretty sure that my problem is not about software such as OS corruption or some kind of block by the ps3 because of detecting modified firmware (software)? If you are pretty sure of that, that would already be a lot of help!
Click to expand...
brick is just a general term meaning the system doesn't function like it should. could be software or hardware related.
 
You must log in or register to reply here.

Similar threads

Back
Top