Mont Blanc Pen

Solar v3.0 PS3 Homebrew 3D Screensaver Update Arrives

2012-01-29T18:45:00.000-08:00

Following up on my previous release, today on Tortuga-Cove I have released my Solar v3.0 PS3 Homebrew 3D Screensaver update followed by version 3.1 below.

Download: Solar v3.0 PS3 Homebrew 3D Screensaver / Solar v3.1 PS3 Homebrew 3D Screensaver

Now Solar v3.0, which brings many new MP3 player features and fixes, including an UI and the option to use your own background music, and much more.

To quote: Hi guys, here's another update to Solar. Lots of things added, and more to come. Hope you enjoy it, and if you have any questions or suggestions feel free to ask in the Forums.

"And please, lets keep the scene going; bickering just hurts it, and takes the fun away." caw!

Solar v3.0 Changelog:

Background music is now customizable "replace /dev_hdd0/game/CNDR00001/USRDIR/theme/bgm.mp3" with your own music
Alphabetized mp3 directory.
Added UI for mp3 player.
Fixed music counters, now shows in seconds: "00:01" format and Total Playtime format: "4.5 minutes".
Removed mp3 path from displayed name, looks cleaner.
Fixed Volume controls, now up and down is seamless.
Added current player status messages: playing, paused, error... etc.
Added keynotes.
Increased mp3 load times and stability.
Improved fast forward and reverse functions.
Increased 3D display frame-rates while playing music, needs some work in BGM mode.
Lots of code cleanup, and other things I can't remember.

BTW, guys, you must have MP3s in the ext drive's "MUSIC" directory, or Solar will seem to hang when you press down..."it will read hot-plugged drives."

Status Update on PS3 4.0 Homebrew Enabler (HEN) by KaKaRoTo

2012-01-29T18:42:00.000-08:00

Today PlayStation 3 hacker KaKaRoToKS has posted a status update on the PS3 4.0 Homebrew Enabler (HEN), which comes just six weeks since the previous confirmation that it indeed works on Sony's latest Firmware version.

To quote: 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 bullsht. 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: 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 self 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!

So anyways, we had all accepted that Mathieulh was full of sht (we knew before, but we gave him the benefit of the doubt) and decided to continue working without considering any of his useless riddles. So we then tried to exploit/decrypt the 3.60+ firmware in order to get the algorithm from there.

Now, a few more weeks later, we finally have succeeded in fully understanding that missing piece from the “NPDRM hash algorithm”, and here it is for everyone’s pleasure with some prerequisite explanation:

A game on the PS3 is an executable file in a format called a “SELF“file (kind of like .exe on windows), those “self” files are cryptographically signed and encrypted.. For PSN games (games that do not run from a Blu-ray disc), they need to have an additional security layer called “NPDRM”. So a “NPDRM self” is basically an executable that is encrypted and signed, then re-encrypted again with some additional information. On 3.55 and lower, we were able to encrypt and sign our own self files so they would look like original (made by sony) “NPDRM self” files, and the PS3 would run them without problem.

However, it wasn’t really like an original file.. a real NPDRM self file had some additional information that the PS3 simply ignored, it did not check for that information, so we could put anything in it, and it worked. Since the 3.60 version, the PS3 now also validates this additional information, so it can now differentiate between NPDRM self files created by Sony and the ones that we create ourselves for homebrew. That’s the “NPDRM hash algorithm” that we have been trying to figure out, because once we can duplicate that information in the proper manner, then the PS3 will again think that those files are authentic and will let us play them.

Another important point to explain, I said a few times that the files are “signed”.. this means that there is an “ECDSA signature” in the file which the PS3 can verify. The ECDSA signature is something that allows the PS3 to verify if the file has been modified or not.. it is easy to validate the signature, but impossible to create one without having access to the “private keys” (think of it like a real signature, you can see your dad’s signature and recognize it, but you can’t sign it exactly like him, and you can recognize if your brother tried to forge his signature). So how were we able to sign the self files that were properly authenticated on 3.55?

