PS3 PS3 HDD Decryption Helper 2023-12-07

[Berion]

Cool, thank You for Your time! I will check those scripts with pleasure. ^^

 

[Iridule]

@gmipf I am fairly new to Linux only having used it for a few months now. I did manage to compile a custom kernel and have been doing some testing on mint 21.1 with kernel version 6.2 stable, and have noticed I had to build the UFS module into the Kernel before it would work properly(it would not work as a loadable module even with write permission chekced) Yet when it does work the proper folder does not open which can be fixed by changing {HOME} to {ROOT} in the mount portion of the scripts yet doing so brings about the "read-only" issue again. Any advice?
Please see video for more detail.
https://mega.nz/file/eRwWESoR#uVqEJIFmRISxapYQMnvZZ-kyfgQ8MGxVqavJ7a6V_SY

 

[Berion]

${HOME} is in Your case "/home/iridule/". ${ROOT} is "/". So I don't have idea WTH until You have "ps3" with stuff in root too.

BTW: Instead using "PS3 KO Manager.sh", try Gimpf scripts. They are far superior than mine.

 

[Iridule]

${HOME} is in Your case "/home/iridule/". ${ROOT} is "/". So I don't have idea WTH until You have "ps3" with stuff in root too.

BTW: Instead using "PS3 KO Manager.sh", try Gimpf scripts. They are far superior than mine.

I will check them. I think now that UFS is built-in and I'm using mounter 1.6c version loading bswap16, will work for me with read/write permission. The folder for hdd0 opening first to home folder after mounting and going back manually is just minor inconvenience which only happens after UFS is built-in working with write permission.

@gmipf I was just testing your scripts. I have some errors is this because I have a custom kernel name and no headers installed maybe? Also .config has a unique filename in my case. However I already have UFS module built-in with write support active. I was just testing your scripts for bswap16 out of curiosity.

 

[gmipf]

I did manage to compile a custom kernel and have been doing some testing on mint 21.1 with kernel version 6.2 stable, and have noticed I had to build the UFS module into the Kernel before it would work properly(it would not work as a loadable module even with write permission chekced)

For me in-place loading the ufs module was possible with write support. You need to first unload any instances of ufs (check with lsmod and unload with modprobe -r) and then use insmod to load by providing the path to your compiled ufs.ko file, do not use modprobe for loading in that case.

@gmipf I was just testing your scripts. I have some errors is this because I have a custom kernel name and no headers installed maybe? Also .config has a unique filename in my case. However I already have UFS module built-in with write support active. I was just testing your scripts for bswap16 out of curiosity.
View attachment 40548

@Iridule I haven't confirmed it, but it seems you kernel version string is something not provided by the official Ubuntu repositories at all. I'm not sure if I should add support for such special cases. My script will try to find a source based off your running kernel string installed from an Ubuntu repository. The package manager or repo doesn't seem to know anything about your kernel version string, therefore that error. As you said, your kernel has a custom string/name.

 

[Iridule]

For me in-place loading the ufs module was possible with write support. You need to first unload any instances of ufs (check with lsmod and unload with modprobe -r) and then use insmod to load by providing the path to your compiled ufs.ko file, do not use modprobe for loading in that case.

I tried that method originally with no success though the touch command said write support was on when I actually tried to write files to the drive it failed saying read-only. The only way for me to get it to work was have it built in which does make it work for sure in my case. All is working well except for improper folder opening automatically once mounted which I think @Berion will be addressing in next update not sure. It really is no major issue in my opinion just minor inconvenience. Though backup gives me many permission denied errors when I try to use it even with write support on. For my uses the major things are working well.

 

[gmipf]

I have updated the auto compiling script for ufs and bswap16 to support newer Linux kernels.

Script link: https://www.psx-place.com/threads/ps3-hdd-decryption-helper.38281/page-5#post-362960

 

[Berion]

Berion updated PS3 HDD Decryption Helper with a new update entry:

PS3 HDD Decryption Helper (2023-11-10)

• Fixed bswap16-ecb module compilation on newest kernels.
• Cosmetic changes in some scripts.
• Moved work on source code to "/tmp".
• Refactorized "PS3 KO Manager" script.
• Replaced *Micro scripts by *Read Only scripts.
• Restored original source code of bswap16-ecb and applying changes by script in "/tmp".
• Added support for OtherOS & OtherOS++ formatted disks.
• Added option in "PS3 HDD Umounter" script for only unmounting all partitions.
• Turned off interactive mode in modules loading menu in "PS3 KO Manager" script.

