Database Info

[Guide] Install Magisk for root & xposed framework and have working OTA updates

Most Nexus phones users use magisk in order to be able to have root and xposed and also be able to easily pass safetynet check tests in order to be able to get OTA updates.
Well now magisk 14.4 works on our device and OTA updates should work just fine according to this https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Of course when Android Oreo rom comes out we should wait before applying it just to be sure that magisk and twrp will work on that rom so that we wont be left without root after updating (or brick the device.
I wrote a guide for installing magisk 14.4 on our device having 2nd october OTA installed, i copy it here so that more people can see it.
DISCLAIMER - USE AT YOUR OWN RISK! Bellow steps worked for my device but they might brick yours, you might lose warranty etc.!!!!!!
I am not a developer, I am just a user that wants to have the new phone setup like the older phones in my possession before using it as the main everyday phone.
All below packages are here due to the hard work of the people who made them. If you use them, give them the appropriate credits. This is also the reason that I don't attach any files in this post, I only give links to download the packages on the the forum threads/ sites I also found them.
Here I just show a combination of packages/ programs that worked.
PREREQUISITES:
1) Read the whole guide before starting. Make sure you are familiar with all the terms used and you understand what you are doing in each step.
2) I advise you to firstly download all the needed packages and have them in a folder in your computer and also make a copy of them in your phone and then start with the steps of this guide.
3) In this guide I use a windows pc. Fastboot commands are written in cmd. If you use a pc with another operating system, just make sure you can use adb/ fastboot commands and that you can also use miflash or another tool to flash the rom to your phone.
4) Make sure you have correct adb drivers installed in your pc. For this guide I have used adb-setup-1.4.3.exe from this thread.
So this is the step by step procedure with links:
Flash official rom with miflash
rom image: Here is the latest rom. (tissot_images_7.10.14_20171014.0000.00_7.1_d791bf99f4.tgz is the image I used while writing this guide)
miflash: MiFlash2017-7-20-0.zip
Boot to freshly flashed rom,
Install second october OTA update (75mb),
Do reboot and wait a few minutes until the update is installed.
If you have not done any changes to your device (other root like supersu, old magisk verision etc) you can ignore above step.
From settings-->developer options:
Usb debuging on
OEM unlocking on
Just to be on the safe side for magisk manager app also go to Settings --> Security and enable Unknown sources.
Then shutdown phone, boot phone to fastboot with Vol- & power button,
send the command "fastboot oem unlock" in order to unlock bootloader.
Phone reboots by it self if I remember correctly.
Boot to rom, now being unlocked, and see the splash screen to see if it says "Unlocked" to be sure that it is unlocked.
Then shut down the phone.
Again boot phone to fastboot with Vol- & power button,
boot twrp (just boot, not flash) with command "fastboot boot recovery.img"
recovery-3.1.1-1
From twrp, install Magisk-v14.4-20171103-073038
It installs magisk 14.4 but magisk manager apk version installed with this is 14.0.
So, in order to have magisk 14.4, reboot to rom, uninstall magisk manager and then install Magisk Manager 5.4.0 (as suggested by matcho13579) MagiskManager-v5.0-20170513.apk
The problem now with this version of magisk manager is that it installs modules correctly and they work just fine, but the installed modules are not listed in magisk manager modules page (they work but they cannot be seen). That means that you cannot disable a single module, you have to enable magisk core mode to disable all of them or normal mode to have all modules enabled - I hope this will be fixed in a newer version. Magisk-v14.4-20171103-073038 zip file as I said installs magisk manager 14.0 which also appears to be working, but I did all tests on my device with MagiskManager-v5.0-20170513.apk installed.
Next, inside magisk manager downloads, search and install xposed framework sdk 25 systemless by topjohnwu.
After installation is completed reboot phone (phone boot takes some time at this step).
Then install this Xposed installer apk -material design XposedInstaller_by_dvdandroid_31_10_17.apk.
Now you have October 2nd update rom in your device, magisk 14.4 & xposed framework.
If you select magisk core only mode (which disables magisk modules), have enabled magisk hide and hide it form all apps except the ones you want to have root access, the device passes safetynet and theoretically you can install OTA updates (xposed framework -systemless or not- does not pass safetynet, but being installed systemlessly through magisk, it can be disabled), according to this link
Inside magisk manager you can also install this MiA1Plus_V1.01 module in order to enable camera2api & EIS, to be able to use google camera application.
Finally, i installed gravitybox using gravitybox non-fbe 7.0.4 - 29/10/2017 and it also appears to be working, I have not tested it thoroughly though:
https://forum.xda-developers.com/showpost.php?p=73340439&postcount=2
https://forum.xda-developers.com/attachment.php?attachmentid=4317286&d=1509267532

