66w ago - Hi sceners, today I have a nice little preview video for you of a new alphabetical sort XMB hack for AC1D CFW.
You may ask now what's the diff to bahamuloard's txt editing one? Well you will see in the video but I'll also explain it here. First his one is a txt edit where mostly on the PS3 txt files are reflections of definitions not real definition files.
Then he edits 3 definitions and the PS3 for sure will rewrite minimum 2 off them and in most case she overwrite all 3. I needed hours of tries to get it only for one time working and even then it doesn't worked for the ALL mode in the game category.
So this hack is real and work for all three modes: Format, Tags and All. Also it works for the other categories like Video or Photo.
I hope for a Beta release of AC1D CFW within the next 1 or two weeks. I'm still working on the convert of Retail 2 Debug consoles and also on the PS3 3.6+ game support. And now enjoy the video and stay tuned.
Have Fun -cfwprpht-
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!
As Nabnab sayed this is not all info needed. So most user wont be able to redo in this stage. We do this for a good reason. 3.6+ games will be a feature of our CFW when its done and CFW released we will give all infos out so that others can implement in there CFW or to do what ever they want with it.
Don't expect too much from me about the masterkey.
I suspected many different process to boot 3.60+ Games on older firmware and also some other stuff related to the internal emulation (PSX/PSP/PS2)
Have many theory about the dongle but i'm gonna explain something.
1-Many Official Game had standart self renamed to EBOOT.BIN (not even npdrm) you can easily unself them (and fix the encrypted section)
2-Patch the header from the official eboot.bin -> (self) and they don't make own eboot from this way, they patch the header to be work on a 3.55 Special CFW (allow to load specific stuff related to the CELL Execution)
3-the dongle = emulate debug patch dev_flash/payload that allow to boot into the debugger mode -> also to patch in real time (syscall function between usb port/CELL) remember jig generate dongle id
4-also some PS3 Games use specific SDK revision (like i show on a another topic)
5-and for the eboot NPDRM is different -> lv2kernel related to the liblv2.sprx, etc patching it's your answer