Sponsored Links

Sponsored Links

PS3 CFW JailBreak 2 and JB2 Updater RE for PlayStation 3 Details


Sponsored Links
149w ago - Following up on the initial PS3 JailBreak 2 news comes various PS3 CFW JailBreak 2 and JB2 Updater details today including the examination of an EBOOT.BIN from the Driver: San Francisco Blu-ray Disc in comparison to one from an official PS3 Game (BLES00891) Disc with developments on reverse-engineering the PS3 JB2 file dumps and more below.

To begin, whyudie states the following on the PS3 CFW JailBreak 2 and JB2 Updater for PlayStation 3: I just wanted to share this CFW. This CFW is intended more specifically for Jailbreak 2 dongle only. Most likely will not run well without that dongle. Perhaps some developers out there could investigate this CFW, and develop it even better.

If anyone out there want to install this CFW on your PS3. Do it at your own risk!!

JailBreak 2 Dongle Features

  • Can play backup games that require firmware 3.60 + (Direct boot just like the original games)
  • Only burned BD Disc format with some patches will work. For now, there's no info how to make a backup iso to work with this CFW.
  • Can play backup games from the HDD. PS3 games with FW 3.55 or lower (via internal or external hdd)
  • Only works on the PS3 with official/custom firmware 3.55, not the downgrade PS3.

Download: [Register or Login to view links]
Mirror: [Register or Login to view links]
Mirror: [Register or Login to view links]
Mirror: [Register or Login to view links]
Password: whyudie

And this is PKG files to upgrade dongle Jailbreak 2:

Download: [Register or Login to view links]
Mirror: [Register or Login to view links]
Mirror: [Register or Login to view links]
Password: whyudie

What's your source? Have you make a dump from JB2 Dongle?

From my local game store. I live in Indonesia. And I bought the dongle. And get the bonus cd and the CFW files is from that cd. And that CFW must be installed first on PS3, and upgrade the dongle with that pkg files.

Driver: San Francisco EBOOT from Blu-ray Disc courtesy of lindwurm:
[Register or Login to view links]
[Register or Login to view links] (Mirrors)
[Register or Login to view links] (Mirrors)

Driver: San Francisco EBOOT (BLES00891) from original PS3 game disc courtesy of elser1:
Download: [Register or Login to view links]

Driver: San Francisco EBOOT (Untested, Generated by SiLENTGame)
Download: [Register or Login to view links]

UPLAY SELF (Untested, Patched by SiLENTGame)
Download: [Register or Login to view links]

FIFA 12 EBOOT from Blu-ray Disc courtesy of lindwurm:
[Register or Login to view links]

Sniper Ghost EBOOT from Blu-ray Disc courtesy of lindwurm:
[Register or Login to view links]

Sakunchai also states the following on examination of the PS3 JB2 dump: I find 1 point not same in original FW in lv2_kernel.self
Download: [Register or Login to view links]

Also below are some related PlayStation 3 JB2 files from 3muk and ireggae among others and a preliminary PS3 JB2 RE examination, as follows:

Here is the files changed in the FMW including CORE_OS_PACKAGE.pkg, dev_flash_010.tar.aa.2010_11_27_051337 and dev_flash_016.tar.aa.2010_11_27_051337:
[Register or Login to view links]

PS3 .PKG File from the dongle, unpacked with an .ELF of the EBOOT included:
[Register or Login to view links]
[Register or Login to view links] (Mirror)

PS3 JB2 Reverse Engineering

Below is a preliminary synopsis from [Register or Login to view links] via [Register or Login to view links] and ps3devwiki.com/index.php?title=PS3JB2_Reverse_Engineering and ps3devwiki.com/index.php?title=Talk:Keys#sv_iso_spu_module_1.02-3.55:

JB2's dongle updater pkg, its EBOOT.BIN is just an FSELF (fake signed), the Driver: SF eboot fix is also an FSELF, FSELF's are mean't for debug consoles, easier to fself your game, then to actually sign it, you can patch retail FW to run FSELF's, either through the fw, or you can modify PL3, or even, resign the EBOOT.BIN, its nothing special, from the looks of it, they don't have any keys, just debug EBOOT.BIN's.

You don't need that dongle either, just resign the EBOOT.BIN or patch the FW to run FSELF's, their MFW could have these patches, or maybe, their dongle deliver's the patches. I do not know for sure, maybe their dongle does something else entirely, but I know its an FSELF, and you can make that run, without their dongle.

Dongle is DRM to make sure you have the dongle, the firmware 'special' functionality will not work without it. Contentdisc's contain fself'ed eboot.bin's.

Those JB2 eboot.bin stuff, actually isn't debug fself's, but readself says it is its their DRM. Can't be decrypted without their stuff. They have their own keys, which they are signing the EBOOT.BIN's with, I think they are debug eboot's resigned with their stuff.

SELF header

Control info

Section header

Encrypted Metadata

ELF header

FW Info

PS3 System Software

Remarks: needs JB2 dongle as DRM

Firmware Changes compared to OFW 3.55:
Download: [Register or Login to view links]

EULA.xml

Version.txt

CORE_OS_PACKAGE.pkg

lv1.self

Just one patch:

This is in lv1_map_htab to allow for RW mapping of all RAM. So who knows how many other lv1 patches are done at runtime.

lv2_kernel.self
dev_flash_010.tar.aa.2010_11_27_051337
\dev_flash\vsh\module\nas_plugin.sprx

