sleirsgoevy/ps4jb

Unstable

Closed this issue ยท 12 comments

Still unstable ๐Ÿ˜‘

Still unstable ๐Ÿ˜‘

Instead of complaining about a instability give more details about your crashes and maybe someone would help you. Btw, in my case, last updates made the exploit much much much stable than before and I hadn't any more KP tbh.

I totally agree with @javierilloqg
When you say 'still unstable' do you mean it is unstable in the amout of times you have to run it to get it to work or that it is unstable after it has loaded and you are using your PS4?

Its crashing when loading exploit and same time crashing during mira load

And it crash when restarting ps4

Make sure you have pulled the lastest version of the exploit or try to host it locally in a different way. I use the last updated version and no troubles loading the exploit and any crashes post-exploitation.

It's the latest version and I host it locally

Are you 100% sure? With the latests update the jailbreak can still crash but i didn't see any crashes on mira loading

Hey guys, im sorry to ask this. Im really lost and new to github. Where can i find here the link address of sleirsgoevy? Been herefor days now and reading updates but i cant seemed to find the address. Hope someone can help me.

Are you 100% sure? With the latests update the jailbreak can still crash but i didn't see any crashes on mira loading

Yes I am sure

Are you 100% sure? With the latests update the jailbreak can still crash but i didn't see any crashes on mira loading

Yes I am sure

Sometimes it works like 3 times in a row, but then there are times when jailbreaking process just abruptly shuts down the ps4 (like a loss of power). It's noticeably better than first version, but still i wouldn't call it stable (yet).

p.s. @sleirsgoevy thanks for your work.

Are you 100% sure? With the latests update the jailbreak can still crash but i didn't see any crashes on mira loading

Yes I am sure

Everytime you get a crash or KP, restart the PS4, then shut it down properly through the power menu and then, after powering it on try to launch the exploit again.