Hello newcomer to the ps3 modding scene, needing help with syscon diagnostic

A

ascendantprime

Forum Noob
I managed to resurrect a ceche01 ps3 from ylod with my hot air station a couple weeks ago and did thermals, and installed hen and eventually evilnat and was getting random crashing during anything intensive with the 3 beeps and i figured it was overheating still and maybe nec tokins are bad, so i delidded a couple days ago and replaced paste under the ihs on the rsx and cell, and it started running great and i could play ps3 games and ps2 games for longer than like 30 mins, it crashed again a couple days ago, thought nothing of it and today i tried booting so i could dump syscon logs to properly diag, and it was ylod again, so i pulled it back apart and reflowed it again(this time with flux i have no idea why i didnt the first time) but i did it without the ihs on both the cell and rsx and so far it is working great.

long story short i dumped the syscon logs and now it is showing me signs not only the rsx is failing but also the nec tokins are failing with 1001, 1002 and also 3034 and 4421 codes, but im also confused as its showing as 2006 being when the codes where thrown, it is a free console that was dead since 2012, should i pray it lasts longer this time, and should i even look into fixing it rather than just get a slim and mod it if both the rsx and tokins need to be replaced? should i wait for it to ylod again to hopefully get a better log? replacing the rsx and tokins are something im capable of doing and have the tools i need like bga rework station at work and all the other soldering stuff i need here at home, but i cant even find 40 or 45nm rsx chips and i dont wanna murder good consoles if im gonna need to spend another 80 bucks on capacitor tantalizer boards. full logs in picture. thankful for any tips yall have.


1778721642474.png
 
Flux was a good move, but the big thing to understand is this:

Without a real preheater, board support/jig, controlled thermal profile, and actually taking the solder into a true liquid state, you're not really doing a proper BGA reflow. You're mostly heat-cycling the board and maybe temporarily restoring a bad connection.

"Reflow" just means bringing solder back to a liquid/wetting state so the pads and balls reconnect properly. That can apply to anything on a PCB — an SMD resistor, capacitor, BGA, RSX, Southbridge, etc. Flux helps reduce oxidation and helps the solder wet the pads, whether you are reinstalling the existing RSX or attaching a new one.

The problem is, with a launch model 90nm RSX, repeated hot-air attempts usually turn into a loop: it works for a little while, crashes again, then needs more heat, and each heat cycle makes the PCB, BGA pads, substrate, and surrounding components worse. Those 90nm chips already have a poor long-term track record, so from a practical repair standpoint I personally treat the original 90nm RSX as bad once it starts showing this kind of behavior.

Technically, 3034 does not always prove the RSX silicon itself is dead. It can be BGA attach, RSX/CELL link training, board damage, or FLEXIO-related. But on a CECHA/CECHB/CECHE with the original 90nm RSX, especially after repeated hot-air revivals and the same faults keep coming back, I would not build the repair plan around trying to preserve that chip.

Flooding flux under the chip can help during removal because it keeps the pads from oxidizing while the chip is coming off. But if the chip is staying on the board, the goal is still the same: the solder balls need to actually reflow. If they do not reach liquid state, you are mostly just stressing the board. With only a hot air wand, that is very hard to do correctly and consistently.

On your syscon codes:

1001 by itself is not something I would chase as a NEC/TOKIN failure. That can be triggered by the power button / shutdown event, so I would not read too far into that one by itself.

3034 is commonly RSX/BGA/link-training related. Again, it does not always mean the RSX die itself is dead, but it usually means the RSX side has a serious connection or communication problem.

4421 can be CELL/RSX/FLEXIO related. Since you also have repeated 3034, I would be looking very hard at the RSX side first.

Before wasting too much time, inspect the RSX and CELL area closely. If the board is bubbled, warped, or the BGA site is damaged, it may not be worth trying to save. If the board looks clean, then proper RSX rework is the better direction.

With repeated 3034/4421 after hot-air "revival," I would not trust that original 90nm RSX. If this was a customer unit or something I wanted reliable, I would plan on RSX replacement first, then deal with anything else only if it remains afterward.

If you just want the console to work and actually be reliable, this is where a Frankenstein RSX swap makes sense. If you are doing it for learning, then by all means keep experimenting — just understand that every heat cycle reduces the odds of that board surviving long-term.
 
iKon said:
Flux was a good move, but the big thing to understand is this:

Without a real preheater, board support/jig, controlled thermal profile, and actually taking the solder into a true liquid state, you're not really doing a proper BGA reflow. You're mostly heat-cycling the board and maybe temporarily restoring a bad connection.

"Reflow" just means bringing solder back to a liquid/wetting state so the pads and balls reconnect properly. That can apply to anything on a PCB — an SMD resistor, capacitor, BGA, RSX, Southbridge, etc. Flux helps reduce oxidation and helps the solder wet the pads, whether you are reinstalling the existing RSX or attaching a new one.

The problem is, with a launch model 90nm RSX, repeated hot-air attempts usually turn into a loop: it works for a little while, crashes again, then needs more heat, and each heat cycle makes the PCB, BGA pads, substrate, and surrounding components worse. Those 90nm chips already have a poor long-term track record, so from a practical repair standpoint I personally treat the original 90nm RSX as bad once it starts showing this kind of behavior.

Technically, 3034 does not always prove the RSX silicon itself is dead. It can be BGA attach, RSX/CELL link training, board damage, or FLEXIO-related. But on a CECHA/CECHB/CECHE with the original 90nm RSX, especially after repeated hot-air revivals and the same faults keep coming back, I would not build the repair plan around trying to preserve that chip.

Flooding flux under the chip can help during removal because it keeps the pads from oxidizing while the chip is coming off. But if the chip is staying on the board, the goal is still the same: the solder balls need to actually reflow. If they do not reach liquid state, you are mostly just stressing the board. With only a hot air wand, that is very hard to do correctly and consistently.

On your syscon codes:

1001 by itself is not something I would chase as a NEC/TOKIN failure. That can be triggered by the power button / shutdown event, so I would not read too far into that one by itself.

3034 is commonly RSX/BGA/link-training related. Again, it does not always mean the RSX die itself is dead, but it usually means the RSX side has a serious connection or communication problem.

4421 can be CELL/RSX/FLEXIO related. Since you also have repeated 3034, I would be looking very hard at the RSX side first.

Before wasting too much time, inspect the RSX and CELL area closely. If the board is bubbled, warped, or the BGA site is damaged, it may not be worth trying to save. If the board looks clean, then proper RSX rework is the better direction.

With repeated 3034/4421 after hot-air "revival," I would not trust that original 90nm RSX. If this was a customer unit or something I wanted reliable, I would plan on RSX replacement first, then deal with anything else only if it remains afterward.

