Jailbreak the PS5 up to 9.00 with New Kstuff Release!_2

jalal khan

We can now Jailbreak the PS5 up to 9.00 -------------------------------------------------------------------------------------------------------- Links:  Kstuff 8.00, 8.20, 8.40, 8.60: https://github.com/EchoStretch/kstuff...  Dump Runner: https://github.com/EchoStretch/dump_r...  Backup File: https://limewire.com/d/FJ8h2#KwFU4uYSOc  Web Server: https://github.com/ps5-payload-dev/we...  PSremote Lua Loader: https://github.com/Master-s/remote_lu...  NetCat GUI: https://www.sendspace.com/file/v765gd -------------------------------------------------------------------------------------------------------- Timestamps: 0:00 - Intro 0:14 - Kstuff Release 1:29 - Save Backup 3:02 - Manual Save Install 6:56 - Loading 8.00 kstuff 10:52 - Running PS4 & PS5 games  -------------------------------------------------------------------------------------------------------- Music Outro: Paul Flint - Sock It To Them -    • Paul Flint - Sock It To Them [NCS Release]   -------------------------------------------------------------------------------------------------------- Find my content on these other platforms: Odysee: https://odysee.com/@MODDEDWARFARE LBRY: https://lbry.tv/@MODDEDWARFARE BitChute: https://www.bitchute.com/channel/cZkN...

Transcript

00:00Hey, how's it going guys? Welcome back to another PS5 video. So it looks like we finally have

00:04K-Stuff for 8.00. This was added by Echo Stretch. Echo Stretch been putting in a lot of work

00:10over the past several weeks to get this out. So we can now jailbreak the PS5 up to 8.00.

00:17Now, if you're a little confused, we can technically jailbreak all the way up to 10.01.

00:22At least 10.01 is the highest jailbreakable firmware so far. But without K-Stuff support,

00:27we can't actually run any of our PS4 fake packages or any of our PS5 game dumps and certain

00:33homebrew applications cannot run on those higher firmwares until we get K-Stuff support. So up

00:39until this point, we could only jailbreak up to 7.61. However, with K-Stuff now supporting 8.00,

00:45we can now go one update higher and jailbreak up to 8.00 with this K-Stuff release. Now,

00:51not only is 8.00 K-Stuff released that you can download here from the GitHub repo,

00:55which will be left in the description along with everything else you need. We also have the

00:59dump runner updated as well for 8.00 support, which allows us to run our PS5 game dumps using

01:05just K-Stuff and the homebrew launcher from John Tornblum. So that is updated there as well.

01:12And of course, K-Stuff for 8.00 also has the DLC fix implemented as well. So it works all the way up

01:18to 8.00 now. So you can run your PS4 fake package games with DLC installed normally and the DLC will work.

01:25So that has also been included. So a few good updates there. So in order to actually jailbreak

01:30on 8.00, it requires the Japanese games to run the exploit because unfortunately all of the

01:37previous methods to load the jailbreak have been patched up to 8.00. So obviously the Blu-ray

01:42exploit was patched in 8.00 itself and the web browser exploit was patched much further back.

01:48So unfortunately, the Lua exploit is the only option. So you need one of the

01:52supported Japanese games from this list. So you need to have a physical copy of one of those games

01:57that you can then install and run on the console to load the save file. And then you need to get

02:03the modified save file installed here. You can download the remote Lua loader from here.

02:08Now there's a couple of different ways that you can get the save file installed. You can either use

02:12a backup file like one of Master S9's latest backups, which you can install. All you have to do is

02:18download the backup file and extract the PS5 folder to the root of your USB drive. Plug that USB drive

02:24into the PS5. Head over to the system settings and go to the backup and restore option and just select

02:30the option to restore the backup. Make sure you obviously backup your own system before restoring

02:35somebody else's backup, because when you restore someone else's backup, it will essentially reset the

