PS4 {UPDATE] PS4 Jailbreak 7.50 /7.55 w/ Mira Support Released

UPDATE 7.55 w/ Mira Support Released

---

.Original Article (7.50) Not only did we just see a PS1 exploit released, the exploited PS4 firmware latter has extended a step to now firmware 7.50 has been officially exploited and released to the public as developer Sleirsgoevy has released the latest PS4 Jailbreak that has utilized the latest findings from TheFlow in his disclosed bug that has the potential to work upto 7.55 but is currently targeted for 7.50 for this release. TheFlow has tweeted several hints regarding 7.55 (tweet 1 / 2) but 7.55 is yet to be solved by other, @zecoxao provided some details and shared via twitter see below.

This is not a fully functional jailbreak yet as there is elements that are needed to be ported like the Mira/HEN and other Payload, so you should not update to this exploit from previous exploits yet. Let it mature, but if your on a PS4 on 7.50 or lower and missed out on previous exploits, Stay Tuned as this progresses,

​

About

• 
  Sleirsgoevy's Twitter (Release)
  

  mega.nz/file/hwEHDQSL#8o-KBeq_Tpd42zIkYt0mx0AduZaanG2hA7nom5AKqvk 7.50, expects payload on 9020/tcp. Applied patches: mmap, mprotect, syscall everywhere, kexec, delayed panics. Note: there is no Mira/HEN for 7.50 yet!

  
  via @zecoxao 's twitter (About 7.55 FW)
  

  the 7.50 exploit shared by @sleirsgoevy
  seems to reach all the way to the end in 7.55 but when listening to payloads, when you send one made by
  @_AlAzif , it immediately throws an out of memory error.

  
  Update(s):
  @_AlAzif
  

  Working on figuring out why payloads aren't working correctly with some people right now.

  
  Progress on 7.55
  
  @sleirsgoevy
  

  I can confirm that this exploit indeed works on 7.55 without any changes. Still no Mira/HEN though

  
  sleirsgoevy
  

  https://mega.nz/file/w0kFSACL#7dxYTiLqXg-n6hhfAMJQsXbGA8NCCRhfXfI8HXPoaOQ
  Added the dynlib_dlsym patch by @_AlAzif. Does not seem to fix payloads.

  
  AlAzif
  

  Utility payloads should be fixed, expect people to start posting them soon as the issues are known now. I'm waiting until I get them all tested before posting another pack/hosting them.

  
  sleirsgoevy
  

  https://mega.nz/folder/5xcRTQ7b#hykaQzVgVPLVWoLeswyNNw
  Mira for 7.55.
  https://mega.nz/file/MsMVDabb#Rt1dXdpRJMvG11RjUHd7gBHRxmV55iLngXH_mmNJWBU
  JB 7.55 with patches by AlAzif and ChendoChap.

Download: 750.zip
UPDATE 1:

ps4jb-750-755 .zip​

Update 2

Mira for 7.55.
JB 7.55 with patches by AlAzif and ChendoChap.​

Update 3 : (GoldHEN released)
https://twitter.com/Joonie86/status/1373703769259532291

Source: twitter.com/sleirsgoevy​

 

I never used online account, all i made is offline account.

 

I'm not sure then. I think the saves are in pfs when on the system in their default state, but then the saves you export (if you're activated) are incompatible with. those I know are in pfs, because they're in .bin format. saves you decrypt will probably be in .sav or .dat format. I've seen both of these formats. I'm not sure what to do now. if they were exported saves, you could just activate your account the same account id, then grab them that way. however, like this, I don't know. I never formatted the drive when I tested if saves worked backed up using sg and db payload, then ftp'd back. they did work, at least then. I think you might be screwed.

 

try just copying over the save data folders. you're not copying over the entire user folder, are you?

 

you might have to create some saves on the system first just to add them to the savedata.db (yes, there is one). then, you can try copying over the files. load the save, then immediately save again to update the database. I don't know if this will work though, but it may be your last hope.

 

I asked around about this. I don't think there's anything you can do. the ids have changed now that you've formatted, so it doesn't matter if the aid is all 0s (no aid) or it's the same system. there's now no way to retrieve the saves. I'm sorry about that. I know it works as long as you don't format.

 

