78w ago - 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.
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
Fixed games requiring "BD Mirror"
True Blue firmware version is now displayed on the XMB "System Information" screen
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:
KaKaRoToKS In your opinion is worth buy the true blue?
xl14 no. Dont
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
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.
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.
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.
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
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.
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
Transient I don't care about fame or credit's i just try to talk to peoples but it is a diff if you talk in public via forums or if you talk private via irc channel's and so on. I never made any mysterious about my finding's but i won't do it puplic any more. Anyway, i already told other's about my finding's in case of the core dump function. It's just thing's like that WHY i mainly don't talk puplic any more. I don't need to proof thing's to any one. If you wan't to know something ask me in private, then trie, and if it works....well you then will see for your self.
One last word about credit's... if i want to have credit's i would release stuff under my public name and not under a "anonymous" name
racer0018 You misunderstood me. I'm still there and do thing's and from time to time you will also see releases under my puplic name. But yea... those are 2 diff world's... the public scene and the underground scene. Really you can't imagine. Everything start underground. And sooner or later it get's public. But the real ongoing is in underground scene.
That is the last thing that we need is for you to do that. Are we not working all for the same goal and that is to play newer games without the need for dongles. Just don't give in a go underground. Thanks