Did you do a clean install when you set it up?
this post was submitted on 13 Dec 2024
15 points (100.0% liked)
technology
23383 readers
136 users here now
On the road to fully automated luxury gay space communism.
Spreading Linux propaganda since 2020
- Ways to run Microsoft/Adobe and more on Linux
- The Ultimate FOSS Guide For Android
- Great libre software on Windows
- Hey you, the lib still using Chrome. Read this post!
Rules:
- 1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
- 2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
- 3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
- 4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
- 5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
- 6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
- 7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.
founded 4 years ago
MODERATORS
This would be my guess too. Weird things happen if files are left behind by the old OS. Otherwise they should be able to reinstall it, or the stock ROM using the instructions on the website.
Those are strange issues, I personally haven't experienced any of them.
If you're interested in malware detection, you might try Hypatia.
A reinstall might be helpful, but if you'd like to go back to the original Pixel firmware you can do that pretty easily. First, go to this GrapheneOS installation page and scroll to the bottom for the instructions on removing the non-stock boot key. Then you can use this link to install the stock firmware: Google web flashing tool. It uses a similar web flash tool to what graphene uses for installation.