PS3Hax member aldostools has released a nice homebrew tool he is calling: CreatePS3EXTRA

What does it do? To quote:

It scans for the PKG, MP4 and P3T files copied to each game folder or its PS3_UPDATE folder, and store them under a PS3_EXTRA structure. When a game is mounted with multiMAN, there will be 2 BD icons on the XMB: one disc for the game itself and another with PKGs, MP4 and P3T. It should make it easier to install the game patches, DLC, fixes, and related videos.

[Grab the download + more information here]

Your Ad Here

reActPSN, the first OFFLINE PSN license generator has been updated to v2.20. The new update brings various changes, to quote:

1. Compatible with reActPSN v2.00.
2. Changed v2.0 backup file format to one zip file, backup speed fast more than 20 times.
Fixed some rap long name bug.
3. Added edat fix mode, this mode works on any CFW, no need aa user or patched vsh.self.
(1) Auto generate XMB purchase full activation edat, no need any raps or official edat files.
Install official LIMBO.pkg TERIS.pkg HCU.pkg,
Run reActPSNv2.10 and keep pressed BUTTON_CIRCLE about 6s, all will be full working.
Higher PS3_SYSTEM_VER also be fixed in SFO files (old save data could not be accessed).
(2) Fix PSone PSP THEME with raps. raps from USB0(1)/exdata/*.rap .
Install official PSone PSP THEME, copy raps to USB0(1)/exdata/ folder(not in subDirs!).
Run reActPSNv2.10 and keep pressed BUTTON_CIRCLE about 6s, all working.
And also fix PARAM.SFO to enable PSP remote, higher PS3_SYSTEM_VER also be fixed.
(3) DLC, in game purchase PSN games now working on this fix mode(not sure for all PSN contents).
Install official 1942.pkg Flower.pkg , copy raps to USB0(1)/exdata/ folder(not in subDirs!),
Run reActPSNv2.20 and keep pressed BUTTON_TRIANGLE about 6s, all will be working,
1942 is full working, Flower still has a error, (press PS KEY)exit to XMB,
Run reActPSNv2.20 again and keep pressed BUTTON_TRIANGLE about 6s, Flower is full working.

DLC also could be fixed with this TRIANGLE mode.
As I know, EBOOT.BIN with self.flag=4 does not works, and don’t run MM with BDEMU2 mode.
All fixed contens maybe still woking on cfw4.0 with data transfer(All signed with …….).
TRIANGLE mode only fix dev_hdd0/game/TITLE_ID/ BIN-sprx-edat-EDAT-self files.
There is a BUTTON_SQUARE mode searching for all type files, but slowly.
(4) Backup v2.10&v2.20 full fixed PSN contents.
Run reActPSNv2.20 and keep pressed BUTTON_R2 about 6s,
All fixed games(only full working) backup to /dev_usb000(1)/reActPSN/FixedNPD

Please use reActPSN v2.00 Raps mode. Only Raps mode works flawlessly for all PSN contents!

XMB purchase- purchase menu is in XMB. CFW3.55, target PSN LOGO, press BUTTON_TRIANGLE.
Activated with edat and rif, trial and full with one installed package.
in game purchase PSN games — purchase menu is in game. Activated with one rif only.

[Download v2.20]

Thanks to aldostools for news tip!

Your Ad Here

The latest update to the multiMAN cobra manager has been released bringing various new and updated features. There are some interesting new updates being made on the manager

To quote:

* Added new display mode (Board 5x4x5), replacing the oldest “Game list (plain)” mode
>”Board” display mode shows ICON0.PNG game images by default. You can use covers by changing the option “XMMB Icon Swap” in Settings

* Improved File Manager visuals when used in SD resolution (480p/576p)

* Fixed an issue, which prevented operation on CFW/MFW 3.41

* Added support for showing PSN titles in all display modes from internal/external HDD (PSN titles cannot be loaded and you have to put empty RELOAD.SELF in game’s USRDIR folder to make it show!) (requested)

* Added lastGAME2 and bdRESET applications

* Added 11 new themes to the theme download section (total of 14 now)

* Updated 15 language files

* Added separate background images for Board and XBDM display modes (PSVBG.JPG and XBDBG.JPG)

* Updated mmCM Original Theme (includes new images PSVBG.JPG, XBDBG.JPG, PBOX0.PNG, PBOX1.PNG)

* Preparations to support loading of network PS3, DVD and Blu-ray ISO files

* Preparations to support firmware version spoofer (auto-spoofing to latest official FW or to user-defined fixed version)
> Required Cobra USB update will be announced when network ISO and firmware spoof support is available

For those of you who own, or plan on purchasing a ProgSkeet flasher, there is some good news.  We have just received confirmation that the offical NOR clips for ProgSkeet will start shipping very soon. The price of the clip is not yet confirmed, but we do know that the clip will NOT require a tristate solder wire to use. We will have pictures for you soon. More information about ProgSkeet can be found over at their official site.

Thanks to nikitis for the news tip.

For the True Blue users on these forums, the newest update to the dongle, v2.5 has been released. The new update just brings various game compatibility fixes. Requires 3.55 TB CFW v2.

True Blue dongle firmware v2.5 has been released. Changes include:
• Requires True Blue CFW v2
• Game compatibility fixes

[Download Update + CFW]

PS3 Dev Evilnat (aka nathan_r32_69) has released a couple of command line based app’s,here are quotes from the read me’s.

PUP Unpacker & Decrypter v2.2

Changes
——-

v1.0 – Initial release

v1.1 – Added more tasks

v1.2 – Keys bug fixed

v1.3 – Fixed bug on folders

v2.1 – Added options menu in help screen
- “pup_PD.exe” modified, now can unpack “spkg_hdr.tar” and “ps3swu2.self” files on 3.56+ PUP
- Added function to decrypt “index.dat”
- Added function to unpack RCO files
- Added function to unpack and convert VAG to WAV files

v2.2 – Aded function to decrypt and unpack Core_OS

What we can do automatically with this program?
———————————————–

- Unpack PUP
- Decrypt TAR/PKG/SELF
- Decrypt index.dat
- Decrypt Core_OS
- Unpack Core_OS
- Unpack decrypted TAR/PKG
- Unpack RCO files
- Unpack and decrypt VAG to WAV files

__________________________________________________________________________________________________

$./pup_unpacker.exe

PUP Unpacker & Decrypter v2.2
By Evilnat

Usage: pup_unpacker.exe [OPTION] filename.pup directory
Example: pup_unpacker.exe -all PS3UPDAT.PUP OFW355

Options (ONLY CHOOSE ONE):

-h, –help displays this help
-x, –un-pup unpack PUP files only
-e, –un-tar unpack update_files.tar of PUP only
-c, –deun-core decrypt and unpack Core_OS of PUP file only
-t, –deun-tar decrypt and unpack TAR files of PUP only
-p, –deun-pkg decrypt and unpack all PKG files of PUP only
-s, –de-self decrypt all SELF files of PUP only
-i, –de-index unpack and decrypt index.dat of PUP only
-v, –conv-vag unpack and convert VAG to WAV files of PUP only
-r, –deun-rco decrypts and unpack RCO files of PUP only
-all, –deun-all unpack and decrypt entire PUP files

__________________________________________________________________________________________________

- Usage:

1) Unpack folder of RAR on your home directory in Cygwin (C:cygwinhomeXXXXUnpacker)
2) Copy PS3UPDAT.PUP file you want in it
3) Open Cygwin’s console and enter the folder
4) And type: (OFW_355 is an example, you can change this)

./pup_unpacker.exe [OPTION] PS3UPDAT.PUP OFW_355

[ Example: ./pup_unpacker.exe -all PS3UPDAT.PUP OFW_355 ]

5) Now depending what option you had choosen the executable will do it all automatically

All is done, “dev_decrypted_unpacked” folders contain self decrypted files

This program requires certain exe files and PS3 keys that are included in RAR, DONґT DELETE THEM
If an error occurs it will stop automatically, showing what has happened
Hope this helps someone

——————————————————————–
——————————————————————–

Thanks to: KaKaRoTo, Waninkoko, Geohot, Team Overflow, and more DEVS

——————————————————————–
——————————————————————–

Evilnat (PS3SOS/PSVITASOS)

Download

PS3 PUP/Dev_Flash File Spoofer v3

Spoofer v1.2
============

* What does this program?
———————-

- Find values of version and Image version on version.txt file
- Find values of version and Image version on vsh.self file
- Modify original values for you prefered
- Creates index.dat
- Rebuild self file

Put your vhs.self and version.txt files on folder where spoofer.exe is and put Version and Image Version you wish to spoof

*************************************************************************
***** CAUTION! ONLY USE FILES OF CFW YOU HAVE INSTALLED ON YOUR PS3 *****
*************************************************************************

_________________________________________________________

Spoofer v1.2″
By Evilnat”

Usage: spoofer.exe [FW VERSION] [IMAGE VERSION]”
Example: $0 04.5500 60917″
__________________________________________________________

It will retrieve info about version and image, decrypt self file, create index.dat and rebuild self file

Finally copy those three files to your PS3

***** If you do something wrong you will see red screen on your tv, if that happend re-install your CFW on Recovery Menu *****

Regards
- Evilnat

Download

Source PS3SOS

A while ago, a pre release of showtime v.3.4 was released, now the developer has been kind enough to provide us with Showtime v.3.4. A few quick notes:

And a Full changelog:

Download version 3.4 for 3.55 CFW
Download version 3.4 for GeoHot 3.55 CFW
Download SELF

Source lonleycoder.com
Check the source for a short history of Showtime on the PS3 and a bit of what Andreas Öman plans to do with his app in the future.

PS3HaX Developer DeViL303 has updated XMB File Manager(XMBFM), he has two versions and they are both included in the download.

D = Works on Debug Rebug Menu
R = Works on 3.55 OFW/Kmeaw and Retail Rebug Menu

Here is a quote from the thread:

I have updated the release to XMBFM Beta v0.03D and XMBFM Beta v0.03R (with D suffix for 3.55 Debug XMBs and R suffix for 3.55 Retail XMBs)

Gonna Change the suffix next time a its confussing because “R” could be for Rebug but it not, it should work on any 3.55 retail xmb, 3.55 kmeaw , 3.55 Official FW, rebug 3.55 retail xmb(in rebug mode) etc.

Download XMBFM Beta v0.03D and XMBFM Beta v0.03R

If you want to give a helping hand, you can also participate in this thread if you wish to:
Technical thread with Code Relating to XMB xml/rco hacks and XMBFM etc

naehrwert has updated his scetool, it now fully supports SELF’s.

Download

Although to most of you this is not big news, I decided to take few pictures of the procedure for using Remote Play on your PS Vita to access your CFW 3.55 PS3.

The main “trick” is to register your PS Vita as “mobile phone” , so that’s about it.

You need:

* PS Vita (mine is on FW 1.05)
* PS3 (mine is on FW 3.55 KMEAW)
* USB Cable (provided with PS Vita) to register the vita to the ps3
* Wi-Fi network to use the remote-play at home
* 2 mins total to complete the registration

More pictures at read more link…..

(more…)

PS3HaX member DeViL303 has released an XMB Filemanager, which allows you to browse the entire PS3 filesystem, straight from the XMB, here is a quote from the developer:

I have made a little XMB mod for Rebug 3.55.2 that I call XMB File Manager (XMBFM). It is a modded version of Rebug’s package manager that allows the entire ps3 filesystem to be browsed and also any files types can be seen and deleted. Im hoping to add things like copy function etc but would like to get feedback and help if anyones game?
This wont work on standard CFW for now , only on Rebug , but i will release a standard version in next few days if anyone thinks I should bother. Please like this post as it will encourage me 

This is a beta version for anyone who might be interested in helping me test it or improve on it.

Install instructions: It requires you to switch 2 files from dev_flash. heres a quick tut:
- I use multiman , go to settings near the bottom of menu.
- select the mount dev_flash to dev_blind option. click enable
- next go to multiman file manager
- copy over the 2 files to thier different locations
- category_game.xml goes in dev_blind/vsh/resource/explore/xmb/
- explore_plugin_full.rco goes in dev_blind/vsh/resource/
- next disable dev_blind option in multiman
- then exit multiman to see your new XMB File Manager 

This is perfectly safe and I have even tested deleting most of dev_flash before and its easy reinstall FW through recovery menu so dont worry, just make sure you are on Rebug 3.55.2, It migtht cause a error on normal 3.55CFW

Have fun and let me know if you have an ideas on how I could expand it by adding things like copy function etc. Im not the best at this so any help is much appreciated? 

Big Thanks to Cyberskunk and Evilsperm (Team Rebug) for the package manager which this is based on. And also for Rebug CFW.. its my favourite!

Please before anyone flames that this is crap I did only start properly making it last night so give me a little time and maybe it will become cool. (I discovered the “exploit” that allows this back in 2010 but didnt get around to doing anything with it until now)

If anyone wants to explain an easy way of making this into a pkg file I would be delighted to hear or get some help, Im sure its not very difficult but I havnt time to figure out everything and would like this to become even more of a collaboration if anyones interested?

DeViL303 @ ps3hax.net

Source, here on PS3HaX

UPDATE

There was a problem with the previous upload, that has been fixed now.
Download

UPDATE 2

It has been confirmed that this method works on 3.55 OFW, by gliitch, so there may be a possibility of it working on 4.0.

UPDATE 3

It has been confirmed that this works on 4.0, for more info, check this post.

A PS3 Dev by the name of ps3hen has shown a video of him installing PKG’s on 4.0 OFW, here is the video followed by a quote from the dev.

Note: This modification does not allow the installation / usage of unsigned content / PS3 homebrew etc. This is purely a convenience hack and is aimed for use by those who have hardware flashers which allow dual boot.

After technodon’s work creating a modified kiosk dev_flash which lets you install retail signed package files. The restrictions of having to use kiosk firmware inspired me to find a way to add “Install Package Files” for retail firmware.

This is hack does the following things:

• adds “★ Install Package Files” and “★ /app_home/PS3_GAME/” to “GAME” on the XMB (allowing the user to install retail package files anytime they want)
• adds other debug functions which are small but still there
• does not give access to “★ Debug Setting” (reasons for this are explained below)

Installation instructions:

This installation procedure is the similar to technodon’s original dev_flash hdd swap procedure

For this you will need two hard drives a e3 flasher or similar device to downgrade your PS3 (assuming that you’re on firmware 4.00 and you have an e3 flasher)

• downgrade to 3.55 using the downgrade tools from e3 (Of course when downgrading to 3.55 make sure you use a different hdd than the hdd which you were using 4.00)
• once booted back into the xmb turn off the console
• swap hard drives turn on the system, press the PS button and you will be asked to reinstall the firmware
• place the pup file from the e3 downgrade tools in the normal PS3/UPDATE usb folder and follow the on-screen instructions to reinstall the firmware
• then install dev_blind.pkg & Blackb0x FTP from install packages
• run dev_blind then BlackB0x and FTP into the console
• goto /dev_blind delete everything and replace them with the customised dev_flash
• press the ps button and the console should reboot and and ask to reinstall the firmware again, switch off the console and swap the hard drive back
• turn on the console press the ps button twice
• the console should boot back into 3.55 Rogero
• goto system update and install 4.00 OFW
• once installed turn the console off again and swap hard drives back and you should boot into a modified 4.00 retail firmware.

My package (Click to download) includes:

• My modded dev_flash
• OFW 4.00 PS3UPDAT.PUP

P.S. BTW the “nas_plugin.sprx” in this dev_flash has not been altered to achieve “Install Package Files”. Also for those who will analyze my modded dev_flash, you will find that I have used debug .sprx files from the a debug 4.00 pup.

P.P.S. I originally intended to get “★ Debug Settings” to work with this. But usage of “debug settings” required the ps3 to use a debug vsh.self, and that crashes the ps3 when trying to load applications (I did some other things as well to prevent the PS3 from giving me a RSOD when I swapped the vsh.self files, I’m not detailing it in public because I don’t want Sony to patch it).

Source Tortuga Cove

UPDATE

PS3Hen has released an .pup file, which makes the above process much easier, here is a quote from his post:

Before I move, on status update on getting “Debug Settings” on OFW 4.00. Its still a bit buggy, so more work needed there.

I’ve managed to put my efforts into a .pup file, which should make the installation of my mod much easier.

Also today I was on another site where user DeViL303 had released a beta of his XMB File Manager (substitute for Install Package Files, but a lot better) and DeViL303 theorized a FW 4.00 port was possible. So I took on the role on making the port for FW 4.00 and after posting it on that thread I integrated it into my firmware. So now I’ve upgraded my firmware mod and put into a .pup.

Here’s some new installation instructions(much shorter, I know isn’t great):

1/Be on a firmware 3.55 or less
2/Install the .pup through the XMB (Make sure you have a working hardware flasher as there is no other way to downgrade)

Remember only retail signed .pkg can be installed with this. Have fun.

Download .pup

deroad a PS3HaX member, developer and MAJOR contributor to both PS3 Dev Wiki and Vita Dev Wiki, has released a snazzy little home brew app, which he calls Buzzer Player, here is a quote from the thread and readme:

i wrote it for naruse and euss since we was talking on the irc about the buzzer.

maybe someone will find it funny xD

this is a simple player
it reads two var (var1 and Var2) from a file.

the file must be called buzzer.txt and placed in the main folder of a USB an example:
on Windows:
My USB is j so, i will put this file here: j:/buzzer.txt

on OSX: My USB is 8GB so,
i will put this file here: /Volumes/8GB/buzzer.txt

on LINUX: My USB is 8GB so,
i will put this file here: /media/8GB/buzzer.txt

======Beeps=======
Var1 Var2 DESCRIPTION
4 6 Makes a short single beep
10 438 Makes a double beep
7 54 End
10 4095 Makes a continuous beep

Source here at PS3HaX

Download Multiupload(Megaupload link wont work)

Before you start b*tching at me that this isn’t PS3 news, yeah i know, but it is still important, Megaupload was used for uploading PS3 homebrew by a lot of people, so some people who amassed a nice little homebrew collection on Megaupload have lost it, i know certain devs used it for uploading certain files, theme creators etc, now its all gone, lost, so if you are trying to download your favourite multiMAN theme and don’t understand, why, now you do., this all done and without SOPA in force, to be blunt, if the US Government deems sites like PS3HaX a danger, they dont need SOPA, they can just come and close it down.

From
Department of Justice
Office of Public Affairs

(more…)

Condorstike has released two updates recently to his popular Solar homebrew application, here is a readme/changelog from the most recent version.

Hi guys, here’s another update to Solar. Lots of things fixed and added, and more to come. Hope you enjoy it, and if you have any questions or suggestions feel free to ask in the FORUMS.
caw!

Solar v3.1
Changelog:
Fixed bug while removing USB drives “hot-pluging now works”.
Added more USB devices compatibility.
Added more UI for mp3 player.
Added Exit Dialog interface. “very fast and user friendly”.
Faster Loading to multiMAN and Browser.
Fixed a memory bug.
Fixed hang/crash if MP3s were not found.
Added Message for Hot-plugging and End of Playlist.
Increased Solar’s boot time.
Fixed Keytones, now single beeps, and removed for some keys.
More code cleanup, and other things I can’t remember.

Source Tortuga Cove

Im sure everyone by now knows of TeaM AC1D and their work on the PS3, their claims of knowing how True Blue Works, their discussion about SPRX’s etc, you can find the discussion here.

True Blue respond to those claims with this statement:

Recently we have been made aware of several announcements made on various forums from people who seek to trivialise the capabilities of True Blue and claim that functionality such as playing 3.6+ games can easily be reproduced on regular custom firmware (CFW).

In each and every case, the announcements amount to nothing more than baseless accusations and disinformation – these people are intentionally spreading information they know to be incorrect in an attempt to create confusion. A lot of effort and research has gone into the creation of True Blue, which has allowed us to take our position as the ONLY team producing any real results, providing solid support and benefits for our customers. For all the people who have claimed that what True Blue does is trivial and can be easily duplicated, there has been absolutely nothing that has come from any of these peopole, they have simply been all talk and have delivered nothing of real value.

The proof is in the result and at the end of the day, with all the claims that have been made by other groups, the fact remains that the True Blue team are the only ones who have actually delivered.

Now “The Scene Donkey” tries to rubbish TeaM AC1D’s claims with his usual babble, pretending he knows what he is talking about, so he makes a thread, on his home forum stating this:

The supposed SPRX theory and why it’s wrong.
First of all, I might of put this in the wrong section and for that I apologize. Second, I’m putting this here in an effort to destroy all the misinformation going around from the rest of the forums and some members here. Hopefully Gary will come in and reaffirm this topic so people do know I’m telling the truth.

now yes there was a “news post” or “theory post” up from it. But of course it got locked. Why? Because it was completely wrong and purposed by a known individual that spreads misinformation in an effort to raise his popularity. That is your very first clue that this theory is completely false. Wish it was still up so Gary could have simply put up a message officially stating how bogus it was so people would know. But hopefully he’ll do it here.

Anywho, so why is the SPRX theory wrong? Well as all of you should know the PS3 uses keys to encrypt, decrypt, and basically authenticate everything on the system. Games are no exception. The keys required for games are stored in Appldr (IIRC. Or it’s isoldr. But I’m 95% sure it’s appldr.) Not some “drivers” or otherwise called SPRX. That is the reason why people haven’t just taken SPRX from a higher firmware, cracked them, and put them on a 3.55 CFW. It’s because they have nothing to do with getting games running. Nothing. Plus it’s impossible to do so. That’s also the reason why we have never messed with SPRX to date. We have always messed with eboot.bin’s which are signed with the keys from Appldr.

Now if you still don’t 100% believe that the SPRX theory is total BS, ask yourself two simple questions. Why hasn’t someone cracked the SPRX already? Why have we all used eboot.bin’s and requested new keys from higher firmwares? It’s because SPRX don’t have anything to do with getting games to function.

So then why has team ac1d come out with this theory? Well I won’t get on this bashing wagon, but just look at how the scene has been up to this point. That should give you a good indication of why. But they are spreading misinformation, that much I will say.

Still don’t believe me? Read the PS3devwiki.

Now the most ironic thing, is the last sentence, when PS3 Dev Wiki posted that they had dumped True Blue dongle, the “Scene Donkey” said it was all lies and stated that everything that was on PS3 Dev Wiki was false and lies, anyhow enough of my mini rant, on to the main story.

PS3 Developer deank replied to that thread, basically teaching the “Scene Donkey” right from wrong, this is what he states, deank in blue text, the “Scene Donkey” in pink text.

”Originally Posted by “Scene Donkey”
There isn’t anything to the SPRX theory. It doesn’t take TB to tell you. Hell open up the PS3devwiki. Anyone who knows ANYTHING about how the PS3 works, knows SPRX don’t have anything to do with running games on the system. Everything pertaining to games is controlled through Appldr and keys. Not SPRX. Otherwise games would ship with SPRX that contain the keys, in which case we would already have them.

Seriously, have we ever patched SPRX to run games? No? That’s your answer. SPRX don’t have a damn thing to do with it.  ”

Actually that’s not entirely true. Anyone who knows anything about programming (pc/mac *nix ps2/ps3) would spot discrepancies. I’ll try to put a very noob-friendly explanation below.

We can drop the big-ass words like SPRX/SELF/EBOOT.BIN and just use “executables” (selfs/elfs/eboot.bins) and “libraries/modules” (sprx/prx). To make it even easier to understand one can think of the executables as “EXE” and the libraries/modules as “DLL” in the windows environment.

Anyway, when talking about the SPRX you may have to differentiate GAME sprx files and FIRMWARE sprx files, because they are a bit different, because of the way they’re used.

”Originally Posted by “Scene Donkey”
Seriously, have we ever patched SPRX to run games? No? That’s your answer. SPRX don’t have a damn thing to do with it.”

Yes, we did – even the ebootFIX / ebootMOD applications process all game sprx+self+eboot.bin files – otherwise nothing would work. Since you can think of a game sprx file as a DLL, it is just a number of functions exported in a separate file, so you don’t have to load all of them along with your executable (EBOOT.BIN or blabla.exe). Whenever you need a function from the (sprx/dll) library – you load the library, call the function and unload the library. That’s all about the game sprx files.

The firmware sprx files… The explanation above can be used for these too, but the main difference is that all applications use these system-wide libraries. It could be games, the video player, the PS Store application or the photo-album slideshow. So each of these applications would at one point load a firmware sprx/library because they need its functions (to access files and folders, to access the network, to process jpg/png images, to read/mount/use psarc archives).

Let’s for a moment forget about keys and encryption, and focus on firmwares and the differences between the libraries/sprx.

We have a console (we name it THE_BOX), running firmware version 3 and we create an application for it, which prints a fancy text on screen. Such imaginary application will look like this:

Load system module: lib_screen.sprx (so we can use its functions)
Load system module: lib_text.sprx
Initialize screen: using init_screen(1920, 1080, 3D) function from system library lib_screen.sprx)
Draw fancy text: using draw_text(x, y, “Hello World”, red_color, vertically, with_water_effect) from system library lib_text.sprx
Wait for 30 seconds and exit

So we test our cool app on firmware version 3 and everything works as expected: a nice text is drawn in fullHD in 3D mode and has a nice water shader applied to it, so it really looks like made of water.

By accident we have a second console (THE_BOX_2), running firmware version 1 (rather old, but we need to test nonetheless). We load our cool app and launch it then we get:

* Black screen or
* Not so cool looking “Hello World” text in 2D, horizontally and not vertically, with the dull gray color and no effects applied).

What happened?!

We know that THE_BOX_2 is running an older version of the firmware and PROBABLY (most definitely) some internal/system modules are quite different. After a later investigation we find that the firmware version 1 has these two sprx libraries, but they provide much limited functionality:

* init_screen(1920, 1080) (it is missing the 2d/3d parameter)
* draw_text(x, y, “Hello World”) (no extended parameters)

It is pure miracle that our sample app even started on that OLD firmware version 1 and produced any results at all.

That should explain why FIRMWARE LIBRARIES (SPRX in the PS3) may affect games, performance and compatibility.

Now back to the reality. Back in the day (and even at the moment) there are games released for firmwares beyond 3.55, but we were still able to play them on 3.55. In most of these cases the games didn’t require nor used any special functions presented in the system libraries/modules of the newer firmware. Luckily even now with the PS3 firmware 4.00 there are games, which use the same functions that are available in the modules/sprx of FW 3.41-3.55.

So let’s say we have the keys and the game in question doesn’t use any of the firmware 4.0 functions – we process our 4.0 game with some tools and we get decrypted (from 4.0) + changed + encrypted/signed (for 3.55) all the eboot.bin/self/sprx fiels. Profit. Game works on 3.55.

Now we find another game and apply the same steps as above. But it happens that that particular game (like most that will follow) actually uses the NEW functions provided by the NEW modules/sprx files in the new firmware 4.0. We test that game and we find that it either doesn’t start at all (black screen) or starts with major glitches, locks after 2mins, etc. etc.

So we decide to make everything right. Since we’re really experienced, we’re going to find what SYSTEM modules from fw 4.0 that particular game requires. It is obvious that our ‘stock’ sprx files miss some functions and we have to find a way to add them or just use the newer module (hoping it won’t brake any other app installed on your loved ps3). We start looking at the game executables (eboot.bin/self) and game libraries (sprx) to find what modules are used. Of course these are not listed in plain text and most of the time you may not even see anything readable, but you’ll have to find the actual assembler functions which call for loading system modules with specific IDs. After couple of days/weeks we find all of the module IDs, so now we know which modules need to be replaced or further edited (because the usually call/use functions from OTHER system modules).

Once we’re absolutely sure we’ve got all that right, we sign (and encrypt if desired) the files for our THE_BOX_2 console (running the older firmware) and we enjoy the result.

Now back to the keys. Since the “S” in SPRX and SELF means “Signed” one must find a way to remove the protection of these system sprx files, of the game sprx/self/eboot.bin files and then work with their contents. Once you finish, you sign them again for your desired firmware with the desired keys (be it for 3.41, 3.55 or 4.0).

That’s about it.

I don’t own a TB dongle and the reason I posted this wall of text is to present a REALLY SIMPLIFIED explanation of what one may have to do EVEN if he has the keys for 4.0 firmware.

Not to dare or challenge anyone, but all of you have the opportunity to prove yourself by installing firmware 3.15 to your PS3 and then try to process UNCHARTED 3 to work on it. Basically everything is the same. If you can make UC3 to work on FW 3.15 – you’re a hero and the scene will love you.

I hope it wasn’t boring for you to read all that, but as a programmer and as someone who watched and learned I decided to clarify something that “anyone” should know.

D

The True Blue and the “Scene Donkey”/deank discussion can be found at PS3Crunch

So there you have it from every side, your decision to believe who you want, i hope it has been a good read

PS3 Developer KaKaRoTo has given a status update regarding his work on getting homebrew running on 3.56 PS3′s, there are quite a few revelations, none of which are a shock, so here is a quote from KaKaRoTo’s blog:

Here’s a “quick” status update on the 4.00 HEN (Homebrew ENabler) for PS3.

Following my clarifications from almost 2 months ago here, there has been a lot of progress. We have not been slacking off, we’re a group of about 10 developers working together for the last 2 months, for sometimes 15 hours everyday in order to bring back homebrew support to the latest version of the PS3.

There are three major parts to the HEN, first, getting the packages to install on the PS3, that part is done, completed, tested, debugged, etc.. the second part is to get the apps to run, that one still has major issues… the last part is something I will not discuss for now (it’s a surprise) but it’s about 60% to 70% done (and it has nothing to do with peek&poke and has nothing to do with backup managers or anything like that. This is and will stay a piracy-free solution for the PS3).

Now, running apps is the biggest challenge that we’ve been working on for the past 2 months. As some of you know, if you’ve been following me on Twitter, we originally had hoped for Mathieulh to give us the “npdrm hash algorithm” that was necessary to run the apps, but he was reluctant, he kept doing his usual whore so people would kiss his feet (or something else) so he’d feel good about himself. But in the end, he said that he refuses to give us the needed “npdrm hash algorithm” to make it work… So what I initially thought would be “this will be released next week” ended up taking a lot more time than expected, and we’re still nowhere near ready to make it work.

Mathieulh kept tossing his usual “riddles” which he thinks are “very helpful for those who have a brain”, and which pisses off anyone who actually does… so he told us that the solution to all our problems was to look in appldr of the 3.56 firmware.. and that it was something lv1 was sending appldr which made the “hash check” verified or not… so we spent one month and a lot of sweat and after killing a few of our brain cells out of exhaustion, we finally concluded that it was all bullshit. After one month of reading assembly code and checking and double-checking our results, we finally were able to confirm that that hash algorithm was NOT in the 3.56 firmware like he told us (at all).

He said that it was an AES OMAC hash, but after tracking all the uses of the OMAC functions in appldr, we found that it was not used for the “hash”… he then said “oh, I meant HMAC“, so we do that again and again come up with the same conclusion, then we’re sure it’s not in appldr, and then he says “ah no, it’s in lv1“.. have a look for yourself to what he decided to write : http://www.ps3devwiki.com/index.php?title=Talk:KaKaRoTo_Kind_of_%C2%B4Jailbreak%C2%B4

That happened after the huge twitter fight I had with him for being his usual arrogant ass and claiming that he “shared” something (For your information, the code that he shared was not his own, I have proof of that too (can’t show you the proof because even if I don’t respect him, I gave him my word to not share what he gave me, and I respect my word) since he forgot to remove the name of the original developer from one of the files… also it was completely useless and was not used at all, just made me waste a day reading the crappy undocumented code. So why is he still trying to force his “advice” through these riddles even after we had that fight? Well to sabotage us and make us lose all those months of hard work!

Read The Full Article Here

This being quite a big story, we had several people submit it, so thanks to all those that posted this news, all your articles have been merged into the one thread.

With so much crap going on in the scene, with people selling out and these DRM dongles, it is a breath of fresh air to see someone releasing something related to the PS3 scene, for fun and for free.

nativesith a PSX-Scene developer has released an update of his PS3 GTA IV mod, here is a quote from the source:

My latest Ish(lol), is just the beginning! Brace your selves for the work of Evil Blunt!
Also Silent_Pavel will be back! =) GTA IV has never been this cool n sexy!

Love my new handle, In May I will be in a Game Development course! It is fate.
P.s. Working on a new Playerped.rpf that has Niko with New colored Clothes!
Later =).

EDIT: Found the source of many problems with Ps3 GTA IV mods. Problems like freezing on the Dardan mission, and even the ******* X and Dwanye selection(even more problems..). IDE or Item Definitions Entries. The vehicle.ide, ped.ide and any ide of the common.rpf can not be changed.

Included:

• New Loading Sexy Screens
• Pause Menu with Old English Font
• New HUD
• Exotic Cars and Bikes Take No Damage
• Screen goes Red and Black when Niko Dies.
• Many PC textures imported to Ps3!
• Reality IV Visual PC Mod
• Niko has new Clothes & Beard!!
• Highlighted Weapon Icons
• In Car as one of Camera modes
• No Cops@ Airport(EvilB’s)
• No Non-Colored Radio Icons
• My Handling Settings
• FBI & SultranRS have Drift Handling.
• Latest Importing W/ No Helis or Boats!
• BloodyFX!!
• Colored Blips!
• This mod will not freeze @ Dardan Mission , Please let me know if it freezes on you.
• Meant to be used with Evil B’s qeens_e.img(The Evil Blunt Airport!)

How To Install:

• common and Ps3.rpf go in BLUS30127/Ps3_Game/USRDIR/
• vehicle and weapon.img go in BLUS30127/PS3_Game/USRDIR/ps3/models/cdimages.

Source PSX Scene

Download

Download EvilB’s Airport is you need it.