Is edxposed working on the 7T Pro? It says active in edxposed manager but none of the modules work.
<img src="https://i.ibb.co/C6bgSfD/Screenshot-20191111-080435.jpg" alt="Screenshot-20191111-080435" border="0">
BlazingKahn35 said:
Is edxposed working on the 7T Pro? It says active in edxposed manager but none of the modules work.
<img src="https://i.ibb.co/C6bgSfD/Screenshot-20191111-080435.jpg" alt="Screenshot-20191111-080435" border="0">
Click to expand...
Click to collapse
You could try the Solohsu magisk linked in this message: https://forum.xda-developers.com/showpost.php?p=80789095&postcount=73
s3axel said:
You could try the Solohsu magisk linked in this message: https://forum.xda-developers.com/showpost.php?p=80789095&postcount=73
Click to expand...
Click to collapse
It works now thank you so much bro
BlazingKahn35 said:
It works now thank you so much bro
Click to expand...
Click to collapse
Hi is it possible to share what file you downloaded on the links and how you installed cause when I download I get a file that Majisk doesn't recognize and I can't figure how to load into Edexposed. I'd appreciate any help you can give me. Thanks
You can just use normal Magisk solohsu is not needed anymore
I've got EdXposed installed successfully with the latest Yahfa beta - framework is active (blue).
Just tried the 'Exi for SwiftKey' module - does not work (not sure if this particular module supports Android 10 a last updated on 07-12-2019).
elmor0 said:
I've got EdXposed installed successfully with the latest Yahfa beta - framework is active (blue)....Just tried the 'Exi for SwiftKey' module - does not work (not sure if this particular module supports Android 10 a last updated on 07-12-2019).
Click to expand...
Click to collapse
Had similar issues with other modules like XprivacyLUA, installing Edxposed canary (presently 4.6.1(4504) solved that ....
EdXposed app crash when I have the magisk modules installed. Without the magisk modules, it dont crash.
Anyone can help? I followed instructions from EdXposed website
Why im getting this error and how to fix
Hi, though I was excited to successfully install Edxposed I had to uninstall it. I was looking forward to be able to further customize my phone by using Gravitybox and XUImod but all they did was get my phone out of whack. Maybe later on when TWRP is fully developed for our phones we can install custom ROMS with integrated customization.
1+ 7t pro, latest beta YAHFU, latest Canary build of Magisk.
The Magisk module is installed and Edxposed Manager reports it's working.
Xposed modules are active, but none of corresponding applications (Lucky Patcher, AFWall, GravityBox, 3C AIO) see the active module.
So the result is: not working.
Deleted.
GrayJack said:
1+ 7t pro, latest beta YAHFU, latest Canary build of Magisk.
The Magisk module is installed and Edxposed Manager reports it's working.
Xposed modules are active, but none of corresponding applications (Lucky Patcher, AFWall, GravityBox, 3C AIO) see the active module.
So the result is: not working.
Deleted.
Click to expand...
Click to collapse
Next time try wiping cache of edexposed manager app and turning modules off then on and rebooting. If that doesn't work try reflashing riru core in magisk, don't reboot then flash edexposed canary. Then reboot
Related
It tries to load the framework and then it says Gravitybox has stopped working, it will close now.
The same problem as here:
http://forum.xda-developers.com/showthread.php?t=2529641
That fix didn't work for me.
Doesn't work on stock ROM
Sent from my Pixel C using Tapatalk
xposed and gravitybox also work sin stock rom.
use xposed v 82 sdk 32
and before you flash it use selinuxmodechanger.
you also can read it on the xposed thread.
xposed needs permissive selinux mode
and our kernel has enforcing mode. thats why it dont work
I have Xposed already installed.
skeleton1911 said:
xposed and gravitybox also work sin stock rom.
use xposed v 82 sdk 32
and before you flash it use selinuxmodechanger.
you also can read it on the xposed thread.
xposed needs permissive selinux mode
and our kernel has enforcing mode. thats why it dont work
Click to expand...
Click to collapse
Hi
Rooted stock rom.
From the official xposed xda page, I installed xposed installer, then flashed framework sdk23 (marshmallow), arm64 v84.
Xposed says 'not compatible with sdk version 23 or your processor architecture (arm64-v8a)'.
Is it the selinuxmodechanger that i haven't installed (yet) or will v84 not work anyway?
arlrb said:
Hi
Rooted stock rom.
From the official xposed xda page, I installed xposed installer, then flashed framework sdk23 (marshmallow), arm64 v84.
Xposed says 'not compatible with sdk version 23 or your processor architecture (arm64-v8a)'.
Is it the selinuxmodechanger that i haven't installed (yet) or will v84 not work anyway?
Click to expand...
Click to collapse
You're using the wrong version of xposed installer, you need v3.0-beta4.
Jonny said:
You're using the wrong version of xposed installer, you need v3.0-beta4.
Click to expand...
Click to collapse
Thank you, Jonny.
In case anyone else runs into this problem, it's the material design version by DVDandroid.
If you have any other version already installed, uninstall it first.
arlrb said:
Thank you, Jonny.
In case anyone else runs into this problem, it's the material design version by DVDandroid.
If you have any other version already installed, uninstall it first.
Click to expand...
Click to collapse
So, you downloaded the app and clicked on INSTALL/UPDATE with framework "xposed-v84-sdk23-amd64" and that's it?
xposed Qs
llucax said:
So, you downloaded the app and clicked on INSTALL/UPDATE with framework "xposed-v84-sdk23-arm64" and that's it?
Click to expand...
Click to collapse
Yes, that was it. It will auto-shutdown & auto-flash in TWRP, then restart & it should be done.
However, xposed installer says, in green, that sdk23 arm64 is active, yet, i'm not sure if a couple of modules i've tried are working properly/at all.
Minminguard module (ad blocker) for instance says that xposed is not enabled, & sure enough ads are still popping up in apps & in chrome.
So i'm wondering if certain modules won't work seeing as i'm using the latest installer & sdk/64? ie do the module developers need to keep up?
Can someone shed some light on how it works in that respect?
Should i try the 32bit sdk? (all 32bit sdks will work on a 64bit cpu, won't they?)
Or should i try a different version - 82?
Is there a version that is most reliable for most modules?
Same results in here, I guess we have to change the SELinux mode somehow for it to work according to what I've read somewhere else...
llucax said:
Same results in here, I guess we have to change the SELinux mode somehow for it to work according to what I've read somewhere else...
Click to expand...
Click to collapse
As skeleton1911 wrote "and before you flash it use selinuxmodechanger". That fixed most of my problems, I also use xposed V84, haven't tried V85 though
there is a solution for xposed by skeleton1911
---------- Post added at 02:25 PM ---------- Previous post was at 02:22 PM ----------
skeleton1911 said:
Guys
there is a solution for xposed:
1. with mixplorer go to system/etc/init.d/ 07permissive and open it with editor (just tap on it)
2. remove the sleep 60 line. save and reboot to recovery
3. flash xposed framework , reboot and install xposed app and your modules. enable them in xposed app and reboot (normal xposed procedure)
4. open your apps like gravitybox etc.. ( they will connect to the xposed framework now)
5. open 07permissive again in system/etc/init.d and add sleep 60 into it again
6. save and reboot
Done!
in short words:
the cause is permissive and enforcing. Xposed only run in permissive mode on boot , but permissive mode forces some apps to close , but it is needed for viper v4a so i did this init.d script, system boots in enforcing and after 60 sec it will switch to permissive.
this is a dirty but working method. there is no other way at the moment because elephone didnt released the kernel source to modify it..
1. remove sleep 60 in 07permissive , save and reboot
2.perform the xposed stuff and after reboot open all xposed apps so they can connect to the xposed framework
3. add sleep 60 back into 07permissive and reboot
All works now!
cheers!
p.s: I will make a flashable zip for that soon
Click to expand...
Click to collapse
Do it anybody probe it? Maybe Do it working?
That's for his custom rom. For the stock rom you need selinuxmodechanger, set it to permissive and soft reboot via xposed. It will work fine then!
Aha, thanks, I didn't know what is the difference
Jtig said:
That's for his custom rom. For the stock rom you need selinuxmodechanger, set it to permissive and soft reboot via xposed. It will work fine then!
Click to expand...
Click to collapse
Mmm, OK, maybe is the soft reboot what I missed, because I used selinuxmodechanger and it didn't work with a full reboot. I am using stock but with RodriguezMod, but I think I will try the Eragon ROM. I'll report back. Thanks!
I'm finally trying the Eragon ROM, and following the steps from skeleton1911 finally seem to be working! At least Amplify for the first time is not complaining about not having Xposed. So I wiped, flashed the ROM, updated the SuperSU binary, rebooted, remove the sleep from the init.d script, went to the Xposed installer Material beta, updated from v82 to v85 using the installer, and after that flash, Amplify started to recognize Xposed!
Jtig said:
That's for his custom rom. For the stock rom you need selinuxmodechanger, set it to permissive and soft reboot via xposed. It will work fine then!
Click to expand...
Click to collapse
That fixed it, thanks.
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.
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?
I was curious to see what Magisk modules are working on stock rooted rom? Is there any Xposed functionality? I have a few Magisk modules working, the Google Product Sans font installer, G Visual mod, QuickSwitch, Sony Music Player and xmlpak modules are all confirmed to be working on my Stock Rooted US variant. What Magisk modules are you all using?
Magisk:
-None Display Cutout
Xposed:
-GravityBox (q)
magisk: systemless hosts
that's the only module i use for adaway
confirmed Not working: viper4android ( device bootloops)
3dekstron said:
Magisk:
-None Display Cutout
Xposed:
-GravityBox (q)
Click to expand...
Click to collapse
so xposed is confirmed working?
That's how it works, you need magisk modules: Riru (Riru-core) and Riru Ex-Xposed (YACHFA or SANDHOOK both work).
My modules:
Magisk
-None Display Cutout
-Riru (Riru-Core)
-Riru Ex-Xposed
-Systemless host
Not working - Miracast enabler - bootloop
Xposed:
-GravityBox (q)
I dont see xposed even mentioned anywhere else in this forum. How did you guys install it? In Magisk, i see 'official xposed framework' 'xposed framework (dalvik)' 'riru - edxposed (sandy hook) and 'riru - edxposed (yahfa).
Which one of these do I install? I just want to run gravity box for the most part.
Magisk modules
1 ."Riru (Riru-core)"
2."riru - edxposed (sandy hook)" or " riru - edxposed (yahfa)"
3dekstron said:
Magisk modules
1 ."Riru (Riru-core)"
2."riru - edxposed (sandy hook)" or " riru - edxposed (yahfa)"
Click to expand...
Click to collapse
any clue why its failing for me? I installed riru first. But when i try to install edexposed (either of them) it fails and says i need to install riru first.
I assume "riru core" is the plain "riru"? Or do i need to install everything labeled riru?
Or is that flashing from within magisk doesnt work? do i need to download everything and flash in twrp or something?
cnoevl21 said:
any clue why its failing for me? I installed riru first. But when i try to install edexposed (either of them) it fails and says i need to install riru first.
I assume "riru core" is the plain "riru"? Or do i need to install everything labeled riru?
Or is that flashing from within magisk doesnt work? do i need to download everything and flash in twrp or something?
Click to expand...
Click to collapse
It was working for me until "Riru - Core" got an update that, among other things, renamed the module to just "Riru." And the Riru EdXposed module seems to be looking for something with the name "Riru - Core," but since that's not the name anymore, it fails. So just wait for an update to the Riru EdXposed modules and it should work again.
_huck_ said:
It was working for me until "Riru - Core" got an update that, among other things, renamed the module to just "Riru." And the Riru EdXposed module seems to be looking for something with the name "Riru - Core," but since that's not the name anymore, it fails. So just wait for an update to the Riru EdXposed modules and it should work again.
Click to expand...
Click to collapse
by chance, do you know of another way to map nav buttons? Im really just looking to get long press back button kill app. and long press recent button to take screen shot. double press recent button to open split screen
cnoevl21 said:
by chance, do you know of another way to map nav buttons? Im really just looking to get long press back button kill app. and long press recent button to take screen shot. double press recent button to open split screen
Click to expand...
Click to collapse
There are plenty of apps on the Play Store that allow you to remap those buttons.
_huck_ said:
There are plenty of apps on the Play Store that allow you to remap those buttons.
Click to expand...
Click to collapse
Those apps are for hardware buttons. I have the moto g power. only virtual buttons
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.