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

[RIP-Felix]

@RIP-Felix Any chance of buying fully assembled tantalizers yet? if so can u link me to where?

No, not yet. Well, booter sells them preassembled, but he asks a high price.

 

[hoyohoo]

You said it's a COK-001, yes? The diag pad is in the picture in the tutorial you quoted.

Yes, it is said model. I know that the diag pad is in the tutorial, but where do I connect it to? Is this a GND on my USB Adapter?
Sorry, I am new to this whole topic of USB TTL adapters

Spoiler: Thats what my Adapter looks like

 

[RIP-Felix]

Yes, it is said model. I know that the diag pad is in the tutorial, but where do I connect it to? Is this a GND on my USB Adapter?
Sorry, I am new to this whole topic of USB TTL adapters

Spoiler: Thats what my Adapter looks like

Yes, you connect it to ground. Can be your adaper, or on the board.

 

[medo mashakel]

does any one have a schematic diagram for cok002

 

[mimi]

does any one have a schematic diagram for cok002

https://gamesx.com/wiki/lib/exe/fetch.php?media=schematics:sony_ps3_cok-002_5th.pdf

 

[Leonellus544]

"IMPORTANT - TO MAKE SURE YOU DID IT RIGHT, AND MORE CAPACITORS NEEDS REPLACEMENT, THE YLOD MUST BE DELAYED, SOMEWHERE IN BETWEEN 3/5 SEC TIME-FRAME, IF ITS IMMEDIATE/SHORTED THAN THAT, IT MEANS THAT THE CAPACITOR ITS NOT PROPERLY SOLDERED, THAT HAPPENS WHEN A NEC ITS REMOVED,BECAUSE THERE IS NO CURRENT SUPPLY TO THE CHIP

you know, I bought NEC/TOKINS 0E128 for a ps3 slim, because I couldn't get neither tantalium capacitor or 0E108 tokins. at first, I wasn't properly welded, but now, it takes 3-5s, as if they needed replacement. is this because they're incompatible with the slim CECH model or my NEC tokins could be in bad shape?

 

[DeadEnd]

you know, I bought NEC/TOKINS 0E128 for a ps3 slim, because I couldn't get neither tantalium capacitor or 0E108 tokins. at first, I wasn't properly welded, but now, it takes 3-5s, as if they needed replacement. is this because they're incompatible with the slim CECH model or my NEC tokins could be in bad shape?

Blindly replacing capacitors is not needed any longer. Please get familiar with syscon diagnostics and read error codes to find out the answer.

 

[Gus21]

Hello, with this log of a cechg01 is it possible a frank ?
the error A0404401 worries me a lot, can the cell be dead?

===================================
ERR 00: 00000000 A0403034 FFFFFFFF
ERR 01: 00000000 A0404401 FFFFFFFF
ERR 02: 00000000 A0902120 FFFFFFFF
ERR 03: 00000000 A0403034 FFFFFFFF
ERR 04: 00000000 A0404401 FFFFFFFF
ERR 05: 00000000 A0403034 FFFFFFFF
ERR 06: 00000000 A0404401 FFFFFFFF
ERR 07: 00000000 A0403034 FFFFFFFF
ERR 08: 00000000 A0404401 FFFFFFFF
ERR 09: 00000000 A0403034 FFFFFFFF
ERR 10: 00000000 A0404401 FFFFFFFF
ERR 11: 00000000 A0403034 FFFFFFFF
ERR 12: 00000000 A0404401 FFFFFFFF
ERR 13: 00000000 A0403034 FFFFFFFF
ERR 14: 00000000 A0404401 FFFFFFFF
ERR 15: 00000000 A0403034 FFFFFFFF
ERR 16: 00000000 A0404401 FFFFFFFF
ERR 17: 00000000 A0403034 FFFFFFFF
ERR 18: 00000000 A0404401 FFFFFFFF
ERR 19: 00000000 A0403034 FFFFFFFF
===================================

 

[DeadEnd]

Hello, with this log of a cechg01 is it possible a frank ?
the error A0404401 worries me a lot, can the cell be dead?

===================================
ERR 00: 00000000 A0403034 FFFFFFFF
ERR 01: 00000000 A0404401 FFFFFFFF
ERR 02: 00000000 A0902120 FFFFFFFF
ERR 03: 00000000 A0403034 FFFFFFFF
ERR 04: 00000000 A0404401 FFFFFFFF
ERR 05: 00000000 A0403034 FFFFFFFF
ERR 06: 00000000 A0404401 FFFFFFFF
ERR 07: 00000000 A0403034 FFFFFFFF
ERR 08: 00000000 A0404401 FFFFFFFF
ERR 09: 00000000 A0403034 FFFFFFFF
ERR 10: 00000000 A0404401 FFFFFFFF
ERR 11: 00000000 A0403034 FFFFFFFF
ERR 12: 00000000 A0404401 FFFFFFFF
ERR 13: 00000000 A0403034 FFFFFFFF
ERR 14: 00000000 A0404401 FFFFFFFF
ERR 15: 00000000 A0403034 FFFFFFFF
ERR 16: 00000000 A0404401 FFFFFFFF
ERR 17: 00000000 A0403034 FFFFFFFF
ERR 18: 00000000 A0404401 FFFFFFFF
ERR 19: 00000000 A0403034 FFFFFFFF
===================================

There is nothing unusual about 4401. It is a data error consistent with failure to complete bittraining . These errros come with 3034 quite often. It is rsx issue . Cell does not just "die" out of the blue.

 

[mafia4]

Hello i have a cecha01 and it kinda has instant ylod.
Is it related to the tokins or somthing else ?


