Decided to make these up since it was a fairly simple trick they’ve used.. Unfortunately it won’t let me upload anything to PS3HAX so here is the link to my original post at PSX-Scene

Like the ‘official’ release.. All it does is stop someone accidentally updating your PS3.. Enjoy

ALL BOARDS HERMES 4B 3.55 SPOOF
ALL BOARDS PL3 DEF 3.55 SPOOF
ALL BOARDS PL3 DEV 3.55 SPOOF
ALL BOARDS PL3 NOUNAUTH 3.55 SPOOF

DanyL a member on PSX Scene, has created quite a handy tool, it is a Payload Downloader, which lets you download payloads for your device, without the need of searching the web, here is a quote from his thread, it isnt quite finished as DanyL is finishing it off and adding more payloads, so be patient:

I’m happy to announce a new project I’m working on, called PS3Payload Downloader.

It’s a program that gathers all the payloads for all the platforms (rockbox, teensy, psfreedom and so on) in one place and allow you to download them.

As all my other projects – it’s an open source.
I’ll release the source in github when I’ll finish working on it.

Most of the programming is done, what I still need to do it:
Improve search engine
Improve GUI
Create a Logo
Create an updater

Server side:
List and upload all the payloads

For those who want to help me out list all the payloads:
Leave a message with the following details:

Device =
Payload name =
Payload version =
PS3 firmware =
Compiled by =
Link =

For example:
Device = ipod 4g grayscale
Payload name = PL3
Payload version = 23.10.10
PS3 firmware = 3.41
Compiled by = DanyL
link = http://rockbox-psgroove.com/Download…e/rockbox.ipod

Thanks in advance for any help

Anyone interested in helping DanyL head over to the source.

Sooner DanyL gets what he needs, the sooner i can add a download link.

PS3Hax member ricardopvz, has released a hybrid version of PSGroove which consists of PL3 and Hermes v4b together, for the Arduino Duemilanove/Mega USB boards. (more…)

fl0PPsy has released Rockbox (download rockbox here) ports for the PL3for various devices as follows: (more…)

Many of you who use KaKaRoTo PL3 payload may have come across an issue where your existing rips did not work. According to a tweet by KaKaRoTo, the issue lies in if you use the Hermes payload. He says that for some reason if you install a game VIA Hermes payload, it seems that the game becomes “locked” to his payload. The fix is to simply UN-install the game, and re-install it with the PL3 payload, and it will work with all other payloads without issues.

iLLNESS confirmed to me that if you install a game with hermes payload, then it will only work with his payload. Seems the payload locks it.

Uninstall games, then reinstall them when using PL3 then they will work with any payload. Don’t know what’s different though with hermes pay

JasonMckey has updated the PL3 payload to fix the 80010019, the error that requires you to update your PS3 to 3.42 in order to play (games such as Medal of Honor). Yes this means now 3.42 required games work without the need of any modifications to them.

To quote:

The fact that Medal of Honor is now working without the need of the game update, makes me think we were mislead by the news that 3.42 brought new EBOOT keys. Unless JasonMckey somehow dumped the keys and that is what he implemented (which seems highly unlikely). Instead it seems 80010019 is just an error that prevents version tampering with the PARAM.SFO by double checking a version in the EBOOT.BIN. However, please note this is just speculation based on JasonMckey’s twitter posts.

On another note, support for 3.41 Kiosk consoles was also recently added to PL3 by Mark Webber. Those of you with store/kiosk demo PS3 units can now join the jailbreaking party!

KaKaRoToKS: Just added a patch to PL3 that fixed 80010019 error of MOH… works with no update necessary now. Patched thx to @JasonMcKey

KaKaRoToKS: Added a new payload to PL3 which is equivalent to hermes’s “patched mode”. Now games compat should be 100%. MOH just works, no hacks needed.

You can download the source code below, and you guys know the drill post ports and compiled HEXs away

[Download PL3 Source]

[VIA PSGroove, VIA Jason Twitter, VIA KaKaRoToKS Twitter]

Thanks to PiZzA for news tip.