If you just want the console to work and actually be reliable, this is where a Frankenstein RSX swap makes sense. If you are doing it for learning, then by all means keep experimenting — just understand that every heat cycle reduces the odds of that board surviving long-term.
Click to expand...
WOW 10/10 fantastic explanation on those codes. sorry for responding so late i had no idea someone bit on this post. I definitely think the rsx is toast and needs replacement as it works again but sometimes takes 2-3 cycles to actually boot and will still randomly crash and ill have to unplug power etc and i definitely wont be attempting another hot air/heat gun resurrection as i am definitely scared of warping atp especially since i did it this time with no ihs on either of them. I was just more worried about having to also replace the tokins cause those nice little tantalizer boards aint cheap. I think i might try removing some rsxs from dead boards at work with the bga station since ive never really messed with it and try to find a slim/super slim to pull the rsx off of if i cant find any already harvested. do you have any recommendations on where i could possibly find harvested rsx chips? the only ones i can see are the 90nm ones cause it seems like frankensteining is a lot more popular these days.
 
Hello, I am trying to ressurrect my PS3 slim as well. It has a GLOD after replacing the HDMI port. I will attach 2 separate reports.
PS3 MODEL: CECH-2001A
Mobo: DYN-001
first code:

Code: 
Microsoft Windows [Version 10.0.19044.6937]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Administrator\Downloads>pip install pyserial
Collecting pyserial
  Downloading pyserial-3.5-py2.py3-none-any.whl (90 kB)
     |████████████████████████████████| 90 kB 2.7 MB/s
Installing collected packages: pyserial
Successfully installed pyserial-3.5
WARNING: You are using pip version 21.1.1; however, version 26.0.1 is available.
You should consider upgrading via the 'c:\users\administrator\appdata\local\programs\python\python39\python.exe -m pip install --upgrade pip' command.

C:\Users\Administrator\Downloads>pip install pycryptodomex
Collecting pycryptodomex
  Downloading pycryptodomex-3.23.0-cp37-abi3-win_amd64.whl (1.8 MB)
     |████████████████████████████████| 1.8 MB 2.2 MB/s
Installing collected packages: pycryptodomex
Successfully installed pycryptodomex-3.23.0
WARNING: You are using pip version 21.1.1; however, version 26.0.1 is available.
You should consider upgrading via the 'c:\users\administrator\appdata\local\programs\python\python39\python.exe -m pip install --upgrade pip' command.

C:\Users\Administrator\Downloads>ps3_syscon_uart_script.py
ps3_syscon_uart_script.py <serial port> <sc type ["CXR", "CXRF", "SW"]> <Optional:[-l log.txt]>

C:\Users\Administrator\Downloads>ps3_syscon_uart_script.py COM3 SW
Press Ctrl+C to exit
>$ auth
Auth1 response invalid
Press Ctrl+C to exit
>$ AUTH
Auth1 response invalid
Press Ctrl+C to exit
>$ AUTH
Auth1 response invalid
Press Ctrl+C to exit
>$ AUTH
Auth1 response invalid
Press Ctrl+C to exit
>$ auth
Auth1 response invalid
Press Ctrl+C to exit
>$ auth
Auth successful
Press Ctrl+C to exit
>$ r 800 8
00000000
# +0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
# -----------------------------------------------
# 0C EF 0B B5 01 90 F3 38

Press Ctrl+C to exit
>$ powerstate
00000000
# ATA  :OFF
# PCI  :OFF
# PCIex:OFF
# RSX  :OFF
# GDDR :OFF
# XDR  :OFF
# EURUS:OFF
# SB   :OFF
# LAN  :OFF
# WLAN :ON

Press Ctrl+C to exit
>$ errlog
00000000
# CODE     CLOCK
# A0802022 1BD41E2D
# A0802022 1BD41DA7
# A0802022 1BCB2A0A
# A0802022 1BCB2860
# A0802022 1BCB2555
# A0802022 1BCB17A6
# A0802022 1BCB0CE4
# A0802022 1BCAFCB5
# A0802022 1BCAA517
# A0802022 1BCAA4DE
# A0802022 1BC9D759
# A0802022 1BC9D64C
# A0802022 1BC99A83
# A0802022 1BC9921F
# A0802022 1BC990D9
# A0802022 1BC990CF
# A0802022 1BC98FFB
# A0802022 1BC98C80
# A0802022 1BC98B90
# A0802022 1BC98B86
# A0802022 1BC98B43
# A0802022 1BC98B39
# A0802022 14E96B9B
# A0802022 14E9516F
# A0802022 14E82EF8
# A0802022 14E82E96
# A0802022 14E82E1C
# A0802022 14E82D65
# A0802022 14E80C3C
# A0802022 14E80BE1
# A0802130 101440F5

Press Ctrl+C to exit
>$ tmp 0
00000000
# TZone No:00
# Temperature:+0.0(0x0000)

Press Ctrl+C to exit
>$ tmp 1
00000000
# TZone No:01
# Temperature:+0.0(0x0000)

Press Ctrl+C to exit
>$ bringup
00000000
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.

Press Ctrl+C to exit
>$ errlog
00000000
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 3.0.0
#!(Build ID: 3684,41778,
#!Build Date: 2009-08-28_22:53:58)
#!
#!Copyright(C) 2009 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# CODE     CLOCK
# A0802022 1BD41E2D
# A0802022 1BD41DA7
# A0802022 1BCB2A0A
# A0802022 1BCB2860
# A0802022 1BCB2555
# A0802022 1BCB17A6
# A0802022 1BCB0CE4
# A0802022 1BCAFCB5
# A0802022 1BCAA517
# A0802022 1BCAA4DE
# A0802022 1BC9D759
# A0802022 1BC9D64C
# A0802022 1BC99A83
# A0802022 1BC9921F
# A0802022 1BC990D9
# A0802022 1BC990CF
# A0802022 1BC98FFB
# A0802022 1BC98C80
# A0802022 1BC98B90
# A0802022 1BC98B86
# A0802022 1BC98B43
# A0802022 1BC98B39
# A0802022 14E96B9B
# A0802022 14E9516F
# A0802022 14E82EF8
# A0802022 14E82E96
# A0802022 14E82E1C
# A0802022 14E82D65
# A0802022 14E80C3C
# A0802022 14E80BE1
# A0802130 101440F5

