I'm rerooting my s7 but I need every advice I can get to make sure my phone does not bootloop I was told it was becuase if you mess with the phone to much it'll go into a bootloop but I really haven't done anything to the phone when it was rooted im not saying it's wrong I'm just saying maybe it's somthing else so if someone out there has a s7 rooted and haven't run into the loop pls leave what you did in the post pls
I've rooted countless times because of the boot loops as well until I found out that the xposed module was causing it. Every since I've rooted without xposed, I haven't had a bootloop since.
officialbambam said:
I've rooted countless times because of the boot loops as well until I found out that the xposed module was causing it. Every since I've rooted without xposed, I haven't had a bootloop since.
Click to expand...
Click to collapse
I didn't find out about xposed like 3 weeks after rooting so that coudnt be the issue
TH3B0SS said:
I didn't find out about xposed like 3 weeks after rooting so that coudnt be the issue
Click to expand...
Click to collapse
I'm almost 100% sure it's the xposed module you've installed that's causing the boot loops. If I were you, I'd uninstall the xposed module and return to stock and reroot without xposed and I'm certain that's the solution to your problem.
officialbambam said:
I'm almost 100% sure it's the xposed module you've installed that's causing the boot loops. If I were you, I'd uninstall the xposed module and return to stock and reroot without xposed and I'm certain that's the solution to your problem.
Click to expand...
Click to collapse
Well like I said during the time I was rooted I didn't install xposed but I'll give it run today when I get home
officialbambam said:
I'm almost 100% sure it's the xposed module you've installed that's causing the boot loops. If I were you, I'd uninstall the xposed module and return to stock and reroot without xposed and I'm certain that's the solution to your problem.
Click to expand...
Click to collapse
I can now confirm that it was not the xposed module I'm rooted now for like 2 to 1 mouth with xposed installed
Related
I want to install Xposed Framework on my Huawei G700 with root access. But when I install it, my phone needs to reboot and then Xposed Installer says: The latest version of Xposed is currently not active. Did you install the framework and reboot?
I did the steps, the install and the full reboot, not the soft reboot. I also checked if I have really root access, and I have, so no problem about that.
I also have installed all bundles and they are all active. So what do I need to do now to get Xposed Framework working correctly?
Julian1911 said:
I want to install Xposed Framework on my Huawei G700 with root access. But when I install it, my phone needs to reboot and then Xposed Installer says: The latest version of Xposed is currently not active. Did you install the framework and reboot?
I did the steps, the install and the full reboot, not the soft reboot. I also checked if I have really root access, and I have, so no problem about that.
I also have installed all bundles and they are all active. So what do I need to do now to get Xposed Framework working correctly?
Click to expand...
Click to collapse
Hi, I've got the same phone and the same problem, did you solve it?
ouardo said:
Hi, I've got the same phone and the same problem, did you solve it?
Click to expand...
Click to collapse
I'm in the same situation. Anyone managed to get xposed working on the g700?
Edit: fixed. Disable resource hooks in the installer settings, reboot, and all is working.
jbbandos said:
I'm in the same situation. Anyone managed to get xposed working on the g700?
Edit: fixed. Disable resource hooks in the installer settings, reboot, and all is working.
Click to expand...
Click to collapse
What you mean with this fix, can you explain it step by step ?
Edit:Never mind, find it, working now
TopperBG said:
What you mean with this fix, can you explain it step by step ?
Edit:Never mind, find it, working now
Click to expand...
Click to collapse
Nice to know. Too bad Huawei doesn't follow its GPL obligations and doesn't publish the sources, it would help.
My device is huawei y625 ana i installed flat colored statusbar and no changes on my statusbar.
Xstana is working
But i wanna colored statusbar ,anyone can help plz.
You must install Xposed version 2.5, and everything will work.Sometimes, some modules will not work unless you have the latest version, so in order to fix that, install older versions of the modules you want.
I just rooted my phone through WeakSauce, turned s-off, installed SuperSU and installed TWRP. Now I installed Xposed Framework and GravityBox and occasionally my system.ui crashes. What can I do to stop these crashes?
Assuming you haven't modified much else, start by turning off some of the Gravity Box tweaks you've used. Or, turn them all off. Might be something in there causing it. If the problem goes away, start enabling one or two at a time until you find the one causing the problem.
robocuff said:
Assuming you haven't modified much else, start by turning off some of the Gravity Box tweaks you've used. Or, turn them all off. Might be something in there causing it. If the problem goes away, start enabling one or two at a time until you find the one causing the problem.
Click to expand...
Click to collapse
Thanks, I'll try that
oFumbleSo said:
I just rooted my phone through WeakSauce, turned s-off, installed SuperSU and installed TWRP. Now I installed Xposed Framework and GravityBox and occasionally my system.ui crashes. What can I do to stop these crashes?
Click to expand...
Click to collapse
You shouldn't use gravity box on a stock ROM. Use sense 6 toolbox. That could be causing your issue.
oFumbleSo said:
I just rooted my phone through WeakSauce, turned s-off, installed SuperSU and installed TWRP. Now I installed Xposed Framework and GravityBox and occasionally my system.ui crashes. What can I do to stop these crashes?
Click to expand...
Click to collapse
sent from my Red HTC M8 using Tapatalk because all Xda apps f/c ?
Hey,
I've got a rooted Nexus which won't start anymore. It has been rooted for months and everything worked fine so far. I've installed a lot of root apps like the Xposed Framework, Titanium Backup and App Ops. The last Rom I had on it was the Stock Android 4.4.3. After running without any problems and me making no modifications, suddenly it stopped working. First, the System UI kept crashing after max. 1 second of running. Now, it won't even get past the boot screen. I think, it is a problem with a Xposed Framework module of which I have a lot installed (I remember XBlast, GravityBox and Wanam but there were more (propably around 10). Is there a way to disable the Xposed modules? Another problem is, that I don't know, if I accidently updated to KitKat 4.4.4 what could've caused those problems.
I hope, you can help me.
Stefan
Stefan Baumann said:
Hey,
I've got a rooted Nexus which won't start anymore. It has been rooted for months and everything worked fine so far. I've installed a lot of root apps like the Xposed Framework, Titanium Backup and App Ops. The last Rom I had on it was the Stock Android 4.4.3. After running without any problems and me making no modifications, suddenly it stopped working. First, the System UI kept crashing after max. 1 second of running. Now, it won't even get past the boot screen. I think, it is a problem with a Xposed Framework module of which I have a lot installed (I remember XBlast, GravityBox and Wanam but there were more (propably around 10). Is there a way to disable the Xposed modules? Another problem is, that I don't know, if I accidently updated to KitKat 4.4.4 what could've caused those problems.
I hope, you can help me.
Stefan
Click to expand...
Click to collapse
I think it's xblast.
Just flash the disabler zip via recovery. Its attached in the Xposed thread:
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
rootSU said:
I think it's xblast.
Just flash the disabler zip via recovery. Its attached in the Xposed thread:
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Click to expand...
Click to collapse
You can repetitively press the volume keys during boot and eventually it'll vibrate every time you do. What it does is add a folder "disabled" in Xposed's data and disables it. No need to push and flash lol. Was implemented a while ago as an easier alternative
Lethargy said:
You can repetitively press the volume keys during boot and eventually it'll vibrate every time you do. What it does is add a folder "disabled" in Xposed's data and disables it. No need to push and flash lol. Was implemented a while ago as an easier alternative
Click to expand...
Click to collapse
Cool. I haven't seen this anywhere
rootSU said:
Cool. I haven't seen this anywhere
Click to expand...
Click to collapse
I think it was in the Q&A thread for Xposed lol
Since nobody knows how to use adb to push
Lethargy said:
You can repetitively press the volume keys during boot and eventually it'll vibrate every time you do. What it does is add a folder "disabled" in Xposed's data and disables it. No need to push and flash lol. Was implemented a while ago as an easier alternative
Click to expand...
Click to collapse
I tried that several times now and it doesn't seem to work. During boot, i repetitively pressed the volume keys as you told me until it vibrated a bit. Then, the boot took a lot longer than usual but it didn't change anything - the com.android.systemui process is still crashing.
Stefan Baumann said:
I tried that several times now and it doesn't seem to work. During boot, i repetitively pressed the volume keys as you told me until it vibrated a bit. Then, the boot took a lot longer than usual but it didn't change anything - the com.android.systemui process is still crashing.
Click to expand...
Click to collapse
Try what @rootSU said then. If that doesn't work either then its not because of Xposed.
Lethargy said:
Try what @rootSU said then. If that doesn't work either then its not because of Xposed.
Click to expand...
Click to collapse
Ok, it seems I did the button pressing the wrong way. After looking at the thread posted by rootSU and especially at this post I was able to do it (I pressed both volume buttons repetitively instead of just one). So, now I was able to boot the Nexus - what next?
Disable all your modules and re-enable Xposed with the instructions of that post. Reboot to see if its Xposed itself causing the issue. If it boots up then enable them one by one and reboot each time. One will be the culprit.
Lethargy said:
Disable all your modules and re-enable Xposed with the instructions of that post. Reboot to see if its Xposed itself causing the issue. If it boots up then enable them one by one and reboot each time. One will be the culprit.
Click to expand...
Click to collapse
Ok, I disabled all of them and it booted now . I saw, that there are a lot of updates for my available (xposed installer, app settings, burnt toast, customshare, gravitybox, holo themer, wanam, xblast, xposed additions and youtube adaway). Should I install those before reactivating the modules?
Up to you
Lethargy said:
Up to you
Click to expand...
Click to collapse
Ok, I updated all the modules, enabled them one by one (with a restart after every one) and now, everything is working again. Thank you very much for your help :good:.
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