Advanced Power Options v1.11 (CFW & HEN)

PS3 [RELEASE] Advanced Power Options v1.11 (CFW & HEN) v1.11

Well, if you want to start on it, do you know how create new entries in the language xmls that are inside an rco? And do you know how to create new ones for all the entries in this mod? :)

Also you would need to know how to add all languages to param.sfos, as some titles are in those. this is possible too. webman updater does it.
 
@Joonie, do you know if its possible to make a pkg that boots into recovery menu, or any way to do this without holding the buttons and rebooting twice? At the moment the recovery mode option in this mod uses mysis code to boot into recovery mode, which is really the "install firmware screen" which is not so useful as the menu.
 
@Joonie, do you know if its possible to make a pkg that boots into recovery menu, or any way to do this without holding the buttons and rebooting twice? At the moment the recovery mode option in this mod uses mysis code to boot into recovery mode, which is really the "install firmware screen" which is not so useful as the menu.

So far there's no homebrew that triggers recovery mode fully. also that eeprom flag doesn't work on NAND either..
 
that's called system crash... :P

From bug to feature.


Now with NAND support!

upload_2019-4-5_23-10-35.png


Im not going to release this, obviously, but for the sake of research, this is how you would crash the system. This exact code will not work with CFW Power Options installed, so its safe. But on normal CFW/OFW, if you call a plugin that does not exist, like videodownloader_plugin.sprx, well if that plugin has no matching rco, it will crash system and end up at "connect the controller using a usb cable" screen, Just like boot to recovery mode in cfw settings.

In theory this could be used on HAN to achieve same thing, but really its probably not good thing to do, and the feature is not very useful anyway. :)


upload_2019-4-6_0-11-33.png
 
Last edited:
Hello! I tried this mod, I also did a quick translation for me, even if I could not translate the "relod xmb" entry because there are no xml ... I still found a small bug, the "reboot into recovery mode" option does not it works, after having selected it does not execute any command ... this problem is present in v 1.03 and 1.04, the other versions I have not tried ...
 
Hello! I tried this mod, I also did a quick translation for me, even if I could not translate the "relod xmb" entry because there are no xml ... I still found a small bug, the "reboot into recovery mode" option does not it works, after having selected it does not execute any command ... this problem is present in v 1.03 and 1.04, the other versions I have not tried ...
Are you on a NAND by any chance? I forgot to put in the info text that that option will only work on NOR. I do know a way to trigger that recovery menu on all console types, but it involves crashing system by calling a missing plugin, so not a good way to do it, although it works perfectly every time, and i suspect it does not cause any damage, its just a system panic due to file not existing.

I am not going to release it though, See the image above your post. a joke. :)

BTW: If you want to translate the Reload XMB item, or the Boot OtherOS title on XMB, you need to do it in the PARAM.SFO of the included packages.


EDIT: actually, you are right, there is an issue with that option even on NOR, thanks for report, i will check it out.
 
I am not going to release it though, See the image above your post. a joke. :)
You are absolutely releasing this! Just saved my life. Me and a few others have a NAND console with the power/eject buttons broken. We use some really funny ways to turn on the console. At the moment it is impossible to trigger safe mode from the hardware aspect so if any wrong XMB mods without crashing and firmware can't be installed from XMB we are stuck for eternity.
This means that only triggering safe mode from software could work. The current solution was only working on NOR and not NAND :culpability:
You must include this since it is the only way for us, the unlucky owners of NAND with broken button clips to go into safe mode.
 
Oh, well I can of course release it, if its useful to someone. Did not know that.

You so you know, this only works to get to this screen, the same as the current "NOR only" recovery option, It does not actually bring up the recovery MENU unfortunately, is this still useful to you if its just a button to access this screen:


upload_2019-4-6_17-7-38.png
 
Oh, well I can of course release it, if its useful to someone. Did not know that.

You so you know, this only works to get to this screen, the same as the current "NOR only" recovery option, It does not actually bring up the recovery MENU unfortunately, is this still useful to you if its just a button to access this screen:


View attachment 16198
I really need that mod now :) Can you send it?
 
I really need that mod now :) Can you send it?

Can you test this.

To enable the NAND option you need to delete strviewer_plugin.rco manaully, its not used for anything really, so wont make any difference, but it is enoough to use this option to trigger recovery.

There might be a better way if i can find a missing plugin that has no rco still in the firmware, but for now they only seemed to remove sprx files, and all rcos are still in, except videodownloader which Im using. I bet there is another one though, it just requires some research.

upload_2019-4-6_17-45-39.png


@DeViL303 does your crash method bring the full recovery menu?
No, same as CFW settings, see screen in image above a few posts back.
 

Attachments

Im guessing... there is one test that worths to be explored
Some of the boot modes are dependand of a file created on hdd, basically, you do something in XMB and that creates a file... then the PS3 reboots, reads that file and initiates the PS3 in that special mode

So im wondering if the ON/EJECT button combo is creating a file on hdd... but nobody realized because is cleaned up almost instantly

The theory of how is working is:
1) On/eject button combo (1st try)
2) The file is created
3) PS3 powers off
4) On/eject button combo (2nd try)
5) The file is loaded
6) PS3 powers on into recovery mode

So im thinking in disconnecting the hdd in step 3... connect it to a PC, and use the hdd tool to decrypt hdd contents
And try to see if there is a new file in hdd
 
Im guessing... there is one test that worths to be explored
Some of the boot modes are dependand of a file created on hdd, basically, you do something in XMB and that creates a file... then the PS3 reboots, reads that file and initiates the PS3 in that special mode

So im wondering if the ON/EJECT button combo is creating a file on hdd... but nobody realized because is cleaned up almost instantly

The theory of how is working is:
1) On/eject button combo (1st try)
2) The file is created
3) PS3 powers off
4) On/eject button combo (2nd try)
5) The file is loaded
6) PS3 powers on into recovery mode

So im thinking in disconnecting the hdd in step 3... connect it to a PC, and use the hdd tool to decrypt hdd contents
And try to see if there is a new file in hdd
This seems likely because this is what happens when rebuilding database for example. There is a file /dev_hdd0/tmp/turnoff, the contents of this file is used as a corrupted file system flag (the message saying the PS3 was not turned off properly). It is most likely used for other things too.
 
So on HAN, we can add db.err and turnoff, we could make a "HAN Power Options" between us if you wanted to @lmn7 .

We have offline Reboot, we can use the poweroff plugin with no confirmation hack on OFW, we have database rebuild with db.err, we have file system check with turnoff, and we have recovery mode if we corrupt strviewer_plugin.rco with a dummy file and call that plugin. So we have the full set just like CFW, except for hard reboot. but that is not required , and no reload xmb/otheros as they are apps.

We could use one of those pkgs to install files to dev_blind even.
 
Back
Top