[Xposed 88.1 sdk 25] Cannot activate modules - Xposed General

Hi,
I've installed the Xposed framework and installer.
I've installed several modules (in order to change IMEI) but I failed activating each one !
A text box shows "cannot write /data/user_de/0/de.robv.android.xposed.installer/conf/modulese.listjava.io.FileNotFoundException: /data/user_de/0/de.robv.android.xposed.installer/conf/modules.list(No such file or directory)" and even if the box is checked, the module doesn't work...
I've got a Samsung Galaxy S5 (klte). I's rooted by Supersu and recovery is TWRP. I recently updated my ROM to lineageOS 14.1 (18/10/17) but with an oldest version of that ROM it was fine.
What can I do to fix that issue ?
Tx

The same thing happens to me with the xposed version 87, any solution?

I think the issue is a rights problem.
I used a microSD card to extend the memory and the app could not write correctly in the extended memory to activate the module.
To fix it, I reinstalled the ROM without the microSD and now it's fine. After that, I put the microSD but I didn't merge it with the stock memory.
Guess it will help you

Related

[Q] No modules working

Hi all.
I installed the xposed framework to take advantage of the available modules. The framework seems to be installed correctly, but none of the modules I tried (after enabling and rebooting) works on my tablet. I uninstalled it and installed the latest stable version and added only one simple module (from which the attached log refers to) but still no luck.
I have a Vivitar XO tablet running 4.1.1, with what seems not to be the original rom (or at least, the original launcher and "environment" has been removed). It has only one storage partition (the storage tab in settings shows only sd card with the full capacity of the tablet, 4GB, and no internal storage). The installer app is installed in /storage/sdcard0/Android/data/de.robv.android.xposed.installer.
So, my questions are...
1 - Is my tablet incompatible with xposed and I should forget about it?
2 - I don't have the /data/xposed folder. Is that expected with the recent versions?
3 - Should I try to reinstall the framework using another method?
4 - Could it just be incompatibility with the modules I tried? If so, is there any module known to be fully compatible so I can test it?
Thanks a lot, any help appreciated
The framework seems to be installed and working correctly, looks like you're just trying incompatible modules.
/data/xposed isn't created/needed anymore.
I can't recommend one that's universally compatible, though.

[Q] no new modules working

hello, i am using xposed framework for many months, but from yesterday any module that i am installing is not working, all the modules that i have installed earlier are still working fine. Also new modules are being installed to sd card, it tried after moving them to phone, but still having the issues, Please help me.
Xposed modules cant work from SD card. Please double check it.
Plus, when you move them back to internal you have to deactivate and activate them in xposed installer again.

[HELP] No Modules Working

