this post was submitted on 29 Jul 2023
30 points (100.0% liked)

Technology

37360 readers
247 users here now

Rumors, happenings, and innovations in the technology sphere. If it's technological news or discussion of technology, it probably belongs here.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 

I've been seeing a lot of people talking about how their android phones are rooted here. I'm very fed up with all the bloatware on my phone and I want to de-Google my life so I'm very interested in rooting my own phone.

People we're really helpful with the last post I made here, thank you all so much! I've been doing a bit of research but I'm hoping for some advice/pointers since I've never rooted my phone before and I'm nervous about trusting random internet guides I find.

My phone is a ROG 3 Strix. I'm mostly using this as my guide but I've read a couple of other guides too. I couldn't find a guide specifically for the Strix so I'm assuming (hoping) the steps will be the same.

From what I've read my understanding is that I need to do the following steps:

  • Unlock the bootloader using a tool like fastboot. I believe ASUS has it's own tool for doing this on ROG phones (obiwan-0902-1738_SIGNED_UnlockTool_9.3.0.0_200820_fulldpi.apk).
  • Install TWRP so that I can install a custom OS onto the phone after rooting.
  • Root the phone using a tool like Magisk.
  • Use TWRP to install my OS. I've seen GrapheneOS and LineageOS being used by various people here on Beehaw.

Is there anything else I need to consider, or other guides/reading that would be worth me checking out? And what OS would people recommend I install on my phone?

I'm aware that some apps won't work on rooted phones (e.g. banking apps) but I have another device I can use for those purposes. To install all the apps I'll need I believe I need to download the FOSSAPPS Magisk Module which installs F-droid, which can then install Aurora Store.

top 14 comments
sorted by: hot top controversial new old
[–] [email protected] 24 points 11 months ago

I would say, do a decently deep dive into your model's section on the XDA forums. The people over there are the go to for rooting and custom recovery flashing.

The reason I think this is super important, is because the fact that you haven't found a specific guide for the 3 Strix might possibly be that it just isn't supported yet (or may not be possible to support). I used to have similar issues with certain carrier-specific models not actually supporting the steps needed to flash TWRP over adb or even unlock the bootloader period.

[–] [email protected] 8 points 11 months ago* (last edited 11 months ago) (2 children)

First, you should check if your exact model is supported by the ROM you're trying to install. I could only find this build on the LineageOS site, not sure if that's the exact model. If you can't find a ROM for your exact model you're out of luck. ROMs for other devices won't just work.
GrapheneOS is afaik only built for Pixels, so no.

Current best practice recommended by the devs is using the LineageOS recovery instead of TWRP. The main reasons being up-to-date support for the encryption used by Lineage and OTA upgrades.
In that case, you'd also want Lygisk instead of Magisk, to automatically have root reinstalled after every OTA upgrade. (Lygisk is a fork of Magisk, you get the same functionality otherwise)
Edit: As pointed out by aleph below, you only need Lygisk if your device is A-partition-only. If your device has AB-partitions, simply run the update and BEFORE REBOOTING, go into the Magisk manager and reinstall to the other partition. To check if your device is A-only or has AB-partitions, you can use this Treble checker. If "Seamless System Updates" says "supported", you have AB-partitions. Otherwise it's A-only.

You can hide root for most apps if you use the right modules. The first one you'd want is Universal SafetyNet Fix. With this installed you'll pass basic SafetyNet attestation in most cases.
The second one is Shamiko, a better implementation to hide root from apps. Install that, go to the Magisk/Lygisk settings, Enable zygisk and disable enforcing the deny list, but do select the apps you want to hide from in the tab below.
Shamiko will take over the blacklisting instead and hide you from apps.

For F-Droid, I'd recommend just installing that manually plus downloading the F-Droid Privileged Extension and installing it through Magisk.
For Aurora Store, you can get a similar privileged extension here.

Good luck and happy rooting

[–] [email protected] 3 points 11 months ago* (last edited 11 months ago) (1 children)

In that case, you'd also want Lygisk instead of Magisk, to automatically have root reinstalled after every OTA upgrade. (Lygisk is a fork of Magisk, you get the same functionality otherwise)

Correct me if I'm wrong, but I don't think Lygisk is a blanket recommendation for all devices running Lineage OS. I believe it's for A-partition-only devices, so phones with A-B should use Magisk instead.

[–] [email protected] 2 points 11 months ago

Yep, you're right. I edited my post to add that info

[–] [email protected] 3 points 11 months ago (1 children)

The second one is Shamiko, a better implementation to hide root from apps.

That's proprietary software AFAICT. I wouldn't grant that any privileges on my phone.

[–] [email protected] 1 points 11 months ago

True, it's sadly the best root hiding mechanism currently.
As it's also created largely by the same people who make LSPosed, this makes it at least somewhat trustworthy in my eyes.

[–] [email protected] 5 points 11 months ago

Phones are not like computers (unfortunately).

Others mentioned, but I wanted to point this out more specifically. Each phone model is unique and will require a different ROM. Generic instructions won't work. Sometimes different ROMs are even need for carrier specific versions of the same model.

[–] [email protected] 4 points 11 months ago (1 children)

If you're in the USA and want to make actual phone calls with your phone, most custom ROMs no longer support that. Your only choice is pretty much Google Pixels if you want full functionality.

[–] [email protected] 2 points 11 months ago (1 children)

Really? I haven't rooted in several years. What changed?

[–] [email protected] 4 points 11 months ago

Cellular providers in the US shut down the 3G network. Making calls on the 4G network requires VoLTE to be working. Most of the software that enables VoLTE is closed source, and so most custom ROMs have no way of making VoLTE work. You'll wind up with 4G data, but not 4G voice. With developer phones, like the Google Pixel, all the software is open source, so VoLTE is working in custom ROMs based on that source code.

[–] [email protected] 4 points 11 months ago (1 children)

My best advice is to do a lot of research in advance of the install and not to panic when things go sideways. The steps you've listed look about right, although I usually have to root after installing the OS as the install will often overwrite Magisk and your custom recovery. As someone else mentioned, https://www.xda-developers.com/ will likely have all the information you need.

[–] [email protected] 1 points 11 months ago* (last edited 11 months ago)

Ah, also, it's worth your time to check if apps that you use a lot can be backed up to the cloud. Messaging, podcasts, etc. It's big time saver when you are setting up your new OS. After you have root, check out SwiftBackup, it will make the next one easier.

[–] [email protected] 1 points 11 months ago

One of the easiest things to do, if you use Telegram, is try to find the main group for your phone then subsequently find the group chat to different roms and pick out the one you like. It's the quickest way to get help since the telegram chats are generally quite active. Alternatively xda also works

[–] [email protected] 1 points 11 months ago

You can install GApps after your custom OS in order to get the features that Google provides with official Android releases like the Google Play Store.

load more comments
view more: next ›