PS3 Rebug Package Manager (standalone)

Developer Sandungas has released a Standalone version of REBUG's Package Manager , this is the same official version with a few changes in the Installation process for installing on other CFW's other the REBUG. This actually can be done with various tools such as Cobra CFW Tools and XMB Mod Manager (the installation of Package Manager on other non REBUG firmwares), but here is a bit of an explanation in how this process works with a few other minor changes from sandungas, Checkout all the details in quote provided below of this release:

install_package_manager1.png

sandungas said:
Rebug Package Manager (standalone)

Is the same package manager used in all classic rebug firmwares, the most notable modification is the installation method and the modifications made in the provided install_package_files.xml, it has been "unlinked" from the resources inside .rco files (the .xml doesnt loads any custom resource from inside .rco's... this is why is named standalone because is not dependant of any other custom modification)


Features

  • All the custom code is in a separated .xml, easy to implement, manage, mantain, update, etc....
  • All the Rebug Package Manager custom texts has been hardcoded in english in the install_package_files.xml (in vintage rebug versions was harcoded in english inside the .rco's and later harcoded in several languages by joonie inside the .rco's)
  • The rebug red custom PSN icon that appeared in a subfolder inside the "package manager" has been replaced by the default folder icon (originally the icon was loaded from explore_plugin_full.rco)
  • All this means in few words... it can be installed in any CFW past/present/future very easy with a simple edit in the original .xml's


Standalone Installation
Because you are supposed to be in a cfw before installing this, it means you have the item "install package files" in your xmb, is located inside:
dev_flash/vsh/resource/explore/xmb/category_game.xml and category_game_tool2.xml (it can appear several times for all PS3 models CEX/DEX/DECR/ARC)

Step 1.- Make a copy category_game.xml and category_game_tool2.xml and move to PC, open them in notepad++ and search for this "item"
Code:
            <Query
                class="type:x-xmb/folder-pixmap"
                key="seg_package_files"
                src="[URL="http://www.psx-place.com/forum/usertag.php?do=list&action=hash&hash=seg_package_files"]#seg_package_files[/URL] "
                />
Step 2.- Replace by:
Code:
            <Query
                class="type:x-xmb/folder-pixmap"
                key="seg_package_files"
                src="xmb://localhost/%flash/xmb/install_package_files.xml[URL="http://www.psx-place.com/forum/usertag.php?do=list&action=hash&hash=seg_package_files"]#seg_package_files[/URL] "
                />
Step 3.- Save the changes
Step 4.- Copy the modifyed files category_game.xml and category_game_tool2.xml and the provided file install_package_files.xml back to the PS3


Notes


  • In a official DEX XMB (and most cfw) the item "seg_package_files" is placed in the list inmediatly before "seg_gameexit" but you can place it at any other position, as example on top of game column
  • xmb://localhost/ is the function that loads another .xml At the end of the function is used the character # that loads an specific segment from the other .xml %flash is a short form of path: dev_flash/vsh/resource/explore/
  • For testing purposes you can load the file install_package_files.xml from the root of a usb device by using: src="xmb://localhost/dev_usb000/install_package_files.xml#seg_package_files "

Thanks
Team AC1D, Team Rebug, Team XMBM+

Source
: PlayStationHAX.it
 
Now I need to get to my PC to add this to the new 4.70 firmware I am using. Then again I still haven't tried to install XMBM+ yet either but regardless its nice to see this out there for those that don't want all the extra bells and whistles of XMBM+
 
This actually can be done with various tools such as Cobra CFW Tools and XMB Mod Manager (the installation of Package Manager on other non REBUG firmwares)
Well, is not the same like what these apps does... what is different is the overall concept behind it
These apps overwrites the original .xml... so they contains a collection of modifyed .xml's for different firmware versions... and consequently needs to be updated for every new firmware version

The way im adding the install_package_files.xml should work for all firmwares and im only modifying 1 line in the original .xml (is a minimal modification, easy for final users to install, and easy for cfw devs to implement)
 
Last edited:
Hey under Package Manager>Install Package Files>

The internal hdd location doesn't have a title.

I figured out that's because it's omitted in install_package_files.xml because its broken by extra unnecessary code

open that xml,
search for this: <Pair key="title_rsc"><String>msg_tool_hdd0_file</String></Pair>
replace with: <Pair key="title"><String>Internal Hard Drive</String></Pair>

or just use mine
FIXED file: https://mega.nz/#!EEJygAKA!O8gHE1Enul2KS79yff2lfrlFQV6zsOhoa0_O-GRX-5g

PS To be technical it should read PS3(TM) Hard Disk but instead I put Internal Hard Drive because to be honest I was in a hurry and didn't care, so change it to that if you want.
 
Last edited:
Hey under Package Manager>Install Package Files>

The internal hdd location doesn't have a title.

I figured out that's because it's omitted in install_package_files.xml because its broken by extra unnecessary code

open that xml,
search for this: <Pair key="title_rsc"><String>msg_tool_hdd0_file</String></Pair>
replace with: <Pair key="title"><String>Internal Hard Drive</String></Pair>

or just use mine
FIXED file: https://mega.nz/#!EEJygAKA!O8gHE1Enul2KS79yff2lfrlFQV6zsOhoa0_O-GRX-5g

PS To be technical it should read PS3(TM) Hard Disk but instead I put Internal Hard Drive because to be honest I was in a hurry and didn't care, so change it to that if you want.

Here's the ready-made XML files, including a multiMAN-self-writable ZIP, yes a self-writable ZIP file that automates the process, and it has been properly edited:

https://onedrive.live.com/redir?resid=6EAB78A042EC59DE!2166&authkey=!AIOPKBRg_B_avGQ&ithint=file,zip

All credit goes to PatrickBatman, sandungas, Team REBUG et al!
 
Hey under Package Manager>Install Package Files>

The internal hdd location doesn't have a title.

I figured out that's because it's omitted in install_package_files.xml because its broken by extra unnecessary code

open that xml,
search for this: <Pair key="title_rsc"><String>msg_tool_hdd0_file</String></Pair>
replace with: <Pair key="title"><String>Internal Hard Drive</String></Pair>

or just use mine
FIXED file: https://mega.nz/#!EEJygAKA!O8gHE1Enul2KS79yff2lfrlFQV6zsOhoa0_O-GRX-5g

PS To be technical it should read PS3(TM) Hard Disk but instead I put Internal Hard Drive because to be honest I was in a hurry and didn't care, so change it to that if you want.

I believe he was trying to point to a msg text from the rco, that way it would use the system translations. The way you have edited it will only show your English line "Internal Hard Drive" in which I believe Sony changed a while back to read "System Storage"
 
Nice find [MENTION=13550]PatrickBatman[/MENTION], it was actually a bug
What i was trying with this .xml is to remove all links to content inside .rco's... and at the same time to respect rebug package manager mostlly as posible
So the file should not have any title_rsc, neither info_rsc (i just verifyed right now)

In the "classic" rebugs (before joonie started to translate that texts to several languages) rebug was loading that texts in english for all languages, what i did was to take them and "hardcode them" in my .xml... the result is the same english for all but this way the .xml is not accessing the .rco contents (so can be used in any firmware because is not dependant of rco's, it works by itself standalone)

In this sense about respecting rebug classic package manager most as posible... i think is better to replace it by PS3™ Hard Disk because this is what they was using (im verifying it right now too), see here:
t2mWwnm.jpg


Give me a few minutes and i will upload a fixed version following the same principles i used when i made the first version (trying to keep it most close to the original as posible)
 
Thanks Sandungas, I've used Rebug ever since using Kmeaw wasn't plausible anymore. Recently, wanting to unban my console I switched to another CFW (Habib 4.75 Cobra) as that's what's recommended currently for safest PSN access (with Cobra). For some reason Brunolee's XMB Manager MOD wasn't installing Package Manager on 4.75 but everything else worked (perhaps because it's only compatible up to 4.70 thus far) and since he hadn't accessed his Hax account in some time (and wasn't aware of him having an account elsewhere), I decided to take matters into my own hands.

Anyway, I'm glad you took the time to do this as it was a life saver for me :)

EDIT:
PS I didn't actually think that code was unnecessary and was thinking it had to do with a .rco (like bitsb said) was just having a brain fart at the time so couldn't exactly find the words to describe it, was in a rush and figured people wouldn't know what I was talking about anyway, even if I did and wouldn't care just so long as it was fixed.
 
Last edited:
Thanks Sandungas, I've used Rebug ever since using Kmeaw wasn't plausible anymore. Recently, wanting to unban my console I switched to another CFW (Habib 4.75 Cobra) as that's what's recommended currently for safest PSN access (with Cobra). For some reason Brunolee's XMB Manager MOD wasn't installing Package Manager on 4.75 but everything else worked (perhaps because it's only compatible up to 4.70 thus far) and since he hadn't accessed his Hax account in some time (and wasn't aware of him having an account elsewhere), I decided to take matters into my own hands.

Anyway, I'm glad you took the time to do this as it was a life saver for me :)

EDIT:
PS I didn't actually think that code was unnecessary and was thinking it had to do with a .rco (like bitsb said) was just having a brain fart at the time so couldn't exactly find the words to describe it, was in a rush and figured people wouldn't know what I was talking about anyway, even if I did and wouldn't care just so long as it was fixed.
What happens with any kind of automated installer (pkg or the zip for multiman like gdrive did) is the installer needs to overwrite the original files category_game.xml and category_game_tool2.xml (are not updated, but replaced)... and this files are firmware dependant... sony makes changes to them for every few firmwares
My file install_package_files.xml with all the custom code is not firmware dependant (should work in all firms) but is needed to create a link for it by editing the other files category_game.xml and category_game_tool2.xml (in the readme.txt i tryed to simplify the explain of how to make this link)
In other words... all automated installers that uses the method of replacing completlly the files category_game.xml and category_game_tool2.xml are firmware dependant and should include some info about wich firmwares are compatibles with it
But is more complex than that... by overwriting these files you are also changing all the contents displayed in xmb game column, and is posible the user had something that you didnt used, or something you used but he didnt had before (like webman)
So the combination of all posible variations is big... this is why brunolee installer contains a lot of .xml files that are variants of the same one with small changes (and this is a pita to mantain and debug... the amount of files is so big that you can spend hours with it and there is too much room for errors)
In some way this is the reason why i explained in the readme.txt how to edit the files manually, because i was trying to avoid any compatibility problems

The code line you changed was there originally in rebug, i forgot to replace it... is nice you went to the point and found exactly the line with the problem even if you are not used to it... when i saw your message i knew you was right and facepalmed myself (sorry)... it took me some time to verify all again but was not a big problem it follows the same rules than the other texts
In the screencapture of my previous message you can see all the custom texts used by rebug package manager... that file is inside explore_plugin_full.rco and is one of the languages (for english, but all the other languages have the same texts)
What i did with the custom rebug texts was to take all them and include them in the install_package_files.xml... now all texts are inside the .xml and you can change them easilly, and for the subtitle texts (the ones that appears in a small font under the title) you can also remove them by deleting the <Pair key="info"> lines
For this kind of tests is good if you do as suggested in the readme, by adding another query to be able to load install_package_files.xml from usb root (i actually use 2... one linking to flash and other linking to usb)
This way the flash writes are minimized and you can make lot of tests from usb witholut any risk of brick at all... when you are happy with your frankenstein you can move the .xml to flash and keep it permanentlly as your personalized package manager
I didnt wanted to make any big change specially any visual or style to avoid giving my own oppinion of why is made that way and not another, how is better to do the things, there is something that could be added or removed, etc, etc, etc... (actually i was messing a bit with it trying to improve it but at some point i realized it could be better to start from scratch)
So this release doesnt have any creativity from myself, lol... but is very open to customizations, feel free to experiment with it :)
 
Last edited:
Im releasing another version because the new "rebug package manager classic" im including in this version is the same i included in this other message some minutes ago ---> http://www.psx-place.com/forum/xmb-...75-rebug-please-3167-post25955.html#post25955
The purpose of this build of "rebug package manager classic" was to be included in rebug officially but never happened, and i think is good to include it here just for completion, the reason why im including it here is because are very related, actually the "classic" version im uploading now was the base used to create the "standalone" version





v0.3
Completion release, by sandungas
Added "rebug package manager classic". This version is ONLY compatible with rebug firmwares (is dependant of rebug custom .rco's), and uses the original rebug code splitted in a separated .xml
 

Attachments

Last edited:
The part editing the category_game.xml and category_game_tool2.xml i understand, but i need paste Install Package Files provided in the download to flash memory as well? Or not?I use HABIB 4.76.
 
Last edited:
The part editing the category_game.xml and category_game_tool2.xml i understand, but i need paste Install Package Files provided in the download to flash memory as well? Or not?I use HABIB 4.76.
Sorry for replying so late, yes you need to write an additional file to flash (install_package_files.xml)

The line src="xmb://localhost/%flash/xmb/install_package_files.xml#seg_package_files" loads the file install_package_files.xml... and from it... loads the seg_package_files at top of the file
 
Cheers. looks like you are way ahead of me. Are there still plans to include this in Rebug officially as a standalone xml or did I misunderstand the above?
Apparently there were plans to include it but it was abandoned eventually.

Sent with Tapatalk
 
For some time [MENTION=29]Joonie[/MENTION] was considering including it in rebug... and at the same time he was taking other path by translating all the custom rebug package manager texts to all the 20 languages supported by XMB

The problem is the idea of separating the package manager as i was suggesting.... doesnt fits well with the other idea of translating all texts to all the languages, because the purpose of separating the package manager is mostlly to make it independant of the other firmware files (the rco's)
One of the reason why i did this was because joonie used to complain in irc (when talking about firmware builds, etc... friendlly talk) about how it sucks to edit the rco files for every new rebug release, lol
Is the kind of thing with the less important of a firmware build, and the last one "to do" in the list so i understand why is annoying to edit rco files

But i understand why he decided to keep editing the .rco because the language translations are an improvement... and also the "rebug style protocol" makes mandatory to edit other .rco files to change some icons to red colour
 
Last edited:
Sorry for replying so late, yes you need to write an additional file to flash (install_package_files.xml)

The line src="xmb://localhost/%flash/xmb/install_package_files.xml#seg_package_files" loads the file install_package_files.xml... and from it... loads the seg_package_files at top of the file

No need to apologize friend, know that you are very busy.
Thank you for answering my questions, now everything is clear.
 
Will this still work on the new 4.81 CFW's? I love this package manager as it has all of my bubbles that I keep for transferring to my Vita otherwise it makes it look cluttered due to the 50+ bubbles I have. It is on my slim running Ferrox as he implemented this but I want this (with XMBM+) on @Bobby_Downgrades Overflow firmware.
 
Will this still work on the new 4.81 CFW's? I love this package manager as it has all of my bubbles that I keep for transferring to my Vita otherwise it makes it look cluttered due to the 50+ bubbles I have. It is on my slim running Ferrox as he implemented this but I want this (with XMBM+) on @Bobby_Downgrades Overflow firmware.
Im not sure if this will suit you as its not the same as havinga full version of "Rebugs Package manager", but just so you know, if you download my webMAN Launchpad v0.16 pkg, and either select the option to install it OR select the option to uninstall it , all your bubbles will get moved inside the "from Hard Drive" section, So this way you move the bubbles but still keep the custom "Install Package Files" from Overflow.

I did this when I added support for XMBM+ to the category game xml (so it will also add the XMBM+ entry to your category game xml). I have made it like this on all the other 5 firmwares that the WMLP installer supports too.

They all have their own category game xmls modified individually to show XMBM+ (if its installed), and to move the bubbles if required. I also added the path dev_hdd0/packages to the "From Hard Drive" section.

It was like this in the Overflow 4.81 PUP:
Code:
<View id="seg_install_files_hdd0_path">
<Items>
<Query class="type:x-xmb/xmlpackagefolder" key="host_provider_flash" src="host://localhost/q?path=/dev_flash/packages&suffix=.pkg&subclass=x-host/package" />
</Items>
</View>

I made it like this:
Code:
<View id="seg_install_files_hdd0_path">
<Items>
<Query class="type:x-xmb/xmlpackagefolder" key="host_provider_flash" src="host://localhost/q?path=/dev_flash/packages&suffix=.pkg&subclass=x-host/package" />
<Query class="type:x-xmb/xmlpackagefolder" key="host_provider_hdd" src="host://localhost/q?path=/dev_hdd0/packages&suffix=.pkg&subclass=x-host/package" />
<Query class="type:x-xmb/folder-pixmap" key="seg_hdd_install" src="ese://localhost/query?type=install_game"/>
<Query class="type:x-xmb/folder-pixmap" key="seg_pkg_install" src="ese://localhost/query?type=install_pkg"/>
</Items>
</View>


NOTE: Just incase you didnt notice, in the newer versions of XMBM+ like 0.24.001 or higher, it shows the bubbles inside "Package Manager Plus" aswell.
 
Last edited:
Will this still work on the new 4.81 CFW's?
Is compatible with any firmware from version 1.00 up to 9.99 and easy to add to any firmware :)

Im not sure if this will suit you as its not the same as havinga full version of "Rebugs Package manager"
When i did this i tryed to be strict to respect he original as most as posible
My changes was mostlly to make it independant of any resource (this is why i named it standalone) but is the same than rebug package manager iirc
 

Featured content

Trending content

Back
Top