How far has PS4 custom firmware come? I haven't been following it closely but I'm kinda curious... is there a functional backup loader yet? And is there a particular PS4 (OFW) that I should be looking for in order to install CFW?
Hacking How far has PS4 CFW come? - Just curious
- Thread starter Gorkensnorkel
- Start date
- Views 19,490
- Replies 13
Its not really a cfw its an exploit with the same principles of a cfw. So its nothing like a jailbroken ps3 yet, you have to perform the exploit everytime you get into the main menu upon console startup to be able to run backups/homebrew
Last edited by MasterJ360,
D
Deleted User
Guest
I don’t mind the browser exploit it’s just on 6.72 it’s not stable.. and also to run your back ups they have to install .. wish it was more like multi man back in the day instead of pkgs or fpkg.
1. Dump game.
2. Convert the game to pkg on pc.
3. Instal .. game are huge and all this takes a lot of time. Especially with the dumper not having a progress bar to know how much it dumped.. PS4 just turns off, that’s the cue.
1. Dump game.
2. Convert the game to pkg on pc.
3. Instal .. game are huge and all this takes a lot of time. Especially with the dumper not having a progress bar to know how much it dumped.. PS4 just turns off, that’s the cue.
Last edited by senas8,
D
Deleted User
Guest
If there is a working jailbreak that becomes stable is it safe to assume it will use 6.72 firmware?
It may even use 7.02 firmware.
6.72 is decent if you expect issues. It’s far from perfect, and not as “stable” as 5.05, but it’s usable.
Ah, okay. I was just thinking of purchasing a PS4 on the proper firmware before they become hard to find.
My understanding - and albeit that's a crude one - There's exploits which exist for 5.05 and 6.72 system software which will simply enable the existing/inbuilt 'DEBUG' menu https://www.psdevwiki.com/ps4/★_Debug_Settings
In addition this removes (or modifies?) the signing requirement for packages. Normally installed software is signed with a key which is unique to the user account or console, my understanding is that these exploits allow packages without valid keys to be launched, provided that they have been compiled with a framework that is at (or lower than) the current installed system software version.
Given that the menu is actually inbuilt (and simply disabled on non-devkit units) it looks official and quite neat, although most people will only use the 'package installer' option from the menus it has a lot of other functionality.
In addition this removes (or modifies?) the signing requirement for packages. Normally installed software is signed with a key which is unique to the user account or console, my understanding is that these exploits allow packages without valid keys to be launched, provided that they have been compiled with a framework that is at (or lower than) the current installed system software version.
Given that the menu is actually inbuilt (and simply disabled on non-devkit units) it looks official and quite neat, although most people will only use the 'package installer' option from the menus it has a lot of other functionality.
Similar threads
