PS3 (Research/Experimental) - NEC/TOKIN Capacitors Replacement - YLOD

[birigui]

I don't reccomend harvesting from slims before 30xx model, since they can be jailbroken. Especially not the 21xx, which is the most reliable model.

good morning,
I found a kte-001 and an mpx-001, these already have their fw 3.65/4.15....my question is, as most of the time the MOD is made on ps3 with ylod, is there any way to check which version it is? current fw of the device? If the answer is yes, is there a tutorial for that? or only through some UART command is it possible to identify.

 

[Casualdehid/Aerials]

Hi there!
My CECHK04 finally got a YLOD while loading Uncarted D'sF from mmCm. Had a few visual glitches before while watching Youtube (ex: Grey bar and flashing, but for strictly one frame), but never had any issues while playing games, well... so far. Also; where and when? During the vacation ofc xD I can still turn it on, and has no visual glitches by default, so I am not suspecting any RSX fails.

However, has the original Tokins, and I am still in the middle of ordering the FTDI UART and stuff to get the messages out of Syscon, but since it's a K model, i'd say it's the most likely. Recommended Panasonics cost unreasonable (2€s/Stk!!! Wtf??), ans LCSC has only 3 of them in stock rn.

Kemet alternative from LCSC (sorry can't post links): C156466

Are theese any good? Would theese be okay, if I ordered 23 of them? Including the size and everything.

Thanks in advance!

 

[RIP-Felix]

good morning,
I found a kte-001 and an mpx-001, these already have their fw 3.65/4.15....my question is, as most of the time the MOD is made on ps3 with ylod, is there any way to check which version it is? current fw of the device? If the answer is yes, is there a tutorial for that? or only through some UART command is it possible to identify.

Sorry I'm not sure what you're asking.

If the console boots into XMB you can check what FW is currently installed in system information.
If it's GLOD, it, the Southbridge UART might say. There are several types of GLOD, and some do not display any SB UART logs.
If it's YLOD and doesn't get far enough for the bootloader to begin, then it's not possible without removing the flash and dumping it's contents.

 

[Casualdehid/Aerials]

Sorry I'm not sure what you're asking.

If the console boots into XMB you can check what FW is currently installed in system information.
If it's GLOD, it, the Southbridge UART might say. There are several types of GLOD, and some do not display any SB UART logs.
If it's YLOD and doesn't get far enough for the bootloader to begin, then it's not possible without removing the flash and dumping it's contents.

Hi Felix!

it YLOD'd during loading the game, and so far no ylod during boot up.

Would you mind checking the cap I shared the part nr from LCSC in my first post? Do you think those would be okay for Tonkin replacements?

What I meant by the UART is to make sure it is the tokins that have failed before I order anything.
Thank you for your support.

 

[birigui]

Desculpe, não tenho certeza do que você está perguntando.

Se o console inicializar no XMB, você poderá verificar qual FW está instalado no momento nas informações do sistema.
Se for GLOD, o UART Southbridge pode dizer. Existem vários tipos de GLOD, e alguns não exibem nenhum log SB UART.
Se for YLOD e não for longe o suficiente para o bootloader iniciar, então não será possível sem remover o flash e despejar seu conteúdo.

Sua resposta está de acordo com a pergunta. Já encontrei um rsx de 40nm de um kte-001, neste final de semana vou substituí-lo e retorno para informar se tudo ocorreu bem.

Your answer is in line with the question. I've already found a 40nm rsx from a kte-001, this weekend I'm going to replace it and get back to you to let you know if everything went well.

Mod edit: Provide an English translation with your post.

 

[RIP-Felix]

Hi there!
My CECHK04 finally got a YLOD while loading Uncarted D'sF from mmCm. Had a few visual glitches before while watching Youtube (ex: Grey bar and flashing, but for strictly one frame), but never had any issues while playing games, well... so far. Also; where and when? During the vacation ofc xD I can still turn it on, and has no visual glitches by default, so I am not suspecting any RSX fails.

However, has the original Tokins, and I am still in the middle of ordering the FTDI UART and stuff to get the messages out of Syscon, but since it's a K model, i'd say it's the most likely. Recommended Panasonics cost unreasonable (2€s/Stk!!! Wtf??), ans LCSC has only 3 of them in stock rn.

Kemet alternative from LCSC (sorry can't post links): C156466

Are theese any good? Would theese be okay, if I ordered 23 of them? Including the size and everything.

Thanks in advance!

You can use any low esr (under 9mohm) 470uF cap you like that will fit. Doesn't have to be tantalum, can be Aluminum Polymer too. I see LCSC has several in the EEF line that are cheap and in stock. Use 3 per tokin replaced.

You can also check the errorlog using PS3ToolSet.com (when they get their SSL issue sorted out). I show how in this tutorial.

 

[lukkasremondi]

Facinating! That is an as yet unreported code! A new code!!!

These things get me excited. BAsed on the step number it's likely related to byte-training. This is the process immediatly after Bit-training, which is what fails in the case of Processor failures, like BGA or Bumps defects in either the CPU/GPU. This is when the processors' high speed interface on the FlexIO, th traces connecting them, are fed a series of bits or bytes, and the expected timing and response is measured to calibrate the phase lock loop and bring the alignment to a center position. This improves high speed signal integrity.

When there's an issue, like a poor solder joint, or a worn out die, this calibration procedure has a harder time completing, and when it finally can't...BEEP...BEEP...BEEP! Byte training come immediately after bit training. BitTraining causes 3034/4xxx errors at step# 40. ByteTraining causes 3035 errors at step# 50, and finally we've seen 3041 at step #52. That's the closest to your 3039 we've seen. We never got a resolution to it, nobody knows what caused it. But I have a guess and your's may help with this...

Your 3039 is right at the last stage before the bootloader. Between ByteTraining at step number 50 and when the StarShip 2 controller loads the bootloader stored on flash at step 60. Issues with the Nand/Nor cause A0603040 errors. But botth you 3039 and that 3041 occured at a previous step number of 52. The 14FF is a clue as to what's going on. That's a Checkstop. This is usually a hardware error during a software check. It discovered a fatal HW error during a check, and stopped because of it.So the poignant questions are...

1. What comes after ByteTraining has determined the CPU and RSX are calibrated and ready for action? (assuming they are)
   
2. What critical HW is needed for the bootloader to start?

I speculate it may be the Flash or controller itself, the starship 2 controller, because it's similar to 603040, but occuring earlier. So perhaps 3041 is an issue with the StarShip 2 controller. And perhaps your 3039 is too. It gives you a place to look at anyway. However, this is not going to be easy to troubleshoot.

Could you please provide as much information about the condition of the console as you can? Like describe if it was sealed, dusty, has evidence of drop damage, water damage, what work have you done, or what work can you see was done. Like, does it have new thermal paste? Is there flux residue around the RSX/CPU/ Has it been delided? And so on.

I don't have many details about the console. I bought it from a seller on Facebook who claimed to be the second owner of the console, who had purchased it together with another PS3 so that it could be a parts donor if necessary.

The console had a fair amount of dust inside, but was well looked after on the outside. Apparently it had a careful owner, but he had never cleaned the interior, which was indicated by the amount of dust in the cooler. It wasn't much, but it indicated it had never been dismantled for cleaning. The entire carcass was in perfect condition, with no signs of falling or knocks, including very few scratches.

There are not many signs of oxidation on the plate (a bit expected, as the owner lived in a drier region and far from the sea), just the steel protection that sits on the plate, which is quite oxidized. As for the console board, when I opened it, I noticed that they had replaced the NECs with tantalum capacitors, with very amateur soldering. I redid the weld, at least making it look better. Weld residues were only present in the NEC region, under the cell or rsx they were intact. The thermal paste still seemed to be the original which, despite being slightly dry, didn't seem to be compromising heat dissipation too much. On the rest of the board, nothing appears to have been changed.

 

[birigui]

good afternoon I changed the rsx and fixed the checksums, now I'm getting an errlog with 2120 10x followed by 3013.

errlog
ofst[56]:err_code:0xffffffff, relógio:0xffffffff
ofst[60]:código_err:0xa0202120, relógio:0xffffffff
ofst[64]:código_err:0xa0202120, relógio:0xffffffff
ofst[68]:código_err:0xa0202120, relógio:0xffffffff
ofst[72]:código_err:0xa0202120, relógio:0xffffffff
ofst[76]:código_err:0xa0202120, relógio:0xffffffff
ofst[80]:código_err:0xa0202120, relógio:0xffffffff
ofst[84]:código_err:0xa0202120, relógio:0xffffffff
ofst[88]:código_err:0xa0202120, relógio:0xffffffff
ofst[92]:código_err:0xa0213013, relógio:0xffffffff
ofst[96]:código_err:0xa0202120, relógio:0xffffffff
ofst[100]:código_err:0xa0202120, relógio:0xffffffff
ofst[104]:código_err:0xa0202120, relógio:0xffffffff
ofst[108]:código_err:0xa0202120, relógio:0xffffffff
ofst[112]:código_err:0xa0202120, relógio:0xffffffff
ofst[116]:código_err:0xa0202120, relógio:0xffffffff
ofst[120]:código_err:0xa0202120, relógio:0xffffffff
ofst[124]:código_err:0xa0202120, relógio:0xffffffff
ofst[0]:código_err:0xa0202120, relógio:0xffffffff
ofst[4]:código_err:0xa0202120, relógio:0xffffffff
ofst[8]:código_err:0xa0213013, relógio:0xffffffff
ofst[12]:código_err:0xa0202120, relógio:0xffffffff
ofst[16]:código_err:0xa0202120, relógio:0xffffffff
ofst[20]:código_err:0xa0202120, relógio:0xffffffff
ofst[24]:código_err:0xa0202120, relógio:0xffffffff
ofst[28]:código_err:0xa0202120, relógio:0xffffffff
ofst[32]:código_err:0xa0202120, relógio:0xffffffff
ofst[36]:código_err:0xa0202120, relógio:0xffffffff
ofst[40]:código_err:0xa0202120, relógio:0xffffffff
ofst[44]:código_err:0xa0202120, relógio:0xffffffff
ofst[48]:código_err:0xa0202120, relógio:0xffffffff
ofst[52]:código_err:0xa0213013, relógio:0xffffffff


Where can I look for a defect? According to ps3devkiwi's error history, the f6302 fusistor is ok.

Sorry I'm not sure what you're asking.

If the console boots into XMB you can check what FW is currently installed in system information.
If it's GLOD, it, the Southbridge UART might say. There are several types of GLOD, and some do not display any SB UART logs.
If it's YLOD and doesn't get far enough for the bootloader to begin, then it's not possible without removing the flash and dumping it's contents.

Good afternoon, I am sending a boot attempt after replacing and training the rsx 40nm taken from a kte-001.
In the previous message I sent the errlog, and I would also like to ask a question, on page 119 of the topic, you cited the following conclusion:

Conclusion:
2120/3013 errors are possible on BGA/bump and fuse/SMD defects. Distinguishing them from one another depends on the step number in which they occur.
80/90 = BGA/Bump defects and possibly voltage ripple/noise.
20/21 = Fuses/SMDs (possibly BGA, but less likely).
00 = fuse.

I would like you to explain to me how to know in which step the error occurred, each line would be a step, until reaching the line where the error occurs? How can I understand this, can you help me?

>$ bringup
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 -> 0302
[SSM] PowSeq Fail : Detected !
[SSM] state: 0302 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120

 

[ABDERRAHMENABDERRAHMEN]

i need help for these error


ERRLOG
*** Unknown Command ***
[mullion]$
errlog
ofst[124]:err_code:0xffffffff, clock:0x2d6f84c0 2024/02/26 17:20:00
ofst[ 0]:err_code:0xa0061002, clock:0x2d71f88d 2024/02/28 13:58:37
ofst[ 4]:err_code:0xa0061002, clock:0x2d7b9b2c 2024/03/06 21:22:52
ofst[ 8]:err_code:0xa0061002, clock:0x2d7b9b32 2024/03/06 21:22:58
ofst[ 12]:err_code:0xa0061002, clock:0x2d7b9b35 2024/03/06 21:23:01
ofst[ 16]:err_code:0xa0061002, clock:0x2d7b9b39 2024/03/06 21:23:05
ofst[ 20]:err_code:0xa0061002, clock:0x2d7b9b3b 2024/03/06 21:23:07
ofst[ 24]:err_code:0xa0061002, clock:0x2d7b9b45 2024/03/06 21:23:17
ofst[ 28]:err_code:0xa0061002, clock:0x2d7b9b48 2024/03/06 21:23:20
ofst[ 32]:err_code:0xa0061002, clock:0x2dde01e0 2024/05/20 12:43:12
ofst[ 36]:err_code:0xa0061002, clock:0x2dde01f0 2024/05/20 12:43:28
ofst[ 40]:err_code:0xa0061002, clock:0x2dde01f7 2024/05/20 12:43:35
ofst[ 44]:err_code:0xa0061002, clock:0x2dde01fc 2024/05/20 12:43:40
ofst[ 48]:err_code:0xa0061002, clock:0x2dde0201 2024/05/20 12:43:45
ofst[ 52]:err_code:0xa0061002, clock:0x2dde0207 2024/05/20 12:43:51
ofst[ 56]:err_code:0xa0801001, clock:0x2de668d0 2024/05/26 21:40:32
ofst[ 60]:err_code:0xa0801002, clock:0x2de668d9 2024/05/26 21:40:41
ofst[ 64]:err_code:0xa0801002, clock:0x2de668e3 2024/05/26 21:40:51
ofst[ 68]:err_code:0xa0061002, clock:0xffffffff
ofst[ 72]:err_code:0xa0071002, clock:0xffffffff
ofst[ 76]:err_code:0xa0801002, clock:0x0b488680 2005/12/31 00:00:00
ofst[ 80]:err_code:0xa0071002, clock:0x0b4886c9 2005/12/31 00:01:13
ofst[ 84]:err_code:0xa0061002, clock:0x0b4886d0 2005/12/31 00:01:20
ofst[ 88]:err_code:0xa0801002, clock:0x0b48e425 2005/12/31 06:39:33
ofst[ 92]:err_code:0xa0801002, clock:0x0b48e434 2005/12/31 06:39:48
ofst[ 96]:err_code:0xa0801002, clock:0x0b4e1e71 2006/01/04 05:49:37
ofst[100]:err_code:0xa0801002, clock:0x0b4e1e78 2006/01/04 05:49:44
ofst[104]:err_code:0xa0801002, clock:0x0b4e1ebb 2006/01/04 05:50:51
ofst[108]:err_code:0xa0801002, clock:0x0b4e1eca 2006/01/04 05:51:06
ofst[112]:err_code:0xa0801002, clock:0x0b4e1ed3 2006/01/04 05:51:15
ofst[116]:err_code:0xa0801002, clock:0x0b4e1f00 2006/01/04 05:52:00
ofst[120]:err_code:0xa0061002, clock:0xffffffff
[mullion]$
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] fatalreq delayed.
[ERROR]: 0xa0061002
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] *** Power Fail RS ***
[SSM] state: 0201 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
becount
Bringup : 1802 times
Shutdown: 1601 times
Power-on: 101day 03hour 22min 00sec
[mullion]$
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] fatalreq delayed.
[ERROR]: 0xa0071002
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] *** Power Fail RS ***
[SSM] state: 0201 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] fatalreq delayed.
[ERROR]: 0xa0061002
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] *** Power Fail RS ***
[SSM] state: 0201 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] fatalreq delayed.
[ERROR]: 0xa0061002
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] *** Power Fail RS ***
[SSM] state: 0201 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] fatalreq delayed.
[ERROR]: 0xa0061002
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] *** Power Fail RS ***
[SSM] state: 0201 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
becount
Bringup : 1806 times
Shutdown: 1605 times
Power-on: 101day 03hour 22min 04sec
[mullion]$

 

