I've got a rooted J700m with Magisk installed, latest firmware and Xposed Installer Meterial Design by dvdandroid.
I think I've done everything correctly, but in the midle of the way, my Xposed framework stopped working. I was messing with unroot supersu to enable Magisk, then I was updating Xposed framework and installing some modules on Magisk.... anyways.
My problem is Xposed Framework is installed but not active. I've searched for solutions, but nothing seems to work.
Even the Xposed Installer error log is empty.
Related
Hi,
I'm trying to inject an Xposed module in a rooted phone with SuperSu configured as "disabled" .
I could download and install Xposed and the corresponding modules with SuperSu "enabled", but I'm wondering if the Xposed modules will actually work when SuperSu is in "disabled" mode.
Specifically, could I inject an Xposed module in a specific app(I.E. angrybird and such) when SuperSu is disabled?(assuming I already downloaded and installed the Xposed module when SuperSu is enabled)
Also, if it is not possible, is there any alternative I can use to dynamically inject code into a running app?
Thanks!
Anyone?
Edit : Nevermind. I tried it and it works!
So I can load install Xposed modules and have my phone unrooted afterwards.
Thanks!
What version Xposed Framework is work? I tried to install 2.6.1, but the modules are not working. I tried to restart the device and installed the module and Xposed to the device, but without success.
Please help me, without which I am unable to use the xposed as normal xposed is not Systemless and I am unable to use the IRCTC app as it now uses the safetynet for checking device compatibility. I have already tried different ways but nothing is working...
Exposed framework must be installed from twrp as a special zip file. Also should be uninstalled with same way (uninstaller zip) it cannot be installed on j7 with normal method.
May be you can install twrp then exposed.zip without rooting your system.
make a backup and give a try.(at your own risk )
I installed xposed but system doesnt boot on SM-G610F Nameless ROM V2
I Tried Magisk
But
I couldn't Succeed
Hello. I have a t mobile galaxy s6 on android 7.0 stock it is rooted has twrp and super su.
I really want to get xposed to use a module called ehi opener to unlock http injector ehi files. I installed the xposed apk downloaded the zip file and installed it. Im surprised the phone didn't hang on a bootloop it finished booting and when i checkes the xposed app it says that xposed is installed but none of the modules i try works. Aftet i select a module and reboot the phone nothing happens. When i tried the 4g/lte icon switcher did not do anything. And when i tried the ehi opner for http injector when i launch http injector it give me a security (-1) error and it tells me to uninstall the module
Does anyone know any custom rom where xposed and the modules work for smg920t
Anyone give me any info on where I'm going wrong or why it isn't working?
So I'm on Android 9 - Running stock OS, rooted with Magisk 19.4, custom Kernel SJ1 (MentalMusos)
I've installed both Riru Core (v19.5) and Riru EdExposed (v.0.4.5.1 beta (tried both Yafta & Sandyhook)) via Magisk and installed the XposedInstaller (by dvdandroid) but each time the app tells me the Xposed Framework is not installed. The app also prompts me to update it, which just returns a parsing error.
Also, not sure if relevant, but if I try to flash Riru Core or EdExposed modules via TWRP I get an "unable to mount system" error?
Thanks for any help guys.
Sorry posted in wrong section, thought I was in Q&A. ?*
Update for anyone that's interested...
Managed to get EdExposed installed. Seems DVDandroids apk, is specifically for Xposed. I used the wrong APK the entire time, you need to get the APK from the Magisk module instructions which is specifically for EdExposed (EdExposed Manager by ElderDrivers) - How I didn't notice they were different APKs is shocking and I guess I deserved the bootloop I got. I Think the mishmash of modules I had installed and uninstalled probably caused that. Or maybe because I aborted the setup process that Tab entered into once it rebooted. Learning experience I guess.