PS3 XMB Package Downloader - An XMB MOD that intergrates a Homebrew Store on the XMB v0.70

[bitsbubba]

What's the problem exactly with hashcalc in 8.1? Error message?

Sent from my GT-I9305 using Tapatalk

said something about not working with this 64bit OS, tried [MENTION=118]kozarovv[/MENTION]'s tut about PUAD unself, I did get it working though, I just put all the files inside ps3tools folder that's inside PUAD folder

 

[pinky]

I forgot to mention that u also need cyggcc_s-1.dll, cygwin1.dll, and cygz.dll which u can get from puad as well. u'll get an error if u don't have them.

 

[bitsbubba]

I forgot to mention that u also need cyggcc_s-1.dll, cygwin1.dll, and cygz.dll which u can get from puad as well. u'll get an error if u don't have them.

now you tell me :p

 

[pinky]

now you tell me :p

u should get a message about them being missing from ur computer unless windows 8 didn't do that.

 

[bitsbubba]

u should get a message about them being missing from ur computer unless windows 8 didn't do that.

yeah I got 2 messages then I just moved everything to PUAD, but I got it working from it's own folder now as in the tut

 

[DeViL303]

so the pkg you sent me is most current?

You will probably notice I have been including the "cfw_settings_en.xml" in the installer for 4.78, the reason for this is in case some muppet ignores the onscreen warnings and the package name saying that its only for "Rebug Only" and installs it anyway :p If they was to do that and that file doesn't exist , then it will soft brick and require a FW reinstall. So including the xml protects against that. I don't think there is any downside to including it.

 

[bitsbubba]

If they was to do that and that file doesn't exist , then it will soft brick and require a FW reinstall. So including the xml protects against that. I don't think there is any downside to including it.

yea I got that soft brick before, BUT the easier way out of it instead of re-installing FW is to press PS button then you'll get a corrupt FW error but it allows webMAN to load so you ftp the file over or rename it, allow to restart Done Deal

 

[DeViL303]

yea I got that soft brick before, BUT the easier way out of it instead of re-installing FW is to press PS button then you'll get a corrupt FW error but it allows webMAN to load so you ftp the file over or rename it, allow to restart Done Deal

I don't seem to have write access to flash via webman ftp, is there an option for that, ive just been using rebug toolbox?

 

[bguerville]

I don't seem to have write access to flash via webman ftp, is there an option for that, ive just been using rebug toolbox?

Even after enabling /dev_blind in wMM setup?

Sent from my GT-I9305 using Tapatalk

 

[bitsbubba]

I don't seem to have write access to flash via webman ftp, is there an option for that, ive just been using rebug toolbox?

yes you need to select it in webMAN settings

 

[DeViL303]

yes you need to select it in webMAN settings

Oh yeah, see it now. duh!

 

[DeViL303]

So decided to just release this version as is as Im busy with other things , I will come back to it.

Download XMBPD 0.18.00

This has all hash's fixed for cobra thanks to bitsbubba and thanks to 0_obeWAN for sorting out the icons and for testing etc, this will install on any Rebug at or above 4.70 (XMBPD will not work on lower FW or on non Rebug FW sorry).

I am considering going back to the old look (list view) as it allows for categories, it allows for backgrounds , and the game doesn't boot after install which annoys me with this view, and it could be built into XMBM+ easily wiith the list view, what do you think [MENTION=6]bitsbubba[/MENTION]? it could be the best way if your fix for Spotify works, and priority pkgs.

Also there are only so many of these entries in the Sony sprx's/xmls , and Im running out of them, so if we go back to using the xil xmls for XMBPD then it frees up the TV channel Item for other mods like Webman Launchpad etc. then they can all be installed at the same time if required.

At the moment you can only run one of my mods at a time, in a few days I will release an installer that allows them both to run together. So if you want to use this then uninstall Launchpad using its own installer first, or vice versa.

(I will be still adding new pkgs to this as they come out, I just added new ScummVM 1.8.0 today).

 

[bitsbubba]

I am considering going back to the old look (list view) as it allows for categories, it allows for backgrounds , and the game doesn't boot after install which annoys me with this view, and it could be built into XMBM+ easily wiith the list view, what do you think [MENTION=6]bitsbubba[/MENTION]? it could be the best way if your fix for Spotify works, and priority pkgs.

I was thinking just that, the older look for Package Downloader, What's New @ & Launchpad would be excellent to install all!

 

[kozarovv]

[MENTION=22544]DeViL303[/MENTION] I'm looking forward for PUP with all of your mods out of the box.

 