[birigui]

Good afternoon Felix, after changing the RSX, as I said, I got errors 2120 x10 and 3013....through measurements I realized that I have a short on the +1.5 RSX VDDIO line and also a low resistance on the FBVDDQ line.
I compared it with a photo with the resistors and I have a frank mod made here, where I could compare and check the short.
As for the +1.5 RSX VDDIO voltage, since its formation, there are only resistors along the way, and it ends directly at the rsx. Do you believe it is a short caused by spheres, during resoldering of the RSX or would you recommend trying something else on the board before resoldering? If you could guide me, I would be very grateful.

 

[Casualdehid/Aerials]

i need help for these error


ERRLOG
*** Unknown Command ***
[mullion]$
errlog
ofst[124]:err_code:0xffffffff, clock:0x2d6f84c0 2024/02/26 17:20:00
ofst[ 0]:err_code:0xa0061002, clock:0x2d71f88d 2024/02/28 13:58:37
ofst[ 4]:err_code:0xa0061002, clock:0x2d7b9b2c 2024/03/06 21:22:52
ofst[ 8]:err_code:0xa0061002, clock:0x2d7b9b32 2024/03/06 21:22:58
ofst[ 12]:err_code:0xa0061002, clock:0x2d7b9b35 2024/03/06 21:23:01
ofst[ 16]:err_code:0xa0061002, clock:0x2d7b9b39 2024/03/06 21:23:05
ofst[ 20]:err_code:0xa0061002, clock:0x2d7b9b3b 2024/03/06 21:23:07
ofst[ 24]:err_code:0xa0061002, clock:0x2d7b9b45 2024/03/06 21:23:17
ofst[ 28]:err_code:0xa0061002, clock:0x2d7b9b48 2024/03/06 21:23:20
ofst[ 32]:err_code:0xa0061002, clock:0x2dde01e0 2024/05/20 12:43:12
ofst[ 36]:err_code:0xa0061002, clock:0x2dde01f0 2024/05/20 12:43:28
ofst[ 40]:err_code:0xa0061002, clock:0x2dde01f7 2024/05/20 12:43:35
ofst[ 44]:err_code:0xa0061002, clock:0x2dde01fc 2024/05/20 12:43:40
ofst[ 48]:err_code:0xa0061002, clock:0x2dde0201 2024/05/20 12:43:45
ofst[ 52]:err_code:0xa0061002, clock:0x2dde0207 2024/05/20 12:43:51
ofst[ 56]:err_code:0xa0801001, clock:0x2de668d0 2024/05/26 21:40:32
ofst[ 60]:err_code:0xa0801002, clock:0x2de668d9 2024/05/26 21:40:41
ofst[ 64]:err_code:0xa0801002, clock:0x2de668e3 2024/05/26 21:40:51
ofst[ 68]:err_code:0xa0061002, clock:0xffffffff
ofst[ 72]:err_code:0xa0071002, clock:0xffffffff
ofst[ 76]:err_code:0xa0801002, clock:0x0b488680 2005/12/31 00:00:00
ofst[ 80]:err_code:0xa0071002, clock:0x0b4886c9 2005/12/31 00:01:13
ofst[ 84]:err_code:0xa0061002, clock:0x0b4886d0 2005/12/31 00:01:20
ofst[ 88]:err_code:0xa0801002, clock:0x0b48e425 2005/12/31 06:39:33
ofst[ 92]:err_code:0xa0801002, clock:0x0b48e434 2005/12/31 06:39:48
ofst[ 96]:err_code:0xa0801002, clock:0x0b4e1e71 2006/01/04 05:49:37
ofst[100]:err_code:0xa0801002, clock:0x0b4e1e78 2006/01/04 05:49:44
ofst[104]:err_code:0xa0801002, clock:0x0b4e1ebb 2006/01/04 05:50:51
ofst[108]:err_code:0xa0801002, clock:0x0b4e1eca 2006/01/04 05:51:06
ofst[112]:err_code:0xa0801002, clock:0x0b4e1ed3 2006/01/04 05:51:15
ofst[116]:err_code:0xa0801002, clock:0x0b4e1f00 2006/01/04 05:52:00
ofst[120]:err_code:0xa0061002, clock:0xffffffff


