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

[RIP-Felix]

i bricked it at 800mhz haha

i have lv1 and lv2 backups before oc, how can i do fix this...

You'll need your NOR backup that you should have made at the beginning of all this. Or when you jailbroke. That will allow you to use a hardware flasher to restore the original OS and unbrick. But that's a difficult process I have so far been lucky I've not had to do...yet. But you can search around the forum or start a new thread for help. "Help me Unbrick" threads have been posted a million times and you should be able to find what you're looking for.

If you have syscon access you could try increasing voltage and/or forcing the fan to 100% to stabilize the core enough to allow you to update back to a safe overclock. That's much easier than a Hardware flasher.

 

[kursatd24]

Update from my shitty overclocked and bricked 2004a

That machine cant boot into recovery

Open the top lid of the PS3 and blast a fan on it. Like a room fan. And try entering recovery mode.

I tried ur suggestion but that doesnt work mate thx to u

You'll need your NOR backup that you should have made at the beginning of all this. Or when you jailbroke. That will allow you to use a hardware flasher to restore the original OS and unbrick. But that's a difficult process I have so far been lucky I've not had to do...yet. But you can search around the forum or start a new thread for help. "Help me Unbrick" threads have been posted a million times and you should be able to find what you're looking for.

If you have syscon access you could try increasing voltage and/or forcing the fan to 100% to stabilize the core enough to allow you to update back to a safe overclock. That's much easier than a Hardware flasher.

I have a friend and he has e3 flasher, but i dont know how to use it, i dont have any flash backups (i have one but hash checker says bad about it)

Can we use e3 flasher without flash backup?
(Thank you so much felix for your answer mate)

Can i force fan to 100 percent by using fan jumpers at ps3's fan socket and speeding fan up via external power supply? Can this work like that?

 

[RIP-Felix]

Can i force fan to 100 percent by using fan jumpers at ps3's fan socket and speeding fan up via external power supply? Can this work like that?

No PS3 uses a PWM fan that has some kind of weird non-standard duty cycle. I tried hooking it up to a PC fan controller once and it burned out the mosfet. I haven't returned to the idea since then.

But technically you could use one of those inline fan potentiometer mods they sell on ebay to accomplish this. Personally I think it's easier to simply open the console install 2 wires and then program the syscon to adjust the console's base fan speed to 100%. here's how:

1. follow syscon UART tutorial.
2. Change the first fan step to 100% instead of the default 20%

   w 2c0 FF

   Default is 33, when you want to revert. This changes the checksum so you then need to fix it using command "eepcsum" to get the value it should be.
   

   eepcsum
   
   csum = 0xEC17
   
   w 7fe 17 EC

   That checksum may be different for your console, but you can use this as a template to figure out how to do it. It's pretty easy.

This is how I would have unbricked my console, but web man mod was still running in the background even though I couldn't see anything on screen. So I set the fan percentage to a static 95% using the browser and that worked instead. But if you can't access wMM, the syscon UART is always an option.

 

[kursatd24]

No PS3 uses a PWM fan that has some kind of weird non-standard duty cycle. I tried hooking it up to a PC fan controller once and it burned out the mosfet. I haven't returned to the idea since then.

But technically you could use one of those inline fan potentiometer mods they sell on ebay to accomplish this. Personally I think it's easier to simply open the console install 2 wires and then program the syscon to adjust the console's base fan speed to 100%. here's how:

1. follow syscon UART tutorial.
2. Change the first fan step to 100% instead of the default 20%

   w 2c0 FF

   Default is 33, when you want to revert. This changes the checksum so you then need to fix it using command "eepcsum" to get the value it should be.
   

   eepcsum
   
   csum = 0xEC17
   
   w 7fe 17 EC

   That checksum may be different for your console, but you can use this as a template to figure out how to do it. It's pretty easy.

I dont have equipment for connect to the syscon, maybe i should send this to my friend and let him do it via e3 flasher mate. But you gave me nice technical information thank you so much about it. If you want i can send this machine to you for your projects

I have a lot of potentiometers at my home, i can do same cable conf about it maybe i can control the fan speed via that (I am living at turkey and turkish customs employees dont pass ebay, aliexpress and amazon produtcs up to their mood at that moment)

 

[RIP-Felix]

I don't need more consoles, but thanks anyway.

 

[kursatd24]

I looked around at reddit, found this.

maybe i can cut the data wire from the middle and try max speed with it, after i fixed the firmware issue i can resolder or connect the wire back?

 

[Mitsu™]

Red Faction Guerrilla seems an interesting game to test overclocking with. Not only does it have an unlocked framerate, but it seems that any kind of overclocking instability will make this game shut down the PS3 as soon as the level loads. I thought my 2003A Slim was stable at 700/950, as I'd tested for many hours on many games including completing GTA V. But RFG wasn't happy until I went down to 700/825. Might be worth trying out if you're looking to find a stable OC.

Okay, so...
I played Red Faction Guerrilla during ~30 minutes on my 2504A, at 800/950, and didn't encountered any issue (except this annoying framerate, it would have been way better with V-Sync, I agree ).


So I think that it's a limitation of your console or more precisely : the shutdown (triple beep) might be (/probably is) a symptom of aging capacitors.
This OC (700/950) on this game is probably too much for them.

Btw, this game receives a nice boost from the OC, but I think that a CPU OC would help way more with it.
The physics (demolition, etc...) is managed by the CPU after all.

 

[kursatd24]

update about shitty 2004a, right now console recognises my ds3 but no display and no power button working, i turned off via pulling power cord


edit: power button works as usual, 5sec hold turns off the console.

edit2: console has 576p output but only black screen

 

