PS4 News on Facebook! PS4 News on Twitter! PS4 News on YouTube! PS4 News RSS Feed!

Home PS4 News - Latest PlayStation 4 and PS3 News

May 20, 2013 // 5:56 pm - Following up on his previous updates, today Spanish PlayStation 3 developer MiralaTijera has updated his PS3 4.40 CFW to include System Manager 1.1 and Integrated Core 3.2.0 alongside QAFlag functionality.

Below are the details, roughly translated: UPDATE 3: Warning, this update if it is best installed first previous... I copy and paste the post of Estwald because of what you put on I have nothing more to add... Estwald wrote:

First of all, Miralatijera me that if they "saw" made ​​public the Core in its name and the rest is of my own by collaborating

On the other hand, the uniqueness of this, is that just your CFW offers the ability to launch applications in the background and these things, show that when the CFW provide useful ideas and instead locked away, are offered the possibility the dev, they can do things and are more likely to do so. In contrast, others, think that by taking out a CFW automatically have to give support... it will be no [poraki]

You try hard enough and you provide the info or you worry your porting (I mean Iris Manager), as did Miralatijera (in 4.31 gave us all the information he could and at 4.40, made the port it, and I then managed some little things: well if you do things), because if not directly rule and I stand so quiet [burla2].

And with that, let the matter:

The Core

The core novelty presents how the possibility of launching an application in the background, which is called "sm.self" and installed in root / dev_flash, which has advantages and disadvantages:


  • If the application in the background hangs the system, obviously, the system will not advance from that point. So the flag is provided removes, but obviously, if someone puts nosearch flag, the result would be a semibrick (have to reinstall CFW). So careful with this.
  • Access to the system is limited to exports of syscalls and basically liblv2.
  • That the application is in the background, does not mean you do not eat resources, obviously


  • The ability to control the temperature and fan without affecting other processes directly or maintaining "awake" USB devices tend to fall asleep, it seems a good start. The application runs on a separate plane to vsh.self, PSX emulator or PS3 game (obviously on the PS2 emulator, at least natively on the FATs, the LV2 ceases to exist and our application dies) and processes not stop LV2 how true alternatives.

The System Manager

The System Manager is how I called the application that will run in the background, basically consists of three separate parts:

1) The main: The main loop is enclosed in a 1 ms in duration to receive commands via address 0x450 of LV2 with which to configure the application (you can set the thread priorities, changing temperature tables, and mode time device activation and get some additional information)

2) FanCtrl_Thread: basically, this thread does the same as the payload that I developed for Fan Control Utility (Incidentally, the application has been updated to the 1.5 to work with this without problems)

The advantage is that unlike the payload, this does not affect directly the processes, so that should not happen reporting problems some users of the application. Basically, this is how I would have liked me to do from the beginning, but until now, there was no way.

Added a small payload that is housed in the direction of LV2 0xF70, like Fan Control Utility, but only to protect the syscalls sm_shutdown and provide compatibility with the previous system, so that it can be integrated in Iris Manager support.

3) UsbWakeup_Thread: This thread has 3 running modes and basically deals with "wake up" USB devices that tend to "sleep" for lack of use, causing problems in games.

The wake mode is to write in a file called "nosleep" we can create in root of the device (no matter that has length 0, just exists or not) for the SM know or not to use units. By default, it does every minute, but you can program steps of 10 seconds (2560 seconds maximum, to which we must add two seconds for the indicator).

USB storage devices, can be divided into hard drives and flash memory devices that are not as convenient to be writing all the time. This is the reason that is delegated to the user to create "nosleep". Indeed, in some games, you must set BD Emu and that makes the USB pass renamed as / dev_bdvd, which also supported.

The three modes are: 0 -> disabled, 1 -> enabled for a single device and 2 -> enabled for all devices (this is the default)

Default operation (autonomous)

