PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

@infinity 888 Watch Computer Booter on YT. He has all videos need. Soon will get a tool from me to test rsx without reball.
Universal jig tester. A slim board fitted with pogo pins enforced with a support around some pcb. Been my dream over years test but was so expensive all this years.
It will be on YT on his channel.
I released pcb and pins can be ordered from Aliexpress, pcb I used jclpcb order needed 9.
Can't attach all photos here so late I'll add all parts into link of rsx_spacers gbr pcb files as zip. For those who order pcbs just mention to factory "please process with any errors".
https://s.go.ro/jr7nqtgb
03546422022114981ae4875ef6f0465d.jpg
80a315969251be4b03ecfdb41ab197e3.jpg
91372e1f7759451c8b1df167fd2183a0.jpg
 
superprokill1 said:
Quoting the PS Dev Wiki:

Are you sure you replaced the cell's tokins and not the RSX's? Did you replace all of them? If so, could you send a picture of how they look and what caps you used?
Also, try taking the Blu-Ray drive out, the console won't launch any games, but if I'm not mistaken it should at least let you boot to the XMB (unless your issues occur mid game)
Click to expand...

It doesnt even boot no voltage comes to cell side when there should be 1v
 
I replaced the bottom CELL TOKINs with 3x470uf caps for each TOKIN. Do I just make sure BE_VDDC is is the normal range? im right at 4.5 ohms on BE_VDDC

edit: still ylod on shutdown trying top tokins.
edit2: all CELL tokins replace still YLOD on shutdown same error
ofst[ 96]:err_code:0xa0801001, clock:0xffffffff
ofst[100]:err_code:0xa0801001, clock:0xffffffff
 
Last edited:
Ganjo said:
I replaced the bottom CELL TOKINs with 3x470uf caps for each TOKIN. Do I just make sure BE_VDDC is is the normal range? im right at 4.5 ohms on BE_VDDC

edit: still ylod on shutdown trying top tokins.
edit2: all CELL tokins replace still YLOD on shutdown same error
ofst[ 96]:err_code:0xa0801001, clock:0xffffffff
ofst[100]:err_code:0xa0801001, clock:0xffffffff
Click to expand...
have you removed the Bluray drive? Tried a different HDD? Uninstalled any homebrew?

May I ask for pictures of your tokins install? The "replacements" and manner in which you do so could be the issue.
 
RIP-Felix said:
have you removed the Bluray drive? Tried a different HDD? Uninstalled any homebrew?

May I ask for pictures of your tokins install? The "replacements" and manner in which you do so could be the issue.
Click to expand...

Actually im a dodo.. The HDD database needed to be rebuilt. Works fine now. Thanks for the help

Heres a pic of my soldering in case I did something wrong. Is it best to add the jumper to each set of caps?

xs6ubIS
 
Hello, I have a bunch of PS3 slim and super/ultra slim with syscon error A0802024 and A0802124. Can anyone help? I've tried replacing the AV and HDMI encoders like on psdevwiki and in some posts here, but nothing seems to work.
 
IDontSpagett said:
Hello All,

I'm new to this forum, so please forgive me for any mistakes that I make in this post.

Firstly, @RIPFelix, thanks a lot for your guides & videos on the YLOD issue.
Your videos are one of the reasons why I took a leap into this rabbit hole.

So, I recently took apart a PS3 Fat (CECHK Model) which I had bought for just messing around as I am electronics engineering student.

The person who sold the console clearly stated that it's broken.

It's in a semi-decent physical state and I am pretty sure that someone has already taken it apart before (due to missing screws & broken tape for the antenna wire), but no work has been done on the motherboard.

There are a few odd things that I noticed in the syscon log, mainly the bring up & shutdown count difference followed by the low usage time. I was also not able to get the dates for the error log list, but that could be accounted for due to the CMOS battery dying out.

I am attaching the Syscon error log along this post.
Please help me understand how I can go about fixing this console.

Thanks in advance.

Code: 
PS3 Fat CECHK Model

Motherboard Revision : DIA-002

