Skip to playerSkip to main content
  • 2 days ago
GoldHEN 2.4b18.5 public beta launch supporting many new previously unsupported firmwares. Should you update your PS5 to 11.60 to grab the lua demos and sync the disc drive? New PS5 tools and Laps3c0re progress.
--------------------------------------------------------------------------------------------------------
Links:

GoldHEN Public Beta: / discord

HackerOne Report: https://hackerone.com/playstation/hac...

Zeco on PS5 Update: https://x.com/notnotzecoxao/status/19...

Open Source etaHEN: https://x.com/LightningMods_/status/1...

ps5-dlc-toolchain: https://github.com/Gudui/ps5-dlc-tool...

Laps3c0re: https://github.com/iMrDJAi/laps3c0re
--------------------------------------------------------------------------------------------------------
Timestamps:
0:00 - Intro
0:11 - GoldHEN 2.4b18.5
4:48 - PS5 Bug Bounty
8:45 - etaHEN Open Source?
9:20 - ps5-dlc-toolchain
11:13 - Laps3c0re Update
--------------------------------------------------------------------------------------------------------
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 PS4 and PS5 jailbreak news update.
00:04We have a bunch of topics to dive into on the PS5, but one big one here for the PS4 just to start
00:10off with, and that is of course the new version of Gold Hen. There is a beta, a public beta that
00:16is currently available right now. You can join the Gold Hen Discord to be able to download the
00:21file for it. And this update provides a huge number of additional firmwares that are now
00:26supported with this version of Gold Hen, which is version 2.4b18.5. This particular version now has
00:33support from basically 5.05, 5.07, 6.71 and 6.72, along with all 7.x, 8.x, 9.x, 10.x, 11.x, which
00:44includes of course 11.02, 11.50 and 11.52 now supported with Gold Hen, and of course 12.0 and
00:5112.02 that were already supported. All of those firmwares are now supported with this current
00:56public beta. Now at the moment, the public beta is like a limited time. It's only accessible right
01:02now for 30 minutes, but it will likely end up in a full release fairly soon. Now probably the reason
01:07for the public beta is that with all of these additional firmwares now being added, we need a
01:12lot of people who are, you know, on all of these different firmwares to actually test it to see,
01:17you know, if there are any problems on certain firmwares with it not working correctly or certain
01:21features not working, crashes, instability issues, that kind of stuff, all needs to be worked out.
01:26And that is of course the purpose of these kinds of public beta tests. So give it a try on all of
01:31those different firmwares. If you're on an obscure firmware that now should have support for Gold Hen,
01:36definitely give this a try because we have so many new firmwares that are now supported,
01:41which is fantastic. There's also been some new features added in this new version, three new
01:46features. The first one is an improvement to the bin loader that runs on port 1990 that's now able
01:52to load elf files as well as bin files. There's also a time played option, game stats option now
01:58available. So if you go to any of your applications or games and press options and go to information,
02:03you will now see a time played at the top as well as game starts. So it counts the amount of time that
02:08you've spent on that application since running Gold Hen. And it also counts the number of game starts as
02:14well. So the number of times you've launched the application is now counted. So you've got game
02:19stats now showing up there as well. And the other feature of course in the Gold Hen settings is the
02:25date and time option. So if we go in here, you can update the date and time via the internet. You just
02:30select that option and it updates it using google.com. You can also change it if you're offline to a fake
02:36date of the 1st of January 2025. So if you can't sync online because you're keeping your console offline,
02:41you can instead just use that date instead, which is better than if your clock has been reset back to
02:481970, which happens if the CMOS battery dies in your PS4 and it's not able to
02:53keep the clock synced when power is cut to the console. Then whenever you reboot, it will reset the clock back to
03:001970. Now, as far as I'm aware, this is not a permanent fix for the kernel clock. The kernel clock, if it has been
03:07unsynced, this does not actually re-sync it properly. But what it does do is that it's a workaround, so that
03:13typically what you had to do before, if you were wanting the correct date and time, is that you'd have
03:18to go into the settings, to the date and time settings, and then enter the correct date and time. But then
03:24every time you reboot the console, if your CMOS battery had died, even if you've replaced it, if it died
03:29previously and you've replaced it with a working CMOS battery, it will still continuously reset back to
03:341970 every time you reboot the console, because it's not being properly synced with PSN, and there's
03:40no way to sync it with PSN right now if you're on an older firmware, because you need to be on the
03:45latest firmware to do that. So instead, what this does is it just basically does the same thing that
03:49you would do setting the clock manually. Instead, it can just do it online through the Google link
03:55instead, and it will set it for you so that you don't have to manually type it in every time you reboot
03:59the console, if your clock is constantly being reset. Plus you can also enable a auto update to
04:05the date and time on Goldhen startup, so that you don't have to come into this menu and update the
04:10date and time every time you reboot the system. It will just automatically run it as soon as you load
04:14Goldhen. So that's another handy feature that has been included in there for people who are having
04:19trouble with their clocks being reset due to a dead CMOS battery. So yeah, that is another handy
04:25feature that's been added there. But we may have to wait for the full release to get rid of this
04:30time limit that we have at the moment for the public beta. But again, that just might be the
04:35particular build that I downloaded at the time. Maybe there'll be other builds in the public beta
04:39that come out that do not have this time limit. And obviously, once the full release comes out or the
04:44full beta gets posted, it will no longer have that time limit applied. Okay, so moving on to some
04:49PS5 news now, we got this new $10,000 HackerOne report on PlayStation's HackerOne Bug Bounty
04:55program from SlidyBat. So unfortunately, I wasn't planning on covering this originally because
05:02of course, if the report's not from the flow, it's probably not going to get disclosed. We can see
05:07another report from SlidyBat that was 10 months old that was also $10,000 and still has not been
05:13made public. So that's why I normally don't kind of cover these particular things if it's not from the
05:19flow. However, the reason I'm covering it here is that there has been a lot of talk about this
05:23because of a post from Zekko, who said strong advice for those of you who are on firmwares
05:29between 10.20 and 11.60, pair your drive and wait, basically telling people to update to 11.60
05:36on a PS5 if you're waiting for a new jailbreak. He's saying if you basically have a console that
05:42does not have a paired disk drive, then you're not able to use any user land exploits at the moment
05:48because the only one that you have access to is the Lua exploit and the Lua exploit requires
05:53either you being on the latest firmware to get the demos or you having a paired disk drive so that you
05:58can get a physical disk version of the game that you can run in your console. And if you don't have
06:03that, then you have no way of actually running any future jailbreaks, any future kernel exploits that
06:07come out for the PS5. And that is the problem. So he's suggesting you just update. However, this was
06:13based on the idea that Slidybat's report is actually a kernel exploit that works up to 11.60 and will be
06:20patched in the upcoming 12.0 update that's currently in beta on the PS5 right now. However, that is not the
06:26case. As of course, Slidybat later clarified, saying that it's a bug that he reported almost a year ago and
06:33was fixed months ago. They just took forever to actually close slash payout. So nothing that would be
06:39interesting for new firmwares. Sorry to disappoint. It was likely patched before 11.60. So maybe not
06:45such a drastic need to update to 11.60 to pair your disk drive. Although Zeko is still recommending it
06:51here, saying that Slidybat's bug was patched before 12.0 or even 11.60. But he still thinks people should
06:58update to pair their drives before it's too late. And it is a bit of a dilemma if you are in that
07:02situation if you don't have a paired disk drive. Obviously, this does not apply to people who do have
07:07paired disk drives. But if you do not have a paired disk drive in your console, you're kind of in a
07:12kind of damned if you do, damned if you don't situation at the moment. It really depends whether
07:16or not a new WebKit exploit comes out first or if a new kernel exploit for 11.60 or higher comes out
07:24first. I think a new WebKit exploit or some kind of new user land exploit that doesn't require the disk
07:29drive is probably more likely to happen than a new kernel exploit on 11.60 or higher. But we just don't
07:36know for sure at the moment. So we can't really say one way or the other what the best option is
07:42here. You know, because normally we say stay on as low a firmware as possible. And that's great
07:46because new kernel exploits might come out for 10.60, 10.40, 11.0. And if you update to 11.60,
07:53you would lose access to those. But then if we don't have a WebKit exploit that comes out that you
07:58can then use to load those new kernel exploits that might come out on higher firmwares, then you're
08:03kind of screwed unless you have a paired disk drive you can use to trigger it with the Lua
08:08exploit instead. So that's kind of where the dilemma goes. Do you update to 11.60 just so that
08:13you can get the Lua exploit going? And at the same time, you can also download things like the Lua
08:17game demos and Okage Shadow King for the MasterCore exploit and get your console already with all of
08:23the user land exploits set up that you can potentially use for any new kernel exploits that
08:29come out in the future. Otherwise, you just stay on as low a firmware as possible and hope
08:33that a WebKit exploit comes out sometime soon that will then allow you to load any future jailbreaks
08:38using that instead. So that is pretty much the dilemma that some people are in if you do not have
08:44a paired disk drive. So next we have Lightning Mods who appears to be considering open sourcing
08:49ETA Hen in the next update. He says to like this tweet if you want to see a community driven version
08:54of open source homebrew enabler. And this would essentially allow a lot more developers to jump in
09:00and start working on ETA Hen to get to a point where we will hopefully see more updates happen
09:05for ETA Hen more frequently, more features being added, that kind of thing. So if you want to
09:11support that, then go ahead and like that tweet if you want to see ETA Hen get open sourced.
09:16So that is something that Lightning Mods appears to be considering quite seriously here. Okay,
09:20so moving on from that, we do have some other projects to talk about here. So we have this
09:24PS5 DLC toolchain from GADU or G-U-D-U-I. So basically this is designed to make it easier
09:32to patch your PS4 DLC because currently on the PS5 there's a problem with fake package DLCs.
09:40Your fake package PS4 games and PS4 fake package updates will install and run no problem on a
09:46jailbreakable PS5. But for some reason the DLC content does not. So any DLC packages you install,
09:52fake packages, you can install them. But when you run the game, the content, that DLC content will
09:58not actually appear and will not be accessible in game. So we have to use Idolsauce's DLC patcher to
10:04actually patch the DLC into the update file and that allows it to work. And that works for most
10:10DLC content for most PS4 games. However, it is a bit of an involved process. So this particular tool
10:16is designed to make it a little bit easier to use. All you really need to do is run the application
10:21and then give it the location of your fake package patch file and then the fake package base file.
10:27So the base package, the game package file, and then finally any DLC packages that you want to add.
10:33You then select that as the third option, all of the DLC that you want to pack inside the update file
10:39and then simply let it run. It will decrypt the executables and then patch them with the DLC patcher
10:44to load the DLC, repackage the update back into a package file that you can then install onto the
10:50game, which will then include all of the DLC as well as that update all included there. So that is
10:56pretty much how this works. It just makes it a lot easier because Idolsauce's original version
11:01required a few more extra steps that you had to do manually that this tool kind of automates now,
11:07which makes it a lot easier. Just pick the game and the patch package and then any DLC you want to add
11:11and it kind of handles the rest for you. Okay, so our final PS5 topic here is of course the
11:16lapse core project from D-Link Turtle, which aims to take the old MasterCore exploits that could be
11:21used to take the PlayStation 2 emulation in the PS5 and PS4, of course. And there's a game in there,
11:29Okage Shadow King, which has a save game exploit that could then be used to kind of break out of
11:33the emulator and use it to actually sideload other PlayStation 2 games. That's what MasterCore on its
11:39own was capable of. But now, of course, D-Link Turtle's trying to combine this exploit and use
11:44it as a userland exploit to then trigger the lapse kernel exploit. So that means if you have the game
11:49Okage Shadow King, which unfortunately is a digital only title that you would have had to have already
11:55purchased and licensed on your console before you took it offline and stayed on the older firmware.
12:00But, you know, if you were around in 2023, when I was originally covering the MasterCore
12:04exploit, you might happen to have a copy of this game, a working copy on your console. If you have
12:10a retail copy of this game, you might be able to use it soon to actually trigger the jailbreak.
12:14And the main updates on this is that it's now got Colonel Arbitry Read-Write added,
12:19and we actually got a screenshot from D-Link Turtle himself with the caption of
12:24Soon TM, and showing the PP pwned notification on the PS4,
12:28which would seem to indicate that he's actually got the exploit up and running here on the PS4,
12:36at least to the point of being able to actually, you know, get kernel access and get notifications
12:41going, which means that it's pretty much in the final stage at this point. So hopefully we might
12:46see a release coming fairly soon here. So that is the updates there. So anyway, guys, that's going
12:52to do it for me. So hope you guys enjoyed this video or found the information useful. If you did,
12:55please leave a like and subscribe. And once again, I'll hopefully see you guys in the next one.
Be the first to comment
Add your comment

Recommended