Modules not active after hard reboot! - Xposed General

I'm using Xposed 2.6.1 (libraries used StickyListHeaders & libsuperuser)
All modules are activated, reboot, etc... The modules never get activated with a normal reboot.
If I do a soft reboot, then they all work...
None of them work with a hard reboot.
All modules are last versions... they are installed on internal memory.
I' tried to uninstall and reinstall * reboot for both modules & even Xposed. Same results.
It seems that I'm not the only one having that issue, but have search for real solution without success.
I do have a phone with Android 4.2.2, Kernel 3.4.5 ([email protected] #1 Tue Jan 13 16.55:43 CSST 2015 / Build number ALPS.JB3.MP.V1
Here is attached the Xposed error log file.
Please help, as I'm sure it will help a lot of other users.
Thanks,
Jean-Frederic

Solved !
Ok, got it solved in between... but I'm back here to explain what happened as it can help others.
I thought the modules were moved to internal memory by pressing the appropriate button in the application options, but when I did move it, the modules was still active in Xposed.
So I guess that the move was not done completely or correctly.
So I uninstalled the module (GravityBox[JB]), then re-installed it and moved it to internal memory BEFORE activating it.
Then reboot, then activation in Xposed, then reboot... then Tadada !!!! it works perfectly even with hard reboot.
Hope this help,
Jean-Frederic

Related

[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.

Xposed installer crashes on opening any module in the download section

Hello!
I have a problem described in the topic.
My device is Samsung GS4 Active running stock 4.4.2 KK, rooted.
Until yesterday I had a working Xposed installer (2.7experimental) with half a dozen modules, namely: Amplify, AppOpsXposed, Lucky patcher, One++, Vk hack and of course Wanam Xposed.
And yesterday I got rid of all the Google stuff. Deleted all Google *** apps, including GP market and GP services. Migrated to 1Mobile Market.
And after that Xposed installer (itself, not the modules) started to crash on doing the following:
1) start Xposed installer, 2) click Download section, 3) click ANY module there including the framework itself.
So I get "Unfortunately, Xposed Installer has stopped".
The error log does NOT have anything about the crashes.
What has been done to avoid this behavior:
- cleared dalvik-cache
- wiped cache partition
- uninstalled an installed back different versions of Xposed installer (2.6.1 & 2.7experimental)
- activated and deactivated all 6 modules installed
Luckily, ALL the modules work perfectly, they have been successfully activated in Xposed installer every time I reinstalled the app.
So my question is: does anyone know what to fix so to make the Installer open the modules in Download section without crashes.
Thank you in advance. Sorry for my English
a.warlamov said:
Hello!
I have a problem described in the topic.
My device is Samsung GS4 Active running stock 4.4.2 KK, rooted.
Until yesterday I had a working Xposed installer (2.7experimental) with half a dozen modules, namely: Amplify, AppOpsXposed, Lucky patcher, One++, Vk hack and of course Wanam Xposed.
And yesterday I got rid of all the Google stuff. Deleted all Google *** apps, including GP market and GP services. Migrated to 1Mobile Market.
And after that Xposed installer (itself, not the modules) started to crash on doing the following:
1) start Xposed installer, 2) click Download section, 3) click ANY module there including the framework itself.
So I get "Unfortunately, Xposed Installer has stopped".
The error log does NOT have anything about the crashes.
What has been done to avoid this behavior:
- cleared dalvik-cache
- wiped cache partition
- uninstalled an installed back different versions of Xposed installer (2.6.1 & 2.7experimental)
- activated and deactivated all 6 modules installed
Luckily, ALL the modules work perfectly, they have been successfully activated in Xposed installer every time I reinstalled the app.
So my question is: does anyone know what to fix so to make the Installer open the modules in Download section without crashes.
Thank you in advance. Sorry for my English
Click to expand...
Click to collapse
Found your old question after having the same problem, with no answer. Later, I realized (from reading xposed installer logs) that the problem was me previously "integrating into ROM" (with Titanium) what is called "Android System Webview" app.. I had problems "undoing" the integration, ended up re-installing it from the Market... but now it works.
So I'm leaving this here: if the installer closes on opening stuff in Modules tab, check your WebView.
Hello friends, I'm running Marshmallow 6.0 on my Oneplus One phone and I need xposed framework... but after flashing it (xposed-v89-sdk23-arm), my phone app stopped working, no access to contacts, favorites... nothing! I tryied even with xposed-v88-sdk23-arm version, but the same.... No phone app access. So, I cannot use my phone with xposed framework flashed on it! Will anybody help me solve this horrible problem, please? Thank you.
almost same question here. My sdk is 22
Running xposed installer after installation makes my phone to soft-reboot
Try force stopping Xposed Installer app, then clear cache and data for app, then restart app and see what happens. Also ask in section for your phone model/ROM if still happening.
Yakimus said:
almost same question here. My sdk is 22
Running xposed installer after installation makes my phone to soft-reboot
Click to expand...
Click to collapse
The posts #3-5 should be in different threads, but i have the same problem as OP, an old device with Android 4.4.2, XI 2.6.1. XI will stop/crash when i try to open any module in the download section.
Also have Titanium backup installed... but i have no app called "Android System Webview". Is it something i should install for Xposed Installer? I never had this problem before but haven't updated for a while, so i'm trying to get some things updated. Thanks
I finally found that the problem was that I had Download Manager disabled. Enabling/(defrosting it with Titanium) has allowed XI to work again!

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:

[HELP] Xposed installed but not active on Oreo

I'm sorry for my poor English..:crying:
This problem has been questioned a lot but I still can't find an answer suitable for me.
I upgraded my LineageOS 14.1 to 15.1 yestdoday with wiping system, cache and dalvik cache, and data not wiped. And install magisk xposed 90.2, but it said 'framework installed but not active'.
I tried reboot (not soft reboot) my phone, then every thing keeps FC.
After a soft reboot, every thing seems to work fine, and Xposed Installer said framework is active. But some modules said 'module not active' while others work perfectly.
Modules not work: QXposed (for QQ), WeXposed (for WeChat), FingerprintPay (for payment apps)
Modules work: Xposed Edge, Android Phone Vibrator, Greenify, InstantFaceUnlock, etc.
Why I got this problem?
In a word, xposed doesn't work after a reboot (via app or power button), but works after a soft reboot. And modules that target for apps (not for system) don't work.
Thx very much!

Magisk Manager Has Stopped. (Crashing on open)

Phone: LG Aristo (LGMS210)
ROM / Android version: Android 7.0
Root (yes/no): Yes
Xposed, or any other modifications: no
Any physical damage prior to defect: no
Magisk Manager keeps stopping. I opened it today and I got the message "Magisk Manager has stopped, open app again" I can't open it without it crashing. I've tried clearing cache, clearing data, reinstalling the APK. What do I do? This is a very big problem as i cannot run any rooted apps without getting the message that magisk has stopped.
Logcat (use ADB)?
Have you tried uninstalling Magisk and then reinstalling?
Have you tried uninstalling Magisk and then reinstalling?[/QUOTE]
I have tried clearing data, clearing cache, and uninstalling and reinstalling. I am VERY new to this so any help is good help.
MMJv3 said:
I have tried clearing data, clearing cache, and uninstalling and reinstalling. I am VERY new to this so any help is good help.
Click to expand...
Click to collapse
When you say you've uninstalled and reinstalled, are you talking about Magisk or the Magisk Manager? I'm talking about completely uninstalling Magisk by using the uninstall zip.
And what about that logcat?
I've got a similar problem. Mgisk Manager keeps crashing, but If I'm not connected to the internet the APP runs fine,
dafreaking said:
I've got a similar problem. Mgisk Manager keeps crashing, but If I'm not connected to the internet the APP runs fine,
Click to expand...
Click to collapse
Likely caused by a bug with checking the Magisk repo. It's been fixed but not yet released.
Clear Repo Cache
Disconnect from internet, go to settings and clear the repo cache helped me to open it again
Didgeridoohan said:
When you say you've uninstalled and reinstalled, are you talking about Magisk or the Magisk Manager? I'm talking about completely uninstalling Magisk by using the uninstall zip.
And what about that logcat?
Click to expand...
Click to collapse
I am facing the same issue. Magisk Manager crashes as soon as I open it (precisely within 3-5 sec of opening the app). Though the root is working perfectly and all apps requiring root behave as intended.
I am attaching a magisk log taken from the magisk manager within the 3-5 seconds window.
Kindly let me know if it's the correct log. I am a noob and still learning the intricacies.
Any help/guidance will be greatly appreciated
Magisk Manager works for me when I wait for a few seconds after opening the app. Cool Tool shows high CPU activity right after starting MM. Once the CPU idles again, MM works without crashing.
This is not a fix, but it may help until a new version gets released.
Didgeridoohan said:
Likely caused by a bug with checking the Magisk repo. It's been fixed but not yet released.
Click to expand...
Click to collapse
v5.8.0 just released does fix this.
Didgeridoohan said:
Logcat (use ADB)?
Have you tried uninstalling Magisk and then reinstalling?
Click to expand...
Click to collapse
Hi, Magisk crash when I go to download and try to search any moudle under it as soon I type two three words it crashes , I tried to use 16.7, 17.1 fresh install but still it does the same
I dont have any xposed root works fine, Im on crDroid Oreo running on g900v unlock bootloader
zfk110 said:
Hi, Magisk crash when I go to download and try to search any moudle under it as soon I type two three words it crashes , I tried to use 16.7, 17.1 fresh install but still it does the same
I dont have any xposed root works fine, Im on crDroid Oreo running on g900v unlock bootloader
Click to expand...
Click to collapse
I encounter the same issue today !!
eric672913 said:
I encounter the same issue today !!
Click to expand...
Click to collapse
Enter this url in the Magisk Manager settings, update channel,custom:
https://bit.ly/2MPKGY5
zfk110 said:
Enter this url in the Magisk Manager settings, update channel,custom:
https://bit.ly/2MPKGY5
Click to expand...
Click to collapse
Great! Thanks a lot.
For those of you that remain stuck on this issue: Magisk Manger doesn't like being used from an external SD card. If that is the case (see app menu) move it back to internal memory. It will work properly then.
JoostA said:
For those of you that remain stuck on this issue: Magisk Manger doesn't like being used from an external SD card. If that is the case (see app menu) move it back to internal memory. It will work properly then.
Click to expand...
Click to collapse
Thanks for this! Was exactly my problem.
Phone: Sony Xperia Z3 Compact (D5803)
ROM / Android version: Android 7.1.2 (LineageOS)
Root (yes/no): Yes
Xposed, or any other modifications: AFwall+ 3.0.4 (IPv6 disabled)
Any physical damage prior to defect: no
After flashing new LineageOS + Magisk.zip and installing the Magisk Manager Apk, the app is also crashing with no internet connection for me. But if I make airplane mode on, then it does work for me.
Magisk not opening or crashing again and again.
First of all desable or uninstall your superuser app and then open magisk manager app again it's very simple. When you done all of magisk installation then you can again activate or install your superuser app.
If it is not working then please tell me i can help you.
Nexus 6, 7.1.1, Magisk root - Google play and Magisk Crashing
Making a long story as sort as I can my Nexus 6 running Magisk to hide the root from Google play, and a stock 7.1.1 ( 7.1.1 (N6F27M, Oct 2017 if it matters) google image, was working flawlessly a couple years ago when I stopped using it.
A few weeks ago I turned it on, clicked Google play and it never opens. Just hangs on the app loading screen unless I disconnect the internet from it. I read somewhere that this may be an issue from something that Google implemented since then In there play services to detect root.
Connected to the internet (WiFi) I opened Magisk and was able to update the Manager app before it quickly crashed. I opened it again and there seems to be a Magisk update but app crashes too fast for me to click update.
What is going on here and/or how do I fix this?
Nexus 6, 7.1.1, Magisk root - Google play and Magisk Crashing SOLVED
jhavron said:
Making a long story as sort as I can my Nexus 6 running Magisk to hide the root from Google play, and a stock 7.1.1 ( 7.1.1 (N6F27M, Oct 2017 if it matters) google image, was working flawlessly a couple years ago when I stopped using it.
A few weeks ago I turned it on, clicked Google play and it never opens. Just hangs on the app loading screen unless I disconnect the internet from it. I read somewhere that this may be an issue from something that Google implemented since then In there play services to detect root.
Connected to the internet (WiFi) I opened Magisk and was able to update the Manager app before it quickly crashed. I opened it again and there seems to be a Magisk update but app crashes too fast for me to click update.
What is going on here and/or how do I fix this?
Click to expand...
Click to collapse
Updated Magisk Manager and was able to download the updated apk using the manager. I then rebooted to recovery and installed the new APK, cleared delvik, & cache, rebooted. Bam! SOLVED

Categories

Resources