• PS3HEN is now supporting 4.93 Firmware

    View Official Release Post for additional information HERE

PS3HEN PS3HEN Open Beta Testing [For Advanced Users Only]

Edit:

I just updated ManaGunZ to the latest nighty release and it's working now hehe


So far so good as long as i keep my fan control to manual ( I set it to 40% and my rsx reached 87°C on the Xmb lol) instead of dynamic.

@aldostools the npsignin_plugin.rco remap is being unmapped after launching MultiMAN, the webMAN folder and etc are still mapped fine.
 
Last edited:
@aldostools the npsignin_plugin.rco remap is being unmapped after launching MultiMAN, the webMAN folder and etc are still mapped fine.

That's an issue of multiMAN that clear all existing mappings. webMAN MOD only tries to solve the issue produced by the old backup managers.

A possible solution could be using the prefix /./ to prevent that the mapping is removed, but AFAIK this is only implemented in Cobra 8.3 / Mamba 8.4. HEN uses a different mapping.c developed by bguerville.
 
@aldostools the npsignin_plugin.rco remap is being unmapped after launching MultiMAN, the webMAN folder and etc are still mapped fine.

That's an issue of multiMAN that clear all existing mappings. webMAN MOD only tries to solve the issue produced by the old backup managers.

A possible solution could be using the prefix /./ to prevent that the mapping is removed, but AFAIK this is only implemented in Cobra 8.3 / Mamba 8.4. HEN uses a different mapping.c developed by bguerville.
this issue should be fixed (in src) with updated mappath. @bguerville added FLAG_MAX_PRIORITY and FLAG_PROTECT flags, which in testing, paths stay mapped even after using multiman.
 
That's an issue of multiMAN that clear all existing mappings. webMAN MOD only tries to solve the issue produced by the old backup managers.

A possible solution could be using the prefix /./ to prevent that the mapping is removed, but AFAIK this is only implemented in Cobra 8.3 / Mamba 8.4. HEN uses a different mapping.c developed by bguerville.
I had noticed that /./ processing in Mamba, I thought I had implemented the same thing in HEN for legacy reasons actually, I would need to double check I suppose, been working on various things recently so getting a little mixed up..lol
 
I had noticed that /./ processing in Mamba, I thought I had implemented the same thing in HEN for legacy reasons actually, I would need to double check I suppose, been working on various things recently so getting a little mixed up..lol

Yes, but I still don't use it in webMAN MOD. Only MAMBA supported it when I added the feature.

I could add it to wMM now that at least Cobra 8.3 supports it.
 
Yes, but I still don't use it in webMAN MOD. Only MAMBA supported it when I added the feature.

I could add it to wMM now that at least Cobra 8.3 supports it.
I just checked my latest HEN mappath.c, I added the protection when the /./ token is found, internally it adds the new FLAG_PROTECT flag to the mapping..
It should work in the test build that esc0 posted.
 
I just checked my latest HEN mappath.c, I added the protection when the /./ token is found, internally it adds the new FLAG_PROTECT flag to the mapping..
It should work in the test build that esc0 posted.

Neat! I updated webMAN MOD a few minutes ago to support the mapping protection using /./ in the beginning of the path.

If someone want to test it, just need to use the online updater or re-download the instalelr from brewology or github.
 
@sandungas
@LuanTeles
@aldostools
@DeViL303

I would assume some of you may have played with this stuff already..
How does the spinning effect on XMB icons work?
Is it possible to edit an rco for instance to disable that stuff altogether and keep an icon fixed without the extra spin? Or via XML (doubtful?), whatever. If so, can it be done on a specific icon only?
What do we currently know about all this?
 
Last edited:
How does the spinning effect on XMB icons work?
I don't know a massive amount about it, just that it uses the tex_loading_icon.gim from inside explore_plugin_full.rco. Then it applies a spinning animation, that animation script is not included in the rco like some others, so it must be controlled by the sprx I guess.

Is it possible to edit an rco for instance to disable that stuff altogether and keep an icon fixed without the extra spin? Or via XML (doubtful?), whatever. If so, can it be done on a specific icon only?
I don't think so, As a workaround to stop the spinning altogther, Aldostools had the idea to use a symmetrical circular icon that hides the spinning effect visually (but really its still spinning). I can't think of any decent way to stop the spinning on a specific icon.

Kind of related, I have used transparent gims sometimes when I wanted no icon to appear in specific location.

Messy way that might work in theory, find the icon in memory and patch new icon over it, but really its probably easier for someone with the skills to find the animation effect code in the sprx and patch it there.