[SSM] *** Power Fail RS ***

This is all RSX related, presumably tokin failures.

 

[Bertus van Zyl]

Hello friends.

I have a PS3 2004A with a Dyn-001 board which has errors 3004 and 1002.
The wording of the guide is a bit unclear so just checking to make sure.
I need 330uf 2.5V tantalum caps and replace only the RSX tokins?
I

Hello friends.

I have a PS3 2004A with a Dyn-001 board which has errors 3004 and 1002.
The wording of the guide is a bit unclear so just checking to make sure.
I need 330uf 2.5V tantalum caps and replace only the RSX tokins?
I

Answered my own question. Put on my reading glasses and reread the guide then proceeded to order the caps on Ali express. In the reviews for the listing was a guy that ordered a set of the same caps for the exact same console as mine so now I have a picture reference too.

Thanks for the nice guide.

 

[Casualdehid/Aerials]

Answered my own question. Put on my reading glasses and reread the guide then proceeded to order the caps on Ali express. In the reviews for the listing was a guy that ordered a set of the same caps for the exact same console as mine so now I have a picture reference too.

Thanks for the nice guide.

Caps from Aliexpress won't be a good idea. Cancel it if you can, and get it from a reputable source, like LCSC or digikey.
Source:

 

[Bertus van Zyl]

