PS3 Frankenstein PHAT PS3: CECHA with 40nm RSX

Hi guys, I need help on a PS3 COK-002. The PS3 turns on and shows a black screen, and after 20 seconds it turns off by itself. I only notice that before turning off the hard disk's orange LED lights up, without giving a YLOD error and without giving a flashing red LED. It turns on and off, the syscon does not show any errors. Any help is appreciated. I have never had such a strange problem.
Overheating?
 
Probably a dumb question but how did I just frankenstein a PS3 on 2.50? Ive always had issue with anything under like 3.42 FW and a 40nm.

It does appear to have CFW. Is it really on 2.50?
 
Probably a dumb question but how did I just frankenstein a PS3 on 2.50? Ive always had issue with anything under like 3.42 FW and a 40nm.

It does appear to have CFW. Is it really on 2.50?
Yeah that doesn't sound right, I'm not sure CFW that low even exists. I certainly can't find any .PUPs for CFW below ~3.4X
 
Hi guys, I'd like to share my story to see if I'm unique. This situation has happened to me a couple of times and I can't explain it.

I have a perfectly working PS3 Slim 25xx, RSX 40Nm, RSX_VDDC measurement of 1.4 Ohm, a low value for a RSX 40Nm. But since the PS3 Slim appears to be working, I proceeded to recover the RSX 40Nm and then perform a Frankie on a PS3 60GB. Result? Frankie not working. Instant YLOD, with no errors in the Syscon.

I then replaced the RSX 40Nm with a new one with a RSX_VDDC value of 2.8 Ohm, and the PS3 Frankie works perfectly!

I reinstalled the RSX 40 Nm RSX_VDDC 1.4 Ohm on my PS3 Slim 25xx and it works perfectly again.

My question is: why, if I use the RSX 40 Nm RSX_VDDC 1.4 Ohm on the Frankie, it doesn't work, showing instant YLOD, while on the Slim it works perfectly?
 
Im willing to bet if you lowered vddc in syscon it would have worked. Two things have caused ylod with no error codes for me. A bad RSX and vddc being too high for the RSX. It's usually those super slim RSX's I have issue with.

I don't know the addresses off the top of my head to change vddc. It's probably easier to just use syscon general or something similar:

 
That shouldn't be possible. A firmware that low should give 1701 with a 40nm installed.
I installed GTAV and it didnt ask to update FW so it must be on a higher FW. I didnt know you could spoof the FW or what exactly it does. I just had to un-frankenstein another unit with 1701 that was on 2.53FW.
 
I installed GTAV and it didnt ask to update FW so it must be on a higher FW. I didnt know you could spoof the FW or what exactly it does. I just had to un-frankenstein another unit with 1701 that was on 2.53FW.
You don't need to do all of that. Buy a flashcat, manually patch the nands and do a blind update with 3.55
 
I installed GTAV and it didnt ask to update FW so it must be on a higher FW. I didnt know you could spoof the FW or what exactly it does. I just had to un-frankenstein another unit with 1701 that was on 2.53FW.
Hmm that's quite strange but yeah installing GTA 5 would indicate it's a spoofed FW, but IDK why someone would do that.
 
Back
Top