That’s because this “ECDSA signature” is just a very complicated mathematical equation (my head still hurts trying to fully understand it, but I might blog about it in the future and try to explain it in simple terms if people are interested), and one very important part of this mathematical equation is that you need to use a random number to generate the signature, but Sony had failed and used the same number every time.. by doing that, it was easy to just find the private key (which allows us to forge perfectly the signature) by doing some mathematical equation on it. So to summarize, a “signed file” is a file which is digitally signed with an “ECDSA signature” that cannot be forged, unless you have the “private key” for it, which is impossible to obtain usually, but we were able to obtain it because Sony failed in implementing it properly.

Now, back on topic.. so what is this missing “NPDRM hash algorithm” that we need? well it turns out that the “NPDRM self” has a second signature, so it’s a “encrypted and signed self file” with an additional layer of security (the NPDRM layer) which re-encrypts it and re-signs it again. That second signature was not verified in 3.55 and is now verified since the 3.60 version of the PS3 firmware.

One important thing to note is that Sony did NOT make the same mistake with this signature, they always used a random number, so it it technically impossible to figure out the private key for it. To be more exact, this is the exact same case as the .pkg packages you install on the PS3, you need to patch the firmware (making it CFW) so that those .pkg files can be installed, and that’s because the .pkg files are signed with an ECDSA signature for which no one was able to get the private key. That’s why we call them “pseudo-retail packages” or “unsigned packages”.

The signature on the NPDRM self file uses the exact same ECDSA curve and the same key as the one used in PS3 .pkg files, so no one has (or could have) the private key for it. What this means is that, even though we finally figured out the missing piece and we now know how the NPDRM self is built, we simply cannot duplicate it.

The reason we wasted 2 months on this is because Mathieulh lied by saying that he can do it.. remember when the 4.0 was out and I said “I can confirm that my method still works” then he also confirmed that his “NPDRM hash algorithm” still works too? well he didn’t do anything to confirm, he just lied about it because there is no way that he could have verified it because he doesn’t have the private key.

I said I will provide proof of the lies that Mathieulh gave us, so here they are: he said it’s in 3.56, that was a lie, he said it’s an AES OMAC, that was a lie, he said it’s an HMAC, that was a lie, he said it’s in appldr, that was a lie, he said it’s in lv1, that was a lie, he said that he can do it, that was a lie, he said that “it takes one hour to figure it out if you have a brain”, that was a lie, he said that he verified it to work on 4.0, that was a lie, he said that he had the algorithm/keys, that was a lie, he said that once we know the algorithm used, we can reproduce it, that was a lie, he kept referring to it as “the hash”, that was wrong.

The proof ? It’s an ECDSA signature, it’s not a hash (two very different terms for different things), it was verified by vsh.self, it was not in lv2, or lv1, or appldr, and the private key is unaccessible, so there is no way he could build his own NPDRM self files. Now you know the real reason why he refused to “share” what he had.. it’s because he didn’t have it...

So why do all this? was it because his arrogance didn’t allow him to admit not knowing something? or was it because he wanted to make us lose all this time? To me, it looks like pure sabotage, it was misleading information to steer us away from the real part of the code that holds the solution... That is of course, if we are kind enough to assume that he knew what/where it was in the first place. In the end, he wasn’t smart enough to only lie about things that we could not verify.. now we know (we always knew, but now we have proof to back it) that he’s a liar, and I do not think that anyone will believe his lies anymore.

Enough talking about liars and drama queens, back to the 4.0 HEN solution... so what next? well, we now know that we can’t sign the file, so we can’t run our apps on 3.60+ (it can work on 3.56 though). What we will do is look for a different way, a completely new exploit that would allow the files we install to actual run on the PS3. We will also be looking for possible “signature collisions” and for that we will need the help of the community, hopefully there is a collision (same random number used twice) which will allow us to calculate the private key, and if that happens, then we can move forward with a release.