After installing xposed... Safety net goes fail
Sent from my Mi A1 using Tapatalk

How do I flash stock recovery. I flashed twrp earlier and cannot find stock recovery. There is no recovery.img in the tissot system image.

Aman301582 said:
How do I flash stock recovery. I flashed twrp earlier and cannot find stock recovery. There is no recovery.img in the tissot system image.
Click to expand...
Click to collapse
Recovery is included in boot.img

tidschi said:
Recovery is included in boot.img
Click to expand...
Click to collapse
Which means I'll lose root after flashing ?

Aman301582 said:
Which means I'll lose root after flashing
Click to expand...
Click to collapse
Yes, but it takes 1min to boot to TWRP, flash TWRP and Magisk?

blackyz01 said:
After installing xposed... Safety net goes fail
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
As I have written in the first post "xposed framework -systemless or not- does not pass safetynet, but being installed systemlessly through magisk, it can be disabled"
This means that if you enable magisk core mode which disables all modules or if you disable xposed framework module, it passes safetynet.

tidschi said:
Yes, but it takes 1min to boot to TWRP, flash TWRP and Magisk?
Click to expand...
Click to collapse
Okay, managed to get stock recovery back. But 2nd ota is not installing. Always fails

Why install old Magisk Manager? New one seems like it works, unless I am missing something..

ilpanos said:
Finally, i installed gravitybox using gravitybox non-fbe 7.0.4 - 29/10/2017 and it also appears to be working
Click to expand...
Click to collapse
Only one question about this: why did you choose NON-FBE version instead of the normal one?

Thank you :good::good::good:
this is worked for me
but i have a qu. how we will update next OTA?

matcho13579 said:
Only one question about this: why did you choose NON-FBE version instead of the normal one?
Click to expand...
Click to collapse
Just because unfortunately it seems that FBE is not currently supported on our device and it is using FDE.
Perhaps the normal version also works, but I didn't want to be in a situation where I find out in the future that something doesn't work correctly and I have to uninstall it.

suryaabadsar said:
Thank you :good::good::good:
this is worked for me
but i have a qu. how we will update next OTA?
Click to expand...
Click to collapse
First we have to make sure that magisk works correctly in the new OTA. Then and only then, enable magisk core mode to disable modules and pass safetynet and update according to the instructions in the link I have on the first post.

Will we lose root after an OTA update?

You have to do the procedure as described in the link I have provided in the first post. I am putting it again here:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

ilpanos said:
Just because unfortunately it seems that FBE is not currently supported on our device and it is using FDE.
Perhaps the normal version also works, but I didn't want to be in a situation where I find out in the future that something doesn't work correctly and I have to uninstall it.
Click to expand...
Click to collapse
I'm currently using the normal version and everything is working as intended.
That's why I ask, because it might not work the same way with Magisk (I used CF-Root + SuperSU + standard Xposed method)

ilpanos said:
First we have to make sure that magisk works correctly in the new OTA. Then and only then, enable magisk core mode to disable modules and pass safetynet and update according to the instructions in the link I have on the first post.
Click to expand...
Click to collapse
I HAVE UNROOT PHONE WITH THE SAME METHOD AND RE-LOCK BOOTLOADER WITH FASTBOOT COMMAND fastboot oem lock
NOW OTA WILL WORK PROPERLY ON MY PHONE.?

Thanks for the perfect guide.
One side note: official ROM on the provided link is already version .30, so no need to boot into the ROM and install the updates, the update is already merged in

@ilpanos hello mate! I just ordered my A1 from Trading Shenzhen. I have an clear conception what to do with my A1 when it has arrived. So therefore I am collecting some knowledge about flashing and modding (I am not a beginner, but not familiar with A/B partitions). Your thread is very useful here, many thanks.
I have still one question and maybe you can answer it: i would like to remove the google apps from the system, but I don't know if this works just like usual (to remove it from /system/app or priv-app). The reason is that I am using microG instead gapps.
Or will removing files and folders screw up something?
Thanks in advance!
Cheers!

