Advanced Power Options v1.11 (CFW & HEN)

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

Download
Overview Extra info Updates (9) Reviews (1) History Discussion
DeViL303 said:
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.
Click to expand...
I'm interested in creating power options for OFW. The turnoff file will need to be researched a little more so we have a better understanding.

Hard reboot is possible, it's a parameter in the shutdown syscall: +syscall(sc_sm_shutdown,soft_reboot,0,0,0,0,0,0,0)

Reload XMB is probably possible somehow, I haven't looked into it at all but it should be doable.
 
lmn7 said:
I'm interested in creating power options for OFW. The turnoff file will need to be researched a little more so we have a better understanding.

Hard reboot is possible, it's a parameter in the shutdown syscall: +syscall(sc_sm_shutdown,soft_reboot,0,0,0,0,0,0,0)

Reload XMB is probably possible somehow, I haven't looked into it at all but it should be doable.
Click to expand...
Cool, Well if you want, use my xml from this as a template , poweroff is already set up, and the menus , and the icons, all that needs adding is the js really in place of current actions. Or create your own completely, whatever, up to you sure. I have already had a request on youtube for a HAN version.
 
sandungas said:
I guess thre are some more like this, intended to trigger some "special boot" modes :)
Click to expand...
We could probably find the list if we decrypted the right file, they are probably all referenced in one place. What file could possibly be checking for those do you think, where to look?
 
DeViL303 said:
We could probably find the list if we decrypted the right file, they are probably all referenced in one place. What file could possibly be checking for those do you think, where to look?
Click to expand...
Dont know, that was something posted in wiki by @mysis
He doesnt uses to join the forum much, but im quoting him just incase he have some ideas to boot PS3 in other modes
 
Joonie said:
that's called system crash... :P
Click to expand...

I am thinking, that by calling an rco that doesnt exist, its not really a crash is it? It seems like a crash to us, but the ps3 is really doing exactly what its meant to, Basically if it looks for FW file that should be there, but it isnt, then reboot into recovery screen. It probably uses same flag as mysis does.

So really I could remove the NOR only option, and just use the "look for rco that doesnt exist" option as a universal option, and it would be fine, what do you think?

This will also work on OFW if you delete the strviewer_plugin.rco
 
He seems to be mounting the main HDD and writing directly to the partition, see below:

Code: 
int fs_check()
{
    int ret;
    ret = cellFsUtilMount("CELL_FS_UTILITY:HDD0","CELL_FS_SIMPLEFS","/dev_simple_hdd0",0,0,0,0);
    if(ret != CELL_OK)
    {
        notify("HDD Mount Error: %x",ret);
        return ret;
    }   
    else
    {
        int fd;
        ret = cellFsOpen("/dev_simple_hdd0",CELL_FS_O_RDWR, &fd,0,0);
        if(ret != CELL_OK)
        {
            notify("HDD Open Error: %x",ret);
            return ret;
        }   
        else
        {
            uint64_t pos;
            cellFsLseek(fd,0x10520,0,&pos);
    
            int buf;
            uint64_t nrw;
            cellFsRead(fd,&buf,4,&nrw);

            buf = buf | 4;

            cellFsLseek(fd,0x10520,0,&pos);

            cellFsWrite(fd,&buf,4,&nrw);

            cellFsClose(fd);
        }
        cellFsUtilUnMount("/dev_simple_hdd0",0);
        return CELL_OK;
    }
}

Not sure if it's possible with HAN, don't think any current tools do this.
 
DeViL303 said:
I am thinking, that by calling an rco that doesnt exist, its not really a crash is it? It seems like a crash to us, but the ps3 is really doing exactly what its meant to, Basically if it looks for FW file that should be there, but it isnt, then reboot into recovery screen. It probably uses same flag as mysis does.

So really I could remove the NOR only option, and just use the "look for rco that doesnt exist" option as a universal option, and it would be fine, what do you think?

