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

180w ago - A few weeks back details and payloads for Dumping PS3 Per Console Keys surfaced followed by news of a PS3 Metldr Exploit, and today PlayStation 3 developer xx404xx on IRC has shared his PS3 Metldr / Per Console Key0 findings thus far.

Included below are a PS3 EID Rootkey Dumper (SELF) which is loaded through lv2patcher, an EID Decrypter Script, the required EID Static Keys and more, as follows:

[xx404xx] lol wtf you can write to metldr!!!!!!
[xx404xx] 0x17014 - Write eEID/Write metldr Holy crap, it writes passed data to the region of FLASH memory where eEID or metldr data is stored !!! And GameOS is allowed to use this service !!! Do not experiment with this service if you don't know what it does or else your PS3 will not work anymore !!!
[xx404xx] http://img841.imageshack.us/img841/1617/newbitmapimage3en.png
[xx404xx] http://img824.imageshack.us/img824/5747/newbitmapimage3f.png I highly recommend you all go look at that
[xx404xx] Is anyone taking a look at that paste bin? http://pastebin.com/rFD5ASJa (via http://pastie.org/private/qwndjafrtkvhe9cikbxhg from lunuxx)
[xx404xx] Here's a pic from this leaked doc i found
[xx404xx] http://img684.imageshack.us/img684/7951/newbitmapimage6k.png
[xx404xx] http://pastebin.com/rFD5ASJa there's no per console key 0 in the guide
[xx404xx] and you need this leaked doc
[xx404xx] ill go upload it
[xx404xx] the per console key0 is only for my console......
[xx404xx] but you can obtain your own lv0
[xx404xx] im upploading the doc now
[xx404xx] i was hesitant about leaking this
[xx404xx] but here you go, you will need this info
[xx404xx] http://uppit.com/caofvtbovo2y/Cell_Broadband_Engine.doc
[xx404xx] it has doc on the spu's
[stronzolo] what do you think about the picture who math posted on the twitter ?
[xx404xx] real
[xx404xx] he already told us how he does it....
[stronzolo] us = who ?
[branan] everybody. His thing about metldr from a couple days ago applies to bootldr just as well
[xx404xx] it's no secret
[stronzolo] so why math can do it... and others can't ? what's wrong ?
[xx404xx] lol if he didnt want other's knowing about it mabye he shouldnt tweet so many hint's.......
[xx404xx] we can do it
[xx404xx] read the docs
[xx404xx] he talk's about how we dump the local storage from the spu's
[stronzolo] 404 when do we know if your key is key 0 ?
[xx404xx] when someone prep's a step by step guide to dump bootldr
[xx404xx] Patent[How to dump lv0 with HW ;] that's all im going to say for know....there will be more later, and this is not a complete guide, but math gave you eveything else you need....
[xx404xx] http://server250.uppit.com/files/7/3pwes08br3bp7m/WHATEVER.pdf
[XX404XX] Ik how math does the bootldr exploit
[antikhris] do tell...
[XX404XX] http://pastebin.com/xkXxk8fM

On the PS3 True Blue Dongle:

[xx404xx] True blue is stupid
[xx404xx] it's the fselfs
[eussNL] its more than / just / fself, try unself one and you see what it is
[eussNL] its DRM'ed fself
[xx404xx] ps3 crunch is trying to make money on the new dongles......
[eussNL] well not surprising as GaryOPA is reseller
[xx404xx] where do you think
[xx404xx] it came from
[xx404xx] i dont mean drm
[eussNL] what?
[xx404xx] i mean the fself
[eussNL] there are plural items
[xx404xx] debug servers obv
[eussNL] well, they only have limited titles so there is your clue

From pastebin.com/rFD5ASJa: (img573.imageshack.us/img573/5026/newbitmapimage4z.png)



BootOrder explained (Thank's wiki) VERY IMPORTANT (per_console_key_0 is not the key which will be derived, but is the key which has derived per_console_key_1) We have pck1 using the dumper, in order to obtain pck you need to dump it out of ls. In order to do that with hardware you should look into math's comment's about dumping a shared lsa.

In order to do this with software you should either use math's bootldr exploit or you need to exploit the spe secure runtime.... (Not all that hard with the two recent exploit's)

With Runtime Secure Boot feature, an application can run a check on itself before it is executed to verify that it has not be modified and compromised.Secure Boot is normally done only at power-on time, but the Cell BE processor can Secure Boot an application thread multiple times during runtime. (PS3'S doesn't do this right as you can see in the failoverflow vid)

