175w ago - Following up on the initial PS3 JailBreak 2 news comes various PS3 CFW JailBreak 2 and JB2 Updater details today including the examination of an EBOOT.BIN from the Driver: San Francisco Blu-ray Disc in comparison to one from an official PS3 Game (BLES00891) Disc with developments on reverse-engineering the PS3 JB2 file dumps and more below.

To begin, whyudie states the following on the PS3 CFW JailBreak 2 and JB2 Updater for PlayStation 3: I just wanted to share this CFW. This CFW is intended more specifically for Jailbreak 2 dongle only. Most likely will not run well without that dongle. Perhaps some developers out there could investigate this CFW, and develop it even better.

If anyone out there want to install this CFW on your PS3. Do it at your own risk!!

JailBreak 2 Dongle Features

Can play backup games that require firmware 3.60 + (Direct boot just like the original games)

Only burned BD Disc format with some patches will work. For now, there's no info how to make a backup iso to work with this CFW.

Can play backup games from the HDD. PS3 games with FW 3.55 or lower (via internal or external hdd)

Only works on the PS3 with official/custom firmware 3.55, not the downgrade PS3.

From my local game store. I live in Indonesia. And I bought the dongle. And get the bonus cd and the CFW files is from that cd. And that CFW must be installed first on PS3, and upgrade the dongle with that pkg files.

Below is a preliminary synopsis from moogie via Twitter and ps3devwiki.com/index.php?title=PS3JB2_Reverse_Engineering and ps3devwiki.com/index.php?title=Talk:Keys#sv_iso_spu_module_1.02-3.55:

JB2's dongle updater pkg, its EBOOT.BIN is just an FSELF (fake signed), the Driver: SF eboot fix is also an FSELF, FSELF's are mean't for debug consoles, easier to fself your game, then to actually sign it, you can patch retail FW to run FSELF's, either through the fw, or you can modify PL3, or even, resign the EBOOT.BIN, its nothing special, from the looks of it, they don't have any keys, just debug EBOOT.BIN's.

You don't need that dongle either, just resign the EBOOT.BIN or patch the FW to run FSELF's, their MFW could have these patches, or maybe, their dongle deliver's the patches. I do not know for sure, maybe their dongle does something else entirely, but I know its an FSELF, and you can make that run, without their dongle.

Dongle is DRM to make sure you have the dongle, the firmware 'special' functionality will not work without it. Contentdisc's contain fself'ed eboot.bin's.

Those JB2 eboot.bin stuff, actually isn't debug fself's, but readself says it is its their DRM. Can't be decrypted without their stuff. They have their own keys, which they are signing the EBOOT.BIN's with, I think they are debug eboot's resigned with their stuff.

That's the algo for masterdiscs, ps3gen.dll has the static keys for masterdiscs. You can also get it from sv_iso the sdk tool that generates masterdisc images.

Then you take the decrypted fself and resign it for 3.55 with makeself then swap eboot. I think it should be somewhere in the PS3_Generator_Tools-312.zip in the 3.60 SDK but I'm not finding it, but that's where the master disc stuff is.

Finally, upon examination several users including DanyL, TheLostDeathKnight and bubbleboy have stated that the JB2 doesn't use a new PlayStation 3 exploit nor contain PS3 3.6+ keys, and that the dongle is only used as identification for activating the patch.

For those curious, patching the appldr keys has been done but not made public back with the PS3 3.56 keys so it isn't unfamiliar to most PlayStation 3 developers but unfortunately it is patchable by Sony. A brief outline of the process involved is below, as follows:

Obtain PS3 Debug EBOOT file from Sony's Developer Network via Debug console by one of the following methods:

Boot up your PS3 to the XMB, make sure in debug settings that NP environment is set to “sp-int” or “prod-qa”, sign into PSN (with sp-int or prod-qa credentials, you can use the quick sign-up), and launch the game. If your in luck, it will say an update is available – download it!

To get the URL you have a few options. You could either sniff out the connection with something like Wireshark - that takes a bit more setup. Other times the URL is actually passed right to dtccons - so make sure you have the debugging windows open. Or, you could use any number of the PS3 Proxy applications to grab the link.

Those who know their PS3 Game's Title ID and are seeking PS3 Game Update Packages can now use this simple guide to grab them while they last.

Patch Retail PS3 Firmware to run a Debug EBOOT file