02:40console. So you'll lose your save files and settings and maybe certain applications you have

02:45installed. So make sure that you make a backup first on your USB drive of your own system and then copy

02:51that somewhere safe on your computer and then restore the backup with the modified save files to be able to

02:57run the exploit from your Japanese game. So that's one option, of course. The other option is that if

03:03you're lucky enough to have had your PS5 connected to PSN at some point in the past and you still have

03:09that same profile on your console from when it was connected to PSN, then your account is online

03:15activated, which means you have the ability to copy save files between the hard drive and the USB

03:20on your PS5. In that case, you can basically just create a new save file on your Japanese game

03:25and then simply head into the settings and go to the save data and game app settings. And then from

03:32there, you can simply go to save data for PS4 and then go to upload or delete from console storage.

03:38And then you have the option to copy to USB drive. So you can simply copy the save file for the

03:44Japanese game to the USB, at which point you can then either use the free Discord save box to decrypt

03:51the save file and replace the decrypted save data with the one from the remote Lua loader.

03:55Or you can use Apollo save tool if you have a jailbroken PS4 or know somebody who does,

04:01they can use the Apollo save tool to basically do the same thing. All you have to do

04:05is make sure that the account on the PS4 is activated with the same account ID as the PSN

04:11account that's being used on the PS5. You can find your PS5's account ID by heading to

04:16psn.flipscreen.games, entering your PSN username of the account and clicking submit. You can copy

04:22that account ID and simply paste it into a decimal to hex converter. And that's the ID that you want to

04:27activate on the jailbroken PS4. And then from there, all you have to do is copy the save file from the

04:33USB to the hard drive using the Apollo save tool. Then go to your HDD saves on the Apollo save tool,

04:39select the save file and copy it back to the USB drive. And that will get the decrypted save data

04:44copied to the USB. Then all you have to do is plug that USB drive back into your computer and then open

04:49up the PS4 save, the decrypted version from the Apollo folder on your computer. There is also the

04:55auto Lua loader, which automatically loads the payloads for you. That one is normally my recommended

05:01one to go for. The problem is I've had like zero success actually getting it to load the lapse

05:06exploit so far. I tried loading it like 10 times and it would just fail every single time. So for me,

05:12the remote Lua loader seems to be more stable at the moment with 8.00. So that's just the one I'm

05:17going to use here. So basically we just go to the code, download it as a zip file, and then simply open

05:22up that zip file, go into the save data folder and copy all the files from the save data folder

05:28into the decrypted save data for your USB. And that will get the save file installed. You then

05:34just plug that back into the jailbroken PS4, go back to USB saves, press square to refresh, which will

05:40then show the save file without the padlock symbol, which is the one that is decrypted. And that is the

05:45one we modified. So we select that with X and then copy it to HDD again. And that will get the decrypted

05:51save now turned into an encrypted save for the console, at which point you can then exit out of the Apollo

05:57save tool, head over to application save data management in the system settings and go to

06:02console storage and simply copy it to the USB drive. And that will copy the encrypted version of the

06:08modified save to the USB. Once that's done, we can plug that USB drive back into our PS5. And then from

06:14there we can go back to our game app settings again on the PS5. And this time we can select save data on

06:20PS4 and copy or delete from the USB and then simply select the save file on the USB and copy that to the

06:26system storage. And that is how you get the save file installed. Again, you don't have to use another

06:31jailbroken PS4 to do this. You can also do the same thing with swapping out the decrypted save and then

06:36re-encrypting that back into an encrypted save and installing it back on the console. You can do the

06:41same thing using the free Discord save bots as well, like the ones on the HTOS Discord server. So that is

06:48another option. But basically those are the ways that you get the save file copied over to your console.

06:53So once we have a working version of the save file on our console, we can get set up here to run the

07:00jailbreak. So what we need to do is first of all, if I head over to my settings, we need to connect to

07:04our network. So if we go to our network settings, our settings, set up an internet connection, and then