Press Ctrl+C to exit
>$ AUTH
Auth successful
Press Ctrl+C to exit
>$ ERRLOG GET 00
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 01
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 02
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 03
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 04
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 05
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 06
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 07
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 08
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 09
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0A
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0B
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0C
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0D
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0E
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0F
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 11
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 10
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$


Internal Mode

>$ errlog
errlog
ofst[116]:err_code:0xffffffff, clock:0xffffffff
ofst[120]:err_code:0xa0093004, clock:0xffffffff
ofst[124]:err_code:0xa0093004, clock:0xffffffff
ofst[  0]:err_code:0xa0093004, clock:0xffffffff
ofst[  4]:err_code:0xa0093004, clock:0xffffffff
ofst[  8]:err_code:0xa0093004, clock:0xffffffff
ofst[ 12]:err_code:0xa0093004, clock:0xffffffff
ofst[ 16]:err_code:0xa0093004, clock:0xffffffff
ofst[ 20]:err_code:0xa0093004, clock:0xffffffff
ofst[ 24]:err_code:0xa0093004, clock:0xffffffff
ofst[ 28]:err_code:0xa0093004, clock:0xffffffff
ofst[ 32]:err_code:0xa0093004, clock:0xffffffff
ofst[ 36]:err_code:0xa0093004, clock:0xffffffff
ofst[ 40]:err_code:0xa0093004, clock:0xffffffff
ofst[ 44]:err_code:0xa0093004, clock:0xffffffff
ofst[ 48]:err_code:0xa0093004, clock:0xffffffff
ofst[ 52]:err_code:0xa0093004, clock:0xffffffff
ofst[ 56]:err_code:0xa0093004, clock:0xffffffff
ofst[ 60]:err_code:0xa0093004, clock:0xffffffff
ofst[ 64]:err_code:0xa0093004, clock:0xffffffff
ofst[ 68]:err_code:0xa0093004, clock:0xffffffff
ofst[ 72]:err_code:0xa0093004, clock:0xffffffff
ofst[ 76]:err_code:0xa0093004, clock:0xffffffff
ofst[ 80]:err_code:0xa0093004, clock:0xffffffff
ofst[ 84]:err_code:0xa0093004, clock:0xffffffff
ofst[ 88]:err_code:0xa0093004, clock:0xffffffff
ofst[ 92]:err_code:0xa0093004, clock:0xffffffff
ofst[ 96]:err_code:0xa0093004, clock:0xffffffff
ofst[100]:err_code:0xa0093004, clock:0xffffffff
ofst[104]:err_code:0xa0093004, clock:0xffffffff
ofst[108]:err_code:0xa0093004, clock:0xffffffff
ofst[112]:err_code:0xa0093004, clock:0xffffffff
[mullion]$

>$ becount
becount
Bringup : 727 times
Shutdown: 172 times
Power-on: 9day 06hour 16min 42sec

bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0093004

>$
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
Click to expand...

Hi All,
It would be great if someone could help me understand if this console can be fixed.

Thanks
 
Hi !
IDontSpagett said:
Hi All,
It would be great if someone could help me understand if this console can be fixed.

Thanks
Click to expand...

Im not an expert but according to this link, the 3004 can be refered to a Core Power Failure. Maybe you can try to test the Nec capacitors with an oscilloscope and the values described in this post :
RIP-Felix said:
This is my standard tokins testing settings. Let's get better measurments, shall we? For posterity.
  • Set Horizontal axis 1uS/div
  • Set Vertical axis 50mV/div
  • Set to AC coupling. Yes, this is a DC voltage, but we're only interested in the AC component of the DC line. The ripple and noise. This will center the axis around 0v and make it easy to find the voltage. With DC coupling, you have to offset the voltage to find it somewhere between 1 and 1.3v. And zoomed in to 50mV/div that can be hard. AC coupling just makes it easy.
  • Use ground springs for a low impedance connection. Otherwise there will be too much noise to make out the ripple and any Vpp will not be accurate enough to make a determination.
Click to expand...

But with 9 days of running this is strange, it can be something else ...
 
In the continuity of the story about very short existence ps3, I have finaly put my hand in my first CECHC ps3 prematurely YOLDead.

