Hiya, everyone;
While it might be a bit harder to notice on a forum like this where situations tend to get mixed around, I'm here to talk about a major issue with SafeSysUpdater. I'm a member of the #3dshacks IRC on Rizon. We generally recommend SysUpdater over SafeSysUpdater because of one
major issue with SafeSysUpdater; the browser generally fails to function at all after a partial downgrade. This is very consistent (with only one or two cases I can think of where this wasn't the case), and as a result, it destroys a very convenient entrypoint from being usable, making you resort to a game exploit like Cubic Ninja. Obviously, this is a very bad thing. SysUpdater doesn't have this issue, which is why we end up recommending it over SafeSysUpdater.
So what can we do to fix this? First of all, we need to debug the issue. We need to figure out EXACTLY where SafeSysUpdater failed the update process when it partialed that causes this issue. To do that, we need one of two things; A. a video of the partial downgrade that shows what CIA the downgrade failed on, or B. A log of the currently installed CIAs and it's versions (which can be obtained through SafeSysUpdater itself by pressing X instead of starting the downgrade). This information will allow us to approximate where the downgrade failed and what we have to do to fix it, making SafeSysUpdater 'safe' enough to recommend usage again. If you want to help out with this, I implore you to read through
this paste and get in contact with me.
Thanks for taking the time to read this.