Press Ctrl+C to exit
>$ help
00000000
# B_AUTH "AUTH1"
# B_AUTH "AUTH2"
# ANY    "AUTHVER"
# A_AUTH "BOOT"
# A_AUTH "BOOTENABLE"
# A_AUTH "CID"
# A_AUTH "CSAREA"
# A_AUTH "DISABLEALLERASE"
# A_AUTH "ECID"
# A_AUTH "EEP"
# ANY    "ERRLOG"
# A_AUTH "HALT"
# A_AUTH "KSV"
# INT    "LS"
# A_AUTH "PDAREA"
# A_AUTH "R16"
# A_AUTH "R32"
# A_AUTH "R8"
# A_AUTH "REV"
# ANY    "SETCMDLONG"
# A_AUTH "SPU"
# ANY    "VER"
# A_AUTH "VID"
# A_AUTH "W16"
# A_AUTH "W32"
# A_AUTH "W8"
# A_AUTH "bestat"
# A_AUTH "bringup"
# INT    "buzz"
# INT    "buzzduty"
# INT    "cleareep"
# INT    "commt"
# A_AUTH "csum"
# A_AUTH "devpm"
# A_AUTH "duty"
# A_AUTH "eepcsum"
# A_AUTH "ejectsw"
# ANY    "errlog"
# A_AUTH "extend"
# A_AUTH "fanconmode"
# A_AUTH "fanconpolicy"
# A_AUTH "fanservo"
# A_AUTH "fanservostat"
# A_AUTH "fantbl"
# INT    "getrtc"
# A_AUTH "hdmi"
# A_AUTH "help"
# INT    "hversion"
# A_AUTH "hyst"
# INT    "meminfo"
# A_AUTH "nonfatalerror"
# A_AUTH "patchinfo"
# INT    "poll"
# A_AUTH "portscan"
# INT    "portset"
# A_AUTH "powerstate"
# A_AUTH "powersw"
# A_AUTH "powupcause"
# A_AUTH "r"
# A_AUTH "r16"
# A_AUTH "r32"
# A_AUTH "r64"
# A_AUTH "r64d"
# INT    "rbe"
# INT    "recv"
# ANY    "revision"
# INT    "send"
# ANY    "setcmdlong"
# A_AUTH "shutdown"
# A_AUTH "syspowdown"
# INT    "task"
# A_AUTH "thrm"
# A_AUTH "tmp"
# A_AUTH "trp"
# A_AUTH "tsensor"
# A_AUTH "tshutdown"
# A_AUTH "tzone"
# ANY    "version"
# A_AUTH "w"
# A_AUTH "w16"
# A_AUTH "w32"
# A_AUTH "w64"
# A_AUTH "wbe"

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] Shutdown Start.
# [SSM] Shutdown ok.
# (PowerOff State)

Press Ctrl+C to exit
>$ powersw
00000000
# [SSM] Bringup Start.
OK 00000000
# [SSM] PS0 ok.
# [SSM] PS1 ok.

Press Ctrl+C to exit
>$

Second code:
Code: 
Microsoft Windows [Version 10.0.19044.6937]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Administrator\Downloads>ps3_syscon_uart_script.py
ps3_syscon_uart_script.py <serial port> <sc type ["CXR", "CXRF", "SW"]> <Optional:[-l log.txt]>

C:\Users\Administrator\Downloads>ps3_syscon_uart_script.py COM3 SW
Press Ctrl+C to exit
>$ auth
Auth successful
Press Ctrl+C to exit
>$ errlog
00000000
# CODE     CLOCK
# A0802022 1BD41E2D
# A0802022 1BD41DA7
# A0802022 1BCB2A0A
# A0802022 1BCB2860
# A0802022 1BCB2555
# A0802022 1BCB17A6
# A0802022 1BCB0CE4
# A0802022 1BCAFCB5
# A0802022 1BCAA517
# A0802022 1BCAA4DE
# A0802022 1BC9D759
# A0802022 1BC9D64C
# A0802022 1BC99A83
# A0802022 1BC9921F
# A0802022 1BC990D9
# A0802022 1BC990CF
# A0802022 1BC98FFB
# A0802022 1BC98C80
# A0802022 1BC98B90
# A0802022 1BC98B86
# A0802022 1BC98B43
# A0802022 1BC98B39
# A0802022 14E96B9B
# A0802022 14E9516F
# A0802022 14E82EF8
# A0802022 14E82E96
# A0802022 14E82E1C
# A0802022 14E82D65
# A0802022 14E80C3C
# A0802022 14E80BE1
# A0802130 101440F5

Press Ctrl+C to exit
>$ help
00000000
# B_AUTH "AUTH1"
# B_AUTH "AUTH2"
# ANY    "AUTHVER"
# A_AUTH "BOOT"
# A_AUTH "BOOTENABLE"
# A_AUTH "CID"
# A_AUTH "CSAREA"
# A_AUTH "DISABLEALLERASE"
# A_AUTH "ECID"
# A_AUTH "EEP"
# ANY    "ERRLOG"
# A_AUTH "HALT"
# A_AUTH "KSV"
# INT    "LS"
# A_AUTH "PDAREA"
# A_AUTH "R16"
# A_AUTH "R32"
# A_AUTH "R8"
# A_AUTH "REV"
# ANY    "SETCMDLONG"
# A_AUTH "SPU"
# ANY    "VER"
# A_AUTH "VID"
# A_AUTH "W16"
# A_AUTH "W32"
# A_AUTH "W8"
# A_AUTH "bestat"
# A_AUTH "bringup"
# INT    "buzz"
# INT    "buzzduty"
# INT    "cleareep"
# INT    "commt"
# A_AUTH "csum"
# A_AUTH "devpm"
# A_AUTH "duty"
# A_AUTH "eepcsum"
# A_AUTH "ejectsw"
# ANY    "errlog"
# A_AUTH "extend"
# A_AUTH "fanconmode"
# A_AUTH "fanconpolicy"
# A_AUTH "fanservo"
# A_AUTH "fanservostat"
# A_AUTH "fantbl"
# INT    "getrtc"
# A_AUTH "hdmi"
# A_AUTH "help"
# INT    "hversion"
# A_AUTH "hyst"
# INT    "meminfo"
# A_AUTH "nonfatalerror"
# A_AUTH "patchinfo"
# INT    "poll"
# A_AUTH "portscan"
# INT    "portset"
# A_AUTH "powerstate"
# A_AUTH "powersw"
# A_AUTH "powupcause"
# A_AUTH "r"
# A_AUTH "r16"
# A_AUTH "r32"
# A_AUTH "r64"
# A_AUTH "r64d"
# INT    "rbe"
# INT    "recv"
# ANY    "revision"
# INT    "send"
# ANY    "setcmdlong"
# A_AUTH "shutdown"
# A_AUTH "syspowdown"
# INT    "task"
# A_AUTH "thrm"
# A_AUTH "tmp"
# A_AUTH "trp"
# A_AUTH "tsensor"
# A_AUTH "tshutdown"
# A_AUTH "tzone"
# ANY    "version"
# A_AUTH "w"
# A_AUTH "w16"
# A_AUTH "w32"
# A_AUTH "w64"
# A_AUTH "wbe"