====================================
[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
>$ errlog
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
errlog
ofst[ 12]:err_code:0xffffffff, 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
ofst[116]:err_code:0xa0093004, 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

 

[Shawn Shakir]

Hello i have a cecha01 and it kinda has instant ylod.
Is it related to the tokins or somthing else ?


====================================
[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
>$ errlog
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
errlog
ofst[ 12]:err_code:0xffffffff, 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
ofst[116]:err_code:0xa0093004, 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

3004 (RSX Core Power Failure)[edit]

This error will occur in the case of a PWR failure on the main core voltage of the GPU (VDDC). For example, if the filtering capacitors (NEC/TOKIN's) are severely damaged. There are other SMD's in that filter, so it could be related to them as well.

 

[mafia4]

3004 (RSX Core Power Failure)[edit]

This error will occur in the case of a PWR failure on the main core voltage of the GPU (VDDC). For example, if the filtering capacitors (NEC/TOKIN's) are severely damaged. There are other SMD's in that filter, so it could be related to them as well.

So it is related to the token's.
"There are other SMD's in that filter, so it could be related to them as well"
Are there any schematics or pics that shows the components?

 

[Shawn Shakir]

So it is related to the token's.
"There are other SMD's in that filter, so it could be related to them as well"
Are there any schematics or pics that shows the components?

You can get schematics by googling COK-001/COK-002 schematics

 

[mafia4]

I think these are the components that is evolved with the GPU VDDC and i think there is a short found by measurements.

I just wonder that i can find the short with injecting voltage ...
Is it possible to find the short with injecting voltage ?

 

[Robbotron]

Hey SuperNoob here, I bought a USB TTL adapter, I made all connections in my SEM-001 but after running the script, a window with message: "Failed to communicate to COM" appear. Googling didn't give me any useful results.
Any ideas?
Thanks

 

[mimi]

Hey SuperNoob here, I bought a USB TTL adapter, I made all connections in my SEM-001 but after running the script, a window with message: "Failed to communicate to COM" appear. Googling didn't give me any useful results.
Any ideas?
Thanks

Double check COM port (1, 2, 3...) in device manager
If you have troubles reading PS3 check wiring, wires should be connected like this:
RX - TX, not RX - RX.

 

[slderin]

Hi,
I have C04 and this is my errorlog.
ofst[ 4]:err_code:0xffffffff, clock:0x2b6e7059 2023/02/02 13:00:09
ofst[ 8]:err_code:0xa0801601, clock:0x2b6e7059 2023/02/02 13:00:09
ofst[ 12]:err_code:0xa0801701, clock:0x2b6f11b9 2023/02/03 00:28:41
ofst[ 16]:err_code:0xa0801601, clock:0x2b6f11b9 2023/02/03 00:28:41
ofst[ 20]:err_code:0xa0003001, clock:0xffffffff
ofst[ 24]:err_code:0xa0003001, clock:0xffffffff
ofst[ 28]:err_code:0xa0003001, clock:0xffffffff
ofst[ 32]:err_code:0xa0003001, clock:0xffffffff
ofst[ 36]:err_code:0xa0003001, clock:0xffffffff
ofst[ 40]:err_code:0xa0003001, clock:0xffffffff
ofst[ 44]:err_code:0xa0801200, clock:0xffffffff
ofst[ 48]:err_code:0xa0801200, clock:0xffffffff
ofst[ 52]:err_code:0xa0801200, clock:0xffffffff
ofst[ 56]:err_code:0xa0801200, clock:0xffffffff
ofst[ 60]:err_code:0xa0801200, clock:0xffffffff
ofst[ 64]:err_code:0xa0801001, clock:0xffffffff
ofst[ 68]:err_code:0xa0801001, clock:0xffffffff
ofst[ 72]:err_code:0xa0801200, clock:0xffffffff
ofst[ 76]:err_code:0xa0801701, clock:0xffffffff
ofst[ 80]:err_code:0xa0801601, clock:0xffffffff
ofst[ 84]:err_code:0xa0801701, clock:0xffffffff
ofst[ 88]:err_code:0xa0801601, clock:0xffffffff
ofst[ 92]:err_code:0xa0801701, clock:0xffffffff
ofst[ 96]:err_code:0xa0801601, clock:0xffffffff
ofst[100]:err_code:0xa0801701, clock:0xffffffff
ofst[104]:err_code:0xa0801601, clock:0xffffffff
ofst[108]:err_code:0xa0801701, clock:0xffffffff
ofst[112]:err_code:0xa0801601, clock:0xffffffff
ofst[116]:err_code:0xa0801701, clock:0xffffffff
ofst[120]:err_code:0xa0801601, clock:0xffffffff
ofst[124]:err_code:0xa0801701, clock:0xffffffff
ofst[ 0]:err_code:0xa0801601, clock:0xffffffff

I trigger 1200 error with i didn't plug to psu 12v line. 3001 was caused by i removed all thermal things. So I have 1701/1601 issue with no 3034 error. Should I change caps or my console bricked?

 

[Grey Ghost]

Holy Cow! I've missed out on a lot the past couple years! I've been re-reading this entire thread (more like skimming) and it seems a lot of progress has been made.

Just to refresh, I made some post in this thread that go back to May of 2020, starting on page 97, then my last post ever was on page 114 - then "life happened" so to speak. Nothing but good things, just put my focus on other projects and hobbies.

My last post, regarding a reflowing of a HA01 that had physical damage to the case but was never able to even revive it in which was likely a poor attempt at a reflow to see if I could even get it to boot, de-motivated me. I decided to take a break and come back to it with a fresh mind. I guess 3 years is long enough for a "fresh mind" LMFAO.

Anywho, I've gotten more confident with my soldering skills as of late as I have just been practicing soldering and removing components from dead boards and I've really developed a hatred for dealing with lead-free solder.

But more to the point, while I was re-reading the thread - I came to the conclusion that if I was to come back into the fold, I just HAD be able to read Syscon. I left before RIP-Felix posted anything regarding the Syscon so up to that point.... we were essentially throwing darts at a dartboard testing everything by physically doing things to the console to bring it back to life, which goes to the NEC/TOKIN caps being replaced.

We all know the history about that an all so I'll save you some verbosity.

The dropped 60GB I was working on (my sole purpose for this console was to practice delidding, more on that in a future post), is put away in storage so eventually I will get back to that, but if its dead, its dead and will be up for grabs for anyone wanting a parts.

My initial posts, where I took an HE01 I bought from ebay specifically for replacing the caps was in a working state if anyone bothers to look at my post history, it worked. But the problem now, was that it needed to be delidded as upon booting it up it would instantly step up the fan speed a few times to the point where it would sound like it maxed out but it never did a thermal shutdown - leading me to believe that it needed a delid.

The RSX was successfully delidded as that was easy as cake (heat up the IHS for a few min to soften up the thermal glue, then used a thin plastic razor blade on each corner and slowly worked them inwards until the IHS popped off), but still had the fan issue leading me to believe the CPU needed it done also. I mean at this point we're nearing 20 year old thermal paste so.... you know.... it needs to be done on every console.

Out of sheer, colossal stupidity.... I practiced delidding the CPU on my revived HE01 and scratched the substrate. Whoops. I realized I used the wrong tools and methods and called it quits.

Squeept offered his services for MAYBE finishing up where I left off - but that fell through because of me taking a break and I wiped my hands of it for the last 3 years.

 

[Grey Ghost]

Now here we are.

Im trying again. I got me a proper delidding tool for future projects. NSC's own design. It was priced accordingly. It wasn't cheap, but its worth it for those who dont have the patience to make their own out of things like paint spatulas or nail files and going through the long task of thinning them down and bending them and all that. Its whatever.

So to actually practice reading syscon and delidding, I found an HH01 on ebay for $25. It was sealed. Never been opened, still had the warranty sticker.

I got my Syscon reader setup - i did not get what Felix posted as his recommendation on his Tutorial post - but i got the common one that everyone seems to be getting.

Opening this unit... man, it was dusty. Dust bunnies everywhere. But thats all. I debated on taking pics but.... we've all seen what they look like. Aside from dust, this console was in good shape appearance wise after some dusting.

Then I got around installing the Syscon and getting it setup. Did I mention I hate lead-free solder? After dealing with just connecting the wires I was confident about getting the logs to see whats up.

Before getting to that, this HH model was sold to me as a YLOD. No other details on the ebay post. Its fine, it was $25 plus shipping, so about $45 total. I'm ok with $45 going towards my education on this project.

Prior to the teardown and dusting, I inspected the console. It looked like it had been well used and not loved. Dust was coming out of every crevice, even the HDD bay when I removed the cover just bunnies wanting to escape.
I plug it in, standby light comes on so thats at least a sign that it takes power still. And then I turn it on. Green light.... I count every second expecting to see that Yellow light.... 5....6....7...Boom: YLOD.

So a long YLOD. Interesting I said. But perhaps that meant some hope?


Anywho, after the dusting and installing the syscon reader and getting used to getting access to the console via CMD.... I noticed something strange. The YLOD was gone. So many thoughts going on: Did I fix it? Were the dust bunnies a factor? Did removing and reinserting the HDD fix it?

Anywho, it was time to get serious about the syscon and diving into it.

 

[Grey Ghost]

I took screenshots of each command I ran, so that everyone has a clear picture of what this HH is telling me/us.

becount

bringup

lasterrlog

and the full errlog

Aside from the 2023/02/14 timestamps down (which was all me playing with syscon and getting used to accessing via CMD) but I just plugged this unit in today after I received it earlier this week. Its a day behind, insignificant.


After running these commands... the console just never YLOD. Like at all.

I plugged in an HDMI cable and its just sitting there in the OS. As far as I can tell, this console was simply used as a media device. The game data utility listed the games that were played on this unit - it has all the typical "filthy casual" games lol. A few Fifa games, GTA5 and thats about it. But it did have every streaming app available... Youtube, Amazon Prime, Spotify, Netflix etc etc.

Given by the syscon and some of the gamesave timestamps, the owner(s) used this thing religiously until about 2017 until it started giving them issues. And now its mine.

But the common error is 1002: The RSX is the issue.

There is also 1004 at the top (power supply), perhaps a blackout?

2203 is a southbridge error - just a single one.

So the GPU needs attention.



At this point in my project, I'm going to clean the console very well, apply new themal paste and then do some gaming to see if I can trigger a YLOD.

As far as the damaged HA, and my HE with a failed delid.... we'll get to those eventually.


My ultimate goal: I have another HE01 that has been my personal console since I bought it brand new from Kmart. Its the Motorstorm bundle. It has YLOD. I have not touched it or recapped it or anything. Once upon a time, I did a reflow that brought it back to life but only temporarily - I can game on it for about an hour before it shuts down but in the XMB its otherwise fine. I'd like to at least be able to read the syscon from it and form a gameplan that will end up finding someone to do a reball of the CPU and GPU as well as a delid on both and give it a really good ultrasonic cleaning and handing me back a working, restored HE01 that still has all of my original data thats still intact on the 500GB hdd that I installed all those years ago - and upgrade it to a 1TB unit and enjoy playing some PS3 games I've missed out on. I'm aware of emulation but... I prefer original hardware if at all possible.