When will the “jailbreak” be released? If I knew, I’d tell you, but I don’t know.. I would have said in last November, then December, then before Christmas, then before new year, etc... but as you can see, it’s impossible to predict what we will find.. we might get lucky and have it ready in a couple of days, or we may not and it will not be ready for another couple of months.. so all you need to do is : BE PATIENT (and please stop asking me about an estimated release date)!

I would like to thank the team who helped on this task for all this time and who never got discouraged, and I’d like to thank an anonymous contributor who recently joined us and who was instrumental in figuring it all out. We all believe that freedom starts with knowledge, and that knowledge should be open and available to all, that is why we are sharing this information with the world. We got the confirmation (by finding the public key used and verifying the signatures) yesterday and since sharing this information will not help Sony in any way to block our efforts in a future release, we have decided to share it with you. We believe in transparency, we believe in openness, we believe in a free world, and we want you to be part of it.

If you want to know more about this ECDSA signature algorithm, read this interesting paper (engineering.purdue.edu/kak/compsec/NewLectures/Lecture14.pdf) that explains it in detail, and you can also watch Team Fail0verflow’s CCC presentation (youtube.com/watch?v=5E0DkoQjCmI) that first explained Sony’s mistake in their implementation, which made custom firmwares possible.

Thanks for reading,

Showtime PS3 Media Player 3.4 Released, Future Plans Revealed

2012-01-29T18:37:00.000-08:00

Following up on the Showtime PS3 Media Player Version 3.4 Release Candidate, today PlayStation 3 developer Andreas Oman has officially released Showtime PS3 Media Player version 3.4.

Download: Showtime PS3 Media Player 3.4 (PKG) / Showtime PS3 Media Player 3.4 (GeoHot CFW) / Showtime PS3 Media Player 3.4 (SELF) / GIT / Showtime.SELF Version 3.4.000.dirty for multiMAN (January 25th, 2012)

To quote: Today marks the release of Showtime 3.4. For a list of most of the important bug fixes and features added, see the 3.4 page. Download the release from github.

Note: It seems Showtime still suffers from out of memory conditions now and then but I've not been able to pinpoint the exact cause of those issues. A few things were implemented just prior to the 3.4 release in order to mitigate the low memory problems.

With that said I though I could write something about what's been done this year and where Showtime is going.

The History

About a year ago Showtime had approximately 5 users. When the PS3 jailbreak was announced I quickly bought a PS3 myself and started to port Showtime to it. I had previously ported Showtime to the Wii homebrew SDK so a lot of code was already quite platform independent already.

In fact I had something running already a few weeks after I acquired the console. So far I've not used my console for anything else. I've never played a game on it, nor do I own a game. After Showtime was released for the PS3 sometime during March 2011 it gained a userbase of a few thousand users instead. Very encouraging!

During the last year Showtime has received ~1400 commits. Some are just a small typo, some are huge changes.

The major features added are:

Downloadable Plugins

While Showtime used to support Javscript plugins even before 2011 this was the year when I added support for a central repository. For a full list of available apps, see the official repo. Big thank you to all the plugin developers that are making the Showtime experience a lot more interesting.

Translations

Thanks to the community Showtime is now translated to 21 different languages.

Sqlite

Currently used to drive the metadata cache and video resume support. In the future I hope to use this for a lot of spiffy features such as possibility to search all your indexed media store detailed information about movies.

The Future

User interface redesign

Personally I think Showtime's weakest point is its User Interface. I hope to be able to present something new in this area during the spring. Some people ask for theme/skin support in Showtime. Thing is, Showtime already have that but it's not exposed to the average user in a good way. Nor is it very appealing to skin/theme developers either.

Adding a new theme requires that all of the UI is redesigned in one go. I don't think that's very productive or creative. Rather I would like plugins to the UI itself so it's possible to create a plugin that alters the home page. Or the settings view. Or the play control. Or perhaps everything.

Grabbing metadata from external locations

For files stored on users hard drives, or NAS, etc Showtime can only show the metadata contained in the file itself.

My plan is to add support for plugins that based on filenames (or file hashes, etc) downloads metadata, artwork, ratings, etc from various online sources such as http://themoviedb.org, etc