Press Ctrl+C to exit
>$ bringup
00000000
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.

Press Ctrl+C to exit
>$ errlog
00000000
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 3.0.0
#!(Build ID: 3684,41778,
#!Build Date: 2009-08-28_22:53:58)
#!
#!Copyright(C) 2009 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [SSM] Cond/Fatal received, msg=2687.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# CODE     CLOCK
# A0801200 0B49D822
# A0802022 1BD41E2D
# A0802022 1BD41DA7
# A0802022 1BCB2A0A
# A0802022 1BCB2860
# A0802022 1BCB2555
# A0802022 1BCB17A6
# A0802022 1BCB0CE4
# A0802022 1BCAFCB5
# A0802022 1BCAA517
# A0802022 1BCAA4DE
# A0802022 1BC9D759
# A0802022 1BC9D64C
# A0802022 1BC99A83
# A0802022 1BC9921F
# A0802022 1BC990D9
# A0802022 1BC990CF
# A0802022 1BC98FFB
# A0802022 1BC98C80
# A0802022 1BC98B90
# A0802022 1BC98B86
# A0802022 1BC98B43
# A0802022 1BC98B39
# A0802022 14E96B9B
# A0802022 14E9516F
# A0802022 14E82EF8
# A0802022 14E82E96
# A0802022 14E82E1C
# A0802022 14E82D65
# A0802022 14E80C3C
# A0802022 14E80BE1

Press Ctrl+C to exit
>$ bringup
FFFFA605

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Press Ctrl+C to exit
>$ powersw
00000000
# [SSM] Bringup Start.
OK 00000000
# [SSM] PS0 ok.
# [SSM] PS1 ok.

Press Ctrl+C to exit
>$ errlog
00000000
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
#!
#!Boot Loader SE Version 3.0.0
#!(Build ID: 3684,41778,
#!Build Date: 2009-08-28_22:53:58)
#!
#!Copyright(C) 2009 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [SSM] Cond/Fatal received, msg=2687.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# CODE     CLOCK
# A0801200 0B49D8C1
# A0801200 0B49D822
# A0802022 1BD41E2D
# A0802022 1BD41DA7
# A0802022 1BCB2A0A
# A0802022 1BCB2860
# A0802022 1BCB2555
# A0802022 1BCB17A6
# A0802022 1BCB0CE4
# A0802022 1BCAFCB5
# A0802022 1BCAA517
# A0802022 1BCAA4DE
# A0802022 1BC9D759
# A0802022 1BC9D64C
# A0802022 1BC99A83
# A0802022 1BC9921F
# A0802022 1BC990D9
# A0802022 1BC990CF
# A0802022 1BC98FFB
# A0802022 1BC98C80
# A0802022 1BC98B90
# A0802022 1BC98B86
# A0802022 1BC98B43
# A0802022 1BC98B39
# A0802022 14E96B9B
# A0802022 14E9516F
# A0802022 14E82EF8
# A0802022 14E82E96
# A0802022 14E82E1C
# A0802022 14E82D65
# A0802022 14E80C3C

Press Ctrl+C to exit
>$ cleareep
F0000003
# [UCMD] Unknown command.

Press Ctrl+C to exit
>$ bestat
00000000
# (Error State) (Fatal)
# State = 07

Press Ctrl+C to exit
>$ hdmi
FFFFA603
# [HDMI] Unknown Sub Command.hdmi

Press Ctrl+C to exit
>$ powupcause
00000000
# BE is not ON.

Press Ctrl+C to exit
>$
 
Last edited:
Komotonoto said:
Hello, I am trying to ressurrect my PS3 slim as well. It has a GLOD after replacing the HDMI port. I will attach 2 separate reports.
PS3 MODEL: CECH-2001A
Mobo: DYN-001
first code:

Code: 
Microsoft Windows [Version 10.0.19044.6937]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Administrator\Downloads>pip install pyserial
Collecting pyserial
  Downloading pyserial-3.5-py2.py3-none-any.whl (90 kB)
     |████████████████████████████████| 90 kB 2.7 MB/s
Installing collected packages: pyserial
Successfully installed pyserial-3.5
WARNING: You are using pip version 21.1.1; however, version 26.0.1 is available.
You should consider upgrading via the 'c:\users\administrator\appdata\local\programs\python\python39\python.exe -m pip install --upgrade pip' command.

C:\Users\Administrator\Downloads>pip install pycryptodomex
Collecting pycryptodomex
  Downloading pycryptodomex-3.23.0-cp37-abi3-win_amd64.whl (1.8 MB)
     |████████████████████████████████| 1.8 MB 2.2 MB/s
Installing collected packages: pycryptodomex
Successfully installed pycryptodomex-3.23.0
WARNING: You are using pip version 21.1.1; however, version 26.0.1 is available.
You should consider upgrading via the 'c:\users\administrator\appdata\local\programs\python\python39\python.exe -m pip install --upgrade pip' command.

C:\Users\Administrator\Downloads>ps3_syscon_uart_script.py
ps3_syscon_uart_script.py <serial port> <sc type ["CXR", "CXRF", "SW"]> <Optional:[-l log.txt]>

C:\Users\Administrator\Downloads>ps3_syscon_uart_script.py COM3 SW
Press Ctrl+C to exit
>$ auth
Auth1 response invalid
Press Ctrl+C to exit
>$ AUTH
Auth1 response invalid
Press Ctrl+C to exit
>$ AUTH
Auth1 response invalid
Press Ctrl+C to exit
>$ AUTH
Auth1 response invalid
Press Ctrl+C to exit
>$ auth
Auth1 response invalid
Press Ctrl+C to exit
>$ auth
Auth successful
Press Ctrl+C to exit
>$ r 800 8
00000000
# +0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
# -----------------------------------------------
# 0C EF 0B B5 01 90 F3 38

Press Ctrl+C to exit
>$ powerstate
00000000
# ATA  :OFF
# PCI  :OFF
# PCIex:OFF
# RSX  :OFF
# GDDR :OFF
# XDR  :OFF
# EURUS:OFF
# SB   :OFF
# LAN  :OFF
# WLAN :ON

Press Ctrl+C to exit
>$ errlog
00000000
# CODE     CLOCK
# A0802022 1BD41E2D
# A0802022 1BD41DA7
# A0802022 1BCB2A0A
# A0802022 1BCB2860
# A0802022 1BCB2555
# A0802022 1BCB17A6
# A0802022 1BCB0CE4
# A0802022 1BCAFCB5
# A0802022 1BCAA517
# A0802022 1BCAA4DE
# A0802022 1BC9D759
# A0802022 1BC9D64C
# A0802022 1BC99A83
# A0802022 1BC9921F
# A0802022 1BC990D9
# A0802022 1BC990CF
# A0802022 1BC98FFB
# A0802022 1BC98C80
# A0802022 1BC98B90
# A0802022 1BC98B86
# A0802022 1BC98B43
# A0802022 1BC98B39
# A0802022 14E96B9B
# A0802022 14E9516F
# A0802022 14E82EF8
# A0802022 14E82E96
# A0802022 14E82E1C
# A0802022 14E82D65
# A0802022 14E80C3C
# A0802022 14E80BE1
# A0802130 101440F5

