Related
https://www.xda-developers.com/official-xposed-framework-android-nougat/
https://forum.xda-developers.com/showthread.php?t=3034811
https://forum.xda-developers.com/xposed/discussion-xposed-nougat-t3685687
Let's share what does/doesn't work
Since I made the post, it's only fair I go first.
On A2017G, stock and updated via OTA to 7.1, the flash was successful. The first boot took ~10 minutes. I will now start testing modules and update this post with what does/doesn't work.
Modules I tried so far:
LP: Works
Amplify Battery Extender: Works
Greenify: Does NOT work - The module is active, however, the app does not seem to be aware that it is.
-I'm looking for the old Youtube Background Playback module. It seems to have been pulled from the download list inside xposed manager. If anyone has a copy of it, it would be great to see if it's still working. The LP patch for background play stopped working for me on 3 different devices about 2 weeks ago.
Great!
Maybe a stupid question, but will installing xposed still break safetynet checks? That was the only benefit of running.g without xposed; aps like horizon / Ziggo Go worked, hate to have to do without it.
TIA,
Cheers,
/Cacti
Sent from my ZTE A2017G using XDA-Developers Legacy app
Amplify can't see wakelock or service...greenfy continue to tell me to activate the module. (I just set on the module and reboot many times)
UPDATE: other users with different device have the same problem, I think we need an update of these apps for working with the new version of exposed.
https://forum.xda-developers.com/xposed/discussion-xposed-nougat-t3685687
Running A2017UV1.1.0B32 (android 7.1.1) rooted by Magisk Version 14.0.
all was good but when installed xposed (SDK 25/API 25) something is wrong;
SafetyNet is faild at check and in Magisk , when pressing Menu->Superuser I get "Magisk Manager has stopped"
but root is working and Xposed modules are working.
mb0 said:
Running A2017UV1.1.0B32 (android 7.1.1) rooted by Magisk Version 14.0.
all was good but when installed xposed (SDK 25/API 25) something is wrong;
SafetyNet is faild at check and in Magisk , when pressing Menu->Superuser I get "Magisk Manager has stopped"
but root is working and Xposed modules are working.
Click to expand...
Click to collapse
I had the magisk FC too. Fixed it by switching to stable channel reinstalling both the zip and the launcher. Safety net is broken with magisk hide setting and the "universal safety net fix" module.
rzarectha said:
I had the magisk FC too. Fixed it by switching to stable channel reinstalling both the zip and the launcher. Safety net is broken with magisk hide setting and the "universal safety net fix" module.
Click to expand...
Click to collapse
Thanks. Not what I wanted to hear but still [emoji4]
Cheers,
/Cacti
Sent from my ZTE A2017G using XDA-Developers Legacy app
@rzarectha thank you, but it didn't help. even tried install beta version;
tried to complete uninstall and install again the zip and apk - it worked and no more FC.
Im also on B32 with Magisk, but currently running the official Xposed for Magisk. Should I use the Xposed uninstaller or just remove and uninstall the Magisk Xposed module before starting with the official Xposed process?
Regarding YouTube background play:
I found the .apk on their github page, it's in the first thread that mentions it being removed from the repo. I tested it and it works!
For whatever reason, I cannot get past a bootloop after installing via TWRP. Interestingly, I can install the unofficial module from back in August. I can uninstall that just fine, but reinstalling the proper one does nothing but bootloop. Anyone else having this problerm?
Could anyone try running Fate Grand Order?
After update to V88 the boot time is longer for 45-50 second on my A2017G with Stock 7.1.1B06. With inofficial V87 boots better
This is what I have setup so far. Crappalinks, YouTube Adaway, XInsta, all work. Greenify doesn't and neither did Amplify, not properly anyway. Also it does break Safety net. We'll have to wait for the Magisk Module
rzarectha said:
Since I made the post, it's only fair I go first.
On A2017G, stock and updated via OTA to 7.1, the flash was successful. The first boot took ~10 minutes. I will now start testing modules and update this post with what does/doesn't work.
Modules I tried so far:
LP: Works
Amplify Battery Extender: Works
Greenify: Does NOT work - The module is active, however, the app does not seem to be aware that it is.
-I'm looking for the old Youtube Background Playback module. It seems to have been pulled from the download list inside xposed manager. If anyone has a copy of it, it would be great to see if it's still working. The LP patch for background play stopped working for me on 3 different devices about 2 weeks ago.
Click to expand...
Click to collapse
why use Xposed for youtube adaway and background player when they make a separate app for that over here https://forum.xda-developers.com/android/apps-games/app-iytbp-injected-youtube-background-t3560900 I have been using this for a while now and it is great
reV17 said:
This is what I have setup so far. Crappalinks, YouTube Adaway, XInsta, all work. Greenify doesn't and neither did Amplify, not properly anyway. Also it does break Safety net. We'll have to wait for the Magisk Module
Click to expand...
Click to collapse
There is a magisk module on the repo but to my knowledge it still breaks safetynet
For those with issues with magisk and xposed, you can't use them both together, if you want to then you have to use the specific xposed magisk module here https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268 also flashing xposed regardless magisk or not its going to break safetynet no matter what. Will explain in that magisk xposed thread.
If someone got problems like me, heres my way i installed it successfully and get everything to work (Magisk!):
- disable xposed modules
- restart to recovery
- install Xposed v88.2 by topjohnwho (from xposed thread) via recovery
- reboot to system (first boot took ~9min)
- install Xposed Installer 3.1.2 for Magisk
- activate modules in xposed installer
- reboot phone and its done.
If you dont deactivate the xposed modules before flashing xposed, you maybe have to reinstall them and maybe set up everything new, if you cant save the settings for the modules. This was happening in my first try. In my second try i disabled them before and activated after flashing and dont have do setup every xposed module again.
A2017G with B06 and Magisk v14.2.
Can you use gravity box module on the stock rom? Is miflavor "close enough" to aosp to be compatible with mods made for that?
rzarectha said:
Can you use gravity box module on the stock rom? Is miflavor "close enough" to aosp to be compatible with mods made for that?
Click to expand...
Click to collapse
Yes. Not all is working, but center clock, battery mod in statusbar, RAM usage in recents, down-/uploadspeed in statusbar and some other things ... enough for me.
Hello guys!
If you update to the latest Magisk version (v16.4), you will notice that it will now pass SafetyNet check.
Check attached screenshots!
rzarectha said:
Hello guys!
If you update to the latest Magisk version (v16.4), you will notice that it will now pass SafetyNet check.
Check attached screenshots!
Click to expand...
Click to collapse
Thats nice to know. I mean i havent used magisk yet (on previous phone it didnt work at all). Currently still on supersu. But its good to know that it works again, so i might switch in the future.
Sent from my ZTE A2017G running V1.2.0B08 using XDA Labs
GodOfPsychos said:
Thats nice to know. I mean i havent used magisk yet (on previous phone it didnt work at all). Currently still on supersu. But its good to know that it works again, so i might switch in the future.
Sent from my ZTE A2017G running V1.2.0B08 using XDA Labs
Click to expand...
Click to collapse
I think it's just as good as SuperSU in handling root apps. The way Magisk stands out though is the modules. I would recommend that you install only the magisk manager (it does not mess with anything in your phone if you just install it), and browse through the list of modules it has. It's very similar to the way modules in xposed look like. Maybe you can find some interesting functionality in there.
I am using the greenify module (works much like boost mode on xposed), busybox, adblocker, systemiser (turns user apps in sys apps), debloater (completely uninstall user apps). There's a ton of mods though, I don't even understand what most actually do.
Keep in mind that having xposed installed will break safetynet no matter what. Magisk can't hide it.
rzarectha said:
I think it's just as good as SuperSU in handling root apps. The way Magisk stands out though is the modules. I would recommend that you install only the magisk manager (it does not mess with anything in your phone if you just install it), and browse through the list of modules it has. It's very similar to the way modules in xposed look like. Maybe you can find some interesting functionality in there.
I am using the greenify module (works much like boost mode on xposed), busybox, adblocker, systemiser (turns user apps in sys apps), debloater (completely uninstall user apps). There's a ton of mods though, I don't even understand what most actually do.
Keep in mind that having xposed installed will break safetynet no matter what. Magisk can't hide it.
Click to expand...
Click to collapse
Edit: i moved this issue to the Q&A and help section since more issues keep coming
https://forum.xda-developers.com/axon-7/help/finally-decided-to-switch-supersu-to-t3787201
just switched to latest stock rom (1.2.0 B10) and installed magisk (16.4). it works and safetynet passes. the problem i got now is that the greenify module fails to install in magisk (see screenshot)
do i gotta flash the module through TWRP maybe? still a newbie to magisk since the axon 7 is the first phone to have it working
EDIT: for some reason magisk doesn't remember which apps have requested root after a reboot. everytime i reboot i get a prompt to allow root access to all my root apps (like greenify). idk why this is happening. i mean, root itself is working as it should. i already uninstalled bloatware and disabled/freezed things like the powermanagement
I'm interested in knowing where Magisk is at
This is Magisk/Xposed Module that allows for Full SafetyNet pass. All green checks with Xposed installed still. Requires Xposed installed on top of Magsik. I recommend Xposed through Magsik for dual systemless, but stand alone install of Xposed is fine. This is a first if it's kind for Magisk with Xposed for full green checks on SafetyNet Check. A game changer. Hope you enjoy . As I do what I can to help keep this epyk monster V20 alive.
Tested For 7.0. May work for others. Backup before testing.
Android 8.0 h910 works perfect.
Seems like it can't bypass logd being disabled.
Alpha Omega 8.0 w/ Magisk Hide enabled, logd disabled = fail.
Edit: Forgot to enable the module in Xposed in addition to Magisk. After enabling in Xposed, it now passes SN with the same parameters as above.
Great stuff!
Edit 2:
While there are now all green checks in Magisk's safetynet check, Google Pay still detects root/alteration.
nickthaskater said:
Seems like it can't bypass logd being disabled.
Alpha Omega 8.0 w/ Magisk Hide enabled, logd disabled = fail.
Edit: Forgot to enable the module in Xposed in addition to Magisk. After enabling in Xposed, it now passes SN with the same parameters as above.
Great stuff!
Edit 2:
While there are now all green checks in Magisk's safetynet check, Google Pay still detects root/alteration.
Click to expand...
Click to collapse
Idk...try using Magisk hide for that on top of this mod. I personally never use Google pay
Mysticblaze347 said:
Idk...try using Magisk hide for that on top of this mod. I personally never use Google pay
Click to expand...
Click to collapse
Have you confirmed that safetynet is actually being satisfied in any other apps that require it?
nickthaskater said:
Have you confirmed that safetynet is actually being satisfied in any other apps that require it?
Click to expand...
Click to collapse
I can only confirmed it passes in Magisk. Can't varify fully as to other uses as I really don't need full Safteynet. I just like seeing it pass and that is why I posted this. I usually don't need full Green for my use.
I do however know that it help with screenshot protection bypass for some banking apps ect.
Don't install it. It messes up with your google app and system apps. There is no turning back one you installed it, fastboot flash can only clean your mobile after that. There is a reason it was banned from official xposed modules.
atul18 said:
Don't install it. It messes up with your google app and system apps. There is no turning back one you installed it, fastboot flash can only clean your mobile after that. There is a reason it was bannejd from official xposed modules.
Click to expand...
Click to collapse
This is why it is controversial. I personally have not had any issues. This is also why I said I recommend "dual piggyback - systemless". I was sceptical myself, main reason for the Magsik mod. Systemless is better than embedded.
Mysticblaze347 said:
This is why it is controversial. I personally have not had any issues. This is also why I said I recommend "dual piggyback - systemless". I was sceptical myself, main reason for the Magsik mod. Systemless is better than embedded.
Click to expand...
Click to collapse
Someone pushing it into xda community silently.
If it was legit it will be on github. There is something wrong about this. If you have much knowledge about code I have a report file on this module. I will post it here.
---------- Post added at 07:39 PM ---------- Previous post was at 07:33 PM ----------
https://forum.xda-developers.com/xposed/modules/hiddencore-module-doing-t3903984/post79085117
Well again...this is systemless (no systematic attaching) disable at will. No footprint left behind. Once deleted its removed....it's fully gone. How can I explain systemless even further? I ment no harm with this thread as to why I made Magisk based. I just thought was sweet to pass SafetyNet in Magisk. I never thought to check SafetyNet app or even knew of stand alone apk.
If this really is as bad as you supposedly say, then I will delete this thread soon. My apologies in advanced if so.
I can't use apps that check safetynet.
It's failing in the response validation
Mysticblaze347 said:
Well again...this is systemless (no systematic attaching) disable at will. No footprint left behind. Once deleted its removed....it's fully gone. How can I explain systemless even further? I ment no harm with this thread as to why I made Magisk based. I just thought was sweet to pass SafetyNet in Magisk. I never thought to check SafetyNet app or even knew of stand alone apk.
If this really is as bad as you supposedly say, then I will delete this thread soon. My apologies in advanced if so.
Click to expand...
Click to collapse
Don't worry, the module is safe
Daved+ said:
I can't use apps that check safetynet.
It's failing in the response validation
Click to expand...
Click to collapse
Sorry it don't pass others other than Magisk it seems. Makes ya wonder where Magsiks SafetyNet is from. I personally don't know what else to say on this matter . I just ported, I didn't create the app. Just the Magsik Module is all I did. I'm in the same boat...but I'm keeping because I like seeing Magsik all Green. Also most likely due to a signature validation that was removed in my guess. Another version of a cloak if ya wanna say.
It's sad since the module removed from the repo, we can't expect update(s)
@Mysticblaze347. I'm using it with Magisk V19. Passes SafetyNet (ctsProfile + Basic System Integrity). Reported by Magisk Manager.
Tests from Any other App reports SafetyNet test Failed!!
So it seems like you only handled checks in setup.zip which Magisk Manager uses to report SafetyNet status!
Sorry.. I edited my Thank you post to this one.
I install it from xposed, and my exposed installed from magisk. Yes it made the magisk green, but my screen can't auto sleep. Uninstalled made normal again. From HTC U11 Android 8.0
A San said:
I install it from xposed, and my exposed installed from magisk. Yes it made the magisk green, but my screen can't auto sleep. Uninstalled made normal again. From HTC U11 Android 8.0
Click to expand...
Click to collapse
That version from Xposed itself does that, this version don't. Whole different area. Also, heads up. I just ported, not created. This also ONLY passes Magisks SafetyNet check for some reason. Why I do not know. I just made an optional port.
Already try install from this application. It won't work with my HTC U11 Android 8.0. Still red.
A San said:
Already try install from this application. It won't work with my HTC U11 Android 8.0. Still red.
Click to expand...
Click to collapse
This Magisk module was made initially for Nougat 7.0. I am running it and it's fine.
Did you check the Xposed side after Magisk install for active module?. Requires 2 reboot s total.. Magisk, then Xposed.
Best Version!
The version of this HiddenCore module is 1.3, which does not have the remaining awake bug found in version 1.7.
Mysticblaze347 said:
This is Magisk/Xposed Module that allows for Full SafetyNet pass. All green checks with Xposed installed still. Requires Xposed installed on top of Magsik. I recommend Xposed through Magsik for dual systemless, but stand alone install of Xposed is fine. This is a first if it's kind for Magisk with Xposed for full green checks on SafetyNet Check. A game changer. Hope you enjoy . As I do what I can to help keep this epyk monster V20 alive.
Tested For 7.0. May work for others. Backup before testing.
Click to expand...
Click to collapse
I just installed the app and it shows that " Launching the app on rooted device is blocked". So I uninstalled it and then reinstalled it again and used magisk hide. Also, I have hide magisk manager already enabled in magisk settings but the app still doesn't budge and somehow still detects root and thus I can't use it. Any solutions ?
I'm on MIUI EU 11.0.6 rooted with magisk 20.4
seshStation 5.1 kernel
Official latest TWRP recovery.
MasterFURQAN said:
I just installed the app and it shows that " Launching the app on rooted device is blocked". So I uninstalled it and then reinstalled it again and used magisk hide. Also, I have hide magisk manager already enabled in magisk settings but the app still doesn't budge and somehow still detects root and thus I can't use it. Any solutions ?
I'm on MIUI EU 11.0.6 rooted with magisk 20.4
seshStation 5.1 kernel
Official latest TWRP recovery.
Click to expand...
Click to collapse
Do you pass safetynet?
There's a magisk hide config module in magisk downloads if you don't.
sotosgolf said:
Do you pass safetynet?
There's a magisk hide config module in magisk downloads if you don't.
Click to expand...
Click to collapse
Yes I'm passing safety net. Both the magisk manager and the check SafetyNet app confirm the same.
MasterFURQAN said:
Yes I'm passing safety net. Both the magisk manager and the check SafetyNet app confirm the same.
Click to expand...
Click to collapse
You could flash your original boot image and see if it's related with the kernel, just in case.
sotosgolf said:
You could flash your original boot image and see if it's related with the kernel, just in case.
Click to expand...
Click to collapse
I was thinking the same. I'll reply with the results. Thanks
You could try renaming the magisk manager.
It worked for me with the McDonald's App.
You can find it in the settings from magisk manager. Give the app a random name like managerxy3 and use magisk hide option, just in case.
Maybe try core mode only, if you only need root and don't use any modules.
SpitFireXB360 said:
You could try renaming the magisk manager.
It worked for me with the McDonald's App.
You can find it in the settings from magisk manager. Give the app a random name like managerxy3 and use magisk hide option, just in case.
Maybe try core mode only, if you only need root and don't use any modules.
Click to expand...
Click to collapse
I already have that enabled (Hide magisk manager). It's in the OP. I only have busybox by osmosis installed in magisk modules.
I just installed Paytm First Games (Lite? ) and upon launching it asked to Login via OTP/Paytm. I didn't proceed any further. Magisk 20.4,crDroid 6.4.
MasterFURQAN said:
I was thinking the same. I'll reply with the results. Thanks
Click to expand...
Click to collapse
Sorry about the delay. I flashed the original stock boot from MIUI EU but the app still detects root somehow.
Any Guesses ?
amn1987 said:
I just installed Paytm First Games (Lite? ) and upon launching it asked to Login via OTP/Paytm. I didn't proceed any further. Magisk 20.4,crDroid 6.4.
Click to expand...
Click to collapse
Yup the lite version on the play store works but not the full version downloadable from their official website
So is there any solution to this??
How the paytmfirstgame (full version) deteck root after renaming magisk , passing safetynet and hiding app from magisk manager. I think magisk is now not a bigshot
Still can't open Paytm First Games even after using Magisk Hide
Any solution?
Facing the same issue. Do we have any solution on how to make the paytmfirstgames app work on rooted device?
Has anyone updated their Magisk version after initial install?
I'm on Magisk 22, and version 22.1 is available. I don't have a burning need for 22.1 but have found from experience that it's best to not lag behind too much; eventually some or other module will require a recent version.
I'm guessing it's similar to initial install, but done from within the Magisk app using 'Recovery Mode'. First for me doing this, so figured I'd ask about pitfalls to avoid from folks who have already done this.
EDIT: To answer my own question (since I'm so impatient), yes. Just remember to rename Magisk-v22.1.apk to .zip before rebooting to save you some time after Magisk reboot takes you to TWRP.
Arobase40 said:
This is indeed an important update so better do the update but prepare yourself to update more stuffs if you want to keep EdXposed and his modules working...
I didn't think about downloading Magisk-v22.1.apk and to rename to .zip before flashing it with TWRP so I had to update the Magisk manager before I could update Magisk itself.
After that you may or may not update the Riru and Riru edXposed modules as the edXposed was not working anymore for me . So I had to also update the edXposed manager.
And don't forget to reboot many times...
Finally you could also update the AFWall+ from the PlayStore... ^
Click to expand...
Click to collapse
All working well here with:
Magisk 22.1
Riru v25.3.3.r393.ed83041
Riru - EdXposed v0.5.2.2_4683-master
EdXposed Manager 4.6.2
Arobase40 said:
This is not related with the Magisk update but can you tell what is actually your Tab S6 SafetyNet status ?
Click to expand...
Click to collapse
I have no idea. I've never looked in to what it even means; sonething that is needed for some apps, from what I've read?
What do want me to look for?
Arobase40 said:
Well, to be short the SafetyNet status indicates what you can potentially do with a rooted device such as creating Secure Folder, installing and use banking apps, probably use Netflix or some other apps or features you would be able to run with a non-rooted device.
So, to know your SafetyNet status you simply have to open your Magisk manager and tap the "Verify SafetyNet" option on the Magisk welcomm screen. Then it may ask or may not ask you the permission to download external modules,do so and then it will tell you if you pass this test or not !
If I ask you that it because some weeks ago I passed all the test with my Tab S6 and my 2 Galaxy Note 9 and now they all fail for some unknown reasons and as I changed nothing in the Magisk environment and the edXposed environment except updating some Samsung and Google apps ! ^^
So I want to try to understand how it comes and when it comes this SafetyNet compatibility was broken... ^^
If other users could also check their SafetyNet status and indicate if there was a change it may help.
Click to expand...
Click to collapse
I tapped 'Check SafetyNet' and got (see screenshot). Not interested in going any further. I hope you understand. fwiw, I too have an S6 with all Google and most Samsung apps either frozen or deleted; at last count 149 of them.