Shouldn't be much of a difference between Un-Install Hax script and running the official updater¹ (which probably considers FIRM0 and FIRM1 as outdated and/or corrupted while B9S is installed) without protection.Yes, that does ring a bell. I can't recall the specific details, but I'm pretty sure that's a bad idea. There have definitely been some very heated threads about it in the past.
If it was that easy to cleanly remove CFW, don't you think that would be in the Guide?
We have that one: https://gbatemp.net/threads/where-exactly-did-my-homebrew-go.613318/ → ()
And another one… by the same person: https://gbatemp.net/threads/hey-so-im-dumb.618907/ →()
Count me as well: I also tested it. (Yes, big "" for me as well for torturing my poor testing O3DSXL): The updater does "repair" the FIRM partitions when updating without CFW protection.
When The Guide warns of unintended consequences, they probably mean early/surprising overwriting of B9S, before all tests are finished. The main test is already passed at this point – leaves only non-fatal consequences (crashing System Settings, missing keyboard…)
Uninstall CFW page is very long, and even includes Format System Memory. They make double and triple sure there is no non-legitimate content left before actually running the uninstall script. And this is surely the way to go for anybody dead set on removing CFW.
The instructions are well-tested and deviating from it is an unneeded risk.
====
Again: Normally I don't react on those question anymore (I wasted countless hours, but stopped caring at some point). Usually it is one of those two:
- "Want to sell the console!" (and conceal previous modding – yeah nice and honest move)
- "[…] is not working and I want to start from scratch!" (this probably comes from Android phones, where "Back to stock and start from scratch!" seems to be standard and sensible/working procedure)
_____________________
¹ Concerning the FIRM partitions. Custom content such as Luma3DS boot.firm on CTRNAND probably aren't removed (I didn't check this).
On the other side: Even having the script delete custom files, this does in no way remove evidence that a console has been hacked before.
Last edited by KleinesSinchen,