PS3 CFW 4.31 OtherOS++ With QAFlag & BD Emu By MiralaTijera WIP

Sponsored Links

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:

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).

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.

Instructions:

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:

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.

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.

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.