PS3 Question: Using a PS3 clean with just cooling improvements

The other solution is to buy a "PS3 fan accelerometer" (around 20$), this is a device connected in between syscon and the fan. It "boosts" the fan speeds in a percentage of your selection (usually +20% is fine for most PS3 models). As a result the other motherboard components doesnt knows what is happening
A bit offtopic but is a fan accelerometer for a slim ps4 worth it? How did sony implement fan speeds for ps4?
 
It's strange, seems kind of like the memory used to store the fan speed is not overwritten when shutting down the console, as long as the console left in standby.

Does anyone understand what is happening there? I wonder could this behavior be exploited somehow.

IIRC If you enable Remote Start the fan will stay running at the last fan speed set by fan controller.
 
IIRC If you enable Remote Start the fan will stay running at the last fan speed set by fan controller.

I'm fairly certain this is a different thing, That's not an option I would ever have enabled normally, same with WLAN in debug settings. I have messed around with that a bit alright, and the behavior is different as the fans stay on slightly all the time with those. This is only seen with a HEN and webMAN combination afaik.
 
I'm fairly certain this is a different thing, That's not an option I would ever have enabled normally, same with WLAN in debug settings. I have messed around with that a bit alright, and the behavior is different as the fans stay on slightly all the time with those. This is only seen with a HEN and webMAN combination afaik.

In Cobra 8.3 & MAMBA 8.4 there a hook function attached to SYS_SM_SHUTDOWN that resets the fan mode to SYSCON.

In HEN payload, that hook doesn't exist.

IIRC that hook was added by Evilnat when he was implementing the fan control in Cobra because on some models the fan stayed running loud after shutdown.

In theory the fan control module should be easy to implement in HEN since the code is based in Cobra payload.
I don't know if @esc0rtd3w has plans to add it to HEN.
 
OK I see. It makes sense then really, if the console is powered all the time, syscon is not reset by shutting down the console.

So in theory someone could make a stripped down hen enabler, that increases the fan speed then deletes itself. And that fan speed would stick as long as there was power going to the console. Not much call for that kind of thing though really.

Its a shame HEN enabler status can not be remembered in the same way, or triggered from syscon somehow.
 
That's confusing for me. cos HEN allows fan control, but HEN does not have lv1 exploited.

I fairly sure I have seen a bug on HEN where the manual fan speed would stick after a reboot, this makes me think a permanent boosted fan speed might be possible on OFW somehow. Does anyone else remember that bug with early HEN versions?

Maybe something like a partial temporary HEN install that deletes itself after doing what it needs to do would be possible, Idk.
I've been using HEN since 4.87 and I'm on OFW 4.89 at the moment, but the fan was always set to 30%.

I could restart or turn off the device, when I turned it on it would be at 30% even without starting the HEN.

I always used this trick when I was going to play online, activate the HEN to increase the fan, restart the console and play with it at less than 60C :cool:
I don't remember if if I unplugged it and then put it back in it was still at 30%, but I'm pretty sure not.
 
So in theory someone could make a stripped down hen enabler, that increases the fan speed then deletes itself. And that fan speed would stick as long as there was power going to the console. Not much call for that kind of thing though really.

Indeed it's possible to make a "fake ofw payload" based on HEN like I did with MAMBA.

It would be the same HEN payload except that it would start without CFW syscalls enabled and therefore without support for homebrews (prevented by the homebrew blocker). If the create syscalls hook is implemented in mappath.c (it is implemented in Cobra 8.3 & Mamba 8.4) then it would be possible to enable/disable CFW syscalls on demand without reboot.
 
Indeed it's possible to make a "fake ofw payload" based on HEN like I did with MAMBA.

It would be the same HEN payload except that it would start without CFW syscalls enabled and therefore without support for homebrews (prevented by the homebrew blocker). If the create syscalls hook is implemented in mappath.c (it is implemented in Cobra 8.3 & Mamba 8.4) then it would be possible to enable/disable CFW syscalls on demand without reboot.

Funnily enough, the first thing I wrote during HEN's initial development phase was a minimal kernel ROP payload that installs only lv2 peek and poke.

At the time the idea in my mind was to have a HEN composed of modular payloads rather than just a full HEN in one payload, the modularity would have enabled users to load whichever features they needed, there would have been a fan control payload, an iso support payload, a rif payload, etc..

Then Habib decided to port Cobra, a trivial thing for him to do given his hands on knowledge of Cobra, so I scrapped those plans and ended up giving up on HEN development altogether soon after that.

Having said that we could potentially revisit the idea.

The only obstacle to the modularity concept is that we would need to create a core plugin payload first, its role would be to orchestrate inter module communications by providing an interface to kernel modules, it is necessary for things like multi threading synchronisation and also for modules to be able to call each other's public functions or access each other's public variables.
Another way around this issue.might be to start making stub libraries for kernel payloads so that other payloads could link their exposed functions.

Neither HEN/Cobra or Mamba do address that problem either actually so the development of an inter kernel payload communication plugin would be a bonus to all existing kernel solutions.
 
Last edited:
A bit offtopic but is a fan accelerometer for a slim ps4 worth it? How did sony implement fan speeds for ps4?
The way how works the fan (by using a PWM signal controlled by syscon) is the same in PS3 and PS4, so the concept is the same

There are many different ways to do this, but the good way is by "intercepting" the PWM signal and "multplying" it by a percentage. If some of you is interested in buying one you need to keep atention at the description of the seller of how it works

If you are not sure... i can tell this one works great, is for PS3, but the same seller have other for PS4 that does exactly the same (the green ones)
https://www.psx-place.com/threads/temps-after-delid.36003/#post-318168

Also... if some of you is interested to do it at home take a read at this project
https://www.psx-place.com/threads/ps4-ps3-hardware-fan-accelerator.31345
 

Similar threads

Back
Top