Related
As the title stated, I keep getting the message, "Unfortunately, the process com.google.process.gapps has stopped." When I press OK, it happens again after less than a second.
I'm on the latest 5.1 OTA b/l unlocked with sunshine and rooted, Xposed installed with GravityBox, lucky patcher, material Xposed installer (themes Xposed app), and amplify installed. Also BusyBox.
I tried removing Amplify, I tried flashing the Xposed disabler package, and still the same problem.
Oh, ps, possibly related problem, my phone doesn't show up in windows explorer when plugged in now, however I was able to get ADB by using device manager to select an ADB driver.
Any advice?
SOLVED:
Downloaded the latest OpenGApps package from here (pico, since the goal was just to reinstall services framework and play services) and flashed. Problem solved!
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!
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
DESCRIPTION
If you have the Pixel Experience module installed on your phone and installed Google Phone from the Play Store or ever tried to use a patched Google Phone version (such as this one), you may have noticed that Google Phone force closes when you try to search for a contact or while opening the keypad. This Magisk module attempts to fix that and it works by replacing your non-AOSP contacts storage with Google's own version, the one supported by Google Phone.
IMPORTANT NOTES
Supports Android versions from Android 7 (Nougat) to Android P.
It will remove any phone/dialer/contacts/people applications from your phone (if supported) because they are incompatible with Google's Contacts Storage.
You should only install this module if you want/need to use Google Phone and Google Contacts.
TESTED/SUPPORTED DEVICES
HTC 10 (Sense based ROMs).
Note: It should work with other devices but I have no means no test them myself, I can only rely on the community to test this for me.
SPECIAL INSTRUCTIONS
Install the Magisk module as usual but DO NOT reboot your device just yet.
Go into "Settings » Accounts & Sync" and disable "Automatically sync data".
Go into "Settings » Apps" a, look for "Contacts Storage" (it's a system app) and clear application data.
Reboot your device now!
Go into "Settings » Accounts & Sync" and enable "Automatically sync data".
Google Phone should now work without force closing, hopefully.
Note: If you ever want/need to disable this module, you should also follow the procedure above (disable module, disable data synchronization, clear contacts storage data, reboot, and re-enable contacts synchronization).
DISCLAIMER
Install this module at your own risk.
Developer is not responsible for what you do on your device.
Please take all necessary precautions (like a nandroid backup) before installing this module.
DOWNLOADS
Google-Contacts-Storage-v0.0.0-TESTING.4.zip
XDA:DevDB Information
Google Contacts Storage, Tool/Utility for the XDA Community Apps
Contributors
rfgamaral
Version Information
Status: Testing
Current Beta Version: v0.0.0-TESTING.4
Beta Release Date: 2018-08-02
Created 2018-08-01
Last Updated 2018-08-02
@rfgamaral after installing magisk module and rebooting i keep getting android.process.acore has stopped.
I cannot get rid of it. By pressing ok all the time i managed to arrive to Apps but there is no Contact Storage app to clear data/cache after the reboot.
stathis95194 said:
@rfgamaral after installing magisk module and rebooting i keep getting android.process.acore has stopped.
I cannot get rid of it. By pressing ok all the time i managed to arrive to Apps but there is no Contact Storage app to clear data/cache after the reboot.
Click to expand...
Click to collapse
I also got that error when developing this module but I never got it after installing/enabling it, only after disabling it.
For some reason, the system does not recognize the /system/priv-app/ContactsProvider/ContactsProvider.apk (although the file is there). I'm not sure how to fix this to be honest, so I recommend you restore your backup to get you back to a working state. Maybe try the whole process again (makre sure you follow every single step) and instead of rebooting the system after installing the module, reboot to recovery and wipe dalvik/ART and cache. If that doesn't help, restore the device again until a solution for this problem is found.
Like I said, I also had this problem and because I live on the edge, I didn't make a backup of my system (idiot me). I had to make the system recognize the ContactsProvider.apk file and wen into recovery, deleted, copied it back from my ROM, set proper folder/file permissions, wiped dalvik/ART and cache and rebooted, the problem was gone. I installed my module again and it worked. But I'm honestly afraid to disable it and get that error back.
Which is weird because I'm replacing this file systemlessly, that's the whole point of Magisk. Maybe I'm doing something wrong, I'm no expert... We'll probably need help from someone with more knowledge on the whole Android system. But for the record, I currently have the version available on this thread installed on my phone. I have the Pixel Experience module installed and installed Google Phone from the store, it doesn't force close and all features seem to be working. I just need to get this module stable.
@stathis95194 Were you able to restore your device? I hope so... I've uploaded a new test version, didn't change much, not sure if it fixes anything.
rfgamaral said:
@stathis95194 Were you able to restore your device? I hope so... I've uploaded a new test version, didn't change much, not sure if it fixes anything.
Click to expand...
Click to collapse
Yeap I always take a nandroid before messing with the phone. Let me try the new version and report
Sent from my HTC 10 using Tapatalk
@rfgamaral soooo after flashing 0.0.4 i faced the same issue with android.process.acore has stopped popping all the time.
This time i took a different approach and didn't restore my nandroid. Instead i dirty flashed my LeeDroid rom.
Rebooted and lo and behold, stock dialer and contacts were missing and google phone was working perfectly. No crashing on searching (nearby places is working)
Now i need to test caller id and spam filter
I will keep testing and let you know.
stathis95194 said:
@rfgamaral soooo after flashing 0.0.4 i faced the same issue with android.process.acore has stopped popping all the time.
This time i took a different approach and didn't restore my nandroid. Instead i dirty flashed my LeeDroid rom.
Rebooted and lo and behold, stock dialer and contacts were missing and google phone was working perfectly. No crashing on searching (nearby places is working)
Now i need to test caller id and spam filter
I will keep testing and let you know.
Click to expand...
Click to collapse
Awesome, glad you got it working.
Now I just need to understand why installing this module crashes android.process.acore... But it's a bummer that this is happening, a little price to pay, I guess? At least until a fix is found... That and that whole install procedure which is required to avoid other different crashes because of incompatible storages.
Hi
I'm running 2.42.400.3 on U11.
I installed this and google phone from
https://forum.xda-developers.com/android/apps-games/app-google-phone-v14-0-175904292-bubble-t3708218
Dialer kept crashing so I installed your mod.
After that,com.android .phone keeps crashing.
I unistalled it and then I got acore crashing.
I restored feom nandroid but for some reason kept getting the acore crash, so I completely uninstalled magisk.
Now.... everything works. Even the dialer.
I'm really not sure what happened but.... thanks
gunnerhk said:
Hi
I'm running 2.42.400.3 on U11.
I installed this and google phone from
https://forum.xda-developers.com/android/apps-games/app-google-phone-v14-0-175904292-bubble-t3708218
Dialer kept crashing so I installed your mod.
After that,com.android .phone keeps crashing.
I unistalled it and then I got acore crashing.
I restored feom nandroid but for some reason kept getting the acore crash, so I completely uninstalled magisk.
Now.... everything works. Even the dialer.
I'm really not sure what happened but.... thanks
Click to expand...
Click to collapse
That's really weird, on so many levels... :/
Screenshot as proof :laugh:
After updating to Magisk 17.1, when I install a new module or update an existing module, it installs successfully but after rebooting all the apps changes to default system apps, and default setting. Again i reboot, then everything comes back except that xposed framework gets deactivated along with all its modules(like gravity box etc.) then i again reboot to activate it, then again reboot to activate its modules. Thus the complete process involves 4-5 reboots to function everything back to normal. This didn't happened before. I'm using Lenovo K8 note, Android O(8.0). Any solution??