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

[tristen8878]

Damn that's horrible silicon luck.

650core 750mem so sad about it not sure how unlucky I can get. I does go to 850 on core but with more artifacting but gta 4 is one of the few games to show it at such low clock speeds.

 

[Tanzu15]

650core 750mem so sad about it not sure how unlucky I can get. I does go to 850 on core but with more artifacting but gta 4 is one of the few games to show it at such low clock speeds.

This is just terrible silicon luck sadly. I have 4 slims. All are 2501A and 2501B and they all handle 700 core and above easily stable with memory at 950 easy. Your model gotta be some early 2010 or late 2009 model. This is the first PS3 I've seen on here this unlucky.

 

[haxxxen]

@LuanTeles
you are trying the _rebuilders, so are you using an OFW? on CFW, almost all coreos files are compressed, so the _rebuilders will fail with a broken file, or they error out.

have you added 4.91 keys with batch or manually? you can also just copy the latest key files and rename them to -491. but keep in mind, there are several key files to update/add (one for each type). also the "ps3keys" folder has to be copied over to user root directory, so to your "Luan" folder

scetool has a single, but different keyfile, found in data folder

I really wonder why so many users have problems with this tool, where I never ever had a single problem. though, I am using it from the very first hour of its existence

 

[Tanzu15]

@LuanTeles
you are trying the _rebuilders, so are you using an OFW? on CFW, almost all coreos files are compressed, so the _rebuilders will fail with a broken file, or they error out.

have you added 4.91 keys with batch or manually? you can also just copy the latest key files and rename them to -491. but keep in mind, there are several key files to update/add (one for each type). also the "ps3keys" folder has to be copied over to user root directory, so to your "Luan" folder

scetool has a single, but different keyfile, found in data folder

I really wonder why so many users have problems with this tool, where I never ever had a single problem. though, I am using it from the very first hour of its existence

Bro I just read all this. And didn't understand a single damn thing bro seriously like I told the other guy. Make a video. Sometimes this type of thing is best understood with video tutorial/example. A lot of us are simple homebrew users. So we know basic shit only. Installing package files maybe navigating through the file system etc etc. A lot of these tools are lost on us. It's like looking at Chinese gibberish.

 

[bizarrewitness]

Bro I just read all this. And didn't understand a single damn thing bro seriously like I told the other guy. Make a video. Sometimes this type of thing is best understood with video tutorial/example. A lot of us are simple homebrew users. So we know basic shit only. Installing package files maybe navigating through the file system etc etc. A lot of these tools are lost on us. It's like looking at Chinese gibberish.

you need to chill with the demands bro. The Internet is filled with resources if you really want to learn how to do something. His response wasn't for you either way.

I get we're all excited for the advancements with this overclock but take it easy. They put in the time to get to where we are now.

 

[Charles_n_town]

@LuanTeles
you are trying the _rebuilders, so are you using an OFW? on CFW, almost all coreos files are compressed, so the _rebuilders will fail with a broken file, or they error out.

have you added 4.91 keys with batch or manually? you can also just copy the latest key files and rename them to -491. but keep in mind, there are several key files to update/add (one for each type). also the "ps3keys" folder has to be copied over to user root directory, so to your "Luan" folder

scetool has a single, but different keyfile, found in data folder

I really wonder why so many users have problems with this tool, where I never ever had a single problem. though, I am using it from the very first hour of its existence

I think it's a permissions issue. I have mine in Program Files (x86), but I had to add full privileges to Users, and it works perfectly. I would suggest putting mfw at root of c for those who have issues with it.

 

[Tanzu15]

you need to chill with the demands bro. The Internet is filled with resources if you really want to learn how to do something. His response wasn't for you either way.

I get we're all excited for the advancements with this overclock but take it easy. They put in the time to get to where we are now.

I'm perfectly chill Brody just saying this tool isn't as easy to use and understand as they keep saying. You gotta understand there's people with way less general knowledge than others.

 

[RIP-Felix]

Just dropped in to say I no longer think the Core Voltage can be increased. And that B_rob, @Nascar1243, and I did successfully manage to volt mod VRAM. I'm not ready to share how. And this is why...

The gains aren't worth it

@Nascar1243 had a 21xx model brick with 1000MHz VRAM OC. It was stable at 950, but 1GHz would freeze before XMB loaded. Couldn't install back to 950 in Safe Mode without freezing. But at 2v_FBVDDQ it booted into XMB. It was not stable and
the volt mod produced so much heat he had to run the fan's at 100% to keep it from overheating. But it was stable enough to install back to a stable OC. That's about all the utility we got out of it.

So I think that's the end of volt modding. While it did allow him to unbrick, it doesn't make a meager 50MHz OC stable, even with +200mV requiring 100% fans to keep cool.

 

[Tanzu15]

Just dropped in to say I no longer think the Core Voltage can be increased. And that B_rob, @Nascar1243, and I did successfully manage to volt mod VRAM. I'm not ready to share how. And this is why...