Press Ctrl+C to exit
>$ tmp 0
00000000
# TZone No:00
# Temperature:+0.0(0x0000)

Press Ctrl+C to exit
>$ tmp 1
00000000
# TZone No:01
# Temperature:+0.0(0x0000)

Press Ctrl+C to exit
>$ bringup
00000000
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.

Press Ctrl+C to exit
>$ errlog
00000000
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 3.0.0
#!(Build ID: 3684,41778,
#!Build Date: 2009-08-28_22:53:58)
#!
#!Copyright(C) 2009 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# CODE     CLOCK
# A0802022 1BD41E2D
# A0802022 1BD41DA7
# A0802022 1BCB2A0A
# A0802022 1BCB2860
# A0802022 1BCB2555
# A0802022 1BCB17A6
# A0802022 1BCB0CE4
# A0802022 1BCAFCB5
# A0802022 1BCAA517
# A0802022 1BCAA4DE
# A0802022 1BC9D759
# A0802022 1BC9D64C
# A0802022 1BC99A83
# A0802022 1BC9921F
# A0802022 1BC990D9
# A0802022 1BC990CF
# A0802022 1BC98FFB
# A0802022 1BC98C80
# A0802022 1BC98B90
# A0802022 1BC98B86
# A0802022 1BC98B43
# A0802022 1BC98B39
# A0802022 14E96B9B
# A0802022 14E9516F
# A0802022 14E82EF8
# A0802022 14E82E96
# A0802022 14E82E1C
# A0802022 14E82D65
# A0802022 14E80C3C
# A0802022 14E80BE1
# A0802130 101440F5

Press Ctrl+C to exit
>$ help
00000000
# B_AUTH "AUTH1"
# B_AUTH "AUTH2"
# ANY    "AUTHVER"
# A_AUTH "BOOT"
# A_AUTH "BOOTENABLE"
# A_AUTH "CID"
# A_AUTH "CSAREA"
# A_AUTH "DISABLEALLERASE"
# A_AUTH "ECID"
# A_AUTH "EEP"
# ANY    "ERRLOG"
# A_AUTH "HALT"
# A_AUTH "KSV"
# INT    "LS"
# A_AUTH "PDAREA"
# A_AUTH "R16"
# A_AUTH "R32"
# A_AUTH "R8"
# A_AUTH "REV"
# ANY    "SETCMDLONG"
# A_AUTH "SPU"
# ANY    "VER"
# A_AUTH "VID"
# A_AUTH "W16"
# A_AUTH "W32"
# A_AUTH "W8"
# A_AUTH "bestat"
# A_AUTH "bringup"
# INT    "buzz"
# INT    "buzzduty"
# INT    "cleareep"
# INT    "commt"
# A_AUTH "csum"
# A_AUTH "devpm"
# A_AUTH "duty"
# A_AUTH "eepcsum"
# A_AUTH "ejectsw"
# ANY    "errlog"
# A_AUTH "extend"
# A_AUTH "fanconmode"
# A_AUTH "fanconpolicy"
# A_AUTH "fanservo"
# A_AUTH "fanservostat"
# A_AUTH "fantbl"
# INT    "getrtc"
# A_AUTH "hdmi"
# A_AUTH "help"
# INT    "hversion"
# A_AUTH "hyst"
# INT    "meminfo"
# A_AUTH "nonfatalerror"
# A_AUTH "patchinfo"
# INT    "poll"
# A_AUTH "portscan"
# INT    "portset"
# A_AUTH "powerstate"
# A_AUTH "powersw"
# A_AUTH "powupcause"
# A_AUTH "r"
# A_AUTH "r16"
# A_AUTH "r32"
# A_AUTH "r64"
# A_AUTH "r64d"
# INT    "rbe"
# INT    "recv"
# ANY    "revision"
# INT    "send"
# ANY    "setcmdlong"
# A_AUTH "shutdown"
# A_AUTH "syspowdown"
# INT    "task"
# A_AUTH "thrm"
# A_AUTH "tmp"
# A_AUTH "trp"
# A_AUTH "tsensor"
# A_AUTH "tshutdown"
# A_AUTH "tzone"
# ANY    "version"
# A_AUTH "w"
# A_AUTH "w16"
# A_AUTH "w32"
# A_AUTH "w64"
# A_AUTH "wbe"

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] Shutdown Start.
# [SSM] Shutdown ok.
# (PowerOff State)

Press Ctrl+C to exit
>$ powersw
00000000
# [SSM] Bringup Start.
OK 00000000
# [SSM] PS0 ok.
# [SSM] PS1 ok.

Press Ctrl+C to exit
>$

Second code:
Code: 
Microsoft Windows [Version 10.0.19044.6937]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Administrator\Downloads>ps3_syscon_uart_script.py
ps3_syscon_uart_script.py <serial port> <sc type ["CXR", "CXRF", "SW"]> <Optional:[-l log.txt]>

C:\Users\Administrator\Downloads>ps3_syscon_uart_script.py COM3 SW
Press Ctrl+C to exit
>$ auth
Auth successful
Press Ctrl+C to exit
>$ errlog
00000000
# CODE     CLOCK
# A0802022 1BD41E2D
# A0802022 1BD41DA7
# A0802022 1BCB2A0A
# A0802022 1BCB2860
# A0802022 1BCB2555
# A0802022 1BCB17A6
# A0802022 1BCB0CE4
# A0802022 1BCAFCB5
# A0802022 1BCAA517
# A0802022 1BCAA4DE
# A0802022 1BC9D759
# A0802022 1BC9D64C
# A0802022 1BC99A83
# A0802022 1BC9921F
# A0802022 1BC990D9
# A0802022 1BC990CF
# A0802022 1BC98FFB
# A0802022 1BC98C80
# A0802022 1BC98B90
# A0802022 1BC98B86
# A0802022 1BC98B43
# A0802022 1BC98B39
# A0802022 14E96B9B
# A0802022 14E9516F
# A0802022 14E82EF8
# A0802022 14E82E96
# A0802022 14E82E1C
# A0802022 14E82D65
# A0802022 14E80C3C
# A0802022 14E80BE1
# A0802130 101440F5

