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

MicrowaveEgg said:
I ran syscon on a PS3 I just picked up. Power on instantly gets YLOD flash then blinking red
The error looks to be
A0801001 = CELL Power on VRAM failure

How would I go about fixing this?

Thanks
>$ ERRLOG GET 00
00000000 A0231002 28F14D34
>$ ERRLOG GET 01
00000000 A0902120 28F14D13
>$ ERRLOG GET 02
00000000 A0231002 28F14D13
>$ ERRLOG GET 03
00000000 A0902120 28F14D02
>$ ERRLOG GET 04
00000000 A0231002 28F14D02
>$ ERRLOG GET 05
00000000 A0902120 28B1E2BD
>$ ERRLOG GET 06
00000000 A0403034 28B1E2BD
>$ ERRLOG GET 07
00000000 A0403034 28B1E23E
>$ ERRLOG GET 08
00000000 A0801001 28B1E1BB
>$ ERRLOG GET 09
00000000 A0801001 28B1E12A
>$ ERRLOG GET 0A
00000000 A0801001 27EEF189
>$ ERRLOG GET 0B
00000000 A0801001 274D12A1
>$ ERRLOG GET 0C
00000000 A0801001 269BC5AB
>$ ERRLOG GET 0D
00000000 A0801001 269BC08A
>$ ERRLOG GET 0E
00000000 A0801001 20C9CCB3
>$ ERRLOG GET 0F
00000000 A0801001 20C9A96E
>$ ERRLOG GET 10
00000000 A0801001 20C9A5B0
>$ ERRLOG GET 11
00000000 A0801001 20676A29
>$ ERRLOG GET 12
00000000 A0801001 20303711
>$ ERRLOG GET 13
00000000 A0801001 20300036
>$ ERRLOG GET 14
00000000 A0902120 202E8F1A
>$ ERRLOG GET 15
00000000 A0801001 202E8F19
>$ ERRLOG GET 16
00000000 A0801001 202E6222
>$ ERRLOG GET 17
00000000 A0801001 1F076740
>$ ERRLOG GET 18
00000000 A0801001 1F0313BE
>$ ERRLOG GET 19
00000000 A0801001 1F02FDBB
>$ ERRLOG GET 1A
00000000 A0801001 1EF5D1A7
>$ ERRLOG GET 1B
00000000 A0801001 1EEA4433
>$ ERRLOG GET 1C
00000000 A0801001 1ED3DBC3
>$ ERRLOG GET 1D
00000000 A0801001 1ED38779
>$ ERRLOG GET 1E
00000000 A0801001 1ED1FF43
>$ ERRLOG GET 1F
00000000 FFFFFFFF 1E6A6F03
>$
Click to expand...
To be honest I have one cok002 water damage. Had 3034 4402, 1001, 1002.
What I've done reball rsx, exchanged both sides caps on rsx and cell. Now state of it is glod. Now I have too much parts to exchange as they went very corroded. I'm not sure if reball cell will fix 1001 as in my case didn't start with only caps exchange.
Not sure what to suggest, probably will work with caps exchange if they have corrosion inside. Then if you see 3.2 ohms on cell vddc line is good ic. Worth trying reball.
I have left only 1001 but not have time and confidence this water damage board will ever work in normal condition.
 
Last edited:
I'm looking for suggestions if anyone has any ideas for trying to fix what's looking like a brick at this point on my CECHA model. I may hook this up to my syscon reader to try to pull error codes if needed, but if anyone has any clever suggestions for the issue i'm having i'm all ears.

So the timeline is this: I was attempting to install a 1.5 tb internal HD to this console. I was told by another user on this site, that I will need to downgrade to a 4.46 CFW first to accomplish this. So I did. I installed Habib 4.46 v. 1.03. It took the update fine and booted into XMB. I then turned off the console, swapped out the HD. It appeared to upgrade it fine initially. It formatted it, booted back into XMB, and showed the proper space in system info. The problem started when I tried to re-install 4.88 CFW. I attempted this thru the XMB, it seemed to copy the file and it was acting like it was moving toward the actual installation process, but instead of updating the FW, it just shut the console off instead of updating the firmware.