Passing execution: (img508.imageshack.us/img508/8544/eib.gif)



Spe execution control diagram: (imageshack.us/photo/my-images/835/newbitmapimage3a.png/)



Error Reporting: (imageshack.us/photo/my-images/193/newbitmapimage5us.png/)



A Debug support flag set in SC EEPROM at address 0x48C50. When this flag is set, the token is read from SYSCON and decrypted, this gets passed to various modules to unlock certain functionality.

Debug support flag is tied to EID which is supposed to be hashed and saves in SC EEPROM

[Register or Login to view code]

A FSELF support flag set in SC EEPROM at address 0x48C06. When this flag is set, the token is read from SYSCON and decrypted, this gets passed to various modules to unlock certain functionality.

[Register or Login to view code]

Eid Rootkey(1) Dumper (Load through lv2patcher) (You need this)
http://uppit.com/pfny5nmqhhs1/Dump_Eid_Rootkey.self

Decrypt your eid with this (You need this)
http://uppit.com/tk5c4svtbz1x/EID_DECRYPTER_SCRIPT.cpp

[Register or Login to view code]

Eid static key's (You need these)

1.00 Debug/DEX - aim_spu_module.self

[Register or Login to view code]

3.15 Retail/CEX - aim_spu_module.self

[Register or Login to view code]

3.41 Retail/CEX - aim_spu_module.self

[Register or Login to view code]

3.55 Retail/CEX - aim_spu_module.self

[Register or Login to view code]

3.56 Retail/CEX - aim_spu_module.self

[Register or Login to view code]

1.00 Debug/DEX - appldr

[Register or Login to view code]

3.15 Retail/CEX - appldr

[Register or Login to view code]

3.41 Retail/CEX - appldr

[Register or Login to view code]

3.55 Retail/CEX - appldr

[Register or Login to view code]

3.56 Retail/CEX - appldr

[Register or Login to view code]

1.00 Debug/DEX - isoldr

[Register or Login to view code]

3.15 Retail/CEX - isoldr

[Register or Login to view code]

3.41 Retail/CEX - isoldr

[Register or Login to view code]

3.55 Retail/CEX - isoldr

[Register or Login to view code]

3.56 Retail/CEX - isoldr

[Register or Login to view code]

1.00 Debug/DEX - lv1ldr

[Register or Login to view code]

3.15 Retail/CEX - lv1ldr

[Register or Login to view code]

3.41 Retail/CEX - lv1ldr

[Register or Login to view code]

3.55 Retail/CEX - lv1ldr

[Register or Login to view code]

3.56 Retail/CEX - lv1ldr

[Register or Login to view code]

1.00 Debug/DEX - lv2ldr

[Register or Login to view code]

1.00 Debug/DEX - spu_pkg_rvk_verifier.self

[Register or Login to view code]

1.00 Debug/DEX - spu_token_processor.self

[Register or Login to view code]

3.15 Retail/CEX - spu_token_processor.self

[Register or Login to view code]

3.41 Retail/CEX - spu_token_processor.self

[Register or Login to view code]

3.55 Retail/CEX - spu_token_processor.self

[Register or Login to view code]

3.56 Retail/CEX - spu_token_processor.self

[Register or Login to view code]

3.15 Retail/CEX - spu_utoken_processor.self

[Register or Login to view code]

3.41 Retail/CEX - spu_utoken_processor.self

[Register or Login to view code]

3.55 Retail/CEX - spu_utoken_processor.self

[Register or Login to view code]

3.56 Retail/CEX - spu_utoken_processor.self

[Register or Login to view code]

In related news, Sony PlayStation 3 hacker Mathieulh Tweeted the following comments on what appears to be the PS3 Firmware 3.73 lv0 bootloader decrypted:

Boot Loader SE Version 3.7.3 (Build ID: 4611,48369, Build Date: 2011-10-12_12:31:19) What's taking you so long ? http://twitpic.com/7e0m6w


Boot Loader SE Version 3.6.6 (Build ID: 4534,47762, Build Date: 2011-06-16_13:24:46) I am bored....

Oh ! that's nothing just a little string from the 3.73 lv0....

By the way, I won't be posting keys, I won't be posting dumps and I won't be saying how it was done, time to work gentlemen.