Just load the SM, the settings are:

  • Temperature control / fan Fan Control Utility equivalent asset.
  • Wakeup writing on all devices, including / dev_bdvd (if a USB device allow writing) on, proceeding to write 1 time every minute or so. Obviously, writing only affects those devices with the file "nosleep" (elsewhere, could detect read access as much)

The LEDs indicate the following:

  • Yellow Led Fixed: temperature below 70 degrees
  • Led yellow / green flashing temperature above or equal to 70 degrees
  • Led red / yellow / green flashing temperature above or equal to 75 degrees
  • Green LED remained two seconds every 10: led activity
  • Leds off for two seconds: indicate a write access to USB device. This is important to know, because we should not unplug a USB device in a deed, obviously (we wait for the LED to turn off and unplug a few seconds later)

External Control Support

Fan Control Utility 1.5:

And soon, Iris Manager:

Installation and Use

  • If you have the flag "nosearch" active, unset. Copy the Core (sys_init_osd.self) and root sm.self in a pendrive and expects the restarts (for many, to install the core and then to install the system manager)
  • If you want to uninstall sm.self then adds the flag "removesm"
  • If you want to prevent a USB device "sleep" create a file "nosleep" in root of the device (whether measured 0 bytes)


Core 3.3.0:

System Manager v1.0:

(Includes source code for compilation under PSL1GHT)

UPDATE 4: another update from Estwald