Press Ctrl+C to exit
>$ help
00000000
# B_AUTH "AUTH1"
# B_AUTH "AUTH2"
# ANY    "AUTHVER"
# A_AUTH "BOOT"
# A_AUTH "BOOTENABLE"
# A_AUTH "CID"
# A_AUTH "CSAREA"
# A_AUTH "DISABLEALLERASE"
# A_AUTH "ECID"
# A_AUTH "EEP"
# ANY    "ERRLOG"
# A_AUTH "HALT"
# A_AUTH "KSV"
# INT    "LS"
# A_AUTH "PDAREA"
# A_AUTH "R16"
# A_AUTH "R32"
# A_AUTH "R8"
# A_AUTH "REV"
# ANY    "SETCMDLONG"
# A_AUTH "SPU"
# ANY    "VER"
# A_AUTH "VID"
# A_AUTH "W16"
# A_AUTH "W32"
# A_AUTH "W8"
# A_AUTH "bestat"
# A_AUTH "bringup"
# INT    "buzz"
# INT    "buzzduty"
# INT    "cleareep"
# INT    "commt"
# A_AUTH "csum"
# A_AUTH "devpm"
# A_AUTH "duty"
# A_AUTH "eepcsum"
# A_AUTH "ejectsw"
# ANY    "errlog"
# A_AUTH "extend"
# A_AUTH "fanconmode"
# A_AUTH "fanconpolicy"
# A_AUTH "fanservo"
# A_AUTH "fanservostat"
# A_AUTH "fantbl"
# INT    "getrtc"
# A_AUTH "hdmi"
# A_AUTH "help"
# INT    "hversion"
# A_AUTH "hyst"
# INT    "meminfo"
# A_AUTH "nonfatalerror"
# A_AUTH "patchinfo"
# INT    "poll"
# A_AUTH "portscan"
# INT    "portset"
# A_AUTH "powerstate"
# A_AUTH "powersw"
# A_AUTH "powupcause"
# A_AUTH "r"
# A_AUTH "r16"
# A_AUTH "r32"
# A_AUTH "r64"
# A_AUTH "r64d"
# INT    "rbe"
# INT    "recv"
# ANY    "revision"
# INT    "send"
# ANY    "setcmdlong"
# A_AUTH "shutdown"
# A_AUTH "syspowdown"
# INT    "task"
# A_AUTH "thrm"
# A_AUTH "tmp"
# A_AUTH "trp"
# A_AUTH "tsensor"
# A_AUTH "tshutdown"
# A_AUTH "tzone"
# ANY    "version"
# A_AUTH "w"
# A_AUTH "w16"
# A_AUTH "w32"
# A_AUTH "w64"
# A_AUTH "wbe"

Press Ctrl+C to exit
>$ bringup
00000000
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.

Press Ctrl+C to exit
>$ errlog
00000000
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 3.0.0
#!(Build ID: 3684,41778,
#!Build Date: 2009-08-28_22:53:58)
#!
#!Copyright(C) 2009 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [SSM] Cond/Fatal received, msg=2687.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# CODE     CLOCK
# A0801200 0B49D822
# A0802022 1BD41E2D
# A0802022 1BD41DA7
# A0802022 1BCB2A0A
# A0802022 1BCB2860
# A0802022 1BCB2555
# A0802022 1BCB17A6
# A0802022 1BCB0CE4
# A0802022 1BCAFCB5
# A0802022 1BCAA517
# A0802022 1BCAA4DE
# A0802022 1BC9D759
# A0802022 1BC9D64C
# A0802022 1BC99A83
# A0802022 1BC9921F
# A0802022 1BC990D9
# A0802022 1BC990CF
# A0802022 1BC98FFB
# A0802022 1BC98C80
# A0802022 1BC98B90
# A0802022 1BC98B86
# A0802022 1BC98B43
# A0802022 1BC98B39
# A0802022 14E96B9B
# A0802022 14E9516F
# A0802022 14E82EF8
# A0802022 14E82E96
# A0802022 14E82E1C
# A0802022 14E82D65
# A0802022 14E80C3C
# A0802022 14E80BE1

Press Ctrl+C to exit
>$ bringup
FFFFA605

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Press Ctrl+C to exit
>$ powersw
00000000
# [SSM] Bringup Start.
OK 00000000
# [SSM] PS0 ok.
# [SSM] PS1 ok.

Press Ctrl+C to exit
>$ errlog
00000000
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
#!
#!Boot Loader SE Version 3.0.0
#!(Build ID: 3684,41778,
#!Build Date: 2009-08-28_22:53:58)
#!
#!Copyright(C) 2009 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [SSM] Cond/Fatal received, msg=2687.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# CODE     CLOCK
# A0801200 0B49D8C1
# A0801200 0B49D822
# A0802022 1BD41E2D
# A0802022 1BD41DA7
# A0802022 1BCB2A0A
# A0802022 1BCB2860
# A0802022 1BCB2555
# A0802022 1BCB17A6
# A0802022 1BCB0CE4
# A0802022 1BCAFCB5
# A0802022 1BCAA517
# A0802022 1BCAA4DE
# A0802022 1BC9D759
# A0802022 1BC9D64C
# A0802022 1BC99A83
# A0802022 1BC9921F
# A0802022 1BC990D9
# A0802022 1BC990CF
# A0802022 1BC98FFB
# A0802022 1BC98C80
# A0802022 1BC98B90
# A0802022 1BC98B86
# A0802022 1BC98B43
# A0802022 1BC98B39
# A0802022 14E96B9B
# A0802022 14E9516F
# A0802022 14E82EF8
# A0802022 14E82E96
# A0802022 14E82E1C
# A0802022 14E82D65
# A0802022 14E80C3C

Press Ctrl+C to exit
>$ cleareep
F0000003
# [UCMD] Unknown command.

Press Ctrl+C to exit
>$ bestat
00000000
# (Error State) (Fatal)
# State = 07

Press Ctrl+C to exit
>$ hdmi
FFFFA603
# [HDMI] Unknown Sub Command.hdmi

Press Ctrl+C to exit
>$ powupcause
00000000
# BE is not ON.

Press Ctrl+C to exit
>$
Click to expand...
check under a microscope or zoom in with a good phone camera if unavailable to see if you have any shorts on the pins, if not try the hdmi ic encoder
 
ascendantprime said:
check under a microscope or zoom in with a good phone camera if unavailable to see if you have any shorts on the pins, if not try the hdmi ic encoder
Click to expand...
Ello, what is the HDMI IC encoder? Are you saying I should swap out the HDMI IC encoder chip? Or are you saying I should get a HDMI port tester?

Thanks.
 
ascendantprime said:
yes check none of the pins on the new port are bridged and if they are fine try swapping the hdmi encoder ic chip
Click to expand...
I actually have a question about that. I did notice some of the pins on the HDMI are shorted to GND, but I don't have another PS3 to compare it with.

Are you saying that none of the HDMI pins should be shorted to ground on the PS3 mobo?

