PS4 HDD reading

filename: /lib/modules/5.3.0-24-generic/kernel/fs/ufs/ufs.ko
license: GPL
alias: fs-ufs
srcversion: A731EE2A41A1EA06C39BC11
depends:
retpoline: Y
intree: Y
name: ufs
vermagic: 5.3.0-24-generic SMP mod_unload
sig_id: PKCS#7
signer: Build time autogenerated kernel key
sig_key: 37:BE:2D:4B:1D:D5:90:E9:EB:DD:1F:9B:10:21:1D:97:58:77:1C:1B
sig_hashalgo: sha512
signature: 2B:DE:F7:96:95:66:77:A9:2D:3E:6A:04:B3:C7:AA:13:50:89:F6:80:
76:68:D7:2B:2D:8E:AD:02:6D:B9:42:16:F2:3A:7F:ED:A9:C7:7D:48:
99:70:74:8B:DA:79:A1:88:B4:F3:D4:EE:08:37:6B:D8:26:00:1F:8C:
F2:FD:14:22:89:F3:34:01:AD:4C:75:C3:2C:C2:65:D6:92:AE:45:50:
FB:65:99:5B:1B:80:ED:C5:C3:C9:DE:0E:17:F7:C8:41:C8:4F:A1:D9:
84:8A:D2:76:47:74:F4:2A:ED:6B:1D:35:96:A4:39:DB:4C:5A:56:3B:
6E:8D:2F:D6:BD:9F:5F:40:3C:72:1A:6E:50:CC:04:BF:7E:C0:5A:78:
E0:3F:38:AF:ED:E9:66:BD:F7:DA:AE:22:D3:1B:E7:DF:97:7B:AA:5A:
3C:E3:AC:89:0A:A6:43:C4:EC:84:26:3D:3B:4D:62:53:8E:C8:DF:E9:
E7:53:06:42:13:02:F0:1B:14:E1:0A:4E:42:0A:11:C0:BC:26:DA:EA:
8F:A5:B9:D3:77:6F:A0:93:71:C9:FB:91:8F:28:2E:BC:3A:53:0B:36:
2E:CB:04:F5:D2:FF:F6:F0:0B:E8:C4:18:E8:2F:81:A0:47:3A:01:59:
91:38:0D:E7:C4:1E:77:06:4F:B8:4D:9B:5C:8E:22:62:CE:B5:93:E8:
DE:F5:D5:EF:1D:EC:64:9D:F5:55:A7:5D:96:84:D7:9A:F4:F6:0E:32:
58:60:B2:49:06:0F:A3:C1:F5:5A:D6:BB:86:73:42:E1:32:EA:EC:2C:
E5:3C:9D:D5:48:5B:2B:1B:33:A6:B4:FD:96:B2:7B:51:AB:22:88:0A:
3E:D4:81:71:4D:99:20:EF:6C:FA:E6:1C:7B:90:BE:D0:6E:14:90:C8:
4B:65:26:7A:53:A5:15:2D:89:5C:02:62:AC:A6:BB:21:75:1A:38:77:
09:6D:61:48:40:02:44:61:21:D3:1E:D9:3C:DD:D2:DA:DF:05:8D:24:
70:9C:49:20:48:9B:C1:25:39:DD:C4:AC:9E:70:76:16:34:FB:4B:83:
E4:D1:59:E4:CC:F9:43:DF:1A:F3:B9:7D:21:0C:C3:F2:05:38:27:74:
E9:1A:39:3A:11:1A:07:CC:9A:6C:79:F5:B7:35:BC:46:B5:99:4C:16:
B0:85:29:E3:85:0B:7E:03:20:77:5D:43:28:33:A7:88:54:B6:67:A2:
6B:7A:52:C3:F5:59:96:30:20:D1:BA:1B:54:E2:90:89:DB:9F:DB:0B:
6B:79:4E:4F:0A:D6:A4:47:22:B9:7C:D1:45:FB:B1:1A:45:49:8B:FB:
91:A9:33:5E:A4:01:50:97:EB:A3:DA:15
 
It seems this is the same version. I don't understand.

So maybe this will solve the mystery:
Code: 
sudo rmmod ufs (or ufs.ko, I dunno)
sudo insmod ~/ps4/ufs.ko
sudo lsmod | grep ufs

Ignore it, and follow the train. For me it is already loaded, so should works. :|
 
Berion said:
And file manager run as root?

So I gave up. Tomorrow I'll test it with PS3 and see.
Click to expand...

Yes file manager as root. When i click properties n a folder it says

Owner: root
folder access: create and delete files
file access: ---

