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

here's the folder with the builds
edit: deleted due to the fact that the pups brick the system.

DISCLAIMER: THESE HAVEN'T BEEN TESTED YET! TRY THEM WITH A HW FLASHER IN HAND! YOU HAVE BEEN WARNED!
 
Last edited:
@zecoxao when I'm on the OC CFW and try to open RDR, the PS3 shuts down, gives the three beeps and the power LED starts blinking red every time. all other games run fine for extended periods of time (tested GTA V, IV, MGS4, WRC5, L.A. Noire, and KZ2). tried reinstalling the game, erasing data, nothing worked, went back to stock CFW and the game runs normally.
I suspect the OC may trigger some sort of instability with RDR, since the game crashes as soon as it tries to go to the title screen, where the world is rendered in real time. I tried following your guide to make a MFW with the lower OC values, but I'm having issues with MFW builder, it always gives me errors.

any chance you could perhaps build a 600/700 or 550/750 that I could test in my specific case?

chances are I just lost the sillicon lottery with my 65nm RSX.

Try RDR on the Rebug CFW patched with the OC and report it back, Evilnat firmware has some game bugs with new cobra.
 
Last edited:
@zecoxao
were those pups that bricked, created with mfwbuilder? if so, how did you reencrypt the elf files, cause you have to use scetool on compressed self files and on Rebug, CoreOS is compressed with scetool
 
here you go ;)
8XAAmWk.jpg
For completionism... you could add the other combinations with the default clocks (and even some more for underclocks)
Im not sure how is the best way to display them in MFW, but i guess it could be splitted in 2 different tasks:

Patch RSX clock (core)
-400MHz
-450MHz
-500MHz (default)
-550MHz
-600MHz

Patch RSX clock (memory)
-550MHz
-575MHz
-600MHz
-625MHz
-650MHz (default)
-675MHz
-700MHz
-725MHz
-750MHz

Is easyer to split them because there are a lot of posible combinations... and yeah the ones marked as "default" are not really a patch so i guess should be displayed in a special way (greyed out or something like that)
 
Last edited:
@zecoxao
were those pups that bricked, created with mfwbuilder? if so, how did you reencrypt the elf files, cause you have to use scetool on compressed self files and on Rebug, CoreOS is compressed with scetool

Teach me how to use mfwbuilder then. besides the option for 4.xx CEX base firmware and LV1 RSX patch i haven't changed anything else.
 
Teach me how to use mfwbuilder then. besides the option for 4.xx CEX base firmware and LV1 RSX patch i haven't changed anything else.
I am sorry that it is a bit confusing with the global options, but I think I have added the info on the readme, but well...

by default isorebuilder and selfrebuilder are selected for the mod version. to make use of scetool and template resigning, you have to untick both rebuilder options

089FjSo.jpg
 
I am sorry that it is a bit confusing with the global options, but I think I have added the info on the readme, but well...

by default isorebuilder and selfrebuilder are selected for the mod version. to make use of scetool and template resigning, you have to untick both rebuilder options

089FjSo.jpg

scetool should be used by default and those options removed :)
either that or xorloser's SecureTool, which contains all necessary keys AND maintains the section names (not to mention it also provides an alternative to --template option using -g and -s )
 
Although I haven't used this tool, something similar happened to me once I had some issues with my PS3 and took the HDD out while it was freezed up (but not shut off)
Upon reentering the HDD, the System would shut off immediately and always panic crash 3 secs after turning it on, unless I put in another drive (doesnt matter which one). Even after I formatted it countless of times it still wouldnt stay turned on.
The solution? Low-Level Format your drive! You could try that, get an extra tool for that stuff since your default Windows stuff won't cut it but it worked in my case for sure!
I had this issue with my first PS3, I tried to format a new hard drive and it was always crashing, making the console shutdown I think on 60% or something. Tried to format on Windows and this issue still persisted, tested the drives and there were no bad blocks. What fixed was formatting on Linux with gparted. The MBR was corrupted somehow, when I clicked on Devices> Create a partition table > MSDOS and then connected to the console and it worked, formatted and installed the cfw fine.
I had this same issue on other devices but at the time I didnt know the exact cause and was always using a Windows 98 disc because for some reason, XP onwards dont fix these kinds of MBR issues and learning on Linux is better because I can do it on any modern computer.
 
scetool should be used by default and those options removed :)
either that or xorloser's SecureTool, which contains all necessary keys AND maintains the section names (not to mention it also provides an alternative to --template option using -g and -s )
tbh, I like self-/isorebuilder most, cause it maintains identical self-size without custom compression.

and about SecureTool, I have tried it with COBRA-payload modified lv2kernel, but it does not resign correctly with template or regularly like scetool. maybe xorloser can take a look at it?
 
tbh, I like self-/isorebuilder most, cause it maintains identical self-size without custom compression.

and about SecureTool, I have tried it with COBRA-payload modified lv2kernel, but it does not resign correctly with template or regularly like scetool. maybe xorloser can take a look at it?

Already removed iso and self rebuilder from my own repo. haven't had a brick since. i suspect that the mfw that someone sent me to "fix" the bluray drive issue had self and isorebuilder options included, which was why it bricked the CECHA
 
Back
Top