Ever since this happened, I cannot get into the XMB, and I cannot get this ps3 to read any HD I put into it (even with full formatting it on a pc. I've tried several). I've tried every single option in recovery to no avail. With different hd's too. It keeps giving me, "the system storage cannot be accessed". I'm honestly stumped, heartbroken, and pissed at myself for trying to do this at this point. I would of just settled for a 1 tb if I would of anticipated something this insane could go wrong. If anyone can offer up a good suggestion or has dealt with an issue like this before I would greatly appreciate your advice.

Note: I do have backup dumps of this console from when it was on 4.88 OFW in case that sounds like a logical path to recovery
 
Checkity_CheckYoSelf said:
I'm looking for suggestions if anyone has any ideas for trying to fix what's looking like a brick at this point on my CECHA model. I may hook this up to my syscon reader to try to pull error codes if needed, but if anyone has any clever suggestions for the issue i'm having i'm all ears.

So the timeline is this: I was attempting to install a 1.5 tb internal HD to this console. I was told by another user on this site, that I will need to downgrade to a 4.46 CFW first to accomplish this. So I did. I installed Habib 4.46 v. 1.03. It took the update fine and booted into XMB. I then turned off the console, swapped out the HD. It appeared to upgrade it fine initially. It formatted it, booted back into XMB, and showed the proper space in system info. The problem started when I tried to re-install 4.88 CFW. I attempted this thru the XMB, it seemed to copy the file and it was acting like it was moving toward the actual installation process, but instead of updating the FW, it just shut the console off instead of updating the firmware.

Ever since this happened, I cannot get into the XMB, and I cannot get this ps3 to read any HD I put into it (even with full formatting it on a pc. I've tried several). I've tried every single option in recovery to no avail. With different hd's too. It keeps giving me, "the system storage cannot be accessed". I'm honestly stumped, heartbroken, and pissed at myself for trying to do this at this point. I would of just settled for a 1 tb if I would of anticipated something this insane could go wrong. If anyone can offer up a good suggestion or has dealt with an issue like this before I would greatly appreciate your advice.

Note: I do have backup dumps of this console from when it was on 4.88 OFW in case that sounds like a logical path to recovery
Click to expand...
Teensy 2.0 and dump nands? Can be hardware or software? What errors are you see on uart ?
Enable SB debugging "w 7202 02" and use second uart port of ps3 for SB debugging log
 
vyktormvmpay25 said:
Teensy 2.0 and dump nands? Can be hardware or software? What errors are you see on uart ?
Enable SB debugging "w 7202 02" and use second uart port of ps3 for SB debugging log
Click to expand...
I haven't plugged it into Uart yet, but i'm going to shortly. I'll report back.

When you say "enable sb debugging" is there any initial commands I need to do alongside the "w 7202 02"? Is this considered an internal command? If possible can you link to instructions for this if they're out there. I got lost trying to use internal commands a few weeks ago working on a different board. I'm still very wet behind the ears using this Uart syscon reader. I basically just know how to do the "GET ERRORLOG" commands. Everything else is very fuzzy to me still and i'm having a hard time finding solid instructions for the more advanced things like internal commands, etc.
 
Checkity_CheckYoSelf said:
I haven't plugged it into Uart yet, but i'm going to shortly. I'll report back.

When you say "enable sb debugging" is there any initial commands I need to do alongside the "w 7202 02"? Is this considered an internal command? If possible can you link to instructions for this if they're out there. I got lost trying to use internal commands a few weeks ago working on a different board. I'm still very wet behind the ears using this Uart syscon reader. I basically just know how to do the "GET ERRORLOG" commands. Everything else is very fuzzy to me still and i'm having a hard time finding solid instructions for the more advanced things like internal commands, etc.
Click to expand...
Need to follow that instructions from pdf in order to enter into CXRF mode first.
http://s.go.ro/zqnqfufq
This is same pdf as first post link to github link from this thread.
After you correct eepcsum from syscon you should be able to write internal commands with small letters.
Anyway read and post here stages.
About level 1 debugging is after unit was fixed and everything is fine.
If bringup command is starting fine by message "SB starting " I assume is kind of Rsod judging by fw updates.
On internal commands is easy as "errlog" will come with last 32 errors.
But if you can start unit and can not install cfw, have you tried ofw and modify /patch again? Think there is an issue regarding qa flag disabled and that can be done easily with software and usb only if unit is booting on screen.
 
vyktormvmpay25 said:
Need to follow that instructions from pdf in order to enter into CXRF mode first.
http://s.go.ro/zqnqfufq
This is same pdf as first post link to github link from this thread.
After you correct eepcsum from syscon you should be able to write internal commands with small letters.
Anyway read and post here stages.
About level 1 debugging is after unit was fixed and everything is fine.
If bringup command is starting fine by message "SB starting " I assume is kind of Rsod judging by fw updates.
On internal commands is easy as "errlog" will come with last 32 errors.
But if you can start unit and can not install cfw, have you tried ofw and modify /patch again? Think there is an issue regarding qa flag disabled and that can be done easily with software and usb only if unit is booting on screen.
Click to expand...
Thank you for linking that. I'm not sure how I missed that.

I can start the unit, doesn't ylod or anything, but I get no display and it shuts off after about 15-20 seconds. It's also not letting me intstall OFW as well. Any firmware I have tried it's giving me the 8002F281 error. I've also tried using restore ps3 in recovery and that keeps giving me the "the system storage cannot be accessed" message.

I'll get this disassembled and try to pull some error codes to report back with. Thank you for your advice and for linking that pdf.
 
Yes you need to reach that SB second uart for debugging after you write to first uart port that command w 7202 02, you will see order and stage of loading but still may be nand corruption if hdd have power and is blinking at beginning. At least on SB debugging you may post that log and more advanced developments will tell you what corrections you have. It may help to have another pair of nands for testing. Once read original nands, write patched dumps on second nands as backup prevents.
Second uart of SB
http://s.go.ro/4t2k3p0v
Now search for example log from SB uart, is back on this thread, been posting few from slims
Read back posts from 1329.
 
Last edited:
vyktormvmpay25 said:
Yes you need to reach that SB second uart for debugging after you write to first uart port that command w 7202 02, you will see order and stage of loading but still may be nand corruption if hdd have power and is blinking at beginning. At least on SB debugging you may post that log and more advanced developments will tell you what corrections you have. It may help to have another pair of nands for testing. Once read original nands, write patched dumps on second nands as backup prevents.
Second uart of SB
http://s.go.ro/4t2k3p0v
Now search for example log from SB uart, is back on this thread, been posting few from slims
Read back posts from 1329.
Click to expand...
I'm quickly realizing i'm over my head with all of this. I do appreciate your advice, I just don't feel confident in my skills with diagnosing these things. If anyone is located in Colorado and is good with these type of diagnostics, i'd gladly pay you for your services to get this recovered if possible. I still can't believe all this occurred. Seemed like such a simple process. I do have backup dumps if that helps the situation.
 
MicrowaveEgg said:
I ran syscon on a PS3 I just picked up. Power on instantly gets YLOD flash then blinking red
The error looks to be
A0801001 = CELL Power on VRAM failure

How would I go about fixing this?

Thanks
>$ ERRLOG GET 00
00000000 A0231002 28F14D34
>$ ERRLOG GET 01
00000000 A0902120 28F14D13
>$ ERRLOG GET 02
00000000 A0231002 28F14D13
>$ ERRLOG GET 03
00000000 A0902120 28F14D02
>$ ERRLOG GET 04
00000000 A0231002 28F14D02
>$ ERRLOG GET 05
00000000 A0902120 28B1E2BD
>$ ERRLOG GET 06
00000000 A0403034 28B1E2BD
>$ ERRLOG GET 07
00000000 A0403034 28B1E23E
>$ ERRLOG GET 08
00000000 A0801001 28B1E1BB
>$ ERRLOG GET 09
00000000 A0801001 28B1E12A
>$ ERRLOG GET 0A
00000000 A0801001 27EEF189
>$ ERRLOG GET 0B
00000000 A0801001 274D12A1
>$ ERRLOG GET 0C
00000000 A0801001 269BC5AB
>$ ERRLOG GET 0D
00000000 A0801001 269BC08A
>$ ERRLOG GET 0E
00000000 A0801001 20C9CCB3
>$ ERRLOG GET 0F
00000000 A0801001 20C9A96E
>$ ERRLOG GET 10
00000000 A0801001 20C9A5B0
>$ ERRLOG GET 11
00000000 A0801001 20676A29
>$ ERRLOG GET 12
00000000 A0801001 20303711
>$ ERRLOG GET 13
00000000 A0801001 20300036
>$ ERRLOG GET 14
00000000 A0902120 202E8F1A
>$ ERRLOG GET 15
00000000 A0801001 202E8F19
>$ ERRLOG GET 16
00000000 A0801001 202E6222
>$ ERRLOG GET 17
00000000 A0801001 1F076740
>$ ERRLOG GET 18
00000000 A0801001 1F0313BE
>$ ERRLOG GET 19
00000000 A0801001 1F02FDBB
>$ ERRLOG GET 1A
00000000 A0801001 1EF5D1A7
>$ ERRLOG GET 1B
00000000 A0801001 1EEA4433
>$ ERRLOG GET 1C
00000000 A0801001 1ED3DBC3
>$ ERRLOG GET 1D
00000000 A0801001 1ED38779
>$ ERRLOG GET 1E
00000000 A0801001 1ED1FF43
>$ ERRLOG GET 1F
00000000 FFFFFFFF 1E6A6F03
>$
Click to expand...
Can you provide any history to the conole? There is a 3034 in the log, before the latest 1002's. That could mean it was reflowed/reballed and later developed tokin issues. However, we would need to see the work history on the console. Can you take a picture? I there any flux residue on the RSX? Have the tokins been replaced? If the previous person tried a tantalum mod and used bad caps or technique, it could explain those errors. The 3034 concerns me.
 
Checkity_CheckYoSelf said:
I'm quickly realizing i'm over my head with all of this. I do appreciate your advice, I just don't feel confident in my skills with diagnosing these things. If anyone is located in Colorado and is good with these type of diagnostics, i'd gladly pay you for your services to get this recovered if possible. I still can't believe all this occurred. Seemed like such a simple process. I do have backup dumps if that helps the situation.
Click to expand...
Victor has way of eliciting that reaction. The SB diagnostics aren't super necessary. Sounds like a nand corruption to me. You can find tutorials for HW flashing the backup you made to return it to stock. I have not had to do this myself, so I can't be of much help, but you can do this. I suggest taking a break and reading about the process until you feel ready. No need to rush it. Take a break and get back to it when you feel the itch. I often get overwhelmed and feel like giving up. I'm currently in one of those funks. Just give it time, you'll feel ready in a week or 2.
 
Checkity_CheckYoSelf said:
I'm quickly realizing i'm over my head with all of this. I do appreciate your advice, I just don't feel confident in my skills with diagnosing these things. If anyone is located in Colorado and is good with these type of diagnostics, i'd gladly pay you for your services to get this recovered if possible. I still can't believe all this occurred. Seemed like such a simple process. I do have backup dumps if that helps the situation.
Click to expand...
Yes better let someone with flasher. Is good that you have dumped, ask any good developer to check in dm. Don't post them public. I assume patch and flashing back using clasic method will help. Or it may be possible with usb only if developer is understanding well this situation.
Edit
Felix I thought he understend to do it, seen him changing parts on board before. Yes that SB uart will probably tell error in memory where is failing but won't help to much without hardware flasher if is required.
 
Last edited:
vyktormvmpay25 said:
Yes better let someone with flasher. Is good that you have dumped, ask any good developer to check in dm. Don't post them public. I assume patch and flashing back using clasic method will help. Or it may be possible with usb only if developer is understanding well this situation.
Edit
Felix I thought he understend to do it, seen him changing parts on board before. Yes that SB uart will probably tell error in memory where is failing but won't help to much without hardware flasher if is required.
Click to expand...
Yea i'm honestly still a novice, i've gotten lucky with a few cap changes and reflows, but I really am not that well versed in any of this. Lately i've been breaking more things than i've been fixing.

So if i understand correctly, I must use the Teensy 2.0 in order to flash my nand backup to this? or is there a way to do it with an e3 flasher, or is that NOR only?
 
Checkity_CheckYoSelf said:
Thank you for linking that. I'm not sure how I missed that.

I can start the unit, doesn't ylod or anything, but I get no display and it shuts off after about 15-20 seconds. It's also not letting me intstall OFW as well. Any firmware I have tried it's giving me the 8002F281 error. I've also tried using restore ps3 in recovery and that keeps giving me the "the system storage cannot be accessed" message.

I'll get this disassembled and try to pull some error codes to report back with. Thank you for your advice and for linking that pdf.
Click to expand...

I have a PS3 with similar problems, it's a CECHE01MG, at what percentage the update fails?
If it's around 3% or 4% may be the same issue I have.
 
CechA CechE are nand models
https://www.psdevwiki.com/ps3/SKU_Models
Psdevwiki will show all knowledge so far.
Need teensy 2.0. It is bit complicated but if you read most tutorials should get it done with time. Just do not rush. I really recommend using socket adapters and desolder nands from board. It will be a pain. My first nand unit was bricked and after 3 months of research went to forum and judges fixed this in 2 hours probably. It was kind of paid service for that time in 2013, now I assure you that is working fine free after 4.81 release.
Edit
As note that time most of problems with algorithms were in sem001 boards. Been doing quite many at that time.
 
Last edited:
K3jpB8dH
hello, i have ps3 DECHA COK-001. previously it had GLOD i've tried to reflow RSX chip but after reflowing now it has YLOD. syscon gives me a0232102 error which means (A0232102 = IC6301 faulty (1.5v RSX_VDDIO) or in that area). I've tried to track all schematics from IC6301, IC6201,IC6003 but i was getting all the voltages except around EmotionEngine chip but it seems to be normal because i have a working CECHA and around EEGS i coudnt get any voltages too. Also i tried to change IC6301 and IC6003 from other ps3 but it didn't helped i'm still getting 2102 error. Maybe someone can give me advices what should i do next? Can it be related with bad RSX or bad RSX solder connections?Also CELL gets hot but RSX not

Also previously i was getting error A0231200 but it seems to be overheating error because when i put motherboard in a heatsink it disappeared. here's a picture:

A1-C06872-0871-44-C3-82-C0-EF5-B50-B5-FEEB.jpg


here's my syscon error log
UlYmE6zVG4
:

C1-A91-F38-30-FB-4-F43-B28-A-02-C2756-DA0-ED.jpg
 
Last edited:
vyktormvmpay25 said:
Take measurements on vdd to gnd
https://www.psdevwiki.com/ps3/index.php?curid=10453
1.8 or near 2.7 or 3.2 ohms resistance to those nec caps.
Click to expand...
i've tested RSX nec caps from both sides and i got 3.0ohms, on a working motherboard i got 4.1ohms, i'm sorry if i didn't understand correctly because i'm new to this. I thought about trying to change RSX caps if won't find the problem i will try to change 4 caps to new original nec
 
Not cap's are your problem. Reball tandem is a must, try reball rsx first and then you should have same measurements or over 2.7 ohms is a good value. If you exchange Nec caps with tantal caps completely you should have about 3.7 ohms which is best value for 90nm rsx. Difficult to explain exactly everything. You just need learn with time without rushing.
Last resort is cell (cpu) reball because is a tandem process but not many people doing this.
 
Hello y'all
I did a Syscon on my CECHK01 (board DIA-002) and got this errors -after replacing one tokin-

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

Can anybody help me out with this? please.

P.S: Before replacing the tokin I was getting this error:

===================================
ERR 00: FFFFFFFF Magic
ERR 01: 00000000 A0093004 FFFFFFFF
ERR 02: 00000000 A0093004 FFFFFFFF
ERR 03: 00000000 A0093004 FFFFFFFF
ERR 04: 00000000 A0093004 FFFFFFFF
ERR 05: 00000000 A0093004 FFFFFFFF
ERR 06: 00000000 A0093004 12B4671B
ERR 07: 00000000 A0093004 12B46717
ERR 08: 00000000 A0093004 12B46710
ERR 09: 00000000 A0093004 12B44196
ERR 10: 00000000 A0093004 12B383C3
ERR 11: 00000000 A0093004 12B383C0
ERR 12: 00000000 A0093004 12B383BD
ERR 13: 00000000 A0093004 12B383BA
ERR 14: 00000000 A0093004 12B383AF
ERR 15: 00000000 A0093004 12B38394
ERR 16: 00000000 A0093004 12B3838F
ERR 17: 00000000 A0093004 12B03012
ERR 18: 00000000 A0093004 12B0300D
ERR 19: 00000000 A0093004 12A88394
===================================

maybe I did something wrong? I messed up?
 
ps06 said:
. I thought about trying to change RSX caps if won't find the problem i will try to change 4 caps to new original nec
Click to expand...
If it makes you feel better, but just know that error is unrelated. Bad tokins cause 1002's.

I would have you ask yourself, "why am I jumping to tokins as if they are some kind of magic fix?"

Diagnose the problem, fix that. Don't fix what ain't broke just because you haven't found a diagnosis.

Okay, with that PSA out of the way, let's get more details shall we. Have you troubleshooted the board (shorts, voltages, fuses, etc)? Try @botakompong's method, it can narrow down the problem area. Read this.

GLOD is potentially worse than the YLOD because RSXRAM going bad, or its bumps, can cause it. A reflow can reform the bad bump (maybe), but it could be incomplete or squeeze the bump out of the underfill depending on your reflow method. Did you thoroughly dry the board before the reflow? What flux did you use? How was the reflow performed? Temps, tools, and technique?

Are you sure the balls flowed? Did you nudge the chip to be certain? I ask because this sounds like an incomplete reflow.
 
You must log in or register to reply here.

Similar threads

Back
Top