"standard pkg patches"

dev_flash_016.tar.aa.2010_11_27_051337
\dev_flash\vsh\resource\explore\xmb\category_game.xml
\dev_flash\vsh\resource\explore\xmb\category_video.xml

Description

Dongle is DRM to make sure you have the dongle, the firmware 'special' functionality will not work without it. Contentdisc's contain fself'ed eboot.bin's

Debunking

  • It does not play 3.6x+/3.7x+ original content (it does not have the keys for it).
  • It can only play such content which is re-encrypted/resigned with their donglekeys.
  • Such content will be limited to those already decryptable and debug eboot.bin's.
  • Content for 3.55 and lower still work (after all, its just a MFW 3.55)
  • Needs the MFW (and cannot work on OFW's, that is why there is 'no power/eject trick')
  • If you are using special firmwares now, they will not be compatible with this one. e.g.
  • Incompatible with: OtherOS++, Cobra, pre 3.50 etc.

Hardware Dongle

Below are some pictures of the PS3 JailBreak 2 (JB2) aka True Blue dongole disassembled using an Actel ProASIC3 A3P250 - FPGA, a 24.000 MHz Crystal and a AMS1117 2.851049 Low Dropout Linear Regulator.

Components

Actel ProASIC3 A3P250 - FPGA

File: VQ100.png (below)
128-bit AES
1,024 bits of user flash memory
Datasheets and usermanuals: [Register or Login to view links]
Familyroot: [Register or Login to view links]

Pinout A3P250 VQ100

24.000 MHz Crystal

CLK for Actel

AMS1117 2.851049 - Low Dropout Linear Regulator

Datasheet: [Register or Login to view links] / [Register or Login to view links]

File: AMS1117 - SOT-223.png (below)

A 47 (unreferenced 5pin IC) - 5-pin SOT5 A 47 pinout

Winbond 25X16AVS1G (SPI Flash 16Mbit) - 8-pin TSSOP Winbond 25X16A SOIC-8 pinout

datasheet: [Register or Login to view links]

Sony PlayStation 3 hacker Mathieulh has also made some comments via IRC today on how the PS3 JailBreak 2 works with a follow-up HERE for those interested.

From [Register or Login to view links] on the PS3 JB2 device, to quote:

It seems the ps3jb2 loads masterdiscs with fself, with the algo provided and the right keyyou can decrypt said masterdiscs images right on pc and grab the fself files.

That's the algo for masterdiscs, ps3gen.dll has the static keys for masterdiscs. You can also get it from sv_iso the sdk tool that generates masterdisc images.

Then you take the decrypted fself and resign it for 3.55 with makeself then swap eboot. I think it should be somewhere in the PS3_Generator_Tools-312.zip in the 3.60 SDK but I'm not finding it, but that's where the master disc stuff is.

Finally, upon examination several users including DanyL, TheLostDeathKnight and [Register or Login to view links] have stated that the JB2 doesn't use a new PlayStation 3 exploit nor contain PS3 3.6+ keys, and that the dongle is only used as identification for activating the patch.

For those curious, patching the appldr keys has been done but not made public back with the PS3 3.56 keys so it isn't unfamiliar to most PlayStation 3 developers but unfortunately it is patchable by Sony. A brief outline of the process involved is below, as follows:

Obtain PS3 Debug EBOOT file from Sony's Developer Network via Debug console by one of the following methods:

  • Boot up your PS3 to the XMB, make sure in debug settings that NP environment is set to “sp-int” or “prod-qa”, sign into PSN (with sp-int or prod-qa credentials, you can use the quick sign-up), and launch the game. If your in luck, it will say an update is available – download it!
  • To get the URL you have a few options. You could either sniff out the connection with something like Wireshark - that takes a bit more setup. Other times the URL is actually passed right to dtccons - so make sure you have the debugging windows open. Or, you could use any number of the PS3 Proxy applications to grab the link.
  • Those who know their PS3 Game's Title ID and are seeking PS3 Game Update Packages can now use this simple guide to grab them while they last.

  • Patch Retail PS3 Firmware to run a Debug EBOOT file
  • Dump and burn the PS3 3.60+ games to BD-DVD with the included Debug EBOOT file
  • Add the DRM to the PS3 MFW / CFW that JB2 uses and validate it via the dongle

The above process will likely continue to work until Sony locks down the PS3 Debug EBOOT files.

PS3 JB2 Keys

The encryption keys for PS3 Debug Discs utilized by the PS3 JB2 method can be found below.

Download: [Register or Login to view links] / [Register or Login to view links]









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!

Comments 860 Comments - Go to Forum Thread »

• Please Register at PS3News.com or Login to make comments on Site News articles. Thanks!

niwakun's Avatar
#845 - niwakun - 106w ago
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.

Tidusnake666's Avatar
#844 - Tidusnake666 - 106w ago
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.

roeykarou's Avatar
#843 - roeykarou - 106w ago
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...

antinun's Avatar
#842 - antinun - 106w ago
Great news!

HeyManHRU's Avatar
#841 - HeyManHRU - 106w ago
Well it looks like I was better off not getting the dongle after all.

Sponsored Links

Sponsored Links
Sponsored Links

Sponsored Links







Affiliates - Contact Us - PS3 Downloads - Privacy Statement - Site Rules - Top - © 2014 PlayStation 3 News