(adsbygoogle = window.adsbygoogle || []).push({}); Hopefully I can get some intellectual discussion here since I'm in a stagnant on what to do and what not to do since I've been partaking in other projects like this. First, I'd love to find documents that helped me, but then it wouldn't be very resourceful to any of you.

1::
Alright, since it doens't say which firmware the backup management was first implemented, I will go off of the firmware I first found it on and studied.
Well, where is this stored? There's 3 places this can be stored and each of them can be modified from input and output during any time in the procedure of restoring the file system. This also doesn't have any layer of encryption to it like backups, so the data can be transferred anywhere upon retrieval of the file.

2::
dev_HDD*
There isn't any access to editing these files without anything being signed from that point on.

3::
.BIN,.TAR,.SELF, and more are editable and resigned through the backup if anything is resigned. If you have an ELF, it updates it with the new encryption upon boot/restoration. The vsh.self can be edited through retrieving the backup since it can be corrupted at will. You have everything you need to create a PUP as well.

4::
Have at it. When questions are presented, I will give you all the help you need just like Unknown with all of us on Black Ops before Choco's tutorial. Please learn things on your own that you don't understand before anything. If you need anything that defines how to do things, ask in here. Otherwise, if you find drive access without decryption then just prepare for an update since I'll leak it.

Also, take exceptions to the PS3 HDD Studio... Nostalgia to those people who remember; feels bad if you don't know it.