Ultimate Toolbox

PS3 [RELEASE] ★ Ultimate Toolbox v2.03 - It Only Does Everything! v2.03 (FW 4.84 - 4.91)

@DeViL303 Some new ideas:

1- Due the large size of the PKG, for future releases you should consider to restructure the tool in a base PKG + modular addons (so the users only install the modules needed)

2- For Firmware category:
- Add option for swap Cobra 8.3 normal / debug (the one used with socat)
- Add option for PS2 Netemu selector => https://store.brewology.com/ahomebrew.php?brewid=315
- Maybe an option for install some debug files (if possible). Something like was done in CFW 487 Pro.

3- Option for delete category files from disk (some files once they are installed, the others are not longer needed)
 
Thanks for the ideas, much appreciated.
@DeViL303 Some new ideas:

1- Due the large size of the PKG, for future releases you should consider to restructure the tool in a base PKG + modular addons (so the users only install the modules needed)
You are right, I will consider that, My thinking is that a few hundred MB is not much in 2021 but I get your point. All the visual customizations could be included in an extra download for starters..
2- For Firmware category:
- Add option for swap Cobra 8.3 normal / debug (the one used with socat)
That would be cool to have alright and I have considered it, but it would make the toolbox firmware dependent. Also I would be afraid a user would install the wrong payload and brick. On NOR consoles you can recover this kind of brick by formatting the HDD, On NAND consoles this is a full brick afaik so its kind of dangerous. Or is there a way to avoid this issue?
Will do. Good idea.
- Maybe an option for install some debug files (if possible). Something like was done in CFW 487 Pro.
I will look into this for sure and do some testing. My initial plan was to avoid including sprx files as much as possible as this has caused me issues in the past, Cobra hashes etc.
3- Option for delete category files from disk (some files once they are installed, the others are not longer needed)
Maybe yes, I will look into it, but again my thinking is that few hundred MB is not going to be missed in 2021. Users can use the File Explorer to delete files too.
 
That would be cool to have alright and I have considered it, but it would make the toolbox firmware dependent. Also I would be afraid a user would install the wrong payload and brick. On NOR consoles you can recover this kind of brick by formatting the HDD, On NAND consoles this is a full brick afaik so its kind of dangerous. Or is there a way to avoid this issue?

I will look into this for sure and do some testing. My initial plan was to avoid including sprx files as much as possible as this has caused me issues in the past, Cobra hashes etc.
Yes that would make the firmware dependent. This tool already modifies files in /dev_flash, so IMO currently it's already risky for NAND consoles.

Maybe you could include the firmware dependent features in a separate addon. If the user decides to install it, it's not your fault if you give the proper instructions.

Maybe yes, I will look into it, but again my thinking is that few hundred MB is not going to be missed in 2021. Users can use the File Explorer to delete files too.

It's just convenient to have the option of delete the files easily. If it's too hard to implement then ignore this suggestion.
 
This issue is that loading the wrong Cobra payload is an instant brick with no recovery menu. All the other files this swaps on flash will not affect the recovery menu on NANDs even if they only partially copy or become corrupted, Cobra payloads are a whole different level of risk.

True, that is an option. Just trying to think of every scenario, for example a user updates the FW after downloading the addon etc.
IIRC Andrews Sebes added an option to install files for specific firmware versions in XMBM+ Installer.

I think you use it for some firmware modifications
 
Nice, that's strange o_O

Here all of them are working lol

Feck they do work. lol, I just figured it out, My custom_render_plugin.rco was modded to allow the coldboot audio to play longer, this was stopping the XMB icons.qrc override from kicking in.

The mods were working for me when I did them myself cos I also modded the coldboot icons.mnus.

I thought maybe you had sent wrong folder at first, my mistake. :)
 
New features coming soon. Now that we can use the music visualizations as a dynamic theme I decided to look at canyon.qrc again. There are 57 presets and we never get to see most of them. Now I have added a new menu to Ultimate Toolbox that can force each preset. Some are very cool and make a nice XMB background.

This basically add 57 new dynamic themes using these official presets! :D

I will be adding a menu for forcing all the presets in lines.qrc too. :)


1.jpg 2.jpg 3.jpg 4.jpg 5.jpg 6.jpg 7.jpg 8.jpg 9.jpg 10.jpg 11.jpg 12.jpg 13.jpg 14.jpg 15.jpg 16.jpg 17.jpg 18.jpg 19.jpg 20.jpg 21.jpg 22.jpg 23.jpg 24.jpg 25.jpg 26.jpg 27.jpg 28.jpg 29.jpg 30.jpg 31.jpg 32.jpg 33.jpg 34.jpg 35.jpg 36.jpg 37.jpg 38.jpg 39.jpg 40.jpg 41.jpg 42.jpg 43.jpg 44.jpg 45.jpg 46.jpg 47.jpg 48.jpg 49.jpg 50.jpg 51.jpg 52.jpg 53.jpg 54.jpg 55.jpg 56.jpg 57.jpg
 
