I'm not aware of any service manuals for any slim motherboards being publicly available. I'd suggest buying those caps in bulk brand new since they seem to be a common failure point on COK-001 / 002 boards.
This particular CELL went from 1.16V to 1.06V. RSX went from 1.28V to 1.12V. Also the CELL / RSX temps before used to peak around 73C/65C and 28% fan speed.
I like ko-fi, I can send people donations without creating an account. I can also send monthly donations, though I assume that requires an account on my end.
So could I just write the 256MB .bin dump that was released to a separate pair of nands, then install them to any nand based motherboard? Or would I need to dump the original nands, then "patch" them with the .PUP update file that you created? (If so, this is something I would need to learn how...
The bd circuit being fully integrated on the slim board is just more non modular components that cant be easily replaced if they fail. Remarrying is easy.
Id argue the K model would probably be more reliable than the 2500 model after replacing the tokin capacitors. Its motherboard has modular USB ports and Wifi / BT… where the slim models have those soldered directly to the motherboard and shorted out wifi chips seems to be a common failure point...
You could try resetting the game from that menu. Otherwise this has been an issue with the new RSX in some cases. Replacing the RSX again may be required to fix your issue.
65nm RSX uses reliable underfill material just like the 40nm, so both are reliable and the difference in operating temps between the two doesn't matter. I recommend watching this video in full, but 1:18:50 talks about the 65nm RSX specifically if you're interested:
Feel free to check out my store page, I can fix any ripped traces at no additional charge if you're looking to get the GPU replacement service.
*** DO NOT ADVERSITE: LINK REMOVED BY MODERATOR ***
I had this issue on a CECH-A01 that had a dual lens bluray drive with a BMD-006 daughterboard. After remarrying it to another known good bluray drive of the exact same model, issue still persisted. I even changed hard drives, reinstalled the firmware twice, and reset the database and filesystem...
Hey there, I wrote this tutorial a while ago for Mac OS. Let me know if it helps you. Also worth mentioning that some commands won't show the entire output for some reason. For example, you may need to press enter multiple times after inputting the "errlog" command to see the full error log in...