PS4 HDD reading

Berion said:
But You must compile this module by yourself after kernel config changes to allow write. I saying this probably 5th time already. The problem not lie in way how this module is load but what this module can. And default build into Linux kernel cannot write into UFS2. That's the reason why we need our ufs fella, not default slow crippled one. :P
Click to expand...


Okay i thought that custom ko was already compiled i know next to nothing about linux so when you say compile myself it's like talking politics to a new born baby haha I will forget it and just grab a hacked ps4 to read without all the extra work to make it work on the pc.
 
Berion said:
It is compiled in some attachment for specific version of Ubuntu Remix. So if You have that ufs.ko, and that distribution, You can mount all shit with write permission.
Click to expand...


I have that ufs.ko downloaded and I also have the distribution it was built for. I loaded the module but didn't give me write permissions. And i know you're probably going to say I have to compile kernel or something right haha
 
Actually no, it should works then. ;]

Have You remount partitions?
Code: 
sudo mount -t ufs -o ufstype=ufs2,ro /dev/mapper/ps4hdd_27 ~/ps4/storage/27_user
sudo mount -t ufs -o remount ufstype=ufs2,rw /dev/mapper/ps4hdd_27 ~/ps4/storage/27_user
sudo mount -t ufs -o ufstype=ufs2,ro /dev/mapper/ps4hdd_29 ~/ps4/storage/29_eap_user
sudo mount -t ufs -o remount ufstype=ufs2,rw /dev/mapper/ps4hdd_27 ~/ps4/storage/29_eap_user
 
Last edited:
I see here two flaws. First You need mount it as ro, then remount it as rw (above there is example how, mapper names and mount point edit for Your needs, I just used those from my script, also put IVs if Your PS4 model needs them). And then, run filemanager as root because probably permissions in filesystem are set to root so ordinary user couldn't write it, only root uber chad. ;p
 
Berion said:
I see here two flaws. First You need mount it as ro, then remount it as rw (above there is example how, mapper names and mount point edit for Your needs, I just used those from my script, also put IVs if Your PS4 model needs them). And then, run filemanager as root because probably permissions in filesystem are set to root so ordinary user couldn't write it, only root uber chad. ;p
Click to expand...



I copied that code and saved it lol I used cryptmount so just mounted it and that's all. I assume in your code ps4_hdd27 would be replaced with sda27/sdb27. and 27_user would be my mount point?

What's the difference between user and eap_user?