This will also work on OFW if you delete the strviewer_plugin.rco
Click to expand...

well VSH panics and calls recovery mode, not sure how you would define..
 
Its like a planned crash IMO, not really harmful to the hardware or anything, or do you think it could be? like no harm to do it every so often. :)

"Panics" puts too emotion on it, its a planned re-action to a situation in a way.
 
Joonie said:
well VSH panics and calls recovery mode, not sure how you would define..
Click to expand...
Yeah, is a crash :D
I dont think is harmful though... the only harmful crashes are the ones that does an abrut "power cut" (this is when you hear a "click" noise coming from the hdd)
That "click" noise of the hdd could create bad sectors

Btw @DeViL303 you can check which .sprx are loaded at boot and his associated .rco in this list:
https://www.psdevwiki.com/ps3/Template:XMB_Indexed_Modules

Decrypt xmb_plugin.sprx (or xmb_ingame.sprx) with scetool.exe and open it in HxD
Then search for one of that names from the wiki page
This search is going to take you to an area of the file where are listed all them together and consecutivelly
It seems to be a "table" inside the file structure specific to store it

*By modifying the info in that list you could make some magic tricks ;)
*As example... rename xai_plugin.sprx by cfw_plugin.sprx (not sure if this would work though, im just shooting an idea for an easy modification of the list)
 
Last edited:
kozarovv said:
Yeah but proper way to launch it will be use syscall 15, since i patched LV2 function that is called on error to display full recovery. There is no need for that, as there seems to exist function that do this without modding. Just need to be called.
Click to expand...

Can't wait to use that :)
 
Joonie said:
Can't wait to use that :)
Click to expand...
Can't wait until you implement that :D Option that i did resulted to be risky, and not fully working. But i know why, if anyone want to mess with this, keep in mind that can put you in a recovery loop. That happen because normal recovery not clean error flag on eeprom. That's why we need to call that second function instead of use my hacky way. Ok so here is what i did (4.84 cex)

I patched param in LV2 create_process_emer_init_self_vflash_recovery, to ones used in create_process_emer_init_self so i patched r4 to pass param with --mode=safe instead of NULL. So when i set error flag in eeprom (xai), then create_process_emer_init_self_vflash_recovery was called like usual, but this time with additional param.

Since now i'm sure that param --mode=safe is used to show full recovery, i know that we probably can just use create_process_emer_init_self from LV2 to run recovery. EDIT: Because that function originally use it. No need to patch function then.
Params for that function are: r3 = *proc_obj, r4 = shut_down_flag, 0(no) 1(yes)
Offset: 0x26C4F0

Just calling it from syscall 15 should be enough.
Direct patch i did to get that recovery (keep in mind that you can lost HDD data, and get into loop) E8 82 17 E0 on 0x27C454 (in file, not memory).
 
To get better view what i'm talking about, i suggest to look into @3141card LV2 reversed files.
Edit: Oh, and keep in mind that menu launched by that hacky way wasn't fully functional. Only option 5, and 6 worked. Exactly 6, after 5. But i think that's because way i launched it.
 
Last edited:
Triple post, i will merge later :)

That's how it is looking for now

Keep in mind that can't be patched dynamically, and you can't load external LV2. Since LV2 is loader for a moment on reboot to load emer_init, so eventual patch need to be done in CFW.
Like you can see at 0:50 option 4 is not working, this time i was able to get out to xmb with usage of old rebug install error. Updater cleaned flag, so console booted to XMB after that. And now the best part, started to rebuilding DB like i selected earlier. :)
 
@kozarovv @Joonie Is there another flag for this error I wonder? Or is PS3 counting number of crashes and shows this one every so often, because I get this sometimes, and not other times, even when I have crashed the ps3 in exact same way? If the PS3 is counting, where?



upload_2019-4-6_22-58-30.png
 
You must log in or register to reply here.

Similar threads

Back
Top