-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unistalling led to dm-verity file corruption #335
Comments
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 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. |
Steps To Reproduce
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:
The text was updated successfully, but these errors were encountered: