Originally Posted by vikviper
by the way, I searched more information about this kind of installation, and I noticed that the original instructions (contrary to downgrade procedure) say to enter recovery.
I thought about it and it makes sense since I expect exting FSM would be impossible on a FW superior to 3.55
Am I wrong?
So the correct procedure would be to install Rogero 4.30 v2.05 in _recovery_ (NOT FSM) after starting console with NOR patched with Three musketeers' patches.
Thank you for your patience, but it seems there's a lot less public infos about this procedure compared with what's available for "normal" downgrade.
PS Rogero is my myth. Not only it gives us a great work, but he's also very very kind and available!
just to give you some quick answers:
- You can patch the NOR with three Muskteteers Patch, Flash it, then start PS3 with connect controller message, and install Rogero CFW4.30 v2.05 from a normal USB directly (no FSM needed at all) this works if the PS3 is on OFW <= 4.30, if the PS3 is on 4.31 then you need the old patches for 3.55 coreos + FSM install ( also use Rogero 4.30 v2.05 from FSM directly )
- another answer is YES you can exit FSM fine after installing Rogero CFW4.30 v2.05 (it have the patch needed to exit FSM)
Also, a new version of the PS3 Auto Nor Patcher is in the work with a new CFW v2.06 that will make the downgrading procedure very simple ( and will be compatible also for PS3's on OFW4.31 with Factory version 3.56, no FSM will be needed to any downgrade anymore )
************* [ - Post Merged - ] *************
Originally Posted by haxxxen
i am looking at the xmb mods especially about the install pkg in app_home, which i think btw is a nice hack
can you tell me what it is about " root_for_BDU" in explore_category_game.xml? and why do you have used gamedebug 2 times.
these changes were needed to add the 2 nodes [app_home] and [Install Package Files] to the retail XMB.
does this make the install pkg appear in app_home?
No, the above modifications are not related to the IPF that appears on [app_home], what makes it appear is the redirection from a special payload injected into LV2_kernel and poked at boot time into memory