[Tanzu15]

update about shitty 2004a, right now console recognises my ds3 but no display and no power button working, i turned off via pulling power cord


edit: power button works as usual, 5sec hold turns off the console.

edit2: console has 576p output but only black screen

Bro that console is cooked. The OC you gave it was way too high. It's just cooked.

 

[kursatd24]

Bro that console is cooked. The OC you gave it was way too high. It's just cooked.

Maybe i can return this i dont have any idea either

 

[Mitsu™]

Maybe i can return this i dont have any idea either

I noticed that the 20XX slims seems to be more prone to hardbrick than the others.
Personal experience (my first 2004) + several other testimonies.
Most of the time, a 25XX can be saved just by cooling it. Concerning the 21XX series, I don't know.
.

 

[Tanzu15]

I noticed that the 20XX slims seems to be more prone to hardbrick than the others.
Personal experience (my first 2004) + several other testimonies.
Most of the time, a 25XX can be saved just by cooling it. Concerning the 21XX series, I don't know.
.

All 20xx slims cannot pass the 650 barrier in core or 800 or 850 memory. They just can't. None of them can. The silicon won't allow it. It isn't efficient and matured enough. Don't know why people try absurdly high OCs from the get go without doing proper testing while only having 1 console. But, we all do learn the hard way I suppose.

 

[Mitsu™]

All 20xx slims cannot pass the 650 barrier in core or 800 or 850 memory. They just can't. None of them can. The silicon won't allow it. It isn't efficient and matured enough. Don't know why people try absurdly high OCs from the get go without doing proper testing while only having 1 console. But, we all do learn the hard way I suppose.

Yeah.
If only our mistakes could prevent other users from destroying their consoles...
But... no.

And we have specified the limits of these models plenty of times.
That's just sad.

Unrelated edit :
New vid !

 

[Raidmax]

All 20xx slims cannot pass the 650 barrier in core or 800 or 850 memory. They just can't. None of them can. The silicon won't allow it. It isn't efficient and matured enough. Don't know why people try absurdly high OCs from the get go without doing proper testing while only having 1 console. But, we all do learn the hard way I suppose.

None of the 20xx slims can due to using the same 65nm RSX as the CECHL models (CXD2991). I have a CECHL that won't do further than 650 either, however in my case I was able to revert to stock.

I also unfortunately have to confirm the fact that datecodes are the worst thing to exist from my own two 2500s. 0D has a A1GB and 0C has a CGB.

 

[RIP-Felix]

I need more 65nm console data from their max overclocks. I couldnt make a good graph of their averages with the small sample size. 650 core seems to be about the average, but 800 on VRAM should be doable on all models. Even 90nm.

 

[SimRacer778]

All 20xx slims cannot pass the 650 barrier in core or 800 or 850 memory. They just can't. None of them can. The silicon won't allow it. It isn't efficient and matured enough. Don't know why people try absurdly high OCs from the get go without doing proper testing while only having 1 console. But, we all do learn the hard way I suppose.

Looks like my 2001B is the exception, not the rule. It was stable at 700/850 for GT5, and somewhat stable on GT6 before slightly artifacting at 60c+ on the RSX.

It's got about 12 days of run time, so the NEC/TOKINs aren't worn out.

I always use 650/875 now, and that's slightly higher than 850 memory.

Yes, people should be aware of the risks of overclocking, it's not exactly free performance if PS3s are bricked.

In the meantime, I have tested GTA 5 - the prologue mission.

 

[Raidmax]

There's always units that will be exceptions - such was the case with two "datecode" units. September 2010 with a potent 5300CGB chip and a October 2010 unit with an poor overclocker (A1GB).

And while I don't plan to OC a BC unit that hasn't been Frankie'd, I figured I'd leave a 90nm RSX string off my signature CECHB00. Apparently, I got one of the better bins, or so I'm probably thinking to myself.

rsx: b02 500/650 vpe:ff shd:7b [4K0326101:1:3:f:8:f:4:f:2][39:2:1:1:1:3:1][0:0:0]

 

[Tanzu15]

Looks like my 2001B is the exception, not the rule. It was stable at 700/850 for GT5, and somewhat stable on GT6 before slightly artifacting at 60c+ on the RSX.

It's got about 12 days of run time, so the NEC/TOKINs aren't worn out.

I always use 650/875 now, and that's slightly higher than 850 memory.

Yes, people should be aware of the risks of overclocking, it's not exactly free performance if PS3s are bricked.

In the meantime, I have tested GTA 5 - the prologue mission.

Then it's not stable. When I say stable I mean every game at any temperature up to around 70 or 75c. No artifacts, no crashing. So no it's not stable. If your temperature were to reach anywhere from 68c to 75c you'd be hard crashing, and artifacting all over.

 

[RIP-Felix]

Looks like my 2001B is the exception, not the rule. It was stable at 700/850 for GT5, and somewhat stable on GT6 before slightly artifacting at 60c+ on the RSX.

It's got about 12 days of run time, so the NEC/TOKINs aren't worn out.

I always use 650/875 now, and that's slightly higher than 850 memory.

Yes, people should be aware of the risks of overclocking, it's not exactly free performance if PS3s are bricked.

In the meantime, I have tested GTA 5 - the prologue mission.

Could I solicit your RSX info from the LV1 dump? And the syscon errorlog dump as well. You can easily dump both using evilnat's CFW tools menu.

For the LV1 info, open it in HxD and search for your current OC timings. In your case "650/875" and it should jump strait to the info I need.

 

[Raidmax]

Just curious, does it have to be the max stable overclock, or the maximum it'll take? I have a 2003B doing nothing that I guess I can sacrifice.