It's a command prompt because I am using my own tool to decrypt selfs to elf and not the buggy unself. Not like an unself prompt couldn't be faked though.

You can't sign lv0 on a cech-3000 sorry. No, the new bootloader uses a new keyset.

The build number should be proof enough, as long as you can get your hands on a decrypted lv0 that is. Posting keys is not an option, posting hashes of the keys wouldn't bring you any additional proof because you have no way of verifying those, besides Sony's lawyers would claim that I'd be posting encrypted forms of the keys like they did in the fail0verflow trial, and I am not posting screenshots because lv0 contains copyrighted code.

So unless you have any other "proof" in mind that I could post legally without fearing prosecutions, feel free to tell me about these.

I am definitely not releasing it anyway, I've already said how I am not releasing anything anymore, EVER. I am a man of my word.

By the way instead of demanding, people should start looking at my "pwning metldr the "easy" way" post where I gave the first steps into exploiting the bootloader and one of the required exploits and start working from that, there is no point in making demands, asking for "proofs", keys and whatnot, I won't be sharing these, so you'd better start working; I've given you a nice starting point.

I am done talking about lv0 decryption, feel free to resume this talk once it becomes public and people can verify the strings I posted.

Although unconfirmed, eitjuhh has Tweeted the following: Don't flame ppl!.. lv0 decrypted from my debug console!! http://pic.twitter.com/sVXinzlb

Posted a little preview of the ps3swu.self from 4.00 - http://pastie.org/2980794