Hi,
I have been using Xposed for a Long time. The first time I downloaded it and installed the latest version, it would keep saying in red that the latest version still needs to be installed. After installing it all different ways, it still didn't work so I discovered that older versions might work. Ever since I have been using version 2.5.1.
Recently, because of the older version, I couldn't download and activate a lot of the modules because they required the later Xposed version so I decided to try fix it and now I'm using version 2.6.1.
I disabled resource hooks and it seemed to work. I'm now using the later version of Xposed and the red message doesn't appear anymore. However, NONE of my modules seem to be working now and I can't figure out why.
If anyone can help me that would be greatly appreciated!
Device: HUAWEI G610-U20
Android 4.2.1 JellyBean
I have attached my latest log file from Xposed.
If any other further information is required I will be happy to provide!
EDIT: one of my modules seem to have randomly started working but the rest still do nothing. They are activated and I have rebooted multiple times.
Anyone?
MasterReturnz said:
I disabled resource hooks
Click to expand...
Click to collapse
According to the log file, multiple modules require those hooks in order to work.
Code:
Loading modules from /data/app/com.elesbb.snapchatfullcaption-2.apk
Loading class com.elesbb.snapchatfullcaption.Xposed
This class requires resource-related hooks (which are disabled), skipping it.
It seems to me that you need to enable the hooks. There are also some other errors, which I can't figure out right now (tired...)
Someguyfromhell said:
According to the log file, multiple modules require those hooks in order to work.
Code:
Loading modules from /data/app/com.elesbb.snapchatfullcaption-2.apk
Loading class com.elesbb.snapchatfullcaption.Xposed
This class requires resource-related hooks (which are disabled), skipping it.
It seems to me that you need to enable the hooks. There are also some other errors, which I can't figure out right now (tired...)
Click to expand...
Click to collapse
If I enable resource hooks then Xposed doesn't work, it says I need the latest version them even tough I already have it installed.
Is there a work around for this?
Im trying to manually flash the ZIP file but I can't actually seem to flash the Xposed installer.zip file. It keeps saying installation aborted in recovery mode. How do I fix this?
Newest version is 2.7 of Xposed Installer. http://repo.xposed.info/module/de.robv.android.xposed.installer
The problem with using the latest version is that it doesn't work. My modules don't work unless I disable resource hooks but then only like 2 of them work
I want to know how to successfully install the latest version onto my phone because currently I can't flash the .zip file to my device. I can't use any custom recovery because there is none that support my device currently.
hi, im running Xposed on lollipop v3.0 aplha 2 !
what is the default setting for the "experimental disabled resource hooks" ?
should it be ticked by default or should it be unticked !
what is the default setting ?
shaajrocks said:
hi, im running Xposed on lollipop v3.0 aplha 2 !
what is the default setting for the "experimental disabled resource hooks" ?
should it be ticked by default or should it be unticked !
what is the default setting ?
Click to expand...
Click to collapse
By default, it should not be ticked.

Need help installing arm64 sdk23 on HTC10. Installed but currently not active.

Hi,
My goal is to successfully install the Xposed framework on the HTC10. I have a stock RUU ROM, unlocked the bootloader, installed TWRP recovery, and rooted it with Supersu with force encryption per Rootjunky.com videos on YouTube. Specifically, I'm using the xposed-v86-sdk23-arm64.zip, SuperSU-v2.71-forceencrypt_v2, TWRP-3.0.2-6-pme. Then I proceeded to install the Xposed framework and APK. It flat out dosesn't work. the Bin folder and log folders are empty and I receive "The latest version of Xposed is currently not active. Did you install the framework and reboot?" I have verified my root is working with a number of other apps. I have tried resolved the issue by executing the methods listed in this article: Can't post links yet cause I'm a noob. And they didn't work. I have completely wiped my device internal and external and tried rerooting and reinstalling and I still get the same result. I also have tried installing older version of the Xposed framwork. I have spend days troubleshooting it and I can't figure it out. No matter what I get the Currently not active.
Some of my reading points to the SE Linux Mode being set to "Enforcing" being the culprit as to why it is not working. I have no idea what this is. However, I can confirm that mine is set to Enforcing despite me executing all three steps in the aforementioned article. I installed that lean kernel so it should be set to permissive I would think but Device Control app shows otherwise.
When I click on Logs in the the Xposed Installer, it says Could not read log /data/data/de.robv/android/xposed.installer/log/error.log. I can confirm that it is installing something because the DE.ROBV.ANDROID.XPOSED.INSTALLER directory is there. And all of the sub directories are present. But bin and log directories are empty which I find odd. I would expect to see many files in there especially the Bin folder.
Any ideas how to resolve this without a log file? I'm sure the HTC10 is arm64 so that shoudn't be the issue. any ideas why this isn't installing correctly? Is it the SE Linux Mode? Do I need to S-Off of something? Any help appreciated!
Regards, Matt.:good:

MagiskHide doesn't work on "Mes Paiements" (PayLib)