Auto updates

I've almost finished my own autobuild system. This will make sure all commits are built for a all supported target platforms and also auto published on the Showtime download page. On this page three different versions will be available.

Stable - A known good version
Testing - Should be OK to use for the average user
Unstable - Latest checking. Can be broken.

Not only will the build be available on the site itself but it will also be possible to upgrade Showtime from within the application.

And the rest...

And of course there are countless bugs to fix, and important features that should be added as well. In particular an on-screen keyboard would be a welcome addition. UPnP/DLNA renderer support so Showtime can be remote controlled from a UPnP control point.

Tomorrow I will be leaving on a six week vacation and during that period I won't do any PS3 related development (as I don't have the console with me). I might do some general Showtime stuff though. I've no idea what that will be though... I guess I'll find out.

So with no further ado, Thank you for the past year. Talk to you all soon again.

Showtime PS3 Media Player 3.4 Changelog:

Bug #216: Image navigator - missing rotation of previews
        Bug #448: Photo - Doesn't display .jpg over 900ko
        Bug #478: new version can't play 1080p movies
        Bug #628: Clock is 1 hour off.
        Bug #716: Video list disappears permanently
        Bug #717: The clock displaying is not right
        Bug #718: italic subtitles display
        Bug #719: Subtitles in mkv file are still on even though in settings they are off
        Bug #720: Rar Split files is broken
        Bug #721: L5.0/5.1 MKV no video playback
        Bug #724: 3 Video Files splitted but Showtime Shows 1 Video in the Directory
        Bug #726: Subtitle BUG (Overlapping)
        Bug #729: .MP4 Container problem (and possible .MKV improvement suggestion)
        Bug #731: Subtitles in rar split files
        Bug #732: Subtitle position.
        Bug #739: SMB (Samba) Network Issue
        Bug #740: Bookmarks: Selecting photo image and appera fodler image?
        Bug #746: SMB (Samaba) Video Playback Issues
        Bug #748: MKV 5.1 igh level ( Debug Option to write a txt when it says CPU to slow )
        Bug #750: high quality mkv (+20gb)
        Bug #757: Samba Playback Video Speed-Ups Slow-Downs
        Bug #760: Memory leak when playing large/long movies
        Bug #771: No video shown when playing this movie sample
        Bug #773: Idee to eliminate the Memory Problem on MKV!!!
        Bug #776: Http Client Hangs
        Bug #779: Plugins: Message with a lot of charaters block
        Bug #781: Plugins: Read local xml files
        Bug #782: Plugins: Read files from SMB path
        Bug #790: Plugins: showtime freeze when reading rtmp
        Bug #794: .OGM Container playback issues [PS3]
        Bug #796: Audio track bug
        Bug #806: Video titles do not flow under cover art image?
        Bug #810: AC3 mono track does not work.
        Bug #834: FLV PLAYBACK BUG
        Bug #836: More than 1 Subtitle per movie.
        Bug #842: Possible bug with AVC codec Baseline@L1.3. (on PS3).
        Feature #348: please add support for EGL / OpenGL|ES
        Feature #417: Mark files that has been played
        Feature #518: Samba streaming
        Feature #640: MP4 codec support
        Feature #690: resuming playback from where left off
        Feature #707: Detect track flags in .MKV container
        Feature #710: Subtitle adjustment.
        Feature #775: mkv track names display
        Feature #784: Plugins: Cache remote (HTTP) image files
        Feature #802: Plugins: settings.createComboBox like in showtime settings

Showtime.SELF Version 3.4.000.dirty for multiMAN (January 25th, 2012) Changelog:

Added: XMB videos and last folder visible in Showtime
Added: Return to multiMAN when using the EXIT icon in to top right corner of main Showtime Interfac

Save the downloaded file as: /dev_hdd0/game/BLES80608/USRDIR/SHOWTIME.SELF

