107w 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!
Recently and_fis reports that the PS3 Slim 3K series of PlayStation 3 consoles are surfacing on 3.55 Custom Firmware (CFW), leading to speculation of a new DRM-infected JailBreak Software Tanpa dongle or service from Indonesia.
To quote (via ps3crunch.net/forum/threads/5321-3K?p=58294&viewfull=1#post58294) on the (tokoteknologi.com/home/browse/25-consolemesin.html?sef=hc):
For some Indonesian rupies according to the site above you can purchase A 3K console with a Seri CFW 3.55 (RFW Version) installed! Which also comes with a JAILBREAK SOFTWARE TANPA DONGLE as they call it... If this site is real then someone has found a new exploit that allows 300X version ps3 consoles to downgrade to 3.55 cfw. They have also locked this to a new drm dongle... Let the games begin again!
Rp 3.700.000,00 or about $320 usa, for a base model 160 gb ps3
The only way this would be possiable is if they used hardware to somehow reflash the syscon. that is where the hash checks are that determine the lowest firmware you can have...or they were able to use a hardware flasher and a cfw that had all the hash checks removed.
Or changed and reflashed a cfw that the ps3 "thought" was the right firmware... IDK there is nothing on wiki about either processes
From Abkarino: I know this seller and i talked with him and have a deal 1 and half month ago, they offer me a pre-moded 3K console and they does not sell the modchip/method used to do that. Also he claim that this console uses a special modified CFW based on Rogero CFW.
Also they had used some kind of modchip/flasher to do that. Also he told me that there is a modchip under development for hacking 3K console and it must be released around this month, but till now no new news from him.
From and_fis: I found this info (lan.st/showthread.php?t=3313&page=2) from back in 2010 when 3.41 had alot of access and workings... So if it is true that syscon can be written to with a pkg BUT, it would have to be offically signed or a hardware flasher of some sorts would have to be used if a pkg could not. So in theory, it would be possiable to reflash a syscon from a factory install of 3.60 to 3.55
Thanks Abkarino I posted this at the same time you did.. So my suspicions were true about a hardware flasher.. Thank you for the info
From Abkarino: Yea may be they had found a way to reprogram Syscon EEPROM may be they had used an SPI Flasher since SysCon conect to Cell/BE using SPI Bus. I think that they had used a hardware method not a software (sure if this is legit and not a fake, until some one get this console and confirm this news).
Below is a video from dantezteam (via twitter.com/dantezteam/status/244856386469638144) demonstrating what appears to be PSN back online for PS3 3.55 TB CFW using a ppoof method.
The video shows today's date (September 9, 2012) with him downloading files from Sony's PS Store while being connected to PlayStation Network using a new PSN passphrase that has surfaced in encrypted and decrypted format (via ps3devwiki.com/wiki/Online_Connections#Online_Connections).
He is on DEX, uses FAKE PLUS and points the finger showing is ON with a CFW (according to him) 3.55 TB spoof.
In short: He bought borderlands in the video via DEX with PLUS option ON... For me is just another attemp to troll or to give some life to TB, since he says he is using CFW TB 3.55 Spoof. And in the part description he says later I will add the Web.
So he avoided so far any download link and surveys because he knows what happens next: youtube.com/user/dantezteam
From dantezteam comes a FckPSN revision by Chinese developer Luckystar (via bbs.duowan.com/thread-28656355-1-1.html): http://www.multiupload.nl/40S5UPQYVH / http://www.putlocker.com/file/E62645DA4EE9339C (Mirror) / https://anonfiles.com/file/03cb21c25efd41bda59885fd2edfca51 (Mirror #2)
Here is the upstreams and video for those interested: ustream.tv/recorded/25308408 and ustream.tv/recorded/25328218
Finally, below is what redcfw claims is a real TB2 LV2 dump for those interested:
ALL TB2LV2 DUMPs posted before were FAKE!! tb2.51 lv2 dumped on Mar 2012. folks, feel free to study it.
Today /GriFFin reports that OxweB has apparently leaked the True Blue PS3 disc BCA codes (although curiously a source wasn't specified), however, they are now conveniently deemed useless as the DRM-infected USB dongle itself.
To quote: When the True Blue dongle first launched last year, it was originally using 'special' blu-ray discs to play games, instead of just DRMencoded eboots on the HDD.
But even after all the Paradox releases, there was a few games that only were available still on 'special' blu-ray discs. Over the course of last year, various groups try to figure out how to copy these discs, as they were sadly pirate stores that wish to sell them to their customers. Finally have much research the BD-Rom marks called 'BCA Codes' were figured out so they could by copied on normal blu-ray burner.
And now an person by the name 'OxweB' has leaked them onto the 'net, as basically they are useless now, but still it is part of sad scene PS3 history!
These are BCA codes off the TB discs (the barcode on the inner part of the disc).
You to can read them off the disc yourself with a scanner or magnifying glass, they are in binary format (skinny line = 0, Fat line = 1). Binary to HEX and there you go, a code almost ready to be stamped on to a BD-R.
*Note - It's not that simple for regular retail games as there is still the PIC Zone to contend with.
**Note - I realize these aren't overly useful but it's information which is all worth it in the long run.
Finally, in related news from GoD]oF[WaR (via nextgenupdate.com/forums/playstation-3-exploits-hacks/583397-bca.html#post4685403) to quote:
I have done more research on BCA codes, they seem to be the new protection put on games, meaning with these values they can be cracked, and possibly pirated to even non-jailbroken systems.
For those unaware, BCA is the new protection utilized in newer games and with a future editor you can have the BCA codes to use with the a loader which can patch games to run without the needed keys.
There will be a patch released for each game, which is basically 64 bytes of BCA data in the form of a separate text file, that will come with the ISO file (this obviously only applies to scene releases)
IF you have access to a retail copy of the game, then you can obtain the BCA code yourself to patch the game.
Changelog, roughly translated:
New IOS 38 base. dev/mload with powerful features and EHCI driver based in interruptions and more stable
Support for DVD USB Devices: It can run only DVD backups from .iso (original don't work because DVD drivers don't support the Wii format). Remember you must insert a DVD to work at start the program.
Support for BCA datas. You can add it from .ISO offset 0x100 (64 bytes). If this area is filled with zeroes it use one BCA by default (NSMB compatible).
New ioctl 0xda function supported in dip_plugin and new option added for
DVD mode to read the BCA Datas from the original DVD
Support to load games from DVD with alternative DOL (press '2' without
USB device or press the DVD icon from the upper-right corner in the selection game screen)
Support for SD and USB FAT/FAT32: Now you can use cheats codes and loads alternative .dol from the USB 2.0 device (FAT partition is required)
Added alternative dol loader (now support for 5+ dols) for games as Red Steel and othrers (see readme.txt) , New error 002 patch and videomode autodetection patch (for PAL2NTSC, NTSC2PAL and NTSC2PAL60 (use F. PAL60 for this))
Added direct access for Dol Alternative selection
You can load differents ehcmodule.elf from sd:/apps/uloader/
Parental control added: by default the password is 00000 (the last 0 is the 'ENTER', so you can program as new password as XXXX0 ). You can change it from special menu pressing HOME. You can exits from the password box pressing B. Parental control list the last 8 games launched with date/time, enables the password box and fix a new password. Now 00000 disables the Parental Control
Support for covers (less than 200KB 160x224). You can download from internet or adquire covers from the curren tfolder in the SD automatically
Added one option to delete PNG icons/covers
Some bugs fixed (bug with no modchip game instal, for examplel)
Support for multiples WBFS partitions (max 4).
Possiblity to use the alternative cIOS 223 (only to launch games)
Added one option to rename games
Added one option to record the cheats selected from txt files
New usb code and more!
The above thread gives information on BCA codes for the Wii, which could also apply to PS3 games in the same way. Meaning these BCA codes could lead to easily pirating games on all consoles who utilize the BCA algorithm.
After further research, I am under the suspicion that these BCA codes are in fact a lead to playing pirated games (3.60+ games burned to BD/Launched via USB or external HDD - played on 3.55 WITHOUT CFW) possibly on current firmwares with a real developer at hand.
Basically these BCA codes could lead to playing these burned ISO images on 3.55 (No CFW; without 3.60+ keys) and possibly current firmwares.
The BCA codes that True Blue "leaked" are actually the codes to games that have been tested and work on 3.55 OFW. With the use of a new true blue dongle (JB2/Jailbreak2), games played off the BD without 3.60+ keys.
The games that have been tested are the ones listed below;
Driver san Fransisco
God of war Origin
Sniper ghost warrior
I load up Multiman, select Ghost Recon FS and it goes backt o XMB like normal.
I try to run GRFS and it black screens and locks up.
I reboot and load up multiman and it also black screens and locks up.
I reboot WITHOUT the dongle and it finally loads MM.
I copy the file over to the PC, convert from ELF to BIN, put it in GRFS folder.
I reboot WITH the dongle. goto MM select GRFS go back to XMB.
I run GRFS from DVD. It loads up Multiman.
I tried this 3 times and each time its the dump of Multiman NOT GRFS. And the file DOESN'T go, 00, 01, 02 etc, there is only 1 file and its 00. At least v1 gave multiple files but I couldn't get GRFS to work without the tb patched files.