PS3 PS3 PRO MOD - Give your XMB a new look with these mods by LuanTeles

Here is a cool mod for 4.81 PS3 Custom Firmware user's as psx-place memeber LuanTeles has put together and released a suite of XMB modifications that he has dubbed the PS3 PRO MOD. This collections contains he PS3 PRO coldboot & gameboot, new boot & xmb sounds, New Custom Icons & new xmb wave , Checkout the video preview and see the included release post for additional details​
-STLcardsWS​

ps3pro.jpg
Release

  • Hey Guys, I made a little mod for PS3 to PS3 PRO as long now we have PS4 PRO, and our PS3 (w/ CFW) just does everything better than a regular PS3 so i created this PS3 PRO MOD


    The Mod Contains
    • PS3 PRO Coldboot
    • PS4 Boot Sound
    • PS4 XMB Sounds
    • PS3 strings changed to PS3 PRO
    • Some Custom Icons
    • PS3 PRO Gameboot
    • PS4 Gameboot Sound
    • PSP Wave Background

    UPDATE 6/22/17:     v1,1
    • Resized Pro Logo in GAMEBOOT to fit better
    • Dev_hdd0 custom RetroArch, PSP Launcher, PKG Launcher And Multiman ICONS like folders, to fit better the XMB

    Next Release: PS4 Browser Enter and Exiting Sounds​


 
Last edited by a moderator:
Click to expand...
pinky
see, I was right about not needing to recalculate the hashes since 7.50, but I assumed all the problems could be the result of not doing so. :-P that's probably y hashcalc wasn't working correctly. I did notice that new hashcalc on @Joonie 's github though earlier today. it's about half the size of the original calculator.

@borzas2010 ,

Code: 
https://www.mediafire.com/?8tz60x6snb0lajw

remember what I was talking about yesterday about there being a coldboot 1 and 2 on earlier firmware. well, here's coldboot 1 and 2 on 2.76. I only assumed the normal coldboot was coldboot 2 due to the size of the ac3 files. I've never listened to them. I hope u find what u need.
 
bguerville
pinky said:
see, I was right about not needing to recalculate the hashes since 7.50, but I assumed all the problems could be the result of not doing so. :-P that's probably y hashcalc wasn't working correctly. I did notice that new hashcalc on @Joonie 's github though earlier today. it's about half the size of the original calculator.

@borzas2010 ,

Code: 
https://www.mediafire.com/?8tz60x6snb0lajw

remember what I was talking about yesterday about there being a coldboot 1 and 2 on earlier firmware. well, here's coldboot 1 and 2 on 2.76. I only assumed the normal coldboot was coldboot 2 due to the size of the ac3 files. I've never listened to them. I hope u find what u need.
Click to expand...
Well I just messaged Joonie on Skype & am waiting for him to answer...

My guess is that Hash_newcalc is there to calculate hashes for older fw versions (pre 4.53?) that are not compatible with the Cobra static hashes & still require the old style hashes..

But there is one last thing I would like to ascertain though, it is how to calculate the new static hashes so they can be verified if required...

We will soon have our answers... [emoji6]
 
Last edited:
pinky
I think it might require a different version of cygwin1.dll than I'm using, because I did try to use the new calculator and I got an error through that file. I forgot what the error was, but it was something like "cannot find target entry." the cygwin1.dll as well as the other two dll's needed I copied from PUAD.
 
bguerville
bguerville
pinky said:
now, I get cannot open temporal file. self/sprx may be invalid or specific files are not installed.
Click to expand...
You have the scetool keys folder in PATH or in the folder?
Here is the code in the older hashcalc.cpp, I suppose the message was changed a little...
Code: 
fprintf(stderr, "Cannot open temporal decrypted file. Most probable reasons are that sce tools are not installed or self/sprx is invalid.\n");
 
Last edited:
pinky
well, the unself I think is the problem actually. the original one I was using was for PUAD, so it would use PUAD's keys' location. I think it even mentioned PUAD actually. lol I'll just wait for u to try it, then tell which files u have in the folder or send me a zip of them. I'm sure the files r named correctly, but Joonie's github has unself.exe when the fail0verflow one is named unself2.exe. maybe it's been modified? however, I don't think it has been since both files seem to be the same size. the cigwin files u sent me were all different sizes, so I don't know if that has any effect on the location of said files. it's been confusing me since last night. lol
 