[DeViL303]

I was thinking just that, the older look for Package Downloader, What's New @ & Launchpad would be excellent to install all!

Yeah I want it all too!

It is gonna get complicated with all the FW versions and different combinations of mods and the fact they all have to not conflict with/overwrite each other. To support them all in one pkg and all the possible combos (ie if a FW 4.70 user wants to install just 2 specific mods) the pkg will grow to over 300MB very quickly. So will possibly need to drop support for older FW? Are there people using rebug 4.70,4.75,4.76 who have not bothered upgrading to 4.78 and is it worth adding support for those people when it adds so much work and makes the file bigger? (I know there are users that havnt upgraded past 4.46 but XMBPD doesn't work for them so not thinking about them right now)

Also its only XMBPD that doesn't work on CEX FW and FW lower than 4.70, so there will be another load of compatibility to add with the other 2 mods if I want to add rebug and non rebug versions of those, that would make the package over 600MB if I was to try support all variations and Im not going to do that.

[MENTION=22544]DeViL303[/MENTION] I'm looking forward for PUP with all of your mods out of the box.

This might be the best way, As every category xml needs to be modded, plus lots of rcos, and a few sprx files. I know people don't like the idea of unofficial PUP files but for the reasons mentioned above its going to be hard to support all FW and make the installer so people can have all options, it will be all or nothing. It would be much easier to make a PUP with all the mods working out of the box as then it only has to be compatible with itself and I don't have to worry about people trying to install non Rebug version on Rebug etc.

I will probably drop support for all FW below 4.78 with pkgs unless there is good reason not to? The way I see it if people want to use new features they need to update to new FW just like if they were on OFW (or they can port the features themselves in the combination they want, its not rocket science and I can help out with the required info).

EDIT: Or to solve all this and make it dynamic, some proper dev could release a patcher that patches the sprx links on the fly using cobra, so then all the code goes from being 600MB to support all those FWs/combos to just KBs.

For example, for the Launchpad to work there is only one sprx that needs patching with one tiny line of code:

https://%s.%s.adproxy.ndmdhs.com/adproxy/getmanifest?aid=%016llx&cc=%s&lang=%d&age=%d&ts=%016llx&env=%s

Needs to be patched to:

http://127.0.0.1/dev_hdd0/tmp/wm_launchpad.xml

I know this must be simple enough for people who know how.

 

[kozarovv]

This might be the best way, I know people don't like the idea of unofficial PUP files but for the reasons mentioned above its going to be hard to support all FW and make the installer so people can have all options. It would be much easier to make a PUP with all the mods working out of the box as then it only has to be compatible with itself and I don't have to worry about people trying to install non Rebug version on Rebug etc.

For sure it's best way, firstly there is no reason to keep support for older firmwares. Just latest one have now all needed functions. I'ts not that people don't like unofficial PUPs, good tested PUP from trusted developer is OK. We are just don't like when people changing coldboot and saying "I made that CFW "..

I will probably drop support for all FW below 4.78 with pkgs unless there is good reason not to? The way I see it if people want to use new features they need to update to new FW just like if they were on OFW (or they can port the features themselves in the combination they want, its not rocket science and I can help out with the required info).

Yeah imo You shouldn't support older cfw, I think that eventually You should think about support for other 4.78 cfws than about older ones.

EDIT: Or to solve all this and make it dynamic, some proper dev could release a patcher that patches the sprx links on the fly using cobra, so then all the code goes from being 600MB to support all those FWs/combos to just KBs.

For example, for the Launchpad to work there is only one sprx that needs patching with one tiny line of code:
Code:
https://%s.%s.adproxy.ndmdhs.com/adproxy/getmanifest?aid=
6llx&cc=%s&lang=%d&age=%d&ts=
6llx&env=%s
Needs to be patched to:
Code:
www.psx-place.com | 404 - Page Cannot Be Found
I know this must be simple enough for people who know how.

I don't know there is a standalone app for ps3 that is patching sprxs, but for sure this can be done by cobra itself by adding this to modulespatch, but then this will be still firmware dependent because cobra files are dependent. So there will be needed different cobra files maybe even between two 4.78 cfw's and all that need to be compiled from scratch, there is no easy way like with fixing hashes.

In this case string:

68 74 74 70 73 3A 2F 2F 25 73 2E 25 73 2E 61 64 70 72 6F 78 79 2E 6E 64 6D 64 68 73 2E 63 6F 6D 2F 61 64 70 72 6F 78 79 2F 67 65 74 6D 61 6E 69 66 65 73 74 3F 61 69 64 3D 25 30 31 36 6C 6C 78 26 63 63 3D 25 73 26 6C 61 6E 67 3D 25 64 26 61 67 65 3D 25 64 26 74 73 3D 25 30 31 36 6C 6C 78 26 65 6E 76 3D 25 73

Need to be patched to:

68 74 74 70 3A 2F 2F 31 32 37 2E 30 2E 30 2E 31 2F 64 65 76 5F 68 64 64 30 2F 74 6D 70 2F 77 6D 5F 6C 61 75 6E 63 68 70 61 64 2E 78 6D 6C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

At right offset..., but still i think that is better keeping this mod to one or two most recent cfws than patching this dynamically.

 

[DeViL303]

For sure it's best way, firstly there is no reason to keep support for older firmwares. Just latest one have now all needed functions. I'ts not that people don't like unofficial PUPs, good tested PUP from trusted developer is OK. We are just don't like when people changing coldboot and saying "I made that CFW "..
Yeah imo You shouldn't support older cfw, I think that eventually You should think about support for other 4.78 cfws than about older ones.

Well that's ok then, Im glad you support this idea..I wonder.. if me and [MENTION=6]bitsbubba[/MENTION] and a few others (didn't [MENTION=3657]pinky[/MENTION] say he was into xmb mods in the xmbm thread? ) was to mod a PUP it would be a lot more than just a coldboot changed. I imagine all these mods built in, plus XMBM+ and more, we still have the store preview to play with, and their is another video channels item that isn't active..yet

