Unistalling led to dm-verity file corruption

Steps To Reproduce

1. Grant the app root privileges
2. Enable the filter
3. Unistall the app
4. Enable system blue light filter
5. Reboot
6. Your device is now bricked (dm-verity device corrupted force dump kernel_restart)

Additional description/details (optional)
Add any other context about the problem here.

It may be a very peculiar situation but, really, who might expected such a thing?!
I had to wipe all my data and reinstall a clean version of Android.

Maybe a warning could have been useful.

Device info:

• Red Moon version (under Red Moon settings): 8.1
• Android version (under Settings > About device): 12.1
• Device: OnePlus 8T

[smichel17]

I'm sorry to hear that. It's quite also odd— as far as I know, root mode only changes parts of the system as it's running; it does not write anything to disk (again, that I know of), so after rebooting there should be no trace. Is it possible that you did something else with root at the same time, and maybe the timing was just a coincidence?

It all stemmed from the fact that the automatic activation of the filter had not happened by the time I had set it for (I always disable tracking, I don't know if it could be related to that).
I then decide to uninstall the application in the classic way (I don't remember if I disabled the module from Magisk first or not) but the reddish tint of the screen seems to have remained. I then activate the system's blue light filter getting a combined effect (even more red screen). I finally decide to reboot in the hope that it would get better. The end of our clumsy story is already known; tragicomic as it sounds.

I don't know if something earlier (I don't recall doing anything of crtical) may have influenced the result which, by the way, you don't expect. That's why I was saying that a warning might prepare the user to spooky unexpected outcomes.