Dump and burn the PS3 3.60+ games to BD-DVD with the included Debug EBOOT file

Add the DRM to the PS3 MFW / CFW that JB2 uses and validate it via the dongle

The above process will likely continue to work until Sony locks down the PS3 Debug EBOOT files.

PS3 JB2 Keys

The encryption keys for PS3 Debug Discs utilized by the PS3 JB2 method can be found below.

Fixed yet another important game compatibility issue affecting recent 4.xx games

The authenticity status display can be used to determine if your True Blue dongle is either authentic or a clone.

For further details, see the information page. How do I know if I have a TB clone?

Q: How can I verify that my True Blue is authentic and not a clone?

A: Install True Blue dongle firmware v2.7 or later.

Then in the PS3 XMB, navigate to Settings -> System Settings -> System Information. Next to the "System Software" version will be information relating to your True Blue dongle. If your dongle is authentic then it will display something like "True Blue v2.7" (this will vary depending on the version of the dongle firmware you have installed).

If your dongle is a clone then it will display "True Blue CLONE" as shown in the following image:

Today True Blue has issued another warning about a TB PS3 dongle clone, as follows:

21 - 5 - 2012

A new clone has appeared (item.taobao.com/item.htm?id=13491601183) using a very similar external housing to that of True Blue. However, after removing the clone PCB from its exterior casing it becomes evident that there are a number of major differences:

Actel used is A3P125 instead of larger A3P250 used on True Blue.

Clone uses a cheap MCU and cheap dip type crystal in addition to cheaper Actel instead of full Actel integration in the original True Blue design

Clone has a tact switch which the original does not require, and switch can only be accessed by pulling PCB out of the case

Actel logic on clone is based on partial guess work of the original and will not function correctly in future updates

PCB circuit design is highly congested, with numerous visual differences evident, such as programming pads for the MCU and addiional resistors/caps

Please refer to the pictures shown below, to compare the original and clone.

A new software update will be made publicly available in the next few days which will allow users to differentiate original from clone by performing a firmware update.

Fixed a major game compatibility issue which will allow the release of several popular, previously incompatible titles

Improved system stability

Recently, EBOOT patches have slowed due to a compatibility issue which prevented recent games from running on 3.55 CFW. This issue has been resolved as of this firmware release, thus we strongly recommend that everyone update their True Blue dongles as soon as possible in anticipation of the upcoming batch of releases.

In related news, Corwin75 has updated True Blue Patch Viewer to V2.0.3 followed by V2.0.5 with the changes outlined below.

Below is a True Blue Patch Viewer from Corwin75 via French site (games-hack.fr/index.php?threads/release-true-blue-patch-viewer.6580/) for those interested. Rough translation (from ps-addict.fr/forum/True-Blue-Patch-Viewer-File-Downloader-t6296.html):

It aims to list all Eboot.bin compatible with the True Blue Dongle and to make available patches created by the various Team direct download. It also incorporates the latest update of True Blue Dongle.

Our goal is to keep it updated constantly so that each new release of patch is integrated into the app. Here are the features:

This is where we need some kind of co-op with TB team and hotz. If reactpsn compatibility would be implemented in new TBCFW or dongle update, this would give us much more working space for fixing additional content.

My team sucessfully fixed several TB games DLCs with use of reactpsn. I hate use of reactpsn to play games. Fully fixed games are the way it should be. Some users don't have act.dat file for never loggin onto PSN and they are forced to use rebug. Rebug is not possible anymore with TB 2.5.

Even better option for us would be if TB team implements "peek and poke" in their CFW so we can fully fix games with help of reactpsn or ps3tools. Then the need for edited VSH.self for TB CFWv2 becomes unnecessary. If this is problematic for TB CFW stability or whatever, then some kind of "switch mode" should be available to enter "peek and poke mode" so we can do our thing and return to "normal payload mode" with DLC content fully fixed. Time to expand views.

Further more, releasing fixed update patches for TB games is necessary for all DLC content to work properly or to work at all. Releasing games with base content only if not enough anymore. Some games expand or get upgraded with DLC content. That's it from me.

I am pleased to issue you the payload of true blue (the last version 2.61). I do not know if it was already 'been discovered by someone, but from what I've seen no one has posted something genere. To whom is developer release download of my discovery I'm a programmer (no faker). I want to help the scene ps3. This file is the result of my study. The software used is IDA PRO.