I asked around about this. I don't think there's anything you can do. the ids have changed now that you've formatted, so it doesn't matter if the aid is all 0s (no aid) or it's the same system. there's now no way to retrieve the saves. I'm sorry about that. I know it works as long as you don't format.

Thanks bro for the confirmation, next time I will be careful.

 

you might ask @Joonie why you couldn't get account activator to work. I'm not sure what the problem was. I know that importing saves will work after a format. when I changed my aid to my original aid, I could decrypt imported saves with save mounter, but games would crash almost instantly. I think it might be due to installing them with an account that no longer existed. luckily, you don't have to open any games to decrypt the saves.

 

About 90% i'm using it for almost 2 weeks i got only two kernel panics.

but it really depends on the host, some are really problematic, i tried a lot of them and i recommend Leeful's hosts, they have the best success rate and features,

90% success rate is impressive. Makes me wanna think about updating to 7.55. I thought 7.55 had very low success rate.

 

90% success rate is impressive. Makes me wanna think about updating to 7.55. I thought 7.55 had very low success rate.

success rate will be different for you. I heard about some guy who's tried over 500 times, and it's only been successful 5 out of 500.

 

success rate will be different for you. I heard about some guy who's tried over 500 times, and it's only been successful 5 out of 500.

I never understood how it works, like PS3 hen, some times when i switch from CFW to HEN, i get a very low success rate, one day i spent 45 minutes ( exploit failed, system rebooting and etc) just to install it, other times i get it on the first try and never get a reboot.

 

from my understand, the ps4 exploits are race attacks like the early wii u exploits. if it fails to make the patches to the ram quickly enough, the system kernel panics. that's why it's so frustrating.

 

like the wii u, everyone has their own little style when it comes to increases success rate. I think the one going on the ps4 is to open playroom. on the wii u, it was to open and close curtains in the browser. I don't know if either really affected/affects success.

 

the success rate for the wii u, at least with 5.5.1, got up to about 99%, so it's possible probably for the ps4 as well. 100% might be impossible and unrealistic.

 

I didn't notice that night host has an option of restoring data back just like data backup but even that restore didn't work

 

I'm sorry to hear that. I'd say hold on to those saves. you may be able to use them again some day. I know that despite both being in .bin format, those saves are not compatible with save wizard (someone tested it with one of my saves). tbh, I don't know about you, but I don't even play my ps4, just use it to dump and test stuff. I have all of my saves intact on another account after my original was banned on the ps3. I haven't made any progress in any of them. and, that's like years worth of time.

 

I heard the problem may be related to user id on top of account id and system id. I know that that changes when formatting the drive. my original was like 10000001 and 10000000, but now my only account is a random bunch of letters and numbers. I formatted the drive on a sata station to remove any xregistry like file, so I don't know how that user id is derived. on the ps3, they go in order. and, on a NOR system, they start over if you format on the pc.

 

I plugged the old hard drive back into my system and everything is there like save data etc etc and i can continue from where I left off but still I don't want to use current hard drive because it's only 500gb.
I just bought another ps4 with 6.72 firmware. Can i just transfer data from 7.55 ps4 to 6.72 ps4 using ethernet cable? I guess i won't loose any save data.
@pinky

 

Hi all! I have interesting case with latest ps4 pro model CUH-7202B and perhaps it might help to write a better exploit!!! Here is the detailed actions and results:

I started jailbreaking with gamerhack exploit. The firmware was 7.51. The console was able to jailbreak about 3 or 4 times quite well, and after all I stacked on the "soft reboot" - the final step when console reboots in jailbreak mode. During the "soft reboot" I was able to hear that HDD stops (like power cut off) but console is still runs, and automatically reboots with checking disk and nothing – no jailbreak. In some cases - console during "soft reboot" just shuts down, and even doesn't power up itself, only once I turn on manually (I need to press power button twice! - Like the console comes from some kind of issue) – and then console again runs with disk check.

Then I update console to 7.55 firmware, thinking it might be due to bad firmware – and the same situation, (2-3 times jailbreak works) like an internal timer, so I could not pass the "soft reboot" stage.

I swapped the console with exactly the same model with base firmware 7.50, and again the same problem, after upgrade to 7.55 (which felt more stable)– again a few times was able to jailbreak and then stacked on "soft reboot" with the same symptoms.

