Category PS4 CFW and Hacks       Thread starter PSXHAX       Start date May 2, 2019 at 5:47 AM       11,066       31            
Status
Not open for further replies.
Following fail0verflow's PS4 Crashdumps / Kernel Dumping and PS4 Aux Hax Documentation alongside his recent PS4 Sflash0 Pack Tool, PlayStation 4 developer @SocraticBliss made available a PS4 Crash Dump Decryptor Python Script for scene devs on Twitter today.

Download: ps4_crash_dump_decryptor.py / ps4_mono_to_il.py (PS4 MONO binaries to IL MONO binaries - updated script to work with the PS4's .dll.sprx and .exe.sprx files to turn them into .dll and .exe to be inspected with something like dnSpy)

From the Tweets below, here's what he had to say on it: "Still tweaking this somewhat, but decided to take a swing at fail0verflow's PS4 Crash Dump Decryptor script (since at this point its fairly outdated), enjoy!

Thanks goes out to notzecoxao, CelesteBlue123, and most of all fail0verflow! :)"

ps4_crash_dump_decryptor.py
Code:
#!/usr/bin/env python
'''

Crash Dump Decryptor by SocraticBliss (R)

Thanks to...
# Team FailOverflow
# CelesteBlue
# zecoxao

1) Replace  AES KEY # with the actual key
2) Replace HMAC KEY # with the actual key
3) Have orbiscore-systemcrash.orbisstate in the same directory
4) python ps4_crash_dump_decryptor.py

'''

from binascii import unhexlify as uhx, hexlify as hx
from Crypto.Cipher import AES
from Crypto.Hash import HMAC, SHA256
import struct
import sys

class Header:
    def __init__(self, f):
        __slots__ = ('VERSION', 'OPEN_PSID', 'PADDING_1', 'PADDING_2',
                     'UNKNOWN', 'STATE', 'DATA_LEN', 'PADDING_3', 'DATA_HMAC')

        # Secure Header
        self.VERSION   = struct.unpack('<I', f.read(4))[0]
        self.PSID_ENC  = struct.unpack('<16s', f.read(16))[0]
        self.PADDING_1 = struct.unpack('<I13Q', f.read(108))[0]
   
        # Padding
        self.PADDING_2 = struct.unpack('<4Q', f.read(32))[0]
   
        # Final Header
        self.UNKNOWN   = struct.unpack('<2Q', f.read(16))[0]
        self.STATE     = struct.unpack('<Q', f.read(8))[0]
        self.DATA_LEN  = struct.unpack('<Q', f.read(8))[0]
        self.PADDING_3 = struct.unpack('<2Q', f.read(16))[0]
        self.DATA_HMAC = struct.unpack('<4Q', f.read(32))[0]

KEYS = [
    ['',''],
    ['AES KEY 1','HMAC KEY 1'], # 1.01
    ['AES KEY 2','HMAC KEY 2'], # 3.55
    ['AES KEY 3','HMAC KEY 3'], # 4.05
    ['AES KEY 4','HMAC KEY 4'], # 4.07
]

def aes_ecb_encrypt(key, data):
    return AES.new(uhx(key), AES.MODE_ECB).encrypt(data)

def aes_ecb_decrypt(key, data):
    return AES.new(uhx(key), AES.MODE_ECB).decrypt(data)

def hmac_sha256(key, data):
    return HMAC.new(uhx(key), msg = data, digestmod = SHA256).digest()

# PROGRAM START
def main (argc, argv):

    # 1) Read the Header
    with open('orbiscore-systemcrash.orbisstate', 'rb') as f:
        ps = Header(f)
   
        KD = KEYS[ps.VERSION][0]
        KC = KEYS[ps.VERSION][1]
        print('\nEncrypted PSID: %s' % hx(ps.PSID_ENC).upper())
   
        PSID_DEC = aes_ecb_decrypt(KD, ps.PSID_ENC)
        print('\nPSID: %s' % hx(PSID_DEC).upper())
        
        # HMAC DIGEST
        DIGEST = hmac_sha256(KC, ps.PSID_ENC)
        print('HASH: %s' % hx(DIGEST).upper())
           
        KD = DIGEST[0x10:]
        KC = DIGEST[:0x10]
          
        print('\nAES : %s' % hx(KC).upper())
        print('HMAC: %s' % hx(KD).upper())
   
        # 2) Dump Starts Here
        f.seek(0x4000)
        DATA_ENC = f.read()

    # 3) Utilize the proper key set to decrypt the data
    IV = '0000000000000000'
    DATA = AES.new(KD, AES.MODE_CBC, IV).decrypt(DATA_ENC)

    # 4) Save the decrypted data
    with open('debug.bin', 'wb') as f:
        f.write(DATA)
   
    print('\nSaved to debug.bin')

if __name__=='__main__':
    sys.exit(main(len(sys.argv), sys.argv))
Crash Dump KeySeed
Code:
kd, kc
KEYS = [
    ['',''],
    [b'8F86DDEDCBF24A44EB6C30607AA26F76', b'4125715AAB8B78E569F512E65CA62DD3'], # 1.01-3.15
    [b'63AEF79DC49969FD8997B2F60DB65F81', b'1800A5DE2D0F0652FA5602FFADD440AA'], # 3.50-3.70
    [b'05205507B7A154E08A7A38B1897563FB', b'AD334D142EAF8B9438DB00D1D0BFF357'], # 4.00-4.05
    [b'04C1A0961BBB0CB2140361B0956AAABA', b'052D2FF3014FB38CAAF6898CB899982A'], # 4.06-4.07 (to test)
]
Sealed Key Values

