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 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).

Yeah bro i also read it some where that both systems has to be online

 

probably won't transfer over fake pkg games either, even if it were possible. I know that the 3ds and wii u will not transfer over fake tickets if you do a system transfer. I don't know if there's ever been a way around it.

 

I tried to DB restore on my 6.72 ps4 using usb but it doesn't work either but the main issue is that there are some games already installed on that 6.72 ps4 and they disappear from the menu but when I checked storage it shows 390gb/450,it means games are in storage but not showing after DB restore.. I also checked through ps4xplorer app on ps4 but i don't know where to look for games because i didn't see any specific folder for games.

 

when games are stored on the hdd, they're in user/app. when they're decrypted (i.e. running), they go in mnt/sandbox/pfsmnt. the reason the games aren't appearing is that they're fake pkgs. the only way to get them to appear is to use the python script to fix the database. I think you use it, then sign out of your profile, then sign back in, and they'll be back. I've never used it though, so that's based on memory. you should keep a backup of your app.db (system_data/priv/mms).

 

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.

Thanks for your reply. So you are staying on 6.72 means in future will you consider to move for higher FW? And should we even expect any significant improvements in jailbreak?

Could you also clarify the full shutdown procedure? Like - power options->power off->(additional steps like wait for some time and possible unplug power)-> then manual push power? is there any difference between shutdown and reboot?

could you name more or less stable hosts and procedures for 7.55 firmware?

thanks!

 

Bad shutdown - Typically happens once JB fails & you get message to restart PS4 & try again. You will get sudden shutdown with HDD clicking noise. Sometimes you will get no message of JB failure & go into instant shutdown. Sometimes you get JB success message but as soon as you launch MIRA, you will have instant shutdown.

To restart PS4, you can do two things. Either hold PS4 power button for few seconds and two beeps and go to rebuild system, your controller may become non responsive while doing that & you may need to hardwire your controller. Then PS4 will start after another restart.

Or you should turn off the main power / remove PS4 power cable. Then plug back in after few seconds. Then start your PS4 and PS4 will automatically go into rebuild database. No need for hard wiring your controller with PS4.

 

it's suggested you immediately restart the system (again) after it it checks the hdd for errors, once it gets back to the home menu. the reason is that the system becomes sluggish for a bit. it's also recommended to wait a couple minutes before deploying hen or a kp then or coming out of rest mode is more likely. the second recommendation is whenever you're deploying hen.

 

I am happ with the 6. 72 jailbreak because it's almost 99% stable but the only issue is that some games not working even after installing backport for some games like Mafia Definitive and Avengers. I installed spiderman miles morale backport and it's working fine.

 

I don't know what you mean by games not working? an error? I have yet to encounter a game that didn't work.

 

CE-4050 something like that.

 

ce stands for common error. the number can be looked up on psdevwiki's ps4 error codes, but you'll need the complete one. it sounds like the error when a game requiring higher firmware is run without a backport (think it starts with a 4). check here for the game: https://defaultdnb.github.io/ if it says est, it means it's estimated based on when the game came out compared to when the last firmware beforehand came out; if it says ofw, it's been verified. almost all games up to the end of 2020 should be playable.

 

