I’ve written this blog post about moving from rooted Samsung to a Pixel running GrapheneOS.
It’s a list of every root tool that I used, with a note on whether I’ll miss it. I wrote it as a checklist for myself initially, and decided to add links and more comments and publish it. Turns out I don’t really need root, which truly surprised me.
Do you have any apps or tools that hold you back from leaving root?
You don’t have to compile GrapheneOS from source thanks to avbroot which can take a release zip, patch it with root and sign it using a custom avb key. This lets you root while keeping the bootloader locked.
The rooted-graphene project automates this completely using GitHub actions. It even lets you do OTA updates like normal GrapheneOS.
Not against the idea of someone doing what they want with their hardware. That’s what got me into custom ROMs, and Linux, and Open Source projects to begin with.
I personally will not be rooting my GrapheneOS, even though once upon a time I would have jumped at the idea because of wanting a few things.
I feel it does compromise some of the security mechanisms and philosphies of GrapheneOS.
Like I said though, it’s our device, use it how we want.
It should be noted that while you can do this, it can increase your attack surface, defeating a lot of the point of Graphene. Before I started using Graphene, I was a huge fan of rooting and getting full control of my device, so I definitely understand the appeal. But I don’t think I would root Graphene myself, automated or otherwise.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
But you have to compile it again on every update, right?
You don’t have to compile GrapheneOS from source thanks to avbroot which can take a release zip, patch it with root and sign it using a custom avb key. This lets you root while keeping the bootloader locked.
The rooted-graphene project automates this completely using GitHub actions. It even lets you do OTA updates like normal GrapheneOS.
Not against the idea of someone doing what they want with their hardware. That’s what got me into custom ROMs, and Linux, and Open Source projects to begin with.
I personally will not be rooting my GrapheneOS, even though once upon a time I would have jumped at the idea because of wanting a few things.
I feel it does compromise some of the security mechanisms and philosphies of GrapheneOS.
Like I said though, it’s our device, use it how we want.
Wait, what? That’s a pretty big deal!
It should be noted that while you can do this, it can increase your attack surface, defeating a lot of the point of Graphene. Before I started using Graphene, I was a huge fan of rooting and getting full control of my device, so I definitely understand the appeal. But I don’t think I would root Graphene myself, automated or otherwise.