At the epoch she possibly received an approximatly bad reflow with a week success but i dont really remember the details.

After connecting my UART arduino, the connection turned out to be very unstable and after many try have finaly got the log of Ext and Int mode but with nearly blind eyes :
-The Auth work after hard try and after a few seconds it seem to lose privilege sometime, randomely, with thing like "FFFFFFFF magic" and outup "FFFFFFFF Answer length"
-The Tx toward the syscon seem good but the Rx toward my machine is annoyingly populated by numerous glyphs, strange typefaces, tabulations and others carriage returns (but after 3 or 4 same command resending i have found the desired complete output).

I already tested my UART device in another serial thing and no glitch or other problems at all...
Any clues of what can cause this problems ? Maybe the board have suffered when she was baked ?

As follow's, for the record :

Code: 
$> becount

Bringup : 2216 times
Shutdown: 2112 times
Power-mn: 049day 04hour 19min 56sec

Code: 
$> errlog

ofst[ 20]:err_code:0xa0403034, clock:0x0d36e3b6  2007/01/09 23:26
ofst[ 24]:err_code:0xa08014ff, clock:0x0d36e3d3  2007/01?$www?-zerrlog
ofst[ 96]:err_code:0xffffffff, clock:0x0d36e368  2007/01/09 23:36:08
ofst[100]:err_code:0xa0403034, clock:0x0d36e368  2007/01/09 23:36:08
ofst[104]:err_code:0xa0404411, clock:0x0d36e374  2007/01/09 23:36:20
ofst[108]:err_code:0xa0403034, clock:0x0d36e374  2007/01/09 23:36:20
ofst[112]:err_code:0xa0404411, clock:0x0d36e37a  2007/01/09 23:36:26
ofst[116]:err_code:0xa0403034, clock:0x0d36e37a  2007/01/09 23:36:26
ofst[120]:err_code:0xa0404411, clock:0x0d36e391  2007/01/09 23:36:49
ofst[124]:err_code:0xa0403034, clock:0x0d36e391  2007/01/09 23:36:49
ofst[  0]:err_code:0xa0404411, clock:0x0d36e39f  2007/01/09 23:37:03
ofst[  4]:err_code:0xa0403034, clock:0x0d36e39f  2007/01/09 23:37:03
ofst[  8]:err_code:0xa0404411, clock:0x0d36e3b0  2007/01/09 23:37:20
ofst[ 12]:err_code:0xa0403034, clock:0x0d36e3b0  2007/01/09 23:37:20
ofst[ 16]:err_code:0xa0404411, clock:0x0d36e3b6  2007/01/09 23:37:26
ofst[ 20]:err_code:0xa0403034, clock:0x0d36e3b6  2007/01/09 23:37:26
ofst[ 24]:err_code:0xa08014ff, clock:0x0d36e3d3  2007/01/09 23:37:55
ofst[ 28]:err_code:0xa0801701, clock:0x0d36e3d3  2007/01/09 23:37:55
ofst[ 32]:err_code:0xa0404411, clock:0x0d36e3f8  2007/01/09 23:38:32
ofst[ 36]:err_code:0xa0403034, clock:0x0d36e3f8  2007/01/09 23:38:32
ofst[ 40]:err_code:0xa0404411, clock:0x0d36e405  2007/01/09 23:38:45
ofst[ 44]:err_code:0xa0403034, clock:0x0d36e405  2007/01/09 23:38:45
ofst[ 48]:err_code:0xa0404411, clock:0x0d36e40a  2007/01/09 23:38:50
ofst[ 52]:err_code:0xa0403034, clock:0x0d36e40a  2007/01/09 23:38:50
ofst[ 56]:err_code:0xa0404411, clock:0x0d36e6d2  2007/01/09 23:50:42
ofst[ 60]:err_code:0xa0403034, clock:0x0d36e6d2  2007/01/09 23:50:42
ofst[ 64]:err_code:0xa0404411, clock:0x0d36e6e2  2007/01/09 23:50:58
ofst[ 68]:err_code:0xa0403034, clock:0x0d36e6e2  2007/01/09 23:50:58
ofst[ 72]:err_code:0xa0404411, clock:0x114c660a  2009/03/13 00:32:10
ofst[ 76]:err_code:0xa0403034, clock:0x114c660a  2009/03/13 00:32:10
ofst[ 80]:err_code:0xa0404411, clock:0x114c6610  2009/03/13 00:32:16
ofst[ 84]:err_code:0xa0403034, clock:0x114c6610  2009/03/13 00:32:16
ofst[ 88]:err_code:0xa0404411, clock:0x114c6615  2009/03/13 00:32:21
ofst[ 92]:err_code:0xa0403034, clock:0x114c6615  2009/03/13 00:32:21

