This will bring the "/app_home/GAME" and "Install PKG" options back.
3. In "/vsh/resource/explore/xmb/category_psn.xml" switch "root" and "tool_root".
This will add Title Store previews in the network section.
4. In "/sys/external" you grab liblv2dbg_for_dex from a debug unit and rename it liblv2dbg_for_cex. Replace liblv2dbg_for_cex with your new one and also add the debug liblv2dbg_for_dex.
Now you also have the debug options enabled. I don't know how to show up the debug options icon yet, but you can modify the settings via the registry.
How2 Handle Debug Options Without Icon
All information should be free. So here another part of the Custom Firmware research.
My previous post already explained some changes they enable. One nice one I didn't mention yet is, that it activates the Debug Options.
The options are enabled now, just the icon is missing. But there is a different way you can handle them. As we already knew, the xregistry.sys (dev_flash2/etc) stores all actual settings.
With the changes mentioned in last post, if you tried those; you may have noticed a debug message in the upper right corner. This actually proves the debug options are unlocked to use.
Just extract the xregistry.sys now and find the debug options. Activate them with a 1 instead a 0. I didn't test all so far, but seems most is fine.
Needa give credits to iQD, KrisAbsinthe, Stoker25 and Comgenie."
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've been thinking about SKFU's CFW Research and came up with this: http://thexcellerator.blogspot.com/
Well, here it is, some PS3 Downgrade Speculation.
OK, well I got think after SKFU's post when he said "We need to find a way to edit the flash directly..."
so I came up with this.
When the PS3 updates, it follows 2 main steps:
1) It copies data from PS3UPDAT.PUP to the HDD.
2) It then sets a boot flag to an "Update Phase/Mode" and then restarts and updates the flash.
If we copy our own update data to HDD, in the correct spot (I assume, it would be the contents of the PUP file, but this will need further research...), and if we can then get the PS3 to change it's boot flag, we could get it to install any Firmware we like. The spoofing side of things comes from editing the SDKHeader.bin in the PUP contents.
So, how do edit the bootflags, is the main question?
It wouldn't be a kind of PS3 GParted LiveCD...
We know that users 'could' edit bootflags (or certain ones) through the DefaultOS option in Firmwares 3.15 and below. They must be stored in the Registry (xRegistry.sys in /dev_flash2/). I'll need someone with Firmware 3.15 or below to tell me the Registry 'Key', so it can be added to a PS3 registry over 3.15...
If we can get the bootflag setting for this update phase/mode, we could make our PS3 write whatever firmware we wanted to the flash, including 3.41 on top of 3.41 with the firmware ID of 3.50, so the PS3 can go online. Does this mean that we could, in theory make the PS3 boot a OS from External HDD? Possibly boot our own flash from it (already done with JaiCraB's Firmware Loader, but still could have interesting possibilities!)
But how do we know the PS3 uses bootflags?
When I was messing with JaiCraB's Firmware Loader, when it messed up, it gave the HDD error message (anyone who's used it will know what I'm talking about!). Anyway, first time this happened to me, I switched off my PS3 and turned it on. The message still came up! Once I followed it through and restarted how it told me to, the PS3 booted up GameOS normally. At the time I thought nothing of it, but when I started thinking about this method, this makes bootflags of some sort seem like an obvious conclusion...
So, to recap!
I need someone with firmware 3.15 or below with jailbreak abilities, to tell me the 'Key' in xRegistry.sys for the DefaultOS menu, so it can be changed on firmware ABOVE 3.15...