Now it is possible to map and mount OtherOS partitions. Script mounting automatically only first partition found table (Red Ribbon, Yellow Dog etc. making only one + swap). All however, are listed under "/dev/loop90p<number>". Bootloader is under "dev/loop91" (NOR models only). Detection is automatic, based on 3rd(NAND)/4th(NOR) region existence in PS3PT.

No OtherOS support in Unattended's, Mounter Decrypted, Dumper and Backuper scripts, because I'm lazy, and because rather no one need it. ;p

 

[Neal Cullum]

Whereabouts is your HDD Backuper software? You mentioned it in the past but I can't find it in the resources section.

 

[Berion]

@Neal Cullum It is one of the scripts in whole package. But take in mind, it was not intense tested. I recommend to check after backup process end if all chosen data is there. They should in theory. ^^

 

[Berion]

Berion updated PS3 HDD Decryption Helper with a new update entry:

PS3 HDD Decryption Helper (2023-12-07)

• Added "PS3 HDD Expander" script for expanding UFS2 on cloned drives (extremely unsafe, avoid it ;p).
• Added "PS3 HDD Mounter (Missing PS3PT)" script for mounting PS3 disks initialized (killed ) by Windows.
• Added "PS3 HDD Umounter (Missing PS3PT)" script for unmounting PS3 disks without PS3 partition table.
• Added "Updater" script for checking if there is new version of PS3 HDD Decryption Helper toolkit.
• Added "dev_hdd1_empty.xz" image of cache partition, needed for...

Read the rest of this update entry...

 

[Victor França]

IDHello @Berion and folks, whats up?

(skippable, just for context)
There is some time since I wanted to do a full backup of my data, but as I haven't been gaming much (as universtiy is going on), I have been procrastinating to do that. The thing is that I recently dropped my PS3 and managed to even brake the HDMI cable, so my conscience started asksing me to do a backup already, before too late.

As a desperation attempt to backup the HDD before it colapses for good, I plugged it indo my Windows machine to clone the HDD using Macrium Reflect (I am somewhat used to it, although not for ps3 use...). But, well... The disk didn't show up either in Windows Disk Manager or Macrium Reflect and then Windows prompted me the classic one, "initialize the drive as MBR buddy?" As I didn't know about the PS3 custom file system, so I did just that...

It's been about 4 days that I'm full commited to recover the data, but... Yeah...

I did a 1 by 1 image of the disk that was initialized in Windows using DMDE and tried a method of transplanting the partition table but it didn't help (although it is probably me that did it wrong). And in some of my searches, the PS3 HDD Decryption Helper appeared and for my joy, with the recent update to mount PS3 disks initialized (killed, lmao F you microsoft haha) by Windows.

The HDD is in 4.88 using HEN (HFW), but as I saw I needed the EID key (never knew about this) I formated the disk (to make it usable once more) and installed the 4.88 CFW evilnat. I tried using the IDPSet store brewology dot com/ahomebrew.php?brewid=271 to get the EID key (I think it worked?) and got it to my Pendrive. The file doesn't have any file extension though, is it like this? I got it to the folder mentioned it to be and rename it as a .bin file.

Then I will take the image of the already initalized by Windows HDD back to the HDD. The thing is, though, that I have no idea whatsoever of how to Compile needed kernel modules and load them (PS3 KO Manager script).

Could you guys help me? I mean, give me some more directions of how to do it?

I am super enthusiast about tech, as I am in the first year of Eletronic Eng., but I am still very noob when it comes to linux side. I really want my precious 13yo data back

(how do I provide screenshots, btw?)

EDIT: BROOOOOOO I JUST SAW YOU ARE FROM POLAND, than remembered the partitioning table transplant guide I read was from a polish guy, IT WAS YOU
BROOOO you are awesome, really! woww

 

[Berion]

@Victor França

IDPSet is for changing IDPS, not for dumping ERK. But I never use it, maybe allows You dumping this key too, I dunno. On Evilnat CFWs, ERK can be read from XMB, at least on 4.90.1: https://www.psx-place.com/threads/dumping-the-eid-root-key.42153/
To be sure that You have indeed right and properly dumped key, try another method. EID Root Key possession is crucial part of all things related to PS3 HDD.

For sure PS3 disk appeared in Disk Managment. Due to encryption etc. just recognized as empty. That's normal.

Use this tutorial (in attachment, the one with newest date): https://www.psx-place.com/threads/tutorial-hdd-mounting-and-decryption-on-linux.23308/
It covering up everything you need to read disk using PS3 HDD Decryption Helper toolkit. However, since Your disk don't have PS3PT, then in section titled "Mounting Partitions" instead using "PS3 HDD Mounter (Read Only).sh", use "PS3 HDD Mounter (Missing PS3PT).sh". Everything will be the same as in tutorial, except You will be asked additionally to point start LBA of VFLASH (if this is NOR model) and UserData partition. You can use some preset listed in script.

If script will not mount "dev_hdd0" (all models) and eventually "dev_flash2" (NORs only) [other partitions aren't mounted in this script, and those which are, are also read only], then use "PS3 HDD Umounter.sh" script and start again from "PS3 HDD Mounter (Missing PS3PT).sh" but feed him by different value. This cannot be make automatic because as name suggest, partition table was wiped out and it is partition table which handle such informations - without it, user must tell him from where to read.

I suggest to try first with HDD which is fully working, just exactly following the guide from PDF. Then You will be familiar with the process and know what to expect. After that, You can try to deal with "broken" HDD. And if You have image on disk, just use image:

sudo losetup -f "/media/<mounted windows partition with disk image>/<image name>.bin"

This will attach this image to "/dev/loop1" which you giving to script instead "/dev/sdx".

- - -

I am super enthusiast about tech, as I am in the first year of Eletronic Eng., but I am still very noob when it comes to linux side. I really want my precious 13yo data back

"Every great journey starting from first step."

You cannot attaching files or linking to www until You will reach some post count (10? maybe little more). Anti-spam security measures.

BROOOOOOO I JUST SAW YOU ARE FROM POLAND, than remembered the partitioning table transplant guide I read was from a polish guy, IT WAS YOU
BROOOO you are awesome, really! woww

Thanks. ^^
If You have in mind this, then yes:
https://www.psx-place.com/threads/tutorial-fixing-windows-disk-initalization.27599/

 

[Victor França]

@Berion wow that's some quick response, thanks!

Well, first, you are right. I didn't need this IPSet to get the key, I will just follow the tutorial you made using the tools from Evilnat itself, actually. I felt a little stupid now lol

Also, I have a spare HDD, although it has less capacity. As I'm already taking the image back to the original HDD (takes super long time), in the meantime I could use the spare HDD to test it first to better understand the proccess, as you suggested (great suggestion actually). My question, though, in this other HDD, is the key different? The key is for the console itselft, or every different instalation has its own key?

Actually, I'm sorry. Reading the PDF guide, my question was already answered there. My other question though, I use Ubuntu with the 6.5 kernel version in my machine.

This phrase "The compiled modules will only fit this particular kernel version. If you upgrade or upload a different kernel, you will have to recompile it (this is why the toolkit contains source code, not so-called binaries)." It means that it was done to work specifically with 6.4 or does it mean that if I upgrade my Ubuntu version, then kernel will change, then I will have to recompile (not planing to upgrade any time soon).

Also, I got this error

ERROR. I couldn't load "bswap16-ecb" kernel module.

It managed to find it (first one ok), got an error on both UFS (as expected) but got this particularly error in the kernel module

I'm really sorry, I feel that I'm spamming right now. Never been much into forum, I mean like, actually posting, so I do lack some sense in that. I'm really sorry, I will try more things before posting.

I actually abandoned Ubuntu and installed Linux Mint 21 on it (kernel 5.15). The error I mentioned is gone (just as you said that Mint has every thing needed installed already).

I was able to pull the data just fine from my spare HDD (which is working fine, but doesn't have any data in it, I'm using it just to be able to boot the PS3). (I had to try mounting it 2 times, 2nd time is the charm)

The actual problem now is with the Broken windows initialized HDD. When I try to mount it, I get the following:

STEP 1: Devices
Choose your HDD from PS3 (type eg: /dev/sdx) from below device list:

MODEL             SIZE NAME
                    4K /dev/fd0
ST9160821AS     149,1G /dev/sda  ##HDD with Linux Mint installation
                  489M ├─/dev/sda1
                  489M ├─/dev/sda2
                148,1G └─/dev/sda3
SAMSUNG HD102UJ 931,5G /dev/sdb ##A HDD which has the .bin image
                398,1G ├─/dev/sdb1
                    1K ├─/dev/sdb2
                133,4G ├─/dev/sdb5
                  400G └─/dev/sdb6
Generic         298,1G /dev/sdd ##The broken HDD.

/dev/sdd
Ok, so You've chose: "/dev/sdd".

Press any key to continue.

STEP 2: Mounting
Choose WISELY:
 1. Mount HDD came from Fat with NAND memory.
 2. Mount HDD came from Fat with NOR memory.
 3. Mount HDD came from Slim with NOR memory.

3

Choose sector of "dev_flash2" partition:
 a. user defined LBA
 b. LBA 439816

b

Choose sector of "dev_hdd0" partition:
 a. user defined LBA
 b. LBA 524304
 c. LBA 524312
 d. LBA 524320

b

WARNING: Device /dev/sdd already contains a 'dos' partition signature.

WARNING!
========
Detected device signature(s) on /dev/sdd. Proceeding further may damage existing data.

Are you sure? (Type 'yes' in capital letters): YES
Device ps3hdd-bs already exists.
Device /dev/mapper/ps3hdd does not exist or access denied.
losetup: /dev/mapper/ps3vflash: failed to set up loop device: No such file or directory
losetup: /dev/mapper/ps3hdd: failed to set up loop device: No such file or directory
mount: /root/ps3/storage/hdd/dev_flash2: mount point does not exist.
mount: /root/ps3/storage/hdd/dev_hdd0: mount point does not exist.
NAME
sdd



"/dev/loop40":

"/dev/loop41":

All done. Press any key to exit (also, yes, I mounted it while having already tried to mount, this was just to get the code to copy)

I guess the problem might be with the sector number. I tried b, c and d but the end result were the same, "no such file or directory" etc (I did unmout before trying the other options, if it makes any difference I hope). Also, my PS3 is a Slim model, the stock firmware was the 3.52, if it helps...

Also, I'm using a external USB case for the HDD. I was able to get the data just fine with the working HDD, but could it be a problem, still?

 

[Berion]

wow that's some quick response, thanks

You're welcome.

As I'm already taking the image back to the original HDD (takes super long time),

But that was not necessary, on Linux You can attach image to loop device and it will be treat like eg. virtual HDD. If You are know eg. Daemon Tools on Windows, then it is the same conception but instead virtual optical drives it is for all kind devices which history burried, current or even not designed yet from the future. ;]

