The Wii works on the same way, but anyway we can change the whole XMB via the XML's. It was a childs play to add some paths from one XML to another and add additional download paths for contents that before was only download able into one path. (eg PS3HDD or PS3 only games).
In my country nearly all chips that can be used to make a PSGroove are sold out. I still have some ATmega8 chips at home but I need to modify the source to get the thing running.
The LUFA software USB LIB doesn't support ATmega8 so I'm trying to use a other smaller soft USB but I will need some days more until I can compile the first hex.
Therefore, I am putting out these modified FW files for PS3 to let other guys test if you wish.
Be careful what you're doing and don't UPDATE. I tried to block every update option but as I said it's the first time and it's not sure that every thing works like it should. But together we will find it out.
• First download a PS3 FW Dump first (THIS is the one I used) so you can replace the files with the PS3 Acid CFW file linked above, and put only the folders from "PS3 Hacked FW files" on your USB stick into the dev_flash folder. Make sure to not have any additional files on it !!
• Extract the contents of dev_flash2.rar on your desktop. Use the xRegistry app (or PS3 Multi Tool) to edit the your own one and activate the debug options. I have set a bit flag but don't know if it will work in case that every reg file I have don't include one single bit flag. But as SKFU told us I have set a flag instead of a value.
• After that is done, put the xReg back on your PS3. Now insert the USB stick with our CFW and load the files with USB Firm Loader.
Let me know if it works and play around a bit, tell me what is working and what not. Currently only English and German should display ALL Debug options. Support for other languages will follow soon.
Below are a few things of what would be changed:
PS3 Debug Options activated:
• Install PKG
• Chancel Purchase
• Update via HDD
• Delate Update from HDD
• Title Store Preview (Store)
• Title Store Preview (In Game)
• Quick Sign Up
• Performance Bar
• No Memory Limit
• Quick Preview
• Owner Information
• Fake HDD Size
• CORE Dump
• Game Debug
PS3 System Hacks:
• Block Updates
• Block Online Updates
• Block Game Updates
• Unlocked Secret Debug Options
• Unlocked PSP Only (now you can copy PSP only tiles on any media)
• Unlocked Pocketstation
• Unlocked PS2
• Unlocked System Driver Pocketstation
• Unlocked System Driver PS2
I will now continue working on the ATmega8 mod and hope that I can get it small enough.
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!
I guess I misunderstood how the updating process works. I assumed that there was a verification process that could be patched out( in ram using a payload) that if fails stops upating. If so we could, in theory, just unpack a pup, modify the files, repack it and tell the ps3 to update.
You can not simply patch out because its a encrypted file and patching one single bit would break the encryption.
There for we have to use custome payloads and patch the ps3 ram in reall time.
Ok im not so sure about if the lv1,lv2 will be encrypted.But even if not the are placed on a other chip then dev_flash will be and to time we have no access to it.Dumping the lv2 with hb is to time the best we can do.
Let assume the lv2 is not encrypted and we can patch some strings.Then we still first need a way to write to the chip where lv2 will be stored. Knightsolidus have told us that now the lv2, lv1 among with some other system files are stored in the CXD flash but dont have shared the info how to read the CXD.
We have to wait if some one other can find a other way or knightsolidus will share the info with us.Maybe some one will develope a new gen downgrader chip like the infectus it was based on the new infos of knightsolidus.
Is there anyone actively searching for a section in lvl2 /lvl 1 code that would allow unverified updates? Then we code patch out lvl2.bin outside and package it in a pup file and allow the ps3 to write its own doom.
To time the debug options in the category systemconfig are not completely unlocked.The first part is done but more changes need to be done.Before you cant see and select the debug options in the category systemconfig.
Allready usable unlocked options in the ACID CFW are:
*Install Package File
*MCutility (ps1/ps2 memory card)
*Quick Sign Up
*Title Store Preview (ingame)
*Title Store Preview (online)
Kicked out PSN Store from the game category
Dont forget that this cfw and the way to load is still a test !!
Goal is that we later have a cfw wich we can put onto our ps3 and replace the files from internal dev_flash with our hacked one.
This doesnt mean that we dont need a JB any more.We still would need the jb.Because the jb make patches to the lv2.bin wich is our game os and stored on a seperated place.Not in dev_flash.
But maybe we can activate the bd emu sometimes.Then we wouldnt need a bm any more and backuploading could be embended into the cfw.