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

March 28, 2011 // 6:57 pm - Today PS3 hacker Mathieulh has tweeted some new details on dumping LV0 from PlayStation 3 3.60 Firmware and obtaining the new keys, followed by Ps3WeOwnYoU claiming he has already reproduced it to confirm it works.

Below are all the tweets, as follows:

Mathieulh's Tweets:

  • xShadow125 You can update from your own pup only from 3.55 or lower, unless you have an exploit.
  • xShadow125 Of course that should be fixed in upcoming lv0 revisions anyway (By moving the ldrs to the top of lv0)
  • xShadow125 You run the 3.60 lv0, then you switch the nor, and pull the cell reset line, and you dump the extra KBs where the loaders are.
  • xShadow125 Basically you have a nor with 3.55 (or lower) lv0 and your own small lv1 code that does the dump, and 3.60 lv0 on the other.
  • xShadow125 You wont get all of lv0 but the part with the loaders shouldn’t be overwritten.
  • xShadow125 You can actually get all the 3.60 keys/loaders without knowing lv0 keys by dumping lv0 from ram with dual nor and signed lv1.
  • To those planning on building a 3.56+ pup for whatever reason, the files attributes changed, the group and user ids for the files as well.
  • The new 3.56+ values for tarballs are the following: owner_id, "0000764" group_id, "0000764" owner, "tetsu" group, "tetsu" ustar, "ustar"
  • You can use fix_tar to use those new values. Use with caution.
  • By comparison, those are the pre-3.56 values. owner_id, "0001752" group_id, "0001274" owner, "pup_tool" group, "psnes" ustar, "ustar"
  • Ps3WeOwnYoU You need to either decrypt or dump lv0, then you can get the encrypted loaders and decrypt them with the metldr key. Good luck.

So, to decrypt this LV0 thing, we need to get to know it better. In the latest blog post by rms, he has explained briefly what LV0 is in the console’s security.

Anyway, let’s really discuss something PS3 instead of my PC xD, let’s start with Lv0, the most unknown level of the PS3. Lv0 initializes PS3 base hardware such as PowerPC/PPU portion of Cell/BE, SPU isolation for asecure_loader, and gelic ethernet/WLAN device. Lv0 also proudly proclaims itself as the "Cell OS Bootloader".

In older firmwares, 0.80-ish to 3.56, Lv0 initialized SPU isolation on one of the SPUs, then it loaded and decrypted asecure_loader. Asecure_loader or metldr then decrypts the isolated loader, in this case, lv1ldr, then lv1ldr decrypts lv1.self. In 3.60 this changed. Lv0 now has all of the loaders integrated into it as one large fat binary.

All the keys one needs such as Public ECDSA key/AES CBC key and Initialization Vector and ECDSA curve type are in there. Just go ahead and grab them if you can get the ldrs out of the binary.

So, unless you can decrypt Lv0, no 3.60 "CFW" for you . Is there any need for it anyway?

Mathieulh also has some facts to clarify about LV0.

1. lv0 isn’t a loader it’s a ppu binary
2. Lv0 isn’t encrypted per console and can be updated with the rest of the coreos
3. Lv0 is decrypted by the bootloader, there is no such thing as a lv0ldr.
4. The bootloader keys cannot be updated/modified on EXISTING hardware
5. lv0.2 is NOT a binary, it’s a new metadata for lv0 which is to be decrypted and verified by a new bootloader (which is to be available on future ps3s), it is NOT used by the current bootloader (and thus in current playstation 3 consoles)

But wait, messing with this thing could lead to the YLOD tragedy, unless you have those expensive NOR flasher you might want to proceed, and that’s according to rms again.

Lv0 also does some more interesting stuff such as SPU mailbox handling, and eEID integrity checks. Lv0 also used to check for QA flag and proper token, that is now in a spu isolated self in Core OS. Now, if you did tamper with eEID, lv0 will panic out, and your console will then "YLOD", and you’d need a flasher for your PS3 to recover.

Finally, from rms on lv0: Lv0 initializes PS3 base hardware such as PowerPC/PPU portion of Cell/BE, SPU isolation for asecure_loader, and gelic ethernet/WLAN device. Lv0 also proudly proclaims itself as the "Cell OS Bootloader". In older firmwares, 0.80-ish to 3.56, Lv0 initialized SPU isolation on one of the SPUs, then it loaded and decrypted asecure_loader.

Asecure_loader or metldr then decrypts the isolated loader, in this case, lv1ldr, then lv1ldr decrypts lv1.self. In 3.60 this changed. Lv0 now has all of the loaders integrated into it as one large fat binary. All the keys one needs such as Public ECDSA key/AES CBC key and Initialization Vector and ECDSA curve type are in there. Just go ahead and grab them if you can get the ldrs out of the binary.

So, unless you can decrypt Lv0, no 3.60 "CFW" for you. Is there any need for it anyway?

Lv0 also does some more interesting stuff such as SPU mailbox handling, and eEID integrity checks. Lv0 also used to check for QA flag and proper token, that is now in a spu isolated self in Core OS. Now, if you did tamper with eEID, lv0 will panic out, and your console will then "YLOD", and you’d need a flasher for your PS3 to recover.


PS3 Hacker Mathieulh on 3.60 Firmware LV0 Dump Exploit & Keys

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.



