Related
After many trial and error (including some research here on XDA), it seems that if you are using stock boot.img and have a root using SuperSU 2.62 (systemless root i.e. your boot image was patched to get a working root), you have to install the systemless Xposed to make Xposed work.
It is an unofficial version which can be obtained here
http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Thanks to DVDandroid for this work, don't forget to leave a thanks for him/her.
Am not facing any crashes or weird behavior after this installation.
@DigiGoon, can you please confirm that the root obtained on Pure Rom is a system root?
I think it is but want a confirmation...
Sent from my PLK-L01 using XDA Labs
muradulislam said:
@DigiGoon, can you please confirm that the root obtained on Pure Rom is a system root?
I think it is but want a confirmation...
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Yes, it is System Root.
@HonorCasper...
Figured it out... Normal Xposed for system root and systemless Xposed for systemless root...
Can you suggest some good modules to use with Xposed?
One more thing, I am already using systemless AdAway but most users of Xposed use minminguard, what is the difference?
Sent from my PLK-L01 using XDA Labs
Or better yet use Magisk as your systemless framework and download Phh's systemless Su and the systemless xposed module.
Raptorta said:
Or better yet use Magisk as your systemless framework and download Phh's systemless Su and the systemless xposed module.
Click to expand...
Click to collapse
I tried magisk but could not make it work. I think, I know how to do it the right way now but have to start with a clean firmware and flash magisk, install magisk manager, install Phh's SuperSU, install systemless Xposed and then modules...
Feeling too lazy to give it a try but for sure, it's on my list of things to do so that I can figure it out.
Are you using magisk on honor 7? How did you get it to work?
Sent from my PLK-L01 using XDA Labs
Sure Its working here.
I installed the magisk manager apk first
then flashed magisk from recovery(twrp required)
and right after that(before reboot) phh's su.
Rebooted, installed phh's superuser application from the playstore.
That got me a systemless root.
A systemless xposed is a little harder.
First you need the Material Design Xposed Installer from that link.
If you installed that then head into the magisk manager, swipe left, downloads
Download and install xposed sdk 21 for android 5.0 and sdk 23 for 6.0
It should reboot into recovery and flash the systemless xposed module.
Reboot into system, its gonna take a while, around 10-15 minutes.
And that got me the systemless xposed.
I should say that you should backup your stuff, but its broken in twrp so whatever.
muradulislam said:
@HonorCasper...
Figured it out... Normal Xposed for system root and systemless Xposed for systemless root...
Can you suggest some good modules to use with Xposed?
One more thing, I am already using systemless AdAway but most users of Xposed use minminguard, what is the difference?
Click to expand...
Click to collapse
Im using xstana, which allows u to mod your nav- and notification-bar, and i knowhow many uses YouTube background play, But i havent been in the game for so long so i havent tried so many yet:victory:
@Raptorta... Thanks buddy, will give it a try... You are using magisk v7 or v6 as there are no toggles in v7 anymore...
Sent from my PLK-L01 using XDA Labs
HonorCasper said:
Im using xstana, which allows u to mod your nav- and notification-bar, and i knowhow many uses YouTube background play, But i havent been in the game for so long so i havent tried so many yet:victory:
Click to expand...
Click to collapse
You can also give BootManager a try to stop unwanted applications starting at boot and another I like is Xposed additions to map hardware buttons to new functions.
Have been trying to find some more but except flat style bar indicators, could not find a good one. It's fun to play with but did not keep it for long...
Sent from my PLK-L01 using XDA Labs
Raptorta said:
Sure Its working here.
I installed the magisk manager apk first
then flashed magisk from recovery(twrp required)
and right after that(before reboot) phh's su.
Rebooted, installed phh's superuser application from the playstore.
That got me a systemless root.
A systemless xposed is a little harder.
First you need the Material Design Xposed Installer from that link.
If you installed that then head into the magisk manager, swipe left, downloads
Download and install xposed sdk 21 for android 5.0 and sdk 23 for 6.0
It should reboot into recovery and flash the systemless xposed module.
Reboot into system, its gonna take a while, around 10-15 minutes.
And that got me the systemless xposed.
I should say that you should backup your stuff, but its broken in twrp so whatever.
Click to expand...
Click to collapse
Are you experiencing any hiccups from EMUI OS after using this method.
I mean, like, settings not working, just flashing and force closing or any other thing which should not be?
Are you using v6 and can you play Pokémon go? (If you do)
Sent from my PLK-L01 using XDA Labs
muradulislam said:
You can also give BootManager a try to stop unwanted applications starting at boot and another I like is Xposed additions to map hardware buttons to new functions.
Have been trying to find some more but except flat style bar indicators, could not find a good one. It's fun to play with but did not keep it for long...
Click to expand...
Click to collapse
Will do mate
Did anyone else try it?
So from what I can understand you need to flash magisk and then phh superuser. Is that right?
themegaphoenix said:
Did anyone else try it?
So from what I can understand you need to flash magisk and then phh superuser. Is that right?
Click to expand...
Click to collapse
Phh's SU first. Then Magisk. You can also use systemless SuperSU with it.
Sent from my Galaxy Tab 3 using XDA Labs
adriansticoid said:
Phh's SU first. Then Magisk. You can also use systemless SuperSU with it.
Sent from my Galaxy Tab 3 using XDA Labs
Click to expand...
Click to collapse
You are wrong. It is Magisk and then Phh' SU
It is all working now
Although if you try to install xposed through Magisk it will bootloop. I spent hours try to figure it out why, before i remembered that the theme manager doesnt work with xposed and i think you need to deodex the rom before you install it
ps: when i finally flashed Magisk v8, rebooted and started magisk manager, guess what-- v9 came out (tried to flash that, but it kept saying that boot image does not enough space, so i fashed Digikernel and it worked)
edit: and pokemon go is working so i assume it passes safetynet
Oops. Sorry about that.
Sent from my Galaxy Tab 3 using XDA Labs
Edit: Flash latest beta SuperSU from Chainfire thread, that'll work.
Currently I'm on Stock Nougat, installed element kernel but I don't how to root it. I have flashed SuperSU 2.79 but I got bootloop any help would be appreciated.
Twrp installed.
Stock Nougat NPJ25.93-14
ElementX Kernel installed (1.01)
Thanks.
Flash the superuser zip file from the thread below and then install phh superuser app from playstore.
https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Sent from my Moto G4 Plus using Tapatalk
Silesh.Nair said:
Flash the superuser zip file from the thread below and then install phh superuser app from playstore.
https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Not working, flashed beta SuperSU from chainfire thread, now working perfectly.
Did you flash supersu in systemless mode? For me it won't even try to boot. I have to restore boot from a twrp backup to boot again.
What's the best method for switching?
Do a TWRP backup, then select unroot in the SuperSU app and then flash the binary for Phh's Superuser then download the manager from the playstore?
Or should I just go with Magisk? If so then is this guide still accurate?
Thanks in advance.
You need stock kernel - boot.img.
Unroot in supersu app should clean and restore it.
One reboot to check/uninstall supersu app.
Flash magisk 14(you can do backup "boot" 1st). @nostang3
Mind if I ask, of the recent worries? Ive been out of the loop.
Sent from my ONEPLUS A5000 using Tapatalk
dzidexx said:
You need stock kernel - boot.img.
Unroot in supersu app should clean and restore it.
One reboot to check/uninstall supersu app.
Flash magisk 14(you can do backup "boot" 1st). @nostang3
Click to expand...
Click to collapse
Just want to be clear on the steps.
So I get the 18-16 boot image from here.
Unroot via app.
flash boot.img.
Boot to make sure I don't have root and the boot.img worked.
Flash Magisk 14.
Profit?
nostang3 said:
Just want to be clear on the steps.
So I get the 18-16 boot image from here.
Unroot via app.
flash boot.img.
Boot to make sure I don't have root and the boot.img worked.
Flash Magisk 14.
Profit?
Click to expand...
Click to collapse
Yes to all.
Nickrick2641 said:
Mind if I ask, of the recent worries? Ive been out of the loop. Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
I'm my own words, he sold SuperSu to a company own by a Chinese company, and it's now closed source I think. So people are worried about malicious intent. Don't quote me exactly but that will get you enough info to google to find all the info you need on it.
dzidexx said:
Yes to all.
Click to expand...
Click to collapse
Thanks for you help and swift replies. I'll try it tonight and report back.
Quick follow up @dzidexx.
Since I'm running xposed:
I'll have to flash the xposed uninstaller.
Install the Xposed Installer in Material Design.
Flash the latest magisk release.
And all my current modules should work just fine, correct?
I don't use xposed. I suggest
1st disable all x modules,
Apply xposed uninstaller before unroot(x installer app too).
Unroot.
...
Flash magisk.
For magisk are systemless xposed modules(framework) - flashable zips with twrp or magisk manager.
After root & magisk xposed yours modules should work.
https://forum.xda-developers.com/apps/magisk/collection-magisk-modules-v2-t3575758
---------- Post added at 06:16 PM ---------- Previous post was at 06:16 PM ----------
@nostang3
Hi guys, just some hours ago i got into a problem (at least for me).
I switched today from LineageOs 14.1 to AospExtended Oreo and since i can't use LineageOs root and i don't trust SuperSu anymore (because CodingCode), the only root available for me is Magisk.
Now i have flashed Magisk and set up some modules and the root itself is working, but i cannot delete system apps and modify /system in general. I haven't faced this problem in LineageOs (also with magisk).
And yes, i have tried "reboot disemmcwp" and it didn't work.
I am on A2017G, TWRP 3.2.1.7 (Nfound's build).
Thanks in advance for the answers.
EDIT: I FOUND A SOLUTION (KIND OF)
The situation, however turned out a bit different. At first i thought it was magisk messing with zte's system write protection, but it turned out that the culprit was actually SdMaid. Yep. It has a bug, so when you install a module that REPLACES a system app, like Vanced Youtube, it cannot recognize all the links and tricks that Magisk does and screws up everything, showing /system as read only and if you try to uninstall any system app with its inbuilt app manager, it makes Android crash.
There are 2 possible causes:
1. Magisk
2. You're on the B35 bootstack
I had your issue with Magisk before. Personally, I still think SuperSU can be trusted. But if you're willing to try it again, you should know that it will cause a bootloop with Oreo. It's because of the dtb patching. But I figured out how to make it work anyway. Download the SuperSU 2.72 SR5 zip. Unzip the file into a folder. Then open /meta-inf/com/google/android/update-binary in a text editor. Search for all instances of dtb, and change true to false. Save the file, and create a new zip. Then get the Aroma SuperSU Config zip. In TWRP, flash the config zip first. Select sbin mode on the first page, on 2nd and 3rd pages just use default options or whatever you want. Then flash your modded SuperSU zip. You should be able to boot. All works fine for me.
The 2nd possibility is that you are using the B35 bootstack. There is an issue with it where root appears to work but system partition can't be changed no matter what you do. You need to find a B32 bootstack zip and flash that instead.
I personally am using AOSP Extended Oreo, with B32 bootstack and SuperSU, all is fine so far. I can modify system partition too. If you need more clarification then just ask.
Good luck!
I've used the "disemmcwp" option in nfounds twrp options and it worked for me.
AnonVendetta said:
There are 2 possible causes:
1. Magisk
2. You're on the B35 bootstack
Click to expand...
Click to collapse
Wow, thanks for the fast answer!
I am currently using the B32 bootstack (also from Nfound), so the culprit must be Magisk (unfortunately).
I think i will try your method in the next days, meanwhile i will post this in the Magisk thread, maybe they have some clues about this.
Sent from my ZTE Axon 7 using XDA Labs
Modded SuperSU zip is attached.....
Modded B32 bootstack:
https://forum.xda-developers.com/attachment.php?attachmentid=4427264&d=1519249436
Aroma SuperSU config:
http://download.chainfire.eu/1121/SuperSU/AROMA-SuperSUConfig-v1.00.zip
Magisk uninstaller:
http://tiny.cc/latestuninstaller
Flash Magisk uninstaller, B32 bootstack, Aroma SuperSU config, then modded SuperSU, in that order. Go to /system/xbin and delete the su file, it will interfere with SuperSU. Wipe cache/dalvik cache and reboot. And run the "reboot disemmcwp" (as root, or with ADB), for good measure. You should be able to modify /system now.
Thanks, really.
Sent from my ZTE Axon 7 using XDA Labs
Ok, i did exactly what you said, but i ended up with a bootloop :/
But after dirty flashing my rom and Magisk and reboot disemmcwp in twrp, guess what? I got complete access to /system. That's wizardry my friend.
wannaskoo said:
Ok, i did exactly what you said, but i ended up with a bootloop :/
But after dirty flashing my rom and Magisk and reboot disemmcwp in twrp, guess what? I got complete access to /system.
Click to expand...
Click to collapse
Just for the sake of knowledge i should report that, after many tries, i discovered something interesting (at least for me). Magisk IS actually messing with system write protection, but only if you have any modules enabled. I have Ainur Sauron, Deep_buffer remover, Dolby Atmos for Oreo, AudioModLib, Youtube Vanced and Syspatch as Magisk modules, and i can't touch system in any way after booting into AEX, but if i enable Magisk Core mode and reboot i get complete access to /system.
I hope this thread will be useful for someone having problems with Magisk, because it is a great tool for modding and rooting, but i do really care to have /system access, that's the point of custom roms (for me).
Sent from my ZTE Axon 7 using XDA Labs
wannaskoo said:
Just for the sake of knowledge i should report that, after many tries, i discovered something interesting (at least for me). Magisk IS actually messing with system write protection, but only if you have any modules enabled. I have Ainur Sauron, Deep_buffer remover, Dolby Atmos for Oreo, AudioModLib, Youtube Vanced and Syspatch as Magisk modules, and i can't touch system in any way after booting into AEX, but if i enable Magisk Core mode and reboot i get complete access to /system.
I hope this thread will be useful for someone having problems with Magisk, because it is a great tool for modding and rooting, but i do really care to have /system access, that's the point of custom roms (for me).
Sent from my ZTE Axon 7 using XDA Labs
Click to expand...
Click to collapse
Thanks. I would recommend you report this on the Magisk Thread
Yep, i will do that.
Sent from my ZTE Axon 7 using XDA Labs
Hi guys, I need some assistance. I only want to install GravityBox in my Mi A1 so that I can enable double tap gesture controls and other GravityBox features.
Now the problem is. Is it possible to install GravityBox using Magisk only, or you will still require Xposed Framework?
I understand that installing Xposed Framework will prevent you from having OTA updates and it will trigger SafetyNet.
So, is there a way to install GravityBox in the most least invasive method?
Thank you in advance for any replies.
Gravitybox is a Xposed Module, so it needs Xposed Framework.
There is a Magisk module that activates Xposed Framework, thus, allows us to install and use any Xposed Module.
All becomes "dead" if we simply uninstall Magisk, so I guess there's no issue regarding OTA's since Magisk installs everything, systemlessly.
That's my current config, by the way...
Cheers!
Enviado do meu Mi A1 através do Tapatalk
Battousai1 said:
Hi guys, I need some assistance. I only want to install GravityBox in my Mi A1 so that I can enable double tap gesture controls and other GravityBox features.
Now the problem is. Is it possible to install GravityBox using Magisk only, or you will still require Xposed Framework?
I understand that installing Xposed Framework will prevent you from having OTA updates and it will trigger SafetyNet.
So, is there a way to install GravityBox in the most least invasive method?
Thank you in advance for any replies.
Click to expand...
Click to collapse
Use magisk to download systemless xposed(sdk26) and the modified apk and then u can download GravityBox
Στάλθηκε από το Mi A1 μου χρησιμοποιώντας Tapatalk
Battousai1 said:
Hi guys, I need some assistance. I only want to install GravityBox in my Mi A1 so that I can enable double tap gesture controls and other GravityBox features.
Now the problem is. Is it possible to install GravityBox using Magisk only, or you will still require Xposed Framework?
I understand that installing Xposed Framework will prevent you from having OTA updates and it will trigger SafetyNet.
So, is there a way to install GravityBox in the most least invasive method?
Thank you in advance for any replies.
Click to expand...
Click to collapse
If you have xposed and only gravitybox enabled i think that the test of safetynet in magisk passes(ctsprofile......). Some other modules mess with safetynet.(not 100 sure).you need to check modules one by one and check also the settings of fxposed (resource hooks) and settings of magisk (magisk hide).if you install the modules one by one and recheck safetynet you will have no issue. As far as the ota updates my opinion is to wait 2-3 weeks after the ota arrival and not be early adopters lol.
Thanks guys for the reply. So just to summarize, these are the steps that needs to be done:
1. Install Magisk only.
2. Once Magisk is installed, look for the Xposed framework module (SDK 26?) from Magisk and install it.
3. Once Xposed has been installed, look for GravityBox and activate/install it.
Is there an easy way to roll-back to original state? (i.e. unroot and bring back stock recovery and stock settings)
Thanks guys!
Battousai1 said:
Thanks guys for the reply. So just to summarize, these are the steps that needs to be done:
1. Install Magisk only.
2. Once Magisk is installed, look for the Xposed framework module (SDK 26?) from Magisk and install it.
3. Once Xposed has been installed, look for GravityBox and activate/install it.
Is there an easy way to roll-back to original state? (i.e. unroot and bring back stock recovery and stock settings)
Thanks guys!
Click to expand...
Click to collapse
Before messing with modules make a backup in twrp first . To go stock it is easy hard reset and then lock bootloaderif you want. in case of bootloop or blackscreen because of fxposed modules you can try several solutions before you hardreset.(deactivate xposed or delete modules in twrp) One module is "dangerous " because of black screen . Dont know if they fixed it.
(https://forum.xda-developers.com/xposed/modules/xposed-android-p-ify-features-t3764556)
Also I said sdk 26 because I assumed that you are on oreo if I'm wronig Google search your Android version and find with one you must install
Battousai1 said:
Thanks guys for the reply. So just to summarize, these are the steps that needs to be done:
1. Install Magisk only.
2. Once Magisk is installed, look for the Xposed framework module (SDK 26?) from Magisk and install it.
3. Once Xposed has been installed, look for GravityBox and activate/install it.
Is there an easy way to roll-back to original state? (i.e. unroot and bring back stock recovery and stock settings)
Thanks guys!
Click to expand...
Click to collapse
Στάλθηκε από το Mi A1 μου χρησιμοποιώντας Tapatalk
Hi guys, quick question, I want to install Magisk, the guide I found lets you install Magisk and lets you retain OTA updates so that is good. Now the guide instructs you to install March and April security patch.
This is the xda link: https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
The question is, what if you are already have April 2018 security patch by default on your Mi A1, do you still need to install those two patches according to the guide? If not then how can you install Magisk without re-installing those patch?
Another question is, there are other guide that advises you to install custom recovery such as TWRP to install Magisk, what is the advantage of having a custom recovery over installijg Magisk via fastboot?
panostheodorakis7 said:
Use magisk to download systemless xposed(sdk26) and the modified apk and then u can download GravityBox
Στάλθηκε από το Mi A1 μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
Thanks panostheodorakis7! I finally able to install Magisk and then Xposed systemless SDK 26 within Magisk. I then noticed that there is no Xposed appa available, I tried to install the modified APK and then finally saw the Xposed app.
My question is, what is the use of installing the systemless Xposed within Magisk and what is the logic why we need to install the systemless and then install the APK to enable the app?
Battousai1 said:
Thanks panostheodorakis7! I finally able to install Magisk and then Xposed systemless SDK 26 within Magisk. I then noticed that there is no Xposed appa available, I tried to install the modified APK and then finally saw the Xposed app.
My question is, what is the use of installing the systemless Xposed within Magisk and what is the logic why we need to install the systemless and then install the APK to enable the app?
Click to expand...
Click to collapse
When you install Xposed framework on Magisk, it doesn't mess with System partition which means it won't break OTA updates. Anything that you flash on Magisk, stays on /Magisk. But anything that you flash on twrp, stays on /System.
Rowdyy Ronnie said:
But anything that you flash on twrp, stays on /System.
Click to expand...
Click to collapse
Not 100% true, depends on what you're flashing in TWRP. For example Magisk itself, Magisk modules or custom kernels with stock Wifi drivers won't touch System partition at all. Also do NOT allow System modifications in TWRP as it will break OTA immediately.
Rowdyy Ronnie said:
When you install Xposed framework on Magisk, it doesn't mess with System partition which means it won't break OTA updates. Anything that you flash on Magisk, stays on /Magisk. But anything that you flash on twrp, stays on /System.
Click to expand...
Click to collapse
Thanks Rowdyy Ronnie, ok so installing the modified Xposed APK file doesn't touch the /System? because at first I don't understand the logic why we need to install the Magisk Xposed module and then we still need to install the APK. What is the difference between the Magisk Xposed module and the Xposed APK?
Lastly, I noticed that when I installed Magisk, you need to make a command "fastboot boot patched_boot.img" is this command the one that roots the device? or is it the Magisk Manager APK?
Battousai1 said:
Thanks Rowdyy Ronnie, ok so installing the modified Xposed APK file doesn't touch the /System? because at first I don't understand the logic why we need to install the Magisk Xposed module and then we still need to install the APK. What is the difference between the Magisk Xposed module and the Xposed APK?
Lastly, I noticed that when I installed Magisk, you need to make a command "fastboot boot patched_boot.img" is this command the one that roots the device? or is it the Magisk Manager APK?
Click to expand...
Click to collapse
First, You flash Xposed framework to make your device Xposed compatible and then you use the Xposed Installer app to install xposed modules.
Second, Magisk root your device by patching the boot image (Unlike SuperSu which modifies System partition). So when you type fastboot boot patched_boot.img, you are booting the device into patched boot image instead of stock boot image and thus gaining root access. You can also just boot your device into twrp and flash magisk zip file instead of patching the boot image manually. And Magisk manager is just an app to control root access and allow you to flash magisk modules. But it doesn't root your device.
Rowdyy Ronnie said:
First, You flash Xposed framework to make your device Xposed compatible and you install the Xposed Installer app to install xposed modules.
Second, Magisk root your device by patching the boot image. So when you type fastboot boot patched_boot.img, you are booting the device into patched boot image and thus gaining root access. You can also just boot your device into twrp and flash magisk zip file instead of patching the boot image manually. And Magisk manager is just an app to control root access and allow you to flash magisk modules. But it doesn't root your device.
Click to expand...
Click to collapse
Thanks Rowdyy Ronnie for the quick reply, now it make sense.