(adsbygoogle = window.adsbygoogle || []).push({}); HV Debugging, PS3MFW, Graf’s Linux And Mathieulh’s Exploit

It’s a great day for developers and hackers alike, first we get to see the release of PS3MFW builder along with the sources from an0nym0us and his team. He will also release PL3 loader, an homebrew application app that first being a proof of concept and originally coded by KaKaRoTo.

UPDATE: Thanks to euss, you can now download the compiled Windows installer portable version here: ps3mfw-w32_portable.rar (4.57 MB)

Then, user has released HVDebug where everyone can now enable HV debugging from GameOS. The project is of course inspired with graf_chokolo’s immense hacks on PS3′s hypervisor that I’m sure we hear them crying constantly in the console.

Speaking of graf_chokolo, it seems that the man has now installed Gentoo on the internal hard disk of the PS3 slim. The first step forward to the HV CFW or let’s just say OtherOS++, miles better version of the old OtherOS from $ONYy which they removed last year. Angry customers dragged them to court because of their stupidity.

The man who is also currently in court battle with $ONY, geohot, is allegedly using OtherOS in some way to help him obtain the metldr. The exploit has been widely compared with the one that Mathieulh has discovered recently and fast becoming on everyone’s wanted list because of it’s ability to exploit future updates from $ONY. The thing about the hack is that, OtherOS is not actually necessary, and that’s coming from Mathieulh himself.

"I don’t know about geohot’s exploit but as far as mine is concerned, I don’t need to use otheros at all."

" If you can exploit loaders, you can patch them on the fly and remove the signature checks, on the other hand of you dump the bootloader keys, you can also calculate the private key for lv0."

"The bootloader cannot be updated, as such the bootloader keys that decrypt lv0 cannot be changed on existing consoles, thus they remain the same since 1.00"

"The metldr keys aren’t the keys that sign metldr, they are the keys that are stored within metldr’s binary."

"In fact metldr and the bootloader aren’t selfs, as such they are signed and encrypted with different algorithms than the rest of the ps3 binaries."

"I see a lot of nonesense regarding lv0 so let me clarify a few things for you:

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)"

sourceS3CRUNCH

Good news!

i am sure there never will be a cfw for 3.60 and for new versions

Inb4 3.60 cfw noobs.

Great information to clear things up :y: very useful

Nice post man this is clearing things out verry fast keep us UPDATE

Well thanks for the good news. I dont doubt someone will eventually hack 3.60 i hope
and they might release it anonymously i hope

So he's giving us hints, and still no one can get it, wtf just release the keys already

very good news hack4life finally we are coming back at sony thanks to all the devs for there hard work

Sorry for the -Rep but personaly, Id like a step by step TUT on how they did it. Some people may call that leeching but atleast then we would have the knowlage on how to JB future FW fail0verflow shown how they exploited the security but its hard to understand for people like me trying to learn.