PS4 News on Facebook! PS4 News on Twitter! PS4 News on YouTube! PS4 News RSS Feed!

Home PS4 News - Latest PlayStation 4 and PS3 News

November 25, 2011 // 4:44 pm - Following up on the version 2.2 update, today True Blue (JB2) version 2.3 has arrived alongside some reverse-engineering updates including v2.3 UnPKG'd / UnSelf'd and the Payload from the PlayStation 3 Development Wiki below.

Download: True Blue (JB2) PS3 Update v2.3 / True Blue (JB2) PS3 Update v2.3 (Mirror) / True Blue (JB2) PS3 Update v2.3 (Mirror #2) / True Blue (JB2) PS3 Update v2.3 UnPKG'd / UnSelf'd / True Blue (JB2) PS3 Update v2.3 Payload_2.3.bin

From the ReadMe File: True Blue Dongle Update v2.3

How to update:

1. Make sure your PS3 is running the True Blue "3.55-Dongle" CFW (custom firmware)
2. Copy TrueBlueUpdate-2.3.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.3.pkg
5. The True Blue updater will be installed onto your PS3 HDD
6. Navigate to (Game) and load "True Blue Update v2.3"
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

Change log:

- v2.3

  • Fixed games requiring "BD Mirror"
  • True Blue firmware version is now displayed on the XMB "System Information" screen

- v2.2

  • Initial worldwide release
  • Support for running "True Blue" titles directly from HDD via standard backup managers

From Bartholomy on the update: This is what happen with Rebug TB using BD mirror. So if this is a problem of Rebug TB i hope will be fixed. For sure i'm not moving to 3.55-dongle, all my saves are ruined with fakesaveowner.


Those interested can see THIS post for more details and updates.

From Sony PlayStation 3 hacker KaKaRoToKS on the True Blue PS3 USB dongle via Twitter:

xl14 (http://twitter.com/#!/xl14/status/140036151984652289):
KaKaRoToKS In your opinion is worth buy the true blue?

KaKaRoToKS (http://twitter.com/#!/KaKaRoToKS/status/140064074988929024):
xl14 no. Dont

KaKaRoToKS (http://twitter.com/#!/KaKaRoToKS/status/144612386341531648): http://pastie.org/2983927

As far as I understand it, the hate for TB is because what they achieved was to decrypt newer npdrm games and what they did is they patch the games to check for the TB dongle or quit. The TB dongle does *NOTHING* other than a DRM that is completely not needed.

The torrent releases that are "TB compatible" just means that they added the DRM check that prevents them from running if you didn't buy a TB dongle. That's not any kind of help to the scene and it's people getting paid by promoting piracy.

PlayStation 3 developer CrashSerious also commented on the True Blue dongle in an interview, to quote in part:

"I can say that we don't like the disease that Cobra pushes with their Cobra and Cobra True Blue DRM replacement dongles. Ironically, they replace one DRM with another- in the process, stealing from those in the scene that did the work in the first place. Cobra offered some features that were new initially, but did so on the backs of the people before them. They made money off these people, like graf and others, and maintain no known public or private link to the scene. We find it interesting that even Cobra does not come out and claim responsibility for the Cobra True Blue dongle, but simple analysis points directly to them.

The Cobra True Blue Dongle seems to only promote theft, yet could have valid uses for those who wish to buy and play newer games on their <3.56 FW Consoles. Yet they have chosen NOT to give back to the scene, by implementing their own Cobra TB Encrypted Eboots, when keys for 3.55 and below are already known and useable by all jailbroken consoles. They have therefore instead chosen to profit from a situation that we all have been placed in by Sony's initial choice to remove otherOS and prohibit true homebrew applications in the name of "preventing piracy".

Additionally, the Cobra True Blue dongle took this one step farther by selling these Cobra TB disks- a clear violation of copyright and a threat to all of us wanting homebrew on future systems."

There is also some reverse-engineering updates from eussNL today as follows via: ps3devwiki.com/index.php?title=PS3JB2_Reverse_Engineering#Content_Releases

lv2_kernel.self

http://pastie.org/private/onlbfdxjdtaddb9blu0sq

[Register or Login to view code]

Only 1 function change, and a section added sub_28fe30 is replaced 1) the new section is loaded at 0x80000000007f0000 (which is where those payloads are being loaded) lv2_kernel.bin (6.41 KB)

Note 1) : * the 28fe30 function is replaced with OFW code during exploit execution (which is why it is OFW, when there is no dongle).

That 28fe30 function mounts dev_flash, so they are in control before even dev_flash loads. When lv2 loads dev_flash, the exploit is triggered which, among the things it does, is replace the function with the proper one to mount dev_flash, then branchs to it and boot continues.

True Blue 2.3

True Blue Dongle Update v2.3 - TrueBlueUpdate-2.3.zip (546.29 KB)

  • Fixed games requiring "BD Mirror"
  • True Blue firmware version is now displayed on the XMB "System Information" screen

PKG:
SHA1: B8A48394FF09A358CAB230823C18F871256C6A34
MD5: 67185C448FAEE1FE262556302FB86240
CRC32: AFF450D2
CRC16: 21C1

Unpkg/unself'ed: TrueBlueUpdate-2.3.pkg.out.rar (1022.45 KB)

Payload (2.3)

Located in unself'ed eboot.bin @ offset:

[Register or Login to view code]

Download: Payload_2.3.bin (461.75 KB)

SHA1: DD8C3302F5F2394B2A0D907DE972AFB8E94DB0B5
MD5: 7E4C3C6D7BA24375D3BE83074D882E0A
CRC32: 7D748CE8
CRC16: 4A3B

lv2 dump (2.3)

Payload @ file offset 0x8698 - 0x736F0

descriptors (2.3)

[Register or Login to view code]

Here is a PS3 True Blue Installation Guide from erick2010 for those interested:

PS3 True Blue Installation Guide

Step 1: Make sure your PS3 is in V3.55 system, either OFW (official firmware) or CFW (official firmware). Which means if your PS3 is lower than V3.55, just update it to V3.55! If your PS3 is higher than V3.55, sorry, you can not use this item. please use E3 flasher to downgrade your PS3 to V3.55 first.

Step 2: When your PS3 is in V3.55, you need to install the PS3 True Blue V3.55 CFW. Here is the method on how to install PS3 True Blue V3.55 CFW.The update method is just the same as update the official firmware via USB storage.

  • Download the PS3 True Blue V3.55 CFW
  • Extract the file, you will get "TrueBlue-3.55-CFW" folder, you can see "PS3UPDAT.PUP" inside.
  • Prepare a USB storage, create a folder named "PS3"in the root of your USB storage, then create another folder named "UPDATE" in the "PS3" folder, in the end put the "PS3UPDAT.PUP" in the "UPDATE" folder. So it is: USB storage----PS3----UPDATE----PS3UPDAT.PUP
  • Insert your USB storage into your PS3 USB interface and power on your PS3.
  • Move to the system update option and choose update via USB storage.
  • Choose the PS3UPDAT.PUP and start updating, go and drink a beer, wait until it finishes updating. Don't do anything during the update progress.
  • Your PS3 will be in PS3 True Blue V3.55 CFW after the installation.

Step 3: Update your PS3 True Blue to the latest version V2.3.

  • Download the True Blue (JB2) PS3 Update v2.3
  • Extract the file you will get "TrueBlueUpdate-2.3.pkg"
  • Put the "TrueBlueUpdate-2.3.pkg" file in your USB storage.
  • Insert the USB storage into your PS3 and then install the pkg file in your PS3.
  • After you finish the installation, you will see the "True blue Update V2.3"
  • Click the "True blue Update V2.3" it will ask you to insert your PS3 True Blue. then insert your PS3 True Blue.
  • Go on the update procress to finish the update.

After this step, you have installed the PS3 True Blue successfully. Let's go and start playing a game. i will take "FEAR 3" as an example.

Notice: You need to replace the PS3 true blue eboot for the V3.60+ games before you play the games.

It means you need to download the both FEAR 3 game file and also F.E.A.R.3_EBOOT_PATCH_TB_ PS3-PARADOX if you dont do this step,the screen will freeze and change black. ok i have downloaded those files and also have patched it, let's go.

  • Before you power on the PS3, just insert the PS3 True Blue and the your game HDD.
  • Login Multiman and find the FEAR3
  • Press X to login the game
  • It will take you back to XMB
  • Go to "app_home/PS3_GAME/" and click it to play FEAR3
  • Done, congratulations!




Finally, below is a video of a True Blue (JB2) freezing issue that occurs on TB JB2 2.3, Rebug CFW TB and with Rebug Update 0.2 according to asdeburn via YouTube and a follow-up and a video detailing how to replace the PS3 True Blue Eboot files for PS3 3.60+ games alongside PS3 True Blue Playing FEAR 3 on v3.55 Firmware.












True Blue (JB2) PS3 JailBreak 2 v2.3 Arrives, RE Progress Updates

True Blue (JB2) PS3 JailBreak 2 v2.3 Arrives, RE Progress Updates

True Blue (JB2) PS3 JailBreak 2 v2.3 Arrives, RE Progress Updates

Follow us on Twitter, Facebook and drop by the PS3 Hacks and PS3 CFW forums for the latest PlayStation 3 scene and PS4 Hacks & JailBreak updates with PlayStation 4 homebrew PS4 Downloads.



#792 - technodon - June 12, 2012 // 7:10 pm
technodon's Avatar
i never tested my dongle updater before release, anyone else tried it? cause puss in boots seems to be the only one game that works it just happened to be the one that i tried? maybe i should start playing the lottery? lol. maybe it has some significance in reverse engineering the dongle though?

#791 - elser1 - June 12, 2012 // 10:41 am
elser1's Avatar
i'm a little confused (nothing new there) so does this mean with the pkg i can use a tb dongle once then instal pkg and no longer need dongle?

that would be great if so and if someone would lend/hire me a dongle for a day.. LOL

#790 - Xyth - June 12, 2012 // 9:29 am
Xyth's Avatar
Wololo's thoughts are ridiculously nonsense. Who cares if TB team will change encryption scheme. They still want us to believe if someone hacks TB, there will be no more new games. This is the same logic if we share PS3 exploits they can patch it. Who cares if Sony of TB patch their exploits. Of caurse they'll patch it, it is their job to protect their property. But if you call yourself a scene developer you can always comeup wit a new solution. This is what makes a scene The Scene.

These "It will lead to piracy" and "They can patch it" execuses are just a cover for their fear of Sony.

#789 - technodon - June 12, 2012 // 9:00 am
technodon's Avatar
following up on shad__'s excellent work on the modified true blue eboot, i repacked it as a installable pkg and also modified the text so it now reads remove the dongle and press x to return to the xmb. download link here: http://www.putlocker.com/file/6B780406C00FD776

#788 - PS4 News - June 7, 2012 // 11:40 am
PS4 News's Avatar
Below is an update from wololo (via wololo.net/2012/06/06/ps3-more-dongles-info-decrypted-by-oct0xor/) dubbed PS3 - More dongles info decrypted by oct0xor (covered a few posts above), as follows:

PS3 hacker oct0xor, who was already behind the base work that led to initial reverse engineering of the True Blue dongle, just twitted that he can decrypt True Blue’s stage2, as well as critical information from other clone dongles.

I can decrypt TrueBlue Stage 2, Cobra EBOOT.BIN, ps3usercheat cheatlist.dat and lv2 stage 1 and 2, right on PC.

You really can call me “DongleBreaker” now Thanks to flat_z who was with me all along.

As I said earlier, the people behind True Blue are not amateurs in the hacking scene and could definitely leverage that type of information. Hackers like oct0xor are not fighting against “we don’t know about it until it’s too late” Sony, but against people who regularly check all scene websites, and take action.

I have no doubt that the next True Blue firmwares will change their encryption scheme, and if not, another “magical” dongle will pop up in the months to come, from another random company (the same people who made true blue, of course), with a completely different security system.

That is, unless PS3 hackers completely reverse engineer the system behind the True Blue dongle, in a way that Sony can finally understand how True Blue are able to patch 3.6+ games so easily, and hoping that future games will be protected against the True Blue patches. That would calm down piracy on the PS3, and people who don’t get it will claim that this could kill the PS3 scene.

#787 - jabberosx - June 4, 2012 // 5:30 pm
jabberosx's Avatar
This is good news. But at the same time ANOTHER frikking dongle is down right shameful. I mean whats the frikking point. arrgghhhhhh I know make more money by pirating from pirates. knowing still doesn't help.

#786 - RobertoSlip - June 3, 2012 // 4:24 pm
RobertoSlip's Avatar
should be transparent, this would greatly facilitate..

#785 - userix - June 3, 2012 // 3:51 pm
userix's Avatar
Can I flash back to kmeaw 3.55 after flashing tb cfw 3.55 or is it a one way street ordeal?

#784 - PS4 News - June 2, 2012 // 4:15 pm
PS4 News's Avatar
Today PlayStation 3 developer Naehrwert has blogged (nwert.wordpress.com/2012/06/02/reversing-tb-part-1-the-vm/) on reversing the TB (True Blue JB2 PS3 Dongle) Part 1: The VM with details below, to quote:

Thanks to oct0xor (twitter.com/#!/oct0xor) we could get our hands on the decrypted TB payload (stage 2). Of course the first thing to do is to fire it up in IDA, our favourite tool of the trade. The entry code of the payload looks like this:

[Register or Login to view code]


In the first loop it will relocate itself using 0x1337C0DE as an identifier for the upper 32 bits and rewrite that to the actual base. The disassembly above was already loaded using 0x1337C0DE00000000 as base. While scrolling through the data section at the end of the payload one quickly figures out that the RTOC is 0x1337C0DE00017E40.

As I was analyzing the code I found a sub that was basically just a really big switch with random looking case values. Once I reversed the sub at 0x1337C0DE00002578 and some of the following ones and analyzed their usage in the switch sub, I knew that I was looking at a fricking virtual machine.

[Register or Login to view code]


Paranoid TB developers even used XOR-tables to obfuscate the VM instructions and data. The virtual machine is mostly stack based but the instructions let you work using registers too. The next thing to do is to reverse all the instructions and write a disassembler and emulator. Here (pastie.org/4015202) is some code to unscramble the embeded vm binary for further investigation. I’m going to write more about this topic in the future.

[Register or Login to view code]


From shad__ on IRC for TB DRM dongle users: EBOOT.BIN

[shad__] if it can help, you can play tb eboot without tb plugged in. Just, patch sys_sm_shutdown call in TB update pkg and unplugg Tb dongle then press x to exit.It will exit without reset lv1 and lv2.
[shad__] POC: http://www.mediafire.com/?z42clbkhjju1khy
[shad__] Now you can share your dongle with your friends
[shad__] was [email protected] * New Now Know How

Also this weekend Team E3DIY claim that they have also managed to run all PlayStation 3 games on 3.55 PS3 CFW (similar to TB/JB2) but they will likely peddle another dongle to do it unfortunately instead of a free PS3 scene solution.

Finally from oct0xor (via twitter.com/#!/oct0xor):

ps3usercheat skip r4=%x,r5=%x main_EBOOT.BIN main_vsh.self

I can decrypt TrueBlue Stage 2, Cobra EBOOT.BIN, ps3usercheat cheatlist.dat and lv2 stage 1 and 2, right on PC. pic.twitter.com/b2awqYLv

You really can call me "DongleBreaker" now Thanks to flat_z who was with me all along.


#783 - PS4 News - May 30, 2012 // 9:05 am
PS4 News's Avatar
Below is an update on the True Blue PS3 JB2 Dongle new security packaging, as follows:

30 - 5 – 2012

New packaging for True Blue incorporating security measures and an updated picture identification reference for clones

Due to the recent emergence of clones we are introducing a new packaging system and a security sticker on the dongle itself to help ensure customers receive original True Blue dongles.

Firstly, a new blister pack with a label over the blister will be introduced, as shown below. This provides several measures for the user to identify if the True Blue device received is likely to be original.

Note the unique security patterns in silver which are difficult to counterfeit, due to the colour variations on the background colours, materials used and complexity of the pattern itself. If the label appears to be stretched or appears to have been used before, then careful attention should be paid to the security sticker on the dongle itself.


The security sticker adhered to the dongle itself (shown below), partially covering the cap will provide the user with an indication of whether or not the dongle has been tampered with before delivery. Therefore, if the portion of the sticker covering the dongle cap has been broken, then it is possible that the dongle may have been tampered with. If this is the case, please use the TrueBlue 2.7 firmware as a means to check the authenticity of the dongle.

If the word clone appears in the PS3 XMB where the TrueBlue 2.7 version number is stated, then you should contact your reseller for assistance. Security stickers are designed with a number of security considerations in mind and are very difficult to reproduce exactly. This will aid retailers and end users in determining whether the product received is an original.


Some original True Blue dongles are in the supply chain yet to be sold, which do not have the new packaging. If you receive a True Blue dongle without the new packaging, then simply use the True Blue 2.7 firmware to identify whether or not it is an original. Details can be found on the information page and inside the 2.7 firmware download package on the downloads page.

Finally, we are updating the picture references for users to identify whether their PCB is an original True Blue or a CLONE. We have released several revisions of the True Blue PCB’s which are shown below. The recent CLONE posing as True Blue in a similar casing is also shown below and referenced as CLONE. If you have received one of these clones instead of the original True Blue you ordered, then you should contact the retailer who you purchased it from for a refund.