[dwood18]

yall think since 4.21-25 lv0s the same 4.3 will be?

[dadi4168]

I'm staying on kmeaw till things calm down and there is some testing done. I'll grab the keys and sign a few files while I'm waiting...

Sent from my MB870 using Tapatalk 2

[cfwprpht]

Originally Posted by JustThatDude They are static but they can still be changed its harder to do it though but they can still be changed.

No to time it looks not that sony can update lv0 static key. Same goes for bootldr, metldr and the derivated Per Console Key.

It's like that:

Syscon send's ConfigRing to Cell >> Cell boot up with this ConfigRing >> Cell use ConfigRing to decrypt bootloader >> bootloader use ConfigRing to decrypt LV0 and run it >> yada yada yada

So Sony can't change your PCK which even isn't a key in first front. It's a value that will be used to calculate your PCK. After calculating your PCK the console decrypt bootloader and so on.

So you see there are a few thing's that sony only can change with a new hardware revision and not truth a update. This means for now LV0 static keys CAN NOT be changed afterwards. Same goes for PCK, Bootloader, Metloader.

The thing with decrypted bootloader:
You guys forget that we have PCK_0, PCK_1 and so on. Well the so called EID_Master-Key is then our PCK_0 but the mess with that is....Bootloader is not encrypted with PCK_0.
It is encrypted with the first derivation of this value that will be used to calculate your PCK and that's Per Console Factory Key.

Per Console Factory Key is then used to derivate PCK_0.

Till now there is no way to dump or get hands on the Per Console Factory Key.

[tjhooker73]

Originally Posted by cfwprpht No to time it looks not that sony can update lv0 static key. Same goes for bootldr, metldr and the derivated Per Console Key. It's like that: Syscon send's ConfigRing to Cell >> Cell boot up with this ConfigRing >> Cell use ConfigRing to decrypt bootloader >> bootloader use ConfigRing to decrypt LV0 and run it >> yada yada yada So Sony can't change your PCK which even isn't a key in first front. It's a value that will be used to calculate your PCK. After calculating your PCK the console decrypt bootloader and so on. So you see there are a few thing's that sony only can change with a new hardware revision and not truth a update. This means for now LV0 static keys CAN NOT be changed afterwards. Same goes for PCK, Bootloader, Metloader. The thing with decrypted bootloader: You guys forget that we have PCK_0, PCK_1 and so on. Well the so called EID_Master-Key is then our PCK_0 but the mess with that is....Bootloader is not encrypted with PCK_0. It is encrypted with the first derivation of this value that will be used to calculate your PCK and that's Per Console Factory Key. Per Console Factory Key is then used to derivate PCK_0. Till now there is no way to dump or get hands on the Per Console Factory Key.

Bootldr Cannot be Changed much with an Update.
metldr Gets changed all the time, Like with 3.41 and 3.55
LVL0 Can be changed along with LVL1 - Metldr and anything else.

[cfwprpht]

metldr can NOT be changed !! You want proof ?? Do a checksum now then update to higher fw and use your flasher to do a dump and do a checksum on metldr again. You will see it's the same checksum. So how could something be changed and still have the same checksum ?? Do your homework Dude. Metldr can only be changed from factory. There for new cons and cons with 3.56 Fw from factory have a metldr_v2. this is happen in factory just like with bootldr NOT with a update.

And i never sayed that LV0 can't be changed i sayed LV0 static keys can not be changed.

No to time it looks not that sony can update lv0 static key.

If oyur not able to read don't piss me on. And beter do your homework twice before stating **** like sony can update metldr all the time. You have no clue what you talking.

[Primulas]

i knew there was a reason for me holding out for 2 freaking years with 3.55. I will be glad to actually be able to purchase games again. I may not buy them all, but i sure as hell will buy more then i have in the last 2 years.

Regardless of intent thanks to all the devs that do what they do.

-Prim

[Cheesethief]

@cfwprpht you used a double negative. Learn to write before you tell someone to learn to read

Sent from my toaster using Tapatalk 2

[tjhooker73]

Originally Posted by cfwprpht metldr can NOT be changed !! You want proof ?? Do a checksum now then update to higher fw and use your flasher to do a dump and do a checksum on metldr again. You will see it's the same checksum. So how could something be changed and still have the same checksum ?? Do your homework Dude. Metldr can only be changed from factory. There for new cons and cons with 3.56 Fw from factory have a metldr_v2. this is happen in factory just like with bootldr NOT with a update. And i never sayed that LV0 can't be changed i sayed LV0 static keys can not be changed. If oyur not able to read don't piss me on. And beter do your homework twice before stating **** like sony can update metldr all the time. You have no clue what you talking.

You make me Want to Slam my Face through a wall. Stop Being a Math.
Old:

Click here to see full text

New:

Click here to see full text

Cannot find the Image of what can and cannot be Updated/TL;Didn't look.

[kriz2391]

So I have a slim ps3 that came with kmeaw 3.55 CFW. Can I now play dead or alive 5?

[JustThatDude]

Originally Posted by cfwprpht No to time it looks not that sony can update lv0 static key. Same goes for bootldr, metldr and the derivated Per Console Key. It's like that: Syscon send's ConfigRing to Cell >> Cell boot up with this ConfigRing >> Cell use ConfigRing to decrypt bootloader >> bootloader use ConfigRing to decrypt LV0 and run it >> yada yada yada So Sony can't change your PCK which even isn't a key in first front. It's a value that will be used to calculate your PCK. After calculating your PCK the console decrypt bootloader and so on. So you see there are a few thing's that sony only can change with a new hardware revision and not truth a update. This means for now LV0 static keys CAN NOT be changed afterwards. Same goes for PCK, Bootloader, Metloader. The thing with decrypted bootloader: You guys forget that we have PCK_0, PCK_1 and so on. Well the so called EID_Master-Key is then our PCK_0 but the mess with that is....Bootloader is not encrypted with PCK_0. It is encrypted with the first derivation of this value that will be used to calculate your PCK and that's Per Console Factory Key. Per Console Factory Key is then used to derivate PCK_0. Till now there is no way to dump or get hands on the Per Console Factory Key.

Lol per console keys just seem like a huge mess. No wonder why the never moved on with trying to decrypt the bootloader. Also @tjhooker73 its LV0 not LVL0