Caps from Aliexpress won't be a good idea. Cancel it if you can, and get it from a reputable source, like LCSC or digikey.
Source:

Thanks. Interesting video, the caps has already been shipped so gonna try them regardless. If the console is unstable i'll get caps from RS-Electronics. Not wanting to order from Digikey or Mouser comes down to the shipping cost. Never heard of LCSC but i'll check them out.

 

[Casualdehid/Aerials]

Never heard of LCSC but i'll check them out.

LCSC is a chineese eqvivalent to digikey or mouser. They are cheap, but ship legitimate components. Same company as jlcpcb.

 

[Gus21]

PS3 Super Slim
Motherboard NPX-001 CECH-42xxB

Defect: turns on, the green LED lights up, stays on the green light, sometimes it turns off by itself, but most of the time I can't turn it off

Can anyone help me? I think it could be CI HDMI ou AV ?


>$ AUTH
Auth successful
Press Ctrl+C to exit
>$ ERRLOG GET 00
00000000 A0802124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 01
00000000 A0802024 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 02
00000000 A0042024 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 03
00000000 A0A02024 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 04
00000000 A0A02124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 05
00000000 A0A02024 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 06
00000000 A0A02124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 07
00000000 A0A02024 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 08
00000000 A0A02124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 09
00000000 A0A02024 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 10
00000000 A0A02024 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0A
00000000 A0A02124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0B
00000000 A0A02024 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0C
00000000 A0A02024 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0D
00000000 A0A02024 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0E
00000000 A0A02024 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0F
00000000 A0A02024 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 10
00000000 A0A02024 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 11
00000000 A0A02124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 12
00000000 A0A02024 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 13
00000000 A0A02124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 14
00000000 A0A02124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 15
00000000 A0A02124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 16
00000000 A0A02124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 17
00000000 A0A02124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 18
00000000 A0A02124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 19
00000000 A0A02124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1A
00000000 A0A02124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1B
00000000 A0A02124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1C
00000000 A0A02124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1D
00000000 A0A02124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1E
00000000 A0A02124 FFFFFFFF
Press Ctrl+C to exit

 