@Nascar1243 had a 21xx model brick with 1000MHz VRAM OC. It was stable at 950, but 1GHz would freeze before XMB loaded. Couldn't install back to 950 in Safe Mode without freezing. But at 2v_FBVDDQ it booted into XMB. It was not stable and
the volt mod produced so much heat he had to run the fan's at 100% to keep it from overheating. But it was stable enough to install back to a stable OC. That's about all the utility we got out of it.

So I think that's the end of volt modding. While it did allow him to unbrick, it doesn't make a meager 50MHz OC stable, even with +200mV requiring 100% fans to keep cool.

I nearly bricked mine too At 1000mhz memory I kept trying recovery mode over and over again until the update finally went through. Had to have my room fan blasted full speed on the PS3 to keep it as cool as possible, and that's how I'm here now with 900/950. I almost lost the PS3. Honestly no one should even dare try 1000. It's too big of a risk. There's no warning either. You're fully stable at 950 and 50mhz more destroys your PS3.

 

[Nate8893]

Hello everyone, i jumped on the trend yesterday after some long reading and testing, as i'm writting this my slim cech2504b 0c date code is running stable at 700/900, unfortunately at 750 core i started to get slight artefacts on crysis and at 700/950 i had a freeze on midnightclub L.A (runs like shit stock btw) after closing crysis at theses clockspeed. to be safe i stuck with 700/900
My console is on the average bin i would say but also i have this unit for 13years now it had 300days(aproximation sicne the drive died before i went cfw) on orignal 320gb hdd and now 300 ish on a samsung 870 evo ssd quite impressive if we consider chip degradation.
Btw i dumped my lv1 but i forgot how to share it lmao sorry, if you have any question about my ps3 feel free

 

[Tanzu15]

Hello everyone, i jumped on the trend yesterday after some long reading and testing, as i'm writting this my slim cech2504b 0c date code is running stable at 700/900, unfortunately at 750 core i started to get slight artefacts on crysis and at 700/950 i had a freeze on midnightclub L.A (runs like shit stock btw) after closing crysis at theses clockspeed. to be safe i stuck with 700/900
My console is on the average bin i would say but also i have this unit for 13years now it had 300days(aproximation sicne the drive died before i went cfw) on orignal 320gb hdd and now 300 ish on a samsung 870 evo ssd quite impressive if we consider chip degradation.
Btw i dumped my lv1 but i forgot how to share it lmao sorry, if you have any question about my ps3 feel free

700/900 is still a fantastic overclock and will do a lot for many games.

 

[LuanTeles]

The CELL overclock only works on 90nm CELL. The PLL value is read by CELL before the config ring. This has been disabled on 65nm/45nm (tested).
View attachment 42958
The info can be found here: https://pastebin.com/qy3u25Av , it's also just a tweak to some Syscon EEPROM values (clockgen and PLL).

I'll investigate how the RSX clock setting from syscon can be brought back to modern firmwares and how it works in the TestBench firmware.

Thanks, keep us in touch

 

[bizarrewitness]

I'm perfectly chill Brody just saying this tool isn't as easy to use and understand as they keep saying. You gotta understand there's people with way less general knowledge than others.

I understand not everyone is going to fully comprehend what is being discussed in this thread, particularly about the mfwbuilder. I simply wanted to let you know there are politer ways to go about asking for help if you are looking for it rather than demanding people to do things for you.

 

[LuanTeles]

@LuanTeles
you are trying the _rebuilders, so are you using an OFW? on CFW, almost all coreos files are compressed, so the _rebuilders will fail with a broken file, or they error out.

have you added 4.91 keys with batch or manually? you can also just copy the latest key files and rename them to -491. but keep in mind, there are several key files to update/add (one for each type). also the "ps3keys" folder has to be copied over to user root directory, so to your "Luan" folder

scetool has a single, but different keyfile, found in data folder

I really wonder why so many users have problems with this tool, where I never ever had a single problem. though, I am using it from the very first hour of its existence

Nah, I'm trying to build from CFW and both of my rebuilder options are unchecked. I just tested with them checked to see if the behavior would be different, but it's the same thing.


