PS3 Project RSX Boost: Overclock your Retail PS3 RSX Speeds (ps3 cfw only)

Hi guys! I have a PS3 Slim CECH-2503c datacode 0D that i bought from a second hand store, i updated it with the Evilnat CFW 4.90 OC version and runs flawless but now i wanna upgrade it to 4.91 but also adding more OC to the RSX so i was wondering if you guys can recommend me which OC is the best for this model. Thanks in advance
Step by step, bit by bit
It is the answer
 
@RIP-Felix how's the testing going? Any new updates?
Today I have been focusing on the DEH-2000A-A, which is a 21xx prototype. So I haven't looked at overclocking yet. Was going to, but we'll see what I get time for.

Specifics. The LV1 rsx string contains the Hex representation of the VID. like 0x22. Convert that to binary and it can be looked up in the VID table of the datasheet for the buck controller. What @M4j0r found were the addresses in syscon eeprom that you can write that hex value to, and that will be used to select the RSX voltage.

Here's the problem and reason I've not yet released specifics. The VID tables I made to map the hex VID to the binary vid that encodes a specific voltage are not matching up perfectly with every RSX VID that I'm seeing in the 150 or so consoles I've recored the LV1 rsx strings. For example, my surtees has a VID of 0x2B which would map to 1.375v and that's WAY too high. I don't trust what my table is saying that is supposed to be. But it works for most consoles in the 20 to 28 range. I'm trying to figure out why.

I dont want to release the tutorial until I'm reasonably sure the VID tables I made arent going to cause you to think you're changing from 0.900v to 0.910v, only for it to jump to 1.600v and fry your console!
 
Last edited:
Hi guys! I have a PS3 Slim CECH-2503c datacode 0D that i bought from a second hand store, i updated it with the Evilnat CFW 4.90 OC version and runs flawless but now i wanna upgrade it to 4.91 but also adding more OC to the RSX so i was wondering if you guys can recommend me which OC is the best for this model. Thanks in advance

It is silicon lottery. 25xx models starts from GPU 700/ VRAM 850 and more if you have lucky sample.
 
As I know LV1 has information about rsx revision. May be it's the thing


what about LV1 rsx revision?

I mean
rsx40 a01 850/850 vpe:ff shd:7d [AP0022738:0:1:8:17:f:2:0:2][28:0:a:0:1:0:1][1:1:0]
Sony calls this the boot0_revision or lets say "Video BIOS version", it was never clarified wether you can map this version to the suffix of the RSX identifier like (theoretical example):
a01 -> CXD5300AGB
a02 -> CXD5300A1GB
a03 -> CXD5300CGB
 
Brother after using e3 flasher my ps3 in continuously showing please wait screen and nothing?
I can't really help you with this, I never had to use it myself. Sorry.
Sony calls this the boot0_revision or lets say "Video BIOS version", it was never clarified wether you can map this version to the suffix of the RSX identifier like (theoretical example):
a01 -> CXD5300AGB
a02 -> CXD5300A1GB
a03 -> CXD5300CGB
I don't know how it works, but mine is a CXD5300CGB and in the LV1 RSX string, it says "a01".

Code:
rsx40 a01 800/1000 vpe:ff shd:3f [AP0022751:0:1:6:a:1a:2:0:2][1f:0:a:0:1:0:1][1:1:0]
That would be great to find a way to identify the RSX model just by looking at this !
 
Last edited:
I can't really help you with this, I never had to use it myself. Sorry.

I don't know how it works, but mine is a CXD5300CGB and in the LV1 RSX string, it says "a01".

Code:
rsx40 a01 800/1000 vpe:ff shd:3f [AP0022751:0:1:6:a:1a:2:0:2][1f:0:a:0:1:0:1][1:1:0]
That would be great to find a way to identify the RSX model just by looking at this !
my ps3 has CXD2991EGB
 
Not that I know of, unfortunately.
If you are really stuck without being able to update through safe mode, all I can think of is to use a hardware flasher.
First I flashed the 4.91 version using the e3 flasher but after flashing the firmware was not installing so I again flashed the 3.55 version and after that the display stopped coming on my PS3
 
Today I have been focusing on the DEH-2000A-A, which is a 21xx prototype. So I haven't looked at overclocking yet. Was going to, but we'll see what I get time for.

Specifics. The LV1 rsx string contains the Hex representation of the VID. like 0x22. Convert that to binary and it can be looked up in the VID table of the datasheet for the buck controller. What @M4j0r found were the addresses in syscon eeprom that you can write that hex value to, and that will be used to select the RSX voltage.

Here's the problem and reason I've not yet released specifics. The VID tables I made to map the hex VID to the binary vid that encodes a specific voltage are not matching up perfectly with every RSX VID that I'm seeing in the 150 or so consoles I've recored the LV1 rsx strings. For example, my surtees has a VID of 0x2B which would map to 1.375v and that's WAY too high. I don't trust what my table is saying that is supposed to be. But it works for most consoles in the 20 to 28 range. I'm trying to figure out why.

I dont want to release the tutorial until I'm reasonably sure the VID tables I made arent going to cause you to think you're changing from 0.900v to 0.910v, only for it to jump to 1.600v and fry your console!
Oh ok. Damn it's seeming to be a mission. Hopefully you can crack it:) this will be so awesome once done correctly and safely. Glad you're thinking about the safety of the consoles. Wouldn't want to fry good working high Overclocking models.
 
I can't really help you with this, I never had to use it myself. Sorry.

I don't know how it works, but mine is a CXD5300CGB and in the LV1 RSX string, it says "a01".

Code:
rsx40 a01 800/1000 vpe:ff shd:3f [AP0022751:0:1:6:a:1a:2:0:2][1f:0:a:0:1:0:1][1:1:0]
That would be great to find a way to identify the RSX model just by looking at this !
how to find it?
 
Today I have been focusing on the DEH-2000A-A, which is a 21xx prototype. So I haven't looked at overclocking yet. Was going to, but we'll see what I get time for.

Specifics. The LV1 rsx string contains the Hex representation of the VID. like 0x22. Convert that to binary and it can be looked up in the VID table of the datasheet for the buck controller. What @M4j0r found were the addresses in syscon eeprom that you can write that hex value to, and that will be used to select the RSX voltage.

Here's the problem and reason I've not yet released specifics. The VID tables I made to map the hex VID to the binary vid that encodes a specific voltage are not matching up perfectly with every RSX VID that I'm seeing in the 150 or so consoles I've recored the LV1 rsx strings. For example, my surtees has a VID of 0x2B which would map to 1.375v and that's WAY too high. I don't trust what my table is saying that is supposed to be. But it works for most consoles in the 20 to 28 range. I'm trying to figure out why.

I dont want to release the tutorial until I'm reasonably sure the VID tables I made arent going to cause you to think you're changing from 0.900v to 0.910v, only for it to jump to 1.600v and fry your console!
Does the voltage maybe increase logarithmically then? Given that 0x2B is 1.375V according to your table, but 0x22 is less than 1V, if I understand correctly, since that's only 9 steps lower the 2B, it should be closer to 1.375 but obviously isn't.

EDIT: I'm not sure what the voltage range of the RSX, probably above 1V though since it's a 40nm we're talking about.
 
Last edited:
REBUG 4.84.2 REX RSX OVERCLOCKED 600/750 (GPU & GDDR3 RAM Clocks)
https://www.psx-place.com/threads/p...etail-ps3-rsx-speeds.36801/page-5#post-327491

REBUG 4.84.2 D-REX OVERCLOCKED 600/750 (GPU & GDDR3 RAM Clocks)
https://www.psx-place.com/threads/p...etail-ps3-rsx-speeds.36801/page-5#post-327507

EVILNAT 4.88.2 OVERCLOCKED 600/750 (GPU & GDDR3 RAM Clocks)
https://www.psx-place.com/threads/p...your-retail-ps3-rsx-speeds.36801/#post-327145

EVILNAT 4.88.2 OVERCLOCKED 550/750 & 600/700 (GPU & GDDR3 RAM Clocks)
https://mega.nz/folder/v1tgAJqS#Gz0uL9KpgygAHgwZs5NH-w
plz share the link of 4.88.2 OverClocked cfw sir above link is dont give me the access
 
Finally got to overclock my 2504B some more and for now I went from 700/900 to 850/975, I'm too scared to try 1000 and I need to be absolutely sure 850 is stable but at least 30 min of 560 ducks worked without issues

rsx40 a01 850/975 vpe:ff shd:3f [L6B891800:0:2:10:a:16:3:0:2][1f:0:a:0:1:0:1][1:1:0]
 
The RSX string ? You need to dump your LV1 with Evilnat extraction tools, then open the file with a program like HxD. Search for your current RSX speeds ("500/650" for example) and you will find it.


Why do you need this Evilnat version ?
Because old Versions don't have overclocked firmware and my collection also
 
Finally got to overclock my 2504B some more and for now I went from 700/900 to 850/975, I'm too scared to try 1000 and I need to be absolutely sure 850 is stable but at least 30 min of 560 ducks worked without issues

rsx40 a01 850/975 vpe:ff shd:3f [L6B891800:0:2:10:a:16:3:0:2][1f:0:a:0:1:0:1][1:1:0]
If you can test Crysis HD (Crysis 1), it would be better than the duck test.
The beginning of the 4th mission is particularly good for testing.
• Just stay still here, it's a safe place.
• Make sure your controller doesn't disconnect, or the pause menu will pop.
• Let your console reach at least 70°C, max 75. A 71°C target is enough.
• With water, explosions, smoke, sparkles, this place is great for stressing the GPU.
• If after a good hour you don't encounter artifacting or freezing, then your OC is stable !
• I can provide a save file if needed.
IMG_20240609_220400.jpg

@SiegHart93
https://github.com/MitsuTM/PS3_CFW_...k/750_850_BETA9_PEX.pup_4.91.CEX-PS3UPDAT.zip

(My MediaFire account is full btw.)
 
Last edited:
Back
Top