[thyaguster]

Spoiler

So following my posts above I ended up replacing both B side Nec/Tokins (RSX) - each with 3x 2R5TPE470M9 470 2.5V 470UF from Aliexpress.
It booted first time!! (Which didn't happen since the YLODs started, I would always have to remove the hdd, turn it on after 10+ tries and let the unit warmup or heat the tokins directly.)

Going to leave some more info on my unit, so people don't read this and assume Tantalums will fix their unit too.
I never had any graphical issues, GPU artifacts or even overheating, just YLODs on start, sporadic ones after some time of gameplay, and some games like Dragon Ball: Raging Blast 2, Dead Or Alive 5: Last Round, would instantly YLOD the unit.
Also this is a 300 days registered uptime unit that still had the warranty seal, so again, a good candidate faulty/end of life Nec/Tokins.
It's been working fine with no ylods for a week with heavy usage. Let's hope...I'll try no to forget to report back in a year or so.

Quick 3 month update: Still going strong, not a single boot/reboot issue since the nec/tokins replacement.

 

[santorfo]

Tokins are the most likely diagnosis. I have since confirmed the 65nm RSX is not affected by bumpgate. At least not the bad underfill. And if there is a lacking polyamide stress layer, it doesn't appear to cause premature failure. So you'll be fine.

I reccomend tantalizers for beginners. Since you want to fix it for the sake of fixing it, not becauae it's econimically viable to do so (it'll cost roughly the same to fix as it does to replace), then I'd say have at it!