What's new:

  • There have been some corrections of time to avoid excessive delays when changing the mode of operation for the Fan and USB Wakeup.
  • Priorities have been reduced to a minimum to try and stop the System Manager as little as possible to other processes running and only use their downtime.
  • Added the ability to change a priority and update time main () (this used to be able to tinker with things, if necessary, but in principle it should count as is)



  • If you already have the previous version, simply copy sm.self in USB root, put it in USB000 (closest to the reader) and reboot.
  • If you have the core 3.2.0 then go here ( and following the instructions, replaces the old sm.self by the new.


  • Copy the folder "flags" is inside the RAR to the device and restart with it plugged in USB000

USB Wakeup:

  • Create a file called "nosleep" (no extension, which I already see it coming XD ) In root of the device you wish that every so often, are accessed by writing to keep alert

Psmaniaco wrote: Estwald a question, in your Iris Manager I think you added the temperatures of Cell and RSX right? Are the temperatures of the sensors you mentioned further back? A greeting.

If put another application in the background... Yes and no. For starters, you can only be accessed through syscalls or liblv2 exportable functions in PSL1GHT. Make them the idea that this is pre-vsh.self and operates completely autonomously. Also, you need a series of special construction flags or not work (which I include in the Makefile to scetool).

If not done well, the best thing you can get, is to ignore your application By the way and for that matter, if you delete the sm.self you can do it directly (root is / dev_flash and just mount it in writing) or otherwise, add the flag "removesm" to do it for the core you: no need to remove the core.

And by the way, a recommendation mine: NEVER put no root any files that could be copied by the core unless it is that what you want: if you put a vsh.self in root, for example, automatically copies and going to care if it's a different version. So very careful with that, it can cause a semibrick

PS3 4.40 CFW MiralaTijera: System Manager 1.1, 3.2.0 Integrated Core

Follow us on Twitter, Facebook and drop by the PS3 Hacks and PS3 CFW forums for the latest PlayStation 3 scene and PS4 Hacks & JailBreak updates with PlayStation 4 homebrew.

#51 - nokkuho - February 27, 2013 // 1:33 am
nokkuho's Avatar
This topic seemed very interesting. It had my hopes up for installing it on OFW 4.31, but it turns out you can't yet still nice work though.

#50 - BOBJONES2013 - February 26, 2013 // 8:40 pm
BOBJONES2013's Avatar
thanks was looking for that answer

#49 - DEUSC2D - February 24, 2013 // 6:33 pm
DEUSC2D's Avatar
You can just disable Core or get nosearch flag working if you are going to be running games via USB.

I currently can not support this CFW as I need to repair my test console from fooling around with DEX (not this CFW related) before I can use this again. I'm also not sure what the dev intends on doing with this CFW and my Spanish is not getting any better.

#48 - accurateguy - February 24, 2013 // 8:45 am
accurateguy's Avatar
Am having issue after i update my core to 2.7.2 my usb games did not appear again on backup managers, please help me out thanks for the support in advance

#47 - DEUSC2D - February 17, 2013 // 6:06 am
DEUSC2D's Avatar
Hi, you must copy all the content from inside of the "Core 2.7.2" folder to the root (E:\root) of your USB device. The folder named "flags" needs to be at the root (E:\flags) of your USB device as well e.g. E:\flags with the boot_otheros flag inside of that folder will boot into otherOS. The PS3 will read it like this ==> /dev_usb000/flags and whatever flag you put in to that folder.

#46 - Doni - February 16, 2013 // 12:19 pm
Doni's Avatar
hi people I have a few questions, yesterday I installed the 4.31v2_CHX cfw.

From the core folder I have the whole folder "Core 2.7.2" in the root of usb copied along with the flags. E:\CORE 2.7.2\flags

Thus, the LED will flash the ps3 in several colors, it also starts the normal cfw, but my problem now..

1. The flags are active now or do I activate?
2. Do I have to enable somewhere bd emu, because i got a broken laser.

Sry for the google english^^
mfg doni

#45 - DEUSC2D - February 10, 2013 // 4:04 pm
DEUSC2D's Avatar
The dev MiralaTijera, is already making update 8. He claims that all games with be payable with no disc. Compiling a .PUP is not necessary for updates 5-7.

Please keep in mind that this is a WIP and if you have any issues just try to be patient.

#44 - abdullahjwz070 - February 10, 2013 // 8:06 am
abdullahjwz070's Avatar
Wow this is nice bro

#43 - okc8200 - February 10, 2013 // 7:07 am
okc8200's Avatar
Hi DEUSC2D. Thanks for the update 4 pup! This update 7 - core 2.7.2 is giving me major problems though. Can you make a pup for me?

#42 - DEUSC2D - February 8, 2013 // 8:59 pm
DEUSC2D's Avatar
To: seeman, this CFW does not need game fixes.

Download: Update 7 / CORE 2.7.2 (15.27 MB) / Core 2.7.2.rar (15.08 MB)

How to install Update 7 / CORE 2.7.2:

  • Connect a pendrive (FAT32 formatted) to PC.
  • Extract the content from "Core 2.7.2" folder to your pendrive.
  • Connect your pendrive to --> /dev_usb000 (closest usb port to bd-drive)
  • Turn on your console, once done CORE 2.7.2 will be installed.

Note: To use flags, copy them from the "All Flags For CORE 2.7.2" folder the flags folder on your pendrive with CORE 2.7.2 (only use the flags you need).

Summarization of flags:

  • Bdemu, If you have the reader controller you have dead or no reader and, therefore, do not npdrm works, enabling this flag, the console will behave as if you had reader. If you do not plan to change your desktop, you can install this flag in the flash through another flag called "installbdemu" not to depend on the pendrive. It has also been rewritten and now has a more accurate and improved.
  • Installbdemu, If your drive controller is dead, use this flag (with the Core Assets) to permanently install the flash BDemu.
  • Enableqa enable QA Flag directly in 4.31.
  • Removeqa, disables QA Flag.
  • Dumpnandflash, makes a full dump of NAND console, which will help us to recover the console of a full brick, with a flasher, of course, because if you have a full brick, CORE will not start.
  • Dumpnor, same function as above, but dedicated to consoles with NOR memories.
  • Dumpdevflash, Dumps the dev_flash (3) in the root of the pendrive.
  • Dumplv2, As stated, makes decrypted LV2 dump.
  • Dumplv1, Same operation as above, but this makes a dump (lv1dump.bin) of LV1 (16 MB).
  • Fullramdump, I think it goes without saying that it serves.
  • Flashnor, If there is a file called "nordump.bin" in the root of the pendrive, the MT will flash the NOR. Beware of this option could be dangerous if you do not know what you do. The flashing process takes around 20 minutes.
  • Anotherlv2, With this flag we can experience with our LV2 modified and tested for correct functioning well without flash this in memory of the console, thus saving many complications and risks of brick. Simply copy the root of pendrive LV2 self from modified and enable this flag, the console will start with the LV2 the pendrive.
  • Clear_bootparam, clean records (Cache and Logs) and "waste" that can leave other flags in use, to have the console as clean as possible. (Thanks for the clarification MrMento ^ ^)
  • Setup_flash_for_otheros, prepare the flash partitions to install OtherOS (Linux).
  • Install_otheros, Use petitboot to install Linux on the console. (Required files contained in the folder "OTHEROSFILES" pack of Update7)
  • Boot_otheros, If you have Linux installed on the console, turning this with this flag in the pendrive, Linux will automatically start at the beginning of the console. CORRECTED small bugs, now runs everything correctly.
  • Nosearch If you want the console boot even faster, besides solving the synchronization of the controls at the beginning of the console, but regardless of the flags in the search for new functions USB enable this flag once and will be installed Standing in the flash. You can restore it by installing the included in the Update7 ResetCore.pkg.

CORE 2.7.2 Changelog (rough translation):

CORE 2.7.2 with major improvements changelog:

  • Deleted and exitfactory enterfactory flag (power + eject works without dongle and you can leave the factory with the 2nd exit Lv2diag always) bone that were useless
  • Added flag "installbdemu" permanently installed bdemu flag causes the bdemu always be loaded without connected or flag setting usb
  • Now the core is automatically installed on the dev_flash to become permanent execution
  • Bdemu completely rewritten, is now more accurate and causes less problems.
  • The core 2.7.2 installs on dev_flash now (is automatic the first time I extort)
  • Added flag "nosearch" permanent flag adds a core to keep you from usb to the console and start the USB core and load without permanent work options with this greatly improves startup time to almost original theme synchronizing the controls
  • Added flag "flashnor" flashes using the normal root file in pendrive nordump.bin / dev_usb000/nordump.bin (you can watch it bricking if you do not know what you do not LOOK this flag)
  • deleted and payloaderdev Payloader flag, (and all managers have their payload to get mine when the managers are more up to date?)
  • Fixed boot_otheros the flag, now loads fine
  • Fixed collision with IRIS MANAGER code no longer asked to restart ..
  • Added flag "dumplv1" creates a file in the root of the pendrive lv1dump.bin with a dump of lv1 16MB

What's Cool:

  • As nocheck flag disables search permanently on usb I created a pkg to reset the permanent flag "nosearch"


  • Put the folder in the flag's flag that querrais start and what you put into the right usb console everything and export
  • Flags are empty files with no extension are created in the folder usb flags
  • From the core of this review is ongoing in flash, the update method is run resetcore pkg (if you have enabled nosearch) and turn off the console, enter the new cellftp.self (assumption 2.7.3) in the folder / updatecore of usb and make magic.


  • The homeless is bdemu reader READER COMPLETE WITHOUT ie no broken lens, if you have broken controller. This is slightly better than the same compatibility APP_HOME games but is better than using a disk.

This update is only, you do not have any other previously installed... and if you had an update not care too.

How to deactivate CORE 2.7.2:

  • Simply extract the contents from "DEACTIVATE CORE 2.7.2" folder to your pendrive.
  • Connect it to /dev_usb000 (closest usb port to bd-drive),
  • Turn on your console, once done CORE 2.7.2 will be deactivated.

Note: To restore CORE 2.7.2, install the ResetCore.pkg from the "TOOLS PKG" folder.

MiralaTijera, CFW 4.31 creator.
Isma_OMG, info/support provided.