KaKaRoTo the creator of PSFreedom has released some information, via his blog, on the differences between his work and others, here is what he said:

Hi all,

I see a lot of people asking me some questions and I notice a lot of ignorance in the net about the different payload and the latest PL3 payload. So I want to make things clear..
First of all, people should stop talking/requesting/using the hermes v3 payload, I don’t like his work, and the payload is not good, it might crash the system in some cases, it’s not written properly, and hermes doesn’t even seem to understand how git works.
Also, PL3 already includes (for some time now) all the good stuff from hermes, it already supports installing game updates, or running games without a disc, anything else that Hermes added is useless and dangerous.

Some might have seen my tweets about my new payload being released, and many are asking me what is the difference between my payload and what is already available.
PL3 doesn’t support syscall 36 anymore, for multiple reasons, first, it was bad code, it was mapping a path to a single hardcoded value (/dev_bdvd or /app_home or /dev_flash or whatever is hardcoded in the payload) which means that, since we (the PSGroove and PSFreedom developers) don’t want to support running backups, all the official payloads weren’t working with the backup manager without being patched first. The syscall 35 I added in my payload is more generic though, it is the proper way of doing things. You can map any path to another other new path, the prototype looks like this :

syscall_35 (char *old_path, char *new_path);

This means that the payload doesn’t need to have a hardcoded /dev_bdvd path in it, or have extra code for mapping /app_home to something else.. or having syscall 36 change both /dev_bdvd and /app_home breaking homebrew when using a discless mode with a backup manager. You also don’t need a special payload to run the ‘firmware usb loader’.. It all just works because the choice of the path mapping is given to the homebrew applications themselves. This means that the backup managers will just map /dev_bdvd to what they want and they will work by default on my payload, there will be no need for a patched version of the payload to make them work.
This however means that the backup managers that depend on syscall 36 will stop working. For now Gaia Manager is the only backup manager available that is compatible with my payload. But I’m sure more will be ported to use syscall 35.
People need to understand that this new syscall 35 has to become the new standard, this is what all the payloads should use, nothing else, and this is what everyone should start using, not the old, crappy, backup-manager specific, PSJailbreak written, syscall 36.

We need to have some form of standardization for all these payloads, I’m tired of seeing about 100 different payloads floating on the internet, it doesn’t make sense. I always believed in a single payload that works for everyone, and that’s why I created PL3, that’s why it’s a project independent of PSFreedom (and PSGroove has been ported to it) and that’s where all the efforts should go. Also, by using PL3, you automatically gain support, and all the same features, for whatever previous firmwares PL3 already supports (3.01, 3.10, 3.15 and 3.41).

I have just recently seen this new payload that everyone is so happy about that includes “all the good things from 3 worlds”, the one created by Rancid, which includes the stuff from hermes, waninkoko and Mathieulh… and I was shocked to see how much people were happy about this.. people don’t really seem to understand that this wasn’t necessary at all? PL3 has had all those patches for a while now, so why did Rancid even bother making this payload that includes the patches from hermes, waninkoko and Mathieulh? Why would you spend your time doing something that already is available!

This blog post is meant to stop all this ignorance and let people know that they don’t need to look for a special payload, just use PL3 and you’ll get everything you need. It is also meant to explain to everyone what is different about my payload.

On a side, I have received a P3Hub device, kindly donated to me by the people from r4king.com, and I have now tried PSGroove for the first time! I’ve also created a fork of jevinskie’s port of PSGroove which is now improved and updated to support the latest PL3 version. This means that the PL3 payload is available for everyone, those using PSFreedom as well as those using PSGroove, so there is no excuse now on not using it or relying on badly written payloads developed by people who barely know how to code (yes, using winrar instead of git is a good indication of that).