bguerville
bguerville
pinky said:
could u send me the contents of ur hashcalc folder? I must be missing something.
Click to expand...
As you can see it calculates the new static hash!
I messaged Joonie for no reason..
He must be laughing...

I don't have anything else in my folder...
But my system is properly setup with all tools & keys in the PATH. Everything can be found automatically...
1df0732e1be935873b60aab716246aca.jpg
 
pinky
something must not be installed on my end. u don't even have cygwin in the folder. mine can't run without it, I guess because it's a linux terminal? plus, u have icons for the sprx files. I do not have that either. it appears that u have cygwin installed, however, is that a requirement?
 
bguerville
So I was right & I have confirmation from Joonie.
When habib said that the static hashes should not change, he meant they would most likely not change from one OFW update to another.
However patching a file can modify its static hash! It depends on the patch so after applying a patch on a file patched by Cobra, one should check with hash_newcalc that the static hash was not affected. If it is affected, a new stage2.bin is required. Ultimately, for the Cobra patches to succeed, Cobra must have the right offsets, if not the patches will fail leading to freezes etc...

If you compare the modulespatch code for Cobra in Alexander's repo (non Rebug) & in Joonie's repo (Rebug) you will notice differences because there are 2 versions of game_ext_plugin.sprx retail & debug with different offsets for the patches.
The retail game_ext_plugin.sprx should not be used on Rebug & the Debug version should not be used on CEX firmware.... Unless stage2.bin is modified & recompiled.
 
pinky
bguerville said:
So I was right & I have confirmation from Joonie.
When habib said that the static hashes should not change, he meant they would most likely not change from one OFW update to another.
However patching a file can modify its static hash! It depends on the patch so after applying a patch on a file patched by Cobra, one should check with hash_newcalc that the static hash was not affected. If it is affected, a new stage2.bin is required. Ultimately, for the Cobra patches to succeed, Cobra must have the right offsets, if not the patches will fail leading to freezes etc...

If you compare the modulespatch code for Cobra in Alexander's repo (non Rebug) & in Joonie's repo (Rebug) you will notice differences because there are 2 versions of game_ext_plugin.sprx retail & debug with different offsets for the patches.
The retail game_ext_plugin.sprx should not be used on Rebug & the Debug version should not be used on CEX firmware.... Unless stage2.bin is modified & recompiled.
Click to expand...

well, u see, I can't even fix the hashes if I wanted to, because the new hashcalc doesn't work on my laptop. I've tried various configurations, but I always get the same error. sce tools - what does that even mean? it's not specific about what app that is. at first I thought scetool, but then y would u need the keys in the hashcalc folder? I have scetool installed in a regular directory as well as the one supplied with ps3tools.
 
bguerville
pinky said:
well, u see, I can't even fix the hashes if I wanted to, because the new hashcalc doesn't work on my laptop. I've tried various configurations, but I always get the same error. sce tools - what does that even mean? it's not specific about what app that is. at first I thought scetool, but then y would u need the keys in the hashcalc folder? I have scetool installed in a regular directory as well as the one supplied with ps3tools.
Click to expand...
This error message pops up if unself failed, it requires unself not unself2 & the keys...
 
pinky
bguerville said:
This error message pops up if unself failed, it requires unself not unself2 & the keys...
Click to expand...

that's how I have it setup. unself won't decrypt the self/sprx file unless it contains 2 or 3 dll files (the ones I already had). it's baffling. u must have cygwin installed (I think) or else it fails. the cygwin dll files don't seem to work correctly with unself, so it fails.
 
bguerville
pinky said:
that's how I have it setup. unself won't decrypt the self/sprx file unless it contains 2 or 3 dll files (the ones I already had). it's baffling. u must have cygwin installed (I think) or else it fails. the cygwin dll files don't seem to work correctly with unself, so it fails.
Click to expand...
It works for me with both the unself.exe(186kb) included in the hash_newcalc folder & with the unself2.exe binary (131kb) renamed unself.exe
 
You must log in or register to reply here.

Similar threads

Featured content

Trending content

Latest posts

Back
Top