Device: Samsung Galaxy Note9 (SM-N960F)
Android: 10 (Q)
ROM: N960FXXS4DTA5_DevBase_v7.1
Magisk : Canary 20306 (last build)
Manager : Canary 277 (last build + hidden)
Xposed: No
SafetyNet : OK (ctsProfile + basicIntegrity)
List of MagiskHidden apps: FateGO, Googlr Pay, La Banque Postale (Mes Paiements), Revolut, knox*, GMS
The app: https://play.google.com/store/apps/details?id=com.lbp.peps
Description:
Even with the latest version of Magisk and the app hidden, when I start the application, I always get a message telling me that the device has been rooted. (Error code 81)
Google Pay is working with the DB modification, Revolut is working, Fate:GO is working but I can't get Mes Paiements working. (So I can't even use my credit card on Internet :cyclops
What I tried:
I tried to unpack the APK and see what trigger the message that telling me the root is detected:
https://i.imgur.com/SWHD5iT.png
If you feel skilled/brave enough or if you have any clue, don't hesitate to tell me.
Same here, with LyfPay (Paylib), on OnePlus 6.
Works fine before Lyfpay last update.
Hi guys,
Same for me too with paylib (caisse d'épargne) with last update 1.8.0 from december.
The app just tell me it no more compatible with my phone...
Do you have "TWRP" folder inside root directory? Try to delete/rename it, reboot and try again.
Micdu70 said:
Do you have "TWRP" folder inside root directory? Try to delete/rename it, reboot and try again.
Click to expand...
Click to collapse
Same problem.
Did you manage to ride over the error 81 ?
marwanpro said:
Same problem.
Did you manage to ride over the error 81 ?
Click to expand...
Click to collapse
I don't use Paylib, but I know "TWRP" folder can be detected for some apps and block them.
Try to download Mes Paiements and try to dodge the error
(L'erreur s'affiche instant au démarrage de l'appli, donc t'es vite fixé)
marwanpro said:
Try to download Mes Paiements and try to dodge the error
(L'erreur s'affiche instant au démarrage de l'appli, donc t'es vite fixé)
Click to expand...
Click to collapse
I can go to "Activation" screen without any issue.
I enabled Magisk Hide for "La Banque Postale" before starting the app.
I use latest Stable Magisk (20.3) with "Hide Magisk Manager" option (rename Magisk Manager app to something else).
You can try to clear app data of this app too.
EDIT: Don't remember why but I renamed any "Magisk" word from filenames in phone's memory too (e.g.: Magisk zip installer and uninstaller).
Hi,
For me, LyfPay app (Paylib Crédit Mutuel), no problem to launch and use Credit Mutuel app and LyfPay app, I can pay with flashcode but I can't pay with NFC.
I enabled Magisk Hide for "Crédit Mutuel" and 'Lyfpay" before starting the app.
I use latest Stable Magisk (20.3) with "Hide Magisk Manager" option (rename Magisk Manager app to something else).
I've cleared app data of Lyfpay app.
However, I'll test by changing the name of TWRP directory and all Magisk filenames...
I'll keep you informed !
Thanks.
It doesn't change...
Rename all files and directories of TWRP and Magisk. Hide Magisk, apps.
I've send a mail to the app contact, they tell me that my phone was rooted... They see the root by an another way...
Hello,
Same for me with Paylib (Caisse d'Epargne).
The old 1.7.1 version works with my Galaxy S8 with Android 9.
But no matter what I try, on my new Galaxy S20, it does not work...
Hello,
I have the same issue (Paylib Caisse d'Epargne), i have tried everything you told in this topic. Nothing work ....
Someone have the solution ?
I do not know if the following will be useful for your issue, but this is how I get my root be hidden from the Crédit Mutuel (CM) app.
I have a Lineage OS 16 (Android 9) running on my Samsung A5 2017 device with Magisk 20.4 and Magisk Manager 7.5.1 installed (with of course Manager hidden by a random package name and the CM app processes checked in Magisk Hide).
Despite all that and after cleaning the CM app storage data and cache, and even after a fresh reinstallation of the CM app, rebooting, etc..., my CM app still started by the warning that my phone was rooted !
Actually, my Samsung phone uses two storage: the internal one (32 Gb) and a Samsung SD card (32 Gb), formatted as extended internal storage.
The CM app was installed on the SD card rather than the native internal storage, along with some installation files I used for rooting the phone (including the magisk.zip and magisk_manager.apk files).
Here is what worked fine for me:
- First, after reading your discussion above, I deleted the previous installation files from the SD card, because those files could indicate that Magisk or whatever rooting methods had been applied on my device.
- Second, and this may be what resolved the issue for me, I moved the CM app from the SD card to the native internal storage, so that it is now installed on a separate storage than the Magisk Manager packages.
Well, now I have a functional root that the CM app does not see anymore.
I don't have a separate SD slot... I deleted files but still don't work.
bolo59 said:
I do not know if the following will be useful for your issue, but this is how I get my root be hidden from the Crédit Mutuel (CM) app.
I have a Lineage OS 16 (Android 9) running on my Samsung A5 2017 device with Magisk 20.4 and Magisk Manager 7.5.1 installed (with of course Manager hidden by a random package name and the CM app processes checked in Magisk Hide).
Despite all that and after cleaning the CM app storage data and cache, and even after a fresh reinstallation of the CM app, rebooting, etc..., my CM app still started by the warning that my phone was rooted !
Actually, my Samsung phone uses two storage: the internal one (32 Gb) and a Samsung SD card (32 Gb), formatted as extended internal storage.
The CM app was installed on the SD card rather than the native internal storage, along with some installation files I used for rooting the phone (including the magisk.zip and magisk_manager.apk files).
Here is what worked fine for me:
- First, after reading your discussion above, I deleted the previous installation files from the SD card, because those files could indicate that Magisk or whatever rooting methods had been applied on my device.
- Second, and this may be what resolved the issue for me, I moved the CM app from the SD card to the native internal storage, so that it is now installed on a separate storage than the Magisk Manager packages.
Well, now I have a functional root that the CM app does not see anymore.
Click to expand...
Click to collapse
Thanks for your reply Bolo59, but I think we have all the same problem, not with the bank app (Crédit Mutuel, Banque Postale, Caisse d'épargne, ...) but with the NFC pay app (Lyfpay Crédit Mutuel, Mes Paiements La Banque Postale, Paiement mobile Caisse d'épargne, ...).
Latest NFC Pay Apps since February detect root.
Hi, I just installed LineageOS 17.1 (in order to get better OS with less bugs... I don't care about root etc.) on an umidigi F1 with Magisk but I cannot access to "Credit Mutuel" app anymore even with this app addede to the Magisk hide list (with magisk hidden, renamed, TWRP directory removed etc.).
The app still recognized the rooted device.
How did you do in order to get it working? Otherwise does someone knows how could I debug it?
Teetoow said:
Hi, I just installed LineageOS 17.1 (in order to get better OS with less bugs... I don't care about root etc.) on an umidigi F1 with Magisk but I cannot access to "Credit Mutuel" app anymore even with this app addede to the Magisk hide list (with magisk hidden, renamed, TWRP directory removed etc.).
The app still recognized the rooted device.
How did you do in order to get it working? Otherwise does someone knows how could I debug it?
Click to expand...
Click to collapse
I'm stilll searching to get Crédit Mutuel from the latest version working on my device.
The latest version working with the now called "Zygisk" (the new Magisk Hide) is the V9.13.0.
You can download it via Aptoide.
Hey there.
Magisk 25.1 with Zygisk, LSPosed and Shamiko installed and configured. XPrivacyLUA with most restrictions on Paylib app. Shamiko on blacklist configured, but Paylib still detects root.
I have no clue what to do more to pass the check…

Categories

Resources