The above video goes away if you are a member and logged in, so log in now!
KaKaRoTo Tells You Why PL3 Has Compatibility Problems
KaKaRoTo Tells You Why PL3 Has Compatibility Problems –
Apparently, everyone who are running Hermes payload before might have some games compatibility problems when trying KaKaRoTo’s PL3 payload in their Jailbroken PS3 console. Here’s the reasons why:
Above are KaKaRoTo’s tweet regarding this issue.
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
Personally, I think its a load of shit.
PS3 Phat with 500GB
1 TB External
AVRKEY (ATMEGA32U2) - 32KB Onboard Flash Memory
Future List -
- PS3 Move Set
Thank you Geohot and fail0verfl0w for fully hacking the PS3.
Kakaroto further clarified his theory later that day:
I think it may only apply to game updates. And it looks like updates installed with hermes v4 won't work even if not jailbroken
This thread is really pointless, here is the steps for the REAL solution to this PROBLEM:
It been a know fact, since the beginning of the PS3 jailbreaking, that "previous stored game data" sometimes breaks compatibilty.
Even on the original first PSJailbreak, you had to delete your old "retail original gamedata" to get the "backup" version to work correctly.
It does seem strange that switching payloads causes problems, but the developers need to dig deeper into the file index tables, I am sure the PS3 keeps like an index how the "game data" is originally stored, maybe even the "syscall" or "path" or another form of checksum, or simple hash stored in another file pointing to the "data".
So once something is changed, it breaks the "checksum" or index, and if the game checks for it, it displays "corrupted data", of it does not, and uses that data, somehow it gets not transmitted to game right and it crashs.
More work really needs to be done in all the files stored on the PS3, and how they are indexed and hashed, doing a binary compare to "stored data" from a "Hermes4 payload" to "Retail untouched" to "PL3 payload", so those pointers can be modded or patch correctly.
The perfect way, would be for the data to be same, so it behaves like "retail untouched", I don't see why not, it just a matter of taking a vigin machine, blank hdd, taking a game that is know to have problems between both "retail install" and "pl3 or hermes" installed, and running it stock untouch, then right away using FTP and copy all the HDD data, and then wiping the drive, and then trying it with "hermes", and again copy all the HDD data, and then once more with "pl3", and again copy all the data, and once you have those 3 sets of files, I talking not just the "game data files" but all the accessable files, comparing them to see why and what is differ between the modes.
Once the common element is found, then this problem can be finally solved for the better of all users.
Maybe it will also give the answer to "black screen", comparing stored data of the retail working game, to the "black screen" game when in jailbroken mode.
Originally Posted by garyopa
I think the black screen games are trying to access memory that is actually in use by the jailbreak exploit itself.
This is the only common element which has not been changed in any payload version since the very first psgroove etc.
Maybe if we can load the exploit/payload to a different area for testing and see if these games will boot afterwards?
If they boot, problem solved. If not, then it could be something else such as a hard-coded path in the eboot which states a physical path or something.
As we are remapping the path by mounting the drive etc, the physical path no longer exists so it can't boot etc.
Just some ideas.....
This can't be true 100% of the time.
I installed Fallout: New Vegas using Hermes v4b. I then used the compiled PL3 from my thread and was able to boot it. The only thing that was weird was when I was using the patched version of PL3. It would boot up Fallout, ask me to install game data (even though I already had) and then install with no errors. But it would just hang after the install.
I checked the space on my hard drive to make sure it wasn't using up space with double installs (it wasn't). As soon as I switched back to the DEFAULT PL3 payload or the Hermes v4b payload, the game didn't ask me to install again and everything worked fine (including saving and loading)
There has to be another factor...