Correct. And any modification carries the risk of unrecoverable brick. On the DSi there is zero protection against this.
The user has to be aware of this and accept this.
No access to my main computer at the moment so I can't find the links easily. There were the following cases with the result of a spontaneous brick:
- Uninstalled unlaunch without having non-legit DSiWare on SysNAND
- Simply installed unlaunch
- Seemingly normal unlaunch update
I lack the expertise to evaluate those but I came to a conclusion myself: Don't touch unlaunch without a good reason.
Install and good. The changes from v1.8 to v1.9 an v2.0 are not that important that I would risk modifying a working installation (exception: my almost busted test DSi where I – big surprise – accept the risk of loosing it forever and even changed SysNAND beyond installing unlaunch)
Bricks of this kind seem to be pretty rare (or there would be many more threads about this). Still not worth the risk.
I fully agree with
@alexander1970
Read BEFORE installing CFW on your consoles. Don't guess, don't try before understanding everything, don't do it if you don't accept the risks.
The developers do their best to make CFW suitable for the end user and as safe as possible. But nobody can guarantee that software modification of a device never intended to grant the user full rights will behave as expected. Opposed to a PC where the user has full rights (mostly up to today) by default and reinstalling the operating system is possible, intended and easy, a gaming console breaks if the OS is damaged.
This is in my opinion the
WORST reason for uninstalling custom firmware of any kind. To put it mildly: Selling a previously modified device without mentioning the modification is not a nice move.