Related
So I've been running the same setup since I updated to 4.4.4 about a month ago. Stock 4.4.4 rom with Xposed framework, rooted, custom kernel, custom DPI.
This morning I wake up and my phone will boot past the boot screen and just keep giving me the "Unfortunately, the process com.android.systemui has stopped.
Does anyone have stock 4.4.4 systemui file in case mine got corrupted somehow? Or should I flash the system.img? What does the system.img change if I flash it. Will if affect my apps/data/etc?
System.img replaces everything in /system. Your data and apps are in /data
Might be worth reading the sticky threads. This is pretty basic info that you should already know if you're messing with root.
Most likely the problem will be with /data anyway
Sent from my Nexus 5 using Tapatalk
I read somewhere that Xposed might be causing it. Is there a way to disable it as I can't get to it fast enough before the systemui crashes.
Isn't there an xposed removal flashable zip in the xposed thread? I think there is.
It won't be xposed itself but it could be a module or the settings of moduke causing it, which are stored in /data.
That said, removal of xposed would be the best course to take for elimination purposes.
Sent from my Nexus 5 using Tapatalk
impruv said:
I read somewhere that Xposed might be causing it. Is there a way to disable it as I can't get to it fast enough before the systemui crashes.
Click to expand...
Click to collapse
I had this problem after flashing a new nightly version of my ROM.
http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401/post51306764
I went into safe mode, documented in the thread above. Uninstalled the xposed installer. Reinstalled the xposed installer apk. Updated Xblast tools to the latest version. Problem seems to have gone away. Will have to see what happens after I flash the next nightly, however. This might have something to do with the ROM overwriting /system
I came across this thread after Googling the issue I was having. I am also rooted, running 4.4.4 (CarbonROM on the Nexus 7 and stock on Moto X), and am running Xposed on both my Nexus 7, and on my Moto X. Suddenly last night I rebooted (first the N7, and then this morning the X), and lo and behold, System UI crashed on both.
I then restored my most recent nandroids on both (within a week), and all good again. Then updated all my apps that needed updating. Rebooted again because the Moto X froze, and again, System UI crash. That got me thinking that an app that was updated may be the culprit. So I updated each of my apps that had updates available one-by-one, and rebooted after each one. All good, until I came to Google+. When Google + updated, and then I rebooted, BOOM. System UI crash. Not sure if this is a conflict with Xposed or a coincidence, but Google + is definitely causing the issue for me. Hope this helps.
EDIT: I will try uninstalling Xposed then updating Google+, and report back.
UPDATE: After once again restoring my latest Nandroid, I uninstalled Xposed, rebooted, and updated all of my apps, including Google+. Rebooted, and all was good. I then went to re-install Xposed, and noticed that there were a few modules, XBlast, Gravity Box, and App Opps, that had updates available. I downloaded and installed the updates, then re-installed Xposed and rebooted. All is fine again.
sn2hotty said:
I came across this thread after Googling the issue I was having. I am also rooted, running 4.4.4 (CarbonROM on the Nexus 7 and stock on Moto X), and am running Xposed on both my Nexus 7, and on my Moto X. Suddenly last night I rebooted (first the N7, and then this morning the X), and lo and behold, System UI crashed on both.
I then restored my most recent nandroids on both (within a week), and all good again. Then updated all my apps that needed updating. Rebooted again because the Moto X froze, and again, System UI crash. That got me thinking that an app that was updated may be the culprit. So I updated each of my apps that had updates available one-by-one, and rebooted after each one. All good, until I came to Google+. When Google + updated, and then I rebooted, BOOM. System UI crash. Not sure if this is a conflict with Xposed or a coincidence, but Google + is definitely causing the issue for me. Hope this helps.
EDIT: I will try uninstalling Xposed then updating Google+, and report back.
UPDATE: After once again restoring my latest Nandroid, I uninstalled Xposed, rebooted, and updated all of my apps, including Google+. Rebooted, and all was good. I then went to re-install Xposed, and noticed that there were a few modules, XBlast, Gravity Box, and App Opps, that had updates available. I downloaded and installed the updates, then re-installed Xposed and rebooted. All is fine again.
Click to expand...
Click to collapse
Yea it was XBlast that caused the issue. I fixed it by disabling Xposed with the key taps, updating all the modules and then rebooting.
Alright, I know the Z5 is supposed to bootloop a few times (AndroPlus says 2-3 times in his rooting thread) before it'll boot with Xposed installed, but after installing the framework, mine just bootloops indefinitely.
I've tried several times on different firmwares (32.0.A.6.152 and 32.0.A.6.209 Customized_US) and with different Xposed versions (xposed-v79-sdk22-arm64.zip and xposed-v80-sdk22-arm64.zip). Each time, I let it bootloop 5+ times for good measure. Each bootup, it'll load the wallpaper, then load SystemUI, and then freeze shortly after, followed by a reboot. It does this perpetually and will not boot all the way. I have no Xposed modules nor the Installer installed on the phone, so there should be nothing interfering with the bootup in that regard. I have tried with the Xposed Installer installed beforehand as well.
The only other advice I've found online is a couple articles that suggest this old modified Xposed package "xposed-v74-sdk21-arm64-dl12345-UNOFFICIAL-20150929.zip" for Z3, Z4, and Z5 that bootloop when installing Xposed, but I'm hesitant to use a dated version and one that's for an older SDK as well. Plus, the threads on XDA recommend the latest Xposed version as working.
The phone is rooted, obviously, with SuperSU 2.46 and running AndroPlus kernel, which shouldn't be a problem. I do have a bunch of system apps (bloatware) that are uninstalled and some disabled, but I don't see why that would cause an issue. I honestly cannot think of anything else that would be causing this to not work. Really hoping someone here has experienced the same and knows the solution. I'm also curious: how many times have others had to let their device bootloop before successfully booting with Xposed?
neonixxx said:
Alright, I know the Z5 is supposed to bootloop a few times (AndroPlus says 2-3 times in his rooting thread) before it'll boot with Xposed installed, but after installing the framework, mine just bootloops indefinitely.
I've tried several times on different firmwares (32.0.A.6.152 and 32.0.A.6.209 Customized_US) and with different Xposed versions (xposed-v79-sdk22-arm64.zip and xposed-v80-sdk22-arm64.zip). Each time, I let it bootloop 5+ times for good measure. Each bootup, it'll load the wallpaper, then load SystemUI, and then freeze shortly after, followed by a reboot. It does this perpetually and will not boot all the way. I have no Xposed modules nor the Installer installed on the phone, so there should be nothing interfering with the bootup in that regard. I have tried with the Xposed Installer installed beforehand as well.
The only other advice I've found online is a couple articles that suggest this old modified Xposed package "xposed-v74-sdk21-arm64-dl12345-UNOFFICIAL-20150929.zip" for Z3, Z4, and Z5 that bootloop when installing Xposed, but I'm hesitant to use a dated version and one that's for an older SDK as well. Plus, the threads on XDA recommend the latest Xposed version as working.
The phone is rooted, obviously, with SuperSU 2.46 and running AndroPlus kernel, which shouldn't be a problem. I do have a bunch of system apps (bloatware) that are uninstalled and some disabled, but I don't see why that would cause an issue. I honestly cannot think of anything else that would be causing this to not work. Really hoping someone here has experienced the same and knows the solution. I'm also curious: how many times have others had to let their device bootloop before successfully booting with Xposed?
Click to expand...
Click to collapse
i have installed it 3-4 times on my phone , and every time , it only bootlooped once. but then i manually rebooted just to be sure. i dont really know what causes yours to bootloop, did you try wiping cache and dalvik after installation? does your device optimize apps on startup?
arismelachrinos said:
i have installed it 3-4 times on my phone , and every time , it only bootlooped once. but then i manually rebooted just to be sure. i dont really know what causes yours to bootloop, did you try wiping cache and dalvik after installation? does your device optimize apps on startup?
Click to expand...
Click to collapse
Thanks for the response. Yeah, I've tried wiping cache and dalvik after installing, before rebooting. It does go through optimizing every single app on the first boot after clearing cache, and doesn't on the subsequent reboots, which is just as is expected.
And I have also tried manually powering off the phone from the power dialog while it was booting, before it could freeze and bootloop itself. It made the device shut down gracefully, then I let it sit for about 15 minutes and turned it on, but the results were the same as well.
Hello all. I'll try to explain my issue with as much detail and hopefully somebody can help me.
Anyways I picked this phone up on sale on amazon and I have already unlocked the bootloader and am successfully rooted. Now I want to use Xposed. I have been trying to get it to work for 2 days now and I am fed up.
I downloaded the correct Xposed installer(SDK 24 v88.2) and it will somewhat work but then after a reboot It says it's installed but not active and it tells me to check the logs of which are blank. I am rooted the supersu way and have twrp installed.
I've read about some script I can put in the init.d folder or something like that but I cannot seem to get it to work.
I am on emui 5.0 with android 7.0.
Can someone please for the life of me help me get this to work?
I'm simply trying to use a module for my Snapchat called snaptools.
I know it's a lot to ask but can someone please help with a tutorial or a fix/instructions?
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
RedSkull23 said:
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
Click to expand...
Click to collapse
I do not have greenify installed unfortunately. I literally got this phone 2 days ago and I've never had this issue before.
I just uninstalled the SuperSU version and Installed the magisk version for root and then installed Xposed through the magisk manager and installed the modified Xposed installer apk that can see the systemless install. Xposed has survived a couple reboots and my modules are working but I fear that it will stop working as you stated before randomly. Have you tried it my way?
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
patrick8996 said:
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
Click to expand...
Click to collapse
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
RedSkull23 said:
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
Click to expand...
Click to collapse
Hmm I'm still active but I haven't restarted since I posted. I'm wondering why there isn't a more detailed thread regarding this as it seems a lot of people use this phone.
Maybe you can try fresh with magisk and the modified Xposed installer for straight systemless. I've had a hell of a lot more luck this way than I have through the regular install. It's survived 5 reboots so far. Have you tried just a soft reboot inside the Xposed installer? I mean I know it's not a full restart but it may maintain Xposed and keep it active.
Maybe because only a limited set of people are facing this. And maybe only some devices suffer this. I tried both, fresh installations of normal Xposed / systemless Xposed, both didn't survived after 2 or 3 normal reboots. Yes I always rebooted by Xposed Installer when it was installed, even because i can preserve on/off button the longest i can this way, but sometimes a soft reboot isn't sufficient to apply some modifications, so i rarely used them. I daily rebooted with normal reboots. I'll try when new versions will be available at this point, i tried actual builds for 2 weeks encountering always this error so I'm not motivated on trying them again
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
RedSkull23 said:
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
Click to expand...
Click to collapse
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
patrick8996 said:
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
Click to expand...
Click to collapse
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
RedSkull23 said:
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
Click to expand...
Click to collapse
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
patrick8996 said:
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
Click to expand...
Click to collapse
Never faced this. The framework keeps staying active actually
RedSkull23 said:
Never faced this. The framework keeps staying active actually
Click to expand...
Click to collapse
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
patrick8996 said:
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
Click to expand...
Click to collapse
V15.1 should fix everything. V15.0 was messing up thousands of phones
RedSkull23 said:
V15.1 should fix everything. V15.0 was messing up thousands of phones
Click to expand...
Click to collapse
Ya I installed 15.1 and no longer have any issues. I'm happy all has been working for this long
Sent from my BLN-L24 using Tapatalk
I have rarely had any bootloop on my previous devices, so I'm not sure if this even counts as bootloop:
An hour ago I found my Pixel 2 (stock 8.1, Magisk 14.5 unmodified, TWRP 3.1.1) restarted itself (with the internal error message it's hard to miss). So I hit OK and enter the pattern to unlock. Upon unlock it reboots and arrives at lock screen again. Another unlock would trigger another reboot, over and over.
Luckily, I had Magisk uninstaller stored on SD card so I went in recovery to flash that, which seems to have restored the backed up boot image, and the phone is properly functional again. Then I flashed Magisk and it's all fine now.
I'm not attributing this issue to Magisk but just wonder if anyone else has seen this issue before. With lock screen being properly loaded, I'm not sure if this even counts as a bootloop.
Another factor to consider is, about two hours before all this happened, I installed AdAway to modify the host file. Don't know if that could be the reason, but now I've modified the host file again, will see if this issue comes back.
I just started having the same problem about the same time. I did a complete shutdown from the lock screen and when it fully booted, it was fine overnight, but it started acting up again this morning, so I did a complete shutdown again. It hung on the shutdown screen, so I had to do the hard reboot. Doing fine again, for now. I also have Magisk and AdAway, but I'd had both of those active for a few days before this started up.
I has something similar but different happen. After updating to 8.1 with magisk, I updated my hosts with adaway. I then had it hang on shutdown (this was the first time this had happened). Hard reset and rebooted and everything seemed to be fine. I then put it on the charger overnight, only to wake up the next morning and find it in the recovery menu saying there was an error booting the system and recommending a factory reset. I ignored that and rebooted, and haven't had any other issues since, but that one was weird.
It's something to do with magisk 14.5 456 beta. I've had the same boot loops, reverted to stock boot.img and problems went away
I haven't has this issue since I posted. To be clear, the problem I had could not be solved by a hard reset - it actually reboots itself every time I try to get past the lock screen for the first time after the previous (self) reboot. It's exactly a bootloop except that the phone makes it into the OS instead of failing to boot.
It can be Magisk or Adaway, no worries. I just pray it's not a hardware issue.
Sounds like my same experience.
Stock 8.1 rooted with Magisk 14.5.
Stock recovery too.
Internal error message on boot.
I've had multiple reboots in a row, one after the other.
Stuck at shut down screen when selecting power off.
Hold down power button for hard reboot gets me back in business until this eventually happens again exactly as above.
No AdAway for me. I'm thinking it's the patched boot.img
Is there now an alternative method for rooting with Magisk other than patching the boot image and then manually flashing it?
I'm still using Magisk 14.3 on 8.1, "Flash" kernel, no issues.
I've not had this issue since I posted about it. I uninstalled one live wallpaper app, which I'm not sure did the trick or not.
froader said:
Sounds like my same experience.
Stock 8.1 rooted with Magisk 14.5.
Stock recovery too.
Internal error message on boot.
I've had multiple reboots in a row, one after the other.
Stuck at shut down screen when selecting power off.
Hold down power button for hard reboot gets me back in business until this eventually happens again exactly as above.
No AdAway for me. I'm thinking it's the patched boot.img
Is there now an alternative method for rooting with Magisk other than patching the boot image and then manually flashing it?
Click to expand...
Click to collapse
Just saw this. I didn't use patched image method, I used TWRP beta 1 to install the Magisk.
cswithxda said:
Just saw this. I didn't use patched image method, I used TWRP beta 1 to install the Magisk.
Click to expand...
Click to collapse
I'll have to try that. Thanks!
Do you also get the internal error message after a reboot?
froader said:
I'll have to try that. Thanks!
Do you also get the internal error message after a reboot?
Click to expand...
Click to collapse
Yes that's a known issue of Magisk and does not affect functionality according to the developer of Magisk.
cswithxda said:
Yes that's a known issue of Magisk and does not affect functionality according to the developer of Magisk.
Click to expand...
Click to collapse
Thanks for confirming. I wasn't sure if that was present flashing via TWRP, but makes sense that it would.
Same exact "Internal error" warning and occasional boot loop after upgrading the Pixel 2 (not XL) to 8.1 from Magisk 14.5.1456 using TWRP 3.2.1.0. Also an AdAway user. Glad to hear I didn't mess it up and it's just a quirk of the method and the alpha/beta stages. Hopefully this resolves soon as I hate guessing whether my device will go belly up at random. Seems like Flash kernel with Magisk 14.3 may be ideal - any other confirmations that this is a stable method?
I'm having this same issue as well! Using Magisk 14.5 1456, with the latest TWRP non-beta, and the Unified Hosts Adblock module. Randomly my phone goes into a soft reboot loop like your describing. If I hard reboot using power + volume up it seems to fix it for a time, then it happens again at a, seemingly, random time. It's crazily frustrating. The only other things I have that involve root are a terminal app, Drives roid, and CoSy to sync Facebook contacts. I also had Substratum using the root method, but I uninstalled that today wondering if that was the cause.
Hmm not sure if we have the same issue. In my experience, I could not solve the issue and at last only uninstalling Magisk (so the boot image reverted back to stock + TWRP) solved the issue.
cswithxda said:
Hmm not sure if we have the same issue. In my experience, I could not solve the issue and at last only uninstalling Magisk (so the boot image reverted back to stock + TWRP) solved the issue.
Click to expand...
Click to collapse
Were you able to recover from the bootloop at all without uninstalling? For me I was able to force restart it, it would be fine for a few hours then it would bootloop again.
Additionally, I uninstalled Magisk and flashed the stock boot image as well and so far it hasn't come back. I still have TWRP.
Not at all, hard reset still sees the same reboots over and over, so I had to try something. And the only thing I found was the Magisk uninstaller on the SD card lol. I then uninstalled the Magisk and reinstalled it, and the issue has not come back so far.
I'm having that boot loop. I'll try uninstalling magisk
Sent from my [device_name] using XDA-Developers Legacy app
I have 2ea Pixel 2 phones. Work one has the camera removed.
One keeps rebooting while the other does not. I had both of them set up the same.
I've read this is due to the kernel panicking if radio doesn't have signal. How true do you all think this is?
I'm almost ready to full wipe and start from scratch. I cannot RMA it since the camera is removed.
So far I've removed in order: Andromeda, Substratum, TulsaDiver Mods, and AdAway. Since removing AdAway I've not had any reboots, though the night is still young.
Any other things other than removing Magisk?
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
I have 2ea Pixel 2 phones. Work one has the camera removed.
One keeps rebooting while the other does not. I had both of them set up the same.
I've read this is due to the kernel panicking if radio doesn't have signal. How true do you all think this is?
I'm almost ready to full wipe and start from scratch. I cannot RMA it since the camera is removed.
So far I've removed in order: Andromeda, Substratum, TulsaDiver Mods, and AdAway. Since removing AdAway I've not had any reboots, though the night is still young.
Any other things other than removing Magisk?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Interesting about removing AdAway. I had a hosts adblocker as well, I wonder if that has something to do with it.
device info: xiaomi mi8 lite, unlocked bootloader, magisk root, twrp, android 10, passed safetyNet
I installed Smali Patcher and my gps completely stopped working. My real location doesn't show on google maps or any other apps that use gps. Enabling google map accuracy doesnt work either, as well as enabling/disabling mock location. Is there anything I can do? It worked completely fine before installing smali patcher. I also tried disabling smali module in magisk but nothing changed.
Not so long ago I uninstalled smali patcher module through twrp and problem still occurs
Reflash phone's Stock ROM to get rid off of all modifications you applied so far.
I flashed lineageOS and location still doesn't work... I have no clue why. I wiped everything.
jwoegerbauer said:
Reflash phone's Stock ROM to get rid off of all modifications you applied so far.
Click to expand...
Click to collapse
so I flashed my stock rom (miui) and it's working now
Idk why it didnt work with lineageos