07:10just press the options button on your registered network and go to advanced settings. And then from

07:15here we want to make sure that we have a DNS enabled. So if we go to DNS settings, we'll set a manual

07:21DNS and just use 62.210.38.117. And that'll get our DNS blocker there to block updates while allowing

07:30us to connect to the network, which we need to be able to use the remote LUA loader. So we'll just

07:35let it get connected back up to the network. It will say cannot connect to internet. That is normal,

07:39but it is actually connected because if we go into system software and console information, we can see

07:45that we do in fact have an IP address there 192.168.1.217. So that's all good. So at this point,

07:52all we need to do is run our Japanese game. And what that's going to do is run the remote LUA loader.

07:59Now, if you're using the backup method, it might just run the auto LUA loader, which you can try with

08:05that. But generally, I think there's normally two profiles with that backup. And one of the profiles

08:10has the remote LUA loader on it, and the other one has the automatic LUA loader on it. So obviously,

08:16you're going to want to sign into the profile that uses the RLL version, the remote LUA loader

08:21version, sign into that profile, which has this version of the save that runs the remote LUA loader

08:26instead of the auto loader. But anyway, as you can see, once we get it running here, we get listening

08:31on our IP address on port 9026 on PS5 8.00 firmware. So at this point, if we switch back over to our PS4,

08:39a few things we want. Obviously, the remote LUA loader we've already downloaded. We also want to

08:43grab this PS remote LUA loader from Master S or Master S9. So just go ahead and download this.

08:50Makes it a little bit easier for sending the payloads. So we're going to go ahead and download

08:54that. And then, of course, I also recommend having Netcat GUI and obviously our K stuff for 8.00

09:00from Echo Stretch. So at this point, what we're going to do is open up the remote LUA loader and then go

09:05into the payloads folder, then open up the PS remote LUA loader from Master S9. And we're just

09:13going to go into the files here, payloads, and basically replace all of the payloads in here

09:18with the one from the latest LUA loader release, just to make sure you have the latest payloads

09:23updated. So we're just going to go ahead and do that. And then we can go ahead and run this program.

09:28We want to enter our PS5's IP address in here, 1.217, port should be 9026. And then all we need

09:37to do is send the lapse payload here. So let's see what happens. We'll click lapse. It may not work

09:43successfully the first time. So we'll just give it some time. And yep, that was successful. There we go.

09:48Look at that. So worked first time there, cleaning up. So obviously, if you do not get the done exploit

09:54state saved into storage, if you do not get this message with debug settings enabled, then obviously

09:59it failed. So you'll have to restart and try again. We can close out of that now and now run the ELF

10:05loader, ELF loader. So we'll select that option next. We switch over to our PS5. You can see it's

10:11loaded the ELF loader there on screen. And then finally, we just need to actually send the KSTUFF

10:17payload now using a payload injector like Netcat GUI. I'll leave this one in the description. So we'll open

10:22this up. 192.168.1.217. Port number for this is 9021. You take the KSTUFF.ELF file downloaded from

10:30Echo Stretch's repo, and you just inject the payload. And there we go. As you can see, KSTUFF

10:36loaded successfully. And that is basically it. So you've now got the exploit set up. So we can go

10:43ahead and exit out of our Japanese game that's used to load the exploit there. And we now have KSTUFF

10:50successfully running. Check that out. So okay, so just as a demonstration here, I've got my USB

10:55drive with a bunch of PS4 DLC for Black Ops 3. Because of course, this version of KSTUFF has the

11:01DLC fix. So we should be able to not only just install and run our PS4 fake packages, but also

11:06run the DLC content as well, install the DLC packages and get those working too. And of course, I've got a

11:13PS5 game. So this is a PS5 game that will also test. In order to get your PS5 games working at the

11:20moment, we can use the dump runner that was also updated for 8.00 by Echo Stretch. So with the dump

