Most part of your question is covered in Magisk Documentation. I will quote one of my previous answers to a different question, with some unnecessary details :)
To have a comprehensive understanding of how Magisk works, one must have basic understanding of:
Discretionary Access Control (DAC)
User identifiers ([ESR]UID), set-user-ID
Magisk is not comparable to an iOS jailbreak, because Magisk simply relies on an existing possibility to access a device on root level so that it can access and modify the flash memory directly (e.g. on an bootloader unlocked device via custom recovery ROM or an existing su/root access).
Instead iOS jailbreaks first have to execute complicated exploit chain ...
xposed-framework is de facto dead , the last update being more than two years ago and that too for Oreo and there is no news of further updates.
EdXposed , being open source is a preferred alternative for me and hence this answer. EdXposed officially supports Android 10 (Incidentally,some Xposed modules were working in earlier versions of EdXposed too) .
This answer is not applicable to Samsung / Huawei devices
First, unlock your bootloader. This again ranges from very easy to complicated procedures getting unlock codes, waiting period etc, so read that up first and you have adb installed (this would help , if you don't have it Is there a minimal installation of ADB?).
Second, and very important read these ...
According to this piece of source code by Intel, there is an uint32_t starting at position0x78 (120) and ending at 0x7b (124). This location is marked as "flags from the AvbVBMetaImageFlags enumeration", which "must be set to zero if the vbmeta image is not a top-level image".
On to the enumeration itself. AvbVBMetaImageFlags is defined in the same file and ...
John Wu (Magisk Developer) posted updates today, which clarifies the reasons.
Earlier, SafetyNet API wasn't fully / correctly implemented, the way it was meant to be :
From what we've seen so far, key attestation doesn't seem to be fully enforced yet, as devices with incompatible, potentially buggy(?) keymaster implementations (e.g. some ...
Magisk provides root access by providing a working "root" binary mounted at /sbin/magisk. Any application that tries to run this binary will bring up Magisk to grant them root access, which is in turn managed and maintained by the Magisk Manager application.
The /boot partition is a separate partition that stores some data required to boot the system. It ...
Stock image dump for running Magisk necessary?
No. Far more easier is to use the flashable ZIP that does all- That performs all the steps: backing up the boot image, creating a patched version, flashing that, installing Magisk Manager (thanks to Izzy in comments)
But to clarify on the instructions
What’s the rationale for having the stock boot image dump ...
Install XprivacyLua and select use tracking Pics below show the difference in output
For spoofing instead of hiding you may have to use custom hooks. You can ask on the XDA thread of the app or use the pro version of the module to change values globally or on per app basis
Quoting Namnodorel from comments
Note that this only works if the apps ...
The Magisk module you linked is using fusermount binary from this thread which is built for Termux environment. But LD_LIBRARY_PATH environment variable is not being set properly in the module, so the error occurs. A simple approach is to use static fusermount binary, I already posted in the same thread.
rclone uses FUSE which you can mount manually from CLI ...
No. TWRP is only a custom recovery that replaces your stock recovery. But be sure to flash the right TWRP for your device.
Searching in this XDA thread
using your model number
would be a good idea (On some devices it is possible that root is lost, and you may need to root again)
If it were to happen to me, my preferred approach would be:
Step 1: Clear data of Magisk Manager app
Whatever way your Android supports, open the App info page for your Magisk manager app, force stop the app, and clear its data/storage. Reboot (optional). Now launch the Magisk Manager app. If the problem still persists, follow the steps below.
Step 2: ...
There is different method from Android 9 and later.
For Android 9 and 10 devices, ensure to disable dm_verity by flashing an empty vbmeta before flashing magisk patched boot. Some devices most especially those using Unisoc chipset require that you generate your custom signed vbmeta.
Sorry, I don't know more but only this difference about Android 9 or newer.
From Magisk tap downloads and search for Xposed
Choose Xposed version corresponding to your Android version- choose the version by rovo89
Tap on the module, on the next screen it will prompt you to download an installer. Do that, give permissions for installing for external sources when prompted. Go back to the earlier screen and install. Let it do it's ...
This is a workaround and not what the OP wants in terms of vertical recents ( I don't think it's possible for reasons mentioned at the end of answer).
Install EdXposed (How to install EdXposed on Android 10 without triggering safety net), Xposed Edge Pro at a minimum and Gravity Box for 10 (beta) (preferred).
In Xposed Edge Pro, enable gestures and select ...
(29 June 2020) It looks like Google is just being cautious, and preparing a new field in the SafetyNet response.
According to the SafetyNet API Clients Team
We have started rolling out a new feature that will provide developers with insight into the types of signals/measurements that have contributed to each individual SafetyNet Attestation API response.
Certainly not. It's safe
All that you are doing in this step is to
Check if your device is recognized in fastboot mode by fastboot devices
Replace the boot image by the patched boot image on your computer by
fastboot flash boot xxx.img.
fastboot reboot will boot you into OS where you can verify root as next step recommends.
This the normal way of rooting ...
Alecxs answer (thanks) led me to a different and easier solution.
I uninstalled the manager and tapped on the hidden manager and it opened up with the correct status! Ridiculously simple.
Note to myself :Remember to unhide Magisk Manager before updating next time
You don't have to root your device for debloating.
System apps can be "uninstalled" from adb shell
adb shell pm disable --user 0 <pkgname>
(actually that will disable the app. Do this again after each factory reset)
If your device is rooted with Magisk you can remove apps from system (overlay).
Just create some empty files for the file/...
As far as I know, the point of that Magisk feature is to hide the hosts file from both apps and Android itself. That means you should be able to edit the hosts file with a file editor app, or use a hosts editor app, without it being aware of Magisk. You just have to turn the feature on and grant root to the app.
My /etc/hosts is identical to my /magisk/....
With Magisk 17.1 (introduced by topjohnwu in this commit), Magisk installer ZIP now detects system_root_image and keeps dm-verity/AVB 2.0 when being flashed in recovery. This should solve the issue most of the times (at least with my OnePlus 5 and OnePlus 6).
Alternatively, create a file at /data/.magisk with the following content:
The developer of GravityBox Xposed modules, C3C0, suggested to use official and original Xposed Framework (flashes system partition and breaks Safety Net). They confirmed it working alongside Play Store, but on Android 8.0 though.
Alternatively, one can try Aurora Store from F-Droid, as an alternative to Play Store and as an interim solution. It fetches ...
I know that to be able to install a driver into the kernel, that means a custom kernel and then you would not be able to have OTA updates which defeats the above purpose.
You can't have OTA updates with Magisk installed because flashing Magisk modifies boot partition in which kernel binary lives. Before OTA update, you will have to uninstall Magisk which ...
When installing Magisk you don't need to wipe anything (data, dalvik, cache, system, etc). All you need is to install the Magisk zip.
If you want to install a custom ROM, then it is recommended to wipe data, system and dalvik/cache.
It cannot hide. Developer of Magisk says in his tweet, after the latest Google update
Q6: Is MagiskHide meaningless now?
A6: It depends on your expectation. MagiskHide is still effective to hide anything in userspace, but is no longer capable of spoofing bootloader/verified boot status.
To put it simply, we can still hide "root", but not ...
It appears that Google may have chosen not to enforce this checking, even though it was implemented for a short while (a few days?). At first, the Magisk developer, John Wu, sounded quite pessimistic about it, going even so far as to say that the fun was over.
A few days after the tweets from John Wu that were referenced in the question, however, on March 14,...
When you are in fastboot mode you can directly start the recovery image without installing it:
fastboot boot recovery.img
Alternatively if you want to start the installed recovery rom execute
fastboot flash recovery recovery.img
fastboot reboot bootloader
and then select Recovery using Vol-Up/Down buttons + Power button to start the recovery ROM.
Answer: it is not possible without unlocking boot loader.
Thank you to @alecxs !
Also for anyone interested, rooting has some side effects: cannot load the Netflix app due to safety net checks. Even with the magisk mod for hiding safety net flags.
And ultimately, ARCore still doesn't work, even after I flagged the Pixel 2 "image", and installed Google ...
If you mean by network connection the applications that has "android.permission.INTERNET" permission, then run this shell script:
for package in $(pm list packages -3 | cut -f2 -d":"); do
dumpsys package $package | grep "android.permission.INTERNET: granted=true" > /dev/null && echo $package
If you want to ...