How To Root Using Magisk

[Robert]

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:

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.

-installable-stock-firmware-packages-for-fairphone-3/57219

Note: When flashing full stock images, that include sbl1 or aboot, make sure both slots have a working fastboot before flashing.

And never flash both slots without first testing on one.

Locking as well as unlocking the bootloader will force a factory reset, which will wipe the data and cache partitions. Only the OS itself will be left as is, and once booted it will greet you with the initial setup.

So you will most importantly lose your data in the Internal Storage, the Apps you installed and the data those Apps themselves stored in the data partition.

If you incorporated an SD card into Internal Storage, it will be wiped. If you let an SD card be external storage, it will not be touched.

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?

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.

One of the side effects of switching to LineageOS 17.1 is that a different method for rooting the phone is required. The OS stores its updates at \data\lineageos_updates in the root directory. Since each update is of the order of 0.5 GB, these will eventually take up all of the available free space on the internal storage of the Moto G3. However, the amount of free space can be managed by deleting old updates or moving these onto the micro-SDcard. But, the file cleanup can only take place if the user has root access.reviously, the LineageOS development team released the addonsu software package for rooting the phone. However, in developing LineageOS 17.1, the programmers were unable to port PrivacyGuard to the Android 10 code that forms the basis of the new software. PrivacyGuard had been used by the addonsu software package and its unavailability resulted in addonsu being discontinued. SuperSU, another rooting package I used previously, has not been recommended for use with LineageOS for some time. Consequently, the rooting software of choice at present appears to Magisk.

This method also simplifies the process somewhat since the installation of MagiskManager is not actually required. Rather, just Magisk itself (i.e. the file Magisk-v21.3.zip) can be installed using TWRP.

Previously, I was using a version of LineageOS 16.1 produced by user MSe1969 on XDA Developers. He has recently switched to Version 17.1, but is now only producing his hardened, microG variant. See: -developers.com/t/rom-unofficial-10-0-0-microg-signed-lineageos-17-1-for-motorola-g3-osprey.4218515/. He dropped his standard build (which I was using) as, going forward, there would be no difference from the build that the LineageOS team is now producing for the Moto G3. (LineageOS dropped support for the Moto G3 some time back and has only recently re-instated development for this model.) MSe1969 suggested that users of his standard build simply switch to the official LineagOS build. So, as the microG variant appears to be a bit different in a variety of aspects, and since the standard build did everything that I needed, I opted for the simple solution and am now using the offical LineageOS 17.1 build. See:

I have no problem taking a picture with HDR enabled on my phone. It takes and stores photographs just the same as with HDR disabled. The camera is the standard app included with the official LineageOS 17.1 build. It shows as being Version 2.02.037.

I'd like to achieve that too. However, I keep running into issues. The problem I'm trying to solve now is that the expected mount points are not available after configuring a new connection. I can use rclone ls to list the contents of a server and that succeeds so I know the connection is working. But there are no mount points under any of these locations:

I have rclone-mount working on two different Android devices now. Both are rooted, of course, but one runs the stock Samsung firmware and the other runs LineageOS. The rclone Magisk module did not work correctly for me on either device. I used Termux:Boot to implement a nice automatic rclone-mount solution on my LineageOS device. On the other device, I had to implement my own simple script.

3a8082e126