The PS4 has been heating up lately thanks to the bounty that developer TheFlow was able to win and also has allowed for disclosure of his discovered bug. The discovered bug allows for a kernel exploit for firmware upto 7.02 (patched in 7.50), However this needs a public webkit (entry point) which are usually easier to obtain then a kernel exploit itself, so we should eventually see one arise for 7.02 but in the meantime developer Fire30 has already released a 6.72 webkit entry point several months ago. So this is why 6.72 is being talked about more then 7.02 as the next step to 5.05 we already have all the pieces its just putting together the puzzle and connecting them all together.
There is a 6.72 Jailbreak (by sleirsgoevy) out in the wild, we have not covered it much due to the fact in its debut state and even in the current state (after some commit updates) its quite buggy / unstable and looks to be rushed to release therefore lacking some testing prior to the exploit going public. The developer did warn it may take upto 10 attempts but some4 user have not got to work at all or had many more attempts some had less . Just is not the best thing for an exploit debut as its not something to blindly install or if your just getting into PS4 jailbreaking to use on your console. (if interested here is the gihub page but be warned its quite buggy in current state and advised to stay on 5.05 at this time). Hopefully it improves in time as it seems work is being done but since its advised to stay on 5.05 still at this time We have. some new guides and information that have been released pertaining how to backport (downgrade) your games firmware requirement to be playable on 5.05 until we see a stable 6.72 jailbreak, if your games require a higher firmware (up to 6.72) then developer @flatz (released Scripts) and then developer @zecoxao (tutorial) has perhaps provided a solution that works for you as the devs provide a wayto play your content on 5.05 that otherwise could not boot, so you do not need to update yet (until a stable jailbreak arises) and can still play your newer games you purchased.. In time we should see some automated tools (update see link): to make this an easier task for noobs who may not be comfortable with this method quite yet.
There is a 6.72 Jailbreak (by sleirsgoevy) out in the wild, we have not covered it much due to the fact in its debut state and even in the current state (after some commit updates) its quite buggy / unstable and looks to be rushed to release therefore lacking some testing prior to the exploit going public. The developer did warn it may take upto 10 attempts but some4 user have not got to work at all or had many more attempts some had less . Just is not the best thing for an exploit debut as its not something to blindly install or if your just getting into PS4 jailbreaking to use on your console. (if interested here is the gihub page but be warned its quite buggy in current state and advised to stay on 5.05 at this time). Hopefully it improves in time as it seems work is being done but since its advised to stay on 5.05 still at this time We have. some new guides and information that have been released pertaining how to backport (downgrade) your games firmware requirement to be playable on 5.05 until we see a stable 6.72 jailbreak, if your games require a higher firmware (up to 6.72) then developer @flatz (released Scripts) and then developer @zecoxao (tutorial) has perhaps provided a solution that works for you as the devs provide a wayto play your content on 5.05 that otherwise could not boot, so you do not need to update yet (until a stable jailbreak arises) and can still play your newer games you purchased.. In time we should see some automated tools (update see link): to make this an easier task for noobs who may not be comfortable with this method quite yet.
-
@flatz via Twitter
@zecoxao via twitter
Instructions on how to backport
-
Step 1: The eboot
- Unfself it and use readelf -a on it~
- you should see this section
- LOOS+0x1000010 0x00000000063c4000 0x0000000006400000 0x0000000006400000
- 0x000000000083a100 0x000000000083a100 R 0x4000
- Example for final fantasy vii remake demo
- Align it upwards from 0x200000 bytes on 2nd Memsize, like so:
- LOOS+0x1000010 0x00000000063c4000 0x0000000006400000 0x0000000006400000
- 0x000000000083a100 0x0000000000a00000 R 0x4000
- Then search for the SDK Version in ORBI Place, for example in ff7r eboot the offset is at 0x6c00010
- 01 00 05 05 <- correct sdk version
- Then at the bottom of the eboot you can find the elf build name
- PATHH���D���c:/j/workspace/B/b_BuPS4M/cw/End/Binaries/PS4/End-PS4-Shipping.self
- After the PATH and name patch every single instance
- 05 05 00 01
-
Step 2: The modules
- These are easy, at the bottom there's an sdk version
- 05 05 00 01
- Near end of module
- Specifically for some modules, an extra step needs to be done:
- Search for 18 00 00 00 00 00 00 00 BF F4 13 3C 01 00 00 00
- After there is sdk version, patch it
- 01 00 05 05
- Some modules are also linked with others modules
- Again at bottom
- PATH0���*���C:/devel/projects/bink/build/Bink2PS4.prx
- After
- 05 05 00 01
- Every single instance
- This one is the most simple
- sdk_ver=
- After this put
- 05050001
- ASCII values
- Then there is a hidden one
- Before the game's name
- put
- 00 00 05 05
- This completes backporting
-
Step 1: The eboot
-
A tip from developer @Joonie Via Twitter
Pro Tip from @joonie
ISSUE: Star Wars Jedi
Backporting EA Titles (Guide)
ToolsPS4 RipKit AIO Tool (new backporting game feature)
1 Click PS4 downporter
Source of Tutorial: twitter.com/notzecoxao
Last edited:
