PS3 PKGi PS3 v1.2.2 released

@bucanero When I use PSNPATCH / WEBMANMOD and I unload them to be able to go online, it was supposed to block all homebrew apps. I tested a few of them like Movian, etc and it blocked. But PKGI was not blocked and it is a Homebrew app. Can you fix it so it will be recognized as a Homebrew app and it will be blocked by PSNPATCH / WEBMANMOD when they are unloaded / stealth?
Someone can get banned by using PKGI by a mistake when PSN is enabled.
The homebrews are blocked by Cobra/HEN payload.
If the title id is NP, BLES, BLUS, BCES, BCUS, etc the application is whitelisted. Otherwise the homebrew is blocked when the CFW syscalls are disabled.

To fix this issue you need to repack the tool with a different title id, delete the current installation and install the new package.

Or add the title id to "/dev_hdd0/tmp/blacklist.cfg"

@bucanero can fix the issue using a different title id in his release package.
 
Last edited:
The homebrews are blocked by Cobra/HEN payload.
If the title id is NP, BLES, BLUS, BCES, BCUS, etc the application is whitelisted. Otherwise the homebrew is blocked when the CFW syscalls are disabled.

To fix this issue you need to repack the tool with a different title id, delete the current installation and install the new package.

Or add the title id to "/dev_hdd0/tmp/blacklist.cfg"

@bucanero can fix the issue using a different title id in his release package.

Thanks @aldostools for the tips.
It must be easy for myself to do it in my console but if @bucanero can repack this tool with a different title id other than NP00PKGI3, in his github, it will avoid potential bans for future newbie users.
 
It must be easy for myself to do it in my console but if @bucanero can repack this tool with a different title id other than NP00PKGI3, in his github, it will avoid potential bans for future newbie users.

that makes no sense, and it's just plain wrong:

if pkgi uses the title_ID already used by another homebrew (for example Irisman), when you install pkgi-ps3, it will overwrite Irisman. So users would have to choose between having Irisman or pkgi.

the right solution, as @aldostools mentioned, is to add the title_id to either cobra payload or blacklist.cfg file.
 
@bucanero I think you understood wrong what @aldotools were suggesting to you.
Instead of beginning the PKGI folder as NP... if the package started as BUCAPKGI3 (for example) your tool would be blacklisted without the need of editing blacklist.cfg.

PSNPATCH and WEBMANMOD was designed to make easy to us to block homebrew, it was not designed to edit blacklist.cfg, it was thought as an automatic solution.

All NP, BLES, BLUS, BCES, BCUS are reserved for OFFICIAL APPS, not homebrew. It's logic, simple and easy. And that makes more sense.

But if you think that's not the way to go, ok... no problem (for me, because I can handle and rename by myself).
I was just worring about the others, fixing it would make it bulletproof for noobs.

BTW thanks for your app.
 
@bucanero I think you understood wrong what @aldotools were suggesting to you.
Instead of beginning the PKGI folder as NP... if the package started as BUCAPKGI3 (for example) your tool would be blacklisted without the need of editing blacklist.cfg.

oh, sorry, my bad. I misunderstood Aldo's message.

All NP, BLES, BLUS, BCES, BCUS are reserved for OFFICIAL APPS, not homebrew. It's logic, simple and easy. And that makes more sense.

Well, let's say it's a convention, but I think that it doesn't apply to every homebrew. Just two examples that I remember: Multiman (BLES80608) and SEN Enabler. (uses a Gran Turismo title id)
 
Np, it happens!

Yup, it's a convention. Hmmm didn't know that these ones use retail title ids because I don't use them (Sen Enabler / Multiman).

Homebrews that I use and have unique / special IDs: Managunz, Managunz File Manager, Irisman, Retroarch, Webmanmod, Rebugtools, Prepntfs, Psnpatch, Habibs QA toogle.

PS: Just a thought... I don't even know if not using retail IDs are safe, if they can detect it in your HDD (even if you don't run the App online).
 
sony is probably the dumbest company of the three when it comes to online, so I wouldn't worry about all that. according to psdevwiki, the history is only last or current game played, and those files are deleted whenever you delete history. they're remade but blank after that.
 
Well, let's say it's a convention, but I think that it doesn't apply to every homebrew. Just two examples that I remember: Multiman (BLES80608) and SEN Enabler. (uses a Gran Turismo title id)

My explanation about NP**, BC**, BL**, etc. was simplified to not enter in details. The homebrew blocker in COBRA/Mamba/HEN also handles the homebrews that use official-like title_ids: BLES806** (multiMAN), BLJS10018, BLES08890, BLES13408, BLES01337, NPEA90124 (SEN). For additional whitelist and blacklist it is required to use the .cfg files.

https://github.com/aldostools/COBRA/blob/master/487/CEX/stage2/homebrew_blocker.c#L139-L160

In the case of the issue with PKGi, it can be fixed if you change the title id to something like PKGI00PS3

@pinky the homebrew blocker is not to prevent the history, it is to prevent that online users appear on friends lists as using multiMAN, IRISMAN, Movian, etc. That's an obvious signal that you're using CFW or HEN and violating the EULA of SEN.
 
My explanation about NP**, BC**, BL**, etc. was simplified to not enter in details. The homebrew blocker in COBRA/Mamba/HEN also handles the homebrews that use official-like title_ids: BLES806** (multiMAN), BLJS10018, BLES08890, BLES13408, BLES01337, NPEA90124 (SEN). For additional whitelist and blacklist it is required to use the .cfg files.

https://github.com/aldostools/COBRA/blob/master/487/CEX/stage2/homebrew_blocker.c#L139-L160

In the case of the issue with PKGi, it can be fixed if you change the title id to something like PKGI00PS3

@pinky the homebrew blocker is not to prevent the history, it is to prevent that online users appear on friends lists as using multiMAN, IRISMAN, Movian, etc. That's an obvious signal that you're using CFW or HEN and violating the EULA of SEN.

oh, I meant using psn patch to delete history.
 
@bucanero What do you think about adding a text in the top bar to identify in what list.txt the user are?

like

<<< :but l2: AVATARS :but r2: >>>

many users don't know that this is possible and they get lost in which list they are (including me)), I know it can be identified in the side menu, but it's not practical
 
Last edited:
i need these files pleace pkgi_games.txt pkgi_dlcs.txt pkgi_themes.txt pkgi_avatars.txt pkgi_demos.txt pkgi_managers.txt pkgi_emulators.txt pkgi_apps.txt pkgi_tools.txt pkgi.txt
 
i need these files pleace pkgi_games.txt pkgi_dlcs.txt pkgi_themes.txt pkgi_avatars.txt pkgi_demos.txt pkgi_managers.txt pkgi_emulators.txt pkgi_apps.txt pkgi_tools.txt pkgi.txt
you have to make those files yourself. they will point to your own file server so they can not be made by anyone but you.
 
thanks but how do i make them ?

it says in the op:

upload_2021-6-15_11-41-59.png
 
still don't understand how to do it is there video tut for it

the descriptions are pretty much all you need. it sounds simple enough based on that, then there is an example. you don't have to fill out the whole thing just put a , to skip to the next section of the format. as you can see in the example, the first one has ,, and the second has three ,,, . that means it's skipping over the next section (i.e. leaving it blank). it says you can leave several things blank if you don't know. the main thing you need is the content id (part of rap creation), rap key in hex (open the rap in a hex editor or use ps3 tools to find this info), pkg location (url). then leave size as 0. I think those are the only things you really need. 0 means that you don't know the size. won't matter if you're getting them from your own server or pc or something. it's time consuming, I guess, but most people won't have too many to do.

edit: I think you need a name as well, but I'm not 100% certain of that. however, you need something to click on.
 
the descriptions are pretty much all you need. it sounds simple enough based on that, then there is an example. you don't have to fill out the whole thing just put a , to skip to the next section of the format. as you can see in the example, the first one has ,, and the second has three ,,, . that means it's skipping over the next section (i.e. leaving it blank). it says you can leave several things blank if you don't know. the main thing you need is the content id (part of rap creation), rap key in hex (open the rap in a hex editor or use ps3 tools to find this info), pkg location (url). then leave size as 0. I think those are the only things you really need. 0 means that you don't know the size. won't matter if you're getting them from your own server or pc or something. it's time consuming, I guess, but most people won't have too many to do.

edit: I think you need a name as well, but I'm not 100% certain of that. however, you need something to click on.
Nice. I really didn't know what ,,, meant. Thanks for helping @joe musashi , it also helped me understand better how these CSV / TSV files works.
 

Similar threads

Back
Top