As for supporting other FW, I think the CEX CFW makers will have to figure out what makes Rebug different for downloading pkgs from the store if they want XMBPD to be compatible, its probably because the pkgs are not properly signed. I don't think I can add support without adding debug files to CEX FW. So again a modded CEX CFW pup is one solution. All the other mods should work on CEX though without any debug files.

Ill be glad to drop support for older FW too as the installer was going to be over 300 files and there is lots of room for error trying to keep track of that many, Im only one person and I don't want to softbrick someones ps3 because I didn't test For example: 4.65 with a strange combination of mods properly.

I don't know there is a standalone app for ps3 that is patching sprxs, but for sure this can be done by cobra itself by adding this to modulespatch, but then this will be still firmware dependent because cobra files are dependent. So there will be needed different cobra files maybe even between two 4.78 cfw's and all that need to be compiled from scratch, there is no easy way like with fixing hashes.

In this case string:

68 74 74 70 73 3A 2F 2F 25 73 2E 25 73 2E 61 64 70 72 6F 78 79 2E 6E 64 6D 64 68 73 2E 63 6F 6D 2F 61 64 70 72 6F 78 79 2F 67 65 74 6D 61 6E 69 66 65 73 74 3F 61 69 64 3D 25 30 31 36 6C 6C 78 26 63 63 3D 25 73 26 6C 61 6E 67 3D 25 64 26 61 67 65 3D 25 64 26 74 73 3D 25 30 31 36 6C 6C 78 26 65 6E 76 3D 25 73

Need to be patched to:

68 74 74 70 3A 2F 2F 31 32 37 2E 30 2E 30 2E 31 2F 64 65 76 5F 68 64 64 30 2F 74 6D 70 2F 77 6D 5F 6C 61 75 6E 63 68 70 61 64 2E 78 6D 6C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

At right offset..., but still i think that is better keeping this mod to one or two most recent cfws than patching this dynamically.

Ok I see. I though it would search the modules and patch dynamically so wouldn't be FW dependant, thats that idea out so.

 

[kozarovv]

About cobra patching this is what I think, but I'm not 100% sure that i have right here. I don't messed with cobra too much, just compiled to test that I can and fixed patches. That's all.

What is wrong on CEX cfws? Error or something?

 

[DeViL303]

Just found out this doesn't work on latest standard CFW, feck that's a shame, works fine on Rebug 4.75+ , but just tested it on Habibs 4.78 CFW and it gives a 80029567 error as it tries to download the packages. So looks like this is becoming more exclusive by the day, now its only confirmed working for Rebug users on 4.75+.

Try to install any not finalized pkg (debug one) you should get same error. But retail pkg's should work ok. Maybe is some new map_path problem due to new cobra.

I never got around to testing retail pkgs but you are probably right

 

[kozarovv]

I never got around to testing retail pkgs but you are probably right

Hmm, maybe just changing NP Environment in QA settings will help.

Edit: probably changing to SP-INT will fix that.