Correct me if I'm wrong (but don't beat me up too hard), SELFs are supposed to contain some pub keys.
If the "A way" is true, then they would just need this method in order to break the chain and get most 3.6x+ pub keys from 3.55.
This or they just decrypted TB EBOOTs/SELFs and got their pub keys there.
If they were using debug EBOOTs, would they still need to sign/encrypt the SPRX files from the debug release ?
I somehow still have problems running Fifa Street. I patched it and rebuilt my PS3s Database for several times now, it still won't work. That means, it works, but the game kinda freezes (just stuck, XMB works) as soon as I try to play in World Tour Mode (however, the first, initial game right before team creation works).
I'm out of options and things to do...
I also tried installing it on HDD. I'm on REBUG 3.55.
seriously another dongle clone profiteering ... if it takes 10 minutes to make the eboot then release the method so we who already have a dongle can make our own eboots...
if E3 is quick in their releases of patches then it may be worth it but if they are as slack as TB then forget about it...also releasing a few broken or crappy carrots to entice us to the E3 dongle will make us more pissed off than actually helping the scene...
seriously another dongle clone profiteering ... if it takes 10 minutes to make the eboot then release the method so we who already have a dongle can make our own eboots...
if E3 is quick in their releases of patches then it may be worth it but if they are as slack as TB then forget about it...also releasing a few broken or crappy carrots to entice us to the E3 dongle will make us more pissed off than actually helping the scene...
Eboots dont take 10 minutes to make. I used to modify eboots manually in hex with all keys and no other files to mod (except sometimes .sprx and other .selfs or .bins) and those took me about 5-10 minutes when I got really good at it.
The protection now is a lot harder encompasses more files and different file extensions, all the keys aren't known. Even if I explained to you the old way of MANUALLY modifying 3.56 to 3.55/3.41 it would take you at least a week to get it non stop if you even could. It requires linux environment knowledge hex offset reading, metadata decryption etc etc I wont go on because its just boring to most people and this was just the old way of doing it. Like I said security is much tighter now on the ps3 hence no CFW in forever.
PS3 Slim w/ Rebug Rex 4.30.2, 500GB Internal, 1TB/3TB External; PS2 Fat McBoot w/ Hard Drive; Windows 7 x64 Ultimate
Last game finished: Crysis 3 | Currently Playing: Dead Space 3
He is referencing the e3 claims in the original news post :
Cool then we should have about 75 eboots by now from them. Takes them "10 minutes to mod the eboot" but 18 hours to actually do it.
Well if thats what they publicly claim let's see how many they release. I don't doubt them like I said I could do it in ten minutes when I knew the method. So we'll see.
Wait a second I do doubt them, if this is the same E3 team that makes the E3 flasher which claimed a few months before True Blue came out their flasher would dual boot CFW 3.55 and then current OFW and then failed for many months but kept making promises. They prolly do have the method but cracking every eboot with files in ten minutes? Take a look at the Ghost Recon eboot that has over 300 SDAT files that needed to be patched. Unless they have 150 employees cracking each SDAT individually at the same time or have a made a "universal" automated patcher that works for all eboots I doubt they'll crack every eboot and files that need to be patched in 10 minutes.
Last edited by PatrickBatman; 06-15-2012 at 12:38 AM.
PS3 Slim w/ Rebug Rex 4.30.2, 500GB Internal, 1TB/3TB External; PS2 Fat McBoot w/ Hard Drive; Windows 7 x64 Ultimate
Last game finished: Crysis 3 | Currently Playing: Dead Space 3
Cool then we should have about 75 eboots by now from them. Takes them "10 minutes to mod the eboot" but 18 hours to actually do it.
Well if thats what they publicly claim let's see how many they release. I don't doubt them like I said I could do it in ten minutes when I knew the method. So we'll see.
Wait a second I do doubt them, if this is the same E3 team that makes the E3 flasher which claimed a few months before True Blue came out their flasher would dual boot CFW 3.55 and then current OFW and then failed for many months but kept making promises. They prolly do have the method but cracking every eboot with files in ten minutes? Take a look at the Ghost Recon eboot that has over 300 SDAT files that needed to be patched. Unless they have 150 employees cracking each SDAT individually at the same time or have a made a "universal" automated patcher that works for all eboots I doubt they'll crack every eboot and files that need to be patched in 10 minutes.
They have promised a lot but never completed. For example E3 NAND Flasher and a E3 MOVE SUIT....
People are all talking about eboots but they can also do something different. Patching those eboots / sprx's is because the decryption key is not available in 3.55.
But when they release a new CFW based on 4.20 or something (since they have the keys they can decrypt the firmware's to create CFW's) and tied that CFW to a special dongle, and put all the functions in the CFW they don't have to recreate every patch. I'm not sure if this is possible but this would save them a lot of work. No more patching of eboots / sprx's since the keys and functions are in the firmware.
This way they provide a dongle + CFW and maybe update CFW when sony releases new one and solve a lot of problems. But like I said don't know if this is possible.
People are all talking about eboots but they can also do something different. Patching those eboots / sprx's is because the decryption key is not available in 3.55.
But when they release a new CFW based on 4.20 or something (since they have the keys they can decrypt the firmware's to create CFW's) and tied that CFW to a special dongle, and put all the functions in the CFW they don't have to recreate every patch. I'm not sure if this is possible but this would save them a lot of work. No more patching of eboots / sprx's since the keys and functions are in the firmware.
This way they provide a dongle + CFW and maybe update CFW when sony releases new one and solve a lot of problems. But like I said don't know if this is possible.
IT IS what i think i too, if they issue a CFW 4.xx will surely be accompanied by another dongle, or only work with their dongle inserted if and when the launch on the market.
To me it seems to me the soup, and if so the DRM there will be always as well as the war of the clones, and True Blue will continue to reign. With regard to TB, i would like to know that end have done those Mushi yellow...
Reply With Quote
Originally Posted by james1510