My other question though, I use Ubuntu with the 6.5 kernel version in my machine. (...) It means that it was done to work specifically with 6.4 or does it mean that if I upgrade my Ubuntu version, then kernel will change, then I will have to recompile (not planing to upgrade any time soon).

It means that every time You change kernel like eg. updating it or downgrading, You will need compile bswap16-ecb and ufs again because kernel modules matching to specific kernel versions only. Consider *.ko like drivers in ring 0 in Windows. There are methods to force them to work but that's asking for troubles.

You do not need compile ufs.ko, as I wrote in tutorial. bswap16-ecb only - and this module altering byte order from Big Endian which PS3's PPC using to Little Endian which Your PC's x86 using.

I'm really sorry, I feel that I'm spamming right now. Never been much into forum, I mean like, actually posting, so I do lack some sense in that. I'm really sorry, I will try more things before posting.

There is "Edit" button under Your posts. But I'm not sure if it is not disabled after some period of time due to prevent modifying old posts by inmature users turning discussion into dead conversations when half of commentaries dissapeard. So only mods, admins and trusted people can do it without time limits.

The error I mentioned is gone (just as you said that Mint has every thing needed installed already).

Yep, this is distribution all-in-one, "for idiots" as some orthodoxies saying, so I'm using it daily with pleasure and stress-less. Recommending.

I guess the problem might be with the sector number.

Yes, but also You didn't removed old loops which script make because "Device ps3hdd-bs already exists." says that this mapper already existing, and Umounter removing also mappers and loop devices. I bet You didn't do proper Umount (something prevent script doing it and You was not aware reading warning on red ;]).

I suggest try again, and be sure that each time, when You need start from scratch, the "/dev/sdd/" is not "revealed" to mappers (in Terminal type "lsblk" to list actual stuff).

If none of values matching, try custom increased or decreased from lowest or highest by 8. For some reason, thresholds are 8.

Eventually: sice this is the same console and You have working setup, You can dump PS3PT there and attach here text dump from it, so I can see what are the values. Yet we still don't know if offsets are tied to disk size and some mysterious calculations or model tied. So this can be a blind corner.

- - -
Whoah, You have connected FDD. ;}

To not been bothered by typing "YES", add "-q" for all cryptsetup lines, like eg. below. I will change that in future versions.