Group: root
folder access: none
file access: ---

folder access: none
file access: ---

When i click properties on a file it says

Owner: root
Access: Read and Write

Group: root
Access Read-only

Access Read-only
folder access
file access
 
Berion said:
And file manager run as root?

So I gave up. Tomorrow I'll test it with PS3 and see.
Click to expand...
In my linux /boot/config-5.3.0-24-generic should i change anything here?

CONFIG_UFS_FS=m
# CONFIG_UFS_FS_WRITE is not set

I also noticed in the mounter I got this error as well STEP 3: Mounting
Choose WISELY:
1. Mount HDD came from none-IVmodel
2. Mount HDD came from IVmodel

1
mount: bad usage
 
Last edited:
When i click properties on (...)
Click to expand...
It only shows permissions on data, not how partition is mounted.
In my linux /boot/config-5.3.0-24-generic should i change anything here?
Click to expand...
Only if You want compile ufs.ko. ;)
Code: 
CONFIG_UFS_FS=m
CONFIG_UFS_FS_WRITE=y
mount: bad usage
Click to expand...
You cannot mount already mounted fs and/or mount to the same mount point two different.

Every time You want mount something from the script to try (for some reason :P) different option, You must first run Umount script to clean mnt, mappers and device constant.

And BTW, if You will choose wrong PS4 model, You will not decrypt partitions, because math will produce garbage. So also You will not able to mount them because garbage cannot be interpreted as filesystem. ;)
 
Last edited:
Berion said:
It only shows permissions on data, not how partition is mounted.

Only if You want compile ufs.ko. ;)
Code: 
CONFIG_UFS_FS=m
CONFIG_UFS_FS_WRITE=y

You cannot mount already mounted fs and/or mount to the same mount point two different.

Every time You want mount something from the script to try (for some reason :P) different option, You must first run Umount script to clean mnt, mappers and device constant.

And BTW, if You will choose wrong PS4 model, You will not decrypt partitions, because math will produce garbage. So also You will not able to mount them because garbage cannot be interpreted as filesystem. ;)
Click to expand...


I will not change anything in the config lol I will leave ufs write setting unset. It said bad usage even though it mounted it successfully just with no write permissions :'(

also I chose option 1 which is no iv model. I have base ps4 CUH10xxxx
 
PC way doesn't seem to be working so I may have to get a hacked ps4 just for the sake of writing to other ps4 hdd's :P Unless you(the script god) can come up with something haha
 
Replace in script: :)
Code: 
sudo mount -t ufs -o remount ufstype=ufs2,rw /dev/mapper/ps4hdd_27 ~/ps4/storage/27_user
by
Code: 
sudo mount -t ufs -o remount,ufstype=ufs2,rw /dev/mapper/ps4hdd_27 ~/ps4/storage/27_user

In other words, comma after remount and before ufstype, instead of blank space.
 
Berion said:
Replace in script: :)
Code: 
sudo mount -t ufs -o remount ufstype=ufs2,rw /dev/mapper/ps4hdd_27 ~/ps4/storage/27_user
by
Code: 
sudo mount -t ufs -o remount,ufstype=ufs2,rw /dev/mapper/ps4hdd_27 ~/ps4/storage/27_user

In other words, comma after remount and before ufstype, instead of blank space.
Click to expand...
I get off work in 3 hours I will test it then and get back to you :) Thank you!
 
Berion said:
@rj017 Updated scripts. Umounter now removing ufs module. Mounter remounting ufs with rw if find ufs.
Click to expand...

Hey! I finally got a chance to test and holy shit it worked first try and gave me write perms! :D On payday I'll pm you for your paypal :)

One more thing since you're a master at all this clearly lmao Are you able to make something to decrypt and re-encrypt trophy folders? Decrypt to modify trophy timestamps and then re-encrypt to put back onto the console?
 
Thanks for the QA tests. ^^ One tiny symbol and what difference can make. ;]

I'm a graphic artist and my Linux knowledge is really basic. All hacking like key retrieving, RE stuff to reveal algorithm used etc. are done by some serious people. As I said, I'm the only a Protemetheus who bringing fire from the Olimp.

To mess with trophies (and decrypt rest of partitions on HDD) You need hack SAMU (to get PFS key because all saves, trophies, games, dlc, patches etc. are closed in those containers). Which last possible was on fw 6.72. And even if You have it and dump bunch of other per console keys along with other keys, no one yet edit them, no one know the structure. For this You will probably wait many years I'm afraid.
 
Last edited:
You must log in or register to reply here.
Back
Top