It has come to our attention that a small number of users may be affected by freezing at boot if using 2.6 dongle fw where they have modified their console cfw's files by installing programs such as ReactPSN, Cineavi protection remover or other such programs. The 2.6 dongle fw functions perfectly where the user has NOT carried out modifications to the console cfw. The console cfw should not be modified when running TB 2.51 cfw or 2.6 cfw, as this will cause incompatibilities which can lead to freezing at boot reported by a few users this evening on the forums.

In order to provide a feature rich experience for users we will add support for some popular programs/applications in TB CFW 2.61 which will be released within the coming days. We thank all TB users for their continued support and patience whilst we develop feature updates and firmwares.

Anyone who has modified their TB CFW and is experiencing freezing, may simply revert to 2.51 TB FW using the special fw file attached here and reinstall the 3.55 CFW DG on their console. This will compeletly fix any freezing issues. We kindly remind TB users not to modify the TB console CFW 3.55 unless we explicitly state in the accompanying notes included with upcoming TB 2.61 fw that the program/application is supported.

How to update:

1. Make sure your PS3 is running the True Blue "3.55-Dongle-DG" CFW (custom firmware)
2. Copy TrueBlueUpdate-2.51.pkg from this archive to a USB flash drive
3. Boot your PS3 _WITHOUT_ True Blue inserted, and then insert the USB flash drive
4. Navigate to (Game) -> (Install Package Files), and then select TrueBlueUpdate-2.51.pkg
5. The True Blue updater will be installed onto your PS3 HDD
6. Navigate to (Game) and load "True Blue Update v2.51"
7. The updater will start, and will then prompt you to insert the True Blue dongle. Insert it only at this point, and continue. Your dongle will then be updated
8. After the update procedure has completed your PS3 will reset, and you will then be able to enjoy your updated dongle
9. You may delete the True Blue Updater from your HDD after the update is complete

I havent tried to install reactPSN straight from 2.61 (you may need the VSH file route which is hazardous as you have to modify dev_blind)

1. Install TB CFW v2 and 2.51 or lower update if havent already.

2. Put your USB Thumb or USB HDD back into your PC or MAC.

3. Download both reActPSN v2.0 or 2.20 and Rebug Spoofer 4.00

4. Now extract reactPSN v2.0.rar (or 2.20) and drag reactPSN v2.0 pkg to the root of your USB Thumb stick or USB HDD, do the same for REbug Spoofer.pkg

5. On the root of your USB Thumb Stick create a folder called exdata. Whenever you get new rap and edat files drag them into this very folder (Every Time) usb:exdata/rap files. Always leave previous rap and edat files in exdata for when you reuse reActPSN v2.0 for newer games downloaded.

6. Now install the reActPSN v2.0 pkg and Rebug Spoofer like any other pkg from usb in furthest PS3 right USB port (but dont run the programs created yet)

7. Turn off PS3 and make sure that the True Blue Dongle is removed, Turn on PS3.

8. Run rebug Spoofer and spoof your ps3 (install files and activate spoofer, will reboot each time) check system info in XMB to make sure version is 4.00

9. Run ReActPSN and hold R1 (Some people say Hold Circle instead) during the restart process should only take about 20 seconds. (Holding R1 will make a ReActPSN folder on the base of your usb drive with 2 folders in it "BK0001" and "pubPSN"). Any content you purchased prior to this hack will be backed up in pubPSN folder in the form of rap and edat files (These are the very files needed for us all to activate any shared psn, dlc or psone classic games, THAT YOU OWN. If you had no previous content BK0001 wont be created).

10. Check to see if reactPSN folder was created on USB HD/STICK if not you didnt hold down R1 or USB HD is not in PS3 right port (cant use HUB at this point)

12. Copy the exdata folder contents in pubPSN to the exdata folder you created on the root of your USB drive.

13. Create a new user account on the PS3 called aa

14. Run reActPSN again *do not push anything this time (it will rename user "aa" to reActPSN v2.0 xrif xedat).

17. Everytime you want to install new PSN , PSone games or DLC content, just go into reActPSN v2.0 ACCOUNT and rename it to aa (You can do multiple games, dlc, etc at one time, if you have rap and edat files, usb HD needs to be in PS3 right port when doing step 17, 18 & 19)

18. Download, extract rap and edat files (that came with dlc.pkg etc) to exdata folder on the root of your USB Thumb stick or USB HDD