11:26runner, all we need to do is basically on our USB, we can create a new folder called Homebrew. And then

11:32just take any PS5 game dump folders and copy them into the Homebrew folder. And then inside our game app

11:38folder that contains the game files for our PlayStation 5 game, we can basically extract

11:44the dump runner contents into that folder, which is the dump runner.elf and the homebrew.js.

11:50So we can just copy those in there. And then that should make this game loadable. So for the web

11:55serve payloads, you can download it from this repo PS5 payload dev from John Tornblum web serve. So if

12:02we go down here and show all assets, we can download the payload here, web serve dash ps5.elf.

12:09And of course, you want to head back to the main project itself and scroll down and download the

12:13launcher package as well, which will give you the package file, which you can copy over to the root

12:18of your USB drive and install with the debug settings package installer. So if we unplug that USB and plug it

12:24into the PS5, however, we do need to run the web serve payload. So this is John Tornblum's web serve

12:31payload. So we want to get this payload loaded as well. So to do that, I'll just open up netcat GUI

12:36again, and then take the web serve payload, load that in on port 9021. Again, we can just inject

12:43payload. And then that should run that on the PS5. There it is. So there we go. That should be it. So

12:49let's see if we can get our PS4 fake packages with DLC and everything working. So if I head into

12:54settings and go to debug settings, game package installer, we've of course got our homebrew loader package

13:01file here for running our PS5 game dumps and all of these DLC packages for Black Ops 3 that I'll

13:06install. And of course, this will hopefully get all the DLC working for my fake package version of

13:12Black Ops 3. Okay, so that's all the DLC installed. Just installing the homebrew loader as well for our

13:18PS5 game. And there we go. Everything is now good. So if we press options, manage game contents,

13:25as you can see, all of our DLC shows up. Kind of cool that on 8.00 and I'm not sure when they

13:31changed this, but I remember like checking my 4.03 system and it would just say like six items

13:36installed. It wouldn't actually list them like this, but you can actually see them all showing up here

13:40as installed. Not sure why Nuketown bonus map is apparently not installed, but everything else is

13:45installed. So if we go ahead and run this, so this is a PS4 fake package game running on 8.00

13:51with all the DLC installed normally. So it should show up with this updated version of KStuff. Okay,

13:58and there is, we have the game loaded up. If I just check the zombie map packs, you can see we have them

14:02all installed. So all the DLC is working. So we've got our PS4 fake packages running on 8.00 with this

14:09version of KStuff with working DLC content now. No need to merge the DLC content with the update file

14:16like we had to do in the past. So a big improvement there. And as for our PS5 game dumps,

14:21we can use the homebrew launcher that I installed and hopefully this will get it up and running. So

14:26there is, there's the high on life PS5 version of the game here showing up and I'll try and launch

14:31this. And if I just press circle to close, it should start running the game. And there is PS5 games also

14:40running on 8.00 with this exploit. So I know the installation was a little bit complicated and

14:46that's because it's not really been streamlined yet for ease of use. So we still have to use the

14:51remote Lua loader. Technically, it might work occasionally with the auto Lua loader. But for

14:57me, it just fails too many times for it to be worth using that at the moment. So yeah, the remote Lua

15:02loader just seems to work a little bit better. It's more stable. But anyway, that's just a rough way of

15:07getting things set up right now in the early stages of this exploit of this firmware getting support.

15:13But hopefully, you know, things will kind of smoothen out over time and there'll be

15:17an easier way to kind of handle this in the future with the auto loader. And then I'll come back and

15:22cover it more in depth with a more in depth beginner's guide once everything is up and running

15:27fully. So anyway, that's going to do it here for this one. So hope you guys enjoyed this video or

15:31found the information useful. If you did, please leave a like and subscribe. And once again,

15:34I'll hopefully see you guys in the next one.

15:43Bye.

Category

Transcript

Be the first to comment

Recommended