Well, the thing is that by even mounting system partition as read-write ,and of course doing any change - even adding a line in build.prop - disables the ability to do OTA updates. You will have to reflash the new rom for each update. This is the purpose of this thread, to show that there is a way to mod root etc systemlessly without loosing the ability to update (of course under certain conditions).

Magisk + xposed on nougat

Does systemless xposed work on nougat? If so, please provide the links.

BELIEVER PK said:
Does systemless xposed work on nougat? If so, please provide the links.
Click to expand...
Click to collapse
Yes,it does,just install magisk and in downloads search for Xposed modul.Then install and reboot your phone.

Thanks bud.

Works flawlessly since V89.0. Available here in OP https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268

Right now I'm using ELITE ROM V7. 3 and i have rooted supersu but i want to install Magisk for using banking apps n to hide root for some apps. Please guid me step by step to install magisk on elite rom v7. 3

RedSkull23 said:
Works flawlessly since V89.0. Available here in OP https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Click to expand...
Click to collapse
Alright. Do apps like Titanium Backup, gravity box and other xposed modules work, just like they do on supersu?

nagrale.prem said:
Right now I'm using ELITE ROM V7. 3 and i have rooted supersu but i want to install Magisk for using banking apps n to hide root for some apps. Please guid me step by step to install magisk on elite rom v7. 3
Click to expand...
Click to collapse
Completely uninstall SuperSU, flash through TWRP the unsu.zip available here on XDA thanks to osm0sis, and then flash Magisk.
BELIEVER PK said:
Alright. Do apps like Titanium Backup, gravity box and other xposed modules work, just like they do on supersu?
Click to expand...
Click to collapse
Of course they works. Every module works, but not GravityBox. It can't work on an heavy Android modification like EMUI as far as I know, so unless that there's a way to make it work while on SuperSU, it isn't possible to use it on EMUI (as stated in module description on Xposed repo).

Failed while flashing magisk zip.
-Mounting /System, /Vendor, /cache, /data
-Device platform: arm64
-Constructing environment
-/data/magisk.img detected!
-Mounting /data/magisk.img to /magisk
-Found Boot Image: /dev/block/mmclk0p34
-Unpacking boot image
-Checking ramdisk status
! Boot image patched by other programs!
! Please restore stock boot image
Updater process ended with ERROR:1
Error installing zip file '/sdcard/MagiskManager/Magisk-v13.3.zip'
Updating partition details...
...done

Need solutions for above error please...

nagrale.prem said:
! Boot image patched by other programs!
! Please restore stock boot image
Updater process ended with ERROR:1
Click to expand...
Click to collapse
Your boot.img looks already patched by a superuser app... You didn't uninstalled SuperSU in the right way, or you're trying to flash Magisk over SuperSU. As suggested in the log, restore stock boot.img of your firmware before trying to flash Magisk, else it won't work. (Plus, try to flash latest version, V15.3, other than 13)

RedSkull23 said:
Your boot.img looks already patched by a superuser app... You didn't uninstalled SuperSU in the right way, or you're trying to flash Magisk over SuperSU. As suggested in the log, restore stock boot.img of your firmware before trying to flash Magisk, else it won't work. (Plus, try to flash latest version, V15.3, other than 13)
Click to expand...
Click to collapse
Can you please give me link of stock boot.img of honor 6x and give steps to Uninstall supersu

