44w ago - Today Spanish PlayStation 3 developer MiralaTijera has shared details on his PS3 CFW 4.31 OtherOS++ WIP (work-in-progress) which contains no spoofing older Custom Firmware versions and includes QAFlag and BD Emu without a controller among the features outlined below.
To quote, roughly translated: Hi, basically I stand in the community giving what I made in the dark slowly.. This is my FULL 4.31 4.31 cfw spoof's nothing, it's all ported to the 4.31, and... I give to my multitool also called "core" which is nothing more than a self that load at startup console if this is available in the right usb of your console "/ dev_usb000 /" which among other things dumpea flash console, you enable qa flags (yes in 4.31 directly) and gets you out and gets you the factory mode... I put the specs:
CoreOS lv1 hash downgradeadas deactivated for consoles
lv1 183/182 undocummented (LV1 peek / poke)
VSH: nas_plugin (all pkgs installable game_ext explore_plugin and plugin to show install package and eliminate epilepsy warning message (though the latter with qa flag leaves only) and for patched vsh rif / rap fakesign) (This last with qa flag leaves only)
default.spp: added extra memory for otheros GameOS
lv2 peek / poke, syscall 6/7,
lv1 lv2 peek / poke (optional syscall 8/9 via core)
Hermes Payload with 36 ported sc
APPLDR: lv2 memory hashing disabled from appldr (no need to have it at lv1 parcheeis) dev_flash whitelist disabled (load any keyset from dev_flash) and ECDSA Off
ISOLDR: ECDSA Off
SPP_VERIFIER: ECDSA Off
spu_utoken_processor: ECDSA off (qa flag)
Payload here to include in your C fixes and managers with the hook:
http://pastie.org/private/cxg8xvohjbh99q45jw (Payload with SC36)
Now the core... is an all-in-one, this cfw to start looking at the dev_usb000 if a and a file called cellftp.self and another called copy_script.txt, enable disable search whoever can do it simply by putting the original sys_init_osd.self 4.31 in dev_flash folder / sys / internal / here and no longer seek more...
Update 6: PS1 games now work with Update 6 / CORE 2.7.1 and mM! ReActPSN also works with the latest update. The boot_otheros flag gives me the same issue so Rebug tool box or going into recovery mode is how I get to Red Ribbon. This CFW searches for CORE (cellftp.self) on boot and it can be deactivated with sys_init_osd.self (it fixes some type of issue with "los mandos", and maybe speed up boot time as well).
Update 7: CORE 2.7.2 download and changes are outlined HERE courtesy of DEUSC2D.
Added new flag = flashnor = flashea nordump file in / dev_usb000 / in the north via software (eye takes as 20 minutes) the file would be dev_usb000 dev_usb000/nordump.bin let the usb.
Put the pack unzipped in the root of a pendrive as it is without flags with their accompanying files in the root also, we put it in the right usb and turn on the console, the core will handle the dirty work, if all went well both. self and. sprx deletes the core once updates, Greetings!
Then developed a homebrew called core which makes everything a little, the self has to go along with pendrive root folder copy_script.txt and flags with flags (functions) as you want to within when starting the console will look and run, leave a log of what was done in the root called core.log are mention the most important and tomorrow I explain a little more.
BD emu flag is for if you have not and do not controller works if you activate this flag npdrm console will behave as if the reader enabled qa, enable you qa flag directly in 4.31:
Start with only core setup_flash_for_otheros flag, to hear a double beep is that everything went well, if you do not hear looking log
Put this after the dtbImage.ps3.bin that corresponds to your console type dtbImage.ps3.bin.nand dtbImage.ps3.bin.nor is for nand and nor it is for renombrais to dtbImage.ps3.bin and you put it in root of pendrive as appropriate in your case and you put the flag install_otheros, same start and soon will hear 2 beeps sound if you look at the log to and that something is wrong
Once done turn off the console and put the flag boot_otheros, when you start your petitboot will see on the screen
Hermes thanks, I used your cosunpkg and cospkg for CoreOS and payload lined with SC36 and more...
Link all this: pastie.org/5913506 / mirror thanks to "Palestine" http://ul.to/0mp1pmbl
Function bd emu's I have also built in a 3.55 cfw I'm uploading it is always useful to dump your key root
CFW 3.55 OtherOS++ CEX, BDemu Without Controller (Integrated)
Hi, as promised here's the integrated version for CEX BDEmulator that has all patches from glevand for OtherOS++ and has the sha1 hash check syscon disabled for consoles for downgrades.
With this CFW because anyone with broken controller (black screen or throwing npdrm update loop etc...) can use the console as controller, you can load is APP_HOME your games from, that's something I have the same function in the CFW 4.31 in this same subforum but got to 3.55 here too integrated for people to use and get their root key inter things... SS unpatched least trophies error
In xdelta patch, the patch obviously apply and give the option to check and keep the original file checksum enabled, you will create another file called * NEW.pup being * the name that you do them to OFW, hashes the PUP should be good:
Of course not bricked any console, hidden takes time and has been tested on all systems that can be installed
I give the core src polish it once, honestly I'm embarrassed both comment on the code you enjoy it, just as I will update the post in these 3 days with what I forget, that sure is a lot to this fw has had his job for.. Now comes Rogero and copy
Finally, some feedback on this PS3 4.31 CFW WIP from butnut: So I did a little testing... It installs fine on my slim 2101 and since I had left QA active the last time I was on 3.55 it is now automatically activated (still have to input button combo) The cold boot takes the same amount of time, only you don't see the epilepsy warning... It has normal install pkg files and app_home icons (just like Kmeaw 3.55)
Backup managers do not work yet because they do not have the new payloads implemented yet. I will go back to Rogero 2.04 for now. QA downgrade does not seem to work. Every firmware I try (CFW and OFW) the PS3 says it is corrupt. Luckily Rogero 4.25 to 3.55 DG pup still works.
FOR PEOPLE WITH BLUE SCREEN: I found the cause of the error and was in SPKG's generation, already fixed and I'm uploading the new delta for a new pup (linked above), yes now installable from anywhere EXCEPT ofw 3.56 + the rhythm of my connection in 30 minutes is up and available, while not install the previous advise, not pass anything that fence (only the blue screen is easily removed) if not for the whole upgrade process will be more comfortable.
Finally, below is a guide from Nicolas19 as follows: Nicolas's MiralaTijera CFW 4.31 NooB Tutorial
Step 0: Important Notes
Use a FAT32 flash memory that has the files needed to install CFW
Eject any disk you have in the drive because if there is a disc in the PS3,Your PS3 will be upgraded with Update File That is inside the game disc
This CFW is installed only on consoles With OFW 1.00--3.55 and All CFW/MFW 3.55 or CFW +3.55 with spkg sig check patched
If you're still using True Blue/JB-King dongle or any DRM dongle, Unplug and Then Put it in Recycle Bin and start Tutorial From Step 1
If your console is Spoof to +3.55 Versions ,you do not need to disable it
Users With Downgraded PS3 no need to dehash (Qa Flag) PS3 but if you like dehash your PS3, Use Toggle QA
Rogero CFW 4.XX must Install Another CFW 4.XX or Downgrade to CFW 3.55.
We Installed This CFW 4.31 on 20 PS3 That were on Rebug CFW 4.30.1 Successfully So in this tutorial we assume that you are on OFW 1.00--3.55 and All CFW/MFW 3.55 or CFW +3.55 with spkg sig check patched except Rogero 4.XX CFW.
Step 1: Download MiralaTijera CFW 4.31
First to start, download MiralaTijera CFW 4.31 (linked above)
Just select your favorite Folder and then Copy all three files (cellftp.self, copy_script.txt, flags folder) within the selected folder into Root of a FAT32 Flash memory. Connect your Flash memory to the nearest port to Blu-ray drive. When your PS3 starts up will search for it and execute it. It will leave a log on root called core.log. Enjoy.
Thanks MiralaTijera for AweSome CFW
Thanks deank for the Best Manager (multiMAN)
Thanks Developers of Iris Manager
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
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 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)
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)
System Manager v1.0: http://mods.elotrolado.net/~hermes/ps3/SM_CFW4.40_v1.0.rar
(Includes source code for compilation under PSL1GHT)
UPDATE 4: another update from Estwald
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 (elotrolado.net/hilo_update3-cfw-4-40-miralatijera-100-core-3-2-0-integrado-qaflag_1880798) 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
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
I am just wondering if there is a good thread around where you actually get a good break down of all the steps it takes to mod your ps3? I still have the ofw 4.40 and haven't bothered updating because it's sooo complicated to find the necessary information! It's like there is no clear path do do anything. i tried the newest 440 rogero but it stops after 71% says file corrupt.
I do appreciate that you can eventually find what you need but I would much appreciate it if someone could guide me to a thread or to the necessary files you need to update to the latest version that allows playing homebrew games.