[GraVoX959]

Originally Posted by naddel81 we already got 4.3 as the new base. so please lord: What are those keys giving us really???

As I said before, this allows people like Rogero improve their CFW, add some of the patches that Rebug have added.
It allows for everything to be decrypted and people to study a new, relatively unknown FW.

[Simonbuck]

Shouldn't this be front page News ?

[ocam]

Originally Posted by GraVoX959 As I said before, this allows people like Rogero improve their CFW, add some of the patches that Rebug have added. It allows for everything to be decrypted and people to study a new, relatively unknown FW.

do you happen to know if someone is working on lv0.2?

[GraVoX959]

@ocam I know its been briefly looked at.
Its very small and seems to be a header that just points somewhere else.

Probably been looked at more but I havent been overly active lately and havent kept up with everything.

[Simonbuck]

Originally Posted by GraVoX959 @ocam I know its been briefly looked at. Its very small and seems to be a header that just points somewhere else. Probably been looked at more but I havent been sexualy active lately and cant keet it up.

Fixed it for ya

[axujen]

Originally Posted by toolz Lv02 is a long way off from being cracked. If you can downgrade then do so.

if you have lv0.2 then you can't downgrade....
Edit: on a side note weren't the lv0 keys used to decrypt everything? or was it just used to decrypt ofw pups? if so then what exactly does this thing do other than allow us to "decrypt everything"?

[zadow28]

Originally Posted by ocam do you happen to know if someone is working on lv0.2?

well the lv0.2 is simply the header(metadata) for the lv0

So if you cut the header of the normal lv0 and replace it with the lv0.2.

[*] SCE Header:
 Magic           0x53434500 [OK]
 Version         0x00000002
 Key Revision    0x0000
 Header Type     [SELF]
 Metadata Offset 0x000001E0
 Header Length   0x0000000000000500
 Data Length     0x00000000000E6EE0
 Auth-ID   [lv0]
 Vendor-ID [hv]
 SELF-Type [lv0]
 Version   04.25

So conclusion.

You need to dump the bootloader 2.
to get the keys for the lv0 version 2 its the same files just different headers.
aka keys.

[ocam]

Originally Posted by GraVoX959 @ocam I know its been briefly looked at. Its very small and seems to be a header that just points somewhere else. Probably been looked at more but I havent been overly active lately and havent kept up with everything.

thanx...

/10

[axujen]

Originally Posted by zadow28 well the lv0.2 is simply the header(metadata) for the lv0 So if you cut the header of the normal lv0 and replace it with the lv0.2. [*] SCE Header: Magic 0x53434500 [OK] Version 0x00000002 Key Revision 0x0000 Header Type [SELF] Metadata Offset 0x000001E0 Header Length 0x0000000000000500 Data Length 0x00000000000E6EE0 Auth-ID [lv0] Vendor-ID [hv] SELF-Type [lv0] Version 04.25 So conclusion. You need to dump the bootloader 2. to get the keys for the lv0 version 2 its the same files just different headers. aka keys.

So whats stopping people now is the fact that they cant dump their bootloader? (incompatible flashers?)

[ocam]

Originally Posted by zadow28 well the lv0.2 is simply the header(metadata) for the lv0 So if you cut the header of the normal lv0 and replace it with the lv0.2. [*] SCE Header: Magic 0x53434500 [OK] Version 0x00000002 Key Revision 0x0000 Header Type [SELF] Metadata Offset 0x000001E0 Header Length 0x0000000000000500 Data Length 0x00000000000E6EE0 Auth-ID [lv0] Vendor-ID [hv] SELF-Type [lv0] Version 04.25 So conclusion. You need to dump the bootloader 2. to get the keys for the lv0 version 2 its the same files just different headers. aka keys.

kool, thanks for the info...

so what are the chances to get the bootldr.2 keys?