Originally posted by ShoTz
yes thats what app_home is for
try naming your folder /app_home/NOT_PS3_GAME.
theres also other things you can do in the elf to prevent them from getting your info.
they do collect mac address, psid, console id too
also they may have added more checks in the 1.07 update, i havent checked yet
If I fully understand what you said there.... the simplest solution is edit the list of suspicious directories directly in the BO2's EBOOT.ELF file. Then Resign it with SCETOOL and run that (your own modded / safe'd EBOOT.BIN binary) instead of the official BO2 EBOOT.BIN.
It makes a lot of sense, because you can't sensibly do away with the /app_home folder. Believe me, I went through all the SPRX and even the VSH & LV2 Kernel of my Rebug CFW. You can actually rename "/app_home" to any other string with the same number of characters. eg "/ps3_home" which was the name I plumped for in this little experiment... and many games will continue to work fine. I tested about 10 games or so but 2 of them didn't properly work anymore and came up with a bizarre trohpy error... Certain games internally expect the "/app_home" folder actually being called "/app_home"... including Mass Effect 1. I think the other game was Killzone 2. Obviously I have quite a limited collection of games so couldn't exhaustively test any further. It was enough to discover the general nature of the problem.
Unless you want to cripple certain other games (or some of the future games you have not played yet) then renaming of "/app_home" in reality is off the table. And therefore eliminated.
Leaving about 4 possible solutions:
* Rename Bubba's list of suspicion folders in the BO2's ELF file. Presumably in the way mentioned above ^^.
* Find the branch in the bytecode of ELF before that list is rung up... And stop the problem at the source. Eg skip over or modify the CFW checks. Might be rather difficult to find without some proper DEX runtime debugging and step-though (I certainly don't have set up).
* Find the place where your IDPS and other info is being reported back to Treyach. Presumably in the ELF also... or where Peek/Poke is being detected... and replace that with fake console info / or disable entirely. So that way whatever checks the game uses to detect it's a CFW console, it doesn't matter. Since it tries but can't successfully phone home the necessary info back to TreyArch servers.
* Run each time the BO2 PSN Tool that disables PEEK/POKE and other cool anti-BO2 measures.... Might forget.
There are some interesting avenues to pursue. They assumed that everything is found there in the main BO2 ELF / runtime files. That may not be the reality however.
Personally, I wasn't able to successfully decrypt the original (presumably v1.00) EBOOT.BIN off the Duplex BO2 torrent. Some scetool error. My scetool is working 100%. I'm sure of it. But maybe there is some layer of additional game-specific decryption for the BO2 binary program (runtime) files... Anyway it's not really expected for these people to leave it in plain sight directly in the main ELF file.
Don't have the full BO2 to play with. But might download the latest game update and try to poke around in again in that one... Probably be unsuccessful (again).