#361 - Bartholomy - February 3, 2012 // 1:17 am
Bartholomy's Avatar
I know what you do, and your spirit, bro. The problem is not your point of view, or mine. Sony is japanese. Japanese looks ps3 hackers/devs as trash who deserve to be digged, deep. Doesn't matter if your work will lead to double Sony's income. Doesn't matter if your work will stop piracy.

Doesn't matter if your work will stop an abuse of some teams. For Sony's eyes, you're using THEIR product and THEIR software (every level of them) and for this reasons, if you release something, you will be sued and called to a particular tribunal, where a funny judge will take care of ruin your life worst than if you was a drug pusher. Sony don't say thanks, neither if you save the CEO's life. You touched THEIR product, you will pay.

It's the truth, bro. And you know i'm right.

#360 - ValoX - February 3, 2012 // 1:15 am
ValoX's Avatar
Thanks for the news.

#359 - cfwprophet - February 3, 2012 // 1:05 am
cfwprophet's Avatar
The only thing what i can say: If sony want to sue some one of us im sure they dono need the help of this so called dev god's. From my point of view they would have more reasons to sue DRM teams then normal scene guys like us.

We don't sell sonys games hacked and pressed on a debug disk with there debug key. We dono use and sell a dongle with sonys drm stuff to prevent our work. We're also not releated to any release of sonys keys or what ever. We using tools, code and stuff others have written and released and this also includes work of this dev's. So what they want to do with us ?

We're not against sony, we're not against the scene, we're not against other dev's. We're against team's and dev's using sonys sys to make money with it. We're against dev's preventing those teams.

So we're not the BAD guys which upset sony. On special case WE help sony to stop those guys making money with sonys work. If you ask me sony have more reasons to sue those both teams and every dev of the scene involved into it then to sue guys like me or others.

And also we have not found something new that we push now. The theory of our ongoing work is based on them. They put the con into debugger mode to be able to let you play new games and sell this for a lot of money.

If those teams never started to sell there dongles we wouldn't never started to do the work we now do. So if some one of thoes dev's want to sue some one they should start and sue themself.

#358 - kira30 - February 3, 2012 // 12:55 am
kira30's Avatar
exactly, they need to relax a little, like you said "it's only video games".

#357 - Bartholomy - February 3, 2012 // 12:08 am
Bartholomy's Avatar
You don't understand those devs, elser1, because:

A You're not a loser nerd who need youpo for take a look to a girl
B You lost somewhere your teenager brain, the same one who make you feel a god when you complete a game on HARD MODE (I felt to be a god when i finally got my Bachelor, big difference)
C As much you're a dev, willing to help, elite group will start to threat you, with something like : "well done, you found a great exploit" "Hehe thanks. I think i'll publish it on ps3news and other major forums" "No, you don't understand how things works. You will keep it for yourself, thanks for share" "I beg your pardon? I'll release it in an hour"

"You still don't understand. We will send an email with your name and location to Sony and your life will be gone, if you try. Beware, no joke. You will do like us. Enjoy your work, play online with every game. Share it with your faithful friends. But again, if something goes leaked, we will be the first to help Sony to sue ya".

This is the real story. Kinda crap, right?

Thanks cfwprophet and nabnab, to ignore them.

#356 - kreus - February 2, 2012 // 8:46 pm
kreus's Avatar
oh I thought they found a way to decrypt the eboot and unsign. That way it would be possible to reverse engineer. Then all hope is lost hehe

Congrats Cfwprophet and nabnab, I know youre trying hard to make a better place for the scene.

#355 - cfwprophet - February 2, 2012 // 8:42 pm
cfwprophet's Avatar
We know how it works and have explained a lot of times. The dongle puts your con into debugger mode. In this special mode you can debug games and thats what they do. They use the system embended debugger to let you play those games.

They take the official game selfs from disk and dump out the elf via the sdk, then re-encrypt them as debug selfs and on a special way thats it.

But it takes a bit more work to get this for free for every one done. The keys have nothing to do with it. They use drm just to hide and to be able to milk us all a bit longer till a free version is done.

#354 - kreus - February 2, 2012 // 8:41 pm
kreus's Avatar
And if someone finds how it works, it should be possible of doing the same thing comparing the eboots without the keys with the ones with keys.

In cryptography, a timing attack is a side channel attack in which the attacker attempts to compromise a cryptosystem by analyzing the time taken to execute cryptographic algorithms. Every logical operation in a computer takes time to execute, and the time can differ based on the input; with precise measurements of the time for each operation, an attacker can work backwards to the input.

#353 - elser1 - February 2, 2012 // 8:32 pm
elser1's Avatar
its a shame they all think its such a big deal.. its only video games not cure for cancer.. sure it would be great and mean a lot to alot of us but in reality its not that big of a deal, but the way they act gives them a feeling of power i guess.. i don't really understand such behavior, myself i get most enjoyment out of trying to help others..

i wish i bought an xbox when i had the spare cash.. but i love psn too much so ill stick to my ps3 and grin and bare it.. LOL

#352 - kreus - February 2, 2012 // 8:30 pm
kreus's Avatar
sorry if it sounds stupid, but we seem to already have the equation ecds uses, cant we extrapolate the variables using multiples ps3 on ofw 4.00 and HFW 4.00?

For what i saw the ECDS encryption only works fine if there is only one or a few machines with the same key. With multiple ps3's its possible to extrapolate, and the higher the number the easier it is.