Rooting Using Magisk

[Patricia]

TheFP3 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?

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.

Perhaps you've thought about rooting your OnePlus 5, but thought again when you heard SafetyNet would prevent you from using apps like Google Pay, Pokmon GO, or Netflix. Those are valid struggles when you root using traditional methods. There are no such worries when using Magisk, as it masks the fact that your device has been modified.

That means you can have your financial apps and use them too. You can play your favorite games. Magisk is a type of "systemless" root that goes straight to the boot partition to make changes, instead of modifying system files. Since Magisk does not modify system files directly, it can go undetected by apps incompatible with root.

Rooting has always been a cat and mouse game. For every modder who finds a way to get around security to gain root access, another developer produces a patch to prevent future access. Another good thing about Magisk is that it is constantly being updated to keep your root intact and your apps in working order. You must be using a device with a bootloader that is capable of being unlocked to flash Magisk, but that's rather easy with the OnePlus 5.

First, you'll want to create a full backup of your OnePlus 5, as unlocking your bootloader will wipe your data. If you have any personal data you want to save (and who doesn't?), there are several apps that can assist you with the process of backing up data to the cloud or a separate storage device.

The trouble is, most of these apps require root or custom recovery, which you probably don't have yet. So your best options are either hooking your phone up to your PC and copying important files over that way, or using a non-root backup solution like Helium.

Now you'll need TWRP. Team Win Recovery Project is a custom recovery tool that helps make rooting and the installation of custom ROMs possible. TWRP also provides a simple and intuitive interface to make the process a little easier. The ease and functionality that come with using TWRP can also help you perform full backups, wipe your device, or even install a custom kernel if you desire. Before you reap the benefits, though, TWRP must be flashed as described in Steps 3 through 5 at the link below.

When you launch the Magisk Manager app you will receive a prompt asking if you want to install the Magisk framework. Tap "Install," then choose "Download Zip Only" and hit "Allow" on the permission request. If you don't see the prompt offering to install, and instead you see the message "Invalid Update Channel" at the top, try closing the app and reopening it.

Another option is to download the ZIP to your PC and transfer it to your device's internal storage via MTP connection, using the link below. You can just copy and paste; no need to use ADB. You may have to disable encryption, and you'll want to ensure that TWRP has mounted properly when you go to flash the file in the next step. Refer to the link below for more details.

Give your phone a chance to download the file, but when it's finished it's time to boot into your new TWRP recovery. To do so, turn off your OnePlus 5 and simultaneously long-press the volume down and power buttons for a few seconds. Or, if you've enabled Advanced Reboot within Developer Options, you need only long-press the power key, tap "Reboot" once, press "Recovery," and hit the "Touch to Reboot" option.

Achieving root can be an awesome feeling, and you've earned it at this point. However, it's easy enough to confirm that everything has gone as planned. Download "Root Checker" from Google Play and install on your OnePlus 5. Open the app and tap on "Verify Root."

Part of the functionality of the Magisk Manager app is being able to confirm your rooted status will go undetected by Google's SafetyNet. It's SafetyNet that can potentially prevent you from using certain apps such as Google Pay, Pokmon GO, and Netflix. From the Magisk Manager app's main menu, press "Tap to start SafetyNet check" to confirm its status. Tap "Yes"on the "Download Proprietary Code" window that pops up. If all is well, SafetyNet should pass without requiring anything else from you.

Maybe you've been over this more than once and you're still not passing SafetyNet. If so, we have a guide to help with SafetyNet problems. If you've passed SafetyNet, but you aren't done tinkering, rest assured that Magisk is for you. You've opened the gateway to a lot more customization.

Just updated your iPhone? You'll find new features for Podcasts, News, Books, and TV, as well as important security improvements and fresh wallpapers. Find out what's new and changed on your iPhone with the iOS 17.5 update.

Android users have been rooting their phones since the beginning of the operating system, but in recent years it has gotten much more complicated. More recently, a new method for handling root management has emerged, and it's called Magisk.

But starting with Marshmallow, Google essentially blocked the most popular root methods of previous versions---dropping the "su" daemon into the /system partition and running it with the required permissions at startup. This resulted in a new sort of root access, called "systemeless" root, named such because it doesn't modify the /system partition in any way.

As part of this increased security, things like Google SafetyNet have been put in place to keep services like Android Pay secure, which leaves users having to choose between root access and valuable services. It's a bummer.

3a8082e126