XMB Package Downloader (XMBPD)

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

Go to download
Overview Extra info Updates (18) Reviews (5) History Discussion
pinky said:
yeah, cobra only records the self files' hash, so the xml files won't matter. :)
Click to expand...

So if ANY sprx or self is modified cobra doesn't work? is this for safety or security or what? seems a bit OTT, I only want to change 1 URL mainly and a title and icon name.. :)

Think im going to leave the tv sprx and network sprx unchanged for now as im making no progress. It means XMBPD will have a spinning icon and no title on ingame XMB for now but it could be worse. Going to concentrate on other things and come back to this later (might not be possible)
 
DeViL303 said:
So if ANY sprx or self is modified cobra doesn't work? is this for safety or security or what? seems a bit OTT, I only want to change 1 URL mainly and a title and icon name.. :)

Think im going to leave the tv sprx and network sprx unchanged for now as im making no progress. It means XMBPD will have a spinning icon and no title on ingame XMB for now but it could be worse. Going to concentrate on other things and come back to this later (might not be possible)
Click to expand...

I believe a correct hash allows cobra to patch addresses in real time. my guess is that it checks the hash before patching to prevent instability. [MENTION=29]Joonie[/MENTION] might be able to shine more light on that.
 
pinky said:
I believe a correct hash allows cobra to patch addresses in real time. my guess is that it checks the hash before patching to prevent instability. [MENTION=29]Joonie[/MENTION] might be able to shine more light on that.
Click to expand...

hashes can be changed in the bin with hex editor?
 
bitsbubba said:
hashes can be changed in the bin with hex editor?
Click to expand...

yes, look up segment 0's hash from hashcalc in hex. then, overwrite that hash with paste+write (not paste+insert or u'll corrupt the file) with hashcalc's segment 0 of the modified self.
 
I had an idea that I thought would be cool, if there was an option to enter the URL for the XMBPD store in the toolbox or somewhere, so then explore sprx could be patched on the fly with it, then if anybody wanted they could access private/unofficial XMBPD lists of packages just by typing in a new URL. It would solve the cobra issue too if cobra was actually doing the patching.

Here is the video that [MENTION=16840]0_obeWAN[/MENTION] made, way higher quality and shows how easy it is to install , thanks again for all your time:

[video=youtube;zuoKiG-kuvA]https://www.youtube.com/watch?v=zuoKiG-kuvA&feature=youtu.be[/video]
 
Last edited:
[MENTION=6]bitsbubba[/MENTION] , try this:

Code: 
http://www.mediafire.com/download/8kiks5qu91kf585/PS3~dev_blind~rebug~cobra.zip

I fixed the hashes...I hope.
 
DeViL303 said:
So if ANY sprx or self is modified cobra doesn't work? is this for safety or security or what? seems a bit OTT, I only want to change 1 URL mainly and a title and icon name.. :)

Think im going to leave the tv sprx and network sprx unchanged for now as im making no progress. It means XMBPD will have a spinning icon and no title on ingame XMB for now but it could be worse. Going to concentrate on other things and come back to this later (might not be possible)
Click to expand...

No there are list of patches that COBRA does dynamically upon events.

VSH ones are critical as it directly affects PSP/PS2 which is why it is important to update hashes for spoofers as it swaps VSH

Anyways here is the quote from COBRA dev himself.

Almost all CFW patch the following files statically:


/dev_flash/vsh/module/vsh.self
/dev_flash/vsh/module/basic_plugins.sprx
/dev_flash/vsh/module/nas_plugin.sprx
/dev_flash/vsh/module/explore_plugin.sprx
/dev_flash/vsh/module/explore_category_game.sprx



COBRA dinamically patches those and also:


/dev_flash/vsh/module/bdp_discheck_plugin.sprx
/dev_flash/vsh/module/game_ext_plugin.sprx
/dev_flash/ps1emu/ps1_emu.self
/dev_flash/ps1_netemu.self
/dev_flash/pspemu/psp_emulator.self
/dev_flash/pspemu/release/emulator_api.sprx
/dev_flash/pspemu/release/emulator_drm.sprx
/dev_flash/pspemu/release/PEmuCoreLib.sprx
/dev_flash/sys/external/libsysutil_savedata_psp.sprx
/dev_flash/sys/external/libfs.sprx
Click to expand...

SRC : COBRA 7.00 Information (Release / Source)
 
pinky said:
[MENTION=6]bitsbubba[/MENTION] , try this:

Code: 
http://www.mediafire.com/download/8kiks5qu91kf585/PS3~dev_blind~rebug~cobra.zip

I fixed the hashes...I hope.
Click to expand...
works perfect thanks pinky, you're my hero :p
 
bitsbubba said:
works perfect thanks pinky, you're my hero :p
Click to expand...

I'm glad. :) I fixed hashes for the first time with the gameboot, but I never tested it. I used the normal cex/dex stage 2 files here, so hashes haven't been corrected for gameboots here. [MENTION=29]Joonie[/MENTION] 's posting will help in knowing what to fix or perhaps not bother. [MENTION=7]atreyu187[/MENTION] , said my original fix, uncompressed, for gameboots worked with cobra without hashes fixed. maybe it was due to being uncompressed? it's one of the sprx files listed by joonie, so I dunno.
 
I wonder does anyone know what type of "encryption" this is in bold or of any possible methods for solving this? I don't think its really secure, just some kind of substitution code maybe. Could really help add a new feature to XMBPD.

you tube entry in xml said:
<data name="416d46fc0d7cf66c64d6c940c227e13a073e8a1a-397458.txt" type="120">WW91VHViZSBhbGxvd3MgdXNlcnMgdG8gdmlldyB1c2VyLWNyZWF0ZWQgdmlkZW9zIGFuZCBjb21tZW50cy4gSWYgeW91IHNoYXJlIHlvdXIgZGV2aWNlIHdpdGggY2hpbGRyZW4gd2hvIHVzZSBTb255IEVudGVydGFpbm1lbnQgTmV0d29yayBzdWItYWNjb3VudHMsIHBsZWFzZSBub3RlIHRoZSBuZXR3b3JrIGNvbnRyb2xzIHlvdSBoYXZlIHNldCBmb3IgdGhvc2Ugc3ViLWFjY291bnRzIHdpbGwgbm90IHByZXZlbnQgdGhlbSB1c2luZyBZb3UgVHViZSBvbmNlIHlvdSBkb3dubG9hZCB0aGlzIHNvZnR3YXJlIHRvIHRoaXMgZGV2aWNlLg==</data>
Click to expand...

That code displays the following message after you select youtube (official):
HYXxes7.jpg



If we can "break" this "code" then we can have similar info screens added for each homebrew, with do's and dont's, usage instuctions, etc. If I try change it too much it just breaks and nothing or like 1 character comes up, so I cant use trial and error to figure this out.

Singstar:
Singstar entry in xml said:
<data name="912d87b20c235994229d5f49c9decc81dc19c887-964681.txt" type="120">QmVsdCBvdXQgdG9wIHR1bmVzIHdpdGggeW91ciBtYXRlcyBpbiBTaW5nU3RhcuKEoiwgdGhlIGJlc3QgcGFydHkgZ2FtZSBmb3IgaGF2ZS1hLWdvIHNpbmdlcnMgZXZlcnl3aGVyZS4KU3RhcnQgeW91ciBwYXJ0eSBub3cgYnkgZG93bmxvYWRpbmcgZnJlZSBkZW1vIHNvbmdzIQpEb3dubG9hZCBvZiB0aGlzIHByb2R1Y3QgaXMgc3ViamVjdCB0byB0aGUgU29ueSBFbnRlcnRhaW5tZW50IE5ldHdvcmsgVGVybXMgb2YgU2VydmljZS9Vc2VyIEFncmVlbWVudCBhbmQgYW55IHNwZWNpZmljIGFkZGl0aW9uYWwgY29uZGl0aW9ucyBhcHBseWluZyB0byB0aGlzIHByb2R1Y3QuIElmIHlvdSBkbyBub3Qgd2lzaCB0byBhY2NlcHQgdGhlc2UgdGVybXMsIGRvIG5vdCBkb3dubG9hZCB0aGlzIHByb2R1Y3QuIFNlZSBUZXJtcyBvZiBTZXJ2aWNlIGZvciBtb3JlIGltcG9ydGFudCBpbmZvcm1hdGlvbi4KTWluaW11bSBIREQgc3BhY2UgcmVxdWlyZWQgMzAwTUIuIEF1ZGlvIGlucHV0IGRldmljZSByZXF1aXJlZCBmb3Igc2luZ2luZyBnYW1lcGxheS4KU2luZ1N0YXIgwqkyMDEyIFNvbnkgQ29tcHV0ZXIgRW50ZXJ0YWlubWVudCBFdXJvcGUuIFB1Ymxpc2hlZCBieSBTb255IENvbXB1dGVyIEVudGVydGFpbm1lbnQgRXVyb3BlLiBEZXZlbG9wZWQgYnkgU0NFRSBMb25kb24gU3R1ZGlvLiDigJxTaW5nU3RhcuKAnSBpcyBhIHRyYWRlbWFyayBvciBhIHJlZ2lzdGVyZWQgdHJhZGVtYXJrIG9mIFNvbnkgQ29tcHV0ZXIgRW50ZXJ0YWlubWVudCBFdXJvcGUuIEFsbCByaWdodHMgcmVzZXJ2ZWQuDQo=</data>
Click to expand...