PS: for the information effort the power on useage would be great to have. becount is the command but it doesnt work on sherwood syscon. So you'll have to check bgtoolset's errorcode under system management tab (same tab as if you were going to jailbreak). Or use ps3advancedtools I linked in my syscon tutorial.

I'm curious how long it lasted before toking out. Also, THX for the backstory. That context is useful and rarely provided.

Took me over a year to finally get to it but after much struggling with removing the tokins and installing the tantalizers it actually worked. I can't really believe it but it actually does work and 7 years after the last time it was properly used, I can finally use my PS3 again.

For future reference I ended up using 3x 330uF caps per tantalizer and I replaced all 4 RSX tokins.

Finally, I checked the system power on usage time with PS3 Toolset:
- Boot Count 3003
- Shutdown Count 2893
- Runtime 280 days 17 hours 15 minutes

 

[doc_gc]

Hi all, new to the forum, thanks everyone for all those informations

i have two DIA-001 boards, one i really want to repair as is from a CECHH00 White 40gb JAP system.

Boards were fine, giving ylod after some time after booting up; after reflowing both system has 2 seconds ylod, and SYSCON error 3003, referred to VDDC CELL 3v line.
Did a check on fuses on both sides and everything is fine; i actually was comparing the board with another DIA-001 i have that works, compared some resistors but everything seems fine....


