The above video goes away if you are a member and logged in, so log in now!
Relationship between payloads & backup managers
Relationship between payloads & backup managers –
Hi! all. i'm very confused with all the payloads from Hermes & others.
1) Firstly, what are they? whats the difference between them & psgroove &
2) I keep seeing terms such as psgroove with Hermes payload etc. what
does this mean & what does it do?
3) Also whats the relationship of all these payloads, psgroove, psfreedom with the backup managers? my current understanding is as long as i have a dongle regardless if its a clone or a TI-84 calculator with the original psgroove that supports Backup manager inside, i can jb a ps3 & install pkgs & play backup games. i've also understand that Hermes payload provides compatibility to other modified backup managers. Why is this compatibility important?
4) Will switching between different payload affect the jailbreak procedure & ability to use the many backup managers out there? cause it seems that everytime a new payload is out i will read about hex files being created for different jailbreak devices. Whats the purpose of these files?
Apologies if my queries are long winded or sound noob.
I am wondering the same since so many files and clones are released every day I'm so confused!
1. Payloads are actually what hack your PS3. Inside the payloads is certain pointers to put stuff in different sections of memory. There has been a lot of discussion of the proper way of doing this, hence all the different versions. PSGroove is a payload for Atmel based devices, PSGrooPIC is for PIC devices, and PSFreedom is for phones and other compatible devices.
Originally Posted by wolvie77
2. See answer #1. Hermes decided he wanted to keep using syscall 36 which points the virtual blu-ray drive to your games folder. KaRaKoTo disagreed with this and created syscall 35 which leaves it up to the application your running to decide which path is linked to where. More versatile.
3. See answer #1 & #2. As the devs started having their disagreements, they kept on upgrading their own payloads. Different things like memory patching, and moving around things in memory created better compatibility with certain games. When this all started, there were games that couldn't sync the controllers because that information was being held up by the payload in memory. Hence why the next version came out that created a patched mode (moved that data to a different point in the memory) so that it would fix previous issues. Same thing goes for games that used to start up with a black screen.
4. The hex's are device specific and have to be based on the coding of those devices. Now with the splitting of school's of thought over syscall 35 & 36, the backup managers were forced to follow suite. They're now starting to support both syscalls, but weren't at first. Also, Hermes has left the scene and he was one of the original coders of PSGroove. So, now we have KaRaKoTo's project of PL3 which is what's taking the place of PSGroove. PL3 is a collaboration between all the different devs that want to work on the payload and try to better it in someway. Kar has a git repository set up so others can download his code and upload patches to it. Hermes is still collaborating on some final things that Kar didn't understand in his code, but will not release anything further.
Hope this explains most of this for you.