cryptsetup create -c bswap16-ecb -d /dev/zero ps3hdd-bs /dev/sdx
am i supposed to change anything? im reading the hdd from the board.
Choose sdx which is Yours PS3 HDD. It can be sda, sdb, sdc etc. depend how Linux enumerate devices. I see that You reading "quick guide" instead full tutorial.
Quick guide is for advanced users which know what they doing! You will stuck several times based only on it. Use tutorial in PDF for Your sanity or else You will be frustrating in cycles.
i changed it to sdb and got the message
Device ps3hdd-bs already exists.
It means that You have already created mapper named "
ps3hdd-bs" so You cannot create another with the same name; probably in earlier attempt. Remove it ("
cryptsetup remove ps3hdd-bs" or choose another name i.e "
ihatelinux" or whatever ;]). You can see all devices and virtual devices by typing "
lsblk".
cryptsetup create -c aes-xts-plain64 -d /home/mint/ps3/ata_key.bin -s 256 ps3hdd
/dev/mapper/ps3hdd-bs
i get
bash: /dev/mapper/ps3hdd-bs: Permission denied
If You didn't byte swapped (by bswap16-ecb) PS3 HDD, creating in the process "
ps3hdd-bs" mapper, this will not sweep You anywhere. Bytes swapping is mandatory because PS3 CPU is in opposite Endian family to PC CPU so CellOS write data in different way. Only after swap it on the fly, You can try to decrypt drive (also via mapper and also on the fly which will make mapper "
ps3hdd" in the process).
Anyway, this means that You have not permission to do that. Only Root (consider it as Administrator on Windows) have access to devices, mappers etc. You need elevated permissions to do all this stuff.
Honestly im starting to think the hdd got screwed when i tried to clone it. Jus out of curiosity i took the new hard drive and tried to use the hhd tool and it worked with no problems.
Do you know a way to try and unscrew it?
All things You are doing (trying to do ;]), are on the RAM. Nothing is written to the HDD.
What do You mean by "new hard drive"? The one inside PS3, currently assigned to it? If his first sector looks similar to my screenshot and HDD Reader recognized it, then for sure it is fully ok. But, it doesn't prejudge anything, as still this "old hdd" can be ok (in assumption that only those values from 0x1B8 are in use in first sector - which we don't know and no one know yet).