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

December 22, 2011 // 11:53 pm - Shortly following the True Blue v2.4 PS3 dongle update below, today EussNL has made available an UnPKG'd / UnSELF'd version, the JB2 TB v2.4 payload and an IDA update which contains fixed EBOOT data for other PlayStation 3 developers.

Download: True Blue Dongle Update v2.4 / True Blue Dongle Update v2.4 (Mirror) / True Blue Dongle Update v2.4 (Mirror #2) / True Blue Dongle Update v2.4 UnPKG'd / UnSELF'd / True Blue Dongle Update v2.4 Payload / IDA DB EBOOT_SHT_Fixed.i64 / True Blue Update 2.1 and 2.4 Comparison by chazz

From the PS3 Dev Wiki (linked above):

True Blue PS3 Payload (2.4)

located in unself'ed eboot.bin @ offset:

[Register or Login to view code]

payload_2.4.bin
[Register or Login to view code]

The True Blue PS3 dongle 'marketing team' have made an announcement ( which sounds worse than what you'd expect to hear from $ony themselves ) regarding the JailBreak 2 TB v2.4 update and clone dongles as well.

For those with a dead True Blue dongle, Mark Webber has posted the following method to attempt repairing it via: ps3crunch.net/forum/threads/2047-JB?p=23677#post23677

JB King is not a 1:1 clone, it uses an ST IC for communication with a PC, the TB does not have this at all. There is a very simple way to repair a "dead" TB dongle but you will need some hardware to do it. The cause of the "death" is that the SPI is blanked out - fill in the blanks.

You will need:

  • SPI Flash Programmer (get one from ebay)
  • The original 2meg update file.

1. Remove SPI flash from TB board
2. Put into programmer
3. Load 2Meg file and flash SPI
4. Replace SPI back onto TB board
5. Put back into PS3 & update as normal.

I did tell everyone way back the TB had a suicide mech built-in. The TB will erase the SPI flash and leave it dead in the water as soon as it detects an attempt to do anything to it. The sad thing is, it is doing it with false positives as well, hence so many dead dongles.

Finally, below is the official True Blue Update 2.4 changes from the ReadMe file as follows:

True Blue Dongle Update v2.4

How to update:

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

  • Stability improvements
  • Enhanced dongle security

- 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



True Blue JB2 PS3 v2.4 Update Payload, IDA Fixed EBOOT Data Out

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.



#852 - StanSmith - August 25, 2012 // 5:27 am
StanSmith's Avatar
So I used this and dumped 2 files from Ghost Recon FS. Now what?

They aren't near the size of the eboot.bin so what are they good for?

#851 - Brenza - August 25, 2012 // 1:10 am
Brenza's Avatar
You shouldn't have released it... now they'll fix the exploit! >.>

#850 - violato135 - August 24, 2012 // 9:40 pm
violato135's Avatar
Can I NOT use a dongle and jailbreak a ps3 without it???

#849 - imajei - August 24, 2012 // 8:43 pm
imajei's Avatar
I don't have a dongle so can someone with a tb upload a decrypted ghost recon eboot i have an idea please

thats a pretty please i'm bored and need something to do thanx to the good ol community lol.

do i need a tb dongle to do this?

#848 - fantopoulos - August 24, 2012 // 7:39 pm
fantopoulos's Avatar
i have a true blue will do my best to get a dump for you to proceed where we were stuck for a long time but no it seems like we are going uphill again thanks shadoxi for starting this elf dumper , amazing work cheers triple thumbs up

#847 - Asure - August 24, 2012 // 9:21 am
Asure's Avatar
shadoxi we can figure out the original ELF size using SCEtool to get this info right? (find start of elf64 header, + size = end of elf)

Example

[Register or Login to view code]


Then we know the section headers start at 0x17EC228

Last section STRTAB:

[Register or Login to view code]


So elf ends at 0x17EC0F7 + 0x12C. We add padding to 0x17EC228, and insert clean elf64 section headerd dump from original eboot.bin, right? Or does this dump ELF+section headers+some extra stuff we can cut off?

Anybody care to post a dumped elf (raw, with this tool) so i can look at it?

#846 - shadoxi - August 24, 2012 // 8:01 am
shadoxi's Avatar
Following up on the previous update, today I am releasing my True Blue USB dongle PS3 ELF dumper which works with any PlayStation 3 Firmware greater than 3.56 to dump the encrypted TB EBOOT / ELF files once they are loaded.

Download: True Blue USB Dongle PS3 ELF Dumper / True Blue USB Dongle PS3 ELF Dumper (Mirror) / True Blue USB Dongle PS3 ELF Dumper (Mirror #2) / True Blue USB Dongle PS3 ELF Dumper (Mirror #3) / True Blue USB Dongle PS3 ELF Dumper (Mirror #4) / True Blue USB Dongle PS3 ELF Dumper (Mirror #5) / True Blue USB Dongle PS3 ELF Dumper (Mirror #6) / True Blue USB Dongle PS3 ELF Dumper Source Code / True Blue USB Dongle PS3 ELF Dumper Source Code (Mirror) / UTEBOOT (DUMPEDBOOT.bin and DUMPEDBOOT1.bin) by arnes_king / Mass Effect 3 BLUS30853 RAMDUMP by gibson25 / TB ELF Dumper v2 (np_trp_prx.rar) / TB ELF Dumper v2 (Mirror) / DUMPEDBOOT PoC by mellss

Tested on:

  • Original 355 -> ok
  • True Blue CFW v2 -> ok
  • ...

There are some bugs (size of dump ...) but it works. It's ELF dumper from memory and it work with True Blue cfw v2 and any 3.55 firmware because it doesn't use lv2 peek/poke.

Warning: It will not brick your ps3. But I am not responsible for any damage.

HOWTO:

  • Enable dev_blind with multiman
  • copy libsysutil_np_trophy.sprx from /dev_blind/sys/external/external to dev_hdd0/ and rename it "orignal_libsysutil_np_trophy.sprx"
  • copy my modified "libsysutil_np_trophy.sprx" to /dev_blind/sys/external/
  • load a True blue game from multiman
  • exit multiman
  • run your game
  • wait few minutes (if you get black screen after 3 minutes reboot ps3)
  • exit game
  • go to ftp
  • in dev_hdd0/ there are your decrypted DUMPEDBOOT.bin
  • copy and rename it with another name.

Howto uninstall patch - Two ways:

  • You could uninstall this patch by replacing modified libsysutil_np_trophy.sprx by orginal libsysutil_np_trophy.sprx
  • Or update in recovery mode

Thanks to: Ps3dev

Brief Guide:

1 - Install TB ELF Dumper first as stated in its readme file.
2 - Start Multiman, it will make a dump of multiman eboots, so you must delete it first by browsing to dev_hdd0 then delete all DUMPEDEBOOT.BIN files you found there.
3 - Back to multiman game selection then select any TB game then launch it.
4 - Start the game from XMB then wait for some times until game start.
5 - Exit game now then start multiman again then browse to dev_hdd0 and now you must found a decrypted game dump.

From PlayStation 3 developer deank (via pastebin.com/avcM5iuU) comes a revision as follows:

Download: TB ELF Dumper v2 (np_trp_prx.rar) / TB ELF Dumper v2 (Mirror)
[code]
// Author: Shadoxi
// Modified:

// Backup the original /dev_flash/sys/external/libsysutil_np_trophy.sprx to /dev_hdd0
// Replace /dev_blind/sys/external/libsysutil_np_trophy.sprx by this sprx


#include
#include

#include
#include

#include
#include
#include
#include

SYS_MODULE_INFO (sceNpTrophyhook, 0, 1, 0 );
SYS_MODULE_START( _start );
SYS_MODULE_STOP ( _stop );

SYS_LIB_DECLARE( sceNpTrophyhook, SYS_LIB_AUTO_EXPORT | SYS_LIB_WEAK_IMPORT );
SYS_LIB_EXPORT ( loader_sprx, sceNpTrophyhook );

int _start(void);
int _stop(void);
void DumpELF_Payload(void);
void loader_sprx(const char* PATH_PRX);

static void write_message (char const * message)
{
unsigned int write_length;
char const * end;
for (end = message; *end != '\0'; ++end);
sys_tty_write(SYS_TTYP_PPU_STDERR, message,end - message, &write_length);
}

void DumpELF_Payload(void)
{
write_message("Dumping ELF from RAM...\n");
int fd;
uint64_t nread;
uint64_t ptr= 0x00010000ULL; //ELF offset in RAM;
uint64_t sizeelf = 35*1024*1024; //Need a way to get size of ELF

char dump_path[30]="/dev_hdd0/RAMDUMP-00.BIN";
for(uint8_t i=0; i

#845 - niwakun - August 22, 2012 // 2:11 am
niwakun's Avatar
the thing here is that they didn't tell anything about the dongle itself, maybe they already pawned the dongle's security chip (ATMEL that is) and they didn't tell it publicly so once TB released something new (security or algo or something), DUPLEX, N0DRM or whatever can do the same to piss off the TB makers again and again.

As always, if TB makers decided to do it all over again with new hardware to support their new security system, a lot of existing TB users will be pissed off for sure.

#844 - Tidusnake666 - August 22, 2012 // 1:53 am
Tidusnake666's Avatar
It seems to me so. They'll pull out new TB CFW v3, new dongle payload, change DRM algo so all new games will still require TB.

They won't quit the scene so easily.

#843 - roeykarou - August 22, 2012 // 1:46 am
roeykarou's Avatar
friends, i don't understand. is it the END for TB, or they going to upgrade the cracking (lets say, i don't know to play a 4.2V games) and come back again to the scene?

i'm very confused on what happened to them and why they are very quiet...