Keyset 1

AES-CBC-128
Key = B5DAEFFF39E6D90ECA7DC5B029A8153E

SHA-256-HMAC
Hash = 8707960A53468D6C843B3DC9624E22AF

Keyset 2
AES-CBC-128
Key = EC0D347E2A7657471F1FC33E9E916FD4

SHA-256-HMAC
Hash = A6D6583D3217E87D9BE9BCFC4436BE4F

Keyset 3
AES-CBC-128
Key = 51D8BFB4E387FB4120F081FE33E4BE9A

SHA-256-HMAC
Hash = FFF9BDEA803B14824C61850EBB084EE9

Keyset 4
AES-CBC-128
Key = 346B5D231332AC428A44A708B1138F6D

SHA-256-HMAC
Hash = 5DC6B8D1A3A0741852A7D44268714824

Dumped with getSealedKeySecret on 5.05

PS4 Crash Dump Decryptor Python Script via SocraticBliss.jpg
 
:idea: Reminder: Those without a Verified Badge yet on Discord to access the private areas we recommend Joining Us! Why? The waiting process takes a week for new Members, and there's a lot we're unable to share on public forums including the latest PS4 PKG Games. 🏴‍☠️

Comments

Status
Not open for further replies.

SSShowmik

Senior Member
Contributor
Those who are giving up and updating had already been late to to join the bandwagon as scene members constantly mentioned to stay on lowest firmware possible.

You know you who you are, you did listen to them when they told you to stop updating, and now you expect them to listen to your petty jailbreak requests. The scene isnt dead. You're not just a part of it.
 
:idea: Reminder: Those without a Verified Badge yet on Discord to access the private areas we recommend Joining Us! Why? The waiting process takes a week for new Members, and there's a lot we're unable to share on public forums including the latest PS4 PKG Games. 🏴‍☠️

fspring

Member
Contributor
Verified
I still got mine running on 5.0.5 and I actually thought about updating too because of some recent games that I'd love to play. Instead I bought some of my all-time-favs on disc an play them through again...
Certainly another kernel exploit will be released in this year ...
 

FalconIndestro

Member
Contributor
I don't know why some people still complain about "no new exploits"!!

You do understand that 5.05 or even lower exploited firmwares have all the tools for the homebrew scene. Higher than that is just about backups. I really don't know about those who earn money with backups (either with some hardware (like modchips) or just sells of modified systems/accounts/...) didn't paid yet some "high skill" folks to exploit the system for some 0day exploit lol... Maybe it can't be possible, or if it is just like they tried on PS3 days but failed, because it got released for everyone after.

The PS4 scene isn't dead for homebrew, but "dead" for backups (meaning newer games backs). They are different things.

Even if in some countries the games might cost a lot, i bet the users can save some money to buy, trade or whatever second hand games (or even share with a close friend/family member, like i do for PS4/X1 with my cousin, we buy all the digital purchases 50/50).

You don't need to buy a game right after its release you can wait a while. There's lots of F2P games you can play online (if you have a internet connection lol) for PS4, cause for those you don't need a PLUS sub., like you need on X1, cause you can't play any game, even F2P without a GOLD sub. with it.

This only for the people that are bored or don't like the available backups for the existing higher public exploit (thats 5.05) or even don't like to use a PS4 with linux or other homebrew stuff.

I think if a new exploit pops up it will be after the new PS is released (next year maybe!?). Till then, wait or update. Not being general of course, cause some do enjoy the current exploits.

Me, for example, i do have more than one PS4 (bought some second hand with hardware problem and fix some) so i do enjoy the public exploits and do use the other(s) for newer games and online. If no new exploit gets to public, i don't mind.

This is just my personal opinion on this subject.
 

SpaceXX

Senior Member
Contributor
I made cheap PC for AAA games, enjoying a lot on window 10
thanks to Codex & CPY !!

on other hand my ps4 is only for exclusive & enjoying online too;
NO more waiting or no more warning !!!

so keep waiting 5.05 users, God knows when will u get kexploit for your system ?
 

wolfsstolz

Member
Contributor
The scene for PS4 and future consoles are dead I think too and devs will sell the exploits to Sony I think in future. It's hard to see but that's fact
 
Status
Not open for further replies.
Recent Articles
SpecterDev Shares Low-Level Details on Porting MUSL to PS4
Since the OpenOrbis PlayStation 4 Toolchain release and related guides on his YouTube Channel, PS4 scene developer @SpecterDev of SpecterDev.ca (Patreon) shared via Twitter a Blog Post detailing...
Sony's Days of Play 2020 Sale Offers Deals on Games and More
With Memorial Day weekend and the unofficial start of summer upon us things are heating up outside as well as in Sony's Days of Play 2020 sale with deals on PlayStation games, accessories, PS Now...
Super Console Wars 1.0 PS4 Homebrew Game PKG by Lapy & Acekone1!
A few weeks back we saw PS4-Xplorer File Manager Theme and Avatar Maker followed by a PS4-Xplorer 1.19 update, and today PlayStation 4 homebrew developer @Lapy returns via Twitter with designer...
Marvel's Iron Man PS VR Bundle & Free Marvel's Iron Man VR Demo
This July 3rd a new Marvel's Iron Man PS VR Bundle launches including the game itself, a PS Camera and two PS Move controllers alongside a free Marvel's Iron Man VR Demo available today for PS4...
Top