Then I was able to pass soft reboot with the darkmoddervc hosting. Like without reboot I was able just once jailbreak the system, and again stacked after restarting the console. After all I tried many combination and finally did the history blocker with darkmoddervc and then I instantly noticed the message – clients are ready… so I did the exploits straight it and again jailbreak worked.

After that one successful jailbreak darkmoddervc eventually stucks on "running webkit…" message with 50% or 100% progress bar, the gamerhack – tried everything, even running disabling updates – after "found validating message – just going into soft reboot with complete shutdown.

After few reboots darkmoddervc was able get into main menu, but after running MIRA from there - resulted just getting a message - Ready for clients and an instant simple shutdown.

Next reboot - I ran again darkmoddervc - and then started HEN - all instantly worked.

It feels like I am always experiencing new behaviour, or is it raw exploit?

Bottom line - the latest pro model (could be due to with MIRA 7.5x jailbreak) doesn't like soft reboot at all !!!!! - practically always lead to complete shutdown with manual power up after all and from there always HDD integrity check and no jailbreak upon that reboot.

Does anyone with the latest ps4 pro model having similar issues? Please let me know! Any ideas, or is it due to some kind of hardware tricks from SONY in this model?

Hopefully this can be eventually solved.

 

I plugged the old hard drive back into my system and everything is there like save data etc etc and i can continue from where I left off but still I don't want to use current hard drive because it's only 500gb.
I just bought another ps4 with 6.72 firmware. Can i just transfer data from 7.55 ps4 to 6.72 ps4 using ethernet cable? I guess i won't loose any save data.
@pinky

I thought the data transfer required the latest firmware and both systems to be on it. I could be wrong. I think it's at least like that with the switch and wii u (have to be online too, I think).

 

Hi all! I have interesting case with latest ps4 pro model CUH-7202B and perhaps it might help to write a better exploit!!! Here is the detailed actions and results:

I started jailbreaking with gamerhack exploit. The firmware was 7.51. The console was able to jailbreak about 3 or 4 times quite well, and after all I stacked on the "soft reboot" - the final step when console reboots in jailbreak mode. During the "soft reboot" I was able to hear that HDD stops (like power cut off) but console is still runs, and automatically reboots with checking disk and nothing – no jailbreak. In some cases - console during "soft reboot" just shuts down, and even doesn't power up itself, only once I turn on manually (I need to press power button twice! - Like the console comes from some kind of issue) – and then console again runs with disk check.

Then I update console to 7.55 firmware, thinking it might be due to bad firmware – and the same situation, (2-3 times jailbreak works) like an internal timer, so I could not pass the "soft reboot" stage.

I swapped the console with exactly the same model with base firmware 7.50, and again the same problem, after upgrade to 7.55 (which felt more stable)– again a few times was able to jailbreak and then stacked on "soft reboot" with the same symptoms.

Then I was able to pass soft reboot with the darkmoddervc hosting. Like without reboot I was able just once jailbreak the system, and again stacked after restarting the console. After all I tried many combination and finally did the history blocker with darkmoddervc and then I instantly noticed the message – clients are ready… so I did the exploits straight it and again jailbreak worked.

After that one successful jailbreak darkmoddervc eventually stucks on "running webkit…" message with 50% or 100% progress bar, the gamerhack – tried everything, even running disabling updates – after "found validating message – just going into soft reboot with complete shutdown.

After few reboots darkmoddervc was able get into main menu, but after running MIRA from there - resulted just getting a message - Ready for clients and an instant simple shutdown.

Next reboot - I ran again darkmoddervc - and then started HEN - all instantly worked.

It feels like I am always experiencing new behaviour, or is it raw exploit?

Bottom line - the latest pro model (could be due to with MIRA 7.5x jailbreak) doesn't like soft reboot at all !!!!! - practically always lead to complete shutdown with manual power up after all and from there always HDD integrity check and no jailbreak upon that reboot.

Does anyone with the latest ps4 pro model having similar issues? Please let me know! Any ideas, or is it due to some kind of hardware tricks from SONY in this model?

Hopefully this can be eventually solved.

Your problems with bad shutdown, need for full cycle manual restart, HDD clicking noise in bad shutdown etc etc are know issues with PS4 Kernel panics in JB 6.72 and above. There is no permanent fix to these problems.

I read somewhere that PS4 Pro has lesser problems compared to base models. But as @pinky said that its not necessarily true.

I will stay on 6.72 for now.