Image navigator - missing rotation of previews
Photo - Doesn't display .jpg over 900ko
New version can't play 1080p movies
Clock is 1 hour off.
Video list disappears permanently
The clock displaying is not right
Italic subtitles display
Subtitles in mkv file are still on even though in settings they are off
Rar Split files is broken
L5.0/5.1 MKV no video playback
3 Video Files splitted but Showtime Shows 1 Video in the Directory
Subtitle BUG (Overlapping)
.MP4 Container problem (and possible .MKV improvement suggestion)
Subtitles in rar split files
Subtitle position.
SMB (Samba) Network Issue
Bookmarks - Selecting photo image and appera fodler image?
SMB (Samaba) Video Playback Issues
MKV 5.1 igh level ( Debug Option to write a txt when it says CPU to slow )
High quality mkv (+20gb)
Samba Playback Video Speed-Ups Slow-Downs
Memory leak when playing large/long movies
No video shown when playing this movie sample
Idee to eliminate the Memory Problem on MKV!!!
Http Client Hangs
Plugins - Message with a lot of charaters block
Plugins - Read local xml files
Plugins - Read files from SMB path
Plugins - showtime freeze when reading rtmp
.OGM Container playback issues [PS3]
Audio track bug
Video titles do not flow under cover art image?
AC3 mono track does not work.
FLV PLAYBACK BUG
More than 1 Subtitle per movie.
Possible bug with AVC codec Baseline@L1.3. (on PS3).
Please add support for EGL / OpenGL|ES
Mark files that has been played
Samba streaming
MP4 codec support
Resuming playback from where left off
Detect track flags in .MKV container
Subtitle adjustment.
MKV track names display
Plugins - Cache remote (HTTP) image files
Plugins - settings.createComboBox like in showtime settings

PS3 4.00 HFW (Hybrid Firmware) v2 Arrives, Adds Debug XMB Items

2012-01-29T18:28:00.000-08:00

Following up on the previous update of my PS3 4.00 Dev_Flash mod, today I've released version 2 of my PS3 4.00 HFW (Hybrid Firmware).

Download: PS3 4.00 HFW (Hybrid Firmware) v2

Change Log:

Version 2:

Adds "Debug XMB Items" to the XMB Column "PlayStation Network" (contains the Debug items found in this column, originally for DEX)
Removes the useless "PlayStation Plus" XMB item from the XMB Column "PlayStation Network"
Disables Cinavia DRM on all media except Blue-ray.

Version 1:

Adds DeViL303's "XMB File Manager" to the XMB Column "Game"
Adds "/app_home/PS3GAME/" to the XMB Column "Game" (has no function at the moment, but is here for completeness)

Installation Instructions are the same as before:

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. THIS HFW WILL NOT ALLOW HOMEBREW!

An important message for users upgrading from a QA Flagged console: If this console is updated to my 4.00HFW from a QA Flagged console, it will not be able to access the extra System Settings provided by QA Flagging. However all settings made with the QA Debug Settings will remain, EXCEPT "System Debug Update".

Extra Credits: This HFW uses the "XMB File Manager" by DeViL303 which is a modification of Team Rebug's "Packages Manager".

PS3 Debug / Test Firmware 3.74 and 4.00 Updates Surface

2012-01-15T17:28:00.000-08:00

For those who own PS3 Debug / Test consoles or are simply into collecting PlayStation 3 file leaks, recently PS3 Debug / Test Firmware 3.74 surfaced alongside version 4.00 from Sony's North American Press Web site.

Download: PS3 Debug / Test Firmware 3.74 / PS3 Debug / Test Firmware 4.00

If you didn't know, the address to their Press site is http://PressCenter.PlayStation.com/ and Sony offers free access to all members of the press there using SCEA / SC3APR to login and obtain the latest press releases and related files.

Finally, keep in mind these PUP updates will currently NOT install on a retail PS3, and so they are intended for examination and comparison purposes only.

We have 100% confirmed that running this updater on a retail PS3 will not damage it, however, it will give the following error before the installation completes: The data type is not supported. (8002F029)

