Pressing R1 + Circle while the in-game xmb is open appears to do nothing. Also, none of the in-game XMB icons are loading. Trying to close the in-game XMB will result in the timer icon in the top right spinning infinitely.
- Thread starter Zar
- Start date
Pressing R1 + Circle while the in-game xmb is open appears to do nothing. Also, none of the in-game XMB icons are loading. Trying to close the in-game XMB will result in the timer icon in the top right spinning infinitely.
If you mean the function prx_start_modules it was already added in Cobra 8.3 (coming soon in Evilnat's 4.87.3)
https://github.com/aldostools/COBRA/blob/master/486/REX/stage2/modulespatch.c#L1071
https://github.com/aldostools/COBRA/blob/master/486/REX/stage2/ps3mapi_core.c#L456
MAMBA 8.3 also includes it too:
https://github.com/aldostools/Mamba/blob/master/stage2/modulespatch.c#L1342
https://github.com/aldostools/Mamba/blob/master/stage2/ps3mapi_core.c#L458
BTW That code is credited to you ;-)
It is Cobra 8.2 and PS3HEN that doesn't have that feature.
Last edited:
haxxxen
Developer
thanks, but damn. I had no problems when I was using my own game plugins...
can you send me this gta plugin? I will try myself
er wut? I have noticed you have added it to wmM, but not cobra
lol, does this work? I mean can you load system plugins with it? I wasn't so successful with it, if I remember right.
I have meant loading game plugins. you can copy vsh prx loading and make it game prx loading. you only have to get game process in hook function
and thanks, but this is not necessary with credits. I really don't need them and it can make me go bad
Last edited:
Sure. Here it is...
Maybe it's not my place to say, but I think we/you should make a new thread for this, since it's no longer related to ManaGunZ.
I haven't tampered much this function, but it seems to work with /gameplugin.ps3mapi (loading a system sprx in game process)
The credits are for respect to the author and as reference for others about who authored the feature.
haxxxen
Developer
hey cool, how could I have missed this? thanks for your answer
if this works, then it is exactly what helps with these game plugins, which are all simply coded like system plugins
I think I found the cause of the issue.
Perhaps, i'm wrong... it need confirmation. An original EBOOT (and also the one you linked) have the lowest capability/control flag, he doesn't have access to everything, it's very limited, so, my guess is it doesn't have access to /dev_hdd0/tmp/ to launch the sprx. When you resigned the EBOOT I set the highest control/capability flag, so it does have access to that directory.
Why when you launch multiman you can access to that directory ? I can't be sure but my guess is deank added a fix_permission to every directory on /dev_hdd0, why ? because at 4.21 era if I remember correctly, these directory where all 'locked' with some CFW and caused lot of issue, most annoying was the infamous blackscreen ! ( I personnaly had that issue... and it took me lot of time to figure what was happening...)
So, to confirm my guess is to 'fix permission' on /dev_hdd0/tmp/ and try again
Perhaps, i'm wrong... it need confirmation. An original EBOOT (and also the one you linked) have the lowest capability/control flag, he doesn't have access to everything, it's very limited, so, my guess is it doesn't have access to /dev_hdd0/tmp/ to launch the sprx. When you resigned the EBOOT I set the highest control/capability flag, so it does have access to that directory.
Why when you launch multiman you can access to that directory ? I can't be sure but my guess is deank added a fix_permission to every directory on /dev_hdd0, why ? because at 4.21 era if I remember correctly, these directory where all 'locked' with some CFW and caused lot of issue, most annoying was the infamous blackscreen ! ( I personnaly had that issue... and it took me lot of time to figure what was happening...)
So, to confirm my guess is to 'fix permission' on /dev_hdd0/tmp/ and try again
Last edited:
I think I found the cause of the issue.
Perhaps, i'm wrong... it need confirmation. An original EBOOT (and also the one you linked) have the lowest capability/control flag, he doesn't have access to everything, it's very limited, so, my guess is it doesn't have access to /dev_hdd0/tmp/ to launch the sprx. When you resigned the EBOOT I set the higher control/capability flag, so it does have access to these directory.
Why when you launch multiman you can access to this directory ? I can't be sure but my guess is deank added a fix_permission to every directory on /dev_hdd0, why ? because at 4.21 era if I remember correctly, these directory where all 'locked' with some CFW and caused lot of issue, most annoying was the infamous blackscreen ! ( I personnaly had this issue... and it took me lot of time to figure what was happening...)
So, to confirm my guess is to 'fix permission' on /dev_hdd0/tmp/ and try again
I will test this now for you. I'm glad to hear you've potentially figured out what the issue is
haxxxen
Developer
if I remember right, this is exactly what I have told to someone on ngu, to use fixpermission on tmp in exactly the same context. I think this really has helped. now I am searching this thread on ngu, lol...I think I found the cause of the issue.
Perhaps, i'm wrong... it need confirmation. An original EBOOT (and also the one you linked) have the lowest capability/control flag, he doesn't have access to everything, it's very limited, so, my guess is it doesn't have access to /dev_hdd0/tmp/ to launch the sprx. When you resigned the EBOOT I set the higher control/capability flag, so it does have access to these directory.
Why when you launch multiman you can access to this directory ? I can't be sure but my guess is deank added a fix_permission to every directory on /dev_hdd0, why ? because at 4.21 era if I remember correctly, these directory where all 'locked' with some CFW and caused lot of issue, most annoying was the infamous blackscreen ! ( I personnaly had this issue... and it took me lot of time to figure what was happening...)
So, to confirm my guess is to 'fix permission' on /dev_hdd0/tmp/ and try again
I think I found the cause of the issue.
Perhaps, i'm wrong... it need confirmation. An original EBOOT (and also the one you linked) have the lowest capability/control flag, he doesn't have access to everything, it's very limited, so, my guess is it doesn't have access to /dev_hdd0/tmp/ to launch the sprx. When you resigned the EBOOT I set the higher control/capability flag, so it does have access to these directory.
Why when you launch multiman you can access to this directory ? I can't be sure but my guess is deank added a fix_permission to every directory on /dev_hdd0, why ? because at 4.21 era if I remember correctly, these directory where all 'locked' with some CFW and caused lot of issue, most annoying was the infamous blackscreen ! ( I personnaly had this issue... and it took me lot of time to figure what was happening...)
So, to confirm my guess is to 'fix permission' on /dev_hdd0/tmp/ and try again
This does indeed fix the problem. Nice find
@Zar
-Short Answer
Using "Set permissions" on /dev_hdd0/tmp is 100% the solution.
-Detailed Answer
I did the following:
1: Factory reset my PS3.
2: Installed ManaGunZ.
3: Installed a pkg containing all GTA updates.
4: Replaced the original eboot with the one to load the sprx.
5: Placed the sprx in tmp.
6: Inserted my GTA disc, and launched it... no welcome message from the sprx.
7: Launched ManaGunZ, and used "Set permissions" on /dev_hdd0/tmp.
8: Launched GTA again... welcome message appeared
-Short Answer
Using "Set permissions" on /dev_hdd0/tmp is 100% the solution.
-Detailed Answer
I did the following:
1: Factory reset my PS3.
2: Installed ManaGunZ.
3: Installed a pkg containing all GTA updates.
4: Replaced the original eboot with the one to load the sprx.
5: Placed the sprx in tmp.
6: Inserted my GTA disc, and launched it... no welcome message from the sprx.
7: Launched ManaGunZ, and used "Set permissions" on /dev_hdd0/tmp.
8: Launched GTA again... welcome message appeared
So if I understand correctly, correct me if I am wrong as I never use those sprx game mods, basically the problem comes from the mod itself. The eboot should check permissions & set them properly if found inadequate before launching the sprx. It does not look like that job should be done by backup managers..
Last edited:
Because I had too many problems related to control/flag and permissions. The most annoying was when I updated from 3.55 to 4.21, I though I broke my ps3 because I couldn't launch any backup, I always had a blackscreen, during weeks I tryed everything... when finally I tryed without any hope an old pkg called 'fix_permission.pkg", it fixed everything ! It's just the 1st issue of a long list that happened to me because of it. Now, it's always my first guess but i was focused on the EBOOT but when I opened the rar file I saw the sprx and it tilted !
Another example of issue cause by it : https://www.psx-place.com/threads/exfat-support.27907/page-3#post-226379 . As I said always my first guess :p
or just give a higher capability/control flag to the eboot
Similar threads
-
PS5 Porkfolio All in One PS5 Utility (Game Library, Backporks, FTP Transfers, Cheats, Saves, Pa- Started by Red
- Replies: 0
-
-
-
PS3 [Tutorial] Update Frankenstein PS3 Firmware That is Too Low to Initialize RSX (< 3.41) (NAND Models)
- Started by byt3swap
- Replies: 0