All language subtitles for [English (auto-generated)] PS4_PS5 Jailbreak News_ Is Mastic0re Dead_, PSVue 13.00 Progress, Y2JB Web-UI, FTP Boost & More! [DownSub.com]

af Afrikaans
ak Akan
sq Albanian
am Amharic
ar Arabic Download
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bem Bemba
bn Bengali
bh Bihari
bs Bosnian
br Breton
bg Bulgarian
km Cambodian
ca Catalan
ceb Cebuano
chr Cherokee
ny Chichewa
zh-CN Chinese (Simplified)
zh-TW Chinese (Traditional)
co Corsican
hr Croatian
cs Czech
da Danish
nl Dutch
en English
eo Esperanto
et Estonian
ee Ewe
fo Faroese
tl Filipino
fi Finnish
fr French
fy Frisian
gaa Ga
gl Galician
ka Georgian
de German
el Greek
gn Guarani
gu Gujarati
ht Haitian Creole
ha Hausa
haw Hawaiian
iw Hebrew
hi Hindi
hmn Hmong
hu Hungarian
is Icelandic
ig Igbo
id Indonesian
ia Interlingua
ga Irish
it Italian
ja Japanese
jw Javanese
kn Kannada
kk Kazakh
rw Kinyarwanda
rn Kirundi
kg Kongo
ko Korean
kri Krio (Sierra Leone)
ku Kurdish
ckb Kurdish (Soranî)
ky Kyrgyz
lo Laothian
la Latin
lv Latvian
ln Lingala
lt Lithuanian
loz Lozi
lg Luganda
ach Luo
lb Luxembourgish
mk Macedonian
mg Malagasy
ms Malay
ml Malayalam
mt Maltese
mi Maori
mr Marathi
mfe Mauritian Creole
mo Moldavian
mn Mongolian
my Myanmar (Burmese)
sr-ME Montenegrin
ne Nepali
pcm Nigerian Pidgin
nso Northern Sotho
no Norwegian
nn Norwegian (Nynorsk)
oc Occitan
or Oriya
om Oromo
ps Pashto
fa Persian
pl Polish
pt-BR Portuguese (Brazil)
pt Portuguese (Portugal)
pa Punjabi
qu Quechua
ro Romanian
rm Romansh
nyn Runyakitara
ru Russian
sm Samoan
gd Scots Gaelic
sr Serbian
sh Serbo-Croatian
st Sesotho
tn Setswana
crs Seychellois Creole
sn Shona
sd Sindhi
si Sinhalese
sk Slovak
sl Slovenian
so Somali
es Spanish
es-419 Spanish (Latin American)
su Sundanese
sw Swahili
sv Swedish
tg Tajik
ta Tamil
tt Tatar
te Telugu
th Thai
ti Tigrinya
to Tonga
lua Tshiluba
tum Tumbuka
tr Turkish
tk Turkmen
tw Twi
ug Uighur
uk Ukrainian
ur Urdu
uz Uzbek
vi Vietnamese
cy Welsh
wo Wolof
xh Xhosa
yi Yiddish
yo Yoruba
zu Zulu
Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 00:00:00,080 --> 00:00:01,280 Hey, how's it going guys? Welcome back 2 00:00:01,280 --> 00:00:03,679 to another PS4 and PS5 jailbreak news 3 00:00:03,679 --> 00:00:06,000 update. Lots of topics to dive into here 4 00:00:06,000 --> 00:00:08,160 in this video. Starting with some 5 00:00:08,160 --> 00:00:11,200 unfortunately bad news, it seems in 6 00:00:11,200 --> 00:00:13,200 terms of the Mastercore exploits and 7 00:00:13,200 --> 00:00:16,240 this is brought to us uh by GJI. So, of 8 00:00:16,240 --> 00:00:17,840 course, this is the exploit using the 9 00:00:17,840 --> 00:00:20,080 Star Wars Racer Revenge game that was 10 00:00:20,080 --> 00:00:21,600 hoping to be chained with the Colonel 11 00:00:21,600 --> 00:00:23,359 exploit to be able to jailbreak higher 12 00:00:23,359 --> 00:00:26,480 firmwares on the PS5 above 10.01 up to 13 00:00:26,480 --> 00:00:29,039 firmwares up to 12.0. 14 00:00:29,039 --> 00:00:31,119 That was the general idea because of 15 00:00:31,119 --> 00:00:33,200 course the masterore exploit has the 16 00:00:33,200 --> 00:00:35,680 dupe privilege sis call that's needed 17 00:00:35,680 --> 00:00:37,520 for a userland exploit to be able to 18 00:00:37,520 --> 00:00:39,360 trigger the kernel exploit to jailbreak 19 00:00:39,360 --> 00:00:42,239 the console. Now we actually got a 20 00:00:42,239 --> 00:00:44,719 pretty positive update initially from 21 00:00:44,719 --> 00:00:46,960 developer gaj here showing lua core 22 00:00:46,960 --> 00:00:49,920 finished from PS2 EMU escape to chaining 23 00:00:49,920 --> 00:00:52,160 Lua code execution with full primitives. 24 00:00:52,160 --> 00:00:54,559 We'll prepare a GitHub in a few days. So 25 00:00:54,559 --> 00:00:55,840 everything was looking good. It looked 26 00:00:55,840 --> 00:00:57,680 like the userland exploit was 27 00:00:57,680 --> 00:00:59,120 essentially done and then it was just a 28 00:00:59,120 --> 00:01:00,800 case of chaining it with the kernel 29 00:01:00,800 --> 00:01:02,320 exploit and then we'd have a jailbreak 30 00:01:02,320 --> 00:01:04,239 that we could use with this Star Wars 31 00:01:04,239 --> 00:01:07,600 game. However, over the past couple of 32 00:01:07,600 --> 00:01:11,040 hours, we got an update from Gina here 33 00:01:11,040 --> 00:01:13,280 saying, "So, we have a situation. 34 00:01:13,280 --> 00:01:15,840 Mastercore does have the dupe privilege, 35 00:01:15,840 --> 00:01:18,960 but at some point firmware 8.xx, XX. So 36 00:01:18,960 --> 00:01:21,280 some firmware around there, Sony has 37 00:01:21,280 --> 00:01:23,759 removed the network socket privilege 38 00:01:23,759 --> 00:01:26,479 from the PlayStation 2 emulator. Now for 39 00:01:26,479 --> 00:01:29,200 Colonel Rewrite Primitive, past exploits 40 00:01:29,200 --> 00:01:32,560 used the IPv6 sockets and Mastercore 41 00:01:32,560 --> 00:01:35,600 cannot use that. So we need some kind of 42 00:01:35,600 --> 00:01:37,280 alternative. 43 00:01:37,280 --> 00:01:39,600 So not looking good. Now you can see in 44 00:01:39,600 --> 00:01:41,360 the initial video that was posted 45 00:01:41,360 --> 00:01:43,200 showing the userland exploit up and 46 00:01:43,200 --> 00:01:45,759 running. We can see it is successfully 47 00:01:45,759 --> 00:01:47,840 mounting the save data for Lua 48 00:01:47,840 --> 00:01:50,079 transition and then it transitions over 49 00:01:50,079 --> 00:01:53,360 to the Lua based exploit. And you can 50 00:01:53,360 --> 00:01:55,200 see there we have a remote Lua loader 51 00:01:55,200 --> 00:01:57,040 running. So the idea is that it's using 52 00:01:57,040 --> 00:01:59,360 the Mastercore exploit to unlock some 53 00:01:59,360 --> 00:02:01,840 kind of Lua execution within the game or 54 00:02:01,840 --> 00:02:04,560 within the emulator that can then allow 55 00:02:04,560 --> 00:02:07,280 it to run a remote Lua loader to execute 56 00:02:07,280 --> 00:02:08,959 Lua scripts that are sent over the 57 00:02:08,959 --> 00:02:10,959 network. But it looks like the net 58 00:02:10,959 --> 00:02:13,280 sockets function is not working on 59 00:02:13,280 --> 00:02:15,360 higher firmwares which would prevent 60 00:02:15,360 --> 00:02:17,840 this remote Lua loader from working. And 61 00:02:17,840 --> 00:02:20,080 I believe that function or some other 62 00:02:20,080 --> 00:02:22,720 functions that are now blocked in these 63 00:02:22,720 --> 00:02:24,879 higher firmwares are needed for the poop 64 00:02:24,879 --> 00:02:26,640 exploits to work which would prevent 65 00:02:26,640 --> 00:02:28,239 this from being used to chain it with 66 00:02:28,239 --> 00:02:30,239 the poop exploit to jailbreak. Unless 67 00:02:30,239 --> 00:02:32,080 some kind of alternative, you know, 68 00:02:32,080 --> 00:02:34,000 method to load it can be found. Some 69 00:02:34,000 --> 00:02:37,360 kind of alternative for these particular 70 00:02:37,360 --> 00:02:40,000 um SIS calls. If those can be, you know, 71 00:02:40,000 --> 00:02:41,599 changed to something else that does 72 00:02:41,599 --> 00:02:43,200 work, then maybe there's still a chance 73 00:02:43,200 --> 00:02:45,360 for this exploit to survive. Now, I 74 00:02:45,360 --> 00:02:47,599 believe the issue is that, of course, 75 00:02:47,599 --> 00:02:49,519 Gina here, you can see, is on firmware 76 00:02:49,519 --> 00:02:52,160 6.02. So, the whole time this developer 77 00:02:52,160 --> 00:02:53,840 has been testing this on an older 78 00:02:53,840 --> 00:02:56,080 firmware, 6.02, which is just, I guess, 79 00:02:56,080 --> 00:02:57,760 the firmware that their console happens 80 00:02:57,760 --> 00:03:00,560 to be on, and it was working fine on 81 00:03:00,560 --> 00:03:02,560 that particular firmware. But then you 82 00:03:02,560 --> 00:03:05,440 can see here on the higher firmware, I 83 00:03:05,440 --> 00:03:07,519 guess this is being tested on when 84 00:03:07,519 --> 00:03:09,360 trying to invoke particular functions 85 00:03:09,360 --> 00:03:10,959 that are needed for the exploit. Here on 86 00:03:10,959 --> 00:03:12,959 higher firmwares, we can see these 87 00:03:12,959 --> 00:03:15,040 errors are appearing. Socket execute 88 00:03:15,040 --> 00:03:18,239 af_etet 6 failed. Function not 89 00:03:18,239 --> 00:03:19,920 implemented. Function not implemented. 90 00:03:19,920 --> 00:03:21,760 So it seems that Sony has removed some 91 00:03:21,760 --> 00:03:23,599 of these functions from the PlayStation 92 00:03:23,599 --> 00:03:26,480 2 emulator. So they no longer exist and 93 00:03:26,480 --> 00:03:28,800 cannot be implemented. So this is a 94 00:03:28,800 --> 00:03:30,959 pretty big blow in the development of 95 00:03:30,959 --> 00:03:33,200 this exploit. We hope that some kind of 96 00:03:33,200 --> 00:03:35,120 alternative could be implemented or 97 00:03:35,120 --> 00:03:37,920 found, but uh it's certainly not looking 98 00:03:37,920 --> 00:03:40,480 good at this stage for higher firmwares 99 00:03:40,480 --> 00:03:42,720 with this exploit. So now this doesn't 100 00:03:42,720 --> 00:03:44,400 immediately mean that this exploit is 101 00:03:44,400 --> 00:03:46,400 completely dead in the water. Of course, 102 00:03:46,400 --> 00:03:48,159 other alternative functions could be 103 00:03:48,159 --> 00:03:50,400 found to make this work and the poop 104 00:03:50,400 --> 00:03:52,480 exploit could be reworked to use those 105 00:03:52,480 --> 00:03:54,159 different functions in order to get that 106 00:03:54,159 --> 00:03:56,080 to work with it. So, it's there's always 107 00:03:56,080 --> 00:03:58,080 a possibility that this could still end 108 00:03:58,080 --> 00:04:00,080 up turning into a working exploit to 109 00:04:00,080 --> 00:04:02,400 load the jailbreak on higher firmwares, 110 00:04:02,400 --> 00:04:03,680 but obviously that's going to take a lot 111 00:04:03,680 --> 00:04:05,200 longer cuz it's going to require a lot 112 00:04:05,200 --> 00:04:07,120 of research. And if an alternative is 113 00:04:07,120 --> 00:04:08,720 found, then the exploit's going to have 114 00:04:08,720 --> 00:04:10,720 to be completely reworked to use that 115 00:04:10,720 --> 00:04:12,640 alternative to get it working on higher 116 00:04:12,640 --> 00:04:14,080 firmware. So, I'll definitely keep my 117 00:04:14,080 --> 00:04:15,439 fingers crossed that some kind of 118 00:04:15,439 --> 00:04:17,680 alternative solution can be found. But, 119 00:04:17,680 --> 00:04:19,519 it's certainly not looking great at the 120 00:04:19,519 --> 00:04:21,600 moment for this particular exploit. Now, 121 00:04:21,600 --> 00:04:24,160 it is working fine on the PS4, but not 122 00:04:24,160 --> 00:04:25,840 that that's really much of a consolation 123 00:04:25,840 --> 00:04:27,680 because, of course, the PlayStation 4 124 00:04:27,680 --> 00:04:29,360 has other userland exploits like the 125 00:04:29,360 --> 00:04:30,800 PlayStation View exploit that's been 126 00:04:30,800 --> 00:04:32,800 implemented and the Blu-ray exploits. 127 00:04:32,800 --> 00:04:34,960 So, this doesn't have that much utility 128 00:04:34,960 --> 00:04:37,280 on the PS4 and it's working on older 129 00:04:37,280 --> 00:04:39,759 firmwares on the PS5, below 8.x 130 00:04:39,759 --> 00:04:41,680 firmwares, but again, we have other 131 00:04:41,680 --> 00:04:43,360 jailbreaks we can use on those older 132 00:04:43,360 --> 00:04:45,600 firmwares. Anyway, so we also have some 133 00:04:45,600 --> 00:04:48,000 updates to the PlayStation View exploit 134 00:04:48,000 --> 00:04:49,360 which is going to be used to jailbreak 135 00:04:49,360 --> 00:04:52,479 the PS4 up to firmware 13.0. Now, the 136 00:04:52,479 --> 00:04:54,160 first thing I saw in this was that there 137 00:04:54,160 --> 00:04:55,759 were some people getting confused about 138 00:04:55,759 --> 00:04:58,800 13.02, as if 13.02 was going to be 139 00:04:58,800 --> 00:05:00,560 supported. The thing is, yes, the 140 00:05:00,560 --> 00:05:02,720 PlayStation View exploit may work up to 141 00:05:02,720 --> 00:05:06,080 13.02 as a userland exploit, but the 142 00:05:06,080 --> 00:05:07,919 kernel exploit that we're triggering 143 00:05:07,919 --> 00:05:10,240 only works up to 13.0. That's the 144 00:05:10,240 --> 00:05:12,080 highest kernel exploit we have for the 145 00:05:12,080 --> 00:05:14,639 PS4 right now. which basically means 146 00:05:14,639 --> 00:05:16,000 we're only going to be able to jailbreak 147 00:05:16,000 --> 00:05:18,800 up to 13.0 because the kernel exploit is 148 00:05:18,800 --> 00:05:20,240 what actually jailbreaks the console, 149 00:05:20,240 --> 00:05:22,320 not the userland exploit. So just 150 00:05:22,320 --> 00:05:24,639 because uh PlayStation View exploits may 151 00:05:24,639 --> 00:05:26,880 work up to 13.02 doesn't mean we're 152 00:05:26,880 --> 00:05:28,880 going to get a jailbreak up to 13.02, 153 00:05:28,880 --> 00:05:31,600 just 13.0 for now until a new kernel 154 00:05:31,600 --> 00:05:34,479 exploit comes out that supports 13.02. 155 00:05:34,479 --> 00:05:36,560 So that's the situation there. But then 156 00:05:36,560 --> 00:05:38,560 as for actual updates, we've had a few 157 00:05:38,560 --> 00:05:40,240 pieces of information. And first of all, 158 00:05:40,240 --> 00:05:42,479 Earth Onion has stated that the Vue 159 00:05:42,479 --> 00:05:44,320 userland exploit is actually very 160 00:05:44,320 --> 00:05:46,720 stable. So that's excellent news. We're 161 00:05:46,720 --> 00:05:48,800 getting a pretty stable entry point to 162 00:05:48,800 --> 00:05:50,720 trigger the kernel exploit. Now, we also 163 00:05:50,720 --> 00:05:52,800 got some information from Dr. Yenyen 164 00:05:52,800 --> 00:05:54,639 outlining some of the challenges in 165 00:05:54,639 --> 00:05:56,639 getting this PlayStation View exploit 166 00:05:56,639 --> 00:05:58,880 done and finished. So, at the moment, 167 00:05:58,880 --> 00:06:00,639 there are several things that need to be 168 00:06:00,639 --> 00:06:02,479 bypassed, and we can see the progress 169 00:06:02,479 --> 00:06:03,680 that is made here. I'm just going to 170 00:06:03,680 --> 00:06:06,000 summarize it here in this video. Uh, so 171 00:06:06,000 --> 00:06:08,000 basically we've got four screenshots 172 00:06:08,000 --> 00:06:09,680 showing some different prompts that 173 00:06:09,680 --> 00:06:11,120 appear when trying to load the 174 00:06:11,120 --> 00:06:13,199 PlayStation View exploit that need to be 175 00:06:13,199 --> 00:06:16,400 worked around. So the first one is the 176 00:06:16,400 --> 00:06:18,240 sign into PlayStation Network to use 177 00:06:18,240 --> 00:06:20,080 network features. You'll get this if you 178 00:06:20,080 --> 00:06:21,520 try and launch the PlayStation View 179 00:06:21,520 --> 00:06:23,360 application without an activated 180 00:06:23,360 --> 00:06:24,960 account. This of course can be worked 181 00:06:24,960 --> 00:06:27,039 around with the backup file. So when we 182 00:06:27,039 --> 00:06:28,800 restore the backup file which contains 183 00:06:28,800 --> 00:06:30,400 the exploit in the PlayStation View 184 00:06:30,400 --> 00:06:32,800 application, it will also contain a fake 185 00:06:32,800 --> 00:06:34,319 activated account which will allow you 186 00:06:34,319 --> 00:06:36,319 to launch the application to bypass this 187 00:06:36,319 --> 00:06:38,240 error. So that's already essentially 188 00:06:38,240 --> 00:06:41,199 been solved. Now the second prompt that 189 00:06:41,199 --> 00:06:43,840 you get when PlayStation View is loaded 190 00:06:43,840 --> 00:06:45,840 is this one. This service requires you 191 00:06:45,840 --> 00:06:47,520 to sign into PlayStation Network. 192 00:06:47,520 --> 00:06:49,759 Apparently, this does not appear if 193 00:06:49,759 --> 00:06:51,919 you're actually using a proper PSN 194 00:06:51,919 --> 00:06:54,000 activated account. But for fake 195 00:06:54,000 --> 00:06:55,520 activated accounts, you will get this 196 00:06:55,520 --> 00:06:57,600 prompt and you just click okay and it 197 00:06:57,600 --> 00:06:59,520 should then start running the exploit. 198 00:06:59,520 --> 00:07:01,039 Then they also had to bypass this 199 00:07:01,039 --> 00:07:02,960 prompt. There is a network communication 200 00:07:02,960 --> 00:07:04,720 issue. The service is not responding. 201 00:07:04,720 --> 00:07:06,880 Click okay to try again or quit the 202 00:07:06,880 --> 00:07:09,199 application using the PS button. So 203 00:07:09,199 --> 00:07:11,120 apparently this one is bypassed via the 204 00:07:11,120 --> 00:07:12,880 save file. So something added to the 205 00:07:12,880 --> 00:07:15,120 save file that allows us to bypass this 206 00:07:15,120 --> 00:07:17,919 which is also present in the PC that was 207 00:07:17,919 --> 00:07:20,080 released by Earth Onion. And then the 208 00:07:20,080 --> 00:07:21,520 final prompt and this is the one that 209 00:07:21,520 --> 00:07:24,240 isn't bypassable uh at the moment which 210 00:07:24,240 --> 00:07:25,919 is that there is a problem connecting to 211 00:07:25,919 --> 00:07:27,280 the internet. Check the connect to 212 00:07:27,280 --> 00:07:29,360 internet setting in settings network and 213 00:07:29,360 --> 00:07:30,800 that you are connected to the internet. 214 00:07:30,800 --> 00:07:32,720 Click okay to try again. This is what 215 00:07:32,720 --> 00:07:34,160 happens if you're not connected to the 216 00:07:34,160 --> 00:07:36,400 internet. So So in its current form, you 217 00:07:36,400 --> 00:07:38,560 need an internet connection on the PS4 218 00:07:38,560 --> 00:07:40,960 to be able to get by this prompt. So you 219 00:07:40,960 --> 00:07:42,319 will not receive this prompt and you'll 220 00:07:42,319 --> 00:07:44,560 be able to actually get the PlayStation 221 00:07:44,560 --> 00:07:46,880 view application running to execute the 222 00:07:46,880 --> 00:07:49,520 exploit. So that's the kind of last 223 00:07:49,520 --> 00:07:51,520 purdle at the moment for the view 224 00:07:51,520 --> 00:07:53,919 application is bypassing this. Maybe 225 00:07:53,919 --> 00:07:56,080 some way to bypass this so that you can 226 00:07:56,080 --> 00:07:58,400 still use it offline because at the 227 00:07:58,400 --> 00:07:59,840 moment it requires an internet 228 00:07:59,840 --> 00:08:01,680 connection. And this is all going on 229 00:08:01,680 --> 00:08:03,919 while the kernel exploit is also being 230 00:08:03,919 --> 00:08:06,560 ported at the same time. So work is 231 00:08:06,560 --> 00:08:08,639 still ongoing importing the net control 232 00:08:08,639 --> 00:08:10,400 exploit from the flow while a more 233 00:08:10,400 --> 00:08:11,759 efficient version of the userland 234 00:08:11,759 --> 00:08:13,759 exploit is trying to be created to you 235 00:08:13,759 --> 00:08:16,400 know bypass these prompts uh as well. So 236 00:08:16,400 --> 00:08:18,560 those are our PlayStation view updates 237 00:08:18,560 --> 00:08:20,960 so far. A few other interesting updates. 238 00:08:20,960 --> 00:08:22,960 We got the release of Shadow Mount from 239 00:08:22,960 --> 00:08:25,520 Void Whisper which was then subsequently 240 00:08:25,520 --> 00:08:28,479 deleted not long after. So, Shadow Mount 241 00:08:28,479 --> 00:08:30,639 is a payload that kind of acts more like 242 00:08:30,639 --> 00:08:33,360 a plug-in that runs in the background 243 00:08:33,360 --> 00:08:35,200 and allows you to automatically mount 244 00:08:35,200 --> 00:08:37,440 your PlayStation 5 or PlayStation 4 game 245 00:08:37,440 --> 00:08:40,240 dumps. But generally, the idea is that 246 00:08:40,240 --> 00:08:42,560 you run this payload, preferably when 247 00:08:42,560 --> 00:08:43,919 you load the jailbreak so that you don't 248 00:08:43,919 --> 00:08:45,440 have to send it separately. And then 249 00:08:45,440 --> 00:08:48,160 whenever you load any game backups onto 250 00:08:48,160 --> 00:08:50,720 say a USB drive, external hard drive, 251 00:08:50,720 --> 00:08:52,959 uh, or transfer it over to the conso's 252 00:08:52,959 --> 00:08:54,959 internal storage or an M.2 two drive. 253 00:08:54,959 --> 00:08:56,560 The payload runs in the background and 254 00:08:56,560 --> 00:08:59,120 it's automatically scanning uh those 255 00:08:59,120 --> 00:09:01,279 directories and those locations where 256 00:09:01,279 --> 00:09:03,200 you typically store your game dumps and 257 00:09:03,200 --> 00:09:04,800 then it will detect if a new game has 258 00:09:04,800 --> 00:09:06,959 been added and it will automatically 259 00:09:06,959 --> 00:09:09,440 create the shortcut on the homepage to 260 00:09:09,440 --> 00:09:11,519 be able to run that game backup. It's 261 00:09:11,519 --> 00:09:12,640 really easy, especially if you're 262 00:09:12,640 --> 00:09:14,320 loading your games onto like a USB 263 00:09:14,320 --> 00:09:16,240 storage of some kind. You can just copy 264 00:09:16,240 --> 00:09:18,720 your game dump folders on, plug the USB 265 00:09:18,720 --> 00:09:20,320 drive into your PS5, and with that 266 00:09:20,320 --> 00:09:22,080 payload running, it will automatically 267 00:09:22,080 --> 00:09:24,080 detect that new games have been added. 268 00:09:24,080 --> 00:09:25,200 It will create these shortcuts 269 00:09:25,200 --> 00:09:26,959 automatically on the homepage, and you 270 00:09:26,959 --> 00:09:28,320 can load them directly from the home 271 00:09:28,320 --> 00:09:30,320 menu and get your game dumps running. 272 00:09:30,320 --> 00:09:31,920 It's really the most convenient way to 273 00:09:31,920 --> 00:09:34,560 get your game dumps running on the PS5 274 00:09:34,560 --> 00:09:36,640 at the moment. Now, there was an update 275 00:09:36,640 --> 00:09:39,360 to version 1.3, which now scans more 276 00:09:39,360 --> 00:09:40,800 locations, including the root 277 00:09:40,800 --> 00:09:44,160 directories of your like USB drive, M.2. 278 00:09:44,160 --> 00:09:45,839 Then all of a sudden the whole project I 279 00:09:45,839 --> 00:09:47,519 think including the account was removed 280 00:09:47,519 --> 00:09:49,600 from GitHub. The account is back and the 281 00:09:49,600 --> 00:09:51,200 Shadow Mount project's back but the 282 00:09:51,200 --> 00:09:53,360 release is still missing. Although maybe 283 00:09:53,360 --> 00:09:55,040 has been updated by now. Ah, there we 284 00:09:55,040 --> 00:09:56,959 go. It's back now. I just refreshed the 285 00:09:56,959 --> 00:09:59,839 page. It's back. Okay. So there we go. 286 00:09:59,839 --> 00:10:02,080 So we're now on version 1.3b. So we can 287 00:10:02,080 --> 00:10:03,839 see what was included here. This release 288 00:10:03,839 --> 00:10:05,680 has been reposted after being flagged. 289 00:10:05,680 --> 00:10:07,279 Okay. So it was flagged. That's why it 290 00:10:07,279 --> 00:10:09,600 was removed from GitHub, but it is now 291 00:10:09,600 --> 00:10:11,920 restored. So you can now access it here. 292 00:10:11,920 --> 00:10:14,000 I did upload a separate link so people 293 00:10:14,000 --> 00:10:16,000 could still access the files when the 294 00:10:16,000 --> 00:10:18,240 project was down, but now it is back up 295 00:10:18,240 --> 00:10:20,399 on the official repo. So, you can go 296 00:10:20,399 --> 00:10:22,160 ahead and just download it directly from 297 00:10:22,160 --> 00:10:24,560 here. So, definitely a useful payload 298 00:10:24,560 --> 00:10:25,920 for running your PlayStation 4 and 299 00:10:25,920 --> 00:10:28,000 PlayStation 5 game backups, but you do 300 00:10:28,000 --> 00:10:29,600 need to make sure you're using Kstuff 301 00:10:29,600 --> 00:10:31,519 version 1.6.7 302 00:10:31,519 --> 00:10:33,360 in order for this to work. And of 303 00:10:33,360 --> 00:10:35,120 course, you can update the version of 304 00:10:35,120 --> 00:10:38,640 KStuff within ETA hen in the KS menu by 305 00:10:38,640 --> 00:10:40,399 using the option to download the latest 306 00:10:40,399 --> 00:10:42,160 KS stuff version from GitHub and then 307 00:10:42,160 --> 00:10:44,160 reloading the jailbreak and ETA hen will 308 00:10:44,160 --> 00:10:46,320 then load that latest version of K stuff 309 00:10:46,320 --> 00:10:48,959 that's compatible with this payload. So 310 00:10:48,959 --> 00:10:50,399 that's the other development and again I 311 00:10:50,399 --> 00:10:52,000 have a full tutorial breaking down how 312 00:10:52,000 --> 00:10:54,079 to set up that payload. Now in other 313 00:10:54,079 --> 00:10:55,600 news, we also got the release of this 314 00:10:55,600 --> 00:10:58,079 YouTube jailbreak web UI from NASI. So 315 00:10:58,079 --> 00:11:00,399 NASI is getting into PS5 development 316 00:11:00,399 --> 00:11:02,079 which is great. So we can see we've got 317 00:11:02,079 --> 00:11:03,360 the ability to manage the YouTube 318 00:11:03,360 --> 00:11:05,839 jailbreak using a web UI. So I haven't 319 00:11:05,839 --> 00:11:07,040 really had a lot of time to look into 320 00:11:07,040 --> 00:11:08,880 this but I believe the idea is that it 321 00:11:08,880 --> 00:11:10,720 runs a web server on you know some 322 00:11:10,720 --> 00:11:12,640 device on your local network and then 323 00:11:12,640 --> 00:11:14,959 from there the YouTube jailbreak when it 324 00:11:14,959 --> 00:11:17,360 loads it reaches out over the network 325 00:11:17,360 --> 00:11:19,839 and this web server will respond by 326 00:11:19,839 --> 00:11:21,760 sending whatever payloads you want it to 327 00:11:21,760 --> 00:11:23,600 load. So you can update this payloads 328 00:11:23,600 --> 00:11:25,839 folder with any payloads that you want 329 00:11:25,839 --> 00:11:27,519 uh YouTube jailbreak to load and then 330 00:11:27,519 --> 00:11:28,800 when the web server is running and you 331 00:11:28,800 --> 00:11:30,560 run the YouTube jailbreak on the PS5, it 332 00:11:30,560 --> 00:11:32,079 will receive those payloads and execute 333 00:11:32,079 --> 00:11:34,000 them one by one. I believe that's the 334 00:11:34,000 --> 00:11:37,200 general idea. Now you could also perhaps 335 00:11:37,200 --> 00:11:39,200 use this to update the exploit itself 336 00:11:39,200 --> 00:11:40,640 whenever there's any new updates 337 00:11:40,640 --> 00:11:42,640 available. And we can also see there's a 338 00:11:42,640 --> 00:11:45,440 update here showing another update to 339 00:11:45,440 --> 00:11:47,680 the web UI of a payload injector that 340 00:11:47,680 --> 00:11:49,920 can be used to remotely send payloads to 341 00:11:49,920 --> 00:11:52,079 the console. And we can see here sending 342 00:11:52,079 --> 00:11:56,079 the shadow mount beta version 1.3 and 343 00:11:56,079 --> 00:11:58,160 that payload being successfully executed 344 00:11:58,160 --> 00:12:00,000 on the console too. So that's an update 345 00:12:00,000 --> 00:12:02,000 there from NASI. This is using just 346 00:12:02,000 --> 00:12:04,560 regular YouTube jailbreak I believe uh 347 00:12:04,560 --> 00:12:07,279 not implemented with the auto loader, 348 00:12:07,279 --> 00:12:09,200 but uh there may be some kind of update 349 00:12:09,200 --> 00:12:11,680 in the future that uh implements this 350 00:12:11,680 --> 00:12:14,399 with the autoloader version as well. And 351 00:12:14,399 --> 00:12:15,920 finally, we've seen a drastic 352 00:12:15,920 --> 00:12:18,800 improvement to FTP speeds with a new FTP 353 00:12:18,800 --> 00:12:21,680 payload from Dramore on the PS5. And 354 00:12:21,680 --> 00:12:23,440 it's also been updated to also support 355 00:12:23,440 --> 00:12:25,360 the PS4 as well. So, there's a PS4 356 00:12:25,360 --> 00:12:28,480 payload for PS4 and a PS5 payload. But 357 00:12:28,480 --> 00:12:31,120 obviously, the PS5 is definitely the 358 00:12:31,120 --> 00:12:33,120 console that needs the improved speed. 359 00:12:33,120 --> 00:12:34,560 So if we take a look at the normal 360 00:12:34,560 --> 00:12:38,160 transfer rates with FTP with ETA hen. So 361 00:12:38,160 --> 00:12:41,920 when I connect via ETA hen on port 1337 362 00:12:41,920 --> 00:12:43,760 and I try and transfer a package file 363 00:12:43,760 --> 00:12:46,880 from my computer to my PS5 into the data 364 00:12:46,880 --> 00:12:49,440 ETA hen folder you can see that this is 365 00:12:49,440 --> 00:12:52,560 a 24 GB file and when I transfer it the 366 00:12:52,560 --> 00:12:54,399 speed starts off high and then it just 367 00:12:54,399 --> 00:12:56,160 craters all the way down to about 5 368 00:12:56,160 --> 00:12:58,160 megabytes per second. And it's telling 369 00:12:58,160 --> 00:13:00,079 me it's going to take about 1 hour and 370 00:13:00,079 --> 00:13:02,639 17 minutes just to transfer a 24 GB 371 00:13:02,639 --> 00:13:04,880 file. And this is on a direct wired 372 00:13:04,880 --> 00:13:06,399 connection. So I should be getting much 373 00:13:06,399 --> 00:13:08,320 higher transfer rates. So this is the 374 00:13:08,320 --> 00:13:10,160 issue. Now sometimes the speeds are 375 00:13:10,160 --> 00:13:12,160 higher than this. They're about 20 to 30 376 00:13:12,160 --> 00:13:14,399 megabytes per second sometimes. Um but 377 00:13:14,399 --> 00:13:16,959 in this case quite often it seems to get 378 00:13:16,959 --> 00:13:19,360 capped at about 5 megabytes per second. 379 00:13:19,360 --> 00:13:21,440 So that is just obviously far too slow. 380 00:13:21,440 --> 00:13:23,519 So with this new payload, if we send 381 00:13:23,519 --> 00:13:25,920 this new FTP payload instead, and then 382 00:13:25,920 --> 00:13:27,920 we repeat the same test by copying the 383 00:13:27,920 --> 00:13:30,320 same 24 GB file over to the same 384 00:13:30,320 --> 00:13:32,720 location, you can see that the speed 385 00:13:32,720 --> 00:13:35,839 stays high at about 75 megabytes per 386 00:13:35,839 --> 00:13:37,519 second thereabouts. And we're getting 387 00:13:37,519 --> 00:13:39,279 much faster transfers rates, and it's 388 00:13:39,279 --> 00:13:40,720 saying it's only going to take about 5 389 00:13:40,720 --> 00:13:43,680 minutes now to transfer that 24 GB file. 390 00:13:43,680 --> 00:13:46,160 So much much faster than the FTP server 391 00:13:46,160 --> 00:13:48,160 built into EThen and some of the other 392 00:13:48,160 --> 00:13:50,399 FTP payloads that we've had in the past. 393 00:13:50,399 --> 00:13:52,480 Now, beyond that, another big advantage 394 00:13:52,480 --> 00:13:54,480 of this is that it does seem to be more 395 00:13:54,480 --> 00:13:56,880 stable with simultaneous transfers as 396 00:13:56,880 --> 00:13:58,320 well. So, when you're transferring 397 00:13:58,320 --> 00:14:00,399 folders that have hundreds or thousands 398 00:14:00,399 --> 00:14:02,320 of files in them, it can take a long 399 00:14:02,320 --> 00:14:04,160 time if it's just transferring like two 400 00:14:04,160 --> 00:14:06,480 at a time. Whereas in FileZilla, you can 401 00:14:06,480 --> 00:14:08,880 go into the FTP settings into the 402 00:14:08,880 --> 00:14:10,639 transfer settings and you can change the 403 00:14:10,639 --> 00:14:12,959 number of simultaneous connections up to 404 00:14:12,959 --> 00:14:15,120 I think 10 is the maximum. And then when 405 00:14:15,120 --> 00:14:16,720 you transfer a folder that has thousands 406 00:14:16,720 --> 00:14:18,800 of files in it, it will transfer them at 407 00:14:18,800 --> 00:14:21,360 10 files at a time, which is going to 408 00:14:21,360 --> 00:14:23,279 get them transferred a lot faster. It 409 00:14:23,279 --> 00:14:24,959 would normally cap out about five 410 00:14:24,959 --> 00:14:27,120 simultaneous transfers, whereas with 411 00:14:27,120 --> 00:14:28,880 this, we can go up to the maximum and 412 00:14:28,880 --> 00:14:30,880 get 10 transferred at a time, which as 413 00:14:30,880 --> 00:14:32,639 you can see is transferring thousands of 414 00:14:32,639 --> 00:14:35,279 files a lot faster. So, if you've got 415 00:14:35,279 --> 00:14:37,040 big folders with thousands of files on 416 00:14:37,040 --> 00:14:39,199 them, this can also help to get those 417 00:14:39,199 --> 00:14:40,639 transferred over. Although, it's still 418 00:14:40,639 --> 00:14:42,880 not recommended to use FTP to transfer 419 00:14:42,880 --> 00:14:44,720 your games. I would highly recommend 420 00:14:44,720 --> 00:14:47,040 using items flow to copy your game dumps 421 00:14:47,040 --> 00:14:49,600 from a USB to the internal storage or an 422 00:14:49,600 --> 00:14:52,000 internal M.2 drive instead. That's going 423 00:14:52,000 --> 00:14:53,199 to do it for this one. Just a quick 424 00:14:53,199 --> 00:14:54,480 update here. So, hope you guys enjoyed 425 00:14:54,480 --> 00:14:55,680 this one or found the information 426 00:14:55,680 --> 00:14:57,199 useful. If you did, please leave a like 427 00:14:57,199 --> 00:14:58,800 and subscribe. And as always, I'll 428 00:14:58,800 --> 00:15:03,320 hopefully see you guys in the next one.31208

Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.