I would only need the first two lines since I'd only be mounting 27
1. Install linux(ubuntu cinnamon)
2. load ufs.ko module as root
3. sudo cryptsetup create -c aes-xts-plain64 -d /home/username/ps4/eap_hdd_key user /dev/sda27 ls -la /dev/mapper (This one confuses me a bit and not sure if this is right. I don't have a ps4 pro or the later models so I not need the iv line.
4. sudo mount -t ufs -o ufstype=ufs2,ro /dev/mapper/sda27 ~/home/username/ps4/user
5. sudo mount -t ufs -o remount ufstype=ufs2,rw /dev/mapper/ps4hdd_27 ~/home/username/ps4/user
6. Run filemanager as root and go to the ps4 hdd's folder and write/read whatever then umount.
 
Ok, from start to end. :P

1. Drop "ufs.ko" to "/home/<user>/ps4/".
2. Now run terminal.
3. Type: cd ps4
4. chmod +x ufs.ko
5. sudo insmod ufs.ko
6. Drop "eap_key.bin" to "/home/<user>/ps4/keys/".
7. mkdir ~/ps4/storage/27_user
8. Create mapper for Your PS4 model from which HDD came from (chose one of them of course):
for non-IV model:
Code: 
sudo cryptsetup create -c aes-xts-plain64 -d ~/ps4/keys/eap_key.bin -s 256 ps4hdd_27 /dev/sdx27
for IV model:
Code: 
sudo cryptsetup create -c aes-xts-plain64 -d ~/ps4/keys/eap_key.bin -s 256 -p 111669149696 ps4hdd_27 /dev/sdx27
replace sdx by e.g sda if PS4 HDD is /dev/sda
9. Type both:
Code: 
sudo mount -t ufs -o ufstype=ufs2,ro /dev/mapper/ps4hdd_27 ~/ps4/storage/27_user
sudo mount -t ufs -o remount ufstype=ufs2,rw /dev/mapper/ps4hdd_27 ~/ps4/storage/27_user
10. Type sudo nemo (or nautilus if there is no Nemo in this distribution) and go to "home/<user>/ps4/storage/27_user/" and You should see PS4 HDD contents from partition no.27 and allowing to delete/rename/move etc.
11. If works, consider a donation. :P
12. If not, prepare PS4 for defenestration.
 
Last edited:
Berion said:
Ok, from start to end. :P

1. Drop "ufs.ko" to "/home/<user>/ps4/".
2. Now run terminal.
3. Type: cd ps4
4. chmod +x ufs.ko
5. sudo insmod ufs.ko
6. Drop "eap_key.bin" to "/home/<user>/ps4/keys/".
7. mkdir ~/ps4/storage/27_user
8. Create mapper for Your PS4 model from which HDD came from (chose one of them of course):
for non-IV model:
Code: 
sudo cryptsetup create -c aes-xts-plain64 -d ~/ps4/keys/eap_key.bin -s 256 ps4hdd_27 /dev/sdx27
for IV model:
Code: 
sudo cryptsetup create -c aes-xts-plain64 -d ~/ps4/keys/eap_key.bin -s 256 -p 111669149696 ps4hdd_27 /dev/sdx27
replace sdx by e.g sda if PS4 HDD is /dev/sda
9. Type both:
Code: 
sudo mount -t ufs -o ufstype=ufs2,ro /dev/mapper/ps4hdd_27 ~/ps4/storage/27_user
sudo mount -t ufs -o remount ufstype=ufs2,rw /dev/mapper/ps4hdd_27 ~/ps4/storage/27_user
10. Type sudo nemo (or nautilus if there is no Nemo in this distribution) and go to "home/<user>/ps4/storage/27_user/" and You should see PS4 HDD contents from partition no.27 and allowing to delete/rename/move etc.
11. If works, consider a donation. :P
12. If not, prepare PS4 for defenestration.
Click to expand...


Perfect thank you so much! I have noted it all down and will try sometime this week when I have time. I will definitely let you know if it works or not. Where do I go to donate lol
 
I'll find You. ;]

Oh and of course:
13. sudo umount -l ~/ps4/storage/27_user
14. sudo cryptsetup remove ps4hdd_27
 
PayPal, by sum which You thinking is worth it. Once it this PS4 stuff will work, send me a private message.
 
@rj017 I made all-in-one package. WIP-3.

1. Start from fresh boot on Ubuntu 19.10 Cinnamon Remix with default kernel (so e.g live session).
2. Unpack archive in home.
3. Put eap_key.bin inside keys dir.
4. Run "PS4 HDD Mounter v0.9c-RW-micro.sh"
5. Just follow the train CJ.
6. Open terminal and type sudo nemo (or sudo nautilus).
7. Enjoy write access to partition 27 alone.
8. Run "PS4 HDD Umounter v1.0.sh".

So I think, this is simpler. When prompt, type Your PS4 HDD device name (if it will be /dev/sda, then type /dev/sda) and when prompt, choose Your PS4 model (IV or none-IV).

If this will not work, it means I made mistake somewhere in the script... Because I'm written it blindly. In such case, go back to instructions from post no. 68+70.

//attachment removed, toolkit moved to site resource section
 
Last edited:
wow I had to try it immediately hahaha It seemed to open and function as intended however i got one error at the start

OK. I've found "ufs.ko".
ERROR. I couldn't load "ufs.ko".
ufs.ko is in the ps4 folder. Should i be doing this as root or no?
 
You cannot seen any error. If this failed, You will not get write support. :/ When root is needed, script will ask for a password. On live sessions are empty so just press enter in such case and should be ok.

Ok, what will happen if You do:
Code: 
sudo insmod ~/ps4/ufs.ko
sudo lsmod | grep ufs
 
Berion said:
You cannot seen any error. If this failed, You will not get write support. :/ When root is needed, script will ask for a password. On live sessions are empty so just press enter in such case and should be ok.

Ok, what will happen if You do:
Code: 
sudo insmod ~/ps4/ufs.ko
sudo lsmod | grep ufs
Click to expand...


insmod: ERROR: could not insert module /home/cinnamon-remix/ps4/ufs.ko: File exists

ufs 81920 0
 
Ok, so You probably inserted it before, not starting from fresh boot as I said in 1. in post no. 74. :P

And what says?
Code: 
modinfo ufs.ko
hostnamectl | grep "Operating System"
hostnamectl | grep "Kernel"
 
I just downloaded the iso and put in on my usb about 20 minutes ago lol I never booted this before :P Here are the returns;

modinfo: ERROR: Module ufs.ko not found.
Operating System: Ubuntu 19.10
Kernel: Linux 5.3.0-24-generic
 
You must log in or register to reply here.
Back
Top