Join Us and become a Member for a Verified Badge to access private areas with the latest PS4 PKGs.
PS4 Jailbreaking       Thread starter stooged       Start date Feb 28, 2018 at 9:28 AM       304      
Status
Not open for further replies.
Following my previous release, I put together an Android app to host the 4.55 exploit and payloads.

You have to setup a wifi hotspot with your phone/tablet and connect the PS4 to that hotspot or connect the phone/tablet to the same network the PS4 is on.

Then install the app and open it and at the top will be the address you need to connect to with the PS4.

Your device might ask you about installing an application from "unknown sources" this is ok to allow, it just means its not coming from Google Play.

You just select the payload you want to run in the app and then use the PS4 to goto the address that you see in the app.

To change the payload just select it in the app and then use the ps4 to revisit/refresh the address again.

you can add more payloads to the app you just plug your phone into your computer and copy any payload BIN file you like into the PS4_455_Payloads directory.

Right now the 4.55 exploit and hen payload are really unstable and you will have to try loading it again and again until the exploit works and payload injects properly.

You will get a lot of "There is not enough free system memory" errors, just select ok and keep trying


Once you fight it enough the payload will work and you will be able to install and play pkg games.

Download: Ps4_Serve2_v2_0.apk (1.8 MB - Changes)

Spoiler: Depreciated

Eye candy:

Android App to Host PS4 4.55 Exploit and Payloads by Stooged.png
 

Comments

@Koh23

The hosting method really has nothing to do with any of the results because its just a webserver so it could be pc host android or usb and its all the same.

Differences in the webkit exploit and hen versions would cause results to be different.

In 4.05 sometimes launching the webkit exploit would straight up cause a panic and others it would work fine.
So it could also be where the memory for the exploit is being allocated and if other parts of the memory are being effected.
 
@stooged can you help me? I am trying to use your app folowing your guide but i have a problem, if i use the hen exploit from the help file it works just fine but if use the enable browser exploit it messes up the ps4, what can i do to fix this?
 
Today I was able to verify that with this new update the ps4 really tends to hang after a while. Probably the problem is in the exploit itself, having no relation to this app.
 
@stooged got it.

I know that hosting method can't really have that much influence, but imagine 2 consoles, one right next to other. Same firmware, one is 500gb slim, other is 1tb fat. Slim works great if exploit is loaded via pc host, not great if same exploit (same version of hen) is loaded via android. Fat works great with android, bad via pc. Figure that.... Or maybr this is just a wierd link between hosting method-errors with no real reason or explanation
 
@Koh23
I know what you are saying but you need to understand how a webserver works.

a webserver is just a vessel to provide a location for say "index.html" to reside and when requested it is sent to a web browser.
the same index html file is sent to every browser, in this case the webserver does not compile or deconstruct or manipulate the index.html in any way.
they "can" modify it to put ads in etc but that's a different story.

we are not using php, all we are using is html and java script so the webserver in this instance does nothing but send the requested data to the browser.

maybe there is corruption in the data sent?
you can test that by taking the file that is sent from the server and received by the browser and hash check it and in my apps case they match.

the web browser is the interpreter and it takes the html and java script data and generates an output.

there has to be something more at play here because if both web servers are sending the same data without any change the web browser is receiving the same thing every time.
I have not checked the pc host to see if the data in and out is a perfect hash match but I would suspect it is a match.

it does leave the question on is there a difference between your fat and slim consoles, we know they have a different motherboard but is there anything else?.

and are you sure both exploits being sent through android and pc host identical? there might be a difference in the html or java script to start with.
 
Thanks
But 1.6 seems to be laggy sometimes in game's loading. Its random.
Specially in Drive Club, after 15 mins gameplay, Close application cant close the Game and you have to Restart your Console
 
ok I think I found the difference.

the payloads in pc host are not the payloads compiled by the authors of the payloads.
for instance the vortex hen payload from xVortex should be 8kb in size but in pc host its 1mb.

so for some reason there is 900+kb of extra data in the pchost payload and this will probably change around memory locations.
all of the xvortex payloads seem to have 1mb more than they should.

the exploit files are probably modified too, but there is your differences, the hen payloads between android and pchost are not the same because I used the 8kb one compiled by xvortex in the android app.

bigger.jpg

@iSCORPION

the only change in 1.6 was the userland.js rewrite by qwerty.
you think he did something that's causing problems and we have to revert to the old userland.js?
 
@stooged yes indeed.
Yesterday ive played MAFIA3 more than 4 hours. It freezed four times while loading to the last checkpoint (they killed me). then have to restart the Console.

And then in Drive Club after 15 min, Close application loop forever trying to close the game. Would you test with Drive Club and see if its there, seems to get back to old userland.js
 
@stooged thank you! Sorry for late reply, i needed some time to read and (try) to understood what you wrote. Sadly, can't say that i did fully.

What do you think, what is that 900kb difference in payloads? Simple requirement from operating sistem (android-win) or something else? I mean, that difference in size mean a lot lot more data in pc code, right? Is there difference in how payloads "do their stuff"?

Or to be paraniod, is there any chance that this "excess code" (let's call it that) can do some harmfull things....

Different code can explain lot of things, but i'm still fail to understand or even guess how come one payload work and other don't on specific ps, and on other ps one that worked on first, dont work, and vice versa. Basicly, differerence from fat to slim ain't that big or important to cause any compatibility issues.

Of course, i don't expect from you to think alot about this (or really do anything), this is not really important, just some curiosity that i wonder why is this happening....

Thank you for your time and will to help me in my thinking
 
Status
Not open for further replies.
Back
Top