sudo cryptsetup create -q -c bswap16-ecb -d /dev/zero ps3hdd-bs $DEVICE

 

[Victor França]

Thanks again! And thanks also for some explanation about the forum, appreciate the info

But that was not necessary, on Linux You can attach image to loop device and it will be treat like eg. virtual HDD.

I'm refraining from doing that's the only raw image I have (I don't have anymore free space this big and OneDrive doesn't let me me upload files bigger than like 200GB I think lol) and as I'm somewhat stupid I'm very afraid of shitting the only backup I have lol. Also, although very annoying, I can wait for it to copy the sectors 1 by 1, so it's ok.

Yep, this is distribution all-in-one, "for idiots" as some orthodoxies saying, so I'm using it daily with pleasure and stress-less. Recommending.

lmao I will take the recommendation into mind haha

Yes, but also You didn't removed old loops which script make because "Device ps3hdd-bs already exists." says that this mapper already existing, and Umounter removing also mappers and loop devices. I bet You didn't do proper Umount (something prevent script doing it and You was not aware reading warning on red ;]).

Yeah that's probably why. I remember there are 2 options, one which doesn't include the loop thing and so the one that I probably chose at that attempt
But even then, I couldn't mount it in my first try :/

Ahhhh I remembered something I forgot to mention
If I remeber correctly, I tried to do a partition table transplant before that. Let me try to make this time line:

I tried to do the partition table transplant a lot of times, maybe about 10 times (so yes, I asked dmde to wrote 300GB of data at least 5 times lmaooo) each time trying something different. First with MBR and if it didn't work, I tried GPT over it.

• For example, the first time I booted the PS3 after having initialized the disk in Windows, it asked me to put a USB Pendrive with >4.88 to format it. (I didn't know, but it was a indicator of which software version was installed). Then I went to Sony website and got the 4.90 OFW (as I jailbroke it like 2 years ago I didn't even remebered about this OFW HFW and CFW thing) and formatted it, got the 1 sector, burned the image on the HD, overwritten the 1st sector and installed it on the PS3. Same annoying 480p black screen asking me to get a USB to format.

• Then I realized I was using HEN on the 4.88, so it was a pain in the ass to downgrade it back but I got the job done at least, making use of the spare HDD. Then, with the 4.88 installed, I made the same thing again, formated the original drive, got the first sector, etc etc. But this time, when I got it back into the PS3, now the welcoming PS5 boot logo actually appeared instead of the annoying safe-mode-like experience (yes lmao PS3 4K PRO was the last thing I was screwing arround before droping the console)

• It gave me some hope, but then it said it needed to rebuild the database or something, I don't remember (but I can easily recreate this situation, maybe take a photo if you want). I selected confirm, but it got a instant error saying it would be actually necessary to format. I said ok then whatever, confirm again. Then, after the formatting, the XMB customization and the user profiles were still there, although with no data obviously. So, thinking now, the transplant was kinda successful, I guess? (btw, should I mention this at the transplant thread?)

Then I got this 1st sector out of this again, remade the process, but same thing again.

Then I think I made the first try with the PS3 HDD Decryption Helper. As at the time I believed the transplant was unsuccessful, I treated it as with no PS3 partition. Maybe the errors were because of that (or so I thought at least), so I reburned the image. It again didn't work on the first try, the second (I will better explain in the other thread) I meant to try 524.288 (as I thought this was the start of a sector) but I skipped the custom insertion by mistake with an enter, and only in the third attempt it worked. (if I'm not wrong, it was like this)

Also, I've been thinking about something, maybe high customization and intrusion in the system files can affect the PS3PT somehow, maybe some mismatch? Because the system could load the XMB customization just fine, but got some problems with the rest... Also, between versions, like what happened to me first, the PS3 itself with 4.90 OFW and the HDD with 4.88 HFW, maybe it impacts somehow, like another mismatch? I'll try to do some tests like this to see if there are any differences, like getting the 1st sector of my spare HDD and then initializing it with Windows to see if it does affect or not, being this other HDD with no software mismatch. Or maybe if the HDD itself is a problem, since this spare is another brand and could have a different impact, maybe?

If you have any tests you'd like to throw in my console version, I'd be more than happy to help you with this. I got a liking to this subject I must say. I've got a PS3 Slim CECH-2501B and some different HDDs I could try also. Furthermore, I'm on vacation 'till march so time is basically infinite for me now (finally). Consider this as a thanks and as new a enthusiast being born i guess?

 

[Berion]

and as I'm somewhat stupid

Why You saying that?

