IndianCheese
January 5th, 2006, 23:53
Well, I was EXTRA bored today at school and came up with a wonderful idea. You are gonna need coding skills though. This may be a bit hard to follow. Also, this involves decompiling a PBP, so you need to figure that out as well.
Retrieve 2.60 update. Use PBP unpacker to trash DATA.PSAR and change the update version to 3.00. Repack the update. Decompile the update. Trash "main.c". Code a new "main.c" that is a bootloader that runs "EBOOT2.PBP" from the same folder it is in. Recompile the update. Place in PSP\GAME\UPDATE along with homebrew game. Rename the homebrew game "EBOOT2.PBP". Run bootloader from PSP menu.
That is as simple as I can put it. As long as the Sony signature is not in "main.c", it will get recompiled. The reason that I am sure that the signature is in the DATA.PSP is because of the fact that these things can occur and the update will still run: ICON0.PNG can be replaced, PARAM.SFO cannot contain this type of information, and if DATA.PSAR is added to a non-KXploited homebrew EBOOT, it will not run on 1.50.
So there you have it. I'm getting better at this!
Retrieve 2.60 update. Use PBP unpacker to trash DATA.PSAR and change the update version to 3.00. Repack the update. Decompile the update. Trash "main.c". Code a new "main.c" that is a bootloader that runs "EBOOT2.PBP" from the same folder it is in. Recompile the update. Place in PSP\GAME\UPDATE along with homebrew game. Rename the homebrew game "EBOOT2.PBP". Run bootloader from PSP menu.
That is as simple as I can put it. As long as the Sony signature is not in "main.c", it will get recompiled. The reason that I am sure that the signature is in the DATA.PSP is because of the fact that these things can occur and the update will still run: ICON0.PNG can be replaced, PARAM.SFO cannot contain this type of information, and if DATA.PSAR is added to a non-KXploited homebrew EBOOT, it will not run on 1.50.
So there you have it. I'm getting better at this!