Both boards has identical syscon verbose:

(ERROR]: becount
Bringup : 319 times Shutdowo: 281 times
Power-on: 12day 19hour 08min 52sec
[nullion]$
errdog
@Est [ 36] :err_code:0xffffffff,
clock:0xffffffff
Qfst[
40]: err_code: 0xa0093003,
clock:0xffffffff
ofatl
44]: err_code: 0x0093003,
clock:Oxffffffff
Qfst[
48]: err. code: 0xa0093003,
Clock:0xffffffff
Qfst [
52] :err_code:0xa0093003,
clock:Oxffffffff
ofstl
56]: err_code: 0x0093003,
Clock:Oxffffffff
Qfst [
60]: err_code: 0xa0093003,
clock:0xffffffff
ofstl
64]: err_code: 0xa0093003,
clock:Oxffffffff
ofst[
68]: err.code: 0xa0093003,
Clock:0xffffffff
ofst [
72]: err_code:0x0093003, clock:0xffffffff
ofst[
76]: err_code:0x0093003,
Clock: 0xffffffff
ofst [
80]: err_code :0xa0093003,
Clock:0xffffffff
ofst [
84] :err_code:0xa0093003,
Clock:Oxffffffff
ofst [
88]: enr. code: 0xa0093003,
clock:Oxffffffff
ofst [
92] :err
_code: 0x0093003,
clock:Oxffffffff
ofst I
96]: err_code :0xa0093003,
clock:0xffffffff
ofst [100]: err_code: 0xa0093003,
Clock:Đxffffffff
ofst [104]: err_code: 0x0093003,
clock:0xffffffff
ofst [108]: erc.code: 0xa0093003,
clock:0xffffffff
ofst [112]: err_code :0xa0093003,
Clock:0xffffffff
ofst [116]: err_code: 0xa0093003,
clock:0xffffffff
ofst [120]: err_code:0xa0093003,
clock:0xffffffff
ofst [124]: err_code:0xa0093003,
clock:Oxffffffff
ofst [
0]: err. code: 0xa0093003,
clock:0xffffffff
ofst [
4]: err_code: 0x0093003,
clock:Oxffffffff
ofsti
8] :err_code:0xa0093003,
clock:0xffffffff
ofst [
12]: err_code: 0xa0093003,
clock:0xffffffff
ofst [
16]: err_code: 0x0093003,
clock:0xffffffff
ofst [
20]: err code: 0xa0093003,
clock: 0xffffffff
ofst [
24]: err_code: 0xa0093003,
clock:0xffffffff
ofstl
28]: err_code: 0xa0093003,
clock:0xffffffff
ofst[
32]: err_code: 0xa0093003,
clock:Oxffffffff
[mullion]$


