[Cheesethief]

I think I need a new pair of pants.

If this leads to CECH-3000+ getting hacked, I will need two new pairs.

EDIT: Only 8 pages... I suggest renaming this: "Play pirated games on 4.25" for more views.

I don't think people understand the gravity of this piece of news.

[r07f1]

@Cheesethief yup and since there are lots of pirates dual booting maybe they can be of some help... lol

[Cheesethief]

Originally Posted by r07f1 @Cheesethief yup and since there are lots of pirates dual booting maybe they can be of some help... lol

I forgot, are the Bootldr keys per console keys?

[r07f1]

http://ps3devwiki.com/wiki/Boot_Order
Bootloader = yes
lv0 = no

[An_FiS]

Yes bootldr is per console just like metldr... But if you can get a decrypted version of bootldr you may be able to figure how to break the chain of trust at the top... lv0 is static which is changeable from firmware to firmware... If you break bootldr at 3.55 i believe you would get the same type of keys from it as you would metldr.. so you could resign whatever you want without lv0 you could completely make a firmware that could say skip lv0 or create a bootldr that dumps lv0 the possibilities are endless... If you pwn bootldr you wouldnt need private keys ever again, basically....


bootldr sets up primary hardware and loads lv0

the hardware or bootldr and metldr verify the integrity of an application and decides whether to allow it to be trusted to run Because the hardware controls all of these steps, the verification of the application's integrity cannot be skipped or manipulated so you couldnt update bootldr sorry. But you can still use it to exploit lv0

[Cheesethief]

Originally Posted by r07f1 http://ps3devwiki.com/wiki/Boot_Order Bootloader = yes lv0 = no

Thought so.

Well, hopefully I can run some homebrews on my 3k soon.

[An_FiS]

Originally Posted by Cheesethief Thought so. Well, hopefully I can run some homebrews on my 3k soon.

with new hardware revisions bootldr and metldr, is updated in factory... we would have to totally compromise a firmware at 4.20 level or have the ability to load a 4.25 cfw on top of a ofw... If we could get this exploit to work then we should be able to make a 4.25+ cfw on an old machine and you could install it on a new machine....

[Simonbuck]

See The "Iluminate" are in again, just passing enough info to feed the fish.

Master, ffs just put everyone out of there misery and tell them when the CFW will be (leaked)

[Cheesethief]

Originally Posted by An_FiS with new hardware revisions bootldr and metldr, is updated in factory... we would have to totally compromise a firmware at 4.20 level or have the ability to load a 4.25 cfw on top of a ofw... If we could get this exploit to work then we should be able to make a 4.25+ cfw on an old machine and you could install it on a new machine....

So bootldr on the 3k is different than the one on a hackable 2500? Either way, a you can use the older bootldr consoles to make a CFW that works on the newer consoles I am sure.

[ryant001]

Originally Posted by Simonbuck See The "Iluminate" are in again, just passing enough info to feed the fish. Master, ffs just put everyone out of there misery and tell them when the CFW will be (leaked)

Imho i would still prefer the complete method to get the bootldr keys/decrypted bootldr to a useless cfw any day but yeah, there are too many people who knows what's going on behind the scenes and are having fun teasing us and telling us that we need to have patience and wait(not specified how much we have to wait, days/weeks/months?)