Update:
I forgot to rant about peek&poke!!! So let’s do it now… well, the default payload in PL3 has peek and poke disabled, and for a simple reason : Nobody needs them! and more importantly they are misued! I’ve look at the code of the different backup managers, and it looks like all of them use poke to patch the memory to ‘fix something’ because they think that it’s their job to do it.. no it’s not! If you have a working patch, then submit it to PL3 and if people complain, tell them “use the proper payload”, don’t try to take advantage of peek&poke to go and modify the kernel’s instructions! The reason is simple.. you are a homebrew app that does X, then do X, leave the kernel patching to the payloads! Just as PL3 doesn’t map /dev_bdvd to /dev_usb000/I.Like.This.Game/ and locks it out! Also, I’m on firmware 3.15, so when you decide to poke and patch the kernel with a hardcoded offset, you’re just screwing up my kernel because the offset is firmware dependent! it’s not the same depending on the firmware you use, and I don’t want you playing with it. So.. peek&poke are really not useful to anybody, they are not even available on a normal linux pc, so why would you want them in your default payload, right?! The only people who should use a payload with those syscalls enabled are real developers, people who want to analyze and patch the kernel on the fly while they are doing some development of, maybe, a kernel driver! That’s it. Anyways, that’s enough ranting from me for today!

P.s:
In my branch of PSGroove, I wrote a script that build the .hex file for every supported device (from the README) for every supported firmware. You can find all the hex files here : PSGroove+PL3 hex files

Update:
Thanks to evilsperm, I’ve updated the archive with hex files for these devices : Blackcat, Xplain, Olimex, UsbTinyMkII, Bentio and OpenKubus.
Update 2:
Some people reported crashes with my payload when running backups with installed updates. I figured out the cause and fixed it now in git. The hex files above have also been updated

Thanks for reading.
KaKaRoTo

SOURCE

KaKaRoTo via his blog has announced PL3 and that he is working on implementing PSGroove on firmwares between 3.01 and 3.15, this is what he said:

I’ll announce two things, first, let’s talk about PL3.. PL3 is a new project I started in order to have a common repository of payloads that can be used by any ‘jailbreak’ implementation. I got tired of copying payloads from PSGroove, and I had some nice changes in mine that I thought the PSGroove project could benefit from, so I thought I’d create a single repository that both projects, PSFreedom and PSGroove (or any other similar projects) could use.

You can find it in github, so don’t hesitate to submodule it and use it.

Second important news… I’ve bought a new PS3 just for homebrew. Thanks to all who donated money so I can buy it (I didn’t get enough donations to pay for it, but enough to help me). I bought this PS3 used and it came with firmware 3.01! This is good and bad news : I can’t use PSFreedom to jailbreak it, so i’ve put on hold any improvements for it, however, it will allow me to actually port PSFreedom to older firmwares! My plan is to get the jailbreak working on 3.01, then move on to 3.10 and 3.15 (depending on how hard it is, i might skip 3.10).

Another good news is that after 4 days of work, I was finally able to dump the LV2 memory from the 3.01 firmware, and now all that remains is to find the right offsets to patch, and port PSFreedom to 3.01, so all those who are still using this firmware version, you will soon be able to jailbreak it! Once I’m done with that, I’ll try to do the same with the 3.10/3.15 firmware versions!

To dump LV2, I used a trick and algorithms found by marcan42, so big thanks goes to him, as well as many other people who helped me out, RichDevX and Aaron in particular. I used RichDevX’s idea of ignoring the JIG and bruteforcing the address in which the port1 descriptor gets stored until I get a hit, then use that payload to dump lv2, then find the right JIG offset for that particular firmware from the dump. Marcan’s trick was to send the data through the ethernet cable by using LV1 only hypercalls, and it worked!

Now the latest git version of PL3 has a new ‘dump_lv2′ payload which you can use, it is firmware independent, and only uses LV1 hypercalls, so it should just work… It will dump all the lv2 memory through ethernet, so fire up wireshark, save the dump to a .pcap file, and use the tool in PL3/tools to extract the memory dump from the .pcap file.

In other news, I will soon upload to Ps3utils an .idc script that will search and find the syscall table, and correctly resolve all of its functions and name them properly.. maybe even have it automatically find all functions of a dump in order to save time creating procs in IDA. I’ll let you know once I’m done with it.

KaKaRoTo

Source
Download PL3 Via Github
Just a note, ps3hax.net are not associated nor hold responsibility with files hosted off forum, you download at your own risk.