I looked at the HDMI pinout diagram, but I don't know what pins are shorted to ground WHEN the HDMI connector is on the PS3 motherboard.
 
Komotonoto said:
I actually have a question about that. I did notice some of the pins on the HDMI are shorted to GND, but I don't have another PS3 to compare it with.

Are you saying that none of the HDMI pins should be shorted to ground on the PS3 mobo?

I looked at the HDMI pinout diagram, but I don't know what pins are shorted to ground WHEN the HDMI connector is on the PS3 motherboard.
Click to expand...
not 100% sure but if youre unsure about the port itself my method for hdmi ports work great for 99% of consoles and super easy, would be way easier to just try the port again and see if it still has the ylod issue then pursue the hdmi ic or other things. try hot swap method, heat gun on bottom and hot air on top in a semicircle around the port almost flush with the top, port should come loose easy since you have heat through both sides of the board, as the port comes off, flux the anchor holes, keep heating with hot air and put some more solder in each of the holes( i prefer 63% and you dont have to wick out old solder just add a little more so it melts easier) remove all heat and while the board is still hot put more flux on the pads for the hdmi pins and add more solder to that, I will tin my new hdmi first with some flux and a quick pass of the iron with a ball of solder on the end(i usually do this first before even touching the board so its ready but make sure you have no bridges here this is the easiest point to mess up) and once youve added the new solder, reheat from both sides till youre ready, grab your port with some tweezers and drop it in the holes, kinda tap it from the back side to bring the port towards you so it aligns in the holes and you dont risk pins touching other pads, keep heat on the back side where the pins are for like 3-5 more seconds while pushing the top of the port down with tweezers and then squirt 99% iso alcohol into the port and around it on the board or just wait till it cools naturally. have done several hundred consoles at my shop with this method and never had an issue, I have access to a microscope and can check for bridges and loose pins by pushing/raking them with precision tweezers but with this method most of the time i dont even have to push them to make sure since they are embedded in the solder on the pads most of the time not just laying on top like i see a lot of ppl doing
 
ascendantprime said:
not 100% sure but if youre unsure about the port itself my method for hdmi ports work great for 99% of consoles and super easy, would be way easier to just try the port again and see if it still has the ylod issue then pursue the hdmi ic or other things. try hot swap method, heat gun on bottom and hot air on top in a semicircle around the port almost flush with the top, port should come loose easy since you have heat through both sides of the board, as the port comes off, flux the anchor holes, keep heating with hot air and put some more solder in each of the holes( i prefer 63% and you dont have to wick out old solder just add a little more so it melts easier) remove all heat and while the board is still hot put more flux on the pads for the hdmi pins and add more solder to that, I will tin my new hdmi first with some flux and a quick pass of the iron with a ball of solder on the end(i usually do this first before even touching the board so its ready but make sure you have no bridges here this is the easiest point to mess up) and once youve added the new solder, reheat from both sides till youre ready, grab your port with some tweezers and drop it in the holes, kinda tap it from the back side to bring the port towards you so it aligns in the holes and you dont risk pins touching other pads, keep heat on the back side where the pins are for like 3-5 more seconds while pushing the top of the port down with tweezers and then squirt 99% iso alcohol into the port and around it on the board or just wait till it cools naturally. have done several hundred consoles at my shop with this method and never had an issue, I have access to a microscope and can check for bridges and loose pins by pushing/raking them with precision tweezers but with this method most of the time i dont even have to push them to make sure since they are embedded in the solder on the pads most of the time not just laying on top like i see a lot of ppl doing
Click to expand...
Ello, thanks for replying!

So I managed to remove the HDMI port, and recorded the resistance/impedance in respect to ground.

Pins inside black boxes are shorted to GND (0 ohms)
Everything else is OL (open - no connection)
5292.jpg


Here are photos of HDMI port after port removal (top and bottom layer). Adding them just because.
Bottom:
5290.jpg

Top:
5291.jpg


Thanks for your help!

Update:
With HDMI port removed, it seems to have made no difference.

I booted into safe mode, but I get the same symptoms, no video, and my ps3 controller cannot sync to the console when plugged into the MOBO.

Code notes: I attempted to run bringup/errlog during safemode, but it didnt give out much info.
so then I used "shutdown/powersw" to turn it off. Then I ran "bringup" followed by a "errlog" to give me more info.
remaining commands are there in case they are needed.

Code: 
Microsoft Windows [Version 10.0.19044.7417]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Administrator\Downloads>ps3_syscon_uart_script.py
ps3_syscon_uart_script.py <serial port> <sc type ["CXR", "CXRF", "SW"]> <Optional:[-l log.txt]>

C:\Users\Administrator\Downloads>ps3_syscon_uart_script.py COM3 SW
Press Ctrl+C to exit
>$ auth
Auth successful
Press Ctrl+C to exit
>$ errlog
00000000
# CODE     CLOCK
# A0801200 0B49DD12
# A0801200 0B49DC7B
# A0801200 0B49D8C1
# A0801200 0B49D822
# A0802022 1BD41E2D
# A0802022 1BD41DA7
# A0802022 1BCB2A0A
# A0802022 1BCB2860
# A0802022 1BCB2555
# A0802022 1BCB17A6
# A0802022 1BCB0CE4
# A0802022 1BCAFCB5
# A0802022 1BCAA517
# A0802022 1BCAA4DE
# A0802022 1BC9D759
# A0802022 1BC9D64C
# A0802022 1BC99A83
# A0802022 1BC9921F
# A0802022 1BC990D9
# A0802022 1BC990CF
# A0802022 1BC98FFB
# A0802022 1BC98C80
# A0802022 1BC98B90
# A0802022 1BC98B86
# A0802022 1BC98B43
# A0802022 1BC98B39
# A0802022 14E96B9B
# A0802022 14E9516F
# A0802022 14E82EF8
# A0802022 14E82E96
# A0802022 14E82E1C

Press Ctrl+C to exit
>$ bringup
FFFFA605

Press Ctrl+C to exit
>$ errlog
00000000
# CODE     CLOCK
# A0801200 0B49DD12
# A0801200 0B49DC7B
# A0801200 0B49D8C1
# A0801200 0B49D822
# A0802022 1BD41E2D
# A0802022 1BD41DA7
# A0802022 1BCB2A0A
# A0802022 1BCB2860
# A0802022 1BCB2555
# A0802022 1BCB17A6
# A0802022 1BCB0CE4
# A0802022 1BCAFCB5
# A0802022 1BCAA517
# A0802022 1BCAA4DE
# A0802022 1BC9D759
# A0802022 1BC9D64C
# A0802022 1BC99A83
# A0802022 1BC9921F
# A0802022 1BC990D9
# A0802022 1BC990CF
# A0802022 1BC98FFB
# A0802022 1BC98C80
# A0802022 1BC98B90
# A0802022 1BC98B86
# A0802022 1BC98B43
# A0802022 1BC98B39
# A0802022 14E96B9B
# A0802022 14E9516F
# A0802022 14E82EF8
# A0802022 14E82E96
# A0802022 14E82E1C