Special Thanks to ConsoleDev for the heads-up on the news tip!

Half byte loader for EU / US models Vita completed

2012-01-12T17:38:00.000-08:00

The known PSP developer "Wololo", which among other things Half of its byte loader is known on the PSP, it has been possible by the "teck4" PSVita exploit found on US / EU to port models and thus make the HBL is functional on this.

Using an exploit in a not-called PSP game, the developers have succeeded, the PSP emulator in the PSVita, to execute unsigned code. The bottom line is, so that you can most of your PSP homebrew running on your PSVita, such as Various emulators or homebrew games.

Release of the whole should take place sometime after the EU / US launch to provide the most PSVitas with the HBL may be because Sony can close the gap with a simple security update without any problems.

I managed to port HBL to the US version of Teck4′s exploit in exactly 45 minutes (including writing the savedata exploit and the binary loader), which is a new personal record, thanks to the scripts included in HBL’s repository...

I also updated the EU/US versions of this HBL port to get the tweaks I worked on for the past weeks in order to get a fair amount of homebrews to work.

Reports have come in that Wololo has managed to port the HBL exploit to the US and EU PS Vita. Also added are some tweaks needed to get the various homebrew applications and emulators running within half-byte loader. This is great news for all who expect to run the above on their PS Vita when launched worldwide.

PS Vita’s Augmented Reality Transforms Your Table Into an Arena in CES 2012

2012-01-11T23:16:00.000-08:00

A couple of months ago, a video surfaced that showed off some cool-looking augmented reality apps running on PS Vita. Since then, it’s been confirmed that Vita will come with six AR Play Cards and a voucher to download a handful of free augmented reality mini games via the PSN. Today at CES, we were able to see one of these games in action: Table Football (it will be called Table Soccer in the US, because we already have football).

Backstage, Sony Santa Monica Sr. Manager Dave Thach dealt the AR Play Cards on a table, and a soccer pitch sprung to life through the window of the PS Vita’s luscious OLED display. The actual game is kind of like a turn-based soccer match – it reminded me of a 2012 version of paper football. But enough talk, let’s see it in action:

Bonus points if you spotted the Men in Black 3 alien who walked through the frame. Vegas is weird.

Table Soccer is just one of the augmented-reality games you’ll be able to play for free if you pick up a new PS Vita on February 22nd. We’ll highlight more closer to launch right here on the PlayStation.Blog.

FIFA 12 for PS3 Custom Firmware 3.55 / 3.41 By EXEtrimALL Out!

2012-01-10T23:37:00.000-08:00

Following last weeks article on FIFA 12 for JFW DH 3.56 MA users, today the legendary EXEtrimALL has released FIFA 12 (NPEB00688) via pr0p0sitionJOE for PS3 Custom Firmware 3.55 and 3.41 fans for free with no DRM-infected dongles required!

Those interested can check out the ongoing thread for all of the related links, and below are some notes from pr0p0sitionJOE as follows:

Download ALL THREE PARTS (PKG) and install in order. People, game is almost 7 GB. Multiple languages inside. This is Full PSN version in one pack... not a fix.

For PS3 3.41 CFW users from Hissatsu:

FIFA Soccer 12 works on FW 3.41 without any special/extra FIXes. Tested myself its set to FW 3.40.

EXEtrimALL was kind enough to set the game to FW 3.40. So get your Soccer on!

Finally, in case you missed it also be sure to bookmark / check out the Duplex PSN Releases for PS3 CFW All in One Place and ReActPSN Game Releases for PS3 CFW All in One Place PSN repositories that are updated daily courtesy of atko. Enjoy everyone!

Sony PS3 Generator Tools Version 3.12 and PDF Guide Leaked

2012-01-10T23:34:00.000-08:00

After the PS3 3.40 SDK and PS3 3.60 SDK leaks from last year, today some more Sony PlayStation 3 tools have surfaced including PS3 Generator Tools Version 3.12 and the related PDF guides.

Download: PS3 Generator Tools Version 3.12 with PDF Guides / PS3 Generator Tools Version 3.12 with PDF Guides (Mirror)

