Ps4 slim hdd mounting problem

[Lord_Kater]

Hello there! As the titel states I am looking for help.
I am running Debian and using cryptmount. Actually I tryed 2 different PS4 systems before and they worked like a charm. (both normal fat ones)
This time I have a PS4 Slim with the model 2216A and it doesn't work.
I dumped the NOR several times by hardware like always. This time it was a "8-WSON chip" that got dumped. Size seems perfect. Python script creates EAP Key file. I also unpacked the sflash0.bin and everything seemed in correct.

Python script:

C:\PS4>python hdd_scriptv2.py​

[DEBUG] e5e5e501​

[DEBUG] 9efc8d9dd42597376edd4d827db96b84​

[DEBUG] LEN 60 | f20c55b5700c355aef583722de5a99550c6b9cb0d228f5fed3aa4d680b9604e8e2316a4b56d27fd78da82bac276fdb0db028f32aac6d61ba9a428a337ab2dead9efc8d9dd42597376edd4d827db96b84f210d36ab1f32db3c98dd0372583e684​

[DEBUG] 00805006​

('XTS data key:', '96D27F425BFADDF59E0D9318353864C6')​

('XTS tweak key:', '6A4C20B0CA0916542B246E5382F8FF0D')​

I was wondering if the whole process is a bit different on a PS4 slim or with a "8-WSON chip"
I tryed hexediting the keyfile several times.
Since I used the script v2 I thought this wasn't necessary. But typed everything reverse. Tryed typing every single line reverse. Typed backwards. Maybe I did a mistake somehow.

Cmtab:

user { dev=/dev/sdh27 -- (it's the biggest partition listed with 400+GB)​

dir=/home/imager/ps4/user​

flags=user,nofsck​

fstype=ufs mountoptions=ro,noatime,noexec,ufstype=ufs2​

cipher=aes-xts-plain64​

ivoffset=111669149696 -- (of cause the offset because model 2xxx+, also tryed without offset anyway)​

keyfile=/home/eap_key.bin -- (renamed it to eap_key.bin)​

keyformat=raw }​

The whole process worked with former ps4 fat consoles without editing the key file.

​

Error Code on Linux with ps4 slim HDD:

​

"wrong fs type, bad option, bad superblock on /dev/mapper/user, missing codepage or helper program, or other error."​

But let me please know if I missed a step somehow.

 

[HerrZecke]

Hi, I've registered an account for a sole purpose of this answer/digging out this thread.
I had a similar problem with PS4 pro, it seems that all python scripts that extract the key file are buggy (wasted two days debugging that).

Basically if you enable 'use_new_blob = True' the correct blob gets overwritten around line 96:

eap_hdd_key_blob = b'SCE_EAP_HDD__KEY' + \
     bytes.fromhex('BB6CD66DDC671FAC3664F7BF5049BAA8C4687904BC31CF4F2F4E9F89FA458793811745E7C7E80D460FAF2326550BD7E4D2A0A0D9729DE5D2117D70676F1D55748DC17CDF29C86A855F2AE9A1AD3E915F0000000000000000000000000000000000000000000000000000000000000000')

If you comment out that line and enable new blob you should get the correct key.

It seems that the key that should work for you is:

XTS data key: ff66abec92a977b58b24780dd60ab269
XTS tweak key: e29429f43e3c50b22ef2c640438f5c85

So I hope you still have the console/HDD and I'm attaching the correct (hopefully) HDD key

 

[chipdouglas]

i, came across this thread in hopes you can help. ps4 slim CUH-2015A. 5.05 FW

mid game, console crashed. happens, reboot, launch hen, crash. stable until i launch hen, and then it crashes

i fear of it being a hdd on it's way out, i immediately hooked it up to clone to another hdd. first used active @, too slow, then just did a straight dd copy (honestly not even sure this method works)

put potentially failing hdd (ps4-hd) back into machine, wont boot. no rebuild options, nothing, just re-init

put cloned disk in (new-sd), same. to rule out machine, reloaded 5.05 on new drive, system working perfect

hdsentinel read surface test on ps4-hd, not a single bad block. wondering if active @ did some flag or something to it, not sure

i'm balls deep in my game, and want to attempt to retrieve my save

if i'm reading this post correctly, i should be able to get some form of encryption key, mount on my linux server, and potentially retrieve my game saves?

i'm happy to start my search on this topic, but any shortcuts you can help with would be greatly appreciated

edit: so this lead me down the path to get the sflash0, retrieve the eap key, and then mount the drive, however it appears that still may not be enough to move old saves to a new hdd

 

[HerrZecke]

(...)
i'm happy to start my search on this topic, but any shortcuts you can help with would be greatly appreciated

edit: so this lead me down the path to get the sflash0, retrieve the eap key, and then mount the drive, however it appears that still may not be enough to move old saves to a new hdd

For some reason SPAMbot blocks my answer, so here's image of it...

EDIT: I've tried the above approach and it seems to be missing something.
- saves on USB drive are not detectable
- when I've manually copied the saves over FTP I got 'db corrupted' system error.
Next idea: copy saves and manually update saves DB...

EDIT2: Wasted another day tinkering with that. It doesn't seem to be that simple. Feel free to try but there's some important piece of puzzle that I'm missing here.