I'm very afraid of shitting the only backup I have lol. Also, although very annoying, I can wait for it to copy the sectors 1 by 1, so it's ok.

sudo losetup -f -r <image>

"f" for use first free slot, "r" for read only. You cannot screw read only file. Eventually You can mount as read only partition where image lies if You do not need use it besides image from it.

I tried to do the partition table transplant a lot of times, maybe about 10 times (so yes, I asked dmde to wrote 300GB of data at least 5 times lmaooo)

Then I realized I was using HEN on the 4.88, so it was a pain in the ass to downgrade it back

You cannot downgrade on HEN. And HEN works on 4.90 HFW, so no need to downgrade.

Then, with the 4.88 installed, I made the same thing again, formated the original drive, got the first sector, etc etc. But this time, when I got it back into the PS3, now the welcoming PS5 boot logo actually appeared instead of the annoying safe-mode-like experience (yes lmao PS3 4K PRO was the last thing I was screwing arround before droping the console)

So it means that transplantation was successful. ;]

It gave me some hope, but then it said it needed to rebuild the database or something, I don't remember (but I can easily recreate this situation, maybe take a photo if you want). I selected confirm, but it got a instant error saying it would be actually necessary to format.

Rather strange. Even if You installed mod for CFW on HEN, worst scenario is fw reinstall force, not drive format.

Then I got this 1st sector out of this again, remade the process, but same thing again.

Something is broken here, so for sure, You cannot fix it by messing with PS3PT alone. That confirms that start clean is best option for You.

Then I think I made the first try with the PS3 HDD Decryption Helper. As at the time I believed the transplant was unsuccessful, I treated it as with no PS3 partition. Maybe the errors were because of that (or so I thought at least)

No, successful. And no, that have nothing to do what You experienced. It looks like other issue You have in parallel to the main one.

Also, I've been thinking about something, maybe high customization and intrusion in the system files can affect the PS3PT somehow, maybe some mismatch?

No.

Also, between versions, like what happened to me first, the PS3 itself with 4.90 OFW and the HDD with 4.88 HFW, maybe it impacts somehow, like another mismatch?

Yes, but ending with fw reinstall, not HDD formatting.

I'll try to do some tests like this to see if there are any differences

Nah, that will be waste of time. You have probably broken UFS2. So safe whatever You can then.

If you have any tests you'd like to throw in my console version, I'd be more than happy to help you with this. I got a liking to this subject I must say. I've got a PS3 Slim CECH-2501B and some different HDDs I could try also. Furthermore, I'm on vacation 'till march so time is basically infinite for me now (finally). Consider this as a thanks and as new a enthusiast being born i guess?

I believe You can talk with @andshrew to join forces on NetBSD journey and UserData expanding tests. ^^

 

[Woolfy982]

Just wanted to say thank you for the tools! Just had a question about one of them though. I used the 'PS3 HDD Dumper' and chose the option to "Dump entire HDD in byte swapped and decrypted form". It created the .bin file just fine but, I can't seem to mount the image on my linux PC and go through the partitions/files, instead of having the HDD hooked up. (Just thought it would make things a lot easier, as an image file). Is it possible to work with the .bin file like that? Not sure if it's even possible to burn that image onto another HDD or not.

 

[Berion]

@Woolfy982 Hello. Thanks.
Decrypted dumps can be mount by "PS3 HDD Mounter (Decrypted).sh" script as name suggest.

You can write decrypted image on any device but if you willing to use it on PS3, then you cannot because she expecting encrypted each sector by her keys (decrypted be treating like empty). If you want clone (in meaning: sector by sector copy) drive to another, you need do that on non-altered drive (not byte swap and decrypted) eg. via dd or ddrescue. I will add that option in future update (near end of this year).

 

[Woolfy982]

I'm kind of confused because, It won't let me mount the .Bin image file with that tool. (Only the HD when connected to my PC). I'm guessing it's not possible to mount the image file alone it seems. That's ok. Maybe I'll just hook the HD back up again. I appreciate it.

@Woolfy982 Hello. Thanks.
Decrypted dumps can be mount by "PS3 HDD Mounter (Decrypted).sh" script as name suggest.

You can write decrypted image on any device but if you willing to use it on PS3, then you cannot because she expecting encrypted each sector by her keys (decrypted be treating like empty). If you want clone (in meaning: sector by sector copy) drive to another, you need do that on non-altered drive (not byte swap and decrypted) eg. via dd or ddrescue. I will add that option in future update (near end of this year).