New Ultimate Toolbox feature allows you to force any of the 18 OFFICIAL lines.qrc presets (overrides) to be used either always, or just in the music player.

On most presets this allows you to get around that annoying color change from boot time to XMB loaded.


screenshot_2012_01_01_02_42_30.jpg


1.jpg 2.jpg 4.jpg 5.jpg 6.jpg 7.jpg 8.jpg 10.jpg 11.jpg 12.jpg 13.jpg 14.jpg 15.jpg 16.jpg 17.jpg 18.jpg
 
Last edited:
New Ultimate Toolbox feature allows you to force any of the 18 lines.qrc presets (overrides) to be used either always, or just in the music player.

On most presets this allows you to get around that annoying color change from boot time to XMB loaded.

Is it possible to use a custom line.qrc for XMB as music player visualization?
 
Is it possible to use a custom line.qrc for XMB as music player visualization?
Yes, there are a few ways.

The way I am doing it here is by using modified qrcs. Each of the 38 options in this new menu installs a special version of the OFFICIAL wave with modified presets to force each official preset in all environments. .

To do what you are saying, to have a CUSTOM wave that has a different preset used for the music player you would need to either create a custom qrc with a modified music_1 preset. OR patch custom_render_plugin.sprx to use a different preset for the music player.

Patching the sprx is the easiest way, this allows you to swap lines.qrc and still have your patch applied, I went with the hard way for my mod so it would remain FW independent. The hard way involved making 38 lines.qrcs with 72 modified mnus in each qrc (over 2700 mnus) :)

If you just want as specific wave style to be used for the music player for yourself I could make you one or patch the sprx for you. Just let me know which lines.qrc or which override you would like.
 
Yes, there are a few ways.

The way I am doing it here is by using modified qrcs. Each of the 38 options in this new menu installs a special version of the OFFICIAL wave with modified presets to force each official preset in all environments. .

To do what you are saying, to have a CUSTOM wave that has a different preset used for the music player you would need to either create a custom qrc with a modified music_1 preset. OR patch custom_render_plugin.sprx to use a different preset for the music player.

Patching the sprx is the easiest way, this allows you to swap lines.qrc and still have your patch applied, I went with the hard way for my mod so it would remain FW independent. The hard way involved making 38 lines.qrcs with 72 modified mnus in each qrc (over 2700 mnus) :)

If you just want as specific wave style to be used for the music player for yourself I could make you one or patch the sprx for you. Just let me know which lines.qrc or which override you would like.

I like the 5th one in orange-black that looks fire.
upload_2021-1-16_16-22-41.png
 
I like the 5th one in orange-black that looks fire.
View attachment 30143
Here is that one, forced to show the same effect on all presets. So you will no longer get that annoying change from coldboot screen to XMB. It will just show the "fire" effect all the time, including in the music player. If you want something changing let me know.
 

Attachments

Here is that one, forced to show the same effect on all presets. So you will no longer get that annoying change from coldboot screen to XMB. It will just show the "fire" effect all the time, including in the music player. If you want something changing let me know.

Thank you. I will try it.

A feature that I miss from the original XMBM+ is the option to delete Trophies folders.

While I was using the XMB File Manager to delete some trophies I noticed this: .bmp .jpg .png files show a preview of the image
but if the extension is in upper case they don't show. If we get XMB File Manager to show .PNG and .JPG it would be a great feature, because it would make easier the identification of the folders because ICON0.PNG, PIC1.PNG, etc. use the extension in uppercase.

I think explore_plugin.sprx is the one that need to be patched, but I'm probably doing something wrong.

Could you check if we can add this feature?


EDIT:
The custom lines.qrc "fire" now works great in the player. It also doesn't break the waves when you exit from the player.

I think other custom waves will need this fix too.

EDIT2:
I found the mistake. I was mapping /dev_blind instead of /dev_flash

explore_plugin.sprx
upload_2021-1-16_17-22-28.png


upload_2021-1-16_17-19-17.png
 
Last edited:
This is the explore_plugin.sprx already patched for Rebug 4.86.1 LITE.
(Anyone in Rebug 4.86 Lite that want to use this mod, the file should be copied in /dev_blind/vsh/module)

I replaced support for preview the rare extensions: .tiff and .jpeg

@Evilnat could you apply this patch in explore_plugin.sprx for final release of Evilnat 4.87.3 ?
upload_2021-1-16_17-27-34.png


I tested it, the patch doesn't break PS2ISO or PSPISO on Rebug 4.86.1 LITE. So no need to change Cobra.
 

Attachments

Last edited:
Yeah, To help mitigate the risk of user error I could add extra warnings in all caps, and double up on the confirmation dialogues so you need to confirm twice after choosing the swap payload option with emphasis put on the fact it can be a hard brick on NANDS.
Even if you use font 72px, red, blinking, with a sound alert and a poison image the users won't read and will install it anyway...:rolling:
 

Similar threads

Back
Top