Post: Sony made 4.xx, no better than 3.55
05-24-2012, 05:16 PM #1
TheSpoken
Questions are answered.
(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.
(adsbygoogle = window.adsbygoogle || []).push({});

The following 7 users say thank you to TheSpoken for this useful post:

Cooler, Kush Friendly, Macdaddy4sure, Ninja, Pauly, rimka06510, SavageRising
05-24-2012, 05:54 PM #2
By what you're saying...

we can create or our key, and sign the vsh.self by encrypting the .elf causing the global key for the executables to be changed? (after data transfer)

:think:
05-24-2012, 09:57 PM #3
TheSpoken
Questions are answered.
Originally posted by SatanicAmerican View Post
By what you're saying...

we can create or our key, and sign the vsh.self by encrypting the .elf causing the global key for the executables to be changed? (after data transfer)

:think:


>Create our key
Can't create a firmware key yourself, good try

>Sign the vsh.self
Signed; HDD Corruption - You also need to edit the vsh to allow unsigned PKGs

The rest, no further details.

Put checkpoints on this as well, after you obtain the "filesystem" backup you should be able to read and write if the backup didn't corrupt. The first line will be just like a SELF.
SCE............ (Hex editor and so forth)
Also, when I get the DRM keys, I'm giving them to pcfreak and/or alfa for their sites.
05-25-2012, 10:53 AM #4
Take a look at RCO Editor its the same as Sprx You can edit the xml and encrypt it back again via VSH it works on 4.11 if you can get access to dev_flash\vsh\resource will find RCO files But only do this if you have progskeet or keys to repack the 4.11.
05-25-2012, 12:50 PM #5
TheSpoken
Questions are answered.
Originally posted by xxmcvapourxx View Post
Take a look at RCO Editor its the same as Sprx You can edit the xml and encrypt it back again via VSH it works on 4.11 if you can get access to dev_flash\vsh\resource will find RCO files But only do this if you have progskeet or keys to repack the 4.11.


Finally someone replies to this. We have both of these right now.
The only thing is: you can't access things through the dev_flash without corrupting files. The PS3 HDD Studio basically opens this up to the public to view if you know what you're doing and use it for different things (edits)
05-25-2012, 03:08 PM #6
The only way to edit files on 4.11 is to disable ps3dm_sm set_del_def_encdec_key which should be the top line if i remember of the hex.
05-25-2012, 03:44 PM #7
xTc
[MOVE]Hello[/MOVE]
well im glad you guys know what your doing cause i dont Happy

The following user thanked xTc for this useful post:

Smexeh
05-25-2012, 10:30 PM #8
ZerOtObey+RM
Bounty hunter
damn looks hard
05-26-2012, 12:03 AM #9
DiJiTaLGoDz
Former Staff
damn looks hard
05-26-2012, 12:14 AM #10
TheManDavid
Your mother!
damn looks hard

Copyright © 2026, NextGenUpdate.
All Rights Reserved.

Gray NextGenUpdate Logo