According to RichDevX's Twitter (linked above), Hellcat plans to release an updated Homebrewed PS3 SFO Editor in approximately 48 hours.
This comes roughly two years after the PS3 BRDGen Team released a similar application dubbed SFO-Edit v1.0.
According to the pictures (below), the homebrew PS3 System File Editor v0.80 will attempt to reproduce the functionality that Sony's PS3Gen (ps3sys.exe specifically) offers for SFO extension files... allowing you to view, edit, and save PARAM.SFO files.
We will update this post when it's actually released of course.
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
No you could not, ever since 2.10 you can no longer use infectus to downgrade even if you possess a nand dump from your own ps3 (not to mention that the new ps3s have /dev_flash stored on the hdd), beside even if you could, can you imagine the hassle it would be to do that all the time ?
Yes you could but then what would be the point ? There would be more efficient ways of running backups then.
Aren't you forgetting something ? The bluray disc binaries aren't signed to run from the hard disc and even if they were, the paths still point to dev_bdvd
beside the loading speed wouldn't be that better considering most games sport hdd installs, so that excuse holds on psp but certainly not on ps3.
u have documents certified it?always talk but never with documents
A log is worth more than a thousand words (see below), but perhaps you could just install something on 2.80+ and decrypt the harddrive, then you will figure it out. And of course there are not any kind of public documentation regarding this point. It is not like sony is handling a ps3 wiki.
Pointless ? No, not necessarily. If developers could have access to save games... Maybe a buffer overflow in a certain game could result in running unsigned code. Remember GTA: LCS or Lumines on the PSP ? Gripshift ?
Well, we could use that Infectus something-something to go back to 2.70 or similar and replace .sfo files at will !
Could it be viewable with kernel privileges ? Once we do something with those modified .sfo files, of course.
Not if you buy an external HDD (which are pretty cheap now). You could transfer the backups to the internal HDD and let the PS3 encrypt the data on the fly. But my best bet would be a "redirection" of the BluRay drive to an SSD (1ms access time). Even tho their a bit pricey, they will probably provide much much better loading speeds than the BR drive. Again, kinda like the PSP with the UMD format. Games would load faster and perform better.
What? On the Wii there is no single document that give infos about a .tik/.tmd/.cert and team twiizers have to unlock the secrets by here own. By the way he is talking about the PS3 not the PSP.Becouse the PSP dont have a hdd as you, for sure, know.
At least as long we dont have a way to fake sign the puplic key or get hands on it trough hacking/exploiting the hardware or some other ways , we cant test it.
Best way would be to alter a .pkg before installing it.For what i have seen the file sys of a WAD from the Wii and a PKG of the PS3 is quite the same.Sure a few things are diff like SHA1 for Wii vs. SHA256 for PS3.
What for the Wii will be the .tik and .tmd will be the param.sfo for the PS3.To think it could be simply swapped without (maybe) re-signing or without (maybe) altering a specific file would be to easy. (We talk off the files from the HDD!!)