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
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) .
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 ...
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 ...
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 ...
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 ...
John Wu 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 OnePlus devices) that ...
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 job ...
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)
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 ...
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 ...
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,...
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 ...
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 ...
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.
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 ...
It seems that the magisk folder is just a link. Not sure about the misc_ce folder.
I copied WifiConfigStore.xml, changed properties and owners and renamed the checksum file. After reboot the checksum was recreated and the xml gets valid...
I finally solved my issue late last night. In recovery, using TWRP, after trying to install Magisk, I'd get a response that was something like "unable to mount /data partition"..and I believe that was what was causing the issue. I found this html site at XDA developers
Install the stock recovery first through fastboot. Then install twrp recovery again through fastboot. Then install the zip file of the stock rom. It worked for me. Get the stock recovery and stock rom from
android.permission.ACCESS_SUPERUSER was defined by SuperSU but:
Due to changes in Android 5.0 Lollipop, this permission has been deprecated and is completely ignored from SuperSU v2.30 onwards
Also only app which declares a permission in its AndroidManifest.xml file can be granted that permission. Shell (com.android.shell) is an AOSP's dummy app to ...
I had the exact same issue when I did an internal upgrade from 18 to 19.1 last night on my Huawei Mediapad M3. I wiped the data as was recommended but it keep rebooting into the unable to decrypt storage.
The easy fix is to boot into fastboot and flash your original, non-magisk boot image. I wish I had tried that before actually going through with the data ...
What data can be wiped? All data on the device can be wiped, it can allow Outlook (actually Exchange server, hosted Exchange server in the case of Office 365) to perform a full factory reset without your intervention, meaning no PIN, no password, or other intervention from the user. If someone issued an erase all data command from the Exchange console to ...
You can flash the custom Rom and Magisk without rebooting. However, I would reboot after flashing the custom Rom and Magisk. That way you can ensure your system and root are setup. Xposed is a bit hacking and it is best to flash on its own.
As far as Xposed you very important to reboot after flashing xposed. Also depending on Rom size it could take around ...
As u mention: if the "Updating partition details..." take more than 4 hours: You have a problem.
As it's noted on the XDA OP, have u flash the "no-verity-opt-encrypt.zip" file ? Apparently it's necessary to completly disabling the forced encryption on your phone.
Try to flash directly the Magisk uninstaller zip, reboot in TWRP, and try again to flash ...
Github does not equal open source. Because a Magisk module is on Github it does not mean it is open source
You can have both open and closed projects hosted on Github and Magisk is no exception as you can see from this XDA post by Magisk developer (though instructions pertaining to Magisk are outdated)
There are projects hosted on Github with a portion of ...
I've had issues installing apps after tweaking stuff before. I was sometimes able to resove it with pm set-install-location 0 in the terminal emulator (executed as superuser obviously).
Though after reading through the comments, it seems like the problem could be more deep then this. I'd also suggest to switch back to SuperSU and see if the problem persists, ...
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: