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

RIP-Felix said:
If the console is jailbroken, use PS3 advanced tools to dump the errorlog. If the log will dump to usb root.
Click to expand...
So i guess it really is the tokins?
But according to the error code is it the RSX Tokins?
I have 4 caps in a piggyback configuration and i still get YLOD...
Here is a pic (I insulated these afterwards,sorry about the bad soldering job):
20220105_201307.jpg
 
Vishera said:
Firmware Version: 4.81 (build 50649)
Platform ID: CokB10
Product Code: 00 85
Product Sub Code: 00 03
Hardware Config: 20000000FFFFFEFF
Syscon Fimware Version: 0C16.0001000100030003 (EEPROM: 0001000100030003)
Bringup Count: 3210, Shutdown Count: 2980
Runtime: 199 Days, 9 Hours, 47 Minutes, 53 Seconds
Error Log
01: A0801002 Fri Feb 17 15:03:41 2006
02: A0801002 Fri Feb 17 06:19:47 2006
03: A0801002 Fri Feb 17 05:50:36 2006
04: A0801002 Fri Feb 17 05:50:26 2006
05: A0801002 Fri Feb 17 05:48:08 2006
06: A0801002 Fri Feb 17 05:47:59 2006
07: A0801002 Fri Feb 17 05:47:43 2006
08: A0801002 Fri Feb 17 05:47:25 2006
09: A0801002 Fri Feb 17 05:47:14 2006
10: A0801002 Fri Feb 17 05:46:57 2006
11: A0801002 Fri Feb 17 05:46:45 2006
12: A0801002 Thu Feb 16 20:53:22 2006
13: A0801002 Thu Feb 16 20:32:38 2006
14: A0801002 Thu Feb 16 20:26:52 2006
15: A0801002 Thu Feb 16 20:21:40 2006
16: A0801001 Thu Feb 16 19:55:46 2006
17: A0801004 Thu Feb 16 19:52:53 2006
18: A0801002 Thu Feb 16 19:41:59 2006
19: A0801002 Thu Feb 16 19:38:56 2006
20: A0801002 Thu Feb 16 19:08:51 2006
21: A0801002 Thu Feb 16 19:02:32 2006
22: A0801002 Thu Feb 16 18:52:59 2006
23: A0801002 Thu Feb 16 18:49:01 2006
24: A0801002 Thu Feb 16 18:43:55 2006
25: A0801002 Thu Feb 16 18:38:28 2006
26: A0801002 Thu Feb 16 18:35:28 2006
27: A0801002 Thu Feb 16 18:35:18 2006
28: A0801002 Thu Feb 16 18:33:43 2006
29: A0801002 Thu Feb 16 18:33:34 2006
30: A0801002 Thu Feb 16 18:33:25 2006
31: A0801002 Thu Feb 16 18:33:17 2006
32: FFFFFFFF Thu Feb 16 18:33:06 2006
Click to expand...
That parasite probably won't work. The wire has too high an inductance to provide a low impedance path to ground. They might as well not be connected. I tried it before, and they either did nothing or made the noise worse. Expose some copper next to the tokins and install to that, or remove one and solder directly to the rails.

1002 means RSX VRM power fail. All it means is there's no powergood. It can be caused by other things than just the tokins. Start there, but do it right. And if it still doesn't work, know that it could be literally any SMD on the VRM module.
 
RIP-Felix said:
That parasite probably won't work. The wire has too high an inductance to provide a low impedance path to ground. They might as well not be connected. I tried it before, and they either did nothing or made the noise worse. Expose some copper next to the tokins and install to that, or remove one and solder directly to the rails.

1002 means RSX VRM power fail. All it means is there's no powergood. It can be caused by other things than just the tokins. Start there, but do it right. And if it still doesn't work, know that it could be literally any SMD on the VRM module.
Click to expand...
So...
I had an accident and a solder blob fell on some SMDs on the back of the RSX near the TOKINs :hopelessness:
I cleaned it and in the process knocked 2-3 of those tiny SMDs off.
While it is repairable,it is not something that i can fix on my own so i will have to send it to a lab :(

And now when i turn it on it gives me an instant YLOD,It is expected since those SMDs were part of the RSX VRMs...
 
Vishera said:
So...
I had an accident and a solder blob fell on some SMDs on the back of the RSX near the TOKINs :hopelessness:
I cleaned it and in the process knocked 2-3 of those tiny SMDs off.
While it is repairable,it is not something that i can fix on my own so i will have to send it to a lab :(

And now when i turn it on it gives me an instant YLOD,It is expected since those SMDs were part of the RSX VRMs...
Click to expand...
Can you show a picture of the smd's lost and post an errorlog with the new errors? This kind of mistake is a learning opportunity.
 
RIP-Felix said:
Its your property. Reflows do not last and usually cause more damage than they are worth. Especially for a non backwards compatible model that can be cheaply replaced.

My advice? Buy a 40nm slim or 28nm SS model.
Click to expand...
i already have a slim, i got this console for free and wanted to try to get it working. maybe i will just reflow and see what happens, or hold it until i can afford a bga setup because like you said non backwards compatible is easily replaced. thank you for your help
 
dood6017 said:
i already have a slim, i got this console for free and wanted to try to get it working. maybe i will just reflow and see what happens, or hold it until i can afford a bga setup because like you said non backwards compatible is easily replaced. thank you for your help
Click to expand...
Well, if you do a reflow, be sure to clean thoroughly (electronics contact cleaner. flow it underneath the RSX) and use AMTECH flux. Use temperature probe next to RSX. Preheater under board to prevent warping. And gently nudge the chip to be sure the solder flowed.

Watch videos to get familiar with it.

I have posted detailed instructions on this before. I don't really feel like finding the post or being super helpful today. Check the links in my signature. I think theres something in my FAQ.
 
Toronto516 said:
We finally made it! Today I removed one of the old tokens and replaced it with 330uf tantalum capacitors that I removed from a dead CECHG. And it worked! I played Tlou, GT6 and Uncharted 2 to try it out. They worked flawlessly. I can't thank you enough. I hope it helps someone who has a similar problem as mine. Here is my modded and repaired CECHC04:
Click to expand...

I've been playing GT6 for an hour a day for a week with my ps3. And it still works. The tantalums I bought from aliexpress have arrived. I will use it if I need it in the future.
 

Attachments

  • IMG_20220109_205423.jpg
    IMG_20220109_205423.jpg
    2.2 MB · Views: 82
  • IMG_20220109_205347.jpg
    IMG_20220109_205347.jpg
    2.2 MB · Views: 68
Toronto516 said:
I've been playing GT6 for an hour a day for a week with my ps3. And it still works. The tantalums I bought from aliexpress have arrived. I will use it if I need it in the future.
Click to expand...
This is the first time I remember seeing 1001/2022 errors "fixed" by replacing tokins.

We have seen DVE/HDMI errors (2020/2120, 2022/2122, and 2024/2124) associated with tokins before. More often they're caused by RSX VRAM or BGA/Bump defects (RSX and/or CPU). They occur often in GLOD consoles. Not very many were actually related to bad DVE/HDMI IC's. We're still learning about these errors.
 
Just revived a ylod CECHB00 (all black ps3) by replacing capacitors. Also delidded what are good temps to set as my targets in webman? syscon errors are below. I have another Japanese unit a silver CECHH00 will post the syscon and result of changing the caps tomorrow or later in the week
cechb00-ylod-fixed.jpg


===================================
ERR 00: 00000000 A0071002 FFFFFFFF
ERR 01: 00000000 A0061002 FFFFFFFF
ERR 02: 00000000 A0071002 FFFFFFFF
ERR 03: 00000000 A0071002 FFFFFFFF
ERR 04: 00000000 A0901001 FFFFFFFF
ERR 05: 00000000 A0061002 FFFFFFFF
ERR 06: 00000000 A0801002 FFFFFFFF
ERR 07: 00000000 A0801002 FFFFFFFF
ERR 08: 00000000 A0101002 FFFFFFFF
ERR 09: 00000000 A0101002 150118F4
ERR 10: 00000000 A0801002 15011884
ERR 11: 00000000 A0611001 15011000
ERR 12: 00000000 A0101001 15010FF4
ERR 13: 00000000 A0611001 15010F7F
ERR 14: 00000000 A0801002 0BD42C4D
ERR 15: 00000000 A0801002 0B6DE036
ERR 16: 00000000 A0801002 0B5CB559
ERR 17: 00000000 A0801002 0B5C60ED
ERR 18: 00000000 A0801002 0B5C60BE
ERR 19: 00000000 A0101001 0B5C60A2
===================================
 
Last edited:
No_Ob said:
Just revived a ylod CECHB00 (all black ps3) by replacing capacitors. Also delidded what are good temps to set as my targets in webman? syscon errors are below. I have another Japanese unit a silver CECHH00 will post the syscon and result of changing the caps tomorrow or later in the week
cechb00-ylod-fixed.jpg


===================================
ERR 00: 00000000 A0071002 FFFFFFFF
ERR 01: 00000000 A0061002 FFFFFFFF
ERR 02: 00000000 A0071002 FFFFFFFF
ERR 03: 00000000 A0071002 FFFFFFFF
ERR 04: 00000000 A0901001 FFFFFFFF
ERR 05: 00000000 A0061002 FFFFFFFF
ERR 06: 00000000 A0801002 FFFFFFFF
ERR 07: 00000000 A0801002 FFFFFFFF
ERR 08: 00000000 A0101002 FFFFFFFF
ERR 09: 00000000 A0101002 150118F4
ERR 10: 00000000 A0801002 15011884
ERR 11: 00000000 A0611001 15011000
ERR 12: 00000000 A0101001 15010FF4
ERR 13: 00000000 A0611001 15010F7F
ERR 14: 00000000 A0801002 0BD42C4D
ERR 15: 00000000 A0801002 0B6DE036
ERR 16: 00000000 A0801002 0B5CB559
ERR 17: 00000000 A0801002 0B5C60ED
ERR 18: 00000000 A0801002 0B5C60BE
ERR 19: 00000000 A0101001 0B5C60A2
===================================
Click to expand...
Interesting... A rare case , not a single 3034.

I just talked to the creator of the syscon script. @M4j0r This automated syscon reader tool may not be 100% accurate. So just a word of caution there... Use python script to be sure you are seeing the latest errors.

Edit. It appears the tool does not clear the error log. It also can't show all 32 errors, only 20. If that's the case, you may be seeing old errors that could happen due to flipping a switch or any other forced shutdowns.
 
Last edited:
DeadEnd said:
Interesting... A rare case , not a single 3034.

I just talked to the creator of the syscon script. @M4j0r This automated syscon reader tool may not be 100% accurate. So just a word of caution there... Use python script to be sure you are seeing the latest errors.

Edit. It appears the tool does not clear the error log. It also can't show all 32 errors, only 20. If that's the case, you may be seeing old errors that could happen due to flipping a switch or any other forced shutdowns.
Click to expand...
I tried the python script first before moving to a windows laptop and couldn't get it to worth because of dependencies issue, I tried both pyserial and serial but was getting some error with them. Will try get it working before touching the silver unit. Those errors are from before changing the caps not after btw
 
No_Ob said:
I tried the python script first before moving to a windows laptop and couldn't get it to worth because of dependencies issue, I tried both pyserial and serial but was getting some error with them. Will try get it working before touching the silver unit. Those errors are from before changing the caps not after btw
Click to expand...
Did you try my tutorial?

Probably the issue with windows dependencies is that you need to use pycryptodome. And don't forget to install to Path when installing python. It's all in the tutorial.

Alternatively, if the console boots and jailbroken, you can use "PS3 Advanced Tools" to dump the full errorlog. It'll dump a text file to your usb stick.
 
RIP-Felix said:
Did you try my tutorial?

Probably the issue with windows dependencies is that you need to use pycryptodome. And don't forget to install to Path when installing python. It's all in the tutorial.

Alternatively, if the console boots and jailbroken, you can use "PS3 Advanced Tools" to dump the full errorlog. It'll dump a text file to your usb stick.
Click to expand...
I'm using arch and did install pycryptodome with pip, no idea why it wasn't working
 
No_Ob said:
Silver unit seems to be fixed after changing 2 capacitors, same ones as in my previous post.
Error logs from before cap change: https://pastebin.com/ejZ3j2Zr
IMG-20220111-214749.jpg



Its a linux distro, setup python on my windows laptop and got logs for the silver unit
Click to expand...
Posting his error codes here for convenience:
Code: 
 ERRLOG GET 1FERRLOG GET 00
F0000006
>$ ERRLOG GET 01
00000000 A0801002 FFFFFFFF
>$ ERRLOG GET 02
00000000 A0801002 FFFFFFFF
>$ ERRLOG GET 03
00000000 A0801002 FFFFFFFF
>$ ERRLOG GET 04
00000000 A0801002 FFFFFFFF
>$ ERRLOG GET 05
00000000 A0801002 FFFFFFFF
>$ ERRLOG GET 06
00000000 A0801002 FFFFFFFF
>$ ERRLOG GET 07
00000000 A0801002 FFFFFFFF
>$ ERRLOG GET 08
00000000 A0801002 29675201
>$ ERRLOG GET 09
00000000 A0801002 296751FB
>$ ERRLOG GET 0A
00000000 A0801002 296751F4
>$ ERRLOG GET 0B
00000000 A0801002 296751EA
>$ ERRLOG GET 0C
00000000 A0801002 296751B5
>$ ERRLOG GET 0D
00000000 A0801002 296751AB
>$ ERRLOG GET 0E
00000000 A0801002 296751A0
>$ ERRLOG GET 0F
00000000 A0801002 2967517D
>$ ERRLOG GET 10
00000000 A0801002 29675172
>$ ERRLOG GET 11
00000000 A0801002 29674FC8
>$ ERRLOG GET 12
00000000 A0801002 242226E6
>$ ERRLOG GET 13
00000000 A0801002 242226D7
>$ ERRLOG GET 14
00000000 A0801002 242226AB
>$ ERRLOG GET 15
00000000 A0801002 242226A5
>$ ERRLOG GET 16
00000000 A0801002 2422269C
>$ ERRLOG GET 17
00000000 A0801002 24222359
>$ ERRLOG GET 18
00000000 A0801002 2421DBCA
>$ ERRLOG GET 19
00000000 A0801002 2421DBB5
>$ ERRLOG GET 1A
00000000 A0801002 2421DBA7
>$ ERRLOG GET 1B
00000000 A0801002 2420E62C
>$ ERRLOG GET 1C
00000000 A0801002 2420E624
>$ ERRLOG GET 1D
00000000 A0801002 2420E60F
>$ ERRLOG GET 1E
00000000 A0801002 2420E608
>$ ERRLOG GET 1F
00000000 FFFFFFFF 2420E5FD
 
No_Ob said:
Silver unit seems to be fixed after changing 2 capacitors, same ones as in my previous post.
Error logs from before cap change: https://pastebin.com/ejZ3j2Zr
IMG-20220111-214749.jpg



Its a linux distro, setup python on my windows laptop and got logs for the silver unit
Click to expand...
What model was this one?

2/2 on bad tokins. Properly diagnosed, there's no doubt. Perhaps the tokins are failing more. It should continue to become more frequent as they age. Especially for more reliable slim models, where the RSX BGA/Bumps don't fail as often.
 
RIP-Felix said:
What model was this one?

2/2 on bad tokins. Properly diagnosed, there's no doubt. Perhaps the tokins are failing more. It should continue to become more frequent as they age. Especially for more reliable slim models, where the RSX BGA/Bumps don't fail as often.
Click to expand...
Idk if its properly diagnosed lol, I just took the errors codes for this thread I dont know what they mean. Just bought these machines as a gamble because they were very cheap. I remember seeing something about some games causing issues after cap changes do you know what games those are so I can test them out?

That was a CECHH00, I think its definitely an age thing in this case because these both failed relatively recently they were on firmware 4.81 and 4.82
 
No_Ob said:
Idk if its properly diagnosed lol, I just took the errors codes for this thread I dont know what they mean. Just bought these machines as a gamble because they were very cheap. I remember seeing something about some games causing issues after cap changes do you know what games those are so I can test them out?

That was a CECHH00, I think its definitely an age thing in this case because these both failed relatively recently they were on firmware 4.81 and 4.82
Click to expand...
I just mean you had the error we associate most with bad tokins. If you didn't use that code to diagnose the problem and repair it, you were increadbly lucky to have guessed the correct repair. Assuming the YLOD is a bad tokin usually backfires.

I'm glad you posted the errorlog, tho. It helps me with statistics.
 
RIP-Felix said:
I just mean you had the error we associate most with bad tokins. If you didn't use that code to diagnose the problem and repair it, you were increadbly lucky to have guessed the correct repair. Assuming the YLOD is a bad tokin usually backfires.

I'm glad you posted the errorlog, tho. It helps me with statistics.
Click to expand...
Yeah very lucky wish i read this thread before ordering them though, saw a bunch of vids on youtube saying its the caps which Is why I ordered these lol. Although if i did read this first i probably wouldn't have taken the chance so maybe it was a good thing I was ill informed

Having some issues with both units tho with the CECHB00 i think that it is failing to shut down correctly because when it turns of it has a blinking red light which needs to be pressed to then go into normal standby with solid red light, this interferes with things like reboot in webman, not sure what the issue is here.

Also i'm having an issue on the silver unit not sure if its to do with the cap replacement or not but i've never experienced this before when using webman. Prior to this ive only used rebug though so maybe evilnat is jsut not as polished. Been trying to play modern warfare 2 and it keeps crashing to a black screen ive tried 2 different isos. I have been playing black ops 2 on the same unit without any issues though so not sure what to think of it

Update on modern warfare 2 tested it on the CECHB00 also both us and pal version. I get crashes at the menu or like 30 seconds into a multiplayer match but its different to the crashes on the CECHH00 the CECHB00 will turn off with beeps/red light like it is overheating, i dont think it is overheating though because I delidded. The CECH00 just black screens and I have to hold power to force the console off. Wondering if modern warfare 2 is using some part of the cpu or gpu and causing crashes that are not happening in blackops/blackops2 because the engines are different. Could be a sign the cap replacement hasn't worked?
 
Last edited:
You must log in or register to reply here.

Similar threads

Back
Top