The concept i think of is so simple but i think it will cost memory/time
the idea is :
- Have the patch file to only change isoldr & spu_pkg_rvk_verifier in coreOS so to allow modified PUP installation (i didn't saw the patches change since a long time, i remember the same patch have been applied for like last 6 to 10 updates lol).
- Auto Dump Flash or (the Two files i mention before) (backup is saved either HDD or USB)
- Patch Flash the files
- Auto Dump the two files again to compare
- if the hash of file is identical to the one set in exploit var it will show green message telling you can reboot
- if hash diffrent from original & different from hash of patched file ,restore original files
If you only change isoldr & spu_pkg_rvk_verifier it will brick due to syscon hash check.
I actually don't mind implementing all of it, or at least most of it (minus Super Slim related things). Sounds like a good exercise for C/C++.
Edit:
I also found some repo of tools included in MFW Builder: https://github.com/manusan/ps3tools
That cosunpkg stuff looks super easy, maybe it could be used to unpack and inspect the CoreOS file before it is written, at least to make sure that noFSM related files are modified. And also that the files inside aren't corrupted in any obvious way.
I'm mostly referring to my other project right now, HEN Flash Patcher.
Well if it's to check the integrity of the noFSM patch data, hash calculation is the easiest way. No need to mess with each files and the file table.