Shortly following, he Tweeted (twitter.com/#!/eitjuhh/status/144763029224038400): Found new keys in OFW 4.00 !! doesn't know which keys they are at this moment!.. but i think the new twitter.com/#!/eitjuhh/status/144763029224038400/photo/1


bit i think they are the new klic_dec_key keys sony wrote them twice in other ofw's now 3 times?? http://pastie.org/2985773

60 00 00 00 E8 01 00 80 38 21 00 70 7C 08 03 A6 --- Second new key found!

And he Tweeted (twitter.com/#!/eitjuhh/status/145054115750346752): Yesterday I did a second test! CFW is RUNNING ppl!!.. Tonight I will build in Peek&Poke! Video: soon, Release: Before Christmas !

From Sony PS3 hacker xorloser (CitizenX of scene release group PARADOX) via Twitter:

V3.60 and above have the secrets encrypted inside lv0, and the lv0 keys are not publicly available.

lv0ldr loads lv0 direct from flash rather than from memory, plus nothing else is running at this stage. So trickier, but doable.

From zecoxao comes a brief guide: How to Dump BOOTLDR Unencrypted (Decrypted)

Things you'll need:

  • PS3 on 3.55 OTHEROS++ (this was tested on a slim, but phats are probably achievable aswell)
  • Latest linux kernel (or any of the 3.x.x kernels by glevand precompiled)
  • Knowledge of linux ( such as , creating symlinks (ln -s), editing kboot.conf, sudoing, etc)

In case you don't have the latest kernel, but already have one installed distro: gitbrew.org/~glevand/ps3/linux/linux-3/linux-3.3.3-build.tar.bz2

[Register or Login to view code]

And now for the fun part:
[Register or Login to view code]


PS: Lv0 keys are STILL encrypted, so don't complain, you have your precious bootldr there, have fun with it.

Finally, from anonymous (via pastie.org/pastes/5090091/) comes a PS3 dump bootldr how to exploit:

Must have a dex 3.55 real or made dex 3.55 ps3 also duel nand/nor installed chip base. In a 3.55 dex console, prepare a lv0.self with the metadata exploit. reboot. lv0 will hang since lv0.self will not run properly. bootldr will send info to lv0 before it hangs, after it decrypts it, running dex with certain switches set up like boot in dev mode Will allow this hang dump of bootldr to be saved to the local store.

But, essentially you will have a bricked ps3 so recovery of the local store wont happen. This is where the duel nand/nor comes in handy and allows you to recover from this and replace your messed up lv0.self with the original to boot up and recover the local store dump and the decrypted bootldr. This will allow the keys to bootldr these keys cannot be changed with any update.

We can then exploit lv0. The exploit of bootldr/lv0 will allow the ability to change the way private keys are made or give us the ability to reset up the private key fail and resign packages with any new firmwares.

This although is just a "well tested Theory" of course.


PS3 Metldr / Per Console Key0 Update, LV0 Bootloader Decrypted?

PS3 Metldr / Per Console Key0 Update, LV0 Bootloader Decrypted?

PS3 Metldr / Per Console Key0 Update, LV0 Bootloader Decrypted?

Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter, Facebook and drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene and PlayStation 4 scene updates and fresh homebrew PS3 Downloads. Enjoy!


  • Sponsored Links




#151 - medi01 - 180w ago
medi01's Avatar
Quote Originally Posted by snoekie]Decrypting code was never a problem, because you need the public keys to do that (which are in the firmware).[/QUOTE]

Orly? Go get PUBLIC lv0 keys pretty please.

Quote Originally Posted by snoekie
Having 3.60 or 3.73 public keys won't help you, unless you have a CFW that will unsigned or mal-signed code.

BS. Did we need new firmware to run Uncharted 3? Nope. Guess what, JUST DECRYPTING EBOOT was enough. All we need are the keys to decrypt eboots. Since SDK didn't change, all games will still work. No need of custom FW at all.

[QUOTE=404
View Post
...but trust me breakself is real....

How do you know? Why didn't M... tell us the hash of the keys as undeniable proof, how does decrypting unknown file prove it?

#150 - snoekie - 180w ago
snoekie's Avatar
It is all about breaking the chain of trust. You need to trick your PS3 to run your code at a sufficient low level. Just as the glitch hack on the XBOX, you can then manipulate the signature comparison (which is a memcmp) to always return true. Decrypting code was never a problem, because you need the public keys to do that (which are in the firmware). It's the private keys that made Firmwares up to 3.55 so interesting. By obtaining the private keys (which were obtainable by the fail of sony) we can make packages that run on OFW.

Having 3.60 or 3.73 public keys won't help you, unless you have a CFW that will unsigned or mal-signed code. Obtaining the 3.60 public keys shouldn't be hard, since they are public.

What I am missing in all of these discussions about keys is the mention whether they are public or private keys. This is a big difference.

#149 - 404 - 180w ago
404's Avatar
Isconkia does your ps3 have the private key, no. Can your ps3 decrypt lv0, yes. Figure it out.... Also anyone could write that, but trust me breakself is real.... Your ps3 has the pub key....

#148 - iscnokia - 180w ago
iscnokia's Avatar
hmmm, how the heck he did it if you need to know necessarily the private key (now not being poorly randomized like failover found) and that only Sony knows. I understand that PS3 console uses several levels of encryption and in order to unencrypt it you must have or know the private key... and there's no way to have it.

Also, that phony DOS windows showing that output is nothing that any program running what you want so I could also write a C program printing:

printf ("I have a 3.60+ CFW \n");

#147 - Natepig - 180w ago
Natepig's Avatar
Its said that if you are working on something and get stuck, if you contact him he is known to be quite helpful.

#146 - fatboyj - 180w ago
fatboyj's Avatar
Agreed, the guy has talent at coding and winding so many people up.

But seriously, if I was the most talented enlargement doctor that could make anyone bigger, and decided to keep it to myself and practice this great talent only on my hamster, wouldn't there be an outcry? I bet Math would be first to post and be the most vocal for my services.

#145 - tulla2010 - 180w ago
tulla2010's Avatar
look we should stop whining about math because, a: he wont release anything, b:all the whining will just make him less likely to help & c: you just wind yourselves up in the process.

There are other talented people out there who can piece the jigsaw together & i wouldn't be surprised when someone does figure it all out that math will be more forthcoming with help, after all he wants others to do the work that he has done.

Now don't get me wrong math has a weird way of going about things & has an uncanny way of getting everyone backs up, but i think its just his way of getting others motivated to crack this.

#144 - Prince Valiant - 180w ago
Prince Valiant's Avatar
Probably because he's a prick about anything new. As soon as something pops up, he's there to insult people, claim it as his own, or just be rude.

I own a second PS3 so I can play new games; it doesn't mean I don't want to cheat or play from the disc on my modded console.

#143 - p0tsm0ke - 180w ago
p0tsm0ke's Avatar
thanks for the info, the scene will love this.

#142 - DemonoidMaster - 180w ago
DemonoidMaster's Avatar
Yep, he did ... and him coming back just to brag is annoying as hell. Why come back just to brag and show off a freaking 3.73 Lv0 decrypt.. MATH DOESN'T DESERVE TO BE THAT SMART.

I just wish he'd stop trying to e-fame his rear off and release all the info and files...