I think we have to use the unfself of the SDK to decrypt the EBOOT.
When you run the fself tool on the Driver: San Francisco EBOOT then it returns no errors and generates an ELF file which is different to the BIN file. Then I looked into the ELF file with a HEX editor but I don`t know how a ELF file has to look be.
Well if its decrypted youll see a lot more zeroes all throughout the file. Also in the text string you should be able to find (via search) 13 BC C5 F6 which is the sys_proc_param info meaning the sdk version 3.40, 3.50, 3.60
also if in readself the metadata is unencrypted thats good.
Well if its decrypted youll see a lot more zeroes all throughout the file. Also in the text string you should be able to find (via search) 13 BC C5 F6 which is the sys_proc_param info meaning the sdk version 3.40, 3.50, 3.60
also if in readself the metadata is unencrypted thats good.
okay then it`s encrypted.
Hm perhabs we have to generate a key file of the masterdisc key and then use this key file with the unself tool of fail0verflow.
Well it doesn't look like anything too positive is going to come of this really, unless the new keys are involved some way, which it doesn't look like they are.
So in essence, we've got a way of playing games from the last few months, as long as we can somehow grab all the debug eboots, and of course work out how to integrate using them in a CFW, but this doesn't offer anything going forward, assuming Sony block off that access to debug eboots......I think I'm right in stating all this....?
i have to diagree i think getting caught up on all the gmaes we cant play for the last 6 months is very pozitive development, even if they dont have the keys , so what it is good for a temporary solution ,like when everyone was asking"will this let me play gt5? "
it got us through untill another solution presented itself, the same will happen again if this isnt the final solution, (oopps that did sound good)
then one will cone eventually and this will be good enough till then, but you are also assuming that they a) didnt use keys for this , and b)that if they didnt use key and are getting leaked files from sony, your assuming that sony doesnt have a rodent problem ,
everyone assumes that its someone with a dev box , and sony can just stop it, but that is more speculation too, it could be a mole, a dev who is selling these leaks to this team, maybe they have already worked a deal out, so even if it isnt the key , we can not just assume that sony can just find the leak and stop it, cause that may not be the case at all ,
It was the reason I bought one myself, spent $50 and it didn't work as well as any of the clones I had :lol: I don't blame anyone as I don't have to believe anyone as I am a grown man and made the choice to get one before they were gone. Silly mistake but it happens to the best of us.
PS3 CECH-25001 4.30.2 REX 1tb iNt & 2tb eXT MM 4.20.04 Xbox 360 Slim with Dual NOR/HDD Trinity 250gb Stock & 1tb RGH using Squirt 360
Why bother even asking, he'll update us I'm sure if he has any more information worth updating....
It is interesting though, obviously Gary knows about all this, and he's informed us it's going international etc.....so what does he think about all the info that's come about with reversing etc, it's almost like he has a conflict of interests
some ex-hacker and release scene member has gotten the 5 games to work with kmeaw from internal hd and he has posted a video in a private german dev board that proofs it. he is trying now to get ALL 3.60 eboots to work startin with battlefield 3.
any chance you can get the video and post it so we can check it out
Originally Posted by SiLENTGame