Hi everyone. I'm new to the forum and would like to share my personal experience with jailbreaking PS4.
Actually I've got two PS4 consoles namely Fat on 6.72 and PRO on 7.55. Basically some time ago I upgraded Fat from 5.05 to 6.72 and really regret it. The rate of JB success dropped perhaps not dramatically but notably. So I will stick with 6.72 for now. As for PRO. I bought it last year, early spring since I thought that PS4 scene was dead at that point and wanted desperately to play more recent game then. Unfortunately there was a breakthrough in the scene with 6.72 exploit which was soon followed by 7.02 and the rest you know. My PS PRO was as far as I recall on 7.50 on the day I bought it and was upgraded with new patches for the games with 7.51. Now I wanted to give a try with new 7.5x exploit but my feelings are a mixture of hope and frustration. I upgraded 7.51 to 7.55 but the success rate is really slow and it has nothing to do with a host I use. It differs from day to day. One time after some 'out of memory' notification I have ratio like 1 kernel panic\one JB success, the other day I have one 'OOM' note and JB with no KP. After three or four days in a row with similar jailbreaking success out of a sudden a I have 3-5 KP and no JB which as a side note takes me an hour or more. I'm not an avid player. I just play 2-3 hours daily or sometimes I don't use console for a week or so. That's even more frustrating when you think of playing a game and how long it may take to finally succeed with JB.
I used the playroom trick (if you know what I meant) but it also stopped having an influence on the ratio of a successful JB soon. I used lots of hosts. Some seemed to be more effective in JB but it was only on the first try or then again I had lots of KPs which are the most frustrating and off-putting part of the newest JB era. So my feeling is that the PS4 hacking scene reached the ceiling and with every new OFW it's even harder to proceed further. So to put it right my my experience with 7.55 exploit is really bad and I'm not even considering jailbreaking PS5 which I sooner or later gonna buy.

 

they're working on making 7.5x as stable as 5.05. they've mentioned that. I don't normally play my ps4, just use it for dumping things and testing. I can understand about it being frustrating, especially on later firmware. some people have a lot of success while others can't get it to work ever. they're not doing anything wrong, it's just the nature of the exploit, which is really a system by system basis on how well it works.

on the wii u, we had race attacks as well, which would sometimes result in "race attack failed" requireing a power off, because I think the system would freeze. you wouldn't have the dreaded kp and checking of the hdd luckily. anyway, the 5.5.1 exploit got up to 99% or so success rate, so it's possible, but 100% success rate is probably unrealistic. there are too many factors that can cause the race attack to fail. it sucks, I know, but the newer consoles are becoming harder to hack. I plan to buy a ps5 as well some day (once it's smaller hopefully), but I don't plan to hack it. I'm hoping to use the same account that I use on the ps3 if I can ever get the damn account to work with adding funds. that has nothing to do with the ps3 as the online shop is just ps4 and ps5 stuff. the ps3 stuff can only be bought on the system itself, so it's really starting to piss me off.

 

With backporting in majority of new titles, you don't need to upgrade to new firmwares. ok some games cannot be backported but that is small downside on staying in low firmware.

 

@pinky. Thanks for the response. I didn't know that devs are working on improving 7.55 exploit. On the contrary here and there I came across comments they are not interested in doing that for now. That is comforting piece of news. Personally I don't follow the tweeter discussions in the scene; truth be told I can't figure out much of it. This is why I make my own research on forums, sharing experiences, looking for some support or a piece of advice. Perhaps the fault is on my side and I keep doing something wrong or perhaps this is the console model which is not responsive to JB. I know quite many people use JB not for playing games and this the freedom of activities it gives to a user. All the more it's frustrating when it literally takes you hours to set the system right. By no means I'm criticizing or blaming anyone for unstable and creepy exploit. this is what it is and as I wrote before with every generation it's getting harder and harder. The XboxOne scene didn't have that much luck at all.
As for the wii u. I used something like Loadiine method ( don't know if I spell it correct) but yes it was a total crap until I had haxchii installed and life changed into a bright side.

 

Whats up with this transfer stuff I don't understand, i can't transfer games on external drive even on 6.72 firmware and this error came up after it completed installation..

 

I don't see that error on psdevwiki, but the error is close to one involving the external hdd, so I think the external hdd is the problem in some way.

 

I tiried on 3 different hard drives.

 

could have something to do with it being a fake pkg. I know that the system doesn't normally recognize fake pkgs, so it will ignore them when rebuilding the database.

 

Just to all that like me do not realise why GoldHEN is not working when we resume from "Rest Mode" when was announced that it work... it is because in the "Power Save Setting", property "Keep Application Suspended", GoldHEN will remain active after resume from ''Rest Mode". The main idea is that jailbreak is memory-related and it keeps in PS4 memory. That's why we need this setting to hold all memory structures alive and do not clean them when we enter in rest mode.
all explained here in "How To Keep GoldHEN After Rest Mode" .