If I knew what you wanted to do I might be able to help more.
 
I don't know a massive amount about it, just that it uses the tex_loading_icon.gim from inside explore_plugin_full.rco. Then it applies a spinning animation, that animation script is not included in the rco like some others, so it must be controlled by the sprx I guess.


I don't think so, As a workaround to stop the spinning altogther, Aldostools had the idea to use a symmetrical circular icon that hides the spinning effect visually (but really its still spinning). I can't think of any decent way to stop the spinning on a specific icon.

Kind of related, I have used transparent gims sometimes when I wanted no icon to appear in specific location.

Messy way that might work in theory, find the icon in memory and patch new icon over it, but really its probably easier for someone with the skills to find the animation effect code in the sprx and patch it there.

If I knew what you wanted to do I might be able to help more.
Well I was trying to think of ways to remedy the spinning icon issue of the package manager as it no longer works without HEN or CFW.

Unfortunately, esc0 is telling me that the spinning icon is the least of our worries, the package manager features don't work at all apparently, the spinning icon is just a side effect of the main issue which is that the sub menus just don't open up, as if there was a permission issue or an incompatibility with a module, maybe nas_plugin or other..
We need to investigate further, maybe swapping a module or 2 with 4.88 versions might work, if not we could be at an impasse.
 
OK I dont really know a lot about this issue. I guess you mean for installing official Sony signed packages without any hacks applied? If that is it I really don't think its that important a feature myself. It's nice and all if it just worked, but 99% will just enable HEN out of habit before installing packages anyway.

I think this must be the thing where the package manager normally only works with the DEX explore plugin, OR with some patches to the CEX explore plugin (or possibly patches to the nas_plugin.sprx?). Joonie would probably know if you are still in contact with him, fairly sure we talked about that at some point early on in HEN development.

Kind of related, but the net_package_install method of installing packages DOES work on OFW with just an xml mod, NOTHING ELSE required, obviously without other patches it will only work for proper signed retail packages. The issue here is that this method will only install packages from a webserver so it depends on the specific use case. IIRC Jonnie was convinced this would be impossible without nas_plugin patches but I tested it and it did work, I could install ANY retail signed package on the latest OFW with just 1 xml edited.

Off topic, and I might be remembering wrong, but I think it was not like this back in the 3.41 or 3.55 days, I think back then the normal "install package files" could be enabled with ONLY changes to the xml, but then at some stage over the next few versions Sony blocked that. Possibly something to do with XMBML classes like subclass=x-host/package or class="type:x-xmb/xmlpackagefolder being blocked but not sure.
 
Kind of related, but the net_package_install method of installing packages DOES work on OFW with just an xml mod, NOTHING ELSE required, obviously without other patches it will only work for proper signed retail packages. The issue here is that this method will only install packages from a webserver so it depends on the specific use case. IIRC Jonnie was convinced this would be impossible without nas_plugin patches but I tested it and it did work, I could install ANY retail signed package on the latest OFW with just 1 xml edited.
Do you have a sample XML file we could use for testing net_package_install, this trick might help us.
 
Do you have a sample XML file we could use for testing net_package_install, this trick might help us.
Yeah the link Coro put up has an example of net_package_install in post #3. That thread was slightly different as I was trying to run it from USB but the principle is the same and this could be added to any category xml so only 1 modded file on OFW flash was required.

Important bits in bold:
<View id="item_NPEA00123_main">
<Attributes>
<Table key="item_NPEA00123_link">
<Pair key="info"><String>net_package_install</String></Pair>
<Pair key="pkg_src"><String>http://zeus.dl.playstation.net/cdn/...hcdSDmKAeaTTjPMeHItFOMiXHTADXBZpLHGmgISYt.pkg</String></Pair>
<Pair key="pkg_src_qa"><String>http://zeus.dl.playstation.net/cdn/EP9000/NPEA00123_00/lqtgHTozJivKzqCPKKoiBLChcdSDmKAeaTTjPMeHItFOMiXHTADXBZpLHGmgISYt.pkg</String></Pair>
<Pair key="content_name"><String>msg_install</String></Pair>
<Pair key="content_id"><String>EP9000-NPEA00123_00-UHUSTLEKIN000001</String></Pair>
<Pair key="prod_pict_path"><String>/dev_flash/vsh/resource/explore/icon/fah-xmb.png</String></Pair>
</Table>
</Attributes>
<Items>
<Item class="type:x-xmb/xmlnpsignup" key="item_NPEA00123_link" attr="item_NPEA00123_link"/>
</Items>
</View>