Press Ctrl+C to exit
>$ powersw
00000000

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] Shutdown Start.
# [SSM] Shutdown ok.
# (PowerOff State)

Press Ctrl+C to exit
>$ errlog
00000000
# CODE     CLOCK
# A0801200 0B49DD12
# A0801200 0B49DC7B
# A0801200 0B49D8C1
# A0801200 0B49D822
# A0802022 1BD41E2D
# A0802022 1BD41DA7
# A0802022 1BCB2A0A
# A0802022 1BCB2860
# A0802022 1BCB2555
# A0802022 1BCB17A6
# A0802022 1BCB0CE4
# A0802022 1BCAFCB5
# A0802022 1BCAA517
# A0802022 1BCAA4DE
# A0802022 1BC9D759
# A0802022 1BC9D64C
# A0802022 1BC99A83
# A0802022 1BC9921F
# A0802022 1BC990D9
# A0802022 1BC990CF
# A0802022 1BC98FFB
# A0802022 1BC98C80
# A0802022 1BC98B90
# A0802022 1BC98B86
# A0802022 1BC98B43
# A0802022 1BC98B39
# A0802022 14E96B9B
# A0802022 14E9516F
# A0802022 14E82EF8
# A0802022 14E82E96
# A0802022 14E82E1C

Press Ctrl+C to exit
>$ errlog
00000000
# CODE     CLOCK
# A0801200 0B49DD12
# A0801200 0B49DC7B
# A0801200 0B49D8C1
# A0801200 0B49D822
# A0802022 1BD41E2D
# A0802022 1BD41DA7
# A0802022 1BCB2A0A
# A0802022 1BCB2860
# A0802022 1BCB2555
# A0802022 1BCB17A6
# A0802022 1BCB0CE4
# A0802022 1BCAFCB5
# A0802022 1BCAA517
# A0802022 1BCAA4DE
# A0802022 1BC9D759
# A0802022 1BC9D64C
# A0802022 1BC99A83
# A0802022 1BC9921F
# A0802022 1BC990D9
# A0802022 1BC990CF
# A0802022 1BC98FFB
# A0802022 1BC98C80
# A0802022 1BC98B90
# A0802022 1BC98B86
# A0802022 1BC98B43
# A0802022 1BC98B39
# A0802022 14E96B9B
# A0802022 14E9516F
# A0802022 14E82EF8
# A0802022 14E82E96
# A0802022 14E82E1C

Press Ctrl+C to exit
>$ bringup
00000000
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.

Press Ctrl+C to exit
>$ errlog
00000000
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 3.0.0
#!(Build ID: 3684,41778,
#!Build Date: 2009-08-28_22:53:58)
#!
#!Copyright(C) 2009 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# CODE     CLOCK
# A0801200 0B49DD12
# A0801200 0B49DC7B
# A0801200 0B49D8C1
# A0801200 0B49D822
# A0802022 1BD41E2D
# A0802022 1BD41DA7
# A0802022 1BCB2A0A
# A0802022 1BCB2860
# A0802022 1BCB2555
# A0802022 1BCB17A6
# A0802022 1BCB0CE4
# A0802022 1BCAFCB5
# A0802022 1BCAA517
# A0802022 1BCAA4DE
# A0802022 1BC9D759
# A0802022 1BC9D64C
# A0802022 1BC99A83
# A0802022 1BC9921F
# A0802022 1BC990D9
# A0802022 1BC990CF
# A0802022 1BC98FFB
# A0802022 1BC98C80
# A0802022 1BC98B90
# A0802022 1BC98B86
# A0802022 1BC98B43
# A0802022 1BC98B39
# A0802022 14E96B9B
# A0802022 14E9516F
# A0802022 14E82EF8
# A0802022 14E82E96
# A0802022 14E82E1C

Press Ctrl+C to exit
>$ cleareep
F0000003
# [UCMD] Unknown command.

Press Ctrl+C to exit
>$ bestat
00000000
# (PowerOn State)
# State = 05

Press Ctrl+C to exit
>$ hdmi
FFFFA603
# [HDMI] Unknown Sub Command.hdmi

Press Ctrl+C to exit
>$ powupcause
00000000
# Powup Cause: 00 00 00 00 00 00 00 04 00 00 00 00 02 00 00 00

Press Ctrl+C to exit

New update:

I noticed that the AV/HDMI chips had some thermal paste in between the pins. I scrubbed the chips using alcohol and a toothbrush and it seems like I am able to get a picture now through the AV port!

But sadly the screen showed artifacts/glitches on the screen. I will have to use a microscope and check to see if there is anything in between the pins. Might even need a high pressure air blower to ensure I remove any left over debris that the toothbrush didn't get.. I'm also thinking of adding extra solder to the pins as maybe the pins aren't soldered on the best.

I'll update next week.
 
Last edited:
ascendantprime said:
I managed to resurrect a ceche01 ps3 from ylod with my hot air station a couple weeks ago and did thermals, and installed hen and eventually evilnat and was getting random crashing during anything intensive with the 3 beeps and i figured it was overheating still and maybe nec tokins are bad, so i delidded a couple days ago and replaced paste under the ihs on the rsx and cell, and it started running great and i could play ps3 games and ps2 games for longer than like 30 mins, it crashed again a couple days ago, thought nothing of it and today i tried booting so i could dump syscon logs to properly diag, and it was ylod again, so i pulled it back apart and reflowed it again(this time with flux i have no idea why i didnt the first time) but i did it without the ihs on both the cell and rsx and so far it is working great.

long story short i dumped the syscon logs and now it is showing me signs not only the rsx is failing but also the nec tokins are failing with 1001, 1002 and also 3034 and 4421 codes, but im also confused as its showing as 2006 being when the codes where thrown, it is a free console that was dead since 2012, should i pray it lasts longer this time, and should i even look into fixing it rather than just get a slim and mod it if both the rsx and tokins need to be replaced? should i wait for it to ylod again to hopefully get a better log? replacing the rsx and tokins are something im capable of doing and have the tools i need like bga rework station at work and all the other soldering stuff i need here at home, but i cant even find 40 or 45nm rsx chips and i dont wanna murder good consoles if im gonna need to spend another 80 bucks on capacitor tantalizer boards. full logs in picture. thankful for any tips yall have.


View attachment 47702
Click to expand...

you could 100% buy a cheap "not reading drives" or similar superslim and harvest the RSX from it
 
You must log in or register to reply here.

Similar threads

Back
Top