nagrale.prem said:
Can you please give me link of stock boot.img of honor 6x and give steps to Uninstall supersu
Click to expand...
Click to collapse
I've already told you how to remove supersu in the previous page dude, you need to read, not going blind.
The boot.img isn't a common file equal in every firmware, it differs by build number, region, version... begin with writing here your actual build number for extended, and I'll look for the relative boot.img (if it's available here on XDA).

RedSkull23 said:
Your boot.img looks already patched by a superuser app... You didn't uninstalled SuperSU in the right way, or you're trying to flash Magisk over SuperSU. As suggested in the log, restore stock boot.img of your firmware before trying to flash Magisk, else it won't work. (Plus, try to flash latest version, V15.3, other than 13)
Click to expand...
Click to collapse
RedSkull23 said:
I've already told you how to remove supersu in the previous page dude, you need to read, not going blind.
The boot.img isn't a common file equal in every firmware, it differs by build number, region, version... begin with writing here your actual build number for extended, and I'll look for the relative boot.img (if it's available here on XDA).
Click to expand...
Click to collapse
I own honor 6x India version. I understand Uninstal process for supersu. Right now I'm using ELITE ROM V7.3 so i don't know bulid no. N all stuff sorry. I know you will help me

Stock Android 11

Just Posted
https://developers.google.com/android/images#sunfish

fronto said:
Just Posted
https://developers.google.com/android/images#sunfish
Click to expand...
Click to collapse
I just checked my 4a with the Check for Updates button under settings and Android 11 is there waiting for me to d/l and install.

I successfully applied the OTA update, then extracted the boot.img from the full image (both versions matching RP1A.200720.011), patched with Magisk, and then flashed it, but now phone wont boot. Just getting the G startup logo for over 10 min now. Has anyone had success with this method? Is there a better way to do it?

Just updated with no issues, but I'm not rooted yet. Only thing I really want is custom accent color (red), so not sure if it's worth rooting.
Sent from my Pixel 4a using XDA Labs

hate to say it but I think at this point that Magisk 20.4 (Manager 7.5.1) cannot root Android 11 on this phone. I have posted this finding on the rooting thread asking if anyone has had success:
https://forum.xda-developers.com/pixel-4a/how-to/guide-unlock-root-pixel-4a-t4153773/page4

I unrooted, applied update, installed Magisk Canary build, patched boot image from downloaded Factory Image, fastboot flash boot... and have successfully rooted my 4a on w/11.

Well I got an email from Google saying that android 11 was waiting for me to download. So I checked updates and it says my device is up to date. So I guess maybe verizon does hold up updates.

moeava said:
I unrooted, applied update, installed Magisk Canary build, patched boot image from downloaded Factory Image, fastboot flash boot... and have successfully rooted my 4a on w/11.
Click to expand...
Click to collapse
where did you find it? nvrmnd https://github.com/topjohnwu/magisk_files/tree/canary

@tcat007 @fronto
For anyone looking to root, you need magisk canary, latest build at time of writing (20424) works fine for me. Took the OTA from 10 to 11 following the magisk OTA update guide here worked like a charm: https://topjohnwu.github.io/Magisk/ota.html
However, somethings seemed to have changed in 11. For audio apps like jdsp and v4a, you'll need to run this in terminal (only needs done once):
Code:
su -c settings put global hidden_api_policy 1
Also note that sbin is gone too (least on pixel 4a) so v4a app install won't work properly (it's being worked on)

fronto said:
I successfully applied the OTA update, then extracted the boot.img from the full image (both versions matching RP1A.200720.011), patched with Magisk, and then flashed it, but now phone wont boot. Just getting the G startup logo for over 10 min now. Has anyone had success with this method? Is there a better way to do it?
Click to expand...
Click to collapse
You need to use latest canary
Stable doesn't yet support 11 afaik

tthalheim said:
You need to use latest canary
Stable doesn't yet support 11 afaik
Click to expand...
Click to collapse
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img

Yeah I dont like that canary Magisk so I used your advice and flashed the patched boot.img and then went back to stable Magisk. I am a little underwhelmed with Android 11 maybe its just me.
fronto said:
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Click to expand...
Click to collapse

good deal...yeah I figured with the pre-patched boot.img, a lot of people could avoid messing with canary alltogether and just keep normal stable.
Agreed 11 does not seem all that revolutionary. ...but all is working well now with no complaints

Archangel said:
Yeah I dont like that canary Magisk so I used your advice and flashed the patched boot.img and then went back to stable Magisk. I am a little underwhelmed with Android 11 maybe its just me.
Click to expand...
Click to collapse
If you’re running boot imaged patched with magisk canary then your running magisk canary
Sent from my iPad using Tapatalk

Yeah brother all I was saying is that I dont like the canary design for Magisk Manager so I went back to stable for manager only.
jrkruse said:
If you’re running boot imaged patched with magisk canary then your running magisk canary
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse

Archangel said:
Yeah brother all I was saying is that I dont like the canary design for Magisk Manager so I wet went back to stable for manager only.
Click to expand...
Click to collapse
Oh ok
Sent from my iPhone using Tapatalk

fronto said:
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Click to expand...
Click to collapse
Thank you for the upload. Can this be flashed in magisk? I presume no.
Can you clarify the steps? I'm already on android 10 rooted.
1. Uninstall magisk / Restore image
2.. Download install Android 11 / no reboot
3..... ? Then with patched boot.
Thank you

mustbevick said:
Thank you for the upload. Can this be flashed in magisk? I presume no.
Can you clarify the steps? I'm already on android 10 rooted.
1. Uninstall magisk / Restore image
2.. Download install Android 11 / no reboot
3..... ? Then with patched boot.
Thank you
Click to expand...
Click to collapse
Its not flashed in Magisk. Its flashed using fastboot via a computer connection. With that file, you never need to touch Canary manager.
1. uninstall Magisk but you keep Magisk Manager
2. update to Android 11 via OTA or with full image provided you revise the flash-all to not wipe, or just manually issue each command.
3. make sure your 11 is up and running
4. reboot to bootloader, connect PC
5. fastboot flash boot magisk_patched_sunfish-rp1a.200720.011.img
6. reboot and open regular stable Magisk Manager
enjoy

I've rooted my 4a with magisk with the Aug factory image (android 10). I have the both Titanium Pro and Mybackup Pro - Do either of those programs create an image backup similar to the image I create of my PC using a program like Acronis, so that I could just re-install the Android 10 system if I don't like Android 11? If those programs don't do that is there any program that will do that?

Has anyone else noticed x google enrollment then updating message every (re) boot? I must have done something wrong. I got magisk working nicely. Can install itself, modules, ctsProfile is true, whatevs... But nothing else gets a su toast. Not too worried with it this first week or so.. I'll stab again weekend after next.
Sent from my Pixel 4a using Tapatalk

Pixel 3, 2021, Android 11 - what to next?

I just bought a pixel 3. It has Android 11 and I've just unlocked the bootloader. My goal is to load a custom rom. But I don't know what to do next because I only have experience with twrp (which is not available).
Could someone advise me at a high level of what the process is to load a custom rom? I don't even know what magisk does.
Please and thanks.

mcsilvio said:
I just bought a pixel 3. It has Android 11 and I've just unlocked the bootloader. My goal is to load a custom rom. But I don't know what to do next because I only have experience with twrp (which is not available).
Could someone advise me at a high level of what the process is to load a custom rom? I don't even know what magisk does.
Please and thanks.
Click to expand...
Click to collapse
Instructions for installing LineageOS on the Pixel 3 are at https://wiki.lineageos.org/devices/blueline/install
LineageOS has it's own custom recovery, so TWRP is not needed. Magisk provides root. Root is not needed to install a custom ROM. If you don't know what Magisk does, you do not need it. You can learn more about Magisk at the support thread. https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/

dcarvil said:
Instructions for installing LineageOS on the Pixel 3 are at https://wiki.lineageos.org/devices/blueline/install
LineageOS has it's own custom recovery, so TWRP is not needed. Magisk provides root. Root is not needed to install a custom ROM. If you don't know what Magisk does, you do not need it. You can learn more about Magisk at the support thread. https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/
Click to expand...
Click to collapse
The perfect response. I will take your advice, and I'll be happy with lineage.
Many thanks!

Lineage OS 18.1-some banking apps not working

Hi. I just installed Lineage OS 18.1 on my Mi A2. It is working fine for now and much appreciates the work done by the developers. However, I cannot open some banking apps now. Is there a way to fix this? I would be grateful if you could give an effective solution.

Banking / payment apps (at least some) are becoming increasingly capable of detecting bootloader unlocking, custom ROMs, and rooting, even with all Magisk cloacking/hiding measures...

jwoegerbauer said:
Banking / payment apps (at least some) are becoming increasingly capable of detecting bootloader unlocking, custom ROMs, and rooting, even with all Magisk cloacking/hiding measures...
Click to expand...
Click to collapse
Could you please let me know how to install Magisk on MI A2 Lineage os 18.1. Since I don't have TWRP now I cannot install Magisk. Also, I tried to extract the boot Img from payload.bin. in order to get the TWRP installed. I couldn't do that either.

Can't help you: Never used TWRP and / or Magisk - was never needed.

jwoegerbauer said:
Can't help you: Never used TWRP and / or Magisk - was never needed.
Click to expand...
Click to collapse
I extracted the boot.img from payload.bin and after patching it with magisk, I was able to install magisk. Thank you

[email protected] said:
I extracted the boot.img from payload.bin and after patching it with magisk, I was able to install magisk. Thank you
Click to expand...
Click to collapse
I know this is old, but were you rooted when your banking apps didnt work?