Root Magisk Without Pc

[Maximilian Lozano]

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?

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.

Now, I'm trying to run adb root from Windows Command Prompt, however, I'm getting adbd cannot run as root in production builds error. So, the very first thing I checked was whether my phone was really rooted?

However, when I do adb root, I get adbd cannot run as root in production builds error.So, I thought, I might have to do some additional stuff beyond what I did above. I tried all the solutions in the following SO questions:

By design adb root command works in development builds only (i.e. eng and userdebug which have ro.debuggable=1 by default). So to enable the adb root command on your otherwise rooted device just add the ro.debuggable=1 line to one of the following files:

In some developer-friendly ROMs you could just enable Root Access in Settings > Developer option > Root access. After that adb root becomes available. Unfortunately it does not work for most stock ROMs on the market.

I ran into this issue when trying to root the emulator, I found out it was because I was running the Nexus 5x emulator which had Google Play on it. Created a different emulator that didn't have google play and adb root will root the device for you. Hope this helps someone.

Samsung seems to make this more difficult than other vendors. I have some adbd binaries you can try but it will require the knowledge of de-compiling and re-compiling the boot.img with the new binary. Also, if you have a locked bootloader... this is not gonna happen.

Lastly, if you are trying to write a windows script with SU permissions you can do this buy using the following command style... However, you will at least need to grant (on the phone) SU permissions the frist time its ran...

Up to Android 9: If adbd on your device is compiled without that flag, it will always drop privileges when starting up and thus "adb root" will not help at all.I had to patch the calls to setuid(), setgid(), setgroups() and the capability drops out of the binary myself to get a permanently rooted adbd on my ebook reader.

If you really need to have ADB running as root, the quickest and easiest way is to install Android Custom ROMs and the most popular is CyanogenMod for it has the Root Access options in developer options menu where you can choose to give root access to apps and ADB. I used CM before but since it wasn't developed anymore, I tried looking for some solutions out there. Although CyanogenMod is still a good alternative because it does not have bloatware.

One alternative I found out from a friend is using adbd insecure app which you could try from here: -developers.com/showthread.php?t=1687590. In my case, it works perferct with an Android custom kernel, but not with the Android stock ROM (vanilla android only). You may try other alternatives too like modifying boot.img of the Android ROM.

Rooting is the process of taking complete control of the operating system of the phone. It has another term jailbreaking. When you learn how to root an Android phone, then you can obtain the privileges to handle all the activities related to the device's OS. You can install, or uninstall any programs despite authorization. By rooting the gadget, you can remove the OS constraints related to software uploads and downloads. It eases in use of the device according to the requirements and convenience.

As you already know that rooting is a jailbreaking process where you are allowed to perform any activities on the phone. Overcoming the OS restrictions, you can make any software uploads without hesitation. Download your favorite games in the Play Store and get access to websites and software as per your needs. Get complete access on your phone and do whatever you want in the absence of device interruptions.

This is a very low level part of the Android system that checks all the partitions and loads up the kernel required to initialize the Android Operating System. Furthermore, it verifies the integrity of the OS image and recovery partition. You can also think of this as the BIOS in desktop computers, the very basic piece of software that makes sure that everything is properly setup and genuine, and ready to go.

Android recovery is the partition that contains some basic utilities that can be used to repair, fix, or update Android. Almost every Android device comes with a recovery mode, which can help you troubleshoot problems that would otherwise seem impossible, like getting out of boot loops, wiping off the entire system even if you are unable to reset your phone from settings, and so on.

You can boot into recovery mode by once shutting off your device then pressing Power + Volume Up/Volume Down button on your device. It also varies from device to device, so if your device has a home button, then you can also try the Power + Home + Volume Up/Volume Down combination.

3a8082e126