EDIT: Some limitations of the net_package_install method:
  • Retail packages only (unless other patches are applied of course)
  • The LONG Content ID in the XMBML (content_id string) must match the package.
  • The title on the XMB will just say "Install", or you can use any other system text from inside the main explore rco, "msg_install" was the most suitable one I could see there as there is nothing similar to "download". As a workaround I normally put the "install" item inside a sub folder that has the name of the package on it. Just adds 1 extra press of X to the install process.
  • The prod_pict_path is for the icon and it will ONLY work with local paths, So we can not use icons from inside rcos, or URLS to hosted icons like in other places. To avoid having no icon here the easiest thing is to pick one from dev_flash\vsh\resource\explore\icon\ like fah-xmb.png
  • XMB must be reloaded after adding this entry to an XML.

My guess is that the XMBML class type:x-xmb/xmlpackagefolder is blocked on OFW as its not required for anything and was a security risk. However the XMBML class type:x-xmb/xmlnpsignup still allows packages to install as its needed in a few places on the XMB like the Photo Gallery add on, and historically PS Home/FAH.

Side Note: If installing from webserver suits you, There are 2 other ways that will still allow packages to install without any sprx patches, and that is via the xil xmls (eg spotify) and the nsx xmls (eg Whats New). In the past these required a PSN account, but something changed around 4.83 IIRC and now if you have no PSN account when you try access Whats New, it gives you the option to enable those features by putting in your region and age. These methods have lots of disadvantages, but also some small advantages vs net_package_install such as icons and titles working properly.

I guess Sony did that because they finally realized they were missing out on pushing adverts to the millions of consoles that have no PSN account.
 
Last edited:
Yeah the link Coro put up has an example of net_package_install in post #3. That thread was slightly different as I was trying to run it from USB but the principle is the same and this could be added to any category xml so only 1 modded file on OFW flash was required.

Important bits in bold:


EDIT: Some limitations of the net_package_install method:
  • Retail packages only (unless other patches are applied of course)
  • The LONG Content ID in the XMBML (content_id string) must match the package.
  • The title on the XMB will just say "Install", or you can use any other system text from inside the main explore rco, "msg_install" was the most suitable one I could see there as there is nothing similar to "download". As a workaround I normally put the "install" item inside a sub folder that has the name of the package on it. Just adds 1 extra press of X to the install process.
  • The prod_pict_path is for the icon and it will ONLY work with local paths, So we can not use icons from inside rcos, or URLS to hosted icons like in other places. To avoid having no icon here the easiest thing is to pick one from dev_flash\vsh\resource\explore\icon\ like fah-xmb.png
  • XMB must be reloaded after adding this entry to an XML.

My guess is that the XMBML class type:x-xmb/xmlpackagefolder is blocked on OFW as its not required for anything and was a security risk. However the XMBML class type:x-xmb/xmlnpsignup still allows packages to install as its needed in a few places on the XMB like the Photo Gallery add on, and historically PS Home/FAH.

Side Note: If installing from webserver suits you, There are 2 other ways that will still allow packages to install without any sprx patches, and that is via the xil xmls (eg spotify) and the nsx xmls (eg Whats New). In the past these required a PSN account, but something changed around 4.83 IIRC and now if you have no PSN account when you try access Whats New, it gives you the option to enable those features by putting in your region and age. These methods have lots of disadvantages, but also some small advantages vs net_package_install such as icons and titles working properly.

I guess Sony did that because they finally realized they were missing out on pushing adverts to the millions of consoles that have no PSN account.
Thanks for that information.

So I assume you tried this on CFW and the system tests the package type and only allows npdrm packages, not debug pkg files.
Have you tried this with the HAN patch applied to see if it would let you install HAN resigned packages?
 
So I assume you tried this on CFW and the system tests the package type and only allows npdrm packages, not debug pkg files.
Have you tried this with the HAN patch applied to see if it would let you install HAN resigned packages?
The limitation of retail signed packages is only there on OFW. On CFW/HAN/HEN we can install anything using this method. AFAIK the download plugin needs patching too for unsigned debug packages. On CFW/HAN/HEN it also works fine to install the "force install to" type packages to dev_blind or wherever.

Also, This method is the magic behind PKG Linker which got around the 4GB package limit on HAN, I've been using it in loads of places in my mods for years. webMAN also uses it for updates these days. It's very reliable. The package downloads, installs, then gets deleted all automatically.
 