Also included are ps3trp.exe, ps3sys.exe, ps3gen.exe, ps3cmd.exe, and ps3chk.exe in the archive above.

To quote, roughly translated: Leak from Generator Tools v3.12, an official package of tools by Sony.

Sony is unlikely to appreciate that! Indeed, a package of tools of his own design has been leaked on the Web, and while this set of software is not of paramount importance, it still proves that no one is to shelter of a leak, not even the multinational influence.

But back on topic, and now let's look at this "kit" of programs, called Generator Tools v3.12 and used to offer PS3 titles to the public. It is intended for the creation and verification of records and masters Masters packages.

In other words, developers of video game studios use it to edit projects, burn an ISO image on a Blu-Ray, extract and decrypt the same time the content of a Blu-ray or an ISO image, create a file system (SFO), etc.. You can find all these features and further explanation concerning the PDF from the archive.

FAQ of PS Vita Half Byte Loader (HBL) Development

2012-01-10T23:32:00.000-08:00

Today PS Vita hacker wololo has made available a Half Byte Loader (HBL) development FAQ for those interested in progress thus far on Sony's PlayStation Vita handheld console.

To quote: A FAQ for HBL on the Vita

We've seen through Teck4′s exploit that PSP exploits run flawlessly on the PSP emulator of the Vita. I've spent the past 3 weeks working on leveraging Teck4′s exploit and port HBL to it. I've been receiving lots of questions (probably from people who haven't used HBL back when it was the only possible way to play homebrews on the PSP Go) and will try to answer them here.

What is HBL?

