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).
The most easiest way to install magisk in lineage os is to use the stock recovery.
Lots of guides are not showing this,they simply say to install a custom recovery and then flash the magisk.
So for absolute beginners,go to stock recovery,click on apply update and then update from adb,have your pc with you and your phone connected to it via a adb connection and then send the file over adb.Done magisk is installed on your phone.
varun94 said:
The most easiest way to install magisk in lineage os is to use the stock recovery.
Lots of guides are not showing this,they simply say to install a custom recovery and then flash the magisk.
So for absolute beginners,go to stock recovery,click on apply update and then update from adb,have your pc with you and your phone connected to it via a adb connection and then send the file over adb.Done magisk is installed on your phone.
Click to expand...
Click to collapse
From what I've read Android 11 does things differently. Stock recovery I would try if it I can get a matching month/year Security Patch file for boot recovery.
My device isn't supported by twrp (Huawei fla-lx1 or fla-l21) and I want to install this gsi image file because my phone is treble compatible, is it a must to have a working twrp image? Doesn't LOS has its own recovery thing? Can I still root it and install modules? Can I do ANYTHING?
Relected said:
My device isn't supported by twrp (Huawei fla-lx1 or fla-l21) and I want to install this gsi image file because my phone is treble compatible, is it a must to have a working twrp image? Doesn't LOS has its own recovery thing? Can I still root it and install modules? Can I do ANYTHING?
Click to expand...
Click to collapse
Once you can unlock bootloader then you could do a step further, GSIs can be installed through fastboot, and in regards LOS recovery it must there one specific for your device, they're not generic recovery images for every android device.
As above, I would appreciate it if someone could share a copy of a Magisk patched 11.0.5.1.GM21AA boot image. Thanks!
P.S. - Do not update to Magisk 24 or 24.1 unless you want to have to mess around with your phone!
Here you go.
Patched with 24.1 Magisk. Rom Zip downloaded from here
[OnePlus 7 Pro (5G)][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: this is not a support thread for issues you may have with...
forum.xda-developers.com
File on MEGA
mega.nz
I also had problems with updating Magisk trough the app. No root after reboot.
Could not get root access with flashing magisk in twrp. I tried several version of magisk but nothing worked. Ended up using the patched boot.img
Dont know what the problem is.
Dan3ll1 said:
Here you go.
Patched with 24.1 Magisk. Rom Zip downloaded from here
[OnePlus 7 Pro (5G)][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: this is not a support thread for issues you may have with...
forum.xda-developers.com
File on MEGA
mega.nz
I also had problems with updating Magisk trough the app. No root after reboot.
Could not get root access with flashing magisk in twrp. I tried several version of magisk but nothing worked. Ended up using the patched boot.img
Dont know what the problem is.
Click to expand...
Click to collapse
Thanks a lot!
I managed to get Magisk 23 installed, would the patched boot image be different from yours?
benengyj said:
Thanks a lot!
I managed to get Magisk 23 installed, would the patched boot image be different from yours?
Click to expand...
Click to collapse
How did you do??
I tried to downgrade Magisk to 23.0 due to the lack of Magisk Hide but now my OnePlus 7 Pro is no longer rooted. So I tried to re-root it in several ways (flashing boot.img previously patched with Magisk Manager or by directly installing Magisk.zip with TWRP) but nothing to do, still without root...
I would like to try to use another boot.img but I would need one taken from a rom 11.0.5.1.GM21BA and patched with Magisk 23. I can't find it on the net.
Frodolo said:
How did you do??
I tried to downgrade Magisk to 23.0 due to the lack of Magisk Hide but now my OnePlus 7 Pro is no longer rooted. So I tried to re-root it in several ways (flashing boot.img previously patched with Magisk Manager or by directly installing Magisk.zip with TWRP) but nothing to do, still without root...
I would like to try to use another boot.img but I would need one taken from a rom 11.0.5.1.GM21BA and patched with Magisk 23. I can't find it on the net.
Click to expand...
Click to collapse
Once you've upgraded to 24 or 24.1 it seems that the only way to go back to an older version is to use the built-in uninstall button in the Magisk app. Just trying to flash a new boot image over it doesn't seem to stick.
In my case, I had to:
Uninstall any version of the Magisk app
Install 24.1
Extract the boot image using Payload Dumper
Creating a 24.1 patched boot image to re-root my device
Uninstalling 24.1 using the uninstall button in the Magisk app
Install Canary Magisk (23 should work too)
Create a new 23 patched boot image and root using it
Still have not gotten around to fixing my MagiskHide and SafetyNet failing though, I think that requires some cache clearing and other steps to resolve. Also somehow managed to get rid of my TWRP accidentally along the way too, so I'll have to reinstall that again.
Thanks a lot!
benengyj said:
Uninstalling 24.1 using the uninstall button in the Magisk app
Click to expand...
Click to collapse
I only see an "Install" button in the Magisk 24.1 app. I don't see an "Uninstall" button.
Were you already rooted when you saw the Uninstall button?
¿GotJazz? said:
I only see an "Install" button in the Magisk 24.1 app. I don't see an "Uninstall" button.
Were you already rooted when you saw the Uninstall button?
Click to expand...
Click to collapse
See steps 1-4. You have to temporarily root it by flashing a patched boot image (that was patched with 24.1) so that you can use the root privileges to uninstall Magisk. It's kinda ass-backwards I know...lol
benengyj said:
See steps 1-4. You have to temporarily root it by flashing a patched boot image (that was patched with 24.1) so that you can use the root privileges to uninstall Magisk. It's kinda ass-backwards I know...lol
Click to expand...
Click to collapse
Yep, that's weird. I was having (a ton of) trouble getting my phone rooted at the time, so that's why I didn't see it.
Hello. I'm trying to flash a TWRP custom recovery on a SM-A305G (Galaxy A30). While reading the official A30's post on the TWRP website, in order to properly flash the custom recovery, they recommend me to first root my device with Magisk (which I understand how to) but THEN flashing a pre-rooted TWRP image for my device. How could this be done?
Related link: https://twrp.me/samsung/samsunggalaxya30.html
Thanks in advance to who could answer this question. Internet hero.
Rooting Android OS is adding an user with elevated rights ( comparable to adminstrator in Windows OS ) to it, nothing else.
TWRP recovery does not require a phone's Android is rooted.
lnrdx said:
Hello. I'm trying to flash a TWRP custom recovery on a SM-A305G (Galaxy A30). While reading the official A30's post on the TWRP website, in order to properly flash the custom recovery, they recommend me to first root my device with Magisk (which I understand how to) but THEN flashing a pre-rooted TWRP image for my device. How could this be done?
Related link: https://twrp.me/samsung/samsunggalaxya30.html
Thanks in advance to who could answer this question. Internet hero.
Click to expand...
Click to collapse
That just isn't how it is done, we don't root TWRP, we root the phone's OS. There isn't anything to "root" in or about TWRP because TWRP has the power to modify a device without needing root.
It isn't required, but, it is possible to root a device and then use an app such as Rashr, Flashify or TWRP Manager along with root permissions to flash a TWRP img or even use a Terminal Emulator app with root permissions to install TWRP via dd commands. It doesn't "have" to be done this way, it's just an alternative way to achieve root and flash TWRP on devices that are capable of doing it this way, in this order, not all devices can do it this way.
I want to have Magisk AND TWRP.
I rooted the phone with Magisk and had Magisk running.
Then installed TWRP app and flashed TWRP with root permission.
Now TWRP is installed but Magisk is gone again.
How can I have BOTH?
woheller69 said:
I want to have Magisk AND TWRP.
I rooted the phone with Magisk and had Magisk running.
Then installed TWRP app and flashed TWRP with root permission.
Now TWRP is installed but Magisk is gone again.
How can I have BOTH?
Click to expand...
Click to collapse
Flash the Magisk.zip via TWRP just to be sure binaries are installed, then wipe cache and dalvik cache in TWRP then boot into system and install the Magisk Manager app(if it dosen't get installed when you flash the Magisk.zip).
Unfortunately not working.
I installed Magisk via Odin wirh a Magisk-patched stock rom ( Galaxy A10). WORKED
Then installed TWRP via Odin and got TWRP and Magisk working by immediately booting into recovery after flashing.
But then I installed the CrDroid custom rom via TWRP and now Magisk is gone.
[ROM][ARM][OFFICIAL] crDroid 8.x for Galaxy A10 [Android 12]
*** Disclaimer I am not responsible for any damage you made to your device You have been warned crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features...
forum.xda-developers.com