Xoeo's custom PL3 payload for 3.15

[Cyberskunk]

Ehm... C'mon...

I just had a quick look at the code. But from what i see, this guy is trying to spoof the index.dat. Haven't seen that in any other payload.

As you might know, there is still this file version.txt on your hdd which seems to store the decrypted system version value from your index.dat. So this could be some kind of the missing link.

How come, that everyone is saying that this payload is nothing new? Are you guys already spoofing the index.dat? Have you ever had look at the code or just posting your personal feelings and opinions.

For porting it to 3.41 we need to find the corresponding offsets for the stuff we do not already have. Kakaroto has some very in depth tutorial on this.

Sorry to break it to you.. It is in all our FW spoof payloads.. Type this into a hex editor.. release:03.5000.. then compare the hex to the index.dat in our PL3.. In the hermes git index.dat is in ascii..

Evilsperms git.. Check it out..

[Scheisen]

Sorry to break it to you.. It is in all our FW spoof payloads.. Type this into a hex editor.. release:03.5000.. then compare the hex to the index.dat in our PL3.. In the hermes git index.dat is in ascii..

Evilsperms git.. Check it out..

Oops... Have you recently added that?
I am quite sure i checked out a PL3 version which had PSN enabled and didnt make any use of an index.dat. Thought everything was done by poking the right values directly into memory.

Can you explain how it works?
The systemcall which reads index.dat is patched up to read our index.dat?
Does the patched version gets written to the version.txt?

I have to admit, I haven't tried no PSN payload yet. Just did some reading on it...

Btw... Nice work of you and evilsperm to port everything that ever came up to PL3 and pushing it to git.

[ganjamann]

i hope it doesn´t sound retarded, but did anyone get this compiled for 3.15? i tried to, but syscall8 is pretty weird. (i am trying to compile it on osx)
if anyone got this fixed or has the .hex files for 3.15, please post them.

[chocobo]

I know its garbage I meant for you to ask him to post a translated version for us =)

Just saw that you did thanx again =)

Just a quick update, we have got it to compile but its black screening. So we still need to find the memory offset to be patched in for 3.41.

Does anyone have a 3.15 LV2 memory dump they'd be willing to share?

[lombers]

The biggest benefit I can see from this would be compatibility...

The hermes payload has generally always had better compatibility and stability compared to PL3. I think compatibility these days is even, but stability is another issue...

The return to XMB freeze is common with PL3, and there are still games like Modnation Racers that refuses to play nice with PL3 and constantly freezes.

I just hope it will work on my Max AVR USB which as mentioned only has 12K of usable space... else it may be time to invest in another device....

[Scheisen]

The return to XMB freeze is common with PL3, and there are still games like Modnation Racers that refuses to play nice with PL3 and constantly freezes.

I can't confirm this. The PL3 no_unauth works like a charm with GAIA. For good reason you act only on userlevel on that payload and can only do things you are able to do on an unjailbroken debug tool.

I am quite sure that most of the crashes you experience on that payload are due to apps which run into access violation and don't make use of any error handling.

Backups work with PL3 no_unauth if they work on any other payload. It seems that some Games even require it for proper backup compatibility. Thats what i experienced.

But i think all payloads lack compatibility for the games where the EBOOT.BIN calls different selfs like all the COD games. When will this be fixed?

[lombers]

I can't confirm this. The PL3 no_unauth works like a charm with GAIA. For good reason you act only on userlevel on that payload and can only do things you are able to do on an unjailbroken debug tool.

I am quite sure that most of the crashes you experience on that payload are due to apps which run into access violation and don't make use of any error handling.

Backups work with PL3 no_unauth if they work on any other payload. It seems that some Games even require it for proper backup compatibility. Thats what i experienced.

Just to confirm, I am using GAIA and PL3 NUS. I have seen freezes when returning to XMB only on 2 occasions, but I know others in this forum have also experienced the same issue.

All other backups I have work fine, except for Modnation Racers. The in game hard lock / freezing is random in it's occurrence, I don't know why this game is problematic. From what I've read this issue does not happen under any hermes payload, but having been spoilt with PL3 NUS I don't want to destroy permissions by trying this out...

[Scheisen]

So if it works for the both of us and for others not, maybe others are doing something wrong? Maybe they use software which doesnt match their payload and isnt able to handle this circumstance...

From what i experienced, you can fix messed up permissions easily if you delete the game via xmb while on elevated permissions than reinstall with no_unauth. I messed around a bit with different payloads in order to compare their effects on the fs. It seems that you dont run into permission issues aslong as data is handled by the system tools like game_data_utility or save_data_utility for example. Problems seem to appear when data is handled not in accordance with the SDK and for example data is transferred via ftp to places which are not meant to store user data.

[TheShredding]

Hello, I'm a noob in modding PS3...my question is: how those payloads works??

I've got a PSJAILBREAK (genuine, I think..) and i want to downgrade to 3.15 and still play game for 3.50, is that possible???

Support for PS2 games is only for Earliest PS3, that had this feature before, right?

Is there a guide or a tutorial or something explaining how to use those payloads?

Thanks a lot

[ieder-zijn-meis]

...