HBL stands for "Half Byte Loader". This is a homebrew loader for the PSP, which was written initially by m0skit0, then improved and maintained by a bunch of devs including myself (those two links are good old memories, when HBL wasn't loading a single homebrew properly). It basically allows to run fanmade games, emulators, etc on the PSP. We've found that it can run on the PS Vita through the PSP emulator.

Will this allow to run PSP backups (isos)?

Although in theory that would be possible, HBL only has access to the PSP "user mode" which is fairly limited. Practically, all teams who have tried to create an iso loader in user mode on the PSP have failed so far.

Will this allow to run PS Vita game backups?

No

Does this give us access to the Vita hardware (touch screen, etc)?

No. HBL accesses the hardware through the PSP emulator, and therefore only has access to what is mapped to the PSP controls. It also only has access to 32MB of ram, etc

Does this give us possibilities to hack the vita further?

Most likely, not. HBL is stuck in user mode, in a sandboxed emulator. To get access to Vita information, we would need first to get kernel access in the emulator (through a psp kernel exploit), and then find other exploits in the emulator/OS itself to break away from the sandbox (which, if the Vita OS is as secure as I think it is, is close to impossible)

But will it give us more horsepower than the psp? Can we expect emulators to run faster, etc?

This still needs to be investigated deeper, but from what I've seen, not really. Memory stick access is definitely faster on the vita (Wagic loads between 5 and 10 times faster on the vita than on a psp go), but the rest seems to follow the psp limitations (as one would expect from an emulator)

Will this be made public?

Yes. Teck4 (who found the exploit) and I agreed to making this public at some point.

When will this be made public?

Some time after the Vita is released worldwide.

I heard Sony can patch this very easily as soon as it's made public?

Yes. Since this uses a vulnerability in a PSP game, as soon as they know which game it is, Sony can remove the game from the PS Store. Once they do that, they can patch the Vita firmware to reject the "malicious" files (either by preventing them from being copied through the content manager assistant, or by patching the PSP emulator, or by patching the PSP game, etc). At that point, people who don't already have the game on their console won't be able to use HBL. Also, people who do have HBL will need to never upgrade their firmware, will have to use some tools such as OpenCMA in order to copy files to the vita, and will be locked out of the PS Store as long as they want to use homebrews.

So shouldn't you keep this under wraps instead?

Meh, it's not like anything is really secret here besides the name of the game. It's already pretty sure this is not useful for hacking the vita further, so even if it gets patched I don't think we will lose "too much".

No iso, no access to the vita internals, and Sony will patch it as soon as it's out, so basically it's useless?

Yes and No. Technically, a hacked PSP is way cheaper and will allow you to do more than that. But this is, as I write these lines, the only way to run unsigned code on the Vita, which in itself makes it a great achievement (and it's always cool to show your friends that your Vita can run Mario, and theirs can't). Also, it didn't take too much time to adapt since most of the code was already available from our past work in the psp scene. It would have been even more useless to say "oh yeah, interesting, we can run psp exploits on the vita" and not do anything with it.

How do you copy/install homebrews to the ps vita, since it cannot be mounted as a regular usb drive?

This will be explained when HBL is released.

PS3 PKGView v1.2 Extractor Homebrew Application Update Arrives

2012-01-10T23:30:00.000-08:00

Following up on my previous releases, today a new PS3 PKGView Extractor homebrew application version 1.2 update is available and has been fully tested by catalinnc.

Download: PS3 PKGView v1.2 Extractor

PKGView is a tool for extracting files from PS3 PKG. Tool is 100% legal it contains no code Sony. PKGView also has a graphical interface that simplifies the extraction of both individual files and the complete package.

PS3 PKGView v1.2 Extractor Homebrew Application Version 1.2 Changelog:

FIX: Still failing to extract large files.
FIX: Structure parsing issues.
FIX: Other extraction issues.
More descriptive extraction window.
Optimized extraction of retail pkg.
Now creates an extraction log.

Top 10 best seller Montblanc Watches Set to Outsell Pens in 2011

2012-01-10T20:05:00.000-08:00

Montblanc Pens' Familiar White Star Was Designed By a Jew for Hitler-Fiction! bullet, Summary of eRumor: Montblanc pens have a trademark on their caps of a finely-crafted white star. Financiere Richemont SA unit is tapping a surge in demand for high-end watches to offset slower growth in the brand’s traditional writing-instrument business. The shift reflects Montblanc’s broader transformation over the past decade into a luxury-goods company.

Mont Blanc Pens tend to be preferred worldwide to be probably the most easy to use as well as attainable types. The actual Mont Blanc offers indisputably created a remarkable tag within the instruments for writing business. These types of writing instruments will also be considered to be selected within marketing reasons sideways using their regular perform.

Mont Blanc Pen, Show Your Unique Charm and Fashionable Writing Tool! ... Wonderful Online Shopping Site of Discounted Montblanc Pen!Montblanc convey love among families and friends as gift. When you need a unique present for someone who you love, it may be challenging to find some thing which they are able to in reality use. Numerous individuals are on diets, forgoing the conventional box of chocolates. Numerous might have allergies, developing flowers not probably the most advantageous choice. Just one present option that will regularly be appreciated is genuinely a fountain pen. The Mont Blanc pen is genuinely a high quality crafted fountain pen that will last a lifetime. Having a high quality Mont Blanc pen helps make producing a satisfaction after again. After you utilize much less pricey reduced price store pens, they drag near to the cardstock and make your producing hand much more tired. It is no wonder that people have switched over to using computer once they should write. But what a variance a high quality Montblanc pen could make for the handwriting.

Review of the Montblanc Meisterstuck Ballpoint Pen

Montblanc International is now the company behind the infamous Mont Blanc Pens, but in the beginning the name was Simplo Filler Pen company. This company was first begun in 1906 with a partnership of three men: Claus-Johannes Voss, August Eberstein, and Alfred Nehemias.It is normally a exceptional time for earning goodwill, and what could possibly be much better than a current to serve getting a token of appreciation for each of the hard purpose your workforce positioned within yr round. A xmas current will make an staff members really feel like a element of the institution family, as well as like a reward for just about any purpose properly done. The option of product as your token of appreciation for the clientele and purpose force should reflect precisely the same exact feeling. A staff member who has worked hard to the accelerated growth from the business should be rewarded within most appropriate way.