does someone has any hint about this? Seems not to be nec caps as boards were working before. Could it be a dead cell?

 

[RIP-Felix]

Hi all, new to the forum, thanks everyone for all those informations

i have two DIA-001 boards, one i really want to repair as is from a CECHH00 White 40gb JAP system.

Boards were fine, giving ylod after some time after booting up; after reflowing both system has 2 seconds ylod, and SYSCON error 3003, referred to VDDC CELL 3v line.
Did a check on fuses on both sides and everything is fine; i actually was comparing the board with another DIA-001 i have that works, compared some resistors but everything seems fine....


Both boards has identical syscon verbose:

(ERROR]: becount
Bringup : 319 times Shutdowo: 281 times
Power-on: 12day 19hour 08min 52sec
[nullion]$
errdog
@Est [ 36] :err_code:0xffffffff,
clock:0xffffffff
Qfst[
40]: err_code: 0xa0093003,
clock:0xffffffff
ofatl
44]: err_code: 0x0093003,
clock:Oxffffffff
Qfst[
48]: err. code: 0xa0093003,
Clock:0xffffffff
Qfst [
52] :err_code:0xa0093003,
clock:Oxffffffff
ofstl
56]: err_code: 0x0093003,
Clock:Oxffffffff
Qfst [
60]: err_code: 0xa0093003,
clock:0xffffffff
ofstl
64]: err_code: 0xa0093003,
clock:Oxffffffff
ofst[
68]: err.code: 0xa0093003,
Clock:0xffffffff
ofst [
72]: err_code:0x0093003, clock:0xffffffff
ofst[
76]: err_code:0x0093003,
Clock: 0xffffffff
ofst [
80]: err_code :0xa0093003,
Clock:0xffffffff
ofst [
84] :err_code:0xa0093003,
Clock:Oxffffffff
ofst [
88]: enr. code: 0xa0093003,
clock:Oxffffffff
ofst [
92] :err
_code: 0x0093003,
clock:Oxffffffff
ofst I
96]: err_code :0xa0093003,
clock:0xffffffff
ofst [100]: err_code: 0xa0093003,
Clock:Đxffffffff
ofst [104]: err_code: 0x0093003,
clock:0xffffffff
ofst [108]: erc.code: 0xa0093003,
clock:0xffffffff
ofst [112]: err_code :0xa0093003,
Clock:0xffffffff
ofst [116]: err_code: 0xa0093003,
clock:0xffffffff
ofst [120]: err_code:0xa0093003,
clock:0xffffffff
ofst [124]: err_code:0xa0093003,
clock:Oxffffffff
ofst [
0]: err. code: 0xa0093003,
clock:0xffffffff
ofst [
4]: err_code: 0x0093003,
clock:Oxffffffff
ofsti
8] :err_code:0xa0093003,
clock:0xffffffff
ofst [
12]: err_code: 0xa0093003,
clock:0xffffffff
ofst [
16]: err_code: 0x0093003,
clock:0xffffffff
ofst [
20]: err code: 0xa0093003,
clock: 0xffffffff
ofst [
24]: err_code: 0xa0093003,
clock:0xffffffff
ofstl
28]: err_code: 0xa0093003,
clock:0xffffffff
ofst[
32]: err_code: 0xa0093003,
clock:Oxffffffff
[mullion]$


does someone has any hint about this? Seems not to be nec caps as boards were working before. Could it be a dead cell?

Replace the CPU side TOKINs.

3003 is the next level escalation of 1001. It's more diagnostic of an issue with the CELL VDDC filter than 1001 is. The behavior is consistant with cpu tokins.

It can be realated to the VRM as well, but start with tokins.