78w ago - 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:
eboot payload
Offset(h) Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00008730 00000000 09 02 12 00 01 00 00 80 FA 09 04 00 00 00 FE 01 .......€�.�.
...
000A3620 0009AEFF 99 0A 4C 65 2A CE DE D6 0D C8 D2 73 FC B3 85 E2 ™.Le*�.�sü�…â payload_2.4.bin
SHA1: C062057BFBE4A0DF6C6C6E1B33C7561BC859C23F
MD5: 69FC4CE04DD4255A0BEEF4C2168F0AB0
CRC32: 1C9EE18
CRC16: 85DE
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
860 Comments - Go to Forum Thread »
ff_8000000000539F78o
After swapping back in my original 160GB HDD, I was still getting the 8002F281 error. I ended up having to do a full PS3 Reset and reformat of the 160...
I don't know about retail though, I only have one and it's already on 3.41 so I rather not touch it, but I didn't see anything that looks like hashes. Flags are there though. (like the product mode flag, QA flag, debug support flag etc etc...) There are also factory informations stored in there (such as the first firmware flashed at factory) but no hash that I could see, though maybe I overlooked something.
Of course the bootloader wouldn't be in any eeprom, lv0 probably starts and talks to syscon through a vuart in order to read the eeprom content (if the hashes are there) and look at the hashes (to compare them to the digests from the other coreos selfs)