Code: 
$> bringup

[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2
[POWERSEQ] Error : BitTraining BE:RRAC:RX1:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0404411
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

So sadly it is another 3034 plus this time 4411 and with the difference between my CECHG thats the BitTraining error start with BE:RRAC:RX1:GLOBAL1:RX_STATUS.
Only 49 day but many more bringup/shutdown.
...
Any diag/repairing tips is welcome !
 
I'm currently working on a CECHL with VER-001 board almost found in the garbage and i can't succeed with the auth step in his SW syscon. I have tried waiting before sending command, spamming the auth and reversing wire with always the Auth1 error ...
The connection is clean (without ascii things) contrary to the last ps3 to which i have connected with the same ttl bridge.

The HDD is missing, is it important for this operation ? Or the YOLD can be provoked by this ?

Im have ordered a more serious USB-TTL converter to be sure this is not the culprit but, according to the following post, i have measured the voltage of the RX and TX wire from the actual converter and from the syscon pins :
db260179 said:
To make sure the tx and rx are correct, first do a 'screen /dev/ttyUSB0 57600', turn off ps3 then back on, should see OK message, if not swap the rx and tx around
If still isnt working, you will need a multimeter and measure the leads, should be 1.5v for RX and 3.3v for TX, if both or one has no voltage, then im afraid your syscon serial power is broken.
Click to expand...

And for the Converter i have :
TX > 3.33
RX > 0.30
For the Syscon :
TX > -0.00
RX > 3.31

I have grounded the operations with an usb cable pluged in usb port using the shield of the wire, the usb gnd is like other gnd right ?
May i ask is my Syscon is dead ?
 
Hi guys,

I have a CECHE-01, When I bought it, I wouldn't boot neither get into Recovery Menu. no blinking lights or anything, it just wouldn`t boot, staying forever with the green light and no display.
After messing with it for days, from replacing hard drive to try to get into the Recovery Menu. Somehow, I was able to get it to display video. I updated it and it ran perfectly fine for many days, had low temps, and low Up time.

Last year, while updating the OS, the screen went off and I never got to see anything on the screen again. The exact same was experienced by the owner when he decided to sell the console.

I was able to pull the following:

ERRLOG:
Code: 
ofst[ 28]:err_code:0xffffffff, clock:0x299caf23  2022/02/14 06:11:47
ofst[ 32]:err_code:0xffffffff, clock:0x299cb840  2022/02/14 06:50:40
ofst[ 36]:err_code:0xa08014ff, clock:0x299cb840  2022/02/14 06:50:40
ofst[ 40]:err_code:0xa0801701, clock:0x29ab5094  2022/02/25 08:32:20
ofst[ 44]:err_code:0xa08014ff, clock:0x29ab5094  2022/02/25 08:32:20
ofst[ 48]:err_code:0xa0801001, clock:0x28adb024  2021/08/16 23:24:20
ofst[ 52]:err_code:0xa0801701, clock:0x29ab50de  2022/02/25 08:33:34
ofst[ 56]:err_code:0xa08014ff, clock:0x29ab50de  2022/02/25 08:33:34
ofst[ 60]:err_code:0xa0801001, clock:0x29ab50de  2022/02/25 08:33:34
ofst[ 64]:err_code:0xa0801701, clock:0x29beb64a  2022/03/12 01:39:22
ofst[ 68]:err_code:0xa08014ff, clock:0x29beb64a  2022/03/12 01:39:22
ofst[ 72]:err_code:0xa0801001, clock:0x29beb64b  2022/03/12 01:39:23
ofst[ 76]:err_code:0xa0801701, clock:0x29beb6aa  2022/03/12 01:40:58
ofst[ 80]:err_code:0xa08014ff, clock:0x29beb6aa  2022/03/12 01:40:58
ofst[ 84]:err_code:0xa0801001, clock:0x29beb6aa  2022/03/12 01:40:58
ofst[ 88]:err_code:0xa0801701, clock:0x29beb9b9  2022/03/12 01:54:01
ofst[ 92]:err_code:0xa08014ff, clock:0x29beb9b9  2022/03/12 01:54:01
ofst[ 96]:err_code:0xa0801701, clock:0x0be4fcd2  2006/04/28 16:18:26
ofst[100]:err_code:0xa08014ff, clock:0x0be4fcd2  2006/04/28 16:18:26
ofst[104]:err_code:0xa0801701, clock:0x0be4fcf0  2006/04/28 16:18:56
ofst[108]:err_code:0xa08014ff, clock:0x0be4fcf0  2006/04/28 16:18:56
ofst[112]:err_code:0xa0801701, clock:0x0be50268  2006/04/28 16:42:16
ofst[116]:err_code:0xa08014ff, clock:0x0be50268  2006/04/28 16:42:16
ofst[120]:err_code:0xa0801701, clock:0x0be50277  2006/04/28 16:42:31
ofst[124]:err_code:0xa08014ff, clock:0x0be50277  2006/04/28 16:42:31
ofst[  0]:err_code:0xa0801701, clock:0x0be502bb  2006/04/28 16:43:39
ofst[  4]:err_code:0xa08014ff, clock:0x0be502bb  2006/04/28 16:43:39
ofst[  8]:err_code:0xa0801701, clock:0x0be5031b  2006/04/28 16:45:15
ofst[ 12]:err_code:0xa08014ff, clock:0x0be5031b  2006/04/28 16:45:15
ofst[ 16]:err_code:0xa0801701, clock:0x0be57d4d  2006/04/29 01:26:37
ofst[ 20]:err_code:0xa08014ff, clock:0x0be57d4d  2006/04/29 01:26:37
ofst[ 24]:err_code:0xa0801701, clock:0xffffffff

My BringUp gives me:

Code: 
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2


I had a feeling the Syscom wasn't logging new errors, so I cleaned the error log, and confirmed new errors are not being registered, as now it only shows
Code: 
ofst[  0]:err_code:0xffffffff, clock:0xffffffff
ofst[  4]:err_code:0xffffffff, clock:0xffffffff
ofst[  8]:err_code:0xffffffff, clock:0xffffffff
ofst[ 12]:err_code:0xffffffff, clock:0xffffffff
... continue ...


Let me know if you have any suggestions, Thank you.
 
The log would normally point to bad HDD (1701+14FF was what I had on a 2500 slim I sold, later found out the original HDD from it was dead as a dodo.), but from your symptoms, I'd be looking at the RSX . GLOD and the way of failure sounds like early to mid stages of RSX failure.

Normally there should have been 1601 as well to confirm an early stage of RSX failure, but IIRC there's chances that 1601 won't trigger and you're left with codes that would (most of the time but not always!) point to a bad HDD.

Did you encounter anything like green splotches in the Recovery Menu, or just anywhere in the OS after getting video output, regardless if they went away or not? (I've seen a case of an G04 with green splotches that went away within 2 minutes of running a FW update in Safe Mode. It still runs to this day though I enforced a very harsh fan control on it - 71*C max temp + 32% as the lowest fan setting.)
 
Last edited:
Raidmax said:
Did you encounter anything like green splotches in the Recovery Menu, or just anywhere in the OS after getting video output, regardless if they went away or not?
Click to expand...

Yes, indeed. I saw weird patterns on the recovery menu, some point last year when I was still able to reach it. They were not green spots, but uneven patterns, such as artifacts, in addition to that, some options on the Recovery Menu were not working or not available, at the time I thought the bad update could have corrupted the FW.
 
When I first saw the artifacts, I thought so. But since the console was working flawlessly before the update and the issue only started when the console rebooted to complete the update, I set this suspicion aside.

Now since I don't get any error recorded on the syscon at all, it makes me think somehow it is not the RSX. I was hoping for something simple, but not finding any error log and nothing on the bringup as well, makes me so unsure where else to look.

Thank you for looking into it, really appreciate your help.
 
hi, after a reflow (320°C for like 10 minutes) for fixing code A0801002, my ps3 didn't turn on anymore, so checking syscon codes two times it gave me that errors:
===================================
ERR 00: 00000000 A0A02131 FFFFFFFF
ERR 01: 00000000 A0A02131 FFFFFFFF
ERR 02: 00000000 A0A02130 FFFFFFFF
ERR 03: 00000000 A0A02130 FFFFFFFF
ERR 04: 00000000 A0A02131 FFFFFFFF
ERR 05: 00000000 A0A02131 FFFFFFFF
ERR 06: 00000000 A0A02130 FFFFFFFF
ERR 07: 00000000 A0A02130 FFFFFFFF
ERR 08: 00000000 A0A02131 FFFFFFFF
ERR 09: 00000000 A0A02131 FFFFFFFF
ERR 10: 00000000 A0112130 FFFFFFFF
ERR 11: 00000000 A0112130 FFFFFFFF
ERR 12: 00000000 A0902130 FFFFFFFF
ERR 13: 00000000 A0112130 FFFFFFFF
ERR 14: 00000000 A0112131 FFFFFFFF
ERR 15: 00000000 A0A02131 FFFFFFFF
ERR 16: 00000000 A0A02131 FFFFFFFF
ERR 17: 00000000 A0A02130 FFFFFFFF
ERR 18: 00000000 A0A02130 FFFFFFFF
ERR 19: 00000000 A0112130 FFFFFFFF
===================================
and
===================================
ERR 00: 00000000 A0112131 FFFFFFFF
ERR 01: 00000000 A0112130 FFFFFFFF
ERR 02: 00000000 A0112130 FFFFFFFF
ERR 03: 00000000 A0A02131 FFFFFFFF
ERR 04: 00000000 A0A02131 FFFFFFFF
ERR 05: 00000000 A0A02130 FFFFFFFF
ERR 06: 00000000 A0A02130 FFFFFFFF
ERR 07: 00000000 A0112131 FFFFFFFF
ERR 08: 00000000 A0112130 FFFFFFFF
ERR 09: 00000000 A0112131 FFFFFFFF
ERR 10: 00000000 A0112130 FFFFFFFF
ERR 11: 00000000 A0A02131 FFFFFFFF
ERR 12: 00000000 A0A02131 FFFFFFFF
ERR 13: 00000000 A0A02130 FFFFFFFF
ERR 14: 00000000 A0A02130 FFFFFFFF
ERR 15: 00000000 A0A02131 FFFFFFFF
ERR 16: 00000000 A0A02131 FFFFFFFF
ERR 17: 00000000 A0A02130 FFFFFFFF
ERR 18: 00000000 A0A02130 FFFFFFFF
ERR 19: 00000000 A0A02131 FFFFFFFF
===================================
looking for informations seems that i broke temperature sensors of RSX and CELL, do i?
its sure that i also fixed A0801002?
and whats the fix for these errors?

its a DYN-001 CECH-2004A.
 
Hi, so I bought a YLOD Fat PS3 as I wanted a repair project and thought it would be a good way to get experience. I was able to solder to the RX, TX and Diag pads on the COK-002 motherboard and was able to get external access and retrieved the codes. I haven't powered it on beforehand so these should be the last ones. I did try to get internal access immediately after but kept getting scopen response invalid and auth invalid even though the wires hadn't changed. I will try that again though. In the meantime, these are the codes I have from SYSCON:
START
>$ ERRLOG GET 00
FFFFFFFF Magic
Press Ctrl+C to exit
>$ ERRLOG GET 01
00000000 A0022110 2D80DAA7
Press Ctrl+C to exit
>$ ERRLOG GET 02
00000000 A0022110 2C262A46
Press Ctrl+C to exit
>$ ERRLOG GET 03
00000000 A0022110 2C2623C6
Press Ctrl+C to exit
>$ ERRLOG GET 04
00000000 A0022110 2C26239C
Press Ctrl+C to exit
>$ ERRLOG GET 05
00000000 A0022110 2C26237E
Press Ctrl+C to exit
>$ ERRLOG GET 06
00000000 A0022110 2C262370
Press Ctrl+C to exit
>$ ERRLOG GET 07
00000000 A0801001 2C26235E
Press Ctrl+C to exit
>$ ERRLOG GET 08
00000000 A0801002 2BE6A642
Press Ctrl+C to exit
>$ ERRLOG GET 09
00000000 A0801001 1DB26EDE
Press Ctrl+C to exit
>$ ERRLOG GET 0A
00000000 A0801001 19CCD421
Press Ctrl+C to exit
>$ ERRLOG GET 0B
00000000 A0801001 19A7F3D7
Press Ctrl+C to exit
>$ ERRLOG GET 0C
00000000 A0801001 18E88C25
Press Ctrl+C to exit
>$ ERRLOG GET 0D
00000000 A0801001 187A320D
Press Ctrl+C to exit
>$ ERRLOG GET 0E
00000000 A0801001 1816E20B
Press Ctrl+C to exit
>$ ERRLOG GET 0F
00000000 A0801004 17E0F183
Press Ctrl+C to exit
>$ ERRLOG GET 10
00000000 A0801001 17DCD320
Press Ctrl+C to exit
>$ ERRLOG GET 11
00000000 A0801001 17D3E1F4
Press Ctrl+C to exit
>$ ERRLOG GET 12
00000000 A0801001 17C25278
Press Ctrl+C to exit
>$ ERRLOG GET 13
00000000 A0801001 179B46D3
Press Ctrl+C to exit
>$ ERRLOG GET 14
00000000 A0801001 1795CA5A
Press Ctrl+C to exit
>$ ERRLOG GET 15
00000000 A0801001 1791E9AF
Press Ctrl+C to exit
>$ ERRLOG GET 16
00000000 A0801001 1791E7AF
Press Ctrl+C to exit
>$ ERRLOG GET 17
00000000 A0801001 17655D91
Press Ctrl+C to exit
>$ ERRLOG GET 18
00000000 A0801001 175F7A14
Press Ctrl+C to exit
>$ ERRLOG GET 19
00000000 A0801001 171A10D8
Press Ctrl+C to exit
>$ ERRLOG GET 1A
00000000 A0801001 1711D6EF
Press Ctrl+C to exit
>$ ERRLOG GET 1B
00000000 A0801001 1710C22B
Press Ctrl+C to exit
>$ ERRLOG GET 1C
00000000 A0801001 170B0D75
Press Ctrl+C to exit
>$ ERRLOG GET 1D
00000000 A0801001 16EE53B8
Press Ctrl+C to exit
>$ ERRLOG GET 1E
00000000 A0801001 1694F92E
Press Ctrl+C to exit
>$ ERRLOG GET 1F
00000000 FFFFFFFF 168CDC29
Press Ctrl+C to exit
>$
END
My thinking is that 2110 is the issue and causing the 1001 error. I don't know if 1004 is anything to worry about with it just appearing once and I'm not certain 1002 is a major issue, again due to it's infrequency. Does anyone have any other thoughts and maybe some ideas on what to check next? Any help would be greatly appreciated.
 
Woodsworth said:
Hi, so I bought a YLOD Fat PS3 as I wanted a repair project and thought it would be a good way to get experience. I was able to solder to the RX, TX and Diag pads on the COK-002 motherboard and was able to get external access and retrieved the codes. I haven't powered it on beforehand so these should be the last ones. I did try to get internal access immediately after but kept getting scopen response invalid and auth invalid even though the wires hadn't changed. I will try that again though. In the meantime, these are the codes I have from SYSCON:
START
>$ ERRLOG GET 00
FFFFFFFF Magic
Press Ctrl+C to exit
>$ ERRLOG GET 01
00000000 A0022110 2D80DAA7
Press Ctrl+C to exit
>$ ERRLOG GET 02
00000000 A0022110 2C262A46
Press Ctrl+C to exit
>$ ERRLOG GET 03
00000000 A0022110 2C2623C6
Press Ctrl+C to exit
>$ ERRLOG GET 04
00000000 A0022110 2C26239C
Press Ctrl+C to exit
>$ ERRLOG GET 05
00000000 A0022110 2C26237E
Press Ctrl+C to exit
>$ ERRLOG GET 06
00000000 A0022110 2C262370
Press Ctrl+C to exit
>$ ERRLOG GET 07
00000000 A0801001 2C26235E
Press Ctrl+C to exit
>$ ERRLOG GET 08
00000000 A0801002 2BE6A642
Press Ctrl+C to exit
>$ ERRLOG GET 09
00000000 A0801001 1DB26EDE
Press Ctrl+C to exit
>$ ERRLOG GET 0A
00000000 A0801001 19CCD421
Press Ctrl+C to exit
>$ ERRLOG GET 0B
00000000 A0801001 19A7F3D7
Press Ctrl+C to exit
>$ ERRLOG GET 0C
00000000 A0801001 18E88C25
Press Ctrl+C to exit
>$ ERRLOG GET 0D
00000000 A0801001 187A320D
Press Ctrl+C to exit
>$ ERRLOG GET 0E
00000000 A0801001 1816E20B
Press Ctrl+C to exit
>$ ERRLOG GET 0F
00000000 A0801004 17E0F183
Press Ctrl+C to exit
>$ ERRLOG GET 10
00000000 A0801001 17DCD320
Press Ctrl+C to exit
>$ ERRLOG GET 11
00000000 A0801001 17D3E1F4
Press Ctrl+C to exit
>$ ERRLOG GET 12
00000000 A0801001 17C25278
Press Ctrl+C to exit
>$ ERRLOG GET 13
00000000 A0801001 179B46D3
Press Ctrl+C to exit
>$ ERRLOG GET 14
00000000 A0801001 1795CA5A
Press Ctrl+C to exit
>$ ERRLOG GET 15
00000000 A0801001 1791E9AF
Press Ctrl+C to exit
>$ ERRLOG GET 16
00000000 A0801001 1791E7AF
Press Ctrl+C to exit
>$ ERRLOG GET 17
00000000 A0801001 17655D91
Press Ctrl+C to exit
>$ ERRLOG GET 18
00000000 A0801001 175F7A14
Press Ctrl+C to exit
>$ ERRLOG GET 19
00000000 A0801001 171A10D8
Press Ctrl+C to exit
>$ ERRLOG GET 1A
00000000 A0801001 1711D6EF
Press Ctrl+C to exit
>$ ERRLOG GET 1B
00000000 A0801001 1710C22B
Press Ctrl+C to exit
>$ ERRLOG GET 1C
00000000 A0801001 170B0D75
Press Ctrl+C to exit
>$ ERRLOG GET 1D
00000000 A0801001 16EE53B8
Press Ctrl+C to exit
>$ ERRLOG GET 1E
00000000 A0801001 1694F92E
Press Ctrl+C to exit
>$ ERRLOG GET 1F
00000000 FFFFFFFF 168CDC29
Press Ctrl+C to exit
>$
END
My thinking is that 2110 is the issue and causing the 1001 error. I don't know if 1004 is anything to worry about with it just appearing once and I'm not certain 1002 is a major issue, again due to it's infrequency. Does anyone have any other thoughts and maybe some ideas on what to check next? Any help would be greatly appreciated.
Click to expand...
To add to this, I tried to get internal access again but still received the message of 'scopen response invalid' and 'AUTH invalid'. I tried reconnecting the Diag and TX but no luck. I've since desoldered them so I'll try soldering them again later. I have replaced the thermal paste and assembled enough to test. I get fan spin then it immediately turns off and I'm left with a red blinking light. It seems to be about 3 seconds before the yellow light flashes and the beeps appear. I'm stuck at this point on what to check next. I have followed @RIP-Felix guide and had success up until trying internal access.
 
You must log in or register to reply here.

Similar threads

Back
Top