Last edited:
The limitation of retail signed packages is only there on OFW. On CFW/HAN/HEN we can install anything using this method. AFAIK the download plugin needs patching too for unsigned debug packages. On CFW/HAN/HEN it also works fine to install the "force install to" type packages to dev_blind or wherever.

Also, This method is the magic behind PKG Linker which got around the 4GB package limit on HAN, I've been using it in loads of places in my mods for years. webMAN also uses it for updates these days. It's very reliable. The package downloads, installs, then gets deleted all automatically.
Thanks.
My question was confusing because I began by mentioning CFW, sorry about that.
What I meant to ask was this.
Have you tried with this method to install a HAN signed (not debug) PKG from OFW or HFW with HAN patches applied in memory?
 
Ah, yes, it works fine. AFAIK this is still the only way to install a 4GB+ package on HAN due to the FAT32 limitation, also for a long time this is what thousands of HAN user were doing for almost all packages. It will basically allow anything the system (OFW/HAN/HEN/CFW) would allow normally, except for with debug packages there is an extra patch required to allow them to download*. That is not an issue for HAN signed packages as the system sees them as retail with HAN enabled.

*The Official DEX download_plugin.sprx has the opposite issue, and will only allow debug packages to download. On CFW the download plugin is patched to allow both, Enabling HEN also allows both.
 
@sandungas
@LuanTeles
@aldostools
@DeViL303

I would assume some of you may have played with this stuff already..
How does the spinning effect on XMB icons work?
Is it possible to edit an rco for instance to disable that stuff altogether and keep an icon fixed without the extra spin? Or via XML (doubtful?), whatever. If so, can it be done on a specific icon only?
What do we currently know about all this?
Is made with an object named <ItemSpin>
Rcomage can deal with it, represented in the main XML generated by rcomage under <ObjectTree> as a children of one of the <xxxList> objects

But as you already know sometimes the .sprx associated with the .rco does some changes to this hierarchy of objects "on the fly", and right now im not sure if the package manager "xxxList" object is defined in a .rco or by a .sprx
The rule to follow most of the times is to search for it in the .rco files, if is not there it means is inside the .sprx files
Im telling files in plural because sometimes his features are combined and im not sure if the package manager have dependencies of several rco/sprx files, or how many rco/sprx files are involved with it

------------
A dirty way i figure to "hide" the spinning icon is by displaying a new icon on top of it with his own parent/children hierarchy in the rcoxml structure under <ObjectTree>
The trick would be to use the same exact position and size settings than the original, included the "overrides" attributes (to allow to scale it dinamically for all the 4 XMB supported resolutions)... and change only the attribute of positionZ
You know... the XMB coordinates are in 3D, everything is "drawn" with Z=0... so if you move something in Z axis (closer to the viewer) it will remain on top of anything else
 
Last edited:
@LuanTeles

Here are 2 BIN files for you to test, if you like.

The original one uses this in mappath.c
Code:
LV2_SYSCALL2(int, sys_map_path, (char *oldpath, char *newpath, uint32_t flags))
{
    extend_kstack(0);
    return map_path_user(oldpath, newpath, flags);
}

The modified one uses this currently, to choose between user and kernel (its just a rough testing example for now)
Code:
LV2_SYSCALL2(int, sys_map_path, (char *oldpath, char *newpath, uint32_t flags))
{
    uint64_t ptr = (uint64_t)(uint64_t*)oldpath;
    #ifdef DEBUG
        //DPRINTF ("sys_map_path ptr 0x%8lx\n", ptr);
    #endif
 
    if(((ptr & 0xFF00000000000000ULL) >> 56)== 0x80)
    {
        return map_path(oldpath, newpath, flags);// kernel
    }
    else
    {
        extend_kstack(0);
        return map_path_user(oldpath, newpath, flags);// user
    }
}

The sample kplugin template included, MUST use the modified BIN, for the below sys_map_path example, and others using this syscall, or it will crash!

I should note that in testing only the FIRST mapping works, please let me know if that is the same for you.
Code:
sys_map_path("/dev_bdvd/PS3_UPDATE", "/dev_flash/vsh/resource/AAA",0);

You can also use the 2 new flags, which is what the default payload for HEN does now, to preserve mappings. Note that HEN uses map_path, while the kplugin uses sys_map_path.
Code:
map_path("/dev_hdd0/hen/xml/hfw_settings.xml","/dev_flash/hen/remap/xml/hfw_settings.xml",FLAG_MAX_PRIORITY|FLAG_PROTECT);
 

Attachments

Last edited:
Back
Top