I have tried to build a UMD master disc with a boot.bin decrypted by PRXdecrypter 2.7a I have some question here: 1. Is it like PS3, UMD master cannot run signed EBOOT.BIN? 2. Some boot.bin work while some of them just hang in a black screen (5.05 eboot)? Any idea why? 3. Is games with OPNSSM.BIN cannot run with the testing tool? haha, I know cfw is a better way, just want to know more about it. Thanks!
Interesting... Tried to master with original eboot without decrypt. The screen is black without error code...
Found that eboot decrypted with A8 FF 08 at 0x10 is playable. More recent eboot with other pattern such as 02 00 08 will give a black screen. Does anyone know about this elf structure and give me suggestion? Thanks
Hi, Is it the old eboots are dynamic elf while eboots > 5.05 are static? Is debug able to load static 02 00 08 elfs? Please help~ Thanks!
Actually newer PSP SDKs have code on one of it's libs to detect if it's running on incorrect version. (decrypted, repacked for lower FW version) Because of that things like "prometeus" (an program/plugin which automatically patch an boot elf on CFW so it works on lower version) exist.
Thanks Oliveria, I have already fixed the problem. After killing a stack of DVD-R, I found that some game EBOOTs retrieve files by their LBA positions instead of file names. If we extract all the files from the UMD image and rebuild it using UMD Image Generator (SCE), the LBAs are changed and the program fails. I have figured out a way to convert UMD9660.iso to USER_L0.IMG (L1 for dual layer) without compromising the file structure. Nearly 100% games work on the Testing Tool as master disc now.
