How To Root Android With Magisk

[Nicol Allphin]

Rootingis basically giving yourself privileges to access features on your phone which either would be blocked by the carrier or the actual provider of the phone. There are a variety of apps, access to which can only be granted if your phone has root permissions. For example, you can download an advanced screen recorder.

To the people new to rooting, you are in safe hands! To the people who know rooting, how irritating was it to constantly keep rooting/unrooting your phone in order to get OTA updates! Or the inability to use banking applications on your phone? We totally feel you.

Now, to run that application, you may choose to unroot your phone, work on that app, and re-root your phone using Chainfire SuperSU. But rooting and unrooting your device is a lengthy process. You may do it once but doing it repeatedly will surely feel tedious.

If you want to grant/deny permission for any application, this can be easily done with the help of Magisk App. There are a ton of free modules available on Magisk App, from them you can download apps and games to your Android device. And the plus point is, you can add your own or custom repositories to get stuff from.

Magisk Manager is a well-developed rooting application compatible with Android smart devices and reportedly does not include any sort of malware. It does not modify the boot partitions neither does it touch the system partitions. Unlike other rooting apps, it does not install any third-party applications. Hence, you can rest assured that Magisk Manager is risk-free.

Q.6 With which Android versions is Magisk compatible?

Magisk is now completely compatible with the latest Android version. This app would function on all the versions above the Android 6.0.

Q.7 Why is Magisk not working properly on my phone?

Installing the Magisk Manager to external or adoptable storage can cause some functioning issues. We recommend reinstalling the app to internal storage.

Magisk Manager is undoubtedly a must-have application. It is a one-stop solution to all the root-related issues that usually arise later after rooting of the device. We hope you have now understood what is Magisk, what is Magisk Manager, and what is the use of Magisk Manager. While it may take some time for you to get a hang of it, you will find it totally worth your while.

Sit, thank you very much for your great work

I am using OnePlus 7T running on 10.3.8 (Indian variant) and rooted with Magisk v 22100, i am having a problem were i cant start my phone, what happen is that uninstalled two Apps (Google Duo & Cloud Services from oneplus) by using Debloat, i rebooted my device only once after i unstilled those two apps, what happened is that my phone went to boot loop animation, i have tried several ways to fix this issue by:

Magisk Manager is the official app for managing root on Android devices. After unlocking the boot loader and flashing the corresponding file to root your device, Magisk Manager allows you to manage root permissions and grant them to the applications that request it. For added security, you can enable biometric verification in Magisk Manager, so that only the super-user permission is granted via fingerprint or face detection.

Magisk Manager also allows you to install additional root-related modules. For example, you can install SafetyNet Fix, which helps you to hide certain apps that your device is rooted, as well as the boot loader is unlocked.

From Magisk Manager's settings, you can also install Magisk with Zygisk, which allows developers to create more efficient modules by preloading the resources to be used in the system's memory. You can also choose the apps in which to hide the root, so that you can use them without problems or limits. Among them, you find games and banking and payment apps, which can limit functions if your device is rooted.

Magisk Manager is the best tool for root permissions on Android. It is the most widespread, flexible, and easy-to-use option thanks to its "systemless" flashing mode, which does not modify the Android system partition. In addition, it is compatible with all devices on the market after Android 8.

It's possible to install Magisk Manager without having root permissions on the device, but you can't root your device unless you've completed the previous steps. So it will tell you if you've successfully completed the steps you need in order to enjoy root permissions.

Uptodown is a multi-platform app store specialized in Android. Our goal is to provide free and open access to a large catalog of apps without restrictions, while providing a legal distribution platform accessible from any browser, and also through its official native app.

I'm working on react native project that require SSL Pinning and Root Detection to be implemented, i've tried using the SSL pinner factory in okhttp method and android security config method for the SSL Pinning, as for the root detection i've tried jail-monkey in js side and rootbeer in native side, but despite all of that the SSL still can be bypassed using this frida script and shows that TrustManager (Android By using this, Frida scripts and also tracing can be detected (only in non-stalker mode, if I'm not wrong), so SSL Pinning bypass shouldn't perform on the device. The main drawback you can find in this example is that there's a lot readable and also patchable. So you must do some work to "avoid" easy patching (integrity checks on the NDK side, obfuscation, or some sort).

Aside from Frida, Magisk Hide and Zygisk deny list can be detected through his method as well: Magisk Hide detector. By using Isolated Processes you could test for Magisk and Zygisk. Although, I think Zygisk can be bypassed if you don't use ZygotePreload while spawning the Isolated Process.

I have tried the encryption setting, but it didn't (possibly) go well, as I ended up having short (possibly) 30 seconds soft restarts with my phone after the encryption process completes, and the only way to end this soft bootloop was to do one hard reboot. I also saw some missing apps (such as Maps) after the (faulty) encryption process. Furthermore, and this is the most important and annoying thing I found, is that once I set a password/pattern/pin after the encryption, and add the option to require it after booting, it will not be changed later, even if I changed it later on and added the same option of requiring it on reboot, the first would still persist.

I would like to know if there are steps (and possibly better ROM suggestions) that I could do to achieve full security using device encryption, while still benefiting from Magisk's systemless root that has the option of Magisk hide (using MagiskSu)?

I don't want to expose my data to thieves, as booting into recovery mode would show all my personal information as if I am running the device on root, and with that, you can easily wipe the lockscreen password by deleting the password database.

This was an old problem with Lineage OS based ROMS, where the encryption just didn't work properly. The problem is that ones the encryption is set, it cannot be changed in the GUI. However, I had a success in the past where I changed my encryption key through vdc cryptfs changepw command that can be run on the Terminal app from the developer menu (or any terminal emulator) with a required root access, and you can only change an old password to a new password, an old pattern to a new pattern, ...etc, but not a pattern to a password, ...etc.

The FP3 is the only smartphone so far supported by /e/ that offers the possibility to close the bootloader after the installation of the custom /e/ ROM - thus significantly increasing device security.

My big questions is:

When the official /e/ Fairphone 3 is locked, and I unlock it. What will exactly happen? How to treat this? WIll I lose fuctionallity? Like google pay or pay with bank? Is the only way to root it using Magisk (no hidden commands like in Lineage OS, no added SU.zip file?

I had no luck with restoring all partitions with TWRP in one go, but installing the OS from scratch, setting up encryption like it was before and then restoring just the data partition was looking good when I tried.

What I did mean is, that I read on the official Fairphone forum about losing important? decription keys, data (factory reset) and in the past I even read something about losing special drivers (modem, camera, other drivers because of license related?) and people never to be able to go back to stuff that involves NFC paying and these more advanced blob drivers?

So to put it simple. If I unluck my /e/ phone, what will I lose now???

Here I only find stories of people going from Fairphone OS to /e/ and leaving it unlocked with magisk root. Not about people actually buying the phone from /e/ and then unlocking it.

3a8082e126