The lvl1 problem was indeed due to the keys. The update keys bat was giving me errors in the second step. (I'm too lazy to do it manually.) But after Charles shared his ps3keys folder, these errors were fixed. But now I'm having another one: failed to unpack the .tar."

For those of you with a high clocking model. Can you please dump the LVL1 and post the RSX info section? I wanna test a hypothesis.

RSX	Fab	MNF	DS (Line)
40nm	2	SONY	3
40nm	4	TSMC	6
65nm	2	SONY	2
65nm	2	SONY	3
65nm	1	TOSHIBA	2
90nm	1	TOSHIBA	2
90nm	2	SONY	3

SONY line 3 is where the better VID binned (VIDbin 2) 90nm comes from. There is also a 65nm from SONY line 3 as well, but I'm not sure if anyone has overclocked one yet and compared it to those off line 2. So if the these higher clocking packages are from the SONY line 3, then they may be binned, explaining why they clock higher. Better silicon.

Or there could be no pattern and it's luck of the draw.

Is there a way to determine the manufacturer by examining the RSX string?
I think we could ask @Evilnat if he can add a function to his XAI plugin to display the information.

Could you elaborate on what we need and provide more details so Nat can modify the XAI plugin to display only the necessary information? I was specifically looking for the first code, AP00008286. What does it mean? At least I found that the codes starting with APXXXXXXXX are the ones that handle higher overclocks.

This is our outdated table (i know, i need to update as he got lots of new reports_

Outdated Table​

RSX	Rev	Max GPU Clock (Stable)	Max Memory Clock (Stable)	Full Details	Notes	PS3 Model	Owner
rsx40	a01	850 MHz	1000 MHz	vpe:ff shd:77 [AP0022017:0:1:3:e:18:2:0:1][2a:0:a:0:1:0:1][1:1:0]	Random crashes at 900 core (Only on RSX-demanding games) Can go up to 1000/1000 without bricking.	CECH-2511A	Me
rsx40	a01	850 MHz	1000 MHz	vpe:ff shd:3f [AP0029328:0:2:11:16:20:2:0:2][24:0:a:0:1:0:1][1:1:0]	CECH-2511A Can go up to 900/1000 without bricking. (Not tested on highter core)	@JoeSapecudo
rsx40	a01	700 MHz	1000 MHz	vpe:ff shd:3f [NN8941-24:0:4:18:12:18:6:0:2][25:0:a:0:1:0:1][1:1:0]	Artifacts at 750Mhz Core in specific games.	CECH-2504A	@Thimblewad
rsx40	a01	650 MHz	800 MHz	vpe:ff shd:3f [NN0078-06:0:4:6:18:4:6:0:2][25:0:2:0:1:0:1][1:1:0]	Artifacts at 700Mhz Core in specific games. Black Dots and crashes at 950 Mhz memory.	CECH-2104B	@cha0shacker
rsx65	a06	700 MHz	800 MHz	vpe:ff shd:6f [KBA857800:1:2:c:11:7:3:8:2][3d:0:2:0:1:2:0][2:1:0]	Artifacts at 750Mhz Core in specific games. 800Mhz memory is stable. WARNING: 1000 Mhz memory bricked his system.	CECH-2004B	@Mitsu™
rsx40	a01	700 MHz	1000 MHz	vpe:1bf shd:3f [NN9095-14:0:4:e:3:12:6:0:2][1e:0:a:0:1:0:1][1:1:0]	Artifacts at 750Mhz Core in specific games.	Frankenstein CECH-A00	@XDeltaOne

 

[Tanzu15]

I understand not everyone is going to fully comprehend what is being discussed in this thread, particularly about the mfwbuilder. I simply wanted to let you know there are politer ways to go about asking for help if you are looking for it rather than demanding people to do things for you.

No one was demanding anything, why do you keep saying that? Not once have I demanded anything. It was a suggestion for a method that may help much more people test. We can't hear tones in here either, so assume someone is being remotely impolite? We can't use emojis here so you can't even see people's expressions either. It ain't that serious.

 

[Yusuf Mantam]

Hello, can you help me? What are the Maximum VRAM Values and Memory Clock Speeds of My Ps3 Slim 2004a Model?

I'm using CFW OF EVILNAT 4.91.2 BETA 8. Can it be done this way? I'd be happy if you help.
600/750
650/800
700/800
700/850
I Want to Try 700/900 Speeds.

 

[Cloud-Stri]

Please Beta 8 pex or d-pex overclock 750/900

 

[shnyaps]

Tried overclocking latest firmware of evilnat B8
I get error of absent key and a fatal error could not rebuild DEVFLASH file lv1.self.self: child process exited abnormally on both errors may I please get help. I'm having issues with 491

I had the same issue. Fortunately I fixed it:
in Settings I changed ps3 keys path (See screenshot #2),
in addition to this I changed Modified Firmware Path (See screenshot #1)
And finally I did it (See screenshot #3)

 

[haxxxen]

I think I have added all necessary notes on my git, but well...you have have won...I don't like video-tutorials, but I can do some pictures let speak for it...must be the new generations, who prefer these kind of manuals?

even though, this won't prevent yourself, of doing possible damage to your console (when not exactly knowing what you are doing). in the end, I just wanted to make it more attractive and user-friendly, like an 1-click solution for modifying CFWs (not on MFW=selfmade CFW), but I never wanted to take responsibilty for any harm it could bring (unlike cfwprophet!)

besides, I think I am the only person on earth, who does explain technical stuff in layman-terms, as easy as possible, so even a young child can understand me

 

[Mitsu™]

Hello, can you help me? What are the Maximum VRAM Values and Memory Clock Speeds of My Ps3 Slim 2004a Model?

Considering NEC Tokins capacitors, 650MHz on core is the limit. 700 will work in many games, but in intensives one, the capacitors won't be able to handle it and your PS3 will crash.
So stay at 650MHz to be safe.
As for VRAM, 900MHz is the maximum for 20XX series, but don't jump directly to such value as limits varies even between same models.