PS3 B01 troubles of a different kind

RCWD21

Member
Ok so here's the dilemma I'm having with a b01 ps3.
A few years ago I bought a working b01 ps3 on 2.83 ofw and after testing it iirc I found the laser was iffy so I just swapped in a known working drive from an a01. I kept the daughter boards with their respective motherboards and as far as I can remember it worked fine so at that time I decided to update it to I think 4.87 downloaded to a USB directly from Sony's website. As most of you know 2.83 doesn't have a recovery menu so I'm stuck.

Upon starting the update it froze so after a fair while of waiting I decided to cut the power (I left it for like an hour I think before flipping the switch).
Since then it will only turn on and remain on for 56 seconds timed via my phone. It does not shut down like a ylod issue, it simply returns to the red standby light with a very light click noise which I am still unsure of what that is, it sounds like a ultra tiny relay clicking.
I've pulled the syscon log and the only error code it gave was Cell power issue syscon code 1001 (this was before replacingthe caps, I haven'thooked it back up to check the syscon again.

I've replaced the nec tokins with 470uf 2.5v tantalum caps as per the help of @Workz_777 and it still does the same thing. I've attached some 30awg kynar wire to the positive and negative side of the caps and with a volt meter I get 1.15 volts constantly until the console shuts off, I'm unable to verify if that is the proper voltage I should be seeing though.

Does that sound like bad tantalum caps or something else?

I've already swapped power supplies to rule that out. All parts swapped have come from fully functioning consoles
 
Ok so here's the dilemma I'm having with a b01 ps3.
A few years ago I bought a working b01 ps3 on 2.83 ofw and after testing it iirc I found the laser was iffy so I just swapped in a known working drive from an a01. I kept the daughter boards with their respective motherboards and as far as I can remember it worked fine so at that time I decided to update it to I think 4.87 downloaded to a USB directly from Sony's website. As most of you know 2.83 doesn't have a recovery menu so I'm stuck.

Upon starting the update it froze so after a fair while of waiting I decided to cut the power (I left it for like an hour I think before flipping the switch).
Since then it will only turn on and remain on for 56 seconds timed via my phone. It does not shut down like a ylod issue, it simply returns to the red standby light with a very light click noise which I am still unsure of what that is, it sounds like a ultra tiny relay clicking.
I've pulled the syscon log and the only error code it gave was Cell power issue syscon code 1001 (this was before replacingthe caps, I haven'thooked it back up to check the syscon again.

I've replaced the nec tokins with 470uf 2.5v tantalum caps as per the help of @Workz_777 and it still does the same thing. I've attached some 30awg kynar wire to the positive and negative side of the caps and with a volt meter I get 1.15 volts constantly until the console shuts off, I'm unable to verify if that is the proper voltage I should be seeing though.

Does that sound like bad tantalum caps or something else?

I've already swapped power supplies to rule that out. All parts swapped have come from fully functioning consoles
Maybe hdd is taking a poop.?
 
Maybe hdd is taking a poop.?
It's been checked and has passed every read and write test I've thrown at it. I've even left it out to see if I'd get that error message and nothing. Itjust stays powered in for 48 seconds now (I timed it earlier) before shutting off just like it did to me originally.

I'm going to be rechecking the syscon and see if anything is different

Sent from my SM-G965U using Tapatalk
 
Have you tried putting in another HDD and try reinstalling firmware I'd recommend evilnats CFW for it.
I'm getting nothing, no display, no sound just a console that powers on for 48 seconds and then goes back to standby. Over and over again.

This isn't a it boots but doesn't work issue this is a it boots but doesn't do anything besides turn on issue.....

Sent from my SM-G965U using Tapatalk
 
Does anyone have any idea what the issue could be? I know I need to access the syscon again but I need some guidance on this as I'm in uncharted territory for myself with these consoles and no amount of research that I've done has shown any similarities with others posts

Sent from my SM-G965U using Tapatalk
 
Have you tried putting back the original BD drive?. Maybe the system is trying to match the hardware IDs during the boot process and is failing because of the recent swap.
 
So I bought one on 1.80 and I had similar troubles. I had to update to 3.55 then from there install CFW. Now despite no recovery menu you can still install as long as you power cycle then hold the button till it beeps again. Just ensure the drive is formatted properly and named correct.
 
Have you tried putting back the original BD drive?. Maybe the system is trying to match the hardware IDs during the boot process and is failing because of the recent swap.
There's no need, I kept the daughter board with the original motherboard and just swapped the physical drive assembly.

