ok i want to explain something about this patch : first who really said this eboot wasn't encrypted with 3.60 keys ? i can see the 3.60 key is required and someone decrypted it with 3.60 key and then encrypt it with lower version key.
that's all and don't forget it that sony is not stupid.
good luck and thanks boss for the news.
well it's a debug update so it's not encrypted... 3.60 or not.. The only thing is the EBOOT is compiled with 3.60 SDK if you look at headers at the end, BUT maybe it will still work fine on 3.55 (just like 3.50 SDK games all work on 3.41)
this eboot is only for disc and is not for update then it's not for debug/ retail update (It's really easy to understand for a ps3 dev)
i can see the 3.60 keys are needed and you and everyone else can test it and see it's not working.. then he have 3.60 keys.
retail = no go because it's 3.60.
since this eboot is compiled with 3.60, unself.exe EBOOT.BIN then signing it isn't enough (else you get the good old 8001003c error that you get when using 3.50+ eboots unselfed on 3.41).
Whatever was done to 3.50 eboots to work on 3.41 and prevent 8001003c error need to be done here, and I don't remember the trick, but Belmondo & the other guy should be able to sign it properly... And if the game doesnt need any 3.60 bins, then it should work on 3.55.