Translates to:
Brx35qx.jpg




I have no idea why sony have garbled the simple info message when all the more important info like the pkg link, the content ID etc is all in plain text? (its the same for any other apps that have an info screen before installing). It has crossed my mind that the .txt filename is actually the key to decrypt but Im not so sure how to work it out..
 
Last edited:
pinky said:
I'm glad. :) I fixed hashes for the first time with the gameboot, but I never tested it. I used the normal cex/dex stage 2 files here, so hashes haven't been corrected for gameboots here. [MENTION=29]Joonie[/MENTION] 's posting will help in knowing what to fix or perhaps not bother. [MENTION=7]atreyu187[/MENTION] , said my original fix, uncompressed, for gameboots worked with cobra without hashes fixed. maybe it was due to being uncompressed? it's one of the sprx files listed by joonie, so I dunno.
Click to expand...
I can't get hashcalc to work on win8.1 64bit :(
 
bitsbubba said:
I can't get hashcalc to work on win8.1 64bit :(
Click to expand...

Dam, Im on Win 8.1 x64 too. Let me know if you've any luck as looks like ill need to be able to do this.

Small progress, I have an installer made up for Rebug 4.70, 4.75, 4.76, 4.78 now. but of course it still needs the hash's fixing as ive changed the 4 sprx's.

The title on the XMB is now "★ Package Downloader" so it matches "★ CFW Settings" and "★ Package Manager", changed the title to that in the rco for all languages.

Also Ive changed the name of the icon used for this as it allows for a tidier uninstall (XMBM+ installer doesnt delete files so before the icon was left behind after uninstalling, now its a 100% clean uninstall with no files left behind).

Gonna look at adding some howebrew games next.

btw: updated movian pkg available via XMBPD as a new version is out today v4.99.754 .
 
bitsbubba said:
xmbpd 0.17.01?
Click to expand...

Well yeah , my version numbers can jump up randomly sometimes depending how many times ive changed the files here myself (have mixed up files before and reverted by mistake so I make lots of version changes on local files) and time put in etc. :) and as its got support for the older FW's I thought maybe jump to 0.17. and start from there again so its easier that everything after 0.17 supports 4.70+ and has the new look. I dunno though, im open to suggestions, just winging it here :)

As the first POC release was 0.10 I thought we could make the next proper public release v0.20.00
 
DeViL303 said:
Well yeah , my version numbers can jump up randomly sometimes depending how many times ive changed the files here myself (have mixed up files before and reverted by mistake so I make lots of version changes on local files) and time put in etc. :) and as its got support for the older FW's I thought maybe jump to 0.17. and start from there again so its easier that everything after 0.17 supports 4.70+ and has the new look. I dunno though, im open to suggestions, just winging it here :)

As the first POC release was 0.10 I thought we could make the next proper public release v0.20.00
Click to expand...

so the pkg you sent me is most current?
 
You must log in or register to reply here.

Similar threads

Back
Top