Originally Posted by BwE
Euss harassed me about this. However, my list does cover some CFW and debug, but not everything.
But realistically, you validate when you downgrade, you downgrade when you're on OFW.
|
And I think he is right
Honestly, folks will do what they want with this code when finish, but if I can finalise it correctly, it will not be aimed to only permit anyone to just validate a NOR for future downgrade, at least I will not use it for that.
For example you can see at the moment that it displays some per console information and generic things from the dump.
As for the validation itself, again if I can have a list of MD5 per ros I would be more than happy to include this in the code and then yes I would be able to implement this 4th point.
EDIT: 0.9.6 is on github
Still a lot is to be done but even if it's not really clean or out of bug, I've uploaded what I've done recenty.
new stuff have been introduced:
Added percentage indicator
Added global status
Added Fixed of some part of the code & cleaning from an0nym0u5
Changed MD5 function, the first one was only valid if done on a full file not on inner sections.
Added report for trvk and ros' files MD5
move part of the definitons in PS3Data.h
As per the MD5 things, it's not complete but it should help to start going further on this.
You will also note that I've increased the status to 97%, but it does not mean that a dump can be considered good if you are green...
I cannot garanty that it really covers critical parts.
For example when you check some per console zone, the code can tell if the header or the size of a region is correct,then it checks if the region is full of data, BUT IT DOES NOT CHECK that the data in it are valide.
Be aware that you cannot rely 100% on this to validate your dump, remember it is aimed to help you validate but it's not able to do all the job for you.
The most important is that you can learn from this code if you want and make your own tools for what ever purpose if you like some part of this.
You will also notice that I have added some lines of MD5 sums in PS3Data.h for example:
Click here to see full text
// FW 3.41 Files
{"creserved_0" , "3.41" , "09A1D434DBD7197E7C3AF8A7C28CA38B"},
{"sdk_version" , "3.41" , "7A2595AECEDE95C9338C710CF8DBBA99"},
{"lv1ldr" , "3.41" , "C7BF42F12A3EE32E694EB9FE46E1DB51"},
{"lv2ldr" , "3.41" , "C8777688BF00F42E6C73DE336E10A25A"},
{"isoldr" , "3.41" , "54490521B6965BD0E95D93928C1B4056"},
{"appldr" , "3.41" , "CF08E9B3421E4B1AA665717C555ED670"},
{"spu_pkg_rvk_verifier.self" , "3.41" , "964A28D0F0E6AA3423A4FF1DA4598C21"},
{"spu_token_processor.self" , "3.41" , "7D71C9C119989446766442E8127BA0CB"},
{"spu_utoken_processor.self" , "3.41" , "92913EAD973B8AA24BFF4F38FE66927E"},
{"sc_iso.self" , "3.41" , "7E9938FF024C809DE3CC950B61E01F6B"},
{"aim_spu_module.self" , "3.41" , "8C3DF66C7BCFCB291221884EE46CB351"},
{"spp_verifier.self" , "3.41" , "A60518DDF46B904E7F8B4ADC96F60342"},
{"mc_iso_spu_module.self" , "3.41" , "07DDFE013304965BF7EB63D9AC5BD0C2"},
{"me_iso_spu_module.self" , "3.41" , "A237F20A0491149B1C0890B0FCE8E0CE"},
{"sv_iso_spu_module.self" , "3.41" , "7D20C0D5F382EEB31E6B830EA1ED4B8F"},
{"sb_iso_spu_module.self" , "3.41" , "5A219A19D772E26F41A86BCB8449093E"},
{"default.spp" , "3.41" , "4E78EA91BE73C71012930C4144B50CC1"},
{"lv1.self" , "3.41" , "200A67508DF9C6B2F47A7A93FF2160CA"},
{"lv0" , "3.41" , "C0C71AE21AEC6A6116464B8A7DF4D534"},
{"lv2_kernel.self" , "3.41" , "9DBFDC3B026622E83398554B783E1CEC"},
{"eurus_fw.bin" , "3.41" , "B5F54D9A11D1EAE71F35B5907C6B9D3A"},
{"emer_init.self" , "3.41" , "D5F6040AAB1B27E29461E847CFFDA08E"},
{"hdd_copy.self" , "3.41" , "F1142B43BCD76C0EC9A0CBF1BE8BE407"},
This list is of course not complete but it's not validated either, so I would appreciate anyone willing to report any additional sums, and prompt me those which are wrong.
You can use both codes from my second repo
here to generate your own list of sums.
Unfortunately for those who want to know more about what it does and what is the exact soucre of information, I did not fill in enough comments...