Sent from my SM-G965U using Tapatalk
 
So I bought one on 1.80 and I had similar troubles. I had to update to 3.55 then from there install CFW. Now despite no recovery menu you can still install as long as you power cycle then hold the button till it beeps again. Just ensure the drive is formatted properly and named correct.
I'll have to see if I can find 3.55 again and I'll give it a shot but I dont have high hopes for it working unfortunately.

Tonight I'm going to check the syscon again and make sure there aren't any errors stored like when I first started.

Sent from my SM-G965U using Tapatalk
 
I'll have to see if I can find 3.55 again and I'll give it a shot but I dont have high hopes for it working unfortunately.

Tonight I'm going to check the syscon again and make sure there aren't any errors stored like when I first started.

Sent from my SM-G965U using Tapatalk
I've tried power cycling the console several times with no luck on it trying to do anything.

The HDD is blank and I have 3.55 on a thumb drive, no luck

I'm about to resolder the wires back to the MB to access the syscon again and I'll go from there.

Sent from my SM-G965U using Tapatalk
 
UPDATE! I am back in the error log and cleared it. The only code I'm getting currently is 0xa0801001. Which is BE VRAM Power Fail.

I've replaced the nec caps with 12 470uf tantalum caps with bridge wires. During power state in syscon I have "ON" for ATA, RSX, XDR Eurus, and SB. The only one that is "OFF" is PCI.

I'm unsure what to do next, send help [emoji23]

Sent from my SM-G965U using Tapatalk
 
UPDATE! I am back in the error log and cleared it. The only code I'm getting currently is 0xa0801001. Which is BE VRAM Power Fail.

I've replaced the nec caps with 12 470uf tantalum caps with bridge wires. During power state in syscon I have "ON" for ATA, RSX, XDR Eurus, and SB. The only one that is "OFF" is PCI.

I'm unsure what to do next, send help [emoji23]

Sent from my SM-G965U using Tapatalk
Possibly bad tokens somewhere .
 
I've already replaced them with tantalums... I'm going to order some different ones and see if these are just duds but where else should I be looking?

Sent from my SM-G965U using Tapatalk
Both cpu and rsx? On both sides of the motherboard?
 
Both cpu and rsx? On both sides of the motherboard?
Just for the Cell on both sides of the MB. Havent touched RSX caps because none of the codes I've gotten indicate there's anything wrong with them.

I've never gotten any codes relating to the RSX only 1001 which is for the Cell.

Sent from my SM-G965U using Tapatalk
 
20200206_073046.jpg
20200206_073055.jpg
Just for the Cell on both sides of the MB. Havent touched RSX caps because none of the codes I've gotten indicate there's anything wrong with them.

I've never gotten any codes relating to the RSX only 1001 which is for the Cell.

Sent from my SM-G965U using Tapatalk
Bad tantalums possibly, I had good luck with one's off off dead ps3's.:D
 
Last edited:
View attachment 37329 View attachment 37330
Bad tantalums possibly, I had good luck with one's off off dead ps3's.:D
I'm going to order some different ones and try replacing these if I don't have enough from other boards.

I'm not understanding how it's showing fully powered on and then just acts like I gave it the shutdown command.

Do you know what voltage I should be seeing at the tantalums?

Sent from my SM-G965U using Tapatalk
 
I'm going to order some different ones and try replacing these if I don't have enough from other boards.

I'm not understanding how it's showing fully powered on and then just acts like I gave it the shutdown command.

Do you know what voltage I should be seeing at the tantalums?

Sent from my SM-G965U using Tapatalk
2.5V per tantalum, to get accurate reading you might have to remove them, you need the same voltage the cpu had with the original tokins, the goal is to get that voltage as close as possible with tantalums. They store voltage so the cpu never starves for voltage.

I also was thinking about your power button. And ribbon cable I've had issues with those before.
 
2.5V per tantalum, to get accurate reading you might have to remove them, you need the same voltage the cpu had with the original tokins, the goal is to get that voltage as close as possible with tantalums. They store voltage so the cpu never starves for voltage.

I also was thinking about your power button. And ribbon cable I've had issues with those before.
Ok so me seeing 1.15v is obviously way too low then.

Besides the tantalums where else should I check for voltage to see if something else on the board is bad or failing?

Sent from my SM-G965U using Tapatalk
 

Similar threads

Back
Top