Discussion in 'PS3 Jailbreak CFW and PS3HEN' started by haxxxen, May 15, 2015.
Typo in the keys...
Well spotted @littlebalup...
yes it seems it's the case since 4.46 for the lv0. Just checked the keys I have in PUAD and it's the same...
I'm too lazy to check the other keys today. And I'd like to have a confirmation from specialists before to push a request to the git.
@habib , @Joonie , @Alexander, @zecoxao ...
Ugg.. I don't know why, mine has it as 0x30 since (4.46) and it still worked for me if my memory serves right.. but @habib can explain it better for you
According to the wiki, the curve type of lv0ldr is 0x33 although the wiki value is taken from a pre 4.xx fw...
But as it's also the value used successfully by scetool in the keys file for 4.46+ lv0ldr as littlebalup mentioned, it's likely that the information is correct for 4.46+ fw.
This is not going to add much info, but i been taking a look at the history of changes of the wiki page just to see if at some point has been a typo in wiki with that 0x33
But no typos in wiki with it, has been always 0x33 since 2013 or so
strange story... it's crazy it has not been identified since four years.
If somebody can reproduce the experience it would be nice. I hope I'm not crazy myself... maybe drunk but not crazy...
Hmm... There must be an explanation though...
It would be truly amazing if Joonie (and others who used the keys in multiple files format) used a wrong curve type for lv0 to compile cfw for years without consequences...
Which tool are you using again to decrypt/encrypt lv0?
Did you say that there are other keys with the same kind of discrepancies?
Yeah, for lv1 at least. But I very quickly looked. To be confirmed.
I only use SCEtool for building REBUG on these days, but before I used to use unself, self_rebuidler and iso_rebuilder
And @littlebalup, were your tests made on 4.81 files only?
Do you get the same results with 4.4x/4.6x files?
Yes, 4.81 only.
I also use LV0tool + SCEtool and I have no problems.
I had added time to do it in the dev area, my lv0 decrypter. If I do not mistake it's 0x33 the curve type.
I guess probably @littlebalup is right about 0x33 as @sandungas also mentioned it about that wiki stuff.
I maybe just mistaken, but I do remember I used to have hard time dealing with this unself/iso_rebuilder stuff when I just started messing with CFW. At the end I was able to fix the issue without knowing that was an issue with ctype [it could have been or not still mystery]
Now that the lv0 curves type set to 0x33, I done few more tests using self_rebuilder vs iso
So, about using self_rebuilder to resign lv0, I get a GLOD on boot. All run fine using iso_rebuilder for the three lv0, isoldr and spu_pkg_rvk_verifier module.
Looking at the wiki (http://www.psdevwiki.com/ps3/Making_Isolated_SPU_Modules_and_Loaders#ps3tools), Glevand said:
So, "isolated SPU modules" includes the spu_pkg_rvk_verifier module of course and "loaders" seems to include lv0 as well.
I'll try to make a test with anther 4.46+ firmware version this week end.
P.S: Can I say I made my first CFW? The "littlebalup 4.81 DB"... lol
I see, I must have been mistaken, because last time I used those tools was like almost 3 years ago. So Iso-rebuilder works for all modules inside CoreOS
If you have beyond2compare, rcoediting tool, and DEX OFWs, you can now probably make REX CFW as well.
oh no. I'm too lazy to even try to do it... even a CEX.
curve type will remain/is same for all firmwares lv0
its related to ecdsa signature
invalid signature will brick and that goes for lv0 and loaders OR if you dont patch them, then ecdsa of lv2/lv1/appldr/isoldr
and yes loaders do include lv0, easy way to check this is compare size of elf and size of self, the difference should be around 1kb only(926 vs 925 for lv0)
for those who have doubts about curve type, just dump your own lv0ldr and look inside... for memes
I don't doubt we've been using 0x33, because that's what I got for scetool's keyset
But it's weird that I had 0x30 for isorebuilder lol oh well I haven't used it since 2014
Sent from my iPhone using Tapatalk
Separate names with a comma.